Where does Materialize stand today ? Why should one choose Materialize over other libraries ?

@Dogfalo It's almost a year since we release 1.0. Since Nov. 2018 till today there has been only a few ( less than 10 may be ) usable ( except patreon updates ) commits.
Can you please clear the air around the development of this project ? Also, it would be very helpful if we can bring-up the advantages of using Materialize over other frameworks, since this project has been stalled for a long time. MDC which released v 1.0 in Mar. 2019, has been actively moved towards v 4.0.alpha ( as of today stable is v 3.1.1 ).

I too also want to know this as I use this too much and I want to know if I need to look at switching to a framework thats still being worked on as this one is stalled

Short answer: yes
The maintainers are just taking a break.

@DanielRuf It's been quite a while since the last update from @Dogfalo on #6243 . It's always great to hear that Materialize is progressing. But as a user the comparison between MDC and Materialize does pop-up. MDC is multi-platform and is being actively updated with features, bug fixes and security patches. I feel moving forward, we must clarify where does Materialize stand today ? What are it's fundamental strengths against other libraries ? ( there wasn't a match to Materialize back then, but that's not the case anymore ) ? And what's the plan for the coming releases ?
Hope you're getting the point.

@Praveen-Rai please see https://github.com/Dogfalo/materialize/issues/6438

@DanielRuf Thanks for linking the issue. So, things are moving ( on other branches ), it's just we aren't releasing. That's good to hear. Though we still need a roadmap and active release cycle. And as i said earlier we need to put up a document "Why use Materialize" or "Core Strengths of Materialize". Meanwhile i'll change the title of this issue.

Short answer: yes
The maintainers are just taking a break.

Thanks for pointing that out :) Awesome to hear stuff is still moving on with this Lib. I would hate to have to rewrite my site with another project. Can't wait for future updates.
I also agree with @Praveen-Rai , a roadmap or similar would be of use

@Praveen-Rai

So, things are moving ( on other branches ), it's just we aren't releasing

I would be not so sure... I took a quick look at the other branches and most of them have not been updated since 2017. Some of the branches have one or two commits more than the master, but there is nothing worth mentioning.

See https://github.com/Dogfalo/materialize/compare/1.0.0...v1-dev (40 commits).
Also both maintainers take a break at the moment. There is no other person with merge permissions afaik (I was an active contributor for a long time).

@DanielRuf it's an indefinite break or you know when they will return?
Currently dropdowns and selects do not work on mobile, it's very important issue.

I can not answer this.
Do you know what has to be fixed / changed? If so you can patch it and provide a PR.
Did you already search all issues and PRs for relevant commits / patches?

@DanielRuf it's an indefinite break or you know when they will return?
Currently dropdowns and selects do not work on mobile, it's a very important issue.

Out of interest what version of Materialize are you using and where is are dropdowns failing for you? As I just tested it and I have dropdowns (and the internal selects) working fine on mobile with my setup using them (currently) within mobile side nav

@Lagicrus 1.0 last version, go to this link https://materializecss.com/select.html and try with your phone.
Using the mobile testing tool of the browser console it work, but not from a real mobile device.

Just tested it on my device (Android, 8.1.0) and it works fine for both triggering the drop-down and choosing the options within

https://github.com/Dogfalo/materialize/issues/6412

https://github.com/Dogfalo/materialize/issues/6369

the second link has a video (not mine) showing whats happening on my device

Huh, thats weird

It's been over a year, how long of a break is it going to be?

Hey Andrew changes are happening look at the v1-dev and rollup branches
On Mon, Oct 7, 2019 at 1:08 PM Andrew Hoffmann<EMAIL_ADDRESS>wrote:

It's been over a year, how long of a break is it going to be?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Dogfalo/materialize/issues/6441?email_source=notifications&email_token=AAVFVR7726NYU5E3ZCWZBJTQNOJMPA5CNFSM4IUJPSZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEARUJMI#issuecomment-539182257,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAVFVR2JWQSPJMJRLL2ZC33QNOJMPANCNFSM4IUJPSZQ
.

--
Doggy sends his greetings from Mars.

Hey Andrew changes are happening look at the v1-dev and rollup branches
On Mon, Oct 7, 2019 at 1:08 PM Andrew Hoffmann @.***> wrote: It's been over a year, how long of a break is it going to be? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#6441?email_source=notifications&email_token=AAVFVR7726NYU5E3ZCWZBJTQNOJMPA5CNFSM4IUJPSZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEARUJMI#issuecomment-539182257>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAVFVR2JWQSPJMJRLL2ZC33QNOJMPANCNFSM4IUJPSZQ .
-- Doggy sends his greetings from Mars.

Any idea when the changelog.MD will be updated so we can figure out whats been changed on those two branches?
Thanks for the updates however :)

When a new release is done. Or check the commits.

When a new release is done. Or check the commits.

New releases make sense rather than every commit thanks
I was just looking for a consolidated overview rather than digging through the commits themselves

I am in the process of making the components being usable as separate imports. This requires a lot of changes however so it is not quite ready

@Dogfalo @DanielRuf Thanks for the updates. We must update all our near future plans in the Roadmap doc page. As far as the changes and releases are concerned, it will be much appreciated to focus on releasing the bug-fixes asap.
There are multiple feature requests ( e.g. #6282   ) in the backlog, sorting them out, will give us the clarity and opportunity to initiate discussions on the usage. And finally a document highlighting the core strengths of Materialize will help the consumers to make an apt choice.

Yes please, work on the bugfix first

"Are we there yet?"
In 2020 should someone use this for new projects or just stay away?
No new release is OK, those issues(500+) might be fixed with next release in 202*. But why not review some of these existing pull request(182)? and/or at least bump minor version to some 1.0.* with those 48commits already in the branch. so that people don't waste time facing known issues when using the 2018 dist/cdn/npm. You have good, nice and clean framework, please don't clutter it with all this confusion.

Hi @AhnafCodes,
I'm just a normal contributor and I can not push to this repository.

Thanks for responding @DanielRuf, Are you aware if any of the fork -ed repository has these 48 commits in master and may be some other much needed pull request. Because, a lot has changed since 2018, just new version of browsers would introduce few issues and might need minor fixes and minor version updates.

@AhnafCodes see https://github.com/Dogfalo/materialize/network

@Dogfalo @DanielRuf @acburst
What is the official status of this project? You have all the right to take the well deserved after the release of v1.
Is there any given roadmap for 2020? Or is this project being neglected and the creators are moving on to the next thing (which is totally fine)?
Just some honest words would be very welcome how and whether this project is going on.
Thanks in advance.
Cheers.

@MacGyer please read the previous comments, I'm not a maintainer / collaborator, just a past long-term contributor.
I can not answer your questions.

@Dogfalo surely you owe us no explanation. We are here because we like and admire this Framework from you. At the same time folks like me and @MacGyer can't use this for in projects and if this remains stagnant.
Like, We use bootstap 3.5 on an old project(from 2015-2016). we plan to upgrade that codebase, and we have been looking at this thread since November end. Now, we have decide to go with a less comprehensive css framework(Ta*****), only because see its roadmap and it being actively maintained, in spite of the reservations we have about it.
No minor version update and 182 PR pending would keep away any new adopters and soon old timers too would flee.

March 2020 still no updates, no fixed bugs no nothing. Oh, but there is some push to sponsors in the footer. I guess I'll leave this framework which it was good at the beginning. Hope it recovers from it was a great framework that it was promising.

Any tips for an easy migration to a different framework? suggestions?

Any tips for an easy migration to a different framework? suggestions?

I just switched over to react and then used material-ui

Any tips for an easy migration to a different framework? suggestions?

I just switched over to react and then used material-ui

Thanks!
I'm using Vue for a small project, so I'd rather find something which is suitable for that.

Any tips for an easy migration to a different framework? suggestions?

I just switched over to react and then used material-ui

Thanks!
I'm using Vue for a small project, so I'd rather find something which is suitable for that.

A quick Google finds this which might be what you are looking for

Any tips for an easy migration to a different framework? suggestions?

I just switched over to react and then used material-ui

Thanks!
I'm using Vue for a small project, so I'd rather find something which is suitable for that.

A quick Google finds this which might be what you are looking for

I ended up going for Vuetify - it's very nice :)

@GuyKh You may like this framework https://tronic247.github.io/material-docs/ :D

Why not https://github.com/material-components/material-components-web ? This is the best material you can get

Why not https://github.com/material-components/material-components-web ? This is the best material you can get

This is good for professionals. but not for beginners.

"BIG NO" to Tronic, I wouldn't personal use Jquery in 2021 & beyond. So, wouldn't use a library which uses it as its base.
Why? because the browser does all those Jquery thing itself now. And browser when does something it does it runs faster & better or will run better soon. Jquery sure has the compatibility and browser support(may be ie11) baggage, which might not be an issue for many of use today.
MaterialUI(react) has some big names behind it, but I don't find the CSS tag generation and insertion the right thing to do.
Now my personal preference and reasons for it. Tailwind CSS, after using it for more than a year and seeing how it can be used to get minimal CSS footprint using PurgeCSS settings, I am happy with it.
What about material design? you have https://material-tailwind.com/ for react now and they plan to come out soon with Vue & Angular. CreativeTim the agency behind it has some history and know-how of web development, so we can expect some quality.

@AhnafCodes that's true, I made this library for jQuery lovers. But I'm also trying to remove jQuery soon :D

"BIG NO" to Tronic, I wouldn't personal use Jquery in 2021 & beyond. So, wouldn't use a library which uses it as its base.
Why? because the browser does all those Jquery things itself now. And browser when does something it does, it runs faster & better or will run better soon. Jquery surely has the compatibility and browser support(may be ie11) baggage, which might not be an issue for many of us today.
MaterialUI(react) has some big names behind it, but I don't find the CSS tag generation and insertion the right thing to do.
Now, my personal preference and reasons for it. Tailwind CSS, after using it for more than a year and seeing how it can be used to get minimal CSS footprint using PurgeCSS settings, I am happy with it.
If material design is not a concern, we have https://tailwindui.com/. It is paid, but not pricey and from creators for tailwind CSS.
For Vue users there are free options like https://www.vue-tailwind.com/.
What about material design & React? you have https://material-tailwind.com/ for React for now and they plan to come out soon with Vue & Angular. CreativeTim, the agency behind it has some history and know-how of web development, so we can expect some quality.

Personally, for React I use https://material-ui.com/ / https://github.com/mui-org/material-ui

@Lagicrus You may like this framework https://tronic247.github.io/material-docs/ :D


add more test REST notebooks and examples

I suggest we create a standard ./notebooks folder and add them there.
We can exclude them from packaging of this extension if you'd like in .vscodeignore:
...
notebooks
...

@tanhakabir I would like to use those two notebooks for html, image and json results testing to see what we need to do to add image view (#87) and better json data display.

cool thank you for your help!


Webhooks do not support multiple handlers

Describe the bug
The Artifactory Webhook REST API supports within one webhook definition multiple handlers with url/secret/proxy.
Example:
"handlers": [
    {
      "handler_type": "webhook",
      "url": "https://webhook.my-company.test/",
      "secret": "tell no one",
      "proxy": "mainProxy",
      "custom_http_headers": [
        {
          "name": "X-MyCompany-Header",
          "value": "whatever"
        }
      ]
    }
  ]

On the other side, the Terraform Provider supports per webhook only one handler/URL.
Example:
resource "artifactory_artifact_webhook" "artifact-webhook" {
  key         = "artifact-webhook"

  [...]

  url         = "http://tempurl.org/webhook"
  secret      = "some-secret"
  proxy       = "proxy-key"
}

Requirements for and issue

[x] A description of the bug
[ ] A fully functioning terraform snippet that can be copy&pasted (no outside files or ENV vars unless that's part of the issue). If this is not supplied, this issue will likely be closed without any effort expended.
[x] Your version of artifactory (you can curl it at $host/artifactory/api/system/version: 7.37
[x] Your version of terraform: 1.1
[x] Your version of terraform provider: 6.6.0

Expected behavior
Possibility to define multiple urls/secrets (aka handlers) within one webhook resource like this:
resource "artifactory_artifact_webhook" "artifact-webhook" {
  key         = "artifact-webhook"
  handlers = [
     - url: https://
        secret: abc
        custom_http_headers:
          token: value
     - url: https://
        secret: abcd
        custom_http_headers:
          token2: value2
  ]

Additional context
Add any other context about the problem here.

@martinm82 The reason the initial implementation only support one handler is to match the capability the Artifactory UI provides. It only allows setting up one handler per webhook.
For the same reason, if you configure a webhook with multiple handlers via the API, you won't be able to see or manage handlers except the first one in the list in the UI.

@alexhung you are right, from UI perspective it is indeed just one handler. I was not aware of it because we configured webhooks in the past on our on-premise environment via REST API (custom Yaml format).
Since we are migrating from our custom REST API based solution to Terraform, the only way around this is to duplicate each webhook that has multiple handlers.
I believe the provider should be in line with the official REST API since it's kind of a replacement for it. Do you think this is something we can change, maybe introduce a new handler block and still have the single url/custom_http_header/proxy values for backwards compatibility?

Fair point, but I am wondering who would create webhooks with TF and later modify it via the UI. We follow strictly the IaC approach.  But you never know how others do it ;)

@martinm82 Because it is possible, someone will do it one day and then come here for help 😄

But that is already nowadays possible if you manage Artifactory directly via REST API.

@martinm82

Do you think this is something we can change, maybe introduce a new handler block and still have the single url/custom_http_header/proxy values for backwards compatibility?

Totally!

@martinm82
I misspoke in my previous message. I was thinking of the criteria block which can be made to support multiples easily. For handler, I will definitely migrate to using handler block for each. I will provide a state migration code as well to transit from current structure to new one.


Imported date values not recognised until entry is re-saved

I have imported a series of entries but they don't appear in the front-end when filtering them by a date field. If I go into the entry and re-save they appear.
It is as though Craft is not registering the date until the page is saved.
Any thoughts? Thanks for the awesome plugin!

Do the dates correctly appear in the CP immediately?

Yes, when you load the entry in CP the dates are correct and then on save it appears on the site.
I imported using the format YYYY-MM-DD HH:MM:SS worked previously on another website.
We're using cache tag, but its disabled in our local environments and we've tried clearing the cache etc

What logics do you use for filtering by date?

{% set entries = entries.endDate( '< ' ~ now ) %}
Where endDate is the field we've imported into

Mmm that should be ok, is there any way you can make this reproducable?


Unsupported attribute, source_json is deprecated

Found a bug? Maybe our Slack Community can help.

Describe the Bug
A clear and concise description of what the bug is.
The latest release breaks helm module without even touch Terraform
│ Error: Unsupported attribute
│
│   on .terraform/modules/external_secrets_helm.eks_iam_policy/main.tf line 17, in data "aws_iam_policy_document" "this":
│   17:   source_json = var.iam_source_json_url != null ? data.http.iam_source_json_url[0].body : var.iam_source_json
│
│ This object has no argument, nested block, or exported attribute named
│ "body".

Expected Behavior
A clear and concise description of what you expected to happen.
Steps to Reproduce
Steps to reproduce the behavior:

Go to '...'
Run '....'
Enter '....'
See error

#
# Helm | IRSA | External Secrets
#

module "external_secrets_helm" {
  source                      = "registry.terraform.io/cloudposse/helm-release/aws"
  version                     = "0.4.3"
  enabled                     = true
  eks_cluster_oidc_issuer_url = module.eks_0.oidc_provider

  name                 = "external-secrets"
  repository           = "https://charts.external-secrets.io"
  chart                = "external-secrets"
  chart_version        = "0.5.1"
  create_namespace     = true
  kubernetes_namespace = "external-secrets"
  atomic               = true
  cleanup_on_fail      = true
  timeout              = 300
  wait                 = true

  service_account_name                        = ""
  service_account_namespace                   = "external-secrets"
  iam_role_enabled                            = true
  service_account_role_arn_annotation_enabled = true

  #    iam_policy_statements = {
  #      ParameterStore = {
  #        effect     = "Allow"
  #        actions    = ["ssm:GetParameter"]
  #        resources  = ["arn:aws:ssm:*:*:fabric/dev"]
  #        conditions = []
  #      },
  #      SecretsManager = {
  #        effect = "Allow"
  #        actions = [
  #          "secretsmanager:GetResourcePolicy",
  #          "secretsmanager:GetSecretValue",
  #          "secretsmanager:DescribeSecret",
  #          "secretsmanager:ListSecretVersionIds",
  #        ]
  #        resources  = ["arn:aws:secretsmanager:*:*:secret:fabric"]
  #        conditions = []
  #      },
  #    }

  iam_policy_statements = {
    ParameterStore = {
      effect     = "Allow"
      actions    = ["ssm:*"]
      resources  = ["*"]
      conditions = []
    },
    SecretsManager = {
      effect     = "Allow"
      actions    = ["secretsmanager:*"]
      resources  = ["*"]
      conditions = []
    },
  }

  values = [
    file("${path.module}/helm_values/external-secrets.yaml")
  ]
}

output "external_secrets_metadata" {
  description = "Block status of the deployed release."
  value       = module.external_secrets_helm.metadata
}

Screenshots
If applicable, add screenshots or logs to help explain your problem.
Environment (please complete the following information):
Anything that will help us triage the bug will help. Here are some ideas:

OS: OSX
Version 1.1.9
running from terminal & Terraform Cloud
versions.tf

# ---------------------------------------------------------------------------------------------------------------------
# Terraform version constraints
# ---------------------------------------------------------------------------------------------------------------------

terraform {
  required_version = ">= 1.0.0"

  required_providers {
    aws = {
      source  = "hashicorp/aws"
      version = ">= 3.72, >= 4.10"
    }
    kubernetes = {
      source  = "hashicorp/kubernetes"
      version = ">= 2.10"
    }
    helm = {
      source  = "hashicorp/helm"
      version = ">= 2.4.1"
    }
    local = {
      source  = "hashicorp/local"
      version = ">= 2.1"
    }
    null = {
      source  = "hashicorp/null"
      version = ">= 3.1"
    }
    http = {
      source  = "terraform-aws-modules/http"
      version = "2.4.1"
    }
    kubectl = {
      source  = "gavinbunney/kubectl"
      version = ">= 1.14"
    }
    random = {
      source  = "hashicorp/random"
      version = ">= 2.2"
    }
    tfe = {
      source  = "hashicorp/tfe"
      version = "~> 0.30.2"
    }
    grafana = {
      source  = "grafana/grafana"
      version = ">= 1.13.3"
    }
  }
}

Additional Context
Add any other context about the problem here.

@nitrocode I believe the issue and solution here

It sounds like this PR will solve the above issue since we have deprecated source_json from the upstream module
https://github.com/cloudposse/terraform-aws-helm-release/pull/32/files
Until that PR is tested, as a workaround, you can pin the related providers to a previous version aws provider version using the terraform {} block.

@ZeroDeth please try 0.6.0 and see if this resolves the issue

Please comment if this issue is not solved and I will reopen.


S3 File permission

I want to upload the video file to S3. I found out that the file permission is private. But I want to make the file permission as Public. I didn't find any way to set file permission as public. I am working on Nodejs 16

There is currently no way to specify object ACL. you would have to change bucket ACL to allow world read on the bucket: https://docs.aws.amazon.com/AmazonS3/latest/userguide/managing-acls.html

I found ACL is available to set in PutObjectInput https://docs.aws.amazon.com/sdk-for-go/api/service/s3/#PutObjectInput


[Refactor] Extract BackendExecState from Coordinator

Relates to #27846.
Extract BackendExecState from Coordinator. Use the state pattern and remove the related fields isInitialized, hasCancelled, isDone.
/**
 * Maintain the execution state of a fragment instance.
 * Executions begin in the state CREATED and transition between states following this diagram:
 *
 * <pre>{@code
 * CREATED ────► DEPLOYING ────► EXECUTING ───► FINISHED
 *                  │                │
 *                  │                │
 *                  │                ▼
 *                  ├──────────► CANCELLING
 *                  │                │
 *                  │                │
 *                  ▼                │
 *               FAILED ◄────────────┘
 * }
 * </pre>
 * <p>
 * All the methods are thead-safe.
 * The {@link #state} and {@link #profile} are protected by {@code synchronized(this)}.
 */

What type of PR is this:

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

Checklist:

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

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

Bugfix cherry-pick branch check:

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

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 172 / 201 (85.57%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/scheduler/dag/ExecutionFragmentInstance.java
128
153
83.66%
[140, 145, 150, 163, 197, 258, 275, 277, 298, 299, 300, 301, 303, 304, 305, 351, 352, 353, 357, 358, 374, 375, 376, 377, 378]

:large_blue_circle:
com/starrocks/qe/DefaultCoordinator.java
44
48
91.67%
[804, 1666, 1667, 1670]

[FE PR Coverage Check]
:heart_eyes: pass : 176 / 208 (84.62%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/scheduler/dag/ExecutionFragmentInstance.java
128
153
83.66%
[140, 145, 150, 163, 197, 258, 275, 277, 298, 299, 300, 301, 303, 304, 305, 351, 352, 353, 357, 358, 374, 375, 376, 377, 378]

:large_blue_circle:
com/starrocks/qe/DefaultCoordinator.java
48
55
87.27%
[380, 804, 1228, 1344, 1666, 1667, 1670]

[FE PR Coverage Check]
:heart_eyes: pass : 176 / 208 (84.62%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/scheduler/dag/ExecutionFragmentInstance.java
128
153
83.66%
[140, 145, 150, 163, 197, 258, 275, 277, 298, 299, 300, 301, 303, 304, 305, 351, 352, 353, 357, 358, 374, 375, 376, 377, 378]

:large_blue_circle:
com/starrocks/qe/DefaultCoordinator.java
48
55
87.27%
[380, 804, 1228, 1344, 1666, 1667, 1670]

[FE PR Coverage Check]
:heart_eyes: pass : 178 / 210 (84.76%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/scheduler/dag/ExecutionFragmentInstance.java
128
153
83.66%
[140, 145, 150, 163, 197, 258, 275, 277, 298, 299, 300, 301, 303, 304, 305, 351, 352, 353, 357, 358, 374, 375, 376, 377, 378]

:large_blue_circle:
com/starrocks/qe/DefaultCoordinator.java
50
57
87.72%
[380, 804, 1228, 1344, 1666, 1667, 1670]

[FE PR Coverage Check]
:heart_eyes: pass : 51 / 58 (87.93%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/DefaultCoordinator.java
51
58
87.93%
[380, 804, 1228, 1344, 1666, 1667, 1670]

[FE PR Coverage Check]
:heart_eyes: pass : 186 / 210 (88.57%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/DefaultCoordinator.java
51
58
87.93%
[380, 804, 1228, 1344, 1666, 1667, 1670]

:large_blue_circle:
com/starrocks/qe/scheduler/dag/FragmentInstanceExecState.java
135
152
88.82%
[161, 166, 171, 184, 218, 315, 317, 383, 384, 385, 389, 390, 406, 407, 408, 409, 410]

[FE PR Coverage Check]
:heart_eyes: pass : 186 / 210 (88.57%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/DefaultCoordinator.java
51
58
87.93%
[380, 804, 1228, 1344, 1666, 1667, 1670]

:large_blue_circle:
com/starrocks/qe/scheduler/dag/FragmentInstanceExecState.java
135
152
88.82%
[161, 166, 171, 184, 218, 315, 317, 383, 384, 385, 389, 390, 406, 407, 408, 409, 410]


Add methods track_download_by_url and track_info

So I propose (I test this code, and it's work):
def track_download_by_url(self, url: str, filename: str = "", folder: Path = "") -> Path:
    fname = urlparse(url).path.rsplit("/", 1)[1].strip()
    assert fname, """The URL must contain the path to the file (m4a or mp3)."""
    filename = "%s.%s" % (filename, fname.rsplit(".", 1)[1]) if filename else fname
    path = Path(folder) / filename
    response = requests.get(url, stream=True)
    response.raise_for_status()
    with open(path, "wb") as f:
        response.raw.decode_content = True
        shutil.copyfileobj(response.raw, f)
    return path.resolve()

Example url:
https://scontent.fdnk3-1.fna.fbcdn.net/v/t39.12897-6/280752329_537789804610385_4797754427131570699_n.m4a?_nc_cat=1&ccb=1-7&_nc_sid=02c1ff&_nc_ohc=7_-yY46rMD4AX8haatv&_nc_ad=z-m&_nc_cid=1489&_nc_ht=scontent.fdnk3-1.fna&oh=00_AT88pUY8Qt6iRFykFG-DAcEZxuzgwGnZPV8Mjs0M3W8nvA&oe=62A80E3F
But have no idea for something like https://www.instagram.com/reels/audio/698069981278947/

@hittiks done instagrapi 1.16.28
https://adw0rd.github.io/instagrapi/usage-guide/track.html

Thanks for this functionality, but I meant that I needed to download the track from the link to it, and not to reels.
However, I have already solved this problem myself by simply replacing some parameters in the data parameter.
So, with link: https://www.instagram.com/reels/audio/698069981278947/
We have this code:
`    data = {
"tab_type": "clips",
"referrer_media_id": "",
"_uuid": self.uuid,
"audio_cluster_id":<PHONE_NUMBER>78947,
"original_sound_audio_asset_id":<PHONE_NUMBER>78947,
}
result = self.private_request("clips/music/", data)`

And in this case I don't need to get the music_canonical_id somehow.
At the end, I got a tool for downloading audio (track) from a link to it :)

Names audio_cluster_id and original_sound_audio_asset_id I found in chrome developers tools in network page in file music/


AF calculation

From Al: I just looked at the vcf from 10X and the AF plot shows that everything is at 50%. I looked at the vcf file and there are many genotypes that are not 0/1 with depths supporting only alternate observations, for example. The AF in the info fields are also not 0.5.
Can we check on the AF calculation to be sure we are calculating this correctly?
http://vcf.iobio.io/?vcf=https://s3.amazonaws.com/iobio/app_testing/vcf_files/NA12878_10X.vcf.gz

From Yi -
code review welcomed. here are the lines regarding AF calculation
https://github.com/yiq/vcfstatsalive/blob/master/BasicStatsCollector.cpp#L148-L156
One confession is that right now vcfstatsalive does not handle multi-allelic sites. It simple grabs the first value available.

From Yi -
two revelation while talking to @tonydisera

my code actually does multi-allelic. It's just that it's not doing multi-allelic when it comes to AF
I probably should change the code that calculates allele frequency based on read counts to sample ratio, because AO / DP is not really what people would come to expect what allele frequency is. That's more of a cancer concept

From Al -
Looking at the 10X vcf, the AF field is present in the INFO string, so vcfstatsalive should be pulling this value. There are many cases where AF=1.0. It is a single sample vcf, so there are only instances of AF=0.5 and AF=1.0, so I would expect the distribution to show values at 1.0.
And yes, we should probably change the calculation to reflect the number of alleles out of the total showing the alternate, so AF = AC / AN. I'm guessing that if AF is not present in the vcf though, neither will AC and AN, so this might be moot. In that case, we may have no choice but to default to the depth calculation you already have. The other alternative would be to parse all of the genotypes and count AC and AN, but that would be violently expensive for vcf files with many samples, so probably not feasible.

Looking at only multi-allelics (chr1) of this file, all AFs are set to .5, with a few occasional 1 or 0:
AF=0.5,0.5
AF=0.5,0.5
AF=0.5,0.5
AF=0.5,0.5
AF=0.5,0.5
AF=0.5,0.5
AF=0.5,0.5
AF=0.5,0.5
AF=0.5,0.5
AF=0.5,0.5
AF=0.5,0.5
AF=0.0,0.0,0.5

violently expensive? word well chosen.
…
On Wed, Jun 8, 2016 at 10:53 AM, Alistair Ward @.***> wrote:
Looking at the 10X vcf, the AF field is present in the INFO string, so
vcfstatsalive should be pulling this value. There are many cases where
AF=1.0. It is a single sample vcf, so there are only instances of AF=0.5
and AF=1.0, so I would expect the distribution to show values at 1.0.
And yes, we should probably change the calculation to reflect the number
of alleles out of the total showing the alternate, so AF = AC / AN. I'm
guessing that if AF is not present in the vcf though, neither will AC and
AN, so this might be moot. In that case, we may have no choice but to
default to the depth calculation you already have. The other alternative
would be to parse all of the genotypes and count AC and AN, but that would
be violently expensive for vcf files with many samples, so probably not
feasible.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#314 (comment)>,
or mute the thread
https://github.com/notifications/unsubscribe/AAWIAB7gBjlSHrIR6tik7t7iFMuJrFoAks5qJvN3gaJpZM4IxFQV
.

See https://github.com/tonydisera/vcf.iobio.io/issues/29


'List' ready event doesn't fire?

video
https://streamable.com/q5trm
bad one
SubscribePeers = () => {
    this.peers = this.connection.record.getList('peers')

    this.peers.on('ready', () => {
      // this should fire once i think
      const peers = this.peers.getEntries()
      console.log('ready', peers)
    })

  }

good one
SubscribePeers = async () => {
    this.peers = this.connection.record.getList('peers')

    await this.peers.whenReady()

    const peers = this.peers.getEntries()
      console.log('ready', peers)

  }

"@deepstream/client": "^4.0.4",
"@deepstream/server": "^4.1.0",

Looks like the ready event was removed from V4.
Instead you should just use the when ready callback if you want that paradigm
list.whenReady(callback)
You can also check if it is ready already using list.isReady


Dynamic Font Resizing - re-added font resizing into generate.ts file …

re-added font resizing into generate.ts file to trigger font resizing on generate when enabled

Hey @hand-dot,
When using the latest version of the main branch in our app, we noticed that the logic for Dynamically Resizing font in the generate.ts had been removed (https://github.com/pdfme/pdfme/commit/22db786ab1ffb36f58773c9f6ad464ac76a78409#diff-86dc2428e01c4f7437bc94fbcff3a568ff6ca637755855eb8ff08c3ca32b9318) was this intentional?
Many Thanks,
Steffan

Hi @steffancarrington
The modification below was intentional.
https://github.com/pdfme/pdfme/commit/22db786ab1ffb36f58773c9f6ad464ac76a78409#diff-86dc2428e01c4f7437bc94fbcff3a568ff6ca637755855eb8ff08c3ca32b9318
The previously merged code did not support multiple inputs (multiple PDF pages). Therefore, I made a correction.
As you can see from the code below, the calculateDynamicFontSize is used to change the font size according to the user's input characters.
https://github.com/pdfme/pdfme/blob/2868f01449193aeae3af1c764dd4663bf145102b/packages/generator/src/helper.ts#L286
Therefore, I think this pull request is unnecessary.

Hey @hand-dot,
Ah ok, that makes sense, good catch! Thanks for the clarification 👍
I'll close this PR now, since it's not required.
Thanks


Settings

NS++ settings will not load at all. no matter how long I wait it's just the loading screen. It also says I don't have authorization for changing titles although I'm the founder.

In my experience, NS++ settings won't load when you're not logged in to a
nation. I should probably add an error message for that case.
On Sun, Apr 30, 2017 at 12:39 PM, Gavin Aagaard<EMAIL_ADDRESS>wrote:

NS++ settings will not load at all. no matter how long I wait it's just
the loading screen. It also says I don't have authorization for changing
titles although I'm the founder.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NationStates/NationStatesPlusPlus/issues/58, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABBxIj_fhMkkOjG-2t0i1Nzg0_Pm0VS9ks5r1Lk7gaJpZM4NMnpm
.


Remove general xref from GO:0004177 aminopeptidase activity

GO:0004177 aminopeptidase activity has many cross reference, including EC:3.4.11.-
This one is too general, it should be removed .
Thanks, Pascale

@pgaudet Why do you say EC:3.4.11.- is too general for GO:0004177 aminopeptidase activity?  Seems an exact match for equivalent grouping terms to me.
https://enzyme.expasy.org/EC/3.4.11.-
Hydrolases -> Acting on peptide bonds (peptidases) -> Aminopeptidases
id: GO:0004177
name: aminopeptidase activity
namespace: molecular_function
def: "Catalysis of the hydrolysis of a single N-terminal amino acid residue from a polypeptide chain."

Thanks @sjm41
OK - we could add this back - and maybe make these narowMatch?

<IP_ADDRESS> Xaa-Pro aminopeptidase
<IP_ADDRESS>  aspartyl aminopeptidase
<IP_ADDRESS>  aminopeptidase B
<IP_ADDRESS> prolyl aminopeptidase

A bit on a different topic- I am not convinced we were right to obsolete these; do they really represent gene functions? It seems they are different specificity of different enzymes.
Pascale

Thanks for adding back EC:3.4.11.- to GO:0004177. I'll reopen this ticket until that's done.
I'm not sure about whether those four other ECs merit their own GO term or not. I agree they are different functions/specificities.
I see there was a previous discussion about <IP_ADDRESS> here: https://github.com/geneontology/go-ontology/issues/6849
Doing a quick search on UniProt for human EC annotations:

<IP_ADDRESS> Xaa-Pro aminopeptidase -> hits 3 paralogs (XPNPEP1, XPNPEP2, XPNPEP3)
<IP_ADDRESS> aspartyl aminopeptidase -> only hit is DNPEP gene?
<IP_ADDRESS> aminopeptidase B -> only hit is RNPEP gene?
<IP_ADDRESS> prolyl aminopeptidase -> only hit is LAP3 gene?
This seems to support distinct functions, though only one gene is involved in each case.  Not sure this helps or not....


Update fileio.MatchContinuously to allow reading already read files with a new timestamp

This will be the Python counterpart of BEAM-14267.
For fileio.MatchContinuously, we want to add an option to choose to consider a file new if it has a different timestamp from an existing file, even if the file itself has the same name.
See the following design doc for more detail:
https://docs.google.com/document/d/1xnacyLGNh6rbPGgTAh5D1gZVR8rHUBsMMRV3YkvlL08/edit?usp=sharing&resourcekey=0-be0uF-DdmwAz6Vg4Li9FNw
Imported from Jira BEAM-14315. Original Jira may contain additional context.
Reported by: yihu.

Unable to assign user @Abacn. If able, self-assign, otherwise tag @damccorm so that he can assign you. Because of GitHub's spam prevention system, your activity is required to enable assignment in this repo.

.close-issue
completed in #17604


DX12 no-resources bounded

Description
I am trying to debug a dx12 application (which is well behaved). It seems like I am not able to see any resource bound like textures:

Repro steps
Just run a simple capture, any of the draw calls do not show bound resources
Please find traced and output log here:
https://1drv.ms/f/s!Ai0n7iKmKMz0gb88FPW2zZ7v1Yvcng
Environment
Windows 10 1809.
Intel integrated graphics on the latest driver
DX12 API
Surface Pro 5

The pipeline in question is using DXIL shaders, which RenderDoc does not support. Your application must query for whether or not shader model 6 is supported via ID3D12Device::CheckFeatureSupport(D3D12_FEATURE_SHADER_MODEL) before uploading DXIL to the API. If you do that under RenderDoc then it will report that only shader model 5.1 at most is supported, so if you have a DXBC fallback you can use it.

Oh, cool to know! Is 6.0 in the roadmap at all?

Currently I haven't yet decided, as supporting DXIL would be a very large and painful undertaking.

Would compile with the new compiler but for 5.1 work under render doc? Or using the new compiler will still be an issue?

DXIL is equivalent to SM6 - dxc only ever outputs DXIL and so it only supports SM6 and above. Only fxc can output DXBC bytecode for SM5.1 and below.


Some problems with my ax40

hello
I got a japan only (J1) sony fdr-ax40,so you know the language problem upsets me a lot.
Knowing that  your app can not support my device without an app launcher,i tried the fwtool.exe.But the modified firmware didn't work at all.
My steps:
unpack the firmware,
swap the bin files in/0110_backup,
swap the second column values in/0111_backup_sum/backup file,
increase the version,
pack.
So is there anything i forgot to do?

@funnykind
You don't have to patch firmware files anymore. There is a new experimental way to tweak settings on older cameras using the firmware update functionality. Read more about it here. Keep in mind that you are probably the first person to test this on an AX40, so your mileage may vary. If you attempt anything, please let us know!

I have the same machine.  Unfortuntly, I can open the language option but I can pagedown for 2 two page.
As soon as I do it, AX40 restart.  Do you have any idea about it?


Add babel plugin rewire

This will make it much easier to test some internal algorithms I don't want to export from any file, as well as test the stuff that is getting exported

Moving into #158


Add Minimalist theme

This should show if the automatic deployment works as expected. The theme can be found here.

Nice, added ... not let's wait.

Are there any issues with the deployment? The theme was added to this repo but isn't shown on the theme site.

Yes. It doesn' work.


[firebase_dynamic_links] Add steps for android specific integration

Description
I added an optional step in the README that will help people better integrate with Android, providing the intent that will make android proposing the app as possible option to open the link directly without passing from the browser.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the [Flutter Style Guide].
[x] I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the [CLA].
[x] I am willing to follow-up on review comments in a timely manner.

Any news one this one @bparrishMines ?

this is quite old and might even be outdated therefore i close


implement demo cw1155 contract

there are several more unit tests to be done, the overall implementation is good for review now.
There are two FIXME currently:

code, we should add overflow error branch in StdError.
code, the list returned by query is out of order, I'm not sure if it's an issue of the test storage itself?

I just got back from vacation and have lots to do before I can take a deeper look, but I did add comments on the 2 FIXMEs. These are subtle points about how cosmwasm-std is designed and actually intended.

Thanks, two FIXMEs are resolved now.

Add unit tests to expect panic when minting token amount overflow.

Created https://github.com/CosmWasm/cosmwasm-plus/issues/261 inspired by your comments


Add Voice Interaction (Speech Recognition & Text-to-Speech)

Expected Updates:

Implement speech recognition for user input (start/stop via button).
Add text-to-speech to read chatbot responses aloud.
Update UI with microphone and stop buttons.
Test functionality for both voice input and output.

I would love to work on it, so will you assign this task to me?

@Varsha-1605 First submit PR for assigned issues then I will assign. Also if any other contributor want they also can contribute ...

@kom-senapati In mean time.
Let me drive my hands on this issue

Ok @priyanshuverma-dev go ahead


Question about a new release

Hello,
I was wondering if you could publish a new release of the library in the near future.
I'd love to use new functions (especially io from and to geoparquet format) in my python library, but putting a git development url in dependencies isn't really sustainable in the long run 😄

Yes, I'm aware of this discussion and I'll be following the development of those changes in the future.
Thank you for the heads up.

Just as information - since it's not possible to release a library on PyPI with a link to the repository library, I had to lock it to the current newest release and I copied some code with the io module with annotation where it comes from:
https://github.com/kraina-ai/quackosm/blob/482e3090dfbefd7fae4374267ad045be0f12465e/quackosm/_geo_arrow_io.py
I'll remove it after the new release of geoarrow-python (or maybe I'll switch to geoarrow-rust-core when it'll have the same IO capabilities regarding GeoParquet files).


UUID support

Add a unique id implementation that works on all platforms
Once there is support for UUIDs the request id policy can be added back: See https://github.com/Azure/azure-sdk-for-c/pull/474

Since we don't have APIs that need UUID support, closing this issue. Atm, it isn't worth the trade off with code size.


InvalidCastException in DefaultHtmlGenerator.GetCurrentValues

I'm currently seeing a behavior difference between Windows and Mono wrt the select tag helper for an enum in beta4. On Mono, DefaultHtmlGenerator.GetCurrentValues throws an InvalidCastException.
I didn't yet dig in very far to check if that's the reason, but at least the return type of ConvertEnumToString should be TEnum, so the returned null has a type other than object and the cast from the delegate invoke in GetCurrentValues doesn't fail.
If I have time, I'll likely look deeper into this. If the above is the offending code path, it shouldn't happen in the first place…

@Tragetaschen which Mono version are you using? What is the minimal repro for this problem? For example does the failure occur only with a string that does not match any enum value?
Actually even the full stack trace when using the latest Beta 5 bits would help.
BTW ConvertEnumFromString() must return object, TEnum?, or perhaps Enum; it must indicate a failed parse to the caller. The caller's cast to Enum might be acting strange on Mono.

Mono version is 4.0.1 with a patch to fix SignalR's IL_0057 bug.
You are right, I had on my mind that the returned null would have the runtime type object and that the downcast to Enum then fails.
The stack trace is literally Razor => SettingTagHelper.Process => GetCurrentValues. I'll try to reproduce this with a full stack trace (with source file numbers) in dev when I'm home and find the time. There, I can also easily look into Mono itself.

8188f59

Thanks for the follow-up @Tragetaschen  Nice to see a few of our fixes are of real bugs :smiley_cat:


Unable to get API KEY

http://edmunds.mashery.com/member/my-account
The page for the api key is unavailable

Hi @mrinalraj  I believe mashery apis have been disabled per the announcement on the Edmunds Developer Network page (http://developer.edmunds.com/index.html) this is perhaps why the API key is unavailable.
Sorry for the inconvenience.

@abrahamcuenca Thanks for the information


Updates method with BeforeUpdate hook

GORM Playground Link

https://github.com/go-gorm/playground/pull/345
Description
https://github.com/go-gorm/gorm/blob/master/callbacks/update.go#L12
When calling Updates with struct parameter, BeforeSave hook would get Model parameter, but Updates parameter is expected.

this is the expected behaviour


added XX and YY pol capability to uvbeam.get_beam_areas

a small addition to allow for 'XX' and 'YY' beam power area integrals for UVBeam, which we need in hera_pspec. should be a quick review..

@nkern can you rebase this on master? I think that'll fix the Travis issues.

yup! i'll rebase it and address your comments some point this evening


nixos/podman: Add docker socket support

Motivation for this change
Podman supports the Docker API.
Enable more compatibility options to use podman as a docker replacement.

Make the Podman socket usable via podman group
Add option to symlink from Docker to Podman socket
Add options for networked socket with TLS client certificate authentication

I've successfully deployed with docker-compose via these Docker interfaces all the way to the Podman socket.
It's a promising solution since Podman promises systemd container support and Docker has regressed in this regard.
cc @NixOS/podman
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 123841 at 5b3620f7 run on x86_64-linux 1

1 package failed to build:

nixos-install-tools

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

@GrahamcOfBorg test podman podman-compat

Two quick comments:
Can we test docker compose?
Can you add yourself as a maintainer for the podman compat test (or add yourself to the podman team)?
I'll be able to do a proper review later today.

Can we test docker compose?

That will be a nice addition. I have to do more (unplanned) work on arion as well, so let's not delay this PR.

Can you add yourself as a maintainer for the podman compat test

Done.

(or add yourself to the podman team)?

Thanks, but sadly I'm not in a position to commit to more maintenance responsibilities.

I'll be able to do a proper review later today.

No hurry, I'm going to get some sleep :)

Sorry but that isn't what I meant. Why can't this be handled by generic method via ghostunnel without the needing a podman.networksocket option?

Sorry but that isn't what I meant. Why can't this be handled by generic method via ghostunnel without the needing a podman.networksocket option?

It adds value. You don't have to look up the details of where the socket is, how the ghostunnel syntax works, etc. It provides a single open source solution for this small problem. It also makes the possibility of exposing Podman via TLS discoverable in the NixOS option docs.

I'm a strong no on this as it is, sorry. I don't agree with the opinionated config and having this much of the implementation under the podman module.

Is there some way the networkSocket option can allow for a different proxy, defaulting to ghostunnel, so we can have the best of both worlds (sane defaults and optionality with respect to the choice of proxy)?

Is there some way the networkSocket option can allow for a different proxy, defaulting to ghostunnel, so we can have the best of both worlds (sane defaults and optionality with respect to the choice of proxy)?

That's possible. You could even use the module system's type merging to make it open for extension. I'd lay it out as follows:

podman-network-socket.nix, declaring the options, including a new enum option virtualization.podman.networkSocket.server
podman-network-socket-ghostunnel.nix, extending the server type with "ghostunnel" and conditionally providing the implementation. mkIf (cfg.server == "ghostunnel") etc.

Providing other server integrations will be a matter of adding another module similar to the -ghostunnel.nix one.
If that sounds ok to you, I'll implement it that way.

That sounds reasonable to me. @zowoq How does that sound?

I'd lay it out as follows ...

This sound okay if the networkSocket.server enum option defaults to null so that ghostunnel needs to be explicitly selected, this would make it reasonably clear that it's a third party package/module and not podman itself.
I'll also ask that the test be split so that the core / first-party local socket be tested separately from the non-core / third party network socket. I'm fine with the local tests being added to the current core podman tests, we should also add a TODO for including docker compose test as part of the core tests as well.

if the networkSocket.server enum option defaults to null so that ghostunnel needs to be explicitly selected,

Done, but the default is unset rather than null. This has the same effect, but won't let people set null, because that is not a server.

:tada: Thank you so much @zowoq!

@roberth Do you happen to recall why the tmpfiles rule is configured to only run on boot? (L! vs L)
Just checking that there's a reason. If so, I may do a PR to mention in the option description so people know to reboot.

only run on boot? (L! vs L)

I don't recall and it may well be a mistake.


Attach nodes on both parts

[x] need adjustment.
[ ] might want to consider using grip pads if serenity is installed.

part.cfg's have been updated


cleanup

Cleans up AUTHORS and CHANGES.rst (as well as a series of other files) in preparation for a v0.7 release (#29).

@tonybaloney thanks for the merge. I'll keep checking up on the status of pip to see if there's a proper way to address the current Travis CI builds [1] (assuming that is the main reason why it's failing).


Speeeeed.

Strippy struggles with tons of keys unique keys because it checks each one to ensure it's new. Strippy is also very male at the moment and unable to focus on more than one thing at once (Super Synchronous).
Options for more power:

We could do away with the unique check entirely, and that might help with performance.
Fork for key finding, consolidate and fork again for sanitisation.
Reducing complexity.

Some mixture of the above would work well, I find the forking solution (and a nice looking tui) particularly appealing.

the forker branch successfully implements the second option with powershell jobs.
We were able to successfully sanitise 1.2GiB of DCRUM logs in ~3 hours. Most of the time was spent on actually doing the replacing of strings.

This could be considered closed for now. I don't think we'll run into further performance problems.


Misc. Improvements to Support Offline Areas

This PR contains a couple of miscellaneous improvements to support the offline imagery feature.
Specifically, it contains the following changes:

Add a getViewport method to the MapAdapter
Rename FileDownloadWorker to TileDownloadWorker

These are prerequisite to downloading tiles, but I still have some questions on our approach to rendering tiles and felt that keeping these PRs separate will help keep that conversation focused.

Thanks Scott! checkStyle is failing - could you try running locally to see what's up?

Thanks for the fixes! LGTM - I'll approve as soon as checkStyle errors are fixed!

Fixed! Indentation issue.


No longer builds on OS X

Looks like latest ARM64 merge has broken things for me on OS X and Linux:
$ go get -u github.com/cespare/reflex
# github.com/kr/pty
../../../github.com/kr/pty/ztypes_arm64.go:7: _C_int redeclared in this block
	previous declaration at ../../../github.com/kr/pty/ztypes_amd64.go:7
../../../github.com/kr/pty/ztypes_arm64.go:8: _C_uint redeclared in this block
	previous declaration at ../../../github.com/kr/pty/ztypes_amd64.go:8

Oups, sorry about this. My fault. I tested only on linux/arm64.. Will get fixed asap.


add latest pedantic lints

Have I already asked why we don't just include their analysis_options.yaml directly?

You have. Because we'd have to add a pubspec to the root of the repo – I think...


Beaglebone

Hi I just wanted to make sure this code/the examples worked as shown with the BBB without modification, or if the Adafruit_GPIO library needed to be replaced with Adafruit_BBIO or something. Thanks!

Yep this will work as is with the BeagleBone Black.  It will use the BBIO library for GPIO access and the normal python-spidev module for SPI access.


Update mattermost-api.md

@neflyte thought something along the lines of these changes might make the conversation around rest vs driver easier.

Summary

Ticket Link

@neflyte, just a draft to communicate how this might be used.  Its just for your info.


Fix hardcoded camera source in async LocalParticipant.set

Hi, I found this bug in the Local Participant async extension.
The source was hardcoded as .camera by mistake and the actual parameter is unused.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Search offset and added missing API key

Hello :)
Supposing two changes:
1. Added search offset
I was implementing a paged gif search and there is already a pos parameter in the internal SDK api but not passing outside. So I added API for that.
2. Missing API Key on category list
Not sure what happened here, but the Key is missing here for some reason. Updating to the master branch it also stopped working for me while the pub.dev version still works. So keep an eye on that if I am wrong with my thought here :D
Regards and have a nice weekend!

@justkawal any chance for review? 🙃

@

@justkawal any chance for review? 🙃

@justkawal any chance for review? 🙃

Sure brother


Embedded Dashboards

Can we send external parameter with the embedded charts or Dashboards ?

what is an external parameter? what do you want to achieve?

Hello ,
I want to embedded the dashboard or the charts into our product.
1)Can I embedded it into our product with the embedded option provided ?
2) if yes , can we send external parameters with it , for example :can I
send a specific request like just show the no. of male in India then it
should show the count specific to India from the world gender database from
my product/in the product?
On Thu, Sep 22, 2016 at 2:00 PM, Riccardo Magliocchetti <
<EMAIL_ADDRESS>wrote:

what is an external parameter? what do you want to achieve?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/airbnb/caravel/issues/1170#issuecomment-248841961,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATFd9zvxiWZUJL1XUxP2SQGj37pylReGks5qsjyOgaJpZM4KDoWU
.

--
Thanks & Regards,
Name: Mohammed Attaullah Khan
email id<EMAIL_ADDRESS>contact number:+91-8123030179

Is it even possible to get the embed code of a superset dashboard?. It will be fantastically awesome if this is possible @alexism @attahkhan016 @xrmx @sco @schleyfox

you can render the dashboard into an  if you want, add the ?standalone=true to the URL if you don't want the Superset menu bar to render.

Thanks so much @mistercrunch. But how do I get superset menu bar to render?

you don't add ?standalone=true

It seems that ?standalone=true just work with slices, but not with dashboards

Howdy! Similar to the original reporter, I want to embed dashboards into a separate product.
How do I, as @mistercrunch suggested, "render the dashboard into an " while avoiding the need to login to Superset?

@diego-d5000 you may want to use &standalone=true if there's already a ? in the url

@bilalakil you should open a new issue for this as it's a different subject altogether, closing this one as I just tested and standalone works just fine

@bilalakil, I am very much interested in your question about how to render private dashboards into an iframe while avoiding the need to login to Superset.
Did you open a new issue or did you find a solution to this?
Please let me know how you solved it.
Thank you

@bilalakil @joseph-luketelo I am also interested in this problem.

Unfortunately I never overcame this problem 🙁 Can't remember where I left off at, as it was a long time ago too. Afraid I can't help.
P.S.: @joseph-luketelo I thought I responded to your question a week ago, but apparently responding through email doesn't work (even though GitHub provides instructions to respond via email)? Oops

@bilalakil I did not see your response! But thank you for getting back to us. I also never figured out how to solve this problem up to date.

@bilalakil hi, though its been years
hope this article helps.
https://medium.com/@sairamkrish/apache-superset-custom-authentication-and-integrate-with-other-micro-services-8217956273c1

@bilalakil hi, though its been years
hope this article helps.
https://medium.com/@sairamkrish/apache-superset-custom-authentication-and-integrate-with-other-micro-services-8217956273c1


❓ [Question]: How to change the font in the video ?

Your Question
How to change the font in the video ?
and how to hide the text at all

see this
https://github.com/RayVentura/ShortGPT/issues/73#issuecomment-1663784546


phd2: add GApps wrapper to fix breakage on non-nixos wayland systems

Motivation for this change
As a gtk application, phd2 should include wrapGAppsHook as a native build input to prevent breakage on some system configurations.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 107416 run on x86_64-linux 1

1 package built:

phd2


Error obtaining access token

I recently (in the last few weeks) started getting the following error in my development environment when trying to obtain an access token for Azure SQL using AzureServiceTokenProvider:
Parameters: Connection String: RunAs=App;AppId=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, Resource: https://database.windows.net, Authority: https://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx. Exception Message: Tried to get token using Managed Service Identity. Access token could not be acquired. A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80)
The code is obtaining the access token is
accessToken = await new AzureServiceTokenProvider($"RunAs=App;AppId={_appId}")     .GetAccessTokenAsync("https://database.windows.net", _tenantId);
This works perfectly well when I publish the application to an App Service - and previously worked in the development environment for many months (with or without the ASTP connection string). I've tried every troubleshooting suggestion I can find online for similar issues - but none work. Suggestions I've tried include:

Updating Visual Studio to the latest version.
Updating from .NET Core 3.1 to .NET 5
Updating all Nuget packages to the latest version.
Allowing all three methods of getting an access token to be tried (this was the original setup before the problems started).
Changing the configuration of Azure CLI to return JSON by default.

With option 4. the full error message becomes:
`Parameters: Connection String: [No connection string specified], Resource: https://database.windows.net, Authority: https://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
Exception Message: Tried the following 3 methods to get an access token, but none of them worked. Parameters: Connection String: [No connection string specified], Resource: https://database.windows.net, Authority: https://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
Exception Message:
Tried to get token using Managed Service Identity. Access token could not be acquired. A socket operation was attempted to an unreachable network. (<IP_ADDRESS>:80) Parameters: Connection String: [No connection string specified], Resource: https://database.windows.net, Authority: https://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
Exception Message:
Tried to get token using Visual Studio. Access token could not be acquired. Exception for Visual Studio token provider Microsoft.Asal.TokenService.exe :  Parameters: Connection String: [No connection string specified], Resource: https://database.windows.net, Authority: https://login.microsoftonline.com/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
Exception Message:
Tried to get token using Azure CLI. Access token could not be acquired. Token response is not in the expected format. Exception Message: Expecting element 'root' from namespace ''.. Encountered 'None'  with name '', namespace ''.`
I don't believe it's a bug in my code or Azure configuration because - as I say - all works fine when published to an app service. Somewhat at my wit's end with this one: can anyone help?

//cc: @nonik0, @anaismiller

Thank you for your feedback.  Tagging and routing to the team members best able to assist.

Hmm, that is interesting; I have not seen this issue before.
When AzureServiceTokenProvider is called, it looks for an identity to use to get the tokens. Are you perhaps logged into multiple accounts and so in different assemblies, it picks up a different account? And this doesn't happen when running in the App Service as there is only one identity there to use.

Hi Anais,
I am working with multiple accounts,  so that's definitely a possibility.
Best regards,
Charles
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Anais Miller @.>
Sent: Tuesday, March 30, 2021 11:28:39 PM
To: Azure/azure-sdk-for-net @.>
Cc: Charles Southey @.>; Author @.>
Subject: Re: [Azure/azure-sdk-for-net] Error obtaining access token (#19914)
Hmm, that is interesting; I have not seen this issue before.
When AzureServiceTokenProvider is called, it looks for an identity to use to get the tokens. Are you perhaps logged into multiple accounts and so in different assemblies, it picks up a different account? And this doesn't happen when running in the App Service as there is only one identity there to use.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-sdk-for-net/issues/19914#issuecomment-810620467, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQJIWG2HQF76WEFWPJKHWILTGJGBPANCNFSM42AGWRHQ.

Alright, then can you open the common shared library, authenticate with the account you want, then run your different assembly code and see if that fixed your issue?

@Contengo , do you have any updates to share?

Hi,
Sorry,  had put this on hold for a while. Could you let me know the exact steps to follow to try your suggestion below? I wasn't exactly sure what you meant.
Thanks,
Charles
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Anais Miller @.>
Sent: Wednesday, April 7, 2021 7:48:54 PM
To: Azure/azure-sdk-for-net @.>
Cc: Charles Southey @.>; Mention @.>
Subject: Re: [Azure/azure-sdk-for-net] Error obtaining access token (#19914)
@Contengohttps://github.com/Contengo , do you have any updates to share?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-sdk-for-net/issues/19914#issuecomment-815142818, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQJIWGZIC2J67C5SS4PJJPTTHSSJNANCNFSM42AGWRHQ.

You mentioned that you have multiple accounts and the authentication flow is in a different project.
I am thinking what is happening is a different account without access is being used to get the token. So you have to try and get the right account to do the access. You can try using AzureCli and logging in to only that one account and signing out of your others or with VS, make sure that the tokens are only being requested from that one account and not any other.

@Contengo, may I close this issue? Have you resolved your issue?

Hi Anais,
Apologies for not responding to this earlier: I am working on multiple projects and had to park this one for a while.
I see you have closed the ticket, but the problem is not solved. I have found a couple of interesting things about it – including a workaround (a bit clunky, but it at least means I can continue with development):

As I mentioned before, the problem only occurs when the code calling GetAccessTokenAsync is in a separate .dll file (shared library) from the application being debugged.
If I put a breakpoint on the line which makes that call, then use a Quick Watch window to manually evaluate “provider.GetAccessTokenAsync("https://database.windows.net", _tenantId).Result”, it successfully returns an access token and I can then remove the breakpoint and continue for the rest of that debugging session.
If, however, I re-start the application the problem returns unless I do the same thing again.

The fact that the problem does not arise in the Quick Watch window, but does if I try to let the code run through without a breakpoint, indicates to me that there must be an underlying bug in this part of the system when running in an environment with multiple Microsoft IDs registered.  The behaviour of the Quick Watch window should surely be the same?
There is another problem with the Visual Studio handling of multiple Microsoft accounts that might be related to the above, but I’ve tried to eliminate it as a factor: in the customer domain I’m working with there is a main Active Directory tenancy, plus there is also a B2C tenancy that I created a while back but am not using. I can no longer access the B2C tenancy because I changed phones and did not re-register the B2C account on Authenticator on my new phone (but it seems I am the only administrator so can’t delete it).
I was struggling for a while to understand why, when I try to “Refresh Credentials” for the account I have on this domain it claims to have sent an authentication request to my Microsoft Authenticator app, but none appears in the app and I can’t log in. I’ve realised it’s almost certainly because, when I try to add the account in Visual Studio I am not asked for a specific Azure tenancy, only a username and password, and I strongly suspect that Visual Studio is defaulting to the B2C version of the identity which I can no longer access.
I have put in a support request to delete this unwanted B2C directory, which will hopefully mean that I can have two Microsoft Identities in Visual Studio without problems – I will let you know if that makes any difference to the problem above.
In general the underlying problem here is that the system is always trying to guess which tenancy I’m trying to use and getting it wrong – I would far rather we have the ability to specifically set which one we’re working with – either within Options or by prompting me  when I run. Users of Visual Studio are software developers – we are generally technical enough to be able to pick the right tenancy if asked – this whole “School or Work Account” thing is too dumbed down – not least because it doesn’t actually work.
Best regards,
Charles
@.***D744CC.93B0E5A0]https://contengo.net/
@.***D744CC.93B0E5A0] https://www.linkedin.com/in/charlessouthey/ @.***D744CC.93B0E5A0] https://www.facebook.com/contengo.net @.***D744CC.93B0E5A0] https://twitter.com/ContengoLtd
From: Anais Miller @.>
Sent: 08 April 2021 19:39
To: Azure/azure-sdk-for-net @.>
Cc: Charles Southey @.>; Mention @.>
Subject: Re: [Azure/azure-sdk-for-net] Error obtaining access token (#19914)
You mentioned that you have multiple accounts and the authentication flow is in a different project.
I am thinking what is happening is a different account without access is being used to get the token. So you have to try and get the right account to do the access. You can try using AzureCli and logging in to only that one account and signing out of your others or with VS, make sure that the tokens are only being requested from that one account and not any other.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/Azure/azure-sdk-for-net/issues/19914#issuecomment-816051332, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQJIWG57X5YODW74FZ4MRTDTHXZ3NANCNFSM42AGWRHQ.


Update sgx_tcrypto_helper to support MesaTEE

As talk in this issue: apache/incubator-teaclave#196, I update the tsgx_tcrypto_helper.
The compiling and running result show sgx_tcrypto_helper works fine.

I'm okay with others. @dingelish, if there is no other issues. This PR is ready to merge.


"JAX array is set a static" warning is raised unwantedly

As of Equinox 0.11.6 and https://github.com/patrick-kidger/equinox/pull/800, the following MWE raises a UserWarning: A JAX array is being set as static! This can result in unexpected behavior and is usually a mistake to do.
import numpy as np
import equinox as eqx

class Foo(eqx.Module):
    x: tuple[int, int] = eqx.field(static=True)

    def add_one(self):
        x_as_np = np.asarray(self.x)
        return Foo(tuple(x_as_np+1))

x = (3, 2)
foo = Foo(x)
foo.add_one()
# UserWarning: A JAX array is being set as static! This can result in unexpected behavior and is usually a mistake to do.

This means that one cannot perform numpy operations (which is often simpler than writing them in plain python) on a static attribute. This is a use-case we have in dynamiqs, see for instance the method __mul__ of this class which represents an array in diagonal (DIA) sparse format. Note that we intentionally use numpy instead of jax.numpy to have "static" logic.

A simple fix would be to replace is_array with is_jax_array (i.e. isinstance(..., jax.Array)) in
https://github.com/patrick-kidger/equinox/blob/804d82e0fe65f85dd9f9a21f03d2784c164bbf8d/equinox/_module.py#L585
but I'm not sure this is in line with the intended use.

I would say this behavior is expected (whether not it is wanted maybe another question). Since in general numpy arrays are not hashable, and making things static is to set them as aux data in the pytree (https://github.com/patrick-kidger/equinox/blob/main/equinox/_module.py#L946), which expects hashability since "JAX sometimes needs to compare treedef for equality, or compute its hash for use in the JIT cache, and so care must be taken to ensure that the auxiliary data specified in the flattening recipe supports meaningful hashing and equality comparisons." (https://jax.readthedocs.io/en/latest/pytrees.html). This can sometimes cause silent or (speaking from personal experience) confusing errors, which is why I wanted to add the warning.
I agree, at the least, that the warning message is wrong because a JAX array isn't being set static (a numpy array is), so matching the message to the check should be done. As for numpy arrays, I think they were included originally because of their hash problems (to quote @/ jakevdp "Neither np.ndarray nor jax.Array satisfy this, so they should not be included in aux_data. If you do include such values in aux_data, you'll get unsupported, poorly-defined behavior."). That being said, there definitely are cases where using static arrays can be fine and correct (which is why the warning can be ignored as opposed to error), and if these cases are very common then the warning could be a burden. WDYT?

But in our example, the numpy array is just an intermediary for the computation. The actual computation is starting with a static tuple, and returning a static tuple, hence why I don't find that this should be an expected warning.
Also, I don't really see a way around it. The warning is being raised upon the class creation, so I don't see how we could filter this warning. In the case of our library, this will be raised everytime we make an operation on our class, and we really cannot make this class attribute not static.

Actually, investigating more, the following works without warning:
import numpy as np
import equinox as eqx

class Foo(eqx.Module):
    x: tuple[int, int] = eqx.field(static=True)

    def add_one(self):
        x_as_np = np.asarray(self.x)
        x_as_np += 1
        x = tuple([i.item() for i in x_as_np])
        return Foo(x)

x = (3, 2)
foo = Foo(x)
foo.add_one()
# no warning

So what's being detected in the first example is that the tuple elements are of type np.int instead of int.

Hmmm I see it yea I misread it, it's a int64 class from numpy. That would be an mis usage of the is_array then, because np.int64's are hashable. I can just add a flag to exclude basic numpy dtypes to the check (maybe just excluding numpy generics from checking, are they all hashable?).


Update README.md

Update domain Join section to match actual requirements.
the main page documentation was using an old object format while 20-DomainJoin has the new format. This correct that error.

Actually, just saw you removed it from 20. Ignore!


No license

I know I know, this is experimental code which you're not taking seriously, but it actually works pretty good. Like Meshlab level but fewer params. Easily better than https://github.com/huxingyi/isotropicremesher
But. Wondering what the license is?

Hi Ben, glad to hear! As you say it’s not something I’m supporting, it was to try out a few sentence description of a remeshing strategy I read in a long forgotten (to me anyway) paper.However, if people find it useful I don’t want to needlessly lock it down for lack of a license. I will update it to be MIT.On Jul 31, 2024, at 10:14 AM, Ben S. @.***> wrote:
I know I know, this is experimental code which you're not taking seriously, but it actually works pretty good. Like Meshlab level but fewer params. Easily better than https://github.com/huxingyi/isotropicremesher
But. Wondering what the license is?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Thank you kindly mister.


[BEAM-7714] [BEAM-7257] Split Python 3 postcommits into several Jenkins jobs.


Publish asciidoc mode for codemirror

Hi ,
First i wanna thank you for this useful mode, i'll be using it in ghost,  i was wandering if you could publish it as an npm module. As i've been informed it has been also successfully used in hubpress.io ( an application to build a blog on github ). So making it available in npm or bower etc... could be useful to more people.
It would be great to have it referenced also in the codemirror website among other language syntax mode.
Thanks you

Agreed, this is useful for other people as well. However, this mode is the great work of Thadee Tyl from this https://github.com/espadrine/ace2cm project.
Would you mind asking the original author about publishing? I already mentioned his name at the bottom of the README, but  will also add a link to his project.

@nerk, as I understand it, you used his tool (ace2cm/convert.js) to transform the Ace mode into a CodeMirror mode, correct? If that's the case, then I think we have full rights to the output. The license of Ace is BSD. In the header of the generated file, we should of course credit Ace as the origin of the mode and Thadee for creating the converter.
Ideally, we should try to get AsciiDoc support in CodeMirror. Perhaps the first step is to try to contribute it upstream. If that doesn't work out, we can create a separate project in asciidoctor.
Thomas, would you be willing to submit a pull request to CodeMirror? https://github.com/codemirror/CodeMirror

@mojavelinux @espadrine Yes, I used this tool to generate the file and manually changed/fixed two or three things, like adding asciidoctor specific support for an additional header level.
Getting this into CodeMirror would be the preferred way to go, I agree. I'll take care of the pull request.

Here is what @marijnh told me when I offered to contribute it to CodeMirror: https://twitter.com/marijnjh/status/465903643095752704.
If there is a way out, I believe it would require a change in the converter. It currently includes code from Ace for compatibility reasons (rewriting the code from scratch so that it keeps the same behaviour, quirks included, is hard).
At any rate, it would help if we included someone from Ace in the conversation. @nightwing, do you know who to contact on the subject of licensing from Ajax.org?

That even sounds as if I would need to change the license of the Brackets plugin to BSD if I want this file being part of it... :-(

There's a persistent misunderstanding (aka fear) about licenses that may never be eradicated. It's perfectly fine to include the source code from another project that is BSD into your MIT-licensed project, so long as you mark the original code with the original license (i.e., meet the requirements). You just can't change the BSD license on that file without the author's permission. That file will always be under that license, but it doesn't taint the source code of your whole project.

It seems to me like the author of CodeMirror doesn't want to include a mode that came from Ace. That gives us reason to create our own repository. Eventually, when we rewrite the CodeMirror mode from scratch (as we will probably do eventually to get more accuracy), then we can contribute it to CodeMirror as original work. Given that I've written a parser for AsciiDoc, I'm pretty sure I can manage to make a CodeMirror mode :)

@espadrine you can contact<EMAIL_ADDRESS>I think sharing language modes between Ace and CodeMirror would benefit both editors.

If there is a way out, I believe it would require a change in the converter. It currently includes code from Ace for compatibility reasons (rewriting the code from scratch so that it keeps the same behaviour, quirks included, is hard).

Codemirrors simplemode seems to be compatible with ace modes.

@mojavelinux What you are saying regarding BSD licensing makes perfect sense. If it would be any different, why would it be allowed to integrate BSD licensed stuff into proprietary commercial applications? I will just mention the appropriate  BSD license in the README.
Having a nice, more accurate mode we can share and contribute to CodeMirror would be great. We just need to find somebody to do it. I actually don't want to take ownership of this - so much other cool things I am interested in, so little time. ;-)

If it would be any different, why would it be allowed to integrate BSD licensed stuff into proprietary commercial applications?

The fact that the code for our project is always available means that we satisfy the basic requirements of most open source licenses, in this case BSD. (We provide copyright and license information). If someone were using this project in a proprietary license, it is they who would have to deal with the requirements of files that have a different license from the project.
Having said that, both MIT and BSD licensed source can be stuffed into proprietary commercial applications as that's sort of the premise of the licenses (very liberal freedom). See https://tldrlegal.com/license/bsd-2-clause-license-(freebsd).

I actually don't want to take ownership of this

I tend to agree that the best person to work on these matchers is someone who is working on the parser. At the moment, that puts me in the hot seat, but I am working to get more people deeply familiar with the grammar rules so that we have more help.

It seems to me the next step is to setup our own repo for the CodeMirror mode so that, at the very least, we can share the files within our own ecosystem of projects. Once the code is there, we can continue to pursue getting it accepted upstream as a longer-term goal (perhaps because we decide to rewrite it...or perhaps we find another path).
@nerk @anthonny @espadrine Sound like a good plan?

we can share the files within our own ecosystem of projects

We can also track changes to it, file issues, all that good open source stuff.

@mojavelinux Sounds good to me. Does it even make sense  to set up one single common project (or organization?) for the mode stuff of all relevant environments like IntelliJ, Eclipse, Netbeans, Ace, CodeMirror, Sublime, etc. ? Such a project would have to deal with different languages and build environments, though.

I've found that when working on GitHub, discrete repositories always works out better. The issue tracker isn't sophisticated enough to deal with multiple components.

Any news about publishing it as a separate module ?

I think we should go ahead and split it out and let requirements drive how it evolves. We should set the license of that repo to BSD and credit the origin in a NOTICE file (Apache style).
Let's call the repository: asciidoctor/codemirror-asciidoc-mode
@nerk if I setup the repo and give you access, will you import the file?
@SamyPesse why repository layout would work best for you? A reference will do. (Here's a repository structure of a codemirror mode that we could mimic: https://github.com/eldargab/codemirror-markdown-mode)

I think It'd be better to make a Node.js/Browserify package, and publish it on NPM (CodeMirror itself works really well with Browserify and is distributed on NPM).
@mojavelinux codemirror-markdown-mode is not a Node.js package (no package.json).
So basically:
- index.js // The mode itself
- package.json
- LICENSE
- README

with a package.json like this:
{
  "name": "codemirror-asciidoc-mode",
  "version": "1.0.0",
  "description": "Asciidoc mode for CodeMirror",
  "keywords": ["asciidco", "codemirror"],
  "main": "index.js",
  "license": "BSD"
}

Here's the space: https://github.com/asciidoctor/codemirror-asciidoc-mode

I think It'd be better to make a Node.js/Browserify package, and publish it on NPM (CodeMirror itself works really well with Browserify and is distributed on NPM).

+1
I'm familiar with all those tools, so I can definitely help guide us towards that goal.

Let's go ahead and put the source file inside the lib directory and name it asciidoc.js. That makes it easier to pull out of the repository for those that want to consume it ad-hoc.
lib/asciidoc.js
package.json
LICENSE
README.adoc

Since we are publishing to npm, the README should use the Markdown syntax where Asciidoctor supports it (headings, etc).

I'll go ahead and setup all the infrastructure files and @nerk can import the asciidoc.js source file. @nerk, go ahead and create an account on npm if you don't have one yet. When you publish the package the first time, it will create it and make you the admin.

Should we just call the repository codemirror-asciidoc ? That seems to be how things are named on npm.

Awesome!
@mojavelinux Agree, codemirror-asciidoc is better.
BTW, We need this for the next big release of our editor, there will be an awesome new WYSIWYG editor (display of image, links, etc). It currently works very well with Markdown, but there is still work needed on the Asciidoc support.

Awesome!!!
@nerk We'll need to modify the asciidoc.js so that it loads using require. Right now, there is Brackets-specific code in the source file.

Renamed: https://github.com/asciidoctor/codemirror-asciidoc
Basically, the "Usage" section needs to work (it's currently pseudo code), but I've never used CodeMirror so I don't exactly know what that should be.

We need to decide how to fill in the authors section in package.json. I figure that crediting Ace, Thaddee Tyl and Thomas Kern makes the most sense.

@mojavelinux I think the API should look like:
var CodeMirror = require('codemirror');

require('codemirror-asciidoc')(CodeMirror);

So that codemirror will not have to be a dependency of the module; and the mode will work with any codemirror version.
The module can look like:
(function(mod) {
  if (typeof exports == "object" && typeof module == "object") // CommonJS
    module.exports = mod;
  else if (typeof define == "function" && define.amd) // AMD
    define(["codemirror"], mod);
  else // Plain browser env
    mod(CodeMirror);
})(function(CodeMirror) {
  "use strict";

  CodeMirror.defineMode("asciidoc", ...);
});

(It'll also use for direct usage in the browser or AMD).

Thanks @SamyPesse! That's super helpful. I'll do some experimenting and tests on my end so I'm ready to review the code.

@SamyPress  Would you like to take ownership of codemirror-asciidoc?

@mojavelinux @SamyPesse Since you are already at it, the easiest would be if you just grab the asciidoc.js and go ahead.

I got a demo working, so I'm able to test that we got the code right.
@nerk I'll import the initial version as you, then update the code to at the CommonJS / AMD wrapper.

I think we are ready to publish a first version to npm. @SamyPesse can you test the package by running npm pack then npm install to see if it works for your needs. I'll hold off publishing until you validate.
@nerk would you like to publish the mode to npm?
The next step will be to get the ace2cm running as part of the build so that we aren't attempting to modify generated code. I think it would be best if the gulp build started from the ace component and generated the lib/asciidoc.js file from there. I'll open an issue.

@mojavelinux It's working perfectly for us :)

@mojavelinux Yes, I can publish it to npmjs.com. Never published anything before to that site, lets see... @SamyPesse I assume your pull request is OK? I'll merge that first.

@nerk Yes, My PR is correct :) (I'm using the module using require('codemirror-asciidoc');)

@mojavelinux @SamyPesse It's published.

Excellent!
@nerk can you tag the releases in the git repository? In my experience, this is a manual process in the npm world.

I'll be excited to see this make its way into the brackets plugin as an external module.

@mojavelinux OK, I created a 1.0.1 release on github, if that's what you meant. (I previously published and unpublished 1.0.0 to npmjs for testing purposes, but npmjs still remembers that it had a 1.0.0 version and won't let me replace it. So 1.0.1 is the one and only release on npmjs)

That's perfect!


Fix the writeFileWithIdentifier method for Android (correct mode for opening stream)

Needed for correct work in Android >= 10

@yegor-pelykh thanks, did you test it on devices prior to Android 10? I think i would prefer it if the change only applies to >= 10 🤔 below that it's not documented eher t is doing?

@hpoul I tested this version both for Android below 10 (works as before) and for Android above 10 (now works correctly, with the file being truncated if the new file size is less than the current one).
Also, as I quoted earlier in this post:
https://github.com/hpoul/file_picker_writable/issues/23#issuecomment-851246614

I poked around the Android source code for different versions, and found that before Android 10, "w" and "wt" were explicitly being parsed exactly the same in ParcelFileDescriptor, resulting in a bitmask with both MODE_WRITE_ONLY and MODE_TRUNCATE to open the file. Then in Android 10, there was a change and 'w' and 't' are now parsed individually.

Therefore, it will work correctly on previous versions, as in those versions w = wt took place. The Android developers now have  just made the modes clearer.

thanks, but I feel more comfortable only using wt only since android 10. see https://github.com/hpoul/file_picker_writable/issues/23#issuecomment-903306591 and https://github.com/hpoul/file_picker_writable/commit/d2d1da2924548280518da8ba350d4a8d6a45f75b


Redundant OpExport?

There's an OpExport defined in compiler/opcodes.go. Is this redundant?

Haha yup. That's from before I refactor module import.


Spikes in latency from the moment we put event till we pop event on another thread

Hello,
We are observing interesting behavior. I do not have a simple compilable code to show. But in our
more complex project here is what we see. There are only 2 threads - 1 Publisher and 1 Consumer. Both
threads don't have a single sleep/wait/lock and run infinite loop. Each thread takes 100% CPU of
pinned core. Both cores are from the same physical CPU. Those cores are isolated from CentOS so
nothing else is running there.
Disruptor:
Ring buffer has 512 cells.
Publisher:
Publisher posts one event with current System.nanoTime() every 1 ms (i.e. 1000 events per second).
In addition every 3.4 second the publisher posts 300 events at once as a burst (put 1 by 1 with
calling "next(),publish()" 300 times).
Consumer:
Consumer is using your com.lmax.disruptor.EventPoller and measures how fast the event got to
consumer - the time from “event enqueuing” till “event dequeuing”. Consumer collects the "number of
events", "min interval", "sum of intervals for average" and "max interval".
Every 1 second the consumer prints the stats, resets stats and ignores the events for next
1000 ms (by silently draining the ring buffer). So, printouts are printed every 2 seconds
Params:
-verbose:gc
-XX:CompileThreshold=1
-XX:-TieredCompilation
-XX:+PrintCompilation
-XX:+PrintFlagsFinal
-XX:+PrintGCApplicationStoppedTime
-XX:+PrintGCApplicationConcurrentTime
-XX:PrintSafepointStatisticsCount=1
-XX:+PrintSafepointStatistics
-XX:+UseLargePages
-XX:LargePageSizeInBytes=2m
Output after warm up:
I|2016/08/25 16:21:31.509081|EventReader|Test: count=1001, min=177, avg=247, max=337
I|2016/08/25 16:21:33.509146|EventReader|Test: count=1001, min=181, avg=248, max=359
I|2016/08/25 16:21:35.509215|EventReader|Test: count=1300, min=180, avg=13169, max=93801
I|2016/08/25 16:21:37.509283|EventReader|Test: count=1001, min=184, avg=250, max=339
I|2016/08/25 16:21:39.509346|EventReader|Test: count=1300, min=183, avg=13081, max=93254
I|2016/08/25 16:21:41.509414|EventReader|Test: count=1001, min=180, avg=248, max=358
I|2016/08/25 16:21:43.509483|EventReader|Test: count=1001, min=184, avg=249, max=335
I|2016/08/25 16:21:45.509551|EventReader|Test: count=1001, min=179, avg=250, max=343
I|2016/08/25 16:21:47.509618|EventReader|Test: count=1001, min=182, avg=247, max=416
I|2016/08/25 16:21:49.509684|EventReader|Test: count=1300, min=185, avg=13160, max=93679
I|2016/08/25 16:21:51.509750|EventReader|Test: count=1001, min=177, avg=244, max=312
I|2016/08/25 16:21:53.509820|EventReader|Test: count=1001, min=184, avg=251, max=364
I|2016/08/25 16:21:55.509886|EventReader|Test: count=1001, min=182, avg=249, max=350
I|2016/08/25 16:21:57.509958|EventReader|Test: count=1001, min=184, avg=248, max=317
I|2016/08/25 16:21:59.510021|EventReader|Test: count=1300, min=179, avg=13132, max=93486
I|2016/08/25 16:22:01.510087|EventReader|Test: count=1001, min=182, avg=250, max=326
I|2016/08/25 16:22:03.510154|EventReader|Test: count=1300, min=186, avg=12997, max=92852
I|2016/08/25 16:22:05.510222|EventReader|Test: count=1001, min=179, avg=248, max=360
As you can see every moment when we do burst with additional 300 events, the max time
statistics jump from 300-400ns to 100,000 ns. It is about 300x worse latency during spikes.
Could you share your thoughts if there are any options to avoid that 300x times increase? Is
this due to slow cache coherency of 300 cells and volatile cursors? In our code we cannot
always predict the number of events that publisher is about to put to do "next(N)"
instead of "next(1)" N times.
Thank you,
Alex Malko

Can you publish your benchmark code?

Hello.
100 microsecond spikes sounds very much like the delay caused by JVM guaranteed safe-points.
Have you looked at the log output from  -XX:+PrintSafepointStatistics? If you see messages like these:
20.204: no vm operation

then safepoints could be the culprit.
Can you try running again with the following flag (assuming you're using Hotspot):
-XX:+UnlockDiagnosticVMOptions -XX:GuaranteedSafepointInterval=300000

More detail is here:
https://epickrram.blogspot.co.uk/2015/08/jvm-guaranteed-safepoints.html

I added the test app here: https://github.com/onxonx/disruptor_latency_test
This test does not show so large spikes when I add the extra 300 events in bursts. It also jumps but reasonably. So, I will continue searching for the difference between this dedicated test and our larger app with the test.
The only suspicious spike is this:

1,472,238,476,381 [ConsumerThread]: count=1,001, min=161 ns, avg=219 ns, max=341 ns
1,472,238,478,382 [ConsumerThread]: count=1,300, min=148 ns, avg=207 ns, max=344 ns
1,472,238,480,382 [ConsumerThread]: count=1,001, min=160 ns, avg=362 ns, max=142,178 ns
1,472,238,482,382 [ConsumerThread]: count=1,001, min=160 ns, avg=225 ns, max=320 ns
1,472,238,484,382 [ConsumerThread]: count=1,001, min=169 ns, avg=224 ns, max=339 ns

Hi with more tests we found that the spike is not due to disruptor being slow. The spike for "max" with 300 events bursts is only because the consumer is a little slower than publisher - the events backfill. If consuming is 100 ns more expensive than the publishing...then the 300-th event will be processed at least 100*300ns=30,000ns.


Configure privateDnsZoneGroups on key vault (vault - privatelink.vaultcore.azure.net)

Addressed by https://github.com/Azure/ResourceModules/pull/1670


ARROW-10083: [C++] Improve Parquet fuzz seed corpus

Add nested columns, as well as a Brotli-compressed column.

I chose to still use a single seed Parquet file. I'm not sure splitting those examples in several files would make a concrete difference.

Related PR to OSS-Fuzz: https://github.com/google/oss-fuzz/pull/4478

+1.  Not in front my personal computer but I can merge later if you don't get to it first.