MultiGrid: Fix extra row being added to the bottom left table when there is a vertical scrollbar, but there is no horizontal one (#1337)

Fixes #1337
For some reason variables related to the vertical scrollbar were used to adjust the row count and the last row height. Now using the state of the horizontal scrollbar.

@bvaughn is there any chance for this to be merged and released?
Thanks.

@bvaughn
bump, faced same problem, looks like this pr fixed this problem. Don't want to fork 😥 Someone needs to take a look.

😭

re-bump -- would like to use MultiGrid but needing to stick with a bit of a custom solution right now. @bvaughn noticed a mention... completely respect if you're busy --  anyone next in line who we can give a bother to? 🙃

@bvaughn is there anything we can do to help move this along?


Date service

Initial work on the calendar branch. This makes the current date handling nicer and more predictable

@amulware Please note that this includes a lot of merge commits. Consider only this subset when reviewing


Unsupported file type: .odt

Too bad for me. I want to use Grav to store some files and give access to them but some standard types like odt (open office or libre office files) are not supported.
When i use the plugin admin with dragging and dropping a file with .odt extension i have this message :
An error occurred while trying to add the file Expose.odt
Unsupported file type: .odt
When i use an editor and link on this file i have a error screen "Woops. Looks like this page doesn't exist."
This feature is important for me in order to use this tool because in my firm we use both .doc or .odt files...

I answer to myself. Maybe this issue can be useful for others.
The supported files are referenced in the media page :
http://learn.getgrav.org/content/media
For the document file only "txt, doc, html, pdf, zip, gz" are supported.
But it is really easy to add some file extension following the doc.
Go to system/config/media.yaml and add for example the support for all the open document (writer, spreadsheet, presentation et drawing) like this :
odt:
type: file
mime: application/vnd.oasis.opendocument.text
ods:
type: file
mime: application/vnd.oasis.opendocument.spreadsheet
odp:
type: file
mime: application/vnd.oasis.opendocument.presentation
odg:
type: file
mime: application/vnd.oasis.opendocument.graphics
Now a link to a odt file can be opened. :)
I will make a pull request when i have some time.
You can close this issue!


Deletion of Keys and wallets/ vaults:

Enable users to securely delete keys and wallets that have been hidden from view.
Users can navigate to the list of all keys/wallets and choose individual items for deletion.
The user will have to confirm deletion by entering the passcode.

Dependencies

#4171
#4172

Keys
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/97e2b6c8-2469-4d5c-85bd-23c9272c3d08/
Wallets
https://xd.adobe.com/view/f1543c84-c25a-4ad6-81ca-1e0c540e956e-a407/screen/0cf4cd89-a6d6-4527-9159-5e440a11c4b1/

Verified this issue on keeper dev app v 1.2.0(319)


Report generator fails with XSL error

When creating a load test report, the report generator complains about errors in an XSL template:
ERROR:  'file:/d:/workspace/xlt-develop/config/xsl/loadreport/util/timer-row.xsl: line 135: Variable 'classNames' is multiply defined in the same scope.'
ERROR:  'file:/d:/workspace/xlt-develop/config/xsl/loadreport/util/timer-row.xsl: line 135: Variable 'classNames' is multiply defined in the same scope.'

The root cause is that - since #205 - HtmlUnit doesn't ship with xalan any longer, which we implicitly used for report generation as well. We now use the XSLT stuff from the JDK, which apparently does not work the same.
We massaged the offending XSL template a bit to fix the error, but there were further issues. The timer tables didn't contain any body rows and the individual timer charts were missing as well.
We will reintroduce xalan to get rid of the issues for now. With the upcoming report creation performance improvements, it is maybe a good idea not to mess with the reports anyway so we can easily compare 6.x reports with 7.x reports.


x I875, Matroska: Fix for added Statistics Tags

Hello,
in f1f2d80a9a8995f32e229b8aaade40a460490e40 you tried to solve issue #875 about added Matroska statistics tags that have been ignored, but you got the comparison of the dates wrong so that only tags that are newer than the file would be treated as invalid. You quickly noticed this and fixed it in<PHONE_NUMBER>d4c726a7268822aeec84384b5a3b45, but you (most likely unintentionally) reversed this in eb0999b917054020f08daba490a87dcf41be8f2f. This PR is intended to fix this.
Greetings
mkver

Oops... Tanks for having remarked that and provided the fix, appreciated.


feat: add dropdown for more straight-forward search mode switching

Describe the bug
Both the search icon and the search bar won't let you type anything in them. They only give you the local results. I've even tried creating a search for the overseerr integration but that doesn't show up and again won't let you type anything in the bar.
Steps to reproduce
deploy current beta using docker compose
import your boards
try to search anything.
Impact
Makes search non-functional
Additional information
No response
Version
1.0.0-beta
Installation method
Portainer
Browser
Edge (Chromium)

Sorry this is not better described yet and we are still on the work of the search functionality (with for example a default search engine) When you want to use a search engine you can type a ! to see all available engines and then select one. Also you can open a list of all available shortcuts by pressing the ? while in search.

Sorry this is not better described yet and we are still on the work of the search functionality (with for example a default search engine) When you want to use a search engine you can type a ! to see all available engines and then select one. Also you can open a list of all available shortcuts by pressing the ? while in search.

Gotcha, I didn't see that in the docs so I assumed it was a bug. Might I suggest doing away with the ! or ? parameter and have the user select a "default" search. When they want to use one of other search options they can then select them from a drop down menu? Seems this would be more intuitive.

I guess you are most likely talking from a mobile user perspective. IMO we can add something in that direction for mobile users, but I think for desktop users it's okay that way. What do you think?

I guess you are most likely talking from a mobile user perspective. IMO we can add something in that direction for mobile users, but I think for desktop users it's okay that way. What do you think?

Personally, I think both experiences should follow eachother. So if you did this for mobile, then desktop should follow. I personally I use homarr on both desktop and mobile. I have no issues with the ! or ? parameters but I know my wife does as its not as intuitive for new or less savvy users.

Makes sense, okay I'll rename this issue to feat: add dropdown for more straight-forward search mode switching. Okay?

Okay you we're actually right. You can't type anything in the home mode of the search right now. I'll fix that combined with the other thing. What do you think of something like this?

It has a new button in the top right corner to get to the help page (with the combinations and links to documentation and such) and below the default search engine and a possibility to open an other search engine which then opens the search engine selection?
IMO a normal dropdown does not really fit in here


Add arguments to benchmark options

Abstract
Add arguments to benchmark options.
Description
In this p-r, I add below options:

host: host to try benchmark
port: port to try benchmark
user: user to connect mqtt server
pass: pass to connect mqtt server

Example
$ GOMAXPROCS=2 go test -run=TestFan -vv=2 -logtostderr=true -host localhost -port 1884 -user "" -pass ""

Merged..Thanks!

@muddydixon Thank you for the contributions. Please don't forget to add yourself to the AUTHORS file.


Pressing PrtScr shows "SysReq" as result

using checkeys from SDL2 test, when I press PrtScr key I get as result SysReq (is on same key, but should be trigger when holding AltGr/Shift/CantRemeberNow).

Teste with ZGloom, and seems not working (SDLK_PRINTSCREEN), maybe you only chnaged
SDL_SCANCODE#? and not SDLK_#? (or ZGloom uses a "dirty" non-correct way)
...
if ((sEvent.type == SDL_KEYDOWN) && sEvent.key.keysym.sym == SDLK_SYSREQ)//SDLK_PRINTSCREEN)
{
printscreen = true;
}
...

Works here with checkkeys and custom example. Are you 100% sure you are using the same SDL2 lib with checkkeys and ZGloom?

Any news?

Hola capehill
El 14-07-2020, escribiste:

Any news?

TBH it worked fine last time a compiled/tested checkeys, but I get again SysReq instead of PrtScr ¿:-/
#version SOBJS:libSDL2.so file
libSDL2.so 0.12
#list check#?
checkkeys.o                   65448 ----rw-d Hoy       14:56:57
checkkeys                   4199995 ----rwed Hoy       14:56:59
checkkeys.c                    6370 ----rw-d 27-Abr-20 17:39:55
3 ficheros - 4171K bytes - 8348 bloques usados
#checkkeys
INFO: Initial state: modifiers: (none)
INFO: Key pressed :  scancode 154 = SysReq, keycode 0x4000009A = SysReq  modifiers: (none)
INFO: Key released:  scancode 154 = SysReq, keycode 0x4000009A = SysReq  modifiers: (none)
INFO: Key pressed :  scancode 154 = SysReq, keycode 0x4000009A = SysReq  modifiers: (none)
INFO: Key released:  scancode 154 = SysReq, keycode 0x4000009A = SysReq  modifiers: (none)
INFO: Key pressed :  scancode 154 = SysReq, keycode 0x4000009A = SysReq  modifiers: (none)
INFO: Key released:  scancode 154 = SysReq, keycode 0x4000009A = SysReq  modifiers: (none)
INFO: Key pressed :  scancode 154 = SysReq, keycode 0x4000009A = SysReq  modifiers: (none)
INFO: Key released:  scancode 154 = SysReq, keycode 0x4000009A = SysReq  modifiers: (none)

Will check it again, so I don't have mixed/old SDL2 headers/libs/...
BTW Can you (re)compile for me (for testing/comparing) static(aly) checkeys  test and send PM<EMAIL_ADDRESS>in case is my headers/lib structure/tree I have wrong.
Saludos
AOS4.1/SAM460ex/PPC460EX-1155MHZ/2048MB/RadeonRX550/SSD240GB/DVDRW  :-P

Please note that commit is only in the master branch, and was not a part of the 2.0.12 release.
So you have to build the master, or wait for the 2.0.13 test build.

Hola capehill
El 14-07-2020, escribiste:

Please note that commit is only in the master branch, and was not a part
of the 2.0.12 release.
So you have to build the master, or wait for the 2.0.13 test build.

Ok then, I tested latest 2.0.12 release/build. Will download 2.0.13 compile and see what happens.
THX
Saludos
AOS4.1/SAM460ex/PPC460EX-1155MHZ/2048MB/RadeonRX550/SSD240GB/DVDRW  :-P

Hola capehill
El 14-07-2020, escribiste:

Please note that commit is only in the master branch, and was not a part
of the 2.0.12 release.
So you have to build the master, or wait for the 2.0.13 test build.

