Don't copy if there's no selection

Summary of the Pull Request
Converts every action we have to a TypedEventHandler. These are in accordance with #1349. This allows us to not handle some events, like the Copy event.

References
Really heavily inspired by #1349. @DHowett-MSFT thinks we should ship this fix this month an I agree. Hence the PR before the spec is finished.

PR Checklist

[x] Closes #2258
[x] I work here
[ ] Tests added/passed - ooh there's an idea

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

The PR mentions closing 2258 but it should be closing 2285 instead right?

@dsafa good catch. thanks.

I'd prefer the name be a little more.. specific on what it does. Fixing copy eating ^C is a side effect of better design more than anything, but .. hm


Makefile: Set VERSION & REVISION only if unset

This is useful while building nerdctl from git tag. For example, while building rpm from a tagged source tarball.
Signed-off-by: Shreenidhi Shedi<EMAIL_ADDRESS>

@AkihiroSuda you're welcome and thank you as well.


Add GitHub Actions workflows for running the Cypress tests

Description
Adds two GitHub Actions workflows that prepare and run the Cypress tests. One workflow prepares OpenSearch and OpenSearch Dashboards from source and the other prepares them from a snapshot executable. The workflows use the github.repository context variable to specify which version of tianleh-test-cases to checkout when running the Cypress tests.
Signed-off-by: Aviv Benchorin<EMAIL_ADDRESS>Issues Resolved
N/A
Check List

[ ] New functionality includes testing.

[x] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Commits are signed per the DCO using --signoff

Could we run test against latest bundle article of OS and OSD both local and with CI


app: Allow to open about:blank URLs

Some plugins may want to show popups, e.g. for authentication, so we
should allow such popups.
How to test:
In a plugin's component that gets loaded, add something like:
React.useEffect(() => {
    window.open('about:blank')
  },
  [])

Launch headlamp desktop.

You should see an empty popup window from the app, not the external browser.
fixes #455

@lijianzhi01 Let me know if this works well for you.

Popup did work, but cross origin problem shows up. Desktop app load landing page through file protocol. But popup page is opened from landing page with http protocol. MSAL in landing page will manipulate popup window. If parent and child page use different protocol, location, and port, it would be failed to authenticate.

Making it a draft now since we'll soon now whether we need it.


verify last hour on energy state

Introduced new potential bug with Nordpool: when processing new data, energy last hour is just added from the hour before. How to verify that it is still in sync with the state?

Not necessary after PR #60


Day49: Reverse String - Recursion

Reverse String
https://leetcode.com/problems/reverse-string/
Write a function that reverses a string. The input string is given as an array of characters s.
You must do this by modifying the input array in-place with O(1) extra memory.

Example 1:
Input: s = ["h","e","l","l","o"]
Output: ["o","l","l","e","h"]
Example 2:
Input: s = ["H","a","n","n","a","h"]
Output: ["h","a","n","n","a","H"]


Tree Shap gives extremely high shap values while Kernel Shap doesn't

Hello there,
I have recently been trying to evaluate SHAP and its reliability. In order to do this, I've been generating datasets with random values and labeled them according to arbitrary conditions (eg: feature_0 < 0.05, feature_1 < 0.95). I have then fitted a RandomForestClassifier from sklearn on the data and explained its predictions. It has worked fairly well for boolean conditions.
I think I ran into what seems to me like a bug with the Tree Shap algorithm. With a condition that includes an addition, the classifier starts having difficulties to predict. In turn, the TreeExplainer starts producing extremely high values while the KernelExplainer outputs values in the usual range. The Kernel Explainer is able to definitively point to the relevant features as showcased in its summary plot while the Tree Explainer's summary plot is much less definitive in its responsibilities.
Tree SHAP summary plot

Kernel SHAP summary plot

Is this expected? Is it a predictable behavior for the algorithm ?
I have also included a jupyter notebook with the necessary code for data/feature generation and other code required to reproduce the issue.
Shap Values Tree vs Kernel.ipynb.zip
Please, let me know if you need details on how to reproduce this.
Thanks for your time and your work.

Thanks for sharing your comparison! It does look like something is strange about the TreeExplainer output in your example. When I downloaded your notebook to reproduce the problem it went away if I set the model's max_depth to 10. This makes me think it is an instability coming from the really deep RF trees that you are building.
I am going to leave this issue open until I track down where there was an issue.

Hi Scott,
Any luck figuring out where this issue is coming from? I ran into the same issue using TreeExplainer(), got really high SHAP values.

Just looking into it again now, and still trying to track it down. It only randomly happens with very specific (and large) trees.

Thanks for looking into this Scott, appreciate this tool!
I'm going to try limiting max_depth to see if that works. Do you have more specific thoughts about what causes values to be large other than trees being deep? You mention randomly, does this mean you've seen cases with large trees that doesn't run into this issue? Was there anything noticeably different about those?

I have only seen it for very deep trees. By "randomly" I mean that if I try and make a simpler model that still has the same issue it goes away. You can always check to make sure things are good by checking that the sum of the SHAP values equals the margin output of the model (minus the expected value).

After looking at this more it does seem to be a floating point prescision issue. I’ll post a note here when I finish implementing a more numerically stable way that fixes this.

Thanks for the offer @andrewortman! I decided the best option right now was to add a check into the code to see when additivity is violated. Since this check is turned on by default, it should catch most things. If a numerical precision issue comes up then we suggest users try the feature_dependence="independent" option. This uses a different more numerically stable algorithm that is better suited to deep trees. If you are still interested in helping, I would appreciate someone looking over the new check_additivity option I added to TreeExplainer. Right now it only checks when the model's output is the margin, and it does not check LightGBM and CatBoost native explainers at the moment.

I'm hitting this too, but:

I'm using feature_dependence="independent";
the additivity check you added is not failing.

@marco-c  could you clarify the problem? If additivity is passing then it is probably working correctly.

I can no longer reproduce, weird. I'll report back if I can reproduce again.


Distinguish generic color and type name colors

I searchd the issues, but didn't find existed request.
Rust is a strong type language. The type definition would look very complicated when there are lots of generics.
Generics are less important than trait name and type name (struct name, enum name), so I'd like to see their colors be different.
It might not be the best place to report this inconvenience here.

