Kubernetes version dropdown is empty

Version:
2.3.2
Steps:

Start rancher server
Create a RKE cluster

Results:
Kubernetes version dropdown is empty

Expected:
Users should be able to see k8s versions.
More Info:
If the connection between rancher server and github is bad, rancher server might take 30 mins to finish the git clone k8s-metadata. During this 30 mins, users will not be able to see any k8s version in create cluster page.

yes, I will meet this same problem

+1

cant see this mentioned already, but this is happening in a fresh 2.3.3 aswell

I have this issue on a fresh v2.3.3 as well

It worked for me after I refreshed the Kubernetes metadata from Tools -> Drivers -> Refresh Kubernetes Metadata

Confirmed, that also fixed it for me.

the bug fix is validated in Rnacher:v2.3-head ab7ce7ba2 and master-head 8bd9f3be2
Steps:

run a new Rancher server container
log into the UI for the first time
check if the dropdown list is empty
check Rancher's log
repeat the above steps several times

Results:

the dropdown list os not empty in all my tests
the log shows the following message, which indicates the fix is working, otherwise the dropdown list may be empty.

2020/01/03 00:53:02 [INFO] driverMetadata: empty setting k8s-version, using stored defaults

Issue seen on 2.3.4rc6. Reopening the issue
Steps:

Have a rancher server set up in HA mode on 2.3.3 (steps followed from rancher docs, using helm 2)
create a cluster, rke DO, the k8s version dropdown will be seen empty.
refresh the kontainer metada from Global --> Tools --> Drivers
Create an rke cluster, the k8s version will be available in the dropdown. Deploy a cluster.
Upgrade rancher to 2.3.4-rc6
Go to edit cluster and user can see k8s version dropdown will be seen empty.
refresh the kontainer metada from Global --> Tools --> Drivers
Create an rke cluster, the k8s version will be available in the dropdown.

@sowmyav27 After upgrade, do you see "driverMetadata: empty setting k8s-version, using stored defaults" in the logs? An upgraded setup would already have some set values, so I wonder what's happening here

@kinarashah I see this in the logs
2020/01/03 05:33:23 [INFO] driverMetadata: refresh data
2020/01/03 05:33:25 [INFO] driverMetadata initialized successfully

Moving out of 2.3.4, need more time to investigate and focus on the zero downtime.

Can confirm that it still is happening with v2.3.5. Metadata refresh works only if the user has admin privileges. Standard users face error when doing metadata refresh.

Running into this as well on new v2.3.5 installs, however, I'm trying to use terraform so a manual step of refreshing the metadata is not a good option. Any ideas?

Should be fixed in 2.4, improvements around loading metadata on startup by
https://github.com/rancher/rancher/issues/25162

@divyangjp correct, the option to refresh the Kubernetes metadata is available for administrators by default, or for any user who has the Manage Cluster Drivers global role

the fix is validated in rancher master-head 854e9ae6f.
Following the same steps provided in the issue, I do not see the dropdown list empty, and Rancher logs show the following message:
2020/02/28 23:48:09 [INFO] Refreshing driverMetadata in 1440 minutes
2020/02/28 23:48:09 [INFO] driverMetadata: refreshing data from upstream https://releases.rancher.com/kontainer-driver-metadata/dev-v2.4/data.json

The same test is done multiple times and the issue is not seen.


Complete 28.c

The program prints its own source code. I have added the function call in main as well.

Further PR without proper instructions and code will be marked as SPAM and tagged as INVALID. Issue will be reported to Hacktoberfest Maintainers. @RKRohk @RonitNayak25 Please take note.


Test pr

Description

How and where has this been tested?

How this was tested:
Browser(s) and OS(s) this was tested with:

Screenshots

To-do list

[ ] If my change impacts other components, I have tested to make sure they don't break.
[ ] If my change impacts documentation, I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.

[ ] This pull request is ready to merge.

Test result: https://jianliao.github.io/spectrum-css-vr-test-result/55bbe80-result-2020-02-18_03-37-06/html_report/index.html


Add DerivedData to .gitignore

Testing
Test: configure Xcode to keep it's cache in a default relative folder - DerivedData, cache generated by demo project shouldn't be tracked by git.

Moved it to mpp/demo/.gitignore, won't hurt anybody here


deleting shuffle stages

In the code https://github.com/zrlio/spark-io/blob/master/src/main/scala/org/apache/spark/storage/CrailStore.scala - the check to delete stages are based upon shuffleCache.contains - which is wrong. See here : https://docs.oracle.com/javase/7/docs/api/java/util/concurrent/ConcurrentHashMap.html#contains(java.lang.Object)
Instead of this, call shuffleCache.containsKey(...) which works nicely ! :)
I wonder why this ever worked before (for testing delete shuffle stages). Spark 2.2 does call to delete shuffle stages.

Fixed in :  8c30b6f


[feature request] N4 bias correction support

Is your feature request related to a problem? Please describe.
N4 bias correction is quite a common preprocessing step when it comes to MRI image data analysis, which is why it should be part of the BrainLesion preprocessing tool. Adding this step manually at the beginning or at the end does not reflect the idea of a compact preprocessing tool.
Describe the solution you'd like
I'd like to be able to add N4 bias correction to the preprocessing pipeline, this could be achieved for example by using SimpleITK. This could go right with the already added normalization step.
Considering that all the different normalizers are stored in a different Github repository, it might make sense to merge the normalizers into the current repo, to simplify any future changes.
Edit: Z-score normalization should be considered as well. But it should be noted, that z-score normalization especially also requires the brain mask as an input

In our experiments, we never found an advantage of running N4 bias field corrections, but I agree, that is well-established in the community. Thus, it should be part of our preprocessing pipeline.
Thank you for the suggestion @LennartPhil
When does N4 produce best results?
should this be run on images with or without skull? before or after normalization?

@MarcelRosier, please also see this thread regarding our discussion about normalizers.

@LennartPhil I see you created a fork
https://github.com/LennartPhil/preprocessingN4
Would you like to work on a PR?


Branch changing

Branch switching feature (I guess the purpose should be obvious :)
Thoughts
Flow: reference to branch becomes a link.