Seems I need to wait to 2.0.13, 'cos trying to compile under OS4 I got some errors when compiling src/video/amigaos4/SDL_os4opengl.c, maybe I have old minigl headers.
my proto/minigl.h is:
*
**  $Id$
**  Includes Release 50.1
**
**  Prototype/inline/pragma header file combo
**
**  (C) Copyright 2003-2005 Amiga, Inc.
**      All Rights Reserved
*/
and mgl/minigl.h:
*

$Id: minigl.h 493 2015-08-03 16:58:26Z sbiro $

$Date: 2015-08-04 04:58:26 +1300 (Tue, 04 Aug 2015) $
$Revision: 493 $

*(C) 1999 by Hyperion

All rights reserved

This file is part of the MiniGL library project
See the file Licence.txt for more details

*/
THX anyway.
Saludos
AOS4.1/SAM460ex/PPC460EX-1155MHZ/2048MB/RadeonRX550/SSD240GB/DVDRW  :-P

What kind of errors? Have you tried to install the latest available MiniGL from OS4Depot?

Hola capehill
El 19-07-2020, escribiste:

What kind of errors? Have you tried to install the latest available
MiniGL from OS4Depot?

Nopr, :-( using os4depot minigl includes, no problems :-)
and PrtScreen (checkkeys) key shows/works fine:
#make -f Makefile.amigaos4
ppc-amigaos-gcc -gstabs -O2 -Wall -ISDK:Local/newlib/include/SDL2 -DHAVE_OPENGL   -c -o checkkeys.o checkkeys.c
ppc-amigaos-gcc -o checkkeys checkkeys.o -lSDL2 -athread=native
#checkkeys
INFO: Initial state: modifiers: (none)
INFO: Key pressed :  scancode 70 = PrintScreen, keycode 0x40000046 = PrintScreen  modifiers: (none)
INFO: Key released:  scancode 70 = PrintScreen, keycode 0x40000046 = PrintScreen  modifiers: (none)
INFO: Key pressed :  scancode 70 = PrintScreen, keycode 0x40000046 = PrintScreen  modifiers: (none)
INFO: Key released:  scancode 70 = PrintScreen, keycode 0x40000046 = PrintScreen  modifiers: (none)
INFO: Key pressed :  scancode 71 = ScrollLock, keycode 0x40000047 = ScrollLock  modifiers: (none)
INFO: Key released:  scancode 71 = ScrollLock, keycode 0x40000047 = ScrollLock  modifiers: (none)
...
THX a sorry for all the hassle.
Saludos
AOS4.1/SAM460ex/PPC460EX-1155MHZ/2048MB/RadeonRX550/SSD240GB/DVDRW  :-P

Nice to hear it works. I guess this one can be closed then.


Build system transition

For the sake of #1 and #2, this needs to use node-pre-gyp and boost-lib. Since the latter is actually a CMake project, need to do the following:

[ ] Convert module's binding.gyp to CMakeLists;
[x] Use CMake's ExternalProject to handle building of libtorrent-rasterbar
[ ] Make a shim between gyp and CMake via gyp's actions

Second: libtorrent has its own CMake inside


Insufficient type narrowing of object with a union property

TypeScript Version<EMAIL_ADDRESS>(typescript@next)

Search Terms: union property type narrowing
Note: this is two bugs in one but they look related.  "Issue 2" might actually be more damning.
Issue 1
Code
// Compile with `tsc --strictNullChecks` maybe1.ts
type Base = { bar: number };
type MaybeFoo = Base & { foo: string | null };
type HasFoo = MaybeFoo & { foo: string };

export function useMaybeFoo(maybeFoo: MaybeFoo) {
  if (maybeFoo.foo !== null) {
    const hasFoo: HasFoo = maybeFoo;
  }
}

Expected behavior:
Should compile because the conditional should have narrowed the MaybeFoo to a HasFoo.
Actual behavior:
maybe1.ts:7:11 - error TS2322: Type 'MaybeFoo' is not assignable to type 'HasFoo'.
  Type 'MaybeFoo' is not assignable to type '{ foo: string; }'.
    Types of property 'foo' are incompatible.
      Type 'string | null' is not assignable to type 'string'.
        Type 'null' is not assignable to type 'string'.

7     const hasFoo: HasFoo = maybeFoo;
            ~~~~~~

Playground Link: click
Related Issues: had a quick search but couldn't anything
Workaround
This code is exactly the same, but compiles
// Compile with `tsc --strictNullChecks` maybe2.ts
type Base = { bar: number };
type NoFoo = Base & { foo: null };
type HasFoo = Base & { foo: string };
type MaybeFoo = NoFoo | HasFoo;

export function useMaybeFoo(maybeFoo: MaybeFoo) {
  if (maybeFoo.foo !== null) {
    const hasFoo: HasFoo = maybeFoo;
  }
}

Playground Link click
Issue 2
Now let's try using the same type definitions as maybe2.ts, but try creating a MaybeFoo:
// Compile with `tsc --strictNullChecks` maybe3.ts
type Base = { bar: number };
type NoFoo = Base & { foo: null };
type HasFoo = Base & { foo: string };
type MaybeFoo = NoFoo | HasFoo;

export function makeMaybeFoo(foo: string | null): void {
  const maybeFoo: MaybeFoo = {foo: foo, bar: 3};
}

Expected behavior:
Should compile.
Actual behavior:
maybe3.ts:7:9 - error TS2322: Type '{ foo: string | null; bar: number; }' is not assignable to type 'MaybeFoo'.
  Type '{ foo: string | null; bar: number; }' is not assignable to type 'HasFoo'.
    Type '{ foo: string | null; bar: number; }' is not assignable to type '{ foo: string; }'.
      Types of property 'foo' are incompatible.
        Type 'string | null' is not assignable to type 'string'.
          Type 'null' is not assignable to type 'string'.

7   const maybeFoo: MaybeFoo = {foo: foo, bar: 3};

Playground Link click
Issue 2 Workaround
Changing back to the original type definitions fixes it:
// Compile with `tsc --strictNullChecks` maybe4.ts
type Base = { bar: number };
type MaybeFoo = Base & { foo: string | null };
type HasFoo = MaybeFoo & { foo: string };

export function makeMaybeFoo(foo: string | null): void {
  const maybeFoo: MaybeFoo = {foo: foo, bar: 3};
}

Playground Link: click

Issue 1 is a duplicate of #30506.
Issue 2 is a duplicate of #33243, I think.

Issue 1 is a duplicate of #30506

Yup.

Issue 2 is a duplicate of #33243, I think.

Yeah, seems related or the same.  The workaround Expand workaround it describes works for my case.
Thanks!  Feel free to dedupe, although I think my explanation of Issue 2 is more minimal than #33243

I will always be against having this narrowing implemented because of,
https://github.com/microsoft/TypeScript/issues/33205#issuecomment-527313227

Your second example (alleged workaround) is saying a very different thing from the first example

type MaybeFoo = NoFoo | HasFoo;

And
type MaybeFoo = Base & { foo: string | null };

Are not the same type and should not be treated the same

Great point.  So you're saying they're not equivalent because you can reassign foo.
Would the types be equivalent if all the properties were readonly?  Sprinkling readonly everywhere doesn't make any of the errors go away.

Ah, I just read the discussion on #33205 where you covered why readonly doesn't change anything (because it's not absolute).  I agree now that Issue 1 is working as intended.
What do you think about Issue 2 though?

For issue 2, it makes sense that the assignment should be sound.
It's an object literal that is not referenced elsewhere.
I'm not sure if it'll be marked as a duplicate of something else or "design limitation", though.

I’m pretty sure issue 2 is a bug as per my first comment. If you remove the intersections and just use a union of object literals it works

Ah. It wasn't obvious to me the issues were indeed related because I was stuck on the fresh object literal part.
I didn't try to remove the intersection =x


Make error on Ubuntu 20.04  on rethinkdb 2.4.1

Stack currently is Ubuntu 20.04 amd64
RethinkDB 2.4.1
followed the instructions on the RethinkDB website up to the build commands.
upon running make
I received this error:
[1/282] CC build/release/obj/clustering/table_manager/table_meta_client.o c++: fatal error: Killed signal terminated program cc1plus compilation terminated. make[1]: *** [src/build.mk:379: build/release/obj/clustering/table_manager/table_meta_client.o] Error 1 make: *** [Makefile:53: make] Error 2

The scope of this issue for resulution is to update the website instructions.

The website has been updated at https://rethinkdb.com/docs/install/ubuntu/ .  We no longer need CXX=clang++ but the instructions are updated with other changes like python3.


[Android] Some of the outgoing tx for ERC20, ERC721, ETH are displayed as custom tx

@liliya-soroka commented on Thu Aug 06 2020
Describe the bug
Custom transactions are displayed for some of the ERC20, ERC721, ETH outgoing tx
Actual for the transactions in waiting for confirmation and executed statuses
To Reproduce
Steps to reproduce the behavior:
ERC20 and ERC721:

Go to the safe 0x1230B3d59858296A31053C1b8562Ecf89A2f888b
Open transactions details
Check txs with nonce 176,175,174

ETH:

Go to the safe 0x938bae50a210b80EA233112800Cd5Bc2e7644300
Open transactions details
Check txs with 46

Expected behavior
If it's outgoing ERC20 or ERC721 tx it should be displayed as outgoing tx ( not custom)
Screenshots
in android app
on web
Smartphone (please complete the following information):

Device: Huawei P30
Android Version: 10
App Version 1.12.1-79

Additional context
Add any other context about the problem here.

Technical note:
check_sender_or_receiver should not be applied of method is transfer

NFT symbol is not used for undefined ERC721 safe =0x938bae50a210b80EA233112800Cd5Bc2e7644300 , staging Rinkeby

the fallback for the token symbol (NTF for ERC721 and ? for ERC20), that should be handled by the client imo (as the service just returns no info in that case) cc @safe-mobile


change position id to work for dynamic tests

changes id to {{rel_test_file_path}}:{{test_position}}
appends file write for multiple errors within a single dynamic test
updates status for dynamic tests considering all individual statuses

Marking it draft since I'm not sure if I've covered all cases and would like some feedback if the approach is okay

I like the approach. I was thinking about using the test lines as well differently, but this is simpler.
I'll try to test it on my own tonight.

I'm trying this PR. The position id seems to work correctly.
I found an issue where the output of the command doesn't clear between runs. Like if you do NeotestOutput at the top of the file, you will see the output repeated and every time you run, it adds to that same output.
It doesn't happen when I switch back to master.

I just rebased on master, and couldn't reproduce the issue. Could you try again to see if the issue still persists?

I didn't notice the streaming results part. I think I should update code there as well?

