ENH: change term zero to root in newton

Is your feature request related to a problem? Please describe.
in root finding, we try to find x | f(x) == 0
here, x is sometimes called a root of the function or a zero of the function.
This request is to use the term 'root' instead of the term 'zero' because it's technically confusing that both x and y can be seen as a "zero value"
consider the specific case of documenting the tol argument to the newton method:
https://github.com/scipy/scipy/blob/v1.9.3/scipy/optimize/_zeros_py.py#L94-L370
tol is labeled as "The allowable error of the zero value." but it is applied along the x-axis only, not to the "zero value" along the y-axis
Describe the solution you'd like.
it would be much clearer if scipy sticks to the term "root" to identify x within root-finding algorithms
Describe alternatives you've considered.
you could also actually apply tol to the output variable. in many cases this speeds things up although i don't think it's backwards compatible. it also arguably doesn't solve the root issue 😉  of confusing parameter naming
Additional context (e.g. screenshots, GIFs)
No response

I ran into this naming confusion too in the special module too: the terms roots and zeros are used both.
With regards to the root finders: I see that issue for two root finders and for the cython optimize zeros description:

In special for example:

I would propose to at change zeros to roots in all of the one line descriptions and the section heading in special.

@j-bowhay would you be willing to submit a PR? If you don't mind, I've removed the "good first issue" label because it is not always immediately obvious whether the text is referring to the x or f(x), and this issue is not as simple as replacing all occurrences of the word "zero" with "root".

Yes happy to although cant guarantee I'll get to it before 1.10 branches. With regard to the scope just get optimise done first or both optimise and special?

I'd prefer to review optimize only.

I think it would be best to focus on the consistent use of root in the root-finding functions in optimize.  In other contexts, the use of zero has a long history, and I think it would be more confusing to switch to root.  For example, with Bessel functions, zeros is widely used:

https://en.wikipedia.org/wiki/Bessel_function#Zeros_of_the_Bessel_function
https://mathworld.wolfram.com/BesselFunctionZeros.html
Chapter XV of the classic "A treatise on the theory of Bessel functions" is "The zeros of Bessel functions"

@mdhaber I did another search for zeros that should be roots and couldn't fine any so I think this is done

Ok, thanks!


Style update v1

DONE
This project is ongoing and incomplete
This PR updates the style for the US event conference by applying vanilla style and making the site responsive.
Pages that are ready for QA and design review are:

Overview (homepage)
Registration (landing page/form/completed form page)
Contribution list (landing page)
Call for abstracts (landing page)
Side navigation (visible on all pages)
Scientific programme

Checkboxes on the survey form look broken:

@petesfrench have you addressed these comments from Scott?

Checkboxes on the survey form look broken:

This is being addressed in another issue

@petesfrench have you addressed these comments from Scott?

Hey @carkod, yes I just push my changes

I am merging this and associated PR's and will create a separate issue to address design changes. This will allow easier reviews of future PR's that branch off of this branch. And will collect all the design changes into one PR.


Cythonize trace object boundaries fixing multi-label tracing issue

Created cython version of trace object boundaries, and tested it on plugin_tests/segmentation_label_test.
This version solves the multi-label tracing problem which occurs when a boundary tracing algorithm performs without any restrictions (e.g. without padding for each label box).

@slee172 The membrane stuff is included in this. Can you please make a PR of just the fix to trace_object_boundaries?
We will do the membrane detection stuff from the other PR you have.

This PR is closed because it includes the other branch commits.


Iss87 test perf

Pull Request Test Coverage Report for Build 495

0 of 0   changed or added relevant lines in 0 files are covered.
335 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-3.8%) to 74.566%

Files with Coverage Reduction
New Missed Lines
%

src/server/common/AutoTestRoutes.ts
9
93.08%

src/controllers/CourseController.ts
20
86.19%

src/controllers/340/AssignmentController.ts
114
72.76%

src/controllers/GitHubActions.ts
192
57.25%

Totals

Change from base Build 488:
-3.8%

Covered Lines:
3110

Relevant Lines:
4152

💛  - Coveralls

Fixed. In the end this ended up being a hybrid setup where most savings come from using a TestGitHubActions class for everything except CourseControllerSpec, GitHubActionSpec, and GitHubControllerSpec. In the end this took the local test execution time from ~8-12 minutes down to 20 seconds. Still slow on CI though as it runs everything there.


Add string properties for IfStartsWith and IfNotStartsWith

@mantinband Completed with Test
I updated the version in Throw.csproj from 1.1.2 to 1.1.3
I suggest this should be merged after Issue #22 (IfEndsWith) since they are similar I think they should be bundled together in a new build (1.1.3)

Codecov Report

Merging #27 (86a53be) into main (3f0c393) will decrease coverage by 0.03%.
The diff coverage is 92.85%.

@@            Coverage Diff             @@
##             main      #27      +/-   ##
==========================================
- Coverage   93.70%   93.67%   -0.04%
==========================================
  Files          28       28
  Lines         763      791      +28
==========================================
+ Hits          715      741      +26
- Misses         48       50       +2

Impacted Files
Coverage Δ

src/Validators/Validator.Strings.cs
83.33% <83.33%> (ø)

...tensions/ValidatableExtensions.StringProperties.cs
100.00% <100.00%> (ø)

...datableExtensions/ValidatableExtensions.Strings.cs
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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

Looks good 🔥


Sigh fails to register Development & AdHoc profile

