Can some of the reusable components be published separately

Some of the components seam to have use cases outside this project. Can they be published separately. E.g.:

low-level bytes library,
serialization and deserialization codecs (e.g. RLP),
various cryptography functions and primatives, and
other helpful utilities

Yes, of course, and they are published to Maven Central. Here:
https://mvnrepository.com/artifact/org.apache.tuweni/bytes/1.3.0
https://mvnrepository.com/artifact/org.apache.tuweni/rlp/1.3.0
https://mvnrepository.com/artifact/org.apache.tuweni/crypto/1.3.0
Others:
https://mvnrepository.com/artifact/org.apache.tuweni/

I added a tutorial to get started with bytes tonight: http://tuweni.apache.org/tutorials/getting-started-with-bytes/
Hopefully it helps you get situated. I am going to close this issue now.

I added a tutorial to get started with bytes tonight: http://tuweni.apache.org/tutorials/getting-started-with-bytes/
Hopefully it helps you get situated. I am going to close this issue now.


T-SNE

Why is the graph I generated from energy data running like this
![image](https://github.com/abudesai/timeVAE/assets/149740828/29fec225-29a2-4701-bafd-60443601ff2d
![屏幕截图 2024-05-17 092813](https:

//github.com/abudesai/timeVAE/assets/149740828/48ed3a52-eca8-48f8-88b8-e642676de0e5)
ori_data = np.asarray(X)
generated_data = np.asarray(samples)

can you share your energy dataset?

It's the dataset in your code

https://github.com/abudesai/timeVAE/blob/main/datasets/energy_subsampled_train_perc_10.npz
Is there a problem with my T-SNE code. I am using the visualization code from Timegan, and the original data is scaled trained data. The generated data is the data after normal distribution sampling.

Hello, is it possible to compare the data generated after sampling the heavy normal distribution with the training data in a t-sne plot

I have updated the repo. Sorry, it's a major overhaul because we are now planning to work on the next version of TimeVAE so we wanted to clean things up.  If you run src/vae_pipeline.py, it will run through all the datasets, train the model, generate samples, and create and save the t-sne plots for each dataset.


ENG-11747: Add resource and datasource for new "log management" integration

Description of the change
There are new generic APIs that will be used for CRUDing all types of log integrations. The changes in this PR are meant to Support this new API in Terraform Provider.
Type of change

[ ] Bug fix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklists
Development

[x] Lint rules pass locally
[x] The code changed/added as part of this pull request has been covered with tests
[x] All tests related to the changed code pass in development

Code review

[ ] This pull request has a descriptive title and information useful to a reviewer. There may be a screenshot or screencast attached
[ ] Jira issue referenced in commit message and/or PR title

Testing
Note: enable_audit_logs changed to receive_audit_logs, but the tests keep passing.
I created the respective resource:
resource "cyral_integration_logs" "int_logs" {
  name              = "myintegrationtest"
  enable_audit_logs = true
  config_scheme {
    elk {
      es_url     = "http://es.com"
      kibana_url = "http://kibana.com"
      es_credentials {
        username = "gabriel"
        password = "password"
      }
    }
  }
}

I ran terraform initand terraform apply
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # cyral_integration_logs.int_logs will be created
  + resource "cyral_integration_logs" "int_logs" {
      + enable_audit_logs = true
      + id                = (known after apply)
      + name              = "myintegrationtest"

      + config_scheme {
          + elk {
              + es_url     = "http://es.com"
              + kibana_url = "http://kibana.com"

              + es_credentials {
                  + password = "password"
                  + username = "gabriel"
                }
            }
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

cyral_integration_logs.int_logs: Creating...
cyral_integration_logs.int_logs: Creation complete after 3s [id=XXXXXXXX]

After this I ran terraform show
# cyral_integration_logs.int_logs:
resource "cyral_integration_logs" "int_logs" {
    enable_audit_logs = true
    id                = "XXXXXXX"
    name              = "myintegrationtest"

    config_scheme {
        elk {
            es_url     = "http://es.com"
            kibana_url = "http://kibana.com"

            es_credentials {
                password = "password"
                username = "gabriel"
            }
        }
    }
}

By changing my tf file to:
resource "cyral_integration_logs" "int_logs" {
  name              = "gabriel-test"
  enable_audit_logs = true
  config_scheme {
    elk {
      es_url     = "http://es.com"
      kibana_url = "http://kibana.com"
      es_credentials {
        username = "another-user"
        password = "123"
      }
    }
  }
}

By running terraform apply
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # cyral_integration_logs.int_logs will be updated in-place
  ~ resource "cyral_integration_logs" "int_logs" {
        id                = "XXXXXXXX"
      ~ name              = "myintegrationtest" -> "gabriel-test"
        # (1 unchanged attribute hidden)

      ~ config_scheme {
          - elk {
              - es_url     = "http://es.com" -> null
              - kibana_url = "http://kibana.com" -> null

              - es_credentials {
                  - password = "password" -> null
                  - username = "gabriel" -> null
                }
            }
          + elk {
              + es_url     = "http://es.com"
              + kibana_url = "http://kibana.com"

              + es_credentials {
                  + password = "123"
                  + username = "another-user"
                }
            }
        }
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

cyral_integration_logs.int_logs: Modifying... [id=XXXXXXXXX]
cyral_integration_logs.int_logs: Modifications complete after 2s [id=XXXXXXXX]

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

Result:
# cyral_integration_logs.int_logs:
resource "cyral_integration_logs" "int_logs" {
    enable_audit_logs = true
    id                = "XXXXXXXX"
    name              = "gabriel-test"

    config_scheme {
        elk {
            es_url     = "http://es.com"
            kibana_url = "http://kibana.com"

            es_credentials {
                password = "123"
                username = "another-user"
            }
        }
    }
}

This worked fine, so I tested the data source, by creating a file like:
data "cyral_integration_logs" "list" {
  type = "ELK"
}

After running terraform apply and terraform show:
data "cyral_integration_logs" "list" {
    id               = "6XXXX"
        {
            config_scheme     = [
                {
                    cloud_watch = []
                    datadog     = []
                    elk         = [
                        {
                            es_credentials = [
                                {
                                    password = "123"
                                    username = "another-user"
                                },
                            ]
                            es_url         = "http://es.com"
                            kibana_url     = "http://kibana.com"
                        },
                    ]
                    splunk      = []
                    sumo_logic  = []
                },
            ]
            enable_audit_logs = true
            id                = "XXXXXXX"
            name              = "gabriel-test"
        },
    ]
    type             = "ELK"
}

Then, for testing delete, I removed the cyral_integration_logs resource.
terraform apply:
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # cyral_integration_logs.int_logs will be destroyed
  # (because cyral_integration_logs.int_logs is not in configuration)
  - resource "cyral_integration_logs" "int_logs" {
      - enable_audit_logs = true -> null
      - id                = "XXXXXXX" -> null
      - name              = "gabriel-test" -> null

      - config_scheme {
          - elk {
              - es_url     = "http://es.com" -> null
              - kibana_url = "http://kibana.com" -> null

              - es_credentials {
                  - password = "123" -> null
                  - username = "another-user" -> null
                }
            }
        }
    }

Plan: 0 to add, 0 to change, 1 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

cyral_integration_logs.int_logs: Destroying... [id=XXXXXXXX]
cyral_integration_logs.int_logs: Destruction complete after 2s

Apply complete! Resources: 0 added, 0 changed, 1 destroyed.

After that, if we look for the data source list, the resource was gone.

I tested after addressing the suggestions and it keeps working just fine:)

I retested (manually and using the written tests) after addressing all suggestions and everything is working fine :)
[
go clean -i github.com/cyralinc/terraform-provider-cyral/...
rm -f terraform-provider-cyral_v4.2.0
rm -rf ./out
rm -rf ~/.terraform.d/plugins/local/terraform/cyral/4.2.0
gofmt -w .
mkdir -p out/
# Build for both MacOS and Linux
GOOS=darwin GOARCH=amd64 go build -o out/darwin_amd64/terraform-provider-cyral_v4.2.0 .
GOOS=darwin GOARCH=arm64 go build -o out/darwin_arm64/terraform-provider-cyral_v4.2.0 .
 I don't have permission for that 😓

I address the changes for removing "config" from resource. Instead, we will be using the ConflictsWith for adding mutual exclusion logic.
I made a new test using:
resource "cyral_integration_logging" "int_logs_elk" {
  name               = "gabriel-test_elk"
  receive_audit_logs = true
  elk {
    es_url     = "http://es.com"
    kibana_url = "http://kibana.com"
    es_credentials {
      username = "another-user"
      password = "123"
    }
  }
}

data "cyral_integration_logging" "list" {
  type = "CLOUDWATCH"
}

resource "cyral_integration_logging" "int_logs_cloudd" {
  name               = "gabriel-test_cloud"
  receive_audit_logs = true
  cloud_watch {
    region = "us-east-1"
    group  = "everyone"
    stream = "abc"
  }
}

resource "cyral_integration_logging" "int_logs_datadog_2" {
  name               = "gabriel-test_datadog"
  receive_audit_logs = true
  datadog {
    api_key = "ANYTHING_IS_API_KEY"
  }
}

resource "cyral_integration_logging" "int_logs_fluentbit" {
  name               = "gabriel-fluent_bit"
  receive_audit_logs = true
  fluentbit {
    config = <<-EOF
      [OUTPUT]
      Name         stdout
      Match        *
    EOF
  }
}

After terraform init and terraform apply:
data.cyral_integration_logging.list: Reading...
data.cyral_integration_logging.list: Read complete after 2s [id=XXXXXXXXX]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # cyral_integration_logging.int_logs_cloudd will be created
  + resource "cyral_integration_logging" "int_logs_cloudd" {
      + id                 = (known after apply)
      + name               = "gabriel-test_cloud"
      + receive_audit_logs = true

      + cloud_watch {
          + group  = "everyone"
          + region = "us-east-1"
          + stream = "abc"
        }
    }

  # cyral_integration_logging.int_logs_datadog_2 will be created
  + resource "cyral_integration_logging" "int_logs_datadog_2" {
      + id                 = (known after apply)
      + name               = "gabriel-test_datadog"
      + receive_audit_logs = true

      + datadog {
          # At least one attribute in this block is (or was) sensitive,
          # so its contents will not be displayed.
        }
    }

  # cyral_integration_logging.int_logs_elk will be created
  + resource "cyral_integration_logging" "int_logs_elk" {
      + id                 = (known after apply)
      + name               = "gabriel-test_elk"
      + receive_audit_logs = true

      + elk {
          # At least one attribute in this block is (or was) sensitive,
          # so its contents will not be displayed.
        }
    }

  # cyral_integration_logging.int_logs_fluentbit will be created
  + resource "cyral_integration_logging" "int_logs_fluentbit" {
      + id                 = (known after apply)
      + name               = "gabriel-fluent_bit"
      + receive_audit_logs = true

      + fluentbit {
          + config = <<-EOT
                [OUTPUT]
                Name         stdout
                Match        *
            EOT
        }
    }

Plan: 4 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

   Resources: 4 added, 0 changed, 0 destroyed.

By using terraform show:
data "cyral_integration_logging" "list" {
    id           = "XXXXX"
    integrations = [
        {
            cloud_watch        = [
                {
                    group              = "everyone"
                    log_retention_days = 0
                    region             = "us-east-1"
                    stream             = "abc"
                },
            ]
            datadog            = []
            elk                = []
            fluentbit          = []
            id                 = "XXXXXXXXX"
            name               = "gabriel-test"
            receive_audit_logs = true
            splunk             = []
            sumo_logic         = []
        },
        {
            cloud_watch        = [
                {
                    group              = "everyone"
                    log_retention_days = 0
                    region             = "us-east-1"
                    stream             = "abc"
                },
            ]
            datadog            = []
            elk                = []
            fluentbit          = []
            id                 = "XXXXXXX"
            name               = "gabriel-test22"
            receive_audit_logs = true
            splunk             = []
            sumo_logic         = []
        },
        {
            cloud_watch        = [
                {
                    group              = "everyone"
                    log_retention_days = 0
                    region             = "us-east-1"
                    stream             = "abc"
                },
            ]
            datadog            = []
            elk                = []
            fluentbit          = []
            id                 = "XXXXXX"
            name               = "gabriel-test23"
            receive_audit_logs = true
            splunk             = []
            sumo_logic         = []
        },
        {
            cloud_watch        = [
                {
                    group              = "group2"
                    log_retention_days = 1
                    region             = "us-east-2"
                    stream             = "abcd"
                },
            ]
            datadog            = []
            elk                = []
            fluentbit          = []
            id                 = "XXXXX"
            name               = "tfprov-acc-integration-log-LogsCloudWatchTest"
            receive_audit_logs = true
            splunk             = []
            sumo_logic         = []
        },
        {
            cloud_watch        = [
                {
                    group              = ""
                    log_retention_days = 0
                    region             = ""
                    stream             = "cyral-sidecar"
                },
            ]
            datadog            = []
            elk                = []
            fluentbit          = []
            id                 = "cloudwatch"
            name               = "AWS CloudWatch (default)"
            receive_audit_logs = false
            splunk             = []
            sumo_logic         = []
        },
    ]
    type         = "CLOUDWATCH"
}

# cyral_integration_logging.int_logs_cloudd:
resource "cyral_integration_logging" "int_logs_cloudd" {
    id                 = "XXXXXXX"
    name               = "gabriel-test_cloud"
    receive_audit_logs = true

    cloud_watch {
        group  = "everyone"
        region = "us-east-1"
        stream = "abc"
    }
}

# cyral_integration_logging.int_logs_datadog_2:
resource "cyral_integration_logging" "int_logs_datadog_2" {
    id                 = "XXXXXXX"
    name               = "gabriel-test_datadog"
    receive_audit_logs = true

    datadog {
      # At least one attribute in this block is (or was) sensitive,
      # so its contents will not be displayed.
    }
}

# cyral_integration_logging.int_logs_elk:
resource "cyral_integration_logging" "int_logs_elk" {
    id                 = "XXXXXXXX"
    name               = "gabriel-test_elk"
    receive_audit_logs = true

    elk {
      # At least one attribute in this block is (or was) sensitive,
      # so its contents will not be displayed.
    }
}

# cyral_integration_logging.int_logs_fluentbit:
resource "cyral_integration_logging" "int_logs_fluentbit" {
    id                 = "XXXXXXX"
    name               = "gabriel-fluent_bit"
    receive_audit_logs = true

    fluentbit {
        config = <<-EOT
            [OUTPUT]
            Name         stdout
            Match        *
        EOT
    }
}

(I had old CloudWatch integrations and that's why the Data Source returned a lot of integrations).
After removing things from the .tf file and running terraform apply, it removed the resource just fine
cyral_integration_logging.int_logs_fluentbit: Refreshing state... [id=XXXXXXX]
data.cyral_integration_logging.list: Reading...
cyral_integration_logging.int_logs_datadog_2: Refreshing state... [id=XXXXXXXX]
cyral_integration_logging.int_logs_elk: Refreshing state... [id=XXXXXX]
cyral_integration_logging.int_logs_cloudd: Refreshing state... [id=XXXXXXX]
data.cyral_integration_logging.list: Read complete after 2s [id=XXXXXXx]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  - destroy

Terraform will perform the following actions:

  # cyral_integration_logging.int_logs_fluentbit will be destroyed
  # (because cyral_integration_logging.int_logs_fluentbit is not in configuration)
  - resource "cyral_integration_logging" "int_logs_fluentbit" {
      - id                 = "XXXX" -> null
      - name               = "gabriel-fluent_bit" -> null
      - receive_audit_logs = true -> null

      - fluentbit {
          - config = <<-EOT
                [OUTPUT]
                Name         stdout
                Match        *
            EOT -> null
        }
    }

Plan: 0 to add, 0 to change, 1 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

cyral_integration_logging.int_logs_fluentbit: Destroying... [id=XXXXX]
cyral_integration_logging.int_logs_fluentbit: Destruction complete after 2s
`´`

Here's the automated test suite:

go clean -i github.com/cyralinc/terraform-provider-cyral/...
rm -f terraform-provider-cyral_v4.2.0
rm -rf ./out
rm -rf ~/.terraform.d/plugins/local/terraform/cyral/4.2.0
gofmt -w .
mkdir -p out/
Build for both MacOS and Linux
GOOS=darwin GOARCH=amd64 go build -o out/darwin_amd64/terraform-provider-cyral_v4.2.0 .
GOOS=darwin GOARCH=arm64 go build -o out/darwin_arm64/terraform-provider-cyral_v4.2.0 .
 Please let me know if you have any additional comments!

@ccampo133 removed this here: 56e769e

Retested after the proposed changes and everything is looking fine :)

LGTM @gabfelp


How to have assert modifiers return the value?

Hi! Thanks for this project!
How would I return the value from an assert modifier?
e.g.:
const foo = check.assert.nonEmptyString('bar');

foo is undefined.
I want to have foo be 'bar'.
Is there a combination of modifiers that makes this achievable?
(Motivation: I'm parsing a string and converting it to be a flow-typed object, so being able to verify types inline is desirable)
Thanks!

Awesome! Thanks so much! This is really useful :)
(qq though - does this not constitute a breaking change?)

qq though - does this not constitute a breaking change?

Ehrrm, I figured no because there was nothing document for the return value from assertions, so nothing is broken in that sense. Do you think that was the wrong call?

unlikely people are relying on the return type, as you say it's not documented. It is still a change in public API though, so observing strict semver suggests a breaking change?
(this is arguably just bikeshedding though, maybe this depends on the interpretation of what is public API...what are your thoughts?)

...maybe this depends on the interpretation of what is public API...what are your thoughts?

I've always considered the public API as being whatever is documented publicly I guess, although it's not a strongly-held opinion. In the future maybe I'll be more aggressive about bumping the major rev, it's not like there's been a shortage of breaking changes in this repo.


gtzan_embeddings.py needs to be run twice to work

The first time gtzan_embeddings.py is run on a dataset, it will error out with
Traceback (most recent call last):
vampnet/scripts/utils/gtzan_embeddings.py", line 263, in <module>
    main()
lib/python3.9/site-packages/argbind/argbind.py", line 159, in cmd_func
    return func(*cmd_args, **kwargs)
vampnet/scripts/utils/gtzan_embeddings.py", line 246, in main
    embeddings = np.stack(embeddings)
  File "<__array_function__ internals>", line 180, in stack
lib/python3.9/site-packages/numpy/core/shape_base.py", line 422, in stack
    raise ValueError('need at least one array to stack')
ValueError: need at least one array to stack

Running gtzan_embeddings.py again will generate the plots as expected. It is likely an issue with caching.

(P.S. the script is awesome, thanks for adding it!)

thanks for catching these!! apologies for being slow to reply to issues, have been doing ISMIR stuff the past couple of weeks. I'll hopefully get to fixing these next week :)

No probs at allll.. Have fun at ISMIR! None of these are blocking for us, I just figure I'll report them as they come along.

Fixed with #23.


[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[ ] I have reviewed the styleguide for guidance on my code quality.
[ ] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

@pivotal-david-osullivan - Can you rebase this & run go mod tidy? I don't feel comfortable manually resolving the conflict that popped up here. Otherwise this looks good.


Fix/remove incorrect JSS that uses '$' but does not reference a rule name

Overview
In JSS, a dollar sign references a rule. But in Header/styles.js, many html elements have a dollar sign in front of them, i.e., $a, $svg, etc. This is incorrect, and there are warnings in the console. For more info on this topic, see https://cssinjs.org/jss-plugin-nested/?v=v10.6.0#use-rulename-to-reference-a-local-rule-within-the-same-style-sheet and other online resources.
Action Items

[x] If the JSS rules are still being applied, despite the incorrect syntax, refactor them.
[x] If the JSS rules are not being applied, remove them.

Reference
Some of the console log warnings:
tiny-warning.esm.js:11 Warning: [JSS] Could not find the referenced rule "svg" in ...

Warning: [JSS] Could not find the referenced rule "a" in ...

I'm still looking into this. Some of the $ appear to be necessary while some are superfluous, though there may be a more apt replacement for them.

Closed via #537


'height' key must be a positive integer -- Code Action in c

Describe the bug
First of all thanks for the amazing work i really enjoyed the plugin so far and its a great help in my workflow. Now to the Bug:
When trying to open Code Action in a specific c code line (see steps to reproduce), there is the error message:
Error detected while processing CursorMoved Autocommands for "<buffer=5>":
Error executing lua callback: ...te/pack/packer/start/lspsaga.nvim/lua/lspsaga/window.lua:152: 'height' key must be a positive Integer
stack traceback:
        [C]: in function 'nvim_open_win'
        ...te/pack/packer/start/lspsaga.nvim/lua/lspsaga/window.lua:152: in function 'create_win_with_border'
        ...ack/packer/start/lspsaga.nvim/lua/lspsaga/codeaction.lua:431: in function 'action_preview'
        ...ack/packer/start/lspsaga.nvim/lua/lspsaga/codeaction.lua:203: in function 'set_cursor'
        ...ack/packer/start/lspsaga.nvim/lua/lspsaga/codeaction.lua:60: in function <...ack/packer/start/lspsaga.nvim/lua/lspsaga/codeaction.lua:59>

The code action does not pop up. This seems at least similar to #679 and #684 and although these seem to be fixed by your patch, the error message is still there for me on the newest version.
When I however open Code Action in for example lua or any other c code (even if it is the same warning: "Statement should be inside braces") it opens normal and sometimes crashes when i press arrow down(and it doesnt do that if i 'open' code action twice). It is pretty wierd and i couldnt find the pattern when it fails yet...
Steps to reproduce
My C code example, that fails:
int main(){
	if (1) return -1;
}

which gives the warning:
"Statement should be inside braces (fix available)" on line 2 by
enableing clangd with clang-tidy checks like this in .clangd:
Diagnostics:
	ClangTidy:
		Add: [readability*]

Then try to open code action on that line
Code for crashing when pressing arrow down:
int main(){
	if(0) exit(1);
}

The steps to reproduce are the same for that code
Expected behavior
Open Code Action normally
Neovim version (nvim -v)
v0.8.2
Operating system/version
Arch Linux
Terminal name/version
st 0.8.5
$TERM environment variable
st-256color

Thanks for the quick help! Everything works as expected now. Keep up the good work.


Fixes #148 and resolves #140

Fixes #148 and #140 as well as fixing view distance not fully working.

Guess the title doesn't support issue mentioning, but yeah it fixes #148 and #140

Coul you add the hologram to the help command? The text is located in the util.Constants class.
LGTM otherwise


feat!: Submittable workflow templates. Closes #2007

Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[ ] I have written unit and/or e2e tests for my change. PRs without these are unlike to be merged.
[x] Optional. I've added My organization is added to the README.
[ ] I've signed the CLA and required builds are green.

Closes #2007
This is a work in progress to get feedback from community.

Superseded by #2222


Problem with dependencies for 2.3.0 release

When I try cargo vendor to create a vendor package containing all the dependencies I get the following:
 Downloading ahash v0.3.8
error: failed to sync

Caused by:
  failed to fetch package

Caused by:
  unable to get packages from source

Caused by:
  failed to parse manifest at `/home/michael/.cargo/registry/src/github.com-1ecc6299db9ec823/ahash-0.3.8/Cargo.toml`

Caused by:
  invalid type: string "fat", expected a boolean for key `profile.bench.lto`

Seems like something wrong with ahash? Does getting ahash work for you?

Hi @jubalh
Just tried it on another machine without any issue.
Maybe try upgrading your rustc version to latest stable?  With a newer version it works without problems. Sorry about the noise! Thanks for the help!
openSUSE package is updated :)

No problem, thanks a lot for maintaining the openSUSE package @jubalh


How to create a stream from client 'browser' to server (Not from client to client)?

Hi,
I want to make streaming (video stream) from client 'browser' to a server to enter this stream to another process running on a server, How do that?

Easyrtc does not provide such feature.
You need to look at uploading the recording via websocket or via peerConnection and use Media Source Extensions on client to decode the stream from the peer.

See easyrtc.register3rdPartyLocalMediaStream(stream, streamName) and easyrtc.addStreamToCall(easyrtcId, streamName, receiptHandler)
https://github.com/priologic/easyrtc/blob/master/api/easyrtc_int.js#L1835


welcome page

User profile management, API key provisioning/handling, information, and demos of API consumption.


Emotions + Sensors Mockup

Create 4 groups one per each question:
Mood, Energy, Temperature, Noise

Groups by daily survey


Fix cans that cant be spilled

About the PR
closes #10527
Added Spillable Component to cans and shakers
Added a check to ensure that closed cans do not spill when thrown a short distance
Changelog
:cl:

add: Cans and shakers can now be spilled on floor

Added a check to ensure that closed cans do not spill when thrown a short distance

Do they still explode?

Added a check to ensure that closed cans do not spill when thrown a short distance

Do they still explode?

I wouldn't say they "explode" but when thrown far away, they do open and spill. Not on short distance.


Do not run version check if stdout isn't terminal

In addition to suppressing the version check if running in CI or with the machine flag, suppress it if stdout is being piped or redirected.
Fixes #79202.
Happy to amend this to use one of the other ways proposed in the original issue.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing

If you need help, consider asking for advice on the #hackers-new channel on Discord.

We're not quite sure we should turn this off globally, perhaps a more targeted change to the shell completion commands first?

For example: what if the tool were piping output to a log file, we'd probably still want to see it.

perhaps a more targeted change to the shell completion commands first

Works for me -- because the check now depends on the name of the command, I adjusted DummyFlutterCommand to allow test cases to specify a name other than 'dummy'.


How to disable multiple selection if video item is being selected?

I'm in a state where multiple images can be picked but not multiple videos. This also means, in the multiple selection mode, if any video item is selected the multiple selection needs to be switched to single mode selection.
I'm already using config.library.maxNumberOfItems = 5 to be able to pick multiple media items. But I can't find a way to accomplish the scenario described above.

@NikKovIos , @s4cha can you guys take a look here?

@M-I-N hello!) Sorry, don't have time for this now. Can you fix it and create a MR by yourself?

@M-I-N extremely busy as well at the moment, this looks like a valid use case though. If you can try and take a crack at it yourself, that'd be amazing.


P0 : Update your compileSdkVersion to allow users who target compileSdkVersion 31+ to be able build the app with mixpanel-flutter

Check this thread : https://github.com/flutter/flutter/issues/153281
you need to update your compileSdkVersion

@zihejia important

Done. https://github.com/mixpanel/mixpanel-flutter/releases/tag/v2.3.2, thanks for bringing it up!


command() hangs with default config on OSX w/MacPorts Vim

I'm using Vimrunner under OSX, and it's hanging on start with vim.  I can manually start and interact with a server as expected from the command line.  The specs/config I'm using work fine in Linux.
I was able to get it working with MacPorts's mvim, which is just a wrapper around MacVim.  Unfortunately, that isn't a headless configuration, so it's not a viable long-term solution.
I've created a gist with config details, including the output of both vim --version and mvim --version.  I'd be happy to help test/track this down, but before I dive in there, do you have any ideas?  I've already read all of https://github.com/AndrewRadev/vimrunner/issues/11, which is how I got this far.
Thanks for the gem!  This has really changed how I write plugins.

Since I can't really debug this issue effectively, and it's been a while, I guess I'll go ahead and close it for the moment.


Questions and suggestions

Hey there.
On my go of exploring JavaScript-ish languages,  I came across this language. And so far, I really like what it looks like! Therefore I'd like to make a few suggestions and ask a few questions also.
First suggestion is: Named parameters. This is something that always bothers me in JS:
myfunc({
    foo: "bar",
    id: 3
});
// ...
function myfunc(o) {
    if(typeof o.name == "string" && typeof o.id != "undefined")
        // Code...
    else throw new Error("Arguments supplied wrongly.");
}

And this is only a very simple case here... So I'd like to suggest a named parameter capability:
function myfunc(name, id) { ... }
myfunc(name: "Bob", id: 9):

The AngelScript language for C++ supports this feature by using a smart parser. It sees the colon in the function list and maps the call from name to name - at least, that is how I understood it. If it is exactly like that, I don't know.
Anyway it'd be really cool if this would go into JSPP.
Next on I'd like to ask if JSPP will support the detection of unused functions, classes and other parts, in order to optimize the final code.
Once JSPP reaches a more suitable stage - from the thin README, I am guessing its still under heavy development - I will be making a WebPack loader, that allows JSPP files to be loaded by Webpack.
I singed up for the newsletter and I am looking forward for JSPP! Kind regards, Ingwie =)

I almost forgot - operator overloading. Will this be made possible also?

First suggestion is: Named parameters. This is something that always bothers me in JS

We already support function overloading so this would be redundant and require changes to the parser, pushing release dates back further. It is not a priority, and, as you've mentioned, this is more or less already accomplished in JavaScript using the object literal syntax. It is, frankly, just two more characters to type ({ and }).

Next on I'd like to ask if JSPP will support the detection of unused functions, classes and other parts, in order to optimize the final code.

Yes, this is already complete.

I almost forgot - operator overloading. Will this be made possible also?

Unfortunately, no.

Ah okay, thanks for the reply. :)
Since you are to support a C# like syntax, will this include LINQ?

