ref fields and scoped. Modify pages on struct creation, variable declaration, and ref struct.

Fixes #30226
https://github.com/dotnet/docs/issues/30226#issuecomment-1230840028 describes the tasks in this PR. The commits follow the task list.
Internal review site:

Language reference article on structs:  ref struct content removed.
Language reference article on ref struct: Contains ref struct content from struct article.
Language reference article on ref keyword: Update and edit article to add new ref fields.
Language reference article on method parameters: New and updated information on pass by value / reference, reference type, value type, and parameter modifiers. Also, define safe-to-escape and ref-safe-to-escape
Language reference article on declaration statements: New article on variables declarations. Includes var, ref locals and ref fields.
Language reference article on assignment operator: Clarify ref assignment.
Language reference article on keywords: add scoped contextual keyword

Changes in other files are primarily updating links and link text.
Note for reviewers:  The articles tagged above have the significant changes. Samples moved to the updated folders. Almost all other article changes were updating links to updated content for the language reference.

@Youssef1313 Is there a tag for the F1 help for scoped? I'll add it to this PR.

@Youssef1313 Is there a tag for the F1 help for scoped? I'll add it to this PR.

I'm not sure. I added a test in https://github.com/dotnet/roslyn/pull/64094 and will see what CI says :)

closing and reopening for a fresh build


Windows 10 - Exits with no errors or results

when I run: diart.stream speakers:9, or execute it in a python script it simply sends a notice about sox_io, and then exits. No errors. How do I figure out what's wrong?
 dev  diart.stream speakers:9
The torchaudio backend is switched to 'soundfile'. Note that 'sox_io' is not supported on Windows.
The torchaudio backend is switched to 'soundfile'. Note that 'sox_io' is not supported on Windows.

If I remove this line:
import diart.sources as src
I get further. But, it obviously crashes once its required.

Hi @matbee-eth,
When diart receives "speakers:9", it will interpret that as a path. You need to provide either "microphone:9" or the path to an existing file.
That said, there seems to be another problem with soundfile, can you set the input to "microphone" and see if you get the same error?

Diart's not yet compatible with output devices so I don't think that will work. Although this is something I would really like to include in future versions.
Have you installed portaudio, pysoundfile and ffmpeg ? Can you identify what line is blocking you in diart.sources ?

I have all of those installed- I'm unable to identify what line is blocking me. Ive tried commenting out a plethora of code in diart.sources but the same symptom occurred- I feel its something else that my lack of python skills are of no help.
If you have any bounty system I'd love to contribute

@matbee-eth you could try putting a breakpoint in the beginning of diart.sources and debug line by line until it breaks or hangs.

If you have any bounty system I'd love to contribute.

What kind of bounty system are you referring to?

An alternative to diart capturing audio-out, I could use ffmpeg to capture and pipe the data. Has this been something you've seen done?

I haven't seen or tries this but it looks like it could work! If you have a working example could you post it here? This could be an interesting alternative to implement a new audio source.

@juanmc2005 is there any progress on this bug? I tried to use this in ubuntu, it failed there due to error in sample rate.
I manually changed the sample rate to 48000, then it progressed and showed me a warning that the pipeline uses 16000hz so it will resample it, but crashed later.
Hoping that it would work in windows, tried to do the same but it shows this output and stops.
(diart) C:\Windows\System32>diart.stream microphone:19 The torchaudio backend is switched to 'soundfile'. Note that 'sox_io' is not supported on Windows. The torchaudio backend is switched to 'soundfile'. Note that 'sox_io' is not supported on Windows.
tried microphone with multiple input devices but it still wont work.
Please let me know if there are any quickfixes I can do to make it work in any of the OS.
Thank you.

Note that diart's inference time will suffer if your microphone doesn't support 16khz sampling. The dynamic resampling is quite slow. I added the possibility to resample on GPU, which might help with that, but the best thing will be to use a device supporting 16khz.


How to get request process PID address

How to get requestor process PID address

Process context is not available on the NDIS level, moreover some packets don't have associated PID (e.g. routed ones).
However, you can use IP Helper API for this purpose. For the TCP protocol it can be done with the following steps:

Use GetExtendedTcpTable and GetOwnerModuleFromTcpEntry to build the mapping from the local (IP address, TCP port) to process executable.
Extract IP and port information from the packet and use the mapping built on previous step to look up the process executable.
Update the mapping periodically or when you can’t lookup process for the certain packet.

For the UDP just use GetExtendedUdpTable and GetOwnerModuleFromUdpEntry instead.

Thanks a lot.


Adding missing Flag --skip-ssl-validation

Adding skip-ssl-validation flag.

LGTM

LGTM

@tboerger is the drone build disabled? I see the last was PR 7


@alloy -> constrain width of launch logo on iphone

fixes https://github.com/artsy/eigen/issues/607
First, I'm using the large retina version of the logo.
Second, I'm setting up a size class-specific constraint to limit the size of the logo on phones.

I’ll assume this looks good now :)
But in the future, when it pertains a visual change like this and there are no snapshot tests, can you please include a screenshot/video?


Clip Children creates a screen mirror on Mobile renderer

Godot version
v4.1.1.stable.official [bd6af8e0e]
System information
Fedora Linux 38 (Workstation Edition), GNOME 44.3 Wayland
Issue description
Clip Children creates a screen mirror on Mobile renderer.
Screencast from 2023-08-08 22-00-30.webm

Screencast from 2023-08-08 22-10-42.webm
Steps to reproduce

Switch to Mobile renderer
Create a TextureRect or a Sprite2D
Give it a texture with transparency
Put anything inside of it
Enable Clip Only in Clip Children

Minimal reproduction project
Clip Children Screen Mirror Bug.zip

Thank you for reporting, duplicate of:

#75956


Problem in dm.data.process

Hi,
during the execution of
train, validation, test = dm.data.process(
    path='sample_data/itunes-amazon2',
    train='train.csv',
    validation='validate.csv',
    test='test.csv')

a KeyError: tensor(2) is raised.
Are there any solutions? Can the problem arise due to a wrong configuration of the deepmatcher installation?

Thank you very much for helping

please i need your help
my issue 29 https://github.com/anhaidgroup/deepmatcher/issues/29 can't save model
@FrancescoDelBuono @goel42 @thodrek @hanli91 @sidharthms


Release slack plugin 1.8.1

This issue is to track progress of releasing slack plugin 1.8.1.
TODO:

[x] Configure your credentials in ~/.m2/settings.xml. (outlined in making a
new release doc)

[x] Create a new issue to track the release and give it the label maintainer communication.

[x] Create a release branch. git checkout origin/slack-1.8-stable -b prepare_release

[x] Update the release notes in CHANGELOG.md.

[x] Open a pull request from prepare_release branch to slack-1.8-stable branch.  Merge it.

[x] Fetch the latest slack-1.8-stable.

[x] Execute the release plugin.
mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare org.apache.maven.plugins:maven-release-plugin:2.5:perform

I pin which version of the release plugin to use because of the working around common issues section of the release document.

Encountering issues with publishing the plugin.

The error was 401 unauthorized.  It's because I mistakenly set ~/.m2/settings.xml credentials for repo.jenkins-ci.org instead of maven.jenkins-ci.org.

The plugin has been released.  It will be roughly 8 hours before the release propagates to the Jenkins Update Center.

http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/slack/1.8.1/

I'll close this issue when it is in the update center and a successful plugin upgrade is performed.  The testing platform is https://github.com/samrocketman/jenkins-bootstrap-slack

cc @Nooba mentioning you since you played a major part in this release.  In case you want to track its progress.

It wasn't but a mere suggestion and a few git shenanigans.
Thanks for the heads up though.

Upgrade successfully tested.  Seems the bug fixes got released without any issues.  It took me a while to test because I've been sick the past week.  In any case, glad nothing went wrong during that time.  I'll release the milestone as well.


Fix for location hash issue

Hi,
I've implemented a fix for the issue in questions (#193), I have tested this and seems to be working well.
This is my first pull request on a project so if there are any problems please let me know so I can learn.
Thanks,

Thanks!


[Area Chart] "Unexpected Error"

Get an unexpected error when trying to generate a superset chart (as seen in the screenshot below) even though the query runs and returns results.
Screenshots

You will see that data section has correct results but chart can't be rendered.
It seems like the SUM metrics are incorrectly being named "sum" in the generated query, which causes some weird sql problems.

Switching to "custom sql" is a workaround but not ideal.
Environment
latest production
Checklist
Make sure to follow these steps before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
CC @serenajiang @villebro

@graceguo-supercat  can you show a screenshot of the metric popover? It looks like it has a custom label, but I assume not? Also, is this Presto?

Even better, can you post the redacted chart metadata, especially params.metrics?

{
  "viz_type": "area",
  "datasource": "158397__table",
  "url_params": {},
  "time_range_endpoints": [
    "inclusive",
    "exclusive"
  ],
  "granularity_sqla": "ds_check_in",
  "time_grain_sqla": "P1D",
  "time_range": "No filter",
  "metrics": [
    {
      "expressionType": "SIMPLE",
      "column": {
        "id": 1895078,
        "column_name": "listings",
        "verbose_name": null,
        "description": null,
        "expression": null,
        "filterable": true,
        "groupby": true,
        "is_dttm": false,
        "type": "BIGINT",
        "type_generic": 0,
        "python_date_format": null
      },
      "aggregate": "SUM",
      "sqlExpression": null,
      "isNew": false,
      "hasCustomLabel": false,
      "label": "",
      "optionName": "metric_ja8im4tgzup_arys39zkcdj"
    }
  ],
  "adhoc_filters": [
    {
      "expressionType": "SIMPLE",
      "subject": "dim_availability_type",
      "operator": "==",
      "operatorId": "EQUALS",
      "comparator": "UNAVAILABLE",
      "clause": "WHERE",
      "sqlExpression": null,
      "isExtra": false,
      "isNew": false,
      "filterOptionName": "filter_uedp7l1zhu_s587slv7edk"
    }
  ],
  "groupby": [
    "dim_unavailability_reasons"
  ],
  "limit": 100,
  "order_desc": true,
  "row_limit": 1000,
  "show_brush": "auto",
  "line_interpolation": "linear",
  "stacked_style": "stack",
  "color_scheme": "supersetColors",
  "label_colors": {},
  "rich_tooltip": true,
  "bottom_margin": "auto",
  "x_ticks_layout": "auto",
  "x_axis_format": "smart_date",
  "y_axis_format": "SMART_NUMBER",
  "y_axis_bounds": [
    null,
    null
  ],
  "rolling_type": "None",
  "comparison_type": "values",
  "annotation_layers": [],
  "extra_form_data": {}
}