Right now, the Rust grammar that we use (https://github.com/dustypomerleau/rust-syntax/blob/master/syntaxes/rust.tmLanguage.json) emits the scope for both TraversePartialTree and  TaffyView.
You can file a feature request again the Rust grammar (https://github.com/dustypomerleau/rust-syntax) that it creates a different token for the trait. Then themes can give it a different color (or you can customize the color in the settings).

@aeschli  I see, thanks


Review the generation of ROS objects, can this be simplified for the user?

See documentation: https://github.com/ipa320/ros-model/blob/master/docu/NewCommunicationObjects.md

Is it possible to integrate it on the web interface?? That means:

[ ] run the command to extract objects on a Docker container
[ ] make the function available though a call from http://ros-model.seronet-project.de/

Done https://github.com/ipa320/ros-model-cloud/commit/35e2b56c97e302da5b1c1faa1a5daf7f1f7d0ff7
See: http://ros-model.seronet-project.de/


Change the page title when navigating to apps

E.g. https://apps.sandstorm.io/app/h37dm17aa89yrd8zuqpdn36p6zntumtv08fjpu8a8zrte7q1cn60 should have a title like "Etherpad - Sandstorm App Market" instead of just "Sandstorm App Market".

+1. This would make finding apps from in history a lot easier (eg. in browser search bar suggestions)

The fix for this is now live. Examples:

https://apps.sandstorm.io/app/h37dm17aa89yrd8zuqpdn36p6zntumtv08fjpu8a8zrte7q1cn60 has a title of "Etherpad - Sandstorm App Market"
https://apps.sandstorm.io/ has a title of "Sandstorm App Market"
https://apps.sandstorm.io/genre/Productivity has a title of "Productivity - Sandstorm App Market"

Thanks all for filing the bug, commenting, and GitHub-reactions-ing! :100:


fix: home page loading & go to add article.

fix bug: #294

fix bug: #293

The PR environment is ready, please check the PR environment
[Attention]: This environment will be automatically cleaned up after 6 hours, please make sure to test it in time. If you have any questions, please contact the author of the PR or the community team.

The PR environment is ready, please check the PR environment
[Attention]: This environment will be automatically cleaned up after 6 hours, please make sure to test it in time. If you have any questions, please contact the author of the PR or the community team.

The PR environment is ready, please check the PR environment
[Attention]: This environment will be automatically cleaned up after 6 hours, please make sure to test it in time. If you have any questions, please contact the author of the PR or the community team.


Start year and end year parameters not being respected

[via email to @jdbcode]
I have been using this module to look at the NDVI time series of some fire sites I studied in the Northwest Territories. I am trying to run the Landsat example, but I seem to be having some problems setting the ee-lcb parameters. I am interested in extracting only the data from 2010-2020. For some reason, regardless of how I change the start/end year, I am still always getting 1984-2018. I have included a screenshot below. The code is line-for-line the same as your example.

I can't reproduce the problem. If I change the start and end year, the chart reflects the change (see image). I know you said the script is line-for-line the same, but can you send me the script link so I can try to reproduce the issue.

Hi Justin, here's the script link.

This is strange. The fix is to define a props variable resulting from the lcb.setProps call and when lcb props are needed, retrieve them with props.propertyName instead of lcb.props.propertyName. I can't figure out I could not reproduce. Anyway here is your script with the changes:
https://code.earthengine.google.com/037107c9d1d958f59da5ce591e6f2df6
I'm going to keep this open for a while until I can figure out why I could not reproduce.
I have fixed the example on the readme page.

Not using the ee-lcb module anymore - this particular issue is not relevant anymore.


Templating is broken.

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
tested on both 1.7.1 and 1.7.4
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN="/home/nikos/projects/go/bin"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/nikos/projects/go"
GORACE=""
GOROOT="/opt/go"
GOTOOLDIR="/opt/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build965913370=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"

What did you do?
please see the the article here
in addition to this {{else if}} also doesnt work
as here
<script>
			  {{ if .PassChange }}
			  swal("{{.Lang.Success}}", "{{.Lang.PleaseLogin}}", "success")
			  {{ else if .UserExists }}
			  swal("{{.Lang.Fail}}", "{{.Lang.AlreadyMember}}", "error")
			  {{ end }}
</script>

For questions about Go, see https://golang.org/wiki/Questions.

@bradfitz this is a bug not a question if you read what i wrote above everything is proper but templating wont render so how come this is just a question i dont ask how to use templating

It's not in the format of a typical bug report. A good bug report includes complete but minimal reproduction code to demonstrate the problem, and describe problems, expectations, and actual results. You deleted those sections from the issue template. You can't just ignore the bug report template and refer to a stackoverflow page which is also lacking detail.
I suggest you discuss this on the mailing list and come back when there's a detailed bug report to be filed.

well so this is how google works if something is not in the shape you expect dont even check that because the cover is more important than the actual problem . Correct ? @bradfitz . Above the problem is entirely described i just didnt want to write the same issue over and over again .

Sorry, if you don't want to write a self-contained and understandable bug report, I guess we can't help.


[Feature] Add features Section

Description
Hey @rohansx I want to add a features section so that readers can know at one glance what features you provide on tour website. Please assign me this issue, Thank you!
Screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the [Contributing Guidelines]
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@sumitkr2000 waiting for your PRs


[doc] Renew the tutorials

The first introductory is completely rewritten from scratch. Now it starts from the generic configuration that ships with ReFrame and expands both the configuration and the test concepts along the way. It should be now feasible to start with the tutorials with practically zero effort.
The previously called "Advanced tutorial" is now renamed to "Miscellaneous topics", since it covers independent topics. A couple of topics has been moved from the previous basic tutorial to this one.
The structure of the tutorial tests has changed drastically as well. They are not sharing a common resources folder anymore, but each example is in general in its own folder. Also, no more generic names for the tutorial example files are used.
The rest of the documentation was adapted and further improved where needed.
The CI is also adjusted in regards to the tutorial examples.

Closes #1158.
Fixes #986.

Hello @vkarak, Thank you for submitting the Pull Request!

In the file docs/conf.py:

Line 149:80: E501 line too long (131 > 79 characters)
Line 150:80: E501 line too long (93 > 79 characters)

Do see the ReFrame Coding Style Guide

@jenkins-cscs retry daint

Codecov Report

Merging #1397 into master will increase coverage by 0.29%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1397      +/-   ##
==========================================
+ Coverage   91.46%   91.75%   +0.29%
==========================================
  Files          83       83
  Lines       12277    12712     +435
==========================================
+ Hits        11229    11664     +435
  Misses       1048     1048

Impacted Files
Coverage Δ

reframe/core/pipeline.py
92.89% <ø> (+0.40%)
:arrow_up:

reframe/utility/color.py
100.00% <0.00%> (ø)

reframe/core/containers.py
100.00% <0.00%> (ø)

unittests/test_argparser.py
100.00% <0.00%> (ø)

unittests/test_check_filters.py
100.00% <0.00%> (ø)

unittests/test_sanity_functions.py
100.00% <0.00%> (ø)

...ittests/resources/checks_unlisted/kbd_interrupt.py
100.00% <0.00%> (ø)

unittests/test_deferrable.py
99.62% <0.00%> (+<0.01%)
:arrow_up:

unittests/test_buildsystems.py
99.16% <0.00%> (+<0.01%)
:arrow_up:

reframe/core/buildsystems.py
96.75% <0.00%> (+0.01%)
:arrow_up:

... and 34 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 5115365...340fe72. Read the comment docs.


Create a postman collection for space cloud

The problem faced currently?
Currently, if we want to test out some endpoints of Space Cloud directly or try out some API which isn't exposed through the API explorers in console, then the only way of knowing the endpoint details is checking the server/routes.go file. And even then we have to inspect the handler and find out all the possible fields in the body and put it manually in postman.
How can we solve it?
Let's make a postman collection for both the config and API endpoints for gateway and runner. And let's commit those postman collections into the space-cloud repository. This will make it easy for other contributors/users also to play around with space cloud API directly.

If you want this feature to be implemented, give it a thumbs up reaction, so that we can determine which features are important to you.
👍

Done


Keybinding conflict with Tasks

Conflict detected, command `editor.action.insertLineAfter` cannot be triggered due to task.new

Moving to @alexandrudima. I have not change anything in terms of keybings & tasks. Might be the new key binding algorithm for Mac. @alexandrudima please move back if you think otherwise.


Remove nodes

Hi,
Having the Add nodes option in IM Dashboard is great.
Would it be possible to have the opposite? i.e. Delete nodes (or similar)
Best regards,
Sebastian

Hi @sebastian-luna-valero,
It is already possible. You have to select one of the VMs, and in the VM Info page, select the "Terminate" option:
https://docs.egi.eu/users/compute/orchestration/im/dashboard/#vm-info-page
Best regards.

Thanks!
But this would imply removing nodes one by one, right?
Would it be possible to remove them in groups?
Best regards,
Sebastian

But this would imply removing nodes one by one, right?

Yes.

Would it be possible to remove them in groups?

I will make it in next releases.

Brilliant, thank you very much!

Thanks @micafer
I tested it with a virtual k8s cluster. I can successfully delete VMs by selecting them from the menu. VMs are removed both from IM Dashboard and OpenStack. However, inside k8s, the deleted nodes appear as NotReady. I guess that's expected.
Thanks for adding this functionality!

An additional comment regarding:

It is already possible. You have to select one of the VMs, and in the VM Info page, select the "Terminate" option:

In the VM Info page, should Terminate button be named Delete? So the name of the button is consistent in both the infrastructure view and the VM Info page. It would also help if they both have the same icon.

Looks great, thanks!


Fix spelling CharacteristicFlags ENCRYPT_WRITE and allow multiple flags on characteristic

Fix spelling of ENCRYPT_WRITE and allow multiple flags on characteristic

Hi thanks for the PR. I believe it's already possible to set multiple flags on both both characteristics and descriptors (for example- CharFlags is an enum.Flag). I'd prefer to keep the current implementation (though it is arguably confusing) but I will add an example to the readme.

I understand. If it already works with multiple flags then no need to change it. Would appreciate a comment in the docs about how it's done though :)
About the spelling of ENCRYPT_WRITE flags that's currently ENCRPYT_WRITE, that does not end up as an accepted flag name by Bluez. Should I make a seperate PR with that commit and you can close this PR or would you prefer making that change?

From: Space Cheese @.>
Sent: Friday, December 16, 2022 8:23:22 PM
To: spacecheese/bluez_peripheral @.>
Cc: Martwall @.>; Author @.>
Subject: Re: [spacecheese/bluez_peripheral] Fix spelling CharacteristicFlags ENCRYPT_WRITE and allow multiple flags on characteristic (PR #16)
Hi thanks for the PR. I believe it's already possible to set multiple flags on both both characteristics and descriptors (for examplehttps://github.com/spacecheese/bluez_peripheral/blob/master/tests/gatt/test_characteristic.py#L30- CharFlags is an enum.Flaghttps://docs.python.org/3/library/enum.html?highlight=flag#enum.Flag). I'd prefer to keep the current implementation (though it is arguably confusing) but I will add an example to the readme.
—
Reply to this email directly, view it on GitHubhttps://github.com/spacecheese/bluez_peripheral/pull/16#issuecomment-1355470684, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIBOXZ22RXTLU5BN54PIUK3WNS6SVANCNFSM6AAAAAATBB2PUY.
 If you don't mind making a PR that would be great and I'll add something to the docs.


Failed to resolve XMPP server

(4:15PM) Failed to resolve XMPP server: lookup _xmpp-client._tcp.www.planconnect.eu on <IP_ADDRESS>:53: no such host

anybody can help?

Same error with my own XMPP server.

Have the same issue.

Have you setup the SRV records for your server correctly? If not, you can probably edit the config file directly to set the server's address.

the SRV records setup correctly, but xmpp-client can't find host.
how should i config file? in .xmpp-client nothing about servers


Weird behavior of the problemMatcher.

VSCode Version: 1.4.0
OS Version: Fedora Linux 24

Steps to Reproduce:
main.cpp:
int main() {
    error
}

.vscode/tasks.json:
{
    "version": "0.1.0",
    "command": "echo",
    "isShellCommand": true,
    "args": ["main.cpp:2:5: error: test\nfoo:1:2: error: test\nmain.cpp:3:0: warning: test"],
    "showOutput": "always",
    "problemMatcher": {
        "owner": "cpp",
        "fileLocation": ["relative", "${workspaceRoot}"],
        "pattern": {
            "regexp": "^(.*):(\\d+):(\\d+):\\s+(warning|error):\\s+(.*)$",
            "file": 1,
            "line": 2,
            "column": 3,
            "severity": 4,
            "message": 5
        }
    }
}

The output is:
main.cpp:2:5: error: test
foo:106:7: error: test
main.cpp:3:0: warning: test

But the first error isn't shown for me. If I remove the second or the third line, it works. Is something wrong with my regexp?

@jhasse the problem matcher looke great to me. I even verified it with https://regex101.com/

OK. The problem is that the error parser currently collects errors per file in batches. So
main.cpp:2:5: error: test
main.cpp:3:1: warning: test
foo:1:2: error: test

produces the correct result.
The reason being is that the task framework wants to report errors are early as possible. So when line foo... is parsed in your example errors for main.cpp are reported and then the internal state for the problem matcher is clear. When main.cpp shows up again only those errors are reported.
Is there a reason why your errors show up so intermixed ?

Yes, it happens because of errors/warnings in header files. Minimal example:
foo.hpp
#error second

main.cpp
#error first
#include "foo.hpp"
#error third

GCC's output:
main.cpp:1:2: error: first
#error first
 ^
In file included from main.cpp:2:
./foo.hpp:1:2: error: second
#error second
 ^
main.cpp:3:2: error: third
#error third
 ^
3 errors generated.

@jhasse Thanks.
Making it a bug.

Thank you :)

This got addressed a while ago. The errors are now collected de-dup in the problem collector and then send as soon as the error count changes for a resource.


[Feature] Add Kafka monitoring to the showcase

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
We are missing Kafka in the showcase, we should consider adding it. Meanwhile, currently, we are using ActiveMQ in the showcase app demo, we should replace it with Kafka, and add demo for https://github.com/apache/skywalking/issues/11929 as well.
Use case
No response
Related issues
No response
Are you willing to submit a pull request to implement this on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@peachisai PTAL.

@peachisai Any update about this?

@peachisai Any update about this?

Sorry for this, I'm preparing for a test , so I don't have time to do it these months

@peachisai Any update about this?

Sorry for this, I'm preparing for a test , so I don't have time to do it these months

Good luck for that. I am closing this for now, as it is not being processed.


find a new continuous fuzzing service

Apparently fuzzit was acquired by GitLab and they're shutting down their continuous fuzzing service, see https://fuzzit.dev/2020/06/11/news-fuzzit-is-acquired-by-gitlab/

We're now using OSS-Fuzz.


Super Admin

Hi, adonis framework is indeed very impressive and very easy to use for website development.
What I want to ask is, can this adonis create a super admin page like django?
Hopefully with a super admin like Django in Adonis, website developers can manage websites very easily in building sophisticated websites with Adonis.
thank you

I know django and I've used it, and in adonisJS the same environment(admin panel) not exist or I don't know yet   :)

Hey @nice9uy! 👋
There's not a super admin provided by Adonis and I don't know any from the community. Feel free to build one if you believe it's useful.


Make sure transparency logs are non repudiable

In #678 we created transparency logs, in #687 we use those logs to verify and in #760 we make sure those logs are available on all nodes.
We are still missing a way to verify that these logs were created by the central (authoritative) node, so this is what this issue implements:

define a way to sign a transaction log and store the signature inside it
define a way for any node to retrieve the public key from the central (authoritative) node
implement the signing when a transaction is added
implement the signature check when a transaction is retrieved

this is superseded by #780


Removed a double quote in property for garage door

There was a wrong double quote within the namespace property of the "data info" object for the "SET" request, which caused a "socket hung up" error

@osigge Wow thanks!


fix the plugins link in home page

looks good

We need a redirect_from on /docs/plugins for /docs/advanced/plugins/

Ok https://github.com/babel/babel.github.io/pull/504

Thanks


I can't find the file: "Statues_4.pcd"

How did you become aware of the file/why do you think it has to exist? Is it mentioned in a tutorial or somewhere else?

Oh, I see: it is mentioned in the conditional euclidean clustering tutorial. The file can be downloaded here: https://sourceforge.net/projects/pointclouds/files/PCD datasets/Trimble/Outdoor1/


Jest stuck - keeps spinning, no output

Environment

node -v: v6.10.3

npm -v: 3.10.10

npm ls react-scripts (if you haven’t ejected):
`-- (empty)
npm ERR! code 1

Operating system: Windows

Steps to Reproduce
No matter if start my project, or stop/start Jest - it keeps spinning and does nothing. One of five it suddenly works, then gets stuck again after a while.
There are some warnings in the developer console:

Hey,
I experience the same error.
Having a look in the Output of Jest there is an error while spawning the git process.

Error: spawn git ENOENT
    at exports._errnoException (util.js:1014:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:189:19)
    at onErrorNT (internal/child_process.js:366:16)
    at _combinedTickCallback (internal/process/next_tick.js:102:11)
    at process._tickCallback (internal/process/next_tick.js:161:9)

System

Windows 10
npm 5.0.3
node v8.1.0
VSCode 1.14.1

I would love to see the Jest integration working in my VSCode. :-)
If you need further information please contact me.
Thanks in advance
Greg

UPDATE
For me it seems that the problem is that VSCode does not resolve the path to the installed git binary.
I don't think that my problems relate to vscode-jest itself.

Have you tried running jest standalone without the plugin?  This plugin doesn't talk directly to git in any way, all of that logic is handled directly by jest.

I get this from Developer Tools
MacOS X
VSCode: 1.16.0
Jest: 21.0.2
shell.ts:419 [Orta.vscode-jest] Cannot read property 'testRegex' of undefined: TypeError: Cannot read property 'testRegex' of undefined
at JestExt.wouldJestRunURI (/Users/nicolau/.vscode/extensions/Orta.vscode-jest-2.3.0/out/src/JestExt.js:253:64)
	at JestExt.canUpdateDecorators (/Users/nicolau/.vscode/extensions/Orta.vscode-jest-2.3.0/out/src/JestExt.js:249:34)
	at JestExt.triggerUpdateDecorations (/Users/nicolau/.vscode/extensions/Orta.vscode-jest-2.3.0/out/src/JestExt.js:131:19)
	at vscode.window.onDidChangeActiveTextEditor.editor (/Users/nicolau/.vscode/extensions/Orta.vscode-jest-2.3.0/out/src/fileChangeWatchers.js:9:21)
	at e.invoke (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:55287)
	at e.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:57078)
	at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:393153
	at e.invoke (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:55287)
	at e.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:57078)
	at e.$acceptDocumentsAndEditorsDelta (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:351598)
	at t.e.invoke (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:423958)
	at e._invokeHandler (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:280554)
	at e._receiveOneMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:280244)
	at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:279271
	at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:281190
	at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:56058
	at e.invoke (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:55287)
	at e.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:57078)
	at Socket.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:28:102495)
	at emitOne (events.js:96:13)
	at Socket.emit (events.js:191:7)
	at readableAddChunk (_stream_readable.js:178:18)
	at Socket.Readable.push (_stream_readable.js:136:10)
	at Pipe.onread (net.js:560:20)

This error points to a failure to load jest settings.  Any chance you have a sample repo we can clone to try to reproduce?

I experience a similar problem, here is the output of the Developer Tools Console:
shell.ts:459 [Orta.vscode-jest] Cannot read property 'forEach' of null: TypeError: Cannot read property 'forEach' of null
	at JestExt.sortDecorationBlocks (/Users/dennisreimann/.vscode/extensions/Orta.vscode-jest-2.4.5/out/src/JestExt.js:187:19)
	at JestExt.updateDotDecorators (/Users/dennisreimann/.vscode/extensions/Orta.vscode-jest-2.4.5/out/src/JestExt.js:220:74)
	at JestExt.triggerUpdateDecorations (/Users/dennisreimann/.vscode/extensions/Orta.vscode-jest-2.4.5/out/src/JestExt.js:171:14)
	at vscode.window.onDidChangeActiveTextEditor.editor (/Users/dennisreimann/.vscode/extensions/Orta.vscode-jest-2.4.5/out/src/fileChangeWatchers.js:9:21)
	at e.invoke (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:84411)
	at e.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:86133)
	at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:479691
	at e.invoke (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:84411)
	at e.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:86133)
	at e.$acceptDocumentsAndEditorsDelta (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:430508)
	at t.e.invoke (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:509443)
	at e._invokeHandler (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:354786)
	at e._receiveOneMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:354476)
	at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:353503
	at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:355422
	at /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:85128
	at e.invoke (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:84411)
	at e.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:86133)
	at Socket.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/node/extensionHostProcess.js:4:144114)
	at emitOne (events.js:96:13)
	at Socket.emit (events.js:191:7)
	at readableAddChunk (_stream_readable.js:178:18)

This happens on startup, after that the Jest extension ist stuck with "testing changes".
Jest extension version: 2.4.5
Jest and Jest CLI version: 21.2.1
jest.config.js:
module.exports = {
  'mapCoverage': true,
  'moduleFileExtensions': [
    'js',
    'vue'
  ],
  'moduleNameMapper': {
    '^@/(.*)$': '<rootDir>/src/vue/$1'
  },
  'snapshotSerializers': [
    '<rootDir>/node_modules/jest-serializer-vue'
  ],
  testMatch: [
    '**/test/unit/**/?(*.)spec.js'
  ],
  'transform': {
    '^.+\\.js$': '<rootDir>/node_modules/babel-jest',
    '.*\\.(vue)$': '<rootDir>/node_modules/vue-jest'
  }
}

Thanks for sharing your problem @dennisreimann. Looking through sortDecorationBlocks and updateDotDecorators it looks like assertions was likely null. This was recently fixed by @BBB in #169 but it hasn't been published yet.

@dennisreimann, the fix has been published.
Closing since we seem to have resolved these.

I can confirm that the error message in the VS Code dev console is gone now. Nevertheless the extension is still stuck with "testing changes". There is no more error output I can send to debug, the Jest console is empty as well.

Any way I can provide more feedback/debugging info? Thanks!

Probably related to https://github.com/facebook/jest/issues/4419, try creating a git repo inside or waiting until the fix is released. At least this fixed it for me.

I missed your reply, sorry @dennisreimann.
Is the project set up in a git or hg repo?
Can you reproduce it with a small repo we can clone?
Are you willing to try debugging the extension with our help?

@seanpoulter unfortunately this isn't a public project.

Are you willing to try debugging the extension with our help?

Of course – is this something we can have a quick look at together in a screensharing session? Otherwise I will try to come up with a similar setup in a separate repo you can reproduce the problem with.

I'd be happy to try and figure this out on a screenshare @dennisreimann!
Here's where I'd suggest we start to figure out what's happened so far, and where it's stuck:

clone this repo  git clone https://github.com/orta/vscode-jest.git
open the repo folder in Visual Studio Code
find the testsHaveStartedRunning() method in JestExt.ts:

comment out the call to clear() the Jest output channel
add a breakpoint in the method -- if we're stuck here, then we can try and figure out how we get here

start the "Launch Extension" debug task
in the window that opens, open your repo that causes problems

Ok, I checked whether or not I can come up with more debuggable output using the steps you provided. I guess this is related, the debugging console outputs this message a few seconds after I save a test file:
Array[1]
  0:Object
    code:"ECONNREFUSED"
    errno:"ECONNREFUSED"
    syscall:"connect"
    address:"<IP_ADDRESS>"
    port:443

However, I don't get to the breakpoint I've set in the testsHaveStartedRunning method. So lets just conect via screensharing. Please send me an email (see the mail address in my GH profile) and we can arrange a time this weekend or in the upcoming week :)

I found the culprit: We are using Webpack's resolve.alias feature. This leads to files that cannot be resolved by the vscode-jest extension, so the tests can't be run.
The relevant webpack config part:
module.exports = {
  resolve: {
    extensions: ['.js', '.vue', '.json'],
    alias: {
      '@': resolve('src'),
    }
  }
}

An import example:
// with resolve.alias
import FormField from '@/vue/components/FormField'
// regular import
import FormField from '../../components/FormField'

If this is something you would like to fix, you can leave the issue open and I'll try to provide a test project. Otherwise you can close this issue as this case might be to special to address.
Thanks for your help!

Wow, glad you found it @dennisreimann!
I'm happy to keep the issue open and make sure we're properly handling the moduleNameMapper option in your jest.config.js. There's something going on if it works from the command line but not in the extension. That should be pretty quick to test.

I'm not convinced that the module resolution is the root cause. This minimal repo worked OK. :confused: The only time it I got the "testing changes" spinner was before setting up a git repo and getting the Error: This promise must be present when running with -o. error from #142.


Support Go semver convention

When running go mod tidy, the version must be prefixed with a 'v'. However, the file at https://github.com/apple/pkl/blob/0.25.2/stdlib/Project.pkl#L276 expects the version without the 'v'. Since I've placed the generated Go files in a separate repository, the default behavior of go mod tidy will fail to locate the package if the version is not prefixed with the 'v'.

I have resolved it by defining a regexp on the PklProject
version =  read?("env:VERSION").replaceFirst(Regex("^v(\\d+\\.\\d+\\.\\d+)(-[\\w\\.]+)?(\\+[\\w\\.]+)?$"), "$1")

I don't think we will support a leading v, because that leads to ambiguous situations (what do you do if there is both v1.0.0 and 1.0.0?)
Your workaround seems like a good solution!


Fix for readme FSAPI example

The FSAPI example in the readme should be:
from fsapi.net import FSDevice, wrap, nodes

# First, create the radio object
device = FSDevice("<IP_ADDRESS>")

# Create a new session id (only one at a time)
device.new_session()

# In order to simplify the usage of the FSDevice class
api = wrap(device)
friendly_name = api.friendly_name
# or manually
response = device.get(nodes / "netRemote.sys.info.friendlyName")
if response.success:
    #_ Again, type(content) = nodes.BaseSysInfoFriendlyName
    friendly_name = response.node.value

# Apply a new name via wrapper
api.friendly_name = "FooBar"
# or manually
device.put(nodes / "netRemote.sys.info.friendlyName", value="FooBar")

# get all elements of a list
valid_modes = api.ls_valid_modes()
# get a certain amount of elements beginning at index 3
valid_modes = api.ls_valid_modes(_pos=3, max_items=10)

instead of:
...

# or manually
response = device.get(nodes / "netRemote.sys.info.friendlyName")
if response.status == FS_OK:
    #_ Again, type(content) = nodes.BaseSysInfoFriendlyName
    friendly_name = response.content.value

    # Apply a new name via wrapper
    api.friendly_name = "FooBar"
    # or manually
    device.put(nodes / "netRemote.sys.info.friendlyName", value="FooBar")

...

First of all thanks for the quick fixes.
But I am verry sorry, there is still an error which you probably missed:
AttributeError: 'FSResponse' object has no attribute 'content'.
The line
    friendly_name = response.content.value
should be
    friendly_name = response.node.value
Greets

You're right, I must've overlooked that. Thank you!


Templatise the institute specific parts of the site for easy replacement

Thos replaces hardcoded oxford specific things with a yaml file in /config that controls all the oxford specific site settings e.g. attributation, favicon logo etc.
Other deployments can add their own config file to this repo to prevent us from having divergent forks, the site can have which config is being used controlled by a new env variable which points to the yaml path (defaults to the current one): YAML_TEMPLATE
This then populates the relevant sections of the site header, footer and the front page text.
closes #59

Description of this and its fields needs added to a deployment guide


Design - notify users when we cannot serve very recent/instantaneous data

The registrar's servers must be treated as unreliable - YACS cannot assume that it can get data whenever it wants. What we can assume, though, is that the server will deliver data the great majority of the time.
I know we made plans to have some way of displaying how up-to-date the data is. My suggestion is that whenever the server fails to get data, there is a prominent display warning the users that the information is X minutes outdated.

This involves frontend and backend work, so I'm tagging it as both.


Unknonw error

I'm getting this error. I was wondering if it's because I'm using it on the client side of JS, not node.
Thanks

there is no browser support for this lib yet, i can't say when i can add it.


Separate included registration templates for different types/categories of registration

In the template core/base/base_event_registration.html, each type of registration item (special/open/closed series and open/closed events) are rendered in a separate block, but all of the logic of displaying those events is contained within the one template.  To simplify the process of changing how registration looks for different types of events (and to make the template more readable and easier to customize), I would like to split each of the five basic types of listing into its own template, which will then just be included in the base template.  So, for example, the base template for series with open registration will now just read something like:
{# List of Class Series with Open Registration #}

{% block reg_open_series %}
	{% include 'core/registration/reg_open_series.html' %}
{% endblock %}

Since flagged individual event categories (such as practice sessions) will soon be able to have their events show up totally separately from other types of events (per the issue described in the comments in #31 ), it may be desirable to have them displayed using a custom template as well.  So, if a category is flagged to be displayed separately, then the ClassRegistrationView will look for a custom provided template entitled something like 'core/registration/reg_eventcategory_'.html.  If that template exists, then it will be included on the registration page to display events in the category.  If that template does not exist, then the category's events will still be displayed separately, but a generic display template will be loaded for the category instead.  This should permit maximum flexibility in displaying things like weekly practice sessions or other types of recurring events, without having to duplicate or maintain the code behind the rest of the registration process.
As part of this, I will be reorganizing the templates in the core app somewhat.  If you're currently modifying any of these default templates, be advised that you may need to move your files once I push this change.  Trying to get these types of things done sooner than later to avoid breaking peoples' installations.

Done.


Current version fully breaks fzf.vim

Description
👋🏼
First a big thank you for all the work put into this plugin. I've been using is without any issues for a long time and really enjoy it!

Today after running an update my fzf setup (with fzf.vim) became fully broken. It outputs an error like this:
Error detected while processing function fzf#vim#files[15]..<SNR>88_fzf[21]..fzf#run[63]..<SNR>31_execute_term[93]..<SNR>31_dopopd:
line   20:
E716: Key not present in Dictionary: "dir && (!&autochdir || w:fzf_pushd.bufname ==# bufname(''))"

I disabled my plugins one by one and as soon as I removed gitsigns it started to work. It also worked earlier today so the issue must have been introduced during the day.
Neovim version
NVIM v0.6.0-dev+220-gdb695cc4c
Operating system and version
Arch @ 5.13.13
Steps to reproduce

nvim -nu minimal.lua
Run :Files or any other fzf.vim based command.

Expected behavior
fzf.vim should work correctly.
Actual behavior
fzf.vim is fully broken and erroring.
Gitsigns debug messages
No response
Minimal config
vim.cmd [[set runtimepath=$VIMRUNTIME]]
vim.cmd [[set packpath=/tmp/nvim/site]]
local package_root = '/tmp/nvim/site/pack'
local install_path = package_root .. '/packer/start/packer.nvim'

if vim.fn.isdirectory(install_path) == 0 then
    print("Installing Gitsigns and dependencies.")
    vim.fn.system {
        'git', 'clone', '--depth=1',
        'https://github.com/wbthomason/packer.nvim', install_path
    }
end

-- Load plugins
require('packer').startup {
    {
        'wbthomason/packer.nvim',
        {'lewis6991/gitsigns.nvim', requires = {'nvim-lua/plenary.nvim'}},
        -- ADD PLUGINS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
        {'junegunn/fzf', dir = '~/.fzf', run = './install --all'},
        'junegunn/fzf.vim'
    },
    config = {
        package_root = package_root,
        compile_path = install_path .. '/plugin/packer_compiled.lua',
        display = {non_interactive = true}
    }
}

_G.load_config = function()
    require('gitsigns').setup {
        debug_mode = true -- You must add this to enable debug messages
        -- GITSIGNS CONFIG THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE
    }

    -- ADD INIT.LUA SETTINGS THAT ARE _NECESSARY_ FOR REPRODUCING THE ISSUE

    -- ALSO INCLUDE GITSIGNS DEBUG MESSAGES
    vim.cmd('Gitsigns debug_messages')
end

require('packer').sync()

vim.cmd [[autocmd User PackerComplete ++once echo "Ready!" | lua load_config()]]

The problem was introduced with 7e5a748f341eed78a0e548ad6a06bcfaa5d5cfe4.

I can report I too am getting errors when trying to load session files with persistence.nvim. Unrelated but may be helpful:
E5108: Error executing lua ...ack/packer/opt/persistence.nvim/lua/persistence/init.lua:69: Vim(lua):E5108: Error executing lua .../site/pack/packer/opt/gitsigns.nvim/lua/gitsigns/git.lua:194: attempt to yield across C-call boundary

Reverting back to commit daa233a fixes it.

Sorry, there was a bad autocmd added in the commit that added g:gitsigns_head. The fix is simple and will do it as soon as I can.


Dialog does not exist

The document says:
_To test this add-in, try signing in again after setting the Use multi-factor auth property to True in the Deployment section of the Web Add-in project properties dialog.
There is no Deployment section in the WebAdd-in project properties:

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

ID: 930ce4fc-c8b8-f756-f03f-a716f1ef7883
Version Independent ID: 753a2e38-9430-25bb-5409-b7eed9c88e47
Content: Build your first Outlook add-in - Office Add-ins
Content Source: docs/quickstarts/outlook-quickstart.md
Service: outlook
Sub-service: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

Thanks for reporting this issue @crgarcia12.
@samantharamon, could you please investigate?


Add support for HSM/Smart Card/TPM ...

Problem Description
I think mitmproxy is mostly used for analysis of single websites/apps ... and not on  a broader scale like TLS interception for all traffic in an enterprise environment or from a complete device.  Though it would be a valuable alternative for current open source options (which mostly is squid)
In this case you also need to think more about the security of the proxy software itself.
In contrast to some ngfw solution, mitmproxy is dedicated to a single function and it is open source. Which I consider as an advantage.
The most valuable part is the private key of the proxy. When it gets stolen an attacker could read/modify traffic. Due to their capabilities and position in the network such proxies are a preferred target (see for example: https://www.schneier.com/blog/archives/2019/11/the_nsa_warns_o.html )
Ideally the key could be saved on some hardware token so it can only be stolen by physical access.
Various options exist for storing such keys exist like commercial HSMs, yubikey, nitrokey, (v)TPMs ...
Proposal
Does mitmproxy work in combination with a hardware token?
If not could this be added as an optional function?
A hardware token would be preferable like a YubiKey or Nitrokey. Alternatively a software solution like a virtual TPM.

broader scale like TLS interception for all traffic in an enterprise environment

We think that broader scale TLS interception is usually wrong and misguided, and thus it's explicitly a non-goal for the project.

Does mitmproxy work in combination with a hardware token?

If you have something that works with pyOpenSSL/cryptography and know what you are doing, you can probably wire up things in https://github.com/mitmproxy/mitmproxy/blob/main/mitmproxy/addons/tlsconfig.py. I don't really have any other guidance.
As you mentioned, this really is mostly useful for broader scale interception. Which again is nothing we intend to support, so I'm closing this here. :)


function "HammingDistance" haven't been exported.

In readme.md there is a function natural.HammingDistance that use for calculating string distance.
However,I find that such a function haven't been exported in the file lib/natural/index.js.

 Will repair that in a moment.
Hugo


List only Item Titles View

Hi, Another thing I was thinking, that show items always with their details, it consumes a lot of screen space. Why don't offer a view "Only Items" or something alike?
Thanks in advance!

This seems to be covered by #48.


Add option to paste text

Add option for user to paste text directly into the shell, as alternative for specifying path

@makoteq assign this issue to me i will work on it

Hello, is this issue still being worked on? If not, I'm interested to do so.

Go ahead!

Hi, I made a PR. Let me know what you think. : )


[BP-1.9][FLINK-13749][client] Make client respect classloading policy

What is the purpose of the change
Backport FLINK-13749 to 1.9 release branch.
Brief change log

Pass configuration to PackagedProgram and initiate classloading accordingly

Verifying this change
This change added tests and can be verified as follows:

Add integration test to verify classloading orders in program execution

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

cc @aljoscha

Thanks a lot, @link3280!


Twister: Skipping *.cpp files

Describe the bug
When a test is written in a *.cpp file Twister does not scan it for tests if it is in the same directory as the testcase.yaml file. If the cpp file is moved into a /src/ sub-directory then it works as expected. E.g. if the directory layout is:
- test:
    - CMakeLists.txt
    - main.cpp
    - testcase.yaml

Then main.cpp will not get scanned but if the layout is:
- test:
    - src
        - main.cpp
    - CMakeLists.txt
    - testcase.yaml

Then it will get scanned.
To Reproduce
Create a test layout as above.
Expected behavior
I would expect the behavior to be the same when the main.cpp file is in a /src/ sub-directory and when it is not.
Impact
Minor annoyance, creates a skipped test in the test report, the tests in the cpp file are still run and are reported.
Environment:

OS: Linux
Toolchain: Zephyr SDK v0.14.2
Commit SHA: 2ddd73feafd3316af2c547c34d6969bea637d5c6

Additional context
I think it is because this line: https://github.com/zephyrproject-rtos/zephyr/blob/db3f8c16e9c95801961a433c07f481bfcb385466/scripts/pylib/twister/twisterlib.py#L2021 has *.c* whereas this line: https://github.com/zephyrproject-rtos/zephyr/blob/db3f8c16e9c95801961a433c07f481bfcb385466/scripts/pylib/twister/twisterlib.py#L2042 only has *.c

can you submit a PR fixing this please?


Failing mypy tests in users app with django-stubs

What happened?
After installing django-stubs (pip install django-stubs) the typing tests in the users app fail with Name 'settings.AUTH_USER_MODEL' is not defined.
reveal_type(settings.AUTH_USER_MODEL) returns Any which doesn't provide much value. Did this work differently at some stage in the past? If not, an easy fix would be to remove the annotations in the test function signatures.
Furthermore, the type of settings.AUTH_USER_MODEL is str and the user type should be a subclass of a django model. If that is correct, that might be another reason to remove the annotation.
What should've happened instead?
No mypy errors
Steps to reproduce
pip install django-stubs
mypy <project dir>

I don't think it worked differently in the past. We should fix this. PR welcome.


boards: adafruit_feather_m0: don't throw compiler warnings on using custom sercom config

In order to use it's serial peripheral SERCOMs SAD1 requires their pins to be configured with pinmux. Currently that's enabled only for the board default serial interfaces: the USART TX/RX on sercom0, an SPI interface on sercom4, and the USB port. The pinmux code currently is written to throw a compiler error if a user app tries to use any sercom in a way it wasn't pre-defined to be used. The error claims the pin mapping have not been configured but at the same time it doesn't give a chance for this configuration to take place in app code.
I propose that those errors are changed to warnings which would allow users to proceed with compilation and configure the pin mappings themselves should they wish to use sercom1-sercom3.
The relevant file is pinmux.c

What do you think @henrikbrixandersen ?

Sounds like an okay solution to me.


{AKS} Refresh vendored SDK

This checklist is used to make sure that common guidelines for a pull request are followed.
{AKS} Refresh vendored SDK to include changes by PR #25494.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

AKS


Added Code Climate badges

Description

Added Code Climate Badges
Related Issue

Related https://github.com/onebeyond/maintainers/issues/113
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Is there any way to configure the analysis?
Because I see many of the stuff mentioned on it is about unit tests and perhaps we should exclude them from the analysis.

Is there any way to configure the analysis?

Yes, @CesarD.
You can change the rules (with some limitations), here

Also you can manage individual issues status (so you can close or won't fix many of them too). In this View

As well you can disable paths here:

Thanks Ulises!! I'll give it a more proper review later.
Have a nice weekend!


Rename Small_Valley.json to small_valley.json

Rename small_valley to small-valley

Rename small_valley to small-valley

rsomething went wrong on nexdoors side so it was with capital letters but the "code" requested it without capital letters

Rename small_valley to small-valley

rsomething went wrong on nexdoors side so it was with capital letters but the "code" requested it without capital letters

https://github.com/IrisDimensions/overworld/blob/9cbd8daa3a54b9c3e0390fa3e6ae138c41d2a293/regions/hot.json#L8

Rename small_valley to small-valley

rsomething went wrong on nexdoors side so it was with capital letters but the "code" requested it without capital letters

https://github.com/IrisDimensions/overworld/blob/9cbd8daa3a54b9c3e0390fa3e6ae138c41d2a293/regions/hot.json#L8

exactly = Rename Small_Valley.json to small_valley.json

Doesn't Iris distinguish between - and _?

wait a sec that overlooked i the issue was capital letters but thats a issue also

merged with another pr


Can't able to place another elements inside particles component.

I wanna place some components inside particles component. Whatever the elements i add inside particles, not at all displaying.

I have a similar issue. I want to use particle js as my background. I am trying to render a button over it and it does not appear. If I enclose the particle js component and button inside a div tag, they are arranged one below the other.

As stated here (#16), the Particles elements does not accept children due its composition: it is a simple canvas.
You can place components on top of the canvas by declaring its position to be absolute.
Check this example.

Yeah I fixed it by moving particles component to bottom. But my question is, why it's allowing other components placed below this component?

One way to do it example:
<Fragment>
       <Particles         params={particleConf}         style={{ width: '100%', position: 'absolute', zIndex: '-1' }}       />
         <Navigation />

       {children}
   </Fragment>


List of Open Issues on Topic of Information Content Entities

For convenience of discussions to follow, here is a list of open issues in descending numerical order on the topic of ICEs:
#184 Spatial and temporal reference systems are directive – Move spatial and temporal reference systems from subclasses of descriptive information content entity to prescriptive as these systems prescribe how to create a geospatial and temporal points.
#160 Deconflicting IBEs and ICEs – this seems to be a simple change of definitions. Change definition of List from “An Information Bearing Artifact that represents an ordered sequence of values, where the same value may occur more than once.” To “An information bearing artifact that is a carrier of some information content entity that represents an ordered sequence of values, where the same value may occur more than once.”
#149 Does CCO contradict an example-of-usage annotation for object property RO_0000059 (concretizes)? – in the object property annotation a plan is a specifically dependent continuant where in CCO a plan is a generically dependent continuant. Calls for either resolving the conflict or explaining why one doesn’t exist.
#140 Difference between information content entity (IBE) and information content artifact (IBA)? – The intended distinction that IBEs are instances of primitive types and IBAs are compounds is not expressed in the definitions and examples are produced intending to show non-disjoint classes.
#132 Characterizing ICEs, propositions, and images – The use of propositions in the definitions of ICEs is both unnecessary and inconsistent with how ICEs are explained in https://ceur-ws.org/Vol-1515/regular10.pdf
#124 Document context for terms that designate, and other questions – The definition of the designates property should show consideration of the context in which a designator is used and issues regarding some of the subclasses of Designative Information Content Entity
#118 Competency questions for temporal information – Calls for set of competency questions from actual uses of temporal information to help assess how such information is represented in the ontologies. Swartik provided one such set.
#114 Reference Systems and Scales – Asks how to place rating scales within the ICE hierarchy, considers two options cco:ReferenceSystem and cco:PriorityScale, points out some issues with both and how those might be mitigated.

This is a very helpful list. As these more strategic discussion items are being moved to the discussion forum, I am converting this to a discussion now where these items may continue to be tracked.


How to use this package

I'm trying to get Rust booting on iMXRT106x chips and I'm finding it difficult to get it to boot properly.
My current setup includes imxrt-rt, imxrt-ral, and imxrt-hal.
I have some code running on the iMXRT1062, but I dont think the QSPI flash configuration is setup up. Usually I expect to see the QSPI flash configs at 0x60000000, and the IVT at 0x60001000. I do have the IVT visible, but the configs are not.
I've been trying to get these for a few days, and I would really appreciate any help. I was wondering if someone could share a project with minimal stuff thats needed to properly boot and setup the flash.
[dependencies.imxrt-boot-gen]
version = "0.2.0"
features = ["imxrt1060"]

The examples in the imxrt-ral project might be a minimal starting point. There's an example that runs on a Teensy 4 (iMXRT1062). Although there's a Teensy 4 BSP, this example does not use the BSP.

QSPI flash config is provided by the teensy4-fcb crate. That crate uses this boot gen crate, and exposes the config as FLEXSPI_CONFIGURATION_BLOCK. See the linker script to confirm that it's at 0x60000000.
IVT is defined in the linker script, along with the rest of the boot data. IVT is offset from start of flash by 4K (absolute address 0x60001000).
The example uses the cortex-m-rt crate, rather than imxrt-rt. It's XIP, not taking advantage of any TCM regions.

These examples don't use imxrt-hal. But, once you get your system booting with a runtime crate and the RAL, including the HAL is straightforward.

I do have the IVT visible, but the configs are not.

Does this mean you're seeing the IVT in the output binary, but not the config? If the linker is stripping the config, make sure that you have a dummy use or extern crate directive somewhere in your library / binary. See the teensy4-fcb docs for more info, and here for the critical line in the imxrt-ral example. Remove that line, and the example fails to boot.

Hi
Thank you so much for your help. Managed to get it booting :)
Just a quick question. I got the imxrt_hal working on both the IMXRT1062EVK and the IMXRT1064EVK boards. Checking the documentation for the imxrt_hal, it does not mention that it supports the MIMXRT1064 device.
I had to change the BOOT and FLASH addresses in the memory.x file to 0x70000000 and 0x70001400 respectively.
My main work is going to be on the IMXRT1064 device with the built-in flash. Is there any potential issues with the imxrt_hal working on the IMXRT1064 (apart from basic booting)?
I'm new to Rust embedded, but I think once I get a bit of experience I wish to contribute back to the project.
HT

Thanks for working through this!
As long as you're not changing FlexSPI2 pin muxing configurations, the unpublished imxrt1060-hal will work on the 1064. Note that the 1060 HAL is using the imxrt1062 imxrt-ral API, which might seem questionable. But, it'll work for early prototyping.
If you'd like a release of the published, 0.4 imxrt-hal that supports the 1064, open an issue in the HAL project. This commit shows that we should be able to build the published HAL with 1064 support.
The HAL is still figuring out the simplest way to support all of the iMXRT MCUs. Our current thinking is to define an imxrt1064-hal crate, and have one HAL per reference manual. These are all just ideas, and we'd love your feedback and ideas in the HAL's issue tracker.

I had to change the BOOT and FLASH addresses in the memory.x file to 0x70000000 and 0x70001400 respectively.

Are you using the 1064's on-board flash? I'm curious as to how to interface that on-board flash. I can't easily find any NXP docs that say "on-board flash starts at this address." (Since the 1064 RM notes that all FlexSPI2 pin muxing registers are "reserved," I'm guessing that on-board flash is available via FlexSPI2.)

I've continued the discussion here

@bfrog Hi I missed the notification for this and apologies. Yeah I'm more than willing to help. Are you talking about this imxrt-rs/imxrt1060evk-bsp? When I tried to use these, they did not build and I hadn't looked further into it.

Indeed the evk board support crate is pretty far behind the ral and hal at the moment, I need to spend a weekend or two at some point updating them. Really though the 1064 has its own evk and should have a similar board crate like the teensy4-rs crate.


Handle synchronize events on github PRs.

Summary
Handle synchronize events on github PRs.
Change Type

[ ] Bug fix (resolves an issue without affecting existing features)
[X] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[X] Refactoring or test improvements (no bug fixes or new functionality)

Testing
Manual and unit tests.
Review Checklist:

[X] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[X] Included tests that validate the fix or feature.
[X] Checked that related changes are merged.

coverage: 52.819% (+0.004%) from 52.815%
when pulling 79f927de7e33e141a4b247320e6057456fbadc29 on enh/github-webhook-pull-request-synchronize
into 1a5c09ec1677fa8382cc3c355300026a4c4053d5 on main.


Fix typo

lhu takes the same syntax as the other loads, with rd as the first argument. I suspect this was a typo and used the syntax of the store instructions instead

Thanks!


Updating Divya's bio & title

Updating Divya's bio and title to reflect new role.

Note you can also add your languages and project specialties so that you get listed accurately in this page: https://www.cncf.io/people/ambassadors/
        "languages":["Spanish","English"],
        "projects":["prometheus","kubernetes","envoy"],


Add Conditional attribute to LogDebug and LogTrace

LogDebug and LogTrace should be decorated with Conditional attribute and tied with defined DEBUG & TRACE in order to not evaluate expensive objects on production.
Reproduce steps
project.json
{
  "buildOptions": {
    "emitEntryPoint": true,
    "debugType": "portable",
    "define": [ ]
  }
}

appsettings.json
  "Logging": {
    "IncludeScopes": true,
    "LogLevel": {
      "Default": "Information",
      "System": "Error",
      "Microsoft": "Error"
    }
  }

AddressRepository.cs
_logger.LogDebug(JsonConvert.SerializeObject(address));
_logger.LogTrace(JsonConvert.SerializeObject(address));

Actual result
Evaluates JsonConvert.SerializeObject(address)
Expected result
It should not evaluate JsonConvert.SerializeObject(address) unless DEBUG and/or TRACE is set on appsettings.json.

Calling _logger.LogDebug(JsonConvert.SerializeObject(address)) will always evaluate JsonConvert.SerializeObject(address) if you don't want it to evaluate if DEBUG or TRACE isn't set then you need to wrap it in a call to if (_logger.IsEnabled(LogLevel.Debug))

if you don't want it to evaluate if DEBUG or TRACE isn't set then you need to wrap it in a call to if (_logger.IsEnabled(LogLevel.Debug))

I'm not sure if I understood correctly, what other options I have?
All I need is not decorating my code with #if or if stuff for each logging and I would like logging to evaluate those ONLY if proper word defined in project.json

#define DEBUG and LogLevel.Debug represent 2 entirely different concepts.
You can add your custom behavior to your programs by adding extension methods that use the Conditional attribute.

Sure thing both of those concepts have different parts but this doesn't mean that they don't have common area.  Therefore please re-consider to tie LOGGING with DEFINITIONS (not even need to be DEBUG and/or TRACE if you don't want to, simply LOGDEBUG, LOGTRACE, LOGINFORMATION etc. can serve the purpose)
This would give us great benefit of eliminating debug code run on production settings as a native way.
By the way, thank you for mentioning to implement it as extension method.  It solves my need but still I believe native way would have more benefits. 👍

+1 on this, at the very least for LogTrace. For performance-sensitive applications, the overhead of repeatedly checking whether the loglevel is enabled can be unacceptable, adding [Conditional("DEBUG")] would mitigate this in release. This seems to be a pretty standard feature with logging packages (e.g. NLog).

Another option is to add separate methods, i.e. ConditionalLogTrace, ConditionalLogDebug which would be identical to LogTrace, LogDebug apart from having [Conditional("DEBUG") on them.

@roji having separate methods wouldn't be nice.  It must be tied with Conditional attribute in order to be ignorable by compiler.

@cilerler, what I'm proposing is indeed tied with the Conditional attribute, but rather than adding it to the existing LogTrace, LogDebug it would be added to new methods. This would provide programmers with the choice of saying "log this trace message in release" or not, based on whether that call would be too expensive or not.
The problem is that in many cases it makes sense to log some debug- (and even trace-) level messages even in release builds, just not necessarily all debug/trace messages.

My bad, didn't get your point at first time, makes sense. 👍

I have to say I agree with @BrennanConroy. Conflating compile time constructs with the logging system isn't correct. You can already do what you want today just not using extension methods.

@davidfowl (and @BrennanConroy) I don't think anyone's conflating things - I think we fully understand the difference between #define DEBUG and LogLevel.Debug (it's true that it's unfortunate they have the same name).
This is simply about permitting developers to avoid the performance penalty of checking if an event should be logged, for performance-sensitive applications. It makes sense for trace and debug log events to always get logged in debug builds (since performance doesn't matter and we're debugging), but in release the cost may be too high.
Can this be implemented via external wrappers rather than baked into the library? Sure. But then the same question can be asked of extensions methods such as LogDebug(), which could be left out (this is just an absurd example).

This is simply about permitting developers to avoid the performance penalty of checking if an event should be logged, for performance-sensitive applications. It makes sense for trace and debug log events to always get logged in debug builds (since performance doesn't matter and we're debugging), but in release the cost may be too high.

I absolutely disagree. One of the features of the logging system is being able to change the level as the application is running. Compiling away log statements is anti this. I think what you want it's a different function altogether and should not be in the core, at least not yet.

Can this be implemented via external wrappers rather than baked into the library? Sure. But then the same question can be asked of extensions methods such as LogDebug(), which could be left out (this is just an absurd example).

I think it should be, at least to begin with. The bar is higher for things going into the main library. If it turns out people want to compile away their statements as a mainline scenario we can look at it. For now I'd suggest making another library with ConditonalBlah log methods.

I absolutely disagree. One of the features of the logging system is being able to change the level as the application is running. Compiling away log statements is anti this. I think what you want it's a different function altogether and should not be in the core, at least not yet.

Sure, until one starts to remove LogTrace() invocations because these are slowing the application down, even if disabled. You guys have done some pretty amazing performance-oriented work recently, so this shouldn't be a coming out of the blue. I've worked in many scenarios where putting a LogTrace in some hot-path is simply unacceptable, and at the same time it's important to be able to understand what's going on in there, when running a debug build. So you compromise by compiling those specific problematic LogTrace invocations out of your release build.
However, since conditional wrappers for logging can be implemented externally, at least it's possible to leave these out to some external library.

Sure, until one starts to remove LogTrace() invocations because these are slowing the application down, even if disabled.

That's why you use the IsEnabled check. We do this ourselves in hot paths. That's why it should always be there, just switched off until necessary. Having it compiled away takes away some usefulness. There might be scenarios where that's warranted but it's not the mainline use case.

Sure, until one starts to remove LogTrace() invocations because these are slowing the application down, even if disabled.

That's why you use the IsEnabled check. We do this ourselves in hot paths. That's why it should always be there, just switched off until necessary. Having it compiled away takes away some usefulness. There might be scenarios where that's warranted but it's not the mainline use case.

As I wrote above, the whole point here is that calling IsEnabled is too much of a performance hit in certain scenarios. Is this something that happens in mainstream code? No. But if you're trying to make .NET a high-performance platform, then these things matter.
Again, I find it really fine to say that this kind of performance-sensitive app is very rare, and therefore this feature doesn't belong in the main library (especially since it can be implemented outside). But it's important to acknowledge that scenarios that warrant this do exist.

As I wrote above, the whole point here is that calling IsEnabled is too much of a performance hit in certain scenarios. Is this something that happens in mainstream code? No. But if you're trying to make .NET a high-performance platform, then these things matter.

Show me the numbers.

In, say, a low-latency algo-trading application, whatever the cost of branching on whether logging is enabled or not, that's one branch that can and should be eliminated. And that's regardless of much that check actually costs.

I personally use the same construct as provided by NLog, i.e. ConditionalDebug() and ConditionalTrace() for exactly the same reasons.
We have some very high perf code, including code-generated code that we lace with these variants of NLog code, and we teach developers to always carefully think when calling a logging function about "where" they are in the code:

if this is a tight loop / high sensitivity code, they should always use ConditionalXXX()
if not, use the regular variant.

The effects of these logging functions/constructs are multi-fold:

JIT'd code size
Inlining
Readability (ConditionalXXX() being more readable than if (Log.IsDebugEnabled) Log.Debug() in NLOG-ish)

Another niche side-effect is that VS/R# know how to mark the ConditionalXXX() statements as inactive when the selected configuration is Release/Debug, which makes reviewing code a more pleasant procedure.
In theory there's no-one/nothing limiting me from making these as extension methods and putting the `[Conditional()]' attribute on my own extensions, but I fail to see the big deal with providing this for ALL users to be able to benefit from if they wish to do so.

We are closing this issue because no further action is planned for this issue. If you still have any issues or questions, please log a new issue with any additional details that you have.


Bugfix/fix welcome buffer layer

This PR will fix #1413 and #1459 it uses the handle input method on the buffer layers to define a custom input handler for the welcome layer which is fairly simple i.e. j and k for navigation and <enter> to select, this PR also adds a method to the oni api called getActiveSection which returns a string representing the active section of the editor e.g. the particular sidebar element or the menu or commandline
Outstanding

[x] Hide cursor when welcome is active
[x] Fix welcome commands (some...)
[x] Allow enter key passthrough
[x] Add tests

~add sessions to welcome screen~ leave for another PR

@CrossR @TalAmuyal I've finished development on this would love it if you could review, atm I've left the sessions out for now since its already turned out fairly large (PRwise I mean) there are a couple of buttons that don't work largely because I wasn't sure what @bryphe had in mind re what those buttons should do but I didnt want to remove them either since we'd likely end up forgetting to implement them


refactor: use new file format

This is a work in progress

this will be revisited later once @zyrouge is done updating yasumu schema language


[MINOR] QuorumController tests use testToImage

Tests that records generated from existing QuorumController tests will generate the same final image regardless of how they are batched in replay.
Builds on top of https://github.com/apache/kafka/pull/13724
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

None of the failed tests are from the affected file QuorumControllerTest.java, so the test failures are unrelated.  Merging to trunk.


HTTP: Gatling shouldn't resolve remote address when connecting through a proxy

After upgrading to Gatling 3.0.0 doesn't seem to work with our proxy. I am trying to access our pre production environment, an external web page that can only be accessed from a small number of IP addresses (like our proxy). This did work in 2.3.1 but stopped working after i upgraded.
I have already tried to clear my DNS cache but this didn't resolve the issue.
StackTrace:
java.net.UnknownHostException: "https://customer-pre-production.company.com/Application/Logon"
	at java.net.InetAddress.getAllByName0(InetAddress.java:1280)
	at java.net.InetAddress.getAllByName(InetAddress.java:1192)
	at java.net.InetAddress.getAllByName(InetAddress.java:1126)
	at io.gatling.http.resolver.ShuffleJdkNameResolver.doResolveAll(ShuffleJdkNameResolver.scala:33)
	at io.netty.resolver.SimpleNameResolver.resolveAll(SimpleNameResolver.java:81)
	at io.gatling.http.cache.DnsCacheSupport$$anon$1.resolveAll(DnsCacheSupport.scala:124)
	at io.gatling.http.client.impl.DefaultHttpClient.resolveRemoteAddresses(DefaultHttpClient.java:441)
	at io.gatling.http.client.impl.DefaultHttpClient.sendTx(DefaultHttpClient.java:338)
	at io.gatling.http.client.impl.DefaultHttpClient.lambda$sendRequest$0(DefaultHttpClient.java:247)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:462)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:897)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.lang.Thread.run(Thread.java:748)

