If a worker is killed, stale work directories exist

I had a Worker disconnect and then reconnect and then the scheduler logged:
[2023-09-07T08:29:17.678Z WARN  simple_scheduler] Internal error for worker 7b2e3f8d-0afb-4774-82e3-cecef835dbf3: Error { code: AlreadyExists, messages: ["File exists (os error 17) : Error creating work directory /root/.cache/turbo-cache/work/f5596fdea33511e1c7f513873c087faee689c6ee024c9d90d2908c351e5b0e83"] }

I think #129 may still be required.

Worker log:
[2023-09-07T08:29:14.537Z ERROR running_actions_manager] Error sending kill to running action
[2023-09-07T08:29:14.537Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.538Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.537Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.551Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.537Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.555Z ERROR running_actions_manager] Error sending kill to running action
[2023-09-07T08:29:14.555Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.555Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.568Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.555Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.555Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.555Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.582Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.554Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.582Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.599Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.599Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.603Z ERROR local_worker] Error { code: Internal, messages: ["UpdateForWorker stream closed early"] }
[2023-09-07T08:29:14.599Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.599Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.629Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.554Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.538Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.551Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.555Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:15.131Z ERROR running_actions_manager] Could not get child process id, maybe already dead?
[2023-09-07T08:29:14.538Z ERROR running_actions_manager] Could not get child process id, maybe already dead?

I spoke too soon, getting stalls again.  When it stalls the scheduler and remoteexec_proxy CPU usage drops to a tiny amount and get these:
[2023-09-07T14:54:23.990Z WARN  simple_scheduler] Internal error for worker 46ecd873-ab4f-4683-958f-c9b5b1db72b1: Error { code: Internal, messages: ["Receiver went away before receiving EOF : Failed to write eof to fast store in fast_slow store update : --- : Writer was dropped before EOF was sent : Failed to receive data in filesystem store : While processing with temp file /root/.cache/turbo-cache/data-worker-test/tmp_path-cas/fcbb86c63a3e9f318ef3e082d7cb809dcc9df658dd9b22a71477000000000000-10778 : Could not upload data to store in upload_to_store : Error while uploading results"] }
[2023-09-07T14:54:25.290Z WARN  simple_scheduler] Internal error for worker 46ecd873-ab4f-4683-958f-c9b5b1db72b1: Error { code: Internal, messages: ["Receiver went away before receiving EOF : Failed to write eof to fast store in fast_slow store update : --- : Writer was dropped before EOF was sent : Failed to receive data in filesystem store : While processing with temp file /root/.cache/turbo-cache/data-worker-test/tmp_path-cas/fe55b3977c64b4d0408e121f3e62406afb2258b73fbe6e192277000000000000-10888 : Could not upload data to store in upload_to_store : Error while uploading results"] }
[2023-09-07T14:54:27.344Z WARN  simple_scheduler] Internal error for worker dbfeef84-d1ad-4f6f-9f1e-9681195f2e35: Error { code: Internal, messages: ["Receiver went away before receiving EOF : Failed to write eof to fast store in fast_slow store update : --- : Writer was dropped before EOF was sent : Failed to receive data in filesystem store : While processing with temp file /root/.cache/turbo-cache/data-worker-test/tmp_path-cas/0d1a3dcffaedfe4a96e4ab48a6b97b627e407045c8393d63a378000000000000-8344 : Could not upload data to store in upload_to_store : for \"/root/.cache/turbo-cache/work/7403455e0ecaa6f782afa837ca22e09c11802d6424b144758d4dbec5de1d36f5/by/goma/obj/components/safety_check/safety_check/update_check_helper.o\" : Error while uploading results"] }
[2023-09-07T14:54:36.713Z WARN  simple_scheduler] Internal error for worker 46ecd873-ab4f-4683-958f-c9b5b1db72b1: Error { code: Internal, messages: ["Receiver went away before receiving EOF : Failed to write eof to fast store in fast_slow store update : --- : Writer was dropped before EOF was sent : Failed to receive data in filesystem store : While processing with temp file /root/.cache/turbo-cache/data-worker-test/tmp_path-cas/faef7fb3995348a490c099684ef8ff48c5a4d21a44cbaaf55079000000000000-8988 : Could not upload data to store in upload_to_store : for \"/root/.cache/turbo-cache/work/a9ef3a5608d364d407ed72a4542393a99aba5bdf327764eca13b7ba4a7f861ad/by/goma/obj/components/security_interstitials/core/core/bad_clock_ui.o.d\" : Error while uploading results"] }
[2023-09-07T14:54:37.671Z WARN  simple_scheduler] Internal error for worker 02ca6e82-c420-4286-b294-cb61181d3b9b: Error { code: Internal, messages: ["Receiver went away before receiving EOF : Failed to write eof to fast store in fast_slow store update : --- : Writer was dropped before EOF was sent : Failed to receive data in filesystem store : While processing with temp file /root/.cache/turbo-cache/data-worker-test/tmp_path-cas/6e6561700bbfbd48a75972966e5bf527a0f7cea14f3ff50cdf77000000000000-9735 : Could not upload data to store in upload_to_store : for \"/root/.cache/turbo-cache/work/ac584fe072761ea0a2a91e8f5a0b3a203e9db4880927581c3ce4cf405ef0d7ab/by/goma/obj/components/security_interstitials/core/core/safe_browsing_quiet_error_ui.o.d\" : Error while uploading results"] }
[2023-09-07T14:54:37.976Z WARN  simple_scheduler] Internal error for worker 02ca6e82-c420-4286-b294-cb61181d3b9b: Error { code: Internal, messages: ["Receiver went away before receiving EOF : Failed to write eof to fast store in fast_slow store update : --- : Writer was dropped before EOF was sent : Failed to receive data in filesystem store : While processing with temp file /root/.cache/turbo-cache/data-worker-test/tmp_path-cas/64f350e0acf2449906c1e7dea239a9fb5600e73b8a88f2e2fa77000000000000-8368 : Could not upload data to store in upload_to_store : for \"/root/.cache/turbo-cache/work/428835674a916f53f6e8b1fdde29879a719d8a6bb3216f5c954e9a57145861b6/by/goma/obj/components/security_interstitials/core/core/controller_client.o\" : Error while uploading results"] }
[2023-09-07T14:54:38.450Z WARN  simple_scheduler] Internal error for worker 02ca6e82-c420-4286-b294-cb61181d3b9b: Error { code: Internal, messages: ["Receiver went away before receiving EOF : Failed to write eof to fast store in fast_slow store update : --- : Writer was dropped before EOF was sent : Failed to receive data in filesystem store : While processing with temp file /root/.cache/turbo-cache/data-worker-test/tmp_path-cas/148722dcd9a71441c5783525482540187c087ae9d17246f21278000000000000-10085 : Could not upload data to store in upload_to_store : for \"/root/.cache/turbo-cache/work/6f35c0b9223d00b71422bec7c5a8a1a585f9bcd44a840064b25871c762071605/by/goma/obj/components/security_interstitials/core/core/https_only_mode_enforcelist.o.d\" : Error while uploading results"] }
[2023-09-07T14:54:38.509Z WARN  simple_scheduler] Internal error for worker dbfeef84-d1ad-4f6f-9f1e-9681195f2e35: Error { code: Internal, messages: ["Receiver went away before receiving EOF : Failed to write eof to fast store in fast_slow store update : --- : Writer was dropped before EOF was sent : Failed to receive data in filesystem store : While processing with temp file /root/.cache/turbo-cache/data-worker-test/tmp_path-cas/346bbdc66eeff2390a88ac5a1707ef7195645ef122d9c366bc7a000000000000-11609 : Could not upload data to store in upload_to_store : for \"/root/.cache/turbo-cache/work/a03735e7d1e744370ec03f9c39ad99fa6390ce6d607efca2d68a7fa31682cee7/by/goma/obj/components/segmentation_platform/internal/internal/field_trial_recorder.o.d\" : Error while uploading results"] }
[2023-09-07T14:54:39.107Z WARN  simple_scheduler] Internal error for worker 02ca6e82-c420-4286-b294-cb61181d3b9b: Error { code: Internal, messages: ["Receiver went away before receiving EOF : Failed to write eof to fast store in fast_slow store update : --- : Writer was dropped before EOF was sent : Failed to receive data in filesystem store : While processing with temp file /root/.cache/turbo-cache/data-worker-test/tmp_path-cas/9c060331fbf2cf65e497a425ff6f33bde624f64b8fbe41d84178000000000000-11684 : Could not upload data to store in upload_to_store : for \"/root/.cache/turbo-cache/work/5cff60d775f277c693c2ad6a7b4e1f39207dcd97ed67beb3a2adb273315382d9/by/goma/obj/components/segmentation_platform/internal/internal/metadata_utils.o.d\" : Error while uploading results"] }


Update to latest PyTorch which does type inference in torch.tensor()

As of https://github.com/pytorch/pytorch/pull/5997, torch.tensor cares about whether its args are floats or ints:
>>> torch.tensor(0).type()
'torch.LongTensor'
>>> torch.tensor(0.).type()
'torch.FloatTensor'

This violates our assumptions in both testing and initialization.

