Improve GPU algorithm in FormDiscreteDivergenceMatrix

This small PR improves the algorithm used to form the discrete divergence matrix in the H(div) saddle-point solver miniapp. It allows for more parallelism by threading over every matrix entry rather than just over every row.
A performance comparison is below. The dashed line represents a performance model for theoretical peak performance based on memory bandwidth and kernel launch latency.

Before
After

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#3967
@pazner
@tzanio
@artv3 + @sohailreddy + @camierjs
11/6/23
⌛due 11/20/23
⌛due 11/27/23

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

can we get another review please?

Looks good to me!

Merged in next for testing...


Enable FILTER_FLAG_EMAIL_UNICODE for email format if present

What
If FILTER_FLAG_EMAIL_UNICODE is available (PHP >= 7.1.0), enable it for email format checks.
Why
Because @abhijit-gaonkar asked for it in #397, and because RFC-5322 does not prohibit unicode characters in email addresses.

LGTM

@bighappyface Can this issue be closed? The fix is merged in both 6.0.0-dev and 5.2.0.


export declare class properties missing proper scopes

From https://github.com/Microsoft/vscode/issues/55575
TS and JS Grammar Extension version:  0.0.43 / latest
Code
export declare class TestClient {
    private readonly test1;
}

Gets highlighted as:

Looks like the scopes of the tokens are all:
variable.other.readwrite.alias.ts
meta.block.ts
meta.export.ts
source.ts

@mjbvz This should only be happening due to #643. My example from Microsoft/vscode#55575 was just using this snippet as an example that the optional property was breaking multiple things.
When I paste the snippet above into a clean .d.ts file I do not see the highlighting issue.

Looks like there was a regression since VS Code 1.25. This was tested using the latest version of the grammar on VS Code insiders


moved write_list_by_name underneath write_by name

just a tidy up, so all read_by_name methods are first then the write_by_names methods as opposed to jumbling them up

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

19 of 19 (100.0%)  changed or added relevant lines in 1 file are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.3%) to 94.174%

Files with Coverage Reduction
New Missed Lines
%

pyads/testserver/testserver.py
5
90.76%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
1665

Relevant Lines:
1768

💛  - Coveralls

We can do that. Brings more shape to the codebase. Don't know why the coverage decreased but can see no issues here. I'll merge it anyway.


Add Helm GitHub Actions

Adds Helm GitHub actions for CI (linting and testing any changed charts in a PR), and CD (packaging merged chart changes and uploading to GitHub releases, and updating the repo index in GitHub pages). For more info, see https://github.com/helm/charts-repo-actions-demo
Note about steps:

~Merging this PR should not publish any charts yet, since there was no previous version of them in a GitHub pages helm repo index file.~
Edit: this did add all the existing charts on PR merge. I seem to remember that not working in the past, but I could be wrong or we may have fixed it upstream in chart-releaser. Either way, it works now. I deleted the releases/tags and reverted gh-pages back to the initial empty commit so we can still proceed with step 2 below
In subsequent PRs, we can bump the versions of individual charts that we want to list. When we do, we should update each chart's README to add the new helm repo to installation instructions. See https://github.com/prometheus-community/community/issues/28 for the overall plan to incrementally improve/simplify charts after moving from stable to a new helm repo in https://github.com/prometheus-community

Fixed #4


apisix和openresty对比几大优势。欢迎补充！

1, etcd 解决分布式配置存储一致性问题,解决了配置变更推送问题;
2, 路由和真实服务配置可以动态调整;
3, nginx配置变更需要reload，worker进程缓存失效问题;

This is not the same, can't compare