Version : sigh 0.10.7
Command line tools installed : :+1:
Command output :
daneo$  sigh --adhoc --app_identifier 'be.company.poc.staging'
[11:01:50]: Starting login with user<EMAIL_ADDRESS>[11:01:52]: Successfully logged in
[11:01:52]: Fetching profiles...
[11:01:54]: No existing profiles, creating a new one for you
[11:01:57]: Creating new provisioning profile for 'be.company.poc.staging' with name 'be.company.poc.staging AdHoc'
/Library/Ruby/Gems/2.0.0/gems/json-1.8.3/lib/json/common.rb:155:in `parse': 757: unexpected token at 'HTTP 400 Bad Request' (Faraday::ParsingError)
	from /Library/Ruby/Gems/2.0.0/gems/json-1.8.3/lib/json/common.rb:155:in `parse'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response/parse_json.rb:11:in `block in <class:ParseJson>'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:48:in `parse'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:39:in `process_response'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:32:in `block in call'
	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.1/lib/faraday/response.rb:57:in `on_complete'
	from /Library/Ruby/Gems/2.0.0/gems/faraday_middleware-0.10.0/lib/faraday_middleware/response_middleware.rb:30:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.1/lib/faraday/rack_builder.rb:139:in `build_response'
	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.1/lib/faraday/connection.rb:377:in `run_request'
	from /Library/Ruby/Gems/2.0.0/gems/faraday-0.9.1/lib/faraday/connection.rb:177:in `post'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.6.1/lib/spaceship/client.rb:228:in `block in send_request'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.6.1/lib/spaceship/client.rb:160:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.6.1/lib/spaceship/client.rb:160:in `with_retry'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.6.1/lib/spaceship/client.rb:227:in `send_request'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.6.1/lib/spaceship/client.rb:203:in `request'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.6.1/lib/spaceship/portal/portal_client.rb:314:in `create_provisioning_profile!'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.6.1/lib/spaceship/portal/provisioning_profile.rb:221:in `block in create!'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.6.1/lib/spaceship/client.rb:160:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.6.1/lib/spaceship/client.rb:160:in `with_retry'
	from /Library/Ruby/Gems/2.0.0/gems/spaceship-0.6.1/lib/spaceship/portal/provisioning_profile.rb:220:in `create!'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.10.7/lib/sigh/runner.rb:95:in `create_profile!'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.10.7/lib/sigh/runner.rb:34:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.10.7/lib/sigh/manager.rb:7:in `start'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.10.7/bin/sigh:34:in `block (2 levels) in run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:68:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.10.7/bin/sigh:86:in `run'
	from /Library/Ruby/Gems/2.0.0/gems/sigh-0.10.7/bin/sigh:93:in `<top (required)>'
	from /usr/bin/sigh:23:in `load'
	from /usr/bin/sigh:23:in `<main>'

Log file :
POST: account/ios/profile/createProvisioningProfile.action {teamId: XXXXXXXXXX}, {provisioningProfileName: be.company.poc.staging AdHoc}, {appIdId: XXXXXXXXXX}, {distributionType: adhoc}, {certificateIds: ["XXXXXXXXXX","XXXXXXXXXX"]}, {deviceIds: ["XXXXXXXXXX"]}

This occurs when creating an Adhoc and a Development Profile, not with an AppStore profile

Could you try running sigh from a different internet connection to see if that's causing the problem?

I have the same issue.

The fact that it runs with an appStore profile, doesn't that tell my connection is ok ?

It is also failing with 400 Bad Request for me too. Properly logged in.

Same here, posted more info on https://github.com/KrauseFx/fastlane/issues/349

Moving further discussion to https://github.com/krausefx/fastlane/issues/349


https://www.facebook.com/mausam.rani.902266

[x] Have you followed the contributing guidelines?
[ ] Have you explained what your changes do, and why they add value to the Guides?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

https://www.facebook.com/mausam.rani.902266

https://www.facebook.com/mausam.rani.902266

https://www.facebook.com/mausam.rani.902266


Nexus Shared Service docs need updating for v2

The Nexus docs listed here - https://microsoft.github.io/AzureTRE/tre-templates/shared-services/nexus/#deploy are not appropriate for the VM based nexus deployment.
They do not cover certificate installation and refer to running setup scripts.

@jjgriff93 are you able to take a look at this? For some reason I thought you had updated the docs (but I might have misremembered that).

@martinpeck apologies for the delay! Yes I had updated it in the Quickstart but not in the template doc. There's a bit of inconsistency where configuration steps were specified for gitea in the Quickstart but not the template docs so I've addressed that in my PR as well as for Nexus


Implementing fzf

Would be great having fzf implemented when user type e.g. chns without any argument. To offer user list of possible options.

Getting list of namespaces require connect to cluster. Let's start with something simple, with e.g. cc

Ok probably depending on FZF is not a good decision. Let's use https://github.com/charmbracelet/bubbletea for list and we don't need to depend on external tool


Ontology header update

This has to be completed by the Editorial Committee

For this pull request, we can postpone the merge after the editorial committee reviews the header in the branch

ontology-header
We can discuss in the group the contents of the header, commit them and then merge.

After Discussion in the editorial committee we postponed this merge.


Warnings to user on install/uninstall for select situations

What this PR does / why we need it

This changes the install script so that if the tanzu cli exists in the PATH (aka is installed), the script will prompt the user to acknowledge that it will be overwritten.
For uninstall, if a management or unmanaged cluster is currently deployed, the script will prompt the user to acknowledge that it will delete access to those systems if you continue.
For both install and uninstall on Linux/Darwin, a silent mode will be available for automation.
Which issue(s) this PR fixes

NA
Describe testing done for PR

Invoked install and uninstall on Linux and Windows to make sure we get the desired behavior.
Special notes for your reviewer

NA

Thanks for putting in some safety rails!

updated based on @jpmcb feedback


Include order of Binders.hpp matters

The include order of "Binders.hpp" matters as it relies on a using statement which is not present in the file itself. It tries using "ComponentContext" but this does not exist in the file and is currently relying on other includes before it to define it.
This manifests itself in a build error when you switch around the include statements order in "ComponentInstanceImpl.hpp".

Able to reproduce the issue. Including "ComponentContext.hpp" and adding a using statement removes the dependence on include order as seen in "ComponentInstanceImpl.hpp"


When set height of camera's destination with 0.0,throw a exception in 2d.

link.
run the following code,then select 2d mode,and click button [Zoom]:
At the same time,the height is close to 0 ,the page crashed without exception message(2d).

code:
var viewer = new Cesium.Viewer('cesiumContainer', {
    //sceneMode:Cesium.SceneMode.SCENE2D,
    terrainProvider: Cesium.createWorldTerrain()
});
Sandcastle.addDefaultToolbarButton('Zoom', function() {

    viewer.camera.flyTo({
        destination : Cesium.Cartesian3.fromDegrees(108.5,33.5, 0.0)
    });
});

Thanks for reporting this and for the minimal code example! I think this is an issue of CesiumJS allowing the camera to go beyond what it expects. The error is thrown in OrthographicOffCenterFrustum.js:
https://github.com/AnalyticalGraphicsInc/cesium/blob/b7c1e301291a3916c4cfc30ff6ab8a6103fbf687/Source/Core/OrthographicOffCenterFrustum.js#L120
I think the viewer/camera fly to should prevent this camera from going in this position.


groups: significant UX issues with group creation

Describe the bug
At the moment, groups creation is littered with a lot of small issues that compound into a larger issue of groups creation feeling needlessly baroque/heavy.
Edit: While this isn't a demo path concern, it's still a rather core set of interfaces that we can stand to improve for a v1 release.
In the following video, I attempt to create a group:
https://user-images.githubusercontent.com/1195363/188939772-60ef5350-a206-4aec-8512-1cce18b5083f.mov

At 4 seconds, we already begin to see some issues with the form field design: The insertion point isn't automatically inserted into the "Group Name" field — I should be able to immediately begin typing the moment this field appears
At 0:29 seconds I attempt to create my group after naming it and granting it a description, only to run into a wall — while the interface (barely) makes it clear that setting an avatar is a required action, the fact that an avatar needs to be explicitly provided in order to proceed feels close to a dark pattern, or at least a needlessly halting one. The "avatar" field should default to the "Letter" + Color presentation, so that all I need to do to proceed is give my group a name
At 0:35 seconds, when I click into the "Group Icon" field, and click out of it to reset the state  (an expectation), it doesn't work. I need to explicitly press the "X" button to clear the field
At 0:39 seconds, when I finally select the "Choose fill color" option, the default "black" icon color apparently isn't enough to proceed. Even after setting the color of the icon at 0:51, I can't proceed to create my group.
It isn't until 0:59 where I finally realize that I need to edit my group's name in order to proceed — this is almost certainly a bug

It nearly takes a minute for me to simply proceed from setting my group's default information — this is pretty insane, and certainly a blocker in getting people to the result they actually expect. Moving onward:

Selecting a Group's privacy level is pretty straightforward, nothing particularly wrong here
At 1:11 we run into an interface that visually blocks you from proceeding unless you invite people to the group. I think this tertiary "Skip" pattern is an antipattern that detracts from an otherwise straightforward interface.
At 1:20, I'm dumped into a blank "groups" screen, rather than the group I just created

Combined, the above issues make for a creation process that feels more difficult than it needs to be.
There are a few updates to the groups creation flow that are on the cusp of being formalized:
Group Details:

Group Privacy

Invite People

The most dramatic + notable changes pertain to "Group Details", which has the most issues in my assessment, and "Invite People", which could be slightly updated for ergonomic reasons, and to eliminate the "Skip" pattern that feels indirect.
cc @jyng + @marisarow + @nerveharp  — tagging y'all because this is an example of one of the more significant updates we're proposing edits to, that directly maps to demo path delivery. A flow that captures the minutiae of these edits is close to being complete.
Edit: This does not in fact get visited by Galen on the demo path, but it's still a significant part of the Groups interface that could use updating sooner than later, I feel.

Please ensure the following:

State is saved if you click out of the modal
The @ps typed in via dropdown are not duplicated (see #651)


Use the job ID instead of the name when retrieving the WPT results

Currently, we read the label from the result XML coming from the WPT server to assign the measurement job that triggered the result to the result.
This is error-prone and the WPT server does not allow a number of special characters in the label and simply cuts them away. This has already caused results not to be persisted in the OSM on several occasions if we have used special characters in the job name.
We should transfer the ID of the triggering measurement job from the JobRunService (formerly JobProcessingService) via the WptInstructionService (formerly ProxyService) to the JobResultPersisterService (formerly ResultPersisterService). This would eliminate the need for the label from the result-xml to determine to which measurement job the result belongs.

Already done in commit c8bc22d and a14217e?


New session does not initiate auto chat

When clicking new session, page navigates to eciso/{session_id} ; however user expects chat to be auto initiated

Works (mostly): https://github.com/cal-poly-dxhub/aws-genai-llm-chatbot/commit/735c5059ca0a564a325b673194fc2b55ae5c23b2


:star2:  Change UI!

Please watch demo.gif for what did I change, thank u :heart:

Hi Sina and thanks for your great design!😍
Maybe in the future, I will redesign the extension due to some new features but I appreciate your help❤

I've been waiting for your response. Now is the time to merge this pull request!

Hi, sorry for my late respone :_), I couldn't check my email and thank u for your merge! :+1:


ZMQError: Operation cannot be accomplished in current state

Hi,
i followed the installation instructions, however when I try to run the following code:
from pycromanager import Core
core = Core()
i do get the following error:
ZMQError: Operation cannot be accomplished in current state

Doesn't reproduce for me. You may have a port that failed to close from some previous PM activity. Try restarting your computer

Assuming this is now working, and recent changes should make this type of thing less likely to come up in the future


Installation with pip2.7

Thanks! I've made a more minimal edit in 6c05f24a54e907e3edebd51702c9e1f9855daaf6 (sudo is situational and not everyone has Python 3). We should just upgrade this to Python 3 only #19 in the future.


ESRI Leaflet Demo Needs W3C Validation

Can the ESRI Leaflet demo HTML file be updated to pass W3C validation?
Whenever I paste the file into the validator, I get the following errors:

Error: Element div is missing one or more of the following attributes: role.
From line 75, column 4; to line 75, column 76
se -->↩
↩				<
Attributes for element div:
Global attributes

Error: Attribute aria-lablledby not allowed on element ul at this point.
From line 82, column 7; to line 82, column 63
/a>↩
↩
Attributes for element ul:
Global attributes

Error: No space between attributes.
At line 90, column 32
="settingsMenu"class="" role="

Error: The aria-controls attribute must point to an element in the same document.
From line 58, column 5; to line 58, column 149
der">↩				<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#mainNav" aria-expanded="false" aria-controls="navbar">↩

Error: The aria-labelledby attribute must point to an element in the same document.
From line 100, column 2; to line 100, column 101
dow -->↩↩
↩

@pmacMaps thanks. Some of that just didn't make the clean up :) but I'll take a look at this and get it dialed in. Thanks.


reset keyboard also with xdotool

copied the method used in plot_kicad_sch

Looks good, thanks for the improvement.


Consider adding a flag for implicit rest parameter in a block (proc { |a,| })

A block with trailing ,  in a parameters list means a rest parameter similar to explicit declaration |a, *|.
But CRuby behaves a bit differently in this case and a block has different arity:
proc { |a,| }.arity # => 1
proc { |a, *| }.arity # => -2

To support this we need either node locations serialised or explicit flag.

This feels like missing information because there is no reasonable way to implement the compatible semantics without this information (well there is with the location but that seems pretty hacky).
BTW @andrykonchin filed https://bugs.ruby-lang.org/issues/19971 but even if that gets fixed it would only apply for 3.3+, so we'd still need it anyway in Prism.
@kddnewton Do you think this could be added soon?
Otherwise we might need to workaround for now by serializing the RestParameterNode#operator_loc location, i.e. a partial revert of https://github.com/ruby/prism/commit/c82a9dad64882f0698b2a0db4c37896af7ef5f42 with different field marked as semantic_field: true.


[Bug Report] Missing Recommended Icons

Expected Behavior
No warnings should be shown when uploading to TestFlight.
Actual Behavior
ITMS-90892: Missing recommended icon - The bundle does not contain alternate app icon for iPad of exactly '167x167' pixels...

ITMS-90892: Missing recommended icon - The bundle does not contain alternate app icon for iPad of exactly '152x152' pixels...

Steps to Reproduce the Problem

Targeted Device Family: 1,2 i.e. universal
Upload to TestFlight

Specifications

Version: @brandingbrand/code-core: 12.0.1
Platform: react-native 0.71.+
Subsystem: @brandingbrand/code-plugin-app-icon: 1.0.0

Solution / Workaround
Update rules https://github.com/brandingbrand/flagship/blob/main/packages/plugin-app-icon/src/utils/rules/ios.ts to add the 167 and 152 with 2x scaling respective resolutions.

@crherman7 Has this been resolved with v13?

@crherman7 Has this been resolved with v13?

no, this has not been resolved in the app-icon plugin. I will put up a PR for this.

We cover these already:

https://github.com/brandingbrand/flagship/blob/7c88cd6a23c2bb387c03ae3e876f7bf9b543c1be/packages/plugin-app-icon/src/rules.ts#L16
https://github.com/brandingbrand/flagship/blob/7c88cd6a23c2bb387c03ae3e876f7bf9b543c1be/packages/plugin-app-icon/src/rules.ts#L27

the error points to alternate app icons, there are no warnings in xcode and those icons are fulfilled.

xcode


manuallyaddfile() if file not image no preview

This is a fix for manuallyAddFile().
this.$refs.myVueDropzone.manuallyAddFile({
name:"xyz.pdf",size:10000, type:"application/pdf"
},fileurl)
if the type of file is not image then it will not create preview. Right now its showing like :  means it shows image preview for pdf and other non image file.

Hi @kishanmadhesiya
Thanks for the change, however it needs to be made to src/components/vue-dropzone.vue file otherwise your change will get blasted away on the next release. If you could update your pull request that would be appreciated.
Thanks,
Rowan

@kishanmadhesiya Thanks for this great contribution! 👍


Add words addition/deletion

Commit https://github.com/SecondThundeR/secondthunder-js-bot/commit/3bfe16f4ae96d1022018179000bce57692252b51 adds this feature


(ignore me): Investigate the error in e2e sink in the main ci

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Checklist For Contributors
~- [ ] I have written necessary rustdoc comments~
~- [ ] I have added necessary unit tests and integration tests~
~- [ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).~
~- [ ] I have demonstrated that backward compatibility is not broken by breaking changes and created issues to track deprecated features to be removed in the future. (Please refer to the issue)~
~- [ ] All checks passed in ./risedev check (or alias, ./risedev c)~
Checklist For Reviewers

[ ] I have requested macro/micro-benchmarks as this PR can affect performance substantially, and the results are shown.

Documentation
~- [ ] My PR DOES NOT contain user-facing changes.~

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

which part failed?

which part failed?

https://buildkite.com/risingwavelabs/main/builds/3909#0187a7bc-c222-487c-bbac-46bc02de7352


Crashing ("Debug assertion failed! Expression: vector subscript out of range") when removing colony with population of 0.

In the update() function in Simulation, I have a check to see if any colonies have a population of 0 ants. If there are 0 ants, removeColony() is called and the colony is removed from the world, as well as being removed under the hood, from the colonies vectors in Simulation, world, and renderer.
Strangely, it also only appears to happen when using colonies with somewhat large starting populations (>50?). If you try testing with small colony sizes, it may not occur. Additionally, I believe I have only one instance of crashing when using the actual "remove" button in the GUI (compared to crashes happening every single time otherwise).
It seems like it is either a problem with the index_vector.hpp class, or maybe the target field in Ant ...? I have been investigating this problem all day with no luck. I'll make a comment below that goes into greater detail.

In simulation's update() function, I have a check at the very bottom (below checkForFights and updateColoniesStats) that checks to see if any colonies are extinct. It looks like this:
            for (Colony& colony : colonies)             {                 if (colony.eliminated)                     removeColony(colony.id);             }
eliminated is a bool that is triggered when the ant population is equal to zero.
When debugging, I see that the error originates from removeColony(uint8_t colony_id) and occurs in the for loop with c.stopFightsWith(colony_id);`
From there, the next error takes place in the Colony class in the stopFightsWith function, inside of the for loop, at if(a.target) {
Where a.target seems to be the problem. Here is the call stack:

Note that the first four lines have line numbers that should match with yours. Everything below operator bool() Line 359 probably differs from your code.

My thoughts:
I don't think anything I added to your code managed to cause this problem.
I think the problem comes from trying to iterate over the Ants of a colony that no longer exists (was deleted because population was 0).  Maybe there is a problem with Ant.target when the colony is extinct, when there are no ants, or when the colony no longer exists?
In any case, debugging keeps pointing to lines of code involving if (ants.target), even when I try to patch this solution.
Let me know if there is anything I can do to help!
Regards,
Marco

Hello,
Thank you for your detailed analysis, I will look into this


Distribution Proposal: Kubernetes-specific distribution

Description
Many many users run the collector in Kubernetes today and the OpenTelemetry project has encouraged that behavior via the helm charts, operator, and Kubernetes-specific components.  To continue fostering the concept that the Collector is a terrific solution for monitoring Kubernetes I believe we need a more direct approach.
In order to facilitate a good default image for the OpenTelemetry-helm-charts, OpenTelemetry-operator, and any user looking to monitor Kubernetes, I propose that we introduce a new community-supported distribution specifically made for monitoring Kubernetes.  This distribution will provide an alternative to the Contrib distribution, which we do not recommend be used in production, for users who want to use a community supported image vs building their own.
Benefits:

Ease of use for users, especially those getting started.  Not all OTel users also want to manage a build pipeline for the Collector.  In order to build an image for Kubernetes today you must run ocb with your manifest AND include the output in a docker image that you then host somewhere. This image provides a solution for those looking to run the collector to monitor Kubernetes but also don’t want the burden of maintaining a collector build pipeline.
Following our own best practices. Today the Collector and Operator helm charts use the Contrib image by default which enables bad practices if the user chooses to use the chart in production without modification.  The operator uses the Core repo, which is limiting for most users.  A Kubernetes-specific distribution would be in line with our best practices and would not limit users by default
Smaller than Contrib. A Kubernetes-specific distribution should naturally be smaller than Contrib.  This follows our and industry best practices.

Rules for components in the image:
This is only my initial ruleset, I am very interested in the community's opinions and feedback.

Only includes components from Contrib and Core
Only components that are Alpha or higher
All receivers must facilitate the collection of data that is generated by Kubernetes or services running in Kubernetes

Although you could run a collector in Kubernetes to reach out to any endpoint, this image is not targeting that use case.  This image is for monitoring Kubernetes and the processes it runs.

All components must be vendor-neutral. (I don’t see another way to ensure vendor neutrality in a community distribution that does not want to be the Contrib distribution - without this rule we'd have to allow every receiver and exporter in Contrib, at which point this image has no relevance)

Proposed manifest:
Please carefully review this manifest.  I believe I have created it correctly based on the initial rules laid out above, but I may have missed a component or two that meets the criteria.
extensions:
  - gomod: go.opentelemetry.io/collector/extension/zpagesextension v0.79.0
  - gomod: go.opentelemetry.io/collector/extension/ballastextension v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/basicauthextension v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/headerssetterextension v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/healthcheckextension v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/httpforwarder v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/oauth2clientauthextension v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/observer/dockerobserver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/observer/hostobserver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/observer/k8sobserver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/oidcauthextension v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/pprofextension v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/storage v0.79.0
    import: github.com/open-telemetry/opentelemetry-collector-contrib/extension/storage/filestorage

exporters:
  - gomod: go.opentelemetry.io/collector/exporter/loggingexporter v0.79.0
  - gomod: go.opentelemetry.io/collector/exporter/otlpexporter v0.79.0
  - gomod: go.opentelemetry.io/collector/exporter/otlphttpexporter v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusremotewriteexporter v0.79.0

processors:
  - gomod: go.opentelemetry.io/collector/processor/batchprocessor v0.79.0
  - gomod: go.opentelemetry.io/collector/processor/memorylimiterprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/attributesprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/cumulativetodeltaprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/deltatorateprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/groupbyattrsprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/groupbytraceprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/k8sattributesprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/metricstransformprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/probabilisticsamplerprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/redactionprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/resourcedetectionprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/resourceprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/routingprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/servicegraphprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/spanmetricsprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/tailsamplingprocessor v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/transformprocessor v0.79.0

receivers:
  - gomod: go.opentelemetry.io/collector/receiver/otlpreceiver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/dockerstatsreceiver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/filelogreceiver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/fluentforwardreceiver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/hostmetricsreceiver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/httpcheckreceiver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8seventsreceiver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sobjectsreceiver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kubeletstatsreceiver v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/prometheusreceiver v0.79.0

connectors:
  - gomod: go.opentelemetry.io/collector/connector/forwardconnector v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/connector/countconnector v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/connector/servicegraphconnector v0.79.0
  - gomod: github.com/open-telemetry/opentelemetry-collector-contrib/connector/spanmetricsconnector v0.79.0

Additional Info
This topic has come up recently in the Collector SIG, but again in the Operator SIG.  Please see the SIG notes for details.
/cc @open-telemetry/operator-approvers

Although I'm not opposed to a k8s distro, I would like to see further discussions on what distros are officially supported by the community progress before making a decision here. See the otep: https://github.com/open-telemetry/oteps/pull/229

A note for the proposed manifest is that the observer extensions are primarily supported by the receiver creator so it would ideally be included as well.

Thank you for the proposal, @TylerHelmuth. It makes a lot of sense. I would even go one step further and suggest yet another one for sidecars, containing only OTLP receiver/exporter and batching processor. We can talk about that on another issue, though.
I have a few comments/questions about some components.

gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/observer/dockerobserver v0.79.0

I feel ashamed for not knowing this, but does this work on Kubernetes? I was always under the impression that this was for "pure" Docker environments. It would be nice to get a positive confirmation from someone using this with their Collector on Kubernetes.

gomod: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter v0.79.0

I'm curious why Prometheus components were selected but not other open-source solutions we promised compatibility with, like Jaeger and Zipkin. I have good arguments for having a Prometheus receiver while still not having a Jaeger receiver, but not so much for a Prometheus exporter when Jaeger is missing. And even if we can make a case for a Prometheus exporter, I would keep only the remote-write exporter, not this one. My suggestion: remove this one, keep the remote-write exporter, and document why we have this exporter but not Jaeger (because it can ingest OTLP already?) and Zipkin (no active code owners?)

gomod: github.com/open-telemetry/opentelemetry-collector-contrib/processor/tailsamplingprocessor v0.79.0

If you include this, you probably need the load-balancing exporter as well so that users can have a scalable tail-sampling setup.

receivers:

I would include a Jaeger receiver there. While the Jaeger client libraries have been deprecated for some time, some users still have services instrumented with OpenTracing+Jaeger.

One question i have is how the release process can be improved to support N distributions. The goreleaser tooling has already hit disk limits with only the two distros we've currently supporting. This isn't to say we shouldn't do this, but that we'll need to spend some cycles finding ways to split the release process to support this. Maybe this could be a separate issue.
Specifically around the k8s distro, would it make sense for different owners to be listed? I understand the overlap of the groups may be enough to have collector-contrib-approvers as the owners for now, but it may not be the case with future distros (one example is @MovieStoreGuy's suggestion of a lambda distro).

@rmfitzpatrick I don't know much about the receiver creator, but is it useful for monitoring Kubernetes or applications that run on Kubernetes?  If not, I'd opt to remove the observer extensions if the other components don't require them.
@jpkrohling after doing a quick test I think you're right. I have removed the dockerobserverextension and dockerstatsreceiver.
I included all prometheus receiver because it directly related to the rule: "All receivers must facilitate the collection of data that is generated by Kubernetes or services running in Kubernetes".  Looking at the rules now they need some work to clarify which exporters should be included.
As for jaeger and zipkin, I think their inclusion will be based on some of the outcomes of https://github.com/open-telemetry/opentelemetry-collector-releases/issues/360.  Again, I think this could use more rules clarification.  Part of me says they can be included bc the facilitate monitoring applications running in Kubernetes and the other part of me says that OTLP meets that goal so we don't need them.  A big question that https://github.com/open-telemetry/opentelemetry-collector-releases/issues/360 will answer is "do all the distros this community supports need to include support for previous standards?".  Would definitely appreciate some ideas on how to adjust to rules to clearly allow or disallow the receivers and/or exporters.  We may need a specific rule for which receivers the distro allows and which exporters the distro allows.
Good point on the loadbalancingexporter, that definitely facilitates telemetry collection in k8s. I have added it.
@codeboten I added the Release pipeline question to https://github.com/open-telemetry/opentelemetry-collector-releases/issues/360 for now.  I think open-telemetry/collector-contrib-approvers should continue to own everything in the repo to guarantee someone is responsible, but I like the idea of different distributions having other supporting owners.  I can see the opentelemetry-operator-approvers and opentelemetry-helm-approvers helping support this distribution.

Based on the discussion so far there there is definitely a need to touch up the rules.  Here are some ideas popping into my head:

All OSS receivers should be included:  This would allow receivers like jaeger, zipkin, prometheus and opencensus, but I think opens the flood gates too wide.  I would need to check but I think this would include many many more receivers in contrib that are for open source technologies.  In an effort to keep this distribution slim and targeted I feel a rule like this is too broad.

All technologies OTel promised to support will be included [as receivers]: This is entirely dependent on #360.  One possible outcome of that issue is that we decide that we need to keep our support promises in all distros we support.  If that is the case, then we include the related component in this distro.  That support might only be for receivers, but might need to include exporters as well.

the only supported export format is otlp (except the logging exporter): This rule would be easy to maintain and pushes forward the idea that OTLP is "all thats needed", but I imaging would be pretty limiting for many users as prometheus is still a huge part of the k8s ecosystem.

@rmfitzpatrick I don't know much about the receiver creator, but is it useful for monitoring Kubernetes or applications that run on Kubernetes? If not, I'd opt to remove the observer extensions if the other components don't require them.

It's helpful for dynamically instantiating other included receivers based on discovered pod/port/node endpoints as presented by the k8s observer: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/receivercreator#rule-expressions. It operates similarly to the prometheus kubernetes_sd_config but for arbitrary receivers and telemetry types.

Ok, it sounds like it qualifies then.  I've updated the manifest.

the Contrib distribution, which we do not recommend be used in production

@TylerHelmuth can you point to a piece of documentation that mentions this? I searched but couldn't find any.

@astencel-sumo the recommendation can be found here: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib#recommendation

I think we should have only OTLP exporters for the Kubernetes distribution. Pretty much everything out there supports ingesting OTLP already, including Jaeger. I remember seeing an issue on Prometheus' side about adding native OTLP ingestion there as well, so, I believe we won't need a Prometheus exporter for this new distribution.
On the receiver side, I have two ways of seeing this:

There are still quite a few workloads out there instrumented with OpenTracing and Jaeger. Having a Jaeger receiver would help them. I haven't seen that many Zipkin workloads out there, but perhaps I'm just an ecosystem away from them? From this perspective, I would vote for having a Jaeger receiver, alongside Prometheus and OTLP.
"All technologies OTel promised to support will be included [as receivers]" is effectively like the above, except that it includes Zipkin.

Between the two, I prefer the second, as it's more objective than the first.

@jpkrohling I'm good with supporting only exporters that use OTLP and also the logging exporter.
I'm also ok with bullet 2, I have a feeling that's where #360 will go anyways.

When using a DaemonSet to read container logs and kubelet logs, the journald receiver is sometimes needed for the kubelet, as it can run as a systemd service outside of the cluster. Should this be considered? The journald receiver complicates the build due to the required dependencies inside the container image.

I'd say if it is a useful component in k8s then it should be considered for inclusion.  What extra dependencies does it require? I am not aware of anything special our existing Contrib pipeline is doing for this receiver.

I'd say if it is a useful component in k8s then it should be considered for inclusion. What extra dependencies does it require? I am not aware of anything special our existing Contrib pipeline is doing for this receiver.

We (observIQ) install systemd, which provides the required journalctl command and its libraries. The journald receiver runs the journalctl command with os.exec. https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/pkg/stanza/operator/input/journald/journald.go#L87. I have seen others install only the required binary and libraries, instead of the entire systemd package but I cannot find the thread right now.
AFAIK, a native pure Go implementation for reading from the journal does not exist, so dependence on the journalctl command is necessary.

journald support can be implemented with go bindings (see coreos/go-systemd). This is what is used in promtail (see here). systemd libs are still needed and promtail uses FROM debian:bullseye-slim.

The journald dependency problem is a bit complicated. If you include a specific version of the systemd libs in the container image, you can run into compatibility issues if the delta between your version and the host's is large enough. It's safest to mount the libraries from the host, but that requires more work from the user.
In the interest of unblocking this release, I'd suggest including the receiver without the binary dependencies, and moving this discussion to a new issue.


Login broken when browser cache is empty

If there is no browser cache, upon loading the app nothing happens. If an old id and settings are in the cache, a 401 ends up getting returned from the API and then it successfully redirects to login
See screenshot

Can you repro locally? I'm having a tough time getting this to happen.

Ok, was able to reproduce. It only pops if you're not on the login page.


Allow the use of bearer_token or bearer_token_file for MarathonSD authorization

This PR enables service discovery for Marathon with token based authorization.
The token specified in bearer_token or bearer_token_file is sent as request header (Authorization) to Marathon / DC/OS
@fabxc am i pinging the right one with this PR?
Best regards, Michael

Thanks for the review, i will implement your suggestions as soon as possible.

@fabxc Tests are now fixed and your requested changes should now also be covered.
Best regards, Michael

Looks good. Thanks!.
Can you document the addition in https://github.com/prometheus/docs/blob/master/content/docs/operating/configuration.md?

@fabxc Documented with https://github.com/prometheus/docs/pull/676

Thanks.


Replace 'Labs' in menu with link to Mozilla Activate

I haven't tested it, but just make sure that this doesn't break the menu on some resolutions. 'Mozilla Activate' occupies more space than 'Labs'.


Specified languages modification null checking

Cannot delete last language when updating resource
This should hopefully account for that case. Let me know if there is anything missing or irrelevant!

Very succinct and elegant. You'll need to rebase to get back in sync with the base branch


[adp-3489] Instruction to sign via external tools for deposit wallet

[x] Document how to derive respective keys using cardano-addresses
[x] Document how to translate them to cardano-cli
[x] Document how to add witness to the existent cbor tx using the keys and submit tx

Comments

Issue Number
adp-3489

@paweljakubas Has this procedure been tested against the current deposit wallet? Remember the goal is to demonstrate some interoperability capabilities from the wallet so we need to make sure this process is actually possible.


replaced deprecated expiresInMinutes and refactored user controller c…

…reate
Also removed required field for first_name and last_name in user model

:+1: looks great - will merge after passing testing


Why does the outputted script type have a hash?

I noticed on https://demo.backpackforlaravel.com/admin/login that the outputted scripts look like this:

@promatik why is the type="2559f5b228d9cebdf685edf1-text/javascript"? Is this intentional or by mistake?

It seems to me to be a CF thing.

Yes, it looks like CloudFlare is doing some nasty stuff there 😅
It's the Cloud Flare rocket loader who's adding that there;
https://community.cloudflare.com/t/script-tags-type-attribute-hash-prepended/145679

Pfiew! Ok fine thanks guys!


Create a correlation plot comparing scanner height measurements vs manual height measurements

Description
For the November meeting, can someone do the comparison of plot level height distributions calculated from the sensors and the ground truth measurements for height? I know it's not an ideal comparison, but it's a measurement that most of the TERRA teams have to provide in their milestones (e.g. "Demonstrate algorithm predictions are within 20% of ground truth values"). It would be ideal if the REF team could set a standard method for doing this for some of the general phenotypes, like height.

@pless and I will work on this for the annual meeting in November.

@rmgarnett is there anything you need to complete this?

The work is completed. How shall I report the results?

@rmgarnett good question. Having the results (and putting this in a quarterly report) is sufficient to close this issue because it specifically follows from a milestone.  Please put the figure and summary stats here here for quick reference. I'll put the rest of my thoughts in #210 which deals with automation of the height extractor.

correlation analysis.pptx

on the last slide of this pptx, both axes have the same label.  is that
correct?
On Thu, Dec 22, 2016 at 2:22 AM, Roman Garnett<EMAIL_ADDRESS>wrote:

correlation analysis.pptx
https://github.com/terraref/computing-pipeline/files/668205/correlation.analysis.pptx
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/terraref/computing-pipeline/issues/175#issuecomment-268735769,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQHJhF-s8A9XHxSlDGlYI_RNSzB2gaJNks5rKiUegaJpZM4KFV46
.

Fixed.

I don't see the fixed version ...
On Thu, Dec 22, 2016 at 12:04 AM Roman Garnett<EMAIL_ADDRESS>wrote:

Fixed.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/terraref/computing-pipeline/issues/175#issuecomment-268741936,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcX57GNB1wS7XbhBkUKa4s4Otfahs-Wks5rKi8XgaJpZM4KFV46
.

I edited my original comment; the file above contains the modified figure.

Thanks!
On Thu, Dec 22, 2016 at 7:46 AM Roman Garnett<EMAIL_ADDRESS>wrote:

I edited my original comment; the file above contains the modified figure.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/terraref/computing-pipeline/issues/175#issuecomment-268826668,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcX5wIGEpGvTli9LhCm1jGl3CuEeSsgks5rKptGgaJpZM4KFV46
.

@rmgarnett what are your suggestions for dealing with the ground issues? Are these responsible for the poor predictions of plants under 60 cm?

New correlation plot with better ground rejection and discarding bad data:

Things look a lot nicer.


Logging null bugfix

@maxekman Fixes https://github.com/looplab/logspout-logstash/issues/49
The issue was that basically null is valid json and gets interpreted as nil by json.Unmarshal and then a crash occurs. (See #49 for a more detailed explanation of the problem)
This fix just makes sure that if the data is nil we change it to data = make(map[string]interface{}) just like if the data is not valid json.
I have also included a regression test that I think will work. (Unfortunately I can do a go get go install and go build without error... but no files are created? And when I do a go test logstash_test.go I get ./logstash_test.go:58: undefined: LogstashAdapter... do you know what I'm doing wrong? Sorry I have never really worked with go before)

This PR solves the issue as described here: https://github.com/gliderlabs/logspout/issues/274

Thanks.

I'll merge as soon as you report the test as working.

Got the test working (just forgot to update the assertion) 👍
zconnelly13@macbook ~/go/src/logstash $ go test ./
ok  	logstash	0.012s

Once it was working I confirmed that it breaks as expected without the fix in 78c9a9b

Thanks for providing a fix for this!


Update sonar-cloud.yml

:white_check_mark: Build POC-dotnet-Dijkstra 1.0.191 completed (commit https://github.com/GuilhermeStracini/POC-dotnet-Dijkstra/commit/7fcfc7231e by @guibranco)


just merge it?

im genuinely trying to understand, why the piracy check? this aint nintendo, they aint gonna sue you if you remove it.

@DeadlyKitten can you explain please? this is more of a question rather than an actual pr.


decoded boundary blocks have epoch index

In the Byron proxy we store boundary blocks on disk. To open the ImmutableDB we need to give a parser which can figure out the slot number from genesis for a serialized block. In order to switch from the old cardano-sl block decoder to those from this package, I need to be able to decode the epoch index from a boundary block. I don't have a deep understanding of this repository but AFAICT this is a nice improvement: we don't need to give the isEpochZero parameter anymore.

Ah, looks like there are other issues in CI actually, but I'm happy to fix this up!

bors r+

Thanks @ruhatch


convert to unit tests

We are heavily depending on integration tests in docker client related tests, gRPC calls and tests that run gitClone.

Docker client supports custom dialers here. We should use an in memory net.Conn as a return value of dialer and validate our business logic by investigating what kinda api calls been produced. Or simply use WithHTTPClient like this: https://github.com/moby/moby/blob/master/client/client_mock_test.go#L20
gRPC calls can be easily mocked by satisfying it's interfaces. e.g.: https://github.com/ilgooz/mesg-go/blob/master/service_test.go#L183-L219
we can add pre downloaded repositories to our test folder to test gitClone behavior.

includes https://github.com/mesg-foundation/core/issues/274

Update:
use buffconn to create a mock server for gRPC

docker client doesn't provide a mocking server nor interface at this moment. this possibly leaves us directly checking generated api calls like described in the first message of this thread.
see https://github.com/moby/moby/issues/30454

I split git and gRPC related tests to other issues. See https://github.com/mesg-foundation/core/issues/339 and https://github.com/mesg-foundation/core/issues/310.


Core-Feature: Full text search in top bar

As a user
I'd like to search for specific words
in order to find related content

Should the search go like this @roschaefer @datenbrei :
(A bit similar to Google-Search.)

If the search field contains one word (no space) then search this as part of the posts fields you mentioned. ("Part of" means as an example: Search of „world“ also finds „worlds“ etc. in the post.)
If there are more than one words in the search field (separated by space(s)) then search all these words as parts of the posts.
If a phrase (more than one word separated by space(s)) is written in ““ it should be seen as one word.
Priority: As higher the priority score as more further the resulting post shall be in the search list.
Priority 1 (highest score): All the words or the most of them are in the same sequence as in the search field.
Priority 2 (second highest score): As more often the same word is in the post.
Priority X: Any other ideas?

@Tirokk I would say: Let's KISS :kissing_heart: Keep It Simple Stupid. If we can send a word to the backend and get all posts containing this word in the content or title field, this is step 1. We can iterate from there and make the search more complex.

😘 It’s future thinking. At first we KISS and than it can get more complicated. 🤗 ^^


Apply the correct scaling attributes when loading a scenario

Based on: https://github.com/quintel/etengine/pull/903#issuecomment-274823170

Does this work for you? When I visit scenarios/:id (where :id) is a scenario based on a derived dataset, pressing "Open this scenario" sends the dataset scaling data to ETEngine:
{
  "scenario": {
    "scenario_id": 606772,
    "scale": {
      "area_attribute": "number_of_residences",
      "value": 10000.0,
      "base_value": 7449298.0,
      "has_agriculture": null,
      "has_industry": null,
      "has_energy": null
    }
  }
}

Fortunately ETEngine rejects this (although only by chance):
Unpermitted parameters: base_value
Unpermitted parameters: base_value

# and ...

Mysql2::Error - Column 'has_agriculture' cannot be null:
  mysql2 (0.3.21) lib/mysql2/client.rb:80:in `block in query'
  mysql2 (0.3.21) lib/mysql2/client.rb:79:in `query'
  ...

This does not happen when creating a new scenario from the front page.

Yes. This is working for me. Though, I do recognize that error. It means that ETEngine tries to create a ScenarioScaling which it shouldn't do because your area is already derived. But just to be clear:
You go to here:

And than you hit "Open this scenario"?
Also on which branch is your etengine?

Also on which branch is your etengine? (mine is on local-datasets-scaling-of-sliders)

My bad. I had changed back to "local-datasets" earlier today. Works fine with "local-datasets-scaling-of-sliders".


Training animation

Show which neurons are activated during training

can make this more powerful to show topographical changes based on weights


Example scripts

Hello Fernando, great job with this repo. My team and I are looking for something like this for AI research.
However, I'm having trouble setting up this repo as none of the example scripts work. For instance, when running python OpenVirtex1Hy2Sw4Host.py, I get:
2020-03-09 16:57:53,001 [WARNING] vsdnemul.dataplane (29): the namespace directory already exists
2020-03-09 16:57:53,005 [ERROR] vsdnemul.models.node.switch.whitebox (253): 409 Client Error: Conflict ("Conflict. The container name "/sw1" is already in use by container "a49f65414931414b2f0ffde65cb872f6a5488a766d4b7fe72b4d50901be522a8". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:57:53,008 [ERROR] vsdnemul.models.node.switch.whitebox (253): 409 Client Error: Conflict ("Conflict. The container name "/sw2" is already in use by container "a3f2470edf85611d1271fce2b36288eed854640ae650d34a1de2fb9a7db2c772". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:57:53,010 [ERROR] vsdnemul.models.node.host.host (122): 409 Client Error: Conflict ("Conflict. The container name "/h1" is already in use by container "33e5303c7a61178f43ea814d21db2f775dac05d848253e4750e1cd0fd3d56cc5". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:57:53,013 [ERROR] vsdnemul.models.node.host.host (122): 409 Client Error: Conflict ("Conflict. The container name "/h2" is already in use by container "0b77080d6a64ee74be9a8c33d7f783348be7578f6522ce3dad4f371ff1f0b7e1". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:57:53,015 [ERROR] vsdnemul.models.node.host.host (122): 409 Client Error: Conflict ("Conflict. The container name "/h3" is already in use by container "22c99862b2e55e7156dc2943067f6939ef0f722b4dbacf301bd60c7312ec2aca". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:57:53,018 [ERROR] vsdnemul.models.node.host.host (122): 409 Client Error: Conflict ("Conflict. The container name "/h4" is already in use by container "3b105b76000d3290875ac763a9e6331a7a58894934ae70139bcb04954daaa77a". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:57:53,020 [ERROR] vsdnemul.models.node.hypervisor.openvirtex (360): 409 Client Error: Conflict ("Conflict. The container name "/hr1" is already in use by container "2015131cfe9504272d91580f179afd36945c40b8889acb29e6439fc7af7d3069". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:57:53,023 [ERROR] vsdnemul.models.node.controller.onos (111): 409 Client Error: Conflict ("Conflict. The container name "/ctl1" is already in use by container "6eddcf867d8c9dd378bf30d4bab140eb74eb7640a908aed5914a59debc2ab504". You have to remove (or rename) that container to be able to reuse that name.")
Traceback (most recent call last):
  File "OpenVirtex1Hy2Sw4Host.py", line 52, in <module>
    mngt_ctl = "tcp:{ip}:6633".format(ip=ctl.getIpController())
  File "/home/oe18433/code_bases/vsdnemul/vsdnemul/models/node/controller/onos.py", line 83, in getIpController
    return _GetIpController(node=self.getName())
  File "/home/oe18433/code_bases/vsdnemul/vsdnemul/models/node/controller/onos.py", line 38, in _GetIpController
    return iproute.get_interface_addr(ifname="eth0", netns=node)
  File "/home/oe18433/code_bases/vsdnemul/vsdnemul/lib/iproutelib.py", line 343, in get_interface_addr
    return _get_interface_addr(ifname=ifname, netns=netns)
  File "/home/oe18433/code_bases/vsdnemul/vsdnemul/lib/iproutelib.py", line 219, in _get_interface_addr
    return (get_addr() if netns is None else get_ns_addr())
  File "/home/oe18433/code_bases/vsdnemul/vsdnemul/lib/iproutelib.py", line 214, in get_ns_addr
    with NetNS(netns=netns) as ipr:
  File "/home/oe18433/miniconda3/envs/vsdEnv/lib/python3.6/site-packages/pyroute2/netns/nslink.py", line 174, in __init__
    super(NetNS, self).__init__(trnsp_in, trnsp_out)
  File "/home/oe18433/miniconda3/envs/vsdEnv/lib/python3.6/site-packages/pyroute2/iproute/linux.py", line 131, in __init__
    super(RTNL_API, self).__init__(*argv, **kwarg)
  File "/home/oe18433/miniconda3/envs/vsdEnv/lib/python3.6/site-packages/pyroute2/remote/__init__.py", line 225, in __init__
    raise init['error']
PermissionError: [Errno 1] mount rundir failed: 'ctl1'

when running python FlowVisor1Hy2Sw4Host.py, I get:
2020-03-09 16:58:44,442 [WARNING] vsdnemul.dataplane (29): the namespace directory already exists
2020-03-09 16:58:44,446 [ERROR] vsdnemul.models.node.switch.whitebox (253): 409 Client Error: Conflict ("Conflict. The container name "/sw1" is already in use by container "a49f65414931414b2f0ffde65cb872f6a5488a766d4b7fe72b4d50901be522a8". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:58:44,449 [ERROR] vsdnemul.models.node.switch.whitebox (253): 409 Client Error: Conflict ("Conflict. The container name "/sw2" is already in use by container "a3f2470edf85611d1271fce2b36288eed854640ae650d34a1de2fb9a7db2c772". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:58:44,452 [ERROR] vsdnemul.models.node.host.host (122): 409 Client Error: Conflict ("Conflict. The container name "/h1" is already in use by container "33e5303c7a61178f43ea814d21db2f775dac05d848253e4750e1cd0fd3d56cc5". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:58:44,455 [ERROR] vsdnemul.models.node.host.host (122): 409 Client Error: Conflict ("Conflict. The container name "/h2" is already in use by container "0b77080d6a64ee74be9a8c33d7f783348be7578f6522ce3dad4f371ff1f0b7e1". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:58:44,458 [ERROR] vsdnemul.models.node.host.host (122): 409 Client Error: Conflict ("Conflict. The container name "/h3" is already in use by container "22c99862b2e55e7156dc2943067f6939ef0f722b4dbacf301bd60c7312ec2aca". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:58:44,461 [ERROR] vsdnemul.models.node.host.host (122): 409 Client Error: Conflict ("Conflict. The container name "/h4" is already in use by container "3b105b76000d3290875ac763a9e6331a7a58894934ae70139bcb04954daaa77a". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:58:44,463 [ERROR] vsdnemul.models.node.hypervisor.flowvisor (182): 409 Client Error: Conflict ("Conflict. The container name "/hr1" is already in use by container "2015131cfe9504272d91580f179afd36945c40b8889acb29e6439fc7af7d3069". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:58:44,466 [ERROR] vsdnemul.models.node.controller.onos (111): 409 Client Error: Conflict ("Conflict. The container name "/ctl1" is already in use by container "6eddcf867d8c9dd378bf30d4bab140eb74eb7640a908aed5914a59debc2ab504". You have to remove (or rename) that container to be able to reuse that name.")
2020-03-09 16:58:44,467 [ERROR] vsdnemul.lib.iproutelib (286): None
2020-03-09 16:58:44,467 [ERROR] vsdnemul.models.link.linkpair (70): 'NoneType' object is not iterable
2020-03-09 16:58:44,468 [ERROR] vsdnemul.lib.iproutelib (286): None
2020-03-09 16:58:44,468 [ERROR] vsdnemul.models.link.linkpair (70): 'NoneType' object is not iterable
2020-03-09 16:58:44,469 [ERROR] vsdnemul.lib.iproutelib (286): None
2020-03-09 16:58:44,469 [ERROR] vsdnemul.models.link.linkpair (70): 'NoneType' object is not iterable
2020-03-09 16:58:44,469 [ERROR] vsdnemul.lib.iproutelib (286): None
2020-03-09 16:58:44,469 [ERROR] vsdnemul.models.link.linkpair (70): 'NoneType' object is not iterable
2020-03-09 16:58:44,470 [ERROR] vsdnemul.lib.iproutelib (286): None
2020-03-09 16:58:44,470 [ERROR] vsdnemul.models.link.linkpair (70): 'NoneType' object is not iterable
Traceback (most recent call last):
  File "FlowVisor1Hy2Sw4Host.py", line 65, in <module>
    mngt_ctl = "tcp:{ip}:6653".format(ip=ctl.getIpController())
  File "/home/oe18433/code_bases/vsdnemul/vsdnemul/models/node/controller/onos.py", line 83, in getIpController
    return _GetIpController(node=self.getName())
  File "/home/oe18433/code_bases/vsdnemul/vsdnemul/models/node/controller/onos.py", line 38, in _GetIpController
    return iproute.get_interface_addr(ifname="eth0", netns=node)
  File "/home/oe18433/code_bases/vsdnemul/vsdnemul/lib/iproutelib.py", line 343, in get_interface_addr
    return _get_interface_addr(ifname=ifname, netns=netns)
  File "/home/oe18433/code_bases/vsdnemul/vsdnemul/lib/iproutelib.py", line 219, in _get_interface_addr
    return (get_addr() if netns is None else get_ns_addr())
  File "/home/oe18433/code_bases/vsdnemul/vsdnemul/lib/iproutelib.py", line 214, in get_ns_addr
    with NetNS(netns=netns) as ipr:
  File "/home/oe18433/miniconda3/envs/vsdEnv/lib/python3.6/site-packages/pyroute2/netns/nslink.py", line 174, in __init__
    super(NetNS, self).__init__(trnsp_in, trnsp_out)
  File "/home/oe18433/miniconda3/envs/vsdEnv/lib/python3.6/site-packages/pyroute2/iproute/linux.py", line 131, in __init__
    super(RTNL_API, self).__init__(*argv, **kwarg)
  File "/home/oe18433/miniconda3/envs/vsdEnv/lib/python3.6/site-packages/pyroute2/remote/__init__.py", line 225, in __init__
    raise init['error']
PermissionError: [Errno 1] mount rundir failed: 'ctl1'

And so on for the other scripts. Any insight on this would be much appreciated!

I saw your errors,

You need clear up the previous containers that already are active on docker before error on script.
The vsdnemul must be running with root privilegies.

Anything, I am avaliable on google hangout


Investigate using apidiff tool to suggest version numbers.

Material motion has a tool to generate API diffs based on two git revisions:
https://github.com/material-motion/apidiff
Things to consider:

Release engineers will need to ensure they have both apidiff and sourcekitten installed

We'd also need to build the logic to auto-generate the suggested versions. Any new public APIs should result in a minor bump, with no public changes resulting in a patch bump. Any breaking changes should be detected and throw tons of errors without an appropriate flag passed through (to prevent breaking changes from being shipped accidentally).

Likely not a high priority - mostly solved by moving to the one version approach.


add math solution #171

Description
LeetCode solution #171 Excel Sheet Column Number
Category: Math
Have you made changes in README file ?

[x] Added problem & solution under correct topic.
[x] Specified Space & Time complexity.
[x] Specified difficulty level, tag & Note(if any).

Make sure all below guidelines are followed else PR will get Reject:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code so that it is easy to understand
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

Can you close this PR and update @verma-anushka
Then again create PR ?


!handle -1 not working

Has !handle -1 been deprecated? It doesn't work on my machine.

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

ID: 6be98bdb-5da9-5ec6-873f-1fcc2fa44d5a
Version Independent ID: 0098d700-6d00-02ea-6217-2893852d1e4f
Content: handle (WinDbg) - Windows drivers
Content Source: windows-driver-docs-pr/debugger/-handle.md
Product: windows-hardware
Technology: debugger
GitHub Login: @DOMARS
Microsoft Alias: domars

@SamZhangQingChuan - This particular channel is monitored by the men and women who write the driver documentation posted on docs.microsoft.com/drivers. Though we'd like to, we don’t have the resources to provide support for specific scenarios.
Your best bet is to use one of the forums where other driver developers and Microsoft engineers can be found. For example the Hardware and Application Developers on Q&A. You can post your question there, and the community of developers usually give feedback fairly quickly.
The !handle docs show that these bit mask options are used with out a dash, so you might try something like  !handle 1 0. Good luck with your issue.


Lower min required iOS version

Why is the minimum iOS version set to 14?
Carplay is already supported from 12.
And even if we would lower to 12. why not just use the minimum supported iOS version that is used by Flutter?
In our case we want to have carplay support. But only for devices that are iOS 14 or higher. All the other devices should still be able to use the app without carplay. That is currently not possible because of the hard min iOS version requirement.
Is there something we can do about this?

Hmm strange, for some reason now I can build with a lower iOS version.
@oguzhnatly why is the min version required in de readme?

No we should lower the min version.
And in the AppDelegate we could use:
      if #available(iOS 14.0, *) {
          return true;
      }

But we should lower the flutter_carplay.podspec to 12.0 (that work for our app)


Supported AWS Regions of the CDK

Hi,
Is there a list which AWS regions are supported by the CDK at the moment?
As I'm experiencing deployment issues in the eu-north-1 region at the moment.

Depending on the issues, you can get around those by adding --no-version-reporting to your cdk command probably.

In eu-north-1 it reports that AWS::CDK::METADATA is not supported as a resource, if that can be obtained by using --no-version-reporting im pleased with that solution.
Hence I think this would be nice if the Framework would handle such things internally for the actual AWS regions.

This is already supported #3149


bug(v4-menu): Menu: must have a "content" element to listen for drag events on.

Bug Report
Ionic Info
Ionic:

   ionic (Ionic CLI)          : 4.1.2 (C:\Users\amitm\AppData\Roaming\npm\node_modules\ionic)
   Ionic Framework            : @ionic/angular 4.0.0-beta.7
   @angular-devkit/core       : 0.7.5
   @angular-devkit/schematics : 0.7.5
   @angular/cli               : 6.1.5
   @ionic/ng-toolkit          : 1.0.8
   @ionic/schematics-angular  : 1.0.6

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : none
   Cordova Plugins       : no whitelisted plugins (0 plugins total)

System:

   NodeJS : v10.1.0 (C:\Program Files\nodejs\node.exe)
   npm    : 5.3.0
   OS     : Windows 10

Describe the Bug
When putting the menu inside a custom component, (app-menu) to make the app component less busy, I get the following error:

Menu: must have a "content" element to listen for drag events on.

Even though I am passing a [content] input containing element ref for ion-router-outlet

The menu icon doesn't show anymore.

Steps to Reproduce

Generate a new app with menu
ionic g component menu
Put the ion-menu in the app-menu
Put the following in app.component:

<ion-app>
  <ion-split-pane>
    <app-menu [content]="content"></app-menu>
    <ion-router-outlet #content main [swipeBackEnabled]="true"></ion-router-outlet>
  </ion-split-pane>
</ion-app>

Expected Behavior
Menu to show, no error to apear

Thank you, that solves it mostly. Now It shows the menu, but doesn't respect the split-pane, and never shows it side by side.

Seems the <ion-split-pane>  and/or the <ion-menu> are broken. Using a former code sample, it's not rendered anymore with @stencil/core v0.12.4.

I think the original issue is solved, please open a new issue for this other issue or open a feature request if something should changed

@AmitMY if you would like the menu to show over the split-pane you will need to add it to the ion-split-pane and not the ion-router-outlet. I have a working example I just created to confirm.
Give an id to your ion-split-pane
<app-menu></app-menu>   <ion-split-pane id="main-content">     <ion-router-outlet main></ion-router-outlet>
Set the contentId in your app-menu.component.html
<ion-menu type="overlay" side="start" contentId="main-content">
Hope that helps!

This is correct and works since beta.18


imagePullSecret structure doesn't match in deployments vs service accounts

Currently the imagePullSecret values are handle different between ServiceAccount and Deployment resources. This, in turn, prevents us from properly configuring secrets to pull from private registries.
deployment config:
      {{- if not (empty .Values.image.pullSecrets) }}
      imagePullSecrets:
{{ toYaml .Values.image.pullSecrets | indent 8 }}
      {{- end }}

service account config:
{{- if .Values.autoscaler.image.pullSecrets }}
imagePullSecrets:
{{- range .Values.autoscaler.image.pullSecrets }}
  - name: {{ . }}
{{- end }}
{{- end }}

I can open a PR with a fix if there is interest

I think you're right and there shouldn't be a difference in the structure. Just note that we actually have two places where we configure this, for coredns itself and in the autoscaler configurations (the deployment and service account for each).
Would be happy to review if you're willing to create PR for this.


Angular 13 support??

Does this support angular 13? If someone can share some demo links it would be very helpful.
Thanks in advance :)

Hi @poke-fcr,
There was a discussion about Angular support recently in #49.

I hope I can close this issue.


on android jax should only be used as a last resort because it will mess with the JavaScript that was originally in place once rebuilt,

it is difficult to change back out of JAX or AJAX JAVA must be written before in the build to help avoid these changes in language. The order is the best way to see this much clearer so you aren't fixing things that cannot be fixed before thefiring of the logfile initial

Please clarify your issue (especially the connection with Apis).

The APIs are separate issue but since you asked here, on analytics (GOOGLE), a problem with embedding them exists if a user is required to only have access through the developer guide instead of the analytics site. Hackers can prevent any user from accessing all functions of the APIs especially ones that are not listed underneath any application. I've embedded them before through Github, but some hacker accessing my account returned them back to a more vulnerable state I'm not sure why because he/she is using the web kit along with SeaMonkey and Gecko. It didn't make sense to me when one is freezing the I frames and manipulating the APIs because the action can be carried out without messing with the APIs necessarily, so it's like using them as a fall safe in case the individual is unable to keep up with the opening of more than four tabs or messing with an advanced user that uses the same options every time. That would definitively throw off any hacker using just the WebKit So any ideas on how to filter the chief APIs without worrying about the less important ones so that computer function is still almost normal even with hacker attached? Especially when they have added a string in front of the parent.

P.s. I hope that is more clear for the comment you submitted because the issue at hand was referring to AJAX, but another repo covering APIs was also listed. I'm not sure if you had been reading all of the different issues and just didn't realize you commented on the wrong repo on the list. Thanks for any help you may have to offer anyways.

Closing issue, I regard it as spam.


WIP: Interactive CLI

Hi, I have made some changes to the CLI.

The CLI is made interactive
Uses this library
tumble and status initially implemented
Help is available at all stages eg. help tumble
More changes to be made based on feedback

Installation:
dotnet restore to add the new library dependency
Typical Usage:

Start the CLI by using dotnet run
Type "help" to get the list of commands available
To start tumbler, type "tumble" (Default is mainnet, for testnet type tumble -n testnet)
Type enter to stop
Type "status" to check start tumbler again
Type enter to stop
Type "quit" to exit

this is awesome. Can you fix white spaces to \r\n on Program.cs so I can better review ?

Also can you keep supporting old style ? like -testnet ?

Also it seems that it will be interactive by default. Can you make it so it is interactive if -i is specified ?

Thanks, I have made the above changes:

-testnet and onlymonitor should work as before
-i will invoke the interactive mode
unix line endings \n restored as used in the source originally

I think it is /r/n look the diff

This is about the line endings in the source Program.cs right? The one from the master is showing only \n in my end.

ha maybe it is indeed fine, sorry. Thanks a lot I will test it.

@subhankarg sorry to have been a bit slow on it. This is an awesome feature, I want to get it in NTumbleBit.
My main complain about the state right now is the size of the diff. Can you arrange the code such that we do not have this big diff when most of the code is the same ?
Do not hesitate to create separate files for the option classes.
I would like that the non interactive mode use the old style parsing to be sure nothing that was working before break now. Maybe it is already the case, but reviewing is kind of hard because of the big diff.

I fixed the big diff issue and separated the options class. Mixing tabs and spaces caused the issue. Sorry about that. Please have a look now.

@subhankarg you should try to pull the new version. Now the CLI has a command called status which allow you to query cycle/transaction or address and see what is going on in the tumbler. This is awesome.


Add Certify bad query and re-org the query CLI

Description of the PR
Add Certify bad query and re-org the query CLI
Last open item for https://github.com/guacsec/guac/issues/769
PR Checklist

[x] All commits have a Developer Certificate of Origin (DCO) -- they are generated using -s flag to git commit.
[x] All new changes are covered by tests
[x] If GraphQL schema is changed, make generate has been run
[x] If collectsub protobuf has been changed, make proto has been run
[x] All CI checks are passing (tests and formatting)
[x] All dependent PRs have already been merged

cc @lumjjb


add guess-indent

I think u could try conform. For detailed configuration, u can refer to my nvim repository.


Per-stub delays

Is your feature request related to a problem? Please describe.
Delays setting in globalActions is not flexible enough, you can only filter request by urlPattern or httpMethod. You can't filter by request body or headers for example. The main issue is that when you need granular control of delays, you have to write a lot of urlPatterns while requestMatcher already does it for you.
Describe the solution you'd like
You should be able to add delay to individual request-response pair (stub) directly.
For fixed delay:
"response": {
	"status": 200,
	"body": "slow response",
        "fixedDelay": 1000
}

For lognormal delay:
"response": {
	"status": 200,
	"body": "slow response",
        "logNormalDelay": {
               "min": 100,
               "max": 10000,
               "mean": 5000,
               "median": 500
            }
}

Local delays (per-stub delays) should override global delays if they're happened to match on the same request. Multiple delays definitions on the same level should be additive.

I have a similar requirement, where I need my virtual service to reproduce the real response time observed on the real service for each different request.
An ideal solution would be the following :

Set a delay for each stub
Allow setting a global delayMultiplier (0 = respond immediately for all requests; 1 = respond with the specified delay)

@tommysitu I think I'm gonna implement this. Only simulate and spy modes should support this? What did you mean byMultiple delays definitions on the same level should be additive.' ?

That would be very helpful! Feel free to have a go.

The delay is applied here: https://github.com/SpectoLabs/hoverfly/blob/9708a10025b41cb68e01f43dd45e9f6d3cfc0ca7/core/hoverfly.go#L209

so it supports any mode except capture

Exactly. If the user provides both delays,  the actual delay will be the total.
So the following is supported:

"response": {
	"status": 200,
	"body": "slow response",
        "fixedDelay": 1000,
        "logNormalDelay": {
               "min": 100,
               "max": 10000,
               "mean": 5000,
               "median": 500
            }
}

Hmm. Taken SynthesizeMode for example. It doesn't grab a response from the storage but instead it calls a middleware that returns the response. So in this case, a middleware should be able to return fixedDelay and logNormalDelay?
On the hand, SimulateMode can grab fixedDelay and logNormalDelay from the storage in case a simulation was imported earlier and then it calls a middleware that can also return different fixedDelay and logNormalDelay. Should we apply both delay sets here?

you're right. it's possible that middleware adds the delay settings. so perhaps the response, err := mode.Process(req, requestDetails) should also returns a  *ResponseDelay struct for the specific response? if it's nil, then use global delay? otherwise, execute the per-stub delay?

Probably, I'll look into it more deeply :+1: But the question remains :-) In simulate mode during Process call I can have one pair of fixedDelay and logNormalDelay from the storage and the one more pair from the middleware. Should I sum them up? Or prefer one over the other?

the RequestResponsePair could only have one response even after applying the middleweare. so it won't end up with two fixedDelay.

Oh. Indeed. my bad :smile:

Thanks @ns3777 👍  and sorry for the wait. Released in v1.3.0


Server does not reboot after installing updates to the server

It doesn't rely on the autoupdater library, which creates a bit of ugliness.
There are a number of related issues as well: you can't walk up to a server and press u to update it, the server will not automatically install updates to other packages besides amber-server it has installed, and so on.

Tested and verified!


wifi: Use COPY etc /etc pattern

I was doing this in a custom build I was using, and I think it's much more elegant because one avoids having multiple files in a toplevel COPY invocation - it generalizes much more obviously into a pattern where one wants to inject config into multiple places.

Rebased :surfer:


ERR_MODULE_NOT_FOUND

Hi,
We just got a Dependabot PR (https://github.com/theupdateframework/go-tuf/pull/312) updating go-version-action. However, it appears to be failing with ERR_MODULE_NOT_FOUND (see this run).
The error persists after a re-run.
Any guidance? This is how we're invoking the action:
https://github.com/theupdateframework/go-tuf/blob/36633af8d7a2162664a58f3fb1fe36a74e10428e/.github/workflows/tests.yml#L5-L13
Thanks for the action; it's been quite useful!

This appears fixed in 1.1.3, so closing.
Thanks!


Update data source tutorial to use more dependable API example

It turns out the IMDB API is pretty unreliable, which is a bummer. This makes it a bad choice for an example data source.
We should revamp the tutorial to use a more reliable API. Requirements are:

[ ] No API key required — we want people to immediately start coding, not have to sign up for API keys
[ ] Reliable — should be up more often than not
[ ] Relatively simple — if we can find a small API with one method, that would actually be the best option. A complete example that doesn’t involve a ton of copy-pasting would make the tutorial much more approachable than having to click through to GitHub for the rest of the code and/or copying hundreds of lines of code to get a proof-of-concept running

I'm currently leaning toward the xkcd API, which is small, reliable, and familiar to many developers.

An example xkcd response:
{
  "month": "10",
  "num": 1905,
  "link": "",
  "year": "2017",
  "news": "",
  "safe_title": "Cast Iron Pan",
  "transcript": "",
  "alt": "If you want to evenly space them, it's easiest to alternate between the Arctic and Antarctic. Some people just go to the Arctic twice, near the equinoxes so the visits are almost 6 months apart, but it's not the same.",
  "img": "https://imgs.xkcd.com/comics/cast_iron_pans.png",
  "title": "Cast Iron Pan",
  "day": "20"
}

That's a pretty straightforward schema with nothing fancy in the field resolvers. We’d basically build the link if it’s empty:
  link: data => data.link || `https://xkcd.com/${data.num}/`,

In progress here: https://github.com/gramps-graphql/gramps/pull/46


No metrics for WebApps slots

If you use webapps slots the metrics are not pulled (only the webapp is)

Hi,
I'm very interested in solving that issue, if people can spend some time on IRC or Slack or email or whatever explaining me where i need to look to find how to solve the issue. I already know how to get the metric definitions for webapp slots in the Azure Monitor API and i think with some patching for that special cases we can solve that issue.
Who's with me on that ? @villekr ? @daniellee

The correct request should be : https://management.azure.com/subscriptions/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/resourceGroups/xxxxxxxxxxxxxxxxxxxxxxx/providers/Microsoft.Web/sites/xxxxxxxxxxxxxxxxxxxxxx/slots/slotname/metricdefinitions?api-version=2016-08-01

There is a PR #45 that solve this issue. Can you merge it to master ? @daniellee Thanks a lot

Still not works
[root@zbx-01 ~]# grafana-cli plugins ls | grep azure grafana-azure-monitor-datasource @ 0.1.1

This fix is released in version 0.1.2.


Add UUID to Prometheus metrics if requested

Description
Closes #1209.

Readiness checklist

[x] I added tests for new functionality or bugfixes.
[x] I ran task all, and it passed.
[x] I added/updated comments for both exported and unexported top-level declarations (functions, types, etc).
[x] I checked comments rendering with task godocs.
[x] I ensured that the title is good enough for the changelog.
[x] (for maintainers only) I set Reviewers (@FerretDB/core), Assignee, Labels, Project and project's Sprint fields.
[x] I marked all done items in this checklist.

doh, that was "last minute fix" 😆


TV Shows display as completed after watching a few episodes

Netflix add-on version
1.18.6+matrix.1
Operative systems used
Linux (Ubuntu / Mint / ...)
Kodi version used
Kodi 19 (Matrix)
Description of the bug
In the addon TV Shows are displayed as completed after watching only part of a season. For example watching half the episodes of season 1 of a show and the addon will display it as completed in Kodi. This has the effect of hiding the show if the Kodi view option is "Unwatched only".
In Kodi a TV show should only display as completed when all episodes in all seasons are watched. If a new episode or new season is added it should also cease to display as completed.
Steps to reproduce the behavior

Watch a few episodes of a show
View any listing with that show, such as My List, Continue watching, Search, etc
Show will display as completed (with Tick icon), and will be hidden when the Kodi sidebar is set to "Unwatched only" view.

Debug log - mandatory
https://paste.kodi.tv/ugihafivar.kodi
Possible fix
No response
Additional context
No response
Screenshots
No response

this is not a bug is intended as it is
netflix api do not provide information about partial or completed on tvshow type
then we know only if a tvshow is started, then kodi think is completed, and will be add the tick "as completed"
some users prefer it that way others like you don't like it
from my POV the only solution are:
-remove the support to tvshow to get the tick "as completed", but i think other users will start complaining
-add another addon setting to disable the tick on tvshow type

I think the current behaviour of marking all watched shows as 'Completed' will continue to confuse users because it is the opposite of how Kodi works. For example this discussion about shows disappearing from 'Continue Watching' menu.
An addon setting to change this behaviour would be welcome. I feel it would be less confusing for this to be the default behaviour and have an addon setting to mark in progress shows as 'Completed' for those users that want the alternative.

@mcdamo i have add a new addon setting in "General" page,
now started tv shows are not marked by default
test build: plugin.video.netflix_1.18.6+matrix.1_20220610_t1.zip
let me know


#25 BIP174 should not have TransactionInput/Output

the build is failing at diff --exit-code
not sure what the fix is (works locally). Bump package version to 2.0.2 maybe?

It runs npm run build and checks if there is a diff.
This probably happened because you modified the d.ts type file manually instead of modifying the ts file then running build.
(the diff is an extra line break)

Fixed.


New arch doesn't render React Native components inside SVG

Description
I'm sorry if it is a duplicate, first time use new arch because of RN 0.76
<PillInforBox>
  <View style={styles.sectionContainer}>
    <Text style={styles.sectionTitle}>top text</Text>
    <Text style={styles.sectionTitle}>BOTTOM TEXT</Text>
  </View>
</PillInforBox>

const PillInforBox = ({children}) => {
  return (
    <Svg>
      ...
      {children}
    </Svg>
  )
}

I code like this and it works in old arch until now (RN 0.76). I tested with

RN 0.75
RN 0.76

Old arch
OK
OK

New arch
Fail
Fail

New arch

Old arch

Steps to reproduce

Clone and build reproduction in new arch
Disable new arch and rebuild
There is rn75 branch if you want to test

Snack or a link to a repository
https://github.com/pnthach95/rn76
SVG version
15.8.0
React Native version
0.76.0
Platforms
Android, iOS
JavaScript runtime
Hermes
Workflow
React Native
Architecture
Fabric (New Architecture)
Build type
Debug app & dev bundle
Device
None
Device model
No response
Acknowledgements
Yes

Hi @pnthach95,
Thanks for bringing this up! There's indeed an issue with the new architecture when it comes to Yoga layouting. It's part of a broader issue we're working on. As a temporary workaround, you can change the order of children so that {children} is the first child of the Svg component, like this:
const PillInforBox = ({children}) => {
  return (
    <Svg>
      {children}
      ...
    </Svg>
  )
}


Unable to connect HA & Deye 5kw Inverter with Stick logger model LSW-3-C

I am trying to use the Solarman integration to Deye 5kw Inverter with Stick logger model LSW-3-C

From below "Unavailable" on all Sensors, it seems that the connection cannot be made to the IP (in the above)

I have set the configuration as follows

I added the the sensor in the configuration.yaml as

I have two topics that expect can be the source of my problem:

Since the serial number 27... is not in the V5-range, this could be a potential problem, but not sure what exactly need to change, should I need V4 instead.

I also have an issue to access the Logger IP <IP_ADDRESS> from my browser (I tried Brave, Chrome & Edge) - all give the same error: "This site can’t be reached<IP_ADDRESS> refused to connect.". I can see the IP in my DHCP listing and I can also PING the IP with no problem. Trying to resolve this issue, I tried:

Firewall settings (and even switched it off)
Antivirus settings (and also set it off)
tries another PC on my network
but the problem remain

PS: I was able to open the logger when I connected directly to the loggers AP_* WiFi network that it created. I am not sure what the "Remote server B = not connected" means ?

try connecting to <IP_ADDRESS> that is your logger IP that is seen on the last screenshot
i have the same V5 with 27xxxxx
to make the connection i used <IP_ADDRESS> as an ip in the HA integration section and device id is 0
i got it connected but it works not as good as expected.
Battery dischage for example worked for a day registering perfectly, next day i got it not working with last message 10 hours ago (battery was discharging during the daytime)

Thanks for you help @denveronly - unfortunately I can also not access or PING the IP <IP_ADDRESS>.
I have also tried the <IP_ADDRESS> IP and device id is 0 in the HA, but still get the "unavailable" response. It's really like the logger is not available on my network, but it's IP IP <IP_ADDRESS> is in the DHCP list on my network. You gave me hope that the connection is possible. Thanks

Thanks for you help @denveronly - unfortunately I can also not access or PING the IP <IP_ADDRESS>.
I have also tried the <IP_ADDRESS> IP and device id is 0 in the HA, but still get the "unavailable" response. It's really like the logger is not available on my network, but it's IP IP <IP_ADDRESS> is in the DHCP list on my network. You gave me hope that the connection is possible.

I think that it is not the stick issue, it is your network problem the ip .100 or .102 is already registered by other device
Maybe try specifying in Stick settings not a fhcp connection, but a static ip with
<IP_ADDRESS> router
<IP_ADDRESS> or 253 which absolutely not taken, please scan as Stick ip
<IP_ADDRESS> as subnet mask
after apllying settings try scan one more time if the device had appeared on network
Inverter sticks are too dumb to fail to connect to network

Yes! it's working now - Thanks @denveronly for your advice. I changed the network settings as you suggested and then I could see the logger on my home network with the static IP. I plugged the IP into the HA configuration.yaml file. However, I had to delete and add the Solarman add-in again. Then the Solarman "device" in HA connected and started to show the values from the logger. After about an hour I started to see data on the Energy dashboard. Thanks a mil for your assistance.

Hello! The datas are live ? No delay, directly from wifi stick or are through solar man servers?


Added an entry on Bar Charts

Going to merge this in. Only change (which I'll make) is that we now need dates as the first bit of the filename, since we're switching to blog format. No way you'd have known that though.
Thanks for the contribution!