Http configuration:
val httpProtocol: HttpProtocolBuilder = http
       .baseURL(Properties.intranetURL)
       .warmUp(Properties.intranetURL)
       .inferHtmlResources(BlackList(Properties.blackList), WhiteList())
       .proxy(Proxy("proxy.company.local", 3128).httpsPort(3128))
       .noProxyFor("test325.company.local", "test078.company.local", "localhost")
       .acceptHeader("application/json, text/javascript, */*; q=0.01")
       .maxConnectionsPerHostLikeIE7
       .acceptEncodingHeader("gzip, deflate")
       .acceptLanguageHeader("en-US,en;q=0.5")
       .userAgentHeader("Gatling/3.0.0")

Thanks for reporting!

@slandelle Can you give any indication when version 3.0.1 will be released?

Most likely second half of November

The error still occurs but with a slightly different stacktrace
java.net.UnknownHostException: customer-pre-production.company.com
	at java.net.InetAddress.getAllByName0(InetAddress.java:1280)
	at java.net.InetAddress.getAllByName(InetAddress.java:1192)
	at java.net.InetAddress.getAllByName(InetAddress.java:1126)
	at java.net.InetAddress.getByName(InetAddress.java:1076)
	at io.netty.util.internal.SocketUtils$8.run(SocketUtils.java:146)
	at io.netty.util.internal.SocketUtils$8.run(SocketUtils.java:143)
	at java.security.AccessController.doPrivileged(Native Method)
	at io.netty.util.internal.SocketUtils.addressByName(SocketUtils.java:143)
	at io.netty.resolver.DefaultNameResolver.doResolve(DefaultNameResolver.java:43)
	at io.netty.resolver.SimpleNameResolver.resolve(SimpleNameResolver.java:63)
	at io.netty.resolver.SimpleNameResolver.resolve(SimpleNameResolver.java:55)
	at io.netty.resolver.InetSocketAddressResolver.doResolve(InetSocketAddressResolver.java:57)
	at io.netty.resolver.InetSocketAddressResolver.doResolve(InetSocketAddressResolver.java:32)
	at io.netty.resolver.AbstractAddressResolver.resolve(AbstractAddressResolver.java:108)
	at io.netty.bootstrap.Bootstrap.doResolveAndConnect0(Bootstrap.java:208)
	at io.netty.bootstrap.Bootstrap.doResolveAndConnect(Bootstrap.java:170)
	at io.netty.bootstrap.Bootstrap.connect(Bootstrap.java:156)
	at io.gatling.http.client.impl.DefaultHttpClient.openNewChannelRec(DefaultHttpClient.java:602)
	at io.gatling.http.client.impl.DefaultHttpClient.openNewChannel(DefaultHttpClient.java:576)
	at io.gatling.http.client.impl.DefaultHttpClient.sendTxWithNewChannel(DefaultHttpClient.java:480)
	at io.gatling.http.client.impl.DefaultHttpClient.lambda$sendTx$2(DefaultHttpClient.java:363)
	at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:511)
	at io.netty.util.concurrent.DefaultPromise.notifyListenerWithStackOverFlowProtection(DefaultPromise.java:454)
	at io.netty.util.concurrent.DefaultPromise.notifyListener(DefaultPromise.java:413)
	at io.netty.util.concurrent.CompleteFuture.addListener(CompleteFuture.java:49)
	at io.gatling.http.client.impl.DefaultHttpClient.sendTx(DefaultHttpClient.java:345)
	at io.gatling.http.client.impl.DefaultHttpClient.lambda$sendRequest$0(DefaultHttpClient.java:250)
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163)
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404)
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:466)
	at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:897)
	at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
	at java.lang.Thread.run(Thread.java:748)

