File menu item with open, save, publish commands semi-functional. Als…

…o added comments.

and down the rabbit hole we go: I saw your comments but let's keep this out in the open more in the issue queue at large - https://github.com/elmsln/issues/issues/new


add unittests with 'spidermonkey'...

It seems that there are only two out-dated packages available:

https://pypi.python.org/pypi/python-spidermonkey/ last release from: 2011-02-17
https://pypi.python.org/pypi/pydermonkey/ last release from: 2009-09-11

Maybe a better idea is to use selenium with a minimal webpage and the heavy usage of webdriver.execute_script() ?

I was thinking of just running them directly in the spidermonkey command-line shell, i.e. plain javascript tests without a python runner around them.  But it's probably too much hassle to be worth setting that up, and a combination of running under nodejs shell and in a browser via selenium will give pretty solid coverage.


1.2.4 gradle release

Hello, will be gradle repo available for 1.2.4 release?

I have an error for version 1.2.3 and 1.2.4 that say that doesn't exits

Yup, because these releases are not pushed to maven repo. You could try jitpack.io but I have had problems with building so idk if you can make it.

@rafalzawadzki  @Spiderbezno  It's available now. Sorry for lately.

@akexorcist thanks, 1.2.3 is syncing ok with gradle. Will release 1.2.4 be available too? It has important commit that fixes a bug which crashes my app for a bunch of users ;)

@rafalzawadzki  try 1.2.5

@akexorcist 1.2.5 works fine, but the bug mentioned here: https://github.com/akexorcist/Android-RoundCornerProgressBar/issues/24 still exists but it was fixed with 1.2.4 commit. Am I missing something?

I've update gradle to 1.3.1 on version 2.0.2. If you have any problem about gradle version, please create new issue.
Thank you


Can't read from 2017 games

After managing to set my schedule up for 2017 games, I'm still having trouble reading 2017 regular season games. Getting the following error, just trying to get basic info that you had from issue #331  :
I updated nflgame and made sure to update the schedule as well as switch it back. Any idea?
Code:
import nflgame
import csv
games = nflgame.games(2017)
print len(games)
Error:
TypeError                                 Traceback (most recent call last)
 in ()