Pressing on that calls branch_popup which also have "new" option (can be a separate feature in fact). User chooses a branch, the program checks local changes vs current branch and shows warning if changes unsaved (blocked by #264), if ok switches to another branch. Only unequal objects are replaced (also blocked by #264). DB is updated.
In case of activation fails the process does not stop but retrieves all objects and shows list of activation issus.

yep, also see https://github.com/larshp/abapGit/issues/127
Overwriting should be handled separately from this issue.
I think this can be solved by updating the mv_branch field to the sha1 of the new branch. Update the persisted branch name, and then call lcl_repo_online->deserialize.

it should also be possible to change the url/repository along with the branch


Sync to fix release check

Wait @ascrutae to fix def file reader bug, casued by header added.

Coverage increased (+0.01%) to 19.247% when pulling ea99e8fce9107049afb3e31bd66cfdea4d904717 on fix/release into f625f609b35706e7247566571fe2e34dbb4de0db on master.


STREAM Sender: Unreachable destinations will retry until timeout but should short-circuit

If a STREAM sender tries to send a payment on a link but the Connector can't forward the packets (i.e., the StreamSender gets an F02 Unreachable error, the Sender should stop sending STREAM packets. However, the current implementation retries every 10ms until the overall sendMoney timeout is hit.

See https://github.com/interledger-rs/interledger-rs/pull/635 for more details


Roll Engine from b55bf988cc9a to fb81dab822e5 (2 revisions)

https://github.com/flutter/engine/compare/b55bf988cc9a...fb81dab822e5
2021-06-13<EMAIL_ADDRESS>Roll Skia from bc4bc5f1e284 to cd33e4accde2 (1 revision) (flutter/engine#26730)
2021-06-13<EMAIL_ADDRESS>Roll Dart SDK from 88b9786db62b to 0a32380de829 (1 revision) (flutter/engine#26729)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/master/autoroll/README.md

Commit queue failed; closing this roll.


Generate 'Now' compatible project

https://zeit.co/now

This is now should be supported by the specific generator.
https://github.com/Raathigesh/AtmoExpressES5Generator is a now supported generator.


Improve import updates with slice change plans and port deltas

Issue #, if available:
#101
Description of changes:
Multiple improvements to service import logic.

EndpointSlice change plan calculates necessary changes for endpoints.
Derived service ports are updated based on imported external changes.
Internal Port model is simplified and used broadly for comparisons ignoring order.
Constructor logic moved to util class
Some common test struct constructor logic moved from test classes to common_test

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Codecov Report

Merging #116 (db1ca36) into main (14b1c36) will increase coverage by 4.68%.
The diff coverage is 84.89%.

@@            Coverage Diff             @@
##             main     #116      +/-   ##
==========================================
+ Coverage   70.30%   74.98%   +4.68%
==========================================
  Files          14       15       +1
  Lines        1357     1443      +86
==========================================
+ Hits          954     1082     +128
+ Misses        330      287      -43
- Partials       73       74       +1

Impacted Files
Coverage Δ

pkg/controllers/serviceexport_controller.go
39.69% <ø> (ø)

pkg/model/types.go
66.03% <0.00%> (-1.27%)
:arrow_down:

pkg/controllers/cloudmap_controller.go
46.35% <52.56%> (-10.11%)
:arrow_down:

pkg/controllers/endpointslice_plan.go
96.03% <96.03%> (ø)

pkg/controllers/utils.go
97.94% <100.00%> (+40.56%)
:arrow_up:

Continue to review full report at Codecov.

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


Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

i run      docker-compose up -d   then show these error

docker issue


Account for empty yaml file in update-yaml.py

If reading a yaml file with no entries, yaml.safe_read() produces a
NoneType object. This commit fixes the issue by re-ordering to ensure
we convert to NoneType before the code to handle NoneType is executed.
Connects #950
Co-Authored-By<EMAIL_ADDRESS>

RPC-AIO-Ceph-Liberty-PR: Fail

RPC-AIO-Liberty-PR: Fail

👍

Not tested but looks good to me. 👍


document how to set result data

How do I set result data?

My handler
    public function __invoke(FetchWikidataMessage $message)
    {
        $id = $message->getWikidataId();
        $wikiData = $this->wikiService->fetchWikidataPage($id);
        $official = $this->entityManager->getRepository(Official::class)->findOneBy(['wikidataId' => $id]);
        $official->setWikiData($wikiData);
        $this->entityManager->flush();;

        // set results for the message monitor?
        return $wikiData; // nope
       // use the logger?

    }

You can find the implementation here: https://github.com/zenstruck/messenger-monitor-bundle/blob/1.x/src/History/ResultNormalizer.php
In other words, there are a couple of special handlers, and anything else is handled as a string. Note that if you are returning an object, the recorded data will be null. If you return an array, all scalar values will be used, datetime object converted to a string, and all other stuff to its debug type.
Don't forget to restart the workers after changes!


README: add table with supported git features

I will contribute to this PR this morning adding, "fully supported", 'basic supported"


Cropping selects wrong region

I downloaded and compiled the latest master branch, after the first image it seems to save the wrong region of the photo

Hello
Could you please provide some more information exactly what you are doing and how, with maybe screenshots so I understand better?


Device Request - Update 13-11-23: Seems to work in the test-version [Tuya Smart Zigbee Plug 16A/20A Eu Outlet 3680W Power Meter Compatiable Met Alexa En Tuya Hub] - [On the device the text: Elivco, model LSPA9] [Like Sun GMBH, Essen] [720416123547]

it would be very nice if this device is supported by the app. Thanks in advance, Ruud
Manufacturer | ModelID (developer tools): _TZ3000_okaz9tjs | TS011F
https://nl.aliexpress.com/i/1005002344798281.html
"ids": {
"modelId": "TS011F",
"manufacturerName": "_TZ3000_okaz9tjs"
},
"endpoints": {
"ieeeAddress": "70:b3:d5:2b:60:03:f9:dd",
"networkAddress": 1637,
"modelId": "TS011F",
"manufacturerName": "_TZ3000_okaz9tjs",
"endpointDescriptors": [
{
"status": "SUCCESS",
"nwkAddrOfInterest": 1637,
"_reserved": 24,
"endpointId": 1,
"applicationProfileId": 260,
"applicationDeviceId": 81,
"applicationDeviceVersion": 0,
"_reserved1": 1,
"inputClusters": [
0,
6,
3,
4,
5,
57345,
2820,
1794
],
"outputClusters": []
}
],
"deviceType": "router",
"receiveWhenIdle": true,
"swBuildId": "500+TZSKT31BS102",
"capabilities": {
"alternatePANCoordinator": false,
"deviceType": true,
"powerSourceMains": true,
"receiveWhenIdle": true,
"security": false,
"allocateAddress": true
},
"extendedEndpointDescriptors": {
"1": {
"clusters": {
"basic": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"onOff": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"identify": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"groups": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"scenes": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"electricalMeasurement": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
},
"metering": {
"attributes": "UNSUP_GENERAL_COMMAND",
"commandsGenerated": "UNSUP_GENERAL_COMMAND",
"commandsReceived": "UNSUP_GENERAL_COMMAND"
}
},
"bindings": {}
}
}
}
Prerequisites:

Before requesting a device addition, please ensure there is not already a request for the device among the open issues.
Make sure your Homey is upgraded to firmware v5 or higher.
You need a physical example of the device

Device Name: [Provide the name of the device]
Device Model: [Provide the model number or identifier]
Device Description: [Describe in short the functionality of the device]
Link to device image: [Provide the URL to an image/photo of the device]
Device Interview:
[Paste the device interview information here]
Additional Comments:
[Provide any other relevant information or requests related to the device. Link to where you bought the device can be of help]
How to interview a device:

Add the device as a generic Zigbee device in Homey
Navigate to https://developer.athom.com/tools/zigbee.
Interview the device, the button for this is to the right of the device in the list of Zigbee units.
Click the copy button/icon to capture the device information.
Paste the copied information above.

Note: To be able to add more devices to the Tuya Zigbee app, we rely on community members like you to provide interviews of the devices you want added. Thank you for your contribution!

@ruudbinnendijk This device is already supported from v.0.2.12. If you install the latest Test version, it will work. You can find the latest (test-)version at https://homey.app/nl-nl/app/com.tuya.zigbee/Tuya-Zigbee/test . Please close the issue marked as resolved.

Thank you!

Do I need a Tuya Hub to connect with Homey?

Maybe You beter don't use Tuya plugs. 3 out of 4 burnt a fuse here.
Verzonden vanaf Outlook voor Androidhttps://aka.ms/AAb9ysg

From: HyungsukRyu @.>
Sent: Wednesday, January 3, 2024 3:23:25 AM
To: JohanBendz/com.tuya.zigbee @.>
Cc: ruudbinnendijk @.>; State change @.>
Subject: Re: [JohanBendz/com.tuya.zigbee] Device Request - Update 13-11-23: Seems to work in the test-version [Tuya Smart Zigbee Plug 16A/20A Eu Outlet 3680W Power Meter Compatiable Met Alexa En Tuya Hub] - [On the device the text: Elivco, model LSPA9] [Like Su...
Do I need a Tuya Hub to connect with Homey?
—
Reply to this email directly, view it on GitHubhttps://github.com/JohanBendz/com.tuya.zigbee/issues/523#issuecomment-1874775686, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BDYY64FDX7LQLL3RDXMOZ23YMS6J3AVCNFSM6AAAAAA67T7GRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZUG43TKNRYGY.
You are receiving this because you modified the open/close state.Message ID: @.***>


Support for Node 15

I extended the previous PR with what you asked its author

Superseded by #16


As a Project Coordinator, I want to view the project forms in read-only mode, so that I can view all the information

Description:
To allow the user to view all the project information without requiring the team to write custom views for every form, a possible first approach is to render each form in disabled mode.
The form in edit or view mode would be rendered in the same page, and the mode would be chosen based on the status of the corresponding project_revision
Acceptance Criteria:
Given that a project_revision is committed
When I visit /cif/project-revision/<projectRevisionId>/form/(overview|contacts|managers)
Then

The form is displayed in disabled mode
There is an Edit button in the top-right corner
The form submit button is not displayed
The TaskList is displayed in view mode

Given that I click the View button for a project in the project list
When I am redirected
Then I land on the /cif/project-revision/<projectRevisionId>/form/overview, where projectRevisionId is the latest committed project revision for the given project.
Given that I am viewing a committed project revision
When the project revision is not the latest committed project revision for the given project,
Then I am redirected to the page for the latest project revision to ensure that I am viewing up-to-date information.
Given that I am viewing a committed project revision
When I click the Edit button
Then a new project revision is created, and I am redirected to the form matching the one I was viewing
Given that I am viewing a committed project revision
When there is a pending project revision in progress
Then the Edit button should display: Resume Edition
Development Checklist:

[x] The TaskList component should have a mode variable, where mode is "view" | "create" | "update" (may have been added in #439 , depending which issue is done first). The task list would be in view mode when the TaskList_projectRevision changeStatus is "committed". In view mode, there will be no link to the "review and submit" page, and the links the the various forms should only be the form name (i.e. no "add" or "update" prefix, see screenshot below). The title of the TaskList should be the project reference.
[x] ~The disabled prop should be passed to every widget. Some widget's implementation may not pass the disabled prop to their component, so that should be checked (and unit tested)~ Used the read-only them instead
[x] Meets the DOD

Wireframe:

Hey team! Please add your planning poker estimate with ZenHub @BCerki @dleard @gurjmatharu @mikevespi @pbastia

Thanks @mikevespi and @matthieu-foucault !
I tested in dev by:

Made amendment for project #001. Able to start, exit and resume an amendment/revision.
Made amendment for project #002. Able to start, exit and resume an amendment/revision.

Observation:

I was able to have two projects in revision (001 and 002)


Remove include directives for proto well-known-types.

I added these in a previous commit, but they shouldn't have been
necessary. I had a broken protocol buffer compiler installation on my
machine, which was why these includes weren't found. While they didn't
hurt to be added, they aren't necessary and ought to be removed.

R: @herohde

That is correct.

@tgroh please merge


feat: Add a public method to determine if the error has been appended to the stack.

feat func ExistStack(err error) bool:
non-intrusive:
Add a public method to determine if the error has been appended to the stack.
Avoid adding the stack repeatedly for errors.
fix: error method
feat: test ExistStack
add ExistStack test
fix: error variable name
style: optimizing code structure
feat: add test example
style(value): delete func reachable code
style(build): edit format files

fix: https://github.com/pkg/errors/issues/210

The previous PR was already closed as “will not merge” https://github.com/pkg/errors/pull/239 and has no changes that we could not have come to through a code review process. (My code review was intended to help you write better code, not to get it to a state that would be merged.)
Please read the project’s README:

Because of the Go2 errors changes, this package is not accepting proposals for new functionality.

ok


Return OrderEventsEmail as Enum in GraphQL API

I've missed it in #2811, OrderEventsEmail should be returned as an Enum

Have you checked if it affects the schema? Does it need to be rebuilt?

@Pacu2 Please rebase this branch with master.


[Discord RPC] Presence update for server gamestates

Dependency of https://github.com/R2Northstar/NorthstarDiscordRPC/pull/25 so it can work properly.

Testing done by @catornot in https://github.com/R2Northstar/NorthstarDiscordRPC/pull/25#pullrequestreview-2288366528


UI updates

Signed-off-by: fjogeleit<EMAIL_ADDRESS>
What type of PR is this?

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

/kind bug

/kind cleanup
/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

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

/area build

/area config

/area outputs

/area tests

What this PR does / why we need it:
UI improvements, simplify VueJS Logic
Reduce initial render errors
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leodido after the PR has been reviewed.
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

Welcome @fjogeleit! It looks like this is your first PR to falcosecurity/falcosidekick 🎉

Change the target to https://github.com/Issif/falcosidekick-ui


Upgrade sysdig to v0.27.0

Upgrade Sysdig to v0.27.0
Install llvm-toolset in base images (source from RHEL official subscription repository)
Reformat and introduce the development base image building script without RHEL subscription required.

Block on

[ ] First GA release

Let's block this PR before GA

This PR would be included in UBI changing work. Let's hold it.


@babel/traverse vulnerability

https://www.mend.io/vulnerability-database/CVE-2023-45133
https://github.com/babel/babel/security/advisories/GHSA-67hx-6x53-jw92
Looks like it should be upgrade to @babel/traverse - 7.23.2

For anyone seeking a quick fix until this is handled, overriding the package version by adding it to your own dependencies seems to work

This code has been removed from the codebase as of 6.1

With yarn adding something like that to package.json works:
...

    },
    "resolutions": {
        "styled-components/@babel/traverse": "7.23.2"
      }
...

Is there any version of v5 with updated package? IMHO using resolution is a kind of nasty workaround. :D


Add bandpass=True to yasa.bandpower

Based on the min and max frequency defined in bands
Also add the total absolute power to the output dataframe

Done in d05904445b82caa3deda213880a8102b56dc5131.
Will be released in next stable version of YASA.


Service discovery fixes

Removes closing of update channels and fixes all missing respects of the context.
Changes across various, mostly recent, SDs. Almost all of these are potential deadlocks "only" manifesting as goroutine leaks.
This needs careful review so we don't break anything further.
@brian-brazil the second commit consolidates the Zookeeper SDs. As far as I could see those were just distinguished by their parsing function.
Those no longer send the initial set of all targets, i.e. could have a bit of flapping now on config reload. However, what was there before was realistically not working anyway as it just immediately sent whatever it got between constructing the SD and calling Run().
If someone cares enough they are free to implement a proper initial walk later.
@juliusv

This was a consequence of the SD API at the time making this impossible to implement correctly. It's since changed so that's no longer the case.

Yes, indeed. The API didn't support sending target group slices but the case that was added here once it did, was effectively not doing anything. I think it was myself adding it back then.

@juliusv @brian-brazil does this look good for merge?

:+1:


Add support for interacting with the Electron API from a game.

This should be possible, but currently as far as I can tell, Indigo doesn't expose any APIs for it.
I'm not entirely sure what the best way to expose such an API would be, as access to such an API is dependent on the version of the game (i.e. is this built for the web, or electron?). Maybe the electron-specific APIs could be exposed as an Option somewhere?

You're the first person to wonder about this, and that includes me! So welcome to the pointy end of Indigo where the path has not been trodden! But I'm excited about discovering and resolving all the things that need sorting out.
No, the electron APIs are not exposed anywhere, two reasons:

The electron support provided out of the box was really just a bare bones minimal reference to help you start building your game. The assumption was always that someone would want to do something custom if they got beyond these meagre needs.
Indigo - apart from a bit of dev support in the plugin - makes no real assumptions about where you're going to deploy to currently. We certainly could add specific and fuller support for obvious platforms like electron though. Maybe in a new module?

Some options:

You roll your own subsystem - if you need to talk to JS, the assumption is that you'll encapsulate that work in a subsystem. This forces your code to play nicely with Indigo, while allowing you to do whatever mutable, scary thing you need to do to make this work via scalajs-dom.
We build in official support and a new module - which will start by us doing point (1) as a PoC and end with an officially published implementation.
You use Tyrian (after the next release? Coming soon) - The next version of Tyrian has built in support for Indigo, including communicating with it. Tyrian's whole purpose in life is talking to JS and the DOM, so maybe what we could do is set up a Tyrian project that acts as a wrapper for Indigo games that need to talk to Electron? We could even have electron publishing as a Tyrian option eventually? Keeps the nasty stuff out of your game / Indigo but has the overhead of people needing to learn about Tyrian. Maybe it's too much?

I think I like the Tyrian idea the best. That seems like the cleanest option to me, and avoids the issue of how to expose specific platform APIs to Indigo -- you just communicate with events (I'm assuming).
I'll have to mess around with creating a wrapper for Electron (or an Electron alternative like Tauri -- I'm hoping that such alternatives still have good enough webGL support and so on to work well with Indigo) that interacts with Indigo.
With a good enough wrapper distributed as a project template and docs, I don't think there's even a lot someone would have to learn about Tyrian unless they have needs that go beyond what is exposed by the wrapper.


Build failure

Hello! Thanks for the great work you've done!
I faced  some difficulties trying to build sources for this project. I find myself not so experienced in building c++ projects, so I wonder if you could help me with this one.
Here is an excerpt of console output:
...
-- Configuring done
-- Generating done
-- Build files have been written to: /home/sergey/PyPatchMatch/build
[ 77%] Built target patchmatch
[ 88%] Building CXX object CMakeFiles/patchmatch_mat.dir/inpaint_mat.cpp.o
/home/sergey/PyPatchMatch/inpaint_mat.cpp: In function ‘cv::Mat inpaintPatchMatch_mat(cv::Mat, cv::Mat, int)’:
/home/sergey/PyPatchMatch/inpaint_mat.cpp:15:44: error: no matching function for call to ‘cv::Mat::Mat(IplImage*&)’
     cv::Mat output_mat = cv::Mat(output_img);
                                            ^
In file included from /usr/include/opencv2/core/mat.hpp:3518:0,
                 from /usr/include/opencv2/core.hpp:59,
                 from /usr/include/opencv2/opencv.hpp:52,
                 from /home/sergey/PyPatchMatch/inpaint_mat.hpp:1,
                 from /home/sergey/PyPatchMatch/inpaint_mat.cpp:1:
...

I have installed OpenCV as stated in the tutorial, and configured paths in setup.py. Is there anything else I am doing wrong?

Which OpenCV version are you using? I only test the project only in OpenCV 2.2.0.

Hi, thanks for your reply, but actually I do not remember what it was then:) I suppose, though, it was 3+, so it might be a resaon for crash.
Anyway, it is not actual as of now, and, if it seems nobody else faced this problem, we can close this issue


Update openshift to 4.17.0 and microshift to 4.16.14

/test e2e-crc

certificate rotation tests are failing which is a known failure in openshift ci


Added Details Struct and added Details Member to Amount struct

In using this module in our project at we encountered a situation where we needed to create payments that contained multiple products with different shipping costs for each. After studying the paypal documentation, the solution was to add the products as Items in the transaction and add the total shipping cost into the Details of the Amount object attached to the Transaction object. The module lacked that struct so i added it. I also added a example using this in the integration_test. In testing adding multiple transactions failed with paypal stating multiple transactions are not allowed.
Daniel @Blendtrix Development Team

Thanks you! Merging it!


Batch verification

Added VerificationInfo type to encapsulate verification result details

Work for #30

Will need to cleanup the status flags first (issue #37) and research how errors should be represented for batch verification and multiple signatures within all operations.

Closing in favor of #47
Batch verification will be merged into normal function definition to accept multiple RequestInfo


chore: certinia rebrand

Description
Changes various instance of FinancialForce to Certinia
Type of change

[X] Chore

Changes

[x] Copyrights
[x] logo + brand color
[ ] screenshots + gifs
[ ] publisher?

fixes # / resolves #

We need to update the install screen shot too, but that can only be done after we release the extension with the updated logo.


[Packager] require('react-native') must be assigned to React

By accident I have assigned require('react-native') to a variable other than React and It failed to execute. hmmm...
This code works fine
var React = require('react-native');

var {
  Component,
  View
} = React;

class MyApp extends Component {
  render() {
    return (
      <View></View>
    );
  }
}

module.exports = MyApp;

By this one doesn't
var Test = require('react-native');

var {
  Component,
  View
} = Test;

class MyApp extends Component {
  render() {
    return (
      <View></View>
    );
  }
}

module.exports = MyApp;

Here's what I got as an error:

:+1:

After some digging I found that JSX transformer is the root cause.
Here's an example:
var Test = require('react-native');
...

render() {
    return (
        <View></View>
    );
}

is compiles into
return (
    React.createElement(View, null)
);

even though I required react-native to Test, JSX compiler doesn't really care and uses React object to create the View element.

What use case do you have for using a name other than React? While this isn't ideal I don't think it is really a big issue either :smile: cc. @frantic.
@alinz - If you want to look into it and submit a PR that would be great.

@brentvatne I don't have any! I wish I had one! ;)
I don't know whether this PR would be beneficial for anyone, but challenge accepted! :+1:

We don't intend to support this in the JSX transformer, sorry. We require that you have React in scope.


Reorder sentences, fix typos

Reorder sentences to make paragraph coherent, fix typo

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thanks for the PR @anhnguyen300795, but I think this makes it more difficult to understand so I am closing it. We welcome future PR's from you, thanks and happy coding!


chore: upgrade bytes to 1.x

I am upgrading tokio/bytes of ckb to 1.x, ckb-vm should be upgraded accordingly, including the current 0.19.x
Do I need another PR for the release branch?

I will cherry-pick this PR to the release branch to ensure that the changes to develop and release branches are consistent, so you don’t need to post another PR.

@xxuejie request for a like


In master EnsembleSampler.sample is only yielding every thin steps.

On L289 in ensemble.py EnsembleSampler.sample only yields (and stores) position every thin steps. The previous behaviour (e.g. 93d464581aa3fdb071e035502dadc9f792cc3b66) was to yield position at every step and store every thin steps.
Is this a mistake, or on purpose?  I like the original behaviour of yielding every step, it makes it easier to follow progress with long running simulations as one knows precisely how many steps have been run. It also makes it easier to checkpoint.  For example:
for results in sampler.sample(pos0, 99, thin=100):
    pass

At the end results will be None because the number of steps never reached 100 and there are 99 wasted steps because the last position was never stored and it wasn't yielded to the user.  Even if EnsembleSampler doesn't store a step (because it never reached thin), if it returned the position at every step the user wouldn't have wasted those steps for nothing.
With the current behaviour iteration progress is also degraded. For example, in a simulation with 500 steps and thin=100 you only know to the nearest 1/5 how many steps you have done. Yielding every step enables fine grain counting. There are many circumstances where one wouldn't want to use a tqdm progress bar. Fine grain is important if each step takes a long time. One has to be able to predict this to request a total Wall time on a supercomputer.
The docstring in both the former and current code is ambiguous. On the one hand it says At each iteration, this generator yields:, indicating there is a yield every iteration. On the other hand it says If you only want to store and yield every ``thin`` samples in the chain, set thin to an integer greater than 1.
I propose the following:
thin (Optional[int]): If you only want to store every ``thin`` samples in the chain, set thin to an integer greater than 1.

and revert L238-245 in ensemble.py to yield every iteration. It also keeps backcompat.
I'm willing to write a PR for this.

The indenting creating this issue was performed in commit https://github.com/dfm/emcee/commit/4a390cb. The commit message was adding contributors, and doesn't give any other information as to why the change was made.

Thanks for them comment. This was on purpose - the old behavior had been considered a bug for a long time and it was the topic of several pull requests and issues. I'll make sure the docstring is consistent when the release comes. Thanks for the heads up!
Your comment gave me a good idea about the interface that I'll comment on when I'm at my computer.

For the sake of compatibility with existing code that was built around what thin has historically done, can thin retain its current meaning and a new parameter instead be used (yield_period or something, but naming things is hard)? That way, users can do all sorts of fun stuff with the chain without having to store every single step.

That's a good suggestion. I'll work on naming and interface to try to make something satisfying to all of us.

@willvousden can PTemcee follow any new behaviour that EnsembleSampler.sample uses please (when the final behaviour is settled)?

@andyfaff @llimeht I'm working on updating this syntax. For reference, if either of you have specific use cases where the current definition of thin is used, can you point me to it? I'm just having a hard time imagining why it would be used. Thanks!

Most of the issues are caused by back compatibility.  I'll recap those.

we currently incrementally save steps to file, keeping the file the same as EnsembleSampler.chain. This was done by writing pos after sample had yielded, but only every nthin steps (we needed to keep track of the number of steps). With new emcee the sampler takes care of that. If we use the same code across both old-new versions then the new version would be thinned by N**2 rather than N.
I'd prefer to use one set of code to deal with new/old emcee versions. Perhaps that could be done by keeping track of the number of iterations. The old EnsembleSampler had an iterations attribute, the new one doesn't.
we kept track of steps carried out by the number of yields from sample (providing it to a progress bar). If we don't make any changes this may be out by a factor of nthin depending on whether the new/old version is installed. yielding every step meant that our progress bar was updated in realtime (if a step takes 30 sec, then yielding every 10 steps means an update is only seen every 5 mins). There is a tqdm progress bar in new version. However, if one wants to provide a progress bar across the new & old versions we have to do it ourselves. A design question for you - shouldn't the progress bar be left to be implemented by the user (VISION.md)?
by yielding every step one is able to keep track of the exact state of the sampler. With the new behaviour you can lose up to steps % nthin steps if the sampling is interrupted.  If your sampling is not so fast and you're working interactively on a PC that is a bit more annoying.

I suppose the first two issues can be circumvented by seeing if the EnsembleSampler has an iterations attribute. If it does, then that specifies the number of iterations. If it doesn't then np.size(chain, -2) (trying to accomodate PTSampler as well) can be used to see what the iterations are.

Just seen that 'new' emcee has EnsembleSampler.iteration, whilst the old emcee has EnsembleSampler.iterations.  Confusing, the two aren't the same, and they're related by a factor of nthin.

It's probably easier for my project in the long run to use requirements.txt (or some such) to specify emcee >=3. Then I don't have to worry about compatibility any more.
(Just as long as there is a pypi / conda-forge release).

Thanks for the info. I'll keep you posted. It seems like, for your use case, you could just always use thin=1 and store=False to get the same behavior that you want.
iterations was never exposed or meant to be a public attribute so I'm not worried about supporting that long term :wink:
The old behavior of thin will be supported in the next release with a deprecation warning.
The progress bar was requested enough (and I like it enough now that tqdm exists) that I decided that it was reasonable to add it.

I did quite a lot of work on my project over the past week and I think I
can now cope with a yield every thin steps (and deal with the difference
between old and new). It was a shock to the system when I saw the change.
However if you want to keep what's currently in master it's OK with me.
BTW,  if you'd like a hand with development I'd be happy to help where I
could and if time permitted.
On 2 Nov 2017 6:23 am, "Dan Foreman-Mackey"<EMAIL_ADDRESS>wrote:

Thanks for the info. I'll keep you posted. It seems like, for your use
case, you could just always use thin=1 and store=False to get the same
behavior that you want.
iterations was never exposed or meant to be a public attribute so I'm not
worried about supporting that long term 😉
The old behavior of thin will be supported in the next release with a
deprecation warning.
The progress bar was requested enough (and I like it enough now that tqdm
exists) that I decided that it was reasonable to add it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dfm/emcee/issues/238#issuecomment-341212063, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAq51rHu0Yihl2tylkEtxReEJlMQ5udzks5syMUigaJpZM4QCPt5
.

@andyfaff Sure thing.  I'll wait a little while for the dust to settle before changing anything, though.


Import parsing pulls in commented out imports

for example a file that looks like
// import colors from '../colors';
import Dropdown from '../Dropdown';

will try to include both colors and Dropdown in the codesandbox when only Dropdown is being used.

Thanks for raising this!
Because we are currently using regex to match imports, determining whether an import is in a comment (or in a string) is near impossible, for example:
/*
import colors from '../colors'
*/

we need a solid way to detect they are in a comment block.
I've got a task to look at the cost of using babel to parse files instead of regex matching for imports, as it would allow us to be way more reliable about edge case matches. Will update this issue once I have a clear idea of the cost/benefits of moving to full AST parsing.


Support TCP_CONGESTION socket option

TCP_CONGESTION is a socket option to choose which tcp congestion control algorithms to use for the socket, which is supported on Linux(since 2.6.13) and FreeBSD(since 9.0).
I wonder would you like to have this socket option in this crate? If so, I would like to contribute this since I have tried to implement it.
While implementing this feature, a string-like(here I choose &str) algorithm name should be passed to the setsockopt function(for example, "reno").
However, while simply convert the name to &[u8] and pass it to the wrapper function setsockopt, the inner calculation of length for this(mem::size_of::<T>) can not have the right value(i.e., true length is 4 while mem::size_of:: gives 16).
Thus, I now implement it with raw syscall! and I wonder if there is a better way to do this?

TCP_CONGESTION is a socket option to choose which tcp congestion control algorithms to use for the socket, which is supported on Linux(since 2.6.13) and FreeBSD(since 9.0).
I wonder would you like to have this socket option in this crate? If so, I would like to contribute this since I have tried to implement it.

This addition would be welcome.

While implementing this feature, a string-like(here I choose &str) algorithm name should be passed to the setsockopt function(for example, "reno"). However, while simply convert the name to &[u8] and pass it to the wrapper function setsockopt, the inner calculation of length for this(mem::size_of::<T>) can not have the right value(i.e., true length is 4 while mem::size_of:: gives 16). Thus, I now implement it with raw syscall! and I wonder if there is a better way to do this?

mem::size_of returns the memory size of the a type, in this case &str and &[u8] both are a pointer and a length, so 2 * 8 bytes = 16 bytes on 64 bit. What you're looking for is the length of the string/bytes which you can get by calling .len() on the string/byte slice.
However I don't think you want to use &str or &[u8] but std::ffi::CStr, since C expects a C string (i.e. null terminated).
Also please take a look at our contributing guide, Socket2 has some oddities due to our low level nature.

Thank you for your reply, sure I will send a pr when ready.

mem::size_of returns the memory size of the a type, in this case &str and &[u8] both are a pointer and a length, so 2 * 8 bytes = 16 bytes on 64 bit. What you're looking for is the length of the string/bytes which you can get by calling .len() on the string/byte slice.
However I don't think you want to use &str or &[u8] but std::ffi::CStr, since C expects a C string (i.e. null terminated).

What I concerns is that the wrapper provided by socket2 crate itself has the implementation like this:
/// Caller must ensure `T` is the correct type for `opt` and `val`.
pub(crate) unsafe fn setsockopt<T>(fd: Socket, opt: c_int, val: c_int, payload: T,) -> io::Result<()> {
    let payload = ptr::addr_of!(payload).cast();
    syscall!(setsockopt( fd, opt, val, payload, mem::size_of::<T>() as libc::socklen_t,))
    	.map(|_| ())
}

But I have to pass the true length of the string(i.e., CStr or whatever) to the setsockopt which can be acquired by calling .len(). So it seems the wrapper cannot achieve this requirement?
By now, in my experimental implementation, I have to directly call the syscall macro like syscall!(setsockopt( fd, opt, val, payload, len,)).map(|_| ()) in set_tcp_congestion function. Thus I wonder is this accepted or are there other methods to solve it?

Thank you for your reply, sure I will send a pr when ready.

mem::size_of returns the memory size of the a type, in this case &str and &[u8] both are a pointer and a length, so 2 * 8 bytes = 16 bytes on 64 bit. What you're looking for is the length of the string/bytes which you can get by calling .len() on the string/byte slice.
However I don't think you want to use &str or &[u8] but std::ffi::CStr, since C expects a C string (i.e. null terminated).

What I concerns is that the wrapper provided by socket2 crate itself has the implementation like this:
/// Caller must ensure `T` is the correct type for `opt` and `val`.
pub(crate) unsafe fn setsockopt<T>(fd: Socket, opt: c_int, val: c_int, payload: T,) -> io::Result<()> {
    let payload = ptr::addr_of!(payload).cast();
    syscall!(setsockopt( fd, opt, val, payload, mem::size_of::<T>() as libc::socklen_t,))
    	.map(|_| ())
}

But I have to pass the true length of the string(i.e., CStr or whatever) to the setsockopt which can be acquired by calling .len(). So it seems the wrapper cannot achieve this requirement?

Correct, the wrapper is for code that mostly uses c_int.

By now, in my experimental implementation, I have to directly call the syscall macro like syscall!(setsockopt( fd, opt, val, payload, len,)).map(|_| ()) in set_tcp_congestion function. Thus I wonder is this accepted or are there other methods to solve it?

Calling it directly is fine. Maybe we can make another version where the length is passed, but that's just the same as use syscall!(setsockopt(...)) directly.


windows 10 service disabler.ps1

this will be the last version of the script the last one
old pull requests:https://github.com/Sycnex/Windows10Debloater/pull/397

this is the lates version of my script

this is the latest version of my script

I'm unsure what you're trying to do with lines 127-141. It looks like some services are being looked to see if they're stopped, and if so, then stop them? Are you trying to instead see if they're enabled and then stop them?
Couldn't you also just add the HyperV services as well as the HP services into the original array starting on line 5?
These are some suggestions.

uh i did all the changes


The project is full of useless comments and unformatted code so I want to PR these two commits

Since most of the comments don't explain anything new pls accept this PR.
Thanks

This is crazy. Unreal that we need these types of PR in GitHub.com

We are all in agreement! How cute is that!
@fcywpo what do you think about this? Wanna hear your response soon.
Bye.

This pull request includes several minor changes to the file/src/banca.java file, primarily focused on code cleanup and removing unnecessary comments. The most important changes are grouped by theme below:
Code Cleanup:

Removed unnecessary comments explaining straightforward code operations, such as variable assignments and control flow structures. [1] [2] [3] [4] [5]

Formatting:

Removed extraneous blank lines to improve the readability and consistency of the code. [1] [2] [3] [4] [5] [6] [7]


503 error

Very often I get a 503 Service Not Available error when loading web page. The page doesn't load at all, or it loads partially and doesn't work as intended. If I load this website through normal Google Chrome, everything works correctly (sometimes the server gives this error, but the page either fully loads or does not load at all - there are no situations when some resources did not load with a 503 error and the page does not work as expected).
await new BrowserFetcher().DownloadAsync();
Browser browser = await Puppeteer.LaunchAsync(new LaunchOptions {
 Headless = true,
 Product = Product.Chrome,
 IgnoreHTTPSErrors = true
});

Page page = await browser.NewPageAsync();
await page.GoToAsync(pageUrl);

Puppeteer-Sharp relies heavily on Chromium features.
Some bugs are caused by puppeteer, but others can be caused by chromium.
This sounds like a chromium issue. You can report those issues here.


OpenSSL 1.0.2 parallel make during Configure can disable tests

Repro instructions:
$ MAKE='make -j8' ./config
Normally, in Configure, 'make links' creates symlinks for the unit tests from their respective directories to test/. Thereafter, 'make gentests' links tests of disabled features to dummytest.c.
With parallel make, 'make links' and 'make gentests' race.and where 'make gentests' gets first, it links the tests to dummytest.c.
Unlike https://github.com/openssl/openssl/issues/298, this is a completely silent failure. The tests will appear to be passing but in fact no tests are run. So, I think that this should be fixed even if changing the 1.0.2 build to fully support parallel make would be too invasive of a change.
Attached the start of a Configure log with parallel make:
DES_UNROLL used
DES_INT used
RC4_CHUNK is unsigned long
created directory 'include'
generating dummy tests (if needed)...
created directory 'include/openssl'
make[1]: Entering directory 'openssl/test'
bntest.c => dummytest.c
e_os2.h => include/openssl/e_os2.h
ecdhtest.c => dummytest.c
ideatest.c => dummytest.c
ectest.c => dummytest.c
ecdsatest.c => dummytest.c
md4test.c => dummytest.c
hmactest.c => dummytest.c
wp_test.c => dummytest.c
making links in crypto...
md2test.c => dummytest.c
md5test.c => dummytest.c
make[1]: Entering directory 'openssl/crypto'
make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
rc2test.c => dummytest.c
rc4test.c => dummytest.c
sha1test.c => dummytest.c
rc5test.c => dummytest.c
destest.c => dummytest.c
shatest.c => dummytest.c
dhtest.c => dummytest.c
randtest.c => dummytest.c
mdc2test.c => dummytest.c
rmdtest.c => dummytest.c
crypto.h => ../include/openssl/crypto.h
opensslv.h => ../include/openssl/opensslv.h

Gotcha.  The easy fix is to make sure those targets get a make call each.  PR coming up.

Have a look at #2332


feat: support confirmation of initial image baselines

Is your feature request related to a problem? Please describe.
Currently, the first run of a new image match defines the baseline and passes by default.
I would like a behavior, where a test fails, if no baseline was explicitly defined yet. This enables developers to double check their initial test setup and not commit faulty tests.
It also enables a nice workflow, where I as a developer can write a test for my feature or change and confirm it with another stakeholder.
Describe the solution you'd like
I'd like to introduce a configuration e.g 'autoCreateBaseline'. On true, the current behavior should apply. But if set to false, a test should fail, if no baseline exists for matchImage.
Describe alternatives you've considered
Right now, the best alternative is to check your version control for newly created baselines, but it doesn't force developer to check it.
Additional context
Personally, I'd suggest to disable this behavior by default in the future, because this ensures a cleaner test development flow and follows a more test driven methodology where tests are supposed to fail initially until implemented.
I do understand that visual regression tests are most often added in the end, when the ui is mostly fixed, which might be a reason why acceptance is the desired default for most.
Although, even in that case, I think a explicit verification is good practice, as it helps to spot bugs.
If you like this option, I'd be happy to provide a PR for it. Really loving the plugin ❤

Hey @goatfryed 👋
Thank you for filing this issue - the feature you have described sounds indeed like a reasonable addition!
Name of the option you've proposed autoCreateBaseline also sounds good and descriptive, I think we can go with it. You're more than welcome to provide a PR if you're able - I'm currently sick, so it's hard for me to spend as much time as I would like on development of this library.
But I would not recommend to change the default behaviour for now. We might think about it for the future though. From my perspective - I've worked with multiple libs/platforms for visual regression testing and none of those had baseline images generation disabled by default. Also your ticket is the first one that references this issue, so I'm not sure if that is a sensible default for whole community.
In the future I'm thinking about providing few more features to this library - for example ready-to-be-used github action that would enable more automated workflows and encourage good practices for our users. Then we might also a breaking change like this and just change the default behaviour 🙂

Hey @goatfryed - I have just created a PR with createMissingImages option which I believe resolves your use case. Would you mind having a look at this PR and giving me feedback if that's what you have had in mind?

Hey @FRSgit,
First of all sorry for being unresponsive on this one. Thank you a lot for your time and effort you put into this plugin and for following up on my request.
Yes, that looks great. That's exactly what I had in mind. 👍


Setup tests w/o GPU

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@7fd9a9f). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master      #7   +/-   ##
========================================
  Coverage          ?   0.00%
========================================
  Files             ?       2
  Lines             ?     116
  Branches          ?       0
========================================
  Hits              ?       0
  Misses            ?     116
  Partials          ?       0

Flag
Coverage Δ

#unittests
0.00% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


[blocker]splunk_eventgen processes crash under multiprocess mode

Describe the bug
most of processes crashed after ~3 hrs running in eventgen multiprcess mode(20 processes)
env:
8 indexers, es bundle, 2 egx nodes, 750G perdayvolume per egx node.

2019-05-20 07:40:03 eventgen        ERROR    MainProcess
Traceback (most recent call last):
File "/opt/splunk/etc/apps/SA-Eventgen/lib/splunk_eventgen/eventgen_core.py", line 335, in _worker_do_work
item = work_queue.get(timeout=10)
File "", line 2, in get
File "/usr/lib/python2.7/multiprocessing/managers.py", line 759, in _callmethod
kind, result = conn.recv()
EOFError
Note: we are not using SA-Eventgen, SA-Eventgen/lib is just a dir location for checkout eventgen 6.3.4 code.

From the image, the 2 egx instances crashed one after one at nearly the same time. After manually restarted, they crashed again after similar time period.

root      55539  16260  0 07:33 pts/1    00:02:14 python /opt/splunk/etc/apps/backend/eventgen_server.py --eventgencmd /opt/splunk/etc/apps/SA-Eventgen/lib/splunk_eventgen
root      55561  55539 35 07:33 pts/1    02:02:41 python /opt/splunk/etc/apps/SA-Eventgen/lib/splunk_eventgen/main.py -v generate /opt/splunk/etc/apps/datamix/app/defa
root      55566  55561 99 07:33 pts/1    06:20:00 [python] <defunct>
root      55681  55561 27 07:33 pts/1    01:35:10 [python] <defunct>
root      55682  55561 27 07:33 pts/1    01:36:06 [python] <defunct>
root      55687  55561 27 07:33 pts/1    01:35:11 [python] <defunct>
root      55692  55561 27 07:33 pts/1    01:35:31 [python] <defunct>
root      55697  55561 27 07:33 pts/1    01:35:28 [python] <defunct>
root      55701  55561 27 07:33 pts/1    01:36:08 [python] <defunct>
root      55705  55561 27 07:33 pts/1    01:36:39 [python] <defunct>
root      55709  55561 27 07:33 pts/1    01:35:20 [python] <defunct>
root      55714  55561 27 07:33 pts/1    01:36:19 [python] <defunct>
root      55719  55561 27 07:33 pts/1    01:36:21 [python] <defunct>
root      55724  55561 27 07:33 pts/1    01:35:54 [python] <defunct>
root      55730  55561 27 07:33 pts/1    01:35:38 [python] <defunct>
root      55734  55561 27 07:33 pts/1    01:36:20 [python] <defunct>
root      55739  55561 27 07:33 pts/1    01:36:19 [python] <defunct>
root      55744  55561 27 07:33 pts/1    01:36:40 [python] <defunct>
root      55749  55561 27 07:33 pts/1    01:36:09 [python] <defunct>
root      55754  55561 27 07:33 pts/1    01:35:29 [python] <defunct>
root      55762  55561 27 07:33 pts/1    01:35:49 [python] <defunct>
root      55767  55561 27 07:33 pts/1    01:36:24 [python] <defunct>
root      55771  55561 27 07:33 pts/1    01:36:29 [python] <defunct>

1 idx, index=main, 100G per node(actual 200), 1 egx node, not crash in 5 hr
1 idx, index=main, 750G per node(actual 1.5T), 1 egx node, not crash in 5 hr
8 idx, index=8*, 750G per node(actual 1.5T), 2 egx node, both crashed in 2.5hr, reproducible
8 idx, index=8*, 750G per node(actual 1.5T), 1 egx node, started
it issue need more investigation to figure out what are the main factors that cause the crash

1 idx, index=main, 100G per node(actual 200), 1 egx node, not crash in 5 hr
1 idx, index=main, 750G per node(actual 1.5T), 1 egx node, not crash in 12 hr
8 idx, index=8*, 750G per node(actual 1.5T), 2 egx node, both crashed in 2.5hr, reproducible
8 idx, index=8*, 750G per node(actual 1.5T), 1 egx node, crashed in 3.5 hr, reproducible
it issue need more investigation to figure out what are the main factors that cause the crash
looks like the crash is related to output module, as logger issue and multiprocess issue are fixed in develop branch, i'll try develop branch to see why the output worker crashes

Thank you Yifeng for the reporting and debugging.

this crash can be reproduced in 6.3.6 latest and no additional logs found

error.log
attached logs found from verbose mode stdout. All the crashes might be related to https://stackoverflow.com/questions/3649458/broken-pipe-when-using-python-multiprocessing-managers-basemanager-syncmanager

I disabled logging queue and run CLI with multiprocess, it kept running 7 hrs and didn't crash. Keep monitoring
            self.loggingQueue = None #self.manager.Queue()
            #self.logging_pool = Thread(target=self.logger_thread, args=(self.loggingQueue, ), name="LoggerThread")
            #self.logging_pool.start()

    @staticmethod
    def _proc_worker_do_work(work_queue, logging_queue, config):
        genconfig = config
        stopping = genconfig['stopping']
        #qh = logutils.queue.QueueHandler(logging_queue)
        root = logging.getLogger()
        root.setLevel(logging.DEBUG)
        #root.addHandler(qh)

not crashed in 1 day, i'll file a commit to disable logging queue in multiprocess mode as it is possibly a python bug

Here is the result of one day running


not working on youtube tab

Description
Reproduction steps

Step 1
Step 2
....

Environment

TabFloater version:
Companion version:
Operating system:
Browser:
Companion installation:

Hi,
It does work for me. Please fill out the issue template and describe the problem properly.
Thanks

Hmm I suspect the issue is with the special characters in the youtube video's title. But I just tried it and it does work for me. If you can reliably reproduce it, please let me know the steps and I can take a look.
thanks


Angular Form Properties not affected when selecting a date

As topic states the form properties is not affected when I choose a date (Google Chrome Version 50.0.2661.86 (64-bit))
Here's what I am trying to do:
        <form name="form">
                <input ng-model="model"
                       name="dateTime"
                       datetime-picker
                       date-format="yyyy-MM-dd HH:mm:ss"
                       close-on-select="true" />
            {{ message }}
        </form>

The message only shows if I manually make some input to the field, not when choosing a date from the datetime-picker

Try :
{{ message }}

Thanks for the input but I get the same result.

We are seeing the same issue. I made a small change that seems to work but I do not know if this is the best fix. Any thoughts?
var datetimePicker  = function($parse, DatetimePicker) {
    return {
      // An ngModel is required to get the controller argument
      require: 'ngModel',
      link: function(scope, element, attrs, ctrl) {
        // Attach validation watcher
        scope.$watch(attrs.ngModel, function(value, old) {
          //force dirty on update
          if (value !== old) {
            ctrl.$setDirty();
          }

Thank you @ryan-morris for your input, it works. I'm not sure if it's the right way to do it either but I will use it until further notice.


Start with current place location

Hi!
I have 2 fields in my app, origin and destiny with location use, and I want the first one to come with the initial location already populated.
Is it possible to do this in the module, passing latitude and longitude?
Example in image below
Regards

I'm also looking forward to this


Fix backup and restore functionality

Fixes #3700 #3923

[x] CHANGELOG.md updated
[x] Rebased/mergable
[x] Tests pass
[x] Sign CLA (if not already signed)

I didn't fix the backup/restore test.

will this land for 0.9.5?

@esecules 0.9.5 will not ship unless backup/restore works. No opinion on this particular PR, but @pauldix himself promised me backup would get the needed attention before 0.9.5 final is cut.

Glad to hear that, since backup is a tad bit important ;)

@saward backups are nice, but it's the restore that counts ;)

Hi, backups can be done to an AWS S3 bucket?

@mjabrandao we plan to do backups to S3 via s3fs mounting after the 0.9.5 is released.

I actually believe we covered this in another PR.
Thanks for your contribution @Pomyk -- let us know if you do not think we're OK now.

@beckettsean Hi, I don't find this change it in Changelog, will backups be corrected with another PR ?
(I only see the #4643 restore-related bugfix).

@ORANGE-XFM there were too many issues with tsm1 for it to be declared production ready, but there were also too many accumulated bug fixes and performance improvements to delay 0.9.5 any longer. While the intention was to only release it once tsm1 and backups were working, that proved too optimistic.

@beckettsean So we have no working backup right now? That must be written in docs.

@beckettsean Hi Sean, in fact my point was that we shoudl state in the changelog that this issue seems to have been fixed indeed ! (communicating that backups are working in the changelog)

Has somebody verified working backups in 0.9.5 stable with same dataset (which failed on <=0.9.4)?

I succeeded backing up a DB with 0.9.5 which failed in <IP_ADDRESS>, but that may not be a good validation for something as important as backups.

The restore is still not working for me with 0.9.5 stable, as per #4806

The only way to currently back up the DB is to copy the underlying files. Meaning to do it safely, it's offline only. This slipped because the new storage engine is still under development and we were going to put this there.
However, we may be able to take a look at this sooner for the older storage engines. I'll leave #4806 open and we can go from there.


Alphabetize Json files

The strings in core have recently been alphabetized and it would be helpful to do the same here prior to bringing over release PRs. This will help to differentiate the lines that have changed line location versus those that are updated or different in core.
Technical Notes:
command + shift + p --> sort lines ascending
QA Notes: https://staging.housingbayarea.mtc.ca.gov/
Spot check staging translations to make sure nothing wonky happened in using the command

Suggestion that came up during lottery -
We should do this in Doorway and HBA before we pull over changes
It will make it really hard to keep track of unique changes

I think this looks ok ! I just did a spot check.


fix: normalize file paths (#993)

Pretty simple fix but appears to resolve this. Tagging @emilgedda for testing and @cseickel / @pysan3  for review :)

This is so straightforward I think we can just merge it to main and let it be tested there.


Support Typed Nested Form Data

I think one could do this by switching from serde_urlencoded to serde_qs here. Or by allowing the user to pick between the two somehow.
Not sure how popular nested form data is but I ran into this when using the Stripe API.

Might be able to have a form_nested() func using serde_qs ?
@seanmonstar What do you think about this ? Maybe also "hidding" it under a feature flag for the crate ?

There isn't a standardized way to present sequences in form-data. As hinted in https://github.com/nox/serde_urlencoded/issues/52, you might expect color=[red, blue] or color[]=red&color[]=blue. However, it's not complicated to serialize using serde_qs or serde_querystring etc, and call .body(bytes) afterwards.


Latest version flunks OWASP vulnerability check

Expected Behavior

It should pass OWASP.
Current Behavior

One or more dependencies were identified with known vulnerabilities:
gradle-api-5.4.1.jar (shaded: org.apache.commons:commons-compress:1.18): ids:(org.apache.commons:commons-compress:1.18, cpe:/a:bzip:bzip2:1.18) : CVE-2005-1260
Context

We have to work with our appsec team to explain why they should whitelist this, and they don't wanna, and asked back why this vulnerability is in the apex release of a project as important as gradle, and we don't have a good answer to that.
Also, because the jar is apparently shaded, it makes it even more difficult to assure appsec that all is well, because they can't even know for sure which classes actually comprise the jar.
Steps to Reproduce

Get latest gradle (5.4.1). Run OWASP on it. We do that by including an OWASP plugin in the  dependencies in the buildscript section:
classpath group: 'org.owasp', name: 'dependency-check-gradle', version: '<IP_ADDRESS>'
and then specifying:
apply plugin: 'org.owasp.dependencycheck'
Really though, you should just wire OWASP into gradle's own build script, so you're the first to find out about about these kinds of problems (and I see this has been requested in a number of filed issues).
Your Environment

Build scan URL:
Linux 64 bit, but it really doesn't matter. This would fail the same way on Android, Windows, or whatever you run it on.

@jimshowalter: This "vulnerability" is clearly a false positive. The version 1.18 of "commons-compress" was released by mid of 2018 whereas the CVE was published in 2005.
You can also see that the CVE is connected to CPE "bzip2". What is meant here is the program "bzip2" and not "commons-compress". This is another sign that this is a false positive.
All in all you should open a bug ticket for your vulnerability scanner and not for Gradle.
And final last hint: You're using a quite outdated version of the "dependency-check-gradle" plugin. Maybe with the latest version this false positive is gone.

Thank you for the response! After updating the configuration, the problem went away. This is a plugin I inherited, but should have look into version upgrades first.


RemovedInDjango20Warning - import of urls

Need to update how url imports are called, etc.
Thought I would put this up now so its "on the radar" as 2.0 will be here soon, and I'd love to be able to switch smoothly from 1.11 to 2.0 on my latest project.
Thanks!

This should work with 1.7. Please test and reopen if you encounter any problems. Thanks!


error while loading images

hello
Im using your implementation for training VisDrone with RCNN-FPN-CROP.yaml config file.
After reading annotation succesfully, I got this error while Im sure my data directory is like you mentioned in your repository.
its just before start to train...........
help me please.
thank you.
Traceback (most recent call last):
File "train_net.py", line 94, in
launch(
File "../Detectron2/lib/python3.8/site-packages/detectron2/engine/launch.py", line 84, in launch
main_func(*args)
File "train_net.py", line 85, in main
return trainer.train()
File "../Detectron2/lib/python3.8/site-packages/detectron2/engine/defaults.py", line 484, in train
super().train(self.start_iter, self.max_iter)
File "../Detectron2/lib/python3.8/site-packages/detectron2/engine/train_loop.py", line 155, in train
self.run_step()
File "../DroneDetectron2/croptrain/engine/trainer.py", line 135, in run_step
data = next(self._trainer._data_loader_iter)
File "../Detectron2/lib/python3.8/site-packages/detectron2/data/common.py", line 291, in iter
for d in self.dataset:
File "../.local/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 521, in next
data = self._next_data()
File "/home/.local/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1203, in _next_data
return self._process_data(data)
File "/home/.local/lib/python3.8/site-packages/torch/utils/data/dataloader.py", line 1229, in _process_data
data.reraise()
File "/home/.local/lib/python3.8/site-packages/torch/_utils.py", line 434, in reraise
raise exception
AttributeError: Caught AttributeError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "/home/.local/lib/python3.8/site-packages/torch/utils/data/_utils/worker.py", line 287, in _worker_loop
data = fetcher.fetch(index)
File "/home/.local/lib/python3.8/site-packages/torch/utils/data/_utils/fetch.py", line 32, in fetch
data.append(next(self.dataset_iter))
File "../Detectron2/lib/python3.8/site-packages/detectron2/data/common.py", line 258, in iter
yield self.dataset[idx]
File "../Detectron2/lib/python3.8/site-packages/detectron2/data/common.py", line 95, in getitem
data = self._map_func(self._dataset[cur_idx])
File "../Detectron2/lib/python3.8/site-packages/detectron2/utils/serialize.py", line 26, in call
return self._obj(*args, **kwargs)
File "../DroneDetectron2/croptrain/data/dataset_mapper.py", line 62, in call
image = read_image(dataset_dict)
File "../DroneDetectron2/croptrain/data/detection_utils.py", line 18, in read_image
if len(image.shape) == 2:
AttributeError: 'NoneType' object has no attribute 'shape'
my dataset directory:

This is a silly path-related error, not an issue of this code base. In my train_net.py script, I am using a temp storage location of the HPC cluster we have.
https://github.com/akhilpm/DroneDetectron2/blob/main/train_net.py#LL49C9-L49C72
You just have to change it to the "data_dir"  to where you store the data.

@AI-AUT @akhilpm
Hello, I have encountered the same problem. I changed the “data_dir”,data_dir = "/home/xxx/Downloads/DroneDetectron2/croptrain/datasets/VisDrone",The files are right here,But the problem hasn't been solved,How did you solve it? Looking forward to your reply.


[feature] Support custom refresh intervals for each group of metrics

What's changed?

close https://github.com/apache/hertzbeat/issues/2188
Support custom refresh intervals for each group of metrics. The specific implementation is as follows:

Construct a cycle of job refresh interval list based on the refresh intervals of each metric.
When the job dispatches, select metrics that are due for refresh to form priorMetrics.

Checklist

[x]  I have read the Contributing Guide
[x]  I have written the necessary doc or comment.
[x]  I have added the necessary unit tests and all cases have passed.

@tomsun28 Hi, the stange problem mentioned here https://github.com/apache/hertzbeat/pull/2271#issuecomment-2232155864 has been solved.
According to the previous code, for jobs with multiple collection metrics, the metrics.setCollectTime execution time for metrics with a higher priority is somewhat delayed. This causes them to be missed during the selection of expired metrics in the next cycle, resulting in updates occurring every two cycles. so I move metrics.setCollectTime in constructPriorMetrics.

Customize collect intervals have been tested and there are no problem.

👍👍thanks LGTM, test passed. Since this involves basic scheduling, and we are preparing a new version, can we merge this major feature after the 1.6.1 release (maybe end of this month)?

I agree, we need to make this feature more stable before releasing it.

😄 When will this PR plan be merged? I need to use this feature.

When will this PR plan be merged? I need to use this feature.😄


Removed BIN as this can miss bruteforces spread across BIN windows

Fixes #
Removed the BIN, and replaced this with a check to see if the bruteforce occurred during a 20 min window.  This is now performed using datetime math instead.
Proposed Changes
In some instance, a bruteforce activity can occur that is of a short duration (< 20 mins) but it spans two BIN windows.  Because it spans two BIN windows, the detection rule will not fire.
For Example:
User A attempt 5 failed logins from 1:19 to 1:20.  This is across a duration of 1 minute but because of the BIN function, the 5 events will be split across two windows.  1:00 and 1:20.  Because of this, the threshold is not met.

@orhanmoye - Apologies for the delay in responding on this one.  We have had some other high priority items over the last several weeks that kept us away from review items.  We don't want to removing the bin concept in this, but agree that there is opportunity to miss.  For that, we think it best to use either Window functions or User Analytics.  Over the next few weeks we will investigate and share back.

No problem.  Thanks for the update.

Closing this as it is out of date now, we have made changes and are looking at one more change to help with the bin() size causing misses.  This will come in the next week.


Kali Sana login not wokring

Please paste the output of the following command here: sudo edit-chroot -all

name: sana
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/sana...
crouton: version 1-20160620130246~master:c39102d9
release: sana
architecture: armhf
xmethod: xiwi
targets: gnome,xiwi
host: version 8172.56.0 (Official Build) stable-channel daisy_spring
kernel: Linux localhost 3.8.11 #1 SMP Thu Jun 16 14:45:49 PDT 2016 armv7l GNU/Linux
freon: yes

Please describe your issue:
"Oh no! Someting is wrong" on login-screen:chronos@localhost / $ sudo startxiwi -n sana -F gnome-session
Entering /mnt/stateful_partition/crouton/chroots/sana...
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
X.Org X Server 1.17.2
Release Date: 2015-06-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-armmp-lpae armv7l Debian
Current Operating System: Linux localhost 3.8.11 #1 SMP Thu Jun 16 14:45:49 PDT 2016 armv7l
Kernel command line: cros_secure console= console= loglevel=7 init=/sbin/init cros_secure oops=panic panic=-1 root=/dev/dm-0 rootwait ro dm_verity.error_behavior=3 dm_verity.max_bios=-1 dm_verity.dev_wait=1 dm="1 vroot none ro 1,0 2506752 verity payload=PARTUUID=93a8c50a-bc62-4b44-b1d0-2999019148e3/PARTNROFF=1 hashtree=PARTUUID=93a8c50a-bc62-4b44-b1d0-2999019148e3/PARTNROFF=1 hashstart=2506752 alg=sha1 root_hexdigest=138be242822890dcac1cc888ce9409da6e009225 salt=c326d30f817d2c38a3d5466478925e5b8decb69b2c407dc0d51b19c5d66903a4" noinitrd vt.global_cursor_default=0 kern_guid=93a8c50a-bc62-4b44-b1d0-2999019148e3
Build Date: 01 July 2015  05:24:31PM
xorg-server 2:1.17.2-1 (http://www.debian.org/support)
Current version of pixman: 0.32.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/tmp/Xorg.crouton.2.log", Time: Sun Jun 26 18:44:00 2016
(++) Using config file: "/etc/X11/xorg-dummy.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
/usr/bin/xinit: XFree86_VT property unexpectedly has 0 items instead of 1
crouton: version 1-20160620130246~master:c39102d9
release: sana
architecture: armhf
xmethod: xiwi
targets: gnome,xiwi
host: version 8172.56.0 (Official Build) stable-channel daisy_spring
kernel: Linux localhost 3.8.11 #1 SMP Thu Jun 16 14:45:49 PDT 2016 armv7l GNU/Linux
freon: yes
Error: not connected.
Cannot connect to extension, retrying...
Error: not connected.
Cannot connect to extension, retrying...
Error: not connected.
Cannot connect to extension, retrying...
Error: not connected.
Cannot connect to extension, retrying...
Error: not connected.
Cannot connect to extension, retrying...
Error: not connected.
Cannot connect to extension, retrying...
Error: not connected.
Cannot connect to extension, retrying...
Error: not connected.
Cannot connect to extension, retrying...
Connected to extension, launched crouton in a window.
Error: target STRING not available
gnome-session-is-accelerated: No hardware 3D support.
gnome-session-check-accelerated: Helper exited with code 256
gnome-session-is-accelerated: No hardware 3D support.
gnome-session-check-accelerated: Helper exited with code 256
** (process:29588): WARNING **: software acceleration check failed: Child process exited with code 1
** (gnome-session-quit:29992): WARNING **: Failed to call logout: The name org.gnome.SessionManager was not provided by any .service files
socket_client_read_frame_header: Connection close from WebSocket client.
^C
Session terminated, terminating shell.../usr/bin/xinit: connection to X server lost
waiting for X server to shut down Hangup
``
If known, describe the steps to reproduce the issue:
sudo startxiwi -n sana -F gnome-session brings up the issue...

sana is apparently not supported anymore.


Minor tweaks to masking docs

Coverage remained the same at 77.404% when pulling 06108c58a7b253b59d635dda935b6c48603e5452 on keflavich:docs_minor into b8c6f3456206eb2d9879a5bc88d7c3979ed97d7d on radio-astro-tools:master.


(Question) Are key fobs compatible?

Are key fobs compatible with nuki_hub? Anything special that would be required or what are the limitations that don't allow them to be supported (if that is the case)?
What other options have you chosen as alternative? Keypad?

You pair the fobs with the lock and not NUKI Hub, in that sense they are compatible.
But if you're asking if you can pair the Fobs with NUKI Hub and get notified about key presses, the answer is no. NUKI Hub is working as a client that connects to the lock. To make it work with Fobs like that, it would need to simulate a lock, because the Fobs expect a lock to be paired with.
The same goes for the keypad, except the NUKI Hub allow to add and remove keypad codes. It does so however by talking to the lock, not to the keypad directly ... which makes a lot of sense because the codes are stored on the lock due to security concerns.


Remove buffer management calls from tokenizer

The following functions were deprecated in tokenizer as of version 1.2. They should be removed in 2.0.

jsonv::tokenizer::buffer_reserve (size_type sz)
jsonv::tokenizer::min_buffer_size ()
jsonv::tokenizer::set_min_buffer_size (size_type sz)

Removed tokenizer in efc80dc.


kob help - Suggestion

We regret for the issue that you are facing, Thanks for helping us by raising an issue so that we can improve ourself to do the best.
Mark one of the issues given below with respect to the issue you are facing with:

[ ] Issue facing with installation or setup of KOBman utility.
[ ] Issue facing while running an environment.
[ ] Issue facing while adding a new environment or new file.
[x] Other issues: please provide the issue in the comment box

Please explain the Issue / Feature Request here:
It would be better if the marked words are shifted to next line

Please provide the necessary screenshots or documents regarding the issue:

KOBman env installation & test script - Success

Aries env installation from wrong directory ( Just reporting )

Aries env installation & test script - Success


Add concurrency to create/update/insert benchmarks

Single threading benchmarking is interesting, but it is also necessary to understand how the system behaves in the face of multiple concurrent clients contenting the database.
This PR adds concurrency to the write path, while keeping operations distinct (i.e. no mixed create/update/delete load). While still a synthetic load, it can be considered "closer to reality".

We are limited in the output of the benchmark test if I remember correctly? We can't combine the results of say the create run, right?

As discussed on MM, we decided to change the naming of the tests as it was quite confusing.
We are keeping them separated so that we can see how it behaves under different kind of loads.

Why is our published benchmark test showing some gaps in the Before column in some places?

Because the matching is done on the name. The master branch only has:
Create/sqlite-4
Create/dqlite-4
Delete/sqlite-4
Delete/dqlite-4
Update/sqlite-4
Update/dqlite-4

While the new set has none of those and new ones. As such, they cannot be compared.
This is also the reason why #170 needs to be rebased once this is in (a merge would not work from the PoV of benchmarking).


Enter an extension in JavaScript asYouTypeFormatter

Hi,
is it possible to add an extension in javascripts asYouTypeFormatter on any position?
I want to use the extension to reflect direct call numbers inside f.e. companies.
Like:
+49 221 12345 ext. 0  <--- main number
+49 221 12345 ext. 10 <-- direct call for staff member x
+49 221 12345 ext. 20 <-- direct call for staff member y
This is more a visual benefits for the caller. But very often used i think. In Germany most time the direct call part is separated by a - (minus) and has no more then 3 digits.
With the library general its possible, but the asYouTypeFormatter doesn't support to enter an extension manually at random position.
Thanks and best regards
Rizzi

The as-you-type-formatter is designed for use in a dialler, where ext. like this isn't really supported. If you want to put the "-" in the as-you-type-formatter should just stop formatting for you? Anyway I'll close this as it's not an issue with the library. Please consider joining
the discussion group if you'd
like to discuss this further.


"Class cros does not exist"

HI
First of all thanks for this nice package . I am using lumen 5.5
i got this error
"message": "Class cros does not exist",     "code": -1,     "status_code": 500,
Here is the bootstrap file
`
$app->configure('cors');
$app->routeMiddleware([
'auth' => App\Http\Middleware\Authenticate::class,
'cors' => \Barryvdh\Cors\HandleCors::class,
]);
$app->register(Barryvdh\Cors\ServiceProvider::class);
`
But when i try to hit url i got this error
@barryvdh can you please help

I'm closing this due to inactivity. If you still encounter this issue on the latest version (2.0.1 at the moment), please open a new issue with detailed information.


Communications/Community/Marketing/Ecosystem liaison: Device/IoT t-shirt integration (TBD)

Oh love this idea, ive built a few IOT t-shirts over the years and can help on this one


🐛 [firebase_auth] Unable to connect to auth emulator from iOS simulator

Bug report
I'm an unable to use the Firebase Auth Emulator from an iOS app running on the iOS simulator. When any firebase_auth-related operation is executed, following exception is thrown: [firebase_auth/network-request-failed] Network error (such as timeout, interrupted connection or unreachable host) has occurred.
Steps to reproduce

Launch Firebase Emulator in your local machine
Enable the usage of the Auth Emulator in the iOS app:

await FirebaseAuth.instance.useAuthEmulator(
  '<IP_ADDRESS>',
  9099,
);

Perform any auth-related op, such as await _firebaseAuth.verifyPhoneNumber(...)

Expected behavior
No exception should be thrown and the emulator should work.
Additional context

Already enabled incoming and outgoing connections in Xcode
Already added following local networking permissions to Info.plist:

<dict>
  <key>NSAllowsArbitraryLoads</key>
  <true/>
  <key>NSAllowsLocalNetworking</key>
  <true/>
</dict>

Already tried localhost, <IP_ADDRESS>, <IP_ADDRESS>...
Firebase Emulator UI is accesible via Safari at localhost:4000 in the simulated device

Flutter doctor
Click To Expand
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.2.3, on macOS 11.4 20F71 darwin-arm, locale es-ES)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Xcode - develop for iOS and macOS
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.2)
[✓] VS Code (version 1.59.1)
[✓] Connected device (2 available)

• No issues found!```

Flutter dependencies
Click To Expand
Dart SDK 2.13.4
Flutter SDK 2.2.3
controlcenter 1.0.0+1

dependencies:
- async_redux 12.0.0 [logging path path_provider file weak_map fast_immutable_collections collection meta flutter]
- carousel_slider 4.0.0 [flutter]
- cupertino_icons 1.0.3
- faker 2.0.0 [crypto]
- firebase_analytics 8.2.0 [firebase_analytics_platform_interface firebase_analytics_web firebase_core flutter meta]
- firebase_app_check 0.0.1+3 [firebase_app_check_platform_interface firebase_app_check_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 3.0.1 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.4.0 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_crashlytics 2.1.1 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_performance 0.7.0+7 [firebase_core flutter]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_svg 0.22.0 [flutter meta path_drawing vector_math xml]
- get_it 7.2.0 [async collection]
- google_fonts 2.1.0 [flutter http path_provider crypto]
- logger 1.0.0
- mask_text_input_formatter 2.0.0 [flutter]
- phone_number 0.11.0+2 [flutter meta]
- pin_code_fields 7.3.0 [flutter]

dev dependencies:
- flutter_lints 1.0.4 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector characters charcode collection matcher meta source_span stream_channel string_scanner term_glyph typed_data]

transitive dependencies:
- async 2.6.1 [meta collection]
- boolean_selector 2.1.0 [source_span string_scanner]
- characters 1.1.0
- charcode 1.2.0
- clock 1.1.0
- collection 1.15.0
- crypto 3.0.1 [collection typed_data]
- fake_async 1.2.0 [clock collection]
- fast_immutable_collections 5.1.1 [collection meta]
- ffi 1.1.2
- file 6.1.2 [meta path]
- firebase 9.0.1 [http http_parser js]
- firebase_analytics_platform_interface 2.0.1 [flutter meta]
- firebase_analytics_web 0.3.0+1 [firebase firebase_analytics_platform_interface flutter flutter_web_plugins meta]
- firebase_app_check_platform_interface 0.0.1+3 [firebase_core flutter meta plugin_platform_interface]
- firebase_app_check_web 0.0.1+3 [firebase_app_check_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 6.0.0 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 3.0.0 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.0.1 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.1.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.1.0 [collection firebase_core flutter meta plugin_platform_interface]
- flutter_web_plugins 0.0.0 [flutter js characters collection meta typed_data vector_math]
- http 0.13.3 [async http_parser meta path pedantic]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- intl 0.17.0 [clock path]
- js 0.6.3
- lints 1.0.1
- logging 1.0.1
- matcher 0.12.10 [stack_trace]
- meta 1.3.0
- path 1.8.0
- path_drawing 0.5.1 [vector_math meta path_parsing flutter]
- path_parsing 0.2.1 [vector_math meta]
- path_provider 2.0.2 [flutter path_provider_platform_interface path_provider_macos path_provider_linux path_provider_windows]
- path_provider_linux 2.0.0 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_macos 2.0.0 [flutter]
- path_provider_platform_interface 2.0.1 [flutter meta platform plugin_platform_interface]
- path_provider_windows 2.0.1 [path_provider_platform_interface meta path flutter ffi win32]
- pedantic 1.11.1
- petitparser 4.1.0 [meta]
- platform 3.0.0
- plugin_platform_interface 2.0.1 [meta]
- process 4.2.1 [file path platform]
- sky_engine 0.0.99
- source_span 1.8.1 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- string_scanner 1.1.0 [charcode source_span]
- term_glyph 1.2.0
- test_api 0.3.0 [async boolean_selector collection meta path source_span stack_trace stream_channel string_scanner term_glyph matcher]
- typed_data 1.3.0 [collection]
- vector_math 2.1.0
- weak_map 2.0.2
- win32 2.2.5 [ffi]
- xdg_directories 0.2.0 [meta path process]
- xml 5.1.2 [collection meta petitparser]

Hi @Pitazzo
Are you able to connect to any of the emulators from iOS simulator?
Have you made sure the simulator and firebase emulator are on the same network?
Thank you

Hey @markusaksli-nc
Thanks for your quick reply. Answering your questions:

Are you able to connect to any of the emulators from iOS simulator?

Yes, I'm able to use Realtime Database emulator without any trouble using as address <IP_ADDRESS>

Have you made sure the simulator and firebase emulator are on the same network?

Absolutely, I can confirm that as Realtime Database simulator works fine and is provided by the same instance as the Auth emulator. Moreover, I can access to the Emulator UI from the emulated device browser.
I would like to add that I have been messing around with a physical Android device and I'm experimenting a similar issue: connection with other emulator such as a Realtime Database emulator works fine, but when I try to authenticate with SMS Auth against the Emulator, I get following error:
E/FirebaseAuth(13940): [SmsRetrieverHelper] SMS verification code request failed: unknown status code: 17499 Invalid authority field:[http:
E/flutter (13940): [ERROR:flutter/lib/ui/ui_dart_state.cc(199)] Unhandled Exception: type 'Null' is not a subtype of type 'String'
E/flutter (13940): #0      MethodChannelFirebaseAuth.verifyPhoneNumber.<anonymous closure>

The error message is different, but the  17499 Invalid authority field:[http: makes me suspect it could be somehow related (also networking stuff) and thus this issue could be broader and related with the emulator as a whole. Let me know if I should open a new issue or edit this one.

So just to be clear you have tried other auth methods than verifyPhoneNumber or other phone-related methods? Could you also npm i -g firebase-tools to the latest version just in case and comment the version.

Hey @markusaksli-nc, sorry for the delay in my response.

So just to be clear you have tried other auth methods than verifyPhoneNumber or other phone-related methods? If this is just related to phone auth using the emulator then I don't think it requires a separate issue.

Other auth related methods such as authStateChanges() lead to the same issue.

Could you also npm i -g firebase-tools to the latest version just in case and comment the version.

I'm using a dockerized version of firebase-tools, but I managed to force an update and check that following is the installed version:
{
  "dependencies": {
    "firebase-tools": "9.18.0"
  }
}

Well in this case I am not seeing the same issue and without being able to reproduce it seems like it shouldn't be coming from the plugin code. Because the issue isn't actionable for us I'm going to close it here but I recommend you send these logs and the strange unknown status code: 17499 to https://firebase.google.com/support
If it they say it could be coming from somewhere in our plugin code then I can reopen.


Fix varnames (no extra tuple)

Also remove test Manifest

Codecov Report

Merging #13 (872fa90) into main (6625479) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage   81.19%   81.19%
=======================================
  Files           7        7
  Lines         319      319
=======================================
  Hits          259      259
  Misses         60       60

Impacted Files
Coverage Δ

src/sparsevararray.jl
80.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 6625479...872fa90. Read the comment docs.


Development

fixes #11
fixes #21

Pursuit
Dependencies are updated
Added some comments
Removed unused by SlamSearch syntax symbols from reserved symbols list. (Except ( and ))
Fixed https://slamdata.atlassian.net/browse/SD-1081
Queries like >foo:bar or foo:!bar..baz couldn't be parsed. (They used to be parsed to incorrect SearchQuery)
Removed qualified, changed formatting a bit.

@garyb Please review

:+1: aside from the strongcheck dependency.

strongcheck dependency is moved, commits are squashed


Update Copy Authorization to throw checked exception

Update Copy Authorization to throw checked exception
Change asDouble to asFloat asper service team's guidance for 32-bit precision.

rerun the "npx embedme sdk//azure-ai-formrecognizer/README.md"

/azp run java - formrecognizer - tests