I just rebased on master, and couldn't reproduce the issue. Could you try again to see if the issue still persists?

Indeed, I couldn't reproduce it either. Seems to be gone.

I didn't notice the streaming results part. I think I should update code there as well?

I think so, yes.

I think this is ready!

One scenario I noticed is when there's a test like this
    for i <- [1, 2, 3] do
      test "weird test: #{i}" do
        if unquote(i) == 2 do
          assert false
        else
          assert true
        end
      end
    end

that passes for 1,3 but fails for 2. The sign indicator shows a pass (green tick) first then changes to error(:red tick). Due to streaming the above mentioned transition (pass to error) happens twice. I think it would be hard to fix this right now, but we can consider it as an improvement to fine tune later on

Yes, that can be left as an improvement.


Change in behavior in how diagnostic squiggle is shown between v1.61 and 1.62+

VS Code version
1.62.1
Extension version
2021.11.1422169775
OS type
Windows
OS version
10
Python distribution
python.org
Python version
3.10
Language server
Pylance
Expected behaviour

Actual behaviour

Steps to reproduce

use this config in settings.json:{
    "python.linting.mypyArgs": [
        "--show-column-numbers"
    ],
    "python.linting.mypyEnabled": true,
    "python.analysis.typeCheckingMode": "off"
}

cause a type error, eg:def foo(value: int) -> None:
        ...

foo("asasdf")

Logs
> ~\proj\.venv\Scripts\python.exe -m mypy --show-column-numbers ~\proj\Sandpit\foo.py
cwd: ~\proj
> "~\proj\.venv\Scripts\activate.bat && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python c:\Users\user\.vscode\extensions\ms-python.python-2021.11.1422169775\pythonFiles\printEnvVariables.py"
##########Linting Output - flake8##########
##########Linting Output - mypy##########
Sandpit\foo.py:5:5: error: Argument 1 to "foo" has incompatible type "str"; expected "int"
Found 1 error in 1 file (checked 1 source file)
> ~\proj\.venv\Scripts\python.exe ~\.vscode\extensions\ms-python.python-2021.11.1422169775\pythonFiles\testing_tools\unittest_discovery.py . *.py
cwd: ~\proj

Code of Conduct

[X] I agree to follow this project's Code of Conduct

You're right, I forgot about this change. The editor used to artificially expand zero width diagnostics (empty ranges) on the word next to the diagnostic.
I changed this for https://github.com/microsoft/vscode/issues/66482 where there were examples where expanding to the word next to the diagnostic is not desirable (e.g. missing semicolon at end of line).

Thank you for picking this up. I'm not sure if I properly understand the original issue from the ticket you mentioned where change of this behaviour was implemented, but I hope there's no conflict in resolution. I'm looking forward to testing the fixed version!

Reverted 51e883793d162727c0e50427ddb0e7f12251c37c and pushed ae7bdc119fca3c34eddf18ec3945da19a55848e2 as an alternative fix for #66482

@alexdima Which version will this fix be included in? v1.65?

Yes, v1.65.

Still seems to repro for me in 1.65-insider:

Verified based on new steps:

@alexdima This is the diagnostic object we get back after parsing mypy output:
{
    "severity":"Error","message":"Argument 1 to \"foo\" has incompatible type \"str\"; expected \"int\"",
    "range": {
        "start"{"line":3,"character":4},
        "end": {"line":3,"character":4}
    },
    "source":"mypy",
    "code":"error"
}

I believe since the diagnostic is falling on " it is treating it as a non-word character, hence not highlighting the entire word. I verified that mypy returns the same bit of information from previous versions.

@karthiknadig Then this issue was always there, because the current behavior matches that of 1.61. If a zero-width error lands in a non-word character, it is rendered with the width of 1ch. You can also try 1.61 or older versions of VS Code using the download links at the top e.g. https://code.visualstudio.com/updates/v1_61

@karthiknadig At this point, VSCode has "fixed" the issue on this side, which ultimately ends up in a breaking change. Now it's time for the Python extension to alter how the MyPy and Flake8 output is parsed, so that the "parsed diagnostic object" you get will actually span the entire argument. Given your example code as test.py:
def foo(v:int):
    pass

foo("something")

..., this is the raw MyPy output (with --show-column-numbers) for it:
test.py:4:5: error: Argument 1 to "foo" has incompatible type "str"; expected "int"

..., which should result in a diagnostic object along the lines of:
{
    "severity":"Error","message":"Argument 1 to \"foo\" has incompatible type \"str\"; expected \"int\"",
    "range": {
        "start"{"line":4,"character":5},
        "end": {"line":4,"character":15}
    },
    "source":"mypy",
    "code":"error"
}

Note that I've included the exact range here. Alternatively, the existing solution with the 5th column could be moved 1 character to the right so that it lands on s, and then the resulting 0-width range would expand to either something or "something". Not sure which one of the two it'd do, so it'd need some testing.
Also, I've installed v1.61.2 and downgraded the Python extension solely to see what would happen, and this is the result:

And the same from v1.60.2:

I even tried v1.53.2 (January 2021, from a year ago), but it looks like you can't go too far back in time without everything collapsing (the Python extension didn't even start because Jupyther crashed), so I'll leave it at that.

@DevilXD where is the end part of the range coming from? From the raw output that you have from mypy I see the start 4:5 but not the end range. Without the tool telling us the exact range, how do we know where to stop?
test.py:4:5: error: Argument 1 to "foo" has incompatible type "str"; expected "int"

I don't see how we can take this (without knowing what exact issue that the linter might be talking about) and translate it to range 4:5 and 4:15. What if the linter as complaining about the type of quote (literal character) that was used vs the entire string. If we for some reason squiggle the entire string it might be wrong. For the best experience here we need the range from the tool.
An interim solution could be:

[Option 1]: Change the logic @alexdima quoted here https://github.com/microsoft/vscode/issues/142810#issuecomment-1054311122 to special case ". Include the full range of the quoted string.
[Option 2]: From the extension, parse the python content and figure out which token marker that the diagnostic lands on. Doing this from the python extension right now is going to be very expensive. We will have to run two separate scripts to get this answer. First to get the raw linting, and again to parse python and get full ranges. We can do this, but this is a massive change and probably not the way we want to go.
[Option 3]: We do have a prototype extension for that wraps linters into their own extension and does this entirely over LSP. https://github.com/python/mypy/issues/12168 . We have lot more freedom there to parse python and send back better ranges. This would be the best interim solution (until tools provide full ranges), but again might take some time to develop. Also, depends on where the ownership of that lands.
[Option 4]: A way to do this without domain specific info on the range is to get this from the language server. This means that it would be a feature to add on to the LSP.

@alexdima I feel Option 1 might be something we could do now. If that is not the route we want to take, then the next best option is [option 3] for the individual linting extensions to be ready. If you have another recommendation, let me know.
Neiter of the above options provide the best experience, ideally this range should come from the tools themselves. pylint recently added start and end ranges to their lint output. Hopefully, other tools also adopt this.
/cc @luabud @brettcannon

where is the end part of the range coming from?

Yes, this is the part where I'm not familiar with how the internals of the extension work, so it'd be "up to figure out". I can see that you've already listed several options, neither of which are trivial. What about the shifting approach then? Still using the 0-width range, but placing it 1 character further to the right, so that it lands on the initial s in something and expands to the whole word automatically? Feels a little bit hacky, but should generally work for most cases I'd think. Only case I can think of where it could not work properly, would probably be an empty string, where it'd underline the second quote only. Still, I think it'd be simple and good enough for now.

@karthiknadig Adding a special case for " is not an option.

The logic of expanding a zero-width diagnostic to the word it touches is driven by the word definition for the current language, which is defined via language configuration. Going outside of the configured word definition and giving special meaning to " as the beginning of a string is not something we can do in the core of the editor. There are languages we must support where " is not the beginning of a string, e.g. " can be the beginning of a line comment, etc.
Even adding something special for " does not solve the underlying problem. I think the first argument could be an expression which results in a string, so the " heuristic would not fly for foo(("a"+"b")).

I suggest that either the extension which can understand the underlying python syntax tries to massage the error or otherwise I suggest that you reach out to the maintainers of mypy and ask them for a special CLI flag or something that would output the errors in a format which contains a range, not just a position.

I just had a go at 1.65.0-insiders to see what's changed.
I should stress that the issue with underscoring the right element I could see in all linters that I use simultaneously, that is: pylint, flake8 and mypy which is quite apparent when I browse larger codebase.
For our test case I compared results of 1.65 to 1.64.2 and 1.60.2  stable and my observations are as follow:

mypy seems to be indeed just one char underscore for this error
flake8 reporting is now fixed - I can see whole words rather than characters underscored (red squiggles on value: , foo call or pass indentation)
there's still something off comparing to 1.60.2 that seems to be related to pylint

the newer vscode versions underscore whole function definition with blue squiggle rather than just def word like before - in this case it is 'disallowed foo name' and missing docstring
unused argument 'value' yellow squiggle got expanded to value:int rather than just value (again I considered that cleaner in the earlier version)

1.65.0-insider:

1.64.2

1.60.2

@moto-ctrl Regarding pylint. We recently added support for error ranges. Those aren't perfect yet, but we (the pylint team) are working on improving them for the next release. Please take a look at https://github.com/PyCQA/pylint/issues/5466
Like others have mentioned already, this is different to mypy and flake which both only report a position, not a range, which VS Code then has to interpret. What is being discussed here is how that behavior has changed / should be changed going forward.

ah I see, so the old version of vscode didn't understand ranges therefore even with latest pylint it still just highlights only the first word (def in this case) whereas new vscode parses ranges and the highlight of the whole function comes from the pylint itself - which is being discussed in the issue you linked. Thanks for clarifying that.
I'm going to stand by my earlier statement - old style looks the best :-)

ah I see, so the old version of vscode didn't understand ranges therefore even with latest pylint

Correct, we had to add range support to pylint first, after which I contributed a patch to the VSC Python to actually use them.

I'm going to stand by my earlier statement - old style looks the best :-)

We, the pylint team, would appreciate feedback about specific issues with ranges (in the pylint repo). Probably best after the next update though since that will already address a lot of issues.
Another point, I've seen discussions about custom language server extensions for Python linters the VSC Python team is working on. A switch to select positions or ranges for highlighting might be a good suggestion.

And something else occurred to me - sorry this was perhaps obvious but I'll write it down for benefit of everyone

