def_load_bio(): Free |biosk| more carefully

If there's anything in the |biosk| stack, the first element is always
the input BIO.  It should never be freed in this function, so we must
take careful steps not to do so inadvertently when freeing the stack.

I still don't know how to reproduce this outside of that one directory, but I can reproduce it without this patch and not with this patch. Valgrind says there are no leaks.

Triggering the fault before this patch is easy, all you need is two files:
entry.cnf:
.include broken.cnf

broken.cnf:
[sect

and then...
./util/shlib_wrap.sh fuzz/conf-test entry.cnf

(oh, and configuring with enable-asan, I believe)

Merged.
85aebfcc6eedceaed34012a8b2c27c43ef402f95 def_load_bio(): Free |biosk| more carefully


node throws error end exits?

hey,
first great work you have done....!
but from time to time when trying to connect to bittrex
the bitrex-market throws an error (on connection) and the enire node brakes and exits
is it possible this to be fixed?

Duplicate of #21.


Add Trillian

Added account deletion information for Trillian to the sites.json file.

Hello @Microgranules ,
This repo is not being maintained anymore, but we are trying to keep it alive on a detached fork here, would you kindly submit your PR there and close this one here? :)


update(userspace/libsinsp): support timestamp priority in async event injection

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area libsinsp
Does this PR require a change in the driver versions?
What this PR does / why we need it:
This is effectively a new feature. A friction that we discovered having when generating async events, is not being able to control their timestamp.
Currently, async event producers are "passive" from this perspective, and are not able to specify any timestamp at all. The current behavior is to have multiple (potentially concurrent) async event producers, and one single consumer that is the inspector listening and owning the async queue. This is used for container events, user/group events, and plugin async events. When an event is popped from the queue by the inspector, it is assigned a new timestamp based on the current time or the most recent time seen in the event stream.
However, this is a limitation for some use cases in which the async event registers a phenomena of which the timestamp is known. In those cases, we have that:

The inspector will overwrite the timestamp with its own logic when popping the event. Even if not doing so,
The async queue guarantees not timestamp-ordering among the async events
There is no way for knowing whether an async event must appear before or after the most recent libscap event in the overall event stream

Think about new fun developments in eBPF - we may have cases in which we known about some phenomena (e.g. an execution), before receiving the syscall event from the kernel ring buffer, which can't be controlled nowadays.
Moreover, further analysis (cc @VadimZy) show that the tbb queue is not the optimal instrument for this use case. In our case we have a Multi-Producer-Single-Consumer queue (so any optimization multiple consumers is a no-gain cost), we expect producers to not be that many (low concurrency and saturation risk), and the event throughput is orders of magnitude lower than the one of the syscall events (the queue will be empty > 50% of the time). With these assumptions, we're discovered gaining performance by simply putting an atomic check on the queue and eventually acquiring a mutex whenever necessary. This also removes the need of tbb in this codepath, which gave us many headaches in the past from a compilation perspective (e.g. welcome async events in our WASM build :)).
Which issue(s) this PR fixes:
Special notes for your reviewer:
I propose bumping the plugin API version by a minot number to 3.2.0. Since this is effectively a new guarantee that plugins can leverage, I think it makes sense to follow the minor bumping logic as we always did. Otherwise, plugins depending on 3.1.0 will have no way to know if they can set custom timestamps or not.
Does this PR introduce a user-facing change?:
update(userspace/libsinsp): support timestamp priority in async event injection

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

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce]

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

/milestone 0.14.0

So, what are the remaining cases for tbb in our build? sinsp_dns_manager alone?

So, what are the remaining cases for tbb in our build? sinsp_dns_manager alone?

That on libs, yeah. It is also used on Falco for the output queue. However, I think that on Falco we may adopt this ordered queue eventually (or something similar), since that's another case of MPSC queue.

Refactored attempting to address all the reviews! Thanks for the great feedback. This should now be more transparent and readable.

LGTM label has been added.  Git tree hash: 3d8f1cccd399c2b4d12cd08680213057c65b052d

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

Needs approval from an approver in each of these files:

OWNERS [FedeDP,jasondellaluce]

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

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

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,jasondellaluce]

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


vagrant synced_folders bug fix

I think this is a bug in the latest vagrant (1.7.2) version, but I get the error as outlined in this thread: https://github.com/mitchellh/vagrant/issues/5199#issuecomment-98874689. Basically an initial vagrant up spins up without any issues, then if I vagrant halt, vagrant up --provision it'll produce an error relating to the file '.vagrant/machines/drupaldev/virtualbox/synced_folders'. Removing this file will fix this issue and I added the proper code to the vagrantfile to do this automatically. I'm sure the next version of vagrant will fix this, but I thought this fix was helpful for me and could help relieve others frustration.
I hardcoded the 'drupaldev' and 'virtualbox' parts of the synced_folder path, but if you know of any variables that can replace these that would be great. I'm new to ruby and couldn't quite track this down.

This seems to cause an error when starting from scratch :-1:  Hopefully vagrant will address this bug themselves soon.

Realized triggers need to be added for this to work:
vagrant plugin install vagrant-triggers


Allow to set a static IP address (MEGH-5506)

Is your feature request related to a problem?
No response
Describe the solution you'd like.
No response
Describe alternatives you've considered.
No response
Additional context.
Do you plan to allow setting static ip address for esp-rainmaker devices anytime soon?

ESP RainMaker uses the underlying esp-idf Wi-Fi Provisioning component. Since that component itself does not provide an option to set static IP address instead of DHCP, RainMaker cannot have it. You can file an issue under esp-idf for this feature request.

Thanks for your reply.
Issue created in the esp-idf repo: https://github.com/espressif/esp-idf/issues/13791


fix(tests): adds additional operator tests

:tada: This PR is included in version 1.36.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


XMLhttp Request error while signing up / logging in

OS: Windows
Browser: Opera GX
Using excode web version not appl.

The supabase db was locked due to inactivity.
The issue is fixed now


chore(website): add support for including descriptions for Typescript in playground

Description

Added checkbox in playground to include descriptions.

Related issue(s)

fixes #1174

@jonaslagoni PTAL

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.404%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
4732

Relevant Lines:
4991

💛  - Coveralls

/rtm


Create a custom Thali PouchDB constructor utility

Problem:
In order to use PouchDB against a local file (as opposed to a remote URL) in JXcore on mobile we need to set two options, one is called db and we have to set it to leveldown-mobile and the other is called prefix and it specifies what directory the DB's files are to be stored in. The prefix matters because on mobile there are only certain directories we can store things in.
Everything was fine and good until PouchDB broke prefix badly in the last major release. In the old days prefix ONLY applied to local DBs. But now pouchDB applies prefix to both local DBs and to remote DBs. In other words if I set new PouchDB('foo', {prefix: '/bar'}) then PouchDB will try to create foo's files in the /bar directory. If I call new PouchDB('http://foo.com', {prefix: '/bar'}) then now it does something really bizarre like try to connect to the server /barhttp://foo.com or something like that. Bad. Bad. Bad.
Now you may ask, who cares? Just make sure not to pass in prefix to PouchDB instances that use a URL. But it's not that simple. The problem is replication. When we replicate we MUST start by creating a var remotePouch = new PouchDB('http://foo.com', {stick in a bunch of ajax options to configure PSK and other stuff here}) in order to configure all of our network options correctly, set up PSK, etc. Then we take that object and we have to call remotePouch.replicate.to(foo). Where foo is the local dB name we are writing to. Now replicate.to() does take options but one of those options is not prefix. So how do we make sure that we read foo from the right directory?
Historically we did this by telling people to use the defaults feature in PouchDB. This feature lets one set a number of default constructor options and when PouchDB creates a new instance of itself (for example, it will create a new instance of itself to represent foo above) it will use those defaults. So we would set prefix on the defaults and when PouchDB created a new instance of itself to represent foo it would automatically have the prefix. But if we use that feature now then it would break the HTTP URL since the default applies to all calls to new now, not just to local files.
So how do we let people set the prefix just for local files and not for remote URLS?
Solution:
The solution is here. This is a function I wrote with the help of Nolan Lawson (it's really just stolen code from PouchDB) that wraps the constructor such that when the constructor creates a new version of itself if the version is for a local file then it will set the db to leveldown-mobile and the prefix to the right directory and if it is for a remote URL it does neither.
But that function right now only exists in our test code. What we need to do is extract it from the test code and we need to update it so it takes two arguments. The first argument is the PouchDB object to be wrapped (no reason to make Thali itself dependent on any particular version of PouchDB) and the second argument is the defaultDirectory.
I do not think we should build this into thaliManager. We should keep it as a stand alone utility because that way people can do other weird stuff with PouchDB and we won't break.
Work Items:
So please:

[ ] Extract the function from the test file and move it into next generation as a utility function, please change the args as I discuss above
[ ] Remove the test version completely and replace our call to it with the 'real' version (so our tests don't break)
[ ] Add tests to our test infrastructure to make sure that the utility is working properly

The code is written and now he just needs the test.


Different configs for environments

Hello!
Is it possible to use different configs for environments? For example, enable notifications only for specific environment, not for all?
Thanks

Yes, I think so.
Look at the the example at https://codeception.com/docs/07-AdvancedUsage#Current-values for WebDriver module how to achieve this.
Try
env:
    development:
         # extension not enabled
    production:
         extensions:
            enabled:
               - Codeception\Extension\SlackExtension

I personally prefer the configuration via command line. I always have the extension inactive in yaml configuration. Then I add --ext SlackExtension to my codecept run --ext SlackEtension depending on which stage i'm in my CI/CD pipeline.

Only one variant is working.
codeception.yml:
... extensions:   enabled:     - Codeception\Extension\RunFailed     - Codeception\Extension\Logger   config:     Codeception\Extension\RunFailed:       fail-group: failed     Codeception\Extension\SlackExtension:       messagePrefix: '*Smoke-Test*'       webhook: https://hooks.slack.com/services/...       strategy: always       extended: true       extendedMaxLength: 150       channel: '#any-channel'
And then
php codecept --debug run api --ext SlackExtension
variant with
env:     development:          # extension not enabled     production:          extensions:             enabled:                - Codeception\Extension\SlackExtension
Not working.
It would be great if you could set different prefixes for different environments, for example
messagePrefix: 'DEV Smoke-Test'
messagePrefix: 'STAGE Smoke-Test'
messagePrefix: 'PROD Smoke-Test'

Take a look into https://codeception.com/docs/06-ModulesAndHelpers#Dynamic-Configuration-With-Parameters .
I create custom messagePrefix myself as well. I use different .env files for each environment.
They are loaded in by adding this to your codeception.yaml:
params:
    - .env

The configuration for the SlackExtension's messagePrefix looks like this:
       messagePrefix: '*%ENV% Smoke-Test*'

Before the test run I copy the appropiate .env file to .env, f.e. cp .env.staging .env
I start my test run as usual with php codecept run --ext SlackExtension.

tl;dr
Try to find a solution with the possibilites Codeception offers. The documentation is great. I cannot how to improve the extension itself to help with your problem.

I close those issue now. Issue should be solved with existing Codeception framework features not by extending the extension.


Compat fix for Policyfile integration

With this commit, chef-dk gem has changed the functionality to export the cookbooks into cookbook_artifacts directory instead of cookbooks directory.
This PR contains the change required to support that.
I think the correct thing to do will be to make a chef-dk release and set the cbdir here based on the chef-dk version in order to support the newer and the older versions.
What do you guys think? @danielsdeleo, @jtimberman @sethvargo

That works for me

Does ChefSpec allow arrays for the cookbook path? That would be the simplest way to support both at once that I can think of.

I'll try @danielsdeleo 's suggestion and see what happens.

Umm - it should - it just passes it to Chef as-is.

@sethvargo @danielsdeleo This works fine!

LGTM

thanks @sethvargo... hope all if good :smile:

Thanks!


Update language in government.md about closure rule availability

This PR updates the OG-Core documentation on government closure rules to specify that only one of the three methods described is currently an option in the model. This PR addresses Issue #783.
cc: @jdebacker

@jdebacker. Any idea what this error is in the CI on this pull request, which only changes one line in the documentation?
E   ImportError: cannot import name 'scope2index' from '_pytest.fixtures' (/usr/share/miniconda/envs/ogcore-dev/lib/python3.8/site-packages/_pytest/fixtures.py)

My most recent commit removes the import of the _pytest.fixtures.scope2index function. This function was the cause of the failing CI tests. And the import was only in test_SS.py and it was not used in those tests. I ran all the test_SS.py tests locally with the change and they all passed.
ogcore/tests/test_SS.py ................................                 [100%]

OK. Now I have three failing tests that are the same as the tests that are failing in PR #785. I'll work on this.

Codecov Report

Merging #784 (2898373) into master (32a1866) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #784   +/-   ##
=======================================
  Coverage   84.13%   84.13%
=======================================
  Files          19       19
  Lines        3411     3411
=======================================
  Hits         2870     2870
  Misses        541      541

Flag
Coverage Δ

unittests
84.13% <ø> (ø)

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

@jdebacker. This very simple PR is now ready for your review.

Thanks for clearing up the documentation @rickecon!


Disk spill metric

Adds a task level disk allocation high watermark accumulator to the GpuTaskMetrics.
Also fixes an issue where direct spills from device to disk were not being tracked in the existing Spark disk spill metric.

build

build

build

build

build


NPM is flagging this package as having a High Vulnerabilty

After npm install:

Duplicate of #117.


[AutoPR postgresql/resource-manager] PostGreSql: added java readme

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6437

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/6166


Add image pull policy

This PR add option image.pullPolicy to allow setting traefik app deployment container imagePullPolicy value, defaults to IfNotPresent.

Hey @j3r0lin,
thanks for your contribution.
Could you please add a proper description to your PR and bump the version on the chart? Otherwise the build will fail.

@SantoDE updated, please review again.

Thanks. We should wait for #221 to be merged first, then update the the versions here one last time and merge then. Sounds good to you?

ok, let me know if #221 merged.

Merged @j3r0lin.
Once you've fixed the conflict, we're good to go

@SantoDE sorry for the delay, I have updated the branch, but the travis job failed cause of installing helm client.


Two or more discrete singletons clash - cannot be subclassed more than once

Fails this test:
- (void)testSingletonDoesNotInterfereWithOtherSingleton
{
    SingletonByChoice *singleton1 = [SingletonClass1 sharedInstance];
    SingletonByChoice *singleton2 = [SingletonClass2 sharedInstance];
    XCTAssertNotEqual(singleton1, singleton2);
}

So the SingletonByChoice class can only be subclassed once.

This ironically defeats the whole purpose of having a parent class!


Query hive external table: ERROR 1064 (HY000): com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: com/amazonaws/auth/AWSCredentialsProvider

Steps to reproduce the behavior (Required)

CREATE EXTERNAL RESOURCE "hive_resource"
PROPERTIES (
  "type" = "hive",
  "hive.metastore.uris" = "thrift://ip:9083"
);

create external table hive_tbl (
eventid bigint(11),
eventname varchar(100),
eventtime bigint(20),
userid bigint(11),
custom string,
dt bigint(11)
)
engine = hive
PROPERTIES (
	 "resource" = "hive_resource",
    "database" = "default",
    "table" = "json_copy",
    "hive.metastore.uris" = "thrift://ip:9083"
);

select * from hive_tbl;

In this step, it raised an error: ERROR 1064 (HY000): com.google.common.util.concurrent.ExecutionError: java.lang.NoClassDefFoundError: com/amazonaws/auth/AWSCredentialsProvider
My hive storage is in S3. and I also tested it using hdfs storage, the error still happend.
And I use Amazon ec2.
Expected behavior (Required)
Can query data without error.
Real behavior (Required)
StarRocks version (Required)
2.3.9 895425a

@Alxe1 could you upgrade your cluster to version 2.5, then you can query Hive data by creating hive catalog

@Alxe1 could you upgrade your cluster to version 2.5, then you can query Hive data by creating hive catalog

Yes, I can, but is there any solutions that can solve this problem using version 2.3?


7/09 PM Publish

Docs Build status updates of commit 5b22d5d:
:clock10: Full build: the average full build time is 28 min(s) 21 sec(s), this is based on the last 444 build(s) for this repository.

Docs Build status updates of commit 5b22d5d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azuresmps-4.0.0/Azure/Set-AzureDataDisk.md
:white_check_mark:Succeeded
View (azuresmps-4.0.0)

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


first pass at reverting PR #5309; see TODOs

Description
Partial work on reverting PR #5309. I have some open questions in pkg/services/invoice/syncada_sftp_sender.go.
References

Jira story
slack a-team pairing thread

Closing this one as it is now superseded by John's PR #5384. 😄


Qr scanners and codes for passing around guardian links / verification codes.

 This adds qr scanning and qr codes for all the inputs/fields that need to get passed around between the guardians.

Note: getting this annoying play() being called suring state change error that I can't pin down, it still works it just throws the runtime error when you open the QRScanner and you click out of it and it works.

I'll take a look in a bit. I have a bunch of high-priority tickets on my sprint board right now.

 Will rebase but then could use some help or maybe just ask around on nostr for someone who might know what's up


Chat Improvements

Doesn't close any issues, but with Glimesh/glimesh.tv#831 being merged, I decided to work on chat a bit.
What this PR adds:

Badges before usernames for Admins, Moderators, Streamers and Channel Subs
Yellow usernames for Gold Supporters
The gold avatar ring for all Supporters
Borders for Follow and Subscription messages
Hides the colon between the name and the message when the message is a Follow or Sub message

The badge icons are inspired by MemoryLeakDeath's as-yet-unmerged PR where he's been working on the same thing for the site.
Here's some screenshots:

Great work! Looks awesome, will be neat to have this style on the site too.


Attitude

@alovak , we'll need to add the alias_method for match_json to map to include_json. Let me know where you'd like that to go (or feel free to edit this PR directly).

it's awesome! mom approved! yeah!
@yazinsai can you add some examples into README to demonstrate one of our cool feature: clear failure messages? You can take them from specs like this one:
"{"one":{"array":[1,2,3,4]}}" was not found in
[{"one":{"array":[1,2,3]}}]

@yazinsai I've added match_json. Let's merge this branch now and add examples with failure messages later. Thanks man! Text is super!


made getEnabledSteps accessible from wizardhandler

Makes it easy to create your own step indicator

@TheBekker Can you fix your white space on the comment and rebase your fork so I can automerge?
Thanks for your contributions!

Should be up to date now

Could we get this into master?

@TheBekker yeah sorry. I just went through all the issues last night and rounded up about 5 enhancements an a few bug fixes for a 0.6.0 release. Scheduled for January 1st. This and many others will be in master, npm, and bower then. Sorry for the delay. Trying to get back on top of it.


setup data download for the DIA files in the server

The Download raw datasets does not work for the DIA module for the moment.

Are available now


Beam wallet crashes on MI-6

Describe the bug
Beam wallet crashes on MI-6 on launch
To Reproduce
Steps to reproduce the behaviour:

Install wallet application
Open

Expected behaviour
Should not crash
Setup
mi6
android 8.1

@vain-onnellinen  fixed


Support ExtractTextWebpackPlugin

This plugin should be able to support operating alongside ExtractText since it is such a frequently utilized plugin.
Fixes #1.
TODO:

[x] Write a test
[x] Fulfill the test for webpack 1
[x] Fulfill the test for webpack 2

thanks!

Thanks a lot for this!


bump go.mod to go 1.14

Proposed Changes
From https://github.com/golang/go/wiki/Modules

When the main module contains a top-level vendor directory and its go.mod file specifies go 1.14 or higher, the go command now defaults to -mod=vendor for operations that accept that flag.

This preserves our prior behaviour of using packages from our vendor dir
Release Note

NONE

will this build with go1.14?

i would think the build tests would use go1.14 but it seems like it doesn't

go version go1.13 linux/amd64

/test ?

/test all

From #test

chizhg  12:10 PM
Hi all, we have switched all the Prow jobs running on master branch to use Go 1.14, please feel free to start using new features in Go 1.14, and let us know if there are any issues!

/assign @mattmoor


Implement tests for Send

[x] Simple Send, ReceiveBatch using Queue/Topic/Subscription
[x] SendBatch, ReceiveBatch using Queue/Topic/Subscription
[x] ScheduleMessage, ScheduleMessages using Queue/Topics/Subscription.
[ ] Cancel a scheduled message using Queue/Topics/Subscription

@ShivangiReja I am adding the test item for cancelling a scheduled message in the above list. So, re-opening this issue

@ramya-rao-a would it make sense to create a new issue for this?

I am ok either way. Will create a new issue


fix Fix CloudPartition.getVisibleVersion return value

Proposed changes
Issue Number: close #xxx
The return value of Partition.getVisibleVersion is 1 if the partition is empty, this PR unifies the behaviors between Partition and CloudPartition.
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Code coverage (CI)

This applies to scanpy as well, but it's easier to try these things here since the test-suite runs faster.
There should be some kind of check on PRs for coverage. It should be really obvious if new code is tested, or if coverage goes down. There have a been a few cases in scanpy (mostly with external) where code just wasn't being tested on CI due to configuration issues. I'd like to avoid this.
Codecov
Codecov seems like a popular solution. I think we had it enabled at one point, but don't remember why we stopped. I remember finding it annoying, and that it gave a lot of notifications. I assume there are ways to make it less annoying, since I haven't been bothered by it recently when I contribute to repositories with it on.
It would be pretty easy to turn on, just add this to test coverage jobs.
It seems very configurable, but without a huge amount of documentation.
Options for integrations include:

a bot comment on a PR with coverage information that gets updated
Using github checks

Features I'd like

I'd like to be able to see which test covered which lines. I don't remember seeing this happen with codecov, but maybe they allow this now. We can generate this output with contexts.
A diff of coverage for a PR
A badge for the repo
Not necessarily failing a PR if some coverage isn't met, but definitely making it visible

Sure, let’s tackle all this directly after #478!

Sure, let’s tackle all this directly after #478!

As noted by @flying-sheep in https://github.com/theislab/scanpy/issues/1576#issue-783385380, there is some support for this directly in azure via an azurepipelines-coverage.yml config file. Unfortunately it looks like it's not available for python projects yet:

While you can collect and publish code coverage results for many different languages using Azure Pipelines, the code coverage for pull requests feature discussed in this document is currently available only for .NET and .NET core projects using the Visual Studio code coverage results format (file extension .coverage). Support for other languages and coverage formats will be added in future milestones.

As noted by @flying-sheep in https://github.com/theislab/scanpy/issues/1576#issue-783385380, there is some support for this directly in azure via an azurepipelines-coverage.yml config file. Unfortunately it looks like it's not available for python projects yet:

While you can collect and publish code coverage results for many different languages using Azure Pipelines, the code coverage for pull requests feature discussed in this document is currently available only for .NET and .NET core projects using the Visual Studio code coverage results format (file extension .coverage). Support for other languages and coverage formats will be added in future milestones.


"disableRoleValidationAtScopeCreation" system property not documented properl

Description:
Reported by @johannnallathamby
The "disableRoleValidationAtScopeCreation" system property seems not to be documented under a suitable section. It is currently only documented under the QuickStartGuide section which is not right.
This property is becoming a very critical property to know about when we combine identity federation with API Manager use cases. But not a lot of folks inside WSO2 even are aware of this property and that may be because it is documented in the wrong place.
I am not sure what would be the correct section to document this, as this property is relevant to all kinds of identity federation scenarios with APIM. If you had such a section in the APIM docs that would have been the ideal place to document this
Suggested Labels:

Suggested Assignees:

Affected Product Version:
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

Fixed in https://github.com/wso2/docs-apim/issues/1927


Edit drawed polygon - Cannot read property 'title' of undefined

[X] I'm reporting a bug, not asking for help
[X] I've looked at the documentation to make sure the behaviour is documented and expected
[X] I'm sure this is a Leaflet Draw code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
[X] I've searched through the issues to make sure it's not yet reported

How to reproduce

Leaflet version I'm using: 1.03
Leaflet Draw version I'm using: 0.4.9
Browser (with version) I'm using: Chrome 56
OS/Platform (with version) I'm using: Windows 10
step 1: Drawing a polygon. Work fine.
step 2: Edit the drawed polygon, I get this error to the console: Cannot read property 'title' of undefined

What behaviour I'm expecting and which behaviour I'm seeing
With the version 0.4.2, it work fine.

I've add this line an line 155 to the file Leaflet.draw.js
                    },                     clearAll:{                         title: 'Clear all layers.',                         text: 'Clear All'                     }
And now it work.


Update state machine for passported applications when dwp override fe…

…ature is on
What
Link to story
Describe what you did and why.
Checklist
Before you ask people to review this PR:

[ ] Tests and rubocop should be passing: bundle exec rake
[ ] Github should not be reporting conflicts; you should have recently run git rebase master.
[ ] There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
[ ] The PR description should say what you changed and why, with a link to the JIRA story.
[ ] You should have looked at the diff against master and ensured that nothing unexpected is included in your changes.
[ ] You should have checked that the commit messages say why the change was made.

@mpw5 ah yes, I've updated the tests so the factory for the application is in a 'checking details' state to prove it still passes.


CB-26917 Fix revert in 0a6f900

Revert was reverted in https://github.com/hortonworks/cloudbreak-images/pull/1036 so this is no longer needed


CLI Links Plugin

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Please include a comment on why an issue is being closed - is this a problem or not? If not, why?

It's not a problem.
Enabling AT_FDCWD in <fcntl.h> would require setting _GNU_SOURCE. I set it and then the latest code could compile.

Ah great, thank you. Now the issue is also useful to others that may run into the same thing.


Clean up comments in code

Cleared unnecessary comments from the code, added comments about the use of functions and other components of the code.


Back to the top automatic links

A potential enhancement to a page could an option for the use of automatic 'Back to the top' links for each page, maybe if they exceed a certain length.

This feature has now been added system-wide. The above commit that added this feature is now part of the latest release. The button will show after scrolling down over 1200px.


Upgrading a WPF .NET Framework SDK-style project fails.

Describe the bug
It seems the "true" property only gets added to the config file if the project is upgraded to the SDK-style project - if it's already SDK-style, it doesn't get added, and we get failures.
To Reproduce
Use a WPF .NET Framework SDK-style project and upgrade to the latest .NET 5/6

@bgarlick By "true" property, did you mean the <UseWPF>true</UseWPF>? If so, that is correct the process that updates the project file to SDK-style adds this setting to the project file. Likely if its already SDK-style project its assumed that this setting is already take care of. We can look into checking for the setting if already SDK-style project.

@bleaphar Could you take a look at this issue?

@bgarlick can you provide the "WPF .NET Framework SDK-style project" you're referring to? Is there a template for that?


imrove vitor with sudoedit rules

sudoedit the program can't be used because in the current state of vitor, but I've found it to be the easiest way to set correct permisisons to the original state.
sudoedit makes a mode 600 copy on /var/tmp/filename.XXXXXX.
But it does not have the same characteristic from visudo to warn file is busy. Using sudoedit with mousepad, if I run sudoedit on the same file on two different terminals, it opens the file the second time but on the temrinal it prints file unchanged and remove the copy. This is possibly a bug on sudoedit, where it opens the editor before checking the file is being used.

currently, the editor is being called as root, because the torrc can only be written to as root or by debian-tor on tails, but to start tor, root is needed and the user option is set on the command line or the file if present.
now to enable GUI editors, can't call the editor as root anymore, need to change the flow to be like sudoedit.

Setting the following on /etc/sudo.conf:
Debug sudo /var/log/sudo_debug edit@debug

And seeing the logs:
sudo grep --color=auto "torrc" /var/log/sudo_debug

Feb 00 00:00:00 sudoedit[118817] /etc/tor/torrc -> /var/tmp/torrc.XXaCiG8y, fd 8 @ sudo_edit_mktemp() ../../src/sudo_edit.c:155


Setup of settings broken (settings/settings folder)

Settings URL:
*** Software Update of devon-ide-settings ***
Updating .../settings from https://repo.maven.apache.org/maven2/com/devonfw/tools/ide/devon-ide-settings
Trying to determine the latest available version from https://repo.maven.apache.org/maven2/com/devonfw/tools/ide/devon-ide-settings/maven-metadata.xml
LATEST = 3.0.0-beta7
Starting installation of devon-ide-settings to .../settings from https://repo.maven.apache.org/maven2/com/devonfw/tools/ide/devon-ide-settings/3.0.0-beta7/devon-ide-settings-3.0.0-beta7.zip
Downloading devon-ide-settings-3.0.0-beta7.zip from https://repo.maven.apache.org/maven2/com/devonfw/tools/ide/devon-ide-settings/3.0.0-beta7/devon-ide-settings-3.0.0-beta7.zip
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 68045  100 68045    0     0   350k      0 --:--:-- --:--:-- --:--:--  351k
Running command: unzip -q '/Users/hohwille/Downloads/devon-ide-settings-3.0.0-beta7.zip' -d '.../updates/extracted/settings'
Succeeded to run command unzip
Successfully extracted archive devon-ide-settings-3.0.0-beta7.zip to updates/extracted
Running command: mv '.../updates/extracted/settings' '.../settings'
Succeeded to run command mv
Successfully installed .../settings
...

*** Setting up mvn ***
Starting installation of maven to .../software/maven from http://ftp.fau.de/apache/maven/maven-3/3.6.0/binaries/apache-maven-3.6.0-bin.tar.gz
Downloading maven-3.6.0-all.tar.gz from http://ftp.fau.de/apache/maven/maven-3/3.6.0/binaries/apache-maven-3.6.0-bin.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 8851k  100 8851k    0     0  2820k      0  0:00:03  0:00:03 --:--:-- 2820k
Running command: tar xfz '/Users/hohwille/Downloads/maven-3.6.0-all.tar.gz' -C '.../updates/extracted'
Succeeded to run command tar
Successfully extracted archive maven-3.6.0-all.tar.gz to updates/extracted
Moving .../updates/extracted/apache-maven-3.6.0 to .../updates/extracted/maven
Running command: mv '.../updates/extracted/maven' '/projects/OpenSongTablet/software/maven'
Succeeded to run command mv
Successfully installed .../software/maven
To be fully functional please rerun 'devon' command to update your PATH properly.
Running command: cp '.../settings/maven/settings.xml' '.../conf/.m2/settings.xml'
cp: .../settings/maven/settings.xml: No such file or directory

******** ATTENTION ********
ERROR: Failed to copy maven settings.xml (cp)
We are sorry for the inconvenience. Please check the above errors, resolve them and try again.
Exit code was 1
ERROR: command 'mvn setup' failed with exit code 1
➜  ls settings/settings/maven/settings.xml
settings/settings/maven/settings.xml

So unfortunately current release (till beta7) extracts settings so that we have them in ${DEVON_IDE_HOME}/settings/settings/* instead of ${DEVON_IDE_HOME}/settings/*.
Should be trivial to fix.

Fixed in beta8.


Add nlopt-f to registry

Fortran bindings for NLopt library
source at grimme-lab/nlopt-f
supports fpm, meson and cmake

Do you want to adopt the convention nlopt.f? I plan to do the same with symengine.f: https://github.com/symengine/symengine.f90/issues/7

We discussed the naming of the project at https://github.com/grimme-lab/nlopt-f/issues/3.


Add surge for deployment of nextjs

Description / Flow
The current flow is very similar to se-1 :

yarn build
This runs next build && next export, the reason for next export is for static files creation because it seems like surge only supports static file deployments.
yarn surge
This run surge out  here out is directory outputted by next build && next export and surge deploys things inside out directory.

IMP
I have used  unoptimized: true for images in next.config.js  because since we are using next export i.e building static pages in this Nextjs dosen't support image optimization with next/image if we don't do it we get the following error :
https://stackoverflow.com/questions/65487914/error-image-optimization-using-next-js-default-loader-is-not-compatible-with-n
Some research
With surge, we won't be able to leverage the best abilities of Next.js like Image, creating api's etc and did some research what would be some other options that go well with Next.js  :

Vercel Cli
Netlify Cli
Layer0 Cli
Fly cli

What do you all think? feel free to suggest more option also happy refactor current approach 🙌
cc @carletex @rin-st

With surge, we won't be able to leverage the best abilities of Next.js like Image, creating api's etc and did some research what would be some other options that go well with Next.js

Yep, we mentioned this on the GH Issue. I guess Vercel is the top option for NextJS projects. I haven't use their CLI, I always configure the deploy connecting github from the Vercel UI (and then any push to main is deployed automatically).
I think it's something we could explore!
@technophile-04 Could you check the differences (specially on DX / simplicity) between Surge CLI vs Vercel CLI? I'll be interested to see the steps you need to take (if you don't have an account on any of them) to deploy: going to the UI? confirm email?

If Vercel CLI allows to not having to create an account (in the UI) and you can deploy directly from the CLI the first time you use it... maybe we could consider switching from Surge to Vercel.
If not, we could offer both options (or just having Surge and telling people about options in the DOCS)

In any case, we have this PR that it's working and we can merge any time :) Thanks Shiv!!!

Closing this for now since we merged #133


Invalid json is parsed ok

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
1.8.3
What operating system and processor architecture are you using (go env)?
GOARCH="amd64" GOBIN="" GOEXE="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOOS="linux" GOPATH="/home/cassiobotaro/go" GORACE="" GOROOT="/usr/lib/go" GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64" GCCGO="gccgo" CC="gcc" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build528676691=/tmp/go-build -gno-record-gcc-switches" CXX="g++" CGO_ENABLED="1" PKG_CONFIG="pkg-config" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2"
What did you do?
https://play.golang.org/p/r7FBkS2Cq7
What did you expect to see?
An error because json is not valid.
What did you see instead?
No errors.

IMO this is working as intended. Your example contains two fragments of json {} which is valid, and } which is not. The json package correctly detects the malformed second json fragment.
https://play.golang.org/p/PMADDC99Zy

What @dcheney-atlassian said. The docs do say:

A Decoder reads and decodes JSON values from an input stream.
...
Decode reads the next JSON-encoded value from its input and stores it in the value pointed to by v.

If you only want to read one element, use Unmarshal or use https://golang.org/pkg/encoding/json/#Decoder.Token to see if EOF is next.


Add jobs.wait_for_job method

Based on @FrancoisZim 's suggestion.
Currently still a draft to get feedback on the proposed interface. Will add test cases, as soon as we got agreement on the interface & functionality.
This commit adds a wait_for_job method which will repeatedly poll
a job's status until that job is finished.
Internally, it uses an exponential backoff for the polling intervals.
That way, it is snappy for fast-running jobs without putting too
much load on the server for long-running jobs.
It returns the successfully finished JobItem object which might be
of interest to the caller, e.g. to inspect the reported started_at
finished_at times or the notes.
For failed jobs, wait_for_job raises an exception. That way, we
ensure that errors in jobs don't accidentally go unnoticed. The
jobs object can still be retrieved from the exception object, if
required.

It makes sense to me.
The back of my head is asking if the Jobs endpoint is the right place for logic like that -- I think this would be the first 'utility' method we have on an endpoint... Is there a different way to present it like a TSC.Waiter that can handle other wait-retry-backoff methods?
Maybe that's too much, it's a bit off-the-cuff. Let me know what you think, otherwise I'll give this code as is a deeper review

Looks good to me.  I don't really agree with @t8y8 about a generalizable TSC.Waiter class - I think all async operations spawn a background job and so this is the right place to implement this wait logic.

I think this would be the first 'utility' method we have on an endpoint...

server.filesuploads.upload is also kind of an utility method. It chunks the file into multiple parts and uploads each chunk through a separate HTTP request. Similarly most publish methods (workbooks, datasources, ...) encapsulate multiple API calls into one utility method (first the upload, then the actual publish)
But I see what you mean here... To me the main question would be:

Is there a different way to present it like a TSC.Waiter that can handle other wait-retry-backoff methods?

which makes me wonder: which other things would there in the Tableau Server API which we might want to wait on?
If there are other things we want to wait on than jobs: yes, maybe a TSC.Waiter makes sense...
But afaict the "jobs" concept is already Tableau's abstraction for everything async on the server, and hence introducing another layer of abstraction on the client would add only limited value

The other thing we can wait for is a Flow Run, which might actually be what the BackgroundJobItem is related to now I look some more. @jorwoods how does this look to you in the context of adding the flows endpoints?

Regarding any changes to #884, this would not be too difficult to implement on the flow_runs endpoint as well.

argh... Ok, so flows are also de-facto jobs, but for some reason didn't use the jobs API. That's sad 😢 Such a nice abstraction on the server side, but then its inconistent by one job type not using the common REST interface... @jacalata maybe the "jobs" endpoint/abstraction should be added as a guideline to the TAG design guidelines for our REST API?
Either way, it is what it is... I will rewrite this code to pull out the "retry with exponential backoff" logic, such that it can be reused across multiple places, in particular also by @jorwoods in the flow endpoint, without having to duplicate that logic.
Will only have time for this a few days from now, though

added test cases and refactored the waiting logic into a reusable ExponentialBackoffTimer which can also be reused for flows.
I think this should be ready for the final review now


npm version 3.3.5  can't run ‘sudo npm install -g reapp’

npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>

resolved. the project need node-gyp to compiled. so need the install vs2013 in Windows.
Detail please to see https://github.com/nodejs/node-gyp#installation


Setting page does not automatically refresh when status changes for Machine Driver

Version - master UI 3/3
Steps to Reproduce:

Go to setting
Add a machine driver (wait)
Remove a machine driver (wait)

Results: Notice that for both the add and remove the state stays in Creating or Removing until you refresh the page
Expected:  Should refresh on change

We don't get change events for these so they need to be polled

Version - master 3/3
Verified fixed


Added grafana to playground cluster

Notes for Reviewers
This PR fixes add Grafana to the playground cluster
mesh design: https://meshery.layer5.io/catalog/a459be4e-3945-4331-acf1-b9fec90846aa
PS: we need to verify if Prometheus and node exporter are still running in the playground cluster
Signed commits

[x] Yes, I signed my commits.

@Freedisch what Grafana dashboards will be available in this Grafana deployment? We'll want a dashboard that is configured to collect the standard metrics available via Node Exporter.

@Freedisch Let's discuss this on Meshery Dev call. Please add this as an agenda item in the meeting minutes if you would. :)

@leecalcote //
1- I’m able to provision the infra into the playground ✅
2- meshery's server cannot to Grafana, I believe this might be a network issue between my playground and Grafana 🚫 I'm still working on it
3- The charts that will provide Grafana are based on the metrics provided by Prometheus previously scraped from node exporter
Question: is the current deployment of Prometheus in the cluster accessible by Meshery's server? same question for node exporter?

@Freedisch I've spoken to this a few times and walked through the Meshery Architecture slide on the Playground's deployment networking. Please refer to that slide. Rephrase your questions in context of that slide, if you have any after studying it.

@Freedisch I've spoken to this a few times and walked through the Meshery Architecture slide on the Playground's deployment networking. Please refer to that slide. Rephrase your questions in the context of that slide, if you have any after studying it.

I meant, is there any way we could verify if the Prometheus deployment still running inside the cluster? if not we should redeploy it.

When you open Visualizer mode, do you see it?

When you open Visualizer mode, do you see it?

I Got it
I think we should have a documentation section for Prometheus setup into the playground


Member Registration: Password too Common Issue

The password rules are good, however, we need to add a bubble, hint or text under the password with the rules.  Its very aggravating to try and try to get the password correct.

Planned date for completion is June 10th, 2021

Peter will look into this.  Link for the document is below.
https://drive.google.com/file/d/1vq9SWGHfevERDLflo4hDGJSRQDJakxQ7/view?usp=sharing

updated:

We updated the settings for password_validators as follows:
8 characters
1 numeric digit
1 special character```


Exporter crashes with index out of range

What happened?
Hello,
while trying to use minecraft-exporter for docker-hosted modded [modpack: Multiblock Madness, hosted via Pterodactyl Panel] Minecraft server I've encountered following error while scraping from Prometheus hosted on another machine:
ts=2022-08-17T23:43:55.773Z caller=main.go:43 level=info msg="Starting minecraft_exporter" version="(version=0.16.0, branch=HEAD, revision=df4d15fe643b0104a0729a08f5340ff3285a6c9d)"
ts=2022-08-17T23:43:55.773Z caller=main.go:44 level=info msg="Build context" build="(go=go1.19, user=goreleaser, date=2022-08-09T05:58:33Z)"
ts=2022-08-17T23:43:55.774Z caller=main.go:53 level=info msg="Disabling collection of exporter metrics (like go_*)" value=true
ts=2022-08-17T23:43:55.774Z caller=main.go:81 level=info msg="Listening signals..."
ts=2022-08-17T23:43:55.774Z caller=main.go:69 level=info msg="Listening on address" address=:9150
ts=2022-08-17T23:43:55.774Z caller=tls_config.go:195 level=info msg="TLS is disabled." http2=false
ts=2022-08-17T23:44:49.024Z caller=exporter.go:897 level=error msg="Failed to get player stats" err=EOF
panic: runtime error: index out of range [1] with length 0

goroutine 39 [running]:
github.com/minecraft-exporter/pkg/exporter.(*Exporter).getServerStats(0xc000128240, 0xc000230040?)
        /home/runner/work/minecraft-prometheus-exporter/minecraft-prometheus-exporter/pkg/exporter/exporter.go:786 +0xb52
github.com/minecraft-exporter/pkg/exporter.(*Exporter).Collect(0xc000128240, 0xc00038a760?)
        /home/runner/work/minecraft-prometheus-exporter/minecraft-prometheus-exporter/pkg/exporter/exporter.go:900 +0x2c5
github.com/prometheus/client_golang/prometheus.(*Registry).Gather.func1()
        /home/runner/go/pkg/mod/github.com/prometheus/client_golang@v1.13.0/prometheus/registry.go:453 +0x10d
created by github.com/prometheus/client_golang/prometheus.(*Registry).Gather
        /home/runner/go/pkg/mod/github.com/prometheus/client_golang@v1.13.0/prometheus/registry.go:545 +0xbac

How can we reproduce this?
Based on README, I've created following docker-compose which I used to run exporter:
version: '3'

services:
  mmad-exporter:
    container_name: mmad-exporter
    image: ghcr.io/dirien/minecraft-exporter
    restart: unless-stopped
    networks:
      - pterodactyl_nw
    volumes:
      - /var/lib/pterodactyl/volumes/cebf950d-e27a-4a7a-a2d5-9d5952c7bb08/world:/minecraft/world:ro
    environment:
      - WEB_DISABLED_EXPORTER_METRICS=true
      - MC_RCON_ADDRESS=${SERVER}:25665
      - MC_RCON_PASSWORD=${RCON_PASS}
      - MC_NAME_SOURCE=mojang
      - MC_MOD_SERVER_STATS=forge
    ports:
      - 9150:9150
    expose:
      - 9150

networks:
  pterodactyl_nw:
    external:
      name: pterodactyl_nw

[part] prometheus.yml
  - job_name: minecraft_exporter
    scrape_interval: 1m
    scrape_timeout: 45s
    static_configs:
      - targets: ["#REDACTED-IP#:9150"]

minecraft-exporter --version
v0.16.0

Search

[X] I did search for other open and closed issues before opening this.

Code of Conduct

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

Additional context
No response

hi @Kamisoi,
thanks for reporting the issue! Looks like there is a space in the Overall Tick RCON output:
[07:41:07] [Server thread/INFO] [minecraft/DedicatedServer]: Overall : Mean tick time: 5.203 ms. Mean TPS: 20.000

The version, I tested with (1.16) has no space:
07:48:49] [Server thread/INFO] [minecraft/DedicatedServer]: Overall: Mean tick time: 0,441 ms. Mean TPS: 20,000

I fixed it, with v0.16.1.
Looking forward for your feedback!

Created an issue #275 for the TPS from the dimensions.


Update tiktok-cohort.md

Updated the disclaimer to make it Closed Beta
Amplitude Developer Docs PR
Description
Describe your changes.
Deadline
When do these changes need to be live on the site?
Change type

[ ] Doc bug fix. Fixes #[insert issue number]. Amplitude contributors include Jira issue number.
[ ] Doc update.
[ ] New documentation.
[ ] Non-documentation related fix or update.

PR checklist:

[ ] My documentation follows the style guidelines of this project.
[ ] I previewed my documentation on a local server using mkdocs serve.
[ ] Running mkdocs serve didn't generate any failures.
[ ] I have performed a self-review of my own documentation.

@amplitude-dev-docs
@caseyamp

Updated the disclaimer to make it "Closed Beta" from Alpha.


Cargo behind SOCKS proxy

I have to use a SOCKS proxy (the kind created by ssh -D). The documentation doesn't say whether/how SOCKS is supported:

proxy = "..."       # HTTP proxy to use for HTTP requests (defaults to none)

I've tried changing config, as mentioned in #636, but Cargo seems to assume the proxy is a HTTP proxy. I've tried:
[http]
proxy = "socks://localhost:9050"
[https]
proxy = "socks://localhost:9050"

but that's not enough:

cargo run
Updating registry https://github.com/rust-lang/crates.io-index
warning: spurious network error (2 tries remaining): [12/-2] [6] Couldn't resolve host name (Could not resolve host: github.com)
warning: spurious network error (1 tries remaining): [12/-2] [6] Couldn't resolve host name (Could not resolve host: github.com)
error: failed to load source for a dependency on vpsearch

Caused by:
Unable to update registry https://github.com/rust-lang/crates.io-index

Caused by:
failed to fetch https://github.com/rust-lang/crates.io-index

Are SOCKS proxies supported?

I believe the syntax for libcurl is the socks5 or socks5h protocol (e.g. socks5://localhost:9050). Does that work?

socks5h worked, thank you!


panicked at 'called Option::unwrap() on a None

I downloaded the latest release version, The version does not seem to be updated to 0.1.1.
:~/csuckit# ./suckit -V
suckit 0.1.0

When I use it, errors occur most of the time. I don't know rust well, the program is great, I hope to get help.
RUST_BACKTRACE=1 ./suckit https://www.bing.com -v -j 8 -u "Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion" -t 2 -e ".*.png"

~/csuckit# RUST_BACKTRACE=1 ./suckit https://www.bing.com -v -j 8 -u "Mozilla/5.0 (platform; rv:geckoversion) Gecko/geckotrail Firefox/firefoxversion" -t 2 -e ".*.png"
2021-01-08 11:17:33.851524278 +08:00: [INFO] Visited: https://www.bing.com/
2021-01-08 11:17:33.888791557 +08:00: [INFO] Visited: https://www.bing.com/th?id=OHR.FoucaultsPendulum_ZH-CN9435794626_1920x1080.jpg&rf=LaDigue_1920x1080.jpg&pid=hp
2021-01-08 11:17:33.952818147 +08:00: [INFO] Visited: https://www.bing.com/sa/simg/hpc27.png
2021-01-08 11:17:34.013390032 +08:00: [INFO] Visited: https://www.bing.com/rs/16/Z/cj,nj/SaARcujqfMTKslsX8RYX1fR5N7Q.js
2021-01-08 11:17:34.063275272 +08:00: [INFO] Visited: https://www.bing.com/rs/16/24/cj,nj/Dm21B_RK98kel_AmFzx_vVUxyA8.js
2021-01-08 11:17:34.178764453 +08:00: [INFO] Visited: https://www.bing.com/dict?FORM=Z9LH3
2021-01-08 11:17:34.181435859 +08:00: [INFO] Visited: https://www.bing.com/sa/simg/favicon-2x.ico
2021-01-08 11:17:34.186635845 +08:00: [INFO] Visited: https://www.bing.com/rs/16/27/cj,nj/HeslkHjv6jsQPEIfhz5LxGWUBHI.js
2021-01-08 11:17:34.191187684 +08:00: [INFO] Visited: https://www.bing.com/rs/16/2e/cj,nj/r55v7gxWDwkhcrGBcy9GDN-1JO8.js
2021-01-08 11:17:34.241397473 +08:00: [INFO] Visited: https://www.bing.com/maps?FORM=Z9LH4
thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', src/scraper.rs:216:59
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:495:5
   1: core::panicking::panic_fmt
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/panicking.rs:92:14
   2: core::panicking::panic
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/panicking.rs:50:5
   3: suckit::scraper::Scraper::handle_url
   4: core::ops::function::FnOnce::call_once{{vtable.shim}}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', src/scraper.rs:68:49
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:495:5
   1: core::panicking::panic_fmt
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/panicking.rs:92:14
   2: core::option::expect_none_failed
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/option.rs:1268:5
   3: suckit::scraper::Scraper::map_url_path
   4: suckit::scraper::Scraper::handle_url
   5: core::ops::function::FnOnce::call_once{{vtable.shim}}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', src/scraper.rs:68:49
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:495:5
   1: core::panicking::panic_fmt
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/panicking.rs:92:14
   2: core::option::expect_none_failed
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/option.rs:1268:5
   3: suckit::scraper::Scraper::map_url_path
   4: suckit::scraper::Scraper::handle_url
   5: core::ops::function::FnOnce::call_once{{vtable.shim}}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', src/scraper.rs:68:49
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:495:5
   1: core::panicking::panic_fmt
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/panicking.rs:92:14
   2: core::option::expect_none_failed
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/option.rs:1268:5
   3: suckit::scraper::Scraper::map_url_path
   4: suckit::scraper::Scraper::handle_url
   5: core::ops::function::FnOnce::call_once{{vtable.shim}}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', src/scraper.rs:68:49
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:495:5
   1: core::panicking::panic_fmt
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/panicking.rs:92:14
   2: core::option::expect_none_failed
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/option.rs:1268:5
   3: suckit::scraper::Scraper::map_url_path
   4: suckit::scraper::Scraper::handle_url
   5: core::ops::function::FnOnce::call_once{{vtable.shim}}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', src/scraper.rs:68:49
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:495:5
   1: core::panicking::panic_fmt
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/panicking.rs:92:14
   2: core::option::expect_none_failed
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/option.rs:1268:5
   3: suckit::scraper::Scraper::map_url_path
   4: suckit::scraper::Scraper::handle_url
   5: core::ops::function::FnOnce::call_once{{vtable.shim}}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', src/scraper.rs:215:60
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:495:5
   1: core::panicking::panic_fmt
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/panicking.rs:92:14
   2: core::option::expect_none_failed
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/option.rs:1268:5
   3: suckit::scraper::Scraper::handle_url
   4: core::ops::function::FnOnce::call_once{{vtable.shim}}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', src/scraper.rs:68:49
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:495:5
   1: core::panicking::panic_fmt
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/panicking.rs:92:14
   2: core::option::expect_none_failed
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/option.rs:1268:5
   3: suckit::scraper::Scraper::map_url_path
   4: suckit::scraper::Scraper::handle_url
   5: core::ops::function::FnOnce::call_once{{vtable.shim}}
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Any', src/scraper.rs:285:10
stack backtrace:
   0: rust_begin_unwind
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/std/src/panicking.rs:495:5
   1: core::panicking::panic_fmt
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/panicking.rs:92:14
   2: core::option::expect_none_failed
             at /rustc/e1884a8e3c3e813aada8254edfa120e85bf5ffca/library/core/src/option.rs:1268:5
   3: suckit::scraper::Scraper::run
   4: suckit::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

I downloaded the latest release version, The version does not seem to be updated to 0.1.1.

:~/csuckit# ./suckit -V
suckit 0.1.0

Sorry about that, you did get the 0.1.1 release, it's just that the code's version specified in the file Cargo.toml wasn't updated :sweat_smile: You can create a PR for it if you want, or I'll update it

I downloaded the latest release version, The version does not seem to be updated to 0.1.1.

:~/csuckit# ./suckit -V
suckit 0.1.0

Sorry about that, you did get the 0.1.1 release, it's just that the code's version specified in the file Cargo.toml wasn't updated :sweat_smile: You can create a PR for it if you want, or I'll update it

I'm going to check the error you encountered. You're trying to download anything but PNG pictures from bing?

I'm going to check the error you encountered. You're trying to download anything but PNG pictures from bing?

I'm going to check the error you encountered. You're trying to download anything but PNG pictures from bing?

Yes! . In fact, I want to do download some resources,such as html/js/css .But not image resources. I used bing for testing. I encountered this panic on many sites.

I'm going to check the error you encountered. You're trying to download anything but PNG pictures from bing?

Yes! . In fact, I want to do download some resources,such as html/js/css .But not image resources. I used bing for testing. I encountered this panic on many sites.

There are lot of issues right now that needs to be fixed before tackling this one. I will notify you when I will start working on this, but I can't give you a time frame, SuckIT is a side project for me for the time being.

There are lot of issues right now that needs to be fixed before tackling this one. I will notify you when I will start working on this, but I can't give you a time frame, SuckIT is a side project for me for the time being.

There are lot of issues right now that needs to be fixed before tackling this one. I will notify you when I will start working on this, but I can't give you a time frame, SuckIT is a side project for me for the time being.

Thank :)

There are lot of issues right now that needs to be fixed before tackling this one. I will notify you when I will start working on this, but I can't give you a time frame, SuckIT is a side project for me for the time being.

Thank :)


Update  Xamarin.PropertyEditing reference for new features.

This pulls in the lastest Xamarin.PropertyEditing with improved
editors and styling.  It also add a simple formatter for a few
of our internal representations.

build

build

squashed some things


[Website] Link/Docs broken

Confirmed that it's broken on at least 3 devices, so it's not cache or something.
https://reacttraining.com/react-router/

click on Web

or go directly to https://reacttraining.com/react-router/web

Not getting this locally. You might have some sort of extension blocking it?

No, this in guest mode without any extensions active, I have it on phone too and initially it wasn't me noticing this but someone on discord.

I can confirm, I'm getting the same issue.


Cannot initialize app in v4

Hey there!
I'm working in a remix website and want to make it a PWA. I followed the Quick Start docs but when I run remix vite:dev --host I get the following errors:
Error during worker build: SyntaxError: [vite-plugin-remix-pwa:virtual-entry-sw] Could not load virtual:entry-sw (imported by node_modules/@remix-pwa/worker-runtime/dist/src/service-worker.internal.js): Unexpected token, expected "}" (7:16)
    at constructor (/Users/myuser/Documents/remix/myapp/node_modules/@babel/parser/lib/index.js:353:19)
    at TypeScriptParserMixin.raise (/Users/myuser/Documents/remix/myapp/node_modules/@babel/parser/lib/index.js:3277:19)
    at TypeScriptParserMixin.unexpected (/Users/myuser/Documents/remix/myapp/node_modules/@babel/parser/lib/index.js:3297:16)
    at TypeScriptParserMixin.expect (/Users/myuser/Documents/remix/myapp/node_modules/@babel/parser/lib/index.js:3601:28)
    at TypeScriptParserMixin.jsxParseExpressionContainer (/Users/myuser/Documents/remix/myapp/node_modules/@babel/parser/lib/index.js:6692:10)
    at TypeScriptParserMixin.jsxParseElementAt (/Users/myuser/Documents/remix/myapp/node_modules/@babel/parser/lib/index.js:6766:36)
    at TypeScriptParserMixin.jsxParseElement (/Users/myuser/Documents/remix/myapp/node_modules/@babel/parser/lib/index.js:6804:17)
    at TypeScriptParserMixin.parseExprAtom (/Users/myuser/Documents/remix/myapp/node_modules/@babel/parser/lib/index.js:6816:19)
    at TypeScriptParserMixin.parseExprSubscripts (/Users/myuser/Documents/remix/myapp/node_modules/@babel/parser/lib/index.js:10580:23)
    at TypeScriptParserMixin.parseUpdate (/Users/myuser/Documents/remix/myapp/node_modules/@babel/parser/lib/index.js:10563:21) {
  code: 'PLUGIN_ERROR',
  reasonCode: 'UnexpectedToken',
  loc: Position { line: 7, column: 16, index: 178 },
  pos: 178,
  pluginCode: 'BABEL_PARSER_SYNTAX_ERROR',
  plugin: 'vite-plugin-remix-pwa:virtual-entry-sw',
  hook: 'load',
  watchFiles: [
<EMAIL_ADDRESS>  ]
}

Error: ENOENT: no such file or directory, open '/Users/myuser/Documents/remix/myapp/public/entry.worker.js'
    at Object.openSync (node:fs:596:3)
    at readFileSync (node:fs:464:35)
    at getWorkerHash (file:///Users/myuser/Documents/remix/myapp/node_modules/@remix-pwa/dev/dist/src/hash.js:7:17)
    at Context.buildStart (file:///Users/myuser/Documents/remix/myapp/node_modules/@remix-pwa/dev/dist/src/plugins/bundler.js:133:24)
    at async Promise.all (index 6)
    at async hookParallel (file:///Users/myuser/Documents/remix/myapp/node_modules/vite/dist/node/chunks/dep-stQc5rCc.js:50358:9)
    at async Object.buildStart (file:///Users/myuser/Documents/remix/myapp/node_modules/vite/dist/node/chunks/dep-stQc5rCc.js:50710:13)
    at async file:///Users/myuser/Documents/remix/myapp/node_modules/vite/dist/node/chunks/dep-stQc5rCc.js:64593:13
    at async httpServer.listen (file:///Users/myuser/Documents/remix/myapp/node_modules/vite/dist/node/chunks/dep-stQc5rCc.js:64611:17) {
  errno: -2,
  syscall: 'open',
  code: 'ENOENT',
  path: '/Users/myuser/Documents/remix/myapp/public/entry.worker.js'
}

If I move entry.worker.ts (which was generated with npx remix-pwa sw) into the public folder and  change the extension to .js, the second error (no such file or directory) seems to go away, but the first one is still there
Any ideas on how to fix it?

Never mind. Don't know if I did something different today but I deleted everything, installed again and it's now working (only issue I found was #158)


DSC Support for splatting resources

It would be great to be able to splat natively into DSC resources.  An example of a workaround for this is described here.
The desired outcome would be to be able to do something like this:
$MyHashes = @(
  @{
    Ensure  = 'Present'
    Name    = 'Putty'
    Version = 'Latest'
    ChocolateyOptions = @{ source = 'https://chocolatey.org/api/v2/' }
  },
  @{
    Ensure  = 'Absent'
    Name    = 'notepadplusplus'
  }
)

Configuration MyDscConfig {
    $Allnodes.nodename {
        foreach($MyHash in $MyHashes) {
            ChocolateyPackage $MyHash['name'] @MyHash
        }
    }
}

@StevenBucher98 can this be moved to the PSDSC repository?


Add space when appending custom classNames

When adding a custom className to the Dropzone component there should be a space to separate the base classNames from the new ones.
New:
<Dropzone className="customClass" .../>

Old:
<Dropzone className=" customClass" ... />

:+1: Thank you very much!


Improvements on Add Plex Server UX and fixed 'of null' common errors

Explanation of the changes, problem that they are intended to fix.
I offer a fix for 3 situations:

A Simple improvement to "Add Server" functionality. Before when you click to "Sign In/Add Servers", a new window/tab is open, when you accept plex authorization, this window not closes and user not get a visual feedback. Now, a new window is open like a popup, staying the dizquetv site on the background, and after authorization this modal is closed.
Added some simple if logics to prevents common of null errors. These errors are showed when you don't have Plex servers.
Removed spaces unnecessary on package.json. The npm install do this automatically.

All Submissions:

[x] I have read the code of conduct.
[x] I am submitting to the correct base branch

New features

[x] I understand that the feature may not be accepted if it doesn't fit the upstream app's planned design direction. But that in this case I am encouraged to share this as an available modification other users can use if they want.

Hello, I am in the process of changing the guidelines, now that 1.2.x is stable, new features should go to dev/1.3.x So please change the base branch to dev/1.3.x .  I'll be testing your changes in the meantime.

Hello, I am in the process of changing the guidelines, now that 1.2.x is stable, new features should go to dev/1.3.x So please change the base branch to dev/1.3.x .  I'll be testing your changes in the meantime.

I changed the base branch myself and there aren't any conflicts. So merged. Thanks, that definitely makes more sense than using a new tab.

I changed the base branch myself and there aren't any conflicts. So merged. Thanks, that definitely makes more sense than using a new tab.


Type validation can not set input state to none after setValueState

SAPUI5 version: 1.54.6
URL: https://sapui5.hana.ondemand.com/#/sample/sap.m.sample.InputChecked/preview
Steps to reproduce the problem:
1. Validation through type validateValue. [Expected behavior]
1.1. Input "12345678901", move cursor to the second input,  input is in error state:

1.2. input "1", move cursor to the second input,  input state set to none.
2.  Validation through setValueState in try..catch... [Confusing behavior]
2.1. click Continue when Name input is empty. input state is set to error
2.2. input "1", move cursor to the second input,  input state is still error.

What is the expected result?
For the second situation, I want to trigger validation in input change event(input state should set to none when the focus leaves the input field).
What happens instead?
After input state set to error through setValueState, it seems can not be reset to "None" through type validation.
I think may be it is because validateValue use message manager to change input value state, whereas setValueState() is another mechanism？
An explanation of this inconsistence behavior is expected, a work around to solve this would be great.

The issue is reproducible on IE, but not on Chrome.

Hi,
Thank you for sharing this finding. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Best,
Teo

Hi team，
I can reproduce it on Chrome Version 67, MacOS Version 10.13.3
I noticed that you must click Continue after you refresh the page(the first thing to do when you enter the page) to reproduce this problem. If you have cleared value state using validateValue, this issue can not be reproduced.
Updated my issue description.

Hello @TinaC,
After we submit a fix the issue closes automatically.
The fix can be seen here: https://openui5nightly.hana.ondemand.com/#/sample/sap.m.sample.InputChecked/preview
Best Regards,
Gergana


[Android] acknowledgePurchaseAndroid() Google is indicating that we have some issue connecting to payment.

Version of react-native-iap > 3.4.12
Version of react-native > 0.58.3
Platforms you faced the error > Android
Actual behavior
I have got a
Google is indicating that we have some issue connecting to payment. error
In logcat I get a E/DoobooUtils: Error Code : 5
I was using version 2.5.5 previously, it was working fine.
The only thing not working there is the acknowledgePurchaseAndroid call
Tested environment > Real Device
Here is my code :
  handleServerSubscribe = async purchase => {
    const {
      productId,
      transactionReceipt,
    } = purchase
    if (transactionReceipt) {
      try {
          // FIXME it fails right here
          await acknowledgePurchaseAndroid(purchase.purchaseToken)

      } catch (e) {
        console.log('subscription error ', e)
      }
    }
  }

componentDidMount() {
    this.purchaseUpdateSubscription = purchaseUpdatedListener(purchase => {
      this.handleServerSubscribe(purchase)
    })
  }

If acknowledgePurchase isn't working, it feels like you've not correctly updated billingClient in android to 2.0.3. Could you check your build.gradle?

@hyochan uh, it looks like it but I have no clue where I can get the correct syntax :/
Is it supposed to be in the README ?

Try to find the line com.android.billingclient:billing by searching.

Well, I didn't have it, I only had
 implementation project(':react-native-iap')

Do I need both implementations ?
 implementation 'com.android.billingclient:billing:2.0.3'
 implementation project(':react-native-iap')

I stil have the same error

@MeisterTea I wanted you to check the version of the billingclient in your installed react-native-iap project. Check inside node_modules/react-native-iap/android/build.gradle

oh, my bad... Yes, it does have the right version
  implementation 'com.android.billingclient:billing:2.0.3'

Any idea ?

@MeisterTea I think I found useful LINK for you.

@MeisterTea Was this helpful?

Well, I still have the error

Well, I still have the error :
js bridge: Google is indicating that we have some issue connecting to payment.
logcat: E/DoobooUtils: Error Code : 5
await acknowledgePurchaseAndroid(purchase.purchaseToken)

, I have some questions:

Do you have any other idea how I could fix the issue ?
How can I debug and use my release key ? react-native run-android seems to always install a generic debug key even after copying my release keystore as debug.keystore and pointing to it inside the build.gradle

Well, I still have the error :
js bridge: Google is indicating that we have some issue connecting to payment.
logcat: E/DoobooUtils: Error Code : 5
await acknowledgePurchaseAndroid(purchase.purchaseToken)

, I have some questions:

Do you have any other idea how I could fix the issue ?
How can I debug and use my release key ? react-native run-android seems to always install a generic debug key even after copying my release keystore as debug.keystore and pointing to it inside the build.gradle

EDIT: It's all the same with the sample project of react-native-iap.
I change the versionCode to the latest I uploaded on the beta track, gave it the release key, added my subscription id, changed the code to load subscriptions, done a react-native run-android variant=release
I can buy the subscription but I am still getting the error 5

having the same issue. any solution for this?

Yes, it's to due to acknowledging a PENDING payment.
IMO, licence testers shouldn't have a PENDING state anyway so maybe Google is at fault there.

I get the same issue also for payments which have the state purchaseStateAndroid 1 (PURCHASED)

Yes, it's to due to acknowledging a PENDING payment.

I confirm this

I had the same problem and I realized that problem was that the PurchaseToken was already confirmed. So I fix the problem controlling the call to await acknowledgePurchaseAndroid(purchase.purchaseToken).  @hyochan
Hope it helps.

I get the same issue also for payments which have the state purchaseStateAndroid 1 (PURCHASED)

have you found the solution?

I have had the same error message recently. So I'd say this should stay active.

I'm getting the same error with RNIap.finishTransaction

@creativemind1 What version are you using? finishTransaction should work on both iOS and android.

I'm using "react-native-iap": "^4.4.1" and when I'm calling finishTransaction in Android, I'm getting error from Google Google is indicating that we have some issue connecting to payment. So after getting successful response from my server I'm calling RNIap.acknowledgePurchaseAndroid which is working but not finishTransaction

Same error, but I on getProducts

Same error, but in consumeProduct:
Error: Google is indicating that we have some issue connecting to payment.     at Object.fn [as consumeProduct] (VM4 index.bundle:2143)

I think if you add the email address in the test users of.google play
settings you will nit see tgat issue
On Sat, Jun 6, 2020, 8:41 PM rafaeelrf<EMAIL_ADDRESS>wrote:

Same error, but in consumeProduct:
Error: Google is indicating that we have some issue connecting to payment.
at Object.fn [as consumeProduct] (VM4 index.bundle:2143)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dooboolab/react-native-iap/issues/721#issuecomment-640075737,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABH54CL5FLAY4C7CTL2V3V3RVJMA7ANCNFSM4IX5EJQA
.

I already added, but the problem was not solved

If I remember right, you can't do it client side when you are on test servers because there is a slight delay between issuing the payment and server validation.
We had to move this logic server side

Hi I am getting the same error while  RNIap.acknowledgePurchaseAndroid(purchase.purchaseToken); API. Can someone please help

I'm getting the same error with RNIap.finishTransaction

me too having this issue using the latest version and test card is used

Same problem here, calling RNIap.finishTransaction(purchase, true) from my purchaseUpdatedListener that gets called as it should just after my RNIap.requestSubscription. This leads to the error. After 5 min I get the cancellation mail "This test purchase was canceled because it was not confirmed" from Google. Of course, I am using a test account, but that ought to be ok.
The same code works like a charm on iOS.

@MeisterTea what did you do backend, did you find out what the equivalent google request of RNIap.finishTransaction(purchase, true) was? Can you share some more info, so the rest of us can use that solution until the plugin works again?

my issue was, I was calling finishtransaction 2 times. when I removed it, worked fine

I got it working: I just made these specific lines for Android, but the need to do so was not very apparent from the documentation. Now it works both on Android and iOS:
       // on Android we need to acknowledge purchase or finishTransaction fails                             // if we do not acknowledge, purchase will roll back in 5 min                             RNIap.acknowledgePurchaseAndroid(purchase.purchaseToken).then(() => {                                 RNIap.finishTransaction(purchase, true).catch(err => {                                     console.log(err.code, err.message);                                 });                             });

i dont know if this working or not for you (this code for consumeProduct):
await RNIap.finishTransaction(purchase).then(async () => {                         await RNIap.consumePurchaseAndroid(purchase.purchaseToken).then(async () => {                             console.log('purchase :', purchase)                         }).catch(err => {                             console.log('consume error: ', err.code, err.message)                             Alert.alert('consume finish error: ', err.message)                         });                     }).catch(err => {                         console.log('finish error: ', err.code, err.message)                         Alert.alert('purchase finish error: ', err.message)                     })
I need to finish the transaction at first then revoke the purchase by hitting the consumePurchaseAndroid() as the code above. Hope it helps.

I got it working: I just made these specific lines for Android, but the need to do so was not very apparent from the documentation. Now it works both on Android and iOS:
 // on Android we need to acknowledge purchase or finishTransaction fails
 // if we do not acknowledge, purchase will roll back in 5 min
 RNIap.acknowledgePurchaseAndroid(purchase.purchaseToken).then(() => {
 RNIap.finishTransaction(purchase, true).catch(err => {
 console.log(err.code, err.message);
 });
 });

That seems to work for me too, i'm using v5.0.0

Getting same when:

purchase error Error: Google is indicating that we have some issue connecting to payment.
at Object.promiseMethodWrapper [as buyItemByType] (VM4 index.bundle:2242)
at VM4 index.bundle:142829
at step (VM4 index.bundle:142328)
at Object.next (VM4 index.bundle:142258)
at fulfilled (VM4 index.bundle:142212)
at tryCallOne (VM4 index.bundle:27056)
at VM4 index.bundle:27157
at VM4 index.bundle:30708
at _callTimer (VM4 index.bundle:30596)
at _callImmediatesPass (VM4 index.bundle:30635)

I was getting this error and I added implementation 'com.android.billingclient:billing:4.0.0'  to my /app/build.gradle. I didn't test in release mode yet but it seems to solve the issue.

I used hooks given in react-native-iap library, Then I had to use above solution like below,
      if (Platform.OS == 'android' && currentPurchase.purchaseToken) {
        acknowledgePurchaseAndroid({
          token: currentPurchase.purchaseToken,
          developerPayload: currentPurchase.developerPayloadAndroid,
        })
          .then(() => {
            finishTransaction({
              purchase: currentPurchase,
              isConsumable: true,
              developerPayloadAndroid:
                currentPurchase.developerPayloadAndroid,
            }).catch(err => {
              console.error(err.code+" finish", err.message);
            });
          })
          .catch(err => {
            console.error(err.code+ " acknowledge", err.message);
          });
      } else {
        await finishTransaction({
          purchase: currentPurchase,
          isConsumable: true,
        });
      }

I used hooks given in react-native-iap library, Then I had to use above solution like below,
      if (Platform.OS == 'android' && currentPurchase.purchaseToken) {
        acknowledgePurchaseAndroid({
          token: currentPurchase.purchaseToken,
          developerPayload: currentPurchase.developerPayloadAndroid,
        })
          .then(() => {
            finishTransaction({
              purchase: currentPurchase,
              isConsumable: true,
              developerPayloadAndroid:
                currentPurchase.developerPayloadAndroid,
            }).catch(err => {
              console.error(err.code+" finish", err.message);
            });
          })
          .catch(err => {
            console.error(err.code+ " acknowledge", err.message);
          });
      } else {
        await finishTransaction({
          purchase: currentPurchase,
          isConsumable: true,
        });
      }

It doesn't work.
After changing code like this, err remain
'E_DEVELOPER_ERROR finish', 'Google is indicating that we have some issue connecting to payment.'

Getting same error. Is there any solution?
[Error: Google is indicating that we have some issue connecting to payment.]
Tested on real device. in debug-release modes

https://github.com/dooboolab-community/react-native-iap/blob/aab948226fd075c759022503af45286262e8ff97/IapExample/src/screens/Subscriptions.tsx#L68C12-L68C32
i guess it was a wrong usage.
https://github.com/dooboolab-community/react-native-iap/issues/2578#issuecomment-1802669630
This usage solved my problem


Incorrect bracket display

As you can see in the below screenshot, the closing bracket is not displayed

thanks for the bug report!  in rare circumstances the pads can go out of
sync (and they should be force-converged after a certain timeout passes).
are there steps to reproduce?
On Tue, Apr 18, 2017 at 9:50 PM, Man Parvesh Singh Randhawa <
<EMAIL_ADDRESS>wrote:

As you can see in the below screenshot, the closing bracket is not
displayed
[image: blindpad io]
https://cloud.githubusercontent.com/assets/6629115/25163671/9d2b23c6-24fe-11e7-8c52-c493a3265b2a.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/blindpad/blindpad/issues/8, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEK18MRsHRvMYT32DRavbw_4pn01l7QDks5rxZKZgaJpZM4NBMgL
.

--
Ryan Noon
http://rmnoon.github.io/ http://rmnoon.github.io/

Yes, I just wrote a simple program in Java and opened the link in an incognito window, and the last bracket was missing.

Step to reproduce:

Switch mode to Java
type {
press Return/Enter
type }

Codemirror seems to be correcting the formatting.

Do we know whether this is a codemirror bug or a blindpad bug?


BuddyBuildSDK Integration

@dennispi, here's the BuddyBuildSDK. You'll get an email that lets you install and try out the build

This should say login. Not login3!


Fixing show typing and delay

When the IActivitie's were being processed ServiceUrl and Conversation were not set. This was preventing the Typing from being sent.
I added the SendActivity method back because there is no flush method in order to force the Typing Activity to show in the chat client.

 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.:x: RyanDawkins sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I don't like the type casting to Activity. I found another way of creating the Activity by setting the ServiceUrl and Conversation if that is preferred.

In case I didn't mention it, thank you. Your help here is really appreciated! 👍

I'd like to link this and #97 together.

@cleemullins Other than the ActivityTypes.Delay, is there anything else you are wanting me to change?

I’m not sure yet on this one. Let me review it again tonight.

From: Tom Laird-McConnell<EMAIL_ADDRESS>Sent: Thursday, February 15, 2018 5:41:34 PM
To: Microsoft/botbuilder-dotnet
Cc: Chris Mullins; Mention
Subject: Re: [Microsoft/botbuilder-dotnet] Fixing show typing and delay (#121)
Merged #121https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fbotbuilder-dotnet%2Fpull%2F121&data=04|01|cmullins%40microsoft.com|cc2e3d03cc484415da8608d574de6990|72f988bf86f141af91ab2d7cd011db47|1|0|636543420972735323|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=65fJP3M9zMg0FymzV%2FiUJfEz%2BAyW%2F124qHSUyiYvzPQ%3D&reserved=0.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fbotbuilder-dotnet%2Fpull%2F121%23event-1477137516&data=04|01|cmullins%40microsoft.com|cc2e3d03cc484415da8608d574de6990|72f988bf86f141af91ab2d7cd011db47|1|0|636543420972735323|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=h9T66Nezl075U0AhzNGJUstSHCMjffdiJ4wc9898pM4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABHICQmfMWY07OH52KvMEYdcGs6NcZ4lks5tVNzNgaJpZM4SGQIH&data=04|01|cmullins%40microsoft.com|cc2e3d03cc484415da8608d574de6990|72f988bf86f141af91ab2d7cd011db47|1|0|636543420972735323|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D|-1&sdata=PBINGJhkPYUV2oIN2F56r3sR%2BOmzaujQGX%2BDafow774%3D&reserved=0.

It's worth noting these changes removed the fluent-API capability of ShowTyping() and Delay()... we can no longer:
context.Reply("msg 1").ShowTyping().Delay(2000).Reply("msg 2");

and must now
context.Reply("msg 1");
await context.ShowTyping()
await context.Delay(2000);
context.Reply("msg 2");

@brandonh-msft that was by design as the feedback was they're confusing and further more they currently complicate the overall lifetime of the context object from a middleware perspective.  And Chris may not of applied all of the changes yet but the end goal for the base context object to only have:
await context.sendActivities([
     { type: 'message', text: 'msg 1' },
     { type: 'typing' },
     { type: 'delay', value: 2000 },
     { type: 'message', text: 'msg 2' }
]);

Does that suck? yes it kind of does... But it's what you get with a unopinionated context object that's been stripped down to its bare basics.
The queue based approach can be added back in using middleware and a builder that looks something like this:
Batch.add(context).reply(`msg 1`).typing().delay(2000).reply(`msg 2`);

I personally think it would be cleaner for the middleware to extend the context object like this:
context.batch.reply(`msg 1`).typing().delay(2000).reply(`msg 2`);

But that would violate the immutable context object @billba has been pushing for.

So these were actually direct methods added to the context object, which again violates the immutability rules that @billba has been pushing for, so I'll let him comment on that as he believes pretty strongly that you shouldn't do stuff like this. For me its a case by case basis.
With that said... Yes these methods go direct and I think you'd want one approach or the other (either batch based or direct.)  There's a couple of advantages to the batch based approach over the direct approach (fluent style being one and potentially the ability to guarantee order on channels like kick) but I think having both models on the same context object will cause general confusion.  We've classically supported the batch based approach as it's the most flexible (or more accurately has the least issues) but I can understand why people hate having to manually call flush().

I should be clear that moving away from the batched based approach does introduce some issues in certain edge cases like Cortana skills but it's nothing they can't work around. We were just able to work around these issues for them before and now we can't.

So these were actually direct methods added to the context object

I'm not sure if you mean "direct communication" or "direct-on-the-interface" … if the former, yes. if the latter, no - they're extension methods.

I think having both models on the same context object will cause general confusion

100% agree.

@brandonh-msft I meant "direct communication"


bump to v1.10.3

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Ser bra ut. Skal eg merge?

Testane må gå gjennom først.


improve key binding

improve key binding for search feature & some improvement

can i work on this?

i already solved it.

i have fixed the show, please check the PR;
https://github.com/code100x/daily-code/pull/193


Improve retry behaviour for failed jobs

It would be nice to have improved logic for retrying failed jobs, for example an exponential backoff.

Hi jameshy,
I have been looking for a job que for postgres and may start using this module. Would you be interested in contributors? I have implemented exponential back off in other job queue solutions and may do so with this. If you'd like I can submit it as PR for you if/when I get to it.

Yes that would be fantastic!


Shell - debouncedUpdateLg cannot handle paralleled lg update requests

Describe the bug
In a parralleled scenario, deboundcedUpdateLg api will lose changes.
Scenario:
Moves lg template A from 'D1.lg' to 'D2.lg', fires 2 paralleled api calls:

create template A' in 'D2.lg'
delete template A from 'D1.lg'

In this case, the first request will be cancelled.

Version

Browser

[ ] Chrome
[ ] Safari
[ ] Firefox
[ ] Edge

OS

[ ] macOS
[ ] Windows
[ ] Ubuntu

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior

Screenshots

Additional context

Possible solutions:

use well-managed immutable states + observer
event stream

Another hack I found in composer codebase (1y ago hacked by Andy)

It should also be addressed here

addressed via https://github.com/microsoft/BotFramework-Composer/pull/2348