Beep. Just wanted to close the issue since its not really an issue, and wish you good luck with developing this. Still looking forward to it. :)


UDP Gateway Error

I am facing few issues and ICE getting failed.
UDP Gateway Logs:
12:49:21.499058 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:58439
12:49:21.499178 server.go:202: turn ERROR: Failed to handle datagram: failed to handle Refresh-request from <IP_ADDRESS>:58439: no allocation found <IP_ADDRESS>:58439:[::]:3478

14:50:38.647262 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:59645

and it continues...
When I tried to connect Browser Client to use ICE :
17:22:14.045530 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:35747
2024-02-23 22:52:14.045 IST
17:22:14.045759 turn.go:239: turn INFO: permission denied for client <IP_ADDRESS>:35747 to peer <IP_ADDRESS>
17:22:14.046632 server.go:202: turn ERROR: Failed to handle datagram: failed to handle Send-indication from <IP_ADDRESS>:35747: unable to handle send-indication, no permission added: <IP_ADDRESS>:55136

and then ICE failed.
Can someone help?

Permission denied errors usually mean that the UDPRoute does not cover the destination address. Does the address <IP_ADDRESS>  belong to the backend Service of your UDPRoute? The first issue might also result from the same problem, but you have to elevate the stunnerd logvelel to know more.
ps: please use code blocks in your postings (see the updated question)