blue squiggle that covers all function - comes from pylint and how it reports error ranges. Will be fixed in pylint.
red squiggles from mypy and flake8 - don't report ranges yet, vscode used to handle it by underscoring whole words and that feature has been brought back and is fixed in this ticket
however in some edge situations - like error pointing special character as in mypy example - this is not currently expanded due to more complex algorithm required for detection

Here's my example with mypy and flake8 (switched off pylint to get better picture)
I changed foo definition to take string rather than int and can confirm the fix is working pretty much as expected
(value, pass, foo errors come from flake8, 12345 comes from mypy)
1.65-insiders

1.64.2

so as this is issue is still not resolved, can it be re-opened and transferred back to the vscode-python repo? or should i re-raise it there?

@DetachHead I think this issue is addressed from VS Code.
There are now two issues:

On mypy, to provide ranges on the reported items. This will resolve the problem in all scenarios.
On vscode-python, to detect and expand the squiggle, for the " case, temporarily only for mypy, until mypy provides ranges.


New Feature Issue Creation template

We will need an issue template for creating new issues, similar to how we did for bug report
Similar to how we did it on https://github.com/rad-ui/ui/pull/492

fixed


Authorization Code Flow

Is PKCE utilized in the Auth Code grant flow? I tried the other grant types that mention proof key in them explicity, but the only one that round tripped for me was the simplest auth code flow. I had the code challenge and challenge method parameters included in the request.

PKCE is not implemented yet.

Any ballpark on an ETA? Thanks.

In the next months.


asyncio: fix event mask conversion with multiple events

Fix KeyError when multiple events are available on one socket
closes #775

Oddly enough, this fix works for me on Python 3.5.1, but I still get a KeyError on Python 3.4.3. Not sure what the difference between the versions is.

Can you show the full traceback you get from Python 3.4?

Fixed the error on 3.4


Fixed bug that when sending data by Post

Signed-off-by: Alisson Fabiano<EMAIL_ADDRESS>Hey, I just made a Pull Request!
Fixed bug when sending data by Post in runChecks and runBulkChecks functions of the TechInsightsClient class, the default Content-Type used was plain/text
Here we have a link for reference here this error has been included
https://github.com/backstage/backstage/pull/13755
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

I think the root cause for both this and https://github.com/backstage/backstage/issues/14140 is be the same. Now I am not sure what happens under surface but we need to check if 'content-type' is empty rather than if it exists.

Are you saying that .has does NOT return a boolean?

@freben Ah I made a mistake there, it does return boolean, I can see why this worked, of course the condition was satisfied all the time this way 😫 However, I did notice one thing.
request.headers.get('content-type') will give 'text/plain;charset=UTF-8', when we actually need it to be set to 'application/json'

Alright, no worries - let's continue in the thread above, I still think that we would be better off reading out of the input parameter than the copy which has this odd behavior.

Thank you for contributing during Hacktoberfest 🍂! You can claim the Backstage Hacktoberfest Holopin at https://bck.st/hacktoberfest-holopin 🙌🏻

What do you all think about releasing this as a bug fix (I think it would be 0.32.2) rather than waiting the standard 3 "next" release cycles?

@jhaals What do you think about putting this out as a patch release rather then waiting for the next minor release in a couple weeks?

Thank you so much for the patch!!


Target Manager fails on Target Refresh with Atom 1.21.0 beta

Hi,
today I tried my build providers (scons, mbed) with Atom 1.21.0 beta with  build 0.68.0. For both, I get an exception when the build package comes to the point where it tries to refresh targets (see below). The issue could be trigered by adding a new project folder or by calling Build: Refresh Targets. I also tried with thebuild-make, same thing. I looked into the code, but it is not obvious to me what the problem is.
Also I know it might be too early to investigate that issue since 1.21.0 is still beta. Just though it might be good to be aware of this.
Regards,
Stefan
Cannot read property 'split' of undefined
Hide Stack Trace
TypeError: Cannot read property 'split' of undefined
    at Object.humanizeEventName (/usr/share/atom-beta/resources/app/node_modules/underscore-plus/lib/underscore-plus.js:196:29)
    at extractDescriptor (/usr/share/atom-beta/resources/app/src/command-registry.js:447:74)
    at new SelectorBasedListener (/usr/share/atom-beta/resources/app/src/command-registry.js:414:29)
    at CommandRegistry.addSelectorBasedListener (/usr/share/atom-beta/resources/app/src/command-registry.js:163:36)
    at CommandRegistry.add (/usr/share/atom-beta/resources/app/src/command-registry.js:152:25)
    at /home/stefan/dev/atom-beta/packages/build/lib/target-manager.js:113:54
    at Array.forEach (native)
    at /home/stefan/dev/atom-beta/packages/build/lib/target-manager.js:108:18

Oh, just realized, that this seams to be a duplicate of #532.

dupe of #532

Thanks for fixing. Works nicely now :-)


Pin version for public_suffix dependency

The public_suffix gem dropped support for ruby < 2.1.
As a consequence this breaks 1.x release with ruby 2.0. The public_suffix gem should should be pinned to an earlier version in sensu-plugins-dns .
I'm not exactly sure how to submit this to the appropriate branch. Please consider making a new 1.x release to include the fix.
For more context, we're seeing this in OpenStack:
https://bugs.launchpad.net/kolla/+bug/1781434
Pull Request Checklist
Is this in reference to an existing issue?
General

[ ] Update Changelog following the conventions laid out here

[ ] Update README with any necessary configuration snippets

[ ] Binstubs are created if needed

[ ] RuboCop passes

[ ] Existing tests pass

New Plugins

[ ] Tests

[ ] Add the plugin to the README

[ ] Does it have a complete header as outlined here

Purpose
Known Compatibility Issues

Thanks for your contribution to Sensu plugins! Without people like you submitting PRs we couldn't run the project.
Just to clarify you are shipping sensu-client with ruby 2.0? To my knowledge sensu has never shipped with ruby 2.0.
I have opened #32 to track the overall effort involved in getting everyone to a happy place.

Thanks, we should be safe on our side, we've already capped all the sensu plugins to the x version that supports ruby 2.0. That why it was surprising to see a dep of sensu-plugins-dns break us.
For the record, latest centos (7.5.1804) still ships ruby 2.0.

It looks like sensu-plugin library does not specify a ruby version constraint. We should rectify this so that breakage will be explicit when we stop ruby versions support. I will update that in a major version please make sure you have locked it at ~> 2.5 to avoid breakage.

For the record, latest centos (7.5.1804) still ships ruby 2.0

Ya sensu-client is typically shipped with an omnibus embedded ruby so it does not really depend on the OS packages. As you are packaging it up this is probably different, for future versions it will require installing either from newer repositories or use something like rbenv/rvm to compile and install user other versions outside the OS support into a specific user. Outside of old (unsupported) ruby versions there are other advantages of using a seperate ruby install from the system ruby.

released:

https://rubygems.org/gems/sensu-plugins-dns/versions/2.1.1
https://rubygems.org/gems/sensu-plugins-dns/versions/1.4.1


Trigger tooltip with event listener on element that already has tooltip

Using the tippy.js library (version 4.2.1), I'm trying to display a tooltip on a single element using event listeners.
Currently I'm displaying tooltips when users hover over a tippy('.menuButtons'); and the tooltip text is being auto-populated from an attribute I've given my elements that looks like data-tippy-content: "myTooltipText".
I've recently added a new element in the .menuButtons class called #newMenuItem and want to display it when the user does certain actions using event listeners that I already have implemented.
Looking through the documentation, I see that there's a trigger option in which I can set the type to manual to display it that way, however, I'm not sure how to go about it.
In my JS file, for tippy I have the following:
	function applyTooltips()
	{
		tippy.setDefaults(
			{
				placement: "top-start",
				animation: "fade",
				duration: 500,
				arrow: true,
				size: "large",
				theme: "light",
			}
		);
		tippy('#newMenuItem',
			{
				trigger: "manual",
				content: "This is a new feature! Try it out today."
			});
		tippy('.menuButtons'));
	}

I'm unsure of:
a) Since #newMenuItem already has a tippy when you hover over it, if you can create a new tippy that appears there on eventlisten as well. Or will the customized attributes of the new tippy cause the default on-hover tippy to disappear/not display the on-hover text defined in the data-tippy-content attribute in the HTML.
b) How to define what the manual trigger is (i.e. when a user does a specific action, display the tippy)
To test, I've tried just creating a new function that looks like this:
function testTooltip()
{
    tippy('#newMenuItem');
}

but now the default on-hover tooltip doesn't appear, and a tooltip doesn't appear when I try to call testTooltip() in the console. I've also tried tippy('#newMenuItem').show(); to no avail.

Hi, this is the issue tracker for the React wrapper. Looks like you are looking for this repo instead: https://github.com/atomiks/tippyjs
Feel free to copy/paste this issue there.


Fix typings for ESM-only consumers

Thanks! This repo is a bit behind the makenew template. I'll try to update it soon in case there are more patches like this one.

Should be address now via https://github.com/razor-x/landlubber/pull/4


Rename --show-hidden command-line option

Rename --show-hidden → --all
Rename -h → -a
Add -h for help

I was almost done with this, but then I realized I forgot abut the "-a" switch. It's already used to disable animations. I'm not sure what switch to use for that. I thought about "-s" for static or something, but it's just not as intuitive.
So I'm not sure what to do about this. There are many programs that use "-h" for something other than help. I don't think it's a big deal.


SSL Problems connecting to Protonmail Bridge IMAP

