Problem with the input function

Description
What steps will reproduce the problem?

I just installed Anaconda, oppened Spyder and a simple input function like m = input("Please, enter first number: ") do not work.
I also can't install scikit-learn on another created environment.
An suggestion to solve this issue?
Thank you very much.
Traceback
Traceback (most recent call last):
  File "C:\Users\apmel\anaconda3\lib\site-packages\qtconsole\base_frontend_mixin.py", line 138, in _dispatch
    handler(msg)
  File "C:\Users\apmel\anaconda3\lib\site-packages\spyder\plugins\ipythonconsole\widgets\debugging.py", line 278, in _handle_input_request
    return super(DebuggingWidget, self)._handle_input_request(msg)
  File "C:\Users\apmel\anaconda3\lib\site-packages\qtconsole\frontend_widget.py", line 512, in _handle_input_request
    self._readline(msg['content']['prompt'], callback=callback, password=msg['content']['password'])
  File "C:\Users\apmel\anaconda3\lib\site-packages\qtconsole\console_widget.py", line 2422, in _readline
    self._show_prompt(prompt, newline=False, separator=False)
TypeError: _show_prompt() got an unexpected keyword argument 'separator'

Versions

Spyder version: 5.1.5
Python version: 3.9.12
Qt version: 5.9.7
PyQt5 version: 5.9.2
Operating System: Windows 10

Dependencies

# Mandatory:
atomicwrites >=1.2.0          :  1.4.0 (OK)
chardet >=2.0.0               :  4.0.0 (OK)
cloudpickle >=0.5.0           :  2.0.0 (OK)
cookiecutter >=1.6.0          :  1.7.3 (OK)
diff_match_patch >=20181111   :  20200713 (OK)
intervaltree >=3.0.2          :  3.1.0 (OK)
IPython >=7.6.0               :  8.2.0 (OK)
jedi >=0.17.2;<0.19.0         :  0.18.1 (OK)
jsonschema >=3.2.0            :  4.4.0 (OK)
keyring >=17.0.0              :  23.4.0 (OK)
nbconvert >=4.0               :  6.4.4 (OK)
numpydoc >=0.6.0              :  1.2 (OK)
paramiko >=2.4.0              :  2.8.1 (OK)
parso >=0.7.0;<0.9.0          :  0.8.3 (OK)
pexpect >=4.4.0               :  4.8.0 (OK)
pickleshare >=0.4             :  0.7.5 (OK)
psutil >=5.3                  :  5.8.0 (OK)
pygments >=2.0                :  2.11.2 (OK)
pylint >=2.5.0;<2.10.0        :  2.9.6 (OK)
pyls_spyder >=0.4.0           :  0.4.0 (OK)
pylsp >=1.2.2;<1.3.0          :  1.2.4 (OK)
pylsp_black >=1.0.0           :  None (OK)
qdarkstyle =3.0.2             :  3.0.2 (OK)
qstylizer >=0.1.10            :  0.1.10 (OK)
qtawesome >=1.0.2             :  1.0.3 (OK)
qtconsole >=5.1.0             :  5.3.0 (OK)
qtpy >=1.5.0                  :  2.0.1 (OK)
rtree >=0.9.7                 :  0.9.7 (OK)
setuptools >=49.6.0           :  61.2.0 (OK)
sphinx >=0.6.6                :  4.4.0 (OK)
spyder_kernels >=2.1.1;<2.2.0 :  2.1.3 (OK)
textdistance >=4.2.0          :  4.2.1 (OK)
three_merge >=0.1.1           :  0.1.1 (OK)
watchdog >=0.10.3             :  2.1.6 (OK)
zmq >=17                      :  22.3.0 (OK)

# Optional:
cython >=0.21                 :  0.29.28 (OK)
matplotlib >=2.0.0            :  3.5.1 (OK)
numpy >=1.7                   :  1.21.5 (OK)
pandas >=1.1.1                :  1.4.2 (OK)
scipy >=0.17.0                :  1.7.3 (OK)
sympy >=0.7.3                 :  1.10.1 (OK)

I've tried that, but then I get the following message while restarting the kernel:
An error ocurred while starting the kernel
The Python environment or installation whose interpreter is located at
C:\Users\apmel\miniconda3\envs\adriano‑env\python.exe
doesn't have the spyder‑kernels module or the right version of it installed (>= 2.3.0 and < 2.4.0). Without this module is not possible for Spyder to create a console for you.
You can install it by activating your environment (if necessary) and then running in a system terminal:
conda install spyder‑kernels=2.3
or
pip install spyder‑kernels==2.3.*

But when I type conda install spyder‑kernels=2.3, I get the following message:
(adriano-env) C:\Users\apmel>conda install spyder‑kernels=2.3
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
PackagesNotFoundError: The following packages are not available from current channels:

spyder-kernels=2.3

Current channels:

https://repo.anaconda.com/pkgs/main/win-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/r/win-64
https://repo.anaconda.com/pkgs/r/noarch
https://repo.anaconda.com/pkgs/msys2/win-64
https://repo.anaconda.com/pkgs/msys2/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org

and use the search bar at the top of the page.

Then, going to this page: https://anaconda.org/conda-forge/spyder-kernels
and trying al those commands:
conda install -c conda-forge spyder-kernels
conda install -c conda-forge/label/broken spyder-kernels
conda install -c conda-forge/label/cf201901 spyder-kernels
conda install -c conda-forge/label/cf202003 spyder-kernels
conda install -c conda-forge/label/beta spyder-kernels
I get this message on Spyder terminal:
Python 3.9.12 (main, Apr  4 2022, 05:22:27) [MSC v.1916 64 bit (AMD64)]
Type "copyright", "credits" or "license" for more information.
IPython  -- An enhanced Interactive Python.
Cannot restart a kernel not started by Spyder
Cannot restart a kernel not started by Spyder
Cannot restart a kernel not started by Spyder
Cannot restart a kernel not started by Spyder
Cannot restart a kernel not started by Spyder

Please, what do I have to do to fix it?
Thank you so much.

I've tried that, but then I get the following message while restarting the kernel

I'm afraid you'll have to reinstall from conda-forge all packages you need for development in your spyder-cf environment, like this:
conda activate spyder-cf
conda install -c conda-forge pandas matplotlib scikit-learn

and other packages you need.

Thank you ccordoba12!
I think it worked now.
I'm in my second year of software engineering.
Is it recommended to use the standalone version or the one with the Anaconda?
Thank you very much for your help.

Thank you very much, Carlos.
It worked now.


Fix on TOML code blocks

Description
This PR fixes an issue with TOML code blocks not rendering as expected. For a more detailed explanation of the issue, see this Notion page
The Problem
This issue is caused by two conflicting dependencies that we have:

prism.js adds a .table class to some tokens for styling the code blocks;
However, that .table class is also inheriting styles from Tailwind CSS, causing the rendering issue.

The Solution
For now, I've overriden the Tailwind styling for these code blocks in the SCSS code. Moving forward, as we start to move away from Sass and into CSS modules, we'll need to refactor this again.

@snehankekre Please take a look and let me know if this issue fixes it! If you could try a page different than this one that'd be great!


bump ssh-key to 0.6.7

This brings in fixes RustCrypto/SSH#291 and RustCrypto/SSH#289

I will release this shortly.

https://crates.io/crates/sshauth/0.1.1


Download the Bot Framework Emulator

Hello. I don't quite understand what I should download to get the Bot Framework Emulator (for windows). Please help!

Hi @HadasBrown
This link is the latest Emulator installer:
https://github.com/Microsoft/BotFramework-Emulator/releases/download/v3.5.36/botframework-emulator-Setup-3.5.36.exe


chore(main): release 1.0.2

:robot: I have created a release beep boop
1.0.2 (2024-07-12)
🐛 Bug Fixes

readme: correct [@use](https://github.com/use) syntax in example (481361a)
triangle: replace division with math.div for border-width (a34096b)
validator: enhance color validation to include var(--color) (6d88816)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Meqn/sass-magics/releases/tag/v1.0.2 :sunflower:


Updates to kinemage parser

Fixed some bugs with the kinemage parsing code.
Added some initial testing code using Jest to check for correct parsing of kinemages.

I also don't know much about the file format, but if it's working then great!
Minor comment (mostly on me for not looking at it earlier) but for older PRs like this is it better to merge as is, or create a new branch, cherry pick the commits (preserving committer/author details) and create a cleaner PR? Pros are a cleaner git history and getting rid of unecessary rebase/merge comits, cons are it requires two maintainers rather than one as one of us needs to approve the other's new PR.
(To be clear, I'm completely happy to merge this now for expediency's sake!)

@fredludlow I'm also generally in favor of a cleaner history. I merged this now since it's been pending for a long time. It's a bit complicated to rebase while preserving the author details (especially committer), but it can be done in most simple cases. I'm happy to try that going forward.


ERROR: Signature extraction failed: Traceback (most recent call last)

** My software version: **

➜  youtube-dl --version
2018.03.14

** error message: **

➜  youtube-dl -F https://www.youtube.com/watch?v=XXXXXXXXXXXXX
[youtube] 3F44De8jeaE: Downloading webpage
[youtube] 3F44De8jeaE: Downloading video info webpage
[youtube] 3F44De8jeaE: Extracting video information
[youtube] 3F44De8jeaE: Downloading js player vflSzU_20
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1191, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1102, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/youtube.py", line 1163, in _parse_sig_js
jscode, 'Initial JS player signature function name', group='sig')
File "/usr/lib/python3/dist-packages/youtube_dl/extractor/common.py", line 796, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract Initial JS player signature function name; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by RegexNotFoundError('Unable to extract \x1b[0;34mInitial JS player signature function name\x1b[0m; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.',)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

@dstftw what is the resolution for this issue? I have update my software to the latest version, what do you mean by "outdated-version", please advice. thanks.


provide an onResult option, with a callback called after each result

This adds an onResult option, when you want to listen to the results as they come, and not all at once. Useful for streaming, and also for showing results while still receiving them.

@fabiosantoscode  Thank you! This is now published under 1.2.0.


Error occurred while reading SSEsjava.lang.IllegalStateException: RESTEASY004087: No suitable message body reader for class : jakarta.ws.rs.core.GenericType

thrown in SSEPublisher#pump() when REST resource method return type is not Publisher<String>.
In my case, the method signature is
@GET
  // the following give media type text/event-stream;element-type="application/json"
  @Produces("text/event-stream")
  @org.jboss.resteasy.annotations.SseElementType(MediaType.APPLICATION_JSON)

  // the following gives media type application/x-stream-general;element-type="application/json"
//  @org.jboss.resteasy.annotations.Stream
  Publisher<SseEventDto> getEvents();

SSEPublisher calls event.readData((Class) typeArgument) which tries to lookup a message bodyx reader for type MediaType.TEXT_PLAIN_TYPE.
SSEPublisher should call  event.readData((Class) typeArgument, MediaType.APPLICATION_JSON) in this case to get the proper reader.
Here is how resteasy-rxjava2 handle this: e.readData(clazz, ((InboundSseEventImpl) e).getMediaType())

I apologize for the very late reply here. I'm not sure how I missed this. Do you have a reproducer by chance? I'm not sure I follow as this seems more like a https://github.com/resteasy/resteasy issue.

Excellent, thank you @emweber. I see the problem now. The MediaType is not being used when reading the event so it's always reading as text/plain.


Add Readme files.

Add readme of folders in which it is missing.

Please assign this issue to me

Please assign me this task

hey could you please assign this task , i want to contribute

please assign me


[jest-mock] Include tracked call results in serialized mock

Summary
Mock functions have recently been updated to not only track params for each call, but also the result of each call (whether it threw an error, what value was returned/thrown).
This PR adds that new information to the serialized representation of a mock function.
Test plan

Updated existing mock_serializer.test.js unit tests to expect additional results data, and updated the mock functions in some tests to actually return a value.
Added a new unit test to mock_serializer.test.js that involves a call to a mock that returns a value, and another call to the same mock that throws.
Ran yarn run jest mock_serializer and reviewed all snapshot mismatches (caused by the new expected data).
Ran yarn run jest mock_serializer -u to update snapshots after confirming the new snapshots looked good.

@SimenB


Set up a training call w/ LSEM's website person

We want to go over how to make updates to the website.

Meeting with Sarah


Choice.convert should use get_missing_message

Was trying to use get_missing_message to offer spelling correction suggestions, but the fail message is hard-coded:
https://github.com/mitsuhiko/click/blob/master/click/types.py#L148-L149

See: https://github.com/pallets/click/blob/master/click/types.py#L161-L162. I'm not sure when was this changed but Choice.conver uses self.choices instead of hard-coded:
    def convert(self, value, param, ctx):
        ...
        self.fail('invalid choice: %s. (choose from %s)' %
                  (value, ', '.join(self.choices)), param, ctx)


DR-33 Add Plywood support for Amazon Athena

awsAthenaDialect.ts - athena dialect
bigQueryDialect.ts - fixed strpos
mySqlDialect.ts, postgresDialect.ts - removed constant group by, this code was never run :D
package.json - added athena client
rrollup - added athena files to build concat script

Question to @Romucmad and @Isabek: as @Isabek told me, the schema introspection is implemented in redash, but I saw your recent commit  changing the code that does introspection for postgresql. I wonder what's the best way to approach it nowadays

I didn't like that some of schema introspection  was on redash and some of plywood.  So I think I moved all to plywood in the last commits .
If I am right redash is not doing anything except passing real types.
So assume that you would get all native values from athena.

So the way it works but schema is parsed on the plywood but not directly in the requery. If you have a look a plywood-server you will see that there is an endpoint responsible for it .

So you should have static function called something like postProcessIntrospect as in PostgresExternal.

@Romucmad I've figured out that redash does the actual schema introspection and sends request to plywood-server to map native types to plywood types. I've created a mapTypes function and pushed it. If the code looks good I can integrate it into plywood-server and then into the redash.


A way to ignore tasks under a section

Please provide a link to the documentation page and section
https://blacksmithgu.github.io/obsidian-dataview/query/queries/#task-queries - Task Queries
Describe the problem
More information on how to filter out tasks. Because of the new feature where the task collection for (!complete) now includes any tasks indented under text headings.
In case this was how people ignore tasks (default tasks that you only want to see in the page and not rolled up to a task dataview table), we can mention how to filter out tasks?
Instead you want to have set headings e.g. "Checklist" for any tasks you don't want rolled up and then add WHERE !contains(meta(section).subpath, "Checklist") to the dataview tables
Describe the solution you'd like
A clear and concise description of what you want to happen. Feel free to suggest wording, full sentences, etc.
Previously the code for tasks from daily page would be this
TASK
FROM #Periodic/Daily📅
WHERE !completed

In order to ignore tasks under the heading "Checklist", can add a line to this
TASK
FROM #Periodic/Daily📅
WHERE !completed
WHERE !contains(meta(section).subpath, "Checklist")

Additional context
Here are screenshots of how it looks like

That looks like the correct way to do it.

I think you don't need to use the section solution.
Try use only WHERE !parent

I think you don't need to use the section solution. Try use only WHERE !parent

Ok tried it and that works well 👍
Conclusion: I found that it helps to use the section filtering for more controlled filtering out of tasks but to mimic previous behaviour !parent works


Adding initial version of fieldy

We should have another project with ownership of the models, they should not be located on the renderer


Victor VosMottor: Watch 1d10ut

Victor VosMottor requests the watch of the watch_keyword 1d10ut. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

1d10ut has been seen in 1 true positive, 0 false positives, and 0 NAAs.

This seems like an outlier keyword. We should try and get more general watches for this kind of stuff.


Bulk duplicate H1 titles

Docs Build status updates of commit ece598c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:warning:Warning

Details

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:warning:Warning

Details

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-d.md
:warning:Warning

Details

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/roundtripmax-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-c.md

Line 13, Column 1: [Warning: duplicate-h1s - See documentation] H1 'ResponseCode element (Schema C)' is duplicated with other articles: 'SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-c.md(13,1), SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-c.md(13,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 13, Column 1: [Warning: duplicate-h1s - See documentation] H1 'ResponseCode element (Schema D)' is duplicated with other articles: 'SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-d.md(13,1), SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-d.md(13,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-c.md

Line 13, Column 1: [Warning: duplicate-h1s - See documentation] H1 'ResponseCode element (Schema C)' is duplicated with other articles: 'SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-c.md(13,1), SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-c.md(13,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-d.md

Line 13, Column 1: [Warning: duplicate-h1s - See documentation] H1 'ResponseCode element (Schema D)' is duplicated with other articles: 'SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-d.md(13,1), SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-d.md(13,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/roundtripmax-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b24bd75:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/roundtripmax-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/roundtripmax-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@lindalu-MSFT
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you’d like to see. Thank you!

Docs Build status updates of commit 936ce96:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md
:bulb:Suggestion

Details

Skype/SDN/articles/roundtripmax-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:bulb:Suggestion

Details

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/renderdevice-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/renderdevicedriver-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecode-element-errorproperties-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecode-element-messageproperties-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsecodetype-complextype-skype-for-business-sdn-interface-2-2-schema-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/responsephrase-element-errorproperties-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/roundtrip-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/roundtripmax-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Bump versions of utilities and platforms in circleci

Description
Updates versions of various images and packages
TODOs
Please ensure all of these TODOs are completed before asking for a review.

[x] Ensure the branch is named correctly with the issue number. e.g: feature/new-vpc-endpoints-955 or bug/missing-count-param-434.
[x] Update the docs.
[x] Keep the changes backward compatible where possible.
[x] Run the pre-commit checks successfully.
[x] Run the relevant tests successfully.

Thanks for review! Merging now.


No module named pywapi

I just installed Melissa-Core and tried to start it, but all I got was a backtrace:
Traceback (most recent call last):
  File "start.py", line 5, in <module>
    from melissa.profile_loader import load_profile
  File "/home/polesz/Projects/NotOwn/Melissa-Core/melissa/profile_loader.py", line 6, in <module>
    from profile_populator import profile_populator
  File "/home/polesz/Projects/NotOwn/Melissa-Core/melissa/profile_populator.py", line 6, in <module>
    import pywapi
ImportError: No module named pywapi

Installing the pywapi module is not that straightforward, as it doesn’t exist on PyPI. It is also deprecated(ish), as the last change in it was back in 2013.

Well, I agree that it is a good idea to replace Pywapi with some other python package. Any thoughts guys @gergelypolonkai @rachmadaniHaryono?

How about OpenWeatherMap?

not quite sure what is the qualification for replacing pywapi.

we can fork the pywapi, but it add technical debt
i have seen pyowm but it require api key, anything without it is better
from pypi the first result for weather is https://github.com/cmcginty/PyWeather from @cmcginty, but i haven't tested yet.

PyWeather is for reading data from a hardware weather station (eg. Davis Vantage pro II)

I agree that pywapi was a good solution and I really liked the search implementation that one of our contributors added. Even though it adds technical debt, I still feel that forking it "might" be a good idea. I don't want to add more modules that require APIs, if the work can be accomplished without it. @gergelypolonkai @rachmadaniHaryono

Well, its API is pretty good and doesn’t feel outdated. So yes, forking it might be a good option, but that means the one who forks it should also maintain it on PyPI and such (also, it should be added to requirements.txt

Anyone interested in picking this up before we get started with https://github.com/Melissa-AI/Melissa-Core/issues/165?

To be honest, I don't wanna maintain it on PyPI, the best solution that I can think of currently, is to include pywapi.py in melissa/utilities and make the respective changes in weather.py. Thoughts @gergelypolonkai @rachmadaniHaryono?

I agree, if:

if it's only one file
the maintenance cost is low (pywapi changes will be scarce)
no one actually plans to pick it up

If so, the best option may be to put it into the project.

Just took a deeper look, and I managed to install it with
pip install -e git+https://github.com/jtasker/python-weather-api@cf79f478c26dd244e0c90e10d6df91bb4ea8cd5e#egg=pywapi

It works both with Python2 and Python3. This line doesn’t look that good in a requirements file, but might be better than maintaining it.

I see @gergelypolonkai. Thanks a lot for the insights. Since it's just a single file, I feel that it shouldn't be a big deal to maintain. How does the installation for the current version work for you?
Final thoughts on https://github.com/Melissa-AI/Melissa-Core/pull/173 @rachmadaniHaryono?

after @gergelypolonkai give the github link, imo it is better to replace the pypi's pywapi with github link.
if anyone want to pickup the module, the change will not in our repo but @jtasker 's python-weather-api
also it is easier to replace the link on requirements file (rather than include the file and deal with the future of the module)

This line doesn’t look that good in a requirements file, but might be better than maintaining it.

it is normal if a module only have github link and haven't been uploaded to pypi, so it is not strange at all

Fair enough, @rachmadaniHaryono. Would you like to put in a PR for this?

ok in a moment.


ArrowCapacityError: List array cannot contain more than<PHONE_NUMBER> child elements, have<PHONE_NUMBER>

Hi, I'm trying to load a dataset from Dataframe, but I get the error:
---------------------------------------------------------------------------
ArrowCapacityError                        Traceback (most recent call last)
<ipython-input-7-146b6b495963> in <module>
----> 1 dataset = Dataset.from_pandas(emb)

~/miniconda3/envs/dev/lib/python3.7/site-packages/nlp/arrow_dataset.py in from_pandas(cls, df, features, info, split)
    223         info.features = features
    224         pa_table: pa.Table = pa.Table.from_pandas(
--> 225             df=df, schema=pa.schema(features.type) if features is not None else None
    226         )
    227         return cls(pa_table, info=info, split=split)

~/miniconda3/envs/dev/lib/python3.7/site-packages/pyarrow/table.pxi in pyarrow.lib.Table.from_pandas()

~/miniconda3/envs/dev/lib/python3.7/site-packages/pyarrow/pandas_compat.py in dataframe_to_arrays(df, schema, preserve_index, nthreads, columns, safe)
    591         for i, maybe_fut in enumerate(arrays):
    592             if isinstance(maybe_fut, futures.Future):
--> 593                 arrays[i] = maybe_fut.result()
    594
    595     types = [x.type for x in arrays]

~/miniconda3/envs/dev/lib/python3.7/concurrent/futures/_base.py in result(self, timeout)
    426                 raise CancelledError()
    427             elif self._state == FINISHED:
--> 428                 return self.__get_result()
    429
    430             self._condition.wait(timeout)

~/miniconda3/envs/dev/lib/python3.7/concurrent/futures/_base.py in __get_result(self)
    382     def __get_result(self):
    383         if self._exception:
--> 384             raise self._exception
    385         else:
    386             return self._result

~/miniconda3/envs/dev/lib/python3.7/concurrent/futures/thread.py in run(self)
     55
     56         try:
---> 57             result = self.fn(*self.args, **self.kwargs)
     58         except BaseException as exc:
     59             self.future.set_exception(exc)

~/miniconda3/envs/dev/lib/python3.7/site-packages/pyarrow/pandas_compat.py in convert_column(col, field)
    557
    558         try:
--> 559             result = pa.array(col, type=type_, from_pandas=True, safe=safe)
    560         except (pa.ArrowInvalid,
    561                 pa.ArrowNotImplementedError,

~/miniconda3/envs/dev/lib/python3.7/site-packages/pyarrow/array.pxi in pyarrow.lib.array()

~/miniconda3/envs/dev/lib/python3.7/site-packages/pyarrow/array.pxi in pyarrow.lib._ndarray_to_array()

~/miniconda3/envs/dev/lib/python3.7/site-packages/pyarrow/error.pxi in pyarrow.lib.check_status()

ArrowCapacityError: List array cannot contain more than<PHONE_NUMBER> child elements, have<PHONE_NUMBER>

My code is :
from nlp import Dataset
dataset = Dataset.from_pandas(emb)

Can you give us stats/information on your pandas DataFrame?

<class 'pandas.core.frame.DataFrame'>
Int64Index: 17136104 entries, 0 to 17136103
Data columns (total 6 columns):
 #   Column        Dtype
---  ------        -----
 0   item_id       int64
 1   item_titl     object
 2   start_price   float64
 3   shipping_fee  float64
 4   picture_url   object
 5   embeddings    object
dtypes: float64(2), int64(1), object(3)
memory usage: 915.2+ MB

Thanks and some more on the embeddings and picture_url would be nice as well (type and max lengths of the elements)

embedding is np.array of shape (128,). picture_url is url, such as 'https://i.ebayimg.com/00/s/MTE5OVgxNjAw/z/ZOsAAOSwAG9fHQq5/$_12.JPG?set_id=880000500F;https://i.ebayimg.com/00/s/MTE5OVgxNjAw/z/OSgAAOSwokBfHQq8/$_12.JPG?set_id=880000500F'

It looks like a Pyarrow limitation.
I was able to reproduce the error with
import pandas as pd
import numpy as np
import pyarrow as pa

 n = 1713614
df = pd.DataFrame.from_dict({"a": list(np.zeros((n, 128))), "b": range(n)})
pa.Table.from_pandas(df)

I also tried with 50% of the dataframe and it actually works.
I created an issue on Apache Arrow's JIRA here
One way to fix that would be to chunk the dataframe and concatenate arrow tables.

It looks like it's going to be fixed in pyarrow 2.0.0 :)
In the meantime I suggest to chunk big dataframes to create several small datasets, and then concatenate them using concatenate_datasets


Map scenarios for content interactions across versions

To elegantly handle versioning in the documentation, we need to map how we plan documents to work across versions

I think https://github.com/cockroachdb/docs/pull/1605 ended up covering this well. @sploiselle, please reopen and add details if you think there are unresolved questions.


Haf 766 Metadata Issues

Card : [#766](https://github.com/hashmapinc/Tempus/issues/766)
Metadata Issues

While deleting Metadata-Config we first need to delete associated Metadata-Queries.
While testing connection-api changed the Http Response Status from Not_Found to OK with response body NOT_CONNECTED.

LGTM


As we renamed the repository resin-am571x-evm from

resin-am57xx-evm, we also need to do this naming change
throughout the layers.
Signed-off-by: Florin Sarbu<EMAIL_ADDRESS>

connects to https://github.com/resin-os/resinos/issues/164


Added two examples for FOR_LOOP

I have added two examples for FOR_LOOP
1.Infinte loop => it  will run infinite times and
2.for-loop to iterate through the array =>it  prints out the elements of the array
Both these files are located in the Loops folder inside For Loop folder with file names as:
1.ForLoopExample1
2.ForLoopExample2
#hacktoberfest

Please Provide a suitable Description for the Pull Request you generated.

I have added two examples for FOR_LOOP
1.Infinte loop => it will run infinite times and
2.for-loop to iterate through the array =>it prints out the elements of the array
Both these files are located in the Loops folder inside For Loop folder with file names as:
1.ForLoopExample1
2.ForLoopExample2
#hacktoberfest


CI failing on main

CI is failing on main:
_unittest/test_00_EDB.py::TestClass::test_72_padstack_instance PASSED    [ 10%]
_unittest/test_00_EDB.py::TestClass::test_73_duplicate_padstack PASSED   [ 10%]
_unittest/test_00_EDB.py::TestClass::test74_set_padstack_property PASSED [ 11%]
_unittest/test_00_EDB.py::TestClass::test_75_primitives_area PASSED      [ 11%]
Error: Process completed with exit code 1.

Seems this was solved with https://github.com/pyansys/pyaedt/pull/876.

@akaszynski I will double check our workflows and actions status for the next PR, just to be sure that everything is back in order.


[FTRUIWebViewTest testLongPressLinkInUIWebView] Sometimes it fails to dectect the UIWebView is idling

this seems to only happen on iOS 8.4, iOS 9 and above works fine.

the error message shows that it timed out due to failing to detect if UIWebView is idling.
Exception: ActionFailedException
Reason: Action 'Tap' failed.
Element matcher: (((respondsToSelector(isAccessibilityElement) && isAccessibilityElement) && accessibilityTraits: UIAccessibilityTraitButton) && ((respondsToSelector(isAccessibilityElement) && isAccessibilityElement) && accessibilityLabel("Cancel")))
Complete Error: Error Domain=com.google.earlgrey.ElementInteractionErrorDomain Code=3 "Failed to perform action within 30 seconds." UserInfo=0x7fadf8fdb890 {NSLocalizedDescription=Failed to perform action within 30 seconds., NSUnderlyingError=0x7fadf8f4b570 "Failed to execute block because the following IdlingResources are busy: ['UIWebView Pre-Load Tracker']
Busy resource description:
  UIWebView Pre-Load Tracker : UIWebView Pre-Load Tracker"}


Extract multipart upload impl from mvcc cataloger

Extracting multipart upload handling from cataloger as a package under gateway

The service is no multiparts.Tracker
Removed the use of repository, it will track parts based on tracking ID
Postgres table and index 'gateway_multiparts'

Codecov Report

Merging #989 (f655cef) into master (4f89db9) will decrease coverage by 0.32%.
The diff coverage is 35.61%.

@@            Coverage Diff             @@
##           master     #989      +/-   ##
==========================================
- Coverage   44.58%   44.26%   -0.33%
==========================================
  Files         142      140       -2
  Lines       11547    11570      +23
==========================================
- Hits         5148     5121      -27
- Misses       5757     5799      +42
- Partials      642      650       +8

Impacted Files
Coverage Δ

api/handler.go
70.83% <ø> (ø)

catalog/mvcc/validate.go
88.23% <ø> (-6.21%)
:arrow_down:

gateway/multiparts/tracker.go
0.00% <0.00%> (ø)

gateway/operations/base.go
0.00% <ø> (ø)

gateway/operations/postobject.go
0.00% <0.00%> (ø)

gateway/operations/putobject.go
0.00% <0.00%> (ø)

gateway/handler.go
58.78% <76.47%> (+0.22%)
:arrow_up:

catalog/mvcc/cataloger_create_repository.go
59.25% <0.00%> (-3.71%)
:arrow_down:

stats/collector.go
61.36% <0.00%> (-0.71%)
:arrow_down:

... and 5 more

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 4f89db9...f655cef. Read the comment docs.


fix 1329

fixes #1329
Signed-off-by: Filip Haltmayer<EMAIL_ADDRESS>

Codecov Report

Merging #1330 (eb74eb7) into main (03e9fc9) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main    #1330   +/-   ##
=======================================
  Coverage   68.21%   68.21%
=======================================
  Files         283      283
  Lines       14958    14958
  Branches     2409     2409
=======================================
  Hits        10204    10204
  Misses       4114     4114
  Partials      640      640

Impacted Files
Coverage Δ

towhee/functional/__init__.py
85.18% <0.00%> (ø)

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 03e9fc9...eb74eb7. Read the comment docs.

The PR may break some of the doctest, some of the doctest are not running as reported in #1275.

This issue is also fixed in #1331.


TSheets Quickbooks Time (Independent Publisher)

When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)
If this is your first time submitting to GitHub and you need some help, please sign up for this session.

[x] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[x] I attest that the connector works and I verified by deploying and testing all the operations.
[x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

[x] I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
[x] Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
[x] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
[x] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

@Ajinder31 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

Contributor License Agreement

@microsoft-github-policy-service agree company="Artesian Software Technologies LLP"

Hi @Amjed-Ayoub, As suggested we updated the apiProperties.json file for TSheets Quickbooks Time and submitted for review.
Also, there was a type mismatch error reported by API Properties Validator for hidden field (screenshot below), so we changed it to Boolean instead of string as suggested in error message.

@artesianst
Thank you

[[certify-connector]]

Hello @Ajinder31,
I hope you are doing well.
Congratulations, your pull request is approved. We will move forward with the certification process. We are preparing your connector for production deployment and will queue up for the next deployment schedule. Once your connector onboards the next deployment schedule, it starts to deploy your connector in our production environments that typically takes 3-4 weeks.
Please let us know if you have any questions.
Thank you very much for working with us.

Thank you for the update @Amjed-Ayoub

Hello @Ajinder31,
I hope you are doing well.
Your connector is in production deployment and queued up for the next deployment schedule. This process typically takes 3-4 weeks. Please note that the documentation for your connector will not be generated until the deployment process is in the final steps.
Please let us know if you have any questions.
Thank you very much for working with us.

Thank you for the update @Amjed-Ayoub

@Ajinder31 can you please test the connector? it should be deployed to all regions.

I can confirm connector is working now. Thank you so much @Amjed-Ayoub.

Hello @Ajinder31,
I hope you are doing well.
Congratulations, the deployment of your connector and documentation page was already completed, We have a short survey on the connector certification process that we would like for you to complete. Your feedback is appreciated and will help us improve the program.
Thank you very much for working with us.


Prefer class

The Prefer module was turned into a class instead of standalone functions. This is due to the need for a connection to UserInputService.LastInputTypeChanged at the root of the functionality. With just a list of functions, this event had to be connected within the root of the module code, which was not possible to disconnect. This is problematic for testing code. By wrapping it in a class, the event will only be connected if the class is instantiated, and offers a destroy method to disconnect the event.

An alternative would be to have another function that acted as a "startup" for the module's functionality. This, however, would feel unordinary. Thus, adding a class seemed to be the most ergonomic decision.


Course Level Bulk Download Videos Option

Description
LEARNER-2771
LEARNER-3913

@salman2013
snapshot test cases renamed. please review it again.

halfScreenHeight

@salman2013
done

@saeedbashir You can take look into this PR.

@saeedbashir
requested changes has been made, please review again.

@saeedbashir
PR is ready for another pass.

@saeedbashir
Feedback changes has been made. Please review it again.


Unit Test Case for useDeepCompareMemoize

Closes: RHOAIENG-2091
Description
Unit Test Case for useDeepCompareMemoize
How Has This Been Tested?
npm run test
Test Impact

Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

@christianvogt Updated accordingly.

/retest

@christianvogt thanks for pointing this out. Updated it accordingly.

/lgtm
/approve


Digging into leap year bug and improvming tests

Ultimately the fix was to run parsedatetime off of their master branch in production. I still want to add the tests and the more generic raise here.

LGTM


Changing MapTilerNavigationControl options have no effect

maptiler-sdk-js version: https://github.com/maptiler/maptiler-sdk-js/releases/tag/v2.1.0
Bug description
When creating a MaptilerNavigationControl the options given are not taken into account, whereas the MapTiler documentation says the constructor takes an options object as argument.
let map = new maptilersdk.Map({
    container: 'mapContainer',
	// ...
    navigationControl: false,
});

const nav = new maptilersdk.MaptilerNavigationControl( { showCompass: false } );
map.addControl(nav, 'top-right');
// Bug : compass is still showing

Moreover :
console.log(nav.options)
/*
// Returns :
Object { showCompass: true, showZoom: true, visualizePitch: true }
// Should be :
Object { showCompass: false, showZoom: true, visualizePitch: true }
*/

Problem
When creating a MaptilerNavigationControl you should be able to pass a NavigationControlOptions to define showCompass, showZoom, visualizePitch.
Solution
https://github.com/maptiler/maptiler-sdk-js/blob/3588c8e55c4e1b253e70b544191be998e93b7391/src/MaptilerNavigationControl.ts#L8-L13
This should instead be something like
  constructor(options: NavigationControlOptions = { showCompass: true, showZoom: true, visualizePitch: true, }) {
    super({
      showCompass: options.showCompass,
      showZoom: options.showZoom,
      visualizePitch: options.visualizePitch
    });

Hello @ThatIsAPseudo , Thanks for your feeback. Originaly, the idea of MaptilerNavigationControl was to provide something simple with no confusing options and that just does the minimum, and you're right, the documentation is not aligned with this and shows the options of the parent class MaptilerNavigation instead.
The best would probably be that it accepts the same options though so I'll make a ticket for this.

Hello, sorry for the late feedback, I kinda forgot to post the update here but this has been fixed


Add min/max value constraints to score and confidence slots.

Resolves #372

[ ] docs/ have been added/updated if necessary (not applicable; the doc was already ahead of the model, this PR is about updating the model to align it with the doc)
[x] make test has been run locally
[ ] tests have been added/updated (not applicable)
[x] CHANGELOG.md has been updated.

The description of the confidence, semantic_similarity_score, and similarity_score slots says that those slots expect a value between 0 and 1, but the model does not enforce that. LinkML provides a way to formalise this kind of value constraints (which could then be automatically enforced by a runtime that is aware of those constraints), so we do exactly that here: we add minimum_value and maximum_value constraints to the aforementioned slots.

Build LinkML model (this ensures that the model is syntactically well-defined)

I believe the existing test suite here (the one that is run by make test) takes care of validating the model at least from a syntactical standpoint. First, because what would even be the point of the test suite if it did not even do that, and second, because when preparing this PR I initially and erroneously wrote maximal_value instead of maximum_value, and the test suite (which I ran locally before even committing any changes) correctly rebuked me for that.

Build version of sssom py with that locally cached linkml model
Run sssom-py test suites

Why would we want sssom to fail because of problems that could exist in sssom-py?
If SSSOM-Py breaks when the model enforces a constraint that has always been a part of the spec but was not previously enforced, then it's a problem with SSSOM-Py, not with the spec.

I believe the existing test suite here (the one that is run by make test) takes care of validating the model at least from a syntactical standpoint.

You are right, forgot about that; it already does what I thought it did not.


QubitDevice removed from toplevel, along with their warnings

Title:
Remove QubitDevice warnings, which will be removed in the 0.40PL
Summary:
as title
Relevant references:
#https://github.com/PennyLaneAI/pennylane/pull/6537
Possible Drawbacks:
None
Related GitHub Issues:

Do we know if blue qubit has updated their device to accommodate this removal?

Do we know if blue qubit has updated their device to accommodate this removal?

@albi3ro , I messaged them on our slack channel when the deprecation first happened to let them know. They said they would resolve it, but I'm not sure if they have or not. I'll check in.

@JerryChen97 the blue qubit device has been fixed, so this PR can be merged now.


Can bus error on remote start

Describe the bug
If I remote start my jeep I get a can bus error. If I start normally it works fine.
Provide a route where the issue occurs
5c77528ab6bf019a|2023-03-01--17-34-37--0
openpilot version
0.9.1
Additional info
No response

Can you provide a route on stock openpilot? I'm not able to parse the logs. If it's not easy, no worries I can pull the fork's log definitions. Is this CAN error persistent, or does it go away once you fully turn your vehicle on?

5c77528ab6bf019a|2023-03-01--22-05-29--0

It goes away when turn car on but openpilot doesn't auto steer.

Can you get a route where you remote start the vehicle, then get in and put it in drive to start moving? I'd like to see what fault code the EPS reports when it finally starts sending, since you say you don't get steering that way.

It engages but no torque. I'll do it right now.

5c77528ab6bf019a|2023-03-01--22-25-37--0 this is the fault. Didn't let me even enable acc it started flashing red.

That's interesting, it doesn't report a fault until openpilot starts sending torque. Can you make sure to get routes on master next time? But this route is on a fork, and you are spoofing the speed to steer at lower speeds, so it's hard for me to rule those out as reasons for the fault.
Can you get a route on master where you:

remote start the car
get in and drive
try to engage above the higher minimum steering speed (~40 mph)

Also would be interesting to see if the stock LKAS system would fault in this instance. For that, it would be a separate test where you keep openpilot disabled in the settings and do the same actions above, but you'd need to find a highway so the stock system would try to apply torque.

5c77528ab6bf019a|2023-03-01--16-35-41--0 this one is stock happened on my way home from work. Above 40 setting acc no steer.

Currently the wp is not always powered only when. Push button start happens. Should the wp always be powered? I'm wondering if that's what causes the can issue on remote start. Not sure if the wp should always be powered.

I think I figured it out. I'll close for now and reopen if problem comes back. Ethernet cable wasn't fully seated.

5c77528ab6bf019a|2023-03-01--16-35-41--5

5c77528ab6bf019a|2023-03-01--16-35-41--5

Fixed. Panda always needs power not switched power on Chrysler. This eliminates the can error.

Fixed. Panda always needs power not switched power on Chrysler. This eliminates the can error.

Guess it's not fixed. 10 minutes ago started truck got lkas error. Restarted vehicle no lkas error. Maybe there needs to be a delay somewhere?

I see you're running a fork with some extra hardware. We can't look into issues from forks. If you can reproduce this with stock openpilot and the extra hardware completely removed, please open a new issue.


Make it possible to change the "json" key in package json

Make it possible to change the "json" key/tag in the json package, so other people can create packages that use different tag name simply by changing the string and extending the functionality.
Apparently it's just a matter of changing the constant "json" on the line below by a public variable
tag := sf.Tag.Get("json")

This line of code is in the following file:
https://github.com/golang/go/blob/master/src/encoding/json/encode.go#L1107
go version go1.8 darwin/amd64
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/cesar/Projects/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/0s/p11dph4n2hv356yq969fxvwm0000gn/T/go-build150354871=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"

other people can create packages that use different tag name simply by changing the string and extending the functionality.

I'm a little confused why this needs the tag name to be configurable. Can't you just implement json.Unmarshaler? Or have packages satisfy some other interface that interacts with your custom decoder?

Hello @kevinburke, I'm not trying to implement a decoder, I just do not want the user of my package that already uses a tag to have to define one more. If I can just change the tag name that the json package is using the problem would be resolved without duplicate code.
I will investigate to find out if an unmarshal coton solves the problem but I believe it is not what I need.

It's unfortunate that they have to define an extra tag, but I'm guessing that changing the tag name is going to be a non-starter... among the problems, what if you rename the json tag to xml, what if you import a package that globally renames the json tag and wreaks havoc on code that isn't expecting it to be renamed, what if you redefine it in the midst of parsing a struct.
You are certainly free to export the code in src/encoding/json/*.go to your own namespace and add code to it there...

Sorry, I'm going to decline this one. The json package is mostly frozen, especially for things like this that introduce extra complexity for everybody (code to maintain for us, godoc for everybody to read and understand) for marginal convenience for a few users.

Certainly, define the new tag name can not be global, so it not to affect the other parts of the code that is using the json package. But this would imply creating a struct to and returning a new instance of the configuration variables.
As you mentioned I could export this small part of the code and make the changes myself, but by default I prefer to try to use the official packages and try to reduce to the maximum duplicate code ... I will reserve this solution in case I can not find another solution.
I'm not sure if I'm being clear so let me show you what I'm trying to do.
This is the package I am trying to implement:
https://github.com/crgimenes/goConfig
Everything works perfectly well, I use the tag "cfg" except when I try to read the settings of a json file, in this case the user of the package must also define a json tag in the struct that It's moving on to my package to have the same changes in the field name.

ok @bradfitz I understand it.
Please if imagine some solution let me know.


Containers and its image (container.image.repository)

Describe the bug
The field container.image.repository (and others similar like container.image) are generated based on the image digest, instead of the "real" name of the image being used. Although this is not a common use case, it might happen that the same digest is associated with more than one image. In this case, it is
I can agree that images with the same digest are the same image, even if they have a different image name. But that does not support the fact that container.image.repository is being computed based on image digest, as there are cases in which this is not true.
How to reproduce it

Create a Dockerfile with a basic program that triggers any of the rules and includes container.image.registry within its output fields. For example:

# Dockerfile
FROM docker.io/library/golang:1.12.0-alpine3.9

RUN mkdir /app
ADD . /app
WORKDIR /app
RUN go build -o read_sens_file read_sens_file.go
CMD ["/app/read_sens_file"]

# read_sens_file.go
package main

import (
    "os"
    "fmt"
    "time"
)

func main() {
    for {
        const filename = "/etc/shadow"
        time.Sleep(5 * time.Second)
        file, _ := os.Open(filename)
        defer file.Close()
    }
}

Build it with: docker build -t <registry/imagename1> .
Build it again with a different image name: docker build -t <registry/imagename2> .
Run both images with docker. Container1 runs image1, container2 runs image2.

Result: some alerts will show that one of the containers is running the image of the other container, hence incorrect.
01:42:33.426489141: Warning Sensitive file opened for reading by non-trusted program (user=root user_loginuid=-1 program=read_sens_file command=read_sens_file file=/etc/shadow parent=containerd-shim gparent=systemd ggparent=<NA> gggparent=<NA> container_id=2095c238932b image=docker.io/my_repo/imagename1) k8s.ns=app3 k8s.pod=read-sens-file-6cc7c65b74-d2z92 container=2095c238932b

Expected behaviour
The field container.image.repository displays the real name.
Environment
I reproduced this several times with Kubernetes (K3s, Helm running falco, contained as CRI) but it is the same with a single host + docker.

Falco version: latest
System info: not relevant
Cloud provider or hardware configuration:
OS: not relevant
Kernel: not relevant
Installation method: not relevant

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

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

/reopen
/remove-lifecycle rotten

@jasondellaluce: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

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

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

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

/reopen
/remove-lifecycle rotten

@jasondellaluce: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

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

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

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

/remove-lifecycle rotten
/reopen

@jasondellaluce: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen

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

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close


Paint bucket doesn't work on vertical half blocks

When I use the paint bucket on a big solid-color blob, it doesn't fill vertical half blocks of the same color.

That's strange, is there any chance you could provide a screenshot?
Sent from my iPhone

On 17 Jan 2017, at 17:36, Josh Renaud<EMAIL_ADDRESS>wrote:
When I use the paint bucket on a big solid-color blob, it doesn't fill vertical half blocks of the same color.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Actually, scratch that, I get what you mean now.
Sent from my iPhone

On 17 Jan 2017, at 17:36, Josh Renaud<EMAIL_ADDRESS>wrote:
When I use the paint bucket on a big solid-color blob, it doesn't fill vertical half blocks of the same color.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Let me know if this doesn't solve the issue.


Automated cherry pick of #5409: Enable IPv6 on OVS internal port if needed in bridging mode

Cherry pick of #5409 on release-1.13.
#5409: Enable IPv6 on OVS internal port if needed in bridging mode
For details on the cherry pick process, see the cherry pick requests page.

/test-all
/test-flexible-ipam-e2e

/test-all
/test-flexible-ipam-e2e

@antoninbas
The flexible ipam e2e job is not stable, I think Ran is still working on this to triage it. @gran-vmv any finding so far for the test failure?


starting etcd service fails

In contrib/ansible, using deploy-cluster.sh to setup a cluster of 3 Ubuntu 16.04.1 servers (virtual machines provisioned on hyper-v), the playbook fails at role etcd, at etcd-start.yml, at task Enable etcd.
The error message returned by ansible is:
fatal: [docker1]: FAILED! => {"changed": false, "failed": true, \
"msg": "Error when trying to enable etcd: rc=1 Failed to execute operation: No such file or directory\n"}

If any more info is required, pls let me know.

This is connected to Ubuntu 16.4 using systemd instead of init, I suppose. A workaround that made the playbook proceed was to use the Debian task in etcd-configure.yml, to be precise:

In roles/etcd/tasks/etcd-configure.yml,
in task Write etcd systemd unit file for Debian
with condition when: ansible_distribution == "Debian",
change the condition to when: ansible_distribution == "Debian" or ( ansible_distribution == "Ubuntu" and ansible_distribution_major_version == "16" )

probably can skip the Create upstart script task in etcd-install-github-release.yml for Ubuntu >= 15, and should rename the tasks accordingly.
... but etcd was still not recognized as a service O_o playbook passes, but running service etcd start on the machine returns the error message etcd: unrecognized service
Going to install with apt-get instead, version 2.2.5 is in repos, and use the config provided by ansible and see where that gets me.

Thanks @valentin-krasontovitsch for looking into it

With vagrant and xenial box (Ubuntu 16.04 LTS) [1] I hit the same error.
[1] https://atlas.hashicorp.com/yk0/boxes/ubuntu-xenial

I got to the point of running systemctl start etcd working (deploying etcd.service file). Just, the service failed to start.

Ok, got it running. Once need to create etcd user and /var/lib/etcd directory (as is specified in etcd.service and etcd.conf files). After that, etcd service is started.

Totally checks out, thanks, @ingvagabund! Ran it like you with Vagrant, worked fine, until the playbook tries to download kubernetes-master, as hinted at in #1697... does that need a new issue?

Already working on kubernetes-master. Almost done.

here https://github.com/kubernetes/contrib/pull/1700

ok, cool : )


AnonReviewers group: add the Authors group as nonreaders

It seems we are not hiding the identity of the reviewers of the papers where the PC is an author.
Issue reported by: https://openreview.net/group?id=ijcai.org/IJCAI-PRICAI/2020/Workshop/XAI

@melisabok The Authors are added as non-readers for the AnonReviewer groups.

And the PC User is not able to access the group directly because of being an author of this paper:

I think the issue is that on the forum page the get /notes api call to get the forum replies is getting the tauthor for all the reviews when the PC is logged in.

I found that when I log in as a Reviewer for this paper, I can only see the tauthor for the review that the logged-in reviewer had posted. For the PC user on the other hand, tauthor is being returned for all the reviews.
It does not seem like an openreview-py issue.

Thanks Mohit for checking this. You are right, the bug is in the backend when it checks if the logged user can see the tauthor of the note. There is an OR condition, where if the user is writer of the note then it can see the identity, I think this is not correct. What do you think?

Here is the code: https://github.com/openreview/openreview/blob/master/repositories/notes.js#L520
if the user is ( writer OR author OR reader_of_the_signature_group OR super_user) then the identity is revealed.

Thanks Mohit for checking this. You are right, the bug is in the backend when it checks if the logged user can see the tauthor of the note. There is an OR condition, where if the user is writer of the note then it can see the identity, I think this is not correct. What do you think?

You are right. The PCs need not be writers for official reviews.

@melisabok can we close this issue since it was fixed at https://github.com/openreview/openreview/pull/2165 ?

Yes!


Adding explanation for hash values assignments

I had a case where I needed to assign a hash to an attribute. I instinctively did
Fabricator(:machine) do
  member {a:1}
end

which of course didn't work, spitting an error saying there was no such Fabricator for member. schematics says in this case that members has a proc value and {a:1} for params.
After thinking this through, it made sense since you can define values by blocks and you can pass options as well.
I tried
Fabricator(:machine) do
  member({a:1})
end

but it didn't turn out to work either since the value I pass is actually considered as parameters for the fabricator, which I find an unexpected behaviour.
In the end
Fabricator(:machine) do
  member {a:1}, nil
end

did get me what I was after, but I thought it might be worth describing this caveat on the official website (provided I have the correct solution).
MRI ruby 2.1.0
Fabrication 2.9.7

I'd suggest adding this to documentation in Defining Fabricators#Attributes, taking from @paulelliott's words:

If you need to assign a Hash value to an attribute, you need to do so inside a block. Otherwise, Fabricate would treat is as he options argument to the fabricated attribute. (where you would normally define a count, custom fabricator, etc.)
Fabricator(:person) do
  name 'Greg Graffin'
  settings do
    {favorite_color: 'yellow', egg_preference: 'scrambled'}
  end
end

Good call, @joallard. I just added it to the docs.
https://github.com/paulelliott/fabrication-site/commit/9318c37fb6c82f7216803c32a4d7edd48b5ab3ec
Thanks!


New normalized changes to a co-ordinate system with (0, 0) at the center

Based on every correction of the previous PR, I've redone the changes and updated the code to normalizes to a co-ordinate system with (0, 0) at the center, using a common denormalize function.

Great work! @nangahamandine
Thanks! LGTM 👍

Thank you!


More features (and tests)

I added a test harness and some tests for the code generator, plus a couple of new features:

Delete elements from an array with = nil
Array indexing will not fail even if the element is nil if the indexing is used for control-flow and not for its value
Coerce integers to floats on the Lua->Titan transition if Titan is expecting a float but Lua is passing an integer

Codecov Report

Merging #29 into master will increase coverage by 2.8%.
The diff coverage is 96.61%.

@@            Coverage Diff            @@
##           master      #29     +/-   ##
=========================================
+ Coverage   71.62%   74.42%   +2.8%
=========================================
  Files          14       16      +2
  Lines        1836     2389    +553
=========================================
+ Hits         1315     1778    +463
- Misses        521      611     +90

Impacted Files
Coverage Δ

spec/checker_spec.lua
100% <100%> (+5.48%)
:arrow_up:

spec/coder_spec.lua
100% <100%> (ø)

titan-compiler/ast.lua
92.85% <100%> (+0.1%)
:arrow_up:

titan-compiler/checker.lua
73.4% <87.5%> (+12.26%)
:arrow_up:

titan-compiler/coder.lua
65.68% <90.74%> (ø)

titan-compiler/types.lua
44% <0%> (+1.33%)
:arrow_up:

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 acc1a27...3523095. Read the comment docs.


Fix for tessera not working in mac m1/m2

Fix for https://github.com/Consensys/quorum-dev-quickstart/issues/277
This is hack or hot fix for mac m1/m2 machines, if we pull tessera amd64 arch docker it works fine in mac m1/m2 machines too.

Yeah, check #274
I too faced the same issue and temporarily resolved it by adding --platform=linux/amd to the script in #274.


fix: center the navbar menu items

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design
/kind user-interface

/kind content

/kind translation

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area videos

What this PR does / why we need it:
Centers the navbar menu.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: bullet03
Once this PR has been reviewed and has the lgtm label, please assign vjjmiras for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

layouts/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: bullet03, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

layouts/OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: ccc5c86c82eda627b8981096f7fc2aff48a86219


(feature) Add ability for proxy to inject context

Requirements
I'd like to be able to add additional context at the proxy level that can be used in addition to the context provided by the client through the proxy.
For example, the user requests a feature flag passing in email address. The proxy adds additional context that was configured by it, such as the environment in which the proxy is run, such as 'production: true/false'. These two values are then used by the rules to return the desired flag.
The use cases are wide-ranging, but essentially consist of context that a generic service or client using the proxy does not know or need to know, but affects the rule processing. This tends to be very necessary when you have multiple deployed environments, where there is a set of dev, staging or production environments and you want differing behaviour between them but don't want to pollute services with environment-specific context.
It may be that this feature exists, but I was unable to find a way to do this.
I had a quick look at the proxy code, and it seems that additional configuration in the form of a context section would be required and then the values in there would be merged with with the incoming client context (probably with the proxy context taking precedence for any matching keys), before passing down to the go-feature module itself.

Hello @richardj-bsquare I like this idea and it will be a nice addition to what is already available.

@richardj-bsquare I have opened a pull request for this new feature.
If you can have a look at it and give me some feedback, I would like to see if it can solve what you had in mind.
https://github.com/thomaspoignant/go-feature-flag/pull/1285


session_regenerate_id

Warning:  session_regenerate_id(): Cannot regenerate session id - headers already sent in C:\server\www\mkmanager\vendor\zendframework\zendframework\library\Zend\Session\SessionManager.php on line 272

Warning:  session_regenerate_id(): Cannot regenerate session id - headers already sent in C:\server\www\mkmanager\vendor\zendframework\zendframework\library\Zend\Session\SessionManager.php on line 272

Warning:  Cannot modify header information - headers already sent in C:\server\www\mkmanager\vendor\fsvxavier\cityware\library\Cityware\Mvc\Controller\AbstractActionController.php on line 72
I using php 5.6, nginx and ZF2.3.5

This appears to be very incomplete, and possibly expected behaviour. you already sent output to the browser in C:\server\www\mkmanager\vendor\fsvxavier\cityware\library\Cityware\Mvc\Controller\AbstractActionController.php on line 72, which makes it impossible for php to send headers.
I'm going to close this for now, but please feel free to re-open with more complete information about what you did and why you feel this is a bug in ZF.


Compilation hangs if there are errors in sw.js

It would be good if compilation errors were displayed when there are errors in sw.js. Currently, it just hangs.

That's a good point. Do you have an example of error that hang the compilation?

https://github.com/oliviertassinari/serviceworker-webpack-plugin/blob/master/docs/src/sw.js
If you just introduce a syntax error, say:
let assetsToCache = [
  ...assets,
  'fasd'
  './',
];

Also, if the project is setup with eslint, it would nice to apply the same.
Thanks for the work :)

@anilshanbhag I have tried your example, here is what I have from webpack@2. It doesn't hang on my side. I'm closing until another reproduction test case is provided.
     ERROR in ./docs/src/sw.js
    Module build failed: SyntaxError: Unexpected token, expected , (20:2)

      18 |   ...assets,
      19 |   'fasd'
    > 20 |   './',
         |   ^
      21 | ];
      22 |
      23 | assetsToCache = assetsToCache.map((path) => {

@oliviertassinari I am using it with Vue. I tried the example in docs and that does print out errors from service worker. However, when i use it with vue templates it doesn't (atleast it doesn't hang now). Steps to reproduce:

Follow instructions here to create a dummy vue project: https://github.com/vuejs-templates/webpack.
Include the service worker plugin in package.json. Add a simple sw.js in src/ folder. Register plugin in `build/webpack.dev.conf

    new ServiceWorkerWebpackPlugin({
      entry: path.join(__dirname, '../src/sw.js'),
      excludes: [
        '**/.*',
        '**/*.map',
        '*.html',
      ],
    }),

I have been using the plugin for a while and making sure the service worker compiles at each step. However just happened to code for an hour and now I have been debugging for nearly an hour trying to isolate where the js error is :/ Would be of great help if the plugin reported errors like it does in the example.

Thanks for the reproduction example. I don't have time to look into it but I'm reopening so someone could.

This seems related to #29


Update tls cert secret validation due VerifyCertSecrets() change

Depends-On: https://github.com/openstack-k8s-operators/lib-common/pull/559
Jira: OSPRH-9991

/retest

/retest

@stuggi: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name 	Commit 	Details 	Required 	Rerun command
ci/prow/heat-operator-build-deploy-kuttl 	1d27c8d link 	true 	/test heat-operator-build-deploy-kuttl
Full PR test history. Your PR dashboard.

error: build error: Failed to push image: trying to reuse blob sha256:c0ca389759b542396e6b30afcb100a3823d3b343bc847eee7f60d609a106f674 at destination: pinging container registry quay.rdoproject.org: Get "https://quay.rdoproject.org/v2/": net/http: TLS handshake timeout

/test heat-operator-build-deploy-kuttl

@stuggi: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name 	Commit 	Details 	Required 	Rerun command
ci/prow/heat-operator-build-deploy-kuttl 	1d27c8d link 	true 	/test heat-operator-build-deploy-kuttl
Full PR test history. Your PR dashboard.

{  failed to wait for the created cluster claim to become ready: timed out waiting for the condition}

/test heat-operator-build-deploy-kuttl

/retest


[UT and Tutorials] Deprecate import intel_extension_for_pytorch in python/test/** and python/tutorials

As per offline conversation with @pbchekin changes in UT's and Tutorials needs to be done at the same time.
Closing

#1853

as duplicate.

Still need to deprecate upstream for python/test/backend/third_party_backends/test_xpu_backend.py.

Done in https://github.com/triton-lang/triton/pull/4616, merged in https://github.com/intel/intel-xpu-backend-for-triton/pull/2081.


ILoggingFactory should not implement IDisposable

A similar issue has been raised here. Abstractions should not implement IDisposable, as @nblumhardt explained this very clearly almost six years ago (and quoted by @ploeh):

an interface [...] generally shouldn't be disposable. There's no way for the one defining an interface to foresee all possible implementations of it - you can always come up with a disposable implementation of practically any interface.

While the default LoggingFactory implementation can (and probably must) be disposable, the interface shouldn't be.

:+1:

@lodejard thoughts on this?

@rynowak What are your thoughts on this (and the corresponding MVC bug)?
We should follow similar patterns...

Discussed with @rynowak and @lodejard and we agree the interface shouldn't implement IDisposable.

After further consideration, we think this change would be incorrect. The disposability of ILoggerProvider objects in an ILoggerFactory is a contractual obligation and needs to be enforced. Because ILoggerProviders are constructed outside a container, there is no central location for them to be disposed aside from the ILoggerFactory.

Interfaces aren't contracts: https://blogs.msdn.microsoft.com/kcwalina/2004/10/24/api-design-myth-interface-as-contract