IP address <IP_ADDRESS> is the client machine IP (browser) from where we are trying to create RTC Peer Connection.
My Configuration is as follows:
Installation Steps:
1. helm repo add stunner https://l7mp.io/stunner
2. helm repo update
3. helm install stunner-gateway-operator stunner/stunner-gateway-operator --create-namespace --namespace=stunner --version 0.16.0
4. helm install stunner stunner/stunner --namespace stunner

GatewayClass:
kubectl apply -f - <<EOF
apiVersion: gateway.networking.k8s.io/v1beta1
kind: GatewayClass
metadata:
  name: stunner-gatewayclass
spec:
  controllerName: "stunner.l7mp.io/gateway-operator"
  parametersRef:
    group: "stunner.l7mp.io"
    kind: GatewayConfig
    name: stunner-gatewayconfig
    namespace: stunner
  description: "STUNner is a WebRTC media gateway for Kubernetes"
EOF

Gateway Config:
kubectl apply -f - <<EOF
apiVersion: stunner.l7mp.io/v1
kind: GatewayConfig
metadata:
  name: stunner-gatewayconfig
  namespace: stunner
spec:
  realm: stunner.l7mp.io
  authRef:
    name: stunner-auth-secret
    namespace: stunner
EOF

Note: I have followed the example of cloudretro and based on it, I tried to connect with Janus using port 8443

