text:
GPU-NVIDIA driver install: Improve log collection

Fix #293
[LISAv2 Test Results Summary]
Test Run On           : 06/04/2019 09:59:07
ARM Image Under Test  : canonical : ubuntuserver : 16.04-LTS : 16.04.201905303
Total Test Cases      : 1 (1 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:12

   ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes)
-------------------------------------------------------------------------------------------------------------------------------------------
    1 GPU                  NVIDIA-GRID-DRIVER-VALIDATION                                                     PASS                 8.49
	Using nVidia driver : GRID
	lsvmbus: Expected "PCI Express pass-through" count: 1, count inside the VM: 1 : PASS
	lspci: Expected "3D controller: NVIDIA Corporation" count: 1, found inside the VM: 1 : PASS
	lshw: Expected Display adapters: 1, total adapters found in VM: 1 : PASS
	nvidia-smi: Expected GPU count: 1, found inside the VM: 1 : PASS

[LISAv2 Test Results Summary]
Test Run On           : 06/04/2019 09:59:12
ARM Image Under Test  : canonical : ubuntuserver : 16.04-LTS : 16.04.201905303
Total Test Cases      : 1 (1 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:18

   ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes)
-------------------------------------------------------------------------------------------------------------------------------------------
    1 GPU                  NVIDIA-CUDA-DRIVER-VALIDATION                                                     PASS                15.15
	Using nVidia driver : CUDA
	lsvmbus: Expected "PCI Express pass-through" count: 1, count inside the VM: 1 : PASS
	lspci: Expected "3D controller: NVIDIA Corporation" count: 1, found inside the VM: 1 : PASS
	lshw: Expected Display adapters: 1, total adapters found in VM: 1 : PASS
	nvidia-smi: Expected GPU count: 1, found inside the VM: 1 : PASS

Running tests against canonical ubuntuserver 18.04-lts Latest and OpenLogic CentOS 7.5 Latest

please also include 16.04 in testing, the nvidia dkms log path is different on it. The code changes will handle that just fine, but please do a run there as well.

@chvalean Previous copied results for ubuntu 16.04, please double check.
[LISAv2 Test Results Summary]
Test Run On           : 06/04/2019 10:28:16
ARM Image Under Test  : canonical : ubuntuserver : 18.04-lts : Latest
Total Test Cases      : 1 (1 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:12

   ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes)
-------------------------------------------------------------------------------------------------------------------------------------------
    1 GPU                  NVIDIA-GRID-DRIVER-VALIDATION                                                     PASS                 9.26
	Using nVidia driver : GRID
	lsvmbus: Expected "PCI Express pass-through" count: 1, count inside the VM: 1 : PASS
	lspci: Expected "3D controller: NVIDIA Corporation" count: 1, found inside the VM: 1 : PASS
	lshw: Expected Display adapters: 1, total adapters found in VM: 1 : PASS
	nvidia-smi: Expected GPU count: 1, found inside the VM: 1 : PASS

[LISAv2 Test Results Summary]
Test Run On           : 06/04/2019 10:28:25
ARM Image Under Test  : canonical : ubuntuserver : 18.04-lts : Latest
Total Test Cases      : 1 (1 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:14

   ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes)
-------------------------------------------------------------------------------------------------------------------------------------------
    1 GPU                  NVIDIA-CUDA-DRIVER-VALIDATION                                                     PASS                10.95
	Using nVidia driver : CUDA
	lsvmbus: Expected "PCI Express pass-through" count: 1, count inside the VM: 1 : PASS
	lspci: Expected "3D controller: NVIDIA Corporation" count: 1, found inside the VM: 1 : PASS
	lshw: Expected Display adapters: 1, total adapters found in VM: 1 : PASS
	nvidia-smi: Expected GPU count: 1, found inside the VM: 1 : PASS

[LISAv2 Test Results Summary]
Test Run On           : 06/04/2019 10:42:53
ARM Image Under Test  : OpenLogic : CentOS : 7.5 : Latest
Total Test Cases      : 1 (1 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:17

   ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes)
-------------------------------------------------------------------------------------------------------------------------------------------
    1 GPU                  NVIDIA-GRID-DRIVER-VALIDATION                                                     PASS                14.06
	Using nVidia driver : GRID
	lsvmbus: Expected "PCI Express pass-through" count: 1, count inside the VM: 1 : PASS
	lspci: Expected "3D controller: NVIDIA Corporation" count: 1, found inside the VM: 1 : PASS
	lshw: Expected Display adapters: 1, total adapters found in VM: 1 : PASS
	nvidia-smi: Expected GPU count: 1, found inside the VM: 1 : PASS

[LISAv2 Test Results Summary]
Test Run On           : 06/04/2019 10:44:35
ARM Image Under Test  : OpenLogic : CentOS : 7.5 : Latest
Total Test Cases      : 1 (1 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:20

   ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes)
-------------------------------------------------------------------------------------------------------------------------------------------
    1 GPU                  NVIDIA-CUDA-DRIVER-VALIDATION                                                     PASS                   17
	Using nVidia driver : CUDA
	lsvmbus: Expected "PCI Express pass-through" count: 1, count inside the VM: 1 : PASS
	lspci: Expected "3D controller: NVIDIA Corporation" count: 1, found inside the VM: 1 : PASS
	lshw: Expected Display adapters: 1, total adapters found in VM: 1 : PASS
	nvidia-smi: Expected GPU count: 1, found inside the VM: 1 : PASS

@LiliDeng Please close @chvalean 's comment. And then let me close this PR.

@juhlee-microsoft Update code based on Chris's comments, do positive and negative testing, both pass.
For negative testing, I updated the target log name which not exist on VM.

authors: LiliDeng chvalean juhlee-microsoft


text:
DPDK: fix meson installation for SUSE, RHEL & CentOS distros.

[LISAv2 Test Results Summary]
Test Run On           : 08/24/2020 18:09:15
Total Test Cases      : 1 (1 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:16

   ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes)
-------------------------------------------------------------------------------------------------------------------------------------------
    1 DPDK                 VERIFY-DPDK-BUILD-AND-TESTPMD-TEST                                                PASS                15.57
      ARMImageName: SUSE SLES-15-sp1 gen1 latest, Networking: SRIOV, TestLocation: eastus2, Initial Kernel Version: 4.12.14-8.33-azure

Logs can be found at C:\LISAv2\HD33\TestResults\2020-08-24-11-08-31-0753
[LISAv2 Test Results Summary]
Test Run On           : 08/24/2020 18:39:46
ARM Image Under Test  : RedHat : RHEL : 7.5 : latest
Total Test Cases      : 1 (1 Passed, 0 Failed, 0 Aborted, 0 Skipped)
Total Time (dd:hh:mm) : 0:0:13

   ID TestArea             TestCaseName                                                                TestResult TestDuration(in minutes)
-------------------------------------------------------------------------------------------------------------------------------------------
    1 DPDK                 VERIFY-DPDK-COMPLIANCE                                                            PASS                10.06
      ARMImageName: RedHat RHEL 7.5 latest, Networking: SRIOV, TestLocation: eastus2, Initial Kernel Version: 3.10.0-862.43.1.el7.x86_64

Logs can be found at C:\LISAv2\UL37\TestResults\2020-08-24-11-39-03-5836

@abhimarathe Are you still working on this PR?

Closing this draft as #1010  will cover this PR.

source: gharchive/pull-request

authors: abhimarathe juhlee-microsoft

license: MIT

license_type: permissive

license_source: github-api


text:
你好，是不是缺少libsoundeditor.so文件？

java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.lkdont.soundeditor-7DUJ7y5rUosyCfhzC2gscg==/base.apk"],nativeLibraryDirectories=[/data/app/com.lkdont.soundeditor-7DUJ7y5rUosyCfhzC2gscg==/lib/arm64, /system/lib64, /system/product/lib64]]] couldn't find "libsoundeditor.so"

Process: com.lkdont.soundeditor, PID: 27965
java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/com.lkdont.soundeditor-7DUJ7y5rUosyCfhzC2gscg==/base.apk"],nativeLibraryDirectories=[/data/app/com.lkdont.soundeditor-7DUJ7y5rUosyCfhzC2gscg==/lib/arm64, /system/lib64, /system/product/lib64]]] couldn't find "libsoundeditor.so"
at java.lang.Runtime.loadLibrary0(Runtime.java:1067)
at java.lang.Runtime.loadLibrary0(Runtime.java:1007)
at java.lang.System.loadLibrary(System.java:1667)
at com.lkdont.soundeditor.MyApplication.onCreate(:17)
at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1197)
at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6660)
at android.app.ActivityThread.access$1700(ActivityThread.java:231)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1965)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7695)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:516)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:950)

重新编译了FFmpeg的库，并更新了工程，现在应该没问题了。

source: gharchive/issue

authors: LKDont wayuhan

repo: LKDont/SoundEditor


text:
Investigate LaTeX in readthedocs

We should see if it's possible to integrate LaTeX in readthedocs/sphinx. @samuelpmishLLNL has some theory documentation that would use this.

LaTeX is supported natively in Sphinx:
I added some text to one of our Sphinx pages
.. math::

   e^{i\pi} + 1 = 0

...and confirmed that it rendered:

Thanks for checking!

authors: jamiebramwell joshessman-llnl

repo: LLNL/serac


text:
Update install instructions and increment version - [merged]

In GitLab by @wtbarnes on Mar 31, 2020, 17:54
Merges update-install-instructions -> master
Now that aiapy is on pip, the primary install instructions should be for PyPI. This updates those in the README and docs.
This PR also increments the version number to 0.2

In GitLab by @wtbarnes on Mar 31, 2020, 18:17
mentioned in commit 3e17538701289e15f599fbbb2ffdd12154daecf2

In GitLab by @wtbarnes on Mar 31, 2020, 17:59
enabled an automatic merge when the pipeline for cfa8f1754064610ed4d11afac4eec0b03a313aa7 succeeds

In GitLab by @wtbarnes on Mar 31, 2020, 18:17
merged

repo: LM-SAL/aiapy


text:
Problem opening one of the sources

Source information
novelsparadise
Steps to reproduce
When I open this source it gives this result novelsparadise
It does not work and it asks me to open it in the application's browser, and when I open it it says that it is forbidden to open the site in this browser
Expected behavior
The site should open
Actual behavior
Could not reach site (403) try to open in webview.
When l use webview it gives me this result

