WordPress Plugin

Would love to see a WordPress plugin. Most WP plugins are either slow or just clunky with bloated code and unnecessary frills. Since page load time is a big concern for websites these days, would be great to have a WP plugin built that has no JS and loads fast without using much resoruces.

Sounds awesome! I think the biggest part of the plugin would be the admin UI. Otherwise it is fairly simple. Should we use the same generator JS as on the site to generate button code or do it with PHP in order to better support for e.g. localization? This is always extra work and I don't know what would be ideal for @mxstbr.
We should support three ways for showing the buttons:

A PHP function for templates, sharingbuttons_io($options).
A shortcode, [sharingbuttons_io option1="foo" option2="bar" ... ]
Admin page, where the buttons can be enabled to be shown above/below the content and for selected post types.

Should we use the same generator JS as on the site to generate button code or do it with PHP in order to better support for e.g. localization?

Could we make the generator JS (and thus the site) better? It seems kind of weird to support two codebases doing almost the same thing :wink:
Otherwise this sounds absolutely amazing, can't wait for this to happen!

I know it is a bit different, but is has the same purpose - No tracking social buttons - https://github.com/privacore/sharebuttons-wp

@mxstbr Okay. How would you think that we could dynamically fill in the URL and the title of the page/post that were on when using JS generator code?

@apkoponen I've honestly never built a WordPress plugin before so I really have no idea :blush: however you want to do this is honestly fine with me!

I was just checking, if you had better ideas than me, because I had a more in depth to the sharingbuttons.io site and realized my initial implementation idea would not work. I initially thought we could just use the JS script to generate the HTML and CSS output, store it to the DB and just input it to the pages. Implementing this would be super easy. However, it would only work if we want to use the same URL and text on every page on the website (which does not seem too useful?).
If we want to support proper localization of the text in the buttons + dynamic URL and text based on the site we're on we can't really utilize much of the application logic from sharingbuttons.io site. We could use the script on the admin site to show the preview of what the buttons would look like and use the HTML and CSS you've done, but otherwise we'd need to implement the display logic (and options storage) in PHP from scratch. This would be not be a lot of work, as the whole app is not too complicated, but I'm not sure if it's worthwhile, as there are 1000+ "share" plugins for WordPress (https://wordpress.org/plugins/search.php?q=share) and very similar plugins already exists (e.g. https://wordpress.org/plugins/dvk-social-sharing/ that I've used previously).
We could, of course, load the JS on every page and give it parameters through PHP using a script tag that outputs global variables, but that pretty much nullifies the whole "no extra JS thing". :)

I'd like to get such a plugin for my website too. Does it matter how the website is created?


docker image pulling failed even if specify geo as CN

I am following the latest instructions to build Apollo by myself. Firstly, I need to run
$APOLLO_HOME/docker/scripts/dev_start.sh
This script can specify the geo parameter, I have specified CN.  During the excution of this script, most of the docker image
are pulled from baidu registry, but there are still some images been pulled from US registry and they all failed. Here is a snippet
of the logging message
[INFO] Start pulling docker image registry.baidubce.com/apolloauto/apollo:data_volume-audio_model-x86_64-latest ...
data_volume-audio_model-x86_64-latest: Pulling from apolloauto/apollo
Digest: sha256:1491b6de2b71bd6bc6326bf70a945da69360e490724df78849f6d70ff4d00f61
Status: Image is up to date for registry.baidubce.com/apolloauto/apollo:data_volume-audio_model-x86_64-latest
registry.baidubce.com/apolloauto/apollo:data_volume-audio_model-x86_64-latest
Unable to find image 'apolloauto/apollo:data_volume-audio_model-x86_64-latest' locally
docker: Error response from daemon: Head "https://registry-1.docker.io/v2/apolloauto/apollo/manifests/data_volume-audio_model-x86_64-latest": Get "https://auth.docker.io/token?scope=repository%3Aapolloauto%2Fapollo%3Apull&service=registry.docker.io": net/http: TLS handshake timeout.
See 'docker run --help'.

OK, I found it is solved if I keep trying several times. It may because the US registry is not stable.


FL Studio Crack <IP_ADDRESS>14 With Serial Key [2025]

FL Studio Crack <IP_ADDRESS>14 With Serial Key [2025]
It is the desktop DAW that music-makers across the world use to turn ideas into reality.


can't build in xcode7.3.1

just like following problem

Can you get me some more details? What device are you trying to build for? What architecture are you using? What version of iOS is your base version / deployment target? The more information you can get me the better.

I believe the last commit should solve your problem. Reopen the issue if it does not

the lastest is usable
and hope to update lastest version to cocoapods.org.
we need this package manager to maintain a available repo version by podfile
thanks:)


Unable to use django-autocomplete-light in forms loaded using a javascript load event

I have a several django forms using dal which are loaded onto the page using a JavaScript load event.  None of the autocomplete light boxes are on the page during initial page load.  These select boxes never get initiated once loaded onto the page.  I followed the instructions for dynamic objects, but the dal-init-function event never gets sent as dal does not appear to load.
Any ideas on how to manually initiate after they are loaded?
I'm using the latest dal 3.8.2 and jQuery 3.x

I'm seeing this too - I'm able to get it working by manually firing .select2(... but I'm having to re-load all the attributes etc.

Had this issue with version 3.8.2.
Upgrading to current master fixed it for me.  Not use where it was fixed.

Released 3.9.0! Does the problem persist for anyone?

This is still broken for me on master
window.dispatchEvent(new Event('load')) fixes it.

Elementary, the DOM watcher code that is in a window.load callback is not executed when the script is loaded after the window.load event which is this case.

We run into the same issue since our form and script is loaded after the window.load event.
The latest version 3.9.4 (and the master) still shows the same behavior.
We used the idea of @davmlaw to fix the form.
if ($("[data-autocomplete-light-function]:not([aria-hidden=true])").length !== 0) {
        window.dispatchEvent(new Event('load'));
    }

Create a custom event that dal also listens for in addition to window load.
Create a global dal (or some other name) object on the window that will accept inputs that need to be initialized. The implementation would probably need to look like if(!window.dal){window.dal = funciton() {window.dal.queue.push(/* inputs to init */)};. The reason is that we can't control which is loaded first.
Make the initialization function

It would be nice to see one of @danielmorell suggestions implemented.

I agree that is definatly a regression.
I can think of a few ways to fix this....

Create a custom event that dal also listens for in addition to window load.
Create a global dal (or some other name) object on the window that will accept inputs that need to be initialized. The implementation would probably need to look like if(!window.dal){window.dal = funciton() {window.dal.queue.push(/* inputs to init */)};. The reason is that we can't control which is loaded first.
Make the initialization function available globally so that it can be called at any time.

I think option 1 is the simplest to add and ship. However, 3 is probably the cleanest for the consumers of the project.
What are your thoughts?

I agree with @danielmorell suggestions. current state of triggering a load event is not nice.


BadRequestException for log groups and GuardDuty

We have tried enabling this module using the below configuration:
data "aws_caller_identity" "current" {}
data "aws_region" "current" {}

module "secure-baseline" {
  source  = "nozaq/secure-baseline/aws"
  version = "0.9.0"

  # insert the 4 required variables here
  audit_log_bucket_name          = "${var.client}.${var.stage}-cloudwatch-logs"
  aws_account_id                 = "${data.aws_caller_identity.current.account_id}"
  region                         = "${data.aws_region.current.name}"
  support_iam_role_principal_arn = "arn:aws:iam::${data.aws_caller_identity.current.account_id}:role/SomethingSomethingAdministrator"
}

Running terraform apply was unsuccessful.
Below is the error messages:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 39236d11-5b8d-11e9-b912-db18f0fda047:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.vpc_baseline_ap-south-1.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 394c2a9a-5b8d-11e9-82f0-079f92f291ce:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.vpc_baseline_us-east-1.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 3927d9c8-5b8d-11e9-82f0-079f92f291ce:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.guardduty_baseline_us-east-1.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 388cd2a0-5b8d-11e9-bcba-f9c17b376a5f
* module.secure-baseline.module.guardduty_baseline_ap-southeast-2.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 39326183-5b8d-11e9-8260-13e36b5f3390
* module.secure-baseline.module.guardduty_baseline_ap-northeast-1.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 3948a815-5b8d-11e9-9ecc-ddb290e7f0c2
* module.secure-baseline.module.vpc_baseline_ap-northeast-1.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 393fa81a-5b8d-11e9-a0f1-b3dd1ae35edf:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.guardduty_baseline_us-east-2.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 38e26bff-5b8d-11e9-a515-737af496302a
* module.secure-baseline.module.vpc_baseline_us-east-2.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 392282d6-5b8d-11e9-b852-5ff5b1767983:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.audit_log_bucket.aws_s3_bucket.access_log: 1 error(s) occurred:
* aws_s3_bucket.access_log: Error creating S3 bucket: BucketAlreadyOwnedByYou: Your previous request to create the named bucket succeeded and you already own it.
    status code: 409, request id: 8665EC6287ABDA3E, host id: 64W3mdLPTgyjx0YjOcV7yUM1JgZzciz3+QGRMSDRynHJ/KFEB+oDdkWZtHcVxda88ACjs7sJMHY=
* module.secure-baseline.module.guardduty_baseline_us-west-2.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 38f2e738-5b8d-11e9-85e3-dbb00e6dba04
* module.secure-baseline.module.guardduty_baseline_ap-southeast-1.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 38d06a98-5b8d-11e9-962a-f7841804025e
* module.secure-baseline.module.guardduty_baseline_ap-northeast-2.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 3922aa05-5b8d-11e9-93fe-af52707faa87
* module.secure-baseline.module.guardduty_baseline_eu-central-1.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 39376a98-5b8d-11e9-af5f-b36cc1cb7a95
* module.secure-baseline.module.guardduty_baseline_ap-south-1.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 394d3ca8-5b8d-11e9-b7b0-8d305d83bc6b
* module.secure-baseline.module.guardduty_baseline_eu-west-3.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 3943ed87-5b8d-11e9-bb7c-f1886c601912
* module.secure-baseline.module.vpc_baseline_ap-southeast-2.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 393287eb-5b8d-11e9-90e6-bd28cc14ba49:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.aws_iam_role.recorder: 1 error(s) occurred:
* aws_iam_role.recorder: Error creating IAM Role Config-Recorder: EntityAlreadyExists: Role with name Config-Recorder already exists.
    status code: 409, request id: 38b716a2-5b8d-11e9-85bf-f1422f566699
* module.secure-baseline.module.vpc_baseline_sa-east-1.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 39245743-5b8d-11e9-95f3-a7b2d1ae7ec7:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.guardduty_baseline_eu-west-1.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 39426730-5b8d-11e9-93fe-af52707faa87
* module.secure-baseline.module.vpc_baseline_us-west-1.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 3931c51e-5b8d-11e9-ac40-a1deac0117ba:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.vpc_baseline_us-west-2.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 3925ddf4-5b8d-11e9-96f5-e7fe73a60eee:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.vpc_baseline_eu-west-2.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 3931501b-5b8d-11e9-b912-db18f0fda047:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.vpc_baseline_eu-north-1.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 39231f1b-5b8d-11e9-b852-5ff5b1767983:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.vpc_baseline_eu-west-1.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 393fa81b-5b8d-11e9-a0f1-b3dd1ae35edf:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.guardduty_baseline_us-west-1.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 388e5915-5b8d-11e9-a3cd-274b24e3c410
* module.secure-baseline.module.vpc_baseline_eu-west-3.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 39465e13-5b8d-11e9-82f0-079f92f291ce:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.vpc_baseline_ap-northeast-2.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 39236d23-5b8d-11e9-a00b-3721a4259847:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.guardduty_baseline_ca-central-1.aws_guardduty_detector.default: 1 error(s) occurred:
* aws_guardduty_detector.default: Creating GuardDuty Detector failed: BadRequestException: The request is rejected because a detector already exists for the current account.
    status code: 400, request id: 391b7d57-5b8d-11e9-8f4d-4f105a9996e8
* module.secure-baseline.module.vpc_baseline_eu-central-1.aws_cloudwatch_log_group.default_vpc_flow_logs: 1 error(s) occurred:
* aws_cloudwatch_log_group.default_vpc_flow_logs: Creating CloudWatch Log Group failed: ResourceAlreadyExistsException: The specified log group already exists
    status code: 400, request id: 39376a86-5b8d-11e9-a0f1-b3dd1ae35edf:  The CloudWatch Log Group 'default-vpc-flow-logs' already exists.
* module.secure-baseline.module.guardduty_baseline_eu-west-2.aws_guardduty_detector.default: 1 error(s) occurred:

We couldn't figure what happened here. Seek your assistance.

Those errors mean that terraform-aws-secure-baseline module tried to create new resources (CloudWatch Log Group and GuardDuty Detector) but your account already had conflicting resources.
You can tell Terraform to refer existing resources instead of creating new ones by importing them into your state file.
The exact instruction to import specific resource type can be found in the terraform document.

Importing aws_guardduty_detector
Importing aws_cloudwatch_log_group

You need to specify GuardDuty Detector ID when importing it, which can be found at AWS Management Console > GuardDuty > Settings > About GuardDuty.
Hope it helps, please let me know if you have further questions :)

@nozaq thanks for your response!
we don't have any resources provisioned related to cloudwatch log groups and guardduty for this account, before we ran terraform apply.
this what boggled us. it's a completely new aws account.

@nazroll Hmm, that's strange 🤔 I'll test with my empty account, let's see if we can reproduce the same errors.

@nazroll
I've run this example with my empty account, and it succeeded.
One thing I noticed was providers are missing in your configuration.
Did you pass providers like this?

@nozaq We did pass in the providers.
module "secure-baseline" {
  source  = "nozaq/secure-baseline/aws"
  version = "0.8.0"

  audit_log_bucket_name          = "${var.audit_s3_bucket_name}"
  aws_account_id                 = "${data.aws_caller_identity.current.account_id}"
  region                         = "${var.region}"
  support_iam_role_principal_arn = "${var.support_iam_role_principal_arn}"

  providers = {
    "aws"                = "aws"
    "aws.ap-northeast-1" = "aws.ap-northeast-1"
    "aws.ap-northeast-2" = "aws.ap-northeast-2"
    "aws.ap-south-1"     = "aws.ap-south-1"
    "aws.ap-southeast-1" = "aws.ap-southeast-1"
    "aws.ap-southeast-2" = "aws.ap-southeast-2"
    "aws.ap-southeast-2" = "aws.ap-southeast-2"
    "aws.ca-central-1"   = "aws.ca-central-1"
    "aws.eu-central-1"   = "aws.eu-central-1"
    "aws.eu-north-1"     = "aws.eu-north-1"
    "aws.eu-west-1"      = "aws.eu-west-1"
    "aws.eu-west-2"      = "aws.eu-west-2"
    "aws.eu-west-3"      = "aws.eu-west-3"
    "aws.sa-east-1"      = "aws.sa-east-1"
    "aws.us-east-1"      = "aws.us-east-1"
    "aws.us-east-2"      = "aws.us-east-2"
    "aws.us-west-1"      = "aws.us-west-1"
    "aws.us-west-2"      = "aws.us-west-2"
  }
}

This is the error message after we ran that plan.
Error: module “secure-baseline”: cannot pass non-existent provider “aws.us-east-1"

Terraform version: 0.11.13
Active AWS region: eu-west-1

@nozaq we figured out what went wrong with our implementation. we did not include the regions.tf file to our implementation. once that was in, it worked pretty darn good.
we love your work and we appreciate you for making this module. thank you!

@nazroll ah, that explains much🤓 feel free to open an issue anytime if you have any comments/feedbacks!


Simplify Spi implementations.

Using objects instead of a hollow class as the "factory" for an Spi makes them being singleton by default, which reduces boilerplate to implement an Spi.
The Dependencies object is not used anywhere and there might be better alternatives which we can decide on once the need of them comes up. For now, the Spi's interfaces are relatively tightly coupled to their current default implementations anyway.

@tysonnorris would you do me the honors?

Looks good - Thanks

does this require any changes to the SPI example doc?


CAUS-2: write CausalImpact shock-based estimator

flake8 didn't like the empty spaces in the file after some of the lines.

Looks good, Ingrid! Ask questions and make comments here, and we can get this thing in there. Try to keep each PR to under 200 lines ... if it's getting longer, we'll merge it in and start a new logical addition.

Hey Ingrid! Just checking in!  lmk if you have any questions, and don't forget to keep your PR up to date, even if it's a total work in progress!

Yeah --- i plan on working on it this weekend! I just havent even started yet.


Double resource load

Sometimes resources are double loaded
Code:

Screenshot:

Hi @ArekZw,
Our apologies for the late reply.
Thank you for the bug report! The script has been updated a lot since your report and the bug has been fixed since 2020.
If you are still using $async, please let us know if the issue is resolved with version 2.0.4.


Reorganize commands and handle datafile

Now we have three top-level commands:

deploy-broker
join
info

Added a commit on top to handle newFromCluster returning an error, which we didn't check

Thanks!!!


create project tab

Would let you know what you need to do and let us know what needs to be done

done.


Kafka scaler not scaling to zero when offset is not properly initialized

Report
How is scaling to zero supposed to work? I'd like to scale to 0 if there is a topic with no messages at all or all consumed so far.
However it always scales to 1.
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: svc-webhook-processor
spec:
  cooldownPeriod: 300
  fallback:
    failureThreshold: 3
    replicas: 6
  idleReplicaCount: 0
  maxReplicaCount: 100
  minReplicaCount: 0
  pollingInterval: 30
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: svc-webhook-processor
  triggers:
  - metadata:
      allowIdleConsumers: "false"
      bootstrapServers: kafka-client.devbox-raffis-1:9092
      consumerGroup: svc-webhook-processor
      lagThreshold: "5"
      offsetResetPolicy: latest
      topic: webhook-request
      version: 1.0.0
    type: kafka
status:
  conditions:
  - message: ScaledObject is defined correctly and is ready for scaling
    reason: ScaledObjectReady
    status: "True"
    type: Ready
  - message: Scaling is performed because triggers are active
    reason: ScalerActive
    status: "True"
    type: Active
  - message: No fallbacks are active on this scaled object
    reason: NoFallbackFound
    status: "False"
    type: Fallback
  externalMetricNames:
  - kafka-webhook-request-svc-webhook-processor
  health:
    kafka-webhook-request-svc-webhook-processor:
      numberOfFailures: 0
      status: Happy
  lastActiveTime: "2021-08-13T09:45:24Z"
  originalReplicaCount: 3
  scaleTargetGVKR:
    group: apps
    kind: Deployment
    resource: deployments
    version: v1
  scaleTargetKind: apps/v1.Deployment

Expected Behavior
Scale deployment to 0.
Actual Behavior
Scaled to 1 replica.
Steps to Reproduce the Problem

Logs from KEDA operator
2021-08-13T09:49:46.505Z	INFO	kafka_scaler	invalid offset found for topic webhook-request in group svc-webhook-processor and partition 0, probably no offset is committed yet
2021-08-13T09:50:17.607Z	INFO	kafka_scaler	invalid offset found for topic webhook-request in group svc-webhook-processor and partition 0, probably no offset is committed yet
2021-08-13T09:50:48.211Z	INFO	kafka_scaler	invalid offset found for topic webhook-request in group svc-webhook-processor and partition 0, probably no offset is committed yet
2021-08-13T09:51:19.244Z	INFO	kafka_scaler	invalid offset found for topic webhook-request in group svc-webhook-processor and partition 0, probably no offset is committed yet
2021-08-13T09:51:49.732Z	INFO	kafka_scaler	invalid offset found for topic webhook-request in group svc-webhook-processor and partition 0, probably no offset is committed yet

KEDA Version
2.4.0
Kubernetes Version
1.18
Platform
Amazon Web Services
Scaler Details
Kafka
Anything else?
No response

@raffis seems like the offset is not properly committed in the topic. Please try to fix that on the Kafka side (or try a new topic) and scaling should work.

@raffis seems like the offset is not properly committed in the topic. Please try to fix that on the Kafka side (or try a new topic) and scaling should work.

Yes I am aware of that but I expected that it scales down still since there is no offset yet.

Same problem here. Does anybody solved this?
It is a very common case to start with an oversized topic with let's say 20 partitions so consumer lag for most of those partitions is -1 hence produces this problem but still sum lag for the topic is 0 and not -1 so it is a valid metric.
In this case if you scale the deployment to 0 KEDA Operator will scale it back to 1.

I see, my only concern is that we might break existing behavior if we do this change. I am curious if there could exist a usecase where we would like to keep the current behaviour in this scenario?
@messense @grassiale @matzew @lionelvillard thoughts?

For our use cases, the lag is the only thing that really matters.

What I would expect from KEDA is:

When there are no messages at all, the lag is 0 so scale to minReplicaCount
When there are messages and no committed offset, the lag depends on offsetResetPolicy, in any case, it should scale to at least one max(minReplicaCount, 1)
When there is a committed offset use the consumer group lag, if the lag is 0, scale to minReplicaCount.

Okay after reading through this and reminding myself what offsetResetPolicy really does.
There might people who depend on the existing behaviour, but it's probably an accident if they do.
If people do solely depend on the kafka lag and want to guarantee at least 1 pod to always be available, regardless of lag being 0, then they should be be setting minReplicas=1. They should not be relying on this particular quirk where 0 gets interpreted as a valid metric preventing them from scaling to 0 even if they set minReplicas=0.
@pierDipi has the right idea.

OK cool, anybody willing to implement this for the upcoming release?

I think this should no be closed as the issue is still on going and affecting a big group of users including myself :)

@gcaracuel following PR https://github.com/kedacore/keda/pull/2621 will be included in the next release. It should fix this issue, is there anything you are missing there?


Fix ensure array children

an alternative to #69
@alexpchin  what you think?
Close #72
Close #68
documentation
// add unique key to each child
React.Children.toArray(children)

@PedroBern
I'm liking this. However, this is still saying that there has to be more than one element in children?
Another example where there might only be one child is. potentially, is if someone wanted to use this package to render a header with the snap, or diffClamp but without a TabBar - perhaps a Searchbox ontop of results?  If we allow one child, then they can re-use the same page structure in the app as a page with more than one tab?
I personally have a use-case in my app (which I know is unusual) where there are multiple user types but the most basic only has one tab as they don't have enough content. However, because of the way the profile page is structured (like Instagram), the user's profile image and details are rendered above the tabs?

@PedroBern
I'm liking this. However, this is still saying that there has to be more than one element in children?
Another example where there might only be one child is. potentially, is if someone wanted to use this package to render a header with the snap, or diffClamp but without a TabBar - perhaps a Searchbox ontop of results?  If we allow one child, then they can re-use the same page structure in the app as a page with more than one tab?
I personally have a use-case in my app (which I know is unusual) where there are multiple user types but the most basic only has one tab as they don't have enough content. However, because of the way the profile page is structured (like Instagram), the user's profile image and details are rendered above the tabs?

I'm liking this. However, this is still saying that there has to be more than one element in children?

No, it accepts 1 or more 👍
if (React.Children.count(children) === 0) {
  throw new Error('CollapsibleTabs must have at least one child.')
}

I'm liking this. However, this is still saying that there has to be more than one element in children?

No, it accepts 1 or more 👍
if (React.Children.count(children) === 0) {
  throw new Error('CollapsibleTabs must have at least one child.')
}

Have you run the Default example and commented out the everything apart from Articles? (Or just leave any other one).

On 30 Jan 2021, at 20:45, pedrobern<EMAIL_ADDRESS>wrote:

I'm liking this. However, this is still saying that there has to be more than one element in children?
No, it accepts 1 or more 👍
if (React.Children.count(children) === 0) {
throw new Error('CollapsibleTabs must have at least one child.')
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

Have you run the Default example and commented out the everything apart from Articles? (Or just leave any other one).

On 30 Jan 2021, at 20:45, pedrobern<EMAIL_ADDRESS>wrote:

I'm liking this. However, this is still saying that there has to be more than one element in children?
No, it accepts 1 or more 👍
if (React.Children.count(children) === 0) {
throw new Error('CollapsibleTabs must have at least one child.')
}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

yes you are right, it throws an error with only 1 child! I will investigate now

yes you are right, it throws an error with only 1 child! I will investigate now

@alexpchin now it's working the problem was with the indicator component.

@alexpchin now it's working the problem was with the indicator component.

I've just pulled the latest version. However, I currrently see:

With the type error being:
(property) Container: React.FC<CollapsibleProps<TabNames, MaterialTabBarProps<TabNames>>>
This JSX tag's 'children' prop expects type 'ReactElement<any, string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<any, any, any>)>[] | ... 6 more ... | (ReactElement<...>[] & ReactPortal)' which requires multiple children, but only a single child was provided.ts(2745)

And:

Is it working for you?

I've just pulled the latest version. However, I currrently see:

With the type error being:
(property) Container: React.FC<CollapsibleProps<TabNames, MaterialTabBarProps<TabNames>>>
This JSX tag's 'children' prop expects type 'ReactElement<any, string | ((props: any) => ReactElement<any, string | ... | (new (props: any) => Component<any, any, any>)> | null) | (new (props: any) => Component<any, any, any>)>[] | ... 6 more ... | (ReactElement<...>[] & ReactPortal)' which requires multiple children, but only a single child was provided.ts(2745)

And:

Is it working for you?

here is working, but there is this typescript error, I will fix now

here is working, but there is this typescript error, I will fix now

I was having this error before, maybe you are not with the latest version, I rebased and forced push

I was having this error before, maybe you are not with the latest version, I rebased and forced push

@alexpchin just rebased and for push again

@alexpchin just rebased and for push again

I merged, if you see any errors, let me know

I merged, if you see any errors, let me know


Update textwindow.css

change the width for a better reading ~70-80 letters each line / holding the propotion by changing the fontsize

Fun stuff!


[Merge] 'phosphoribosylpyrophosphate synthetase deficiency'

Mondo term (ID and Label)
MONDO:0043176 'phosphoribosylpyrophosphate synthetase deficiency'
Reason for deprecation
Duplicate
Term to be merged with
MONDO:0010395 'phosphoribosylpyrophosphate synthetase superactivity'
@galyea-gard
I think these two terms in Mondo are the same, not sure why the 'deficiency' term was create as a distinct entity from the 'superactivity' term. I added hyperlinks to OLS so you can easily see them.
Thanks!

Phosphoribosylpyrophosphate synthetase deficiency:  They are two different disorders; In GARD we currently have the phosphoribosylpyrophosphate synthetase superactivity (we had  phophoribosylpyrophosphate synthetase deficiency as a synonym but I fixed this issue). Missense mutations in PRPS1 are rare and may result in increase or decrease in PRS-I activity (PRS-I deficiency is VERY rare (only 12 families described) and includes  Arts syndrome (GARD 8756), X-linked Charcot-Marie Tooth 5 (OMIM 311070 – we only have the parent term for this one ), and X-linked non-syndromic sensorineural deafness (OMIM 304500 – we don’t have this on GARD).  Thank you! Gioconda

Thank you @galyea-gard, I'll close this.


Basic support for static constexpr variables

Fixes #1421

Not sure why InternalsVisibleTo in  linux / mono doesn't work. I'll check it tomorrow.

This looks nice.
The CI issue seems related to the parser bindings, you only updated the generated C++/CLI bindings, which are only used on Windows, on other platforms generated C# code is used.
They need to be re-generated for all platforms by running https://github.com/mono/CppSharp/blob/master/src/CppParser/ParserGen/ParserGen.cs. You can generate them all from Windows, but you need a folder with the header files for all platforms.
@ddobrev Can you upload those to our releases page on Github?

@tritao it was loooong due...
@josetr please get the headers here and unpack them in build (so that you have build/headers/...), then rerun the generator for the parser.

I just generated the bindings and I've realized that they were already outdated with #1429

Thank you, @josetr . An outstanding feature.
We had actually noted it years ago but I think you extended it even further. At the bottom, though, I can see a note that could've simplified your work. I apologize for not linking it earlier. Still, you could check it if you like.
To my surprise, there's a regression in your code which breaks the build. It wasn't there in your previous commit. I apologize for merging in a hurry instead of waiting to make sure but could you please send a new PR to fix this?

@ddobrev Anytime 👍 . To be honest I was looking into using CppSharp in a personal project that requires high performance and some of the pull requests like this one were really needed for me.
I actually realized my mistake very fast but you were too quick at merging it 😄

It's all right now. :) Let me ask you: do you intend to send further improvements? We're considering a release to update our NuGet which has stalled for a few months now. However, we'd rather wait to include anything else you might have.

@ddobrev I have made pull requests for nearly everything I had in my local repo except 3 that are probably a bit incomplete like supporting string_view, copying arrays using System.Buffer.MemoryCopy rather than using a loop and fixing const wchar_t* marshalling.

OK, we won't release today. If there's nothing new from you in a day or two, we'll release. If you send sth later, we'll have it in the subsequent release.


dart2js keep function or class

@pragma('dart2js:noElision') is just working for keep unused fields or unused parameters ,I want to keep a function or class, what should I do

i wantI want to keep some specific functions even though they are not used, so I would like to know if there is any solution @rakudrama

There is no way to declare that a function or class should be retained by dart2js.
Please could you describe what you are trying to do? If we understand what you want to do we can perhaps suggest a solution for your need.


./gdrive: No such file or directory

I have extracted gdrive_2.1.1_linux_amd64.tar.gz on my ubuntu 20.04 but when I try to run gdrive with executable permissions I get this error.

You can use i386 binary instead amd64. It works fine for me.
wget -q -O /tmp/gdrive.tar.gz "https://github.com/prasmussen/gdrive/releases/download/2.1.1/gdrive_2.1.1_linux_386.tar.gz"
mkdir /tmp/gdrive && tar -xf /tmp/gdrive.tar.gz -C /tmp/gdrive
chmod +x /tmp/gdrive/gdrive
/tmp/gdrive/gdrive download 1o1qjRgkJtnF_8uGB1z6MRsQUjWinHUsw --recursive --path ~/Downloads

(Possible reason) The doc say this program is statically linked, which is false on amd64 build . It depends on... musl, and not glibc, which is the default on many linux distro (including ubuntu, arch, etc...). Use the i386 build which is statically linked.

I confirm that it needs musl, I had the same problem with Arch Linux

strings gdrive |egrep "[.]so$|[.]so[.]1"
yep: sudo apt install musl
strace gdrive help didnt help, but I think there is some command that let we see the dependencies other than force it thru strings

ldd  is the command you are looking for I think.

i spent near one hour to find this problem.
all those workaround always tell me to "chmod +x gdrive", which leads to nothing.
THIS confirm my sanity, that indeed it's a real bug.
@ma3yta yes, thank you i386 binary works just fine. I temporarily using this, any downside compared to amd64?

@marhensa no downsides. the program just uses 32-bit (i386) CPU instructions instead of 64-bit (amd64) instructions which is OK for x86_64 processors.

I think we should keep the issue open, until readme atleast mentions this.

I have the same issue on 2.1.1

same issue

same issue

root@localhost:~# gdrive about
-bash: /usr/local/bin/gdrive: No such file or directory
root@localhost:~# ldd gdrive
ldd: ./gdrive: No such file or directory
root@localhost:~# ldd /usr/local/bin/gdrive
	linux-vdso.so.1 (0x00007ffcaacbe000)
	libc.musl-x86_64.so.1 => not found
root@localhost:~#
root@localhost:~# apt install -y musl
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  musl
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 418 kB of archives.
After this operation, 800 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian bullseye/main amd64 musl amd64 1.2.2-1 [418 kB]
Fetched 418 kB in 0s (2947 kB/s)
Selecting previously unselected package musl:amd64.
(Reading database ... 30457 files and directories currently installed.)
Preparing to unpack .../musl_1.2.2-1_amd64.deb ...
Unpacking musl:amd64 (1.2.2-1) ...
Setting up musl:amd64 (1.2.2-1) ...
Processing triggers for man-db (2.9.4-2) ...
root@localhost:~#
root@localhost:~#
root@localhost:~# gdrive about
Authentication needed
Go to the following url in your browser:

Confirm same issue, on a Linux 3.10 compute cluster. Musl didn't fix, using i386 seems fine.

Confirm same issue on Ubuntu x86_64 machine Linux 5.15.0-46-generic
Installing musl (via apt install musl) fixed the issue


Czml properties changed as fillcolor

#5705 changed the example to reference to the fill color instead of outlineColor

@esraerik thanks for the pull request!
I noticed that CHANGES.md has not been updated. If this change updates the Cesium API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and bump this pull request so we know it was updated. For more info, see the Pull Request Guidelines.
I am a bot who helps you make Cesium awesome! Thanks again.

@ggetz can you review this?  I updated the example

@hpinkos Just that one comment


object created with ph.createOutObject() crashing when asked for a property

Expected behavior
_outObj.property("urls") returns the property I asssigned
Actual behavior
_outObj.property("urls") returns an error:
Error:

 undefined is not an object (evaluating 'objectSpace[command.target][command.params[0]]')
    at Stream.Phantom.process.stdout.pipe.on.data (...\node_modules\phantom\dist\phantom.js:141:31)
    at Stream.emit (events.js:182:13)
    at drain (...\node_modules\through\index.js:36:16)
    at Stream.stream.queue.stream.push (...\node_modules\through\index.js:45:5)
    at emit (...\node_modules\split\index.js:37:14)
    at next (...\node_modules\split\index.js:49:7)
    at Stream.<anonymous> (...\node_modules\split\index.js:54:5)
    at Stream.stream.write (...\node_modules\through\index.js:26:11)

Steps to reproduce the behavior
Just trying to run the following code:
var _ph, _page, cookie, _outObj, regex = '^http(s)?://(www|ssl)\.google-analytics\.com.*';
  phantom
  .create(['--ignore-ssl-errors=yes', '--load-images=no'])
  .then(ph => {
    console.log("startSubscribe")
    _ph = ph;
    _outObj = _ph.createOutObject();
    _outObj.urls = [];
    return _ph.createPage();
  })
  .then(page => {
    _page = page;

    _page.setting("loadImages",false);
    _page.setting("resourceTimeout",4000);
    console.log("trying on resource")
    _page.on('onResourceRequested',true, function (requestData, networkRequest,_outObj, regex) {
      if (new RegExp(regex, 'ig').test(requestData.url)) {
        request.abort();
        _outObj.urls.push(requestData.url)
      }
    },_outObj, regex);
    _page.on("onConsoleMessage", function () {
                //ignore the trash coming from the page
            });
    _page.on("onError", function () {
      //ignore the trash coming from the page
    });
    _page.on("onAlert", function () {
      //ignore the trash coming from the page
    });
    return _page.open('www.example.com');
  })

  .then( session => {
      console.log(session);
      return _page.property('cookies');
  })
  .then(ck => {
    return _outObj.property('urls');
  })
.then(urls => {
    //do something with the urls
   _page.close();
    _ph.exit();
})
.catch(e => console.log(e));

I know the error is ocurring the index.js property function of the package, where you call this:
 command.response = objectSpace[command.target][command.params[0]];
Environment

OS: Windows
Node version (node -v): 10.1.0
package version:  6.0.3

Yup, I can confirm this is a bug. I was able to reproduce it. :/ So much going on with my other projects. But I'll try to take look at it. I had initially deprecated OutObject so I hadn't really tested this. I think with on and deprecating property this is now broken. Is your use case to just return a list of URLs?

Thanks! It's just that I would like to retrieve the list of urls that i have aborted when they match a certain condition. I'll let you know if I'm able to fix it myself


[Bug]

Hey!
So i have a few bugs to report that are all on iOS devices.
anyway here are the bugs i report in this comment.

Cant install profile
-- The profile of m.eaglercraft.com cannot be installed for some odd reason. I have a iPhone 14 and with the iOS 18 update.

Keyboard on iOS doesnt work after using the chat
--Some servers in the game has to verify user right? Or lets just say you got cheats on, and you want something with the /give command on Mobile, The Keyboard button doesn't work after you type and enter. After you use it, it just thinks the whole page is a text and selects the Arrow keys.

Anyways thats all the bugs i have to say. If you see this by any chance please fix these bugs. Other Mobile players would Love this fix.
If your associated with M.Eaglercraft.com
Please send me the discord link as the link of it is expired.

so like are yall finna fix the profile download for the eaglercraft

Closed due to duplicate issue. Please note that this extension is not developed by the eaglercraft developers. In fact, I was quite surprised to see it being used on the official website.


relativize ~root:"a" "a" gives Some "../a" instead of None

Hello,
I ran into difficulties and unexpected behavior for the Fpath.relativize function.
Here are my assumptions:

the root argument is interpreted as a path to a directory regardless of its directoriness.
the other argument is considered a directory or a file of a more general kind depending on the directoriness of the path.

I would describe relativize ~root p as follows:
Given two paths root and p that are either both absolute paths or both relative paths, relativize ~root p translates the path p into an equivalent path q that is relative to root. In other words, p and q are paths to the same file or directory before and after changing the current directory to root using a command such as Unix.chdir (Fpath.to_string root). Because of this, root is always interpreted as a path to a directory regardless of its directoriness, e.g. a and a/ are both understood as a/. The path p however is interpreted as a directory or not depending on its directoriness. For example, a/ is interpreted as a path to a directory but a is a path to an arbitrary file. This distinction is necessary since the path . can be used to reference directories but not ordinary files. When the above conditions aren't met, relativize ~root p will evaluate to None.

The current implementation and the documentation disagree with some of the above. For the sake of brevity, let's define the shorthand function rel:
let rel root p = Fpath.(relativize ~root:(v root) (v p) |> Option.map to_string)

Incorrect results include:

rel "a" "a": should be None but gives Some "../a"
rel "/a" "/a": should be None but gives Some "../a"

Correct example in the documentation but incorrect implementation:

rel "/a/b" "/a/b" should give None but gives Some "../b".

Incorrect example in the documentation and incorrect implementation:

rel "a/b" "a/b" should give None but the documentation says Some "." and the implementation gives Some "../b".

Summary of requested changes:

a longer description of the relativize function as drafted above.
a fix for the one incorrect example given in the documentation.
a fix for the implementation of the failing cases above.

I'm happy to provide these if you could confirm that the assumptions above are correct.

Ah, I hate relative file system paths with a passion :–)
Maybe it is not the most pleasing result but unless I'm mistaken all the implementation results of your examples match the specification: a relative path q was found such that root // q is equal to p.
And I think this exactly matches your description of:

In other words, p and q are paths to the same file or directory before and after changing the current directory to root using a command such as Unix.chdir (Fpath.to_string root).

Thinking this a bit further I think the only reason why relativize might return None is when root is relative and the path p to relativize is absolute: it's not possible to know how to get to the absolute p from root because you don't know where root is in absolute terms.
Note that in a more recent design of the function I opted in this case to return p rather than None, very much like Fpath.(q // p) returns p if p is absolute.

Maybe it is not the most pleasing result but unless I'm mistaken all the implementation results of your examples match the specification: a relative path q was found such that root // q is equal to p.

In the example where the root is a and the target p is a, we get q = ../a. root // q is then a/../awhich is only valid ifais a directory. Linux indeed disagrees thatREADME.md/../README.mdandREADME.md` are the same:
utop # Unix.stat "README.md";;
- : Unix.stats =
{Unix.st_dev = 66306; st_ino = 47850560; st_kind = Unix.S_REG; st_perm = 436;
 st_nlink = 1; st_uid = 1000; st_gid = 1000; st_rdev = 0; st_size = 6112;
 st_atime =<PHONE_NUMBER>.13635707; st_mtime =<PHONE_NUMBER>.1628015;
 st_ctime =<PHONE_NUMBER>.1628015}

utop # Unix.stat "README.md/../README.md";;
Exception: Unix.Unix_error(Unix.ENOTDIR, "stat", "README.md/../README.md")

which is only valid if a is a directory.

Yes the function expects root to be a directory. I mean applying Fpath.(root // q) makes no sense if root is not a directory. The library being file system independent it cannot check that.

which is only valid if a is a directory.

Yes the function expects root to be a directory. I mean applying Fpath.(root // q) makes no sense if root is not a directory. The library being file system independent it cannot check that.

The directoriness of p could be used for that. I understand if this is too tricky to check but can you please clarify things in the documentation, add the missing test cases, and fix the incorrect example (relativize ~root:(v "a/b") (v "a/b") is Some (v "."))?

The directoriness of p could be used for that.

It's not that it's tricky but rather in general I don't think it's a good idea to rely on syntactic directoryness. For example I find rsync's subtelties w.r.t. directoryness unusable, each time I write an rsync invocation I have to look it up again (or don't and screw my sync).
You want your users to be able to write directories with or without the final / regardless and things to work (like in Fpath.append). If we start relying on directoryness I can already see people adding Fpath.to_dir_path to get a proper root so that users don't have to care, so we just pushed the same problem one step away: you really need to consult the file system to see if it's applicable.

You want your users to be able to write directories with or without the final / regardless and things to work (like in Fpath.append).

I agree with this goal.
I find reasoning about paths much harder than it looks, resulting in many mistakes being made. If you can recommend best practices or any guiding principle that would make our lives easier, it will certainly be appreciated by me and by others.
In semgrep, the sort of problems we're dealing with include:

Taking user-specified paths and listing files and folders recursively
... while dereferencing symlinks under certain conditions
... and making sure to preserve the original path specified by the user when returning the path to a discovered file.
Grouping files that share some common root.
Expressing paths relative to a project root.
Going back from the in-project path to a filesystem path.
Doing these things while minimizing file system calls.

... and it's complicated.

Incorrect results include:

rel "a" "a": should be None but gives Some "../a"
rel "/a" "/a": should be None but gives Some "../a"

So while the results were not incorrect I was still annoyed by these. I made a shortcut so that when the paths are equal . or ./ is returned. This makes sense because root is assumed to be a directory.
To show how brittle all that is, that change actually broke the implementation of is_rooted and changed an invariant that held about the function (see the changes in the test suite).
That being said I'm not sure returning either . or ./ according to the directoryness of p makes sense but that's what the function did on some cases and I rather not touch this too much…

... and it's complicated.

Yes the notion of file system path is absolutely horrible and symlinks effectively turn what you think is a tree hierarchy into a graph.
I think this is is the most difficult aspect of your constraints:

... and making sure to preserve the original path specified by the user when returning the path to a discovered file.

If you relax this idea then one thing that works well and that I settled on in my programs (in particular in my build systems)  and never looked back is to internally only work with absolute paths as returned by realpath(3) (which you can find in the Unix module nowadays).  Everything becomes simpler, e.g. you can easily check if things are in a directory with Fpath.is_prefix or and make the elements of a given directory relative with Fpath.rem_prefix etc. So the first step on any user provided path is to realpath it.
If you need to output paths for the users you can either output absolute paths – which is often anyway clearer (e.g. for jump to error in editors and users can't keep track of the cwd each of their windows operate in) or relativize them according to a root with Fpath.relativize if outputs become too noisy (possibly only activated via a dedicated --relative-to option for clarity).
IIRC it may end up disagree with a user's shell state because the shell maintains an illusion when you cd to a symlink and then cd ... But it will always be correct from a file system point of view (i.e. for system calls).
I never felt the need for it or thought a lot about it but it's likely that this approach can be improved for rendering the UI in order to respect symlink specifications by manipulating a tuple:
type ui_path =
{ user : Fpath.t; (** as specified by user, may have symlinks *)
  real : Fpath.t (** realpath of [user] *) }

let render_relative ~to_dir:(p : ui_path) (p : Fpath.t (* realpathed *)) =
  (* … likely a mess *)

Not sure if it's worth the trouble though, start simple and see what becomes really annoying for users.


[v1.0.1-rhel] Backport #375

Required for https://bugzilla.redhat.com/show_bug.cgi?id=2130235

/hold
/lgtm

/lgtm

@mheon I assume we no longer need this and it can be closed now?

Yeah, let's close


Role detecting host (local) java. Deploying to Google Cloud Engine.

The IP is for the gce. The java version is on the host (local).
TASK [ansiblebit.oracle-java : determine if Java is already installed] *********
task path: /etc/ansible/roles/ansiblebit.oracle-java/tasks/check_environment.yml
ok: [<IP_ADDRESS>] => {"changed": false, "cmd": "which java", "delta": "0:00:00.002333", "end": "2017-07-19 18:07:23.761431", "failed": false, "failed_when_result": false, "rc": 0, "start": "2017-07-19 18:07:23.759098", "stderr": "", "stderr_lines": [], "stdout": "/usr/bin/java", "stdout_lines": ["/usr/bin/java"]}
TASK [ansiblebit.oracle-java : determine which Java version is installed] ******
task path: /etc/ansible/roles/ansiblebit.oracle-java/tasks/check_environment.yml:21
ok: [<IP_ADDRESS>] => {"changed": false, "cmd": "java -version", "delta": "0:00:00.055572", "end": "2017-07-19 18:07:23.994431", "rc": 0, "start": "2017-07-19 18:07:23.938859", "stderr": "java version "1.8.0_131"\nJava(TM) SE Runtime Environment (build 1.8.0_131-b11)\nJava HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)", "stderr_lines": ["java version "1.8.0_131"", "Java(TM) SE Runtime Environment (build 1.8.0_131-b11)", "Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode)"], "stdout": "", "stdout_lines": []}
What am I doing wrong?

from the log you sent you seem to be communicating to 2 hosts: <IP_ADDRESS> and <IP_ADDRESS>.
On <IP_ADDRESS> you have Java installed at /usr/bin/java.
On <IP_ADDRESS> you already have Java 1.8.0_131-b11 installed.
@svanschalkwyk what is your problem exactly?

No java on either of those. Role is determining that the local has java installed and skips java installation on those servers.

@svanschalkwyk do you have connection: local defined?

I'd check what you have in the inventory, then what are you passing as command-line arguments and finally playbook variables.

It may be some massive misunderstanding on my side.
My inventory contains 35.1... etc.
I'm running ansible-playbook with the -c local flag. When I remove -c local, I get ssh errors.

@svanschalkwyk if you use -c local it will run the whole playbook locally.
if you get ssh errors then that's good; it means you are, at least, trying to connect to the servers.
if you use key authentication be sure you ssh-add the key to access the servers before you run the playbook and check you ~/.ssh/config and see if you got the correct config to access those servers (path to identity file, username, etc).
I'd also double check if you can ssh directly to the servers from the command-line (just to double check it's not the firewall blocking your IP).
I suggest asking for help regarding access to the servers to a work colleague (best), ansible mailing list or stackoverflow.
I'd also say to first run a simple playbook (e.g. one that only contains a task that prints the server IP address / hostname / username or a basic shell command: whoami) to be sure you got everything (connectivity and authentication) right; after that run the playbook with this role.
I'll close the issue since this isn't a problem with the role.
if you use this role, please star it.
thank you!

Thank you for the help! I seem to have a problem with ssh to the servers.
This works: $ssh <IP_ADDRESS> -i ~/.ssh/google_compute_engine
I have it in my ansible_hosts as:
<IP_ADDRESS> ansible_ssh_private_key_file=/home/steph/.ssh/google_compute_engine ansible_user=steph
which fails to connect with this: Failed to connect to the host via ssh: Permission denied (publickey)

@svanschalkwyk I suggest you setup a ~/.ssh/config file.
Something like this:
Host <IP_ADDRESS>
    IdentityFile ~/.ssh/google_compute_engine
    User steph

then try ssh <IP_ADDRESS>. if this config is correct it will work and so will ansible.
if all of this works just change the value for Host to some pattern and keep the same settings.
good luck!

Oh my. Thank you for the help!
I had to add the key to ssh with ssh-add. Then could I ssh into the VM.
However, I am still unable to run the playbook  with
ansible_ssh_private_key_file=/home/steph/.ssh/google_compute_engine``` in
my ansible_hosts file. I have added and removed ssh_user as well.

Oy vey.

*Steph van Schalkwyk*
Principal, Remcam Search Engines
+1.314.452. <+1+314+452+2896>2896<EMAIL_ADDRESS> http://remcam.net
<http://www.remcam.net/> Skype: svanschalkwyk
<https://mail.google.com/mail/u/0/#>
<http://linkedin.com/in/vanschalkwyk>

On Thu, Jul 20, 2017 at 2:40 PM, Pedro Salgado<EMAIL_ADDRESS>wrote:

> @svanschalkwyk <https://github.com/svanschalkwyk> I suggest you setup a
> ~/.ssh/config file.
>
> Something like this:
>
> Host <IP_ADDRESS>
>     IdentityFile ~/.ssh/google_compute_engine
>     User steph
>
> then try ssh <IP_ADDRESS>. if this config is correct it will work and
> so will ansible.
>
> if all of this works just change the value for Host to some pattern and
> keep the same settings.
>
> good luck!
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/ansiblebit/oracle-java/issues/55#issuecomment-316808801>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAMxTKABb9W_tVitMYurj_-6MflIMNFkks5sP61AgaJpZM4OdahV>
> .
>

@svanschalkwyk try running ansible-playbook -vvvv it will give you more output.

Had to specify remote in ansible_hosts as this:
<EMAIL_ADDRESS>The ```ansible_user``` flag is not honoured?

Java is being installed(phew!) but I'm getting this:
``` ____________________________________________________________
/ TASK [ansiblebit.oracle-java : debian | in case there were \
\ changes, check host environment again]                     /
 ------------------------------------------------------------
fatal<EMAIL_ADDRESS>FAILED! => {"failed": true, "reason": "Unable to retrieve file contents\nCould not find or access '/home/steph/Ansible/repos/check_environment.yml'"}

when the file is installed in /home/steph/.ansible/roles/ansiblebit.oracle-java/tasks

Changed tasks/debian/main line 56 to
``- name: debian | in case there were changes, check host environment again
include: "{{ role_path }}/tasks/check_environment.yml"
when: oracle_java_task_apt_install|changed or oracle_java_task_set_default|changed''

check_environment.yml is a local file.
Ansible doesn't work like that.
if you want make a role for that piece of .yml or add it as an include directly to your playbook.

Thank you for the help! I really appreciate your work.
Do you speak Dutch? Love the rocksalt handle.

I don't speak Dutch but I used Dutch, yes. :)
You're the 2nd Dutch that came close to decipher the reason behind my GitHub handle :)
See if you can figure out why...
please star the repo :)

Thanks! Will Sta and think about it as I cycle in a bit.
-----Original Message-----
From: "Pedro Salgado"<EMAIL_ADDRESS>Sent: 20/07/2017 17:04
To: "ansiblebit/oracle-java"<EMAIL_ADDRESS>Cc: "Step van Schalkwyk"<EMAIL_ADDRESS>"Mention"<EMAIL_ADDRESS>Subject: Re: [ansiblebit/oracle-java] Role detecting host (local) java.Deploying to Google Cloud Engine. (#55)
I don't speak Dutch but I used Dutch, yes. :)
You're the 2nd Dutch that came close to decipher the reason behind my GitHub handle :)
See if you can figure out why...
please star the repo :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Ha! I just looked at your last name. I still have some Portugese from my military days: Sal=salt, gado=cattle and having grown up on a farm, I still remember the big blocks of salt they used to lick.
-----Original Message-----
From: "Pedro Salgado"<EMAIL_ADDRESS>Sent: 20/07/2017 17:04
To: "ansiblebit/oracle-java"<EMAIL_ADDRESS>Cc: "Step van Schalkwyk"<EMAIL_ADDRESS>"Mention"<EMAIL_ADDRESS>Subject: Re: [ansiblebit/oracle-java] Role detecting host (local) java.Deploying to Google Cloud Engine. (#55)
I don't speak Dutch but I used Dutch, yes. :)
You're the 2nd Dutch that came close to decipher the reason behind my GitHub handle :)
See if you can figure out why...
please star the repo :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

close. you're on the right track.
note: Salgado is a whole word in Portuguese => Salty or Salted => Salt.
what about Pedro? what is the synonym of Pedro? ;)

Saltpeter? Pedro=son of Peter, Salted Peter = saltpeter. That's all  my overheated brain can come up with :)

Pedro => (name) means Rock or Stone.
Salgado => (name) means Salty or Salted or with Salt (with lots of salt actually).
Pedro Salgado => Rock with lots of Salt => why not Rock Salt (I think the correct name is Halite) -dutch> Steenzout.
There you go. :)
To be honest Google Translator is the one that come up with this weird direct translation; it was 1st one that was cool so I used it. ;)

Ah! I didn't think of the bible reference to Peter... Anyway, good
diversion. Well thought-out! Good night!
Steph van Schalkwyk
Principal, Remcam Search Engines
+1.314.452. <+1+314+452+2896>2896<EMAIL_ADDRESS>http://remcam.net
http://www.remcam.net/ Skype: svanschalkwyk
https://mail.google.com/mail/u/0/#
http://linkedin.com/in/vanschalkwyk
On Thu, Jul 20, 2017 at 9:34 PM, Pedro Salgado<EMAIL_ADDRESS>wrote:

Pedro => (name) means Rock or Stone.
Salgado => (name) means Salty or Salted or with Salt (with lots of salt
actually).
Pedro Salgado => Rock with lots of Salt => why not Rock Salt (I think the
correct name is Halite) -dutch> Steenzout.
There you go. :)
To be honest Google Translator is the one that come up with this weird
direct translation; it was 1st one that was cool so I used it. ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ansiblebit/oracle-java/issues/55#issuecomment-316885389,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMxTDSB4HUPfrqSGuWurzKsg_ZUqmyjks5sQA42gaJpZM4OdahV
.


When pausing music I get: "Playback Stopped" Pressing Play does nothing.

I'm using Shuttle 2 as my audio player.
Reselecting Shuttle 2 sometimes works but sometimes I get: failed to play please check media queue
Phone is Google Pixel 6 and Smartwatch is Galaxy Watch 5

The processing of audio control commands is implemented by the apps and they provide different quality of support. So I think it's rather a player issue


Tests refactor/cleanup

test_cropped_decoding.py, test_trialwise_decoding.py refactor to use new dataset classes

If this is done can you close @sliwy ?


[Bug]: Release workflow broken

Email (Optional)
No response
Version
v0.8.6
Which OS(es) are you using?

[ ] MacOS
[ ] Windows
[ ] Linux

What happened?
This doesn't look right. Skips the release step even when it shouldn't. You probably wan't if: github.event_name == 'release' && needs.tests.result == 'success'.
https://github.com/materialsvirtuallab/matgl/blob/d9f266523983fdea0baeacc16dece83f447e5a14/.github/workflows/testing.yml#L51
Hence https://github.com/materialsvirtuallab/matgl/releases/tag/v0.8.6 didn't make it to PyPI.
Code snippet
No response
Log output
No response
Code of Conduct

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

I am unclear of the bug. This runs the release porition only when the event is release and needs: test already specifies that it should run only when the tests pass. What is the bug?

github.event.name doesn't exist. It's github.event_name.


build(behavior_path_avoidance_by_lane_change_module): prefix package and namespace with autoware_

Description

This PR adds the autoware_ prefix to the package and puts headers in the autoware namespace.
Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@xmfcx @mitsudome-r @rej55 @satoshi-ota @shmpwk @TomohitoAndo @tkimura4 @zulfaqar-azmi-t4
This is now ready for review, please have a look at it when you have a moment. Thanks.

I've reverted any performance or any other improvements detected by clang-tidy, the CI will now fail because of the clang-tidy check, but now the PR only conntains the prefix changes.

Back to draft because I'm going to rename folders and move headers to a separate folder (see https://github.com/autowarefoundation/autoware/issues/4569#issuecomment-2097690750)

@xmfcx this PR is ready for review again.

Hi @esteve . I missed your PR and created https://github.com/autowarefoundation/autoware.universe/pull/7309 accidentally. Could you fix build fail? After that, I'll approve your PR.

@satoshi-ota done, I've fixed all the build issues. I've also moved the header to src so they are not exported (there are no downstream packages that depend on this package), and put all the code in the autoware:: namespace


HostFragments all have the same DoveCote name, so all react to Pigeons

@dmfs Push was rejected, but the quick fix I did was to replace this:
"wizardhost"

with this
"wizardhost_" + hashCode()

in HostFragment onCreate() for the DoveCote id. Not sure if this is the best solution, but it worked in ED SDK where I tried.


Name change

Babili has been renamed to babel-minify - Ref: https://github.com/babel/minify/issues/124 ..

[x] Change this project to babel-minify-webpack-plugin.
[x] Update Travis service
[x] Update Appveyor service
[x] Update Codecov.io service
[ ] Publish on npm with new name - after babel-minify is published. I already have the name on npm.

I'll take care of this shortly

The standard group needs to be given owner access to the new pacakge. i.e @bebraw & @d3viant0ne

npm access rights: Done

Defaults is finished & in master ( seemed a good time to finish given this will be a new major version anyway ).
Given you are far more in the know as to when this is going to be published on the babel side, fire off a new release at your leisure.

need to update readme as well

<EMAIL_ADDRESS>has been published.


revert(ci): e2e timeout 15 -> 17

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
CI e2e timeout was bumped from 15m to 17m in #12858, on suspicion that there was perf regression #12825. It ran consistently slower (batch taking 8m50s) during 2023-10-20T15:06Z - 2023-10-21T07:27Z but came back to 7m30s after that.
https://buildkite.com/risingwavelabs/pull-request/builds/33837
https://buildkite.com/risingwavelabs/pull-request/builds/33835
https://buildkite.com/risingwavelabs/pull-request/builds/33834
Ideally there should be no such ci performance fluctuation. Still no clue what happend.
At the same time started an attempt to reduce test time #12984

Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

8m40s again 😂

It seems there has been fluctuation for a while, but it's not clear what's wrong. 😟 Maybe we need more fine-grained monitoring for CI to know regression better.


How to use this Plugin? I am new to this!

I have downloaded this package. How to use this?

please have a look at the instructions in the readme and let me know if there's anything missing

I my case plugin should be in *.hpi format. How to get that?

this is the source code. you'll have to build the plugin in order to use it with jenkins. First, you need to set up your build environment, and then build the plugin.


Release | Release version 0.2.1

[0.2.1] - 2023-08-17
Changed

Fixed errors in the README of the crate.
Control characters will now be removed from JSON keys, as per the strict JSON requirements.
Formatted the code using standard RustFMT.

Close PR due to fix being done on old version.


Can't open Sanddance, no Data tab in Explorer

The Data tab in Explorer is missing, right click on the open file in the Open Editors tab doesnt show the option to open Sanddance.
Any ideas to fix this?

Hello, can you add a screenshot of your issue? I'm guessing you mean in VSCode...

Hi Dan,
You’re correct, I mean VSCode.
According to the video that’s shown when I select the SandDance extension in VSCode, I have to right click on the open file in the Data section of Explorer, and select ‘View in SandDance’.
As you can see from the screenshot below, I don’t have that Data section, and right clicking on the file in the Open Editors section doesn’t give me the option to view in SandDance.
<EMAIL_ADDRESS>Any help would be welcome.
Best regards,
Arthur
From: Dan Marshall<EMAIL_ADDRESS>Sent: Wednesday, August 5, 2020 7:28 PM
To: microsoft/SandDance<EMAIL_ADDRESS>Cc: Arthur<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/SandDance] Can't open Sanddance, no Data tab in Explorer (#266)
Hello, can you add a screenshot of your issue? I'm guessing you mean in VSCode...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/SandDance/issues/266#issuecomment-669325485, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEVZUNHATR45XOJA3XARVTLR7GJCTANCNFSM4PVSHKYQ.

Hi Dan,
I found out I can invoke SandDance by right clicking on the tab label instead of on the file name, so everythings works now.
Great extension, thanks for the good work!
Best regards,
Arthur
From: Dan Marshall<EMAIL_ADDRESS>Sent: Wednesday, August 5, 2020 7:28 PM
To: microsoft/SandDance<EMAIL_ADDRESS>Cc: Arthur<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/SandDance] Can't open Sanddance, no Data tab in Explorer (#266)
Hello, can you add a screenshot of your issue? I'm guessing you mean in VSCode...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/SandDance/issues/266#issuecomment-669325485, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEVZUNHATR45XOJA3XARVTLR7GJCTANCNFSM4PVSHKYQ.


clerification about sql server 2005 Database

Orchard-1.9.1 works on SQL server 2005 Database ?

Please ask questions on the forum, not as issues. Thanks!


Write down "unit" as the default unit type

When a request is made and the Partner selects the default "unit" custom-unit, go ahead and write down "unit" as the custom-unit instead of empty-string.

I'm going to close this until it is more obviously a good idea!


Fix rector

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
-

Action should ued pull_request_target for allow commits.

Done


chore(tasks): remove dummy comment

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2784  👈
#2783
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @overlookmotel and the rest of your teammates on  Graphite


Convert backslashes to slashes

Fix for Windows path separator "". When generating URLs to i.e. Github these backslashes must be converted to slashes.

I've moved replace to another place. Thanks for your help.


perform escaping for comments & PIs in ceylon.html

Comments (and PIs) are currently not escaped:
    void visitComment(Comment node) {
        flush();
        write("<!-- `` node.data `` -->"); // escape?
    }

which is actually a security vulnerability, since it's quite possible node.data will be untrusted user data.

The spec states that the text within <!-- and --> must not:

start with a single ">" (U+003E) character, nor
start with a U+002D HYPHEN-MINUS character (-) followed by a ">" (U+003E) character, nor
contain two consecutive U+002D HYPHEN-MINUS characters (--), nor
end with a U+002D HYPHEN-MINUS character (-)

The correct approach would probably be to throw if any of these rules are violated. But that may be inconvenient and surprising.
I wonder what XSLT does.


ARIA: Add results for Edge

@halindrome Because test results don't require review, and because we need these in place in order for the CfC to go out, I've gone ahead and merged them in.


ipv6 support

ipv4 is going to die. Let's support ipv6

I'd say support ipv6 even if ipv4 doesnt die

I agree this would be pretty neat

IPv6 works.
Just start server with arguments like ./code-server -h :: -p 8080 -H -P password
Where is :: is like <IP_ADDRESS> but for IPv6.
Now you can open Code-server in Chrome by IPv6 address like http://[2022:1111:1111:1111:1111:1111:1111:1111]:8080/ (Change it to your IPv6).
With other browsers (Firefox and Edge) here is small bug https://github.com/cdr/code-server/issues/739
But I fond workaround: just add DNS AAAA record and it will work with any browser.
Personally I use https://www.dynu.com/ and set IP with cron job:
# m h  dom mon dow   command
  * *    *   *   *   /usr/bin/curl 'https://api.dynu.com/nic/update?hostname=MY.DOMAN.NAME&alias=ALIAS&myip=no&myipv6=yes&password=MYDYNUPASSWORD'

IPv6 and IPv4 both work.
Modify the file ~/.config/code-server/config.yaml:
bind-addr: "[::]:8080"
auth: password
password: your password
cert: false

Then you can enjoy accessing http://ipv4-address:8080/ and http://[ipv6-address]:8080/ in your browser.
IPv6和IPv4都可以正常工作。
修改~/.config/code-server/config.yaml文件：
bind-addr: "[::]:8080"
auth: password
password: your password
cert: false

然后在浏览器中输入http://ipv4-address:8080/和http://[ipv6-address]:8080/即可访问。


Feature/setup cargo

The Cargo project is properly setup

Approved by myself because I can... just kidding... this was discussed with the team


Package description identical to cottz-publish

https://atmospherejs.com/cottz/publish-relations
https://atmospherejs.com/cottz/publish
Both are described as "Edit your documents before sending without too much stress".

the 2 packages are different and have a different Api, the package I'm using is cottz-publish-relations because it is simpler (in code and usability)

I see this on https://atmospherejs.com/cottz/publish

NOTE: this package is now called cottz:publish-relations and is hosted on https://github.com/Goluis/cottz-publish-relations

Authors who no longer wish to maintain a package can hide it from Atmosphere search results while still letting the package be installable by existing apps and dependent packages by running
meteor admin set-unmigrated <package_name>


webcontents: minor patches

Fixes #2413
Fixes #2388
Fixes #2420

What does the load-commit event do?

I don't #2413 is actually solved, the main purpose of that issue is to know whether the navigation is started by drag-drop, which this PR doesn't solve.

@zcbenz have removed the commit related to #2413. Does the renderer contain information on what kind of user_gesture caused the navigation ?

Looks good to me, thanks!

Does the renderer contain information on what kind of user_gesture caused the navigation ?

I don't think we can get it from renderer.


Drop support for Python 3.6

Python 3.6 reached end-of-life on Dec 12, 2021.

Codecov Report

Merging #23 (90eaba7) into master (392f36f) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##            master       #23   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         5    +1
  Lines          393       399    +6
  Branches        89        89
=========================================
+ Hits           393       399    +6

Flag
Coverage Δ

3.10
100.00% <ø> (ø)

ubuntu-latest
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


cranelift: Implement ineg.i128 for everyone

👋 Hey,
This PR implements ineg.i128 for all backends, except s390x which already supports it.
Fixes #5108
Fixes #5105

Thanks!
I've also enabled the fuzzer for ineg (on the last commit), and it ran for about an hour on x86 without issues.

@afonso360 would you mind rebasing on top of #5150 so the Docs CI job gets the updated URL?

There seems to be a lot of Internet Weather today! ⛈  It looks like the build job also spuriously failed for a different reason.

Yup, I just clicked "rerun" on the failed build jobs (crates.io errors?); I'll keep an eye on this and hopefully merge it soon.


Include filesystem dock split offset in editor layouts

If the layout doesn't contain the relevant value, it will be set to 0, so

this change is compatible with current layout settings file;
the default layout doesn't need an explicit value for it.

Cherry-picked from 2ac89f65403c606ad9a3cdf65e591cb375faf024

By the way, at first I've thought to make this less case-specific by providing an API such that any dock could add custom values to the layout. But since the filesystem dock would be the only use case right now, I've decided to apply the KISS principle.


Added image field

Thanks for the patch. Could you please also add the new widget to check.py.
check.py lets you/devs see the behaviour of a widget when chosen to be rendered using different methods (ie, using a macro, or using the field's __call__)


Insert Title Here

Describe the issue in detail here. Attach any relevant screenshots or files. The section below was automatically generated. Remove any information that you do not wish to include in the report.

Debug Data

Property
Value

Name
"Wolfram/Chatbook"

Version
"1.0.4"

EvaluationEnvironment
"Session"

FrontEndVersion
"Desktop: 13.3 for Microsoft Windows (64-bit) (July 24, 2023)"

KernelVersion
"13.3.1 for Microsoft Windows (64-bit) (July 24, 2023)"

SystemID
"Windows-x86-64"

Notebooks
True

DynamicEvaluation
False

SynchronousEvaluation
False

TaskEvaluation
False

Settings
Inherited

Stack Data
checkResponse
throwFailure
trimURL

Failure Data
<|
  "Evaluation" :> Wolfram`Chatbook`Actions`Private`toolFreeQ[ProgressIndicator[Appearance -> "Percolate"]]
  "Arguments" -> {}
|>

Duplicate of #375


Send a MS Teams notification if nightlies (MAPDL or docs) fails

As the title.
I thought an email will be more useful, but

it is difficult to setup an outlook email because of the 2FA
We will need an email address for the project?

So, although I'm not big fan of MS Teams, let's give it a try.

Ha! This is actually really cool.
Please add this as a recommendation/best practice in our dev-guide.


Update 052-working-with-generated-types.mdx

This took me a good amount of time to figure out why it wasn't working.  On 2.19!

Hey @amcjen, thanks for the PR, and good catch! This is being fixed in #1462 😊 We'll hopefully merge that today so i'll close this.

Awesome, excited to see the new docs!  Also, just wanted to offer an incredibly heartfelt thank you for such a wonderful framework, and such fabulous documentation. Seriously a shining star in a sea of poorly-written READMEs.  Thank you and your team so much for all your work. 🖤


[RFC] Include LESS and CSS

Feature Request
Include CSS with our package.
Problem description

Currently, adding CSS is complicated.  Theming for the CSS is even more complicated.
As maintainers, we also do not have control over the updates and release of the CSS since it is managed in another repo.  This makes updates and fixes incredibly difficult.

Proposed solution

Copy the LESS distribution to our repo.  Take over maintenance and updates entirely.  Ship the included themes as part of our package, simplifying the setup process.
Update the doc site to be a theme designer and sharing app.

Number 2 is a big one.  I'd like users to be able to sign in to the doc site to create and share themes. Every component page would include a sidebar for editing the theme variables for the component you are viewing.  Changes would be compiled and applied on the fly.
Taking over CSS would allow us to fix things we have been unable to fix in the past.  It would also allow us to add features we have been unable to add.
MVP
I'm toying with the "Docs as a theme designer and sharing app"  in #2938.

I like this idea a lot. Semantic isn't as active as it used to be and there's a lot of power we could be harnessing if SUIR "took control" so to speak. It also opens the doors for some things like css-modules should the need arise.
In the circumstance that SUI is updated, how would that be handled? Would we try to back port the changes to maintain consistency?

Step 1, include all the less files directly.
Step 2, gradually refactor the less files to actually use less features, and nest css properly. This way we can get rid of the tons of important declarations that are used all over the place.

Thanks for the feedback guys.  I agree wholeheartedly with the statements here.
I also don't think we need to worry about 100% consistency.  If anything, I think we can make more things consistent moving forward.  We've talked about this in the MANIFESTO.md for Stardust (essentially a hard fork effort).
I think where we are headed is to have Stardust run alongside of SUIR.  Initially, I had thought Stardust would really be SUIR v2, however, the changes there are drastic enough that I think we'll brand it as "Stardust" only.  It is heavily inspired by SUI, but will not be close enough at completion to be considered an update.
As for SUIR, I think pulling in the styles here is a good move and will ensure the future of the project.  Maybe someday, we can converge the efforts in Stardust with SUIR and or SUI.  Until then, we should move forward.

In the long run for SUIR this is probably the best solution. There are SO many questions about how the styles work or for style related issues that we can simply not solve. It doesn't matter how well we document the solutions. And the experience for the user when they have to dig in to customizing styles is not the best and basically requires you to install SUI core if you want all of the theming and tooling that is part of it.
Not to mention when there are massive, breaking changes that we have no idea about and then all of a sudden they hit and we have to scramble to try to support a community when we all have our main work taking priority.
Issues like this one are also another problem. When something major in the main SUI library gets updated, we have to move to make a fix... and when inevitable bugs pop up, part of our work is trying to react to an already slow moving project. https://github.com/Semantic-Org/Semantic-UI/issues/6185#issuecomment-403618632
No disrespect at all to SUI core of course. When things get busy on other fronts, it is completely understandable that work on open source projects is lower priority. Having styles here where we can at least offer immediate solutions and also shelter users of the library from other potential upstream issues I think is going to lead to an overall better user experience.

@jlukic is flying out tomorrow to meet about Stardust and some other collaboration stuff.  I will discuss this with him then as well.

In that case... it might be worth exploring the idea of moving things to a monorepo somehow. Or at least discussing what that might look like. There could still be separate read only repos that get generated and PRs there would go upstream to the mono where they come down to the separates.
For the styles, the build tools that @jlukic built with gulp are great. It would be awesome if there was a way for us to logically maintain that in some way. Not sure if that's the best way moving forward with the modern frontend ecosystem though. I know there is also an Angular flavor of SUI. I do not have visibility on how this impacts them.
This is mostly a brain dump. Just throwing ideas to see if anything sticks.

This is mostly a brain dump. Just throwing ideas to see if anything sticks.

Definitely.  I have similar ambitions for taking a more cohesive approach to how Semantic Org handles sharing specifications, tooling, and styles.  We need a better story here.
As for Stardust, we'll be adding pretty robust theme editing experiences right into the doc site.  We have a branch that enables each example to become aware of which theme values it is using and expose those to the user to play with in a form.  This will quickly grow into color pickers, range sliders, etc and essentially become a full blown theme designer.  At that point, I want users to be able to "Sign in with GitHub" to save/share/spin themes.
The power that will be shown there is pretty impressive already, but it is going to get a whole lot better.  Add to this the fact that Stardust is also tackling Accessibility, RTL, and a host of other pains out of the gate and the future is looking good.  I want to make sure all those goodies don't get locked up in Stardust alone, but are open to the world to compose in their framework or app as well.

Any updated thoughts on this?

I appreicate that the core team has little or no time to work on this right now, but to my eyes it seems fundamental to the progression of SUIR. It would be good to get an official update on where the project's heading, and if that just means the current state of minor improvement releases then so be it.

I agree.  We're in a slow period, but by no means stopped.  We will continue to make bug fixes and minor updates for now.
The reason we are not moving forward with this at full pace is largely because we do not want to fracture Semantic UI as an ecosystem.  There is a certain tone, quality, and vision to Semantic's components and we do not want to harm that by deviating with our own updates.
I keep in close contact with Jack (original SUI author) on this issue and the future of the library.  We have many plans and are still working in the background on much larger picture items.  Semantic is by no means dead and we haven't left.  Just making sure the next phase of development is both high quality and sustainable.
Thanks for your understanding and patience.

Thank you very much for the reply - I look forward to hearing more about future developments!

I keep in close contact with Jack (original SUI author) on this issue and the future of the library. We have many plans and are still working in the background on much larger picture items. Semantic is by no means dead and we haven't left. Just making sure the next phase of development is both high quality and sustainable.

@levithomason thank you for this info. Could you please just, very quickly, give us some more details about the dev. of SUI? There is no activity on the repo since October 2018, I think it should stated if dev. will be resumed or not.
People (me! :)) looking for UI frameworks need to have elements to decide if SUI + SUIR is a candidate to be evaluated or to be immediately discarded... At this moment, I am discarding it... :(

I will say that you can use Fomantic UI (https://fomantic-ui.com/) as drop in replacement for now.

@layershifter thank you, but I read your comment [here] during my investigation, you are actually not recommending it, or am I wrong? :)
Do you have any idea if at some point Semantic-UI development will be resumed?

I am closing this issue as proposed thing will never happen due resources limits.

@ntarocco things changed, see my comment (https://github.com/Semantic-Org/Semantic-UI-React/issues/3397). For now, I definitely recommend to switch to Fomantic UI.


Merge main branch changes into copyright-fix to get latest CI changes

Description
Merge main branch changes into copyright-fix to get latest CI changes
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

We aren't merging to main line branch right.. You should generally be able to rebase without needing a PR

We aren't merging to main line branch right.. You should generally be able to rebase without needing a PR

 % git push origin copyright-fix
To https://github.com/opensearch-project/asynchronous-search.git
 ! [rejected]        copyright-fix -> copyright-fix (non-fast-forward)
error: failed to push some refs to 'https://github.com/opensearch-project/asynchronous-search.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

Lmk if you need help with branches. This should go to main.


Ability to export and import pins

Description of the new feature / enhancement

As a user, I may have set up specific pins for different software (gating, pinning, blocking). I would like the ability to export those pins and subsequently import the pins later.
Some pins may collide with existing pins while importing. WinGet would need to determine if the import for a pin can be added cleanly with an existing pin. If not, importing that specific pin may fail.
Proposed technical implementation details
winget pin export & winget pin import

Ah, I couldn't find the related issue since I was searching for issues under https://github.com/microsoft/winget-cli/labels/Command-Pin. I don't know whether the export command should have this functionality or this be added under winget pin export / winget pin import

Duplicate of #3493

[Policy] Command-Pinning
For housekeeping


Fixes for #895 & #1014

#1014 was discussed a bit on discord, and we agreed that all packages should be singular

Mind turn fixes into fix and schemas into schema instead for subpackages?

Have we thought of possibly making a subcategory within the data package so it would be net.minecraft.data.fixer.NbtOps for example.

Note that this isn't a full fix for #895 as it also relates to the relevant method/field names in Entity.
i509VCB: Datafixer stuff should not be moved to net.minecraft.data as that package only has data generation tools.

@Juuxel, as I said on your issue, entity nbt is still named "Portal" and does not contain "NetherPortal", that's why I was not sure to rename these fields


[Android] Fix 1px border radius

Due to hardware-acceleration & 750px viewport & sub-pixel, border-radius of some page will not be rendered.
This commit try to fix the problem, using Canvas.drawArc instead of Path.addArc to skip hardware-acceleration behavior.

          2 Errors

:no_entry_sign:
ios/sdk/WeexSDK/Sources/Utility/WXConvert.h#L14: include of non-modular header inside framework module ‘WeexSDK.WXConvert’ [-Werror,-Wnon-modular-include-in-framework-module]
#import "WXBoxShadow.h"

:no_entry_sign:
ios/sdk/WeexSDK/Sources/Module/WXInstanceWrap.h#L9: could not build module ‘WeexSDK’
#import "WXModuleProtocol.h"

  Generated by :no_entry_sign: danger

Send new PR to https://github.com/apache/incubator-weex pls.


Documentation for the backend API

For those that wish to write their own front-end we need to document the backend API.

Closed by #43


Reduce TCP Read Delay

Hi Everyone
I'm using esp32 to access dev-board UART wirelessly in the following way.

In recent test, I found that the delay between esp32 RD request and RD respond is about 250ms in sequential read access.
Is there any way to reduce this delay? Any comment would be very helpful.
Thanks

Any comment?

Hi, How do you get 250ms? Sniffer the packet in the air?


Added boolean option 'showZoomButtons'

to show -100, -10, -1, +1, +10, +100 buttons under the slider for zoom fine tuning

Zoom buttons are a great option, but I think you should only add two buttons for zoom in and zoom out and allow the developer to set the zoom step value.


Update simple-data-scripter extension

This PR fixes #
Add support for unicode and varbinary

@ecirpnaes the new version has been published.


Readmes rach java1

First batch of my Java Android readme makeovers, @sorenoid could you take a first look please when you have a moment, thanks.

thanks @sorenoid, nice catch! how's it looking now, happy for this to go to second review?

@hud10837 please could you do a second review?

thanks @hud10837! Changes made, happy with these?


Message input box is broken in latest build.

Input is broken on the message compose box where text only shows up in a small sliver.

Something in the latest React Native version broke it.
We are replacing it with a better one anyways.

Fixed in latest master by merging the new compose box design.