Hi @villebro do you need more information for this issue? thanks!

this issue also happens to Line Chart
{
  "viz_type": "line",
  "datasource": "158840__table",
  "url_params": {},
  "time_range_endpoints": [
    "inclusive",
    "exclusive"
  ],
  "granularity_sqla": "ds",
  "time_grain_sqla": "P1D",
  "time_range": "No filter",
  "metrics": [
    {
      "expressionType": "SIMPLE",
      "column": {
        "id": 1904718,
        "column_name": "unique_visitors",
        "verbose_name": null,
        "description": null,
        "expression": null,
        "filterable": true,
        "groupby": true,
        "is_dttm": false,
        "type": "BIGINT",
        "type_generic": 0,
        "python_date_format": null
      },
      "aggregate": "SUM",
      "sqlExpression": null,
      "isNew": false,
      "hasCustomLabel": false,
      "label": "",
      "optionName": "metric_76gswmgyogo_kymat50bwcj"
    }
  ],
  "adhoc_filters": [
    {
      "expressionType": "SIMPLE",
      "subject": "valid_visitor",
      "operator": "==",
      "operatorId": "EQUALS",
      "comparator": "valid_visitor",
      "clause": "WHERE",
      "sqlExpression": null,
      "isExtra": false,
      "isNew": false,
      "filterOptionName": "filter_sq1vozrzik_49hy4x6kuxy"
    }
  ],
  "groupby": [
    "dim_platform_mode"
  ],
  "limit": 100,
  "order_desc": true,
  "row_limit": 50000,
  "color_scheme": "supersetColors",
  "label_colors": {},
  "show_brush": "auto",
  "rich_tooltip": true,
  "line_interpolation": "linear",
  "bottom_margin": "auto",
  "x_ticks_layout": "auto",
  "x_axis_format": "smart_date",
  "left_margin": "auto",
  "y_axis_format": "SMART_NUMBER",
  "y_axis_bounds": [
    null,
    null
  ],
  "rolling_type": "None",
  "comparison_type": "values",
  "annotation_layers": [],
  "extra_form_data": {}
}

bump to p0, it is also happening in echarts. there are 2 workaround, another one is to create a chart with some other aggregate.. then switch to SUM
https://user-images.githubusercontent.com/67837651/128950710-145d55ab-97ae-4375-b1aa-5367503fe500.mov

I was able to reproduce

wow thanks so much for everyone @villebro @kgabryje @junlincc !!


Unable to Track Version from Terminal and Module Import Failure

Description
When attempting to track the version of the eda_toolkit library from the terminal, an error occurs due to a missing module (IPython). The import fails, making it impossible to proceed with version tracking or usage.
Steps to Reproduce

Open a terminal and activate the virtual environment.
Start a Python interactive session (python).

import eda_toolkit

The following error is raised:
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/lshpaner/Python_Projects/circ_milan/venv_circ_311/lib/python3.11/site-packages/eda_toolkit/__init__.py", line 42, in <module>
    from .main import *
  File "/home/lshpaner/Python_Projects/circ_milan/venv_circ_311/lib/python3.11/site-packages/eda_toolkit/main.py", line 11, in <module>
    from IPython.display import display
ModuleNotFoundError: No module named 'IPython'

The library should import without errors, and the version should be retrievable using:
eda_toolkit.__version__

Root Cause Analysis
The error indicates that the IPython module is a dependency but is not installed in the current environment. This dependency is critical for the library to function, particularly for displaying outputs.
Proposed Solutions

Update Installation Requirements: Ensure that IPython is listed as a required dependency in the eda_toolkit package's pyproject.toml`.

install_requires=[
    "IPython>=7.0.0",
    ...
]

Remove Necessity for UsingIPython Display:

from IPython.display import display

This line supports the display(crosstab_df) statement inside the stacked_crosstab_plot function. To resolve the issue:

Remove the import for IPython.display.
Replace the line display(crosstab_df) with an alternative approach, such as using print() or returning the DataFrame explicitly.

This way, the library would no longer require IPython, reducing overhead and preventing import issues.

Update the installation guide to specify the required dependencies or provide instructions for ensuring a complete setup.

Resolved via https://github.com/lshpaner/eda_toolkit/pull/68


frequency shift in beamforming.lcmv_raw

Hi,
recently I'm dealing with the following problem: I wanted to reconstruct the MEG resting state signals in specific frequency band. I heard about one approach in which you apply inverse method to epoched data in specific frequency. So I did the following:

filtered my signal in alpha;
epoched my continuous data into 2 sec trials;
created also the same epochs for broadband data;
created covariance matrices both for alpha: band_cov and broadband signal noise_cov.

Then I followed standard steps: computed source space, created BEM, made forward model and assembled inverse operators for  band_cov.
The problem appears when I want to apply an inverse method. I do it by calling two functions on my continuous recordings filtered in alpha band (to be consistent with covariance matrix and inverse operator creation).
So this is PSD of my raw filtered recordings:

This is output from one of the channels from sLORETA:
        stc_sol = apply_inverse_raw(raw_band, inverse_operator, lambda2,
                                    method=method, pick_ori=pick_ori)

And this is what I got from from beamforming:
        stc_sol = beamformer.lcmv_raw(raw_band, forward, noise_cov, band_cov, reg=reg,
                        pick_ori=pick_ori, weight_norm='unit-noise-gain',
                        max_ori_out='signed')

As you can see there is strange frequency shift. I thought at the beginning that there is something wrong with my input data, but results from sLORETA suggest that everything is fine. The difference appear after that line.
For completeness I just add that I plot data after parcelation:
    labels = mne.read_labels_from_annot(subject_number, parc='aparc', subjects_dir=head_shape_dir)
    label_names = [l.name for l in labels]
    label_ts = mne.extract_label_time_course(stc, labels, inverse_operator['src'], mode='pca_flip',
                                            return_generator=False)
    a = label_ts[21,:]
    p,f=mne.time_frequency.psd_array_welch(a,fs)
    plt.plot(f,p)

Can you spot any mistake in my procedure, or should I dig more into the code to solve this?

I would recommend providing us a "minimal reproducible example" so it's easy to trace the bug (if any)


[graphql-language-service]: TypeError [ERR_INVALID_ARG_TYPE]: The "chunk" argument must be one of type string or Buffer. Received type object

graph-language-service doesn't return an error message that shows what you need to do.
how to reproduce
Run one of the following commands in the root of package graphql-language-service, then you got the same error message as the title.
bin/graphql.js autocomplete --text foo --schemaPath ...
bin/graphql.js outline --text foo
bin/graphql.js validate --text foo --schemaPath ...
(Before running these scripts, you need to run yarn build in advance.)
cause
error given at https://github.com/graphql/graphiql/blob/917c3931634cf27eb31a0383ff7c15ffd902d221/packages/graphql-language-service/src/client.ts#L105
or
https://github.com/graphql/graphiql/blob/917c3931634cf27eb31a0383ff7c15ffd902d221/packages/graphql-language-service/src/client.ts#L134
or
https://github.com/graphql/graphiql/blob/917c3931634cf27eb31a0383ff7c15ffd902d221/packages/graphql-language-service/src/client.ts#L148
is actually type object, though process.stderr.write method doesn't allow for type object. Therefore, the method throws an error.

I've almost done to fix this issue at my local branch. Soon I'll PR for this.

thanks @yoshiakis! we have an outstanding bug for this: #1306

we're already underway with a fix. which needs to be in graphql-language-service-server, is that where your fix is?

@acao Although this issue looks similar to #1306, it seems the cause of this issue is different from the cause of #1306.

i’ll get a chance to take a closer look next week probably


Added Tracy 2.6 support

@Vrtak-CZ Looks like packagist can't see new releases. Can you fix it please?


Add docker file

I found it difficult to get running on my host machine due to specific versions of dependencies. Using docker was a great solution for me, so hereby I provide the script to others.

Thanks @JJK96 for your contribution!


Fix Playwright test fail in todo-nodejs-mongo

Fixes issue https://github.com/Azure/azure-dev/issues/246
Change files: templates/todo/common/tests/todo.spec.ts
Add setTimeOut is used to wait for the page data to full load.
@rajeshkamal5050 for notification.

I think it's better to pass { waitUntil: 'networkidle' } to the initial page.goto call as an option. So the code has now been corrected according to this idea.

pipeline is currently broken after this PR:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1814636&view=logs&j=9392ca66-1ee4-52af-022d-b22076a99114&t=6db148d5-c790-543c-3e98-57830bb8eafe&l=162
Change:

@hongli750210 , any ideas?

@vhvb1989
Replace ： with :  to fix the problem you mentioned. Can I still upload a new version after the code has been merged?

@hongli750210 additional syntax fix was made by @ellismg. Should be good now.

https://github.com/Azure/azure-dev/pull/546


[6.x] Adds a pipeline() helper

The problem
Currently there is only one way to create a pipeline, and this is calling the app() helper and point out the Pipeline class.
$pipeline = app(\Illuminate\Pipeline\Pipeline::class);

$pipeline->send($passable)->through([ /* ... */ ])->thenReturn();

There is no other way to do it.
The Fix
This PR adds a pipeline() helper that can take the passable and the pipe stack as an array, leaving the developer to return the result or decorate it before returning it, callable from anywhere.
$pipeline = pipeline($passable, [ /* ... */ ])->thenReturn();

These two arguments are optional, and since it just returns a Pipeline instance, the developer can still change the handling method or replace the passable.
$pipeline = pipeline($passable, [ /* ... */ ]);

$pipeline->send($other_passable)->through([ /* other pipe stack */ ]);

The Magic
Just some lines in the Illuminate/Foundation/helpers.php to add the helper.

I don't plan on adding more global helpers.


Outline not showing functions or erroneously showing imports as functions

Issue Report Checklist