@scramados Sorry, I can't reproduce and Gatling works as expected on my side. I suspect the problem is on your side as
at io.netty.bootstrap.Bootstrap.connect(Bootstrap.java:156)
at io.gatling.http.client.impl.DefaultHttpClient.openNewChannelRec(DefaultHttpClient.java:602)

means you're trying to open a connection directly to customer-pre-production.company.com instead of your proxy.

The same code works in version 2.3.1. The only changes made are the ones mentioned in the migration notes.
When adding a breakpoint  to the mentioned code the proxyServer object is filled with the proper configuration.
It looks like it doesn't work for https because when i change the url from https to http i am able to reach the server and retrieve a 404 response.
My current proxy configuraiton is Proxy("proxy2.dev.local", 3128).httpsPort(3128)
@slandelle if necessary i could setup a call so i can share my screen

Sadly, the issue is in Netty: https://github.com/netty/netty/issues/8589

Note: what I actually fixed in 3.0.1 was proxy connection over plain HTTP. The issue is still there over HTTPS as the mechanism is different.

@mailtoshrb compared to 3.0.1, <IP_ADDRESS> only contains one single: logback not shipped in the bundle.
The fix for this issue will be shipped in 3.0.2.
Then, your stacktrace shows you’re using Gatling 2, not Gatling 3. We no longer use org.asynchttpclient.