UDP Gateway Logs: (Reverse Order of timestamp so please read from end)
INFO 2024-02-24T10:40:15.439482837Z 10:40:15.439418 server.go:202: turn ERROR: Failed to handle datagram: failed to handle Send-indication from <IP_ADDRESS>:36691: unable to handle send-indication, no permission added: <IP_ADDRESS>:52282
INFO 2024-02-24T10:40:15.439465318Z 10:40:15.439312 turn.go:269: turn DEBUG: Received SendIndication from <IP_ADDRESS>:36691
INFO 2024-02-24T10:40:15.439456777Z 10:40:15.439230 server.go:64: turn DEBUG: Handling TURN packet
INFO 2024-02-24T10:40:15.439395586Z 10:40:15.439070 server.go:39: turn DEBUG: Received 124 bytes of udp from <IP_ADDRESS>:36691 on [::]:3478
INFO 2024-02-24T10:40:14.432141555Z 10:40:14.431805 server.go:202: turn ERROR: Failed to handle datagram: failed to handle Send-indication from <IP_ADDRESS>:36691: unable to handle send-indication, no permission added: <IP_ADDRESS>:52282
INFO 2024-02-24T10:40:14.432134250Z 10:40:14.431767 turn.go:269: turn DEBUG: Received SendIndication from <IP_ADDRESS>:36691
INFO 2024-02-24T10:40:14.432104681Z 10:40:14.431733 server.go:64: turn DEBUG: Handling TURN packet
INFO 2024-02-24T10:40:14.432030251Z 10:40:14.431602 server.go:39: turn DEBUG: Received 124 bytes of udp from <IP_ADDRESS>:36691 on [::]:3478
INFO 2024-02-24T10:40:13.927495573Z 10:40:13.927093 server.go:202: turn ERROR: Failed to handle datagram: failed to handle Send-indication from <IP_ADDRESS>:36691: unable to handle send-indication, no permission added: <IP_ADDRESS>:52282
INFO 2024-02-24T10:40:13.927487546Z 10:40:13.927046 turn.go:269: turn DEBUG: Received SendIndication from <IP_ADDRESS>:36691
INFO 2024-02-24T10:40:13.927478419Z 10:40:13.927033 server.go:64: turn DEBUG: Handling TURN packet
INFO 2024-02-24T10:40:13.927335559Z 10:40:13.927001 server.go:39: turn DEBUG: Received 124 bytes of udp from <IP_ADDRESS>:36691 on [::]:3478
INFO 2024-02-24T10:40:13.926831896Z 10:40:13.926397 turn.go:239: turn INFO: permission denied for client <IP_ADDRESS>:36691 to peer <IP_ADDRESS>
INFO 2024-02-24T10:40:13.926826660Z 10:40:13.926382 handlers.go:91: stunner-auth DEBUG: permission denied on listener "stunner/udp-gateway/udp-listener" for client "<IP_ADDRESS>:36691" to peer <IP_ADDRESS>: no route to endpoint
INFO 2024-02-24T10:40:13.926820523Z 10:40:13.926367 handlers.go:74: stunner-auth DEBUG: permission handler for listener "stunner/udp-gateway/udp-listener": client "<IP_ADDRESS>:36691", peer "<IP_ADDRESS>"
INFO 2024-02-24T10:40:13.926814255Z 10:40:13.926336 handlers.go:30: stunner-auth DEBUG: static auth request: valid username
INFO 2024-02-24T10:40:13.926808638Z 10:40:13.926309 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:36691
INFO 2024-02-24T10:40:13.926801852Z 10:40:13.926254 turn.go:214: turn DEBUG: Received CreatePermission from <IP_ADDRESS>:36691
INFO 2024-02-24T10:40:13.926793626Z 10:40:13.926234 server.go:64: turn DEBUG: Handling TURN packet
INFO 2024-02-24T10:40:13.926717974Z 10:40:13.926176 server.go:39: turn DEBUG: Received 124 bytes of udp from <IP_ADDRESS>:36691 on [::]:3478
INFO 2024-02-24T10:40:13.681387453Z 10:40:13.681239 allocation_manager.go:116: turn DEBUG: Listening on relay address: <IP_ADDRESS>:39081
INFO 2024-02-24T10:40:13.681128045Z 10:40:13.680924 handlers.go:30: stunner-auth DEBUG: static auth request: valid username
INFO 2024-02-24T10:40:13.681113827Z 10:40:13.680901 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:36691
INFO 2024-02-24T10:40:13.681107921Z 10:40:13.680866 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:36691
INFO 2024-02-24T10:40:13.681099667Z 10:40:13.680847 server.go:64: turn DEBUG: Handling TURN packet
INFO 2024-02-24T10:40:13.681030934Z 10:40:13.680807 server.go:39: turn DEBUG: Received 132 bytes of udp from <IP_ADDRESS>:36691 on [::]:3478
INFO 2024-02-24T10:40:13.662016098Z 10:40:13.661706 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:36691
INFO 2024-02-24T10:40:13.662006787Z 10:40:13.661687 server.go:64: turn DEBUG: Handling TURN packet
INFO 2024-02-24T10:40:13.661906171Z 10:40:13.661596 server.go:39: turn DEBUG: Received 40 bytes of udp from <IP_ADDRESS>:36691 on [::]:3478
INFO 2024-02-24T10:26:49.509112758Z 10:26:49.508438 reconcile.go:180: stunner INFO: status: READY, realm: stunner.l7mp.io, authentication: static, listeners: stunner/udp-gateway/udp-listener: [turn-udp://<IP_ADDRESS>:3478<0:0>], active allocations: 0
INFO 2024-02-24T10:26:49.509106539Z 10:26:49.508412 reconcile.go:176: stunner INFO: reconciliation ready: new objects: 0, changed objects: 2, deleted objects: 0, started objects: 0, restarted objects: 0
INFO 2024-02-24T10:26:49.509096964Z 10:26:49.508402 reconcile.go:156: stunner WARNING: running with no clusters: all traffic will be dropped
INFO 2024-02-24T10:26:49.509091083Z 10:26:49.508393 reconcile.go:131: cluster-manager DEBUG: reconciliation ready: to-be-created: 0, changed: 0, deleted: 0
INFO 2024-02-24T10:26:49.509084279Z 10:26:49.508384 reconcile.go:131: listener-manager DEBUG: reconciliation ready: to-be-created: 0, changed: 1, deleted: 0
INFO 2024-02-24T10:26:49.509077332Z 10:26:49.508353 reconcile.go:131: auth-manager DEBUG: reconciliation ready: to-be-created: 0, changed: 0, deleted: 0
INFO 2024-02-24T10:26:49.509026167Z 10:26:49.508279 reconcile.go:112: stunner INFO: setting loglevel to "all:DEBUG"
INFO 2024-02-24T10:26:49.506413Z {"level":"INFO", "msg":"Writing /etc/stunnerd/stunnerd.conf (ascii)", "taskName":null}
INFO 2024-02-24T09:43:03.763212031Z 09:43:03.762883 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:49997
INFO 2024-02-24T09:43:03.752403401Z 09:43:03.752111 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:49997
INFO 2024-02-24T09:43:03.483993022Z 09:43:03.483646 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:49997

$ kubectl -n stunner describe stunner
Name:         stunner-gatewayconfig
Namespace:    stunner
Labels:
Annotations:
API Version:  stunner.l7mp.io/v1
Kind:         GatewayConfig
Metadata:
Creation Timestamp:  2024-02-24T07:42:08Z
Generation:          2
Resource Version:    140886493
UID:                 b1c5d6f3-9121-49d5-abf7-f0a7ccedd5ff
Spec:
Auth Ref:
Group:
Kind:       Secret
Name:       stunner-auth-secret
Namespace:  stunner
Auth Type:    plaintext
Dataplane:    default
Log Level:    all:DEBUG
Realm:        stunner.l7mp.io
Events:
Name:         media-plane
Namespace:    stunner
Labels:
Annotations:
API Version:  stunner.l7mp.io/v1
Kind:         UDPRoute
Metadata:
Creation Timestamp:  2024-02-24T07:42:49Z
Generation:          1
Resource Version:    140758131
UID:                 e27c23f5-3aa3-4d85-8d6f-b9d4134ceb70
Spec:
Parent Refs:
Group:  gateway.networking.k8s.io
Kind:   Gateway
Name:   udp-gateway
Rules:
Backend Refs:
Group:
Kind:       Service
Name:       janus-udp-service
Namespace:  jobma
Events:

So here is the offending log line:
INFO 2024-02-24T10:40:13.926826660Z 10:40:13.926382 handlers.go:91: stunner-auth DEBUG: permission denied on listener "stunner/udp-gateway/udp-listener" for client "<IP_ADDRESS>:36691" to peer <IP_ADDRESS>: no route to endpoint

This means someone with the address <IP_ADDRESS>:36691 is trying to reach a peer, namely <IP_ADDRESS>, they don't have permission to reach. If <IP_ADDRESS> is indeed the browser, then I guess <IP_ADDRESS> is the pod IP of your Janus media server. So what happens is that the media server opens a TURN relay connection on STUNner and tries to send media to the browser via this relay connection. This obviously fails, as  stunnerd cannot reach the private IP of the browser.
Things should occur precisely the other way around: it should be the broswer that initiates the TURN connection and Janus should run with no ICE servers configured at all, see here.
So please remove all ICE servers from Janus config and add STUNner's TURN URI as the only ICE server for your browser and things should just work fine. If you're using the latest master (just reinstall from the "dev" channel and install stunnerctl) then the below would return a valid config that you can use for configuring the PeerConnection on your browser:
./stunnerctl -n stunner auth
{"iceServers":[{"credential":"xxxxxxx","urls":["turn:A.B.C.D:3478?transport=udp"],"username":"xxxxxxx"}],"iceTransportPolicy":"all"}

Ok, I removed ICE servers from the Janus config. But it still didn't work.
One more question to be sure,
For this scenario.
Browser <---->Stunner UDP Route <------> Janus Service (8443 UDP) <-----> Janus Media Server.
Do we need to open 8443 necessarily on Janus Server.?
PS: I am following cloudretro deployment , where a single UDP port has been opened on workers. So I am assuming Janus Media Server as My workers.

2024-02-24 19:57:20.229 IST
14:27:20.228837 server.go:39: turn DEBUG: Received 20 bytes of udp from <IP_ADDRESS>:63891 on [::]:3478
2024-02-24 19:57:20.229 IST
14:27:20.228876 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.229 IST
14:27:20.228889 stun.go:12: turn DEBUG: Received BindingRequest from <IP_ADDRESS>:63891
2024-02-24 19:57:20.262 IST
14:27:20.262127 server.go:39: turn DEBUG: Received 28 bytes of udp from <IP_ADDRESS>:63895 on [::]:3478
2024-02-24 19:57:20.262 IST
14:27:20.262166 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.262 IST
14:27:20.262183 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:63895
2024-02-24 19:57:20.269 IST
14:27:20.269390 server.go:39: turn DEBUG: Received 28 bytes of udp from <IP_ADDRESS>:63887 on [::]:3478
2024-02-24 19:57:20.269 IST
14:27:20.269654 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.269 IST
14:27:20.269697 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:63887
2024-02-24 19:57:20.273 IST
14:27:20.273372 server.go:39: turn DEBUG: Received 28 bytes of udp from <IP_ADDRESS>:63891 on [::]:3478
2024-02-24 19:57:20.273 IST
14:27:20.273499 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.484 IST
14:27:20.484631 stun.go:12: turn DEBUG: Received BindingRequest from <IP_ADDRESS>:63895
2024-02-24 19:57:20.492 IST
14:27:20.492685 server.go:39: turn DEBUG: Received 20 bytes of udp from <IP_ADDRESS>:63887 on [::]:3478
2024-02-24 19:57:20.493 IST
14:27:20.492751 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.493 IST
14:27:20.492764 stun.go:12: turn DEBUG: Received BindingRequest from <IP_ADDRESS>:63887
2024-02-24 19:57:20.495 IST
14:27:20.495646 server.go:39: turn DEBUG: Received 20 bytes of udp from <IP_ADDRESS>:63891 on [::]:3478
2024-02-24 19:57:20.495 IST
14:27:20.495770 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.495 IST
14:27:20.495874 stun.go:12: turn DEBUG: Received BindingRequest from <IP_ADDRESS>:63891
2024-02-24 19:57:20.536 IST
14:27:20.536075 server.go:39: turn DEBUG: Received 28 bytes of udp from <IP_ADDRESS>:63887 on [::]:3478
2024-02-24 19:57:20.536 IST
14:27:20.536111 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.536 IST
14:27:20.536126 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:63887
2024-02-24 19:57:20.536 IST
14:27:20.536624 server.go:39: turn DEBUG: Received 28 bytes of udp from <IP_ADDRESS>:63895 on [::]:3478
2024-02-24 19:57:20.536 IST
14:27:20.536711 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.536 IST
14:27:20.536819 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:63895
2024-02-24 19:57:20.536 IST
14:27:20.536819 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:63895
2024-02-24 19:57:20.539 IST
14:27:20.539145 server.go:39: turn DEBUG: Received 28 bytes of udp from <IP_ADDRESS>:63891 on [::]:3478
2024-02-24 19:57:20.539 IST
14:27:20.539252 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.539 IST
14:27:20.539297 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:63891
2024-02-24 19:57:20.546 IST
14:27:20.546672 server.go:39: turn DEBUG: Received 120 bytes of udp from <IP_ADDRESS>:63887 on [::]:3478
2024-02-24 19:57:20.547 IST
14:27:20.546937 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.547 IST
14:27:20.547119 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:63887
2024-02-24 19:57:20.547 IST
14:27:20.547313 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:63887
2024-02-24 19:57:20.547 IST
14:27:20.547489 handlers.go:30: stunner-auth DEBUG: static auth request: valid username
2024-02-24 19:57:20.547 IST
14:27:20.547819 allocation_manager.go:116: turn DEBUG: Listening on relay address: <IP_ADDRESS>:42391
2024-02-24 19:57:20.550 IST
14:27:20.549984 server.go:39: turn DEBUG: Received 120 bytes of udp from <IP_ADDRESS>:63895 on [::]:3478
2024-02-24 19:57:20.550 IST
14:27:20.550183 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.550 IST
14:27:20.550273 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:63895
2024-02-24 19:57:20.562 IST
14:27:20.562291 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:63891
2024-02-24 19:57:20.562 IST
14:27:20.562422 handlers.go:30: stunner-auth DEBUG: static auth request: valid username
2024-02-24 19:57:20.562 IST
14:27:20.562641 allocation_manager.go:116: turn DEBUG: Listening on relay address: <IP_ADDRESS>:60991
2024-02-24 19:57:20.797 IST
14:27:20.797402 server.go:39: turn DEBUG: Received 120 bytes of udp from <IP_ADDRESS>:63887 on [::]:3478
2024-02-24 19:57:20.797 IST
14:27:20.797496 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.797 IST
14:27:20.797522 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:63887
2024-02-24 19:57:20.797 IST
14:27:20.797593 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:63887
2024-02-24 19:57:20.797 IST
14:27:20.797616 handlers.go:30: stunner-auth DEBUG: static auth request: valid username
2024-02-24 19:57:20.832 IST
14:27:20.832320 server.go:39: turn DEBUG: Received 120 bytes of udp from <IP_ADDRESS>:63895 on [::]:3478
2024-02-24 19:57:20.832 IST
14:27:20.832370 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:20.832 IST
14:27:20.832391 turn.go:18: turn DEBUG: Received AllocateRequest from <IP_ADDRESS>:63895
2024-02-24 19:57:20.832 IST
14:27:20.832428 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:63895
2024-02-24 19:57:20.832 IST
14:27:20.832447 handlers.go:30: stunner-auth DEBUG: static auth request: valid username
2024-02-24 19:57:23.855 IST
14:27:23.854833 turn.go:180: turn DEBUG: Received RefreshRequest from <IP_ADDRESS>:63891
2024-02-24 19:57:23.855 IST
14:27:23.854862 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:63891
2024-02-24 19:57:23.855 IST
14:27:23.854908 handlers.go:30: stunner-auth DEBUG: static auth request: valid username
2024-02-24 19:57:23.868 IST
14:27:23.868637 server.go:39: turn DEBUG: Received 124 bytes of udp from <IP_ADDRESS>:63887 on [::]:3478
2024-02-24 19:57:23.868 IST
14:27:23.868820 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:23.987 IST
14:27:23.986895 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:23.987 IST
14:27:23.986950 turn.go:269: turn DEBUG: Received SendIndication from <IP_ADDRESS>:63887
2024-02-24 19:57:23.987 IST
14:27:23.987036 server.go:202: turn ERROR: Failed to handle datagram: failed to handle Send-indication from <IP_ADDRESS>:63887: unable to handle send-indication, no permission added: <IP_ADDRESS>:42590
2024-02-24 19:57:24.129 IST
14:27:24.129273 server.go:39: turn DEBUG: Received 124 bytes of udp from <IP_ADDRESS>:63887 on [::]:3478
2024-02-24 19:57:24.129 IST
14:27:24.129487 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:24.129 IST
14:27:24.129586 turn.go:214: turn DEBUG: Received CreatePermission from <IP_ADDRESS>:63887
2024-02-24 19:57:24.129 IST
14:27:24.129723 handlers.go:25: stunner-auth INFO: static auth request: username="user-1" realm="stunner.l7mp.io" srcAddr=<IP_ADDRESS>:63887
2024-02-24 19:57:24.129 IST
14:27:24.129790 handlers.go:30: stunner-auth DEBUG: static auth request: valid username
2024-02-24 19:57:24.130 IST
14:27:24.129918 handlers.go:74: stunner-auth DEBUG: permission handler for listener "stunner/udp-gateway/udp-listener": client "<IP_ADDRESS>:63887", peer "<IP_ADDRESS>"
2024-02-24 19:57:24.130 IST
14:27:24.130049 handlers.go:91: stunner-auth DEBUG: permission denied on listener "stunner/udp-gateway/udp-listener" for client "<IP_ADDRESS>:63887" to peer <IP_ADDRESS>: no route to endpoint
2024-02-24 19:57:24.130 IST
14:27:24.130071 turn.go:239: turn INFO: permission denied for client <IP_ADDRESS>:63887 to peer <IP_ADDRESS>
2024-02-24 19:57:30.525 IST
14:27:30.524767 server.go:39: turn DEBUG: Received 20 bytes of udp from <IP_ADDRESS>:63887 on [::]:3478
2024-02-24 19:57:30.525 IST
14:27:30.524874 server.go:64: turn DEBUG: Handling TURN packet
2024-02-24 19:57:30.525 IST
14:27:30.524894 stun.go:12: turn DEBUG: Received BindingRequest from <IP_ADDRESS>:63887

Stunner POD IP:  <IP_ADDRESS>
Janus UDP Service IP: <IP_ADDRESS>

So far, so good. Can you post the output of kubectl -n janus-media describe svc janus-udp-service? We also need the dataplane config: if you're on the stable channel then kubectl -n stunner get cm udp-gateway -o yaml is the command, and if you're using the dev channel then see here.

I think, I am wasting time over a non-reliable github repo. Its not working


LCOE legend

LCOE values are not reflected in LCOE legend -> no variation in pixel coloring on the map

Actually this problem wasn't from the legend itself but because for LCOE layer we have a fixed range for values [80, 300] and with that range in some cases no (or more accurately too little) color variation show up on the map.
This issue has been fixed
Before:

After:

nicely done!
I've tested it for couple countries and it looks good!
One thing I noticed for Offshore Wind is that the layer is under the EEZ layer, making it hard to see; can you move it on top of all other layers?

@akshay2048

hi Akshay, I also included a screenshot - is that not visible? It shows exactly what I expressed in writing. You can also test it yourself -> run the tool for a country for Offshore and (for comparison) for Onshore and compare the result in display for the LCOE layer.
You can also compare the 2 screenshots in my message and Belgacem's message above and notice the difference in the display of the layer, which make the difference very obvious..

@akshay2408 , i simply asked for a change in the order of the spatial layers overlay, meaning to display first the LCOE layer on top of the EEZ border (the transparent polygon) so that it looks similar to the other technologies. This doesnt look good, there is no variation in the LCOE layer color at all, please revert all changes to what Belgacem implemented for the LCOE layer and simply focus on the drawing order of the files

okay @ClaraIV
I have not deployed these changes to staging.
They are only in my local machine, so I will do the suggested changes.

@dimasciput Please review this PR https://github.com/worldbank/WB-rezoning-explorer/pull/27

Hi @ClaraIV
here is the updated UI

thanks, this works well!


how can i write query to get random rows with limit in postgresql using knex?

Environment
Knex version:
Database + version:
OS:
Select applicable tempalate from below.
If issue is about oracledb support tag @ atiertant. For MSSql tag @ smorey2 .
Rest of dialects doesn't need tags.
Bug

Explain what kind of behaviour you are getting and how you think it should do

Error message

Reduced test code, for example in https://npm.runkit.com/knex or if it needs real
database connection to mysql or postgresql, then single file example which initializes
needed data and demonstrates the problem.

Feature discussion / request

Explain what is your use case

Explain what kind of feature would support this

Give some API proposal, how the feature should work

Missing / erroneus documentation
Send issue to documentation repo, or fix it and send PR https://github.com/knex/documentation
Questions about how to use knex
Github issues are for knex development. Please send questions how to use knex to
stackoverflow or ask about it in gitter chat.

Please use stackoverflow for usage questions as is stated in the issue template you left here. Closing as being disrespectful for the OS community + not following rules of knex issues.


Fixed deprecated warn call

Replaced warn() with warning
Summary
This pull request fixes the issue described in 365
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

 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.Alex seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the update @awb1015!

Thanks for taking the time on this PR. But this PR is no longer compatible with the latest source code. Please allow me to close this PR.


change coding style to PSR-2

Coverage decreased (-1.0%) to 95.0% when pulling 0d794c9776d592ec7f292bcfd49ac08a8f5a181a on psr-2 into ee9f8ff42ccbd5cbeffd6587d20a41a857bd44f1 on master.

have no clue why. but will tackle code coverage in an extra pr


added private FQDN

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[x] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[x] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[x] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

LGTM

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

@sergey-shandar can you review this PR? I think I need one more?

@KrisBash are you the right person to review from ARM side?

@ravbhatnagar Please help with this review. This is work scheduled for Ignite.

@sergey-shandar can you help merge it?

@sergey-shandar I removed the example as it will be a duplicate key in swagger. After all, it's the same API as ManagedClusters_Get. Just a variant feature.

@jhendrixMSFT would you be able to help merge it while Sergey is OOF please?


Implement FFT using Apple's Accelerate framework

Implement an FFT based on Accelerate / vDSP, which should be the
fastest possible option on Apple platforms. Well, maybe debatable.
I did find that it was several times faster than PFFFT in the pffft
repository, using their bench_pffft.c process, which I had to extend
to support double precision operations, since the stock version
only supported single precision vDSP for comparison.
PFFFT double in the above comparison mostly scored about 10-14
Gflops on the FFT sizes that r8b is likely to be using, while vDSP
scored from 32 to 60 Gflops on the same filter sizes of real FFT.
The most extreme case was 2Mi sample filter, which slowed PFFFT
down to 4.6 Gflops, while vDSP pulled 29.6 Gflops.
I don't know if this is because SIMD was not being compiled in,
or what. I'll need to try enabling the NEON code path, and see if
it changes the speed of PFFFT for the better.

I'll do my own performance tests to see if it's any good in the context or r8brain-free-src.

Well, whatever other benchmarks show, PFFFT DOUBLE is a lot faster than VDSP in my tests, on Apple M1. VDSP is slightly faster than Ooura FFT. So, I do not see a reason to include VDSP in this form. I think it's possible to get rid of vDSP_ztocD so that things may work faster. But this will take some time to do.

I've also did a benchmark with vDSP_ztocD and vDSP_ctozD commented out, and the improvement is negligible, so the conclusion there's no much need in vDSP. First, it's not widely-available (e.g. on other ARM64), and secondly, PFFFT DOUBLE works faster on Apple M1 which are what both Apple's desktop and mobile processors are going to be, architecturally.

On the other hand, I may add R8B_VDSP macro anyway, just won't describe it on the project page so that users do not automatically use something IMO inferior.

Hmm, I guess I wasted my time, then. Do I need to define any particular macros to build SIMD accelerated PFFFT Double? I need to declare the macros per architecture, unfortunately, since I build a Universal app.

PFFFT DOUBLE expects aarch64, arm64 or __ARM_NEON, see pf_neon_double.h:42. Apple clang defines these per platform automatically.


Add full json schema

Something not quite working after the last change, preview build shows an error for all schema templates (you can still Save & they work fine despite the error)

@sdairs I don't have any errors, try rm -rf node_modules && npm install && cd packages/mockingbird/ && npm run build && cd ../../apps/web/ && npm run dev

@radchukd this is on the Vercel preview build https://mockingbird-web-git-feat-add-full-jsonschema-tinybird.vercel.app/

@sdairs I don't have this error there as well. I tried tinybird and upstash and all the schemas. 🙃

It's stopped doing it for me now as well 🤨


Suggestion about PojoPropertyBuilderFactory: Change the alerts about Jackson 2.6 compliance

Hi, first of all thanks for the awesome work you all have done!
I just like to ask for changing the alert when PojoPropertyBuilderFactory  tries to instantiate jackson in 2.6 version.
When we are in troubleshooting for any reason, springfox give us a lot of "false positive" messages in our logs on application startup. I'd like to suggest, change the way of this log. As it is a debug message, I think it's not relevant to print the stacktrace every single time the method jackson26Instance  is called.
May be the best way to do that is just log Unable to instantiate jackson 26 object  without the exception stacktrace. Another suggestion is implement a way to try instantiate only once in jackson 2.6. I guess, if the exception was catched once, there is no reason to try again using this version, a simple flag can solve that.
Thanks!

Thanks for pointing that out. Would you be able to submit a PR/patch for that. Would be a great help and glad to accept it.


pypi: support updating resources for git clones

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

This teaches brew update-python-resources how to handle a formula with a git url, like arcade-learning-environment.
Before:
$ brew update-python-resources arcade-learning-environment
Error: Unable to determine metadata for "https://github.com/mgbellemare/Arcade-Learning-Environment.git" because of a failure when running
<EMAIL_ADDRESS>-m pip install -q --no-deps --dry-run --ignore-installed --report /dev/stdout https://github.com/mgbellemare/Arcade-Learning-Environment.git`.
Please report this issue:
  https://docs.brew.sh/Troubleshooting

After:
$ brew update-python-resources arcade-learning-environment
==> Retrieving PyPI dependencies for<EMAIL_ADDRESS>==> Getting PyPI info for "importlib-resources==6.0.0"
==> Getting PyPI info for "numpy==1.25.2"
==> Updating resource blocks

Maybe it'd be a good idea to add a specific section that talks about url options.

Good idea 👍🏻

Thanks again @branchvincent!


Compose functions for action hooks

This implements functions for composing Before and After hooks and IsFunction functions. For example part of ResourceOptions object, assuming canManage is a factory for Before hooks and validatePayload is a Before hook:
actions: {
  list: {
    before: composeBefores(
      canManage('admin'),
      validatePayload,
    ),
  },
},

Didn't notice it's kind of already implemented.


PHP8 compatibility

Hello, can you add php8 compatibility for this great bundle ?

Hello,
It would be also great to have the possibility to declare the mapping with PHP 8 attributes.

Hello @ColonelMoutarde PHP8 is available since the version 0.5 of the Bundle.
@pierre-H it's a nice idea indeed 👍

Please @pierre-H create an another issue :)