[x ] Searched the issues page for similar reports
[ x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[x ] Tried basic troubleshooting (if a bug/error)

[x ] Restarted Spyder
[x ] Reset preferences with spyder --reset
[x ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[x ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
What steps reproduce the problem?

outline not listing functions, doesn't matter if they are in code cells or not

outline listing module imports as generic functions when they are moved to a new line with ""

What is the expected output? What do you see instead?
 I'm afraid that in order to understand why that's happening, you'd need to upload your entire code project (not just the files you're showing us), so we can reproduce the problem in our side.
If you don't feel comfortable sharing it in public, you can send it to my email (it's on my Guthub profile). Also, please let us know if you0re using a Spyder project or not.

no problem - it's public: https://github.com/mluerig/phenopype
Started happening after I moved from 5.0.5 to 5.1.3. I am not using a Spyder project.

Maybe this is an issue on Windows because I can't reproduce it on Linux. I'll take a look at it soon and let you know.
Another question for you: how did install Spyder?

ok thanks - let me know if there is anything else you need or if I should test stuff.
I installed manually from conda forge because the latest version wasn't available yet through the anaconda main channel

I'm seeing a similar issue and I think I could at least identify part of the problem, maybe the whole problem: It seems like any module that is part of a namespace package does not have its functions and classes listed in the outline.
I made a test project that contains a module with the exact same content once in a namespace package and once in a "normal" package. The "normal" package works correctly with the outline panel, but the namespace package does not show anything.
The test project is here (I also made a spyder project in the top-level directory):
TestProject.zip
I've installed spyder from the official installer and I'm using version 5.1.4. I just upgraded from 5.1.2 where I'm pretty sure the outline was working correctly. I can double-check that if it helps.

curious...

Your phenopype.core package is a namespace package. Is that intentional?

I guess not, because I don't know what a namespace package is. at least, I couldn't guess from your example...

A bit off topic here but just in short: The python import system considers
each package (i.e. folder) that dies not contain a "init.py" file a
"namespace package". You don't need that for standalone projects normally.
It is only useful if you want to have multiple projects to be importable
from the same namespace. This is the (lenghty but detailed) description of
namespace packages: https://www.python.org/dev/peps/pep-0420/
Moritz Lürig @.***> schrieb am Mo., 13. Sep. 2021,
16:28:

curious...
Your phenopype.core package is a namespace package. Is that intentional?
I guess not, because I don't know what a namespace package is. at least, I
couldn't guess from your example...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/spyder-ide/spyder/issues/16406#issuecomment-918250866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD7SKK365XTAKSZO4QLV243UBYDBJANCNFSM5D4FXIAA
.

I'm seeing a similar issue and I think I could at least identify part of the problem, maybe the whole problem: It seems like any module that is part of a namespace package does not have its functions and classes listed in the outline.

I can confirm that this is the issue - adding an __init__.py solved it for me

@mluerig or @Brow71189, did you install your packages installed with pip install -e .?

yes I am working on my project in pip dev mode

I was able to reproduce the problem with @Brow71189's example and will try to fix it in our next release. At least you have a workaround until then.

@mluerig or @Brow71189, did you install your packages with pip install -e .?

I don't have any of my packages installed in the python installation that spyder uses (since I'm using the installer, it is completely separate from any other installations on my system).
Great that you could reproduce the problem and thanks for taking it on!

I have the same problem!
My code was completed in spyder 4.1.5, I encountered this problem when using 5.1.5.
Can create a new .py in 5.1.5 and copy the code to this file to solve this problem!

Versions

Spyder version: 5.1.5
Python version: 3.8.12
Qt version: 5.9.7
PyQt version: 5.9.2
Operating System name/version:win10

I have the same problem!
the .py files in the project folder is well, but the .py files in the subfolders of the project folder is bad

@ccordoba12
Thanks for merging issues.
I also solved this issues by adding init.py

I got similar issues at spyder 5.1.5; after putting an empty init.py under the concerned directory, the outline come back again after restarting spyder.

As a workaround I have downgraded python-lsp-server to version 1.2.1 (pip install python-lsp-server==1.2.1).
Then the functions are shown again in the outline pane. (I didn't  notice any drawbacks from this.)

@glaida2020, although there's no big harm in doing that, we fixed other problems related to the Outline in newer python-lsp-server versions, so it'll break it in other situations. That's why I'm going to hide your comment, as well as mine.

Adding a __init__.py file solved this problem for me one time in the past, but I'm having the same problem again adding a __init__.py file and restarting doesn't change anything.
Versions
Spyder: 5.2.2
Python: 3.9.10
Qt: 5.12.9
PyQt5: 5.12.3
OS: Debian 11
Linux kernel: 5.10.0-11-amd64

I have also encountered this problem with Spyder 5.2.2 on Windows 10.
Continuing discussion from comment on issue #15139 after some more testing.
Project directory structure (in summary)
Project_root/
├── some_directories ...
├── some_files ...
├── src/
│   ├── main_module.py
│   └── submodules/
│       ├── __init__.py
│       ├── submodule_1.py
│       ├── submodule_2.py
│       └── subsubmodules/
│           ├── __init__.py
│           └── subsubmodule_1.py
└── build_script.py

Versions

Spyder version: 5.2.2 None
Python version: 3.7.9 64-bit
Qt version: 5.12.10
PyQt5 version: 5.12.3
Operating System: Windows 10

Installed with .exe installer, same result with Spyder's own Python 3.7.9 and the system-wide Python 3.9.2 which I mainly use.
Results
The outline view works for modules placed in the project root directory (e.g. build_script.py), but not for anything under src/ and further down (only filename is shown).
Curiously, the outlines for src/ and its modules work and update even for new files after removing __init__.py from src/, changing the Python interpreter and restarting Spyder (?!)
Workaround
Putting an __init__.py into src/ and restarting Spyder (or the LSP language server) makes the outline work for all the modules in src/ and its subdirectories.
I didn't think about doing it at first, given that src/ is just my folder for keeping code and is not intended to be a package. But happily it looks workable.

Hi @ccordoba12 thanks for linking my issue 18712 to this duplicate. I just wanted to add that I do also have a directory structure
Project_root/
├── app/
├── helpers/
├── logs/

putting init.py into the subdirs helped to get the Outline running. Although I have no idea what this file is for ;)

Same problem here with Spyder 5.2.2.
My folder structure is
mypackage
│   LICENSE
│   pyproject.toml
│   README.md
│   requiremets.txt
├───docs
├───scripts
├───src
│   └───mypackage
│          config.py
│          first_module.py
│          utils.py
│          second_module.py
│          __init__.py
└───tests

all I had to do is to add an empty __init__.py file in src/ and the outline is back.


@OneToOne mapping in MS SQL Server

In new ebean (4.5) there has beed added UNIQUE CONSTRAINT for One to One mapping.
Generated SQL by ebean 3.4.1 for MS SQL Server 2012:
create table users (
  id                        numeric(19) identity(1,1) not null,
  username                  varchar(48) not null,
  preferences_id            numeric(19),
  user_type                 integer,
  constraint ck_users_user_type check (user_type in (0,1,2,3,4,5)),
  constraint uq_users_username unique (username),
  constraint pk_users primary key (id))
;

create table users_preferences (
  id                        numeric(19) identity(1,1) not null,
  username                  varchar(48) not null,
  ui_preferences            varchar(max),
  user_credentials          varchar(max),
  constraint pk_users_preferences primary key (id))
;

ebean 4.5.4-SNAPSHOT for MS SQL Server 2012:
create table users (
  id                        numeric(19) identity(1,1) not null,
  username                  varchar(48) not null,
  preferences_id            numeric(19),
  user_type                 integer,
  constraint ck_users_user_type check (user_type in (0,1,2,3,4,5)),
  constraint uq_users_username unique (username),
  constraint uq_users_preferences_id unique (preferences_id),     # new UNIQUE CONSTRAINT
  constraint pk_users primary key (id))
;

create table users_preferences (
  id                        numeric(19) identity(1,1) not null,
  ui_preferences            varchar(max),
  user_credentials          varchar(max),
  constraint pk_users_preferences primary key (id))
;

In new ebean there is:
  constraint uq_users_preferences_id unique (preferences_id),

which is good because one to one mapping should check this, and is correct with ANSI:

According to the ANSI standards SQL:92, SQL:1999, and SQL:2003, a UNIQUE constraint should disallow duplicate non-NULL values, but allow multiple NULL values.

and this unique constraing is consistent with definition of one to one mapping:

A one-to-one relationship in a relational database occurs when one parent record or field has either zero or one child record only.

Problem is with databases implementations.
mySQL (OK):

A UNIQUE index creates a constraint such that all values in the index must be distinct. An error occurs if you try to add a new row with a key value that matches an existing row. For all engines, a UNIQUE index allows multiple NULL values for columns that can contain NULL.

PosgreSQL (OK):

When an index is declared unique, multiple table rows with equal indexed values are not allowed. Null values are not considered equal. A multicolumn unique index will only reject cases where all indexed columns are equal in multiple rows.

MS SQL Server 2012 (Invalid):

In the Microsoft world of SQL Server however, a single NULL is allowed but multiple NULLs are not...
https://connect.microsoft.com/SQLServer/feedback/details/299229/change-unique-constraint-to-allow-multiple-null-values

Therefore in MS SQL Server 2012 (and 2008) there can be only one NULL (not connected) entity.
For MS SQL Server (>=2008) there is a workaround about this:
CREATE UNIQUE NONCLUSTERED INDEX idx_yourcolumn_notnull
ON YourTable(yourcolumn)
WHERE yourcolumn IS NOT NULL;