@slandelle Thanks for the update, we installed both old and new versions in the same server and somewhere it was referencing to old version so seen above exceptionsc(resolved it now). We have workaround for now for proxy redirection and will wait until gatling 3.0.2 release,  it would be great if you throw some light when this new version will be out?

it would be great if you throw some light when this new version will be out?

Most likely mid-December


Redesign the FRI remainder verification procedure

The current implementations of ext2fri::verify_remainder_32 and ext2fri::verify_remainder_64 are inefficient in that the hashing that is used for loading the remainder codeword and remainder polynomials is the same that is used for generating the challenge $\tau$ in the aforementioned procedures. Thus we can save a few cycles by rectifying this.

Closed by #947


Remove duplicated callings set() from SceneTreeDock

Fixes https://github.com/godotengine/godot/issues/77866
SceneTreeDock modifies the value of NodePath when there is a change in the tree, but it duplicates a direct set() call, even though the modification is executed in the UndoRedo::add_do_property() method.
This duplicated calling is problematic because it indicates an invalid NodePath, since it is actually called before the Node path change is complete. This is also problematic because unlike applying internal properties it calls the actual setter. Basically, setters should not be called if NodePath points to the same thing.
For example, when setting the ExetrnalSkeleton in BoneAttachment, the ObjectID of the Node is cached, but it does not indicate the correct Node at the time of the first call when the BoneAttachment change the nest in the SceneTree, then the error is caused. (But the UndoRedo::add_do_property() is fired immediately after the first call, so the error is resolved immediately afterwards).
This PR remove these unneeded callings set().

