Closes #154 Council update blogpost TOC looks strange

Thank you for your Pull Request! We have developed this task checklist to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your blog post.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update), and make sure the corresponding issue is linked in the Development section on the right hand side
[x] Run the script from CICD.R line by line to first check the spelling in your post and then to make sure your code is compatible with our code-style. Address any incongruences by following the instructions in the file!
[x] Choose (possibly several) tag(s) or categories from the current list: c("Metadata", "SDTM", "ADaM", "TLG", "Shiny", "Community", "Conferences", "Submissions", "Technical") for your blog post. If you cannot find anything that fits your blog post, add your own tag! We occasionally tidy up all tags for consistency.
[x] Add a short description for your blog post in the description field at the top of the markdown document.
[x] Blog post is short, personalized, reproducible and readable
[x] Add a disclaimer at the top of your post, if appropriate (example: Disclaimer
This blog contains opinions that are of the authors alone and do not necessarily reflect the strategy of their respective organizations.)
[x] Address all merge conflicts and resolve appropriately
[x] Assign two of us (@bms63, @manciniedoardo, @StefanThoma, @kaz462) as reviewers in the PR.
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

Closes #154

I just added the PNG file to your folder, and updated the script, now the rendering is fixed, I think.

I just added the PNG file to your folder, and updated the script, now the rendering is fixed, I think.

Great, thank you!
I didn't think everybody needed to copy in the same images again 😃


Convert stored properties into computed properties

This PR addresses a compiler error in Xcode 15.0 Beta, which states:

Stored properties cannot be marked potentially unavailable with '@available'

Since use of such properties is inhibited through a compiler error, I've simply replaced the stored properties marked as unavailable with computed properties that are returning the same result they're returning now.

Thank you!

Wouldn't it have been better if instead of
public var allowTap: Bool { return true }

to do this:
public var allowTap: Bool { self.singleTapGestureRecognizer.view != nil }

It would stay consistent with the new API instead of being a computed property which in essence is a constant?

Wouldn't it have been better if instead of
public var allowTap: Bool { return true }

to do this:
public var allowTap: Bool { self.singleTapGestureRecognizer.view != nil }

It would stay consistent with the new API instead of being a computed property which in essence is a constant?

Since the property is annotated with @available(*, unavailable, renamed: "isUserInteractionEnabled"), accessing it results in a compiler error: 'allowTap' has been renamed to 'isUserInteractionEnabled', because of which a value of this property is irrelevant.
(I believe) It's just kept to make upgrades from older package versions easier to perform, since it's not really obvious that isUserInteractionEnabled does the same thing that allowTap used to do.

Thanks man, Save my time


Updated deps and switch from youtube-dl to yt-dlp

Some of the dependencies would not work when I was trying to use it, and as for yt-dlp it is a more up to date version of youtube-dl. Also from lines 349-352 there was a bug with it adding .wav to a file that was something.mp4 leading to the file being called something.mp4.wav so I just removed the .mp4 since otherwise it would break the rest of the code.

LGTM


How to implement form controls? Controlled/Uncontrolled components

Support questions
There are some scenarios where folks need to have control over the value of a form control in order to be able to satisfy the requirements, currently, most of our implementations are uncontrolled components that encapsulate the state value within the implementation and can't be accessed from outside.
Should we aim to have components that work out of the box but also expose a prop to control the state if needed?
Similar to the approach described at https://egghead.io/lessons/react-make-controlled-react-components-with-control-props

@duranmla Thanks for bringing this topic up as an issue. I think most of our components are controlled components (or at least support that api). I'm a big fan of controlled components as they seem to fit very well in the React landscape for components to always render deterministically. Let's find the components that don't match this and update them (where possible) so wave is more consistent overall

@snapsnapturtle that is true, most of the components we use are controlled components. But what @duranmla was pointing out is a step further.  The idea is to have a component that works in isolation with it's own state that does not depend on its environment and also exposes props to control its state and relative renders. So far the ones we have don't work in isolation.
The video explains the idea behind it quite well.
Here you have an example of a possible implementation: https://github.com/freenowtech/wave/pull/153
Feel free to start the discussion there, so we can decide on a common strategy.


Improve handling of output

before beautifully visualizing the output, the formatting of output should be re-considered
using more structured data format like JSON Lines would be good
using PHP as a template engine might be also good

yeah, it's a template engine in the first place...

done on #32