card.io Partner setup

We are planning to use card.io for one of the apps coming soon from us. But I don't find initial setup process with card.io and pricing details anywhere on top of this integration. Where can I find those details?

@naiducrm card.io is free to use.

@romk1n Thank you Roman for your reply. But there would a fee for payment processing.
Look at the below article. But, I don't see any details in card.io and no proper support details too.
http://blog.unibulmerchantservices.com/card-io-vs-jack-dorseys-square-scan-it-or-swipe-it/

@naiducrm This article is outdated. Card.io has been acquired by PayPal and made free. What payment processor you going to be using is up to you. You can also use PayPal solution which integrated CardIO. As a standalone library it only offers credit card scanning capabilities. Hope it help.

@romk1n Ahh ok. Thank you so much!


Add the ability to build PDF without paragraph segmentation

Add the ability to build PDF without paragraph segmentation.
(aside:_ add a progress bar for downloading word2vec models)
Context

low-commital way to try out repo
faster

Expected result
use with some switch or arg to not have to do the paragraph seg
Current result
well. you are forced to do it now

Nevermind, this feature already exists. dumb mistake


Build failed for x86_64

ignoring file /Users/xxx/graphhopper-ios/build/libgraphhopper.a, file was built for archive which is not the architecture being linked (x86_64): /Users/xxx/graphhopper-ios/build/libgraphhopper.a
Undefined symbols for architecture x86_64
"OBJC_CLASS$_GHRequest", referenced from:
objc-class-ref in Directions.o
"OBJC_CLASS$_EncodingManager", referenced from:
objc-class-ref in Directions.o
"OBJC_CLASS$_GraphHopper", referenced from:
objc-class-ref in Directions.o
ld: symbol(s) not found for architecture x86_64
please help me
thanks in advance