Thanks!


fix(@angular-devkit/core): transform path using getSystemPath for NodeJsAsyncHost's exists method

Getting therw

Thanks for your contribution.
LGTM, can you please fix the commit message to the below?
fix(@angular-devkit/core): transform path using getSystemPath for NodeJsAsyncHost's `exists` method

resubmitted！

Did CI run @angular-devkit/core 's unit tests? I added a problematic test case, but it passed.
I don't know how to run the test locally for @angular-devkit/core, have any related documents？

Did CI run unit tests for @angular-devkit/core , I added a problematic test case, but is passed.
I don't know how to run the test locally only for @angular-devkit/core, have any related documents?

Before, write operation did not succeed.
 it('should get correct result for exists', async () => {
    let isExists = await host.exists(normalize('not-found')).toPromise();
    expect(isExists).toBe(false);
    host.write(normalize('not-found'), virtualFs.stringToFileBuffer('content'));
    isExists = await host.exists(normalize('not-found')).toPromise();
    expect(isExists).toBe(true);
  });

After
 it('should get correct result for exists', async () => {
    let isExists = await host.exists(normalize('not-found')).toPromise();
    expect(isExists).toBe(false);
    await host.write(normalize('not-found'), virtualFs.stringToFileBuffer('content')).toPromise();
    isExists = await host.exists(normalize('not-found')).toPromise();
    expect(isExists).toBe(true);
  });