2023-09-27 09:39:37.415 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.415 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.416 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.416 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.417 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.417 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.419 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.419 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.419 [CLI ] Skipping Steam App 736260 as it has unknown installed version
2023-09-27 09:39:37.420 [CLI ] Skipping Sublime Text_is1 as it has unknown installed version
2023-09-27 09:39:37.421 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.421 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.422 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.423 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.424 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.426 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.427 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.429 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.430 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.430 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.431 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.432 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.432 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.433 [CLI ] Package [Xmind.Xmind with Version[23.07.180256] from Source[Microsoft.Winget.Source_8wekyb3d8bbwe] has a Pin with type[Gating]
2023-09-27 09:39:37.434 [CLI ] Package [Xmind.Xmind with Version[23.06.301214] from Source[Microsoft.Winget.Source_8wekyb3d8bbwe] has a Pin with type[Gating]
2023-09-27 09:39:37.434 [CLI ] Package [Xmind.Xmind with Version[22.11.3771] from Source[Microsoft.Winget.Source_8wekyb3d8bbwe] has a Pin with type[Gating]
2023-09-27 09:39:37.434 [CLI ] Package [Xmind.Xmind with Version[22.11.3656] from Source[Microsoft.Winget.Source_8wekyb3d8bbwe] has a Pin with type[Gating]
2023-09-27 09:39:37.434 [CLI ] Package [Xmind.Xmind with Version[22.10.0919] from Source[Microsoft.Winget.Source_8wekyb3d8bbwe] has a Pin with type[Gating]
2023-09-27 09:39:37.435 [CLI ] Package [Xmind.Xmind with Version[22.10.0631] from Source[Microsoft.Winget.Source_8wekyb3d8bbwe] has a Pin with type[Gating]
2023-09-27 09:39:37.435 [CLI ] Package [Xmind.Xmind with Version[22.9.3168] from Source[Microsoft.Winget.Source_8wekyb3d8bbwe] has a Pin with type[Gating]
2023-09-27 09:39:37.435 [CLI ] Package [Xmind.Xmind with Version[22.8.2357] from Source[Microsoft.Winget.Source_8wekyb3d8bbwe] has a Pin with type[Gating]
2023-09-27 09:39:37.435 [CLI ] Package [Xmind.Xmind with Version[22.8.2195] from Source[Microsoft.Winget.Source_8wekyb3d8bbwe] has a Pin with type[Gating]
2023-09-27 09:39:37.435 [CLI ] Terminating context: 0x8a15002b at D:\a_work\1\s\external\pkg\src\AppInstallerCLICore\Workflows\UpdateFlow.cpp:b8
2023-09-27 09:39:37.439 [REPO] Downloading manifest
2023-09-27 09:39:37.439 [CORE] WinINet downloading from url: https://cdn.winget.microsoft.com/cache/manifests/n/Notion/Notion/2.0.49/75d8-Notion.Notion.yaml
2023-09-27 09:39:37.849 [CORE] Download request failed. Returned status: 429
2023-09-27 09:39:37.849 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(67)\WindowsPackageManager.dll!00007FFD54624046: (caller: 00007FFD5477D7C2) Exception(17) tid(4984) 801901AD     Msg:[Download request status is not success.]
2023-09-27 09:39:37.850 [REPO] Downloading manifest failed, waiting a bit and retrying: https://cdn.winget.microsoft.com/cache/manifests/n/Notion/Notion/2.0.49/75d8-Notion.Notion.yaml
2023-09-27 09:39:38.353 [CORE] WinINet downloading from url: https://cdn.winget.microsoft.com/cache/manifests/n/Notion/Notion/2.0.49/75d8-Notion.Notion.yaml
2023-09-27 09:39:42.007 [CORE] Download request failed. Returned status: 429
2023-09-27 09:39:42.007 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(67)\WindowsPackageManager.dll!00007FFD54624046: (caller: 00007FFD5477D7C2) Exception(18) tid(4984) 801901AD     Msg:[Download request status is not success.]
2023-09-27 09:39:42.007 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Microsoft\SQLiteIndexSource.cpp(97)\WindowsPackageManager.dll!00007FFD548B79C7: (caller: 00007FFD546A3481) LogHr(13) tid(4984) 801901AD     Msg:[GetManifest failed on primary location -- D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(67)\WindowsPackageManager.dll!00007FFD54624046: (caller: 00007FFD5477D7C2) Exception(18) tid(4984) 801901AD     Msg:[Download request status is not success.]
]
2023-09-27 09:39:42.007 [REPO] Downloading manifest
2023-09-27 09:39:42.007 [CORE] WinINet downloading from url: https://winget-cache-pme-cxfsgwfxarb8hwg0.z01.azurefd.net/cache/manifests/n/Notion/Notion/2.0.49/75d8-Notion.Notion.yaml
2023-09-27 09:39:42.116 [CORE] Download request failed. Returned status: 429
2023-09-27 09:39:42.116 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(67)\WindowsPackageManager.dll!00007FFD54624046: (caller: 00007FFD5477D7C2) Exception(19) tid(4984) 801901AD     Msg:[Download request status is not success.]
2023-09-27 09:39:42.116 [REPO] Downloading manifest failed, waiting a bit and retrying: https://winget-cache-pme-cxfsgwfxarb8hwg0.z01.azurefd.net/cache/manifests/n/Notion/Notion/2.0.49/75d8-Notion.Notion.yaml
2023-09-27 09:39:42.628 [CORE] WinINet downloading from url: https://winget-cache-pme-cxfsgwfxarb8hwg0.z01.azurefd.net/cache/manifests/n/Notion/Notion/2.0.49/75d8-Notion.Notion.yaml
2023-09-27 09:39:43.098 [CORE] Download request failed. Returned status: 429
2023-09-27 09:39:43.098 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(67)\WindowsPackageManager.dll!00007FFD54624046: (caller: 00007FFD5477D7C2) Exception(20) tid(4984) 801901AD     Msg:[Download request status is not success.]
2023-09-27 09:39:43.098 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Microsoft\SQLiteIndexSource.cpp(105)\WindowsPackageManager.dll!00007FFD548B7A07: (caller: 00007FFD546A3481) LogHr(14) tid(4984) 801901AD     Msg:[GetManifest failed on alternate location -- D:\a_work\1\s\external\pkg\src\AppInstallerCommonCore\Downloader.cpp(67)\WindowsPackageManager.dll!00007FFD54624046: (caller: 00007FFD5477D7C2) Exception(20) tid(4984) 801901AD     Msg:[Download request status is not success.]
]
2023-09-27 09:39:43.098 [FAIL] D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Microsoft\SQLiteIndexSource.cpp(107)\WindowsPackageManager.dll!00007FFD5477D0D0: (caller: 00007FFD546A3481) Exception(21) tid(4984) 801901AD
2023-09-27 09:39:43.099 [CLI ] Caught wil::ResultException: D:\a_work\1\s\external\pkg\src\AppInstallerRepositoryCore\Microsoft\SQLiteIndexSource.cpp(107)\WindowsPackageManager.dll!00007FFD5477D0D0: (caller: 00007FFD546A3481) Exception(21) tid(4984) 801901AD
`

Same problem here
Windows 11 Pro

Logfile:
WinGet-2023-09-27-16-14-35.284.log

@denelon Would you mind re-opening this issue? Several of us are still having problems.

Same here ... Win 11


DOC: stats.goodness_of_fit: improve examples

Issue with current documentation:
Hello, I feel confused about the description about stats.goodness.fit. Why I got totally different result when using the two commands:

stats.goodness_of_fit(stats.lognorm, data, fit_params= {'loc':0},statistic='ad', n_mc_samples=9999,)
2.stats.goodness_of_fit(stats.lognorm, data, known_params= {'loc':0},statistic='ad', n_mc_samples=9999,)

Idea or request for content:
Maybe more detailed text and examples about fit_params and known_params in goodness_of_fit?
Additional context (e.g. screenshots, GIFs)
No response

The distinction is documented pretty succinctly: use known_params to specify parameters of the distribution that are known; use fit_params to specify parameters of the distribution that you fit to empirical data.
For example, suppose you are interested in the goodness of fit of a normal distribution.

Based on knowledge of your problem, you are only interested in considering the family of normal distributions with zero mean. This would be provided via known_params={'loc': 0}.
You also have fit the scale parameter to your data by taking the standard deviation sigma. This would be provided via fit_params={'scale': sigma}.

What about the existing documentation is causing the confusion?

Dear, Thanks a lot for your reply and help! But I am confused why I got different results by setting loc as a known parameter of 0, or by setting loc as a fitting parameter of 0. The derived statistics value is different while loc is 0 in both cases?在 2024年11月26日，16:25，Matt Haberland @.***> 写道：
The distinction is documented pretty succinctly: use known_params to specify parameters of the distribution that are known; use fit_params to specify parameters of the distribution that you fit to empirical data.
For example, suppose you are interested in the goodness of fit of a normal distribution.
Based on knowledge of your problem, you are only interested in considering the family of normal distributions with zero mean. This would be provided via known_params={'loc': 0}.
You also have fit the scale parameter to your data by taking the standard deviation sigma. This would be provided via fit_params={'scale': sigma}.
What about the existing documentation is causing the confusion?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

As he explained, loc is not going to be 0 in both cases. When passed in the fit_params, goodness_of_fit will refit each sample using the value that you passed as an initial guess, not a fixed value.

I've amended the answer above. Maybe take another look at the last sentence of the second pair of bullets.
There are two things that "known", "fit", and "guessed" have the potential to change:

the value of the parameter used when generating resamples.
the value of the parameter used when calculating the statistic (for the original sample and all resamples).

When a parameter is "known", it is used for both. When a parameter is "fitted" to the data, it is only used for generating resamples; the parameter always gets fit to the data before calculating the statistic. When a parameter is "guessed", it used not used directly for either; it is just a guess used when fitting with numerical optimization.
If you want to get the same statistic using known_params and fit_params, the known parameter have to be the same as the fitted values:
import numpy as np
from scipy import stats
rng = np.random.default_rng(833679544785446)
x = rng.standard_normal(size=100)
res_known = stats.goodness_of_fit(stats.norm, x, known_params={'loc': np.mean(x), 'scale': np.std(x, ddof=1)}, random_state=rng, statistic=statistic)
print(res_known.statistic)  # 0.04261248791026049
res_fit = stats.goodness_of_fit(stats.norm, x, fit_params={'loc': np.mean(x)}, random_state=rng, statistic=statistic)
print(res_fit.statistic)  # 0.04261248791026049

Dear，Thank you for your explanation. It is clear now.Best regardsJQ在 2024年11月27日，17:21，Matt Haberland @.***> 写道：
I've amended the answer above. Maybe take another look at the last sentence of the second pair of bullets.
There are two things that "known", "fit", and "guessed" have the potential to change:
the value of the parameter used when generating resamples.
the value of the parameter used when calculating the statistic (for the original sample and all resamples).
When a parameter is "known", it is used for both. When a parameter is "fitted" to the data, it is only used for generating resamples; the parameter always gets fit to the data before calculating the statistic. When a parameter is "guessed", it used not used directly for either; it is just a guess used when fitting with numerical optimization.
If you want to get the same statistic using known_params and fit_params, the known parameter have to be the same as the fitted values:
import numpy as np
from scipy import stats
rng = np.random.default_rng(833679544785446)
x = rng.standard_normal(size=100)
res_known = stats.goodness_of_fit(stats.norm, x, known_params={'loc': np.mean(x), 'scale': np.std(x, ddof=1)}, random_state=rng, statistic=statistic)
print(res_known.statistic)  # 0.04261248791026049
res_fit = stats.goodness_of_fit(stats.norm, x, fit_params={'loc': np.mean(x)}, random_state=rng, statistic=statistic)
print(res_fit.statistic)  # 0.04261248791026049
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>


Problem with composite index that has embeddedset followed by datetime

The following sequence of statements cause exception listed below.
create class test extends v
create property test.set1 embeddedset string
create property test.t datetime
create index test.i_set1_t on test(set1, t) notunique
create vertex test set set1 = 'asdf', t = sysdate()
update test remove set1 = 'asdf' where set1 = 'asdf'
delete vertex test

com.orientechnologies.orient.core.index.OIndexException: Error during removal of entry by key
--> java.lang.ClassCastException

Reproduced in 2.0.x branch.
See OCompositeKeySerializer, row 376, it seems that the composite index key does not match key types. @laa any ideas?

Hi @Ziink I have tried several times and can not reproduce the issue on the latest version. Please reopen the issue if you reproduce it.


Change file name spec.html to _spec.html

What this PR does / why we need it:
Currently URL for gateway-api/spec does not work although gateway-api/spec/ works.
OK: https://kubernetes-sigs.github.io/gateway-api/spec
NG: https://kubernetes-sigs.github.io/gateway-api/spec/
(e.g. - README uses the NG url.)
This is because gateway-api/spec shows docs/spec.html,
while gateway-api/spec/ shows docs/spec/index.html.
To fix this issue, this patch changes file name spec.html to _spec.html in docs-src directory.
What type of PR is this?
/kind cleanup
Does this PR introduce a user-facing change?:
NONE

/ok-to-test
/lgtm
/assign @robscott
Rob is working on moving the website from Github pages to Netlify and this patch conflicts with his work. We can get this in first or after the migration is complete.

Hey @nak3, thanks for catching this! I think this will be resolved once #560 gets in - I added a comment explaining the change here: https://github.com/kubernetes-sigs/gateway-api/pull/560#discussion_r578603202. That renames the file to genspec.html which I'm not particularly tied to, but it should fix the root issue here. Once #559 gets in, this file along with all other generated docs files will be removed from git entirely. I think this is probably safe to close in favor of #560, but let me know if not.

With #560 merged in, I think this has been resolved. Feel free to reopen if not. Thanks again for catching this!
/close

sure, no problem at all! Thank you for the change.


#4305 Display comparison value and absolute/relative delta of SLI

Closes #4305
Collapsed:

Negative change:

Positive change:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


feat: populate the Web Dev section

What feature?
add the "building projects" section
https://www.youtube.com/playlist?list=PLPoSdR46FgI4K36elsmeoUynDUXhjvtEn
Add screenshots
No response
Record

[X] I have checked the existing issues
[ ] I want to work on this issue

Hi, I've submitted a pull request #68  adding the first 5 videos.
I left the remaining videos open for new contributors, considering it's a beginner-friendly task.
Feel free to use my pull request as a guide, and don't hesitate to ask me if you have any problems.

thanks


Updated README for Prometheus 2.x

Updated HA configuration, adding Prometheus 2.x.

Done. I added the version caveat but could remove it too.

Thanks!


Add release script

What it does:

Saves your current branch name
Fetches from remote
Checks out RC branch based on origin/develop
Creates a backup of origin/master
Force pushes to master from the release branch
Deletes the release branch
Switches back to the starting branch

There is also a cleanup script that should be used to delete the master backup once you are sure that nothing
went wrong.

Updated


Error with consultaCEP

Hi @vitorleal thanks for the awesome package!
I think something is wrong with correios.consultaCEP.
I'm receiving this error:
TypeError: Cannot call method 'consultaCEP' of undefined

Precisely in this line: https://github.com/vitorleal/node-correios/blob/master/lib/correios.js#L123
Although correios.calcPrecois working just fine.
Do you have any thoughts on how I would be able to fix this?
Thanks

Look's like the search for CEP server is down :rage4:
I will take a better look and try to find an alternative.
Cheers

Can we use JSON instead of SOAP?

Unfortunately the Brazilian Correio's  is a shi@#!$ and the only option they provide to calculate the shipment prices is this SOAP service.
The CEP search i was using was not from Correio's, it was made from someone and they probably was scrapping the Correios search page.
I don't like SOAP at all but we can only move on to migrate is to a better solution when the start to modernize their services.
I will use this option to keep the buscaCEP method in the API but if this AvisoBrasil comes down it will happen again.

Ok cool, I'll keep up posted if something goes wrong with this AvisoBrasil.
Do you need some help to do the change?
Thanks!

Thanks,
no need i will push the changes latter today :smile:
Thanks for the heads up!


Wrong transfer

My name is andre.Please I beg you i mistake sent $9 to a wrong address using tonkeeper and I traced it down here,pls that's my last hope. Please can you send it back😭😭😭😭😭
This is my usdt address in tonkeeper:UQBm30PbZ_MtSCd7MeEK5k3o4TCoSM-uis24fUALJZQnUYc4
Pls I'll be greatful i need it urgently this morning please please

Please close this Issue as it is not related to the repo @tolya-yanot


Finish test for testCreatePeerListener

There are a whole mess of fairly straight forward tests we haven't finished in testCreatePeerListener. They are important for confirming even basic functionality.

This is really about the iOS tests we haven't put in. That is covered under other bugs.


[FR] Docker container-name prefix

All containers on our server are prefixed with the "parent" name - I.E "monitoring-"
So when a service called "elastic" spins up, it's container name is actually "monitoring-elastic".
It would be useful if this could be specified within configuration somewhere and automatically applied within crazyarms so when looking down a list of 101 containers, we can easily see the crazyarms containers.
I.E crazyarms-app, crazyarms-db etc.

Definitely doable. I'll prefix the names tomorrow!


Update Code - Proof_Of_ContributionSnapshot5.md

Apply for Morpehus listing on CoinGecko

Thanks. CoinGecko application that was accepted was submitted by a different contributor.


Access editor font and other styles.

Operating system or device - Godot version:
Any-Godot 2.1alpha
Issue description (what happened, and what was expected):
If we can access the font style and other styles of the editor(May be changed by user to non-default) we can keep the GUI of plugin with same look with editor.
The defaulit  font is too small on my reina laptop screen and it doesn't support Chinese characters. So I changed the font of editor and it works fine. I hope plugins can access and follow the font of editor's to keep same style and display with editor. If it is possible the developers of plugin will no have to add an extra font like this guy TeddyDD/gtern

I am not sure if I understand the issue. Are you trying to do something like editor_plugin.get_editor_settings().get("global/font")?

@neikeq I don't find the method get(String) in class EditorSettings.

@Geequlim EditorSettings is a derived class of Object which has the method get(String). You need the EditorSettings instance that is used by the editor, which can be obtained by calling get_editor_settings() from an EditorPlugin object.

@neikeq  Thank you! I get the font file path by this function call.


Set folder vm folders only

VMware providers contain folders for both "Hosts & Clusters" and "Vms & Templates" which can have duplicate names.  During VM provisioning only vm/template folders should be available for selection as the target folder.
This change limits the drop-down in the provisioning dialog to only the VM folders.  In addition the set_folder method available to automate has been updated to use the same code path as the UI drop-down to ensure the same folder section is available to the caller.
Links

https://bugzilla.redhat.com/show_bug.cgi?id=1414136

Steps for Testing/QA [Optional]
In the VMware provider create a folder in 'Hosts and Clusters" with a different name from any folders listed for vms/templates.  Load the VM provisioning dialog and verify the host folder is not available in the list.
cc @syncrou @agrare

LGTM, @syncrou what do you think?


Usually i do microk8s.status --wait-ready before enabling addons.

@octopus-prime I cannot reproduce this. Could you please attach the microk8s.inspect tarball? in addition to what @balchua suggested could you try to enable each addon separately? The dns addon is a bit special because it has to restart services. It might be that there is a delay in services comming up and the triggering of the next addon.

Well I guess it wont harm to wait in enabler tool too, no ?

@rzr we recently added the microk8s.status --wait-ready in the microk8s.enable wrapper https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/wrappers/microk8s-enable.wrapper#L38 . It might worth making the microk8s.enable ingress addon blocking (ie wait for services to come up). Any tips on how to reproduce this race condition?

Running microk8s.enable separately for each add-on works. Thanks!

is it same issue as:
https://github.com/ubuntu/microk8s/issues/705
?

Yes it seems to be the same only in rev 936 we have some mitigation: https://github.com/ubuntu/microk8s/blob/master/microk8s-resources/wrappers/microk8s-enable.wrapper#L38
Unfortunately I cannot reproduce this anymore.

Unfortunately I cannot reproduce this anymore.

Revision 940 works like a charm:
mike@workstation:~/idea/demo$ sudo snap install microk8s --channel=edge --classic
microk8s (edge) v1.16.1 aus Canonical✓ installiert
mike@workstation:~/idea/demo$ microk8s.enable dns ingress registry helm
Enabling DNS
Applying manifest
serviceaccount/coredns created
configmap/coredns created
deployment.apps/coredns created
service/kube-dns created
clusterrole.rbac.authorization.k8s.io/coredns created
clusterrolebinding.rbac.authorization.k8s.io/coredns created
Restarting kubelet
DNS is enabled
Enabling Ingress
namespace/ingress created
serviceaccount/nginx-ingress-microk8s-serviceaccount created
clusterrole.rbac.authorization.k8s.io/nginx-ingress-microk8s-clusterrole created
role.rbac.authorization.k8s.io/nginx-ingress-microk8s-role created
clusterrolebinding.rbac.authorization.k8s.io/nginx-ingress-microk8s created
rolebinding.rbac.authorization.k8s.io/nginx-ingress-microk8s created
configmap/nginx-load-balancer-microk8s-conf created
daemonset.apps/nginx-ingress-microk8s-controller created
Ingress is enabled
Enabling the private registry
Enabling default storage class
deployment.apps/hostpath-provisioner created
storageclass.storage.k8s.io/microk8s-hostpath created
serviceaccount/microk8s-hostpath created
clusterrole.rbac.authorization.k8s.io/microk8s-hostpath created
clusterrolebinding.rbac.authorization.k8s.io/microk8s-hostpath created
Storage will be available soon
Applying registry manifest
namespace/container-registry created
persistentvolumeclaim/registry-claim created
deployment.apps/registry created
service/registry created
The registry is enabled
Enabling Helm
Fetching helm version v2.14.3.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 25.3M  100 25.3M    0     0  7474k      0  0:00:03  0:00:03 --:--:-- 7476k
Helm is enabled
mike@workstation:~/idea/demo$ snap list | grep microk8s
microk8s              v1.16.1                     940   edge          canonical*   classic
mike@workstation:~/idea/demo$


[Enhancement]: Grid Map & Maze Generator

Enhancement
Implementing Grid Map, transitioning from existing Hex Map with Maze Generator as an example.
If the request is accepted, would you be willing to contribute it?

[x] Yes I would be willing to contribute

Hi guys, for some reason I can't finish this in near time, I will temporary close this and will get back to it soon 🌚


Fixes #2279 ExecuteInRepl command may let exception escape

Fixes #2279 ExecuteInRepl command may let exception escape
Handles exceptions and displays appropriate user feedback.

👍


Cabana: add save DBC dialog

I think adding a "copy to clipboard" button and a "save as" button to this dialog popup can complete the save DBC feature.

updated:

need test case for this function

fixed precision problem:

tools/cabana/tests/test_cabana.cc:30: FAILED:
REQUIRE( sig[j].factor == new_sig[j].factor )
with expansion:
0.0049015947 == 0.004901595


Script not running

I have a line in my plugin:
Refresh | bash="python3 /Users/zeev/iCloud/bitbar/mint/mint-getData.py" terminal=false refresh=true
which does NOT run when clicked.
It only runs if I set terminal=true

anyone?

I am too busy to help right now, but please read the docs and consult other examples.
https://github.com/matryer/bitbar-plugins/search?l=Python&q=terminal%3Dfalse

I was facing a similar problem this same problem, but just using open: echo "Spotify|bash=open param1=/Applications/spotify.app terminal=false", where terminal=true works
This is the technique I borrowed from the other plugins I was seeing:
if [[ "$1" = "open" ]]; then
  open /Applications/Spotify.app
fi

...

echo "Spotify|bash=$0 param1=open terminal=false"

It's not ideal though, and I couldn't see any documentation for this

I've tried 5 different examples, e.g., showhide-files.1d.py – which does not work.
Thoroughly confused.


Added MirrorTool

Add MirrorTool to Big Data projects and Newest projects.
Remove php-legal-licences from Newest projects

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for adding this @rhysmccaig ! Please just sign the CLA (will be recognized for your project too) and then we can merge this.


Decide whether need to store the NLP Tools results in a DB

A Data Hosting Site with a private dataset won't allow the infrastructure to return the predictions generated by a NLP Tool to the Sandbox backend / Synapse. Currently, we are only considering computing performance metrics like F1 score as part of the processing workflow. However, additional metrics would be useful such as computing confidence interval using bootstrapping and any post analysis that we may thing off. Bootstrapping can be very time consuming with the evaluation of 10,000+ bootstrapped predictions, which is why it has so far never been included as part of the evaluation process.
Here are different options:
A. We don't save the predictions to persistent storage anywhere and we forget about doing additional analysis.
B. We save the predictions to persistent storage INSIDE the private network of a Data Hosting Site. Staff members of the Data Hosting Site could then help performing the analysis and return to the organizers or community only the results that they are comfortable sharing. This non-automatic process means that the returned data would likely not be included in a live leaderboard.

I think we should definitely store the results on persistent storage somewhere just like we do for the EHR challenges.  This way if we do plan to do more analysis, we have the results.

@thomasyu888 In addition of saving the predictions to Synapse as done in other challenges, let's save them to them to the data node.

Create the AnnotationStore named submission-SUBMISSION_ID linked to the Dataset used for evaluation
Push the predicted annotations to the newly created AnnotationStore

This would enable us to then use the Data Node client to easily pull the gold standard and annotation to do additional analysis. Another application I have in mind is to apply a "wisdom of the crowd" algorithm to aggregate predictions generated by different tools!

Thanks @tschaffter!  This was my reason for adding the 'store_annotations' function

I thought this was to store the annotations.

So you were correct, this ticket is about storing predictions (not prediction evaluation).


Maximum update depth exceeded

andriod
Version
Which versions are you using:

1.5.14
0.55.3

the method setState:
scrollBy = (index, animated = true) => {
if (this.internals.isScrolling || this.state.total < 2) return
const state = this.state
const diff = (this.props.loop ? 1 : 0) + index + this.state.index
let x = 0
let y = 0
if (state.dir === 'x') x = diff * state.width
if (state.dir === 'y') y = diff * state.height
if (Platform.OS !== 'ios') {
  this.scrollView && this.scrollView[animated ? 'setPage' : 'setPageWithoutAnimation'](diff)
} else {
  this.scrollView && this.scrollView.scrollTo({ x, y, animated })
}

// update scroll state
this.internals.isScrolling = true
this.setState({
  autoplayEnd: false
})

// trigger onScrollEnd manually in android
if (!animated || Platform.OS !== 'ios') {
  setImmediate(() => {
    this.onScrollEnd({
      nativeEvent: {
        position: diff
      }
    })
  })
}

}
case Exception:
Maximum update depth exceeded. This can happen when a component repeatedly calls setState inside componentWillUpdate or componentDidUpdate. React limits the number of nested updates to prevent infinite loops.

This repo dead: https://github.com/leecade/react-native-swiper/issues/713

I read now .. so bad


[Bug]: route is always null on tour

What happened?
At the moment I am not able to make a tour show up, unless I specificaly set the "ignoreRoutes()" to true on the tour itself.
this is the code I have on my resourceEditPage:
public function tours(): array
    {
        return [
            //this will show
            Tour::make('edit-order')
                ->steps(
                    Step::make()
                        ->title("Showing !"),
                )->alwaysShow(true)
                ->ignoreRoutes(true),

            //this will not show
            Tour::make('ddd')
                ->steps(
                    Step::make()
                        ->title("Not showing !"),
                ),
        ];
    }

I investigated the issue (a bit) and what I can see in the index.js file is:
 if (
                (conditionAlwaysShow && conditionRoutesIgnored) ||
                (conditionAlwaysShow && !conditionRoutesIgnored && conditionRouteMatches) ||
                (conditionRoutesIgnored && conditionVisibleOnce) ||
                (conditionRouteMatches && conditionVisibleOnce)
            ) {
                openTour(tour);
                break;
            }

I guess the default behaviour should be the last statement: the route matches and it has never been shown. However as my tour.route is always null, this condition is always false.
            let conditionRouteMatches = tour.route === window.location.pathname;

not sure what I am doing wrong. Do I have to register my routes where it should be visual manually (in the example given this is not done however). I don't find in the code where the routes are "automagically" set, so I guess I have to do it manually.
How to reproduce the bug
I am not sure how to reproduce this, as I am not sure that I am actually using it right...
Package Version
v<IP_ADDRESS>
PHP Version
8.1.6
Laravel Version
10.20.0
Filament Version
v3.0.31
Which operating systems does with happen with?
macOS
Notes
No response

ok, I think I found out you expect a "slug" attribute on the tenant model. I will see if I can rework this and do a pull request so you can use the id, or defined slug attribute.

I'm a bit struggling with all the requirements to calculate the correct route, because there are tenants, multiples panels, custom pages routes...
That's a functionnality that I need to rewrite, with a clear head.

I completely understand.
I wanted to propose a PR, but I got stuck in the getURL method, I have the feeling there might be a bug on Filament's well when calculating the routes for Resourcepages (edit, list and create)

On 21 Sep 2023, at 18:17, Jibay Mcs @.***> wrote:
I'm a bit struggling with all the requirements to calculate the correct route, because there are tenants, multiples panels, custom pages routes...
That's a functionnality that I need to rewrite, with a clear head.
—
Reply to this email directly, view it on GitHub https://github.com/JibayMcs/filament-tour/issues/5#issuecomment-1729897132, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC7LAWFGA7MCFUNVNUQC23X3RSA5ANCNFSM6AAAAAA475MMRI.
You are receiving this because you authored the thread.

I am interested in fixing

Is working fine to me, the only bug that I have so far is when I'm in the login route, it shows a
-> Error: Call to a member function getTenants() on null in file /var/www/html/vendor/jibaymcs/filament-tour/src/Tour/Traits/CanConstructRoute.php on line 21

digging into it, you are trying to get the tenant from the authenticated user Filament::auth()->user() but at this stage (login) there's no auth user yet. That's why I'm getting this error: Call to a member function getTenants() on null
 $tenants = Filament::getCurrentPanel()->getTenantModel()::find(Filament::auth()->user()->getTenants(Filament::getCurrentPanel()));

digging into it, you are trying to get the tenant from the authenticated user Filament::auth()->user() but at this stage (login) there's no auth user yet. That's why I'm getting this error: Call to a member function getTenants() on null
 $tenants = Filament::getCurrentPanel()->getTenantModel()::find(Filament::auth()->user()->getTenants(Filament::getCurrentPanel()));

did you manage to fix this? I keep getting "Call to a member function getTenants() on null"

digging into it, you are trying to get the tenant from the authenticated user Filament::auth()->user() but at this stage (login) there's no auth user yet. That's why I'm getting this error: Call to a member function getTenants() on null
 $tenants = Filament::getCurrentPanel()->getTenantModel()::find(Filament::auth()->user()->getTenants(Filament::getCurrentPanel()));

did you manage to fix this? I keep getting "Call to a member function getTenants() on null"

No sir, I couldn't... just waiting to see if there's a solution from the author.

Hi all,
I encountered this error today and got around it by adding a check in the tours function to return an empty array if a user isn't logged in:
class ListDocuments extends ListRecords
{
    use HasTour;
    ...

    public function tours(): array
    {
        if (! request()->user()) {
            return [];
        }

        return [
            Tour::make('list_documents')
                ->steps(
                    Step::make('.fi-ta')
                        ->title('Your documents')
                        ->description('This table contains all of your and your teams documents. From here you can edit or delete them'),
                    Step::make('[data-id=new_document]')
                        ->title('New document')
                        ->description('Clicking here will allow you to create a new document')
                        ->icon('heroicon-o-document')
                        ->iconColor('primary'),
                ),
        ];
    }
}

With this change I can use all of the authentication pages without an error and the tours work on the pages I have defined them

Hi ! This bug will be fixed in the next release :)

Fixed here (I hope so): https://github.com/JibayMcs/filament-tour/releases/tag/v<IP_ADDRESS>


Added Block_Ninja Game to the Repository

PR Description 📜
This PR adds the new game "Block Ninja" to the repository. Block Ninja is an engaging and addictive game where players must slash through blocks that appear on the screen while avoiding dangerous obstacles. The game tests the players' reflexes and precision as they aim to score the highest points.
Fixes #3090

Mark the task you have completed ✅

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generate no new warnings.
[x] I have followed proper naming conventions shown in CONTRIBUTING GUIDELINE
[x] I have added a screenshot for website preview in assets/images
[x] I have added entries for my game in the main README.md
[x] I have added README.md in my folder
[ ] I have added a working video of the game in README.md (optional)
[x] I have specified the respective issue number for which I have requested the new game.

Add your screenshots (Optional) 📸

Thank you so much for contributing to our repository 💗

Thank you @SumitKumar-17 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @SumitKumar-17 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Add CI Integration

Updated github actions to run lint and test on CI

@GoogleFeud can we merge this?


Add compat for web logical style props with unit tests

Summary
Adds compat with W3C logical CSS properties. See https://github.com/facebook/react-native/issues/34425
This is a replacement for reverted #34590, which can no longer be imported internally.
Changelog
[General][Added] - Added CSS logical properties.
Test Plan
Unit test snapshots.

This diff was already merged and I've resubmit with a fix and tests. I agree that in the long term all the props and styles should be done in native, but in the meanwhile they've all been done in JS. I don't think we should block this patch after already merging 30+ props and styles also shimmed in JS

I know it was merged before, but I would still like to review the change 😉.
There are negative properties of JS shimming as a solution for layout properties specifically. It adds newly inconsistent behavior for native components (you can flexbox layout arbitrary native views), along with some debt in our components. It also means we need to rebuild a solution once Yoga supports the shorthand.
None of this is the end of the world, but this seems to be building a foundation for more changes. If we are adding more of these, we can avoid a lot of debt, rework, and correctness issues if we instead implement these layout properties as a couple of switch cases in native (and I am willing to add those).

@NickGerleman This diff contains tests needed to meet an internal SLA. What do you want to be changed in order to get this merged ASAP? Shall I remove the layout prop shim in favor of the draft PR you posted?

@NickGerleman This diff contains tests needed to meet an internal SLA. What do you want to be changed in order to get this merged ASAP? Shall I remove the layout prop shim in favor of the draft PR you posted?

Yeah, I'd prefer we hold off on merging the layout reprojection portion until a couple more details get ironed out. But I would sign off the rest, being the tests and fixes for existing implemented props.


ENH: Update percentile dask chunking

Pull Request Checklist:

[x] This PR addresses an already opened issue (for bug fixes / features)

This PR is related to #932

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
[x] HISTORY.rst has been updated (with summary of main changes)

[x] Link to issue (:issue:number) and pull request (:pull:number) has been added.

[ ] bumpversion patch has been called on this branch
[ ] The relevant author information has been added to .zenodo.json

What kind of change does this PR introduce?
This PR make sure percentile_doy rechunking preserve the initial chunk size.
Currently, percentile_doy multiply the size of chunks by at least window width (default 5).
This size increase can even be larger because the time dimension initial chunking is lost in percentile_doy rechunking.
This PR fix this by chunking dayofyear dimension in window * time_chunk_count chunks.
Using dask dashboard I see the memory peak use being reduced by about 30% for a mono-threaded launch with theses changes,
However, I expected a bigger reduction of memory use.
The performances seems to also improve, even though dask exhibits a new warning: PerformanceWarning: Slicing with an out-of-order index is generating 36 times more chunks
I'm not sure what this warning is about, it comes from [dask slicing].(https://github.com/dask/dask/blob/main/dask/array/slicing.py#L630)
I suspect the performance improvement is mainly due to fewer I/O tasks for spilling and reading memory on disk.

Test Script
client = Client(memory_limit='16GB', n_workers=1, threads_per_worker=1)
big_tas_file = "../icclim/netcdf_files/tas_day_INM-CM5-0_ssp585_r1i1p1f1_gr1_20650101-21001231.nc"
da = xr.open_dataset(big_tas_file).tas
dask.config.set({"array.chunk-size": f"{200} MB"})
chunking = {d: "auto" for d in da.dims}
# chunking["time"] = -1
da = da.chunk(chunking)

da_per = da.sel(time=slice("2065-01-01", "2094-12-31"))
tas_per = percentile_doy(da_per, window=5, per=90)
a = xc.atmos.tg90p(tas=da, t90=tas_per, freq="MS", bootstrap=False)
a.compute()

Does this PR introduce a breaking change?
No.
Other information:
I'm putting this in draft for now as I would like to do a few more tests.
Any feedback would be also appreciated.

Fichtre.
It doesn't work when input has leap years. adjust_doy_calendar calls a apply_ufunc dayofyear as a core dim...

Leaving draft!
Performances and memory looks good.
Christian is doing a few more test with real data but I think it can be reviewed as is.

Coverage increased (+0.001%) to 91.455% when pulling 52231fd6a42911c0c34c6a3aa6c488e080d18ff3 on enh/perc_doy_rechunk into 7686259ef0de440fbd5ef92b25048219b1215410 on master.

Feel free to merge when you're ready! Thanks again!

Thanks guys for the review !


Don't delete label after deleted all of nodes and relationships.

how to remove all label in with a query?
I delete node and relationship before.

Hello @kienbui1995
I'm not positive that I understand your problem. Is the situation that you have a Neo4j database, in which you have deleted all nodes and relationships, and you are now looking to also delete the tokens that Neo4j keeps as representations for labels and relationships?
If my interpretation is correct, I'm afraid the answer is that you can't. But that is not as bad as it sounds. These tokens existing in the database does not impact database performance or behaviour. If it is absolutely necessary, you could simply delete the database directory (default located in data/databases/graph.db), since your graph is empty already.
Should you have any additional problems with this situation, I think it would be more appropriate to raise an issue on the Neo4j repository, as this is more a database concern than a query language concern. From Cypher's point of view, a label or type does not exist if no entity (node or relationship) is associated with it.

Sure. I will close this issue and yesterday  I created a issue on the Neo4j repository.


Split creating media from creating post

Also fix

Media upload size limit bug, e.g. it counted total of all media instead of individual media
Image uploading UI

Resolved in #437


Mark lifecycle with 100% QE test coverage

Can you remove the changes here as well?

Just leave the QE flag change and that should be good-to-go.

This is how the lines look like.


Can't deploy to Heroku

Hello,
I'm trying to deploy Hours to Heroku but I keep receiving the error 'No such add-on plan.' related to 'pg-backups'. Can you please remove this add-on from the app.json file or advise on how to address this issue?

Ah, it looks like a typo, it should be pgbackups. Would you mind opening a PR with the change?

Sure thing!


Dismiss gesture

I just learn swift. I don't know how to dismiss gesture. I want to hide menu left when I touch on table of menu left and stay on main screen. Can you give me an example about it ?

/// The left menu swipe to dismiss gesture.
open static weak var menuLeftSwipeToDismissGesture: UIPanGestureRecognizer?

Sorry, I'm not your teacher. Everything is in the README. You'll have to figure this out or try stackoverflow.com.


Docs: tsconfig.json is not a json5 file

Page URL: https://www.typescriptlang.org/docs/handbook/declaration-files/dts-from-js.html
Issue:
tsconfig.json is not a json5 file, it is a jsonc file.
Therefore, tsc cannot recognize the example in the page.
Recommended Fix:
{
  // Change this to match your project
  "include": ["src/**/*"],

  "compilerOptions": {
    // Tells TypeScript to read JS files, as
    // normally they are ignored as source files
    "allowJs": true,
    // Generate d.ts files
    "declaration": true,
    // This compiler run should
    // only output d.ts files
    "emitDeclarationOnly": true,
    // Types should go into this directory.
    // Removing this would place the .d.ts files
    // next to the .js files
    "outDir": "dist",
  },
}

I see your recommended fix would be to only change the wording in the sentence before: The TSConfig is a json5 file... from file to jsonc.


Is there any way to prevent the search field from clearing on focus?

Define a searchable component.
Search a term and accept the selection
Click the search field again
The previously selected term is removed.

I'd like to prevent the search field from clearing. Is there any clean way to do it? I think I could listen to events and restore the state manually, but it feels a bit hacky to me.

Sadly it is not possible at the moment.

That would be nice to have. But I think, doing type-ahead would require a whole lot of remodeling.

Type-ahead should return string, while options could be an array of strings or objects.
Typed text should persist at all times.

That's not the case for vue-multiselect at the moment.
Might be worth to make another library. BTW, there is one. Not sure about its quality or usefulness though.

There will be a new prop preserveSearch that preserves the search query through opening/closing the select. Will be available in the next release.

Useful option, however the search is not preserved after selection, is there a way to do that ?

Useful option, however the search is not preserved after selection, is there a way to do that ?

Useful option, however the search is not preserved after selection, is there a way to do that ?

As said in the docs you can use

:clear-on-select="false" – the search query stays the same after selecting an option

Well the prop docs actually says

Clear the search input after select(). Use only when multiple is true.

While I was talking about a non multiple select here, it's not keeping the search on a multiple either, maybe I have another incompatible prop

Interesting, I am using the same version 2.1.6, and clear-on-select prop is working as expected with both single and multiple
Here is my config:
<multiselect
    v-model="editingItem.mxikCategoryCode"
    class="custom-multiselect"
    :class="[
		    !!errors.length ? 'invalid' : '',
		    valid ? 'valid' : ''
    ]"
    label="mxikCategoryNameUz"
    :custom-label="customLabel"
    placeholder="MXIK search"
    open-direction="bottom"
    :options="mxikCategories.map(cat => cat.mxikCategoryCode)"
    :searchable="true"
    preserve-search
    :clear-on-select="false"
    :loading="isLoadingMxik"
    :internal-search="false"
    :hide-selected="false"
    :options-limit="300"
    :limit="3"
    :max-height="600"
    :show-labels="false"
    @search-change="debounceSearchMxikCategories"
    @select="mxikCategorySelected"
    >
    Hech qanday element topilmadi. Qidiruv so'rovini o'zgartirib ko'ring.
</multiselect>```

I think you should use preserve-search prop as well, set it to true.
From docs:

preserveSearch | Boolean | false | If set to true, will preserve the search query when opening/closing the component.

Crutch solution
<multiselect v-model="value"
....
:class="`el_${parentIndex}_${index}`"
@open="presetValue"
/>

methods: {
presetValue() {
        if (this.v.title)
                this.$nextTick(() => $(`.el_${this.parentIndex}_${this.index} input`).val(this.v.title));
        }
}

Here is my solution:
<multiselect
    ref="multiselect"
    v-model="search_text"
    :multiple="false"
    :preserve-search="true"
    :clear-on-select="false"
    @open="open"
/>

methods: {
  open() {
    this.$nextTick(() => {
      this.$refs.multiselect.search = this.search_text
      this.$refs.multiselect.placeholder = this.search_text
    });
  },

@donnyv try :can-clear="false"

clear-on-select="false" or clear-on-select="true"
It's working. Thank you so much everyone.


printWidth setting is ignored when max-len ESLint rule is explicitly disabled

Given ESLint rule max-len: 0 (explicitly disabled) and a prettier.printWidth setting (e.g. 80), this extension ignores the prettier.printWidth setting and instead uses the fallback (80).

Potentially related https://github.com/prettier/prettier-eslint/issues/97

Seems highly related to me

just published an updated version with your fix ;-)


rename changelog entry

#687 changelog entry had the wrong number in the filename

o crud the mock e2e regression test workflow has the wrong names


#5 Added Botalka service design document

We can replace Telegram completely with some queue, where we will send events.


Wire up reading file for signing command

A fix for https://github.com/github/smimesign/issues/50
Add logic to read file from command line for signing command in parallel to verify command.

After you merge this, would you mind trying out the release process I'm documenting in https://github.com/github/smimesign/pull/52? We can create a v0.0.11 with with this fix.

After you merge this, would you mind trying out the release process I'm documenting in #52? We can create a v0.0.11 with with this fix.

Sure!


Error Installing on Windows 10

Following the instructions for new version (with plugin), I get an error when installing homebridge, but homebridge-http installs fine.
Code:
1387 error Command failed: git -c core.longpaths=true clone --template=C:\Users\Nick\AppData\Roaming\npm-cache_git-remotes_templates --mirror git://github.com/KhaosT/node-curve25519.git C:\Users\Nick\AppData\Roaming\npm-cache_git-remotes\git-github-com-KhaosT-node-curve25519-git-750fb09d
1387 error Cloning into bare repository 'C:\Users\Nick\AppData\Roaming\npm-cache_git-remotes\git-github-com-KhaosT-node-curve25519-git-750fb09d'...
Any help?

It's also throwing the same errors for node-srp and ed25519.

Installed dependency packages one by one.  bignum and srp were the biggest trouble makers, srp is unable to be installed by npm.  git clone and npm link were my work arounds.

I had the same problem on my new system. There seems to be a problem of Node.JS 4.x.x.. I have updated the installtion instructions. To which i have yet elemeniert other bugs at the installtion instructions.
=> https://github.com/nfarina/homebridge/wiki/Install-Homebridge-on-Windows
Greeting
Patcher


Cannot generate importc statements using Nim templates.

So I'm trying to generate individual nim wrapper files for each header in a library (libDragon, to be specific), and I figured the best way to go about this was to create a template that I could call that would be expanded before compiling, but it doesn't seem to work, giving the following error:
chris@stanford:~/gits/Nimtendo64/src$ nim c create_wrapper.nim
Hint: used config file '/home/chris/.choosenim/toolchains/nim-#devel/config/nim.cfg' [Conf]
Hint: used config file '/home/chris/.choosenim/toolchains/nim-#devel/config/config.nims' [Conf]
..............................................................................................................................................
stack trace: (most recent call last)
/home/chris/.nimble/pkgs2/futhark-0.13.6-3483cfec18042ba11474675ec7a3648492e4d583/futhark.nim(656, 19) importc
/home/chris/gits/Nimtendo64/src/create_wrapper.nim(12, 11) template/generic instantiation of `wrapHeader` from here
/home/chris/.nimble/pkgs2/futhark-0.13.6-3483cfec18042ba11474675ec7a3648492e4d583/futhark.nim(656, 19) Error: node lacks field: strVal

Here's the template I wrote:
template wrapHeader(name: string): untyped =
    importc:
        outputPath "Nimtendo64" / name & ".nim"
        path n64_inst
        name & ".h"

Even if you solved the initial problem you'd be very likely to run into further issues using Futhark that way. What I'd recommend instead is using project mode. What it allows you to do is simply specify all the paths you want to wrap, and then it will wrap all the header files in those paths and recreate the same folder structure. Your example would be something like:
importc:
  outputPath "Nimtendo64"
  path n64_inst # Assuming this is a constant holding the path to a folder

Then every header file in the folder pointed to by n64_inst would get wrapped into separate Nim files and placed in the "Nimtendo64" folder.

Awesome! Thank you! One problem with project mode, however, is that those header files are stored alongside other header files, as they're part of a toolkit. I'll have to figure something out. Currently, I have separate importc statements, and that one seems to fail on one of the header files, though that's a separate issue.

Well you can always use the ignore function to ignore header files you don't want to wrap.

Actually, maybe I could do that to ignore the c++ folder, which seems to be the biggest issue when trying to use project mode.

Am I using ignore correctly, here?
importc:
    outputPath "Nimtendo64"
    path n64_inst
    ignore "c++"
    ignore "libdragon.h"

Hard to tell without knowing the folder structure, but ignore needs to be relative to the project being compiled, or absolute. I typically have something like:
const relPath = currentSourcePath().parentDir

importc:
  path relPath / "cfiles"
  ignore relPath / "cfiles" / "somefolder"


individual Section in sections do not exec block

Issue to raise for SitePrism framework
  section :my_section, MySection, 'div.locator'

  @page.my_section do |section|
    section.something # executes
  end

 sections :my_sections, MySection, 'div.locator'  #

  @page.my_sections.first do |section|
    section.something # does not execute block
  end

While the second behavior is not explicitly documented, one would it expect it to work since :sections is in many ways an Array-like of :section.  Not sure whether this should be considered a bug or feature-request, but failing to execute the block could lead to incorrectly-passing tests.
Environment

OSX
SitePrism itself at recent master 4c568ddf7029273fcb02c3230b21a82b11d54c44
SitePrism's own cucumber scenarios
firefox default

Expected Behavior
We can exec inside a section similar to Capybara within functionality on an individual section.  But on an array of sections generated by :sections this does not work.
I expected that my block would be executed when passed as @page.my_sections {|s| raise 'ermagerd'}
Actual Behavior
Code in the block is not exec'd
Steps to reproduce

clone https://github.com/tgaff/site_prism/tree/tg/sections_dont_exec_blocks
cucumber -r features
observe test failure

cucumber scenario
In the below I verify that on the Section features we do execute the contents of the block.
However when it comes to the Sections features, the same functionality fails - the block is not executed.  Specifically the tests fail with:
    Then I can execute in the context of a section using a block # features/step_definitions/sections_steps.rb:22

      expected: 2
           got: 0

      (compared using ==)
       (RSpec::Expectations::ExpectationNotMetError)
      ./features/step_definitions/sections_steps.rb:39:in `"I can execute in the context of a section using a block"'
      features/sections.feature:21:in `Then I can execute in the context of a section using a block'

Failing Scenarios:
cucumber features/sections.feature:19 # Scenario: access elements in the section by passing a block

91 scenarios (1 failed, 90 passed)
229 steps (1 failed, 228 passed)
0m23.693s

Patch that reproduces this behavior
diff --git a/features/sections.feature b/features/sections.feature
index 1705336..4f9aee8 100644
--- a/features/sections.feature
+++ b/features/sections.feature
@@ -15,3 +15,7 @@ Feature: Interaction with groups of elements
   Scenario: anonymous sections collection
     When I navigate to the nested section page
     Then I can see a collection of anonymous sections
+
+  Scenario: access elements in the section by passing a block
+    When I navigate to the nested section page
+    Then I can execute in the context of a section using a block
diff --git a/features/step_definitions/section_steps.rb b/features/step_definitions/section_steps.rb
index a56cd57..45e5bb0 100644
--- a/features/step_definitions/section_steps.rb
+++ b/features/step_definitions/section_steps.rb
@@ -12,13 +12,19 @@ Then('I can see a section in a section') do
 end

 Then('I can access elements within the section using a block') do
+  block_inner_executions = 0
+
   expect(@test_site.home).to have_people

   @test_site.home.people do |section|
+    block_inner_executions += 1
+
     expect(section.headline.text).to eq('People')

     expect(section).to have_individuals(count: 4)
   end
+
+  expect(block_inner_executions).to eq 1
 end

 Then('I cannot access elements that are not in the section using a block') do
diff --git a/features/step_definitions/sections_steps.rb b/features/step_definitions/sections_steps.rb
index f57cbe7..4e1f0c9 100644
--- a/features/step_definitions/sections_steps.rb
+++ b/features/step_definitions/sections_steps.rb
@@ -17,3 +17,24 @@ Then('I can see a collection of anonymous sections') do

   expect(anonymous_sections.size).to eq(2)
 end
+
+
+Then('I can execute in the context of a section using a block') do
+  block_inner_executions = 0
+
+  expect(@test_site.nested_sections).to have_search_results(count: 4)
+
+  @test_site.nested_sections.search_results.first do |sec|
+    block_inner_executions += 1
+    expect(sec).to be_an_instance_of(SitePrism::Section)
+    expect(sec).to have_text('Result 0')
+  end
+
+  @test_site.nested_sections.search_results.last do |sec|
+    block_inner_executions += 1
+    expect(sec).to be_an_instance_of(SitePrism::Section)
+    expect(sec).to have_text('Result 3')
+  end
+
+  expect(block_inner_executions).to eq 2
+end

Definitely a bug. If you've got bandwidth feel free to dig in. It's likely that the area in which it will need looking is around here: https://github.com/natritmeyer/site_prism/blob/master/lib/site_prism/dsl.rb#L116
This map which creates the constructor (per se), is not passing the defined runtime block (Furthermore we make the check for element block - as intended).
To me this "may" be a 1line fix? But I've not got time to investigate as I'm deep into this recursion stuff.

I'll try to figure it out.  Might not be till next week though.  Wanted to make sure we intend to support this as a feature first.  Sorry I've been so busy!

No probs. I'm likely to be making a new subgem for all the work I've been getting into with the recursion work, as it's seen me dive into a whole new inheritance / class structure. So just do what you can

Hmm, I'd be interested to know more about that structure and whether it might be applicable to this bug.
From what I'm seeing here now I have a suspicion that this isn't a trivial fix.
I'm either going to need to add a Section#within method and use that instead of exec'ing the block in initialize or implement an iterable replacement for the array of sections we use, e.g. a SectionCollection class.

You've actually exposed a larger issue (Which I'm not sure is explicitly tested). Which is the raise_if_block check doesn't seem to be working!

See #397 for a similar issue. Both of these are separate bugs though. I'm making a deprecator class to triage these and we can then start firing warnings / fixing as we deem fit.

Yeah I noticed.  I'm wondering why we'd want to prevent a block there though.  We support both run-time and define-time blocks on section, so I'm not sure if this code just snuck through or if there was real intent here to prevent blocks.

those blocks are never parsed and they're ignored. For now I'm going to put in a soft-deprecation to ban that code in 2 major versions time. Next version will warn users to remove them.
A lot of this is just edge cases which are likely to have been missed.

@tgaff are you working on this?

I need to be.  I haven't been.  :-/  sorry.
So I had two thoughts on how to tackle this AND keep the current expected functionality.

Build a SectionCollections class that implements all the usual array methods :[], :first, :last, :map but passes around the blocks as needed.

OR

deprecate the current style of passing a block directly to a section and add a .within (or similar) method on sections that does take a block.  That way when you have my_sections.first.within {|s| } the block can be executed in the right context.

I think I prefer #2 since it's more similar to Capybara (which many users already have experience with) and is almost certainly easier to implement/maintain.

Why don't you just pass the block into the existing method as it's done for the others. I had a quick play and it should just work with a 1/2liner change.

Any updates on this @tgaff ?
Just reviewing the status' on this (the old repo)

Kamino closed and cloned this issue to site-prism/site_prism


for_sensors_results branch erorr

ERROR - orsum - Failed after 0:06:15!
Traceback (most recent calls WITHOUT Sacred internals):
File "run.py", line 454, in train
run.finish()
AttributeError: 'Run' object has no attribute 'finish'

Updating wandb to recent version will fix this.


Enable workspace lint missing_docs

Ensures that the windows-core crate docs are generated correctly.

The CanInto trait is internal and should not be documented.
The new VARIANT and PROPVARIANT types are public and needed a basic description.

Getting a little frustrating that I keep getting some warnings only show up on ubuntu builds and not reproducible on Windows. Anyone else seeing this? @riverar @ChrisDenton

It might be "user error" in this case - I keep forgetting about the silly docs feature...

It might be "user error" in this case - I keep forgetting about the silly docs feature... #2676

Ah. Hopefully we can remove that sometime this year. The Cargo feature to replace it should be in edition 2024.


Overlapping in MeetingRow at big text sizes

Bug Report
Problematic behavior
Increasing text size in MeetingRow make the "Join" button and the meeting name overlap, even if there is still enough space for both (see screenshots).
The problem may appear sooner with long meeting names
Expected behavior/code
No overlapping
Steps to Reproduce
See the storybook !
Additional context/Screenshots

Hi,
From what I can see their is no more MeetingRow in the repo. I guess it was replaced by RoomRow, should we close the issue ?


Suport building for other distros/releases

This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] create a file in news/unreleased directory if this change should be mentioned in the release news
[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

[ ] 1st commit of any rhbz# related PR contains bug reproducer; CI reports FAIL or
[ ] PR contains automated tests for new functionality and
[ ] QE has approved reproducer/new tests and
[ ] Subsequent commits provide bug fixes without modifying the reproducer; CI reports PASS and
[ ] QE approves this PR; RHBZ status is set to MODIFIED + Verified=Tested

(leaving the above alone for now)
What we have here is a bunch of changes that make it possible to build images for all the other supported distributions.
The blueprint now supports a distro field that tells it which distro to build for when a compose is started. If it is missing it builds for the host system's distro.
You can list supported distros with curl --unix-socket /run/weldr/api.socket http://localhost:4000/api/v1/distros/list | python -m json.tool -
{
    "distros": [
        "centos-8",
        "fedora-32",
        "fedora-33",
        "rhel-8",
        "rhel-84",
        "rhel-90"
    ]
}

Routes that could return different results based on distro selection now support an optional ?distro=DISTRONAME parameter.
This includes compose/types since image types are implemented per-distro there may be a different set available.
FYI - composer-cli has not been updated to support any of these new features. You can still use it to push a new blueprint though, it doesn't care what the content is.
Currently this doesn't limit what you can build. In production I think we want to limit building to similar releases of the host's distro (although, in my fedora-33 VM I can successfully build a centos-8 image). We need to figure out what these limits are, and they may be limited for support reasons more than technical reasons.
This does not include any changes to the sources API or TOML yet. The plan there is to default to supporting the host distro, or adding a distros list to the source to list the distros it supports. Possibly with wildcard? eg. distros="fedora-*"
Some of these commits still need cleanup and documentation. But this 'snapshot' of things builds, passes tests, and can build other distros, depsolve, etc.

Thanks for all this work @bcl! Nice to see how quickly this came together.
Regarding the open question about which distros should be supported where, I think we have two options:

basic version: only the host distro on itself (Fedora on Fedora, RHEL on RHEL)
stretch goal: upstream builds downstream (Fedora, CentOS and RHEL on Fedora; CentOS and RHEL on CentOS; RHEL on RHEL)

We'd have to make sure we get the messaging right for option 2, but I think it could be very powerful.
@msehnout, @thozza and @ondrejbudai, we had a discussion about the subscription story, and my understanding was that subscribing non-RHEL hosts should work just fine, so as long as we do the integration right, the above will "just work". Did I get that right?

Yes, you can subscribe Fedora and CentOS Stream. On my subscribed Fedora, I have a keypair in<PHONE_NUMBER>72977190.pem but I'm not entirely sure which repos I can access with it. I know that when I'm running ubi in a podman, I can access RHEL repositories in the container so the keypair is definitely valid. As @thozza pointed out, subscriptions without Simple Content Access might make this more difficult.

@teg @ondrejbudai let me check with the subscription-manager team to make sure we have accurate information, because I literally have no way to verify the behavior without SCA.

It is possible to subscribe Fedora and get RHEL content. For example using my subscription I can invoke:
$ curl --head --cacert /etc/rhsm/ca/redhat-uep.pem --cert /etc/pki/entitlement/6074731247270028676.pem --key /etc/pki/entitlement/6074731247270028676-key.pem https://cdn.redhat.com/content/dist/rhel/atomic/7/7Server/x86_64/cdk/3.3/os/repodata/repomd.xml
HTTP/1.1 200 OK

And get access to RHEL7 content.

See #1427


Avoid scaling triggered by events/messages when ScaledObject is paused

Signed-off-by: Sanskar Jaiswal<EMAIL_ADDRESS>
Fixes the issue of a ScaledObject scaling up/down based on the incoming events/messages when it's paused.
Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)
[x] Tests have been added
[ ] A PR is opened to update our Helm chart (repo) (if applicable, ie. when deployment manifests are modified)
[ ] A PR is opened to update the documentation on (repo) (if applicable)
[ ] Changelog has been updated and is aligned with our changelog requirements

Fixes #3009

/run-e2e

/run-e2e

/run-e2e

/run-e2e

/run-e2e

/run-e2e

wow, thanks a ton @v-shenoy , you have given me the starting point. ❤

please @aryan9600 ,
rebase main into your branch, we have fixed the problem with e2e tests

/run-e2e

/run-e2e azure*

/run-e2e azure*

/run-e2e

Could you update the changelog too please?


Question: when should I use a custom scene object over a custom visualization?

Please let me know if there's a better forum for this conversation, happy to redirect elsewhere!
I'm working on a custom panel in a scene app that displays query data. I first implemented the panel as a CustomSceneObject, but ended up with formatting issues putting the object into a SceneFlexLayout - the width and height would overflow and didn't scroll nicely.
After reading the docs on custom visualizations, I decided to rewrite the panel as a custom visualization. It looks a lot better, but now I'm not sure of the best way to interact with the sceneGraph to look up variables and ancestors. Additionally, I'm having trouble rendering data links correctly in this visualization -- the ${__value.text} macro isn't being interpolated.
Do you have a suggestion or reference implementation for interacting with the scene graph from a custom visualization? Or should I move back to the custom scene object model?

The ${__value.text} has been implemented, see here https://github.com/grafana/scenes/blob/main/packages/scenes/src/variables/macros/dataMacros.ts#L45

Im not sure of the best way to interact with the sceneGraph to look up variables and ancestors

We have yet to add a scene context ability to visualization components, it will likely be exposed via the new SceneContext added recently (still work in progress)
what you can do in the meantime get the root scene node from window.__sceneObject , or it should also be present in the data passed via PanelProps (data.scopedVars.__sceneObject.value)


App won't work in local Grafana installation

I'm running Grafana on-premise and the application installs nice and smooth via grafana-cli plugins install ns1-app
Configuring the plugin is also very easy since it only asks for both my Grafana API key and my NS1 API key.
But after that, the generated dashboards won't work since there is something funky going on with the authentication with the datasources created by the app.

raintank
raintankEvents
These are the two datasources created but they somehow won't work. I guess it's trying to reach to a certain endpoint in the API that doesn't exist or needs some sort of authorisation? I have tried setting the Basic HTTP auth for both data sources but to no avail.

Specs:
 Grafana v4.4.2 (commit: 6d9cbdd)

Have same issue.
Installed via the instructions: https://grafana.com/plugins/ns1-app/installation
App, datasources and dashboards appear, with no data (the setup process was intelligent enough to tell me what specific NS1 permissions were missing (manage account, really?), and this was done... so don't think it is permissions of API user).
Server version is:  Grafana v4.4.3 (commit: 54c79c5)
App version is: ns1-app @ 0.0.5

We're having this same issue - it'd be very handy to see NS1 metrics from our grafana as part of a unified source of data, rather than having to log into the site itself - is this app even still under development?

Well, are you sure to have created tasks ?
Each zone need that you create a task (see Dashboard «add task»), to collect data.


Null safety migration

Fixes #15 :)

Hi @Jjagg, huge thanks for proposing the migration. I have been quite busy at work and I did not have much time to read all the new stuff that comes with the recent release of Flutter 2, but I want to update my packages and personal projects to null safety now that Flutter 2 is out in the stable channel.
So expect to have this MR reviewed pretty soon. Thanks again for your work on this.

No worries :)

Hi @Jjagg, you've done just what I would have done if I had done the migration myself, so huge thanks for this. I'm going to review the documentation, README etc. and update it for the null safety version, and publish the null safe version of the package after that.
Thanks for contributing!

Awesome! You're very welcome 😉
Thanks for the great package!


Absolute imports do not work when Yarn PnP is enabled

I created a React App using create-react-app with PnP enabled.
npx create-react-app pnp --use-pnp
Then following the documentation, I created a jsconfig.json file to enable absolute imports.
https://create-react-app.dev/docs/importing-a-component/#absolute-imports
 {
  "compilerOptions": {
    "baseUrl": "src"
  },
  "include": ["src"]
}

When I use absolute imports, the compiler fails to resolve those. Changing the imports to have relative paths work. Just to see whether this is PnP related, I deleted the '.pnp.js' file and removed the relevant config from package.json as well. Then it worked fine. So I assume this is PnP related.
Environment: create-react-app v3.2.0 on Mac OS X Catalina

Can reproduce!

For people coming from search engines, I think this is the issue to subscribe to: https://github.com/yarnpkg/berry/issues/589

@hlian Thanks for the confirmation and sharing the related issue with regards to Typescript. However, I see this issue with regular JavaScript as well. It seems yarnpkg/berry#589 is Typescript specific.

Also just ran into this. @nickmccurdy assuming a monorepo with packages/bar and packages/foo, using "foo": "link:../foo" "foo": "workspace:packages/foo" in packages/bar/package.json dependencies results in the same error. Am I doing it wrong?

This may work in a single repo, but not working with typescript + monorepo

It seems like this should work with Yarn 2 as long as workspaces aren’t used https://github.com/yarnpkg/berry/issues/589#issuecomment-573617227


unable to create session: invalid ClusterSecretStore: missing AWS AccessKeyID Namespace

Good evening guys, how are you ?
I'm trying to create a ClusterSecretStore using the following configuration
apiVersion: external-secrets.io/v1alpha1
kind: ClusterSecretStore
metadata:
name: saccarclusterstore
namespace: kube-system
spec:
provider:
aws:
service: SecretsManager
region: sa-esat-1
auth:
secretRef:
accessKeyID:
name: awssm-secret
key: access-key
namespace: kube-system
secretAccessKey:
name: awssm-secret
key: secret-access-key
namespace: kube-system
But the following error is displayed.
unable to create session: invalid ClusterSecretStore: missing AWS AccessKeyID Namespace
When checking the created object, I noticed that the clustersecretstore is not receiving the secret value
spec:
provider:
aws:
auth:
secretRef: {}
region: sa-esat-1
service: SecretsManager
I'm using openshift 4.8, installed via helm.
Same scenario when installed via operator

hey, first thing: the region sa-esat-1 should be sa-east-1, right?
Could you please provide a properly formatted yaml? I bet it's a indentation issue.

Hi @fscojr ! Is your issue still ongoing?


Long generated URLs result in 503

See if the issue can be fixed now that we are using HttpClient.
https://tweetinvi.codeplex.com/workitem/2240

user_ids.txt


Create Standard Issue Templates for Projects

@EbonyLouis raised: "Can we create issue templates for all projects"?
Issue templates are done in GitHub by simple Markdown files in .github/ISSUE_TEMPLATE. We could add some starter ones to the https://github.com/TBD54566975/tbd-project-template repo, and issue PRs into existing projects.
Example of issue template:

In use: https://github.com/TBD54566975/collaboration/issues/new?assignees=&labels=To-Be-triageD&template=-proposal----open-source-programs.md&title=[PROPOSAL]+-+Your+Idea+Here
Backing file: https://github.com/TBD54566975/collaboration/blob/main/.github/ISSUE_TEMPLATE/-proposal----open-source-programs.md

To be vetted by stakeholders, particularly in OSE, and if approved create issue for this in tbd-project-template.

@EbonyLouis and I slating for Phase 4 as a stretch

Descoping off Phase 4

@EbonyLouis provided: https://github.com/TBD54566975/tbd-project-template/pull/18


use k8s.io/cri-api v0.25.x

v0.26.x breaks compatibility with containerd v1.5. Revert https://github.com/inspektor-gadget/inspektor-gadget/pull/1392 and use the latest v0.25.x release of k8s.io/cri-api.
Fixes https://github.com/inspektor-gadget/inspektor-gadget/issues/1484

The change is looking good but we should plan when do we want to switch to cri api v1 ? I see following state for different projects:

Kubernetes - Removed support for v1alpha2 from v1.26.0
CRI-O - Removed support for v1alpha2 from v1.26.0
Containerd - Plans to remove support of v1alpha2 from v2.0

Since we talking to cri-o/containerd using CRI makes sense to define a timeline to support containerd v2.0 and cri-o v1.26.0+.    How about creating a support matrix for supported CRI version for ig and drop v1alpha2 support after couple of releases with a deprecation notice?

Great analysis @mqasimsarfraz. This is a tricky situation for Inspektor Gadget, we want to support as many as possible scenarios. I'm wondering if there is a way to keep supporting both (v1 and v1alpha2) at the same time. I'd be great to keep supporting users that can't update to v1 too. I'll merge this and open an issue to study this.


sqlx::test error message incorrectly implies migrate feature is disabled

Bug Description
Summary
Error message implies that the "migrate" feature isn't enabled when it actually is. When the feature isn't enabled, the error doesn't mention that it's necessary.
Detail
I am receiving the following error message when I use cargo test:
error: control attributes are not allowed unless the `migrate` feature is enabled and automatic test DB management is used; see docs

This error is generated on test_attr.rs:36:
    if input.sig.inputs.is_empty() {
        if !args.is_empty() {
            if cfg!(feature = "migrate") {
                return Err(syn::Error::new_spanned( // <--- line 36
                    args.first().unwrap(),
                    "control attributes are not allowed unless \
                        the `migrate` feature is enabled and \
                        automatic test DB management is used; see docs",
                )
                .into());
            }

            return Err(syn::Error::new_spanned(
                args.first().unwrap(),
                "control attributes are not allowed unless \
                    automatic test DB management is used; see docs",
            )
            .into());
        }

        return Ok(expand_simple(input));
    }

However, my setup DOES include the default migrate feature.
Cargo.toml
[package]
name = "test-rust2"
version = "0.1.0"
edition = "2021"

[dependencies]
sqlx = { version = "0.7.4", features = ["runtime-tokio-rustls"] }

🕙 00:54:42 ❯ cargo add sqlx --dry-run
    Updating crates.io index
      Adding sqlx v0.7.4 to dependencies
             Features:
             + _rt-tokio
             + any
             + json
             + macros
             + migrate
             + runtime-tokio
             + runtime-tokio-rustls
             + sqlx-macros
             + tls-rustls
             24 deactivated features
warning: aborting add due to dry run

The code above appears to give the extra "unless the migrate feature is enabled" wording only when… the migrate feature is enabled. (if cfg!(feature = "migrate")) However, the time when that caveat is relevant is when the migrate feature is not enabled. Otherwise, the error should just point to "automatic test DB management" as the issue.
Minimal Reproduction
Cargo.toml as above, with main.rs:
fn main() {
    println!("Hello, world!");
}

#[cfg(test)]
mod tests {
    #[sqlx::test(migrations = "../sibling-dir/migrations")]
    fn name() {
        assert_eq!(1, 1);
    }
}

Info

SQLx version: 0.7.4
SQLx features enabled: default, and runtime-tokio-rustls
Database server and version: Irrelevant
Operating system: macOS
rustc --version: rustc 1.78.0 (9b00956e5 2024-04-29)

Also experiencing this issue, though only when the fixtures argument is passed. It does not occur with a plain sqlx::test macro.
Does not cause the error message: #[sqlx::test] (Migrations are applied successfully, in this case.)
Causes the error message: #[sqlx::test(fixtures("graphs")]

Yep, the code path that leads to the incorrect error is only triggered when the test macro has arguments. And adding one of the various arguments to the function enables Automatic Test DB Management, which means the error is no longer necessary.


Switch to PacketEvents

I suggest switching from ProtocolLib to PacketEvents 2.0.
It's faster, works with 1.7-1.18, much easier to use and can be shaded instead of requiring ProtocolLib installed on the server.

Hey, thanks for your suggestion, but because of the current api structure, it's not that easy to replace ProtocolLib, as it is referenced in some parts of the api. And it should be possible to relocate and shade ProtocolLib too. Either way the dependency on a library like this is not that great.


Replace all "Terms and definitions" preview images with Clause 3

In author/topics/document-format/section-terms.adoc
All the images are showing "Terms and definitions" as Clause 1 or Clause 2. Terms and definitions is always clause 3 in ISO.
@manuel489 could you help update them? Thanks.

Task is merged. Closing.


Update CopyColumnsTransformer

Codecov Report
Attention: Patch coverage is 91.17647% with 3 lines in your changes missing coverage. Please review.

Project coverage is 99.68%. Comparing base (dd93111) to head (5429056).
Report is 2 commits behind head on main.

Files with missing lines
Patch %
Lines

src/grizz/transformer/columns.py
89.65%
3 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##              main     #256      +/-   ##
===========================================
- Coverage   100.00%   99.68%   -0.32%
===========================================
  Files           38       39       +1
  Lines          933      959      +26
  Branches        36       37       +1
===========================================
+ Hits           933      956      +23
- Misses           0        3       +3

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


Replace Wizards with Goblin Priests

Should be straight forward. Don't worry about the spells yet, just let them do what wizards do for now. This also includes replacing the Wizard's name table with Goblin Priest names.

Need to fix names now.


Fancy Compendia doesn't work for me anymore

Just wanted to leave straightforward report here and say that Fancy Compendia just doesn't work for me anymore, which is a shame, because I was adoring it a ton.
Hopefully we can find a way to fix it because at the moment spell compendiums will not open.

I think I'm getting the same issue


Nelson crashes after a few hours/days

I don't run nelson as a service. I run it using the command:
nohup sudo nelson --config /Users/iota/nelson/config.ini &
Just happened for the 3rd time. I go to check my node and found out that nelson is not running.  This last time it was running for almost 24 hours before crashing. More details in the log below.
Expected behaviour
Nelson running continuously
Actual behaviour
After a while, can be hours or a few days, Nelson crashes.
Steps to reproduce
Not sure. It crashes randomly
Basic Info

Operating System: Macos High Sierra (10.13.2)
Node (npm) Version: v8.4.0
IRI Version: <IP_ADDRESS>
Nelson version: 0.3.16

Nelson Info

Epoch: don't know
Cycle: don't know
Connected peers: my configuration is 6 in, 5 out

8:30:23 AM.190	16600::NODE  new cycle
8:30:23 AM.195	16600::IRI   Neighbors removed (if there were any): udp://<IP_ADDRESS>:14600
8:30:23 AM.195	16600::NODE  connection closed <IP_ADDRESS>:16600 (remotely dropped)
8:30:23 AM.195	16600::IRI   Neighbors removed (if there were any): udp://<IP_ADDRESS>:14600
8:30:23 AM.195	16600::NODE  connection closed <IP_ADDRESS>:16600 (remotely dropped)
8:30:23 AM.196	16600::IRI   Neighbors removed (if there were any): udp://<IP_ADDRESS>:14600
8:30:23 AM.196	16600::IRI   Neighbors removed (if there were any): udp://<IP_ADDRESS>:14600
/usr/local/lib/node_modules/nelson.cli/node_modules/ws/lib/WebSocket.js:638
this._req.abort();
^
TypeError: Cannot read property 'abort' of null
at ClientRequest._req.setTimeout (/usr/local/lib/node_modules/nelson.cli/node_modules/ws/lib/WebSocket.js:638:16)
at Object.onceWrapper (events.js:314:30)
at emitNone (events.js:105:13)
at ClientRequest.emit (events.js:207:7)
at Socket.emitTimeout (_http_client.js:722:34)
at Object.onceWrapper (events.js:314:30)
at emitNone (events.js:105:13)
at Socket.emit (events.js:207:7)
at Socket._onTimeout (net.js:398:8)
at ontimeout (timers.js:469:11)

nelson gui also errors out for me after about a day of running. In the top left quarter of the screen, I see the following error multiple times: Unhandled Rejection at: Promise Promise
Seems Nelson is still running though, ,because the bottom half is still updated with neighbor connects and disconnects.

@rafaelbrizola any update?

Hi @lpinca sorry for not getting back to you. After that day, I still run Nelson for a couple of days but didn't notice any other crashes. However, I stopped running the experiment, and for other reason, never got back to that. So, it's inconclusive it that change helped in my case. If nobody else is noticing the crash, you can close this issue. Thanks!


Availability in PDP

[ ] display "Available" if stock of the product is > 0

@trangng For the demo data, what do we use for stock? Do we disable stock?
Do we use a big stock like<PHONE_NUMBER> elements?
Should we have products out of stock in the demo data? How much?
Should the availability information included in the product csv? Maybe this is too much effort and the availability data can be generated.

@trangng Is this an MVP feature?

if a product is on stock, the customer is able to see a green symbol with the information that the product is available and it can be delivered in 2-5 days

I think there are 2 topics (ability to add to cart and availability info) mixed together. If product is on stock then we show "add to cart button" if not we disable it and show availability info based on expectedDelivery and restockableInDays values.
http://dev.sphere.io/http-api-projects-inventory.html#inventory-entry
@trangng Could you check this?

Done :)


python310Packages.ypy-websocket: 0.9.0 -> 0.12.1

Description of changes
Diff: https://github.com/y-crdt/ypy-websocket/compare/refs/tags/v0.9.0...v0.12.1
Changelog: https://github.com/y-crdt/ypy-websocket/blob/refs/tags/v0.12.1/CHANGELOG.md

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

38 packages built:

manim
manim.dist
python310Packages.jupyter-server-ydoc
python310Packages.jupyter-server-ydoc.dist
python310Packages.jupyterlab
python310Packages.jupyterlab-git
python310Packages.jupyterlab-git.dist
python310Packages.jupyterlab-lsp
python310Packages.jupyterlab-lsp.dist
python310Packages.jupyterlab.dist
python310Packages.jupytext
python310Packages.jupytext.dist
python310Packages.layoutparser
python310Packages.layoutparser.dist
python310Packages.mkdocs-jupyter
python310Packages.mkdocs-jupyter.dist
python310Packages.pdfplumber
python310Packages.pdfplumber.dist
python310Packages.ypy-websocket
python310Packages.ypy-websocket.dist
python311Packages.jupyter-server-ydoc
python311Packages.jupyter-server-ydoc.dist
python311Packages.jupyterlab
python311Packages.jupyterlab-git
python311Packages.jupyterlab-git.dist
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab-lsp.dist
python311Packages.jupyterlab.dist
python311Packages.jupytext
python311Packages.jupytext.dist
python311Packages.layoutparser
python311Packages.layoutparser.dist
python311Packages.mkdocs-jupyter
python311Packages.mkdocs-jupyter.dist
python311Packages.pdfplumber
python311Packages.pdfplumber.dist
python311Packages.ypy-websocket
python311Packages.ypy-websocket.dist