I'm not entirely sure how xcode params are passed to the makefiles so I can't help with that. I too noticed the output was always of a wrong architecture.
When you use the makefiles directly however, you'll build a fat-library (library that includes all architectures). Include that into your project and there are no more errors.
When deploying to the appstore:
Make sure to set up a "stripping" script in your build phases. There are shell scripts for it widely available online. It's essentially just a shell script that will remove unnecessary architectures (such as simulators).


docs: bad link

On griffe's docs, for instance here, the link for View the source of this page points to a page that only contains Not found.

Oh wow, these are my local paths :rofl: Thanks for the heads up! Will fix right now.

And it actually affects all my docs pages :scream: I wonder if this is a change in mkdocs-gen-files :thinking:

This is fixed, thanks again :slightly_smiling_face:


clear up dependencies such that the latest versions can be published to pub.dev

(base) ➜  convenient_test_dev git:(master) flutter pub publish --dry-run --server=https://pub.dartlang.org
Publishing convenient_test_dev 1.0.1+3 to https://pub.dartlang.org:
|-- CHANGELOG.md
|-- LICENSE
|-- README.md
|-- analysis_options.yaml
|-- example
|   '-- README.md
|-- lib
|   |-- convenient_test_dev.dart
|   '-- src
|       |-- data
|       |   |-- generate.sh
|       |   '-- icon_name_info.dart
|       |-- functions
|       |   |-- binding.dart
|       |   |-- command.dart
|       |   |-- core.dart
|       |   | (5 more...)
|       |   |-- misc.dart
|       |   |-- widget_controller.dart
|       |   '-- widget_tester.dart
|       |-- support
|       |   |-- compile_time_config.dart
|       |   |-- declarer.dart
|       |   |-- executor.dart
|       |   |-- get_it.dart
|       |   |-- manager_rpc_service.dart
|       |   |-- setup.dart
|       |   |-- slot.dart
|       |   '-- suite_info_converter.dart
|       |-- third_party
|       |   '-- my_test_compat.dart
|       '-- utils
|           |-- errors.dart
|           |-- snapshot.dart
|           '-- util.dart
|-- pubspec.yaml
'-- test
    '-- main_test.dart