http://msdn.microsoft.com/en-us/library/ms190457.aspx
Adding this to DDL generator would make ebean platform independ for One-to-One mapping.
and to fix change is required for method:
com.avaje.ebeaninternal.server.ddl.CreateTableColumnVisitor.visitOneImported.
I think that the same should be with column unique - it should be database platform independed.
I know that I can set in DbDdlSyntax.setAddOneToOneUniqueContraint(false) to ignore this, but this is not the right (nice) solution.
(I didn't checked this on H2 so far)

Updating my last entry.
H2 database is working as expected.
Also intereseting article: http://tech.pro/tutorial/1419/10-things-in-sql-server-which-don-t-work-as-expected

Fixed in master, rolling out with 6.3.1


Fix esm module resolution

@LilyRose2798
Somehow this slipped past my testing, but getting this error with 1.4.0 on Next 14.2.3
 ⨯ ModuleBuildError: ./src/pages/api/openapi.json.ts:1:1
Module not found: Can't resolve '@lilyrose2798/trpc-openapi'
> 1 | import { generateOpenApiDocument } from '@lilyrose2798/trpc-openapi'
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  2 | import { NextApiRequest, NextApiResponse } from 'next'
  3 | import { appRouter } from 'server/routers/root'
  4 |

Import map: aliased to relative "./src/@lilyrose2798/trpc-openapi" inside of [project]/

https://nextjs.org/docs/messages/module-not-found

The package.json was misconfigured so that the esm module entry was pointing to a non-existant file.
This PR fixes this issue.

Thanks for the fix!

Published as v1.4.1


move question about starting services after start upper before configuration happen

currently "Do you want to start service? y/n [y]:" question is displayed when selenoid part is updated.
Sometimes it is annoying when you wanna to answer "y" for everything except services startup... It is difficult to stop when selenoif is being updated

Right after S3 or minio configuration we should see such warning and question:
`Minio S3 Storage for Reporting
Enable? y/n [y]:
  WARNING! Your services needs to be started after setup.
  Start now? y/n [y]:

`
if you answer no - setup is finished without startup. if yes - configured services should be started

Testing scenario:
Steps:
1.Cloning Zebrunner
2.Git checkout develop
3.Run./zebrunner.sh setup
Actual result: Automatic services startup is not started after  Start now.
Please see screenshot:

root cause detected and fixed in brnach develop

Fixed.


Update playtron os files 0.16.7

I created the git tag: https://github.com/playtron-os/playtron-os-files/tree/0.16.7
Regarding the license change, here's when it happened:

GPLv3 = https://github.com/playtron-os/playtron-os-files/blob/0.2.1/LICENSE
ASLv2 = https://github.com/playtron-os/playtron-os-files/blob/0.2.0/LICENSE


[WIP] [ExternalNode] Controller validates connection peer

A single token is created and used on Antrea Agent per VM, which is bound to a separate Secret. The Secret name is added in ExternalNode Spec.
When a connection comes to Antrea Controller with Node/ExternalNode name as a parameter in the request, Controller validates the used token to read the bound Secret. Then Controller compares it with the valid ExternalNodes which have been configured with the Secret.
The check is bypassed if a connection is using the token generated for the ServiceAccount, e.g., from Antrea Agent on a K8s worker Node, or from Nephe Controller.

Signed-off-by: wenyingd<EMAIL_ADDRESS>

@wenyingd, as we are discussing Antrea/Nephe scale-out design which impacts agent-controller auth, I feel we should pause the auth changes inc. this PR, before we conclude on the future direction.

@wenyingd, as we are discussing Antrea/Nephe scale-out design which impacts agent-controller auth, I feel we should pause the auth changes inc. this PR, before we conclude on the future direction.

Sure, I would modify this PR as [WIP] by now, and abandon it or continue the review process after the final decision is made.


Lab4 and Lab 5 : Numeronyms for given input string and implement stringer interface

Fixes #67
Fixes #70
Changes proposed in this PR:

Implement numeronyms for given input string
Implement stringer interface to print dotted ip address

Codecov Report

Merging #89 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #89   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          11     13    +2
  Lines         170    187   +17
=====================================
+ Hits          170    187   +17

Impacted Files
Coverage Δ

05_stringer/NimishMudhale/main.go
100% <100%> (ø)

04_numeronym/NimishMudhale/main.go
100% <100%> (ø)

Continue to review full report at Codecov.

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


how to switch to CK+ in visualize.py

I trained a CK+_VGG19 model by
python mainpro_CK+.py --model VGG19 --bs 128 --lr 0.01 --fold 1
and the confusion matrix shows that the accuracy is 93.939%.
Then I changed visualize.py
checkpoint=torch.load(os.path.join('FER2013_VGG19','PrivateTest_model.t7'),map_location=torch.device('cpu'))
net.load_state_dict(checkpoint['net'])
to
checkpoint=torch.load(os.path.join('CK+_VGG19','Test_model.t7'),map_location=torch.device('cpu'))
net.load_state_dict(checkpoint['net'].state_dict())
Then I put my own image into images fold to test
It run successfuly
but the result is quite inaccurate
I dont konw where the problem is
Please help me....

please train ('CK+_VGG19','Test_model.t7') by yourself, and put in this dir.


Revert stylistic changes in runWithoutResolvedSignatureCaching

this PR targets https://github.com/microsoft/TypeScript/pull/54121 , see https://github.com/microsoft/TypeScript/pull/54121/files#r1231905436

Closing because https://github.com/microsoft/TypeScript/pull/54658 already landed on main so I'm just gonna sync https://github.com/microsoft/TypeScript/pull/54668 with main again.


Update port for azure-template

Update port for azure-template

This PR shows an expected set of changes. Closing.


Build time sorted by spended time

Could you add some ability to sort desceding goals by spended time?
I have a very big project and want to see most problematic items but now i need to expost data to CSV and then sort them in Excel.
For me looks that this feature will be useful.

That's exactly the reason we added CSV support so that you could analyse it in Excel or whatever other Spreadsheet program you are using. The console is the wrong place to analyse data as there are many different dimensions you might want to analyse, e.g. which module took the longest, or aggregate the time for each mojo in the different modules.

Ok, thanks. Maybe you can determine the most used way and add it? I mean for me sorting by speed looks like first interesting metric.

@stokito this extensions original primary concern was capturing the data and reporting it out in the console. In the next major release (3.0) we will decouple capturing from reporting. This will allow you to output the data to csv or some other location so you can sort, aggregate, and filter however you'd like.
Until then, you can work around using @leonard84 suggestion.


operator project-quay (3.9.0-nightly.20230717)

Add 3.9.0-nightly.20230717 to community operators

/merge possible


WOT (Strengths, Weaknesses, Opportunities, and Threats) analysis

SWOT (Strengths, Weaknesses, Opportunities, and Threats) analysis
Strengths:
User-friendly interface
Dynamic data visualization
Efficient database integration with Sequelize ORM
Security features for authentication and authorization
Weaknesses:
Low brand recognition and awareness
Competition from established financial tracking apps
Limited marketing and promotional resources
Opportunities:
Growing demand for financial tracking apps among young adults and college students
Room for innovation and differentiation in the market
Potential for partnerships and collaborations in finance and tech industries
Threats:
Competition from established financial tracking apps
Technological advancements by competitors
Changes in finance and tech regulations and policies.


npm run build(Create React App) fails to minify the library

As per https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#npm-run-build-fails-to-minify
is it possible for you to publish the code after compiling to ES5 ?

Oh I guess you are already providing the minified version in dist.
Sorry just came to my notice :)


Fix 'yotta version' in Windows

This is a re-open of #122. Local tests yield identic results with
and without this patch in place.

Yup, apparently --work-tree doesn't do what I thought it does. Closing this.


[Improvement] Change Identity-apps build from Jenkins to GitHub actions

Is your suggestion related to an experience ? Please describe.
Currently, the Identity-Apps build happens in Jenkins. Regardless of the changed module, the whole project is built and released as artifacts. With independent versioning and releasing this can be improved to build and release only the changed (affected) modules. This drastically reduces the build times and increases the efficiency in CI/CD.
Describe the improvement
As Jenkins, out of the box doesn't support such behavior, moving the release workflow to a GitHub Action should be considered.
A GitHub Action can build the affected modules and push artifacts to NEXUS by combining changesets with a custom release script.