The bigger problem that I see is that it does not do any type casting when you would expect it to. See below.
>>> import torch
>>> t = torch.tensor([0, 1])
>>> u = torch.tensor([0.0, 1.0])
>>> u * t
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: Expected object of type torch.FloatTensor but found type torch.LongTensor for argument #2 'other'

Or, even int to long:
>>> t = torch.tensor([0, 1], dtype=torch.int32)
>>> u = torch.tensor([0, 1], dtype=torch.int64)
>>> u * t
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: Expected object of type torch.LongTensor but found type torch.IntTensor for argument #2 'other'

This could require a lot of changes in the code, but before undertaking that, is this really the designated behavior for the next release?

@gchanan Has PyTorch casting behavior settled down to the point where we should update Pyro, or should we hold off for a week? (Thanks for the heads up BTW!)

From @colesbury on slack:

We plan to support at least some implicit type casting. I don't think we supported it previously, though

I suppose I noticed this now because a lot of our tensors are now getting converted to long instead of floats.

@fritzo @neerajprad there are a few different things going on here:

type inference: torch.tensor and variable now do type inference based on the data, like np.array does; this is probably what @neerajprad is referring to and we aren't planning to make any changes there.  See PR: https://github.com/pytorch/pytorch/pull/5997
type casting: @apaszke is working on this over in PR: https://github.com/pytorch/pytorch/pull/5864; this is the "you would expect it" case and you can (probably) work around it now by doing the casting yourself, but it might be easier just to wait.

Thanks, @gchanan! Looking forward to seeing https://github.com/pytorch/pytorch/pull/5864 in master.

For fixing 1., if you want a tensor of the default (floating) type, make sure the data has a floating element, i.e. do torch.tensor(1.) instead of torch.tensor(1).

For fixing 1., if you want a tensor of the default (floating) type, make sure the data has a floating element, i.e. do torch.tensor(1.) instead of torch.tensor(1).

Thanks, @gchanan. We were planning to do exactly that. We have a bunch of tensors which were earlier float but are now being inferred as long without the ..


Get Restaurants in City by Cuisine

Currently Jughead only gets the Top 5 Restaurants in any city. Enable Jughead to get the Top 5 radius in a radius of 5Km of a specific area, for a specific Cuisine.

commit id : dd80e7f58eff3fcacabd499b246b6a18cf0523d7


Fix for #548 - List of Spring guides are difficult to read on mobile.

Great, thanks!
Did you already sign the CLA?

Yes, I just signed it. Thanks.

Thanks @briancavalier :+1:


Clarify issues to pass all FAPI R/W OP w/ MTLS conformance tests

By re-running the latest FAPI R/W OP w/ MTLS conformance tests against the latest keycloak to clarify issues to pass all FAPI R/W OP w/ MTLS conformance tests.

KEYCLOAK-15236
KEYCLOAK-14195
KEYCLOAK-14204
KEYCLOAK-14205
https://github.com/jsoss-sig/keycloak-fapi/issues/34

The detailed results can be found on FAPI-SIG Activities Update #1 in JPN


[Flutter GPU] Create a simple package that demonstrates model rendering using Flutter GPU.

This is underway at https://github.com/bdero/flutter_scene/issues/1.

Impeller Scene has been fully ported to Flutter Scene. It supports glTF binaries with PBR, translucency, and animation! This package will continue to evolve as we land features in Flutter GPU.


Miners not syncing

many many many nebra miners aren't able to sync. Theye are stuck at a specific block. Don't give the advice to mail sales@nebra because that would take weeks.
it has something to do with pocv11 and region. Please fix it asap, many people are in trouble

I've the same issue. One of mine miners are indeed stuck at block: 1091824 and the syncing percentage is going down instead of up. It is almost 30 hours now. Please fix this!!! This started after the pocv11 update on 9 nov.

This is not a support channel
Email<EMAIL_ADDRESS>


Add Right Click Menu Save Files In Download Queue

Is your feature request related to a problem? Please describe
Currently if one closes the tab, the downloads get cancelled. There is also no confirmation dialog or any intimation that downloads are ongoing.
Describe the solution you'd like
Regardless of how downloads are added, they must be added to the download queue so they remain independent of the tab they were initiated on. Also the user will be able to see the progress on them as well.
If they are through the download menu item, they will just start automatically.

It's funny tyhat

It's funny that you're posting those issues now since I've started working on this at the beginning of the week. So yes it's totally planned, as it's necessary for the rework of batch downloads I'm planning (necessary for concurrent batch downloads that do NOT take focus, kind of what you described in #1628). 😄
I just pushed a few modifications to add the queue for the right click and monitors (see #1620), it should land in nightly soon.

I don't see any getting added in the downloads page at all.
I always have internet issues for 2-3 hours a day where my VPN randomly fails thus resulting in failed downloads. Like currently it is failing on every 4th/5th image but I still don't get the option to retry them at all...

Currently if one closes the tab, the downloads get cancelled. There is also no confirmation dialog or any intimation that downloads are ongoing.

What was done is to make downloads independent from the tab you're on, so you can now close the tab and nothing will change.
There is no new part in the "Downloads" tab or anything. Because if you just want to add images to the downloads tab, you can already do so. Just use Ctrl + Click (or Ctrl + Shift + Click for range selection) and then click "Add selected". Selected images will be added to the Downloads tab where you can download them like any other download.

I know what that feature is. But it is still more convenient to use the right click save option instead doing Ctrl+Click. At least the program will download simultaneously rather than afterwards the user has to initiate the download manually. For users like me who use VPN for these, its actually bad as we have to live with the VPN even afterwards and wait for the downloads to finish.

I meant adding the downloads to downloads tab, inferred from download queue. I am a user, not the developer of the program. I don't know what you make or name inside it.


Support for datetime[*] numpy dtype

Currently, a pandas DataFrame with a column of eg. datetime[ns] dtype is resulting in an obscure ValueError:
ValueError: cannot include dtype 'M' in a buffer
values = {'time':  ['20190902093000','20190913093000','20190921200000']}
df = pd.DataFrame(values, columns = ['time'])
df['time'] = pd.to_datetime(df['time'], format='%Y%m%d%H%M%S')
df.dtypes

time       datetime64[ns]
dtype: object

# current workaround
df['time'] = df.time.values.astype(int)
akarr = ak.Record({c: df[c].values for c in df.columns})

This is actually waiting on a pybind11 feature: it currently can't ingest datetime64 ('M') or timedelta64 ('m') arrays as py::buffer_info. I think that's being handled in pybind/pybind11#2078 or pybind/pybind11#2085 or both, I'm not sure. (Issue pybind/pybind11#1970 might also be related.)
Either way, we have two dtype enums ready and waiting:
https://github.com/scikit-hep/awkward-1.0/blob/46767d776dcdc825621f8151dbd4289225b09659/include/awkward/util.h#L26-L47
The bigger question, though, is what reducers would mean for these types. ak.sum could make sense for timedelta64, but not datetime64, ak.prod wouldn't make sense for either, though ak.min and ak.max could be extended for either. (Maybe the datetime64 could reuse the uint64 min/max and the timedelta64 could reuse the int64 min/max...)
All the type coersions when concatenating non-temporal and temporal numbers would also have to be added, which is a lot of boilerplate, but straightforward.

It's actually not a pybind11 error, it's a NumPy error:
>>> memoryview(np.array(["2018-01-01", "2019-01-01", "2020-01-01"], "datetime64[s]"))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: cannot include dtype 'M' in a buffer

and that's why we get an error here:
https://github.com/scikit-hep/awkward-1.0/blob/c41360532ed0e36660fcc918965f49451d1d3677/src/python/content.cpp#L1674
To work around this, we'd have to detect it with array.dtype().kind() == 'M' and then get the data pointer, shape, strides, itemsize, and mock up a format manually using the py::array only, with no help from py::buffer_info.
In the py::array class,
https://github.com/pybind/pybind11/blob/6f3470f757cc5162d5f9115ea9e280e071c212fa/include/pybind11/numpy.h#L543-L834
I see everything that we need except the pointer (have to .attr("ctypes").attr("data") to get a Python integer of the pointer, then unbox that as a size_t, then cast that as a void*) and the format string. There is no equivalent of the format string, but I could do py::str(array.dtype()) and cast that as a std::string to get something like "datetime64[s]", which is not a format, but combined with the util::dtype enum telling me it's a datetime64, put in special logic to construct the appropriate Python dtype when turning it back into a NumPy array on the other side. It can't go through the buffer interface, but I should be changing the Python to call to_numpy() as opposed to to_cupy() to accommodate GPU arrays, anyway.

I'd like to thank you, @YannickJadoul, for your help in the above. Feel free to "unwatch" this thread, since giving you credit also pulled you into the GitHub issue as a side-effect.

Hello, is there an ETA on fixing this? I was hoping it would land in 1.0.0.
The underlying numpy issue is 6 years old: https://github.com/numpy/numpy/issues/4983.
I'd have a go, except this is probably not the best "first issue" for someone new to Awkward!

There isn't an ETA, though I've been eyeing it as a medium-priority item. It's on my increasingly-misnamed November bug-fixes project, one of the (currently 3) C++ tasks; the majority are Python tasks and much lower-hanging fruit.
If you're interested in working on this, I can help. In particular, I can give background and status of the problem, answer questions on a PR (open a draft PR early so we can talk), and even on Zoom/other chat for "broader bandwidth" clarifications and context.
Here's some initial background to the status:

Since there are many NumPy versions out there already whose datetime dtypes don't support the buffer protocol, an Awkward implementation of this will have to bypass the buffer protocol. This won't be entirely novel, since CuPy arrays are already handled as a special case in the constructor and a method for output, and NumPy arrays with datetime type would have to be handled something like that. It means that np.asarray(numpyarray) won't work on these NumpyArray instances, but this isn't an issue for the high-level user interface. The high-level interface is an ak.Array class that wraps these NumpyArrays (and other layouts).
Datetime types are already stubbed out everywhere as enum values that have been commented out. So for instance, searching the repo for "datetime64" reveals all the places where a change is needed.
Most of the operations you might do on specialty types are not actually performed by Awkward Array. All ufuncs, for instance, which includes implementations of operator overloads like __add__, __mul__, etc., are passed to NumPy (between unwrapping and rewrapping the one-dimensional NumPy array buried inside the Awkward layout). So most of the things that would be different for date-time types, such as the fact that the difference of two datetime64 arrays is a timedelta64 array, do not need any explicit code in Awkward Array.
The exception to the above is reducers: (see the base case that all reducers eventually reach, NumpyArray::reduce_next). The ReducerSum class, which implements ak.sum, for instance, needs to know how to add elements of an array and hence it needs to know what types they are. But among all the reducers, only ak.count, ak.count_nonzero, ak.min, ak.max, ak.argmin, and ak.argmax could be used on data of date-time type, and possibly ak.any and ak.all if we consider 0 to be false and any other value to be true. Maybe you can ak.sum timedelta64, but not datetime64. ALL of these would be implemented by view-casting the data as int64_t anyway, so there isn't any computation to do, just a proper accounting of types before and after the reduction.
The NumpyArray class has somewhat redundant dtype information: itemsize is the number of bytes in each item, format is the string returned by Python's buffer protocol, and dtype is our own enum, added later to reign in the madness. Part of this "madness" is the platform-dependence of format. On the bright side, that means there's plenty of room to add all the metadata needed to track date-time types through the system. I know that date-times have units, and perhaps these can be put in the format string, since format won't be useful when the NumPy array doesn't pass through the buffer protocol. (I wish I hadn't ever used the buffer protocol—pybind11 made it look like the right way to do this, but there are exceptions like CuPy and date-times that have to work around it.) Since NumPy+Python might start representing date-time types in the format string someday and we don't know what convention they'll choose, perhaps this format string could be prepended by "ak" or something? (It will always be in conjunction with our dtype enum being equal to datetime64 or timedelta64, so maybe that kind of future-proofing is unnecessary.)

The problem of adding date-time dtypes is similar to the problem of adding complex dtypes, which is PR #421, temporarily stopped, but @sjperkins intends to pick it up again. The difference with that case is that Python's buffer protocol does support complex numbers (format strings that start with "Z") and reducers like ak.sum and ak.prod need special calculations for complex types, but date-time types can just be passed through these calculations as though they were int64_t. So they're similar problems, but each is easier/harder in different ways.

Thanks for the extended write up, @jpivarski. I'll dive into the code this weekend and see if I can make some progress. It feels a lot to assimilate for the time I have, so I won't promise a solution.
On the positive side, I am highly motivated to try Awkward for a large scale problem (processing 3m Arrow tables of 1k-1m rows, each with time histories of some related business entities). Time is an intrinsic part of the processing I need to do on this dataset.

Hi @stevesimmons! Let me know if you're willing and able to do this (date-time types in Awkward Array).
If not, I'll move it out of "in progress," but it will be a high priority item for me. There's evidently a lot of interest.
Thanks!

Hi @jpivarski
First off all, I'd like to thank you for Awkward Array – it's so nice to have a tool like this to handle... well, awkward and ragged data structures!
Secondly, while I don't have the skills required to help with the development of the datetime functionality, it's a feature I'd love to see included in Awkward, as I work with at lot of time series data... so please increment the "interest counter" by one ;)

I think this is the top-requested feature right now. I'll keep that in mind and prioritize it accordingly.
I just went searching for a formal upvote tool, but I couldn't find one that

stays open indefinitely (Slideo, which we used to good effect in the PyHEP workshop, only supports week-long events)
lets me pick a list of things to provide upvotes for
ideally, would be something I could insert in the GitHub readme, right next to the Roadmap.

GitHub suggests "thumbs up" on issues, but I don't see a way to make a leaderboard of most thumbs-up issues. No wait, yes I do.
I added instructions for upvoting issues, though it will take some time before enough people do this that the vote is very meaningful.

@jpivarski  Does the sort-by-upvotes view of the open issues aggregate the total number of upvotes in the thread, or just the number of upvotes on the initial post?
At the time if writing, the second result seems to have a single upvote quite a bit down the thread... this behaviour might not be the intended one, when using it to prioritize issues?

@jpivarski  Does the sort-by-upvotes view of the open issues aggregate the total number of upvotes in the thread, or just the number of upvotes on the initial post?
At the time if writing, the second result seems to have a single upvote quite a bit down the thread... this behaviour might not be the intended one, when using it to prioritize issues?

I'll modify the recommended search string to include a filter for nonzero reactions (on the initial comment): is:issue is:open sort:reactions-+1-desc reactions:>0. Only two issues actually have reactions on the initial comment because we've never done this voting thing before.

I'll modify the recommended search string to include a filter for nonzero reactions (on the initial comment): is:issue is:open sort:reactions-+1-desc reactions:>0. Only two issues actually have reactions on the initial comment because we've never done this voting thing before.

I'll modify the recommended search string to include a filter for nonzero reactions

Done: https://github.com/scikit-hep/awkward-1.0/commit/97124efaf9f7f17dc0ae17410ae1113c99f1f147.
Now if anyone is trying to vote, they can check against this list to see if they've actually done it; this might be enough to see that the reaction has to be on the initial comment (or at least, it would prompt a search, rather than just assuming that it worked).

I'll modify the recommended search string to include a filter for nonzero reactions

Done: https://github.com/scikit-hep/awkward-1.0/commit/97124efaf9f7f17dc0ae17410ae1113c99f1f147.
Now if anyone is trying to vote, they can check against this list to see if they've actually done it; this might be enough to see that the reaction has to be on the initial comment (or at least, it would prompt a search, rather than just assuming that it worked).

Hi @stevesimmons! Let me know if you're willing and able to do this (date-time types in Awkward Array).
If not, I'll move it out of "in progress," but it will be a high priority item for me. There's evidently a lot of interest.

I'm afraid I have too many other things on my plate right now and won't be able to work on this. Sorry about that, because this is a feature than lots of people clearly want.

Thanks for giving it a look! I understand that things come up. Also, this does seem to be the most requested feature right now, so it's high on my priority list, too. I'll feel free to work on an implementation when I get a chance.

@drahnreb - please, let me know if this is what you'd expect. Thanks!
    values = {"time": ["20190902093000", "20190913093000", "20190921200000"]}
    df = pandas.DataFrame(values, columns=["time"])
    df["time"] = pandas.to_datetime(df["time"], format="%Y%m%d%H%M%S")
    array = ak.layout.NumpyArray(df)
    assert ak.to_list(array) == [
        np.datetime64("2019-09-02T09:30:00"),
        np.datetime64("2019-09-13T09:30:00"),
        np.datetime64("2019-09-21T20:00:00"),
    ]

@jpivarski Yes, it's fixed. Thanks, great update!
Not sure if this and my comment passed unnoticed.
This is yet another way of dealing with datetime types (besides the confusing and different ways in pandas, numpy and pyarrow including your reported issue). But after giving it a bit of thought it is probably the most concise way. It should be documented though that ak.to_list() always creates lists of np.datetime64 objects independent from - but with the same - input unit.
# numpy converts to `py_datetime` iff possible and same type...
>>> np_ms = np.asarray([np.datetime64('2019-09-02T09:30:00', 'ms')])
>>> ak_ms = ak.Array(np_ms)
>>> np_ms.tolist()
[datetime.datetime(2019, 9, 2, 9, 30)]
>>> ak_ms.tolist()
[numpy.datetime64('2019-09-02T09:30:00.000000000')]

# ...but `py_datetime` does not support `ns` scaled units
>>> np_ns = np.asarray([np.datetime64('2019-09-02T09:30:00', 'ns')])
>>> ak_ns = ak.Array(np_ns)
>>> np_ns.tolist()
[1567416600000000000]
>>> ak_ns.tolist()
[numpy.datetime64('2019-09-02T09:30:00.000000000')]

# ...but `option` typed numpy arrays are of dtype object
>>> np_ms_opt = np.asarray([np.datetime64('2019-09-02T09:30:00', 'ms'), None])
>>> ak_ms_opt = ak.Array(np_ms_opt)
>>> np_ms_opt.tolist()
[numpy.datetime64('2019-09-02T09:30:00.000'), None]
>>> ak_ms_opt.tolist()
[numpy.datetime64('2019-09-02T09:30:00.000000000'), None]

I guess the reasoning for numpy is that a list should preferably hold python native datetime objects if possible/supported.
I do not see a problem here (people are used to unintuitive datetime conversions for a long time). As the current implementation is not vectorized, ak.to_list() is also not performance critical? One could argue, why not just converting to pure int64 (that will prevent convenient arithmetics in pure python and then there is also int96 coercing of timestamps)...


Go to Type Definition does not work for Optional[] Fields

 Environment data

Language Server version: 2022.11.20
OS and version: darwin arm64
Python version (and distribution if applicable, e.g. Anaconda):
python.analysis.indexing: true
python.analysis.typeCheckingMode: off

 Code Snippet
from dataclasses import InitVar, dataclass, field
from decimal import Decimal
from enum import Enum
from functools import cached_property
from typing import Any, Callable, Dict, List, Optional, Union

JSONValue = Union[str, int, float, bool, None, Dict[str, Any], List[Any]]
JSONType = Union[Dict[str, JSONValue], List[JSONValue]]

@dataclass
class PaymentMethodInfo:
    """Uniform way to represent payment method information."""

    first_4: Optional[str] = None
    last_4: Optional[str] = None
    exp_year: Optional[int] = None
    exp_month: Optional[int] = None
    brand: Optional[str] = None
    name: Optional[str] = None
    type: Optional[str] = None

@dataclass
class CustomerSource:
    """Dataclass for storing information about stored payment sources in gateways."""

    id: str
    gateway: str
    credit_card_info: Optional[PaymentMethodInfo] = None
    credit_card_info_test: PaymentMethodInfo = None

    metadata: Optional[Dict[str, str]] = None

 Repro Steps
I create a file with this content, and opened it in Visual Code.
right clicking on credit_card_info and selecting "go to type definition"
 Expected behavior
should behave like the right click and "Go to Type Definition" on credit_card_info_test - that is navigate to PaymentMethodInfo
 Actual behavior
Nothing happens, doesn't navigate to the  PaymentMethodInfo, It does work if removing the Optional[] part.
 Logs

[Info  - 8:04:51 PM] (21957) Pylance language server 2022.11.20 (pyright 470188d0) starting
[Info  - 8:04:51 PM] (21957) Server root directory: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist
[Info  - 8:04:51 PM] (21957) Starting service instance "vscode-test"
[Info  - 8:04:51 PM] (21957) Notebook support: LSP
[Info  - 8:04:51 PM] (21957) Interactive window support: LSP
[Info  - 8:04:51 PM] (21957) No configuration file found.
[Info  - 8:04:51 PM] (21957) No pyproject.toml file found.
[Info  - 8:04:51 PM] (21957) Setting pythonPath for service "vscode-test": "/Users/yuvalyellin/.pyenv/versions/3.9.7/bin/python"
[Warn  - 8:04:51 PM] (21957) stubPath /Users/yuvalyellin/source/temp/vscode-test/typings is not a valid directory.
[Info  - 8:04:51 PM] (21957) Assuming Python version 3.9
[Info  - 8:04:51 PM] (21957) Assuming Python platform Darwin
[Info  - 8:04:51 PM] (21957) Search paths for /Users/yuvalyellin/source/temp/vscode-test
[Info  - 8:04:51 PM] (21957)   /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib
[Info  - 8:04:51 PM] (21957)   /Users/yuvalyellin/source/temp/vscode-test
[Info  - 8:04:51 PM] (21957)   /Users/yuvalyellin/source/temp/vscode-test/typings
[Info  - 8:04:51 PM] (21957)   /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/...
[Info  - 8:04:51 PM] (21957)   /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs
[Info  - 8:04:51 PM] (21957)   /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9
[Info  - 8:04:51 PM] (21957)   /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/lib-dynload
[Info  - 8:04:51 PM] (21957)   /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages
[Info  - 8:04:51 PM] (21957) Adding fs watcher for library directories:
 /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9
/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/lib-dynload
/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages
[Info  - 8:04:51 PM] (21957) Adding fs watcher for directories:
 /Users/yuvalyellin/source/temp/vscode-test
[Info  - 8:04:51 PM] (21957) Searching for source files
[Info  - 8:04:51 PM] (21957) Found 1 source file
[Info  - 8:04:51 PM] (21957) Background analysis(1) root directory: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist
[Info  - 8:04:51 PM] (21957) Background analysis(1) started
(21957) Background analysis message: setConfigOptions
(21957) Background analysis message: setImportResolver
(21957) Background analysis message: ensurePartialStubPackages
(21957) Background analysis message: setTrackedFiles
(21957) Background analysis message: markAllFilesDirty
(21957) Background analysis message: analyze
(21957) [BG(1)] parsing: /Users/yuvalyellin/source/temp/vscode-test/test.py [fs read 1ms] (15ms)
(21957) [BG(1)] parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (35ms)
(21957) [BG(1)] binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/builtins.pyi (15ms)
(21957) [BG(1)] binding: /Users/yuvalyellin/source/temp/vscode-test/test.py (1ms)
(21957) [BG(1)] indexing: /Users/yuvalyellin/source/temp/vscode-test/test.py [found 4] (0ms)
(21957) Indexing Done: /Users/yuvalyellin/source/temp/vscode-test/test.py
(21957) Background analysis message: setFileOpened
(21957) Background analysis message: getSemanticTokens full
(21957) [BG(1)] getSemanticTokens full at /Users/yuvalyellin/source/temp/vscode-test/test.py ...
(21957) [BG(1)]   parsing: /Users/yuvalyellin/source/temp/vscode-test/test.py (1ms)
(21957) [BG(1)]   parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 0ms] (44ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/builtins.pyi (11ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/source/temp/vscode-test/test.py (0ms)
(21957) [BG(1)]   parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/typing.pyi [fs read 0ms] (14ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/typing.pyi (3ms)
(21957) [BG(1)]   parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 0ms] (1ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/typing_extensions.pyi (5ms)
(21957) [BG(1)]   parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi [fs read 1ms] (8ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/_typeshed/__init__.pyi (1ms)
(21957) [BG(1)]   parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/abc.pyi [fs read 0ms] (0ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/abc.pyi (1ms)
(21957) [BG(1)]   parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/dataclasses.pyi [fs read 1ms] (3ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/dataclasses.pyi (1ms)
(21957) [BG(1)]   parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/collections/abc.pyi [fs read 1ms] (1ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/collections/abc.pyi ...
(21957) [BG(1)]     parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/_collections_abc.pyi [fs read 0ms] (0ms)
(21957) [BG(1)]     binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/_collections_abc.pyi (0ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/collections/abc.pyi (1ms)
(21957) [BG(1)]   parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/decimal.pyi [fs read 0ms] (1ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/decimal.pyi ...
(21957) [BG(1)]     parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/_decimal.pyi [fs read 0ms] (2ms)
(21957) [BG(1)]     binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/_decimal.pyi (1ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/decimal.pyi (3ms)
(21957) [BG(1)]   parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/enum.pyi [fs read 0ms] (1ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/enum.pyi (0ms)
(21957) [BG(1)]   parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/functools.pyi [fs read 0ms] (2ms)
(21957) [BG(1)]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/functools.pyi (0ms)
(21957) [BG(1)] getSemanticTokens full at /Users/yuvalyellin/source/temp/vscode-test/test.py (141ms)
(21957) [FG] parsing: /Users/yuvalyellin/source/temp/vscode-test/test.py (12ms)
(21957) [FG] parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 1ms] (39ms)
(21957) [FG] binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/builtins.pyi (17ms)
(21957) [FG] binding: /Users/yuvalyellin/source/temp/vscode-test/test.py (0ms)
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
[Info  - 8:04:52 PM] (21957) Indexer background runner(2) root directory: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist (index)
[Info  - 8:04:52 PM] (21957) Indexing(2) started
(21957) Background analysis message: analyze
(21957) [IDX(2)] scan packages /Users/yuvalyellin/source/temp/vscode-test ...
(21957) [IDX(2)]   read stdlib indices (33ms)
(21957) [BG(1)] analyzing: /Users/yuvalyellin/source/temp/vscode-test/test.py ...
(21957) [BG(1)]   checking: /Users/yuvalyellin/source/temp/vscode-test/test.py (10ms)
(21957) [BG(1)] analyzing: /Users/yuvalyellin/source/temp/vscode-test/test.py (10ms)
(21957) Background analysis message: resumeAnalysis
(21957) [BG(1)] indexing: /Users/yuvalyellin/source/temp/vscode-test/test.py [found 4] (0ms)
(21957) Indexing Done: /Users/yuvalyellin/source/temp/vscode-test/test.py
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
(21957) [IDX(2)] scan packages /Users/yuvalyellin/source/temp/vscode-test (187ms)
[Info  - 8:04:52 PM] (21957) scanned(2) 29 files over 1 exec env
(21957) [IDX(2)] index packages /Users/yuvalyellin/source/temp/vscode-test ...
(21957) [IDX(2)]   index execution environment /Users/yuvalyellin/source/temp/vscode-test ...
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/jmespath/jmespath/__init__.pyi [fs read 0ms] (39ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/builtins.pyi [fs read 2ms] (45ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/builtins.pyi (7ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/jmespath/jmespath/__init__.pyi (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/jmespath/jmespath/__init__.pyi ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/jmespath/__init__.pyi [fs read 2ms] (6ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/jmespath/__init__.pyi (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/jmespath/visitor.pyi [fs read 1ms] (1ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/jmespath/visitor.pyi (1ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/jmespath/jmespath/__init__.pyi [found 3] (8ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/openpyxl/openpyxl/__init__.pyi [fs read 0ms] (5ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/openpyxl/openpyxl/__init__.pyi (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/openpyxl/openpyxl/__init__.pyi ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/openpyxl/openpyxl/compat/numbers.pyi [fs read 1ms] (1ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/openpyxl/openpyxl/compat/numbers.pyi (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/openpyxl/reader/excel.pyi [fs read 1ms] (3ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/openpyxl/reader/excel.pyi (1ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/openpyxl/workbook/__init__.pyi [fs read 0ms] (0ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/openpyxl/workbook/__init__.pyi (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/openpyxl/workbook/workbook.pyi [fs read 1ms] (6ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/openpyxl/workbook/workbook.pyi (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/openpyxl/xml/__init__.pyi [fs read 0ms] (1ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/openpyxl/xml/__init__.pyi (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/openpyxl/openpyxl/_constants.pyi [fs read 0ms] (0ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/openpyxl/openpyxl/_constants.pyi (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/openpyxl/openpyxl/__init__.pyi [found 9] (13ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/pkg_resources/__init__.pyi [fs read 0ms] (3ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/pkg_resources/__init__.pyi (2ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/pkg_resources/__init__.pyi [found 79] (0ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/__init__.pyi [fs read 0ms] (3ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/__init__.pyi (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/__init__.pyi ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/_deprecation_warning.pyi [fs read 0ms] (0ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/_deprecation_warning.pyi (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/depends.pyi [fs read 1ms] (1ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/depends.pyi (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/dist.pyi [fs read 0ms] (3ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/dist.pyi (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/extension.pyi [fs read 1ms] (1ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/extension.pyi (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stubs/setuptools/setuptools/__init__.pyi [found 12] (5ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django/__init__.pyi [fs read 0ms] (1ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django/__init__.pyi (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django/__init__.pyi ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django/utils/version.pyi [fs read 0ms] (0ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django/utils/version.pyi (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django/__init__.pyi [found 4] (1ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django/shortcuts.pyi [fs read 0ms] (4ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django/shortcuts.pyi (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django/shortcuts.pyi ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django-stubs/http/response.pyi [fs read 0ms] (7ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django-stubs/http/response.pyi (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs/django/shortcuts.pyi [found 10] (8ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/xml/__init__.py [fs read 0ms] (0ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/xml/__init__.py (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/xml/__init__.py [found 0] (1ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/astroid/__init__.py [fs read 0ms] (9ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/astroid/__init__.py (2ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/astroid/__init__.py [found 0] (0ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/__init__.py [fs read 0ms] (2ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/__init__.py (1ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/__init__.py ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/_version.py [fs read 0ms] (0ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/_version.py (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/api.py [fs read 0ms] (9ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/api.py (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/place.py [fs read 1ms] (3ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/place.py (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/settings.py [fs read 1ms] (12ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/settings.py (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/isort/__init__.py [found 16] (25ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/lazy_object_proxy/__init__.py [fs read 0ms] (5ms)
[Info  - 8:04:52 PM] (21957) Could not import 'copy_reg' in file '/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/lazy_object_proxy/__init__.py'
[Info  - 8:04:52 PM] (21957)   Looking in stubPath '/Users/yuvalyellin/source/temp/vscode-test/typings'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve stub package using root path '/Users/yuvalyellin/source/temp/vscode-test/typings'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve using root path '/Users/yuvalyellin/source/temp/vscode-test/typings'
[Info  - 8:04:52 PM] (21957)   Looking in root directory of execution environment '/Users/yuvalyellin/source/temp/vscode-test'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve stub package using root path '/Users/yuvalyellin/source/temp/vscode-test'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve using root path '/Users/yuvalyellin/source/temp/vscode-test'
[Info  - 8:04:52 PM] (21957)   Looking in python search path '/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve stub package using root path '/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve using root path '/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9'
[Info  - 8:04:52 PM] (21957)   Looking in python search path '/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/lib-dynload'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve stub package using root path '/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/lib-dynload'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve using root path '/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/lib-dynload'
[Info  - 8:04:52 PM] (21957)   Looking in python search path '/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve stub package using root path '/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve using root path '/Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages'
[Info  - 8:04:52 PM] (21957)   Looking in bundled stubs path '/Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve stub package using root path '/Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs'
[Info  - 8:04:52 PM] (21957)   Attempting to resolve using root path '/Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/bundled/stubs'
[Info  - 8:04:52 PM] (21957)   Looking for typeshed stdlib path
[Info  - 8:04:52 PM] (21957)   Looking for typeshed stdlib path
[Info  - 8:04:52 PM] (21957)   Attempting to resolve using root path '/Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib'
[Info  - 8:04:52 PM] (21957)   Typeshed path not found
[Info  - 8:04:52 PM] (21957)   Looking for typeshed third-party path
[Info  - 8:04:52 PM] (21957)   Looking for typeshed stubs path
[Info  - 8:04:52 PM] (21957)   Typeshed path not found
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/lazy_object_proxy/__init__.py (1ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/lazy_object_proxy/__init__.py [found 0] (0ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pip/__init__.py [fs read 0ms] (0ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pip/__init__.py (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pip/__init__.py [found 2] (1ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/platformdirs/__init__.py [fs read 0ms] (4ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/platformdirs/__init__.py (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/platformdirs/__init__.py ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/platformdirs/api.py [fs read 0ms] (1ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/platformdirs/api.py (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/platformdirs/version.py [fs read 0ms] (1ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/platformdirs/version.py (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/platformdirs/__init__.py [found 25] (2ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pylint/__init__.py [fs read 0ms] (1ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pylint/__init__.py (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pylint/__init__.py ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pylint/__pkginfo__.py [fs read 0ms] (0ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pylint/__pkginfo__.py (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pylint/__init__.py [found 7] (0ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pyright/__init__.py [fs read 0ms] (3ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pyright/__init__.py ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pyright/cli.py [fs read 0ms] (0ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pyright/cli.py (1ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pyright/__init__.py (2ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pyright/__init__.py ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pyright/_version.py [fs read 0ms] (0ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pyright/_version.py (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/pyright/__init__.py [found 8] (0ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomli/__init__.py [fs read 0ms] (0ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomli/__init__.py (1ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomli/__init__.py ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomli/_parser.py [fs read 0ms] (3ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomli/_parser.py (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomli/__init__.py [found 5] (3ms)
(21957) [IDX(2)]     parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomlkit/__init__.py [fs read 0ms] (0ms)
(21957) [IDX(2)]     binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomlkit/__init__.py (0ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomlkit/__init__.py ...
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomlkit/api.py [fs read 0ms] (4ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomlkit/api.py (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomlkit/toml_document.py [fs read 0ms] (0ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomlkit/toml_document.py (0ms)
(21957) [IDX(2)]       parsing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomlkit/items.py [fs read 1ms] (13ms)
(21957) [IDX(2)]       binding: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomlkit/items.py (1ms)
(21957) [IDX(2)]     indexing: /Users/yuvalyellin/.pyenv/versions/3.9.7/lib/python3.9/site-packages/tomlkit/__init__.py [found 27] (19ms)
(21957) [IDX(2)]   index execution environment /Users/yuvalyellin/source/temp/vscode-test [found 207 in 16 files] (239ms)
(21957) [IDX(2)] index packages /Users/yuvalyellin/source/temp/vscode-test [found 207 in 1 exec envs] (240ms)
[Info  - 8:04:52 PM] (21957) indexed(2) 16 files over 1 exec env
[Info  - 8:04:52 PM] (21957) Indexing finished(2).
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
(21957) IntelliCode model /Users/yuvalyellin/.vscode/extensions/visualstudioexptteam.vscodeintellicode-1.2.29/dist/bundledModels/python_intellisense-members-lstm-pylance
(21957) [FG] parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/typing.pyi [fs read 1ms] (13ms)
(21957) [FG] binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/typing.pyi (4ms)
(21957) [FG] parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/typing_extensions.pyi [fs read 1ms] (2ms)
(21957) [FG] binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/typing_extensions.pyi (2ms)
(21957) [FG] parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/dataclasses.pyi [fs read 0ms] (2ms)
(21957) [FG] binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/dataclasses.pyi (1ms)
(21957) [FG] parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/collections/abc.pyi [fs read 0ms] (0ms)
(21957) [FG] binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/collections/abc.pyi ...
(21957) [FG]   parsing: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/_collections_abc.pyi [fs read 0ms] (1ms)
(21957) [FG]   binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/_collections_abc.pyi (0ms)
(21957) [FG] binding: /Users/yuvalyellin/.vscode/extensions/ms-python.vscode-pylance-2022.11.20/dist/typeshed-fallback/stdlib/collections/abc.pyi (1ms)
(21957) Loading ONNX runtime...
(21957) Loaded ONNX runtime. Creating IntelliCode session...
(21957) Created IntelliCode session.
(21957) Initialize deeplearning succeeded
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange
(21957) Background analysis message: getDiagnosticsForRange

Go to Type Def works for PaymentMethodInfo | int but not PaymentMethodInfo | None.

Thanks. The highlight was too subtle for me to notice I guess. I was expecting that with a union of types we would display the options as a list as we do with PaymentMethodInfo | int. But I guess there is not definition of None anywhere?

That's correct. There's no definition of None in builtins.pyi or typing.pyi. It's hard-coded by all Python type checkers. A new NoneType was added to types.pyi in Python 3.10 and newer. I suppose we could take you to that location if you ask for the Type Definition of None, but I think that would be confusing to most pylance users.

When adding the lines
x = CustomerSource("", "") x.credit_card_info
clicking Go To Type Definition on the declaration leads to the usage (x.creadit_card_info) which is very strange .

clicking Go To Type Definition on the declaration leads to the usage (x.creadit_card_info) which is very strange .

I'm not able to repro that behavior using Go to Type Definition.  I believe Go to Definition on the definition of a symbol gives Find All References behavior. TypeScript also behaves this way.

I'm able to repro it by selecting "Go To Type Definition" from the declaration (i.e. where the field is declared within CustomerSource). It takes me to just after the dot in x.credit_card_info. I can't (yet) explain why. I've stepped through the code in pyright, and it's returning the location of the declaration, so I'm not sure why VS Code is taking me to a different position.

Ah, ok, I interpreted "on the declaration" as "on the declaration of x".
I think Go to Type Definition on the declaration of credit_card_info may also be doing Find All References. Try it with an extra usage of credit_card_info:
x = CustomerSource("", "")
x.credit_card_info
x.credit_card_info

@debonte, yes that's correct. VS Code appears to be sending pylance two requests — an onTypeDefinition callback followed by an onReferences callback. Not sure why it's sending the latter. I'm guessing that if the first call returns a range that overlaps with the position of the request, it assumes that it should show references instead of the type definitions.


added set models for ios and android

Can one of the admins verify this patch?

@AppInventorWorkerBee ok to test

The iOS side checks out.


Company completion with Clojure - arrow keys are closing the selection list

What did you expect to happen?
Whenever I use omnicomplete, I can use the arrow keys to select the appropriate item in the list and select it with Enter
What actually happened?
omnicomplete for Clojure files (with Cider connected), the arrow keys causes the caret to move up/down a line and just close the selection list
Steps to reproduce:

Use the latest doom
Open a clojure project
Cider jack-in (localleader ')
omnicomplete anything via ctrl-x + ctrl-o
Try to select an item via the up/down arrow keys

System information:
Attached is the sys info for the version that works doesn't have this bug - not the latest doom!

WARNING (:tools flycheck) module was moved to (:checkers syntax)
((emacs
  (version . "26.1")
  (features . "NOTIFY ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS")
  (build . "May 31, 2018")
  (buildopts "--with-ns '--enable-locallisppath=/Library/Application Support/Emacs/${version}/site-lisp:/Library/Application Support/Emacs/site-lisp' --with-modules")
  (windowsys . batch)
  (daemonp . server-running))
 (doom
  (version . "2.0.9")
  (build . "HEAD 21db1b7c9 2020-02-13 14:45:08 -0500")
  (dir . "~/.dotfiles/.doom.d/"))
 (system
  (type . darwin)
  (config . "x86_64-apple-darwin14.5.0")
  (shell . "/bin/zsh")
  (uname . "Darwin 19.2.0 Darwin Kernel Version 19.2.0: Sat Nov  9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 x86_64")
  (path "~/bin" "/usr/local/sbin" "/usr/local/bin" "/usr/sbin" "/usr/bin" "/sbin" "/bin" "/usr/games" "/usr/local/games" "/usr/local/sbin" "/usr/local/bin" "/usr/sbin" "/usr/bin" "/sbin" "/bin" "~/bin" "~/android-sdk-linux/tools" "~/android-sdk-linux/platform-tools" "~/.local/bin" "~/p4v/bin/" "~/.local/bin" "~/.cargo/bin" "/usr/local/share/dotnet" "/usr/local/opt/go/libexec/bin" "~/.config/nvim/plugged/vim-iced/bin" "/Applications/Emacs.app/Contents/MacOS/bin-x86_64-10_10" "/Applications/Emacs.app/Contents/MacOS/libexec-x86_64-10_10" "/Applications/Emacs.app/Contents/MacOS/libexec" "/Applications/Emacs.app/Contents/MacOS/bin"))
 (config
  (envfile . envvar-file)
  (elc-files . 0)
  (modules :completion company (ivy +fuzzy) :ui doom doom-dashboard doom-quit hl-todo modeline nav-flash ophints (popup +all +defaults) treemacs vi-tilde-fringe window-select :editor (evil +everywhere) file-templates fold multiple-cursors rotate-text snippets :emacs dired electric ibuffer vc :tools (eval +overlay) :checkers syntax :tools (lookup +docsets) magit :lang clojure data elixir emacs-lisp (java +meghanada) markdown (org +dragndrop +ipython +pandoc +present) sh :config (default +bindings +smartparens))
  (packages . "<(void-function sp-point-in-string)>")
  (elpa "n/a")
  (unpin "n/a")))

A bit of digging shows that it's probably the same as issue #1335
I tried the suggested fixes there, but none of them work. Any help/simple hacks will be greatly appreciated - just want to traverse my completion list via the arrow keys and select with Enter.
Thanks

Managed to solve this via this link:
https://github.com/company-mode/company-quickhelp/issues/17
Essentially, my config.el now has this:
(after! cider
  (add-hook 'company-completion-started-hook 'ans/set-company-maps)
  (add-hook 'company-completion-finished-hook 'ans/unset-company-maps)
  (add-hook 'company-completion-cancelled-hook 'ans/unset-company-maps)

  (defun ans/unset-company-maps (&rest unused)
    "Set default mappings (outside of company).
Arguments (UNUSED) are ignored."
    (general-def
      :states 'insert
      :keymaps 'override
      "<up>" nil
      "<down>" nil))

  (defun ans/set-company-maps (&rest unused)
    "Set maps for when you're inside company completion.
Arguments (UNUSED) are ignored."
    (general-def
      :states 'insert
      :keymaps 'override
      "<down>" 'company-select-next
      "<up>" 'company-select-previous)))

Just want to confirm that this was an issue, and the pasted workaround solved it for me - many thanks @nirrub
The strange thing was that it was only broken in clojure/cider mode - the completion bindings in elisp worked fine.


Cannot run locally anymore

Hi Sleepbus team,
I'm having issues following the local instructions for a local build. I have reinstalled docker and still get this issue after a fresh checkout of the project. This is what happens when I visit the homepage localhost:8080 once its running in docker.
Warning: include_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/html/index.php on line 58

Warning: include_once(./application/vendor/autoload.php): failed to open stream: No such file or directory in /var/www/html/index.php on line 58

Warning: include_once(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/html/index.php on line 58

Warning: include_once(): Failed opening './application/vendor/autoload.php' for inclusion (include_path='.:/usr/local/lib/php') in /var/www/html/index.php on line 58

Warning: main(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /var/www/html/index.php on line 60

Fatal error: Class 'Dotenv\Dotenv' not found in /var/www/html/index.php on line 60

@bakersemail - sorry, may have been a few changes in there, mine runs fine with the destroy_rebuild script, so I think it may be due to adding Composer, would explain the missing vendor folder and dotenv lib. Let me check what the command should be...

With composer installed, will need to
php composer.phar install
passing in argument for target dir, which is
/src/application

php composer.phar install composer install -d /src/application should do it.
I've just been a bit busy travelling and trying to get some quick fixes in, so have been a bit sloppy with the local dev env.

php composer.phar install composer install -d /src/application should do it.
I've just been a bit busy travelling and trying to get some quick fixes in, so have been a bit sloppy with the local dev env.

Can this be included into the destroy_rebuild script?

@bakersemail, haven't forgotten about this, just on some really crappy internet for next 2 days, so can't easily rebuild without cache. Aiming to get this sorted over next week.

Cheers. Will be glad to see it fixed so I can help out where I can again.

@bakersemail - have just pushed a fix to master that sorted this out on a new env for me, let me know if any issues

@bakersemail - just added another commit which should retain the vendor files after the watch job syncs app folder again. missed that!


Exception if there are spaces in the data directory path

When using setDataDir() if the path contains spaces then newEmbeddedDB throws an exception. Looks like command line arguments are not being escaped. This could be an attack vector for a malicious user who has control over the database file name.
Exception in thread "main" ch.vorburger.exec.ManagedProcessException: An error occurred while installing the database
	at ch.vorburger.mariadb4j.DB.install(DB.java:117)
	at ch.vorburger.mariadb4j.DB.newEmbeddedDB(DB.java:68)
	...
Caused by: ch.vorburger.exec.ManagedProcessException: Program [/var/folders/m7/vwmfxlgd5655j5ysw0qbtyg00000gn/T/MariaDB4j/base/bin/mysql_install_db, "--datadir=/Users/john/my database", --basedir=/private/var/folders/m7/vwmfxlgd5655j5ysw0qbtyg00000gn/T/MariaDB4j/base, --no-defaults, --force, --skip-name-resolve] (in working directory /var/folders/m7/vwmfxlgd5655j5ysw0qbtyg00000gn/T/MariaDB4j/base) failed, exitValue=1, last 100 lines of console:
Installing MariaDB/MySQL system tables in './data' ...
/private/var/folders/m7/vwmfxlgd5655j5ysw0qbtyg00000gn/T/MariaDB4j/base/bin/mysqld: Too many arguments (first extra is '"--datadir=/Users/john/my').
150831 16:41:53 [ERROR] Aborting

Hello @jahewson, thanks for your interest in MariaDB4j! That's a great point, and should be fixed ASAP.. I don't suppose you have the time and interest to join this project via a pull request that addresses this?

https://issues.apache.org/jira/browse/EXEC-93

@jahewson This particular problem re. space in setDataDir() is now fixed. Because of your comment “This could be an attack vector for a malicious user who has control over the database file name.” I’ve gone beyond a trivial quick fix, and done some work for a lower level and more generic - all arguments should now be escaped for spaces correctly. (If you find anything else, about this or other feedback on MariaDB4j, please do open new issues. Also any PRs always welcome.)

:+1:


Add UserTargets class and use it for User#targets

User#targets isn't a straight Set but a derived class from it.
I also made a PR for the system so it will be in UserPF2e#targets as well.

https://github.com/foundryvtt/pf2e/pull/17444#event-15408757814
system PR was accepted


Notifications - please add date/time to all notifications (Feature request)

As per title - please add date/time to all notifications.
Because notifications don't always load up properly (e.g. node syncing) it is a pain to see which notifications are new, or when they were posted.
Surely it must be possible to get the date & time of all notifications to display on the notification panel.
Please consider - its my no 1 issue at the moment :)
Thanks guys.
p.s. Please don't take any of my posts as negatives, i'm just trying to help with constructive criticism and enhance the platform.

Here's a possible solution I mocked up.

This is not a straightforward solution and requires changes to the blockchain as far as I can see to implement.
The only transaction that stores a timestap (postContent.TimestampNanos in this case) is submit post.
The others dont.
If you have an idea of how to get around this, please share.

@tijno - I've not had a chance to dig into the firehose, but if we know the datetime of the surrounding "submit post"s, can we not workout the (at least approximate) datetime of the transactions between based on index?
I'd have to consider it more and look closer myself, but would think that there are now enough submit posts to be able to get reasonably accurate with the times of other transaction types between (?).
Ideally, would like to see timestamp (or probably better instant) added to chain for every transaction type so that its easy to determine.

Anything is possible - but it may just be too intensive to do. If it was straightforward the devs would have done it - so they must have made the decision at that time to not add the info with a workaround.
Also - they could store timestamp with every transaction. But a timestamp takes up 9 bytes i guess. Theres 26m transactions already. That 250Mb of data that has to be stored in the block chain of everything that has happened in the past.

indeed.
instant would probably be best option, think that's 8bytes - but yes would increase overall size.
Could possibly log a regular transaction with a fixed instant, then store a smaller value for transactions after that to then allow time to be calculated without hugely increasing overall size (although its a given that it would increase).
don't know much about crypto, so just throwing my thoughts out there before i actually look at it!

Yeah same as you - this is where my knowledge ends of what is possible or not. Additional additional transactions feels wasteful, and to lookup two transactions may be too intensive.
Maybe the block time is available for each transaction?
If so - that could be used here to prepare the notification data.
https://github.com/bitclout/backend/blob/90cb5e88879160fee7b2ff0c0259c8273ec3deda/routes/user.go#L1899


Add build tool config

Allow easier contribution by rearranging the source into a separate directory from the build and provide a means for authors to build locally. This will open up the ability to more easily test, as well.

hi, i made the pr #43 that can address this issue.

Resolved by pull request #43.


Use logo as icon in linux

I liked the logo + name. Did you had an issue with it ?

On my system (Ubuntu 20.04) the text was pretty small and hard to read and thus it made the icon smaller for no apparent benefit.


check subscriber should test for offline

The check:
./check_activemq.py -u admin -p admin subscriber --clientId Sub3 --topic preise
ACTIVEMQSUBSCRIBER OK - Client Sub3 is subscriber of Topic preise
tests if Sub is a subscriber. But it should check is Sub is currently an active subsciber.
If Sub3 is not an active subscriber => WARN
If Sub3 is not an subscriber at all => CRITICAL

Implemented with 3c7418e.
For this to work, the script needed some restructuring, but this feature commit also includes better debug output and error handling.


fix: hpmn registration after revocation caused mining failure

Issue being fixed or feature implemented
We reset operator info on revocation; but then on replacement via new register we try to "RemoveMN", which tries to remove platformNodeID but that's already been cleared
What was done?
Only try to delete platformNodeID if it's non-null
How Has This Been Tested?
Mined with it on testnet; mining works
Breaking Changes
This will fork off other testnet nodes, as this fixes the logic
Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation

For repository code-owners and collaborators only

[x] I have assigned this pull request to a milestone

which tries to remove platformNodeID but that's already been cleared

So basically it tries to remove a null platformNodeID which was never added in the first place (because UpdateUniqueProperty won't let you). Makes sense I guess cause a null platformNodeID should never be considered unique, that's clearly a bug. We should never try to add it via AddUniqueProperty in AddMN either... pls fix it with a similar patch while we are at it.

In Testnet, a HPMN was revoked (hence setting the platformNodeID) and then a new HPMN registration with the already used (revoked) collateral.

@UdjinM6 Added the check in AddMN as well (although it should never happen as explained above)


Modify button styling on eligibility questionnaire welcome page

In light of user feedback, we'd like to update the styling of the button on the Welcome page on the eligibility questionnnaire. The primary changes are:

Change text from 'Next' to 'Start'
Add a right arrow.
Change button styling to make it more rounded.

Design is viewable in Figma (03.1).

The button styling has been updated, but the content hasn't been updated as it still reads 'Next'. I think this is good enough for now. I'll leave it open but will push it out of the Q4 milestones.


Non-Markovian Environments

What's the recommended way to rewind a simulation environment back to its full state at some point? For example, the following code (in python, for a dmc2gym environment):
a = np.copy(env.physics.get_state())
b = env.step()[0]
env.physics.set_state(a)
c = env.step()[0]

would produce the same b and c for the cart-pole, but not for the pendulum. In other words, the pendulum environment is Non-Markovian. Do I need to save some other "hidden" states of the pendulum?

Could you please also save and set env.physics.qacc_warmstart?
This is a usually-unimportant "hidden state", the previous accelerations which are used to warmstart the solver. It only matters for exact bitwise equality or after integrating for long periods.


weird hanging

node.js: v4.1.1
lzma-native: 0.3.9
i try:
var fs = require('fs');
var lzma = require('lzma-native');
var r = fs.createReadStream('test.jpg');
var compressor = lzma.createCompressor();
var decompressor = lzma.createDecompressor();
var w = fs.createWriteStream('test2.jpg');
r.pipe(compressor).pipe(decompressor).pipe(w);
test2.jpg is generated correctly, but execution wont stop.

Okay, I can confirm this – will probably fix it within the next hours :)

I’ll just wait for the tests to pass and then I’ll publish this as 0.3.10

Done, fix published as 0.3.10. I don’t think this should be considered a huge bug anyway, since the hang would have stopped with the next garbage collection (which would happen somewhat regularly in larger applications).
I hope this module will be useful to you – Let me know if there happen to be any more problems!

yes, it works now.
thank you for your effort :)


Adding VMware vCenter infra provider

Hi,
I have added and successfully validated VMware vCenter provider on my manageIQ(Version: capablanca-2.20160531195249_d083ab5), but getting the following error while refreshing the relationships and power states

Last Refresh
Error - 7 Minutes Ago
undefined method `[]' for nil:NilClass
vCenter login credentials are having limited access and it doesnt have privilege to create a VM, but can list all VMs associated with it through vcenter client. So I guess atleast it should discover the VMs associated with it right?
Error in evm.log
> > [----] E, [2016-05-30T19:23:38.315609 #3132:633990] ERROR -- : [NoMethodError]: undefined method `[]=' for nil:NilClass  Method:[rescue in block in refresh]
> > [----] E, [2016-05-30T19:23:38.315707 #3132:633990] ERROR -- : (druby://<IP_ADDRESS>:47828) /var/www/miq/vmdb/gems/pending/VMwareWebService/MiqVimInventory.rb:482:in `objFixUp'
> > (druby://<IP_ADDRESS>:47828) /var/www/miq/vmdb/gems/pending/VMwareWebService/MiqVimInventory.rb:442:in `addObjHash'
> > (druby://<IP_ADDRESS>:47828) /var/www/miq/vmdb/gems/pending/VMwareWebService/MiqVimInventory.rb:962:in `block in resourcePools_locked'
> > (druby://<IP_ADDRESS>:47828) /var/www/miq/vmdb/gems/pending/VMwareWebService/MiqVimInventory.rb:961:in `each'
> > (druby://<IP_ADDRESS>:47828) /var/www/miq/vmdb/gems/pending/VMwareWebService/MiqVimInventory.rb:961:in `resourcePools_locked'
> > (druby://<IP_ADDRESS>:47828) /var/www/miq/vmdb/gems/pending/VMwareWebService/MiqVimInventory.rb:981:in `resourcePoolsByMor_locked'
> > (druby://<IP_ADDRESS>:47828) /var/www/miq/vmdb/gems/pending/VMwareWebService/MiqVimInventory.rb:1011:in `block in resourcePoolsByMor'
> > /var/www/miq/vmdb/bin/rails:4:in `require'
> > /var/www/miq/vmdb/bin/rails:4:in `<main>'
> > [----] E, [2016-05-30T19:23:38.315793 #3132:633990] ERROR -- : MIQ(ManageIQ::Providers::Vmware::InfraManager::Refresher#refresh) EMS: [vCenter-Onprem], id: [23] Unable
>
> > to perform refresh for the following targets:
> > [----] E, [2016-05-30T19:23:38.315862 #3132:633990] ERROR -- : MIQ(ManageIQ::Providers::Vmware::InfraManager::Refresher#refresh) EMS: [vCenter-Onprem], id: [23]
>
> > ManageIQ::Providers::Vmware::InfraManager: [vCenter-Onprem], id: [23]
> > [----] I, [2016-05-30T19:23:38.402441 #3132:633990]  INFO -- : MIQ(ManageIQ::Providers::Vmware::InfraManager::Refresher#refresh) Refreshing all targets...Completed in
>
> > 1.102555489s
>

Thanks @adlinix, originally from http://talk.manageiq.org/t/adding-vmware-vcenter-infra-provider/1400

@adlinix can you test with a user that has full privileges to see if the limited access is causing the issue?

@agrare, will check, thanks

Going to close this assuming it was a permissions issue.  If this is still causing you problems please re-open.


feat: update prometheus config.

🅰 Please add the issue ID after "Fixes #"
feat: update prometheus config.

I have read the CLA Document and I hereby sign the CLA


Improvements: see the specs/tests in "File structure"

Hi,
Using the menu "Navigate -> File structure", it would be nice if specs / tests could appear here.
Comparing to JUnit where each test is a method (and easy to find using the "File Structure"), it would be easier to have this functionality to search for tests.

I think this is just part of intellij looking for methods in a class. And since kotest is not method based, it can't appear here.
There doesn't appear to be a way to hook into that functionality.

This is in the next build.


Use Pipeline._repr_html_ after dropping python3.9

Once we drop python3.9, we can use Pipeline._repr_html_
Currently it's broken since it is not showing the real name of the NewType in python3.9

You can drop 3.9 now, this has been decided a couple weeks ago.


Test pr to deploy changes from master to demo env

JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

No longer needed


Instances not auto running on MacOs

When trying to get multirun working on Mac, the additional instances popup to the Project Selection screen of Godot. I've tried resolving this myself but have been unable to get it working. Seems to work just fine on Windows and Linux as well.
I'm running the MacOS 12.3 with M1

Adding a fix here! https://github.com/perfoon/Multirun/pull/5

Nice! I was planning on making the suggestion 👍


APP_URL is changed after update docker | APP_URL no longer persistant after reboot!

Describe the bug
After restarting docker today I noticed I could no longer access my wiki, I checked the config for bookstack on two instances of the wiki I am running and in both the APP_URL had changed to my public IP. As I am using bookstack behind traefik, I prefer to keep it the way it was... but that did not let me do this as it was persistant to reset it to the public IP after the restart of the container again! My wiki is now not working since the latest update!
EDIT:
When I set the APP_URL manually correctly (as traefik serves it) it works again, yet after a docker-restart of the container, bookstack will now replace the APP_URL by my public IP and that will not work obviously, can BOOKSTACK, please leave my APP_URL alone?
Steps To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings):
PHP Version:
Hosting Method (Nginx/Apache/Docker):

Additional context
Add any other context about the problem here.

Hi @SupaYoshi,
Am I right in thinking that you're using the linuxserver.io image? If so, you'll need to open an issue on their repo since we don't manage and production docker images in the core project.
https://github.com/linuxserver/docker-bookstack

@SupaYoshi Do you added the APP_URL environment variable in your docker run or docker-compose? Mine got reset, because it wasn't set there like shown here: https://hub.docker.com/r/linuxserver/bookstack
Unfortunalety my instance of bookstack is still not reachable.

Cleared cache of Bookstack and it's working again.

Having a similar issue. After the latest update, the app is no longer accessible. I noticed the change for the required APP_URL so I added that to my docker-compose, however it is still inaccessible. Have tried clearing cache as well as deleting and recreating the container to no avail.

Nevermind! Looks like it just took awhile to notice the changes. It's working again.

Will therefore close this since the original issue creator has not responded and it looks like this was generally due to a change in a specific hosting setup.


there is a bug about mixed chart

Bug description
use mixed chat ,when the X-axis is number ,The histogram goes beyond the end of the x-axis
like

I can solve it with string X-aix，but I still like that it would be a little better to use numbers as the x-axis
How to reproduce the bug
1
Screenshots/recordings

Superset version
4.0.0
Python version
3.9
Node version
16
Browser
Chrome
Additional context
1
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

I believe this is a duplicate of #26254, see that conversation for more context.  Let me know if you disagree.


nacl-did dependency missing

After upgrading to the latest version, I'm getting this error:
error: bundling failed: Error: Unable to resolve module `nacl-did`
 from `.../uport-mobile/node_modules/did-jwt/lib/NaclSigner.js`:
Module `nacl-did` does not exist in the Haste module map

It is being used explicitly:
https://github.com/uport-project/did-jwt/blob/develop/src/NaclSigner.js#L3
But it was removed from dependency list on purpose? :
https://github.com/uport-project/did-jwt/commit/37a57409de8a5f4175a26dead35b547cdd4617cd#diff-b9cfc7f2cdf78a7f4b91a753d10865a2R44

Seems quite redundant to import nacl-did for only this line of code: https://github.com/uport-project/nacl-did/blob/develop/src/register.ts#L86

Should be fixed by https://github.com/uport-project/did-jwt/pull/34
Available on npm now as v0.1.3-alpha.1

Nice @mi-xu 🙌

@mi-xu this issue is still present. Seems like you forgot to build before you did the release. It's usually good to add an autobuild script when you run npm publish 🙂

@oed Can you try the release version? https://www.npmjs.com/package/did-jwt/v/0.1.3

Sorry my bad! Should had double checked, thought I did update to 0.1.3, but was on 0.1.2.

@oed No worries! Closing this issue now that it seems to be working.


allow magellan to connect to sauce tunnel pool without launching new tunnel

connect to a sauce tunnel pool to use available tunnel directly, no need to launch new tunnel in this case.
@Maciek416 @geekdave

👍


data-vaul-no-drag on parent element not working with input fields

its about this issue https://github.com/emilkowalski/vaul/pull/267
this solution still not working with input field.if you place  data-vaul-no-drag on input element it work fine, but this not work when parent element has     data-vaul-no-drag attribute
I've reproduced it here
link

@Poylar pretty sure the fix wasnt part of the release 0.9.0, they should release soon together w/ other fixes

I have a similar issue. I am using MonacoEditor/react. When I drag to select the text inside it the drawer slides together. I inspected and noticed that all the lines inside the Monaco Editor are  tags. Even if I wrap arroud a  around the Monaco Editor it still sliding.
Shoudn`t it not drag the Vaul if a parent of it is with   "data-vaul-no-drag" ?

Shoudn`t it not drag the Vaul if a parent of it is with "data-vaul-no-drag" ?

There is a merged fix for this https://github.com/emilkowalski/vaul/pull/267
We are only waiting for a new release bump

Im sorry, now I see. I though #267  was on 0.9 already, My bad.
@maiconcarraro is there some release date in your mind? So I can keep checking for updates;

@lucarampi I'm not a maintainer, I mean "we" as part of the people that are waiting for the next release, I noticed Emil merged a few PRs days ago, hopefully it's going to be soon

Opened an issue to bump npm version: #319


expectError on array arguments mismatch

Following example:

const a = (a: [string, number]) => a[0];

expectError(a([1, 2]));

No overload matches this call.
  The last overload gave the following error.
    Type string is not assignable to type never.
      Type string is not assignable to type never.

Sorry, bad example, will fix it later

tsd gives error because test1(...) emits 2 errors for each array item.
Solution is to wrap with expectError() n times where n is errors count


Ability to compute checksums in parallel

can now compute table checksums using multiple threads

Implemented here https://github.com/Altinity/clickhouse-sink-connector/pull/577