NullSafetyCompliance.analysisFailed
Package validation found the following error:
* Your pubspec.yaml must not override non-dev dependencies.
  This ensures you test your package against the same versions of its dependencies
  that users will have when they use it.
Sorry, your package is missing a requirement and can't be published yet.
For more information, see: https://dart.dev/tools/pub/cmd/pub-lish.
pub finished with exit code 65

https://github.com/zino-hofmann/graphql-flutter/issues/299

maybe have to really remove this...

let's firstly write changelog...

gh issue list --limit 300 --state all --json > ~/temp/0.json


Review edits

List to track progress on reviewer comments. Will add/edit as we go.

[ ]  nitpick (domain.py): there is no need for a raw string for TADA_DATA_URL
[ ] discussion (convert.py): About the TODO - both points of view (regrouping constants in a single place, or having them defined near their place of use to avoid jumping around the code base) are valid. I am usually in favor of the former.
[x] suggestion (domain.py): In harmonize_TADA_dict, we could use a groupby operation to avoid looping through the dataframe using python. TOCHECK
[x] suggestion (domain.py):  replace x in list(set(pandas_series)) pattern w/ .unique method
[ ] suggestion (domain.py, basic.py): replace one dict functions (e.g., out_col_lookup) w/ module-level dicts. Move their docstrings (e.g., sources) to module docstring.
[ ] suggestion (convert.py): We could add "references" sections in the docstrings so that the sources are present in the website and not only in the source code.
[ ] suggestion (basis.py, general): use pandas' methods, e.g., assign w/ np.where() for masked replace. Do compare on timeit, consistency and any other pros/cons.
[x] todo (init.py): importlib.metadata was added in python 3.8, which is the minimal version supported by the package according to its pyproject.toml. The try .. except block should not be needed, even more so considering that importlib_metadata is not listed in the project requirements.
[x] todo (basis.py): group the conditions branches in update_result_basis
[x] todo (contributing.rst): Add a section describing how to setup development environment (e.g. installing the test and docs dependencies).
[x] issue (domain.py): list sub-dependencies (e.g., requests)
[x] issue (domain.py): specify exception expected in re_case.

Note: several items not on the list have been or are being resolved.

These may not get resolved for future features adds:
nitpick 1: TADA_DATA_URL and the URL for domain tables are only used by one function each, but the plan is for additional resources on both to be able to be used by future feature adds. For example new crosswalks with the upcoming transition from WQX2.0 -> 3.0
todo 2 (basis.py): Yes these could be replaced by if in [a,b,c], this would reduce by about 2 lines. These additional basis column haven't received much attention yet. It was coded this was to make it easy to come back to and write specific handling.

pyOpenSci Review complete and branch merged


Hot corner extension support

Problem description
Whoever using hot corner extended, is there an entry for adding clipboard pop-up there?
Potential solutions/workarounds
Currently have no idea how to work this out.
Additional context
Does it also need support from hot-corners-extended too?
Great Extension btw. Must need as gnome-shell lacks it.

Closing in favor of the other issue.


Introduce a new conf for vacuum parallel listing

Currently, vacuum uses spark.sql.sources.parallelPartitionDiscovery.parallelism to control the parallelism for files and directories listing for vacuum and the default value is 10000.
This PR introduces a new Delta SQL conf DELTA_VACUUM_FILE_LISTING_PARALLELISM to control the file listing parallelism for vacuum command. The default value for this conf is 200.
Closes #859

@JassAbidi Could you take a look at my comments when you have time? Thanks!


What pyviz packages should there be?