2 import csv
3
----> 4 games = nflgame.games(2017)
5 print len(games)
C:\Program Files\Anaconda2\lib\site-packages\nflgame_init_.pyc in games(year, week, home, away, kind, started)
227     (as opposed to waiting for a 404 error from NFL.com).
228     """
--> 229     return list(games_gen(year, week, home, away, kind, started))
230
231
TypeError: 'NoneType' object is not iterable

had to add the following to the statement
games = nflgame.games(2017, kind = 'REG')

Not sure why that would do anything different for you...'REG' is the default value for kind.
https://github.com/BurntSushi/nflgame/blob/master/nflgame/__init__.py#L192

I'm not sure, It was something that ended up happening last year where I had trouble getting individual postseason games and since then I've had some problems, but that seemed to be the solution that worked.


OCIS web downloads fail

I have an OCIS deployment running on macos. I recently upgraded from a 5.0 alpha to 5.0.5 by replacing the binary and adding the needed OCIS_SERVICE_ACCOUNT and OCIS_SERVICE_ACCOUNT_SECRET env vars.
When I attempt to download a file from the web, I get a standard apache web authentication dialogue. Clicking "cancel" results in a 0b file. Very odd.
Below is the terminal output from the server. The relevant messages seem to be "proxy error signature match" "Could not get user by claim"
server:~ user$ sudo /opt/ocis.sh
Password:
2024/07/04 14:49:21 ERROR failed to set GOMEMLIMIT package=github.com/KimMachineGun/automemlimit/memlimit error="failed to set GOMEMLIMIT: cgroups is not supported on this system"

{"level":"error","service":"thumbnails","time":"2024-07-04T14:49:37-04:00","message":"resource info is missing checksum"}
{"level":"error","service":"thumbnails","time":"2024-07-04T14:50:01-04:00","message":"resource info is missing checksum"}
^C{"level":"error","service":"auth-machine","server":"auth-machine","time":"2024-07-04T14:50:59-04:00","message":"Shutting down server"}
server:~ user$ sudo /opt/ocis.sh
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 6m34.175197s","authenticator":"oidc","path":"/ocs/v1.php/cloud/user","time":"2024-07-04T15:01:06-04:00","message":"failed to authenticate the request"}
2024/07/04 18:15:51 http: TLS handshake error from <IP_ADDRESS>:43714: unexpected EOF
2024/07/04 18:52:48 http: TLS handshake error from <IP_ADDRESS>:43034: unexpected EOF
2024/07/04 18:52:49 http: TLS handshake error from <IP_ADDRESS>:45388: tls: unsupported SSLv2 handshake received
2024/07/04 18:53:20 http: TLS handshake error from <IP_ADDRESS>:43676: tls: first record does not look like a TLS handshake
2024/07/04 18:53:20 http: TLS handshake error from <IP_ADDRESS>:43680: tls: unsupported SSLv2 handshake received
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55478: tls: no cipher suite supported by both client and server
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55522: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55494: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55508: tls: no cipher suite supported by both client and server
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55512: tls: unsupported SSLv2 handshake received
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55536: tls: no cipher suite supported by both client and server
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55530: tls: client offered only unsupported versions: []
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55548: EOF
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55572: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55556: tls: client offered only unsupported versions: [302 301]
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55602: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55612: tls: client offered only unsupported versions: [302 301]
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55586: tls: no cipher suite supported by both client and server
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55584: EOF
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55628: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55650: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55634: EOF
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55644: EOF
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55660: EOF
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55670: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55676: tls: no cipher suite supported by both client and server
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55698: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55682: EOF
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55712: tls: client offered only unsupported versions: []
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55736: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55714: read tcp <IP_ADDRESS>:9200-><IP_ADDRESS>:55714: read: connection reset by peer
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55726: EOF
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55752: tls: no cipher suite supported by both client and server
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55790: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55784: tls: no cipher suite supported by both client and server
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55768: read tcp <IP_ADDRESS>:9200-><IP_ADDRESS>:55768: read: connection reset by peer
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55804: tls: no cipher suite supported by both client and server
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55820: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55810: EOF
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55816: EOF
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55836: tls: no cipher suite supported by both client and server
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55852: tls: client offered only unsupported versions: [301]
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55840: EOF
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55842: EOF
2024/07/04 18:53:31 http: TLS handshake error from <IP_ADDRESS>:55866: tls: no cipher suite supported by both client and server
2024/07/04 18:53:32 http: TLS handshake error from <IP_ADDRESS>:55878: EOF
2024/07/04 18:53:32 http: TLS handshake error from <IP_ADDRESS>:55874: read tcp <IP_ADDRESS>:9200-><IP_ADDRESS>:55874: read: connection reset by peer
2024/07/04 18:53:32 http: TLS handshake error from <IP_ADDRESS>:55882: tls: client offered only unsupported versions: [302 301]
2024/07/04 18:53:32 http: TLS handshake error from <IP_ADDRESS>:55892: tls: no cipher suite supported by both client and server
2024/07/04 18:53:32 http: TLS handshake error from <IP_ADDRESS>:55904: tls: no cipher suite supported by both client and server
2024/07/04 18:53:32 http: TLS handshake error from <IP_ADDRESS>:55906: tls: no cipher suite supported by both client and server
2024/07/04 18:53:32 http: TLS handshake error from <IP_ADDRESS>:55910: tls: no cipher suite supported by both client and server
2024/07/04 18:53:32 http: TLS handshake error from <IP_ADDRESS>:55912: EOF
2024/07/04 18:53:33 http: TLS handshake error from <IP_ADDRESS>:55916: EOF
2024/07/04 18:53:33 http: TLS handshake error from <IP_ADDRESS>:55930: EOF
2024/07/04 18:53:52 http: TLS handshake error from <IP_ADDRESS>:55938: EOF
2024/07/04 21:37:26 http: TLS handshake error from <IP_ADDRESS>:36566: tls: first record does not look like a TLS handshake
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 11.009796s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T00:01:46-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 1.004269s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T00:06:47-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 1.014154s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T00:11:48-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 1.188557s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T00:16:49-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 1.089392s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T00:21:50-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 82.802ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T00:26:50-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 61.37ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T00:31:50-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 64.624ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T00:36:50-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 28.911181s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T00:42:18-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 28.979087s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T00:47:47-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 910.388ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T00:52:48-04:00","message":"failed to authenticate the request"}
2024/07/05 00:53:45 http: TLS handshake error from <IP_ADDRESS>:15668: EOF
2024/07/05 00:53:45 http: TLS handshake error from <IP_ADDRESS>:15672: EOF
2024/07/05 00:53:45 http: TLS handshake error from <IP_ADDRESS>:15678: EOF
2024/07/05 00:53:46 http: TLS handshake error from <IP_ADDRESS>:15688: EOF
2024/07/05 00:53:46 http: TLS handshake error from <IP_ADDRESS>:15698: EOF
2024/07/05 00:53:46 http: TLS handshake error from <IP_ADDRESS>:15706: tls: client offered only unsupported versions: [302 301]
2024/07/05 00:53:47 http: TLS handshake error from <IP_ADDRESS>:15712: read tcp <IP_ADDRESS>:9200-><IP_ADDRESS>:15712: read: connection reset by peer
2024/07/05 00:53:47 http: TLS handshake error from <IP_ADDRESS>:15718: EOF
2024/07/05 00:53:48 http: TLS handshake error from <IP_ADDRESS>:15732: EOF
2024/07/05 00:53:48 http: TLS handshake error from <IP_ADDRESS>:15740: read tcp <IP_ADDRESS>:9200-><IP_ADDRESS>:15740: read: connection reset by peer
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 8m46.80277s","authenticator":"oidc","path":"/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$945e05c8-29f8-4c72-8938-f69cf932434c/","time":"2024-07-05T13:13:10-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 1.625859s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:17:07-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 625.134ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:22:07-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 612.522ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:27:07-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 616.105ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:32:07-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 2h12m13.869805s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T13:35:46-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 1.611435s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:37:08-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 20m21.493123s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T13:38:31-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"could not authenticate with username and password user: xdXOt13JKxym1B1QcEncf2XDkLAexMBFwiT9j6EfhhHFJhs2KM9jbjTmf8JBXE69, got code: 6","authenticator":"basic","path":"/index.php/apps/oauth2/api/v1/token","time":"2024-07-05T13:38:34-04:00","message":"failed to authenticate request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 764.924ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:42:08-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 7.591843s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:47:15-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 3m14.548072s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:48:59-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 10m3.206491s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:50:50-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 578.928ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:52:15-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 11.36522s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:54:11-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 566.163ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T13:57:15-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 5m24.820108s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:01:14-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 2m36.755192s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T14:01:47-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 553.545ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:02:15-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 1.554504s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:07:16-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 526.506ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:12:16-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 6m37.924829s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:13:24-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 626.171ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:17:16-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 620.041ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:22:16-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 5m48.989419s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T14:24:13-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"could not authenticate with username and password user: xdXOt13JKxym1B1QcEncf2XDkLAexMBFwiT9j6EfhhHFJhs2KM9jbjTmf8JBXE69, got code: 6","authenticator":"basic","path":"/index.php/apps/oauth2/api/v1/token","time":"2024-07-05T14:24:27-04:00","message":"failed to authenticate request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 704.119ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:27:16-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 27.966024s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T14:30:25-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 6.125855s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:32:22-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 23h39m57.817931s","authenticator":"oidc","path":"/ocs/v1.php/cloud/user","time":"2024-07-05T14:34:29-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 9.928407s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T14:35:35-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 104.99ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:37:22-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 9.911929s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T14:40:45-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 169.162ms","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T14:42:22-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 9.887026s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T14:45:55-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 102.413ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:47:22-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 9.858628s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T14:51:05-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 101.826ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:52:22-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 9.929571s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T14:56:15-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 1.163565s","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T14:57:23-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 20m59.931781s","authenticator":"oidc","path":"/ocs/v1.php/cloud/user","time":"2024-07-05T15:00:29-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"thumbnails","time":"2024-07-05T15:00:31-04:00","message":"resource info is missing checksum"}
{"level":"error","service":"proxy","error":"signature mismatch: expected ff668c9da4aaba1813abc08f580309bc71f12c44d4ebf52270699c146bfecd08 != actual 871840de192d05190f12f45c002713643a98459acf388234c3934216695b95fa","authenticator":"signed_url","path":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg","url":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg?OC-Credential=peter&OC-Date=2024-07-05T19%3A00%3A47.841Z&OC-Expires=1200&OC-Verb=GET&OC-Algo=PBKDF2%2F10000-SHA512&OC-Signature=871840de192d05190f12f45c002713643a98459acf388234c3934216695b95fa","time":"2024-07-05T15:00:47-04:00","message":"Could not get user by claim"}
{"level":"error","service":"proxy","error":"signature mismatch: expected ff668c9da4aaba1813abc08f580309bc71f12c44d4ebf52270699c146bfecd08 != actual 871840de192d05190f12f45c002713643a98459acf388234c3934216695b95fa","authenticator":"signed_url","path":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg","url":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg?OC-Credential=peter&OC-Date=2024-07-05T19%3A00%3A47.841Z&OC-Expires=1200&OC-Verb=GET&OC-Algo=PBKDF2%2F10000-SHA512&OC-Signature=871840de192d05190f12f45c002713643a98459acf388234c3934216695b95fa","time":"2024-07-05T15:00:59-04:00","message":"Could not get user by claim"}
{"level":"error","service":"proxy","error":"signature mismatch: expected c4653f64ba11ee03859924b228bdd6640f744fd92b2a6aa708bb4d6576b706d1 != actual f00c4a8f592f15244db6ff22ecfe4f7d1d55b646029c0f7be9ef93fb840a8492","authenticator":"signed_url","path":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg","url":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg?OC-Credential=peter&OC-Date=2024-07-05T19%3A01%3A12.169Z&OC-Expires=1200&OC-Verb=GET&OC-Algo=PBKDF2%2F10000-SHA512&OC-Signature=f00c4a8f592f15244db6ff22ecfe4f7d1d55b646029c0f7be9ef93fb840a8492","time":"2024-07-05T15:01:12-04:00","message":"Could not get user by claim"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 9.905443s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T15:01:25-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"signature mismatch: expected c4653f64ba11ee03859924b228bdd6640f744fd92b2a6aa708bb4d6576b706d1 != actual f00c4a8f592f15244db6ff22ecfe4f7d1d55b646029c0f7be9ef93fb840a8492","authenticator":"signed_url","path":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg","url":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg?OC-Credential=peter&OC-Date=2024-07-05T19%3A01%3A12.169Z&OC-Expires=1200&OC-Verb=GET&OC-Algo=PBKDF2%2F10000-SHA512&OC-Signature=f00c4a8f592f15244db6ff22ecfe4f7d1d55b646029c0f7be9ef93fb840a8492","time":"2024-07-05T15:01:41-04:00","message":"Could not get user by claim"}
{"level":"error","service":"thumbnails","time":"2024-07-05T15:02:13-04:00","message":"resource info is missing checksum"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 156.845ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T15:02:23-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"thumbnails","time":"2024-07-05T15:02:52-04:00","message":"resource info is missing checksum"}
{"level":"error","service":"proxy","error":"signature mismatch: expected e1a89a6ef74e1f0e54f83e74afd2341ce3a717bd0254406a31af4c8bfa891ef8 != actual dd65deb323490dc41a5c3ef61b1db7ceba9c1d9a66484384fc26b013ce5d998b","authenticator":"signed_url","path":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg","url":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg?OC-Credential=peter&OC-Date=2024-07-05T19%3A03%3A09.684Z&OC-Expires=1200&OC-Verb=GET&OC-Algo=PBKDF2%2F10000-SHA512&OC-Signature=dd65deb323490dc41a5c3ef61b1db7ceba9c1d9a66484384fc26b013ce5d998b","time":"2024-07-05T15:03:09-04:00","message":"Could not get user by claim"}
{"level":"error","service":"proxy","error":"signature mismatch: expected e1a89a6ef74e1f0e54f83e74afd2341ce3a717bd0254406a31af4c8bfa891ef8 != actual dd65deb323490dc41a5c3ef61b1db7ceba9c1d9a66484384fc26b013ce5d998b","authenticator":"signed_url","path":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg","url":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/folder/file.jpg?OC-Credential=peter&OC-Date=2024-07-05T19%3A03%3A09.684Z&OC-Expires=1200&OC-Verb=GET&OC-Algo=PBKDF2%2F10000-SHA512&OC-Signature=dd65deb323490dc41a5c3ef61b1db7ceba9c1d9a66484384fc26b013ce5d998b","time":"2024-07-05T15:03:12-04:00","message":user}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 9.892711s","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-05T15:06:35-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 145.533ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-05T15:07:23-04:00","message":"failed to authenticate the request"}

We had a bug in the signed urls in 5.0.0
That can cause old presigned URLs before the upgrade to fail.
Restart should fix everything.

I am just assuming the upgrade path for the precompiled binaries is to swap out the binary, but if there are more steps I'd be grateful for a point in the right direction.

Your asssuption is correct. When we need manual interaction, we would mention that in the release notes.

I also tried 6.1.0. Using Web, I can upload and delete files, but not download them. Thumbnails don't work. I also can't replace the logo for some reason-it acts like it is replaced, but doesn't work.
server:~ user$ sudo /opt/ocis.sh
2024/07/08 12:08:54 ERROR failed to set GOMEMLIMIT package=github.com/KimMachineGun/automemlimit/memlimit error="failed to set GOMEMLIMIT: cgroups is not supported on this system"
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 650.633ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-08T12:11:36-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"thumbnails","time":"2024-07-08T12:15:40-04:00","message":"resource info is missing checksum"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 635.751ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-08T12:16:36-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 798.423ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-08T12:21:36-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 7m30.517866s","authenticator":"oidc","path":"/ocs/v2.php/apps/notifications/api/v1/notifications/sse","time":"2024-07-08T12:25:38-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: token is expired by 797.045ms","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-08T12:26:36-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"thumbnails","time":"2024-07-08T12:27:02-04:00","message":"resource info is missing checksum"}
{"level":"error","service":"proxy","error":"signature mismatch: expected 9d9a8f09b314ef3e30986eabc76a125a049778706ce31a31ca57f0a2d47a3e93 != actual bb1980114cf83897b2343ff5ced09758bd6f5de95ebfc2a623b61bab58a3d8e7","authenticator":"signed_url","path":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/DSCF2003.JPG","url":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/DSCF2003.JPG?OC-Credential=peter&OC-Date=2024-07-08T16%3A27%3A33.388Z&OC-Expires=1200&OC-Verb=GET&OC-Algo=PBKDF2%2F10000-SHA512&OC-Signature=bb1980114cf83897b2343ff5ced09758bd6f5de95ebfc2a623b61bab58a3d8e7","time":"2024-07-08T12:27:33-04:00","message":"Could not get user by claim"}
{"level":"error","service":"proxy","error":"signature mismatch: expected 9d9a8f09b314ef3e30986eabc76a125a049778706ce31a31ca57f0a2d47a3e93 != actual bb1980114cf83897b2343ff5ced09758bd6f5de95ebfc2a623b61bab58a3d8e7","authenticator":"signed_url","path":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/DSCF2003.JPG","url":"/remote.php/dav/spaces/dc0b96eb-74ac-49aa-bbf4-fe3415810fd7$4c7bc07e-8526-454b-ad2c-fc28654b26a9/DSCF2003.JPG?OC-Credential=peter&OC-Date=2024-07-08T16%3A27%3A33.388Z&OC-Expires=1200&OC-Verb=GET&OC-Algo=PBKDF2%2F10000-SHA512&OC-Signature=bb1980114cf83897b2343ff5ced09758bd6f5de95ebfc2a623b61bab58a3d8e7","time":"2024-07-08T12:27:34-04:00","message":"Could not get user by claim"}
{"level":"error","service":"thumbnails","time":"2024-07-08T12:27:44-04:00","message":"resource info is missing checksum"}
{"level":"error","service":"thumbnails","time":"2024-07-08T12:27:59-04:00","message":"resource info is missing checksum"}
{"level":"error","service":"thumbnails","time":"2024-07-08T12:28:00-04:00","message":"resource info is missing checksum"}

Something seems to be really broken.
Seems that all access tokens and signatures are invalid.

@ScharfViktor could you try reproduce that?

Something seems to be really broken.
Seems that all access tokens and signatures are invalid.

My prior version was 5.0.0-rc.5. When I switch back to that binary, everything works fine. I haven't tried starting fresh but am hoping to avoid that...

@ScharfViktor could you try reproduce that?

hm, I couldn't reproduce it. I tried to switch ocis between ocis-5.0.5-darwin-arm64 and cis-6.1.0-darwin-amd64
with envs:
export OCIS_URL=https://ocis-server:9200
export PROXY_HTTP_ADDR=<IP_ADDRESS>:9200
export PROXY_TLS=true
export OCIS_INSECURE=true
export OCIS_LOG_LEVEL=error
export OCIS_CONFIG_DIR=/Users/scharfviktor/.ocis-test/config
export OCIS_BASE_DATA_PATH=/Users/scharfviktor/.ocis-test
export PROXY_ENABLE_BASIC_AUTH=true
export OCIS_SERVICE_ACCOUNT_ID=uuid
export OCIS_SERVICE_ACCOUNT_SECRET=test

works fine to me. I can download files and view thumbnails

@ScharfViktor could you try reproduce that?

hm, I couldn't reproduce it. I tried to switch ocis between ocis-5.0.5-darwin-arm64 and cis-6.1.0-darwin-amd64 with envs:
export OCIS_URL=https://ocis-server:9200
export PROXY_HTTP_ADDR=<IP_ADDRESS>:9200
export PROXY_TLS=true
export OCIS_INSECURE=true
export OCIS_LOG_LEVEL=error
export OCIS_CONFIG_DIR=/Users/scharfviktor/.ocis-test/config
export OCIS_BASE_DATA_PATH=/Users/scharfviktor/.ocis-test
export PROXY_ENABLE_BASIC_AUTH=true
export OCIS_SERVICE_ACCOUNT_ID=uuid
export OCIS_SERVICE_ACCOUNT_SECRET=test

works fine to me. I can download files and view thumbnails

Steps to reproduce would be to initialize storage with 5.0.0-rc5 and go from there

Steps to reproduce would be to initialize storage with 5.0.0-rc5 and go from there

works also if I upgrade ocis from ocis-5.0.0-rc.5-darwin-amd64 to cis-6.1.0-darwin-amd64

Steps to reproduce would be to initialize storage with 5.0.0-rc5 and go from there

also works if I upgrade ocis from ocis-5.0.0-rc.5-darwin-amd64 to cis-6.1.0-darwin-amd64

Strange. Well, I appreciate you guys looking into it. Unless there's anything else you can think of that would cause this to happen, I'm willing to try it. Otherwise I guess I will start over with a fresh install.

I would not start with a fresh system. There seems to be a problem which I would suggest to find.
Maybe related to the bare metal setup. We don’t have a lot of these. And MacOS is also very rare.

I would not start with a fresh system. There seems to be a problem which I would suggest to find. Maybe related to the bare metal setup. We don’t have a lot of these. And MacOS is also very rare.

Yes, I have a WOPI deployment in a Docker container in a VMware VM that we use for some things. For large files we have this other bare metal setup. I am using the shell script you see above and then a plist LaunchDaemon to keep it running. All in all it was very simple to set up-much easier than getting Docker working on a Mac.
Below is my apache config, which hasn't changed.
<VirtualHost *:80>
	ServerName files1.<redacted>.com
	DocumentRoot /opt/www/files1.<redacted>.com/
	ErrorLog "/opt/local/var/log/apache2/error_log"
	CustomLog "/opt/local/var/log/apache2/default.access_log" common
	CustomLog "/opt/local/var/log/apache2/access_log" vcommon
	CustomLog "/opt/local/var/log/apache2/extended_log" vuser
</VirtualHost>

<VirtualHost *:443>
  ServerName files1.<redacted>.com

  SSLProxyEngine on
  SSLProxyVerify none
  SSLProxyCheckPeerCN off
  SSLProxyCheckPeerName off
  SSLProxyCheckPeerExpire off

  ProxyPass / https://localhost:9200/
  ProxyPassReverse / https://localhost:9200/
  ProxyPreserveHost on

  SSLCertificateFile /opt/local/etc/letsencrypt/live/files1.<redacted>.com/fullchain.pem
  SSLCertificateKeyFile /opt/local/etc/letsencrypt/live/files1.<redacted>.com/privkey.pem

  Include /opt/local/etc/letsencrypt/options-ssl-apache.conf
  #SSLOpenSSLConfCmd DHParameters /opt/local/etc/letsencrypt/ssl-dhparams.pem

  ErrorLog "/opt/local/var/log/apache2/files1_error_log"
  CustomLog "/opt/local/var/log/apache2/files1_access_log" vcommon

</VirtualHost>

Were there any changes to ocis.yaml between 5.0.0-rc5 and 5.0.5? Or anything there or in the env vars I should play with?
Thanks again.

I would not start with a fresh system. There seems to be a problem which I would suggest to find. Maybe related to the bare metal setup. We don’t have a lot of these. And MacOS is also very rare.

As a troubleshooting step I did the following:

Fresh install using ./ocis init
Run server ./ocis server

2024/07/10 02:44:23 ERROR failed to set GOMEMLIMIT package=github.com/KimMachineGun/automemlimit/memlimit error="failed to set GOMEMLIMIT: cgroups is not supported on this system"

{"level":"info","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"Migrating spaces directory structure..."}
{"level":"info","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"Migrating space types indexes..."}
{"level":"info","root":"<redacted>/ocis1/storage/metadata","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"Migrating to messagepack metadata backend..."}
{"level":"info","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"done."}
{"level":"warn","error":"open <redacted>/ocis1/storage/metadata/indexes/by-user-id: no such file or directory","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"error listing user indexes"}
{"level":"warn","error":"open <redacted>/ocis1/storage/metadata/indexes/by-group-id: no such file or directory","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"error listing group indexes"}
{"level":"info","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"done."}
{"level":"info","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"done."}
{"level":"info","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"Migrating spaces directory structure..."}
{"level":"info","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"Migrating space types indexes..."}
{"level":"info","root":"<redacted>/ocis1/storage/users","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"Migrating to messagepack metadata backend..."}
{"level":"info","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"done."}
{"level":"warn","error":"open <redacted>/ocis1/storage/users/indexes/by-user-id: no such file or directory","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"error listing user indexes"}
{"level":"warn","error":"open <redacted>/ocis1/storage/users/indexes/by-group-id: no such file or directory","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"error listing group indexes"}
{"level":"info","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"done."}
{"level":"info","time":"2024-07-10T02:44:25-04:00","caller":"github.com/cs3org/reva/v2@v2.21.0/pkg/storage/utils/decomposedfs/decomposedfs.go:183","message":"done."}
{"level":"error","service":"proxy","error":"not found","service":"com.owncloud.web.idp","time":"2024-07-10T02:44:27-04:00","message":"could not select service from the registry"}
2024/07/10 02:44:27 http: proxy error: unsupported protocol scheme ""
{"level":"error","service":"proxy","error":"failed to verify access token: 502 Bad Gateway: ","authenticator":"oidc","path":"/graph/v1.0/me/drives","time":"2024-07-10T02:44:27-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"not found","service":"com.owncloud.web.idp","time":"2024-07-10T02:44:27-04:00","message":"could not select service from the registry"}
2024/07/10 02:44:27 http: proxy error: unsupported protocol scheme ""
{"level":"error","service":"proxy","error":"could not authenticate with username and password user: xdXOt13JKxym1B1QcEncf2XDkLAexMBFwiT9j6EfhhHFJhs2KM9jbjTmf8JBXE69, got code: 6","authenticator":"basic","path":"/index.php/apps/oauth2/api/v1/token","time":"2024-07-10T02:44:27-04:00","message":"failed to authenticate request"}
{"level":"error","service":"proxy","error":"failed to verify access token: crypto/rsa: verification error","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-10T02:44:30-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: crypto/rsa: verification error","authenticator":"oidc","path":"/remote.php/webdav/","time":"2024-07-10T02:44:34-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: crypto/rsa: verification error","authenticator":"oidc","path":"/ocs/v1.php/cloud/capabilities","time":"2024-07-10T02:44:43-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: crypto/rsa: verification error","authenticator":"oidc","path":"/api/v0/settings/roles-list","time":"2024-07-10T02:44:43-04:00","message":"failed to authenticate the request"}
{"level":"error","service":"proxy","error":"failed to verify access token: crypto/rsa: verification error","authenticator":"oidc","path":"/graph/v1.0/me","time":"2024-07-10T02:44:43-04:00","message":"failed to authenticate the request"}
^C{"level":"error","service":"groups","server":"groups","time":"2024-07-10T02:47:09-04:00","message":"Shutting down server"}

Seems to be working fine, thumbnails are working.

Compare the ocis.yaml to the one generated by 5.0.0-rc5

I notice the following new sections: collaboration, ocm, and activitylogs. Do any of these need to be added to the yaml generated by 5.0.0-rc5?

I experience similar issues with bare metal install under Linux.
Using ocis 5.0.5 or below I'm able to download files via oCIS Web, but using version 6.0.0 or 6.1.0 each download via web interface ends in a signature mismatch error.
{"level":"error","service":"proxy","error":"signature mismatch: expected 65bca42caf193a6e85131121e395ec1b93dfdf03499e2b69c8e43f2635704cff != actual 44a89a472b67fc1d59dc2716c53cfee24a7ca86cf4c41fb2da23acf56e136149","authenticator":"signed_url","path":"/remote.php/dav/spaces/f2528657-cfb9-4ce7-af08-805a4bb9fae1$4c49c1a8-4e31-1030-8639-1f621ceb306f/Windows Test.xlsx","url":"/remote.php/dav/spaces/f2528657-cfb9-4ce7-af08-805a4bb9fae1$4c49c1a8-4e31-1030-8639-1f621ceb306f/Windows%20Test.xlsx?OC-Credential=tschaaf&OC-Date=2024-07-10T14%3A46%3A32.788Z&OC-Expires=1200&OC-Verb=GET&OC-Algo=PBKDF2%2F10000-SHA512&OC-Signature=44a89a472b67fc1d59dc2716c53cfee24a7ca86cf4c41fb2da23acf56e136149","time":"2024-07-10T14:46:32Z","message":"Could not get user by claim"}

WebDAV seems unaffected I can also open a picture in the preview or use OnlyOffice via WOPI.
External LDAP provider is used for user authentication.

I experience similar issues with bare metal install under Linux. Using ocis 5.0.5 or below I'm able to download files via oCIS Web, but using version 6.0.0 or 6.1.0 each download via web interface ends in a signature mismatch error.
{"level":"error","service":"proxy","error":"signature mismatch: expected 65bca42caf193a6e85131121e395ec1b93dfdf03499e2b69c8e43f2635704cff != actual 44a89a472b67fc1d59dc2716c53cfee24a7ca86cf4c41fb2da23acf56e136149","authenticator":"signed_url","path":"/remote.php/dav/spaces/f2528657-cfb9-4ce7-af08-805a4bb9fae1$4c49c1a8-4e31-1030-8639-1f621ceb306f/Windows Test.xlsx","url":"/remote.php/dav/spaces/f2528657-cfb9-4ce7-af08-805a4bb9fae1$4c49c1a8-4e31-1030-8639-1f621ceb306f/Windows%20Test.xlsx?OC-Credential=tschaaf&OC-Date=2024-07-10T14%3A46%3A32.788Z&OC-Expires=1200&OC-Verb=GET&OC-Algo=PBKDF2%2F10000-SHA512&OC-Signature=44a89a472b67fc1d59dc2716c53cfee24a7ca86cf4c41fb2da23acf56e136149","time":"2024-07-10T14:46:32Z","message":"Could not get user by claim"}

WebDAV seems unaffected I can also open a picture in the preview or use OnlyOffice via WOPI.
External LDAP provider is used for user authentication.

@ScharfViktor @micbar Echoing that for me the WebDAV connections are unaffected. Sync with apps works fine. Only web downloads result in the apache auth dialog.

Can't reproduce on mac. Could it be some apache configuration issue?
Please take a look at the similar issues:
https://github.com/owncloud/ocis/issues/9499
https://github.com/owncloud/ocis/issues/8694

Can't reproduce on mac. Could it be some apache configuration issue? Please take a look at the similar issues: #9499 #8694

Hi @2403905 thanks for the pointer-I think the key to solving this is to identify what changed between 5.0.0-rc5 and 5.0.5 that would impact an apache reverse proxy configuration.
As it stands, I can simply switch my binary back from 5.0.5 to rc5 and the issue is solved completely. Should I start trying other old versions to identify when the change occurred? My apache config is posted above. I did try restarting apache a few times.

Something else I found:
Using FireFox instead of Chrome downloads start working.
First time using FireFox to download a file, prompts a second login in browser (probably due to files are being downloaded with "WebDAV" in the background(?))
For this to work "PROXY_ENABLE_BASIC_AUTH" must be active else download in FireFox doesn't work either.
Which currently I use anyway as I want to use WebDAV directly on client without extra authentication software.
Still trying to see if apache headers can adjusted for this to work, I also read some said using nginx instead works, I might try this as well, but I would prefer to keep using apache instead.

Something else I found: Using FireFox instead of Chrome downloads start working. First time using FireFox to download a file, prompts a second login in browser (probably due to files are being downloaded with "WebDAV" in the background(?))
For this to work "PROXY_ENABLE_BASIC_AUTH" must be active else download in FireFox doesn't work either. Which currently I use anyway as I want to use WebDAV directly on client without extra authentication software.
Still trying to see if apache headers can adjusted for this to work, I also read some said using nginx instead works, I might try this as well, but I would prefer to keep using apache instead.

When I try Firefox, I see the same behavior as Safari. Until now I did not try to authenticate with the standard web login. When I do that, it authenticates successfully and downloads the file, albeit with "_" characters appended to the beginning and end of the filename.
I hope it is not the case that bare metal with apache is unsupported going forward.

Finally got around testing with nginx instead of apache and could confirm nginx is working.
I dug a bit deeper and the option
proxy_set_header Host $host;

in nginx does make this setup work, removing this header from nginx results in the same behavior as in apache.
I assumed setting something like: RequestHeader set Host "<ServerName>" in apache config should work here, but it seems not to work.

@meveric Thank you for digging! That sounds like the first real "hunch" on this problem. I am interested to see if apache could be used to proxy ocis also.
We ourselves have good experience with nginx and traefik.

@micbar Please keep in mind, that in general it works fine using apache if using oCIS 5.x (under Linux at least) this seems entirely related to changes made in oCIS 6.x. (while I can't speak for MAC where this issue seems to show up even in 5.0.5 here).
As well as some browsers work, using the basic_auth backend.

Edit: Asked an AI and here's what it said: Nginx's proxy_set_header directive modifies the request before it is proxied, whereas Apache's RequestHeader directive only modifies the response. It also suggested building my own apache module, which modifies the request before it's proxied.

I tried quite a few options in my Apache vhost config, but they did not work. This user suggested that ProxyPreserveHost On might work, but alas, not for me:
https://stackoverflow.com/questions/17227789/changing-request-header-before-forward-proxy-in-apache
The config I tried is as follows:
<VirtualHost *:80>
	ServerName files1.<redacted>.com
	DocumentRoot /opt/www/files1.<redacted>.com/
	ErrorLog "/opt/local/var/log/apache2/error_log"
	CustomLog "/opt/local/var/log/apache2/default.access_log" common
	CustomLog "/opt/local/var/log/apache2/access_log" vcommon
	CustomLog "/opt/local/var/log/apache2/extended_log" vuser
</VirtualHost>

<VirtualHost *:443>
  ServerName files1.<redacted>.com

  SSLProxyEngine on
  SSLProxyVerify none
  SSLProxyCheckPeerCN off
  SSLProxyCheckPeerName off
  SSLProxyCheckPeerExpire off

  ProxyPass / https://localhost:9200/
  ProxyPassReverse / https://localhost:9200/
  ProxyPreserveHost on
  ProxyAddHeaders On
  RequestHeader set Host "files1.<redacted>.com"
  ProxyRequests On

  SSLCertificateFile /opt/local/etc/letsencrypt/live/files1.<redacted>.com/fullchain.pem
  SSLCertificateKeyFile /opt/local/etc/letsencrypt/live/files1.<redacted>.com/privkey.pem

  Include /opt/local/etc/letsencrypt/options-ssl-apache.conf
  #SSLOpenSSLConfCmd DHParameters /opt/local/etc/letsencrypt/ssl-dhparams.pem

  ErrorLog "/opt/local/var/log/apache2/files1_error_log"
  CustomLog "/opt/local/var/log/apache2/files1_access_log" vcommon

</VirtualHost>

@meveric Thank you for digging! That sounds like the first real "hunch" on this problem. I am interested to see if apache could be used to proxy ocis also.
We ourselves have good experience with nginx and traefik.

Apache works perfectly on 5.0rc5, but not on subsequent versions. I forget where I found the config above-I believe it was contributed by another user in these forums. I did tweak it some, but never had any issues until moving to more recent versions. I hope the culprit can be identified, because for me at least, there is not much point to a bare metal version if there can't be a choice of web server (Apache being the more popular server by far).
The next step for me is to give up and move to an intel NUC for our local fileserver, in which case I would be using a Docker deployment.

@butonic any ideas?
we had a sec fix in 5.0.0 in regards of signed urls.

@butonic any ideas?
we had a sec fix in 5.0.0 in regards of signed urls.

Hi @micbar @ScharfViktor
I've tested the latest release (6.4.0, darwin amd64 build) on Apache with the ProxyPass directives outlined above and can confirm the web authentication problem persists.
If there's a preferred set of Apache directives or other troubleshooting steps, I'm happy to do them. If it is helpful, I can also set up a new VMWare VM with Ubuntu Server and see if these issues with Apache exist in that environment. I haven't played with Nginx just because we don't use it on any server.
One of my favorite things about this project (and, I think, a nice advantage over competitors) is the fact that you guys don't require everyone to deploy with Docker but provide binaries for every release with a bare metal configuration option. I wish I could force all our users to rely on the OC apps but some still need to use Web.
Thanks guys for all the hard work! Let me know what I can do to run this down.

Looking into your initial post.
2024/07/05 00:53:46 http: TLS handshake error from <IP_ADDRESS>:15706: tls: client offered only unsupported versions: [302 301]
2024/07/04 18:52:49 http: TLS handshake error from <IP_ADDRESS>:45388: tls: unsupported SSLv2 handshake received
2024/07/04 18:53:20 http: TLS handshake error from <IP_ADDRESS>:43676: tls: first record does not look like a TLS handshake
2024/07/04 18:53:20 http: TLS handshake error from <IP_ADDRESS>:43680: tls: unsupported SSLv2 handshake received
2024/07/04 18:53:30 http: TLS handshake error from <IP_ADDRESS>:55478: tls: no cipher suite supported by both client and server

This looks fishy. Seems that your Operating System and the reverse proxy have issues to establish a TLS connection.

Thanks for the pointer. I see there are some resources here, so I'll try to play around with the vhost conf more. For now we are still using 5.0rc5 and it works great with the config above.

IMHO it is not about the Certificate.
This looks more low level, a mismatch in the TLS handshake on the protocol level.
Can you tell me your operating system? Maybe we can try that too.

Can you tell me your operating system? Maybe we can try that too.

macos was stated in the initial post. Do you need an exact version of the OS?
cc @prohtex

Can you tell me your operating system? Maybe we can try that too.

macos was stated in the initial post. Do you need an exact version of the OS?
cc @prohtex

Its an older version - macOS 10.14.6, Apache/2.4.58 (Unix) OpenSSL/3.2.1 PHP/7.4.33
I ended up switching to a new machine with nginx but can still troubleshoot.


perf(vue): use shallowRef for data

Summary
As graphql response usually contains a quite huge nested objects structure, wrapping it with ref() is not memory efficient.
Instead of doing this, it's more efficient to use shallowRef() for data reactive variable, where the payload is stored.
However, in https://github.com/urql-graphql/urql/pull/3611 while optimizing other variables, @negezor missed the data variable. I can assume there was a reason for that, so I consider this PR as a suggestion/discussion. Personally, I don't see any negative side effects from using shallowRef(), but maybe you guys have some thought on it.
I see only one possible scenario in which this would be a "breaking change": updating some nested data parts manually outside of this plugin, but I'd say - this is a quite specific pattern.

Set of changes

Replaces ref() with shallowRef() for the data variable

Makes sense, I wasn't originally looking at data as to how field level changes might be happening there. But I forgot that we always replace the contents of ref 😅


[INTERNAL] Add SECURITY.md

Coverage increased (+0.02%) to 90.1% when pulling cb51b1bdf53b089312c7912fcf378230c8011fbc on add-security-md into af4318a75d742bbd2e5566d2ffde2bc5a823ef06 on master.


Create new electron app does not use latest release beta53

Preflight Checklist

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details
When I run yarn create electron-app my-new-app, I expect to use the latest version of electron-forge.

Electron Forge Version:

6.0.0-beta.51

Electron Version:

10.1.0

Operating System:

macOS 10.14.6

Last Known Working Electron Forge version::

n/a

Node Version:

14.9.0

Yarn Version:

1.22.5

Expected Behavior
Expect to see latest version of electron-forge 6.0.0-beta53
Actual Behavior
Creates new app using electron-forge 6.0.0-beta51
To Reproduce

Run yarn create electron-app my-new-app
cd into my-new-app folder
run yarn outdated or inspect package.json or yarn.lockfile

Workaround: yarn global remove create-electron-app and then rerun the yarn create command in the repro steps.

I confirm that worked. Thank you!


Enable YJIT Seems to not support arm64

Steps to reproduce the behavior
First reinstall rust
Then, try to enable YJIT with the following command:
ruby-build 3.3.3 /opt/rubies/ruby-3.3.3 -- --enable-yjit got from here
Expected vs. actual behavior
Expected it to enable YJIT
Currently crashes
Logs
Log Output:
touch yjit/target/release/libyjit.a
partial linking yjit/target/release/libyjit.a into yjit/target/release/libyjit.o
ld: warning: ignoring file yjit/target/release/libyjit.a, building for macOS-arm64 but attempting to link with file built for macOS-x86_64
Undefined symbols for architecture arm64:
  "_rb_yjit_before_ractor_spawn", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_bop_redefined", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_call_threshold", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_cme_invalidate", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_code_gc", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_cold_threshold", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_collect_binding_alloc", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_collect_binding_set", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_constant_ic_update", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_constant_state_changed", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_count_side_exit_op", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_disasm_iseq", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_enable", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_enabled_p", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_get_exit_locations", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_get_stats", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_incr_counter", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_init", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_insns_compiled", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_iseq_free", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_iseq_gen_entry_point", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_iseq_mark", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_iseq_update_references", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_live_iseq_count", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_option_disable", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_parse_option", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_print_stats_p", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_record_exit_stack", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_reset_stats_bang", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_root_mark", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_show_usage", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_simulate_oom_bang", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_stats_enabled_p", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_trace_exit_locations_enabled_p", referenced from:
     -exported_symbol[s_list] command line option
  "_rb_yjit_tracing_invalidate_all", referenced from:
     -exported_symbol[s_list] command line option
  "_rust_eh_personality", referenced from:
     -exported_symbol[s_list] command line option
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make: *** [yjit/target/release/libyjit.o] Error 1
external command failed with status 2

I ran ruby-build 3.3.3 /opt/rubies/ruby-3.3.3 and got the following error:
*** Following extensions are not compiled:
openssl:
        Could not be configured. It will not be installed.
        /Users/bespin-starter/src/ruby-3.3.3/ext/openssl/extconf.rb:122: OpenSSL library could not be found. You might want to use --with-openssl-dir=<dir> option to specify the prefix where OpenSSL is installed.
        Check ext/openssl/mkmf.log for more details.
psych:
        Could not be configured. It will not be installed.
        Check ext/psych/mkmf.log for more details.
*** Fix the problems, then remove these directories and try again if you want.

I already have openssl and libyaml installed so there's clearly another error happening here, but probably nothing wrong with ruby-build other than obfuscating the original error.


Cisco ID's

Hi,
I wanted to decode some more advanced netflow record types, so I added the Cisco NBAR based fields. As a part of this I discovered that variable length fields are not properly decoded (the slice is resized, but this is not send back 'up) so I changed the function to explicitly return the slice.
This works for me to decode ipfix records from my test router.
Best regards, Peter

Could you provide example flows containing the Cisco specific records please?

Hello,
I took a capture on my lab machine. It is exporting a lot of templates every 5 seconds, so it's rather big. In packet 2152 you'll see a record of accessing the lab webserver using curl.
I had to remove some other packets which showed 'sensitive' information, but the capture decodes properly with wireshark. Please yell if there is a problem.
Thanks, Peter
variable-length-netflow-sensored.zip

Thanks, it was indeed required to pass back the new slice if it's altered.


ingress.class not propagated

First off, I'm not sure which of these things are cause and effect, or if they are unrelated, so let me know if I should split this issue or rephrase it. Also, this is a (somewhat rambling) summary of a discussion in #kube-lego on the k8s Slack, I hope I didn't miss any context.
Edit: I solved the latter half of this issue by fixing my ingress configuration, but I'll keep the original description for now. Back to pre-edit
I had problems when trying out lego on my test-case today, replacing self-signed certs on our monitoring (grafana/kibana/etc) ingress point. To test, I have a fairly empty cluster. Here's my setup:

Kubernetes 1.7.7 (Azure ACS)
Nginx Ingress Controller (0.9.0-beta.17, installed via Helm), with custom ingress.class, kubernetes.io/ingress.class: monitoring, deployed to namespace monitoring.
Four services in the monitoring namespace, and an ingress resource:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: monitoring-web
  annotations:
    kubernetes.io/ingress.class: "monitoring"
    kubernetes.io/ingress.provider: "nginx"
    kubernetes.io/tls-acme: "true"
    ingress.kubernetes.io/rewrite-target: "/"

    ingress.kubernetes.io/auth-url: "https://$host/oauth2/auth"
    ingress.kubernetes.io/auth-signin: "https://$host/oauth2/sign_in"
spec:
  rules:
  - http:
      paths:
      - path: /prometheus
        backend:
          serviceName: prometheus-server
          servicePort: 9090
  - http:
      paths:
      - path: /alertmanager
        backend:
          serviceName: prometheus-alertmanager
          servicePort: 80
  - http:
      paths:
      - path: /grafana
        backend:
          serviceName: grafana-grafana
          servicePort: 3000
  - http:
      paths:
      - path: /kibana
        backend:
          serviceName: kibana
          servicePort: 5601
  tls:
  - hosts:
    - monitoring.example.com
    secretName: monitoring-ingress-tls

So, up until this works fine with the self-signed setup. I then deployed kube-lego (to the kube-system namespace) using helm with the stable chart. However, it does not accept my "monitoring" class, so my first step is to upgrade to the canary tag (after reading some issue or post on Slack).
Adding LEGO_SUPPORTED_INGRESS_CLASS: "monitoring" to values.yaml, I can now start getting 404:s in the reachability tests. Looking at the generated ingress resource, it has not set the correct ingress.class, and is setting it to nginx instead. Bug or misconfiguration?
(Setting LEGO_DEFAULT_INGRESS_CLASS: "monitoring" LEGO_DEFAULT_INGRESS_PROVIDER: "nginx" "works", but from the docs I would have expected the default-values to be used only when I hadn't annotated the target ingresses myself? As an additional confusion, having default provider set to default class strikes me as backwards, shouldn't it be the other way around?)
Moving on, when I get the correct class and provider, I then start getting my certificates generated. I can read the certificates with kubectl and verify that they are indeed correctly generated from Let's Encrypt. However, my ingresses don't use them. Connecting to the ingress, I still get the Kubernetes Ingress Controller Fake Certificate. I've tried recreating the ingress, restarting the controller, recreating and restarting kube-lego... I can't figure out how it can use the wrong cert. I've tried setting the defaultSSLCertificate on the nginx-controller chart to point to the cert generated by kube-lego. Doesn't seem to make any difference.
There are no suspicious entries in the controller logs, and kube-lego also seems happy.

As ideas always come to late, I didn't look until now at the generated nginx-config checking for the certificate configuration. The ingress certs are not mentioned. The only configuration in there regarding certs is these lines:
ssl_certificate                         /ingress-controller/ssl/default-fake-certificate.pem;
ssl_certificate_key                     /ingress-controller/ssl/default-fake-certificate.pem;

Maybe this is actually an nginx-ingress bug?

@carlpett Thanks for the detailed issue, looks like I missed a TODO when I was re-introducing the provider concept -- https://github.com/jetstack/kube-lego/blob/039ab9cb50872e63d3b68d2e48b1a950fcc6f24f/pkg/provider/nginx/nginx.go#L123
I'll submit a PR this weekend to fix that as it only looks at the default you have set currently.
As for "having default provider set to default class strikes me as backwards", yeah it is backwards although to be backwards compatible it needed to be implemented that way as provider came after class even though it is in a way more of a low level configuration.

@jackhopner Nice, looking forward to it!
Regarding backwards compatibility, I see your point, but isn't this "forwards incompatible" instead? :)


[Doc improvement][Proactive messages aadObjectId]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
90
25
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
90
25
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Closing the PR as the issue is resolved.


ks pkg get displays unhelpful error message

bash-3.2$ ks pkg get incubator@redis:test-reg
ERROR Command 'pkg' requires a subcommand

Usage:
  ks pkg [flags]
  ks pkg [command]

Available Commands:
  describe    Describe a ksonnet package
  install     Install a package as a dependency in the current ksonnet application
  list        Lists information about all dependencies known to the current ksonnet app

Flags:
  -h, --help   help for pkg

Global Flags:
  -v, --verbose count[=-1]   Increase verbosity. May be given multiple times.

Use "ks pkg [command] --help" for more information about a command.

@hausdorff -- trying to take some work off your plate! There is no get command; I'm assuming the desired "fix" for this is for get to be an alias for install?


Add support for 10.0.17738.1000

Windows 10 recently update has rendered rdpwrapper non-functional.  I've tried previous versions of termsvr.dll which had worked but the Windows service won't start with them in place.  Please add support for termsvr.dll version 10.0.17692.1004.

How could I add new version for support if you did not shared the file? :confused:

Sorry about that.  Windows got updated again since the issue was created, I'm now with ver 10.0.17738.1000

termsrv.zip

10.0.17738.1000

https://github.com/sebaxakerhtc/rdpwrap.ini/commit/106f09d83b137a27a3554fb9dc7c5e0027a0c2da


Bug: thread 'state_store_tests::test_iter_log' panicked at src/storage/hummock_test/src/state_store_tests.rs:1619:5: assertion left == right failed

I recently started to see these bugs in the PR workflows. Looks like a regression.
thread 'state_store_tests::test_iter_log' panicked at src/storage/hummock_test/src/state_store_tests.rs:1619:5:
assertion `left == right` failed
  left: 9999
 right: 10000
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/std/src/panicking.rs:645:5
   1: core::panicking::panic_fmt
             at /rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/core/src/panicking.rs:72:14
   2: core::panicking::assert_failed_inner
             at /rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/core/src/panicking.rs:342:17
   3: core::panicking::assert_failed
             at /rustc/e4c626dd9a17a23270bf8e7158e59cf2b9c04840/library/core/src/panicking.rs:297:5
   4: risingwave_hummock_test::state_store_tests::test_iter_log::{{closure}}
             at ./src/state_store_tests.rs:1619:5

Source: https://buildkite.com/risingwavelabs/pull-request/builds/48640#018f27b6-e81f-457c-8882-7022dd6fb022

Fixed by https://github.com/risingwavelabs/risingwave/pull/16534


which python version is it?

Hello, thank you for opening this issue. I used python 3.8 but I believe it should also work with later versions. I will also include it in the Readme.

Thank you!


Error : Unable to access jarfile VertigoBoostingPanel.jar

And i guess it's because it's nowhere in the files folders

You need to download release, not source code (download from here 3 files: https://github.com/SamHoque/Vertigo-Boosting-Panel/releases/tag/1.0.0 )


Readme states that "config" is available within the "kafka" class

Readme says that it's possible to supply the config hash withing the "kafka" class, but it doesn't work. Puppet says "invalid parameter".

Same problem here! How do I supply config parameters?

Hello Andrey,
I think you used the wrong class. The parameter config is only supported by the classes kafka::broker, kafka::consumer and kafka::producer.
Kind regards,
Dennis

True. Thanks @dhoppe.
Still, this report is valid, seeing as our docs are broken. Opened #48 to fix this. Reviews are appreciated.

fixed in #48


Add Intel syntax support for ELLCC. Fixes #1014

ellcc supports the same set of options as Clang to emit Intel syntax output, so I've added the necessary line to enable Intel syntax support

Hi @phuclv90. Sorry you did not get an answer in #1014 The fact that you've put the effort to add support for it by yourself is great.
In #1014, you mention that -masm=intel should be added, but here you've instead added -mllvm --x86-asm-syntax=intel Could you share the reasoning as to why you've done that? (I admit I'm not the most knowledgeable regarding ellcc)
Also, did you test (or do you know) if the changes work for all the currently supported ellcc versions?

Hi @RabsRincon
-masm=intel is supported by newer clang versions, but I saw the below commit so I use -mllvm --x86-asm-syntax=intel like that instead for consistency

commit 78a3f344aa5eaada38506b49bd2e2e493783cfb9
Author: Matt Godbolt<EMAIL_ADDRESS>Date:   Thu Feb 16 09:21:37 2017 -0600
Use `-mllvm --x86-asm-syntax=intel` to get intel asm syntax on clang. Works on all clang versions. Fixes #280

I tried those options on all ellcc versions of compiler explorer and they work without problem

That's great to hear, and even better that you caught that change and implemented it. I'll merge right away. Thanks for taking the time to improve CE
The change should arrive "soon" to the live site. I'll be sure to let you know once it's live :)


Blogger Upload image when insert new post

I want to know how I can upload an image when I insert a new post.
Here code i use for insert new post :
blogger.posts.insert({
  blogId: 'my-blog-id',
  resource: {
    title: 'Post title',
    content: 'Post Content',
  }
}, function(err,output){
	console.log(output)
});

Does this help at all?

no, there is no Property for uploading an image, it seems to google doesn't allow upload image through API.


[FEATURE] - Manual counting for encode in class CodaBarWriter

Manual counting of complexity for encode in class CodaBarWriter.
Adding comments in the code for each count

done


Fixing issue #63 (prevent empty note)

fixes #63 and includes some minor changes (see commit messages)

added missing end tag  in all translations
updated German translation of categories

One thing is still unclear to me:
locales/de/categories.json:894 used to have an empty category. I guessed it was unintentional, but please check.

Thanks!


Need support for background images

First of all, Great package. Currently this module supports only image tags. Can we please make it work for background-images too ? That would be really helpful.

Hello, @ateev. It works with any type of content. Can you describe your case in more detail?

Hey @sergeylaptev . I have a div with background-image set. To be exact, i'm looking for this functionality. http://dinbror.dk/blog/blazy/?ref=demo-page#Background

Here is the possible solution:
<div className="MyComponent-container">
  <LazyLoad>
    <div
      className="MyComponent-containerImage"
      style={{ backgroundImage: 'url("http://apod.nasa.gov/apod/image/1502/HDR_MVMQ20Feb2015ouellet1024.jpg")' }}
    />
  </LazyLoad>
</div>

@component MyComponent {
  @descendent container {
    position: relative;
    height: 700px;
  }

  @descendent containerImage {
    position: absolute;
    top: 0;
    left: 0;
    width: 100%;
    height: 100%;
  }
}


Fix for SIGABRT

We noticed that the string indexing is causing some out-of-bounds errors now and then. The problem is that the code checks !s.empty() in the while condition, but then mutates the string using s.pop_back() so that s may be empty at that point. You may be able to reproduce this yourself using a file that only contains three characters: " , "  (space comma space). In any case, I have provided a patch that fixes the problem.
Abort signature is below.
Using host libthread_db library "/lib64/libthread_db.so.1".
/builddir/build/BUILD/gcc-8.5.0-20210514/obj-aarch64-redhat-linux/aarch64-redhat-linux/libstdc++-v3/include/bits/basic_string.h:1071: std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::reference std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::operator[](std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::size_type) [with _CharT = char; _Traits = std::char_traits<char>; _Alloc = std::allocator<char>; std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::reference = char&; std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::size_type = long unsigned int]: Assertion '__pos <= size()' failed.

Program received signal SIGABRT, Aborted.
0x00004000003a69f4 in raise () from /lib64/libc.so.6
. where
#0  0x00004000003a69f4 in raise () from /lib64/libc.so.6
#1  0x00004000003909ec in abort () from /lib64/libc.so.6
#2  0x000040000011aa68 in std::__replacement_assert(char const*, int, char const*, char const*) () from /lib64/libstdc++.so.6
#3  0x0000400000195388 in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::operator[](unsigned long) ()
   from /lib64/libstdc++.so.6
#4  0x00000000004020f0 in main (argc=<optimized out>, argv=<optimized out>) at compare/text_compare.cpp:89

Hi! Did you have a chance to test?


global: v1.2.2 wasn't released on PyPI

Missing on pypi

Re-triggered travis. It might release? https://travis-ci.org/github/inveniosoftware/invenio-accounts/builds/686531910


Added repository parameters and system_prompt

closes #3
the model llama-3 is set through Launchpad, along with the linked repo. Thus, no need to define it through SDK.
I just added the parameters related to the repository, along with the system_prompt.

N.B.: I just need to do more checks regarding the truthfulness of the model answers @filopedraz @nsosio


Support for Innovator 12

When accessing an Innovator 12 BETA instance, Innovator Admin v18.324.23900.0 produces an Unauthorized error when Testing the connection,   A connection cannot be made to the Innovator 12 BETA database.
Can this be resolved?  I'm not sure what changed in the logon protocols between Innovator 11 and 12.
Thanks
Stuart

It also doesn't work in Innovator 12 official release that was made available today ...

The latest release (just uploaded) should now support Innovator 12. If you notice any specific issues, let me know.

Hi Eric
That works fine, thank you so much!
I have a requirement to do baseline compares of an Innovator 11 database
configuration, comparing the entire current configuration with I guess the
entire configuration as exported at a baseline date, to help with tracking
of changes and traceability.  Do you think the Innovator Admin package can
handle this use case?  I can't quite see how to get the current config of
the entire system output as a .innpkg file.
Thanks for your attention to this …
Best regards
Stuart
--
[image: Description:
http://www.matrix.co.nz/data/media/images/LOGO_RGB_25.JPG]
Stuart Hodder  BE, PhD  Principal Information Engineer
Matrix Applied Computing Ltd
PO Box 56-316, Auckland 1446, New Zealand
Unit 2-5, 72 Dominion Rd, Mt Eden, Auckland 1024, New Zealand
M +64 27 593 7001  DDI +64 9 972 9027  T +64 9 623 1223  S stuart_hodder  E
<EMAIL_ADDRESS> [image:
https://media.licdn.com/mpr/mpr/shrinknp_100_100/AAEAAQAAAAAAAAY5AAAAJGM2NzVkMDI1LTAwMTMtNGY5MS1iZDUzLWVjMDU3N2MyMTE1Yg.png]
https://www.linkedin.com/in/stuart-hodder-54100714/
http://www.matrix.co.nz  HelpDesk<EMAIL_ADDRESS>From: Eric Domke<EMAIL_ADDRESS>Sent: Monday, 3 June 2019 2:11 AM
To: erdomke/InnovatorAdmin<EMAIL_ADDRESS>Cc: StuartHodder<EMAIL_ADDRESS>State change <
<EMAIL_ADDRESS>Subject: Re: [erdomke/InnovatorAdmin] Support for Innovator 12 (#207)
The latest release (just uploaded) should now support Innovator 12. If you
notice any specific issues, let me know.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/erdomke/InnovatorAdmin/issues/207?email_source=notifications&email_token=AL6VQBOTOOCYWWA2676C7DLPYPIIXA5CNFSM4HJ3GRQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWXWQ4Q#issuecomment-498034802,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL6VQBLJQMXKRUJ55J5MD63PYPIIXANCNFSM4HJ3GRQA
.[image: Image removed by sender.]
--
CAUTION
This message may contain privileged and confidential information
intended only  for the use of the addressee(s) named above.  If you are not
the intended  recipient of this message you are hereby notified that any
use, dissemination,  distribution or reproduction of this message is
prohibited.  If you have  received this message in error please notify
Matrix Applied Computing Ltd  immediately.


Remove no longer relevant TODOs

What does this PR do?
After https://github.com/PyTorchLightning/pytorch-lightning/pull/11577 these TODOs are no longer necessary.
Does your PR introduce any breaking changes? If yes, please list them.

Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

Looks like we are going to need a CI rerun...  :/


Unable to run release build

I am trying to deploy my app to android. I follow the steps on this page https://facebook.github.io/react-native/docs/signed-apk-android.html.
When I try to run it, it tells me not such file or directory '.../assets/index.android.bundle'
or i get Task 'installReleaseDebug' not found in root project 'awezaEduApp'
Using Windows 10 and react-native 0.39.2
Any help would be appreciated please.

Hi, see #11767 . A temporary fix is to create the assets folder manually.

Thank you, but now i get this error

Had to reformat my laptop for other reasons. I redid the signing process and everything is working. I see that --variant=release changed to --configuration=release from v0.39.x. I will update the docs and put in a pull request when i get a chance.

react-native run-android --configuration=release worked for me with release 0.40


Extract the GitHub model to a separate library

It would be nice if other (Kotlin) projects could make use of the GitHub model for submission to the dependency API by extracting it to a separate library for reuse in other projects, like ORT.

Given the model is literally 3 kotlin data classes, I don't know how much value would be added by publishing these independently.
https://github.com/gradle/github-dependency-extractor/tree/main/plugin/src/main/kotlin/org/gradle/github/dependency/extractor/internal/model

Agreed, it's probably not worth the effort of publishing a separate library.


fix: init Web3HttpProvider without chain id

Summary of Changes
Fixes HTTP method
Test Data or Screenshots
By submitting this pull request, you are confirming the following:

I have reviewed the Contribution Guidelines.
I have performed a self-review of my own code.
I have updated my repository to match the develop branch.
I have included test data or screenshots that prove my fix is effective or that my feature works.
I have checked that all tests work and swiftlint is not throwing any errors/warnings.

@yaroslavyaroslav APIRequest.getNetwork.call returns RPC method name net_version not http method

Outdated, #831


[Ease of Use] Styling is different between settings and the launched dialogues

this is tracked in #2168 and #2170. closing for now


Document, test, and improve functionality.

We've written unit and functional tests for most of the project. Additionally, we've implemented some chunks of the core spec that were missing. We have all of the Core API spec implemented with the exception of node_start, node_stop, repo_init, repo_config_get, and repo_config_set. We also have a working version of add, cat, and get. (Add does not currently handle filtering added files by a regular expression though.)
Resolves #45 and #34 .

Actually, we're not quite ready yet. Just realized this branch is missing something. Will open a new one when fixed.

Okay, fixed now.

This is great, thanks so much! :) I have only very little experience with python so I can't give much valuable feedback. @alexander255 @amstocker @jbenet what do you think?

:+1: on this, we're currently shelling out to go-ipfs to do recursive adds


"Apply the migration to the existing database." linkls to itself (the same heading) explaining nothing

Description
https://learn.microsoft.com/en-us/aspnet/core/data/ef-rp/complex-data-model?view=aspnetcore-8.0&tabs=visual-studio#applyexisting links to itself in:

Apply the migration to the existing database. The instructions in this section work for SQL Server only, not for SQLite.

"Drop and re-create the database" properly links to SQLLite delete DB
Page URL
https://learn.microsoft.com/en-us/aspnet/core/data/ef-rp/complex-data-model?view=aspnetcore-8.0&tabs=visual-studio
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/data/ef-rp/complex-data-model.md
Document ID
7a77b058-f005-8d68-ae46-e487c597f18e
Article author
@tdykstra

Associated WorkItem - 295453

See SQLite limitations on migrations

Yes, but that was not the question. It was a pure stylsitic mistake here. This link, links to itself i.e. the same headline. To highlight it again :


AP reports as an appendix?

Should we include the AP fishery reports as an appendix? I feel that it would be good practice and hopefully encourage them to write these reports.  Do we italicize the text to make it clear that it is a quote, and not the writing of the JTC?

Yes, I agree with this.

I agree, but have a feeling the SRG was going to ask for this for next year. Do we have the report? I can start it now.

Can see how the italics look - whole Appendix may be overkill. So just have an explanation at the start of it.....

The Canadian AP is updating the report, so let's make sure we update it when they provide a new version.

Do we have the US report to include yet?

Not yet. I sent them an idea for a start, but if they don't get us one by
tomorrow morning, then it won't be included.
On Mon, Feb 29, 2016 at 8:26 AM, cgrandin<EMAIL_ADDRESS>wrote:

Do we have the US report to include yet?
—
Reply to this email directly or view it on GitHub
https://github.com/cgrandin/hake-assessment/issues/149#issuecomment-190276791
.

I'd rather go with a cut-off time of, say, 3pm today? We can't be expected to include (and format) stuff at the last minute.
I have an all-day meeting tomorrow starting at 9:30 - it's downtown and I'll have wireless, so can easily check in. Would rather get it submitted by then though (or even today?).

I will offer to do it if they get it to us by noon

Okay. I can check in at lunch. Make a note on this issue if you get something.

Think I'm done for now. I'm only on my small laptop screen so not ideal for looking through the document, so someone should look through with an eye to formatting.......

I did just have a skim through and formatting looks good. I'll check in again later, as it looks like you're still doing some minor tweaks....

The US AP will not be submitting a report this year.


Adapts compilations to the new Zig compiler version 0.12.0

Hi there, I am a novice and don't know much about bash scripting or bash-completor. I tried my best to get the completions in sync with the new Zig compiler version 0.12.0.
I focused on zig build so I did not add completion help for zig init|fetch|std. Hope I can help :)
Also, since I don't use zsh, I did not update that either.

Thanks! I'm not familiar with bash completions so I'm gonna assume you tested these locally since they look correct-ish.


Release stable version

The latest stable version of this plugin was released more than one year ago. Now only beta versions are released. Why is that? When will be the next stable version?

Hi there,
I'm also wondering when the next stable version will be released. Our suite of apps relies on this library and our users are experiencing issues related to the metadata which was fixed for version 4.4.8-beta.
Thanks,
Sam.

5.0 i snow in beta and if goes well will release to stable :)

Thanks for the response James. :)
🤞

Hi @jamesmontemagno . I was wondering if there were any updates on this?

Yes, I am waiting for us to release Xamarin.Essentials 1.5.2 which should be soon here.

@jamesmontemagno
Hi. Any update on this?

I was wondering too as Xamarin Essentials 1.5.2 was released!! :)

Hi @jamesmontemagno
Thanks for getting all of this sorted. Right on time too. :)
I'm guessing this issue can be closed?

Thanks @jamesmontemagno
Now it's time to release stable version of PermissionsPlugin

@Mikilll94 if you're referring to the Media plugin dependency, then that's not necessary, since the updated media plugin now relies on Xamarin.Essentials to manage permissions.

@InquisitorJax
Yes. But many projects uses PermissionsPlugin to request permissions manually. So it would be nice to have stable version of this plugin.

Would recommend switching to Essentials for permissions :)

@jamesmontemagno
I will switch to Essentials when this feature will be implemented
https://github.com/xamarin/Essentials/issues/1160
Right now it is not implemented.


wheel CI: Always use latest minor version of cibuildwheel

By removing the exact minor and patch version of the cibuildwheel action, it will always use the latest minor/patch version. For Travis, it will use the latest version even for new major versions.
This ensures the latest Python versions are always used to build wheels.
Major version updates will be handled by #17327 for GitHub Actions.

My mistake, cibuildwheel (currently) doesn't allow this and requires pinned major.minor.patch versions specified. So closing this PR.


Error when generating coverage report on some Vue files with import

I'm trying to generate coverage report for Vue files using Playwright Component Testing. It was working fine until recent updates. When a Vue file has imports from @heroicons/vue package, e.g. import { ChevronDownIcon } from '@heroicons/vue/20/solid', I get following error. When I remove that import, there is no error.
[MCR] loaded 6 sourcemaps (80 ms)

  1 passed (5.3s)
[MCR] generating report data ...
[MCR] generating global coverage report ...
[MCR] decode source mappings assets/index-caf6d1d3.js (189 ms)
[MCR] decode source mappings VerticalNavMobile-54b3351d.js (76 ms)
[MCR] decode source mappings vue.runtime.esm-bundler-bcfba368.js (76 ms)
Error in reporter TypeError: Cannot read properties of undefined (reading 'generatedOffset')
    at findMapping (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/plugins/coverage/converter/find-original-range.js:20:26)
    at findOffsetMapping (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/plugins/coverage/converter/find-original-range.js:31:21)
    at findStartMapping (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/plugins/coverage/converter/find-original-range.js:432:26)
    at findOriginalRange (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/plugins/coverage/converter/find-original-range.js:512:25)
    at /Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/plugins/coverage/converter/converter.js:420:28
    at Array.forEach (<anonymous>)
    at /Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/plugins/coverage/converter/converter.js:418:22
    at Array.forEach (<anonymous>)
    at unpackSourceMap (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/plugins/coverage/converter/converter.js:417:20)
    at unpackDistFile (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/plugins/coverage/converter/converter.js:477:9)
    at convertV8List (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/plugins/coverage/converter/converter.js:536:9)
    at getGlobalCoverageData (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/plugins/coverage/coverage.js:236:43)
    at generateGlobalCoverageReport (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/plugins/coverage/coverage.js:279:20)
    at artifactsHandler (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/generate-data.js:23:24)
    at generateData (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/generate-data.js:83:23)
    at Reporter.onEnd (/Users/admin/code/web-app/frontend/node_modules/.pnpm/monocart-reporter@1.7.3/node_modules/monocart-reporter/lib/index.js:198:28)
    at wrapAsync (/Users/admin/code/web-app/frontend/node_modules/.pnpm/@playwright+test@1.35.1/node_modules/@playwright/test/lib/reporters/multiplexer.js:92:5)
    at Multiplexer.onEnd (/Users/admin/code/web-app/frontend/node_modules/.pnpm/@playwright+test@1.35.1/node_modules/@playwright/test/lib/reporters/multiplexer.js:59:45)
    at InternalReporter.onExit (/Users/admin/code/web-app/frontend/node_modules/.pnpm/@playwright+test@1.35.1/node_modules/@playwright/test/lib/reporters/internalReporter.js:94:5)
    at Runner.runAllTests (/Users/admin/code/web-app/frontend/node_modules/.pnpm/@playwright+test@1.35.1/node_modules/@playwright/test/lib/runner/runner.js:78:5)
    at runTests (/Users/admin/code/web-app/frontend/node_modules/.pnpm/@playwright+test@1.35.1/node_modules/@playwright/test/lib/cli.js:132:93)
    at qr.<anonymous> (/Users/admin/code/web-app/frontend/node_modules/.pnpm/@playwright+test@1.35.1/node_modules/@playwright/test/lib/cli.js:40:7)

let me check, thanks

Unfortunately, I can not reproduce it with following
import { ChevronDownIcon } from '@heroicons/vue/20/solid'

can you create a minimal demo that reproduces the issue?

can you try<EMAIL_ADDRESS>there is a quick fix with following, please try and see if the issue still exists?

@cenfun thanks for the quick fix! It's working now 👍🏻