Trying to use imap-backup to pull messages out of protonmail using their bridge.
When I configured the bridge, I tested it with kmail, and kmail can use the bridge imap server, though it gave a warning and I accepted the bridge's self signed ssl certificate, then it worked.
The bridge provides an imap port on localhost port 1143 , so I configured imap-backup thus:
  "accounts": [
    {
      "username": "username",
      "password": "password",
      "server": "<IP_ADDRESS>",

...

      "connection_options": {
        "ssl": {"verify_mode": 0},
        "port": 1143
      }

...

  "debug": false
}

This results in the following SSL error:
Traceback (most recent call last):
        14: from /usr/bin/imap-backup.ruby2.7:23:in `<main>'
        13: from /usr/bin/imap-backup.ruby2.7:23:in `load'
        12: from /usr/lib64/ruby/gems/2.7.0/gems/imap-backup-3.3.1/bin/imap-backup:76:in `<top (required)>'
        11: from /usr/lib64/ruby/gems/2.7.0/gems/imap-backup-3.3.1/lib/imap/backup/configuration/list.rb:18:in `each_connection'
        10: from /usr/lib64/ruby/gems/2.7.0/gems/imap-backup-3.3.1/lib/imap/backup/configuration/list.rb:18:in `each'
         9: from /usr/lib64/ruby/gems/2.7.0/gems/imap-backup-3.3.1/lib/imap/backup/configuration/list.rb:20:in `block in each_connection'
         8: from /usr/lib64/ruby/gems/2.7.0/gems/imap-backup-3.3.1/lib/imap/backup/account/connection.rb:61:in `run_backup'
         7: from /usr/lib64/ruby/gems/2.7.0/gems/imap-backup-3.3.1/lib/imap/backup/account/connection.rb:93:in `imap'
         6: from /usr/lib64/ruby/gems/2.7.0/gems/imap-backup-3.3.1/lib/retry_on_error.rb:4:in `retry_on_error'
         5: from /usr/lib64/ruby/gems/2.7.0/gems/imap-backup-3.3.1/lib/imap/backup/account/connection.rb:98:in `block in imap'
         4: from /usr/lib64/ruby/gems/2.7.0/gems/imap-backup-3.3.1/lib/imap/backup/account/connection.rb:98:in `new'
         3: from /usr/lib64/ruby/2.7.0/net/imap.rb:1093:in `initialize'
         2: from /usr/lib64/ruby/2.7.0/net/imap.rb:1535:in `start_tls_session'
         1: from /usr/lib64/ruby/2.7.0/net/protocol.rb:44:in `ssl_socket_connect'
time="Feb 26 21:47:55.876" level=error msg="cannot send response:  write tcp <IP_ADDRESS>:1143-><IP_ADDRESS>:36288: write: connection reset by peer\n" pkg=server-imap
/usr/lib64/ruby/2.7.0/net/protocol.rb:44:in `connect_nonblock': SSL_connect returned=1 errno=0 state=error: wrong version number (OpenSSL::SSL::SSLError)
time="Feb 26 21:47:55.877" level=error msg="cannot send response:  write tcp <IP_ADDRESS>:1143-><IP_ADDRESS>:36288: write: connection reset by peer\n" pkg=server-imap
time="Feb 26 21:47:55.877" level=error msg="cannot send response:  write tcp <IP_ADDRESS>:1143-><IP_ADDRESS>:36288: write: connection reset by peer\n" pkg=server-imap
time="Feb 26 21:47:55.877" level=error msg="cannot send response:  write tcp <IP_ADDRESS>:1143-><IP_ADDRESS>:36288: write: connection reset by peer\n" pkg=server-imap
time="Feb 26 21:47:55.877" level=error msg="cannot send response:  write tcp <IP_ADDRESS>:1143-><IP_ADDRESS>:36288: write: connection reset by peer\n" pkg=server-imap
time="Feb 26 21:47:55.877" level=error msg="cannot send response:  write tcp <IP_ADDRESS>:1143-><IP_ADDRESS>:36288: write: connection reset by peer\n" pkg=server-imap
time="Feb 26 21:47:55.877" level=error msg="cannot send response:  write tcp <IP_ADDRESS>:1143-><IP_ADDRESS>:36288: write: connection reset by peer\n" pkg=server-imap

Have I missed a configuration option somewhere?
Environment details:
OpenSUSE Tumbleweed
ruby --version
ruby 2.7.2p137 (2020-10-01 revision 5445e04352) [x86_64-linux-gnu]

Hi @processor286
I think the best thing is to work out which ciphers the bridge supports.
imap-backup uses this config by default:
{port: 993, ssl: {ssl_version: :TLSv1_2}}

so, servers needs to support TLSv1.2 for that to work out of the box.
Please run the following:
nmap --script ssl-enum-ciphers -Pn -p 1143 <IP_ADDRESS>

As an example, here's the output I get for GMail's server:
$ nmap --script ssl-enum-ciphers -Pn -p 993 imap.gmail.com
Host discovery disabled (-Pn). All addresses will be marked 'up' and scan times will be slower.
Starting Nmap 7.91 ( https://nmap.org ) at 2021-03-20 12:04 CET
Nmap scan report for imap.gmail.com (<IP_ADDRESS>)
Host is up (0.072s latency).
Other addresses for imap.gmail.com (not scanned): <IP_ADDRESS>
rDNS record for <IP_ADDRESS>: wr-in-f108.1e100.net

PORT    STATE SERVICE
993/tcp open  imaps
| ssl-enum-ciphers:
|   TLSv1.0:
|     ciphers:
|       TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (ecdh_x25519) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
|     compressors:
|       NULL
|     cipher preference: server
|     warnings:
|       64-bit block cipher 3DES vulnerable to SWEET32 attack
|   TLSv1.1:
|     ciphers:
|       TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (ecdh_x25519) - A
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
|     compressors:
|       NULL
|     cipher preference: server
|     warnings:
|       64-bit block cipher 3DES vulnerable to SWEET32 attack
|   TLSv1.2:
|     ciphers:
|       TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (ecdh_x25519) - A
|       TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (ecdh_x25519) - A
|       TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (ecdh_x25519) - A
|       TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 (ecdh_x25519) - A
|       TLS_RSA_WITH_3DES_EDE_CBC_SHA (rsa 2048) - C
|       TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_AES_128_GCM_SHA256 (rsa 2048) - A
|       TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
|       TLS_RSA_WITH_AES_256_GCM_SHA384 (rsa 2048) - A
|     compressors:
|       NULL
|     cipher preference: client
|     warnings:
|       64-bit block cipher 3DES vulnerable to SWEET32 attack
|_  least strength: C

Nmap done: 1 IP address (1 host up) scanned in 4.30 seconds

@processor286 wondering if you ever solved this as I am encountering the same issue.

Sorry no. I needed a robust IMAP solution so I off-boarded from Proton Mail and moved to another provider.

All good. Thanks!

Closing.


unable to install morphio in Windows

Hi,
I didn't have a problem to install your package until early this year.
However, recently I formatted my laptop and got a new computer, so I tried to install anaconda3 and morphio in Windows10 again, but some errors returned to me.
https://github.com/brainglobe/brainrender/issues/159
it looks like morphio requires CMake, which also requires Visual studio.
So should I install visual studio first, and then install CMake then try to install morphio??
Previously I didn't install visual studio but it was fine, so I was wondering what happens now.
Thanks

No update in a while, closing.


[BUG]: Type error when specifying schema for NodePgDatabase

What version of drizzle-orm are you using?
0.26.1
What version of drizzle-kit are you using?
0.18.1
Describe the Bug
When trying to use the newest relation API, I am getting a type error when passing the schema from the docs to the drizzle config.
typescript: Type 'NodePgDatabase<typeof import("/project/packages/db/src/schemas/main")>' is not assignable to type 'NodePgDatabase'.
  The types of '_.schema' are incompatible between these types.
    Type 'ExtractTablesWithRelations<typeof import("/project/packages/db/src/schemas/main")> | undefined' is not assignable to type 'ExtractTablesWithRelations<Record<string, never>> | undefined'.
      Type 'ExtractTablesWithRelations<typeof import("/project/packages/db/src/schemas/main")>' is not assignable to type 'ExtractTablesWithRelations<Record<string, never>>'.

This is the db.ts
import { NodePgDatabase, drizzle } from 'drizzle-orm/node-postgres';
import { Pool } from 'pg';
import { Logger } from "drizzle-orm";
import * as schema from './schemas/main'

export let db: NodePgDatabase;

export function connectDB(logger: Logger) {
	 const pool = new Pool({
		connectionString: getDBUrl(),
	});

	db = drizzle(pool, { logger, schema});
}

schemas/main.ts
import { integer, serial, text, pgTable } from 'drizzle-orm/pg-core';
import { relations } from 'drizzle-orm';

export const users = pgTable('users', {
	id: serial('id').primaryKey(),
	name: text('name').notNull(),
});

export const usersConfig = relations(users, ({ many }) => ({
	posts: many(posts),
}));

export const posts = pgTable('posts', {
	id: serial('id').primaryKey(),
	content: text('content').notNull(),
	authorId: integer('author_id').notNull(),
});

export const postsConfig = relations(posts, ({ one }) => ({
	author: one(users, { fields: [posts.authorId], references: [users.id] }),
}));

Expected behavior
It should just work
Environment & setup
During development in my IDE

The type should be NodePgDatabase<typeof schema>


Supported Games List Typo

Fist of The Nortstar ought to be Fist of the Northstar

Gounnies 2 should be The Goonies 2

https://github.com/spiiin/CadEditor/commit/d531b0bf21c5221cfd363860e6538154779d9262


Remove superfluous AsObservable calls from ReactiveCommand

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Correctness/performance improvement. Fixes #1236.
What is the current behavior? (You can also link to an open issue here)
ReactiveCommand includes a couple of unnecessary calls to AsObservable.
What is the new behavior (if this is a feature change)?
Remove the unnecessary calls.
Does this PR introduce a breaking change?
No.

@reactiveui/reviewers-core any of you fine people want to 👀 this?

LGTM. I imagine this was probably discussed in Slack, but if I were to be picky, I would say the one thing this bug description is missing is a bit of history -- how did those calls come to be in the first place?

@mteper it's hard to say for sure due to the mangled history, but I believe this was just a vestige of the code's evolution. That is, at one point I had written it to use subjects to back CanExecute and IsExecuting. Consequently, I did the right thing and called AsObservable on those subjects. When I improved the code to remove the subjects, I neglected to remove the AsObservable calls.
How do you feel about merging this, following the process set out by @ghuntley?

I've limited time and I'll need to set up a dev environment. If this can wait a week or two, I'll gladly figure out where the process is documented and follow it. If this sounds like I'll be the bottleneck, then I'll bow out.


[clang-tidy] [clang-check] Correctly pass args

Passing the arguments like it was done is not documented and seems to
even override any options, this means that clang is in fact only invoked
with said options, which not only suppresses warnings but also ignores
input from compile_commands.json etc. including include directories.
The correct way to pass arguments to clang is to use -extra-arg=.

What problem are you trying to solve?

Eg. when having a compile_commands.json file it's completely ignored if one passes any flags via the old technique since that overrides any settings. To only make additional settings, one needs to use the extra-arg flag. This is exactly what we want as we want to have the same flags as for a usual build but also flags to disable color output etc.

Easy to reproduce example:
Have a c file include a header that's not in the standard include path, create a compile_commands.json file that specifies said include path. clang-check and clang-tidy would ignore said file, thus always complain about missing include dirs.

Have you considered reading the manual?  F.i. :h syntastic-cpp-clang_check.

What is "correct", and how do you validate correctness?
Does your patch work for all versions of clang-check where the existing code works?
Can you point out a situation where the method described in the manual doesn't work?

This feature was added 5 years ago: https://reviews.llvm.org/D919?id=2275
The correct way is the way it does what it should. Currently, all compiler flags etc. are ignored because the -- overrides. But we just want to add supplemental compiler flags and not replace all flags.
This way we even turn off some warnings that the user might want.

Can you point out a situation where the method described in the manual doesn't work?

It's not "not working" in the strictest sense of the word. It's more "not working as expected". It's also -- strictly speaking -- working as specified.
One can set the post_args to an empty string, but this might mean that the checker output might change and become unparseable; the DB will be read and applied.

It's more "not working as expected".

Then perhaps what needs to be fixed is your expectation.  Defaults are there to be overridden, and you can do that without changing the code.

One can set the post_args to an empty string, but this might mean that the checker output might change and become unparseable; the DB will be read and applied.

It's up to you to prevent that from happening, by passing the correct options to the linter. shrug


Unnecessary code execution in LogValuesFormatter

Title
Unnecessary code execution in LogValuesFormatter. The ctor contains the following code:
https://github.com/aspnet/Logging/blob/5a906a4e8492f709d25a2f7cc737da2915771d44/src/Microsoft.Extensions.Logging.Abstractions/Internal/LogValuesFormatter.cs#L38-L53
However, as formatDelimiterIndex is only ever used inside the else block, it should be moved there, thus removing some unnecessary calls to FindIndexOfAny.
Functional impact
No functional impact, just more optimal code execution.

Sounds like it would make a great pull request.

Fair point, I'll see what I can do....

I have submitted a pull-request. Please review the same and let me know the review comments.


Add output_shape argument to jax.lax.conv_transpose.

TensorFlow v1 and v2 support output_shape argument [link]. Can this be added to JAX?

@tamaranorman was looking at this.

We were looking at it together. I'm a bit stuck now, so I'm hoping to get some tips here. Would it be possible to get the same behavior by manipulating user code (e.g. changing padding)? If so which, arguments would I need to change. If not, what would we have to expose in lax.conv_transpose?
And finally what low-level XLA op is being called by both TF and JAX - that would help in debugging.

In all cases the underlying XLA op is ConvGeneralDilated. To get a specific output shape from the transposed convolution, you simply need compute the correct padding to get that output shape.
One way to deduce the correct padding would be via jax.vjp. A transposed convolution is one of the gradients of a forward convolution, and jax.vjp will already know how to compute the correct padding to get back a particular input shape under transposition.

@levskaya might be able to help here also.

Thanks for the help Peter. I managed to find the function that would produce the desired before and after padding based on the input. Will include it to Haiku soon. For posterity, this is the function:
def compute_adjusted_padding(input_size: int, output_size: int,
                             kernel_size: int, stride: int, padding: int,
                             dilation: int) -> Tuple[int, int]:
  """Compute adjusted padding."""
  effective_kernel_size = (kernel_size - 1) * dilation + 1
  if padding == "VALID":
    assert input_size == (output_size - effective_kernel_size + stride) // stride
    padding_before = 0
  elif padding == "SAME":
    assert input_size == (output_size + stride - 1) // stride
    padding_needed = (output_size - 1) * stride + effective_kernel_size - output_size
    padding_before = padding_needed // 2

  expanded_input_size = (input_size - 1) * stride + 1
  padded_out_size = output_size + effective_kernel_size - 1
  pad_before = effective_kernel_size - 1 - padding_before
  pad_after = padded_out_size - expanded_input_size - pad_before
  return (pad_before, pad_after)

Perhaps it would make sense to add output_shape support to lax.conv_transpose?

Yes I think that would be a great feature. I think that with this function it would be very simple to add. The final bit would be to figure out which input dimensions correspond to which output dimensions. I guess this is stored as part of ConvDimensionNumbers, but I have no clue how to interpret those TBH.

+1 to adding this to lax.conv_transpose

+1 to adding this to lax.conv_transpose

I've added this capability to Haiku. You can find the computation from output_shapes to adjusted padding here.

I've added this capability to Haiku. You can find the computation from output_shapes to adjusted padding here.


Create Documentation

I would like to work on this issue. Kindly assign me

Go for it @Snehil0603

I would like to work on it


How to specify schema search path using knex.raw to call pl/pgsql in postgres

Hi,
I have a pl/pgsql created in the public schema public.foo() which references a table "bar" based on the current schema context (e.g. the table could be schema1.bar or schema2.bar):
CREATE OR REPLACE FUNCTION public.foo() RETURNS TEXT AS
$$
print_strict_params on
DECLARE
user_uuid TEXT;
BEGIN
SELECT uuid INTO user_uuid FROM bar;
RETURN user_uuid;
END
$$
;
Because I uses pl/pgsql, I need use "SELECT public.foo();" to call it. I can't use knex.withSchema().select().from() construct as the query doesn't have a FROM clause, so I resort to use knex.raw(), the only way I can think of is to call "SET SCHEMA xxx" before and reset it after the query. I am wondering if there is better way to do it.
Appreciate any help.
Thanks

This should work..
knex.select(knex.raw('??.foo();', 'public'))
//select "public".foo();


Save multi-part stls

Hello @wolph ,
First of all, thanks a lot for this great package. In the same way multi-part stls can be loaded one by one with the mesh.Mesh.from_multi_file method but I didn't find a way to save multiple meshes as named parts.
I used the following :
combined_mesh = mesh.Mesh(np.concatenate([m.data for m in stl_meshes])) # stl_meshes is a list of Mesh objects
combined_mesh.names = stl_mesh_names # a list of names
combined_mesh.save("combined.stl")

but when loading it back with :
meshes = mesh.Mesh.from_multi_file("./combined.stl")
for m in meshes:
    print(m.name)

I don't get my names list back.
Is this something which is supposed to be supported or not ?
Thanks in advance
version :
pip show numpy-stl
Name: numpy-stl
Version: 3.0.1
Summary: Library to make reading, writing and modifying both binary and ascii STL files easy.
Home-page: https://github.com/WoLpH/numpy-stl/
Author: Rick van Hattem
Author-email<EMAIL_ADDRESS>License: BSD
Location: /home/container_user/.local/lib/python3.8/site-packages
Requires: numpy, python-utils
Required-by:

A "multi" STL file is just a bunch of ASCII (text) STL files concatenated so you can write them by appending multiple meshes to the same file descriptor.
Your version is combining the meshes together into a single file so the names are lost.
To write the meshes separately to the same file this should work:
with open('combined.stl', 'w') as combined_mesh_fh:
    for stl_mesh in stl_meshes:
        stl_mesh.save(fh=combined_mesh_fh)

Great ! Thanks a lot. I was afraid this would write a header multiple times but reading carefully the source code indicated that :

there is no header for ASCII stl files
multi-part stl is not supported in binary file format
Is this correct ? Thanks again for the super fast answer.

That's completely correct :)
I'm not sure which libraries support the multi STL format to be honest... I haven't seen it that much in the wild so far.


Add an option to disable removal of "unused" css rules

Describe the problem
The Svelte CSS preprocessor is removing CSS styles (to produce an arguably minimal result in reducing bundle size) which means:

Components cannot use scoped styles to target any third party components.
Scoped styles cannot target classes that are programmatically added.
Developers are having to resort to using :global styles as a workaround, which causes CSS to leak out of possibly deeply nested components.

Describe the proposed solution
As an alternative, we should be able to have these "unused" CSS removals become warnings on compilation or the ability to completely turn off this feature.
In my opinion, Svelte has no business removing code it regards as "unneeded" especially when there is much better tooling for detecting unused code such as https://github.com/webpro/knip.
Alternatives considered
Tried using the :global flag on style rules, but this results in CSS leaking out of the component, defeating the entire purpose of style scoping.
Importance
i cannot use SvelteKit without it
Additional Information
I realize that this has been requested multiple times and dismissed by certain maintainers, but I view it as important enough to severely impact the adoption of Svelte.

Svelte's feature that scopes styles to components works at compile time via component-specific scoping classes added to the selectors and to the elements. Keeping these styles when the compiler can't see what they match would have to mean either:

The selectors do not get the scoping class, and they become global, affecting all elements on the page, or
The selectors do get the scoping class, but there's no guarantee that the elements they want to match will get it, so you have no idea whether they will apply to the elements in that component that you want them to.

Having a given selector mean radically different things depending on whether the compiler can see during compilation what it applies to is bad. The answer is to use :global(...), which lets you explicitly opt in to global selectors and styles. Keep in mind that you can also wrap part of your selector in :global() and leave the rest scoped to the component.
The reason that certain maintainers have closed all of these issues is because the above is true no matter how many times people ask about it. Until modern browsers ship some other CSS feature that lets us scope styles better, this is the kind of scoping that Svelte is going to have.


Css changes

Made a few small changes while trying to get the hang of the new repo.
Let me know if I did anything horribly wrong @jjeffryes

Looks fine at first glance. I'll test and go over it in detail soon.


Undefined local timezone causes errors on some browsers

https://sentry.inspirehep.net/inspire-prod/ui/issues/20193
Issue appears when momentInstance.format is called but the main reason is momentInstance is created with undefined timezone which means Intl.DateTimeFormat().resolvedOptions().timeZone is undefined for some browsers.

Let's decide if we care to support these browsers: https://sentry.inspirehep.net/inspire-prod/ui/issues/20193/tags/browser/

https://sentry.inspirehep.net/inspire-prod/ui/issues/24135 same issue, happens on author detail pages too.


Git Standards and Workflow Requirements

Create processes, hooks, and standards across my projects and stick to them.

Goal 1 - To have a basic process shared across projects for a common vocabulary and process.
Goal 2 - To combine tools used for testing and release management with personal projects.
Goal 3 - Welcome a community of contributors working to become better individually.
Goal 4 - Merge past professional processes with more independent ways to balance knowledge.

[ ] Workflow
[ ] Hooks
[ ] Standards/Requirements

Workflow

A master branch is always tracking production ready code (i.e. master)
A deployment/release build is created from this branch master
An integration branch is always tracking master, separating the working branches (i.e. develop)
A working branch which contains a feature is a new branch off develop
A working branch which contains a bugfix is a new branch off a feature or master branch
A feature branch that is finished is then merged back into develop
A bugfix branch that is finished can be merged into the feature or directly into develop
A branch (feature or bugfix) being merged into develop a pull request must be created
A commit in the develop branch will become the release candidate
A new branch is created from this commit for the release (i.e. release-x.x.x)
A freeze on this release branch is created to allow for last minute bugfix and qa commits
A merge is made once all tests are done into the master branch
A historical branch is now created from the release-x.x.x branch for future fixes
A production issue is fixed with a hotfix branch created off master


vulnerability in rack

Hello,
version of rack, mailcatcher is using has some critical vulnerability.
Is there any plan to to upgrade rack version to 2.2.3?
https://nvd.nist.gov/vuln/search/results?form_type=Advanced&results_type=overview&search_type=all&cpe_vendor=cpe%3A%2F%3Arack_project&cpe_product=cpe%3A%2F%3Arack_project%3Arack&cpe_version=cpe%3A%2F%3Arack_project%3Arack%3A1.6.13

Thanks for reaching out!
Rack 2 is a big upgrade, I think.
There is a long term effort to refactor mailcatcher onto using async, decoupling from eventmachine, thin, skinny, and sinatra, and then modernising from there.
MailCatcher is designed to be a local development tool run and accessible on only localhost, so until then the linked vulnerabilities do not seem like a considerable threat.


Fix: Replacing empty screens with messages in myworkflow and favorite_workflow fragments

Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Apply the AndroidStyle.xml style template to your code in Android Studio.

[x] Run the checks with ./gradlew check to make sure you didn't break anything

[x] If you have multiple commits please combine them into one commit by squashing them.

UI after changes

Hey @sagar15795 , i think the white background on these screens looks more good than grey. So, we will discuss about the backgrounds while discussing about the color theme for the application. Until, i think the grey is also good.


A cursor position is not restored when switching to and back from a pane without cursor

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
When switching between panes using keyboard, if a pane you switched to is cursor-less (like About or Welcome pane) the cursor position is not restored when returning back to an editable pane. This is similar to #6662 but without a mouse. Mouse works as expected
Steps to Reproduce

Open a new file, enter some text in multiple lines
Open About pane (on macOS Atom -> About Atom
Switch between text pane and About pane using keyboard Cmd-Alt-Arrows or Cmd-Shift-[, Cmd-Shift-]

Expected behavior: When returning to a pane with an edit have a cursor where I left it and move it using arrows or other navigation keys
Actual behavior: Only line number is highlighted and no cursor is visible in the line and no reaction to arrow keys and other typing or navigation inside a pane
Reproduces how often: 100%
Versions
Atom    : 1.18.0
Electron: 1.3.15
Chrome  : 52.0.2743.82
Node    : 6.5.0
apm  1.18.1
npm  3.10.10
node 6.9.5 x64
python 2.7.13
git 2.11.0
macOS Sierra 10.12.5
Additional Information
Clicking on panes does not behave the same way and does what expected.

Thanks for the report, I can reproduce with 1.20.0-dev-116a90fe2 on macOS 10.12.5.


[@vitest/web-worker] Cannot acces the crypto API from vitest web worker

Describe the bug
When testing a web-worker that tries to access the crypto API, it seems that the worker doesn't have access to this API.
It seems that the worker runs in a somewhat isolated context that overwrites self and global, which then breaks access to to self.crypto or global.crypto. (see https://github.com/vitest-dev/vitest/blob/main/packages/web-worker/src/worker.ts#L78-L82)
I'm not entirely sure how to fix that, but maybe there could be an option to provide extra values to the context?
If I'm using happy-dom for example I could expose a few API from there to the webworker.
Let me know what you think
Reproduction
// worker.test.ts
describe("worker", () => {
    it("works", async () => {
        const worker = new Worker(new URL("./worker.js", import.meta.url), {
            type: "module",
        });
        worker.postMessage("test");
    });
});

// worker.js
self.addEventListener("message", (event: MessageEvent<Uint8Array>) => {
    const value = new Uint8Array(32);
    self.crypto.getRandomValues(value);
    console.log(value);
});

This will crash with Cannot read properties of undefined (reading 'getRandomValues')
System Info
System:
    OS: macOS 14.5
    CPU: (8) arm64 Apple M2
    Memory: 121.13 MB / 24.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.4.1 - /opt/homebrew/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 10.8.1 - /opt/homebrew/bin/npm
    pnpm: 9.3.0 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 126.0.6478.128
    Safari: 17.5
  npmPackages:
    @vitejs/plugin-react: ^4.3.1 => 4.3.1
    @vitest/web-worker: ^2.0.3 => 2.0.3
    vite: ^5.3.4 => 5.3.4
    vitest: ^2.0.3 => 2.0.3

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Thanks @sheremet-va 👌
Please let me know when this fix is released, I'll give it a try


Set uploadpack.allowFilter etc on gitea serv to enable partial clones with ssh (#20902)

Backport #20902
When setting.Git.DisablePartialClone is set to false then the web server will add filter support to web http. It does this by using-c command arguments but this will not work on gitea serv as the upload-pack and receive-pack commands do not support this.
Instead we move these options into the .gitconfig instead.
Fix #20400
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

I can still not use the clone filter with SSH on my instance after upgrading to 1.17.2.
The built-in SSH server is used on my instance. Is this related?

It really would have been helpful if you could have tested the proposed PR and stated that it didn't solve your issue BEFORE it sat there for two weeks.

It really would have been helpful if you could have tested the proposed PR and stated that it didn't solve your issue BEFORE it sat there for two weeks.

Sorry for that. I was not aware that I could be more helpful by trying the branch of a PR and responding to the community earlier. Thank you for letting me learn this.

Hi,
we encountered the same problem as @Shuenhoy even after updating to 1.17.3
If I try to clone with ssh i get "warning: filtering not recognized by server, ignoring" but over https it works just fine.
Gitea is running as binary install on a redhat 7.5 with the existing ssh client (i think).
I hope this is not the wrong spot to post this message, if I can help in any other way please tell me :)

@Shuenhoy I have the same problem. Using ubuntu 22.04 LTS and gitea 1.17.3

Please fire a new issue.

Is there an easy way to replicate this issue? The stated replicator:
git clone --filter=tree:0 git@try.gitea.io:olblak/updatecli-mirror.git tree

works fine now.


Support Unicode filenames and folder names

Related: #569, #671, #1274
I'm a Korean speaker and previously named many requests in Korean on Postman and Insomnia.
When I tried to import from them to Bruno, it failed.
After some research, I found that it's because Bruno doesn't support unicode filenames and folder names.
Would there be any problems if Bruno supports Unicode alphanumeric characters on filenames and folder names?

Closed: duplicate


Remove numberpicker module

Description
As the minimum API version has been increased to 16 (4.1) there is no longer a need to depend on the number picker module for backward compatibility.
This PR removes the module and uses the Android framework's NumberPicker view intead

😍


[Feature] Expose publicPath to loader context

Do you want to request a feature or report a bug?
Feature

What is the current behavior?
nested-require-loader uses this._compilation.options.output.publicPath which is set to be deprecated, to set __webpack_public_path__.

What is the expected behavior?
nested-require-loader should use this.publicPath to set __webpack_public_path__.
If this is a feature request, what is motivation or use case for changing the behavior?
Due to nested-require-loader's nature it is required to known public path at loader execution time so it can set __webpack_public_path__ for other loaders, however deprecation of this._compilation will break this loader completely.

@evilebottnawi The problem is that this.publicPath does not exist in loader context.


Twitter moved to fabric

Twtitter plugin moved from Twitter4j to Twitter kit (Fabric)

@llaerto, did you do testing of this stuff?

Yes I did, all methods was working.


Unknown error

I have OpenMediaVault version 5.6.2-1 installed on a VM.
I'm trying to setup the HA integration by using the IP (port 80) and the same username I used before.
Keep in mind that this problem came out about three days ago and I don't know what the cause might be.
`Logger: aiohttp.server
Source: custom_components/openmediavault/omv_api.py:20
First occurred: 11:23:00 (25 occurrences)
Last logged: 11:25:38
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_protocol.py", line 422, in _handle_request
resp = await self._request_handler(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_app.py", line 499, in _handle
resp = await handler(request)
File "/usr/local/lib/python3.8/site-packages/aiohttp/web_middlewares.py", line 119, in impl
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 56, in security_filter_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 18, in request_context_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 72, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 129, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 129, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 150, in post
return await super().post(request, flow_id)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 60, in wrapper
result = await method(view, request, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 106, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 158, in async_configure
result = await self._async_handle_step(flow, cur_step["step_id"], user_input)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 216, in _async_handle_step
result: Dict = await getattr(flow, method)(user_input)
File "/config/custom_components/openmediavault/config_flow.py", line 78, in async_step_user
if not api.connect():
File "/config/custom_components/openmediavault/omv_api.py", line 122, in connect
cookies = load_cookies(self._cookie_jar_file)
File "/config/custom_components/openmediavault/omv_api.py", line 20, in load_cookies
return pickle_load(f)
EOFError: Ran out of input
`

I have no idea what this could mean. Try restarting OMV middleware.

Hi, I restarted OMV and it's services tens of times and I still get the error. I even tried creating a different user and giving it all the permissions.
Scarica Outlook per Androidhttps://aka.ms/ghei36

From: Tomaae<EMAIL_ADDRESS>Sent: Sunday, March 7, 2021 11:55:22 AM
To: tomaae/homeassistant-openmediavault<EMAIL_ADDRESS>Cc: handryck<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [tomaae/homeassistant-openmediavault] Unknown error (#36)
I have no idea what this could mean. Try restarting OMV middleware.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/tomaae/homeassistant-openmediavault/issues/36#issuecomment-792257056, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJUVBZTBF33Q44KGEECHXWDTCNLRVANCNFSM4YXW33WQ.

try to delete file .omv_cookies.json. it could be corrupted.

try to delete file .omv_cookies.json. it could be corrupted.

Where do I find the file?
I tried navigating into the custom_components and I cannot figure out where the file is.
I tried via console and file editor.


Does eshop support i18n ? how to add language ?

Does eshop support i18n ? how to add language ?

Hi,
eshop supports localization. It's a bit complicated because you can localize text, not products ... Eshop uses Total.js localization mechanism, read here:

https://docs.totaljs.com/latest/en.html#pages~Localization
try example https://github.com/totaljs/examples/tree/master/localization-resources


Move deploy to staging back to preDeploy for race condition

Details
Fixes race condition we added with deploy.yml by moving this back into preDeploy which runs under turnstyle which will only allow one staging deploy version to get determined at a time.
Fixed Issues
Fixes race condition we added with deploy.yml
Tests

Merge this PR
Verify it pushes tags and runs a staging deploy on the preDeploy step

Oops, this failed for an unrelated reason. Need to retest.

Retested at it worked!


Tried to join instagram group

Got banned when tried to join instagram group. I need more details about how iitc can handle the new features of discovering all visited and not visited portals.

Sorry for late reply, but there is no instagram group for IITC-Mobile(iOS)..
AFAIK, this feature is supported by IITC-CE's plugin. You can try it in testflight version of IITC-Mobile on iOS or visit iitc.app for Android and Desktop version


Update Automation .NET Overview

Added description, examples, and links to samples. Tagging @eamonoreilly and @jwhit-MSFT as engineer/manager and @CamSoper for documents. Someone on the CDA team with review for sign-off.

:x: Validation status: errors

File
Status
Preview URL
Details

api/overview/azure/index.yml
:x:Error

Details

:x:Error

Details

api/overview/azure/index.yml

[Error] Error transforming model "W:\tssk-o-unknown\raw-\ogk2wlwt.izq\rawmodel\api\overview\azure\index.raw.json" generated from "api/overview/azure/index.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor:

[Error] Error transforming model "W:\tssk-o-unknown\raw-\ogk2wlwt.izq\rawmodel\api\overview\azure\index.raw.json" generated from "api/overview/azure/index.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor:

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

#sign-off

:x: Validation status: errors

File
Status
Preview URL
Details

api/overview/azure/index.yml
:x:Error

Details

:x:Error

Details

api/overview/azure/index.yml

[Error] Error transforming model "W:\kakp-o-f539a2c3\raw-\zhi3t25z.pe3\rawmodel\api\overview\azure\index.raw.json" generated from "api/overview/azure/index.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor:

[Error] Error transforming model "W:\kakp-o-f539a2c3\raw-\zhi3t25z.pe3\rawmodel\api\overview\azure\index.raw.json" generated from "api/overview/azure/index.yml" using "ManagedReference.html.primary.js". Error running Transform function inside template preprocessor:

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Introduce Backend trait for eval

This change updates the way the evaluator targets the quantum backend by introducing a new trait, Backend, that is provides the quantum functionality for the evaluation. The sparse simulator becomes one option for a backend, and other implementers could be included in the future.
As written, this is dependent on https://github.com/qir-alliance/qir-runner/pull/84, since it avoids a dependency on either the qir-backend or qir-stdlib crates in favor of building against just the sparse simulator alone.

Fun, very minor benefit: with qir-backend and qir-stdlib layers are skipped by this change, the WASM module got slightly smaller, going from 1.609 MB to 1.51 MB.


[gsoc] Conclusion Blog Post

This is the blog post, as translated from the Google Doc.

Ok, this needs review from @asb and then it can go forward. I'll let him merge when he's back in the office.

I did just force push a change to give it today's date rather than last week's date, but looked like I missed the merge. Probably not a big issue just felt it's a bit weird for posts to appear with dates in the past.

I agree - I actually pushed a commit a bit before your message that fixes the publish date to today :)


RPC Monitoring and Statistics

[ ] Create an RPC statistics collection interceptor. grpc.UnaryServerInterceptor
[ ] Export stats via expvar

Other possible production monitoring frameworks are possible.

Consider using https://github.com/grpc-ecosystem/go-grpc-prometheus


idf.py has no 'bootloader-encrypted-flash' target (IDFGH-5660)

Environment

Development Kit: ESP32-DevKitC
Module or chip used:  ESP32-WROOM-32
IDF version (run git describe --tags to find it): v4.4-dev-2487-g8131d6f46d
Build System: idf.py
Compiler version (run xtensa-esp32-elf-gcc --version to find it): xtensa-esp32-elf-gcc (crosstool-NG esp-2021r1) 8.4.0
Operating System:  Linux

Problem Description
When using both secure boot v2 and flash encryption, idf.py has no easy way to reflash the bootloader.
Expected Behavior
idf.py has a 'bootloader-encrypted-flash' target which calls esptool with the --encrypt flag.
( Note: for other partitions, one can use 'encrypted-flash', but due to secure boot v2 being enabled, the bootloader partition is expectedly not flashed. )
Actual Behavior
idf.py has no such target.
Fix
Could you add a 'bootloader-encrypted-flash' target to `idf.py, is the same vein there is already 'flash' and 'encrypted-flash' ?

+1 would like to see this, very frequently I am testing boot loader configuration changes on a device that has flash encryption enabled. This would save me time having over having to copy/type out the esptool command every time.


[1.15] Conveyor Belt crash OR Right click with modded item/block Crashes Game

I just got into modded Minecraft and thought this mod looked awesome to learn, but messing with the items I placed a conveyor belt and click the belt with the conveyor belt addons. How can I fix?
EDIT: Anytime I right click one mod item/block with another, then it automatically crashes. Maybe not specific to the belts.
Industrial Foregoing Version:
indusrial foregoing mod 1.15-2.3.0
Titanium Version:
titanium- 1.15.2 - 2.4.0
Crashlog If Applicable (Upload to pastebin/gist):
The game crashed whilst unexpected error
Error: java.lang.NoClassDefFoundError: mezz/jei/api/gui/handlers/IGhostIngredientHandler$Target

Duplicate of #773


[Fern's Documentation] Unlinked link text to a non-existent document

What can be improved
https://docs.buildwithfern.com/overview/cli/fern-register
Text says:

Read more in the Depending on other APIs section.

This section does not exist and there is no link. According to #1543 it may exist in a different repo?
This page appears to currently be a stub and could use more info in general.

Found the Depending on other APIs page in the deprecated-pages folder:
https://github.com/fern-api/fern/blob/main/fern/docs/deprecated-pages/depending-on-other-apis.mdx
Is this then a deprecated feature? If so, then shouldn't the fern register page be removed?

Closing - tracking internally.


Add recognizers (et, lt, pl)

Change Description
Added:

ET IK recognizer
LT national identification number recognizer
PL identity card recognizer

You can verify recognizers using:

ET & LT - europa.eu -> "Get the TIN specifications"
PL - Wikipedia

Checklist

[x] I have reviewed the contribution guidelines
[x] I have signed the CLA (if required)
[x] My code includes unit tests
[x] All unit tests and lint checks pass locally
[x] My PR contains documentation updates / additions if required

/azp run

Thanks! We'll review this shortly. Please also add the new entities to docs/supported_entities.md

@bckamil are you interested in completing this PR?


Use with TypeScript!?

I can't seem to figure out how to use this library with TypeScript (and async/await) .
I'm told either that it returns void or that it returns a promise which then seems to resolve to void when I await for it. Please advice.
import { readJson, readJsonSync } from 'fs-extra-promise';

  // sync
  loadPackage() : Object {
    try {
      return readJsonSync(this.path);
    } catch (err) {
    }
  }

Trying with async:
  async loadPackage() : Promise<Object> {
    try {
      return readJson(this.path);
    } catch (err) {
      return {};
    }
  }

Also tried return readJson(this.path).then(obj => return obj); to no avail.

I have no idea about Typescript - never used it - so I'm not 100% sure how to read your code examples above. In an async function, don't you need to await the response rather than return it?
But... the promise-returning methods have 'Async' on the ends of their names. So in your examples above, I think the method you should be using is fs.readJsonAsync().
So, readJsonAsync(this.path).then(obj => return obj);
Let me know if that solves your problem.
NB This module is just a thin wrapper around fs-extra. It's also worth checking the non-promisified version of the function and see if that works. If not, the problem is probably in fs-extra rather than this module.

Sweet, I thought readJson was async and returned a promise. I didn't notice there was a specific readJsonAsync variant. I will try it out ASAP. Thanks!
Perhaps improve the docs for async/await and also on how to use/install the typings for TypeScript
typings install dt~fx-extra-promise --global --save
Cheers!


Feature Request: Sound ChangeEffect

I really love the way that you've included a .haptic ChangeEffect, and was wondering if it'd be possible to do the same for playing a sound.
Right now I have my own homegrown that I expose through the environment like so
@Environment(\.sounds) private var sounds

And it's invoked by calling the playSound method like this.
sounds.playSound(effect: .plinkSound, source: self.preferences.preferredSoundSource)

I'm envisioning a solution that looks much like .changeEffect(.haptic(.success), value: someStateChanged), but instead of .haptic it would be .changeEffect(.sound(.plinkSound), value: someStateChanged).
I'm also including the complete solution if it can be of any help, or provide any more context, please let me know if there's any more information that would be helpful.
public enum SoundEffect {
    case dataAsset(NSDataAsset)
    case file(filename: String, `extension`: String)
}

public final class Sounds {

    public enum Source: String {
        case none
        case headphones
        case speakers
    }

    private var player: AVAudioPlayer?

    public init() {}

    public func playSound(effect: SoundEffect, source: Source) {
        let shouldPlaySound: Bool

#if targetEnvironment(simulator)
        shouldPlaySound = true
#else
        switch source {

        case .none:
            shouldPlaySound = false

        case .headphones:
            shouldPlaySound = AVAudioSession.sharedInstance().currentRoute.outputs.map(\.portType).contains(where: { $0 == .headphones || $0 == .bluetoothA2DP })

        case .speakers:
            shouldPlaySound = true

        }
#endif

        if shouldPlaySound {
            do {
                try AVAudioSession.sharedInstance().setCategory(.playback, mode: .default, options: [.mixWithOthers])
                try AVAudioSession.sharedInstance().setActive(true)

                switch effect {

                case .dataAsset(let dataAsset):
                    self.player = try AVAudioPlayer(data: dataAsset.data)

                case .file(let filename, let fileExtension):
                    guard let url = Bundle.module.url(forResource: filename, withExtension: fileExtension) else { return }
                    self.player = try AVAudioPlayer(contentsOf: url)
                }

                self.player?.play()
            } catch let error {
                print(error.localizedDescription)
            }
        }
    }

}

private enum SoundEnvironmentKey: EnvironmentKey {
    static let defaultValue = Sounds()
}

public extension EnvironmentValues {
    var sounds: Sounds {
        get { self[SoundEnvironmentKey.self] }
        set { self[SoundEnvironmentKey.self] = newValue }
    }
}

Yeah, makes sense – we're looking into it.


can't jailbreak after updating to 2.0

iOS 15.0
iPhone XR
error "
XPF failed with error: (Set "physmap" failed on "kernelSymbol.pv_head_table")
Patchfinding"

Try 2.0.1

fixed in 2.0.1