LNReader version
V2.0.0
Android version
Android 10
Other details

Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 1.1.19.
[X] I have updated all installed extensions.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

duplicate of #1101

repo: LNReader/lnreader-plugins


text:
Never opens crashes immediately after

Steps to reproduce
Try to open app then it crashes immediately
Expected behavior
Click on app then it should open to your library.
Actual behavior
Tries to open crashes immediately
LNReader version
1.1.19
Android version
Android 14
Device
Samsung galaxy s21 ultra 5g
Other details
I didn't have any issues until this week. I even tried to Uninstall and re-install but it's thsame issue
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with a source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 2.0.0.
[X] I will fill out all of the requested information in this form.

If this issue is still happening, could you provide crash logs? You can use a Logcat Reader.

authors: DuckyDaNewb rajarsheechatterjee

repo: LNReader/lnreader


text:
change_detector.get_unstaged_mds() behaves out of expectation.

This function actually add all the untracked files to git.
I guess this is not the expected behavior.

Solved! thanks for your comment!


text:
move ccl_gsl and ccl_splines to be allocated once per cosmology

Right now these are global state. We should associate them with each cosmology. Then we can make them modifiable from python. We can also include the physical constants in here too.
See these comments:

https://github.com/LSSTDESC/CCL/pull/433#discussion_r206719385
https://github.com/LSSTDESC/CCL/pull/433#discussion_r206677013
https://github.com/LSSTDESC/CCL/pull/433#discussion_r206719627

Note that the last one is asking for a new integration parameter to be added to the structures above.

@rmjarvis for viz

This is a good change. One of the reasons that this was not done earlier was that not all functions take a cosmology object as an argument, which causes all kind of awkward constructs (e.g., the ccl_splines and ccl_gsl pointers you mention, the error handling system, etc).

Right. We can change that too

One problem I see with doing this is that these objects are completely cosmology-independent, so associating them with a cosmology object (or initializing them every time) seems ugly. I'd propose an alternative, which has an added advantage:
1- One creates a NumParams (or whatever) class at the python level that contains all the information about splining, error tolerances etc. Each of these is then associated to a corresponding ccl_splines and a ccl_gsl structure in C (or a merged version of both). This would allow people to fully tune any numerical parameter in CCL.
2- We add an optional parameter to the Cosmology constructor (e.g. num_params). This can be either a NumParams object or None. If None, then the a default C structure gets created and attached to this cosmology. Otherwise, the structures associated with the NumParams object just get linked to the ccl_cosmology object.
Thoughts?

Creating extra versions of these classes costs almost no time or work. I can see how it seems ugly, but the code to override the global settings with local ones has its own edge cases and issues.
It is a lot simpler and easier in my mind to simply copy in the defaults each time. As part of this, I am going to remove the params.ini files. Instead the defaults will be hard coded. People can change them after the cosmology object is made if they want to.

OK, as long as all parameters are easily accessible from python, I'm cool with it (just saying because sometimes this won't be transparent through the swig layer).

Right. Unfortunately we have to deal with the C code first. Then we can do the python code. This is all a lot more work than it has to be. We need to deprecate the C API.

authors: beckermr damonge tilmantroester

repo: LSSTDESC/CCL


text:
Document the pserv lower level interfaces

This will enable user-defined tables, queries, etc..

Done by adding docstrings throughout.

repo: LSSTDESC/pserv


text:
demo paths incorrect

there are a couple minor problems with paths in the goldenspike.ipynb demo, should fix those for easy running by people trying to get started

closed by #8


text:
Set up CIT

We would like to make the notebooks useable outside the jupyterlab instance, for longevity and general usefulness. This ties in well with our CIT (continuuous integration and testing) aspirations, so here's an epic to get this going:

[x] Figure out how to unit/continuously test notebooks, preferably with Travis CI - this needs setting up sooner rather than later, so we can use it to check our tutorials as we go. #17 Deploy the notebook outputs in html format to a web gallery, so they can be printed out etc
[x] Make a first tutorial notebook to exercise DM Stack (and hence check that people are set up correctly). This could be “Hello Sky” (#13 ) or something else. This will be useful for:
[x] Extend CIT to include use of docker to recreate Stack v15 environment

This should have been closed by the messages in #62...

repo: LSSTScienceCollaborations/StackClub


text:
Removing unused code and reorganizing a bit, some minor bug fixes

A lot of cleaning up unused pieces from the 11ty boilerplate, along with consolidating page content into a single area (/pages)
Fix for favicon not showing up
Fix for form labels not appearing on the "join us" form
Adding the site name to the title (e.g. "Join Us - La Murga de Austin" instead of just "Join Us")
Minor content formatting updates to some of the lyrics (adding in some missing accents, etc.)
Updated the root README

👷 Deploy Preview for gracious-mcclintock-aa8c1f processing.

Name
Link

🔨 Latest commit
700635941118b4583b69692a061e66ab3533c069

🔍 Latest deploy log
https://app.netlify.com/sites/gracious-mcclintock-aa8c1f/deploys/62acb6d95d55b20009efade1

authors: SpareNichols mateoclarke


text:
Scene and section folds

Thanks so much for enabling Fountain support on Zed!
One feature that would be nice is support for folding the script based on scenes, sections, etc.
Here is the feature on VSCode, for example, where sections, and scenes, can be recursively folded,

Currently, zed-fountain only supports folds on header fields,

Cheers!

I looked into it, and it looks like Zed does this automatically based on indentation! I didn't manage to find a way to enable folding based on the document structure instead...

Thanks for checking @LaPingvino! Strange findings.  Sure, I'll take a look on my end too. Cheers.

authors: LaPingvino gabrielmontagne

repo: LaPingvino/zed-fountain


text:
Issue 47330: quotation marks in JMX-exposed objects breaks datadog's …

…jmxfetch
Rationale
Developers may include problematic characters in cache names and other objects that are exposed via JMX
Changes

Replace potentially problematic characters

This looks fine, but what's the downside of unconditionally calling ObjectName.quote()? It seems like that would make the strings legal while preserving their contents.

This looks fine, but what's the downside of unconditionally calling ObjectName.quote()? It seems like that would make the strings legal while preserving their contents.

That would be fine if I had a convenient way to test it, as I'm more confident that the underscores will work than the quoted values, since I can't find much in the way of what will be acceptable.

authors: labkey-adam labkey-jeckels

repo: LabKey/platform


text:
feat(Redis Memory storage): Caching module with redis and memory stor…

BREAKING CHANGE: Simple and extensible caching module with redis and memory storage and supporting decorators.
This caches function response using the given options. Works with different strategies and storages. Uses all arguments to build an unique key.

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: JamilOmar chandgi

repo: LabShare/services-cache

license: mit

license_source: bigquery


text:
Availability of "beta" for models with distal outcome

Hi,
Is it possible to obtain parameters in the form of logistic regression when predicting a binary (or categorical) distal outcome? It appears that the "beta" parameters are not available for models with a distal outcome. If not, is there an alternative approach to extract these parameters?
Here's an example using a binary distal outcome:
import pandas as pd
import numpy as np
from stepmix.stepmix import StepMix
from sklearn.datasets import load_iris
from stepmix.utils import identify_coef

data, target = load_iris(return_X_y=True, as_frame=True)

for c in data:
  c_binary = c.replace("cm", "binary")
  data[c_binary] = pd.qcut(data[c], q=2).cat.codes

X = pd.DataFrame(data, columns=['sepal width (binary)',
                                        'petal length (binary)',
                                        'petal width (binary)'])

sepal_length_Binary = data['sepal length (binary)']

model = StepMix(n_components=3,
                measurement='binary',
                structural='binary',
                n_steps=3,
                random_state=123)
model.fit(X, sepal_length_Binary)

model.get_parameters()['structural']['beta']

The code runs without any errors, but when I try to access the "beta" parameters, it returns an empty result.
Thank you!

Yes. The key to use is "pis" (model.get_parameters()['structural']['pis']). Remember you can always look at the available keys of a dictionary when in doubt (model.get_parameters()['structural'].keys()).

You can also refer to this tutorial.

In case you are looking for the betas as in the "linear coefficients", please note that they are exclusive to the covariate model or more generally logistic regressions. Binary and categorical models are not regression models.
Binary and categorical parameters ("pis") instead represent conditional probabilities. This is the standard way of parametrizing Bernoulli or Multinoulli random variables. I agree the documentation regarding this could be clearer. It is explained at page 22 of the StepMix preprint, if that can help.

In the binary case for example, pis is a K x M matrix representing conditional probabilities over K latent classes and M possible outcomes.
pis[k, m] gives you the probability that variable m = 1 given that your latent class is k.

Thank you for all the information.
Therefore, I will rephrase my question as follows:
Is it possible to transform the conditional probabilities (model.get_parameters()['structural']['pis']) obtained with StepMix into coefficients of a "classic" logistic regression?
To clarify, I aim to compare the results of an LCA model with binary distal outcome (presented in a published article) with the results obtained using StepMix. The authors used a "naive" three-step approach:

They presented an LCA model obtained with another software/package (step-1).

Then, they created a new variable by recording the class membership without considering the uncertainty of class assignment (step-2).

Using the newly created variable, they predicted a binary distal outcome through a logistic regression (step-3) and presented a table of the logistic regression results (coefficients, p-values, etc.).

Therefore, is it possible to transform the conditional probabilities into coefficients to compare the coefficients from this article with the coefficients obtained using the different approaches offered by StepMix ("naive" three-step, two-step, etc.)?
In other words, I wish to obtain the following equation (with the first class as the reference category):
log(p/1-p) = β0 + (β1∗class2) + (β2∗class3) + ... + (βk∗classk)
Thank you for your time and assistance!

The 3-step approach you're describing here is not currently implemented in StepMix.
I don't know of a straightforward way to convert binary mixture parameters to logistic regression parameters. @robinlegault any idea?

You could always do this yourself however, using StepMix and some logistic regression estimator. Let me give you an example.

I think this does what you are describing.
import pandas as pd
from stepmix.stepmix import StepMix
from sklearn.linear_model import LogisticRegression
from sklearn.datasets import load_iris

data, target = load_iris(return_X_y=True, as_frame=True)

for c in data:
  c_binary = c.replace("cm", "binary")
  data[c_binary] = pd.qcut(data[c], q=2).cat.codes

X = pd.DataFrame(data, columns=['sepal width (binary)',
                                        'petal length (binary)',
                                        'petal width (binary)'])

distal_outcome = data['sepal length (binary)']

model = StepMix(n_components=3,
                measurement='binary',
                n_steps=3,
                random_state=123)

# Step 1
model.fit(X)

# Step 2
input = model.predict_proba(X)

# Step 3
distal_outcome_model = LogisticRegression(fit_intercept=True, random_state=123).fit(input, distal_outcome)
print(distal_outcome_model.coef_)

Thank you. It answers my question. I was trying to perform the analysis without using another package.

authors: FelixLaliberte sachaMorin

repo: Labo-Lacourse/stepmix


text:
joystick events stack up?

investigate if we can make it more responsive

the jog queue is cleared on the joystick going idle (when not previously). This is analogous to how we handle keyboard events (jog clear queue on key release)

repo: Labsmore/pyuscope


text:
Inflated Times Imported Compared to HLTB Website

Describe the bug
At some point recently, this add-on has started importing times that are completely wrong compared to the HLTB website. And not "slightly" wrong, but stuff like a game that the website says takes 52 hours for the main story gets imported as 200 hours.
To Reproduce
Use externsion normally. For a seemingly random selection of games, one or more of the times will be vastly inflated. I have confirmed this to be the case for Trails through Daybreak (Main reports as 200h), Eiyuden Chronicle (Main + Sides reports as 200h) and Monochrome Mobius (Main reports as 271h).
Expected behavior
The times would match the data on HLTB.
Screenshots

Extensions log
extensions.log

I have the same issue. Except it can also under report the time, for example it reports that Call of Cthulhu main story takes 21 minutes

but the real time is 8 hours actually

The same thing for Control

Just to add +1 for this odd bug, I imagine something has changed in the HLTB side, since the plugin was working beautifully a few days ago.
To add info: this happens to games that are newly added to the collection, as well as to games which had HLTB times registered inside playnite. I mean, if you "refresh" the HLTB data on old games, the new incorrect times replace the old correct ones.

Update: now, instead of crazy times,  I am getting the infamous "Vale cannot be null. Parameter name: collection" error (same one I was getting about 1 week ago). Sounds like the HLTB site is changing something, so I guess we just sit tight and wait?

Can you try this?
playnite-howlongtobeat-plugin_3_3.zip

Extracted the archive content to the plugin's folder and it works fine

Can you try this? playnite-howlongtobeat-plugin_3_3.zip

Oh, baby! Yes, this fixed all the bugs I have been seeing (both for incorrect times and "Cannont be null")! Thank you!

I can also confirm that the test version fixed it for me.

yes it also fixed my issue with the "Cannot be null" Thank you!


text:
RetroAchievements heavily reliant on filetypes? (no .7z support for SNES games)

I have my SNES games in 7z files because it helps to save on space. These 7z files can be easily read by emulators like RetroArch no problem.
However, it seems that this is stopping SuccessStory from detecting these games. If a SNES game is linked to a .7z file, SS won't find achievements. But if the exact same SNES game is pointing to an .sfc file instead, SS detects it easily. Strangely enough i've had no problem with SS detecting my Sega Genesis games, which are also in the form of .7z files.
I really don't understand why this would affect SS's functionality. If a game is named "Mario Paint" and has the platform "Nintendo SNES", surely that should be enough for SS to detect it regardless of the state of the file?
I'm also starting to wonder if this may be related to the reason why my PSP games (.iso) are never detected by SS either.

Normally the name of the game and the platform are sufficient.
Can you post your extension.log after to try to refresh achievements for game with the issue?

Ok, for some reason I can't attach my extension.log, so here's a copy paste of what happens when I try to refresh a SNES game that uses a 7z file.
18-02 21:29:17.932|INFO |SuccessStory#PluginDatabaseObject4:RefreshNoLoader(Super Mario World - 0a888d7c-402d-4e1f-866c-4264ea5c3a27)
18-02 21:29:17.932|WARN |SuccessStory#PluginDatabaseObject4:Used SuccessStory.Clients.RetroAchievements for Super Mario World - 0a888d7c-402d-4e1f-866c-4264ea5c3a27 18-02 21:29:18.258|WARN |SuccessStory#GenericAchievements:No game find for Super Mario World with 18265da8b39d145fea99680d347c9521 in PlatformType.All 18-02 21:29:18.269|WARN |SuccessStory#GenericAchievements:No game find for Super Mario World with ef43b8ef2b0bad0f0b8cee7c220cd2df in PlatformType.SNES 18-02 21:29:18.294|WARN |SuccessStory#GenericAchievements:No game find for Super Mario World with 18265da8b39d145fea99680d347c9521 in PlatformType.SNES 18-02 21:29:18.308|WARN |SuccessStory#GenericAchievements:No game find for Super Mario World with cb57c0e998748f3b542e9e0d5faacd7d in PlatformType.Sega_CD_Saturn 18-02 21:29:18.335|WARN |SuccessStory#GenericAchievements:No game find for Super Mario World with 18265da8b39d145fea99680d347c9521 in PlatformType.SNES 18-02 21:29:18.335|WARN |SuccessStory#GenericAchievements:No game find for Super Mario World with b31e1500a2b3ccf2268394fd7d158787 in PlatformType.Sega_CD_Saturn 18-02 21:29:18.348|WARN |SuccessStory#GenericAchievements:No console find for Super Mario World with Nintendo SNES 18-02 21:29:18.348|WARN |SuccessStory#GenericAchievements:No game find for Super Mario World with Nintendo SNES in 0 18-02 21:29:18.348|INFO |SuccessStory#PluginDatabaseObject4:No achievements find for Super Mario World - 0a888d7c-402d-4e1f-866c-4264ea5c3a27`

Also, just in case this is somehow related, this is what happens when I try to get achievements for my PSP games.

19-02 20:57:02.591|INFO |SuccessStory#PluginDatabaseObject4:RefreshNoLoader(Pangya: Fantasy Golf - 8d58f2d9-3812-40a2-b869-a8be2ce9638f) 19-02 20:57:02.591|WARN |SuccessStory#PluginDatabaseObject4:Used SuccessStory.Clients.RetroAchievements for Pangya: Fantasy Golf - 8d58f2d9-3812-40a2-b869-a8be2ce9638f
19-02 20:57:02.630|WARN |SuccessStory#GenericAchievements:Hash impossible - The file is too long - C:\Users\Nathan\Games\PSP\Pangya - Fantasy Golf (USA).iso
19-02 20:57:02.637|WARN |SuccessStory#GenericAchievements:No console find for Pangya: Fantasy Golf with Sony PlayStation Portable
19-02 20:57:02.637|WARN |SuccessStory#GenericAchievements:No game find for Pangya: Fantasy Golf with Sony PlayStation Portable in 0
19-02 20:57:02.637|INFO |SuccessStory#PluginDatabaseObject`4:No achievements find for Pangya: Fantasy Golf - 8d58f2d9-3812-40a2-b869-a8be2ce9638f


text:
Update also installed games when library updates

It would be nice if the "Automatically update data when library is updated" functionality also updated all installed games, rather than only newly added games. Whether optionally (another checkbox) or not, but likely better optionally.
Why? Currently you either seem to have to play current games through Playnite (game end event) or update the achievements manually through menu. Personally I often launch games directly through other means, for various reasons, so games don't get updated automatically. I only have around 20 games installed at a time so I don't mind Playnite checking each time for changes.

Yes please, having an "update all" option would be GREAT
I can't imagine having to Right-Click > SuccessStory > Refresh data for every single menu item... it's just too much, even though I want to see ALL achievements, all of them...

You have in the main menu of the plugin an option to download data with many options.

Yes. The point of this issue is that people don't want to click that manually but rather have an option to update with each library update like bunch of other plugins do.

#451


text:
entity_visible events are empty

Hello.
According to documentation, there is an event called entity_visible https://cs2.poggu.me/dumped-data/game-events/#entity_visible
PRoblem is, for every demo I parse there are no such events.
Should I enable some console option to store those events, or it is a bug?

Many of the event listed here are not part of the demos. I'm not sure it is even possible to enable them trough any setting?
Anyhow if you are looking for visibility between players you can do something like this:
from demoparser2 import DemoParser

parser = DemoParser("path_to_demo.dem")
ticks_df = parser.parse_ticks(["approximate_spotted_by"])

The event would most likely just listen to changes in this value. But it is not perfect and the event would likely not be any better. Exactly determining when a player spots another is a very complicated process and not something the game keeps track off in some kind of even/variable as far as I know.

Closing for now as I don't think there is much that can be done

authors: LaihoE bukson

repo: LaihoE/demoparser


text:
Installed cypress as a devdepencies, added simple tests with cypress …

…for visiting our app url and localhost app under form_test.js file
Description
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Change Status

[x] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[x] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[x] Test A
[x] Test B

Checklist

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts

good effort but we are actually going to be using jest for testing

repo: Lambda-School-Labs/Studium-FE


text:
Light / Dark Mode

App is set for light mode, needs help for dark mode.

DO NOT use pure black (#00000) for dark mode. Use a softer black (like a dark charcoal) so it is easier on the eyes.

Light Mode color palette:
Trinidad Orange #D44808
static let trinidadOrange = UIColor(red: 212.0/255.0, green: 72.0/255.0, blue: 8.0/255.0, alpha: 1.0)
Tundra #404040
static let tundra = UIColor(red: 64.0/255.0, green: 64.0/255.0, blue: 64.0/255.0, alpha: 1.0)
Dove Gray #737373
static let doveGray = UIColor(red: 115.0/255.0, green: 115.0/255.0, blue: 115.0/255.0, alpha: 1.0)
Alto Gray #D9D9D9
static let altoGray = UIColor(red: 217.0/255.0, green: 217.0/255.0, blue: 217.0/255.0, alpha: 1.0)
Cinnabar Red #E33434 (Error state only)
static let cinnabarRed = UIColor(red: 208.0/255.0, green: 68.0/255.0, blue: 61.0/255.0, alpha: 1.0)

repo: Lambda-School-Labs/betterreads-ios


text:
Feature/member reaction search

This feature adds the search functions of member reactions, where one can search for member reactions by club activities and/or members.
Tested with postman

This implementation uses native SQL query on DB level instead of retrieving everything from the DB and filtering a Java list due to my belief that it would have speed benefit when the table gets large.
I have no proof of whether this is actually the case even though I feel that it could. All in all, this might introduces a minor difficulty in maintainability for the next team when handling this.


text:
Feature/Add a weighted city score route

Files Modified:

app/ml.py
app/config.py
app/helpers.py

Details:

Add a config.py file that reads environment variables if present in order to configure a default set of city score weights -> used to generate a weighted average of the underlying city quality of life scores
Add a route that returns an overall city score given the user's selected city and personal weighting
Add helper functions to support the city score route handler and abstract code

@PalmerTurley34 hey... there's a lot going in this PR.  If you think I should break this up, let me know. Thanks for taking a look

Closing this pull request and will reopen a new one

repo: Lambda-School-Labs/cityspire-d-ds


text:
Axios auth

Description
Created an axiosAuth helper function and refactored endpoint URL's to point to staging.
Keep in mind that the Property components will comeback with empty arrays (no properties yet, need to integrate my create property form to dashboard) and the Property endpoints require a valid token to process a request!
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[ ] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] There are no merge conflicts

fixed anythony's placeholder marketing content (removed whitespace and scroll bars, still might need adjustments such as switching from color codes to color variables)
adjusted routes.

authors: IXLives techturnip

repo: Lambda-School-Labs/property-manager-fe


text:
Minor fixes updates

Description
Added queries to courses for filtering and removed subsection from table and seeds
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Change Status

[ ] Complete, tested, ready to review and merge
[x] Complete, but not tested (may need new tests)
[ ] Incomplete/work-in-progress, PR is for discussion/feedback

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] There are no merge conflicts

 Tweak Student Endpoint to match new migrations

repo: Lambda-School-Labs/speak-out-be


text:
🛑 Billing is down

In 2019f95, Billing (https://whmcs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Billing is back up in c6c670c.

repo: LampyXd/Status-Page


text:
Feedback form at "Details" and "Language profile"

Create a prominent link to the feedback form at bottom of the “Details” and “Language profile” views using a style button or prominent link element, and add basic supplemental text if needed.
In terms of the latter, some disclaimer like the following would be ideal:
"Note that [Lang Name] may be spoken throughout the New York area — this is just one significant location. Submit your feedback." (where the second bit could be in button form?)

"Note that [Lang Name] may be spoken throughout the New York area — this is just one significant location. Submit your feedback."

does this still apply to Lang Profile or only Details?
for that matter, where should it be included besides Details? i could see including it in Lang Profile at the /Explore/Something/Something/LangName but not at /Explore/Language/LangName.
if we ARE including it at more than just Details (which is how i worded in SOW but maybe it's not applicable), let me know the wording for non-Details supplemental text.
if it matters, keep in mind we'll likely have another Feedback Link sprinkle in the catch-all menu. so, as a user my vote would probably be only include it in Details with the supplemental wording, and then either exclude it from all other views, or put it most or all of them at the bottom, but w/more generic text than what we'd use for Details.

The question is how to sprinkle generously without overloading, and I’m open to different options. The supplemental text may be needed only for Details and maybe just ”Submit your feedback” will be sufficient for Lang Profile

On Mar 21, 2021, at 8:31 PM, Jason Lampel @.***> wrote:
"Note that [Lang Name] may be spoken throughout the New York area — this is just one significant location. Submit your feedback."
does this still apply to Lang Profile or only Details?
for that matter, where should it be included besides Details? i could see including it in Lang Profile at the /Explore/Something/Something/LangName but not at /Explore/Language/LangName.
if we ARE including it at more than just Details (which is how i worded in SOW but maybe it's not applicable), let me know the wording for non-Details supplemental text.
if it matters, keep in mind we'll likely have another Feedback Link sprinkle in the catch-all menu. so, as a user my vote would probably be only include it in Details with the supplemental wording, and then either exclude it from all other views, or put it most or all of them at the bottom, but w/more generic text than what we'd use for Details.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Language-Mapping/language-map/issues/205#issuecomment-803690995, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMNKB5GO34J2VLIGU3UQGT3TE2FU5ANCNFSM4ZRMSUTQ.

ok. i think the "outlined" button variant is pretty non-overloady, so we'll start there.
clarify please, for feedback link btn:

Details (YES)
Lang profile: only non-/Explore/Language/LangName, or that one too?

popups link
Related: SOW says:

Map popups: include a feedback link at the bottom of all popups if it looks relevant in this context.

i think we (or I) just kinda threw that one in there, but with all the other sprinkles, the popup sounds overloady to me. not to mention, since we're moving forward w/the "more routes and nesting panelage" approach, it's less necessary to cram things into the lil' popups, so can we scrap that SOW item (2.3.2)?
keep in mind verrrrrry few people are going to provide feedback no matter how many sprinkles you put on this UI donut. so i think:
best use of time + less potential annoyance to users = no feedback link in popups.

What was the thinking for not including at /Explore/Language/LangName? Mind working a little slow at the moment, would probably just say Details and Lang Profile both. But I think I agree on the pop-up, we can scrap that. I know we won’t necessarily get tons of feedback, but providing the option is important adn the disclaimer is important too

On Mar 21, 2021, at 9:04 PM, Jason Lampel @.***> wrote:
ok. i think the "outlined" button variant is pretty non-overloady, so we'll start there.
clarify please, for feedback link btn:
Details (YES)
Lang profile: only non-/Explore/Language/LangName, or that one too?
popups link
Related: SOW says:
Map popups: include a feedback link at the bottom of all popups if it looks relevant in this context.
i think we (or I) just kinda threw that one in there, but with all the other sprinkles, the popup sounds overloady to me. not to mention, since we're moving forward w/the "more routes and nesting panelage" approach, it's less necessary to cram things into the lil' popups, so can we scrap that SOW item (2.3.2)?
keep in mind verrrrrry few people are going to provide feedback no matter how many sprinkles you put on this UI donut. so i think:
best use of time + less potential annoyance to users = no feedback link in popups.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Language-Mapping/language-map/issues/205#issuecomment-803698751, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMNKB5HRRB44BOJVAJCH2A3TE2JSTANCNFSM4ZRMSUTQ.

What was the thinking for not including at /Explore/Language/LangName

i think i was just hung up on the specific supplemental text, but since we're not using that for either of the Lang Profiles now, it makes sense to include in both.

sufficient in details?

or subtle outline? i like this better but not married to either and am open non-buttony too (like no fill or outline or shadow, just the text and icon):

and here it is on lang profile:

FYI it opens to a modal from both details and lang profile. couldn't get scroll-to-the-form to work inside that panel on mobile. so modal = nuclear easy. it's the same modal we have now in prod.
i left it as-is in /Info/Feedback though. it's totally fine on its own in there and there's not as compelling a reason to stay in the same view (/Info) as there is in details or lang profile. modal also seems overkill for a feedback form when you're already coming from an Info-like view.
any wording or style changes to any of the scenarios, let me know. would prefer not to de-panel-view the current in-panel /Info/Feedback form is all.

Need to change one word here, my bad, to cover sign language(s) and liturgical ones:
"may be used” instead of “may be spoken"

On Mar 27, 2021, at 12:07 AM, Jason Lampel @.***> wrote:
Closed #205 https://github.com/Language-Mapping/language-map/issues/205 via #211 https://github.com/Language-Mapping/language-map/pull/211.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Language-Mapping/language-map/issues/205#event-4516642870, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMNKB5BBH7FFHKI6WT3HZKTTFVKZRANCNFSM4ZRMSUTQ.

your baby now! https://github.com/Language-Mapping/language-map/pull/213
before you ask for dynamic text on this one (the language-specific reference in details), please keep in mind that i've just added the ability for you to control just about any bit of text in the UI now. we've lost many hours on the back and forth of these little things, or days over the course of the project if we're being honest, so i hope that what i implemented tonight will heal that painful process and save us both a lot of time and hassle by giving you 100% control over these contentious bits of text that are so prone to change.
i don't think we're going to lose/confuse any users with something generic like this:

...as opposed to specifying the language. so unless anyone mentions otherwise, let's keep it generic and call it a fair trade for the text control you now have for the 14 pieces of UI i added tonight, and whatever other ones you want in the next week.  super easy to set up on my end now!

authors: abettermap rperlin-ela

repo: Language-Mapping/language-map


text:
Bug on enum field

Hello, there's a bug when i create a migration like this:
$table->enum('status', ['In attesa', 'Aperto', 'Chiuso'])->default('In attesa');

and in my CRUD controller there's
$this->crud->addField([
    'name' => 'status',
    'label' => 'Stato del ticket:*',
    'type' => 'enum'
], 'both');

On my DOM I see something like this that seems fine.

But when I save, it seems that the indexes are broken (they should be +1), example:
If I save selecting "In attesa", then it saves "In attesa" (correct behaviour).
If I save selecting "Aperto", then it saves "In attesa" (wrong behaviour).
If I save selecting "Chiuso", then it saves "Aperto" (wrong behaviour).

Hi @EmanueleCoppola ,
It's very weird how your HTML looks. As far as I know, the "value" should be exactly like in the DB, not 0, 1, 2. I've just tested it and that's how it works for me:

What version of MySQL & PHP are you on? What version of Backpack\CRUD?

My PHP version is 7.1.5 and my MySQL 5.6.34-log - MySQL Community Server (GPL). And my backpack version is "backpack/crud": "^3.2".

@tabacitu Have you considered that the values in the DB are actually 0, 1, 2 etc?
My guess is getPossibleEnumValues is returning something weird:
https://github.com/Laravel-Backpack/CRUD/blob/0250f8dd23a4572c2cffa19e209e009b8c903943/src/CrudTrait.php#L17

@lloy0076 well from his migration I see they're not 0, 1, 2:
$table->enum('status', ['In attesa', 'Aperto', 'Chiuso'])->default('In attesa');

Which is what makes it weird :-)
@EmanueleCoppola I'm afraid I'm out of ideas here. Have you been able to debug this by now? I guess there's nothing else to do but to go through the enum blade file, up the functions, until you discover why it outputs 0 1 2 instead of the actual values... Sorry I can't be of more help...
Feel free to reopen this if you think it's Backpack issue - just tested it again and ENUMs work fine for me...

authors: EmanueleCoppola lloy0076 tabacitu

repo: Laravel-Backpack/CRUD


text:
Sidebar doesn't open

Hi everybody
So i've just managed to get backpack working with the admin flow running
Now for some reason after logging in the dashboard seems stuck
The logout but doesn't work, the sidebar doesn't open
Trying to track any JS or CSS errors but nothing on console
I've run the following commands to publish the assets
php artisan vendor:publish --provider="Backpack\CRUD\BackpackServiceProvider" --tag=public --force
npm -i
npm run dev

Here's what my version output looks like
`### PHP VERSION:
PHP 7.3.19 (cli) (built: Jul  4 2020 20:25:10) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.19, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.19, Copyright (c) 1999-2018, by Zend Technologies
LARAVEL VERSION:
v7.22.4@30e851a2b3a2af73fba0b7f4fa22b04260db98e7
BACKPACK VERSION:
4.1.15@6c751de946a9c8511dd32eb7bfa3ca6a568849f5
`

##Update
So looking at my checkIfAdmin even after login
backpack_auth()->guest() resolves to true
What could be the problem?

@AlexandreCarvalhoDeMelo - from your video I think your problem is with the login itself, rather than the sidebar. I noticed even after reaching the dashboard page, your top-right corner says "Login", not "Logout". That means you're not actually logged in. Which is very weird, because you normally shouldn't even be able to see the dashboard without being logged in (obviously).
I'm 99.9% sure this is not a bug in Backpack, but an error in implementation, so I'm going to close this. We're trying to get the issue count down.
But feel free to reply below and I'll try to help out, time permitting.
First thing I'd check would be the parts of the authentication you customized. Have you changed config/backpack/base.php in any way? Middleware, guard, etc? Have you changed the backpack auth routes? Something in those changes must have triggered this weird behaviour.
Cheers!

authors: AlexandreCarvalhoDeMelo tabacitu


text:
V6 Uploaders - deleteWhenEntryIsDeleted not working

Discussed in https://github.com/Laravel-Backpack/community-forum/discussions/586

Originally posted by christmex July 26, 2023
Hi guys, I have a problem with V6 uploaders, can you guys help me out?
What do I want?
When I delete the model/entry it will also delete the picture file
What did I do?
reading the documentation and trying it, also I already solved it but with v5 ways
What is actually happening?
It did not delete the picture file when I delete the model/entry
Here's my backpack version
### PHP VERSION:
PHP 8.1.10 (cli) (built: Aug 30 2022 18:05:49) (ZTS Visual C++ 2019 x64)
Copyright (c) The PHP Group
Zend Engine v4.1.10, Copyright (c) Zend Technologies

### LARAVEL VERSION:
10.16.1.0

### BACKPACK PACKAGE VERSIONS:
backpack/basset: 1.0.2
backpack/crud: 6.0.6
backpack/generators: v4.0.2
backpack/theme-tabler: 1.0.6

Here's my controller
        CRUD::field('member_profile_picture')
            ->type('upload')
            ->withFiles([
                'disk' => 'public', // the disk where file will be stored
                'path' => '/uploads/member/', // the path inside the disk where file will be stored
        ]);

I already solve it with backpack v5 ways, something like
//inside my related model
public static function boot()
    {
        parent::boot();
        static::deleting(function($obj) {
            if($obj->member_profile_picture){
                \Storage::disk('public')->delete($obj->member_profile_picture);
            }
        });
    }

Did I miss something? let me know, thank you 🙏.

Thank you @pxpm

authors: christmex pxpm


text:
I changed my github username

I'm retiring my old github username and switching to a new one for the new year.

the artist formerly known as dvkt

Wonderful, Chris! I'm glad you are using your full name here! Shall I change dvkt to Chris West on the website as well? :smiley_cat:
Btw what does xvxx stand for?

Shall I change dvkt to Chris West on the website as well? 😺

Sure!

Btw what does xvxx stand for?

It's an old childhood nickname - my grandma called me it when I was a baby, and I guess it just stuck!

It's an old childhood nickname - my grandma called me it when I was a baby, and I guess it just stuck!

Your grandma called you "ex vee ex ex"?
Now that your username has changed, shall I still contact you to the usual email address?

Well, she pronounced it "Peanut", but she spelled it xvxx. I'm not sure she ever learned to write properly. But anyway, yes, my regular email still works! I might be switching to ProtonMail in the future to de-Google myself further (I use GMAIL), but I will let you know and try to never break the old one.

authors: Lartu xvxx

repo: Lartu/ldpl


text:
clang doesn't really support -static on darwin

On macOS 10.14.1:
$ make
awk -f lib-to-string.awk ldpl_lib.cpp > ldpl_included_lib.cpp
c++ -g -c -Wall -std=gnu++11 -fpermissive -DVERSION='"2.0.7"'   -DSTANDARD=19         -DCOMPILEDATE='"Tue Mar 12 22:23:30 PDT 2019"' ldpl.cpp
c++ -g ldpl.o -o ldpl -static-libgcc -static-libstdc++
clang: error: unsupported option '-static-libgcc'
make: *** [all] Error 1

clang has a -static option, but using it fails with ld: library not found for -lcrt0.o.
From developer.apple.com.

Apple does not support statically linked binaries on Mac OS X. A statically linked binary assumes binary compatibility at the kernel system call interface, and we do not make any guarantees on that front. Rather, we strive to ensure binary compatibility in each dynamically linked system library and framework.

I removed the -static flags and built a binary that works on both my laptop and another mac. Not sure if there's a better flag or way to do it.

Hmm this is a problem. I don't have an intel era mac (I do have an old PPC one, that's why the PPC architecture is supported) so I did not try this with clang but with gcc. The thing is this: if you remove those flags, you will not be able to compile for Windows. If you keep them, you won't be able to compile for mac. I'd rather just add a comment saying something in the lines of "if you are using clang under macOS, remove this line" instead of removing it altogether.
What do you think?

I added a check for Darwin in the Makefile, can you see if it works for you? I tested it on Arch Linux and it built using the flags.

Sorry, I don't see the change. Did you push it? (you can paste it here if you want and I can paste it in my makefile)

It's in the original commit on this PR, if it's not showing up for you I can push a new branch: c7ce1d9225915dc5da87811bf560eb6c393cad9c
Here's the raw diff if you want to test it by hand:
--- a/src/makefile
+++ b/src/makefile
@@ -15,7 +15,9 @@ OBJS = ldpl.o
 SOURCE = ldpl.cpp
 OUT = ldpl
 FLAGS = -g -c -Wall -std=gnu++11 -fpermissive -DVERSION=$(VERSION) -DSTANDARD=$(LDPLSTD) -DCOMPILEDATE='"$(shell date)"'
-LFLAGS = -static-libgcc -static-libstdc++
+ifneq ($(shell uname -s),Darwin)
+	LFLAGS = -static-libgcc -static-libstdc++
+endif

 all: $(OBJS)
 	$(CXX) -g $(OBJS) -o $(OUT) $(LFLAGS)

Yes, sorry, it was like that all along! I didn't see it, sorry. I'll try it right away.

Great! Thank you very much for your contributions!

authors: Lartu dvkt


text:
Feature to add budget analytics

Feature to add budget analytics

: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:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
see 1 file with indirect coverage changes

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles

authors: LavanyaMiddha codecov-commenter


text:
Please, add Photomath icon!

com.microblink.photomath
Add an icon for Photomath, thanks!

com.microblink.photomath

Hello! Weʼre switching to a new system for icon requests in order to be able to better manage them. From now on, icon requests can be submitted here: https://forms.gle/Fx8vZAiWdW1Tyjo57. If your icon request hasnʼt yet been fulfiled, it has been copied to our new icon request database, meaning no action is required. Consequently, this issue will be closed.

authors: CatInTheVoid ghost lawnchairci

repo: LawnchairLauncher/lawnicons


text:
multiple different client offset_encodings detected for buffer

When opening a cpp file, after I entered insert mode once, I get spammed with the message above on every move I get spammed by this warning, and I'm not sure where it originates from and how to fix it.
I've found https://github.com/jose-elias-alvarez/null-ls.nvim/issues/428 but I'm not sure how to set the encoding now from within LazyVim.
NVIM v0.9.0-dev-884+gadae075fc
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by root@mbp.zhinst.com

Features: +acl +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/share/nvim"

Run :checkhealth for more info

There seems to be issues when doing a healthcheck. I'm closing it for now and trying to clean that up first.

==============================================================================
gitsigns: require("gitsigns.health").check()

- OK git version 2.39.1

==============================================================================
lazy: require("lazy.health").check()

lazy.nvim ~
- OK Git installed
- OK no existing packages found by other package managers
- OK packer_compiled.lua not found
- WARNING {neo-tree.nvim}: unknown key <deactivate>

==============================================================================
lazyvim: require("lazyvim.health").check()

LazyVim ~
- OK Using Neovim >= 0.8.0
- OK `git` is installed
- OK `rg` is installed
- OK `fd` is installed
- WARNING `lazygit` is not installed

==============================================================================
lsp: health#lsp#check

- ERROR Failed to run healthcheck for "lsp" plugin. Exception:
function health#check[25]..health#lsp#check, line 2
Vim(lua):E5108: Error executing lua [string ":lua"]:1: attempt to call field 'check_health' (a nil value)
         stack traceback:
           [string ":lua"]:1: in main chunk

            ==============================================================================
            man: require("man.health").check()

            - ERROR plugin/man.vim detected. Please delete /usr/local/share/nvim/runtime/plugin/man.vim
            - ERROR autoload/man.vim detected. Please delete /usr/local/share/nvim/runtime/autoload/man.vim

            ==============================================================================
            mason: require("mason.health").check()

            mason.nvim report ~
            - OK neovim version >= 0.7.0
            - OK **Go**: `go version go1.19.5 darwin/arm64`
            - OK **cargo**: `cargo 1.64.0 (387270bc7 2022-09-16)`
            - WARNING **luarocks**: not available
            - OK **Ruby**: `ruby 2.6.10p210 (2022-04-12 revision 67958) [universal.arm64e-darwin22]`
            - OK **RubyGem**: `3.0.3.1`
            - WARNING **Composer**: not available
            - OK **PHP**: `PHP 8.2.1 (cli) (built: Jan 12 2023 03:48:24) (NTS)`
            - OK **npm**: `9.3.1`
            - OK **node**: `v19.5.0`
            - OK **python3**: `Python 3.11.0`
            - OK **pip3**: `pip 22.3 from /Users/philippg/venvs/zi/lib/python3.11/site-packages/pip (python 3.11)`
            - OK **javac**: `javac 16.0.1`
            - OK **java**: `openjdk version "16.0.1" 2021-04-20`
            - WARNING **julia**: not available
            - OK **wget**: `GNU Wget 1.21.3 built on darwin22.1.0.`
            - OK **curl**: `curl 7.85.0 (x86_64-apple-darwin22.0) libcurl/7.85.0 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.11 nghttp2/1.47.0`
            - OK **gzip**: `Apple gzip 400`
            - OK **tar**: `bsdtar 3.5.3 - libarchive 3.5.3 zlib/1.2.11 liblzma/5.0.5 bz2lib/1.0.8 `
            - WARNING **pwsh**: not available
            - OK **bash**: `GNU bash, version 5.2.15(1)-release (aarch64-apple-darwin22.1.0)`
            - OK **sh**: `Ok`
            - OK GitHub API rate limit. Used: 4. Remaining: 56. Limit: 60. Reset: Tue Feb  7 10:51:28 2023.

            ==============================================================================
            neoconf: require("neoconf.health").check()

            neoconf.nvim ~
            - OK **treesitter-nvim** is installed
            - OK **TreeSitter jsonc** parser is installed
            - OK **neodev.nvim** is installed
            - OK **lspconfig** is installed
            - OK **lspconfig jsonls** is installed
            - OK **lspconfig sumneko_lua** is installed

            ==============================================================================
            noice: require("noice.health").check()

            noice.nvim ~
            - OK **Neovim** >= 0.8.0
            - OK Not running inside **Neovide**
            - OK You're using a GUI that should work ok
            - OK **vim.go.lazyredraw** is not enabled
            - OK **nvim-notify** is installed
            - OK **TreeSitter vim** parser is installed
            - OK **TreeSitter regex** parser is installed
            - OK **TreeSitter lua** parser is installed
            - OK **TreeSitter bash** parser is installed
            - OK **TreeSitter markdown** parser is installed
            - OK **TreeSitter markdown_inline** parser is installed
            - OK `vim.notify` is set to **Noice**
            - OK `vim.lsp.handlers["textDocument/hover"]` is set to **Noice**
            - OK `vim.lsp.handlers["textDocument/signatureHelp"]` is set to **Noice**
            - OK `vim.lsp.handlers["window/showMessage"]` is set to **Noice**
            - OK `vim.lsp.util.convert_input_to_markdown_lines` is set to **Noice**
            - OK `vim.lsp.util.stylize_markdown` is set to **Noice**
            - WARNING `cmp.entry.get_documentation` is not configured to be handled by **Noice**

            ==============================================================================
            null-ls: require("null-ls.health").check()

            - OK stylua: the command "stylua" is executable.
            - OK flake8: the command "flake8" is executable.

            ==============================================================================
            nvim: require("nvim.health").check()

            Configuration ~
            - OK no issues found

            Runtime ~
            - $VIMRUNTIME: /usr/local/share/nvim/runtime
            - ERROR $VIMRUNTIME has files from an old installation (this can cause weird behavior):
              /usr/local/share/nvim/runtime/plugin/man.vim
               /usr/local/share/nvim/runtime/autoload/man.vim
               /usr/local/share/nvim/runtime/scripts.vim
               - ADVICE:
               - Delete $VIMRUNTIME (or uninstall Nvim), then reinstall Nvim.

               Performance ~
               - OK Build type: Release

               Remote Plugins ~
               - OK Up to date

               terminal ~
               - key_backspace (kbs) terminfo entry: `key_backspace=\177`
               - key_dc (kdch1) terminfo entry: `key_dc=\E[3~`
               - $COLORTERM="truecolor"

               ==============================================================================
               nvim-treesitter: require("nvim-treesitter.health").check()

  Installation ~
  - OK `tree-sitter` found 0.20.7 (parser generator, only needed for :TSInstallFromGrammar)
- OK `node` found v19.5.0 (only needed for :TSInstallFromGrammar)
  - OK `git` executable found.
  - OK `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }
Version: Apple clang version 14.0.0 (clang-1400.0.29.202)
- OK Neovim was compiled with tree-sitter runtime ABI version 14 (required >=13). Parsers must be compatible with runtime ABI.

OS Info:
{
  machine = "arm64",
          release = "22.2.0",
          sysname = "Darwin",
          version = "Darwin Kernel Version 22.2.0: Fri Nov 11 02:04:44 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T8103"
} ~

Parser/Features         H L F I J
- json5               ✓ . . . ✓
- jsonc               ✓ ✓ ✓ ✓ ✓
- json                ✓ ✓ ✓ ✓ .
- vim                 ✓ ✓ ✓ . ✓
- lua                 ✓ ✓ ✓ ✓ ✓
- bash                ✓ ✓ ✓ . ✓
- help                ✓ . . . ✓
- html                ✓ ✓ ✓ ✓ ✓
- javascript          ✓ ✓ ✓ ✓ ✓
- markdown_inline     ✓ . . . ✓
- python              ✓ ✓ ✓ ✓ ✓
- regex               ✓ . . . .
- tsx                 ✓ ✓ ✓ ✓ ✓
- typescript          ✓ ✓ ✓ ✓ ✓
- yaml                ✓ ✓ ✓ ✓ ✓
- c                   ✓ ✓ ✓ ✓ ✓
- markdown            ✓ . ✓ . ✓
- query               ✓ ✓ ✓ ✓ ✓
- cpp                 ✓ ✓ ✓ ✓ ✓

Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
+) multiple parsers found, only one will be used
x) errors found in the query, try to run :TSUpdate {lang} ~

==============================================================================
provider: health#provider#check

Clipboard (optional) ~
- OK Clipboard tool found: pbcopy

Python 3 provider (optional) ~
- pyenv: Path: /opt/homebrew/Cellar/pyenv/2.3.11/libexec/pyenv
- pyenv: Root: /Users/philippg/.pyenv
- `g:python3_host_prog` is not set.  Searching for python3.9 in the environment.
- WARNING Your virtualenv is not set up optimally.
- ADVICE:
- Create a virtualenv specifically for Nvim and use `g:python3_host_prog`.  This will avoid the need to install the pynvim module in each virtualenv.
- Executable: /opt/homebrew/bin/python3.9
- Python version: 3.9.16
- pynvim version: 0.4.3
- OK Latest pynvim is installed.

Python virtualenv ~
- WARNING $VIRTUAL_ENV is set to: /Users/philippg/venvs/zi
And its /bin directory contains: python, python3, python3.11
But $PATH in subshells yields this python3 executable: /opt/homebrew/opt/python@3.10/bin/python3.10
And $PATH in subshells yields this python3.11 executable: /opt/homebrew/opt/python@3.11/bin/python3.11
So invoking Python may lead to unexpected results.
- ADVICE:
- $PATH ambiguities in subshells typically are caused by your shell config overriding the $PATH previously set by the virtualenv. Either prevent them from doing so, or use this workaround: https://vi.stackexchange.com/a/34996

Ruby provider (optional) ~
- Ruby: ruby 2.6.10p210 (2022-04-12 revision 67958) [universal.arm64e-darwin22]
- WARNING `neovim-ruby-host` not found.
- ADVICE:
- Run `gem install neovim` to ensure the neovim RubyGem is installed.
- Run `gem environment` to ensure the gem bin directory is in $PATH.
- If you are using rvm/rbenv/chruby, try "rehashing".
- See :help |g:ruby_host_prog| for non-standard gem installations.
- You may disable this provider (and warning) by adding `let g:loaded_ruby_provider = 0` to your init.vim

Node.js provider (optional) ~
- Node.js: v19.5.0
- WARNING Missing "neovim" npm (or yarn, pnpm) package.
- ADVICE:
- Run in shell: npm install -g neovim
- Run in shell (if you use yarn): yarn global add neovim
                                  - Run in shell (if you use pnpm): pnpm install -g neovim
                                                                    - You may disable this provider (and warning) by adding `let g:loaded_node_provider = 0` to your init.vim

                                                                    Perl provider (optional) ~
                                                                    - WARNING "Neovim::Ext" cpan module is not installed
                                                                    - ADVICE:
                                                                    - See :help |provider-perl| for more information.
                                                                    - You may disable this provider (and warning) by adding `let g:loaded_perl_provider = 0` to your init.vim

                                                                    ==============================================================================
                                                                    telescope: require("telescope.health").check()

                                                                    Checking for required plugins ~
                                                                    - OK plenary installed.
                                                                    - OK nvim-treesitter installed.

                                                                    Checking external dependencies ~
                                                                    - OK rg: found ripgrep 13.0.0
                                                                    - OK fd: found fd 8.6.0

                                                                    ===== Installed extensions ===== ~

                                                                    ==============================================================================
                                                                    treesitter: health#treesitter#check

                                                                    - ERROR Failed to run healthcheck for "treesitter" plugin. Exception:
                                                                    function health#check[25]..health#treesitter#check, line 2
                                                                    Vim(lua):E5108: Error executing lua [string ":lua"]:1: attempt to call field 'check_health' (a nil value)
                                                                             stack traceback:
                                                                               [string ":lua"]:1: in main chunk

                                                                                ==============================================================================
                                                                                vim.lsp: require("vim.lsp.health").check()

                                                                                - LSP log level : WARN
                                                                                - Log path: /Users/philippg/.local/state/nvim/lsp.log
                                                                                - Log size: 2098 KB

  vim.lsp: Active Clients ~
  - copilot (id=1, root_dir=nil)
- clangd (id=2, root_dir=/Users/philippg/Repos/labone)

  ==============================================================================
  vim.treesitter: require("vim.treesitter.health").check()

  - Nvim runtime ABI version: 14
  - OK Parser: bash       ABI: 14, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/bash.so
  - OK Parser: cpp        ABI: 14, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/cpp.so
  - OK Parser: help       ABI: 14, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/help.so
  - OK Parser: html       ABI: 13, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/html.so
  - OK Parser: javascript ABI: 14, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/javascript.so
  - OK Parser: json       ABI: 13, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/json.so
  - OK Parser: json5      ABI: 13, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/json5.so
  - OK Parser: jsonc      ABI: 13, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/jsonc.so
  - OK Parser: lua        ABI: 13, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/lua.so
  - OK Parser: markdown   ABI: 13, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/markdown.so
  - OK Parser: markdown_inline ABI: 13, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/markdown_inline.so
  - OK Parser: python     ABI: 14, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/python.so
  - OK Parser: query      ABI: 14, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/query.so
  - OK Parser: regex      ABI: 13, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/regex.so
  - OK Parser: tsx        ABI: 14, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/tsx.so
  - OK Parser: typescript ABI: 14, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/typescript.so
  - OK Parser: vim        ABI: 14, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/vim.so
  - OK Parser: yaml       ABI: 13, path: /Users/philippg/.local/share/nvim/lazy/nvim-treesitter/parser/yaml.so
  - OK Parser: c          ABI: 13, path: /usr/local/lib/nvim/parser/c.so
  - OK Parser: help       ABI: 14, path: /usr/local/lib/nvim/parser/help.so
  - OK Parser: lua        ABI: 13, path: /usr/local/lib/nvim/parser/lua.so
  - OK Parser: vim        ABI: 14, path: /usr/local/lib/nvim/parser/vim.so

  ==============================================================================
  which_key: health#which_key#check

  WhichKey: checking conflicting keymaps ~
  - WARNING conflicting keymap exists for mode **"v"**, lhs: **"a"**
  - rhs: `v:lua.MiniAi.expr_textobject('x', 'a')`
  - WARNING conflicting keymap exists for mode **"v"**, lhs: **"i"**
  - rhs: `v:lua.MiniAi.expr_textobject('x', 'i')`
  - WARNING conflicting keymap exists for mode **"n"**, lhs: **"gc"**
  - rhs: `v:lua.MiniComment.operator()`
  - WARNING conflicting keymap exists for mode **"o"**, lhs: **"i"**
  - rhs: `v:lua.MiniAi.expr_textobject('o', 'i')`
  - WARNING conflicting keymap exists for mode **"o"**, lhs: **"a"**
  - rhs: `v:lua.MiniAi.expr_textobject('o', 'a')`

I saw this mentioned in a PR and it does seem to have a solution about the
problem you're mentioning here. Check to see if it works for you.

This is not a LazyVim issue. You should post this in the discussions instead.
Either way, this is a current Neovim limitation. You could try changing the offset encoding for clangd or for null-ls.

Just to understand: can this be that this is only a null-ls problem? Because I've used clangd and lsp before I started using LazyVim but without null-ls, and I didn't encounter this issue.

Is there a way to fix this for rust-analyzer?
It seems rust-analyzer and copilot are conflicting.
my rust setup:
return {
  { -- extend auto completion
    "hrsh7th/nvim-cmp",
    dependencies = {
      {
        "Saecki/crates.nvim",
        event = { "BufRead Cargo.toml" },
        config = true,
      },
    },
    ---@param opts cmp.ConfigSchema
    opts = function(_, opts)
      local cmp = require("cmp")
      opts.sources = cmp.config.sources(vim.list_extend(opts.sources, {
        { name = "crates", priority = 750 },
      }))
    end,
  },

  -- add rust to treesitter
  {
    "nvim-treesitter/nvim-treesitter",
    opts = function(_, opts)
      if type(opts.ensure_installed) == "table" then
        vim.list_extend(opts.ensure_installed, { "rust", "toml" })
      end
    end,
  },

  -- correctly setup mason lsp / dap extensions
  {
    "williamboman/mason.nvim",
    opts = function(_, opts)
      if type(opts.ensure_installed) == "table" then
        vim.list_extend(opts.ensure_installed, { "codelldb", "rust-analyzer", "taplo" })
      end
    end,
  },

  -- correctly setup lspconfig for Rust 🚀
  {
    "neovim/nvim-lspconfig",
    dependencies = { "simrat39/rust-tools.nvim" },
    opts = {
      -- make sure mason installs the server
      servers = {
        rust_analyzer = {},
      },
      setup = {
        rust_analyzer = function(_, opts)
          require("lazyvim.util").on_attach(function(client, buffer)
          -- stylua: ignore
          if client.name == "rust_analyzer" then
            vim.keymap.set("n", "K", "<cmd>RustHoverActions<cr>", { buffer = buffer, desc = "Hover Actions (Rust)" })
            vim.keymap.set("n", "<leader>cR", "<cmd>RustCodeAction<cr>", { buffer = buffer, desc = "Code Action (Rust)" })
            vim.keymap.set("n", "<leader>dr", "<cmd>RustDebuggables<cr>", { buffer = buffer, desc = "Run Debuggables (Rust)" })
          end
          end)
          local mason_registry = require("mason-registry")
          -- rust tools configuration for debugging support
          local codelldb = mason_registry.get_package("codelldb")
          local extension_path = codelldb:get_install_path() .. "/extension/"
          local codelldb_path = extension_path .. "adapter/codelldb"
          local liblldb_path = vim.fn.has("mac") == 1 and extension_path .. "lldb/lib/liblldb.dylib"
            or extension_path .. "lldb/lib/liblldb.so"
          local rust_tools_opts = vim.tbl_deep_extend("force", opts, {
            dap = {
              adapter = require("rust-tools.dap").get_codelldb_adapter(codelldb_path, liblldb_path),
            },
            tools = {
              on_initialized = function()
                vim.cmd([[
              augroup RustLSP
              autocmd CursorHold                      *.rs silent! lua vim.lsp.buf.document_highlight()
              autocmd CursorMoved,InsertEnter         *.rs silent! lua vim.lsp.buf.clear_references()
              autocmd BufEnter,CursorHold,InsertLeave *.rs silent! lua vim.lsp.codelens.refresh()
              augroup END
              ]])
              end,
            },
            server = {
              settings = {
                ["rust-analyzer"] = {
                  cargo = {
                    allFeatures = true,
                    loadOutDirsFromCheck = true,
                    runBuildScripts = true,
                  },
                  -- Add clippy lints for Rust.
                  checkOnSave = {
                    allFeatures = true,
                    command = "clippy",
                    extraArgs = { "--no-deps" },
                  },
                  procMacro = {
                    enable = true,
                    ignored = {
                      ["async-trait"] = { "async_trait" },
                      ["napi-derive"] = { "napi" },
                      ["async-recursion"] = { "async_recursion" },
                    },
                  },
                },
              },
            },
          })
          require("rust-tools").setup(rust_tools_opts)
          return true
        end,
        taplo = function(_, _)
          local function show_documentation()
            if vim.fn.expand("%:t") == "Cargo.toml" and require("crates").popup_available() then
              require("crates").show_popup()
            else
              vim.lsp.buf.hover()
            end
          end
          require("lazyvim.util").on_attach(function(client, buffer)
          -- stylua: ignore
          if client.name == "taplo" then
            vim.keymap.set("n", "K", show_documentation, { buffer = buffer, desc = "Show Crate Documentation" })
          end
          end)
          return false -- make sure the base implementation calls taplo.setup
        end,
      },
    },
  },
}

but when i add in this for copilot:
return {
  -- copilot
  {
    "zbirenbaum/copilot.lua",
    config = true,
    event = "VeryLazy",
    opts = {
      suggestion = { enabled = false },
      panel = { enabled = false },
    },
  },
  {
    "zbirenbaum/copilot-cmp",
    event = "VeryLazy",
    config = true,
  },
}

it seems to blowup.

the LazyVim copilot + rust extra works without issues for me

You're probably globally overriding offsetencoding

You're probably globally overriding offsetencoding

I looked and did not find anything with grep effecting anything with keywords offset, encoding, etc.
Just got a virtual machine going and will see if I can replicate, or at least get it working using the extras.  Did not see them there a month or two ago, you are a beast.

https://github.com/Thevetat/lazy-rust-copilot-issue
I believe all I added was this:
{ import = "lazyvim.plugins.extras.lang.typescript" },
{ import = "lazyvim.plugins.extras.lang.json" },
{ import = "lazyvim.plugins.extras.lang.rust" },
{ import = "lazyvim.plugins.extras.coding.copilot" },
cargo init in a new folder, opened up the main.rs and on insert I get that warning.

authors: Thevetat dpetka2001 fibbo folke

repo: LazyVim/LazyVim


text:
Update input text on autocomplete option highlight

Just want to start out by saying that I'd be happy to implement any work that might come out of this issue. I'm more looking for a general +1 on the idea, as well as hash out what the api might look like. With that out of the way...
Goal: I'm looking to replace a jQuery-UI based autocomplete implementation with Awesomplete. However, for feature parity, I need the input text to update as I navigate through autocomplete choices. More concretely:

A list of autocomplete options are shown (e.g., I've typed "ja" and get the choices "java" and "javascript")
I navigate through the options
As I navigate, the input text updates to reflect the highlighted choice (pressing down once will update the field text to "java" and so on)

hitting escape closes the autocomplete dialog and reverts the input text back to the original value ("ja")
"selecting" the option works as is already implemented

I'm fairly confident that this can all be achieved with the existing API. Live-updating the input text is fairly trivial with the awesomplete-highlight event, and the original value can be cached on awesomplete-open. The hacky part comes with the escape functionality, as the code currently makes no distinction between pressing escape and any of the other methods of closing. I might be able to do something with setTimeout / clearTimeout, but it's definitely not ideal, hence this issue.
So open questions:

Is there general value in this behavior? Does it fall inline with the goals of this library?
If yes, would this be best wrapped up in a single constructor option (and if so, what's a good name), or would it be preferred to leave much of this in userland and a) expose an update to the escape/blur functionality to either close in a "close and do nothing" state, or b) alternatively fire off a second, more meaningful event? Or something else entirely?

@jimf Thanks for very detailed explanation.
So how does jQuery UI autocomplete widget handles this case? Does it have option, event or something else?

@vlazar this is the default behavior. Afaict, there is actually no direct way to disable it.

Personally I'm leaning towards having additional event and implementing your use case in userland.

b) alternatively fire off a second, more meaningful event

It will be trivial to add new event here: https://github.com/LeaVerou/awesomplete/blob/gh-pages/awesomplete.js#L70
It looks like hitting escape is the only case when the currently highlighted choice should be reverted on close(). In all other cases where close() is called and already triggers awesomplete-close event should keep currently highlighted.
But then, of course, it's an API and obvious question would be wether we should add one more event or not.
Also, I'm a bit worried about meaningful event name. If we'll add, say awesomplete-cancel it will have no meaning for Awesomplete itself, since it doesn't change input currently, so there is nothing to cancel.

Okay, I've hacked together a proof-of-concept that does what I want using the existing API (only tested in Chrome): https://jsfiddle.net/jimfitz/wgk9a32c/. I'm not in love with the timeout stuff, but I don't think there's an alternative without updating the library. The cancel-event approach would allow me to consolidate onClose and onComplete into a single, more purposeful callback. A dedicated option would get rid of all of the callbacks and state variables, but at the expense of more API surface and library code.
--
PS: Possibly worth a secondary PR, but it seems the close event gets fired, even when the dialog isn't open. Is this known/intentional? I had to work around it in the fiddle. I'd imagine close could just be updated with an if (opened) check to early-return.

Also, I'm a bit worried about meaningful event name. If we'll add, say awesomplete-cancel it will have no meaning for Awesomplete itself, since it doesn't change input currently, so there is nothing to cancel.

Another option worth considering is adding an argument to the cancel event that would expose the cancel method. The following example would suffice for my needs:
$.fire(this.input, "awesomplete-close", { escape: true });

However, it may be beneficial to encode the "close reason" for all the places where the dialog closes, so one could differentiate between escape/blur/confirm etc. directly in the event callback.

I've played a bit with your example at https://jsfiddle.net/jimfitz/wgk9a32c/. I don't know if this is something you care about, but jQueryUI example at http://jqueryui.com/autocomplete/ does not revert selected text on blur event in addition to keydown esc, while yours does.
Here is how I would probably implement this https://jsfiddle.net/yaufeLwn/. It also handles blur/esc similarly to jQueryUI.
Is it simple enough for not to add new features to Awesomplete? Or maybe there are other good reasons to support add new event or "close reason" so that library users can simplify their code?

I don't know if this is something you care about, but jQueryUI example at http://jqueryui.com/autocomplete/ does not revert selected text on blur event in addition to keydown esc, while yours does.

Yes, sorry. I fixed that behavior in my own code but didn't bother to update the fiddle. The behavior you describe/implemented is what I'm after.

Here is how I would probably implement this [snip]

Nice! I got so caught up trying to do this with the given Awesomplete events that it didn't even occur to me to just use a keydown. This is much nicer.

Is it simple enough for not to add new features to Awesomplete? Or maybe there are other good reasons to support add new event or "close reason" so that library users can simplify their code?

At this point I am satisfied. Thank you for your time! :beers:

I got so caught up trying to do this with the given Awesomplete events that it didn't even occur to me to just use a keydown.

Yep, exactly. I was trying to do the same thing initially. It's like trying to do something X-way immediately shuts off the brain for other options :)

I like the proposed behavior.
The fact that it needs a keydown instead of one of the existing events sounds like a failing of our API to me. It sounds like awesomplete-close does need a parameter about the reason for closing. Thoughts?

reason? With values like blur, esc, submit, select, minchars, nomatches?

reason? With values like blur, esc, submit, select, minchars, nomatches?

:+1: from me. I'd be happy to implement if we're in agreement.

Sure, as long as you update the docs too!

Can you do the tests too, please?

Just reviewed the list of cases when awesomplete-close event is fired. It's probably a good time to do some cleanup as well?
For example, I agree with this concern:

PS: Possibly worth a secondary PR, but it seems the close event gets fired, even when the dialog isn't open. Is this known/intentional? I had to work around it in the fiddle. I'd imagine close could just be updated with an if (opened) check to early-return.

Also, does minchars case is valuable enough to be implemented as a separate reason or at all? What if we combine it with nomatches?

Sure, as long as you update the docs too!

Will do.

Can you do the tests too, please?

Of course!

It's probably a good time to do some cleanup as well?

Sounds good. I'll make that change in a separate PR.

Also, does minchars case is valuable enough to be implemented as a separate reason or at all? What if we combine it with nomatches?

Combining makes sense to me, but I don't have strong feelings.

Is this new behavior released yet? I can't tell but I don't think it is?

Also: I used the enhancement from @vlazar fiddle (https://jsfiddle.net/yaufeLwn/1/). But this behavior does conflict with 'autoFirst:true'. I kinda need both features to work. But if you use them together, you lose the ability to backspace and type something else.

Is this new behavior released yet? I can't tell but I don't think it is?

@El4a What behavior are you referring to?
#16898 and #16899 are released in v1.1.1

@vlazar I meant the proposed behavior described by jimf in the original post concerning :
"A list of autocomplete options are shown (e.g., I've typed "ja" and get the choices "java" and "javascript")
I navigate through the options
As I navigate, the input text updates to reflect the highlighted choice (pressing down once will update the field text to "java" and so on)"
I just got the latest zip and this feature didn't seem to be included, so I used the fiddle you made to enhance it.
About my other issue that it conflicts with the setting autoFirst:true -> I realised that's to be expected.

No, the proposed behavior is not supported out of the box, but is easy to implement.
This issue however led to #16899 with additional info available on events, so it should be even easier o implement than in original fiddle.

authors: El4a LeaVerou jimf vlazar

repo: LeaVerou/awesomplete


text:
doulbe lists of items

in reference to this discussion https://github.com/LeaVerou/awesomplete/issues/17208 I have solved, for the moment, reloading the page and then resetting all the lists of Awesome. As I was asked I proceeded to create a codepen https://codepen.io/CaneRandagio/pen/QWjydBO in the js code there are instructions for recreating the problem. Thanks to the availability

Perfect, providing a Codepen makes it MUCH easier to assist. I spotted your issue immediately!
Every time popola() is called it does another new Awesomplete(). You're creating multiple Awesomplete instances on the same input. Instead you should do something like.
const textboxAwesomplete = new Awesomplete(textbox, {list:items});
and when you want to update
textboxAwesomplete.list(newListOfItems)

ok. Thanks


text:
stop the shim from treating gradient-center as a color stop

A partial fix for #10. Ideally, the background-position property should also be taken into account. This may come in another commit somewhere down the line ;)

Thanks for contributing and spotting what was causing that bug!
Agreed with the fix, but the terminology is confusing. This is not the background-position property, this is the center point of the gradient. Could you fix that please?

done.

Thanks! Also please remove the console.log() or add a check if the console object exists? (and make it console.warn). i.e. self.console && console.warn && console.warn("text here");

I've gone ahead and made an implemented functionality to specify the gradient's center position. That commit would supersede this one, so, I'd like to close this PR.

Hello,
I think this PR broke RGBA colors. Could you please look into it?
Thanks.

Hi, can you give a reproducible example? It'd help in tracking down the issue

It's very weird. It was magically fixed on its own, without a Chrome update even. So odd. But less to debug!

Hmm, that's odd... If it happens again, please grab a screenshot and put it here. I can try to trace it.

authors: LeaVerou kumarharsh

repo: LeaVerou/conic-gradient


text:
Adding a single marker, with a custom count

Markers below a certain zoom level are clustered by the server in my case, and markers above a certain zoom by the client. I already saw this issue and implemented Danielku15's method, but it didn't work out.
https://github.com/Leaflet/Leaflet.markercluster/issues/217
It works fine, except that it displays a single marker when there are no nearby clusters. I tried to fix this issue by myself, but I'm having a hard time doing so. Any plans on adding the ability to make a custom cluster count? So that the MarkerClusterer doesn't display a single marker instead?
There are other cases when this can be of use. Also for client side purposes e.g. having a own client side clustering implementation, or other scenarios where the clusters are known before adding them to the MarkerGroup.
Thanks in advance!

Currently my team and I are also facing the exact same issue. Wherein we need to render server clusters that are computed by density on a grid and then sent to the client with a count field of >0. However the clustering on the server does not concern itself with rendering on the viewport as far as overlaying clusters and markers, so we need to upgrade that view with clustering on the client. Has anyone found a streamlined implementation for this. Has this feature been added somewhere.

authors: dewdad rrooij


text:
map.getCenter() does not work with polarstereograhic maps

Especially if one of the poles is within the bounds results are outside of the map. Currently I use this code to circumvent:
getCenter: function(map){

  var prj = map.options.crs.projection,
      sw  = map.getBounds()._southWest,
      ne  = map.getBounds()._northEast,
      psw = prj.project(sw),
      pne = prj.project(ne),
      x   = psw.x + (pne.x - psw.x)/2,
      y   = psw.y + (pne.y - psw.y)/2;

  return prj.unproject({x:x, y:y});

},

Works at least with EPSG:3413. L.ImageOverlay._reset() and ._animateZoom() have  same problem.

I think it might have been fixed in 1.0.0-beta.1, can you verify?

Like @mourner says, this looks like it has been fixed in current master, although I can't verify since I don't have a polarstereograhic map to test with.
Closing for now, but feel free to add more info if this is still a problem.

authors: mourner noiv perliedman

repo: Leaflet/Leaflet


text:
Draggable: Remove offset subtract from _startPos

I will try to explain this, hopefully it works.
If the dragging is started (_onDown) and then the first mousemove event is fired (_onMove), the _startPos is calculated wrong. The element can't be moved until now, because it is the first mousemove event, so it makes no sense that for the startPos calculation the offset is removed from the current position. -> there is no offset because the element is not moved.
this._startPos = DomUtil.getPosition(this._element).subtract(offset);

Example: https://plnkr.co/edit/Fz9jPeP7JIrPleXo

Create draggable Marker
Hold down on the Marker
Call manual _onMove to visualize the wrong _startPos calculation.

var marker = new L.Marker([0, 0], { draggable: true}).addTo(map);
setTimeout(function () {
    marker.dragging._draggable._onMove({
        type: 'mousemove',
        buttons: 1,
        clientX: 100,
        clientY: 100,
        target: marker._icon
    });
}, 3000);

Expectation:
The marker "jumps" to the position of the mousemove event ([100, 100]). But instead it creates the _startPos (currentElementPos - offset) and then it calculates the new position of the element by calling _startPos + offset = currentElementPos - offset + offset = currentElementPos -> And now we are at exact same position where the marker already is. If the next mousemove is fired, the dragging starts working because now the _startPos is defined and the offset is different.
Solution:
This can be simply fixed by changing:
this._startPos = DomUtil.getPosition(this._element).subtract(offset);

to:
this._startPos = DomUtil.getPosition(this._element);

We see this wrong usage in already existing tests. If toucher.wait(100).moveTo(200, 200, 0) .down().moveBy(5, 0, 20).moveBy(256, 32, 200).up(); is called, the first mousemove while dragging is ignored moveBy(5, 0, 20) and the marker is not moved.
The offset subtracting was added in this commit https://github.com/Leaflet/Leaflet/commit/2d2fc74110f2fe7fbc06d7f6e0a2e90528ce46c6

Seems duplicate of some other pr

Ah yes I found #7446.
@johnd0e Can you convert your PR from draft to "ready for review" ? Then I will close this one.

Close in favor of #7446