Openresty is a full-fledged web platform
APISIX is an high-performance API-Gateway
You can compare APISIX to other API-gateways, like tyk, kong, orange, and
so on.
ShaoBo Wan(无极<EMAIL_ADDRESS>于2019年10月29日周二 下午1:32写道：

This is not the same, can't compare
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-apisix/issues/753?email_source=notifications&email_token=AA5DWDK65WCLPRWCDXIJ7HDQQ7DHTA5CNFSM4JGDHGEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECPJIJI#issuecomment-547263525,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA5DWDN6OUU6WWSRGFNS3B3QQ7DHTANCNFSM4JGDHGEA
.

@ygm521 I think we can close this issue.

希望院生补充补充吧，许多入门者都不清楚apisix和nginx有啥区别？ @moonming @membphis

@Miss-you  I agree

@ygm521 we'd better using English here, on account of we're in the apache-incubator now.
For your question, apisix is a Cloud Native Api GateWay, but Nginx or OpenResty are web Servers,
Apisix now is based on Nginx and Luajit(ngx_lua), there’re totally different things.
I think maybe your experience of Nginx using made you're  confused. Such as using Nginx as a revers Proxy,
Or a simple web server.
As a Cloud Native Api GateWay ApiSix not only provider a proxy ability, but also the ability of Service governance for your Cloud Native Micro services.
If you want some Chinese communication, you can discuss those questions in QQ group(552030619).

I am based on nginx to write related c language modules. As far as I know,
1, apisix is nothing more than using the etcd storage configuration to implement dynamic configuration changes;
2, instead of nginx's location{} matching
3, using a large number of worker process caches.

APISIX is not only implement dynamic configuration changes;
I think The most import things which APISIX have done are:

Provider a high performance route to mange your business traffic.
Provider a flexible mechanism(plugins) to add your custom logic about your own business.
Based on the upon second point, APISIX bring us many good plugins out of the box, such as rate-limit, trace, server-less and so on.

All in one world APISIX is a API Gateway Not a Web Server.


Any kind of state with cached compiled templates

Hi there,
I know Handlebars doesn't support state, however,
I would like to keep some form of state in a single HandlebarsEnvironment-instance, which I want to use in a (block)helper, but I also want it to be fast (by caching the compiled templates).
When compiling templates, variables used in (block)helpers are captured in a closure; so when trying to store the templates in a static dictionary this will preserve state.

Because of the closure, when I try to reuse the compiled templates in a new  HandlebarsEnvironment instance, the original values of the closure are present, so I can't update my state.
As an alternative I tried to extend the delegate signatures of HandlebarsHelper and HandlebarsBlockHelper with an addional HandlebarsConfiguration parameter (I know, breaking change, I'm not submitting this as a pr... I'm exploring my options).
I thought, maybe I could preserve state in the Configuration instance, but this also seems to be captured somehow.
public delegate void HandlebarsHelper(TextWriter output, dynamic context, *HandlebarsConfiguration configuration*, params object[] arguments);
public delegate void HandlebarsBlockHelper(TextWriter output, HelperOptions options, dynamic context, *HandlebarsConfiguration configuration*, params object[] arguments);

See my experimental commit https://github.com/Hybrid-SaaS/Handlebars.Net/commit/81eb8a6ced13392966cf391907f8460d00cd117f
I'm building a project where I'm heavily relying on Handlebars.net. But I'm kind of stuck right now.
Can you assist me with my attempt to maintain some form of state? I would be very appreciated.
Kind regards
Jeffrey

What problem are you trying to solve by attaching state to the environment?

What do I want?#
I want to keep track of data in cached (block)helpers.
Because compilation is a heavy operation, I want to compile and store partials in some caching mechanism. However, when doing so, the active state is captured.
Example
I created a sample WinForm application in https://github.com/Hybrid-SaaS/Handlebars.Net/commit/10dca9f0e28313a91be33bc785163d905c8bc958 to showcase my problem.

How to ..
In the example application I want to keep track of the current language, but when I cache the partials in a static Dictionary, the first selected language is captured and reused.
To simulate what I mean:

Checkout this commit: https://github.com/Hybrid-SaaS/Handlebars.Net/commit/10dca9f0e28313a91be33bc785163d905c8bc958
Debug application from Visual Studio
Set language to English
Push Run button
Set a breakpoint here https://github.com/Hybrid-SaaS/Handlebars.Net/blob/feature/state-example/source/Handlebars/Compiler/Translation/Expression/PartialBinder.cs#L86
Set a breakpoint here https://github.com/Hybrid-SaaS/Handlebars.Net/blob/feature/state-example/source/Example/TemplateCache.cs#L63
Set language to Nederlands
Push Run button again

At line 86:
configuration.RegisteredTemplates[partialName](context.TextWriter, context);

When I quickwatch
configuration

the value is (as expected) Nederlands

When I quickwatch
configuration.RegisteredTemplates[partialName]

the closure contains a reference to the original config object (value English)

Continue execution to break at TemplateCache.cs#L63
var customConfig = configuration as CustomConfig;

When I quickwatch the configuration argument the original state is present (English)

What did I expect?
When I changed the code to include the configuration in the delegate, I thought the active instance would be passed to the delegate, however, the original value is stored and passed.
I'm looking for a way to pass some variable(s) to the delegate.
I hope this explains my problem.
Thanks again 👍

This seems like global/application state that cuts across all currently executing instances, is that an accurate characterization?

This is true for the delegates, if an single Hangfire instance has its own compiled helpers, the state is different for an other Hangfire instance.

Also the state is captured (like a snapshot)

I am going to give this some thought over the weekend.

Happy days, I just created a workaround.
I'm using HttpContext.Current.Items to store my state data, in the first tests this seems to work. Maybe because HttpContext.Current is a [ThreadStatic] property?
:thinking: I can imagine the capture of global context with cached (helper) delegates may prevent garbage collection (memory leaks). Not sure though.


Pull in Upstream Updates

🗣 Description
This PR is to pull in changes from cisagov/skeleton-generic#41.
After a long period of sorting out updating to include necessary cisagov/skeleton-packer-cool elements, this now also includes cisagov/skeleton-generic#42 and cisagov/skeleton-generic#43.
The project has been updated to use cisagov/ami-build-iam-user-tf-module instead of cisagov/molecule-packer-ci-iam-user-tf-module for creating the test-skeleton-packer user. This has required a transition to building in the COOL, and breaks backwards compatibility with this project and non-COOL Packer projects we have developed.

💭 Motivation and Context
Updates and bugfixes are good.

🧪 Testing
Automated testing passed.
I was able to successfully create the test-skeleton-packer user in the COOL and successfully build an AMI using the local environment setup. I verified it was found in the list of AMIs in the Images (Staging) account on AWS.

📷 Screenshots (if appropriate)
🚥 Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (causes existing functionality to change)

✅ Checklist

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

I have removed the existing Secrets for this repository and have used the terraform-to-secrets tool from cisagov/development-guide to add in updated and new Secrets now that this PR has been approved.

Looks good. Check that "Breaking change" checkbox in the description.

Thanks for the catch on that. Updated the Types of Changes and Checklist in the PR description to correctly reflect all the changes that have been made.


ticket

requested icon

category suggestion
tbd
search synonyms
pass, coupon, voucher, slip, card, fine, label, tag, sticker, tally, tab

[ ] pop
[ ] print

released in v2
https://github.com/CyCraft/pepicons/releases/tag/v2.0.0


Whether it doesn't work for the full connection layer

Thanks for your open souring. I'm confused about whether it doesn't work for the full connection layer?

Fully connected layers are supported via the GroupLasso* regularizes. Does this answer your question?

Fully connected layers are supported via the GroupLasso* regularizes. Does this answer your question?

thanks for your reply! i already  use the flop_regularizer.GroupLassoFlopsRegularizer, but the JSON file just has the convalution layer without fc layer.
Besides, the README file says "use Gamma regularizer if the seed network has BatchNorm; use GroupLasso otherwise", now if my network architecture has both BN and fc, should i use  GroupLassoFlopsRegularizer or GammaFlopsRegularizer.
thank you !

It seems to me this is working as intended.
Usually, the last layer (fully_connected or conv) has a fixed number of outputs, think of num_labels. For example if your network has the following structure:
net= conv(inputs...)
net= conv(net...)
...
net= conv(net...)
logits = fully_connected(net, num_labels)

You simply cannot regularize or learn the number of the output of the fully connected layer.
We will try to clarify the README to clarify this misconception.


Frontend stage, SWOC 21

Please, Update my PR in Script winter of Code as Soon as possible before 10th March because then only i will be able to Score in SWOC,
Also, Please Label it with Difficult under SWOC21

Create a merge request for the front-end stage branch. Not the main branch.


UnboundLocalError: local variable "hostnames referenced before assignment"

Running into this issue on Ubuntu 14.04.2 on Python 2.7.6.  I had to modify cluster.py to get "setup_storage" command to work while installing the Contrail Storage solution.
Added this line to the top of get_all_hostnames() function:
hostnames = []

Once added, the command executes and Contrail storage is installed correctly.

Fixed this issue in commit https://github.com/Juniper/contrail-fabric-utils/commit/dbe38cc4f1e770f17b1b84199f8a28d6ae316d3e

Excellent, thanks


Use equals() rather than comparing String object using == or !=

Changed == and != to use equals() when comparing strings
Added a unit test with positive/negative tests
Added Mockito to test dependencies

this PR was merged into develop in 11e89ef


Got CLientConnectorCertiticateError while trying to access https://alpha4.starknet.io/gateway/add_transaction.

Environment:

OS: macOS Monterey v12.5.1
Python 3.7.9
Cairo version:  0.9.1
Warp Version: 2.1.0

Description:
I'm using. the example_contracts ERC20 to transpile the solidity code into cairo code, this generate a warp_output dir successfully with 3 files, ERC20__WC__WARP_abi.json, ERC20__WC__WARP_compiled.json, ERC20__WC__WARP.cairo and when I try to deploy the contract file I get this error:

Hi There,
A new version of Warp got released last night v2.2.2. Could you attempt the same with that version?
We are aware there have been some issues with prior versions.

Hi @GuyMcComb,
I'm update my warp version to 2.2.2 and I get a similar error

Hi @ArturVargas, sorry it took us a while to get your query on discord. I posted a possible solution there just today.
The problem is here how macos handles python installations, can you try the suggestion in this thread
https://github.com/Rapptz/discord.py/issues/423#issuecomment-272093801

Thanks @swapnilraj! I'm just install the Certificates because I'm using python3.7 and that fix the issue

Glad that your issue was resolved @ArturVargas!


Fix typos

This PR fixes various typos I spotted in the project.

@deining, thanks, this is much appreciated!


Contour as library

Hi there!
I consider to implement a terminal in the Godot game engine
The idea is to replace the central part here, the scripting editor, to use Helix and other tools.

Is your terminal capable to be implemented? The engine is written in C++

Contour is separated into few parts, terminal handling is happening in vtbackend part (https://github.com/contour-terminal/contour/tree/master/src/vtbackend) and gui part is here contour (https://github.com/contour-terminal/contour/tree/master/src/contour)


Allow transfer of attrs between classes.

I've run into many cases where, to avoid duplicating types and defaults, it would be nice to be able to "transfer" attributes between classes.
Example: We would like to do the following:
@attrs
class InnerClass:
    a = attrib(type=float, default=3.)

@attrs
class OuterClass:
    inner = attrib(type=InnerClass)
    b = attrib(type=int, default=1)

@attrs
class BuilderClass:
    a = InnerClass.a  # <- This Line fails, forcing us to duplicate types and defaults
    b = OuterClass.b  # <- This one too..

    def build_inner(self) -> InnerClass:
        return InnerClass(self.a)

    def build_outer(self) -> OuterClass:
        # Just to demonstrate why we use this builder class
        return OuterClass(inner=self.build_inner(), b=self.b)

builder = BuilderClass()
inner = builder.build_inner()
assert inner.a == 3.

builder = BuilderClass(a=4.)
inner = builder.build_inner()
assert inner.a == 4.

It would be really nice if attrs supported this syntax:
@attrs
class BuilderClass:
    a = InnerClass.a  # <- This Line fails

Instead, we usually end up just doing
@attrs
class BuilderClass:
    a = attrs(type=float, default=3.)

which requires us to duplicate type/default/validators/doc/etc.
Is that something that Attrs would be willing to support?

could this be part of #829?

Seems similar.  Would really be nice to have that syntax supported.  It lets us get around a general shortcoming of python - that there's not really a clean way to defer defaults (see thread).

Closing this in favor of #829.
Your desired syntax won't work tho, since we don't attach attributes to the classes anymore. You're gonna have to use attrs.fields() unless we'll find a nicer syntactic sugar.


Rails can't locate tesseract directory

I'm in a new rails 7 app running webpack. When I try to run
image_path = ActionController::Base.helpers.image_url('receipt.jpg')
image = RTesseract.new(image_path, lang: 'eng')
image.to_s

I keep getting the error
Errno::ENOENT: No such file or directory - tesseract

even though I have followed all the steps for setup. Any idea how to fix it?

Did you work this out?

Nevermind, was missing the actual tesseract install: brew install tesseract


WIP chore: Introduce sig-compute

/area instancetype
/cc @0xFelix
/cc @xpivarc
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/cc @dhiller
Can you please have a look as well?

/hold
The idea of sigs is to not define them on a feature level, but rather on a crossfunctional level.

sig-network, sig-storage and sig-live-migration all exist and counter that suggestion.

if we start to do feature drive sigs, where do we end? And we actualy loose the focus of sigs: maintain and improve shared knowledge. HOW good controlelrs are written, HOW good APIs look, etc. With feature driven sigs, the focus is on the feature, then I worry that the shared info (which we want to maintain) to rot anyhow.

I understand but think the two can co-exist (once sig-api and sig-controllers are actually populated) as the current proposal would already with the wider list of approvers and reviewers.

Quick note, I just noticed that during all the SIG iterations, we did not introduce sig-compute and sig-storage even tho they are used in i.e. the tests.
Can we change this pr to rather introduce the "missing" sigs in this tpo level owner_alias file:
tests $ git grep -oe "sig-[a-z-]\+" | cut -d ":" -f2 | sort -u

sig-compute
sig-compute-migrations # too fine grained, don't add
sig-compute-realtime # too fine grained, don't add
sig-monitoring
sig-network
sig-network-approvers
sig-network-reviewers
sig-operator
sig-performance
sig-scale-approvers
sig-scale-reviewers
sig-something  # bogus, don't add
sig-storage
sig-test-approvers
sig-test-reviewers

Quick note, I just noticed that during all the SIG iterations, we did not introduce sig-compute and sig-storage even tho they are used in i.e. the tests.
Can we change this pr to rather introduce the "missing" sigs in this tpo level owner_alias file:
tests $ git grep -oe "sig-[a-z-]\+" | cut -d ":" -f2 | sort -u

sig-compute
sig-compute-migrations # too fine grained, don't add
sig-compute-realtime # too fine grained, don't add
sig-monitoring
sig-network
sig-network-approvers
sig-network-reviewers
sig-operator
sig-performance
sig-scale-approvers
sig-scale-reviewers
sig-something  # bogus, don't add
sig-storage
sig-test-approvers
sig-test-reviewers

Okay I've switched the PR over to introducing the missing sig-compute and seeding that group with myself and @0xFelix with an eye on looking after the core instance type code.
After talking thigs over with @fabiand on slack I'm also going to organise a call in a few weeks to discuss the logistics around these SIGs, namely to agree on the final list of SIGs, define a process for adding/removing SIGs and a process for adding/removing individuals from SIGs.

Okay I've switched the PR over to introducing the missing sig-compute and seeding that group with myself and @0xFelix with an eye on looking after the core instance type code.
After talking things over with @fabiand on slack I'm also going to organise a call in a few weeks to discuss the logistics around these SIGs, namely to agree on the final list of SIGs, define a process for adding/removing SIGs and a process for adding/removing individuals from SIGs.

FWIW My ML post, call invite (03/08/23 @ 13:00 BST) and notes can be found below:

https://groups.google.com/g/kubevirt-dev/c/OkaCbq8uKcI
https://groups.google.com/g/kubevirt-dev/c/aSwIC-9P0d8
https://docs.google.com/document/d/1yOtxWS2eIgA2VT71NbFaDEzGyVfmiDCwoRBHKow0K6c/edit


tracker

why tracking algorithm is not required?
I am to count the number of people entering a vehicle.   How can I provide the ROI line so that people leaving or entering past that line will be counted?
thank you

The idea is simple:
The input video or real time camera record is read frame by frame via OpenCV.
The each frame will be send to TensorFlow Object Detection Model as an input. TensorFlow detects the objects on each frame. This process is repeated again and again till the video finish and so while frames which has bounding boxes on detected object are reading, processed and showing consecutively so objects are being tracked and you do not need any special tracker for it.
Your project topic (counting the number of people entering a vehicle) sounds interesting! You should change the ROI Line position with suitable angle and TensorFlow detect the people entering or exiting vehicle and also you can count them by this way.
Just focus to change ROI line angle and remove unnecessary modules sucs as color recognition module or speed and direction prediction module.
The ROI Line is assigned on line 252 in this class. Focus on it to change the line with true angle and do some modifications on general code to fit the program on your case.

thank you. I will try it and post the result
On Tue, Mar 6, 2018 at 5:05 AM, Ozlu<EMAIL_ADDRESS>wrote:

The idea is simple:
The input video or real time camera record is read frame by frame via
OpenCV.
The each frame will be send to TensorFlow Object Detection Model as an
input. TensorFlow detects the objects on each frame. This process is
repeated again and again till the video finish and so while frames which
has bounding boxes on detected object are reading, processed and showing
consecutively so objects are being tracked and you do not need any special
tracker for it.
Your project topic (counting the number of people entering a vehicle)
sounds interesting! You should change the ROI Line position with suitable
angle and TensorFlow detect the people entering or exiting vehicle and also
you can count them by this way.
Just focus to change ROI line angle and remove unnecessary modules sucs as
color recognition module or speed and direction prediction module.
The ROI Line is assigned on line 252 in this class
https://github.com/ahmetozlu/vehicle_counting_tensorflow/blob/master/utils/visualization_utils.py#L252.
Focus on it to change the line with true angle and do some modifications on
general code to fit the program on your case.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ahmetozlu/vehicle_counting_tensorflow/issues/1#issuecomment-370774906,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AgXgdVH6ilI1PMi4HCxpbF0JaHXN1rJwks5tbomMgaJpZM4SS0hP
.

Interesting way for counting vehicle, I must say.
Can I understand line 252 in this class ?  How do you change the ROI Line angle ?
What do the code below means ? What if i change 205 or 210 ?
if ((len(bottom_position_of_detected_vehicle_temp_list) != 0) and bottom-bottom_position_of_detected_vehicle_temp_list[0] > 0 and 205 < bottom_position_of_detected_vehicle_temp_list[0] and bottom_position_of_detected_vehicle_temp_list[0]< 210 and 200 < bottom ):

if ((len(bottom_position_of_detected_vehicle_temp_list) != 0) and bottom-bottom_position_of_detected_vehicle_temp_list[0] > 0 and 205 < bottom_position_of_detected_vehicle_temp_list[0] and bottom_position_of_detected_vehicle_temp_list[0]< 210 and 200 < bottom ):
This means that, if the detected vehicle's bottom y pixel values (actually, bounding box's bottom y pixel values) is between 205 and 210, increase the counter. Thus, you can increase by 1 the detected vehicle count.
If you want to change ROI line, you should play with these pixel value range. For example, if you want to move above the ROI line as y axis, just set that range
185 < bottom_position_of_detected_vehicle_temp_list[0] and bottom_position_of_detected_vehicle_temp_list[0]< 200
Maybe it looks a bit complicated but the developing is on progress, these points will be divided more functions are in different classes so it will be easier to understand and manipulate.

Thanks for your explanation, can you please explain how you are calculating the speed in this block ?
Because I can't understand some of the transformations like scale_real_length, scale_real_time_passed, speed = speed/6*40 and scale = 1
please elaborate a bit.

Ahmetozlu, great work!! One thing we're struggeling with is the counting part. If the object recognition loses track (for a very short time), there's no bounding box aound the object thus doesn't register once it passes the ROI line. Widening the ROI line caused vehicles being counted twice because the bottom of the bounding box hits the ROI line, tracking is lost and regained agai, hitting the RIO line again.

@Gerry-K ,
Widening ROI Line causes counting one vehicle as 2-3 or more maybe. You should consider about fine-tuning the coco  model that is used in this work so you can detect vehicles in your case with higher accuracy (you can boost the accuracy via fine-tuning). Thus, your object recognition will not loses track!
If you will make wider ROI Line, then you should consider about the counting range so you should manipulate this line

@ahmetozlu :  there is no increase of the bounding box in the Y pixel. the change in bounding box pixel is along the X axis. since the vehicle is moving in the x direction. why we consider the y pixel? that was logical if the object were moving upstairs or downstairs ( it's y coordinate decrease and increase based on the situation)

The pipeline and explanation of the tracker are available in here
I have developed my system just considering y pixel because it was enough for my case. However, you can adopt it for your case, you can use x pixel ROI line and adopt this project to count, predict speed and color of the vehicles that are on moving on x direction, moreover you can adopt it for the vehicles are moving on both x and y angles.


On state change and component re-rendering animation becomes junky.

First of all thanks for providing this wonderful library.
ISSUE
I am using MotiView for creating Waves animation and every time the component mounts it is working fine and on state update, the animation becomes junky and stops working at the end.
I have also wrapped my animation component into the AnimatePresence but still no success.
Code Sample
     <AnimatePresence style={[styles.dot, styles.center]}>
        {[...Array(5).keys()].map(index => {
          return (
            <MotiView
              from={{opacity: 1, scale: 0}}
              animate={{opacity: 0, scale: 9}}
              transition={{
                type: 'timing',
                duration: durationCal,
                easing: Easing.inOut(Easing.ease),
                delay: index * 400,
                repeatReverse: false,
                loop: true,
              }}
              key={index}
              style={[StyleSheet.absoluteFillObject, styles.dot]}
            />
          );
        })}
     </AnimatePresence>

Demo Video
https://user-images.githubusercontent.com/67545083/151162365-ed8ec682-f8ff-4472-9e6d-f8e28f690bb4.mov

I am also facing the same issue. Any chance to get help on it @nandorojo. Thanks!

what's the point of animate presence here if you don't have an exit prop?

also animate presence doesn't accept styles

@nandorojo As I have shown in the attached video I am trying to create waves that will never end to animate and I have control their frequency dynamically for that I am using a local state. But every time the state change the animation becomes junky in the start and then stops.
I have shown this behavior in the above-attached video and thanks for helping out me.
<AnimatePresence>
        <View style={[styles.dot, styles.center]}>
          {[...Array(5).keys()].map(index => {
            return (
              <MotiView
                key={(Math.random() + 1).toString(36).substring(7)}
                from={{opacity: 1, scale: 0}}
                animate={{opacity: 0, scale: 9}}
                exit={{opacity: 1, scale: 0}}
                transition={{
                  type: 'timing',
                  duration: durationCal,
                  easing: Easing.inOut(Easing.ease),
                  delay: index * 400,
                  repeatReverse: false,
                  loop: true,
                }}
                key={index}
                style={[StyleSheet.absoluteFillObject, styles.dot]}
              />
            );
          })}
        </View>
      </AnimatePresence>

This code isn't proper. AnimatePresence requires components with unique keys as direct children. Also, if you want an infinite loop, there's no reason to use AnimatePresence or exit.

As for potentially weird behavior with state changes + loops, if they persist, I recommend memoizing your moti components. To avoid them changing from parent state components.
const animation = useMemo(() => {
  ;[...Array(5).keys()].map((index) => {
    return (
      <MotiView
        key={(Math.random() + 1).toString(36).substring(7)}
        from={{ opacity: 1, scale: 0 }}
        animate={{ opacity: 0, scale: 9 }}
        exit={{ opacity: 1, scale: 0 }}
        transition={{
          type: 'timing',
          duration: durationCal,
          easing: Easing.inOut(Easing.ease),
          delay: index * 400,
          repeatReverse: false,
          loop: true
        }}
        key={index}
        style={[StyleSheet.absoluteFillObject, styles.dot]}
      />
    )
  })
}, [])

Is the issue that changing duration breaks it?

Alright, I will remove AnimatePresence and exit prop then what will be the solution to my issue. And thanks for the suggestion to use useMemo I am actually using it like this:
const normal_speed = 2000;

  const [waveCounter, setWaveCounter] = useState(100);

const onSwipe = () => {
    setIsBackground(true);
    setWaveCounter(waveCounter + 100);
  };

const durationCal = useMemo(() => {
    const durationValue = JSON.parse(normal_speed) - waveCounter;
    return JSON.stringify(durationValue);
  }, [waveCounter]);

const BottomMotiView = useMemo(
    () => (
      <AnimatePresence>
        <View style={[styles.dot, styles.center]}>
          {[...Array(5).keys()].map(index => {
            return (
              <MotiView
                key={(Math.random() + 1).toString(36).substring(7)}
                from={{opacity: 1, scale: 0}}
                animate={{opacity: 0, scale: 9}}
                exit={{opacity: 1, scale: 0}}
                transition={{
                  type: 'timing',
                  duration: durationCal,
                  easing: Easing.inOut(Easing.ease),
                  delay: index * 400,
                  repeatReverse: false,
                  loop: true,
                }}
                key={index}
                style={[StyleSheet.absoluteFillObject, styles.dot]}
              />
            );
          })}
        </View>
      </AnimatePresence>
    ),
    [waveCounter],
  );

why is durationCal using JSON.parse and JSON.stringify? Shouldn't it just be this?
const durationCal = Number(normal_speed) - waveCounter

Is normal_speed a string or something?
PS you can format your code if you add backticks like this: ```tsx at the start of your code block.

I just saw an issue with your code here. You're using random numbers for key here. That is guaranteed to break code in react. It should always be a stable ID, or an index if indices are stable. This is guaranteeing a full re-render and random behavior. I'm almost certain this is never what you should do.

@nandorojo normal_speed is a number.

In this case, your code should just be this:
const durationCal = normal_speed - waveCounter

Also, rather than a state change, use a shared value. Moti lets you pass the result of useDerivedValue to transition, meaning you don't have to trigger re-renders and get better performance. You'll have to split each item into its own component, and then you can do something like this:
const waveCounter = useSharedValue(100)
const onSwipe = () => {
  'worklet'

  // change your waveCounter here somehow
  waveCounter.value = 200
}

// then return each item

// then inside of each item

const transition = useDerivedValue(() => ({
  type: 'timing',
  duration: normal_speed - waveCounter.value,
  easing: Easing.inOut(Easing.ease),
  delay: index * 400,
  repeatReverse: false,
  loop: true
}))

return <MotiView transition={transition} />

Do not use exit or AnimatePresence, they don't make sense here.

Thanks, @nandorojo let me try this one and I will be back to you shortly.

@nandorojo  I have the same issue and it's not fixed by following what you have suggested!

Please create a reproducible snack, I can't help with that.

Sure I will try to reproduce it and share it with you today.

Hi @nandorojo actually I am not able to create a reproducible snack because of reanimated2 and gesture-handler version issue.
By the way, I have created a sample class which is having the code for this whole scenario. Hopefully, this will be helpful to reproduce this issue on your side.
import {View, StyleSheet} from 'react-native';
import React from 'react';
import {MotiView} from 'moti';
import {Easing, useDerivedValue, useSharedValue} from 'react-native-reanimated';

const Test = () => {
  return (
    <View style={styles.container}>
      <View style={{alignSelf: 'center'}}>
        {[...Array(5).keys()].map(index => {
          return <MotiViewShow index={index} />;
        })}
      </View>
    </View>
  );
};

const MotiViewShow = ({index}) => {
  const waveCounter = useSharedValue(2000);
  React.useEffect(() => {
    setInterval(() => {
      onValueChange();
    }, 3000);
  }, []);

  React.useEffect(() => {
    console.log('value', waveCounter.value);
  }, [waveCounter.value]);

  const onValueChange = () => {
    'worklet';

    // change your waveCounter here somehow
    waveCounter.value = waveCounter.value - 50;
  };

  const transition = useDerivedValue(() => ({
    type: 'timing',
    duration: waveCounter.value.toString(),
    easing: Easing.inOut(Easing.ease),
    delay: index * 400,
    repeatReverse: false,
    loop: true,
  }));
  return (
    <MotiView
      from={{opacity: 1, scale: 0}}
      animate={{opacity: 0, scale: 9}}
      transition={transition}
      style={[StyleSheet.absoluteFillObject, styles.dot]}
    />
  );
};

export default Test;

const styles = StyleSheet.create({
  container: {
    flex: 1,
    justifyContent: 'center',
    alignItems: 'center',
  },
  dot: {
    width: 52,
    height: 52,
    borderRadius: 50,
    backgroundColor: '#417040', //'#417040',
  },
});

And here is the demo video attached for this scenario.
https://user-images.githubusercontent.com/44516486/154840512-609534da-7bd7-4537-aadc-6f4f1f3e90f2.mp4

Hi @nandorojo did you able to get some time to reproduce it on your side?

Hi @nandorojo actually I am not able to create a reproducible snack because of reanimated2 and gesture-handler version issue.

I believe these do work on Snack for iOS


Fix coredns security context and CSR version

Codecov Report
Base: 75.61% // Head: 75.56% // Decreases project coverage by -0.04% :warning:

Coverage data is based on head (4a9ea25) compared to base (74b034a).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #139      +/-   ##
==========================================
- Coverage   75.61%   75.56%   -0.05%
==========================================
  Files          76       76
  Lines        6208     6205       -3
==========================================
- Hits         4694     4689       -5
- Misses       1259     1262       +3
+ Partials      255      254       -1

Impacted Files
Coverage Δ

...tl/cmd/client/command/meshinstall/base/k8sutils.go
64.46% <100.00%> (ø)

...ent/command/meshinstall/coredns/deployment_spec.go
92.53% <100.00%> (-0.11%)
:arrow_down:

.../client/command/meshinstall/controlpanel/deploy.go
50.00% <0.00%> (-1.45%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Rename "Nearby" feature?

With the implementation of #591 , it seems that Nearby is no longer just "Nearby" any more, but rather a full-fledged map of places that need pictures, anywhere in the world.
I wonder if we should consider renaming the feature? To be fair, I can't think of anything else that is equally concise, and "Nearby" is what all of us refer to it as now. But it just doesn't seem accurate anymore.

Maybe just "map"? I feel if we were to call it this it would need a search feature which I think could be difficult to implement well without using non-open-source services.
Given it does start at your location "nearby" does still kinda make sense

We need to update nearby info i consequently, see #2194 . Map is a alternative, does "Upload via Map" too long;?

I think "Nearby" is the best for now.
It makes people curious, it is personal and a call to action.
An even more personal name could be "Around you".
If the tab was called "Map" I believe many people would think "Why would I want to see a map, that's boring".

@nicolas-raoul @4D17Y4 this issue is obsolete so we can close this now

Yes, I think the consensus is that "Nearby" is still best. Closing. :)


MdButtonModule is not an NgModule

Bug, feature request, or proposal:
Bug
What is the current behavior?

Upgrading from beta 8 to 10
Applying all the required chages
Ending up with this Typescript error while building: ERROR in MdButtonModule is not an NgModule

Which versions of Angular, Material, OS, TypeScript, browsers are affected?
@angular/cli: 1.3.2
node: 8.0.0
os: linux x64
@angular/animations: 4.1.3
@angular/cdk: 2.0.0-beta.10
@angular/common: 4.1.3
@angular/compiler: 4.1.3
@angular/core: 4.1.3
@angular/flex-layout: 2.0.0-beta.8
@angular/forms: 4.1.3
@angular/http: 4.1.3
@angular/material: 2.0.0-beta.10
@angular/platform-browser: 4.1.3
@angular/platform-browser-dynamic: 4.1.3
@angular/router: 4.1.3
@angular/cli: 1.3.2
@angular/compiler-cli: 4.1.3
@angular/language-service: 4.1.3

Have you deleted node_modules directory before running npm install?

I had the same problem. After removing node_modules and reinstall packages, it worked.

Yes I've tried to remove node_modules, remove yarn.lock and reinstall.
It didn't change anything. BUT, I was running angular 4.1.3 and when I upgraded to 4.3.x it seems to work fine. Just few things I need to check but I might close the issue soon.

That was it, closing :+1:


Parameter passed from JS to Apex had the wrong name.

Warning
Info

Properly saving changes to Affiliation Mappings in Settings (9194).

@daveperry In theory this could be merged as well, but the status is not green because of a "default" build that apparently is running. Let's wait until @jlantz clarifies what's going on with the build jobs before merging.

@jlantz ~ is it ok to merge this pull request now?


flag "-ref subject" produces a warp_subject2template transfo which is wrong

the registered data is missing (zero everywhere)

fixed in c14ccb18b1099332dd37686e377bc7ff55cf4dc8


API reference docs missing for event-processor-host package

https://docs.microsoft.com/en-us/javascript/api/overview/azure/eventhubs?view=azure-node-legacy is the landing page for Event Hubs in the "legacy" moniker.
It currently shows ref docs for @azure/event-hubs v2
Since we now have v5 of the same package under the "latest" moniker, we do not need to have the same package listed under "legacy". Instead, we should be having ref docs for @azure/event-processor-host under "legacy"

It is now updated to legacy moniker. Close this issue. Feel free to reopen if anything unaddressed.

https://docs.microsoft.com/en-us/javascript/api/@azure/event-processor-host/?view=azure-node-legacy

Thanks @sima-zhu!


feat: Add inset logical properties to layout props

This PR updates the Layout Props documentation to include the following new inset logical properties:

inset
insetBlock
insetBlockEnd
insetBlockStart
insetInline
insetInlineEnd
insetInlineStart

Related to https://github.com/facebook/react-native/commit/9669c10afceef65626c82149210afc07d47df98b

Hi @NickGerleman, who should I ping for a review on this?

Right now the "next" version of the documents targets React Native 0.71. These are cut as part of a react-native release, and after, "next" will target 0.72. Since this change targets 0.72, we need to wait until that cut before merging it.
Content-wise, mostly LGTM. Could we add the clarification that these only work on Fabric?

Could we add the clarification that these only work on Fabric?

Sure, I completely missed that, should we have some sort of tag for Fabric only props? Just like we have for Android and iOS? e.g.

I think something like that would be great. Last time I asked around, I think these props and the ones for pointer events are the first ones that are Fabric only, so I'm not sure we've made anything yet.

Nope, we do not have the dedicated label for Fabric yet, but it can quite easily created as a variant of platform tag if needed, as Gabriel suggested:

https://github.com/facebook/react-native-website/blob/main/website/src/css/customTheme.scss#L1418

Sounds good, thanks for the feedback @NickGerleman and @Simek, I've just pushed a commit adding a Fabric only tag

https://deploy-preview-3493--react-native.netlify.app/docs/next/layout-props#insetblock-fabric
LGTM

Cc @rickhanlonii, from offline discussion, can we go ahead and merge?

any updates on this? cc @NickGerleman

any updates on this? cc @NickGerleman

This change ended up sparking a lot of discussion internally on how we should be framing the New Architecture and Fabric. I think there's a good concern here, about the majority user not yet being on Fabric, or more casual users not knowing what Fabric is. So UI-wise, I think the uncertainty is coming down to how we represent, and what prominence we want to give to Fabric-only props.
Should be able to share more on Monday. Apologies for this stretching out, I am really glad you made this change to add the documentation.

The latest update, we still don't have great agreement on how we should handle this case. So we're continuing to refine that (for future cases where we want to do something similar to this).
In this specific case, it sounded like there may also be a natural Paper implementation for aliasing layout props. @gabrieldonadel is that something you think you would be willing to take on for the 0.72 timeframe?
I do also want to apologize my role in this, advocating for switching from a JS-side shim to native Fabric implementation. Part of the reason I did that was knowing the Fabric only implementation was not much more expensive to build, and I still think it's likely the better alternative in that case, but it also landed the change into some unknown territory we're still figuring out.

No worries, thanks for the update @NickGerleman, I can definitely implement this on Paper within the 0.72 timeframe


Translations

I've added some translations including a little grammar for one sentence.

Thank you for your contribution!


:seedling: Bump Golang to v1.23.4

What this PR does / why we need it:  Bump Golang from v1.23.3 to v1.23.4

/test metal3-centos-e2e-integration-test-main metal3-ubuntu-e2e-integration-test-main


move listener + ctrl key

Hello,
Is it possible to detect if the user is holding the ctrl key when he moves the steps?
A similar feature is available in the click listener.
Thanks

Added MouseEventDetails to move and resize events. Check ctrl key by event.getDetails().isCtrlKey().


Need a way to insert newlines on iOS

Since there is no alt modifier on the virtual keyboard, we need to come up with some new way of adding newlines within a row.

A toolbar button has been added in the upcoming 2.1 release with this feature.


Spring Cloud Gateway MVC, order of before and after functions.

Question
I'm using Spring Cloud Gateway MVC to create custom routes. I need to associate multiple before functions and multiple after functions for each route I build. I needed to control the order of execution of these before and after function. I was assuming the order of functions in the route definition would also be the execution order of these functions. In practice during my testing I'm seeing the "before" functions are execution follow the order they are defined in but the "after functions execution is in the reverser order.
Is there anything I can do to control the order?
Example:
route(routeId)
        .nest(
            path("customPath/*"),
            () ->
                route()
                    .before(beforeFunction1)
                    .before(beforeFunction2)
                    .before(beforeFunction3)
                    .route(all(), routeHandlerFunction)
                    .after(afterFunction1)
                    .after(afterFunction2)
                    .after(afterFunction3)
                    .build())
        .onError(Throwable -> true, exceptionHandlerFunction)
        .build();

The order of execution I'm seeing is:
beforeFunction1 -> beforeFunction2 -> beforeFunction3 -> routeHandlerFunction -> afterFunction3 -> afterFunction2 -> afterFunction1
If there is a fixed order to expect I can define my route based on that. Is there documentation about this anywhere?
Thanks,
Gotham

Your finding are correct about the order. Let's use this to document that fact. Before and after functions are special cases of HandlerFilterFunction, which has both before and after. So the more accurate execution is this
beforeFunction1 -> beforeFunction2 -> beforeFunction3 -> afterFunction1 (no op) -> afterFunction2 (no op) -> afterFunction3 (no op) ->

routeHandlerFunction ->

afterFunction3 -> afterFunction3 -> afterFunction1 -> beforeFunction3 (no op) -> beforeFunction2 (no op) -> beforeFunction1 (no op)

All the before parts are executed in the order defined, then all the afters are executed in the reverse order they are defined. The fact that you put the route() call in between the calls to before() and `after() has no bearing on the order.

Thanks that helps. Would the after functions still run if there is an exception that is handled by the onError functions?

I'm not positive. @poutsma could say with certainty.

Looking at the code, onError() is just a specialization of a handler filter function. Looking at the code it looks like they might still run. What is your experience? https://github.com/spring-projects/spring-framework/blob/8137cc95669690f3e4055d6ccf484e98a07b6703/spring-webmvc/src/main/java/org/springframework/web/servlet/function/HandlerFilterFunction.java#L106-L129

I'm not seeing the after() functions run after an exception has been handled in my example above, not sure if that is because I defined the onError() handler outside the nested route. The exception happens to be thrown by one of the before() functions in my testing.  I had to define the onError() handler outside the nested route otherwise any exceptions being thrown were not getting handled.

Thanks that helps. Would the after() functions still run if there is an exception that is handled by the onError() functions?

As you already found out, they don't.

I'm not seeing the after() functions run after an exception has been handled in my example above, not sure if that is because I defined the onError() handler outside the nested route. The exception happens to be thrown by one of the before() functions in my testing. I had to define the onError() handler outside the nested route otherwise any exceptions being thrown were not getting handled.

Filters—such as those registered with before, after, and onError—are scoped, and only apply to the routes in the same nesting.


Task Execution Paused

Describe the bug
Every time I start Burp, headless or not the "Task Execution" option is paused. This means that no matter how many tasks I send (spider, passive, active scan) they will only be added and not actually executed, since all the tasks are paused. I can observe that by running with headless=false:

I've tried changing that option and then saving project options, user options and project state - it still stays 'paused'.
To Reproduce
I'm just Adding Target -> Check if it's in scope -> Start spider (/burp/spider?baseUrl).
Desktop (please complete the following information):

OS: Mac
Burp Suite _Professional_2.0.09 version
Extension burp-rest-api-2.0.0 version

Not if there is something I'm missing.

That's the default behaviour in Burp.
You can use the following command line --unpause-spider-and-scanner or simply run in headless mode (which won't pause spider and scanner)
Cheers,
Luca

i`m using --unpause-spider-and-scanner and ran into same problem, any progress on the matter ?

Unless you provide step by step instructions, we won't be able to help you. I don't believe there's any bug since it is all native Burp stuff


README updates

should include "database" for SEO, since that is what people usually call them? ;)
link to windows build steps
link to blog; convienance & more SEO

Is that better?

lgtm, thanks @tomByrer

Welcome!


docs: Azure authentication refactoring design

Description
What this PR does / why we need it:
This PR proposes a design doc for refactoring Azure authentication modules in Ratify. It describes the existing Azure authentication modules and it's pain points and provide a solution to refactor the code to solve those pain points.
Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Provide a design doc to #1944
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
[x] This change requires a documentation update

Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

Post Merge Requirements

[ ] MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

Ready for review, maintainers please take another look @binbin-li , @akashsinghal , @susanshi


Non-consistent calculation of concentration parameters

concentration parameters for MAGIC are computed from non cleaned image:
https://github.com/cta-observatory/magic-cta-pipe/blob/01f273d656d9a440ef43802b30aa25a99975d889/magicctapipe/scripts/lst1_magic/magic_calib_to_dl1.py#L291
same is done for MCs (both MAGIC and LST-1):
https://github.com/cta-observatory/magic-cta-pipe/blob/01f273d656d9a440ef43802b30aa25a99975d889/magicctapipe/scripts/lst1_magic/lst1_magic_mc_dl0_to_dl1.py#L328-L330
however for LST this is done after selecting only image pixels:
https://github.com/cta-observatory/cta-lstchain/blob/e4a5b7a36dfd643acf47b9006f51fe882b6dbc5c/lstchain/reco/r0_to_dl1.py#L164
the difference is not huge, but especially if there are multiple islands the concentration parameters can behave in complicated way.
Thankfully the concentration parameters are not used in the standard chain.
There are two possible ways to fix it:

change both for MAGIC data and for MC to have it the same as for LST-1 data
change the behavior for LST-1 MCs to reproduce what is done in the data (which would mean that the parameter would have slightly different meaning for different telescopes)

this is the difference between the values of the parameters for the data between LST data (computed from the cleaned image in blue and from full image in orange:

(computed by @nzywucka )


Get git importer component to show in UI

This ticket is for adding the bootstrapping necessary for showing the git importer component stubbed out in #86 in the UI.

@miltontony Ready for review.

:+1: on condition you replace the templates of import-from-ucd

Ready for re-review.

:+1:


[language][move] Avoid hardcoded 32 byte address length in a few more places

Most of the references to the address length in shared/mod.rs have already
been replaced to use the ADDRESS_LENGTH constant, and this changes a few
more of them in the code that inserts leading zero bytes for short addresses.
Motivation
Avoiding hardcoded constants
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
No functional changes here

@bors-libra r=tzakian

:pushpin: Commit 67424cd has been approved by tzakian

:hourglass: Testing commit 67424cd5583a0a2182abcd4e61beccbb7c625750 with merge cd31c78ffb63c760afca78e071552fd5456a425f...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: tzakian
Pushing cd31c78ffb63c760afca78e071552fd5456a425f to master...


DataLoader worker (pid(s) 412512) exited unexpectedly in ptvsd

I debug fairseq with ptvsd. However, it encountered the following error:
DataLoader worker (pid(s) 412512) exited unexpectedly

After some investigation, I found that the data loader uses Multiprocessing which causes this problem. Setting --num-workers to 0 solves this problem. Is it possible to set the default value of --num-workers to 0? It has the same effect while avoiding errors in ptvsd.

No, it's much slower.  If you want to debug, you'll have to manually set --num-workers to 0.


Node appearing twice in peers list

I run a node monitor which is appearing in the peers list as well as appearing under the IP. It appears that the data is not being aggregated and must be because mynano.ninja doesn't recognize my node yet. Therefore it is showing CPS, BPS and missing node monitor data on one of the entries and node monitor data with missing CPS, BPS telemetry on the other.
I notice you iterate through the peers and look for node monitors so possibly here you could map them?

What is your node called? The only way to match is by the rep account and if your node is not voting it simply can't match it. I don't know how to solve that? What other data would be available from both the monitor and telemetry? The account comes from the confirmation_quorum RPC command which in turn matches the IP from the telemetry. If the node monitor would report the IP it would have been easier.

Could you map the peer IP with the monitor paths which would be one way of matching without needing the rep account?
Specifically here, you could create KVP with the peer IP being the key and an array of node paths as the value, and when you go to verify the monitors you just remove all the ones that don't work and now you've got a matched up peer/monitor

Yeah that could work, thanks


Custom banner at top page

Example: http://flask.pocoo.org/docs/dev/

I'm trying to achieve this for marshmallow. I tried using the following config:
https://github.com/marshmallow-code/marshmallow/blob/5f2470470ab29f9fa87341db118c55cd00a2916e/docs/conf.py#L104-L120
But versionwarning_body_default_selector and versionwarning_body_extra_selector didn't have any effect, since process_version_warning_banner doesn't seem to respect those options.
Expected result

Actual result

Thanks for posting it here.

But versionwarning_body_default_selector and versionwarning_body_extra_selector didn't have any effect, since process_version_warning_banner doesn't seem to respect those options.

Yes, process_version_warning_banner doesn't respect this. Those values are considered only when the banner is injected dynamically by Javascript.
Currently, there are two ways of inserting the banner: statically (done by Python/Sphinx as a docutils node) or dynamically (done via Javascript).
When injecting the banner statically, this is injected as a first node of the reST document (https://github.com/humitos/sphinx-version-warning/blob/master/versionwarning/signals.py#L21). So, there is not too much the extension can do here.
The HTML structure is managed by the Sphinx theme, so to change that, the Sphinx theme has to be altered. flask theme alters this by rendering the version warning without being part of the reST document: https://github.com/pallets/pallets-sphinx-themes/blob/master/src/pallets_sphinx_themes/themes/pocoo/layout.html#L19-L21

This is a completely hack...
In case you really, really want this and do not want to create/adapt a theme and you don't care about this hack, you can create a simple JS and add it to project with this code:
$(document).ready(function () {
    $('#version-warning-banner').prependTo($('div.document'))
});

That will move the HTML of the banner before the document itself :grimacing:
Remember to add this file into your conf.py:
def setup(app):
    app.add_javascript('js/movebanner.js')

Check the example at: https://sphinx-version-warning-example.readthedocs.io/en/flask-like-warning/

marshmallow is already using my fork of alabaster, so I don't have a problem modifying the theme. Would it be feasible for sphinx-version-warning to add the version warning banner to the template context so I could just drop it into the layout?

@sloria I've been thinking on your needings here and I found that maybe I need to change the design of the extension.
As I commented in this issue, there are two ways of generating the banner: dynamically (via Javascript) and statically (via Sphinx/docutils admonition node).
When I design it, I was thinking that if you already know the banner that you want to show in a specific version that was a great use case for the static case, but now I'm thinking that this complicates things. Why? Because if you tweak the HTML from the config and use a custom selector (as you mentioned) that won't be reflected in any static-generated banner.
Looking for feedback:

do you think it could have any drawback if I remove completely the static way of adding the banner and only relies on the dynamic one?
do you think there is an amazing use case for the static banner that I'm missing and can't be achieved with the dynamic one?
do you think... (whatever you want to add here)?

As as a side note, Read the Docs only adds the banner dynamically and this has been working fine since it was implemented.

I think only using the dynamic approach makes sense for both maintainability of this package and for the sake of being able to place the banner anywhere.

@sloria I started working on this. I opened #15 for this and did a very simple test at https://sphinx-version-warning-example.readthedocs.io/en/flask-like-warning/
I need to keep working on this for a proper release, though.

Great! Looking forward to it.

@sloria I just released v1.0.0 and you should be able to customize with your needings. Please, let me know if this does work.

Weird. One of my tests was with Sphinx 1.8. I'll check this again and fix it.
Thanks for the report. Hopefully, you will be able to use this extension soon 😊

Weird. One of my tests was with Sphinx 1.8. I'll check this again and fix it.
Thanks for the report. Hopefully, you will be able to use this extension soon 😊

No worries. I've just pinned to sphinx==1.7.9 for the time being.


Support for Spring Boot Management endpoints

The Swagger2Controller uses the @Controller annotation which simplifies the registration for a Spring MVC controller. It would be great if this could be changed to allow its registration as a MvcEndpoint. This would allow the registration of the controller under the management port of Spring Boots Actuator.

@sbuettner not sure we want to show that endpoint in the management console. What is the use case thats driving this need?

Hi @dilipkrish. Assuming you only expose the management port internally this would allow to hide the documentation from the public and make it only privately accessible. Maybe you are developing multiple applications but you only want to provide a documentation that contains all apis from all services and not one for each application/microserver. You might then generate a documentation based on your complete api from all swagger documents.
I hope this makes things a little bit more clearer.

@sbuettner not entirely...
Currently all the swagger controllers Swagger2Controller, Swagger1Controller and ApiResourceController are all ignored using @ApiIgnore so that they don't show up in the swagger docs.
Other than that they are all regular mvc enpoints activated via @Controller and @RequestMapping annotations. Are you suggesting we implement MvcEndpoint interface explicitly? I thought that was an either or option. Is that not correct?


Create cmake module config files during install

Some of our users may want to use cmake for their builds, we should create module files during the installation so the find_package(bigtable-client) (or whatever we call our library) function works correctly.
See the protobuf install.cmake file for an example.

This might be useful too:
https://cmake.org/cmake/help/v3.5/module/CMakePackageConfigHelpers.html#command:write_basic_package_version_file


Revert "actionlib: 1.11.14-0 in 'melodic/distribution.yaml' [bloom]"

Reverts ros/rosdistro#17923 - This caused breakage with realtime_tools which will also be reverted.

Code change looks good but commit list is fishy, we should squash and merge and remove the mention to other commits that are not actually reverted by this PR


website: disable --with-vercel-static for now

even #313 didn't work.
The problem is generated html that only happens Vercel production build. It doesn't happen with Vercel preview build.
index.html.zip
Assuming it's static only problem, disabling it for now.

Oooops, this doesn't help because / is a static path. 😢


[REVIEW] inb

Project link
https://github.com/joshiayush/inb

Nice repo! Some thoughts from my side.
There is lots of duplicate information in the readme maybe considering removing the badges showing the open issues etc and I think also the tech stack could be found at the right side provided by GitHub itself.
Further consider adding issue templates (maybe also issue forms due those are way cooler) to the repo.
Also take a look at the failing action.

Looks good, some suggestions

wiki looks empty, suggest removing tab
hide releases and packages as not being used
hide project board tab as not used


Add non-nil check before logging volume errors.

Fixes daemon panic in #31903
Signed-off-by: Anusha Ragunathan<EMAIL_ADDRESS>

LGTM

LGTM


Batch processing

this PR contains some more behind-the-scenes improvements related to ease-of-use and/or batch processing for the Summarizer class object:

disable the progress bar for within-loop summarization of a single long string
add a 'smart' __call__ function that hands off to the text and filepath processing fns
small improvements/updates to docs

todo:

[ ] check/test that the default-disabled autocast doesnt break anything
[ ] add a batch_delimiter (or similar) kwarg for setting the join string for output of summarize_string()


Move New Notebook command to core

Currently our New Notebook command in the File menu is contributed from the built-in notebook extension, which means we can't open a new notebook until the extension host finishes loading. This change moves that command into core so that we can use it immediately.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 17 (0.0%)  changed or added relevant lines in 2 files are covered.
14 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.04%) to 41.95%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/contrib/notebook/browser/notebookActions.ts
0
2
0.0%

src/sql/workbench/services/notebook/browser/notebookServiceImpl.ts
0
15
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/dialog/configurePython/configurePathPage.ts
1
57.02%

extensions/sql-bindings/src/common/azureFunctionsUtils.ts
1
80.65%

src/sql/workbench/services/notebook/browser/notebookServiceImpl.ts
1
31.21%

extensions/notebook/src/jupyter/serverInstance.ts
4
75.5%

src/sql/workbench/contrib/notebook/browser/notebookActions.ts
7
52.99%

Totals

Change from base Build<PHONE_NUMBER>:
-0.04%

Covered Lines:
28742

Relevant Lines:
63649

💛  - Coveralls


Proposal: add phpstan for installer

After having issues with previous alpha's (now fixed, see #220), why not benefit from phpstan to ensure the skeleton passes static analysis ?
I think the skeleton should not be opinionated. So the changes I've made are only tested with travis (no composer scripts) and deps are removed after install. The drawback is that it's not totally accurate (tests does run prior to an actual installation).
So for now it's open for ideas... (travis build stages with real installs... ?).
BTW, travis will probably stop to complaining after #229 is merged

@belgattitude I took the liberty of rebasing off current release-3.0.0, and fixing some errors phpstan flagged. All looks great!


[DM-3921] S3 Notifications

S3 Notifications
Notify an external backup service when there are new POSTs to the '/verify' path of the git-lfs web server.
This is one of two pull requests to help meet the git-lfs project requirement to externally backup git-lfs blobs. The other coming from the s3 to s3 backup service.
Summary
After an HTTP POST to /verify publish a message to redis' backup channel with the S3 key/object name.
Implementation details###
To facilitate this the after_do ruby library is used to keep notification code external to the lsst-git-lfs-s3 library. This is complex because Sinatra uses a single base :call method for all routes.
Redis pubsub is used to publish to the s3 key/object name to the backup channel. Redis is used instead of SNS to avoid any unnecessary dependencies on AWS services.
Concerns

The git-lfs-s3-server.rb file is arguably complex enough to be split between more than one file.
I don't have a complete understanding of Sinatra internals and though no problems have been found there may still be issues.
I have not tested redis over an extremely long time period. I don't know know what to expect from redis publish / subscribe after hundreds of days of run-time.

Approved by @jhoblitt. Merging.


Requesting multiple machine states

I'm looking to find all states that are not equal to destroyed or expunging, so it possible for list_virtual_machines to ask for multiple machine states e.g. state = 'Running, Stopped'.

You can just parse the response like
client.list_virtual_machines["virtualmachine"].find_all { |vm| %w[Running Stopped].include? vm["state"] }


runtime/cgo: relocation target _InterlockedExchangeAdd not defined in Windows build.

What version of Go are you using (go version)?

$ go version
go version go1.16.2 windows/amd64

Does this issue reproduce with the latest release?
Yes 1.16.2
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\xf\AppData\Local\go-build
set GOENV=C:\Users\xf\AppData\Roaming\go\env
set GOEXE=.exe
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\xf\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\xf\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.16.2
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\xf\AppData\Local\Temp\go-build1530397974=/tmp/go-build -gno-record-gcc-switches

What did you do?
I tried to build a project.
This project was previously succesfully built in go 1.14.6 on the same machine.
The interesting thing is I then uninstalled 1.16.2 and reinstalled 1.14.6 and it compiled fine again.
I then kept 1.14.6 and installed 1.16.2 as a second version on my system following these instructions. I was then able to build it with go1.16.2.
So to me it seems like the problem is not in the go compiler itself but in something that go uses.
I found a microsoft article which states that

This function is implemented using a compiler intrinsic where possible. For more information, see the WinBase.h header file and _InterlockedExchangeAdd

Does Go implement this Function itself or does go rely on gcc?
My gcc Version is 8.3.0
I don't really know which part of the project is relying on this function and I cannot share the project source code.
If someone knows how to trigger an include of that function just tell me I'll try to build it then.

What did you expect to see?
succesful build like it was on 1.14.6
What did you see instead?
runtime/cgo(.text): relocation target _InterlockedExchangeAdd not defined

/cc @ianlancetaylor

Go relies on a C compiler to implement the InterlockedExchangeAdd function.  This is only used by programs that use cgo, and such programs already require a C compiler anyhow.
I do not know why you only see this error in some cases.
CC @alexbrainman

I agree with @ianlancetaylor - your program must be using cgo. And cgo requires properly working C compiler - gcc. With all proper libraries installed.
Perhaps you gcc installation is broken.
Perhaps if you show your program and full error output, we could try and reproduce the error ourselves.
Thank you.
Alex

Like I said I cannot share the source code. It's proprietary company code.
I tested a little more the project also builds fine on 1.16.0 but still not on 1.16.2
I am unable to reproduce the error in a small example program.
I will close this now as it is very unlikely to be resolved and probably just a problem with the environment on my work machine.


Feature/2

Pull request description

PR meta checklist

[ ] Pull request is targeted at main branch for code
or targeted at stable branch for documentation that is live on bunit.dev.
[ ] Pull request is linked to all related issues, if any.
[ ] I have read the CONTRIBUTING.md document.

Code PR specific checklist

[ ] My code follows the code style of this project and AspNetCore coding guidelines.
[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[ ] I have updated the appropriate sub section in the CHANGELOG.md.
[ ] I have added, updated or removed tests to according to my changes.

[ ] All tests passed.

Sorry wrong repo


Useless linking to libdbus-1.so.3?

VSCode Version: 1.6.0
OS Version: Ubuntu 15.10

I'm packaging vscode via OBS for myself.
Today I noticed following warning in the logs:
[  309s] dpkg-shlibdeps: warning: package could avoid a useless dependency if debian/vscode/opt/vscode/code was not linked against libdbus-1.so.3 (it uses none of the library's symbols)
Steps to Reproduce:
$ ldd /opt/vscode/code  | grep dbus
	libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x00007f9df1580000)
...

Is linking with libdbus required?

@artem-sidorenko this would be either an Electron or Chromium problem.


Support Titan

First of all, thanks for making such a nice Gemini server for Deno!
Have you considered adding support for Titan? I could give it a go, but I would need some tips or assistance to get started.

Hi @joakim! Thanks for a good suggestion and, more importantly, for bringing my attention back to Gemini-sphere. It's been a long break!
As you can see in feature  roadmap, currently I have no plans to expand functionality to handle Titan protocol. The reason behind this is the fact that this project was intended to solve my basic needs in serving Gemini pages and small stateful apps in convenient for me express-like (or rather koa-like) way.
I believe that full Titan protocol is currently quite difficult to implement, due to hardcoded limitation to request size as per Gemini protocol specification, and the request-response approach I've used initially, instead of more flexible streaming one.

I'd be happy if you come up with generic protocol-agnostic connection handling approach using streams. This will allow to outsource handling of additional Titan's request contents to middleware, leaving Gemini as default option.
I can probably deal even with unreasonable amount of regressions within my 2.5 apps that are running on kaksik, due to its minimal API surface (it's only Application#use after all).

Hehe OK. I'm all for a protocol-angostic approach!


offsetof is actually a standard thing nowadays it would seem

First reported https://www.reddit.com/r/gamedev/comments/3bv7oq/torque_3d_37_released_linux_opengl_client/cspvouc
@dottools found the following:
http://lxr.free-electrons.com/source/include/linux/stddef.h#L15
http://lxr.free-electrons.com/source/include/linux/compiler-gcc4.h#L14
MSDN:
https://msdn.microsoft.com/en-us/library/dz4y9b9a.aspx

Oh, awesome! Nice work the both of you.


markdownlint README.md (deeply optional)

I don't know if this better or not, but it makes my VSCode markdownlint plugin stop complaining about these mostly stylistic choices

Surprisingly the lint is excellent.


[BugFix] NullableAggregateFunctionVariadic process only null column

cp https://github.com/StarRocks/starrocks/pull/28098 's bugfix
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 0 / 6 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/exprs/agg/nullable_aggregate.h
0
6
00.00%
[636, 637, 638, 639, 640, 642]


Login/auth. token retrieval takes 30 seconds with BIG-IP <IP_ADDRESS> Build 0.0.10 Point Release 1 => workaround

Hi,
probably more a "FYI" for anyone who is also hitting the same issue we had. For some reason BIG-IP <IP_ADDRESS> Build 0.0.10 Point Release 1 has some odd behaviour if one requests an authentication token and uses basic authentication to retrieve that token. It takes over 30 seconds for this request to complete! Funny part is that it works fast if one access the REST API via localhost / <IP_ADDRESS> (think ssh port forwarding). So I still think that this is just a bug in f5 because it worked with 14.x. (Using 1.4.0 but happens with 1.7.3 too.)
Anyway, the issue can be easily fixed by patching BIGREST: You need to edit big.py and utils/utils.py. Just search for "Required for 12.0.0, but not in 15.1.0".
# ---
# big.py

         # I guess those two lines can be commented also but didn't test (yet).
         if self.request_token is False:
            self.session.auth = (username, password)

         ...

         # Required for 12.0.0, but not in 15.1.0
         self.session.auth = (self.username, self.password)  # <= comment this line
         response = None

# ---
# utils.py

      response = requests.post(
        f"https://{device}/mgmt/shared/authn/login",
        json=data, verify=False, auth=auth)

# =>

      response = requests.post(
        f"https://{device}/mgmt/shared/authn/login",
        json=data, verify=False)

Maybe I will provide some patch sometime. But I hope that information is helpful anyway for someone.
Kind regards,
Dietmar

diff -x '*.pyc' -x '*.bak' -r REDACTED/big.py ./big.py
439c439
<         # self.session.auth = (self.username, self.password)
---
>         self.session.auth = (self.username, self.password)
diff -x '*.pyc' -x '*.bak' -r REDACTED/utils/utils.py ./utils/utils.py
57c57
<         json=data, verify=False)
---
>         json=data, verify=False, auth=auth)
88c88
<         json=data, verify=False)
---
>         json=data, verify=False, auth=auth)
[REDACTED@REDACTED bigrest]$

Hi,
following https://support.f5.com/csp/article/K69245523 this does not look like a bug on the F5 side, it looks like 'works as designed', as they say that basic authentication may be slower and take more time to finish. So if token authentication should be used, then the login should not happen via basic authentication.
Greetings,
Eric

Thanks for the information, closing this now.


Support for Node 12

Add support for Node version 12, which I think is dependent on https://github.com/nodejs/nan/issues/849.

Nan supports node 12. In that thread @bnoordhuis says many issues are caused by old nan versions

Yeah, this is fixed by #150, there is nothing wrong with Nan.

Hi,
Thinking of trying this library. Is this still an open issue?

@innerop I've just merged the PR that addresses it. Will push a new release to NPM soon.


User based config

How do I set up a user based config for stfp? I currently place the sftp.json in the .vscode folder in my workspace folder but I want a global configuration for all my projects. Is there a way?

I was wondering this too, having to set a workspace up for it is just weird :/


Button tap event runs twice

Environment

NativeScript-Angular: 5.4

Describe the bug
Tap event runs twice on button double tap.
Created blank angular app
<GridLayout class="page">     <Button (tap)="onButtonTap()"></Button> </GridLayout>
async onButtonTap() {
    await dialogs.alert("Alert");
}

Double tap on the button quickly.
Sometimes tap event runs twice.
Sometimes second tap is intercepted by the alert dialog (first tap opens the dialog and second tap closes it) as expected, sometimes it's not and onButtonTap method runs twice.

Hi @valera1401,
I've checked the case on my side, however, was unable to recreate a problem with the tap event with latest {N} (v6.0). On that matter, can you test with the most recent {N} version? Also, can you provide more info about the device/emulator that you are using for testing?

Hi @tsonevn ,
Thank you for your response.
ok I will check it with NS 6 in a few days.

Unfortunately I've reproduced the issue with the NS 6.0.3
Clean NS install.
Created a new project with tns create --ng command
I'm using the Android studio Android emulator (Android 9 API 28) and I saw that the issue was reproduced on the Samsung S10 as well.


SQLDatabase async support

Add support for async sql database (by utilizing sqlalchemy apis). Could do with some more tests. But, would like some comments while i add tests.
Sample usage with SQLDatabaseChain as follows:
#!/usr/bin/env python3
import gevent.monkey
gevent.monkey.patch_all()
import asyncio
import asyncio_gevent
asyncio.set_event_loop_policy(asyncio_gevent.EventLoopPolicy())
import langchain
langchain.verbose=True
from langchain.utilities import SQLDatabase
from langchain.llms import OpenAI
from langchain_experimental.sql import SQLDatabaseChain
async def say(what):
cnt = 0
while cnt < 5:
print(what)
await asyncio.sleep(1)
cnt += 1
async def do_db():
db = await SQLDatabase.from_uri_async("sqlite+aiosqlite:///Chinook.db")
llm = OpenAI(temperature=0, verbose=True)
db_chain = SQLDatabaseChain.from_llm(llm, db, verbose=True)
await db_chain.arun("How many employees are there?")
async def main():
task1 = asyncio.create_task(say("HELLO"))
task2 = asyncio.create_task(do_db())
asyncio.gather(task1, task2)
asyncio.run(main())

@eyurtsev Any comments on the PR?

@sudranga Apologies for taking so long to get back to you.
If you're interested in pursuing this, feel free to rebase from new master (code has moved to community), I'll help to take care of the review, but we'll need an implementation that does not depend on nest_asyncio.
I'm going to close for now since the PR, but if you're pursuing this feel free to open a new PR


Invalid object name dbo.table

Hi everybody.
I don't know more what I can do.
What's wrong with my code?
`
package main
import (
_ "github.com/denisenkom/go-mssqldb"
"database/sql"
"log"
"fmt"
)

func main() {
connectionDB()
}

func connectionDB() {

log.Println("Main:")

log.Println("Opening")

db, err := sql.Open("mssql", "server=pwbt.database.windows.net;Initial Catalog=dbo;user id=admin-jose;password=password")

if err != nil {
    log.Println("Open Failed: ", err.Error())
}

log.Println("Opened")

log.Println("Pinging")

err = db.Ping();
if err != nil {
    log.Println("Failed to ping: ", err.Error())
}

log.Println("Pinged")

x := 2
rows, err := db.Query("select Nome from dbo.tbPessoa where Id=?", x)
if err != nil {
        log.Fatal(err)
}

defer rows.Close()
defer db.Close()
fmt.Println(rows)
fmt.Printf("bye\n")
    }

`
It can connect but can't select.
 That would be my guess.
On Sat, Feb 25, 2017 at 10:55 AM Joseph<EMAIL_ADDRESS>wrote:

[image: select-golang]
https://cloud.githubusercontent.com/assets/26029170/23333889/c8589840-fb72-11e6-9928-4be832a623c3.PNG
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/denisenkom/go-mssqldb/issues/223#issuecomment-282504346,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAuFscQPtboTUL1RQN4cRU2hglQz9cYfks5rgHkqgaJpZM4MMGTV
.

@kardianos thanks so much!
 I add the "database=PWBT" on connect string and it works!
It look like this way:
db, err := sql.Open("mssql", "server=pwbt.database.windows.net;user id=admin-jose;password=password;database=PWBT;port=1433")


should mv maintain attributes?

I'm chasing down an issue in nushell, linked below, and I'm wondering what the standard is for moving files to/from internal/external drives and preserving file/directory attributes like timestamps. The OP reports that nushell's mv, nor nushell's uutils umv, nor your mv command maintain these attributes but the native mv does. Thoughts?
https://github.com/nushell/nushell/issues/11943
Kind of related
https://github.com/uutils/coreutils/issues/4192

It probably should yeah. I haven't tested this myself.

Thanks @tertsdiepraam. Closing this issue as you answered the question but I opened a related feature request issue #6004.


add ci test for gpu

update test script to use the compiled binary
add GPU compile dockerfile and CI test
fix the bug that "even if HTTP status code is not 200, it can pass the CI"
add description of SERVING_BIN to COMPILE.md
fix import error and fix multi-card parse in gpu web part

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Your Name seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Modify the update_sub_ids.py script to ingest api

The update sub ids that populates the submission ids in the readme currently queries the tracker api which is likely to go extinct so we may want to modify this to work with the ingest api which is likely to be more stable.
Fairly low priority for now.

We need to look at this at some point, but it is currently impossible without adding a --token argument (projects endpoint is protected)


Add fea generation support

This PR enables fonttools to generate fea syntax from a fea ast, as per issue #772. I notice that #479 is not ast based and simply generates text as it goes.
One calls asFea() on the output from a Parser().parse() and is returned a string containing the generated fea text.
At this point in the PR's history not all the tests are giving identical results. This is due to the following features not yet having been implemented:

Ranges are expanded in the parser and not contracted in fea generation. This might be worked around by keeping a side copy of the original glyph list specification including ranges.
nameid attributes are often defaulted and expanded in the parser. These are not defaulted out in the fea generation.

In order to get the tests to pass, many of them have been adjusted in layout and some keywords regularised. These need to be reviewed to ensure that the tests are still testing what the test was originally designed to test. A special comment can also be used to acknowledge different output from fea2fea for a test. E.g. feaLib/testdata/size.fea

Thank you, looks good to me! There’s a minor typo which I’ll fix myself.

wow this is huge! thanks a lot Martin! 💯
I'm look forward to use this.

cool!

I was wondering if instead of, or in addition to, asFea() methods, we could have __str__ methods for each ast object, so one could do str(something) or print(something).


Add result timestamp to results API

Signed-off-by: Frank Jogeleit<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.395%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3503

Relevant Lines:
3711

💛  - Coveralls


Magazine ammo uses do not update in attack popout

Issue appears on 5.11.2
How to Reproduce

Take a PC, add repeating crossbow and two separate magazines with different charge levels (e.g. 3/5 and 5/5)
Drag strike from repeating crossbow to macrobar
When macrobar is clicked and popup is rendered, try switching between magazines
Indicator of how much ammo is in each magazine will not change between 3 and 5 rounds in response to user input

Note that this bug does not appear when changing magazines from the character sheet, only when operating from the macrobar.  Issue confirmed to not manifest on 5.10

Fix confirmed!  Thank you.


[Task] The tests in thenewboston-node may contain information about possible features and input / output to expect from future endpoints (POC)

Task
Contributors are able to complete this task and earn thenewboston coins.  Check out the labels to learn how much you can earn for contributing by completing this task.  Please make sure to be honest if you wish to contribute by saying you can't finish this and we can just un-assign you with no harm done!  There is no point in delaying tasks from being completed for miscommunication!

Overview
In https://github.com/thenewboston-developers/thenewboston-node/tree/master/thenewboston_node/business_logic/tests
You will find different tests for features that are internal as well as possible exposable features.
Compile a list of tests that could be as part of the final API documentation when this task will be ready https://github.com/thenewboston-developers/thenewboston-node/issues/29
Note: this task is ongoing and should be visited as new tests are added or more clarification is gotten from the team working on tnb node
Submit a google doc with the list of tests/features which look like public features as well as possible places where they can fit in our existing system or as part of a brand new set of classes.
Behavior

a living document that identifies and groups possible features based on existing tests.

Please ask for this task to be assigned to you and earn and its sweet reward 😉
Remember to include your account number in your PR description for us to pay you 💰
** Pull Requests **
All Pull Request should be made to development branch, read contributors guild for more information about contributing

@zinoadidi Please, be aware that the API will be ready after this task is completed: https://github.com/thenewboston-developers/thenewboston-node/issues/29

@dmugtasimov, the Plan is to keep the sdk development in sync so that BETA features are available as soon as they are ready on node
That's why I wrote earlier asking about documentation.
It would be nice if rhe apis are made as features are completed rather than at the end of the whole thing so we can follow as well and make corrections were necessary.
In a nut shell we are not interested in creating apis we just need to know what features are available what data is needed to send and what output

Maybe It's time to make a branch called beta.

yea @mrbusysky the branch comes sooner;
I just need a concrete task that will go into it + I want all changes that come from Account manager integration to be done before switching focus/attention

I'll work on this

https://docs.google.com/document/d/1r_Zd5jOdS2teXQwuKYtDpkPOnr99jOFYbzKIPxAPdGs/edit


Remove special Firefox instructions in >=.NET 6 sections

Fixes #33230

Internal previews

📄 File
🔗 Preview link

aspnetcore/security/enforcing-ssl.md
Enforce HTTPS in ASP.NET Core

I think these changes were probably prompted by a comment from me, but I can't recall the context.  Would you happen to have a link or something?

I think these changes were probably prompted by a comment from me, but I can't recall the context. Would you happen to have a link or something?

#33221

Addressed by #33221


Update README.md

Describe your changes
added readme badges
Screenshots - If Any (Optional)

Issue ticket number and link - If Any
Closes #108
Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] Starred the repository.
[x] Added My Name to the Contributor's List.
[x] Followed the repository's Contributing Guidelines.
[x] I ran the app and tested it locally to verify that it works as expected.

Thanks @S-ishita. Nice


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

Thanks @bryant1410 👍