Cant connect to atlas - ConnectionTimeoutException: No suitable servers

Hi when trying to connect to MongoDB Atlas via PHP and write a simple document I get the following error:

Fatal error: Uncaught MongoDB\Driver\Exception\ConnectionTimeoutException: No suitable servers found: serverselectiontimeoutms timed out: [connection closed calling ismaster on 'test-shard-00-00-waf4c.mongodb.net:27017'] in /Applications/AMPPS/www/mongodb/liveserver.php:63

Here is my code trying to connect and bulk write a document:
$manager = new MongoDB\Driver\Manager("mongodb://admin:admin@test-shard-00-00-rbgc.mongodb.net:27017/db?ssl=false&replicaSet=test-shard-0&authSource=admin&serverSelectionTryOnce=false");

var_dump($manager);

$bulk = new MongoDB\Driver\BulkWrite;

$bulk->insert(['x' => 1]);
$manager->executeBulkWrite('db.collection', $bulk);

When I var_dump the $manager I get:
    object(MongoDB\Driver\Manager)#1 (2) { ["uri"]=> string(64) "admin:admin@test-shard-00-00-rbgc.mongodb.net:27017/" ["cluster"]=> array(0) { } }
Some additional information:
I am using MongoDB Atlas and connecting to it via compass works great, I have whitelisted my IP and also allowed all ips to have access to the cluster.
I am using MacOS, PHP 7.1, any idea on what causes this problem and if its a driver issue?
(the above code works perfectly with no errors when tested on local installation of mongodb)
Thank you in advance for your time and help.

I am using MongoDB Atlas and connecting to it via compass works great

Are you using the exact same connection string with Compass? I ask because it includes ssl=false, and I believe Atlas requires SSL.
Since you're using macOS, I'll also note that 1.4.x currently has a bug that may lead to dropping previously persisted connections. This is likely to come up in a web SAPI, but I don't expect you'll run into it from a CLI environment unless it's a long-running script. See https://github.com/mongodb/mongo-php-driver/issues/855#issuecomment-398801444 and https://github.com/mongodb/mongo-php-driver/issues/791#issuecomment-383328627 for more information. That issue should be addressed in 1.5.0, which was just tagged today (formal announcement due tomorrow).

I have tried the exact same code on a windows machine using 1.4.x and it works, so its likely this MacOS bug, that you mentioned.
In order to update to newest (1.5.x) version on mac do I need to just replace the old .so file with the new one and restart apache right?
Thank you very VERY much for your fast response.

The CLI script in https://github.com/mongodb/mongo-php-driver/issues/791#issuecomment-383936108 can be used to determine if you are actually encountering PHPC-1169 or not.
I'd still appreciate a response to my question about using the same connection string with Compass, as I'm fairly certain that Atlas requires SSL for its connections. It's possible that Compass may have some internal logic that silently enables SSL, although that would be unexpected.

In order to update to newest (1.5.x) version on mac do I need to just replace the old .so file with the new one and restart apache right?

You can follow the PECL install process in the manual. PECL should install the mongodb.so file for you, provided that you use the pecl binary corresponding to your PHP runtime (e.g. MAMP and Homebrew would each have their own pecl and phpize commands, which should know about their respective PHP environments). After installing the new mongodb.so file, you may need to restart Apache to ensure the new module is loaded.

I used the same connection string in compass and it worked fine, also in compass there is an option to connect via SSL or unvalidated (insecurely).

I used the same connection string in compass and it worked fine, also in compass there is an option to connect via SSL or unvalidated (insecurely).

I reached out to the Compass developers and they confirmed that it does actually have logic to detect Atlas connection strings and will override ssl=false and set other appropriate SSL options (e.g. certificates) if needed.
In any event, I would certainly advise removing ssl=false from any Atlas connection string being used with the PHP driver. We have no logic to override that option and will end up trying to open a non-SSL connection to Atlas, which will most certainly fail.

I have a very similiar issue. I have php docker image on kubernetes , and every second time i deploy the image and the container is restarted , mongo connection fails with the same errors message as the above. If i only restart the container right after , then it works. It is really strange. Something to do with Mongo Atlass still haing a connection open and the new try failing ?

@bujardeari: Rather than comment on closed issues, it'd be preferable to open a new issue describing your problem and then link back to the old thread(s) for context. This also applies to the comment you added in https://github.com/mongodb/mongo-php-library/issues/372#issuecomment-482055822.
If I understand your problem correctly, the connection cannot be established after restarting the container once as part of your deployment, but restarting it a second time after deployment resolves the issue. This does not sound like anything we have control over in the PHP driver if the PHP process itself is being restarted (i.e. state is being cleared entirely).
I'm not aware of any restrictions within Atlas for accepting multiple connections for the same host, given that would interfere with common PHP deployments (e.g. FPM worker pools) and connection pooling on other drivers. If you're hitting connection limits in Atlas (each tier has its own limits), that's another issue and likely something the support team could identify; however, I wouldn't think limits are an issue if a second restart of the container fixes the problem. It's possible that the root cause rests in the network configuration or container stack. If you have access to Atlas Support that may be a better channel to investigate this, as that team may have more awareness of Kubernetes-related issues.

For me simply helped updating on mondodb php driver

For me simply helped updating on mondodb php driver

Thanks a lot for this answer! ?Thats true
i update driver as 1.11.0 to 1.13.0


⚠ Forum - Funcraft has degraded performance

In ce6047e, Forum - Funcraft (https://community.funcraft.net/) experienced degraded performance:

HTTP code: 200
Response time: 2518 ms

Resolved: Forum - Funcraft performance has improved in 52a0c5c after 34 minutes.


Explore how to tag information in CC nodes and extract it later on

Currently, a floating rate claim could look like this:
 (When (TimeGte 2022-09-16T12:00:00Z) (Scale (Const 1000000.0) (Scale (Mul (Add (Observe "USD/LIBOR/3M", Const 0.005), Const 0.2527777778)) (When (TimeGte 2022-12-20T12:00:00Z) (One InstrumentKey {depository = 'Custodian', issuer = 'Issuer', id = USD, version = "0"}))
We need a way to extract information from this calculation:

fixing date: 2022-09-16
notional: 1000000.0 (trivial in this case, but could be amortizing and fx adjusted, i.e. depend on both calculations and observations)
floating rate: 0.013 (not shown above)
floating rate spread: 0.005
floating rate used, including spread: 0.018 (not shown above)
daycount fraction: 0.2527777778
payment date: 2022-12-20
currency: USD

Alternative suggestion from Georg: I could see this working through methods on the swap interface, where the implementation could also just pull the information out of the FpML. Or one could split it up into separate interfaces, like HasNotional, HasSchedule, etc. So it’s not clear at this point what the best way to provide this functionality is, maybe it becomes clearer once we have more concrete requirements.

Putting this on hold for the time being, due to the release deadline approaching and this is a rather large change.


YouTube detecting it?

Is YouTube detecting the extension now?

i got it errors now

Version 2.8.5 is being uploaded for Chrome and is already active for Firefox so make sure you update it.
I'll close this issue for now, but feel free to open a new one after checking. Thank you


Release v0.5.3

Publishes v0.5.3 of volatile and volatile-macro.

I created a test v0.5.3-rc.1 release using cargo release rc --workspace. It looks like it handled the version bump for both crates and the dependency update correctly.

Published a v0.5.3-rc.2 release. The derive macro now shows up on docs.rs: https://docs.rs/volatile/0.5.3-rc.2/volatile/index.html
@mkroening Ready for publish from your side?

Ready for publish from your side?

Yes, thank you! :)


Unstable heap memory issue

Describe the bug
Memory has been unstable since Dec 06, we need to investigate which PRs caused it

Expected behavior
Memory should be stable like in v1.2.2

Have deployed some branches in feat1/beta, it shows that this has happened since we merges https://github.com/ChainSafe/lodestar/pull/4849
it's also confirmed by regen metrics

in my opinion, for the release of v1.3.0 we should just revert that PR and comment the edge cases that we may need it. In the long term, it will be resolved if we implement the committee cache which is lightweight compared to the current regen strategy. What do you think @dapplion @wemeetagain ?

Ok to me to revert, open an issue and fix properly latter. I would rather wait for a more "proper" solution of regen usage.


bump kubectl version to enable 1.3 clusters

What
the kubectl binary is backwards compatible, so this upgrade shouldn't affect clusters < 1.3.4

Awesome, now we just need to make sure we keep it up to date in the future

Oh nice. Thanks @wincus!


COS objetstore client MaxIdleConnsPerHost too few

Thanos, Prometheus and Golang version used: v0.21.1

Object Storage Provider: COS
What happened:
the thanos tools bucket web run after some duration, there will a lot of error logs like dial tcp 169.xxx:443: connect: cannot assign requested address. netstats show many TIME_WAIT connection.

What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
run thanos tools web on a objectstore which has many object.
Full logs to relevant components:
Logs

2021-07-24T19:55:27.837291407+08:00 level=debug ts=2021-07-24T11:55:27.837083718Z caller=fetcher.go:321 component=block.BaseFetcher msg="fetching meta data" concurrency=32
2021-07-24T19:57:05.947864137+08:00 level=error ts=2021-07-24T11:57:05.94755018Z caller=runutil.go:101 msg="function failed. Retrying in next tick" err="incomplete view: 8 errors: meta.json file exists: 01F3Z65VWTE6C5DSB7P6XZWQ2W/meta.json: head cos object: Head \"https://${cos url, i replaced}/01F3Z65VWTE6C5DSB7P6XZWQ2W%2Fmeta.json\": dial tcp *.*.*.*:443: connect: cannot assign requested address; meta.json file exists: 01F3YZA8HTSR577AXRYFSJ057K/meta.json: head cos object: Head \"https://*******.cos.ap-guangzhou.myqcloud.com/01F3YZA8HTSR577AXRYFSJ057K%2Fmeta.json\": dial tcp *.*.*.*:443: connect: cannot assign requested address; meta.json file exists: 01F3Z65VXQ5YR6MCG6K29NG5Z2/meta.json: head cos object: Head \"https://*******.cos.ap-guangzhou.myqcloud.com/01F3Z65VXQ5YR6MCG6K29NG5Z2%2Fmeta.json\": dial tcp *.*.*.*:443: connect: cannot assign requested address; meta.json file exists: 01F3Z65VXHMKDV684WB7XJ0VJJ/meta.json: head cos object: Head \"https://*******.cos.ap-guangzhou.myqcloud.com/01F3Z65VXHMKDV684WB7XJ0VJJ%2Fmeta.json\": dial tcp *.*.*.*:443: connect: cannot assign requested address; meta.json file exists: 01F3Z65VWKX3T5QMAH92V0NJZ8/meta.json: head cos object: Head \"https://*******.cos.ap-guangzhou.myqcloud.com/01F3Z65VWKX3T5QMAH92V0NJZ8%2Fmeta.json\": dial tcp *.*.*.*:443: connect: cannot assign requested address; meta.json file exists: 01F3Z65VX487XNYTSZ7VDWA65H/meta.json: head cos object: Head \"https://*******.cos.ap-guangzhou.myqcloud.com/01F3Z65VX487XNYTSZ7VDWA65H%2Fmeta.json\": dial tcp *.*.*.*:443: connect: cannot assign requested address; meta.json file exists: 01F3Z65XVZKBXMT7Y4EN4MH7VX/meta.json: head cos object: Head \"https://*******.cos.ap-guangzhou.myqcloud.com/01F3Z65XVZKBXMT7Y4EN4MH7VX%2Fmeta.json\": dial tcp *.*.*.*:443: connect: cannot assign requested address; meta.json file exists: 01F3ZD1N3Z15EPT9X677B5H913/meta.json: head cos object: Head \"https://*******.cos.ap-guangzhou.myqcloud.com/01F3ZD1N3Z15EPT9X677B5H913%2Fmeta.json\": dial tcp *.*.*.*:443: connect: cannot assign requested address"
2021-07-24T19:57:05.947916124+08:00 level=debug ts=2021-07-24T11:57:05.947797162Z caller=fetcher.go:321 component=block.BaseFetcher msg="fetching meta data" concurrency=32

Anything else we need to know:
Environment:

OS (e.g. from /etc/os-release): Linux
Kernel (e.g. uname -a): 4.14.105
Others:
inspect metrics

$ curl -s *${thanos tools web addr}/metrics|grep fail
# HELP thanos_bucket_blocks_meta_sync_failures_total Total blocks metadata synchronization failures
# TYPE thanos_bucket_blocks_meta_sync_failures_total counter
thanos_bucket_blocks_meta_sync_failures_total 4
thanos_bucket_blocks_meta_synced{state="failed"} 123
# HELP thanos_objstore_bucket_operation_failures_total Total number of operations against a bucket that failed, but were not expected to fail in certain way from caller perspective. Those errors have to be investigated.
# TYPE thanos_objstore_bucket_operation_failures_total counter
thanos_objstore_bucket_operation_failures_total{bucket="***",operation="attributes"} 0
thanos_objstore_bucket_operation_failures_total{bucket="***",operation="delete"} 0
thanos_objstore_bucket_operation_failures_total{bucket="***",operation="exists"} 753
thanos_objstore_bucket_operation_failures_total{bucket="***",operation="get"} 0
thanos_objstore_bucket_operation_failures_total{bucket="***",operation="get_range"} 0
thanos_objstore_bucket_operation_failures_total{bucket="***",operation="iter"} 0
thanos_objstore_bucket_operation_failures_total{bucket="***",operation="upload"} 0
# HELP thanos_status Represents status (0 indicates failure, 1 indicates success) of the component.

I think the root cause it the cos client use http.MaxIdleConnsPerHost=2, but it concurrent num of fetch metadata is 32, then many http connection create and close. too many TIME_WAIT.


Update understand-cost-mgt-data.md

updated Tags section: removed list of services that support/partly support tags in cost reports

@bandersmsft
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


[Feature] status: get running status of your app

$ rudr status frontend
Running Status  1/1 (OK)
Workload:
  apiVersion: apps/v1
  kind: Deployment
  metadata:
    name: frontend
  status:
    ...
Route:
  apiVersion: core.oam.dev/v1alpha2
  kind: Route
  metadata:
    name: frontend-xxx-trait
  status:
    ...

As we will support multiple workloads in one app, workloads should be in a list format and traits should be in traits list of each workload.


CAN_BE_NULL_AFTER_NULL_AWARE too aggresive

CAN_BE_NULL_AFTER_NULL_AWARE triggers even with method calls that are defined on Null:
void main() {
  String a = null;
  // Analyzer warning: The expression uses '?.', so can be 'null'
  print(a?.length.hashCode);
}

https://dartpad.dartlang.org/0980bcd5579ed5643c5ac6f87d06fac0
In this case, hashCode is defined on Null.
For justification on why anyone would want to do this, we want to generate a hashCode on an instance of a class whose attributes might have null values, such as this hashCode method from package:html.

For the record, I think this is so uncommon that we should change the language to let something?.foo.bar evaluate to null when something is null, instead of trying to read bar off null.
Then this code would have to be written as (something?.foo).hashCode.

https://codereview.chromium.org/2320573003

https://github.com/dart-lang/sdk/commit/114fcdb839e2b0ba8902fb5422aa55fb02d74aec


Proposal: introduce --filter-trace-tunnel-type and --filter-trace-tunnel-pcap

As for VxLAN env, it'll be really convenient to trace skb with filtering inner-VxLAN packet info with pcap-filter, as pcap-filter does not support filtering inner-VxLAN packet info directly.
To achieve it, let me introduce --filter-trace-tunnel-type and --filter-trace-tunnel-pcap options to accept a pcap-filter expr to filter inner-VxLAN packet info.
$ sudo pwru --filter-trace-tunnel-type vxlan --filter-trace-tunnel-pcap 'host <IP_ADDRESS> and icmp' host <IP_ADDRESS> and icmp

Then, pwru is able to trace skb before decapsulating VxLAN and after encapsulating VxLAN.
And --filter-track-skb does not work well before decapsulating VxLAN.
Furthermore, --filter-trace-tunnel-type should support geneve, ipip and so on.
TODOs:

[ ] Introduce --filter-trace-tunnel-type vxlan
[ ] Introduce --filter-trace-tunnel-type geneve
[ ] Introduce --filter-trace-tunnel-type ipip

I like this, thank you!
Just to be clear, --filter-trace-tunnel-pcap 'host <IP_ADDRESS> and icmp' host <IP_ADDRESS> and icmp in your proposal, will match nothing, right? My understanding is
--filter-trace-tunnel-pcap 'host <IP_ADDRESS> and icmp' host <IP_ADDRESS> and icmp
                            ---------------------  ---------------------
                                      ①                      ②

① filters inner packet, from skb->data + sizeof(outer)
② filters outer packet, from skb->data
Since a vxlan can't have an outer icmp, no traffic will be captured.

Oh, what are we missing here?
It's the bool logic between ① and ②. It should be "① or ②" by default. And use --filter-trace-tunnel-both, or any option, to indicate "① and ②" instead.

What is the use case of "or"? I think "and" is more useful to catch "out ip <IP_ADDRESS> and vxlan and inner ip <IP_ADDRESS>"

"out ip <IP_ADDRESS> and vxlan and inner ip <IP_ADDRESS>"

This seems better for me.
Why not use "and vxlan", "or vxlan" instead of --filter-trace-tunnel-XXX options? The pcap-filter expr before them filters vxlan outer packet. The one after them filters vxlan inner packet. "and" and "or" in them indicate the bool logic.
Same for geneve and ipip.

Was thinking about this. I have an ambiguous feeling of cool and dangerous about what we are doing here: extend pcap filter.


M3-281 - Notice component functional test

Adds test spec for the notice component

To Test
yarn storybook
yarn storybook:e2e --story Notice

Coverage decreased (-0.05%) to 27.414% when pulling fa5c61f0ef9526f8e680f2e0a905a7027914e8b4 on patthiel:M3-281 into 9e9b3eb3a67b645e07af69d18c4ef9029473e22e on linode:develop.


Allow Terraform to create security group for MI install

Currently the security group needs manually creating in Openstack and then defining by name in the TF automation for MI, this can be automated by terraform (much as we create the keypair in Openstack automatically) and would reduce complexity + documentation steps.

I agree.
@matjohn2, did you have a list of rules that you would like to include in the security group?
We could think about public ip rules vs. private ip rules. Ideally, they would be the same.
List of ports we are using:
5050/tcp mesos-leader
5051/tcp mesos-worker
8080/tcp marathon
2181/zookeeper
2888/zookeeper
3888/zookeeper

Consul uses the following ports that need to be considered:
Server RPC (Default 8300). This is used by servers to handle incoming requests from other agents. TCP only.
Serf LAN (Default 8301). This is used to handle gossip in the LAN. Required by all agents. TCP and UDP.
Serf WAN (Default 8302). This is used by servers to gossip over the WAN to other servers. TCP and UDP.
CLI RPC (Default 8400). This is used by all agents to handle RPC from the CLI. TCP only.
HTTP API (Default 8500). This is used by clients to talk to the HTTP API. TCP only.
DNS Interface (Default 8600). Used to resolve DNS queries. TCP and UDP.

Hey.
I would like to contribute and fix this issue. But since I am new to certain methods I have two options to continue:

Read the entire source code and understand what exactly each ansible role does and how multiple technologies are curated to run together with all details
Dive right into this issue with some help and then figure out things on the go, a pure bottom up approach

Would anyone please suggest whether I can go on about fixing it right now following approach 2 or go to approach 1 and get implementation details cleared out first?

@sharma-abhishek-it Hopefully the following will help you get started!
Steven provided the ports above which should cover the inputs.
Then it is a matter of writing the terraform modules for the different cloud providers, see link for more details.
https://www.terraform.io/docs/index.html
This is an example of one I did for Openstack (specific to another project but an example):
variable cluster_name {}

provider "openstack" {
}

resource "openstack_compute_secgroup_v2" "cluster" {
    name = "${ var.cluster_name }"
    description = "Security Group for ${ var.cluster_name }"
    rule {
        from_port = 1
        to_port = 65535
        ip_protocol = "tcp"
        self = true
    }
    rule {
        from_port = 1
        to_port = 65535
        ip_protocol = "udp"
        self = true
    }
    rule {
        from_port = 80
        to_port = 80
        ip_protocol = "tcp"
        cidr = "<IP_ADDRESS>/0"
    }
    rule {
        from_port = 443
        to_port = 443
        ip_protocol = "tcp"
        cidr = "<IP_ADDRESS>/0"
    }
}

output "cluster_name" {
    value = "${ openstack_compute_secgroup_v2.cluster.name }"
}

Matt, also did a great write up with examples on terraform as well.
http://www.matt-j.co.uk/

@kenjones-cisco Alright let me iterate what I understand so far. We need terraform configuration for providing rules to security group(s). Now since we support multiple providers we need to write config for each provider's security group. An example for specifying aws security group rules can be seen here from line 6. In a similar fashion we need to rewrite rules. as mentioned by Steven, for all the providers we currently support.
So first you will need to tell whether my understanding is correct.
Meanwhile I have a few questions regarding implementation.

I believe we will be using variables for port numbers? Since we will be repeating config in each provider's security group block I think it is better to make it a bit DRY. Right now all we can do is map the values of port numbers to variables. Is there any other way to do this? A for loop would have been great, but it does not YET exist(look here)
I think the rules will be written inside corresponding terraform/{provider}/*.tf  files?  I saw aws.tf and it has some existing rules. So these new rules will go in those blocks right?

@sharma-abhishek-it Your understanding is correct.
The port numbers within each resource would be static, and DRY within each provider. But each provider is independent such that the same information will need to be repeated for each cloud provider currently supported.
Yes, the rules are written within terraform/{provider}/*.tf files. For aws it would be adding rules based on the list provided by Steven.

@kenjones-cisco regarding variables I was meaning to load a .tfvars file where all the port numbers will be listed. That way without repeating the actual values of port no I will simply be using their corr. variable names in each provider.
That was one thing. Another thing is that terraform also accepts JSON and recommends it for machine generated files. Do you think we should generate the configuration for providers instead of writing it down for each separate one? Why I say that is we might need to add new ports tomorrow or something else completely different to run things like Kubernetes which needs a subnet of all machines for proper resource allocation. If we are generating those JSON then things are way more DRY. Don't know if that is out of scope of this issue or whether there are any drawbacks of it. For instance one drawback is that our generation script/tool will need to be tightly coupled with terraform provider's resource definitions. Although we are already tightly coupled since we are defining those tf files in the first place. Please share your thoughts on this.

The .tvars would be a good approach for handling all the exposed ports.
I like where you are going with the generate direction, but I believe that part could be a second PR to enable automation of creating the terraform files.
@matjohn2 @stevendborrelli Please feel free to weigh in.

oops seems like I cannot run infrastructure locally yet! Look hashicorp/terraform#265
guys am waiting on you to tell me how to proceed ahead on this one. Where do I run my code after developing it? I do not have any account with cloud provider... And my AWS free tier expired way back in time. Please help!

@sharma-abhishek-it You can at least test your code in Vagrant once written. If you submit a PR and ask for help testing, we can lend a hand.

Regarding .tfvars file. I am trying to write all ports in one tfvars file that could be reused by any provider. My only concern is that some providers(e.g GCE) use strings for port no. like "22" while other(e.g AWS) use numbers 22. So in this case what should I do? Is it possible that it does not matter whether the port no. is a string or an integer(no.)? If it does matter should I make two variables then, like this
mesos_leader_port = 5050
mesos_leader_port_str = "5050"

Guys any suggestions for the above? should I skip tfvars for now and instead hardcode these ports? That makes testing also easier since tfvars need to copied to the directory where terraform is run on. So we will need a script to do that and include those in tests as well. So should I skip using tfvars and just hardcode ports in the providers tf files?

My thoughts, continue the hard coded approach for now to keep things simple.

Hey guys I opened PR #651 and it failed all tests. Could anyone help me sort out where the test is failing and how to debug this? The output is here

Hey guys stuck a bit on this. Issues are happening in my PR #651 but I do not have openstack setup on my dev desktop. So I believe I will need to do a local openstack and deploy things to debug this locally? What should I do?

Do you have access to an openstack cluster?
If not, you could try trystack.org or one of us will have to test it.

Ok I will try out trystack.org. And terraform will handle setting up the cluster on trystack?

Hi. I've been working on implementing group creation for terraform/openstack and also some refactoring for auth and terraform variables, but I'm unable to push and create a remote branch for pull request. Could someone help me and grant an access? Thanks.

@antimack I'm assuming you figured out how to make a clone, etc.? Did you need any other help?

@siddharthist I've forked the repo and created a pull request, so this isn't a problem anymore, thanks.

I think automation of security group creation should focus on end usage.  For example, a security group containing my control nodes has a homogeneous set of connection needs, while the same is true for compute and edge.  Without the edge nodes in their own security group, we're likely to accidentally shoot ourselves in foot as we try to expose an app and instead expose the admin console (where this isn't prudent).   Therefore, a security group for each type of node would be best, if it's being automated anyway.  Manually, this would be too much work, IMHO.


Error: Bad Credentials | Buffer() is deprecated due to security and usability issues

I encounter this issue when trying to print the report.

Nvm error is on my side. I used the wrong github token


Firmware update is not comprehensible and look very buggy.

Sorry for this mess, I rather post a half assed bug report and format it later than risk not following through onto something that I think is urgent.
I've seen too many error messages , unexpected and incomprehensible behavior trying to do the firmware update.

I've tried updating a Nano-S, I saw something on the screen asking to approve the update. I don't remember exactly but when I tried the update a 2nd time the ledger got forever stuck at "UPDATE" on the screen wherever I would plug it. (Looked Bricked)

I later found out that I had to click firmware on the other tab...
I tried updating another Ledger using another computer and different problem.
ledger-manager-logs-1477033204318.txt
Every time I click "firmware" it update the firmware - (it seems like it did - no progress - no completion message)
Your button should say UPDATE FIRMWARE and UPDATE OSU then pop-up the disclaimer/warning about deletion of the seed requiring to agree.

Compared to Trezor Ledger notice is very easy to miss :

Is it normal that the wallet say there is no update ?

I click :

I get :

Ledger does not verify that the OSU is already updated or not. It's not clear whether it ever worked or not.
Ledger Manager addon taking 100% CPU

On two browser at once without a ledger connected:

CPU when killing one addon then killing the 2nd :

It seems that you applied the OSU (which prepares the device for a firmware update) but not the firmware itself.
"Update" means that you now have to install the firmware, see the "Firmware" section in the Ledger Manager: there is an "OSU" button and a "Firmware" button. Plug the Nano S, wait for the "Update" screen to show, and click "Firmware".

Did you click on firmware (right button) after having clicked on osu? When
in update mode the Nano S is waiting for the firmware to be flashed
Le 21 oct. 2016 09:11, "Transisto"<EMAIL_ADDRESS>a écrit :

I've tried updating a Nano-S, I saw something on the screen asking to
approve the update. I don't remember exactly but when I tried the update a
2nd time the ledger got stuck at "UPDATE" on the screen.
[image: image]
https://cloud.githubusercontent.com/assets/388716/19589729/f3a11202-973b-11e6-899d-e7578095314a.png
Also is it normal that the wallet say there is no update.
[image: image]
https://cloud.githubusercontent.com/assets/388716/19589330/aa44b3ea-9739-11e6-8c52-850da41a4da9.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/LedgerHQ/ledger-nano-s/issues/8, or mute the thread
https://github.com/notifications/unsubscribe-auth/AA-H-HNZV1cz9UP2iniGRU0tnYqMb19dks5q2GW1gaJpZM4Kc7Mw
.

Any updates here?
Is there still issues to address with firmware updates given that it has been a year?

No, it works well for all purposes


If a temp file cannot be created, report that as a separate error message (not just UnsatisfiedLinkError)

This cost me a few hours, in the hope it won't for the next guy.

Something seems to be wrong with the test setup here, I don't think it has anything to do with my PR.

@jernst I believe you are correct. I'll merge!


Request for clarifications regarding hardware capabilities for shared mappings

In the target platforms doc, there is a section explaining that the E-SIG feels comfortable assuming an MPU or MMU for efficient implementations.  This is very helpful since it gives us a baseline of memory-related hardware capabilities that we can assume when considering implementations strategies for various features.
Just to state some assumptions to see if I'm understanding these terms correctly so folks can correct me if I'm wrong:

an MMU includes some sort of page table for mapping virtual addresses to physical addresses allowing page-granularity control over both access-rights as well as sharing (where multiple virtual addresses map to the same physical address);
an MPU includes a finite set of protection registers that can be used to configure at runtime access-rights for a finite set of address ranges.

Based on these assumptions, one corollary is that any feature that requires fine-grained/page-level control over an unbounded set of memory ranges wouldn't work on an MPU and thus would not work across all the target platforms.
But one thing that's unclear to me is whether an MPU allows mapping a finite set of distinct "virtual" addresses to the same "physical" page of RAM.  Hypothetically, it seems like an MPU could do this without blowing its limited hardware budget by including an "offset" field in its per-region configuration state that was added as part of address translation.  With this hardware capability, we could, e.g., efficiently support a small finite number of "mmap()s" (or features that want to be implemented in terms of mmap()).  However, scanning the docs of the popular ARM Cortex-M MPU, it seems like at least this one popular MPU can't do such shared mappings.  However, I've also heard that various extensions outside the official ARM Cortex-M MPU extension might allow this?  Also, I have no idea about the wider world of MPUs.
So, what I'd love to get a clarification on (here and, ideally, in the doc) is whether the E-SIG believes that such shared mappings are indeed possible across the target platforms' MPUs or perhaps whether we want to raise the baseline to assume an MMU.
One discussion where this is concretely relevant is in the WebAssembly CG memory-control proposal (and its collection of sub-proposals), e.g., memory-control/#19, which does seem to assume an MMU.

IMO, some RTOS and bare-metal applications need memory protection, but they don't require full virtual memory support. Therefore, having a MMU is optional.
In scenarios without an MMU, a few customers opt to extend the sandbox to cover the entire memory, or in other words, disable the boundary check.
Another interesting case is with another customer's product, where a Wasm application and its native libraries can use virtual memory and DMA to access two different address spaces.

Thanks for raising this, your right @lukewagner we could do more to clarify this.  This is a good issue to also bounce of the e-sig mailing list, and I'll do that. Also useful to bring this up on Zulip, just to get additional eyeballs on it.
E-SIG Hardware Platforms and Memory Control Hardware
The e-sig stated that the devices that the we should target would come with a minimum of 512kb of RAM and 1mb of storage. Finding devices with this much RAM without any form of hardware memory protection was hard. If the device has more than a handful of kb of RAM it will undoubtedly come with either an MPU or an MMU. Based on the e-sig's hardware list (see below) of the 5 platforms we've selected 3 come with an MMU and 2 with an MPU.
What does this mean in practice ?

So, what I'd love to get a clarification on (here and, ideally, in the doc) is whether the E-SIG believes that such shared mappings are indeed possible across the target platforms' MPUs or perhaps whether we want to raise the baseline to assume an MMU.

I think it is probably not possible to assume the presence of an MMU, and we should account for MMU or an MPU. We do not need to account for a world in which neither are present, as these devices are just too limited even for the E-SIG. - However, I'm be delighted to open this up to debate, and see what the other stakeholders in the E-SIG think - email promotion of this issue is coming ;)
There is an argument which says that the growing capabilities of MPUs and the growing prevalence of MMUs mean that the need to support limited MPU's is shrinking. - Hence why I'd like to open the discussion a little wider.
But, without a chip in from others, I'd assume that we should aim to support both an MMU and an MPU.
Picking Hardware for An Application
In my view @lum1n0us two examples provide the two extremes of the embedded world -  The real truth is that the choice of hardware is application specific. if we've got an application that needs virtual memory, then selecting hardware with an MMU is preferable.
Impact on WASM - Functional Equivalence, Not identical functionality (Similar to Linux's Approach?)
So, if we can't assume that there is something MMU like on a device, what can we do? - Well, looking out at other projects we can take a queue from Linux. Which provides user land source if not binary compatibility.
Today it is possible to run Linux on devices without an MMU (uClinux for example), and in those situations Linux can provide the running application functional compatibility but with out the same side effects. For instance we can use mmap to in a function which look's like it is going to memory map access to a peripheral. If that device has an MMU then, that will be exactly what happens - and the mapping is implemented via hardware mapping. On a device without the MMU then the real physical address of the peripheral is simply returned, as the there is no mapping to do. On devices with an MPU, this function can be used to reconfigure the MPU to allow the running application to see the physical address, even if there is no hardware mapping occurring. - The kernel.org page here provides a pretty detailed explanation of what Linux is doing.
As @lum1n0us suggests something similar is needed in the embedded Wasm world. The same code should function as expected, but it is acceptable to encounter performance  impacts with manual copies of memory between locations, or perhaps alternatively allow a weak sandbox where memory protection isn't present. But these are trade offs that can be made based on the application use case and cost point for hardware.
The important aspect is that the same code will operate successfully.
To aid in this discussion I've updated the selected hardware table (see below) with hardware management features.

ISA
Board / Purchasable Hardware
Memory Management Features

Xtensa
ESP32-S3-BOX-3
MPU present Tensilica Xtensa LX7 Processor Datasheet

RISC-V 32
N/A - Suggestions welcome

ARM 32
STM32H747AG
MPU present link

RISC-V 64
PINE64 Ox64
MMU present (RISC-V Ox64 BL808 SBC: Sv39 Memory Management Unit

ARM 64
Raspberry Pi 3
MMU present

x86-64
Lattepanda-v1
MMU present

Hypothetically, it seems like an MPU could do this without blowing its limited hardware budget by including an "offset" field in its per-region configuration state that was added as part of address translation. With this hardware capability, we could, e.g., efficiently support a small finite number of "mmap()s" (or features that want to be implemented in terms of mmap()). However, scanning the docs of the popular ARM Cortex-M MPU, it seems like at least this one popular MPU can't do such shared mappings.

This is an interesting idea. Perhaps Stephen from Aytm would have a view on this? I think Aytm's mainly focusing the ARM market at the moment.

(Thanks for all the info so far and looking forward to seeing all the other responses.)

per The same code should function as expected, but it is acceptable to encounter performance impacts with manual copies of memory between locations, or perhaps alternatively allow a weak sandbox where memory protection isn't present. and in other words, disable the memory check I'm assuming this breaks the core spec, yes? Because understanding how to navigate that it's not core spec compatible will be a thing we should tackle head on.
For example, if:

we cannot run on a required hardware spec without breaking the core spec's security guarantees and
we cannot figure out a path to modify things such that it can be done then
it's possible we are creating the boundary "branding" between wasm and something else that is almost wasm but which doesn't have the same security guarantees. But it wouldn't be able to claim wasm runtime guarantees though it could claim to execute wasm code.

There really are lots of angles to explore prior to that, however, but it remains possible for sure.
That issue aside -- because it may be a no-op if there are in fact ways to finesse this as the component model evolves forward -- the hardware specificity we can tackle together is a great result of this document. Without it, we can't really change the spec as needed to address the issues. I love that the SIG is in fact digging into where things work, where they don't, and what the limits may actually be in the future (We do not need to account for a world in which neither are present, as these devices are just too limited even for the E-SIG. is definitely a limit! :-) )

per The same code should function as expected, but it is acceptable to encounter performance impacts with manual copies of memory between locations, or perhaps alternatively allow a weak sandbox where memory protection isn't present. and in other words, disable the memory check I'm assuming this breaks the core spec, yes? Because understanding how to navigate that it's not core spec compatible will be a thing we should tackle head on.

I was thinking more along the lines of what Linux is doing - and using this as a bit of an inspiration.  There are two behaviours for the same function call. I'll explain the thought exercise here, but it could equally well live with the discussion over on the structured memory issue @lukewagner pointed to.
Considering Linux:

On an MMU -  The mmap call on an MMU device does map the memory range into the calling processes memory space.
On an MPU - The mmap call on an MPU device returns the raw memory address (no mapping) but could, and should, if possible, provide memory protection around accessing that memory.

The results from the caller perspective are same -> they have access to the memory address they require. But the implementation is, of course different.
Thinking about WASM - Regarding Memory Protection for the returned pointer from mmap for MPU devices
This is of course with native non-wasm code. In a Wasm runtime we'd need to somehow track and accommodate that mmap pointer - there would be some housekeeping around this.  This is worth a bit of brainstorming here to really explore the options. But it could be the case that the MPU is limited and cannot provide guarded memory access to the raw pointer returned by the call to mmap. Here (again this is the thought experiment) we could do one of two things:

Drop the memory protection - this is roughly what @lum1n0us was indicating happens today for some WAMR users - and hey, this is alright because the hardware is application specific, and the risks known and understood. But I do get potential branding issues around claiming this as core-wasm / wasi concept.
Enforce software bounds checking for memory accesses to this pointer to host memory - this isn't possible today without a core WASM change, but this could be achieved with a fat pointer - which would include a flag saying it was a native pointer, not an offset inside a memory index, and it would also include the bounds checking information - the permitted range. When these pointers are dereferenced they could then be verified. - This is what CHERI is doing in HW. Yes, there would be a performance hit - and that would be acceptable, if you wanted to the performance hit to go away, the use an MMU.

It is also this thinking (2) which pushes us toward the concept of just having a second memory mapped with mmap.
Note this is just brainstorming - all thought experiments, I can see avenues in which support from core-wasm would really help. That aside, I hope this brainstorming helps in explaining how some folks are approaching the constraints. Certainly, the performance hit is totally acceptable - in the embedded world the hardware is chosen and is application specific, it's not a general compute device, therefore if you really need to do a lot of memory sharing there is an argument that says - you should stump up and pay for hardware with an MMU, or accept the limitation.


Error on Microsoft.AspNetCore.Mvc.Routing.ApiVersionMatcherPolicy

I get this error
"Method 'ApplyAsync' in type 'Microsoft.AspNetCore.Mvc.Routing.ApiVersionMatcherPolicy' from assembly 'Microsoft.AspNetCore.Mvc.Versioning, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation.":"Microsoft.AspNetCore.Mvc.Routing.ApiVersionMatcherPolicy"
my code is
services.AddApiVersioning(o =>
{
o.ReportApiVersions = true;
o.AssumeDefaultVersionWhenUnspecified = true;
o.DefaultApiVersion = new ApiVersion(2, 0);
});

@iceoz As in #504, .NET Core 3.0 is not yet supported. Use preview for now:
<PackageReference Include="Microsoft.AspNetCore.Mvc.Versioning" Version="4.0.0-preview8.19405.7" />

Correct. You need to use the preview version - for now. Working on the official release. It'll be out ASAP. I expect this issue is now resolved. If not, feel free to reopen it. Thanks.

I havent seen anyone else say anything about it but, Im still getting this issue with 4.1
System.Private.CoreLib: Exception while executing function: WebAppProxy. Microsoft.AspNetCore.Mvc.Versioning: Method 'ApplyAsync' in type 'Microsoft.AspNetCore.Mvc.Routing.ApiVersionMatcherPolicy' from assembly 'Microsoft.AspNetCore.Mvc.Versioning, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60' does not have an implementation.

Clearly I'm doing something wrong.
Project file
<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp3.0</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer" Version="4.1.0" />
    <PackageReference Include="Swashbuckle.AspNetCore" Version="5.0.0-*" />
    <PackageReference Include="Swashbuckle.AspNetCore.Annotations" Version="5.0.0-*" />
  </ItemGroup>
</Project>

@abezverkov 4.1 targets ASP.NET Core 3.1 and .NET Core 3.1. Beyond that, there is zero difference from 4.0. I see your application is configured for NET Core 3.0 and not 3.1. Updating that will probably fix it. Unfortunately, API Versioning still multi-targets to ASP.NET 2.2 in order to support OData. It targets .NET Standard 2.0. You'd have to look in the restore logs, but I willing to bet that NuGet couldn't match the .NET Core 3.1 reference and fell back to using the .NET Standard 2.0 version, which is completely wrong. I don't have a good answer for that. I'm not sure there's anything more that I can do to avoid this behavior (a few people seem to have encountered it now).
I hope that helps.

Is there a reason why 4.1.1 doesn't support .net standard? Looks like 4.1.0 does...
Severity	Code	Description	Project	File	Line	Suppression State
Error	NU1202	Package Microsoft.AspNetCore.Mvc.Versioning 4.1.1 is not compatible with netstandard2.0 (.NETStandard,Version=v2.0). Package Microsoft.AspNetCore.Mvc.Versioning 4.1.1 supports: netcoreapp3.1 (.NETCoreApp,Version=v3.1)	<obfuscated>	C:\dev\<obfuscated>\src\<obfuscated>\<obfuscated>.csproj	1


docs: fix docs for catalog module "unprocessed"

Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@pjungermann will need a changeset for the readme and a rebase to make the build 🟢


fix: change go module name to match dagger module name

This effectively reverts #5983, since with go.work support we can't have duplicate module names inside a single namespace.
Thankfully though, we can avoid the original issue that this fixed (where go is effectively a reserved module name), by prefixing all module names with dagger/).
This helps for daggerverse-like repo structures, where the top-level go.work would ideally need to contain all the sub-modules.

Does it mean the generated main.go file has now the package dagger/xxx on top? Then where is the package main file?

No, the package main remains the same. It's just the module dagger/xxx in go.mod changes, which avoids having the weird go.work clash we previously introduced.


Explorer mode

Closes: #2024
Adds an ability to explore the site using any wallet address.
Main changes:

adds Explorer Mode
adds icon of the wallet on the top-right of the page
adds the ability to log in to the wallet and send a transaction that you executed while being in explorer mode (you have to connect to the same account that you have used in explorer mode)
[IN PROGRESS] add the ability to go into explorer mode by pasting the url with the correct address in it (example pattern: https://dashboard.keep.network/<address>/delegations/granted)

Side notes:

creates a custom subprovider for Explorer Mode that catches the 'eth_sendTransaction' method and emit the payload of it to the ui to save it in redux store
creates a transaction queue in the store where we are saving the payloads of the 'eth_sendTransaction' methods are added while being in explorer mode. Then these methods will be executed when user connect to the wallet.
background of address in the top-right corner is greyed out to emphasise clearly that user is in Explorer Mode
[DESIGN NEEDED?] We probably need to think about some different icon for the explorer mode. Right now i used the wallet icon, but i think it does not match it. Maybe it will be better to add like svg icon of the eye since it's the read-only mode? 🤔 Please see screenshots below.

Applied UI solutions:

Wallet icons of the connected wallet on the top-right corner of the page
MetaMask:

Explorer Mode:

Connect wallet dropdown

Explorer mode modal window
This windows pops up after choosing ExplorerMode in the connect wallet dropdown.

Connect to wallet modal window
This windows pops up after trying to do a transaction while being in Explorer Mode

Hovering on Connect Wallet button:

@liz-shinn You can check the top post for the UI solutions that i applied in this task. Feel free to propose some improvements 😃

Awesome! Have a few thoughts:

Wallet icons of the connected wallet on the top-right corner of the page

I like the solution of adding the wallet icon into the header when you have a particular wallet connected!
I think that the Explorer Mode icon could look more like "explore" though – perhaps it's a 🚀 or a 🌐 , potentially 🔍 but that could look like search so maybe not. I lean towards 🌐

Connect wallet dropdown

Would add a space so it's "Explorer Mode" instead of explorermode, and swap out the icon for whatever the more "explore" icon is from above.

Explorer mode modal window

The modal title would make more sense as "Connect Ethereum Address" instead of Connect Wallet.

Connect to wallet modal window

Modal title would be "Select Wallet" with a capital "W" to be consistent since we use title case in other modal instances
Would alter the modal text to read: "You're viewing the Dashboard in Explorer Mode. Connect a wallet to proceed."

This line on the modals should be above the button as a footer indication:

Should also have a cancel option next to the action button

@michalsmiarowski Added the icon to the Figma file! It's here: https://www.figma.com/file/Su61MwHLrQn3ld24q85pMx/Token-Dashboard-dApp?node-id=8739%3A28

@r-czajkowski All comments addressed - ready for another round of review


Installation failed

Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...
npm ERR! Exit handler never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     https://github.com/npm/cli/issues
npm ERR!      C:\Users\New\AppData\Local\npm-cache_logs\2022-05-12T05_42_42_179Z-debug-0.log
Aborting installation.
npm install --no-audit --save --save-exact --loglevel error react react-dom react-scripts cra-template has failed.

I've encountered this multiple times.
First I would suggest that you run npm uninstall -g create-react-app since the global version isn't supported anymore. And this is where every devloper face this issue
Then try npx create-react-app my-app again.
If that does not work, try to run:
npm init
npm install create-react-app
npx create-react-app my-app
The steps above have solved the issue for me a couple of times.


Orphan Nodes can go below 0

Godot version:
3.2.dev.custom_build. 15425b450
OS/device including version:
Ubuntu 19.04

Steps to reproduce:

Run scene 3DALL and wait

Minimal reproduction project:
https://github.com/qarmin/The-worst-Godot-test-project/
commit 33ae1b283fad1b8e58072d5b763b6898d7104512
ZIP - https://github.com/qarmin/The-worst-Godot-test-project/archive/33ae1b283fad1b8e58072d5b763b6898d7104512.zip

Can't reproduce with Godot 3.2.2


⚠ GitLab Server has degraded performance

In fdae570, GitLab Server (https://gitlab01.its-telekom.eu) experienced degraded performance:

HTTP code: 200
Response time: 6088 ms

Resolved: GitLab Server performance has improved in 0535b09.


html sax parser not fixing not closing attributes

<IP_ADDRESS>
require 'bundler/setup'
require 'nokogiri'

class Doc < Nokogiri::XML::SAX::Document
  def characters(chars)
    p chars
  end
end

str = "<html>
<meta name = 'bla
<body>
body
</body>
</html>
"

parser = Nokogiri::HTML::SAX::Parser.new(Doc.new)
parser.parse_memory(str)

output is empty.
but if i change meta to:
<meta name = 'bla'

output is "\nbody\n"
i think nokogiri also should fix first example;

Hi,
Thank for reporting this.
Can you provide the output from nokogiri -v so that we know what your
environment looks like?
-m
On May 10, 2015 11:56 AM, "kostya"<EMAIL_ADDRESS>wrote:

<IP_ADDRESS>
require 'bundler/setup'require 'nokogiri'
class Doc < Nokogiri::XML::SAX::Document
def characters(chars)
p chars
endend
str = "<meta name = 'blabody"
parser = Nokogiri::HTML::SAX::Parser.new(Doc.new)
parser.parse_memory(str)
output is empty.
but if i change meta to:
<meta name = 'bla'
output is "\nbody\n"
i think nokogiri also should fix first example;
—
Reply to this email directly or view it on GitHub
https://github.com/sparklemotion/nokogiri/issues/1286.

# Nokogiri (<IP_ADDRESS>)
    ---
    warnings: []
    nokogiri: <IP_ADDRESS>
    ruby:
      version: 2.2.0
      platform: x86_64-darwin13
      description: ruby 2.2.0p0 (2014-12-25 revision 49005) [x86_64-darwin13]
      engine: ruby
    libxml:
      binding: extension
      source: packaged
      libxml2_path: "/Users/kostya/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>/ports/x86_64-apple-darwin13.0.0/libxml2/2.9.2"
      libxslt_path: "/Users/kostya/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/nokogiri-<IP_ADDRESS>/ports/x86_64-apple-darwin13.0.0/libxslt/1.1.28"
      libxml2_patches:
      - 0001-Revert-Missing-initialization-for-the-catalog-module.patch
      - 0002-Fix-missing-entities-after-CVE-2014-3660-fix.patch
      libxslt_patches:
      - 0001-Adding-doc-update-related-to-1.1.28.patch
      - 0002-Fix-a-couple-of-places-where-f-printf-parameters-wer.patch
      - 0003-Initialize-pseudo-random-number-generator-with-curre.patch
      - 0004-EXSLT-function-str-replace-is-broken-as-is.patch
      - 0006-Fix-str-padding-to-work-with-UTF-8-strings.patch
      - 0007-Separate-function-for-predicate-matching-in-patterns.patch
      - 0008-Fix-direct-pattern-matching.patch
      - 0009-Fix-certain-patterns-with-predicates.patch
      - 0010-Fix-handling-of-UTF-8-strings-in-EXSLT-crypto-module.patch
      - 0013-Memory-leak-in-xsltCompileIdKeyPattern-error-path.patch
      - 0014-Fix-for-bug-436589.patch
      - 0015-Fix-mkdir-for-mingw.patch
      compiled: 2.9.2
      loaded: 2.9.2

Hi @kostya,
Apologies for not responding sooner. In the first example, libxml2 considers everything after the ' character to be an unclosed string, not an unclosed tag.
Nokogiri is limited in how broken markup is corrected by its underlying libraries (libxml2 for MRI or xerces for JRuby), and unfortunately there's nothing we can do without drastically invasive changes.
Sorry we can't help you in this situation.


Giving an Arcade body to a tileSprite doesn't take the correct dimensions if static

When giving a non-static Arcade body to a tileSprite, the dimensions of the body will correspond to those of the tileSprite, so that works as expected:
// non-static (size of physics body correctly  matches that of tileSprite)
  let platform1 = this.add.tileSprite(10, 100, 36 * 4, 30, 'block').setOrigin(0);
  this.physics.add.existing(platform1, false);

However, if the Arcade body is set as static, the dimensions of the body don't match those of the tileSprite. Screenshot: https://www.screencast.com/t/nZZxbUKEm
// static (size of the physics body doesn't match that of the tileSprite)
  let platform2 = this.add.tileSprite(10, 200, 36 * 4, 30, 'block').setOrigin(0);
  this.physics.add.existing(platform2, true);

Full example:   https://github.com/fariazz/phaser-tilesprite-size-issue

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

Thanks for the quick fix @photonstorm ! That fixed it on my end.


Window transparency enabled + a hidden screen-reading shader over a Camera3D makes the game window semi-transparent

Godot version
v4.1.2.stable.official [399c9dc39], v4.2.beta3.official [e8d57afae], Forward+
System information
Godot v4.2.beta3 - Windows 10.0.19044 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 (NVIDIA; <IP_ADDRESS>99) - Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz (4 Threads)
Issue description
There seems to be a bug with sampling the screen texture when:

Window transparency is enabled
A canvas item that has a material with a screen-reading shader is hidden, i.e. this node's visibility is false
The scene is 3D
Only in Forward+

It only seems to happen when all of these are true.

A workaround is to keep the node visible and instead set the alpha of its modulate to 0
I think #78207 could be related, but I haven't found any other issue with this problem
Steps to reproduce

Start a project in Forward+
Enable Window Transparency in the project settings (display/window/size/transparent, and other settings related to transparency do not seem to affect this issue)
Add a ColorRect covering the screen, add a ShaderMaterial to it with the following shader:

shader_type canvas_item;

uniform sampler2D screen_texture : hint_screen_texture;

void fragment() {
    COLOR = texture(screen_texture, SCREEN_UV);
}

Hide this node
Add a Camera3D to the scene

Minimal reproduction project
Transparency Bug Minimal Repro.zip

This screenshot may be a better indication of what I mean. This entire 3D scene is rendered semi-translucent due to this issue (looks like additive blending?), the expectation is that all of this should be opaque.
Note that I don't have any other of the "required" settings for a transparent window, like "per pixel transparency" (as per the docs: "For the background to be transparent, the root viewport must also be made transparent by enabling rendering/viewport/transparent_background." and "Note: This setting has no effect if display/window/per_pixel_transparency/allowed is set to false."), and I had only enabled the transparent window for the sake of having a transparent splash screen.

This is due to the alpha channel being set to 0, which means additive blending is used (because transparent windows use premultiplied alpha).

Thanks for your response Calinou :)

This is due to the alpha channel being set to 0.0, which means additive blending is used (because transparent windows use premultiplied alpha).

This happens even when I manually do COLOR.a = 1.0, unless you mean visibility being false sets alpha to 0.0 behind the scenes?

You should be able to turn off window transparency in DisplayServer after starting the project. We should probably add a specific project setting that enables transparency only during the splash screen phase.

I actually tried several ways of doing this to no avail, iirc this is everything I tried:
get_window().transparent = false
get_window().transparent_bg = false
get_viewport().transparent_bg = false
DisplayServer.window_set_flag(DisplayServer.WINDOW_FLAG_TRANSPARENT, false)
ProjectSettings.set_setting("display/window/size/transparent", false)

I'm guessing the last line does nothing anyway, and that's one of those settings that gets read only on startup? But it's there for good measure I guess.
Is there another way that I'm missing?

I have run into the same problem when attempting to enable Subsurface Scattering or DOF Blur; without these options enabled, transparency works as expected, but once either one is enabled, the problem reappears.
Perhaps not coincidentally, both of these options are only available in the Forward+ renderer, which leads me to suspect that the issue has something to do with Forward+ renderer being enabled/used, at the same time as window transparency.
Could someone who knows the renderer better than me speak to whether that even makes sense? When in Forward+ renderer mode, are parts of the renderer 'disabled' until a feature is used?
Alternative version of step 3 to reproduce the problem: enable Subsurface Scattering on any mesh, or DOF Blur on your camera's attributes.

Looks like it is fixed in master since v4.3.dev3, except for a moment when it starts.


'cl.exe' is not recognized as an internal or external command, operable program or batch file.

This github action puts msbuild in the PATH but not other compiler tools, like CL.
Is this intended? How can I use CL for compiling in a github workflow?
This caused the problem for me: https://github.com/gaebor/primes/blob/b8f0f58970529bd89a0ace7191e6d9ef2cbbc223/.github/workflows/test.yaml#L32-L42
where msbuild  # success
where cl       # cannot find

But msbuild can clearly use cl during the build.

Hi @gaebor, this action only sets the path for MSBuild...it does not add the other VC tools paths (which are not in the same location). There are a few other community actions that have configured these such as https://github.com/seanmiddleditch/gha-setup-vsdevenv (that do some vcvarsall type activity).
I understand that msbuild clearly can use a set of other tools (cl, etc), but for this action we've focused only on msbuild and not expanding as of now.  We get a few requests for other paths (eg test), etc. but keeping this solidly focused on the name -- msbuild
Going to just close this as we are not planning on changing to expand support in this action

Thanks 🤗


[red-knot] Add support for untitled files

Summary
This PR adds support for untitled files in the Red Knot project.
Refer to the design discussion for more details.
Changes

The parsed_module always assumes that the SystemVirtual path is of PySourceType::Python.
For the module resolver, as suggested, I went ahead by adding a new SystemOrVendoredPath enum and renamed FilePathRef to SystemOrVendoredPathRef (happy to consider better names here).
The file_to_module query would return if it's a FilePath::SystemVirtual variant because a virtual file doesn't belong to any module.
The system_virtual_path_to_file was adopted from the existing system_path_to_file.
The sync implementation for the system virtual path is basically the same as that of system path except that it uses the virtual_path_metadata. The reason for this is that the system (language server) would provide the metadata on whether it still exists or not and if it exists, the corresponding metadata.
The implementation of the virtual path related methods on the OsSystem and MemoryFileSystem always returns an Err(not_found)

For point (1), VS Code would use Untitled-1 for Python files and Untitled-1.ipynb for Jupyter Notebooks. We could use this distinction to determine whether the source type is Python or Ipynb.
Test Plan
I don't see any obvious way to tests this right now except for relying on the compiler guarantees.

@dhruvmanila -- #12494 is ready to land now. I'm going to land it and then push to your branch to fixup the merge conflicts for you, since it feels unfair to do such a huge refactor and then expect you to have to fix the conflicts :-)


Remove enrichment options

This PR finalized simplifying enrichments, removing the enrichment_for and by options in favor of using multiple functions per enrichable message type (introduced in the related PR in core-java).
Notable changes:
Removed options and corresponding classes

enrichment_for and by options and support classes.
EnrichmentMessage is removed. Now any message can serve as an enrichment.  It could be entity state, for example, or standard message type.
EnrichmentType and related query methods were removed..
io.spine.type.enrichment package is removed.
Support for setting enrichment message interface is removed.

Other changes

Removed previously deprecated Logging.supplyFor().
MessageClass got method for querying super interfaces extending Message.
Classes implementing MessageContext no longer need to have a name ending with Context.
Elements of TaskName enumeration were renamed to their Gradle task counterparts.
Gradle-related testing utilities moved under io.spine.tools.gradle.testing package to avoid split-package problem with the main plugin JAR.
Introduced TaskSubject for testing Gradle tasks.

@armiol, @yuri-sergiichuk, PTAL. Most of the changes are removal.
This PR is the basis for this one from core-java.


Filter out known issues

In order to make the logs more usable, we should filter out known error that we can't or won't fix, like for instance:
2020-06-11T09:46:16.760581362Z Message: "/checkouts/github.com-perfectlysoft-perfect-cloudformation: error: package at '/checkouts/github.com-perfectlysoft-perfect-cloudformation' is using Swift tools version 3.1.0 which is no longe
r supported; consider using '// swift-tools-version:5.2' to specify the current tools version"
2020-06-11T09:46:16.760584459Z Output: """ (id: Optional(B93B714E-4415-422C-B5E3-C8BEA912F497))
2020-06-11T09:46:16.760809181Z [ ERROR ] Generic error: getManifests failed: Shell command failed:
2020-06-11T09:46:16.760840731Z command: "swift package dump-package"
2020-06-11T09:46:16.760847713Z path:    "/checkouts/github.com-perfectlysoft-perfect-cloudformation"
2020-06-11T09:46:16.760880268Z message: "ShellOut encountered an error
2020-06-11T09:46:16.760886700Z Status code: 1
2020-06-11T09:46:16.760889754Z Message: "/checkouts/github.com-perfectlysoft-perfect-cloudformation: error: package at '/checkouts/github.com-perfectlysoft-perfect-cloudformation' is using Swift tools version 3.1.0 which is no longe
r supported; consider using '// swift-tools-version:5.2' to specify the current tools version"
2020-06-11T09:46:16.760893153Z Output: """ (id: Optional(B93B714E-4415-422C-B5E3-C8BEA912F497))
2020-06-11T09:46:16.761017951Z [ ERROR ] Generic error: getManifests failed: Shell command failed:
2020-06-11T09:46:16.761030137Z command: "swift package dump-package"
2020-06-11T09:46:16.761249611Z path:    "/checkouts/github.com-perfectlysoft-perfect-cloudformation"
2020-06-11T09:46:16.761279478Z message: "ShellOut encountered an error
2020-06-11T09:46:16.761284049Z Status code: 1
2020-06-11T09:46:16.761455601Z Message: "/checkouts/github.com-perfectlysoft-perfect-cloudformation: error: package at '/checkouts/github.com-perfectlysoft-perfect-cloudformation' is using Swift tools version 3.1.0 which is no longe
r supported; consider using '// swift-tools-version:5.2' to specify the current tools version"
2020-06-11T09:46:16.761573502Z Output: """ (id: Optional(B93B714E-4415-422C-B5E3-C8BEA912F497))
2020-06-11T09:46:18.102000448Z [ ERROR ] analysis error: Shell command failed:

These are happening a lot and will never go away.

Another candidate:
2020-06-11T09:58:53.427685736Z Message: "fatal: could not read Username for 'https://github.com': No such device or address"

Actually, that one we want to fix by removing the package with the private repo (https://github.com/SwiftyBeaver/AES256CBC.git, it's been failing forever)

See https://github.com/daveverwer/SwiftPMLibrary/pull/345

Another candidate:
2020-06-11T09:58:53.427685736Z Message: "fatal: could not read Username for 'https://github.com': No such device or address"

Yep, this one is valid and the correct fix for it is to remove the repo if it continues to happen.


Failure to compile: recipe for target 'all' failed

I've followed all ur steps, typed "make", it processed well at first, but then i ran into this error:
[ 32%] Linking CXX executable airwave-host-64
winebuild: gcc-4.7 failed with status 1
winegcc: winebuild failed
src/host/CMakeFiles/airwave-host-64.dir/build.make:250: recipe for target 'src/host/airwave-host-64' failed
make[2]: *** [src/host/airwave-host-64] Error 2
CMakeFiles/Makefile2:142: recipe for target 'src/host/CMakeFiles/airwave-host-64.dir/all' failed
make[1]: *** [src/host/CMakeFiles/airwave-host-64.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2

I'm running a 64bit ubuntu-gnome OS...plz help! Thanks in advance!

Anyone here possibly help?

Is this all error messages? I see only the fact that build was failed, but no description of any reason. Do you have all 32-bit and 64-bit dependencies installed? Do you use multilib gcc (the one, which can generate machine code for both 32/64 bit architectures)? Do you have "development" versions of dependency packages installed?
What Linux distribution do you use, by the way? You can download pre-built package for Ubuntu from here: https://github.com/phantom-code/airwave/releases/tag/1.3.3

Thanks i didn't realize theres binary packages...i'll try them out

It worked! Pretty well so far :-)
Thanks dude!

...Despite the fact that some characters coudn't be displayed correctly...or sometimes couldn't be displayed at all; and it usually happens with dropdown menus--which seems like a font issue. I can still see the functionality of that particular controll by...well...clicking on it, but it'd be so nice if i could just see the text and have an idea of what i am doing.

There are ton of different VST plugins, also some of them require additional packages to be installed (in your case it may be gdiplus or even some fonts). And some plugins don't work at all (because of wine).

I figured out that after i copied all fonts from my windows partition to ~/.wine/drive_c/windows/Fonts the vsts can display texts again!
All problems solved thx dude~


jest error

$ jest packages/reactivity/tests/reactive.spec.ts
FAIL packages/reactivity/tests/reactive.spec.ts
● Test suite failed to run
TypeScript diagnostics (customize using `[jest-config].globals.ts-jest.diagnostics` option):
packages/compiler-core/src/codegen.ts:285:36 - error TS2339: Property 'toJSON' does not exist on type 'Source                                 MapGenerator'.

285     map: context.map ? context.map.toJSON() : undefined
                                       ~~~~~~

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        14.909s
Ran all test suites matching /packages\reactivity\tests\reactive.spec.ts/i.

Please DO NOT abuse pull requests. It's not for bug reports.
And, make sure to have a look at https://github.com/vuejs/vue-next/blob/master/.github/contributing.md first.

@xiake-1024 Please try : lerna changed


BC SaaS Sandbox deleting itself

I am trying to create a new sandbox in BC saas, but it keeps deleting itself. Had the same issue earlier, and it resolved itself, but now the problem is back. What is causing this?

Let's get the issue to a team who will fix and backport it, as this repository is only for issues related to the latest developer preview environment for Dynamics 365 Business Central. We suggest that you open a support case or file a bug in Collaborate, to ensure that all Business Central users benefit from your catch as soon as possible.
To open a support case, you can:

Open a support request to CSS through the PartnerSource portal
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company

If you file the bug in Collaborate, remember to include steps to reproduce the issue, and the Business Central build number and country version you're using.


Hotfix for broken docs link

What does this PR (Pull Request) do?

[x] This PR is not related to any Issue

This is a backport of the fix from #4220
Which Traffic Control components are affected by this PR?

Documentation

What is the best way to verify this PR?
Build the docs, observe no warnings or errors
If this is a bug fix, what versions of Traffic Control are affected?
See #4220
The following criteria are ALL met by this PR

[x] Tests are unnecessary
[x] This PR includes documentation
[x] An update to CHANGELOG.md is not necessary
[x] This PR includes any and all required license headers
[x] This PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4961/

Backport PRs should only be opened after the corresponding PR has been reviewed and merged into master, after which the commit should be cherry-picked using the -x option to include the git hash of the corresponding commit on the master branch. When you cherry-pick a PR before it's been merged, the commit hash references the commit in your PR branch which can be lost.
That said, I don't see this as a blocker for the 4.0 release, but if I have to cut a new RC for a different major issue anyway, I'll consider including this docs fix in the next RC.


Reading tar file

jenkins test please

cmake and misc fail can be ignored - submodule uzlib should be added (ignore binary file warning)

jenkins test please


Bug: emit of shorthand property is wrong with non-ES6 ModuleKind

TypeScript Version:
1.8.7 / nightly (1.9.0-dev.20160217)
I believe there is a logical error in emitShorthandPropertyAssignment in emitter.ts. When determining whether to emit a : name after a shorthand property, the code checks what the current ModuleKind is rather than what ScriptTarget we have.
I believe the following change is required
// A self-contained demonstration of the problem follows...
function emitShorthandPropertyAssignment(node: ShorthandPropertyAssignment) {
    // The name property of a short-hand property assignment is considered an expression position, so here
    // we manually emit the identifier to avoid rewriting.
    writeTextOfNode(currentText, node.name);
    // If emitting pre-ES6 code, or if the name requires rewriting when resolved as an expression identifier,
    // we emit a normal property assignment. For example:
    //   module m {
    //       export let y;
    //   }
    //   module m {
    //       let obj = { y };
    //   }
    // Here we need to emit obj = { y : m.y } regardless of the output target.
-    if (modulekind !== ModuleKind.ES6 || isNamespaceExportReference(node.name)) {
+    if (languageVersion < ScriptTarget.ES6 || isNamespaceExportReference(node.name)) {
        // Emit identifier as an identifier
        write(": ");
        emit(node.name);
    }

    if (languageVersion >= ScriptTarget.ES6 && node.objectAssignmentInitializer) {
        write(" = ");
        emit(node.objectAssignmentInitializer);
    }
}

For example, when transpiling this with tsc --module commonjs --target es6
export const foo = { a, b };

Expected behavior:
"use strict";
exports.foo = { a, b };

Actual behavior:
"use strict";
exports.foo = { a: a, b: b };

The same example with tsc --module amd --target es6
Expected behavior:
define(["require", "exports"], function (require, exports) {
    "use strict";
    exports.foo = { a, b };
});

Actual behavior:
define(["require", "exports"], function (require, exports) {
    "use strict";
    exports.foo = { a: a, b: b };
});

Specifically, I'm encountering this issue when using transpileModule with ModuleKind.ES6 and SourceTarget.ES5. The suggested change should address both use-cases.
Expected behavior:
export var foo = { a: a, b: b };

Actual behavior:
export var foo = { a, b };

I've tried to implement the changes, but I haven't been able to update the baseline tests successfully. I don't get any clear indication of why they're failing, nor can I try using transpileModule manually to verify that it works.
Debug Failure. False expression: Output generation failed
Error: Debug Failure. False expression: Output generation failed
    at Object.assert (/Users/oskar/github/typescript/built/local/typescript.js:1612:23)
    at Object.transpileModule (/Users/oskar/github/typescript/built/local/typescript.js:45683:18)
    ...

I'll extend the necessary changes to this:
-    if (modulekind !== ModuleKind.ES6 || isNamespaceExportReference(node.name)) {
+    if (languageVersion < ScriptTarget.ES6 || (modulekind === ModuleKind.ES6 && isNamespaceExportReference(node.name))) {

We ought to verify that modulekind is ES6 before checking whether the name is a namespace export reference.

i do not see the same error. making the change and running all tests for me produce one change in baselines in tests/baselines/reference/shorthandPropertyAssignmentInES6Module.js which is actually the correct output. how can i get the error you are seeing?

@mhegazy Sorry about the confusing comment. I encountered the Debug Failure when I tried to use the locally generated typescript.js programatically. But never mind that.
Yes, I get the same error as you do. The baseline fails. I'd submit a PR for this myself, but I just don't know how to update/add new tests for this.

thanks @Victorystick!


Retrie plugin

It seems like retrie would make a good plugin. TODO, figure out exactly what functionality would be appropriate to expose.
Perhaps this would be better placed in the https://github.com/haskell/haskell-language-server, I assume there'll be some issue migration at some point?

Looks really good. I guess the new plugins would be added directly to hls, once it has the base work to to do it: https://github.com/haskell/haskell-language-server/pull/45

The plugin support landed via that PR, it is now in master.  The concept is very similar to that in hie, but the process of getting information from GHC is slightly different. But you can see how it works from e.g. the ormolu plugin, which uses the GHC AST


support for @testing-library/react with Select

I am having trouble triggering the onChange or setValues when dispatching a change event when using a Select.  Would you be able to provide an example for this?  I have a suspicion this might be a bug.
Here is what I have been trying:
fireEvent.change(container.querySelector('input[name="phoneNumber"]'), { target: { value: "18005551234" } });

This works for basic fields like TextField but I think some of the onChange shims might be interfering the dispatched change event for Select.
The values prop in the Formik render scope never updates if the input is from the Select, however immediately updates if it's a TextField.

in tests i typically mock all material ui components. do you have a reason for not doing so here? it is much easier just to replace all material ui inputs with native html  tags. i think you can trust material-ui's internal unit tests to verify that a select input works the way it's supposed to.


Make angular.$apply optional

In order to avoid calling scope.$apply(scope.infiniteScroll); every time, let's add the option to handle it with a parameter.

@miguelangelmunoz ngInfiniteScroll doesn't call $rootScope.$apply

Sorry, scope.$apply(scope.infiniteScroll);

@miguelangelmunoz it already does it in a phase: https://github.com/sroze/ngInfiniteScroll/blob/master/src/infinite-scroll.js#L89-L93

Hi @graingert,
The intention is to have an option to manage when angular digest is executed. This is for performance purposes.
In our application we use this library having tons of bindings so a digest flow can take long. Would be nice to have the possibility to execute digest wherever and whenever we want.
Miguel created a brach adding a new parameter where you can set avoiding the explicit call on $apply().

@danielkocsan have you considered https://material.angularjs.org/latest/api/directive/mdVirtualRepeat

Hi @graingert,
Not yet, it looks like a thing to consider for our further improvements. Thanks for the tip and also for the quick responses.
Currently though, we use this library and we are having performance issues which should be fixed.
Do you think we can apply this change? Could be useful for other users as well and doesn't affect the rest as it defaults to the current behaviour. @miguelangelmunoz has added test coverage too.

@danielkocsan I've not seen anything yet...?

@graingert you can find the Pull Request in the following link:
https://github.com/sroze/ngInfiniteScroll/pull/300

I don't think it's a good idea to expose this sort of interface. I think this should always call $apply().
Also IMHOP ngInfiniteScroll is in permanent feature freeze / maintenance mode and people should be using https://material.angularjs.org/latest/demo/virtualRepeat or waiting for https://github.com/angular/material2/issues/823

It would make sense to explain why do you think things rather then just saying them.

This is because handler is responding to a callback from the dom, like $timeout and $http this must invoke $apply for angular to update the model.

This is not the same case.
The responsibility of this library is just to call the "loadMore" function whenever the user scrolls out of the container.
All managing your items and rendering them is (should be) out of scope.

the loadMore function is passed as a directive callback, all directive callbacks should trigger a digest cycle, eg ngClick

You are safe if you do that but not efficient. That's why there are multiple performance issues reported with Angular 1.x


Oracle Connector without Oracle Client libraries

Update the Oracle connector to work without having to use Oracle Client libraries. Look into Oracle thick and thin.
More info can be found here regarding thin/thick mode.

More info

Table of differences of Thin and Thick mode.

Closing this. Will return to it as and when an Oracle connector becomes a priority.


Windows msys2 $make menuconfig gives Permission denied

Error:
running msys2 build system gives the following error, while attempting to change toolchain executables path
$ make menuconfig
make: ./tools/W806/mconfig.sh: Permission denied
make: *** [tools/W806/rules.mk:141: menuconfig] Error 127
system:
msys2 is running onto windows 11, all necessary packages updated/installed
msys2 (run as admin) did not work

reviewing https://github.com/msys2/msys2.github.io/issues/168 the problem may be due to windows antimalware or antivirus

Please execute ls -l under path wm-sdk-w806/tools/W806/ and post the output content.
I guess the permission of mconfig.sh is incorrect.

Close for no further discussion


Fix non-toplevel imports

The build on https://github.com/tarmstrong/git2json/pull/12 was failing because of problems with updates to flake8. This PR fixes those flake8 style problems.
(Ideally I would just pin the flake8 rules git2json uses but I'm not going to shave that yak right now.)

Coverage remained the same at 74.49% when pulling 41602e6ad282aa8f5fe285121610cc4a0c6ea828 on appease-flake8 into 3ff21f951ca191e480a962eefc3f584f47143b4b on master.


LoadMoreEvent

I am build an app using the CarouselView the I will am displaying current items to the user but they will have the ability to "LoadMore" to see items that have been displayed in the past.  Does your control have this ability or is there plans to allow for this "Chunking \paging " of data.

Hi @4gDad
You can try this plugin https://github.com/AndreiMisiukevich/CardView
If you want to load more items, just add them to your observableCollection

I am going to release small update to support XF 3.x.x and maybe more.

@4gDad next release


Unable to identify Cloudflare IUAM Javascript on website. Cloudflare may have changed their technique, or there may be a bug in the script.

Before creating an issue, first upgrade cfscrape with pip install -U cfscrape and see if you're still experiencing the problem. Please also confirm your Node version (node --version or nodejs --version) is version 10 or higher.
Make sure the website you're having issues with is actually using anti-bot protection by Cloudflare and not a competitor like Imperva Incapsula or Sucuri. And if you're using an anonymizing proxy, a VPN, or Tor, Cloudflare often flags those IPs and may block you or present you with a captcha as a result.
Please confirm the following statements and check the boxes before creating an issue:

[x] I've upgraded cfscrape with pip install -U cfscrape
[x] I'm using Node version 10 or higher
[x] The site protection I'm having issues with is from Cloudflare
[x] I'm not using Tor, a VPN, or an anonymizing proxy

Python version number
Run python --version and paste the output below:
Python 3.10.4

cfscrape version number
Run pip show cfscrape and paste the output below:
Name: cfscrape
Version: 2.1.1
Summary: A simple Python module to bypass Cloudflare's anti-bot page. See https://github.com/Anorov/cloudflare-scrape for more information.
Home-page: https://github.com/Anorov/cloudflare-scrape
Author: Anorov
Author-email<EMAIL_ADDRESS>License: UNKNOWN
Location: c:\users\adrian\documents\tibi\venv\lib\site-packages
Requires: requests
Required-by:

Code snippet involved with the issue
import cfscrape
scraper = cfscrape.create_scraper(delay=10)
print(scraper.get("https://medivia.online/").content)

Complete exception and traceback
(If the problem doesn't involve an exception being raised, leave this blank)

URL of the Cloudflare-protected page
[MEDIVIA]
URL of Pastebin/Gist with HTML source of protected page
[CODE]

CF Scrape is pretty outdated. I recommend using a Chrome Driver.


Remove creating project info

There is enough info in verbose, we shouldn't always be outputting that
a project is being created.

/retest all

/test v4.1-benchmark

/test v4.2-benchmark

/retest

small fix
/lgtm
/approve


Failed loading language 'Armenian' and 'hye'

My tesseract version:
tesseract 3.05.01
 leptonica-1.74.4
  libgif 5.1.4 : libjpeg 8d (libjpeg-turbo 1.5.1) : libpng 1.6.34 : libtiff 4.0.8 : zlib 1.2.11 : libwebp 0.6.0

I have put the Armenian.traineddata and hye.traineddata from this repo in /usr/share/tessdata.
Running the following commands:
$ tesseract whatever.jpg whatever.out -l Armenian
Failed loading language 'Armenian'
Tesseract couldn't load any languages!

$ tesseract whatever.jpg whatever.out -l hye
Failed loading language 'hye'
Tesseract couldn't load any languages!

Tell me if you need any more info to fix this.

Those traineddata files only compatible with version 4.0.

@amitdo Hmm downgraded tesseract to:
tesseract 3.04.01
 leptonica-1.74.4
  libgif 5.1.4 : libjpeg 8d (libjpeg-turbo 1.5.1) : libpng 1.6.34 : libtiff 4.0.8 : zlib 1.2.11 : libwebp 0.6.0

And still getting the same error.
Also how can I build the traineddata files for latest version?

I said version 4.0, not 3.04.01.
3.0x does not have traineddata for Armenian.
To use the traineddata files in this repo, you need the latest code from tesseract master branch.

Yep 4.0 worked for me, though various font recognition for Armenian is far from perfect.


Bug with the Recaller... or the Wither Arena Ritual, maybe both

Please fill out this template when submitting an issue.

Mod Version:0.0.8
Forge Version:<IP_ADDRESS>08
This issue occurs on the lastest version of Forge? (Y/N):Y
Crash Log (Post to Pastebin/Other Text hosting): https://pastebin.com/kPG7meS6
What happens: Use the Recaller in the Overworld. Then do the "Wither Arena Ritual". Defeat the Wither. Instead of using the portal to go back, now use the Recaller to go back. I was told that this is a bug and I should report it.

This is fixed pending the next release


Spark Translation Layer

Hey folks, I'm starting to use the pyspark.ml library and it'd be cool to create a translation layer from pandas to spark to make it easy for local code to easily translate into spark. I have two ideas and would would be great to hear feedback. If positive I'd be happy to create a PR.

Direct translation

spark_df = pandas_df.to_spark(spark_context)

Pseudo translation: only permit spark compatible operations on this DataFrame

restricted_spark_df = pandas_df.restrict_spark()

Would error if any operation that would not work on a spark df were performed on this df. Harder, but potentially useful for seeing if code designed for local use can be used for spark, without even installing spark.

why do you think this should be in pandas rather than PySpark?

@jreback
I did notice that pyspark.sql.createDataFrame accepts a pandas.DataFrame so most of the work is done  but having it linked from pandas might be nice so that it's more discoverable? I guess I don't have terribly strong feelings about the translation layer living in pyspark instead but pandas does link into other DataFrame-like objects with some of the pandas.DataFrame.to_* methods and wouldn't be hard to have a to_spark method.

@danfrankj I am not saying this is hard. But why this should be a good thing to live in pandas. It is already in PySpark. Why does pandas have to know about this? what good is that?

@jreback thinking about it some more, I think you're right. Probably best for this to just live in pyspark. Closing issue. Thanks!


Added checkstyle rules, and made the repo multi modules.

PTAL

Validate checkstyle rules to Cloud Style Guide and 80 character line length.
Add back appengine plugin.

@lesv PTAL

LGTM


terraform plan is not working

Hi,
When I run this terraform module, I got the below error
Error: Invalid function argument
on main.tf line 4, in resource "aws_s3_bucket" "default":
4:   acl           = trim(length(var.grants), 0) == 0 ? var.acl : null
|----------------
| var.grants is null
Invalid value for the "value" parameter: argument must not be null.
Error: Invalid function argument
on main.tf line 88, in resource "aws_s3_bucket" "default":
88:     for_each = trim(length(var.grants), 0) == 0 || trim(length(var.acl), 0) > 0 ? [] : var.grants
|----------------
| var.grants is null
Invalid value for "value" parameter: argument must not be null.

Hi @jatinder10
can you paste your sample code here?
what did you set for acl and grants variable?

Yes, seems like an empty grants. Closing for now. Please comment back and we can reopen if it's a bug


EXSWHTEC-224 - Test cases ID clean up and documentation for Error Handling

Added Doxygen comments for all Test Cases regarding the following Error Handling APIs:

hipGetLastError
hipPeekAtLastError
hipGetErrorName
hipGetErrorString

The goal is to generate HTML pages for Test Plan based on the state of tests source code.

@milos-mozetic
Will you please resolve the merge conflicts for this PR?


Enrich data left menu button

Enriches and creates an insert data query?

Enrich data functionality is achieved by using the query screen


added discord

added discord with a hover effect please assign me gssoc extnd and hactoberfest accepted

@abhi200446 Websites Don't have Discord generally ............. Find another issue or feature to contribute to. Thank you!


Screen reader thinks that karrot is always in English

From foodsharing Poland:

ok, this is a long shot but i think it's worth mentioning: one of our most active users is a blind person and she uses some software that reads to her the web content. what is problematic is that the software detects english as the code language and automatically switches to english even when karrot is in polish. i don't understand exactly how it works and i don't know if that can be fixed at all, so i don't expect you to look into that, but maybe you happen to have an idea what is going on :slightly_smiling_face: after all, we want to make karrot accessible to all people. anyway, there is always somebody to sign up for her so it kinda works in some way...

We maybe need to set the lang attribute dynamically, currently my browser shows it as en-us. I don't know where it is defined, but overriding like this could be worth a try: https://forum.vuejs.org/t/settings-lang-sv-to-the-html-tag/7047

Would it make sense to add a global Navigation Guard to @store/plugins/router.js to set the 'lang' meta attribute based on store.i18n.locale? I could give that a shot.

Hey @mike-ap, welcome!
I'd put the lang set code in our vuex store plugin, as the language changes are unrelated to route transitions.
And we should make sure to check with a screen reader if it really did the trick :)

Great! I've added this functionality to the i18n store plugin and confirmed that this fixes the issue in the case of macOS VoiceOver.
There is a different voice for each language. Without setting the lang tag, VoiceOver will continue using the voice that matches the browser's language. When the tag is set, VoiceOver uses the lang attribute voice. The user was likely hearing the screen reader's English voice executing a (English) phonetic pronunciation of the Polish text.
I extracted this to a function with an eye toward testing, but I'm not sure what would be appropriate. Can you suggest a testing strategy?

Sounds good. From my POV, no testing is needed and you can directly call document.documentElement.setAttribute('lang', locale) from the store plugin.
Ping @nicksellen because he has stronger opinions about testing than me ;)

OK, I've inlined it and pushed in case nicksellen is in agreement.


Menu and add-button

created menu for user for a goal,
changed add-button to core-team functionality

Apart from the duplicate notEmpty statements in core.js and join.js I am ok with this PR :)

[Current coverage][cc-pull] is 68.75%

Merging [#19][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master        #19   diff @@
==========================================
  Files             2          2
  Lines            16         16
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits             11         11
  Misses            5          5
  Partials          0          0

Powered by Codecov. Last updated by [45b1a12...f6ee75c][cc-compare]
[cc-base-branch]: https://codecov.io/gh/feedbackfruits/bepstore-ui-goals/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/feedbackfruits/bepstore-ui-goals/compare/45b1a12515676c9bba21fa839bb0d6a3cf0176f9...f6ee75cd49259483d971f0a78c34655814daafe2
[cc-pull]: https://codecov.io/gh/feedbackfruits/bepstore-ui-goals/pull/19?src=pr

@steffansluis @WouterKvG please review

:+1: :+1:

Does this also fix the white text when adding repos?

@WouterKvG It does fix the whitespace for text-fields & text-areas in goal.sass


AGDIGGER-125 Configure container cap option in K8s plugin

How to verify:
ansible-playbook -i cluster-up-example sample-build-playbook.yml

You might have problems with SSL (if really using local cluster). In that case, either add SSL cert of to Java's trusted certs or modify the java -jar jenkins.cli.jar ... in the playbook to use -noCertificateCheck flag.
You might also have "ERROR: anonymous is missing the Overall/Read permission" error. In that case change your private key with a no-password-protected one temporarily or modify the java -jar jenkins.cli.jar ... in the playbook to use -i <new no-password private key> flag.

@aliok this looks good with one comment I'm unsure about


Fix for Specialist Publisher failing make command

Couldn't run the Make command because of missing updates in the apt-get
library triggering 404 errors. Added an apt-update to make sure it can
grab the needed resources correctly.

am i missing something?

This is because the image automatically does an apt-get clean after any apt-get update. This is evidences by us already having multiple apt-get updates.

Ah ha, great to know thanks for that link too!

Was away for the best part of a week. Sorry for the delay!


Problem Metric Integration

Create an extension of the base APIMetric class for use with problem detection API.

Also remember to add to .yml configuration files.