Release builder improvements are completed implementation-wise. As there is a major folder restructuring to accomplish separate versioning [https://github.com/wso2/product-is/issues/16417], planning to merge the changes after the jsp-apps and console refactoring changes are merged. Therefore pushing the milestone.

Release workflow improvement is completed along with the separate app versioning. Product-is end improvement is yet to be merged due to integration test failures.

Product-is end improvement is merged.


Dimensions of Icon in golden image test seem wrong

In a golden image test where I have an Icon widget, the generated screenshot seems a bit off. In the example I have Container (size: 60x60) which has an Icon (size: 50x50) as a child. Since the alignment is set to centre, I would expect that the spacing between the icon box and the outer container, would be the same on all sides. What I get is the following:

Is this the expected behaviour? Did I miss something in the setup of the test?
Steps to Reproduce
import 'dart:io';

import 'package:flutter_test/flutter_test.dart';
import 'package:flutter/material.dart';

void main() {
  Widget testWidget() => MaterialApp(
        home: Scaffold(
          body: RepaintBoundary(
            child: Container(
              width: 70.0,
              height: 70.0,
              alignment: Alignment.center,
              decoration: const BoxDecoration(
                color: Colors.green,
              ),
              child: const Icon(Icons.add_a_photo, size: 50.0),
            ),
          ),
        ),
      );

  testWidgets('test 1', (WidgetTester tester) async {
    await tester.pumpWidget(testWidget());
    await expectLater(
      find.byType(Container),
      matchesGoldenFile('golden_images/test1.png'),
      skip: !Platform.isMacOS,
    );
  });
}

Flutter analyze
flutter analyze
Analyzing dachue...
No issues found! (ran in 32.1s)

Flutter doctor
flutter doctor -v
[✓] Flutter (Channel unknown, v0.9.2, on Mac OS X 10.13.6 17G65, locale en-NL)
    • Flutter version 0.9.2 at /Users/user/IdeaProjects/dachue/flutter
    • Framework revision 85b4670b2a (5 weeks ago), 2018-09-19 14:59:23 -0700
    • Engine revision 2e8e96fad1
    • Dart version 2.1.0-dev.4.0.flutter-4eb879133a

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.io/setup/#android-setup for detailed instructions).
      If Android SDK has been installed to a custom location, set $ANDROID_HOME to that location.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.0, Build version 10A255
    • ios-deploy 2.0.0
    • CocoaPods version 1.5.3

[✗] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.io/setup/#android-setup for detailed instructions).

[✓] IntelliJ IDEA Community Edition (version 2018.1.6)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 27.1.2
    • Dart plugin version 181.4892.1

[✓] Connected devices (1 available)
    • iPhone XS • 68C9BA47-3E93-41B9-96BD-AFA0F1F777A6 • ios • iOS 12.0 (simulator)

! Doctor found issues in 2 categories.

I think this is working as intended.
As far as I know square is not the border of the icon, but just a default character from the font used in tests and it's one without descender.

@zoechi, that's a pity. Then in this case I'll use normal widget tests instead.

I think I saw some comments recently about supporting assets and fonts in tests. That should fix this problem.
Currently golden tests are still failing if the icon is rendered differently than it was when you created the reference file. So you still have some safeguard against unintended layout changes.


Handle both 201 and 202 response codes as success

During a demo we saw a 202 response code printed out as a "Failure". I did see a fix for that yet and so I wanted to open an issue so we don't forget about it.

I accepted the 202 response when creating documents and databases. I do not believe that either of those are possible when doing things like creating/deleting cookies and modifying permissions. At least I did not see anywhere in the documentation where they were possible. They were only explicitly stated for creating documents and databases.


error[E0425]: cannot find function generate_header in crate taskchampion_lib in release mode

chromy@astra ~/s/taskchampion (main) [101]> cargo --version
cargo 1.77.2 (e52e36006 2024-03-26)
chromy@astra ~/s/taskchampion (main)> rustc --version
rustc 1.77.2 (25ef9e3d8 2024-04-09)
chromy@astra ~/s/taskchampion (main)> cargo build -r
   Compiling xtask v0.5.0 (/home/chromy/src/taskchampion/xtask)
error[E0425]: cannot find function `generate_header` in crate `taskchampion_lib`
   --> xtask/src/main.rs:50:49
    |
50  |     write!(&mut file, "{}", ::taskchampion_lib::generate_header()).unwrap();
    |                                                 ^^^^^^^^^^^^^^^ not found in `taskchampion_lib`
    |
note: found an item that was configured out
   --> /home/chromy/src/taskchampion/lib/src/lib.rs:170:8
    |
170 | pub fn generate_header() -> String {
    |        ^^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0425`.
error: could not compile `xtask` (bin "xtask") due to 1 previous error

Hopefully GothenburgBitFactory/taskchampion#3426 will make tc-lib unnecessary, but until then perhaps we should just remove the conditional attribute.


Redux persist integration

Integration with redux presist
I was able to do it to some extent, but things like dynamic reducers still confuse me.
I have a working integration model but I am unable to figure out the behavior of the reconciler of redux-persist. It's very weird
Redux persist v5 has 270 issues pending and is very primitive.
Problems

Integrate with dynamically injected reducers from react-loadable.
Integrate with hot-reload
Persist merge mechanism (stateReconciler) needed for this sort of project.

configureStore.js
/**
 * Create the store with dynamic reducers
 */

import { createStore, applyMiddleware, compose } from 'redux';
import { fromJS } from 'immutable';
import { routerMiddleware } from 'react-router-redux';
import thunk from 'redux-thunk';
import createReducer from './reducers';
import immutableTransform from 'redux-persist-transform-immutable';
import { persistStore, persistReducer } from 'redux-persist';
import {
  stateIterator,
  stateGetter,
  stateSetter,
  stateReconciler,
  lastStateInit,
} from 'redux-persist-immutable-state';
import localforage from 'localforage';
import storage from 'redux-persist/lib/storage'; // defaults to localStorage for web and AsyncStorage for react-native
import autoMergeLevel2 from 'redux-persist/lib/stateReconciler/autoMergeLevel2';

const persistConfig = {
  debug: true,
  transforms: [immutableTransform()],
  key: 'root',
  reducerVersion: '1.0',
  stateReconciler: stateReconciler,
  storage: localforage,
  stateIterator: stateIterator,
  stateGetter: stateGetter,
  stateSetter: stateSetter,
  lastStateInit: lastStateInit,
};
const persistedReducer = persistReducer(persistConfig, createReducer());

export default function configureStore(initialState = {}, history) {
  // Create the store with two middlewares
  // 1. X sagaMiddleware: Makes redux-sagas work
  // 2. routerMiddleware: Syncs the location/URL path to the state
  const middlewares = [thunk, routerMiddleware(history)];

  const enhancers = [applyMiddleware(...middlewares)];

  // If Redux DevTools Extension is installed use it, otherwise use Redux compose
  /* eslint-disable no-underscore-dangle, indent */
  const composeEnhancers =
    process.env.NODE_ENV !== 'production' &&
    typeof window === 'object' &&
    window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__
      ? window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__({
          // TODO: Try to remove when `react-router-redux` is out of beta, LOCATION_CHANGE should not be fired more than once after hot reloading
          // Prevent recomputing reducers for `replaceReducer`
          shouldHotReload: false,
        })
      : compose;
  /* eslint-enable */
  if (process.env.NODE_ENV !== 'production') {
    persistConfig.storage = storage;
  }

  const store = createStore(persistedReducer, initialState, composeEnhancers(...enhancers));

  // Extensions
  store.injectedReducers = {}; // Reducer registry

  // Make reducers hot reloadable, see http://mxs.is/googmo
  /* istanbul ignore next */
  if (module.hot) {
    module.hot.accept('./reducers', () => {
      // please use with caution to persist dynamic reducers with redux persist
      // store.replaceReducer(persistReducer(persistConfig, createReducer(store.injectedReducers)));
      store.replaceReducer(store.injectedReducers);
      persistor.persist();
    });
  }
  const persistor = persistStore(store);
  store.persistor = persistor;
  window.store = store;
  return store;
}

reducers.js
import { fromJS } from 'immutable';
import { combineReducers } from 'redux';

reducerInjectors.js
    store.injectedReducers[key] = reducer; // eslint-disable-line no-param-reassign
    store.replaceReducer(createReducer(store.injectedReducers));
    store.persistor.persist();

I have removed the top level immutable for this.
Let me know if you are able to help it.
I will update another implementation with redux-persist-immutable where I am facing issues with dynimically injected reducers not getting rehyderated.

Yes, sure thanks for the help. If you can have any other suggestions to persist redux data with localstorage, because while building any app my data gets remove on refresh. So I don't know if any other out of the box solution to do it. Thanks for building such a wonderful project.

Sure! I think my first guess would be to skip the "magic" of redux-persist and just pick a well-maintained browser storage library with no relation to redux (such as store.js or localForage). Then wrap your reducers' initialStates in a helper function which checks for persisted state or returns a default initialState. And something similar in the reducer to save the data you want to persist.
This seems like overkill if you're only doing it to make up for the shortcomings of hot reloading though (vs as an actual feature of your app).
(I didn't build this project, just helping maintain it)

@julienben I was able to integrate redux-persist-immutable successfully with RB, not sure if that is what @arindampradhan is asking for.

@satishjhanwer could you please share somewhere?

inside configureStore.js
add this import statement
import { persistStore, autoRehydrate } from 'redux-persist-immutable';
and the below code
  /* istanbul ignore next */
  if (process.env.NODE_ENV !== 'test') {
    enhancers.push(autoRehydrate());
  }

  return (done) => {
    // Un-comment following lines to enable persistance to local-storage.
    /* istanbul ignore next */
    if (process.env.NODE_ENV !== 'test') {
      persistStore(store, { blacklist: ['route', 'form'] }, () => done(store));
    }
  };

@satishjhanwe can you give more context on where in the file your suggested snippets should go?

@Get-Kraken You need to place the enhancer.push() snippet right after the const enhancer line and the other snippet at the end of the file replacing this return store;. I hope its clear now.

Cool thanks - all working now :)


Blueprint-related refactoring

There are several pieces of refactoring that will benefit the ongoing blueprint migration:

[x] Rename or encapsulate DataResultTree -> QueryResult and move DataQuery evaluation earlier in the frame:

Will be done in: https://github.com/rerun-io/rerun/pull/4310
The location is roughly app_state.rs :: show() or equivalent. Right before we create ViewerContext.
All QueryResults will be added to the ViewerContext.
Invocations of execute_query and resolve from the DataQuery trait are instead replaced by something that looks up the QueryResult in the ViewerContext.
Future: QueryResult can be merged with the QueryCache logic.

[x] Replace SpaceViewContents with DataQuery

Will be done in: https://github.com/rerun-io/rerun/pull/4311
Everywhere that we use SpaceViewContents needs to use an appropriate QueryResult instead

[ ] Moved to: https://github.com/rerun-io/rerun/issues/4440
Refactor blueprint lifecycle, construction and component patterns.

Each type: ViewportBlueprint, ContainerBlueprint, SpaceViewBlueprint, DataQueryBlueprint should follow the same design.  They are generally considered to be read-only views of the blueprint on the current frame. They should always store their own BlueprintId, which is mappable to an EntityPath used to store any edits. These edits are always deferred through the CommandSender and won't be visible until the next frame.  The basic pattern should look like:/// Create a new ephemeral blueprint entity.
ContainerBlueprint::new() -> ContainerBlueprint;

/// Send the initial state of an ephemeral blueprint entity to the store
/// Should never be used on a non-ephemeral blueprint entity such as created via `from_store`
ContainerBlueprint::save_initial(deferred: &CommandSender);

/// Remove the entity and all of its children
/// Note: because blueprint entities aren't stored hierarchically this will generate multiple clear events.
ContainerBlueprint::clear(deferred: &CommandSender);

/// Load an actual blueprint component from the store.
/// Recursively loads all the referenced types.
ContainerBlueprint::from_store(store: &StoreDb, id: ContainerId) -> ContainerBlueprint {...}

/// Modify some field.
/// Used by UI events to modify the blueprint component. Encapsulates all
ContainerBlueprint::edit_foo(foo: Foo, deferred: &CommandSender)

When this is complete, sync_viewport_blueprint should be completely gone.

[ ] Moved to: https://github.com/rerun-io/rerun/issues/4441

Deprecate "groups" as a concept from the DataResultTree.

Now we have "groups" which map to override-recursive and "entities' which map to override-individual
After we will have entities with two override paths: "override" and "override_recursive". The UI can then choose which path to use depending on some context of how the override is being set (i.e. a flag for "apply to children")

Closing in favor of new explicit issues.


Service Principal Creation Update

az ad sp create-for-rbac no longer takes --username --password, maybe update to az ad sp create-for-rbac --sdk-auth

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

ID: a310f63f-d11a-2b6a-0abd-4b75f543676b
Version Independent ID: 21c8a211-1f42-9448-b72e-c84a52ae9ad2
Content: Tutorial - Scale Jenkins deployments with Azure VM agents
Content Source: articles/jenkins/scale-deployments-using-vm-agents.md
Service: jenkins
GitHub Login: @TomArcherMsft
Microsoft Alias: tarcher

Hey @angelo-loria,
I could not find any reference to the az ad sp command within the linked documentation. Perhaps it's been removed since you filed the issue, or the wrong article was linked. Because I can't find the reference, I'm closing the issue. Please let me know if the mistake remains and I'll investigate.
Thank you,


Switch to use a new relay chain module

@toshihiko-okubo could you review this?

@dongrie sorry, the previous commit has conflict with the latest v0.3. I've rebased with the latest one, so can you review this again?


tcl 8.7/tk8.7: init at a5

Description of changes
Added Tcl/Tk 8.7a5. These packages must be added together per the comments in their source.
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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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.

Tcl 8.7 seems to have been dropped in favor of proceeding straight to 9.0.


promptfoo: 0.28.0 -> 0.33.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/promptfoo/promptfoo/releases.
meta.description for promptfoo is: Test your prompts, models, RAGs. Evaluate and compare LLM outputs, catch regressions, and improve prompt quality.
meta.homepage for promptfoo is: https://www.promptfoo.dev/
meta.changelog for promptfoo is: https://github.com/promptfoo/promptfoo/releases/tag/0.33.2
Updates performed

NPM version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.33.2 with grep in /nix/store/zcxi7jajf92c7nh3yzddq9hl5sjm91yf-promptfoo-0.33.2
found 0.33.2 in filename of file in /nix/store/zcxi7jajf92c7nh3yzddq9hl5sjm91yf-promptfoo-0.33.2

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
promptfoo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/zcxi7jajf92c7nh3yzddq9hl5sjm91yf-promptfoo-0.33.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/798437ac6b0662fabd84ccf5907d5004dedb0c15#promptfoo

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/zcxi7jajf92c7nh3yzddq9hl5sjm91yf-promptfoo-0.33.2
ls -la /nix/store/zcxi7jajf92c7nh3yzddq9hl5sjm91yf-promptfoo-0.33.2/bin

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

1 package built:

promptfoo

Maintainer pings
cc @silvergasp for testing.

Looks good to me


Create values.yaml examples

Create values.yaml examples for deployment 1 click deployment help
like
helm install foundry-vtt foundry-vtt/ -f example/eks.aws.values.yaml

This will install based on a EKS configuraiton with ISRA and related needs, same for
GKE
AKS
SelfManaged
K3S
And also include
nginx & traefik intgress controller variantes for all

Working on examples:

s3 with json
s3 with environment variable + service account
contour without TLS
contour with TLS
nginx without TLS
nginx with TLS


Can't add comment on task card modal.

Describe the bug
I can't add link comment on task card, for example the comment content is: https://github.com/JordanKnott/taskcafe/issues/new?assignees=&labels=&template=bug_report.md&title=
and the page will be crashed.
Expected behavior
What did you expect to happen?
Screenshots / Live demo link
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Please send the Taskcafe web service logs if applicable.

This should be fixed in the latest (0.3.2) version.


When will the source code be available to the public?

excellent work！

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx


Improve logging and add events

The rcs-ocm-deployer code currently includes some very basic logging and this should be enriched so that the code is easier to debug.

/kind feature
/assign sahar2339


Frontend improvements

Closes #105, closes #108, closes #109
Changes:

Fix bug on receive table to show addresses properly. Now using the same format as MetaMask, e.g. 0x1234...abcd
Add contact and FAQ pages. FAQ page just has a few placeholder questions with "TODO" as the answer for now

As part of this, we remove route guards, so you can now visit any page directly (instead of being forced to go through the home page) and will be asked to connect your wallet as needed

Add support for all ENS domains to the Send page
Small improvement to the user wallet info is saved to the store, which provides better UX

Now using the same format as MetaMask, e.g. 0x1234...abcd

This looks much better! I wonder if we can find some way for the user to view/copy the full address? Maybe tooltip full address on hover and click to copy?


Tag Based Default Thumbnail Templates

Modifies thrimshim.get_row to choose the default thumbnail template based on tags and modifies sheetsync to determine the shift of an event and added it as a tag.

I believe I have addressed all of your comments ekim. I added a bit more code to sheetsync to make things more robust if no shift definitions are provided or there are errors parsing the shift definition.

I have now tested the thrimshim part of the changes and thethrimshim can correctly select templates using tags and the playlists table.


qbs: 1.22.0 -> 1.23.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/qbs/versions.
meta.description for qbs is: "A tool that helps simplify the build process for developing projects across multiple platforms"
meta.homepage for qbs is: "https://wiki.qt.io/Qbs"
meta.changelog for qbs is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.23.0 with grep in /nix/store/24fmjnq0qpgbmzp3i2iks7c9mvaw4z4h-qbs-1.23.0
found 1.23.0 in filename of file in /nix/store/24fmjnq0qpgbmzp3i2iks7c9mvaw4z4h-qbs-1.23.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
qbs

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/24fmjnq0qpgbmzp3i2iks7c9mvaw4z4h-qbs-1.23.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/24fmjnq0qpgbmzp3i2iks7c9mvaw4z4h-qbs-1.23.0
ls -la /nix/store/24fmjnq0qpgbmzp3i2iks7c9mvaw4z4h-qbs-1.23.0/bin

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

1 package built:

qbs

Maintainer pings
cc @expipiplus1 for testing.

built went fine on NixOS 22.05 x64 Linux
1 package built:
qbs

Programs also seem to work and upstream changelog look lightweight
@expipiplus1 Qbs can probably updated to Qt6, at least the changelog notes support for it


COPY failed when building with --state flag

when running img build -s <folder> -f Dockerfile -t <tag> ., it failes on COPY command.
once -s <folder> is taken, it can build successfully.
#11 [compilation 4/8] COPY . /go/src/github.com/
#11       digest: sha256:9f9d8f9ec942454a48bae9f769a75a85c9057d0fc7667e0d72e75ed38ba5c866
#11         name: "[compilation 4/8] COPY . /go/src/github.com/"
#11      started: 2018-11-30 06:56:57.154522146 +0000 UTC m=+213.053313865
#11 0.129 container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:58: mounting \\\"overlay\\\" to rootfs \\\"/tmp/build/2ebbeb81/cache/runc/overlayfs/executor/qg593ckedekv12831f4nevs99/rootfs\\\" at \\\"/tmp/build/2ebbeb81/cache/runc/overlayfs/executor/qg593ckedekv12831f4nevs99/rootfs/dest\\\" caused \\\"no such file or directory\\\"\""
#11    completed: 2018-11-30 06:56:57.465694351 +0000 UTC m=+213.364486108
#11     duration: 311.172243ms
#11        error: "executor failed running [copy /src-0 go/src/github.com/]: exit code: 1"

error reproduce:
runtime && setup:
○ → uname -a
Linux huan-Inspiron-5379 4.18.0-11-generic #12-Ubuntu SMP Tue Oct 23 19:22:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

○ → docker --version
Docker version 18.06.1-ce, build e68fc7a

○ → docker run --entrypoint sh --user root --rm -it --privileged r.j3ss.co/img
/ # mkdir -p /tmp/temp && cd /tmp/temp

/tmp/temp # mkdir cache context dockerfile

/tmp/temp # cat <<'EOF' > dockerfile/Dockerfile
> FROM ubuntu
> COPY . /tmp
> EOF

/tmp/temp # tree            # installed using `apk add tree`
.
├── cache
├── context
└── dockerfile
    └── Dockerfile

testing:
/tmp/temp # img build -f dockerfile/Dockerfile -t test context/
Building docker.io/library/test:latest
Setting up the rootfs... this may take a bit.
[+] Building 1.9s (8/8) FINISHED
 => [internal] load .dockerignore                                             0.0s
 => => transferring context: 2B                                               0.0s
 => [internal] load build definition from Dockerfile                          0.0s
 => => transferring dockerfile: 61B                                           0.0s
 => [internal] load metadata for docker.io/library/ubuntu:latest              0.8s
 => CACHED [internal] helper image for file operations                        0.0s
 => => resolve docker.io/tonistiigi/copy:v0.1.9@sha256:e8f159d3f00786604b93c  0.0s
 => [internal] load build context                                             0.0s
 => => transferring context: 2B                                               0.0s
 => CACHED [1/2] FROM docker.io/library/ubuntu@sha256:6d0e0c26489e33f5a6f002  0.0s
 => => resolve docker.io/library/ubuntu@sha256:6d0e0c26489e33f5a6f0020edface  0.0s
 => [2/2] COPY . /tmp                                                         0.6s
 => exporting to image                                                        0.5s
 => => exporting layers                                                       0.4s
 => => exporting manifest sha256:c2575f4e9a615f4f58b78e77918a449cdf6b85ec0eb  0.0s
 => => exporting config sha256:ec88ee2b1ee574f7ad6faf11d86619a36d05939771ae9  0.0s
 => => naming to docker.io/library/test:latest                                0.0s
Successfully built docker.io/library/test:latest

/tmp/temp # img build -s cache -f dockerfile/Dockerfile -t test context/
Building docker.io/library/test:latest
Setting up the rootfs... this may take a bit.
[+] Building 1.3s (7/7) FINISHED
 => [internal] load .dockerignore                                             0.0s
 => => transferring context: 2B                                               0.0s
 => [internal] load build definition from Dockerfile                          0.0s
 => => transferring dockerfile: 31B                                           0.0s
 => [internal] load metadata for docker.io/library/ubuntu:latest              0.7s
 => [internal] load build context                                             0.0s
 => => transferring context: 2B                                               0.0s
 => CACHED [1/2] FROM docker.io/library/ubuntu@sha256:6d0e0c26489e33f5a6f002  0.0s
 => => resolve docker.io/library/ubuntu@sha256:6d0e0c26489e33f5a6f0020edface  0.0s
 => CACHED [internal] helper image for file operations                        0.0s
 => => resolve docker.io/tonistiigi/copy:v0.1.9@sha256:e8f159d3f00786604b93c  0.0s
 => ERROR [2/2] COPY . /tmp                                                   0.5s
------
 > [2/2] COPY . /tmp:
#7 0.440 container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"rootfs_linux.go:58: mounting \\\"/tmp/temp/cache/runc/native/executor/0ce4hpp715qbvwg8gj8y5vwxa/cache/runc/native/snapshots/snapshots/13\\\" to rootfs \\\"/tmp/temp/cache/runc/native/executor/0ce4hpp715qbvwg8gj8y5vwxa/rootfs\\\" at \\\"/dest\\\" caused \\\"stat /tmp/temp/cache/runc/native/executor/0ce4hpp715qbvwg8gj8y5vwxa/cache/runc/native/snapshots/snapshots/13: no such file or directory\\\"\""
------
failed to solve: executor failed running [copy /src-0 tmp]: exit code: 1

What's the filesystem of the directory?
Either changing the directory or specifying native snapshotter should work.

both are btrfs. I don't think its file system's problem. Because if I symlink the cache directory to /home/user/.local/share/img, then I can run img build -f dockerfile/Dockerfile -t test context/ just fine. And all the contents are successfully cached in the cached directory

I've had a very similar issue that in the end was due to hitting the page size limitation on mount arguments. On overlay mounts as carried out by img / runc, the "lower" argument in the mount data grows with every layer added. When the mount data hits 8192 bytes in my case, the build process failed with the confusing error above. In my case I could not build Dockerfiles with more than around 80 layers. I extended the number of layers that could be build properly by using a very short path to state and specified that using the "-s" parameter.
Docker at one time ran into the same issue apparently:

https://github.com/portworx/docker_docs/blob/master/docs/userguide/storagedriver/overlayfs-driver.md

Further discussion:

https://github.com/moby/moby/issues/26380


Need update to support flutter last version

Synchronous waiting using dart:cli waitFor and C API Dart_WaitForEvent is deprecated and disabled by default. This feature will be fully removed in Dart 3.4 release. You can currently still enable it by passing --enable_deprecated_wait_for to the Dart VM. See https://dartbug.com/52121.

Yes, we have noted this internally. because we have a dependency on the Dcli package and that doesn't completely solve the problem. I hope I can fix it as soon as possible.

hi @the-best-is-best  we have a rebrand for this gits_cli to morpheme_cli and this issue has already fixing in morpheme_cli. you can try and check
https://morphemedesign.github.io/morpheme-flutter-documentation/
https://pub.dev/packages/morpheme_cli

now this issue can be closed


Turn into Kotlin ?

Really nice and clean work guys,
If you want to move to the next level I can turn it into Kotlin for you, it will remove tons of boilerplate code.
Give me a green-light if you want me to do it.

Thanks for the interesting offer!
However, as I'm the main maintainer of this codebase and I'm not well-versed in Kotlin at the moment, I don't think it would be a good idea right now.


Issue with k8s.io/docs/tutorials/hello-minikube/

This is a Bug Report

Problem: Minikube unable to expose the service to external ip
$ minikube service hello-node
| NAMESPACE |    NAME    | TARGET PORT |           URL
| default   | hello-node |        8089 | http://<IP_ADDRESS>:31019 |
🎉  Opening service default/hello-node in default browser...
rajendra@master:~$ Opening in existing browser session.
[0606/234938.552552:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
Most likely you need to configure your SUID sandbox correctly
Proposed Solution: Waiting for the inputs here
Page to Update:
https://kubernetes.io/docs/tutorials/hello-minikube/

@rpcyn can you describe the environment where you're running Minikube? It sounds like there might be some issue with the integration between Minikube and your preferred web browser.
/triage needs-information

Please report the bug to the minikube project because this doesn't look like a doc issue.
/close


Added purge command

This is a priority addition requested by Molls.

Adds =purge_inactive command, which asks if you would like to remove all inactive officers, then does so.
Added automatic role removal in OfficerManager.remove_officer. All LPD ranks and roles will be removed.
Altered OfficerManager.is_officer()  to prevent attempted double-removal of an officer when the LPD role is removed by the bot

We won't be pursuing this because of the cost if it ever malfunctions


[Bug]  error: unknown field "spec.primaryService.annotations"

Describe the bug
When setting annotations in service or primary / secondary Service this pops up:
  primaryService:
    type: LoadBalancer
    annotations:
      external-dns.alpha.kubernetes.io/hostname: mariadb-001-pri.ns.bla.local

-> strict decoding error: unknown field "spec.primaryService.annotations"

when using metadata like this:
  primaryService:
    type: LoadBalancer
    metadata:
      annotations:
        external-dns.alpha.kubernetes.io/hostname: mariadb-001-pri.ns.bla.local

it is applied but won't get applied to the service
Environment details:

Kubernetes version: 1.25
Kubernetes distribution: Vanilla
mariadb-operator version: 0.0.27
Install method: helm to static
Install flavor: helm template?

Hey there @blodone ! thanks for reporting
Sorry, the example manifests in main correspond to version v0.0.28, yet to be released.
This is fixed via https://github.com/mariadb-operator/mariadb-operator/pull/537 and will be shipped shortly with v0.0.28. Stay tuned and sorry for the inconvnience!


Add test for appending headers

Relates to #4.
/cc @ricardochimal @shurcooL

I've tested this on my integration tests and it's passing, once you're OK with it @ricardochimal I'll merge and tag the release.


"Paragraphs" link incorrect in Section component

The "Paragraphs" link in the section component top paragraph is incorrect.
The link is currently: https://grommet.github.io/hpe/docs/pargraph
It should be: https://grommet.github.io/hpe/docs/paragraph
Should also add appropriate spacing between links in this paragraph.
Your Environment

Browser Name and version: Firefox 48.0 and Chrome 53.0.2785.116

Fixed in https://github.com/grommet/grommet-docs/commit/e89c0354c41a90e978feac50feb36b6e4c96ee07


Update the note message when logging in to make it easier to understand and clearer

It's simply a message update that helps lazy people like me know what they need to do when they're in a hurry on their notebook.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Enable all extensions by default

Common other logging libs like log4j or slf4j allow to crate namespaced loggers too. However, they always output those loggers by default.
It would greatly increase the workflow if one would not have to manually add each namespaced logger to the config.
Instead how about treating enabledExtensions as an include list only if it exists. Otherwise all extensions are enabled by default.
We could also think about something like the well known node package debug does by enabling fine grained sub-loggers via wildcards.

Actually, your idea is not wrong, it makes much more sense to leave them enabled by default.
Using instead the debug way I think is complex especially if we want to maintain the current performance (to use the package well in production).
In the next version I will change enabledExtensions to an inclusive list. Thanks!

@alessandro-bottamedi is this already in the current version?

@pke i've been messing with for the last three days. you still have to enable the extension after you declare it.

Sorry for the delay, I have been busy at work, I will update you in the next few days on the progress

Since v 4.0.0 the extension system has been reversed, now if they are not set in the config, the logger will show them all.

Hurray thanks for implementing that!


Make sure all pip dependencies are updated

It turns out ansible pip state: latest does not update package dependencies. To make sure every [packagename] deploy uses the most recent version of packages, a seperate pip install -U on outdated packages needs to be performed.
This PR supersedes https://github.com/SURFscz/SCZ-deploy/pull/134

I'm still hesitant to accept this PR.  I would really like some solution in which I can fix the versions, so that deployments are reproducible and versions can't change between deployments.
For bonus points, the script might also emit a warning if the versions are not up to date.
For even more bonus points, we would use as many distribution packages are possible.
I'll breed on this a little bit and see if I can think something up.

#137 has a nice list of distribution packages that can be used.

No it hasn't: https://github.com/SURFscz/SCZ-deploy/pull/137#issuecomment-429873662

well, a number of them, anyway ;)

I would strongly advice you against that plan.

Well, I think there are two possible solutions to the problem:

ﬁx the versions of all dependencies in SCZ-deploy config, so that we are always sure which versions  are installed
change the current release model and switch to deploying docker containers instead of managing virtualenvs by hand (or ansible) for satosa and pyff

The first is sort of feasible (but hard to test and might break things).  The second is great for the long term, but quite invasive.
Maybe we should not try to solve the general case now.  Can we just upgrade only pysaml to the correct version, and leave everything else be?  Then we can worry about the other dependencies later.

I think the best solution is to ship a pi freeze based requirements.txt with our ansible deploy and pip install that in the virtualenv before installing the application. See https://github.com/SURFscz/SCZ-deploy/pull/137/commits/993b9e7b1e6724bcaaaa3277d2323fe0194bc90d


Closes: #1

Updated validations.py python script.
Fixed the code error in the function validate_user and comment to reflect the change.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Update the NPM package

Will the npm package ever be updated?

When we have a working travis test I think is a good time to update the npm package.


C34360: Converting reserved words to codebox to avoid localization issues

Hello, @MandiOhlinger,
Localization team has reported source content issue that causes localized version to have broken/different format compared to en-us version.
"Converting reserved words to codebox to avoid localization issues and also escaping links that must be shown as text"
Please review and merge the proposed file change to fix to target versions. If you make related fix in another PR  then share your PR number so we can confirm and close this PR.
Many thanks in advance.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/adapter-oracle-database/message-schemas-for-functions-and-procedures.md
:white_check_mark:Succeeded
View

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

Thanks @MandiOhlinger


stdenv's linuxHeaders (or allowedRequisites) incorrect in the presence of overlays overriding glibc

Consider the following expression, where we apply an overlay that uses an older NixOS release's glibc with newer nixpkgs (the motivation for such an overlay might be building DSOs that may be linked and loaded on some other Linux distribution).
let recentNixpkgsSrc = builtins.fetchGit
    {
        url = "https://github.com/nixos/nixpkgs";
        ref = "master";
        rev = "7c7d71d90e7d715847809a65fa2463c668e58ab3";
    };
    olderNixpkgsSrc = builtins.fetchGit
    {
        url = "https://github.com/nixos/nixpkgs";
        ref = "nixos-19.09";
        rev = "75f4ba05c63be3f147bcc2f7bd4ba1f029cedcb1";
    };
    oldPkgs = import olderNixpkgsSrc {};
    overlay = self: super: rec
    {
        glibc = oldPkgs.glibc // {pname = "glibc";};
        glibcLocales = oldPkgs.glibcLocales;
        glibcIconv = oldPkgs.glibcIconv;
        stdenv = super.stdenv //
        {
            overrides = self2: super2: super.stdenv.overrides self2 super2 //
            {
                glibc = glibc;
            };
        };
    };
in import recentNixpkgsSrc {overlays = [overlay];}

Based on https://github.com/NixOS/nixpkgs/blob/master/pkgs/stdenv/linux/default.nix, I'd expect to get a working stdenv with the older glibc (assuming that glibc 2.27 works with current master's toolchain, and it happens to for the revs I've chosen) and I do, until I get to the allowedRequisites check
$ nix-build ./repro.nix -A hello
...
building '/nix/store/n28xd4xq6f11lcbc1ir5lszc2bfj4n23-stdenv-linux.drv'...
output '/nix/store/cmk1rwz6raj480fqvv7rvxcabdmqh9k6-stdenv-linux' is not allowed to refer to the following paths:
  /nix/store/b3vajivl1gvq1c2p1x62672sqg8f983l-linux-headers-4.19.16

Initially one might try to fix this by getting linuxHeaders from the older nixpkgs too:
    overlay = self: super: rec
    {
        glibc = oldPkgs.glibc // {pname = "glibc";};
        glibcLocales = oldPkgs.glibcLocales;
        glibcIconv = oldPkgs.glibcIconv;
        linuxHeaders = oldPkgs.linuxHeaders;
        stdenv = super.stdenv //
        {
            overrides = self2: super2: super.stdenv.overrides self2 super2 //
            {
                glibc = glibc;
                linuxHeaders = linuxHeaders;
            };
        };

However, this doesn't work, because pkgs.linuxHeaders is somehow not the same linuxHeaders that's passed as input to glibc:
Welcome to Nix version 2.3.16. Type :? for help.

nix-repl> pkgs = import ./repro.nix

nix-repl> pkgs.linuxHeaders
«derivation /nix/store/n3vbnnrggh7prji14g1g2iizdjh06afq-linux-headers-4.19.16.drv»

nix-repl> pkgs.glibc.buildInputs
[ «derivation /nix/store/z0bf9m7i2228smqc97akym9ps6a0jrd7-linux-headers-4.19.16.drv» ]

The way allowedRequisites is computed in stdenv-linux suggests that stdenv needs to be given the same linuxHeaders that was used to build glibc, so this (totally cursed) overlay actually works:
    overlay = self: super: rec
    {
        glibc = oldPkgs.glibc // {pname = "glibc";};
        glibcLocales = oldPkgs.glibcLocales;
        glibcIconv = oldPkgs.glibcIconv;
        stdenv = super.stdenv //
        {
            overrides = self2: super2: super.stdenv.overrides self2 super2 //
            {
                glibc = glibc;
                linuxHeaders = builtins.head glibc.buildInputs;
            };
        };

$ ldd $(nix-build ./repro.nix -A hello)/bin/hello
        linux-vdso.so.1 (0x00007ffd48462000)
        libc.so.6 => /nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/libc.so.6 (0x00007fcefe42e000)
        /nix/store/wx1vk75bpdr65g6xwxbj4rw0pk04v5j3-glibc-2.27/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007fcefe3bd000)

So it seems to me, one of these must be true:

This bit here https://github.com/NixOS/nixpkgs/blob/master/pkgs/stdenv/linux/default.nix#L421 is grabbing the wrong linuxHeaders if stdenvOverrides are used (although I can't work out how the stdenv bootstrap staging machinery works, so I'm not sure what's wrong).
If stdenv must be passed the same linuxHeaders that's passed to glibc (and I assume that linuxHeaders that's different from top-level pkgs.linuxHeaders comes from inside the bootstrap machinery somewhere), shouldn't it grab it from glibc somehow (hopefully through a passthru and not the abomination builtins.head glibc.buildInputs?
The most likely answer: I've misunderstood something about how stdenvOverrides/the stdenv bootstrapping business works.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/derivation-that-builds-standard-linux-binaries/21557/7

You can use linuxHeaders = glibc.linuxHeaders; instead of linuxHeaders = builtins.head glibc.buildInputs;. However, when I try this I get the following error:
error: assertion '(libc_bin == (bintools).libc_bin)' failed

       at /nix/store/wdf2jhfwsn294yk4n91fhz660bi9l0np-source/pkgs/build-support/cc-wrapper/default.nix:119:1:

          118| # Ensure bintools matches
          119| assert libc_bin == bintools.libc_bin;
             | ^
          120| assert libc_dev == bintools.libc_dev;
(use '--show-trace' to show detailed location information)

Do you know how to make these versions match?


Farsi Support 🇮🇷🇦🇫🇹🇯

First attempt in Adding Farsi Language support.
Start of https://github.com/microsoft/TypeScript-Website/issues/278
cc: @orta

 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.:x: ashkan18 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

All i8n details here: https://github.com/microsoft/TypeScript-Website/issues/100

Hey, How can I help this move forward? This can be merged for now and I make a follow up for fixes. What do you think?

Hi @Ladsgroup , sorry I've been in between switching jobs now and haven't had a chance to address your feedback, they all make sense to me, just need to find time and do it. Bu everything works for me, this is going to be an ongoing teamwork anyways. ❤

Yep, merging this and improving in the future is fine with me 👍
@ashkan18 - is there a good day for our pairing session? I'm free weds-fri, and thanks to COVID19, I've got a completely empty two weeks of plans next week as I'm not out in redmond

Thanks @orta just came to address some comments 😄 i'll have time next week if that works for you, we can finalize it on slack but i'll be out of town from tomorrow till Sunday.


Node.js v18 Compatibility Test for [dashboards-observability]

Introduction
As part of our continued efforts to improve OpenSearch Dashboards, we are planning to upgrade the underlying Node.js version from v14 to v18. This change will enhance performance, add new features, and bolster security. However, such major version changes might also affect the compatibility of existing plugins. Here is more introduction: https://github.com/opensearch-project/OpenSearch-Dashboards/issues/3601.
Therefore, we kindly request assistance in testing this plugin the compatibility of with this new version of Node.js. We've prepared a branch with the Node.js v18 upgrade, which you can find here:
https://github.com/AMoo-Miki/OpenSearch-Dashboards/tree/node-18-webpack-4
Steps to Proceed

If you think your plugin won't be affected by OpenSearch Dashboards Node.js upgrade. Pls ignore the rest steps and close the issue directly.
Pull the provided branch that includes the Node.js v18 upgrade and OpenSearch 3.0.0.
Hook up your plugin with the updated OpenSearch Dashboards.
Run your existing test suites and perform manual testing as necessary.
If no issues are encountered, feel free to close this issue.
If there are any problems, report them in this issue thread and also link them in the overall OpenSearch Dashboards Node.js upgrade issue thread https://github.com/opensearch-project/OpenSearch-Dashboards/issues/4058
The purpose of linking any questions or issues back to the main issue is to maintain visibility and transparency among all plugin owners. A problem encountered by one plugin might also affect others. This shared knowledge base will foster collaborative problem-solving and prevent duplication of effort.

We appreciate your support and cooperation in ensuring a smooth transition to Node.js v18 for the entire OpenSearch Dashboards community.

#474

The official Node.js 18 PR raised in OSD: https://github.com/opensearch-project/OpenSearch-Dashboards/pull/4071

We have tested the plugin for node 18 and everything works as expected.


Upstream openshift/origin's project node selector admission controller.

@ncdc
I looked into label selector but it seems that the Parse function seems to be using entire file but still looking if any refactoring is possible. Also need to fix unit tests.

@aveshagarwal I'd suggest just using the upstream label selector code for now. We can add some validation in somewhere to make sure the values only use =

Closing this as now sent to kube: https://github.com/kubernetes/kubernetes/pull/24980


Anyway to modify rumble effect on mouse/trackpad?

Hi, I noticed there's a healthy level of rumble on the left trackpad/d-pad. I was just wondering if there is a way of adding a rumble effect to mouse/trackpad?

It's not currently configurable by client code, but you can modify it - I believe the relevant line is https://github.com/ynsta/steamcontroller/blob/master/src/events.py#L283 for mouse mode but you can look for other lines with "amplitude".
I'm pretty sure the line for D-pad mode is https://github.com/ynsta/steamcontroller/blob/master/src/events.py#L391 so that one's set to 300 - but according to docs on SteamControll::addFeedback() it goes as high as 65535

Thanks so much, I'll give it a go!


Yarn build not working

Yarn build always display this errors
yarn build
yarn run v1.22.5
$ next build
info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
info  - Checking validity of types
./src/pages/index.tsx
33:9  Warning: Do not use . Use Image from 'next/image' instead. See https://nextjs.org/docs/messages/no-img-element.  @next/next/no-img-element
./src/pages/my-nfts.tsx
37:15  Warning: Do not use . Use Image from 'next/image' instead. See https://nextjs.org/docs/messages/no-img-element.  @next/next/no-img-element
./src/components/recaptcha-button.tsx
34:6  Warning: React Hook useCallback has missing dependencies: 'actionName', 'executeRecaptcha', and 'onClick'. Either include them or remove the dependency array. If 'onC
lick' changes too often, find the parent component that defines it and wrap that definition in useCallback.  react-hooks/exhaustive-deps
info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
info  - Creating an optimized production build
info  - Compiled successfully

Build error occurred
TypeError [ERR_INVALID_URL]: Invalid URL: undefined
at onParseError (internal/url.js:279:9)
at new URL (internal/url.js:355:5)
at new Connection (C:\Users\user\ssscc\solana-candy-factory\node_modules@project-serum\anchor\node_modules@solana\web3.js\lib\index.cjs.js:3472:15)
at Object.3924 (C:\Users\user\ssscc\solana-candy-factory.next\server\chunks\924.js:29:20)
at webpack_require (C:\Users\user\ssscc\solana-candy-factory.next\server\webpack-runtime.js:25:42)
at Object.9064 (C:\Users\user\ssscc\solana-candy-factory.next\server\pages_app.js:21:83)
at webpack_require (C:\Users\user\ssscc\solana-candy-factory.next\server\webpack-runtime.js:25:42)
at webpack_exec (C:\Users\user\ssscc\solana-candy-factory.next\server\pages_app.js:155:39)
at C:\Users\user\ssscc\solana-candy-factory.next\server\pages_app.js:156:70
at Function.webpack_require.X (C:\Users\user\ssscc\solana-candy-factory.next\server\webpack-runtime.js:108:21) {
type: 'NodeError',
input: 'undefined',
code: 'ERR_INVALID_URL'
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Same problem for me

You need to have a .env file ready otherwise it will not build.


qqc2-breeze-style: init at 5.21.3

Motivation for this change
For plasma mobile so I'm guessing @samueldr might be interested.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 118637 at d67eaf59 run on x86_64-linux 1

1 package marked as broken and skipped:

libsForQt512.qqc2-breeze-style

1 package failed to build:

libsForQt514.qqc2-breeze-style

1 package built successfully:

libsForQt5.qqc2-breeze-style (libsForQt515.qqc2-breeze-style ,plasma5Packages.qqc2-breeze-style)

1 suggestion:

warning: unclear-gpl
fdl12 is a deprecated license, please check if project uses fdl12Plus or fdl12Only and change meta.license accordingly.
Near pkgs/desktops/plasma-5/default.nix:85:15:
   |
85 |               license = with lib.licenses; [
   |               ^

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement.