KeyError in PyLS when opening projects

Description
What steps will reproduce the problem?

The error occurred immediately after Sypder startup
Traceback
  File "C:\Continuum\miniconda3\envs\vmx_cms_model_gxmxxx_01\lib\site-packages\pyls_jsonrpc\endpoint.py", line 113, in consume
    self._handle_request(message['id'], message['method'], message.get('params'))
  File "C:\Continuum\miniconda3\envs\vmx_cms_model_gxmxxx_01\lib\site-packages\pyls_jsonrpc\endpoint.py", line 182, in _handle_request
    handler_result = handler(params)
  File "C:\Continuum\miniconda3\envs\vmx_cms_model_gxmxxx_01\lib\site-packages\pyls_jsonrpc\dispatchers.py", line 23, in handler
    return method(**(params or {}))
  File "C:\Continuum\miniconda3\envs\vmx_cms_model_gxmxxx_01\lib\site-packages\pyls\python_ls.py", line 236, in m_text_document__did_close
    self.workspace.rm_document(textDocument['uri'])
  File "C:\Continuum\miniconda3\envs\vmx_cms_model_gxmxxx_01\lib\site-packages\pyls\workspace.py", line 74, in rm_document
    self._docs.pop(doc_uri)

Versions

Spyder version: 4.0.0b2
Python version: 3.6.4
Qt version: 5.9.6
PyQt5 version: 5.9.2
Operating System: Windows 10

Dependencies
pygments >=2.0     :  2.4.0 (OK)
qdarkstyle >=2.6.4 :  2.6.8 (OK)
sphinx >=0.6.6     :  2.0.1 (OK)
pyls >=0.19.0;<0.25:  0.24.0 (OK)
nbconvert >=4.0    :  5.5.0 (OK)
pandas >=0.13.1    :  0.24.2 (OK)
numpy >=1.7        :  1.16.4 (OK)
sympy >=0.7.3      :  None (NOK)
cython >=0.21      :  None (NOK)
qtconsole >=4.2.0  :  4.5.1 (OK)
IPython >=4.0      :  7.5.0 (OK)
matplotlib >=2.0.0 :  None (NOK)
pylint >=0.25      :  2.3.1 (OK)

Thanks for reporting. Is this something that appears every time you close Spyder and open it again?

No, it appears infrequently. It also appears when opening a new script in an already active Spyder session
From: Carlos Cordoba<EMAIL_ADDRESS>Sent: Thursday, June 6, 2019 10:54 AM
To: spyder-ide/spyder<EMAIL_ADDRESS>Cc: Ionut Barbu<EMAIL_ADDRESS>Manual<EMAIL_ADDRESS>Subject: [EXT]Re: [spyder-ide/spyder] Internal Python Language Server error (#9522)
Thanks for reporting. Is this something that appears every time you close Spyder and open it again?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_spyder-2Dide_spyder_issues_9522-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAK5DXRUUPZXYHTK27LIZZZTPZDGBJA5CNFSM4HU5NZP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXCF6OY-23issuecomment-2D499408699&d=DwMCaQ&c=yIH1_-b1hO27QV_BdDph9suDL0Jq0WcgndLmIuQXoms&r=UAQb9k8x1Hi0IrUihi2d_w8nQGGdNzemw38djy05P0g&m=Fj_tHkvxlUztkeX5DVotgKBdTX5pW4v7RSBrVeJwIek&s=iHGUEQjHeFiKg677DLd3sVdWDozSWM4kgbZX5yLQt5I&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AK5DXRWZLPPHZVGY52KWOGTPZDGBJANCNFSM4HU5NZPQ&d=DwMCaQ&c=yIH1_-b1hO27QV_BdDph9suDL0Jq0WcgndLmIuQXoms&r=UAQb9k8x1Hi0IrUihi2d_w8nQGGdNzemw38djy05P0g&m=Fj_tHkvxlUztkeX5DVotgKBdTX5pW4v7RSBrVeJwIek&s=tkiwUa6tEUM08NYf_zUdKwJDdZAVHy1HRp-7pwXhc28&e=.
+========================================================================+
This email is confidential and may be privileged. If you have received it
in error, please notify us immediately and then delete it.  Please do not
copy it, disclose its contents or use it for any purpose.
+========================================================================+

@andfoy, was this fixed in PR #9468?

I still get this, or a very similar, error on master post PR 9468. The error dialog shows
  File "/home/jitse/misc/miniconda/envs/std/lib/python3.6/site-packages/pyls_jsonrpc/endpoint.py", line 113, in consume
    self._handle_request(message['id'], message['method'], message.get('params'))
  File "/home/jitse/misc/miniconda/envs/std/lib/python3.6/site-packages/pyls_jsonrpc/endpoint.py", line 182, in _handle_request
    handler_result = handler(params)
  File "/home/jitse/misc/miniconda/envs/std/lib/python3.6/site-packages/pyls_jsonrpc/dispatchers.py", line 23, in handler
    return method(**(params or {}))
  File "/home/jitse/misc/miniconda/envs/std/lib/python3.6/site-packages/pyls/python_ls.py", line 236, in m_text_document__did_close
    self.workspace.rm_document(textDocument['uri'])
  File "/home/jitse/misc/miniconda/envs/std/lib/python3.6/site-packages/pyls/workspace.py", line 74, in rm_document
    self._docs.pop(doc_uri)
  File "/home/jitse/misc/miniconda/envs/std/lib/python3.6/site-packages/pyls_jsonrpc/endpoint.py", line 113, in consume
    self._handle_request(message['id'], message['method'], message.get('params'))
  File "/home/jitse/misc/miniconda/envs/std/lib/python3.6/site-packages/pyls_jsonrpc/endpoint.py", line 182, in _handle_request
    handler_result = handler(params)
  File "/home/jitse/misc/miniconda/envs/std/lib/python3.6/site-packages/pyls_jsonrpc/dispatchers.py", line 23, in handler
    return method(**(params or {}))
  File "/home/jitse/misc/miniconda/envs/std/lib/python3.6/site-packages/pyls/python_ls.py", line 236, in m_text_document__did_close
    self.workspace.rm_document(textDocument['uri'])
  File "/home/jitse/misc/miniconda/envs/std/lib/python3.6/site-packages/pyls/workspace.py", line 74, in rm_document
    self._docs.pop(doc_uri)

Unfortunately, the error message seems to have disappeared.
This error appeared when opening a new project. It is not triggered all the time, only about half the time when opening a project.
Versions:
Spyder 4.0.0.dev0 (Commit: 15868e54a) | Python 3.6.8 64-bit | Qt 5.9.6 | PyQt5 5.9.2 | Linux 4.19.0-5-amd64
$ conda list python-language-server
# packages in environment at /home/jitse/misc/miniconda/envs/std:
#
# Name                    Version                   Build  Channel
python-language-server    0.24.0                   py36_0    spyder-ide

pygments >=2.0     :  2.3.1 (OK)
qdarkstyle >=2.6.4 :  2.6.4 (OK)
sphinx >=0.6.6     :  1.8.5 (OK)
psutil >=0.3       :  5.6.1 (OK)
pyls >=0.19.0;<0.25:  0.24.0 (OK)
nbconvert >=4.0    :  5.4.1 (OK)
pandas >=0.13.1    :  0.24.2 (OK)
numpy >=1.7        :  1.16.2 (OK)
sympy >=0.7.3      :  1.3 (OK)
cython >=0.21      :  0.29.6 (OK)
qtconsole >=4.2.0  :  4.4.3 (OK)
IPython >=4.0      :  7.4.0 (OK)
matplotlib >=2.0.0 :  3.0.3 (OK)
pylint >=0.25      :  2.3.1 (OK)

@andfoy, please take a look at this one.

@IonutBarbu @jitseniesen Thanks for reporting this issue, is it possible to get a copy of the Spyder LSP client log?

@jitseniesen, you can do that by starting Spyder with
python bootstrap.py --debug

and then going to
~/.config/spyder-py3-dev/lsp_logs/client_python.log

Thanks for reporting this issue, is it possible to get a copy of the Spyder LSP client log?

I sent it to you by email.

@jitseniesen, could you test again with the latest master? I think this was fixed by PR #9482 (at least I can't generate the error anymore).

It seems to be fixed for me too.

I do not get an error anymore  after switching project, but the codestyle analysis stop working.

@jnsebgosselin, I can't reproduce that on Linux, but please open another issue for it (it's probably a Windows only problem).

could you test again with the latest master?

I can't reproduce the error anymore, so it seems to be fixed. Thanks, @andfoy!

Thanks for the confirmation @jitseniesen and @jnsebgosselin!

@jnsebgosselin, I can't reproduce that on Linux, but please open another issue for it (it's probably a Windows only problem).

Ok, what can I provide as information or logs to help with this? client_python.log and server_python.log?

Yeah, please create a gist for both of them and put its link in the description.


Crop only giving center of image

Hi I tried to use the patches inference with crop but it cropped the center and didnt provide the rest of the image. is there a way to do patch based inference and aggregate to get whole image?

yeah the new crop works but I would really prefer a tuple for shape

perfect, heres a side by side fgatir btw:


Subject: [MR] Fix: Update README with corrected image table and list of available blocks

Hi @tommyjepsen,
I've made some adjustments to the README file to ensure that the image table displays correctly and the list of available blocks is accurate. Here's a summary of the changes:

Corrected the formatting of the image table to display light and dark mode images side by side.
Updated the list of available blocks to accurately reflect the current offerings.

Please review the changes and let me know if everything looks good to you.
Thanks!

Super nice! @M-U-C-K-A
Can you update it to "Heroes" instead of "Heros"? Then it's good - thanks! 💪

it's done, sorry for the mistake 💪


Check loading state with dependencies

A handle should only be counted as loaded by this plugin when all it's dependencies are loaded.
count_loaded_handles should be using https://docs.rs/bevy_asset/latest/bevy_asset/struct.AssetServer.html#method.is_loaded_with_dependencies

@NiklasEi I briefly tested that out 1 line change locally, looks to be working 😌

The failure variable also needs to account for deps too otherwise if a dep fails to load the loading screen infinitely shows rather than transitioning to the error state.


python312Packages.django-debug-toolbar: 4.4.2 -> 4.4.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.django-debug-toolbar is: Configurable set of panels that display debug information about the current request/response
meta.homepage for python312Packages.django-debug-toolbar is: https://github.com/jazzband/django-debug-toolbar
meta.changelog for python312Packages.django-debug-toolbar is: https://django-debug-toolbar.readthedocs.io/en/latest/changes.html
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.4.6 with grep in /nix/store/bwnfb5q883jmkl23j81ah7midxqhwmbc-python3.12-django-debug-toolbar-4.4.6
found 4.4.6 in filename of file in /nix/store/bwnfb5q883jmkl23j81ah7midxqhwmbc-python3.12-django-debug-toolbar-4.4.6

Rebuild report (if merged into master) (click to expand)

13 total rebuild path(s)

13 package rebuild(s)

First fifty rebuilds by attrpath

netbox
netbox_3_6
netbox_3_7
peering-manager
python311Packages.django-cachalot
python311Packages.django-debug-toolbar
python311Packages.django-graphiql-debug-toolbar
python311Packages.netbox-reorder-rack
python312Packages.django-cachalot
python312Packages.django-debug-toolbar
python312Packages.django-graphiql-debug-toolbar
python312Packages.netbox-reorder-rack

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/bwnfb5q883jmkl23j81ah7midxqhwmbc-python3.12-django-debug-toolbar-4.4.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.django-debug-toolbar https://github.com/r-ryantm/nixpkgs/archive/7d0356ef2b50f84c723305c6dc1d064387ef0a58.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7d0356ef2b50f84c723305c6dc1d064387ef0a58#python312Packages.django-debug-toolbar

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/bwnfb5q883jmkl23j81ah7midxqhwmbc-python3.12-django-debug-toolbar-4.4.6
ls -la /nix/store/bwnfb5q883jmkl23j81ah7midxqhwmbc-python3.12-django-debug-toolbar-4.4.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

9 packages failed to build:

netbox (netbox_3_7)
python311Packages.django-graphiql-debug-toolbar
python311Packages.django-graphiql-debug-toolbar.dist
python311Packages.netbox-reorder-rack
python311Packages.netbox-reorder-rack.dist
python312Packages.django-graphiql-debug-toolbar
python312Packages.django-graphiql-debug-toolbar.dist
python312Packages.netbox-reorder-rack
python312Packages.netbox-reorder-rack.dist

9 packages built:

peering-manager
python311Packages.django-cachalot
python311Packages.django-cachalot.dist
python311Packages.django-debug-toolbar
python311Packages.django-debug-toolbar.dist
python312Packages.django-cachalot
python312Packages.django-cachalot.dist
python312Packages.django-debug-toolbar
python312Packages.django-debug-toolbar.dist

Maintainer pings
cc @yuuyins for testing.

Result of nixpkgs-review pr 328092 run on x86_64-linux 1

1 package marked as broken and skipped:

netbox_3_6

18 packages built:

netbox (netbox_3_7)
peering-manager
python311Packages.django-cachalot
python311Packages.django-cachalot.dist
python311Packages.django-debug-toolbar
python311Packages.django-debug-toolbar.dist
python311Packages.django-graphiql-debug-toolbar
python311Packages.django-graphiql-debug-toolbar.dist
python311Packages.netbox-reorder-rack
python311Packages.netbox-reorder-rack.dist
python312Packages.django-cachalot
python312Packages.django-cachalot.dist
python312Packages.django-debug-toolbar
python312Packages.django-debug-toolbar.dist
python312Packages.django-graphiql-debug-toolbar
python312Packages.django-graphiql-debug-toolbar.dist
python312Packages.netbox-reorder-rack
python312Packages.netbox-reorder-rack.dist


run run_classifier.py UnicodeDecodeError

Traceback (most recent call last):
File "run_classifier.py", line 24, in
File "/home/mlp/xxl/nlp_bert/bert_ner/bert_ner/modeling.py", line 27, in
import tensorflow as tf
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/init.py", line 24, in
from tensorflow.python import pywrap_tensorflow  # pylint: disable=unused-import
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/python/init.py", line 55, in
'tensorflow_estimator.python.estimator'))
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/python/tools/component_api_helper.py", line 56, in package_hook
child_pkg = importlib.import_module(child_package_str)
File "/home/mlp/python/anaconda3/lib/python3.6/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow_estimator/init.py", line 8, in
from tensorflow_estimator._api.v1 import estimator
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow_estimator/_api/v1/estimator/init.py", line 8, in
from tensorflow_estimator._api.v1.estimator import experimental
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow_estimator/_api/v1/estimator/experimental/init.py", line 8, in
from tensorflow_estimator.python.estimator.canned.dnn import dnn_logit_fn_builder
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow_estimator/python/estimator/init.py", line 25, in
import tensorflow_estimator.python.estimator.estimator_lib
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow_estimator/python/estimator/estimator_lib.py", line 22, in
from tensorflow_estimator.python.estimator.canned.baseline import BaselineClassifier
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow_estimator/python/estimator/canned/baseline.py", line 54, in
from tensorflow.python.feature_column import feature_column as feature_column_lib
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/python/feature_column/feature_column.py", line 143, in
from tensorflow.python.keras.engine import training
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/python/keras/init.py", line 24, in
from tensorflow.python.keras import activations
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/python/keras/activations.py", line 23, in
from tensorflow.python.keras import backend as K
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/python/keras/backend.py", line 33, in
from tensorflow.python.client import session as session_module
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 36, in
from tensorflow.python.ops import session_ops
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/python/ops/session_ops.py", line 34, in
from tensorflow.python.ops import array_ops
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/python/ops/array_ops.py", line 2141, in
@ops.RegisterGradient("FakeQuantWithMinMaxArgs")
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/python/framework/ops.py", line 2412, in call
_gradient_registry.register(f, self._op_type)
File "/home/mlp/python/anaconda3/lib/python3.6/site-packages/tensorflow/python/framework/registry.py", line 67, in register
stack = traceback.extract_stack()
File "/home/mlp/python/anaconda3/lib/python3.6/traceback.py", line 211, in extract_stack
stack = StackSummary.extract(walk_stack(f), limit=limit)
File "/home/mlp/python/anaconda3/lib/python3.6/traceback.py", line 364, in extract
f.line
File "/home/mlp/python/anaconda3/lib/python3.6/traceback.py", line 286, in line
self._line = linecache.getline(self.filename, self.lineno).strip()
File "/home/mlp/python/anaconda3/lib/python3.6/linecache.py", line 16, in getline
lines = getlines(filename, module_globals)
File "/home/mlp/python/anaconda3/lib/python3.6/linecache.py", line 47, in getlines
return updatecache(filename, module_globals)
File "/home/mlp/python/anaconda3/lib/python3.6/linecache.py", line 137, in updatecache
lines = fp.readlines()
File "/home/mlp/python/anaconda3/lib/python3.6/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xd2 in position 1338: invalid continuation byte

use tensorflow-gpu 1.12


☂ Freeze a v1 of the API

This is a meta-issue.
We currently have routes at /api/edge/*, but the implicit contract with edge is that things aren’t super stable (we try not to break partners, but could easily accidentally break users we don’t know about). It would be good to get something we can call a v1 of the API and treat that like a semantic version (we can add to it, but not fundamentally change the format of an existing field or remove something).

[x] Remove support for ?external_id_format when VtS is ready (#213)
[x] Drop provider_locations.eligibility field (#154)
[x] Formalize response format for errors (#66)
[x] ~Consider changing the data model to match more closely with Vaccinate the States (#49)~ (The bits worth considering adding are mostly additions, not renamings, removals, or consolidations, so are better done post v1.)
[ ] Make /api/v1/* routes
[ ] Update documentation

This is no longer relevant with the service sunsetting in a month.


Power platform admins can access admin cmndlets too, but are not listed in the prerequisites

[Enter feedback here]
The prerequisites here only list M365 Global Admin, AAD Global Admin, and D365 Global Admin to be able to access admin cmndlets. However Power Platform Admins can access those cmndlets too (and it wouldn't make much sense if they cannot).
Please add Power Platform Admins to both sections of the prerequisites.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 02f1be79-2b3a-31da-7a7d-ace1eac5d1f1
Version Independent ID: fa7c7450-15a6-edc8-5671-f45763267ca6
Content: PowerShell support - Power Platform
Content Source: power-platform/admin/powerapps-powershell.md
Service: power-platform
GitHub Login: @jimholtz
Microsoft Alias: jimholtz

@user0604
Thanks for the feedback. This change has been made.

@jimholtz thank you for your reply but I currently don't see the change. The content itself has been reorganized into another page, on which the role (Power platform Administrator) is missing too.


Fix Metrics for Goerli

Goerli pools are not even close to mainnet, for example 1 Goerli ETH is worth 4.558213e+12 DAI.
Should use realistic looking numbers.

The subgraph is currently using hardcoded numbers for tokens' USD values. When time comes for mainnet, the early returns should be deleted.


[WIP] Save inventory container: remove target option

This logic was probably meant to support a targeted refresh which we do not use or plan to. However, it actually causes us a problem since the target isn't being passed through the recursive calls.
Partial refresh for containers entities will be introduced as part of the container graph refresh in https://github.com/ManageIQ/manageiq/pull/14337. Meanwhile, I suggest we remove this code:

Remove target argument from save inventory container methods.
Remove deletes variable and always pass :use_association instead.

This should solve:
https://bugzilla.redhat.com/show_bug.cgi?id=1436132
https://bugzilla.redhat.com/show_bug.cgi?id=1451832
Still need to add tests.
cc @cben @moolitayer @simon3z

@miq-bot add_label providers/containers, bug

cc @cben @moolitayer
This worries me a little because I have the feeling we'll need some really good testing before deeming it stable enough for a stable release.

We didn't do really good testing when introduced this broken code several stable releases ago ;-)
I'm very interested in more tests, we should assume graph refresh will break any untested aspects, with an emphasis on deletions.
Current tests I'm aware of check only:

[x] Refresh into empty DB.
[x] Idempotence: 2nd refresh of unchanged inventory into same DB.
Don't have but ought to:
[ ] Additions/changes then refresh.  (Not for this PR, but we want some.)
[ ] Deletions then refresh.  Should also test what gets deleted vs disconnected.

Had some discussions with @zakiva, with some ideas how to reproducibly record more complex scenarios.

Would love to see this unused code go away

@cben @moolitayer can you test/review/approve?
How confident are we on this fix? Have you tested/verified this properly?

@zakiva are the tests ManageIQ/manageiq-providers-openshift#18 close to ready?

Yes, added also the k8s tests in https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/44 both pending review/merge

kubernetes tests merged, ManageIQ/manageiq-providers-openshift#18 is only pending on this PR, right?

@cben yes

@simon3z please review

@miq-bot add_label fine/yes

Overall this looks OK to me, but I've asked @agrare to be the merger on it to make sure I didn't miss anything.  A change like this has a chance of nasty side effects if something fundamental is missed, and Adam has been living in Inventory for several months now.

@agrare @blomquisg we have the FINE backport here:
https://github.com/ManageIQ/manageiq/pull/15543
It also includes extra-tests to be on the safe side.

@agrare @blomquisg we have the FINE backport here:
https://github.com/ManageIQ/manageiq/pull/15543
It also includes extra-tests to be on the safe side.

@agrare @blomquisg I asked @cben and @zakiva to have a FINE PR with both the extra-tests and this PR, although it doesn't seem that one yet (it seems it's just the tests).

@zakiva can you cherry-pick the merge commit to your fine pr with the added tests?  That way the tests can run on the PR before backporting it.

@simon3z :smile: I was a little confused looking at #15543.
If you want to have #15543 be the Fine backport for this PR, just remember to remove the Fine/yes label from this PR.

@miq-bot rm_label fine/yes
will backport in #15543 with some tests

Backported to Fine via https://github.com/ManageIQ/manageiq/pull/15543

@zakiva @agrare The BZ flag indicates this change needs to be backported to Euwe branch. Not sure if https://github.com/ManageIQ/manageiq/pull/15543 should be backported to Euwe or you'd need a separate PR for Euwe. Please advise.

Sent a separate PR for Euwe: https://github.com/ManageIQ/manageiq/pull/15573

Backported to Euwe via https://github.com/ManageIQ/manageiq/pull/15573


topbar: make buttons configurable

We have a use case where we would like readers that are uncomfortable directly editing our content to submit feedback using our Jira ticketing system. I am looking into creating a partial to add a feedback icon next to the edit button in the page header. Upon clicking it a new page would open to our designated URL to allow the user to submit a ticket for feedback.
If something like this would be useful for others could it be added to the core theme? The destination URL certainly would not need to be Jira but any URL useful for sending folks to a projects designated place for feedback.

That was definetly a thing that was on my backlog. I've already seen a need for this in the ksu-cs-textbooks/ fork. But as no one was asking, I postponed it - until now.
First I thought I could use Hugos menu feature (as with the shortcut links), but because buttons may need to be shown in disabled state or omitted at all on certain conditions, I plan to do it differently.

The right buttons of the header will be completly configurable by the user.
The defaults for the theme will not change compared to now.
The primary area will always be displayed.
The secondary area will be displayed in desktop mode but will move to the tertiary area on mobile.
The tertiary button will only be visible if something needs to be displayed - either by explicitly putting something into it by the user or on mobile if secondary items are moved over.
The tertiary button will not be configurable.
Pressing the tertiary button will open an overlay similar to the toc showing items vertically..
If secondary and tertiary items are shown together in the overlay, they will be divided by a horizontal ruler.
To configure the areas, a new directory structure will be established. The following shows the proposed strucutre coming with the theme. As always, you can redefine those files in your own layouts/partials/topbar folder to your liking.
- layouts
  - partials
    - topbar
      - primary
        - 1.html
        - 2.html
      - secondary
        - 1.html
        - 2.html
      - tertiary
      - topbar-button.html
      - prev.html
      - next.html
      - print.html
      - edit.html

Each of primary, secondary, and tertiary can contain files numberd starting with 1 and will be displayed from right to left in the topbar or top down in the overlay. The numbers must be sequential, the built of the areas will stop when the sequence breaks.
topbar-button.html will be the default implementation for defining topbar buttons much similar to the current button shortcode.
For the themes default functionality, there will be predefined buttons in prev, next, print and edit.
In the themes default configuration

primary/1 calls next
primary/2 calls prev
secondary/1 calls print
secondary/2 calls edit

With this indirection you are free to easily use the default functionalities at different positions in the header without copying over the implementation.
Also you will be free to implement your sequential files as you like. If you decide not to display a button at all because of certain conditions, this will be pretty fine.
Does this sound reasonable?

While the above was a nice outline, implementing this proved some design flaws. Thats the reason why it's now implemented a bit differently but not less versatile. See https://mcshelby.github.io/hugo-theme-relearn/basics/topbar/index.html


Connect Business Central to Dataverse and Dynamics 365 Sale - Problem with customers

Description:
We are attempting to synchronize Business central to Dynamics 365 Sales but ends up with problem regarding sync of Customers. The sync fails on every record on SystemUser not exist. See error below
We Tried:
We have gone through permissions and user and can't find anything that could be the stopper. The user ID guid shown on the error message cannot be found either in BC, Dataverse or Sales.
Error:
An error occurred when communicating with Dataverse.
Detailed description: Entity 'SystemUser' With Id = <> Does Not Exist
Question:
Where to look and what to do?

@viktorglemne for this type of issue you should open up a support ticket with us so that we can look at you're in context of the environments and data you're working with.
I'm sorry I cannot provide more information here, however this is likely something specific to your environment / data.

Thanks for the response! Can you please provide me with guidance where do i open a support ticket?


fix leaking TCP connections which leads to consistent conformance test failures

What type of PR is this?
/kind bug
/kind test

What this PR does / why we need it:
The problem:

At present, each HTTP request creates a new TCP connection within our tests.
We make keep-alive HTTP requests which means that after the HTTP request completes, we don't close the TCP connection.
While we are waiting for convergence, we continuously make HTTP requests which keep on leaking TCP connections.

# Example of active TCP connections to a Gateway with IP <IP_ADDRESS>
❯ ss -tan | grep <IP_ADDRESS> | head -n 3
ESTAB      0      0               <IP_ADDRESS>:50606           <IP_ADDRESS>:80
ESTAB      0      0               <IP_ADDRESS>:51233           <IP_ADDRESS>:80
ESTAB      0      0               <IP_ADDRESS>:41312           <IP_ADDRESS>:80

# Count of active TCP connections keeps on increasing
❯ ss -tan | grep <IP_ADDRESS> | wc -l
130

If the implementation takes longer to program the Gateway, the leaks end up exhausting the maximum number of active connections to a single host

The limit of maximum active connections to a single destination may either come from the client machine, or from any NAT system which sits in front of the client machine where the tests are run.

On reaching the limit, we fail to make new HTTP requests and end up failing the tests.

Solution:
Solution is pretty straightforward: we disable HTTP keep-alives.

Even right now, although we use HTTP keep-alive, we are actually not making use of this feature since we always create a new TCP connection for each HTTP request. This means the change does not have any adverse effect as we just closes the old TCP connections which we are no longer using.
Given that we are just working with tests here, we may not want to over-optimize by reusing TCP connections and just use the simplest approach to fix this right now.

Which issue(s) this PR fixes:

Fixes https://github.com/kubernetes-sigs/gateway-api/issues/2357
Does this PR introduce a user-facing change?:

NONE

Thanks @gauravkghildiyal!
/lgtm


Get error object if send_user_message request fails

https://www.rubydoc.info/github/google/google-api-ruby-client/Google%2FApis%2FGmailV1%2FGmailService:send_user_message
From the docs we know that if we send a block to send_user_message we can get the error object in the case that it fails.
We should also raise the error.

Error is being raised.


Patched images appears to hang, then WSA restarts

As per title - I ran through the scripts, didn't get any errors on patching, but when I start WSA, nothing happens.
To test my app install, I uninstalled, reverted the original .img files in the msix folder, and can install.
My quick and simple test is to open the WSA Settings app, and click on the file explorer - in the unpatched images, that comes up, in the patched image, I get the window that WSA is starting, it sits for a while and then dies.
I re downloaded GApps a few times to validate a good copy.  I am attaching the WSA Log
One other oddity I noticed, though I am not sure of the relevance,  WSA installed on my D: Drive instead of C: when I installed using Add-AppxPackage

it is at
D:\WpSystem\S-1-12-1-4140780673-1275759584-2860555682-3946019302\AppData\Local\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe\LocalState\diagnostics\logcat

31102021210201.log

@ADeltaX @nihil-2019  removing AOSP apps for some reason causes issues. You might want to fix that

@dnabsuh reading over your log, this is caused by "GoogleExtServicesConfig" not being installed, which the script does by default (it's in #GAPPS/product_output). did you remove it or do anything to the script or image before starting?


Interfacial components

See issue 1067 in gdsfactory
How easy would it be for sax.circuit to also account for interfaces between components?
I am thinking a flag that, if True,
(1) requires the user to provide models for component pairs that show up connected in the graph
(2) adds a component evaluating these models at every "connection" of the netlist
The obvious use case is to model reflections in direct transitions between waveguides with different widths or bend radii. Currently gdsfactory+SAX throws a critical warning for the former, and evaluates the second without mode mismatch reflections.
Maybe this should be added as an option in gdsfactory.get_netlist()?
Example behaviour for bend --> coupler --> straight :
Input:
circuit, _ = sax.circuit(c.get_netlist(), models=models, interfaces=True)
Output:
"Given Models": [],
"Required Models": ["bend_circular", "coupler_full", "straight"],
"Required Interface Models": [("bend_circular", "coupler_full"), ("bend_circular", "straight")],
If there were open-source EMEs around the required reflection matrices would be very easy to calculate :)

Thanks Simon,
I agree that that would make EME simulations easier.
That said, maybe this is something we can do by just patching the netlist? An interface can also be seen as a length-0 2-port (one input, one output) component and hence we could patch certain connections in the netlist by patching these 0-length component models in. I am more of the opinion that connections within sax should remain purely logical.
That said, if other people think differently about this, I'd be open to work on this (or accept a PR 😉).
@simbilod
@joamatab
@tvt173

To come back to the error you copied in above... it seems that this is unrelated to the issue at hand. The issue here is that no models for 'bend_circular', 'coupler_full' and 'straight' were given to the circuit factory... (it's hard to tell what exactly went wrong without seeing the full models dictionary)
Let me know if you need any more assistance.

Yep patching the netlist is definitely the way to go, especially since as you say the impact of interfaces shows up as non-unity transmission of 1-port in, 1-port out components that don't change the graph
My main question for everyone is if it's better to:
(1) artificially add these "interface" components in gdsfactory when extracting the netlist
or
(2) building this option into SAX directly
I edited my comment to make the "desired behaviour" example clearer :) It also seems that the interfaces would probably need to be defined on a component:port basis, and not just component, for instance as "component_name:port_name" :
"Required Interface Models": [("bend_circular:o2", "coupler_full:o1"), ("coupler_full:o3", "straight:o1")],

I think it might be worth implementing this in SAX directly.
I think a slightly cleaner api would be to always optionally accept interface models. If interface models are given, those models are patched into the netlist. If no interface models are given a 100% transmission is assumed.
This might potentially also help with resolving routes in the netlist yaml in a pretty clean way.

Sounds good, I can take a stab later this week
Maybe we can call them "connection models" to keep with the existing SAX terminology of instances + connections

I like the idea of calling them connection models.
Sounds good. I'll let you take on this issue. Let me know if you need any help.


fix(Styles): Force republish on gamut-styles and downstream deps

Overview
Still looking for a non existant 7.0.1

📬Published Alpha Packages:@codecademy/gamut-labs@4.2.9-alpha.8a5804.0@codecademy/gamut-styles@7.0.2-alpha.8a5804.0@codecademy/gamut@16.1.4-alpha.8a5804.0@codecademy/markdown-overrides@0.3.2-alpha.8a5804.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://5f7f34440f42e500ef937575--gamut-preview.netlify.appDeploy Logs


Add Ints larger than UInt64 param handling

Resolves Issue: https://github.com/plausible/ecto_ch/issues/180

@aschreifels thank you!


⚠ Bofrost.fr has degraded performance

In a1f6c05, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1275 ms

Resolved: Bofrost.fr performance has improved in b2895c5 after 6 minutes.


Adding scene object by coords

Is it possible to somehow define a point on the scene using real coordinates?

https://github.com/mapbox/tilebelt will help in this matter


Add missing cspell:ignore to registry entries

@svrnm - is this the followup to #3292, or is there more?


refactor(fallback-img): add fallback image to reduce cdn usage

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 78.46%. Comparing base (08a36ab) to head (64a2719).
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1227      +/-   ##
==========================================
+ Coverage   78.12%   78.46%   +0.33%
==========================================
  Files          40       41       +1
  Lines         512      520       +8
  Branches       84       86       +2
==========================================
+ Hits          400      408       +8
- Misses        106      112       +6
+ Partials        6        0       -6

Flag
Coverage Δ

unittests
78.46% <100.00%> (+0.33%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Invalid command to initialize a project with react-native-template-typescript

Description
I was trying to initialize a project using react-native-cli on windows with typescript support by using a typescript template as mentioned in the documentation here https://reactnative.dev/docs/typescript. But the command npx react-native init MyApp --template react-native-template-typescript mentioned in the documentation seems to prepend "react-native-template" to the command line argument --template hence the setup failing.
I got it working by just using npx react-native init MyApp --template typescript.
Documentation version
0.64

It seems I have installed an outdated version of react-native-cli that has caused the issue. The documentation is right.


Add tests to Continuous Integration

Tests in Unreal are new as of #1109. @kring
We need to integrate running these tests into the GitHub workflows that build on commit / merge / etc.
For reference, cesium-unity already has tests integrated...
https://github.com/CesiumGS/cesium-unity/actions/runs/5158167857

A related draft PR that we never merged #548


Stop pipe breaking on JS uglify error

Useful to not have the pipe break because Uglify chokes on your JS errors when you're using gulp watch.

this also came up recently: https://discourse.roots.io/t/js-build-error-gulp-work-gulp-production-fail/5268/2?u=benword
we should probably update the scripts task in the gulpfile to be like the styles one (which uses plumber):
// By default this task will only log a warning if a precompiler error is
// raised. If the `--production` flag is set: this task will fail outright.

/cc @austinpray

So this should definitely only be plumbed during watch. It should fail under all other circumstances. Having a fail silently could be deadly for automated deploys and such.

For me, the problem with with a fail in production was the site being left with no assets at all. clean gets run first before any failure happens (on the default task) so any dodgy JS being mistakenly deployed = a completely broken site. Not good!
Wonder if there's an easy way to only run clean after everything else has finished successfully?

The deployment process should abort or roll back if it encounters an error during the build process. That's where your issue really is.

@vonkanehoffen You could also avoid this by running gulp task in a "before" hook in whatever deployment solution you have. It should make sure the assets build before even starting to deploy the latest changes.
But yeah also what @mAAdhaTTah said.


fail: pip install git+https://github.com/iree-org/iree-torch.git, How can I install iree-torch with existing torch_mlir?

When I tried to install iree-torch by 'pip install git+https://github.com/iree-org/iree-torch.git', it reports below.
Collecting git+https://github.com/iree-org/iree-torch.git
Cloning https://github.com/iree-org/iree-torch.git to /tmp/pip-req-build-20px4dwa
Running command git clone --filter=blob:none --quiet https://github.com/iree-org/iree-torch.git /tmp/pip-req-build-20px4dwa
Resolved https://github.com/iree-org/iree-torch.git to commit 5fbaf505384eef01f63a618bcc4e59929b87f676
Running command git submodule update --init --recursive -q
Preparing metadata (setup.py) ... done
Requirement already satisfied: iree-compiler in /anaconda3/envs/python38/lib/python3.8/site-packages (from iree-torch==0.0.1) (20220930.282)
Requirement already satisfied: iree-runtime in /anaconda3/envs/python38/lib/python3.8/site-packages (from iree-torch==0.0.1) (20220930.282)
ERROR: Could not find a version that satisfies the requirement torch-mlir (from iree-torch) (from versions: none)
ERROR: No matching distribution found for torch-mlir
I know from another issue that I can install torch_mlir individually, however, I have built torch_mlir from source code and set pythonpath. I can import torch_mlir in other python source code successfully, like below.
Python 3.8.15 (default, Nov 24 2022, 15:19:38)
[GCC 11.2.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.

import torch
import torch_mlir
import torch_mlir_e2e_test

How can I install iree-torch with existing torch_mlir?

Since you're building and installing it yourself, I'm not sure what may have gone wrong.  It seems like pip doesn't think you have it installed, for whatever reason.  Some workarounds I can think of would be to git clone the repo, remove the torch_mlir requirement, and install from there (since you're confident it will be available at import time).
It looks like pip also has a --no-dependencies flag you could try using.

Thank you. I successfully installed iree_torch by  pip install git+https://github.com/iree-org/iree-torch.git --no-dependencies


Various containerd-shim-runhcs bug fixes/improvements

Forward containerd debug to shim invocation
Fixes containerd-shim-runhcs Delete on exec id
Fixes containerd-shim-runhcs State on exec id
Adds containerd-shim-runhcs verbose logging support

Codecov Report

Merging #2686 into master will decrease coverage by 2.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #2686      +/-   ##
==========================================
- Coverage      45%   42.99%   -2.02%
==========================================
  Files          92      100       +8
  Lines       10114    10588     +474
==========================================
  Hits         4552     4552
- Misses       4842     5316     +474
  Partials      720      720

Flag
Coverage Δ

#linux
46.99% <0%> (-1.76%)
:arrow_down:

#windows
40.13% <0%> (-1.64%)
:arrow_down:

Impacted Files
Coverage Δ

runtime/v2/shim/shim.go
0% <0%> (ø)

runtime/v2/shim/util_windows.go
0% <0%> (ø)

runtime/v2/shim/util_unix.go
0% <0%> (ø)

runtime/v2/shim/shim_unix.go
0% <0%> (ø)

runtime/v2/shim/shim_windows.go
0% <0%> (ø)

runtime/v2/shim/util.go
0% <0%> (ø)

runtime/v2/shim/shim_linux.go
0% <0%> (ø)

runtime/v2/shim/reaper_unix.go
0% <0%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f88d3e5...18f7a7c. Read the comment docs.

LGTM


What happens when dates are the same?

We discussed in ECMA 402 and Issue #1 that there seems to be a desire to allow dates to be given to the API in either order.
What happens if the dates are the same?
I think this should not be an exception, because if we are friendly about the order in which you provide dates, it feels unexpected that we would throw an exception just in this one case.
A few options:

Fall back to a non-range format
Display the range naively, as in "July 20 - 20, 2018"
Use an approximation pattern, as in "July ~20, 2018"

This question also came up in the context of currency range formatting.  The solution over in that space is not locked in yet.  The decision here might set a precedent for how to deal with this problem in range formatting APIs in general.

The three options look interesting. I think that instead of simply using one fallback mechanism, we could potentially give users the possibility to choose which one they want to use.
Option 1)
TR-35 already uses this as the fallback when the two dates are the same: If all calendar fields that are being displayed are common between the two dates (e.g. equal or sufficiently similar dates), the dates will be formatted using the regular date/time format.
This is the fallback that's being used on the current draft of the spec text.
Option 2)
In this case, the date interval should be formatted using the interval pattern for the smallest calendar field and not the regular date/time pattern (as in option 1).
For example, we have these interval patterns:
y: 'MMM dd, y - MMM dd, y'
M: 'MMM dd - MMM dd, y'
d: 'MMM dd - dd, y'
If both date's y, M and d are equal, then the d pattern should be used.
Option 3)
Supporting this fallback will require implementers to add additional localized pattern data (the previous two options can be implemented using the data that is already there).
We should explore this option, but I think we should add it only if we see an actual need for an approximation pattern.

We discussed this in the August 2018 Ecma402 monthly call and we agreed to only support Option 1 on the initial version of this proposal.
We could support Option 2 (with option 1 being the default) on a second version.

Closing this issue for now. We can reopen once we decide to explore options 2 or 3.

I'm +1 to keep it as Option 1.

We could support Option 2 (with option 1 being the default) on a second version.

I don't think this should ever block this current proposal.


Add python formatter

Fixes #1030

Turns out i actually meant "formatter" not "linter" when I opened the issue.

I'm vaguely surprised by how little this changed the file. Perhaps we want a more opinionated formatter like Black or YAPF?
https://blog.frank-mich.com/python-code-formatters-comparison-black-autopep8-and-yapf/

I'm in favor of Black, we use it at work

I'm in favor of Black, we use it at work

Awesome. Do you have any default config you like? That'd help this move forward. I'm way out of my familiar territory on setting this up. So if you either have a config file you can share or if you just wanna take over this PR, I welcome it. :)

yeah happy to just take over this issue :)

Superseded by #1120.


Berks install - chef supermarket

Hello all ,
i am trying to use supermarket  . however berks install throws type error
matadata.rb file contains :
depends 'ark', '~> 4.0.0'
i see there is already open issue for the same but raised on jan11 . Anyone has any idea on this ?
over view of error - also attached detailed log
"Installing seven_zip (3.1.0)
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:3: warning: already initi
alized constant Archive::LIBPATH
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:3: warning: previous defi
nition of LIBPATH was here
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:4: warning: already initi
alized constant Archive::PATH
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:4: warning: previous defi
nition of PATH was here
Installing windows (5.3.0)
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:3: warning: already initi
alized constant Archive::LIBPATH
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:3: warning: previous defi
nition of LIBPATH was here
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:4: warning: already initi
alized constant Archive::PATH
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:4: warning: previous defi
nition of PATH was here
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:3: warning: already initi
alized constant Archive::LIBPATH
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:3: warning: previous defi
nition of LIBPATH was here
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:4: warning: already initi
alized constant Archive::PATH
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/ffi-libarchive-0.4.6/lib/ffi-libarchive.rb:4: warning: previous defi
nition of PATH was here
TypeError unable to resolve type 'mode_t'"
berks_error.txt

i was working on your issue and will let you know once it is done

Thanks for looking into it . I tried to add mentioned line in the file and ran the berks install , however it failed with belo error .
OS: win7
PS D:\Devops\Chef\chef-starter\chef-repo\cookbooks\supermarket_mysql> berks install
An error occurred while reading the Berksfile:
The version constraint syntax you are using is not valid. If you recently
upgraded to Chef 0.10.0, be aware that you no may longer use "<<" and ">>" for
'less than' and 'greater than'; use '<' and '>' instead.
Consult https://docs.chef.io/config_rb_metadata.html for more information.
Called by: depends 'java', '~= 3.2.1'
Called from:
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/chef-14.10.9-universal-mingw32/lib/chef/cookbook/metadata.rb:667:i
n validate_version_constraint'   C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/chef-14.10.9-universal-mingw32/lib/chef/cookbook/metadata.rb:291:i n depends'
D:/Devops/Chef/chef-starter/chef-repo/cookbooks/supermarket_mysql/metadata.rb:13:in from_file'   C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/chef-14.10.9-universal-mingw32/lib/chef/mixin/from_file.rb:34:in
instance_eval'
C:/opscode/chefdk/embedded/lib/ruby/gems/2.5.0/gems/chef-14.10.9-universal-mingw32/lib/chef/mixin/from_file.rb:34:in `
from_file'

i think there is some syntactical error in your metadata file
first try using foodcritic in powershell where your cookbook is present so it will evaluate your cookbook and let you know if there are any syntactical errors in your cookbook so that we can proceed our investigation further

created new linux workstation and new starter kit . It worked there .
on my current lappy top its stil issue , not sure if it  has got to do any thing with any version of tools.
Closing this thread , Thanks Bhaskar,for looking into it


Any plans of hiding "Windows hidden files" on WSL bash?

Now that %userprofile% is mounted as the ~ directory, became clear to me that NTUSER.DAT and a thousand others system files are unnecessary shown to WSL. So, is there any plans of hiding "Windows hidden files" on WSL bash? They are already specially treated as accessing them was causing BSoD. Hiding them, to me, is a step forward to prettify ls output.
On the other hand, *NIX applications tend to store configuration files on home directory using the dot convention, and then %userprofile% became full of dotfiles. Any plans of automatically applying the atribute on Windows-side when a .dotfile is created on WSL?

@mths0x5f Great questions! A couple of clarifying comments.

The ~ directory does not actually map to %userprofile%.  The user home directory is in %localappdata%\lxss\home (or %localappdata%\lxss\root for root).  If you launch bash.exe from a cmd prompt it will launch in the current working directory of the cmd prompt.  You can launch in your user's home directory by typing "bash.exe ~"
The bluescreen caused by opening the NTUSER.dat files has been fixed.  The open will now fail and you won't be able to bugcheck the machine.  Previously we had a bug in the lookup failure path for these types of files but that was fixed.
@russalex has a great writeup on the differences between the /mnt/ drive mounts and the Linux filesystem.

@benhillis  I'm running build 14352. Update was applied yesterday.

The ~ directory does not actually map to %userprofile%.

That's weird. I swear I can ls ~ and actually see %userprofile% content...
EDIT: I've just tried and well... a picture is worth a thousand words:

The bluescreen caused by opening the NTUSER.dat files has been fixed.

Yup, I know. what I'm proposing is about this:

As you can see, ls ~ output even files with no reasons to. They're in the folder but they can't (and shouldn't) be accessed inside WSL, so what is the point of this kind of file being visible?
Obs.: You can also notice on background, .bash_history, .ssh/, .dbus-keyrings/ and .python_history, files created by *NIX applications inside WSL.
Thanks for your response.

@benhillis  I'm running build 14352. Update was applied yesterday.
SECOND EDIT (I sincerely apologize saying this is default behavior):
I decided to reinstall the image using lxrun and this behavior is gone. So I remembered one of the things I tried first was mapping ~ to %userprofile%, but gave up when it didn't work. At that time, I was editing /etc/passwd. Weeks later, after an update it works and I didn't remember. I'm sorry. :disappointed:
But questions still valid if in the future, if mapping ~ became a feature.

The ~ directory does not actually map to %userprofile%.

That's weird. I swear I can ls ~ and actually see %userprofile% content...
FIRST EDIT:
I've just tried and well... a picture is worth a thousand words:

The bluescreen caused by opening the NTUSER.dat files has been fixed.

Yup, I know. what I'm proposing is about this:

As you can see, ls ~ output even files with no reasons to. They're in the folder but they can't (and shouldn't) be accessed inside WSL, so what is the point of this kind of file being visible?
Obs.: You can also notice on background, .bash_history, .ssh/, .dbus-keyrings/ and .python_history, files created by *NIX applications inside WSL.
Thanks for your response.

@mths0x5f No problem at all!  As you noticed we now support changing your user's home directory, and that directory can be somewhere under /mnt/c/.  There may be things that do not work 100% due to the differences between VolFs (the Ubuntu file system) and DriveFs.(/mnt/c).  We have a blog post and video coming soon that will explain some of the differences in great detail.
You do raise an interesting point about what files should show up in DriveFs.  Right now we don't do any kind of filtering on what files show up in directory listings for DriveFs but it's something we can consider in the future.

On Wed, Jun 1, 2016 at 5:43 PM, Ben Hillis<EMAIL_ADDRESS>wrote:

@mths0x5f https://github.com/mths0x5f No problem at all! As you noticed
we now support changing your user's home directory, and that directory can
be somewhere under /mnt/c/. There may be things that do not work 100% due
to the differences between VolFs (the Ubuntu file system) and
DriveFs.(/mnt/c). We have a blog post and video coming soon that will
explain some of the differences in great detail.
You do raise an interesting point about what files should show up in
DriveFs. Right now we don't do any kind of filtering on what files show up
in directory listings for DriveFs but it's something we can consider in the
future.

Caution hiding things can prove a mixed bag.
Perhaps require a special group ID that is normally not assigned.
There may be a dozen+ files where the answer is obvious to MS but this is
where aspects of MS security and *niux security differ at times.
See "ls -M " and other extended file attributes for security enhancements
to Linux.
https://www.ibm.com/support/knowledgecenter/SSLTBW_1.13.0/com.ibm.zos.r13.bpxa500/ls.htm
The value is that done correctly file system attributes could make it
obvious why a file
or directory is closed.   Ad-hock filtering would add confusion to places
where clarity
makes the difficult possible.
--
T o m    M i t c h e l l

I understand there is a grander scale at play, but I resorted to a simple ls alias I found off of superuser.com and modified for my needs:
alias ls='command ls --human-readable --group-directories-first --color=auto -I NTUSER.DAT\* -I ntuser.dat\*'

At least for short term, this solves the problem of hiding all those pesky NTUSER.DAT files that I am not interested in.

To me it's mostly an annoyance when running ls (and this is not unique to WSL--this has annoyed me for years on Cygwin too).  I've considered just building my own patched ls that by default excludes Windows hidden files.

I ended up writing an ls() function that takes --ignore arguments from dir to know what to hide. Works well: https://gist.github.com/notlaforge/f05bdb9540308a63de90f5f3d69ced95

Is there any solution to this now? My antimalware software (Palo Alto Traps) creates a bunch of hidden/system files in directories to check for malware that shouldn't be visible to the user and ls shows them in WSL. I've tried manually adding --ignore options for them but the pattern is not consistent so it's not possible to exclude them all. The gist posted above by @notlaforge no longer exists. Any suggestions?

I also took a look at uutils coreutils, which is able to recognize and hide Windows hidden files. But that only has effect in the Windows version of coreutils, not the Linux version which is used by WSL.
One big question is whether the 9p filesystem used by WSL to mount the Windows partition even provides the metadata necessary to filter on system/hidden files. Does anyone know?

Adding my comments here since my attempt to open a new issue was closed as a dupe:

Unfortunately this is something that WSL can do since there's no mechanism for us to expose Win32 attributes on Linux mount point.

Is there nowhere a bug on this could be filed? What code needs to be modified to expose those attributes--Windows OS code? 9p filesystem? This is a systemic issue that really should be solved universally rather than with one-off hacks.

If you need to "hide" some files maybe an alias for ls with a custom filter is the easiest way for you.

I don't see a way to do this with files like the antimalware honeypots -- they don't have a predictable filename convention. If there were a way for ls to access the output of windows dir, I guess that could work, but seems awfully inefficient.

I ended up writing an ls() function that takes --ignore arguments from dir to know what to hide. Works well: https://gist.github.com/notlaforge/f05bdb9540308a63de90f5f3d69ced95

what happened to it where is it?


Cleanup NetBeans license header for module netbinox

Review and cleanup the license header in netbinox
Oracle donated NetBeans to the Apache Software Foundation.
Your task now is to replace the old license header that has Oracle (and/or Sun Microsystems
and/or NetBeans) in it with the standard Apache Software Foundation license header.
For an empty file that supports headers you must add the Apache license header.
Note that you have to use the proper license header for Java, .properties or HTML files.
Look at the nearby files for templates and copy-paste the license header.
When done commit the changes with a commit message that starts with first line
"[NETBEANS-54] Module Review " and a message body describing your review.
See a longer explanation about what we are doing here: https://cwiki.apache.org/confluence/display/NETBEANS/List+of+Modules+to+Review
Please announce in a comment when you have started work.
Files that need to be looked at in netbinox:
netbinox/test/unit/data/jars/activate.mf
netbinox/test/unit/data/jars/activate/org/activate/entry.txt
netbinox/test/unit/data/jars/agent.mf
netbinox/test/unit/data/jars/agent/org/agent/HelloWorldAgent.java
netbinox/test/unit/data/jars/depends-on-simple-module-2.mf
netbinox/test/unit/data/jars/depends-on-simple-module.mf
netbinox/test/unit/data/jars/external.mf
netbinox/test/unit/data/jars/externaldir.mf
netbinox/test/unit/data/jars/hook.mf
netbinox/test/unit/data/jars/simple-module.mf
netbinox/test/unit/data/jars/simple-module/org/foo/hello.txt
netbinox/test/unit/data/jars/uses-swing.mf

jkostaras


OG title & image

Is your feature request related to a problem? Please describe.
We need the product show certain message and image.
Describe the solution you'd like
Set up the OGtitle and OGimage.
OGtitle:
大家來找廠｜動手指，拆工廠
OGimage:
https://drive.google.com/file/d/1Zsw0zb4zU7tBE-GG4QQDHy-DMtxA9hDr/view?usp=sharing

Description
5000人花3分鐘，就可以找出農地違章工廠！


Adds Battery Chart widget and app

The icon.js needs fixing. Don't know why I never manage to get this working the first time. I would like to already release it, though. Since the data logging seems to work and people should be aware that the logger exists.

Thanks! Just done - I think it was just using app.img.js and not .img - changed, and now it passes :)


wireguard: Clarify token scope requirements

Until we smooth out this flow with oauth2, we need to explain this
better.
Signed-off-by: Andy Doan<EMAIL_ADDRESS>

Docs for 357a9505a198e22c4f0bf4b850a57e560dc4a8fc are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1310/docs/artifacts/html/index.html


Create date parser with Parboiled2

We're going to be moving forward using the a parser lib for more and more parsing of Marc fields, so to be sure fastparse is right, we'd like to give it a go with Parboiled first before moving forward.

https://github.com/wellcometrust/catalogue/pull/73


Allow the image to be rotated independent of the camera

This would provide a method for rotating the image rather than the camera.
The benefit of doing this rather than the existing startAngle property is that it works the same regardless of camera control method or panorama type.
The main difference is that it doesn't change the orientation of the direction indicator. In my projects case, that's a benefit since we are applying a rotation correct for the fact that images start facing backwards using this library

Thanks for the PR


Make installable via LuaRocks

Switched to ltreesitter-ts which bundles the tree-sitter library as well as ltreesitter. Also, put in an issue in the ltreesitter repo about potentially including the library as part of the bindings.
Not sure why the build is failing, planning to have it fixed before merging. The script works locally and my hererocks [local] setup also works just fine. When installing tree-sitter-cli, it seems to not be able to find the builder for it, which is a bit odd.
closes #26

Not sure why the build is failing, planning to have it fixed before merging. The script works locally and my hererocks [local] setup also works just fine. When installing tree-sitter-cli, it seems to not be able to find the builder for it, which is a bit odd.

Turns out it worked locally because I had the tree-sitter-cli builder installed at the system level and it was finding that. When I removed it, I started getting the same error message.
The error message was about not being able to find the builder, which got fixed by upgrading to LuaRocks 3.10.0+. I think there might by ways to support versions below 3.10.0. I'll investigate that a bit, and see what can be done.


Fix use-after-move in console implementation

Summary:
Changelog: [Internal]
In the new CDP backend, calling any console method a second time involves a call to a moved-from std::function. This shouldn't work, but depending on the toolchain, sometimes it does - likely because moving from a std::function leaves it in an unspecified state rather than a definitely empty state, and std::functions are always copyable so falling back to a copy is technically legal.
In the code in question, we're right to want to avoid a copy of the body function into the argument of delegateExecutorSync - only one copy of this function needs to exist at a time. But the correct way to avoid this copy is to capture body by reference, as we can do that repeatedly with no ill effects. (delegateExecutorSync is, as its name suggests, synchronous, so there are no lifetime issues.) Doing this also allows us to remove the use of mutable so the capturing is by const reference.
Differential Revision: D56673529

Merged as https://github.com/facebook/react-native/commit/fb0c856cf298c6f9310423fb443a6d2c8f3b6252


add renderLastLine method to overriding if it need

I use this component to truncating a text, and I need to use react-linkify inside. I can override renderLine for this goals, but I noticed that last line rendered with broken link, because of slicing text.

@thykos does the change with renderLastLine actually make any functional difference?

@thykos does the change with renderLastLine actually make any functional difference?

yes, if we use linkify and last line include link, link will be cutted and broken. With renredLastLine we can prevent broke


add rename feature to Duplicate

Add rename feature to Duplicate

Hey! Looks pretty good, but we already have the similar feature that is called 'Duplicate'. Any reason why we need one more similar possibility?

I think now it's very similar, so it's have not many sense now. (Be honest I did it cause I didn't know about duplicate) But when I creating it, I got some ideas in mind to upgrade it to something unique (like .tamplateignore similar to .gitignore). So I move it to draft

And Duplicate don't change project name (notice it's after test Duplicate). ^_^

I think we can apply the idea to 'Duplicate'. For instance, add a checkbox for overriding the name and add something like '.duplicate-ignore' or stuff. What do you think?

I think we can apply the idea to 'Duplicate'. For instance, add a checkbox for overriding the name and add something like '.duplicate-ignore' or stuff. What do you think?

Yes, I understand. Create similar features is bad idea. I will move this functionality to Duplicate.

Thanks!


istio.io test framework: set default Script.WorkDir to env.IstioSrc

I think this will eliminate a potential source of errors when writing tests. Most istio.io test scripts will want to use files from the samples/ directory, which is only accessible when you set the WorkDir correctly.

@dgn: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
84df252d3b17eaa6fc92d5a828bbd9ab3eb7e466
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Nevermind, this does not work with the SDS tests. Closing, going for another solution.


Added Open Issues Section

cc @joshfree, @terrajobst

@davidfowl did you have anything to add around the slow-span impl?

@KrzysztofCwalina this is an OK list.  Did you want to seed the discussion on these by putting a stake in the ground on any of them?

@joshfree, I will try. I really would like to put a stake in the ground for Memory<T> design, but I need some time to prototype.


Configure the containers of the infra to always restart

The idea is that the containers of the infrastructure restart if they exit for a reason other than being manually stop. This change should contribute to fix the issue where the controller container dies sometimes during weekly Synapse updates.

[x] Controller
[x] Data-node
[ ] ELK

Tagging @gkowalski because we discussed this issue the controller issue this morning.
@thomasyu888 What is the typical time range when Synapse is down for its weekly update?

@thomasyu888 Can you apply this update?

I'm going to leave ELK alone for now. Typical time range that Synapse is down for update is 15-30 minutes I think.

Aside setting the restart policy for the controller, do you know how the controller would need to be modified in order to prevent its crash when Synapse is down? Maybe this could be a separate ticket.

The client is actually configured to do so but it's not effective 100% of the time.

Does the check in the boxes means that the change is effective? If yes, we can close this ticket.

Yes, the check in the boxes means the change is effective on the Sage side.

I see that the docker-compose of the data-node has the restart policy. What does George have to do to apply the update for the controller? I don't see a docker-compose to run.

@tschaffter, you added the restart policy in the data node: https://github.com/nlpsandbox/data-node/blob/main/docker-compose.yml.  All he has to do is pull the image down and restart the data node and it should be applied.

I know. My question was for the controller.

Ah, clearly i'm on labor day mode and not reading carefully. Please review: https://github.com/Sage-Bionetworks/SynapseWorkflowOrchestrator/pull/32/files.  Once merged, it is the same workflow as how he can update the data node.

@tschaffter Am I good to go to pull down this latest code ?

@gkowalski Yes. In the future we will write down specific instructions for updating the components of the infrastructure but for now let's move forward. The update consists of the following:

Data Node: the docker-compose.yml has been updated 15 days ago to include the restart policy. If you don't know how to update we can provide instructions.
Controller: nothing to do, the update is already effective according to @thomasyu888

updated our data-node


Add an API version of the rendered output.

I happen to have a use case where I'd like to use the Jingo interface to maintain my wiki contents, however, for my API's audience, I'd like to embed the pages directly into another web application that I already have.  For this purpose I'd like to basically expose the page retrieval/rendering part of the application as an API.  This API would do the same as the standard /wiki/:page route, however leave out the layout and toolbar parts.
Then I can call the API and load another div in my other application with the result, skin with some CSS and now I've got the wiki pages in my app.
I can edit the pages, live, in the usual way also...best of both worlds.
I don't know if anyone else has the same needs as I do, but I figure I could post my PR, just in case.

Hi @kaiserfro
this is a basically what I have in mind for Jingo 2, which (if ever released) will split jingo in a REST server and a client (HTML + JS) part. The project will release both of them, so one could use only the server or both to have what we have now :)
Actually your PR is a good idea because it would already meet some of the criteria which are the basis for Jingo 2, but I am not going to merge as it is (I will mention you in the credits nonetheless), because I need to think a bit more about it and I will probably release it with Jingo 1.6.
Thanks a lot!

In designing this API, do you intend to make use of Linked Data standards such as LDP (for a generalized storage backend) or Hydra (for a self-documenting API)?
Exposing Jingo's data via JSON-LD as RDF would make its content immediately available to DBpedia and easier searchable for anyone due to the structured data attached to pages. Content-Negotiation would even allow for using the same routes and URLs for both machine and browser consumers.
Is there any anticipation about if and/or how to include the Jingo community in preparing 2.0?

@almereyda wow, lot of food for thought here! I am not familiar with LD and I should definitely take a look at it.
Jingo 2 at the moment (as you'd probably already inferred) is just an idea. It will be a complete rewrite of the codebase (to finally also move to ES2015, SASS and Webpack too). The effort would probably take something around 80 hours which in my current job situation (a crazy startup) would take a long time stretch.
I'd be more than happy to involve other people in this effort but this is also why I want to start the project only when I'd be able to finish it.

why I want to start the project only when I'd be able to finish it.

Isn't this the main reason why you host the code here, to attract further developers and engage your initially very own project in an ecosystem?
Could you activate the wiki for this GitHub Repository at https://github.com/claudioc/jingo to allow the community to scope expectations, possible hints for implementation and design quirks?
I.e. the role of a plugin/media system if server and client are decoupled (where do they live, how many assumptions does a client plugin make, how's it served)?

For a more exhausting investigation of where my motives are coming from:
I'd be happy to contribute content around a simple git-based node Markdown wiki engine, possibly involving real-time capabilities, (nested) templating and even more loosely-coupled alignment with an existing wiki federation (Federated Wiki - http://wikity.net/).
Goal for many could be to replace Hackpad as an "etherwiki", in the simplest form possible and extensible to computational scopes (think of IPython, IJulia) while retaining user ownership of data (Authentication mainly denominated to E-Mail, currently involving GitHub, Google and git, Persona favourable) or bleeding edge "standard" readwriteweb APIs (like LDP, Hood.ie, remoteStorage, etc.).
As you see on http://wiki.transformap.co/wiki/TransforMap, it's even simple to integrate into another federation of annotations by including https://hypothes.is - also see #117.

It is of course a pleasure to see this project used and contributed to by a lot of people. What I meant with that comment is that – so far – Jingo development has been quite "under control" because I've been able to follow it and because after all it is quite a simple piece of software. Of course I'd like to see further and great developments of it but... will I be able to follow them if its community really wants it to become a ecosystem? Isn't there a peril for it to become yet another bloated monster, unmaintainable and horribly patched just to "make it work"? I'd hate that.
As we already discussed, I don't think Jingo 1.x would be suitable for these features (real time above all, because it would need a WebSocket channel and even maybe something like what I use on my antipad.com, https://github.com/share/ShareJS)
My "problem" is that your use cases look quite complex, in that you have quite a broad understanding of technologies with which I am not familiar with :/

Well, I had an immediate need to hack together a wiki page renderer so I could embed the wiki in another application.  Jingo fit the bill for a quick and easy renderer and editor.  My implementation of an API for the renderer is pretty crude, so I would not expect that to be any thing like a final solution.  Aside from that, there is probably few other features that would be useful for my needs.

@kaiserfro since the request to the "api" is made through an ajax call (I see the CORS header you added), I guess the cleanest way is to just read the X-Requested-With header (which it is automatically set by almost all frameworks and can be manually set when it doesn't) and, if the value is XMLHttpRequest, provide the rendered body with anything else.
The nice advantage is that we don't need another route, just a couple of IFs :)
What do you think?

That sounds perfect...better than duplicating the code.  As for the CORS stuff, hardcoding the headers to a particular value is probably not ideal either.  Adding those values to your config file is probably better.

I implemented this feature (not directly with this PR, though, as I mentioned) and released it with 1.6.0. I added you to the AUTHORS because I guess this is the least I can do to thank you for the idea. I also made the CORS configuration a bit configurable as you can read in the wiki page
Thanks!


Css issue

Hi,
I am trying to build my project and it fails on the css of this library (csso gulp). It specifically points to these lines:
moment-picker { position: relative; }
.moment-picker .moment-picker-contents { cursor: pointer; }
.moment-picker .moment-picker-container { color: #404040; min-width: 15em; background: #fff; padding: 4px; border: 1px solid #f0f3f4; border-radius: 4px; position: absolute;
	top: 100%; margin-top: 4px; margin-left: -.5em; box-shadow: 0 2px 4px rgba(0, 0, 0, .075); z-index: 5; }
.moment-picker .moment-picker-container:before,
.moment-picker .moment-picker-container:after { content: ''; display: block; width: 0; height: 0; border: 8px solid transparent; border-top: none; position: absolute;
	top: -9px; left: 15px; }
.moment-picker .moment-picker-container:before { border-bottom-color: #f0f3f4; border-width: 9px; }
.moment-picker .moment-picker-container:after { border-bottom-color: #fff; margin-top: 1px; margin-left: 1px; }
.moment-picker table { border-collapse: collapse; border-spacing: 0; width: 100%; table-layout: fixed; }

When I run the code through a css validator (https://jigsaw.w3.org/css-validator/validator) I get the following errors:

URI : TextArea
7	.moment-picker .moment-picker-container:before, .moment-picker .moment-picker-container:after	Lexical error at line 7, column 31. Encountered: "?" (63), after : "" ;??}
9	.moment-picker .moment-picker-container:after	Lexical error at line 9, column 110. Encountered: "?" (63), after : "" ;??}

Any idea?

After a lot of research, it seems like the build process of the plugin is somewhere faulty and the generated css is not valid but also different than the original. Minification?

Ok @checklist, I know what this is caused. This is due to the keyboard combination ALT+SPACE on mac that generates a non-breaking space character (0xA0) instead of a normal space (0x20).
Give me five to replace all these characters.

Let me know if this causes troubles to you yet. :)


Generate JSON response instead

I'm not sure if this feature is already implemented or not, but I would find very useful to retrieve search data as a JSON object instead of XML: it would simplify drastically the parsing process.
Maybe adding a flag to choose response type could be the way to go...
Example of possible JSON search response:
[{
  "title": "Hello World!",
  "url": "/hello-world",
  "type": "html",
  "content": "
Hello World!
"
}. {
  ...
}, {
  ...
}]

@zuck I've implemented this feature via #20 .
Try to update this plugin and set the path configuration in your _config.yml file to be search.json .

Ops, sorry, my fault! Thank you, you can close this issue then...

@zuck Actually the feature is fired by you. So thank you for asking that.

Yes, so sorry again: I was reading the GitHub's notification by email on a phone and I didn't realize your commit was the response to this issue. I thought you already implemented the feature before my issue report...eh eh, I need some coffee! :smile:
So thank you for your work!!


How can I add new latex packages?

I tried to convert my previously written .tex file to .qmd, but some added packages, such as usepackage{bm}, I don't know which part of the .qmd file such code should be placed.

Awesome! Typically, you would include these type of statements in the document header, using include-in-header. more here:
https://quarto.org/docs/output-formats/pdf-basics.html#latex-includes


plugins/lsp: add ast-grep language server

Add support for the ast-grep language server.
Fixes #1463

I get the following error message when trying to use it
Failed to setup: ...mPackages/start/nvim-lspconfig/lua/lspconfig/configs.lua:71: attempt to index local 'user_config' (a nil value)

But the plugin does work


Do not apply extra spacing twice.

Remove unnecessary code missed in https://github.com/godotengine/godot/pull/80954 and causing extra spacing to be applied twice.
Fixes https://github.com/godotengine/godot/issues/83061

Thanks!


New pagination / iteration model.

One fairly large change requested, I can't submit and official review on this though because it's technically my PR.

Few more minor requests.

All LGTM, again, can't officially approve this since I opened it.


Prepare 38.0.0

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

I'm going to get this in so I can cut the release, the release process will serve as review


redoing docs

Codecov Report

Merging #236 (a6aacc1) into main (3f851f9) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #236   +/-   ##
=======================================
  Coverage   69.40%   69.40%
=======================================
  Files         106      106
  Lines        6178     6178
  Branches      488      488
=======================================
  Hits         4288     4288
  Misses       1773     1773
  Partials      117      117

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3f851f9...a6aacc1. Read the comment docs.


Why is an error returned (exit code 1) just because no strict files were found?

Title pretty much sums it up.  Was just wondering why an error would be returned in the event that no files match the strict criteria.  This may be desired behavior; for instance, I intentionally set the "paths" array such that no files would be checked.  In this case I'd expect the build script to continue successfully when using "npm run build tsc-strict && other-script"; instead it fails.

Would be happy to create a PR to address this, unless this was intended behavior.

I'm trying to understand using the script if the paths array is empty and there are no //@ts-strict comments. Could you tell me more about your use case?