I resubmit a PR use a feature branch replace with this, see https://github.com/angular/angular-cli/pull/21005
Closed this PR.


Store.hasChanged being called excessively

Probably a question for @jhollingworth to answer, although would appreciate any other input from the rest of @martyjs/core. I believe fetch is making excessive calls to Store.hasChanged, especially when it comes to handling fetch dependencies. It seems that after a fetch resolves, no matter what happens, a store update is triggered which causes all dependent containers to re-fetch and all subsequent components to re-render.
Maybe my understanding of how fetch is working internally is flawed, but to me it doesn't make sense that a fetch directly triggers a store change. Surely a change should only be triggered if the store has actually been mutated?
Furthermore I don't understand why a fetch using dependsOn triggers yet another fetch - surely this one is completely pointless, because the call above to store.fetch(options) will result in one being done anyway?
This behaviour was brought to my attention by large parts of my app being re-rendered 8 times on load when only 3 queries (and ultimately 3 calls to store.replaceState) were called. I know React and Flux are designed to support regular re-rendering, but this just seems a little wasteful?

I've noticed the same thing. It's a little tricky, though. What's happening is:

Fetch triggered by container.
Local fetch fails.
Remote fetch triggered, fetch marked as "in progress".
Remote fetch succeeds and dispatches action.
Store picks up dispatched action, marks itself as having changed.
Fetch triggered by container, sees that fetch is in progress and returns pending.
Success continuation on remote fetch invoked, fetch marked as "finished"
Something has to make the container re-render with the now-present fetch results.