(I thought I already created this issue, but apparently not. If I missed a duplicate issue, or we discussed this elsewhere and I've forgotten to import the discussion here, please close or edit this issue...)
Currently we have one pyviz package, with dependencies for all the topics. We don't yet list topics, but will soon. At that point, should we have multiple packages (i.e. options), with each corresponding to a topic?
Also: we currently produce only a highly pinned conda package. That's ok, because pyviz isn't a library that's designed to be integrated into someone else's package (that's what the libraries underling pyviz are for). But a highly pinned conda package can be difficult to install, except in a dedicated environment. By which point, a "conda env create (some file env file on anaconda.org or maybe github)" command might make more sense...?

I think we have resolved this somewhat by saying holoviz is a highly pinned set of packages that are guaranteed to work together, but not guaranteed to be up to date. Then there is pyviz-topics/examples which uses the anaconda-project approach.


typings.json

Really sorry for posting a support questions here. But the slack registration is not working :(
I am trying to use GSAP (http://greensock.com/) in angular2-webpack-starter
In the GSAP forum I found a ts typing file.
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/greensock/greensock.d.ts
But in the angular2-webpack-starter I can really find a typings.json file to add it to.
Any suggestions? Thanks

As far as I understand this, the Webpack Starter is not using (anymore) Typings, but instead the "@types" that comes with the new version of typescript.
So to solve your problem, first look if there is a "@types" for GSAP.
Else, you can try to paste the content of you ".d.ts" file in the "custom-typings.d.ts" of the Webpack Starter.

Thanks for the quick reply.
Didn't find much about @types and GSAP, don think they support it officially.
I tried moving the content from the .d.ts film to custom-typings. But it created some other issues.
But think I got GSAP to work without typings, so for now I will just do it this way.
Thanks

I encountered in my app http://github.com/orizens/echoes-ng2.
for getting youtube api support, i installed:
npm i @types/youtube @types/gapi @types/gapi.youtube

then, i added these to custom.typings.d.ts:
import<EMAIL_ADDRESS>import '@types/gapi';
import '@types/youtube';

@orizens can you make a PR explaining this for users who have problems with @types

@gdi2290 sure.
should I add it to Readme.md?

ya


Feature/fund admin/revenues

This PR solves the following issues:

Fix #276
Fix #281

Backend is done @tlacloc


hlint outputting multiline code references MySource.hs:(104,1)-(105,49):

Recently hlint (I am using hlint-3.1.6) sometimes outputs codeline ranges for its hints.
This "breaks" comint (compile-mode) error line detection in Emacs for example.
Is there some way to unconfigure this or change the output format perhaps to be more backwards compatible?
Are other IDEs more flexible about this - maybe I need to teach emacs to parse this type of line reference...
Been hitting this sometimes lately - so thought I would ask about it here first before investigating further.

It now reuses the GHC pretty-printing code for multi-line formats, and in some cases we have better tracking of locations, so I can certainly imagine it happens more. My suggestion would be to fix Emacs itself, as then you'll get range locations in GHC, which I've found very valuable for debugging errors.
Of course, if that's difficult, I could imagine a flag to change the rendering - although it wouldn't be trivial to plumb in and seems sad to lose the extra info.

Okay, thanks Neil, that's totally fair - I'll look into the emacs side next time I hit it.


Update snap to core18, other miscellaneous Edinburgh fixes

This PR does a lot of things, including defining a base (and thus using "legacy" snapcraft) and thus using the newer version of snapcraft (3.X) directly which will unbreak the daily jobs such as https://jenkins.edgexfoundry.org/view/Snap/job/edgex-go-snap-master-stage-snap/347. Additionally, this fully switches from having the build scripts defined here to using the build definitions defined in the jenkins job instead.
Tasks for devops / ci-management:

[x] ci-management PR (https://github.com/edgexfoundry/ci-management/pull/357) merged
[x] deploy verify job for edgex-go to jenkins sandbox to test this PR - see https://jenkins.edgexfoundry.org/sandbox/view/All/job/edgex-go-snap-master-verify-snap
[x] open back-port PR to delhi - actually unnecessary as we are able to specify to use job definitions per build stream, so delhi continues to use the old build_script

This PR also:

Fixes #1204
Fixes #1282
Fixes #1262
Fixes #888
Fixes #922
Fixes #1363
Partially addresses #959 by adding Redis to the snap, but doesn't enable it by default
Fixes #799 by specifying epoch: 1 for the edinburgh snap to block refreshes from delhi to edinburgh
Fixes #1103 by using the archive download links
Adds a work-around for #1306
Addresses #1227 for the snap scripts at least
Limits RAM usage by cassandra to something more reasonable, on a 16 GB amd64 machine:

before (approx 770 MB in non-swappable memory):
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root     23764  4.7  2.9 2440648 474816 ?      SLl  17:51   3:11 /snap/edgexfoundry/x1/usr/lib/jvm/java-1.8.0-openjdk-amd64/bin/java -Dcassandra.config=file:///var/snap/edgexfoundry/x1/cassandra/etc/cassandra.ya

after (approx 60 MB in non-swappable memory):
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root      3547 60.0 27.3 6231000 4443968 ?     SLl  19:02   1:13 /snap/edgexfoundry/857/usr/lib/jvm/java-1.8.0-openjdk-amd64/bin/java -Dcassandra.config=file:///var/snap/edgexfoundry/857/cassandra/etc/cassandra.

Switches to downloading the go release binaries from upstream directly and hashing them, which closes #1202 (because it is no longer needed to build go from source during the build)
Removes erroneous daemon-notify plug from sys-mgmt-agent service
Attempts to work around snapd bug https://bugs.launchpad.net/snapd/+bug/1818306 by not only disabling services with systemd when we initially install but also set the snap config items for those services to be off so that after a refresh when (due to the bug) snapd erroneously starts every service we will at least disable/turn off services that should have been left disabled and stopped during the configure hook
Uses command-chain with passthrough for the hooks so that we have a wrapper generated for the hooks with proper environment variables set
Eliminates the mongod wrapper and just runs mongod executable directly from the app
Dynamically determines the perl version when running kong as we now have a different version of perl with the core18 base
Removes calls to make prepare as that's obselete with go modules
Removes all of the build scripts for the snap from here as all of that now lives in the ci-management repo here
Eliminated the fork-wrapper and go-services-wrapper to just call the binaries directly and use adapter: none for static pure go binaries and adapter: full to use command-chain instead of snapcraft wrappers
Specify profile directories explicitly in configuration.toml files for the device-* services so that we don't need to run the device services with a working directory of $SNAP_DATA/config/device-*/

To justify some of the changes made with respect to the adapter and the scripts we're using, previously with the delhi version of the snap we had 27 snapcraft generated shell wrappers (1 for each app) and 13 shell wrappers for the services, and now we have 1 snapcraft generated wrapper in /snap/command-chain/snapcraft-runner and 12 shell wrappers for the services (though I think we should have 11, the go-build-helper.sh is creeping in from somewhere and it shouldn't be). Associated with this change, the snap.yaml grew in size from 207 lines to 343, but that's being generated by snapcraft so I think it's okay to have it get more complex.
Originally opened as #1297
I now have tests updated that should test all the additional new features in this branch available in the checkbox repo under branch feature/edinburgh-tests. The refresh tests are currently skipped because now all the snap revisions that have been released are epoch: 0 and since this is epoch: 1 it's not refresh-able. To run the tests:
$ # install snapcraft and multipass to build the snap
$ snap install snapcraft --classic
$ snap install multipass --classic --beta
$ # build the snap somewhere say $GOPATH/src/github.com/edgexfoundry/edgex-go/edgexfoundry_*.snap
$ git clone<EMAIL_ADDRESS>$ cd checkbox-provider-edgex
$ git checkout feature/edinburgh-tests
$ # install tools to run the tests
$ snap install jq remarshal
$ snap alias remarshal.toml2json toml2json
$ snap alias remarshal.json2toml json2toml
$ # run the tests against the local snap - note the script needs to be run as root now
$ sudo bin/run-all-tests-locally.sh $GOPATH/src/github.com/edgexfoundry/edgex-go/edgexfoundry_*.snap --verbose --ignorefail

The only tests that currently fail are the refresh tests and the security services, but the security services will need to be fixed up anyways and I don't want to hold back this PR for the security services.

Adding @mhall119 as a reviewer for the changes to snap/README.md

This PR should also remove a roadblock to building behind a proxy since Cassandra is fetched from Apache archive instead of built from source.  (FYI to future readers of this PR).

recheck

Relabeling for Fuji since we missed the branch cut for this PR, however since this is still needed for Edinburgh, I have filed #1389 which will actually implement these changes for Edinburgh proper


"Feature Request: Add 'Go to Top' Button in Footer"

Hi [@anuragverma108 ],
I'd like to contribute to this project by adding a useful feature. I propose adding a "Go to Top" button in the footer section of the website/application.
Rationale:

Enhances user experience by providing easy navigation
Improves accessibility for users who scroll through long pages
Consistent with modern web design conventions

Expected Outcome:

A clickable button labeled "Go to Top" or an appropriate icon (e.g., ↑)
Button is positioned in the footer section
Upon clicking, the button scrolls the page to the top

Hi
I'd like to add the 'go to bottom' page as well. Kindly assign me this issue under Hacktoberfest '24
Thanks


Implement Java runtime provider and Java Templates

Description of changes:

added java building and packaging
added helloworld template

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #3715 into master will increase coverage by 0.43%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3715      +/-   ##
==========================================
+ Coverage   59.24%   59.68%   +0.43%
==========================================
  Files         286      285       -1
  Lines       13325    13227      -98
  Branches     2679     2662      -17
==========================================
  Hits         7894     7894
+ Misses       4997     4900      -97
+ Partials      434      433       -1

Impacted Files
Coverage Δ

packages/amplify-util-mock/src/index.ts

...plify-util-mock/src/__e2e__/utils/cognito-utils.ts

packages/amplify-util-mock/src/storage/storage.ts

packages/amplify-util-mock/src/api/index.ts

packages/amplify-util-mock/src/storage/index.ts

packages/amplify-util-mock/src/utils/index.ts
0.00% <0.00%> (ø)

packages/amplify-util-mock/src/utils/ddb-utils.ts
0.00% <0.00%> (ø)

...ges/amplify-util-mock/src/utils/config-override.ts
0.00% <0.00%> (ø)

...plify-util-mock/src/__e2e__/utils/lambda-helper.ts
0.00% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 841297f...d7003e1. Read the comment docs.


Feat: Add versioning to BIDS and collab datasets

In order to allow a user to have full control of the state of his dataset(s), we need a dataset versioning system.
To achieve this, we propose to leverage Datalad, a data versioning system tailored to neuroimaging data.

This would involve the following changes:
Private space

[x] Call datalad.create() function in DatasetHandler.dataset_create(): create an initial datalad/git-managed dataset
Call datalad.save() function in:

[x] ParticipantHandler.sub_import(): save the dataset state with the new imported files
[x] ParticipantHandler.sub_delete() and  ParticipantHandler.sub_delete_file(): save the dataset state taking into account the deleted file(s)
[x] ParticipantHandler.sub_edit_clinical(): save the dataset state when the participants.tsv is modified

Collab space

[x] Call datalad.create() function in datahipy.handlers.project.create_project(): create an initial datalad/git-managed dataset for (1) the Coolab folder and for (2) the nested BIDS dataset.
[x] Call datalad.save() function in:

[x] datahipy.handlers.project.import_subject(): save the dataset state when a sub-<label> folder is imported from an existing BIDS dataset of the center (private space)
[x] datahipy.handlers.project.import_document(): save the dataset state when a document is imported into the documents folder of the Collab project.

This would also require the following developments:

New versioning module that provides functions for:

[x]  create_tag(dataset, version_tag, changes_message): create a version tag with message containing the list of changes. The BIDS CHANGES file has to also be updated with the version tag, date, and list of changes. This can be achieve with datalad.save(), specifying a <version_tag> which save at the same time the lines added to the CHANGES file.
[x] get_tags(dataset): get the list of version tags of a dataset via git tag -n
[x] checkout_tag(version_tag): checkout the existing dataset tag to a branch with the same name via git checkout tags/<version_tag> -b <version_branch>. master branch is the current dataset. If not tag present in the last commit, it is a draft. If tag is present, it means that the dataset is exactly at the state specified by the version tag.

New CLI commands that call the previous new functions

[x] dataset.create_tag
[x] dataset.get_tags
[x] dataset.checkout_tag
[x] project.create_tag
[x] project.get_tags
[x] project.checkout_tag

Notes

All functions / methods should work on both BIDS and Collab datasets.
A version tag has to be in the X.Y.Z format, where X is the major, Y is the minor, Z is the patch.

Environment and dependencies

[X] Install standalone git-annex and pytest-order in Dockerfile
[X] Add datalad and datalad-neuroimaging to the install_requires of setup.cfg, such that they are installed along datahipy

Tests:

[X] Extend adapt tests to take into account and test all the previously enumerated changes or new developments.

Documentation has to be updated:

[X] README: update list of commands
[x] README: update usage help
[X] API doc of the new utils.versioning module
[x] Double-check if existing docstrings of modified functions / methods need to updated

closed by PR #82


Test the three gyro components

The anti shake code would test the x gyro component twice, and it would never test the z component. This was presumably a typo.

You are correct it was a typo.


HODLER Wallet iOS version

Testing operating system: 12 & 13
Waiting for D-U-N number
Waiting for activation AppStore developer account
Waiting for approval of the app
ETA - 20 November 2018

App in Apple review


network_cmds: unconditionally exclude Unbound

Description of changes
Unbound doesn’t build with newer versions of OpenSSL or LibreSSL, so it is pinned to LibreSSL 3.4. This is causing problems now that LibreSSL 3.4 is marked as insecure and is slated to be dropped.
The easy fix is to disable Unbound unconditionally:

aarch64-darwin already doesn’t build it;
Apple dropped it from newer versions of the source releases; and
Unbound is already packaged in nixpkgs and builds on both Darwin architectures.

Fixes #223977 and removes darwin.network_cmds as a blocker for #216207.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 224423 run on x86_64-darwin 1

6 packages failed to build:

hyprspace
isabelle
isabelle-components.isabelle-linter
swtpm
swtpm.man
tlaps

19 packages built:

acme-sh
cvsq
gitolite
iodine
nettools
openconnect
openconnect.dev
openconnect_openssl
openconnect_openssl.dev
openconnect_unstable
openconnect_unstable.dev
testssl
tinystatus
unixtools.arp
unixtools.ifconfig
unixtools.netstat
unixtools.ping
unixtools.route
vpnc-scripts

None of these appear to be related to the change.

hyprspace fails because it doesn’t support building with Go 1.18;
swtpm is probably sandbox-related; and
isabelle is also probably sandbox-related (reports an error when it tries to write to /tmp/isabelle- during the build).

Result of nixpkgs-review pr 224423 run on aarch64-darwin 1

6 packages failed to build:

hyprspace
isabelle
isabelle-components.isabelle-linter
swtpm
swtpm.man
tlaps

19 packages built:

acme-sh
cvsq
gitolite
iodine
nettools
openconnect
openconnect.dev
openconnect_openssl
openconnect_openssl.dev
openconnect_unstable
openconnect_unstable.dev
testssl
tinystatus
unixtools.arp
unixtools.ifconfig
unixtools.netstat
unixtools.ping
unixtools.route
vpnc-scripts

For the SDK bump I patched it to depend on current OpenSSL 1.x, I could bring those patches up to date probably but if nothing depends on it anyway, I'm in favor of dropping it.

Thanks for your work on those patches. I also agree.
I checked the version shipped in network_cmds, and it’s very old (1.5.1). There’s at least one known vulnerability if not more. It we wanted to continue shipping an unbound binary in darwin.network_cmds, it would make more sense to symlink the binary from the maintained version in nixpkgs than to continue to build this old one. However, anything that does need Unbound should really just take the dependency directly (since it’ll have to do that for other platforms anyway).


Release 2.0

Ok, let's do this. @erjohnso PTAL
Tested #180 - looking good 👍
Since we're entering 2.0, will implement 2 additional breaking changes:

image parameter will no longer default to an arbitrary one.
Not setting it will throw a user-friendly error. Since the
image/image_family logic is dealt with in zone-specific config,
this will greatly simplify things.
Provider-level configuration shouldn't have contained that
information in the first place as it's executed multiple times
and will cause collisions if the zone parameter is set at runtime (like image family).

Upgrading to new standard SyncedFolders action and removing old rsync code. This time it should be ok as I finally found a proper workaround - all test pass ^___^
Fixes #158, #152, #137, #109

Made some drive-by fixes as well:

Fix disk cleanup issue causing the disk to be marked as created before insertion
Test environment fixups to avoid 'Encoded files can't be
read outside of the Vagrant installer.'

Was testing this release locally and found a small issue: for some reason I can't specify the location of the GCE key using ~/... anymore. I have to specify the full, absolute path now.

@zackangelo Thanks for catching this! Should be fixed now.


Upgrade Node.js from 8.4.0 to 8.9.1 LTS

Node.js 8.9.1 released. It's LTS(Long Term Support) version.
ISSUE=#174

LGTM


Contrib revamp

Overhaul of the contributing guidelines for Bittensor.
This PR does several things:

Borrows elements from Bitcoin's contrib guide and philosophy into Bittensor style
Remove references to outdated github links
Refactors contributing guide into a separate directory /contrib so as to not overpopulate the main directory
Makes several additions to the CONTRIBUTING.md guide, including:

A PR philosophy
A Testing guide
A Debugging guide
An explicit PR process to augment DEVELOPMENT_WORKFLOW.md
An opinionated STYLE.md code and commit guide for consistent and efficient open-source collaboration

Although I've made some comments, this is very good work and a good base to iterate on.
Nice work @ifrit98