Within this setup, unless you can somehow get the fetch to be marked as no longer being "in progress" before the dispatched action gets picked up by the store, it's not clear how you'd get around the extra store update.

Ah I think I understand it better now - can see why fetches need to trigger changes. Guess there isn't any way to solve this without completely refactoring how fetches work internally

I'm going to close this for now. Please re-open if you've got more thoughts on the matter


fix: move restore credentials into SEA User prototype object

Description
add restoring of credentials as SEA User function, so all changes are made to internal class variables

@sirpy I didn't create new PR for the react-native branch as there are many conflicts for the UserStorageClass file and I don't know what changes we need or do not need.


Could not detect the Python executable based on npm config ls

I am on Windows, and I have Python 3 in the command line for general Python programming.
$ python --version
Python 3.5.1 :: Continuum Analytics, Inc.

To enable node-gyp, I use windows-build-tools to install Python 2 and configure npm as desired:
$ npm config ls
scope = ""
user-agent = "npm/4.3.0 node/v6.3.1 win32 x64"

msvs_version = "2015"
python = "C:\\Users\\username\\.windows-build-tools\\python27\\python.exe"

prefix = "C:\\Users\\username\\AppData\\Roaming\\npm"

I still get the following error while running electron-rebuild because electron-rebuild could not find the correct Python 2 based on npm config ls:
$ npm install zerorpc # the package I could not bind to electron
$ npm install electron electron-rebuild

$ ./node_modules/.bin/electron-rebuild
× Rebuild Failed
An unhandled error occurred inside electron-rebuild
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "C:\Anaconda3\python.EXE", you can set the PYTHON env variable.
...

Expected result: no errors, and the package could detect the Python 2 executable properly.

Same problem here!

It is not compatible with python 3.x.x . Try to install ^2.7.x (the lest one).

Same problem with python 3.5.2.
Rebuild completed after installing python 2.7.14 and updating the PYTHON environment variable.

Don't know why this stayed open so long :laughing:
But yeah, python 3.x doesn't work with node-gyp, you need python 2.x as people in this thread have already determined

For people who have the latest version of python, the error message doesn't help much. It should tell that there is no python, or its version is not compatible.


[Help] Hitmarker

anyone know where is the location of that 4 files?
"effects/dronecam",
"effects/underwater_overlay",
"effects/healthboost",
"effects/dangerzone_screen"

In game files, in pak files to be more exact. To access them open pak01_dir in GCFscape and search for folder "effects"

In game files, in pak files to be more exact. To access them open pak01_dir in GCFscape and search for folder "effects"

thanks my friend.


Segmentation fault when reloading waybar with pkill -SIGUSR2 waybar

Doesn't happen every time, has a chance to properly reload. But fails most of the time.

Seems to be related to #1749

can confirm I also experience the same.

Some clarification: seems to happen only with tray module

Seems to be fixed? Running latest commit, no issues here

Can't reproduce original crash, although a similar crash happens on latest commit:
GLib-GIO:ERROR:../glib/gio/gapplicationimpl-dbus.c:837:g_application_impl_command_line: assertion failed: (object_id != 0)
Bail out! GLib-GIO:ERROR:../glib/gio/gapplicationimpl-dbus.c:837:g_application_impl_command_line: assertion failed: (object_id != 0)
zsh: IOT instruction (core dumped)  waybar -c .config/waybar/hyprland.jsonc

I think it happens much more frequently if you're running multiple bars, not sure

Happens only when I run a second bar.


Install Trouble

I have prepared the SD card as indicated in the README. Format FAT32. Extract the release to the root of the card, modify config.inc.
The instructions are slightly less clear on what to do next. I've tried the following.

With the camera powered on, just insert the card and wait. Nothing happens.

With the camera off, insert the card. Then power the camera. Firmware does not get installed.

With the camera off, insert the card. Then hold "RESET" while powering the camera until the LED changes colors. After a very long time, this resulted in the "Installation complete. Remove SD Card" message.

If step 3 is the correct procedure, the README should be updated to reflect that.
Continuing from 3, the instructions say to remove the card. I removed it, but was unable to connect via telnet. So then I restarted the camera, and I'm still unable to connect.

I tried several more things and didn't keep track. I was running a watch on my NFS directory waiting for the camera to create a directory. But, somewhere in all of that, telnet started working.
NFS doesn't appear to be mounting. However, with telnet I'm able to try a few things.
I did this:
cd /tmp/run/wyze_hack/
export NFS_ROOT=`<IP_ADDRESS>:/wyze/`
./mount_nfs.sh

I get this message, which takes 5 seconds or so to produce:
          inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
<IP_ADDRESS>:/wyze/ not mounted, try mounting to /mnt...
mount: mounting <IP_ADDRESS>:/wyze/ on /mnt failed: Permission denied
[/bin/mount -o nolock,rw <IP_ADDRESS>:/wyze/ /mnt] failed, will retry...

Which repeats over and over.
I am able to set THIS_DIR and run install.sh in the same directory. However, it doesn't seem to fix the NFS mounting issue.

I figured this out. It seems that even thought this will connect to an nfs4 server, it doesn't support fsid=0. In other words, you have to provide the full path to the nfs share. For me this meant:
export NFS_ROOT='<IP_ADDRESS>:/srv/nfs/wyze/`

Simply inserting the SD card is enough, you shouldn't need to reset or doing anything unless the camera has a previous version of wyzehacks installed.

also, you want to update the config file with your NFS settings. On device, the latest version config file is located at /params/wyzehacks.cfg. So you can telnet to the device and modify it with vi.


how to use this?

I haven't found any option containing "Js Api" in ankidroid prallel builds..
Is this project abondoned?

This project is not abandoned, it will be updated after scope storage will be finished in AnkiDroid. Because Play Store has not updated AnkiDroid because of scope storage. The addons features will be available soon.

Is there any apk version on github releases that has this?

@krmanik AnkiDroid 2.17 release on google play store now, Is it time to update?

The JS Addons is part idea list for GSoC 2024, if AnkiDroid team gets a good candidate who can continue this feature implementation and idea selected then we may have this feature in next AnkiDroid version.


Markdown: Too greedy italic punctuation

Information

Language: Markdown
Plugins: none

Description
The punctuation of italic text with * and _ will match any number of leading *s and _s.
Scratch and bold have similar issues.
Code snippet
*__foo__* or _**bar**_

I want to mention that this bug is trivial to fix using #1679.
Possible solution:
// Allow only one line break
pattern: /(^|[^\\])([*_])((?:(?:\r?\n|\r)(?!\r?\n|\r)|.)+?)(\2)/,
lookbehind: true,
greedy: true,
groups: {
	$2: 'punctuation',
	$4: 'punctuation',
}

Support for nested styles could be added with $3: Prism.languages.markdown.

Can confirm. The behaviour of PrismJS and GitHub markdown is the same. Both do not implement bold italics as expected:
# Chapter Title

A **bold** sample.

## Section Title

An _italicised_ sample.

### Subsection Title

A **_bold italicised_** sample.

When converted from pandoc to ConTeX, the output resembles: