chore(lint): use mypy 1.0.0

"40% faster." https://mypy-lang.blogspot.com/2023/02/mypy-10-released.html

Regarding the pipeline error:
Looking in indexes: https://test.pypi.org/simple/
Collecting onnx-weekly
  Downloading https://test-files.pythonhosted.org/packages/9e/43/78e78b495e9c12bb50d5be945eb2ade2f2de47bd82c8662535ee27af733b/onnx-weekly-1.14.0.dev20230206.tar.gz (11.2 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 11.2/11.2 MB 42.9 MB/s eta 0:00:00
  Installing build dependencies: started
  Installing build dependencies: finished with status 'error'
  error: subprocess-exited-with-error

  × pip subprocess to install build dependencies did not run successfully.
  │ exit code: 1
  ╰─> [3 lines of output]
      Looking in indexes: https://test.pypi.org/simple/
      ERROR: Could not find a version that satisfies the requirement setuptools>=40.8.0 (from versions: none)
      ERROR: No matching distribution found for setuptools>=40.8.0
      [end of output]

pip install setuptools>=40.8.0 before installing TestPyPI package should help.

It's failing because the latest weekly does not have a linux wheel. Was it able to rerun? Normally we don't need these depencencies.

It's failing because the latest weekly does not have a linux wheel. Was it able to rerun? Normally we don't need these dependencies.

I see. ONNX pipelines are green now, I will rerun it soon.

It's failing because the latest weekly does not have a linux wheel. Was it able to rerun? Normally we don't need these dependencies.

That pipeline is still using the codebase with wrong URLs so it cannot rerun successfully... It has been fixed in the main branch so next weekly package should be good


Dont want Ios notification image to expand

Hi there is there any way, to not expand the ios notification image. Just like how we can control in android.

Do you mean how on iOS if you expand the notification the badge image displays larger beneath the message? If so then no I don't think so. I have looked into that and the image for iOS is not actually a badge, it's a thumbnail for media content.
If you have discovered a way to do this I would be interested to know as my client has a requirement for this which I am telling them can only be done in Android.


Improve compatibility with older auto1111 UI versions

Hi!
This changes around a couple of imports to allow this to work on the last commit to the AUTO1111 repo prior to the Gradio upgrade - a lot of users (myself and many colab users included) are still hanging around on the old version for the time being, as many other extensions don't work on 3.23 just yet.
It's just a try/catch on two import statements since the import path for extensions_dir moved.
Let me know if I need to change anything? 😄

There is an error using it in Colab, I think im using another gradio version


1Password Item update error when inserting fields

Your environment
Terraform v1.5.7
on linux_amd64

provider registry.terraform.io/1password/onepassword v2.1.0

What happened?
When inserting fields at the beginning of a section:
Error: 1Password Item update error
  with onepassword_item.environment_variables,
  on 1password.tf line 75, in resource "onepassword_item" "environment_variables":
  75: resource "onepassword_item" "environment_variables" {
Could not update item 'xkjcynmzjjkwjfenfmkd6mffuy' from vault
'5rmq6vebgi3c2iejytskh52d6y', got error: op error: unable to process line 1:
Validation: (validateVaultItem failed to Validate), Couldn't validate the
item: "[ItemValidator] has found 3 errors, 0 warnings: \nErrors:{1.
details.sections[9].fields[13] has non-unique name}, {2.
details.sections[9].fields[14] has non-unique name}, {3.
details.sections[9].fields[15] has non-unique name}"
Releasing state lock. This may take a few moments...

What did you expect to happen?
New fields get correctly inserted.
Notes
the same configuration change was applied successfully after moving the new fields to the bottom of their section.

Hi @DavidS-ovm :wave: Thanks for your interest in our Terraform provider and for filing this issue.
I’m hoping to clarify a few things:

You mention that when inserting new fields at the beginning of a section that the 1Password Item update error occurs. Just to rephrase the steps to ensure that I'm understanding it correctly: are you referring to a flow where a 1Password item is created with a section and a number of fields, saved, and then modified afterwards where new fields are added to the above-mentioned section and placed at its beginning?
I see from the error message you included that several details.sections[9].fields[$INDEX] has non-unique name errors are being logged. Just to confirm, during your testing did you double-check that each field’s name was a unique string? (The main reason I ask to confirm is because personally I've done this myself many times before; if I have an item with a lot of fields on it and I’m making a lot of changes to them it’s very common for me to accidentally end up with duplicate field keys at the end.)
Could you kindly provide us with the full set of commands/actions that you ran in order to help us reproduce this error?

I can also suggest the following workaround (which I will be the first to admit is not the most ideal solution, but I’ll include it here anyway just in case it’s helpful for your situation/anyone else who may come upon this issue): if the order of fields within the section is important, you could make note of the section’s names and values and then re-create the section on the item with the fields sorted in your preferred order.

Hi @DavidS-ovm 👋 Thanks for your interest in our Terraform provider and for filing this issue.
I’m hoping to clarify a few things:
1. You mention that when inserting new fields at the beginning of a section that the `1Password Item update error` occurs. Just to rephrase the steps to ensure that I'm understanding it correctly: are you referring to a flow where a 1Password item is created with a section and a number of fields, saved, and then modified afterwards where new fields are added to the above-mentioned section and placed at its beginning?

Yes.

2. I see from the error message you included that several `details.sections[9].fields[$INDEX] has non-unique name` errors are being logged. Just to confirm, during your testing did you double-check that each field’s name was a unique string? (The main reason I ask to confirm is because personally I've done this myself many times before; if I have an item with a lot of fields on it and I’m making a lot of changes to them it’s very common for me to accidentally end up with duplicate field keys at the end.)

It applied successfully when I moved the same additional fields to the end of the section.

3. Could you kindly provide us with the full set of commands/actions that you ran in order to help us reproduce this error?

my terraform manifest looks approximately like this:
provider "onepassword" {
}

data "onepassword_vault" "env_vault" {
  name = var.terraform_env_name
}

resource "onepassword_item" "environment_variables" {
  vault = data.onepassword_vault.env_vault.uuid

  title      = var.terraform_env_name
  category   = "secure_note"
  note_value = "MANAGED BY TERRAFORM - DO NOT EDIT MANUALLY\n\nAll the values for the ${var.terraform_env_name} environment"

  section {
    label = "generated"
    field {
      label = "description"
      type  = "STRING"
      value = "These values are generated by the terraform deployment and any changes will be overwritten"
    }

    field {
      label = "some_secret"
      type  = "STRING"
      value = module.some_module.some_secret
    }

our CI pipelines for this basically boil down to terraform plan/terraform apply.

I can also suggest the following workaround (which I will be the first to admit is not the most ideal solution, but I’ll include it here anyway just in case it’s helpful for your situation/anyone else who may come upon this issue): if the order of fields within the section is important, you could make note of the section’s names and values and then re-create the section on the item with the fields sorted in your preferred order.


Propel diff task does not honor column order on MySQL

When new columns are added to a table from one version to the other, the propel migration will add all columns to the end of the table.
For MySQL this is fixable, because MySQL supports an ALTER TABLE ADD COLUMN abc AFTER Xy Syntax.
I fixed this by reimplementing getAddColumnDDL() and getAddColumnsDDL() in MysqlPlatform.
Pull request incoming...

Here is the link to the pull-request implementing a fix:
https://github.com/propelorm/Propel/pull/275

For us it is a requirement, as we use the column order to automatically generate forms to edit models. So for us its important to have the correct order. And when we have to rewrite all migrations by hand this feature is not of great use for us.
So you tell me that we have to apply this patch every time we update Propel?


[Bug] [admin] 如果on k8s application模式提交失败时控制台无任何信息

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
on k8s application模式提交失败时控制台无任何信息，此bug已修，此issue只为提pr
解决后的效果：

What you expected to happen
能打印出错误信息
How to reproduce

方式一： k8s on application模式下重复提交同一个任务
方式二：任务名用中文

Anything else
No response
Version
0.7.3
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

关联pr： https://github.com/DataLinkDC/dinky/pull/2177

#2173


Failing to start jekyll server

Checklist

[X] I have read and accepted the contributing guidelines.

How did you create the site?
Generated from chirpy-starter
Describe the bug
Since 7.2.0 I am getting that error. On 7.1.1 it did work. Maybe someone have an idea what's wrong?
user@users:~/test > JEKYLL_ENV=production bundle exec jekyll serve --open-url --livereload --watch
logger was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0.
You can add logger to your Gemfile or gemspec to silence this warning.
Configuration file: /test_config.yml
            Source: /test
       Destination: /test_site
 Incremental build: disabled. Enable with --incremental
      Generating...
Deprecation Warning: Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0.

More info and automated migrator: https://sass-lang.com/d/import

  ╷
1 │ @import 'dist/bootstrap';
  │         ^^^^^^^^^^^^^^^^
  ╵
    main.bundle.scss 1:9                                                                                @use
    /testassets/css/jekyll-theme-chirpy.scss 1:1  root stylesheet
Deprecation Warning: Sass @import rules are deprecated and will be removed in Dart Sass 3.0.0.

More info and automated migrator: https://sass-lang.com/d/import

  ╷
2 │ @import 'main';
  │         ^^^^^^
  ╵
    main.bundle.scss 2:9                                                                                @use
    /testassets/css/jekyll-theme-chirpy.scss 1:1  root stylesheet
Error: Can't find stylesheet to import.
  ╷
1 │ @import 'dist/bootstrap';
  │         ^^^^^^^^^^^^^^^^
  ╵
  main.bundle.scss 1:9                                                                                @use
  /testassets/css/jekyll-theme-chirpy.scss 1:1  root stylesheet
  Conversion error: Jekyll::Converters::Scss encountered an error while converting 'assets/css/jekyll-theme-chirpy.scss':
                    Can't find stylesheet to import.
                    ------------------------------------------------
      Jekyll 4.3.4   Please append `--trace` to the `serve` command
                     for any additional information or backtrace.
                    ------------------------------------------------
/Users/user/.gem/ruby/3.3.0/gems/jekyll-sass-converter-3.0.0/lib/jekyll/converters/scss.rb:175:in `rescue in convert': Can't find stylesheet to import. (Jekyll::Converters::Scss::SyntaxError)

        raise SyntaxError, e.message
              ^^^^^^^^^^^^^^^^^^^^^^
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-sass-converter-3.0.0/lib/jekyll/converters/scss.rb:159:in `convert'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:105:in `block in convert'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:104:in `each'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:104:in `reduce'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:104:in `convert'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:84:in `render_document'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:63:in `run'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:572:in `render_regenerated'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:564:in `block in render_pages'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:563:in `each'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:563:in `render_pages'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:211:in `render'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:80:in `process'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/command.rb:28:in `process_site'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/commands/build.rb:65:in `build'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/commands/build.rb:36:in `process'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/command.rb:91:in `block in process_with_graceful_fail'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/command.rb:91:in `each'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/command.rb:91:in `process_with_graceful_fail'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/commands/serve.rb:86:in `block (2 levels) in init_with_program'
        from /Users/user/.gem/ruby/3.3.0/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `block in execute'
        from /Users/user/.gem/ruby/3.3.0/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `each'
        from /Users/user/.gem/ruby/3.3.0/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `execute'
        from /Users/user/.gem/ruby/3.3.0/gems/mercenary-0.4.0/lib/mercenary/program.rb:44:in `go'
        from /Users/user/.gem/ruby/3.3.0/gems/mercenary-0.4.0/lib/mercenary.rb:21:in `program'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/exe/jekyll:15:in `<top (required)>'
        from /Users/user/.gem/ruby/3.3.0/bin/jekyll:25:in `load'
        from /Users/user/.gem/ruby/3.3.0/bin/jekyll:25:in `<top (required)>'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli/exec.rb:58:in `load'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli/exec.rb:58:in `kernel_load'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli/exec.rb:23:in `run'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli.rb:455:in `exec'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/vendor/thor/lib/thor/command.rb:28:in `run'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/vendor/thor/lib/thor.rb:527:in `dispatch'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli.rb:35:in `dispatch'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/vendor/thor/lib/thor/base.rb:584:in `start'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli.rb:29:in `start'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/exe/bundle:28:in `block in <top (required)>'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/exe/bundle:20:in `<top (required)>'
        from /etc/profiles/per-user/user/bin/bundle:25:in `load'
        from /etc/profiles/per-user/user/bin/bundle:25:in `<main>'
/Users/user/.gem/ruby/3.3.0/gems/sass-embedded-1.82.0-arm64-darwin/lib/sass/compiler/host.rb:86:in `compile_request': Can't find stylesheet to import. (Sass::CompileError)
        from /Users/user/.gem/ruby/3.3.0/gems/sass-embedded-1.82.0-arm64-darwin/lib/sass/compiler.rb:171:in `compile_string'
        from /Users/user/.gem/ruby/3.3.0/gems/sass-embedded-1.82.0-arm64-darwin/lib/sass/embedded.rb:37:in `compile_string'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-sass-converter-3.0.0/lib/jekyll/converters/scss.rb:160:in `convert'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:105:in `block in convert'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:104:in `each'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:104:in `reduce'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:104:in `convert'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:84:in `render_document'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/renderer.rb:63:in `run'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:572:in `render_regenerated'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:564:in `block in render_pages'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:563:in `each'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:563:in `render_pages'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:211:in `render'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/site.rb:80:in `process'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/command.rb:28:in `process_site'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/commands/build.rb:65:in `build'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/commands/build.rb:36:in `process'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/command.rb:91:in `block in process_with_graceful_fail'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/command.rb:91:in `each'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/command.rb:91:in `process_with_graceful_fail'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/lib/jekyll/commands/serve.rb:86:in `block (2 levels) in init_with_program'
        from /Users/user/.gem/ruby/3.3.0/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `block in execute'
        from /Users/user/.gem/ruby/3.3.0/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `each'
        from /Users/user/.gem/ruby/3.3.0/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `execute'
        from /Users/user/.gem/ruby/3.3.0/gems/mercenary-0.4.0/lib/mercenary/program.rb:44:in `go'
        from /Users/user/.gem/ruby/3.3.0/gems/mercenary-0.4.0/lib/mercenary.rb:21:in `program'
        from /Users/user/.gem/ruby/3.3.0/gems/jekyll-4.3.4/exe/jekyll:15:in `<top (required)>'
        from /Users/user/.gem/ruby/3.3.0/bin/jekyll:25:in `load'
        from /Users/user/.gem/ruby/3.3.0/bin/jekyll:25:in `<top (required)>'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli/exec.rb:58:in `load'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli/exec.rb:58:in `kernel_load'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli/exec.rb:23:in `run'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli.rb:455:in `exec'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/vendor/thor/lib/thor/command.rb:28:in `run'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/vendor/thor/lib/thor.rb:527:in `dispatch'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli.rb:35:in `dispatch'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/vendor/thor/lib/thor/base.rb:584:in `start'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/cli.rb:29:in `start'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/exe/bundle:28:in `block in <top (required)>'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/lib/bundler/friendly_errors.rb:117:in `with_friendly_errors'
        from /Users/user/.gem/ruby/3.3.0/gems/bundler-2.5.21/exe/bundle:20:in `<top (required)>'
        from /etc/profiles/per-user/user/bin/bundle:25:in `load'
        from /etc/profiles/per-user/user/bin/bundle:25:in `<main>'

Steps To Reproduce
Run JEKYLL_ENV=production bundle exec jekyll serve --open-url --livereload --watch
Expected Behavior
Page should be generated and loaded.
Environment

Ruby: ruby 3.3.5 (2024-09-03 revision ef084cc8f4) [arm64-darwin24]
Jekyll:

logger was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0.
You can add logger to your Gemfile or gemspec to silence this warning.
csv was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.4.0.
You can add csv to your Gemfile or gemspec to silence this warning.
/Users/user/.gem/ruby/3.3.0/gems/safe_yaml-1.0.5/lib/safe_yaml/load.rb:22: warning: base64 was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.4.0.
You can add base64 to your Gemfile or gemspec to silence this warning.
jekyll 4.3.4

Chirpy:

* jekyll-theme-chirpy (7.2.1)
        Summary: A minimal, responsive, and feature-rich Jekyll theme for technical writing.
        Homepage: https://github.com/cotes2020/jekyll-theme-chirpy
        Documentation: https://github.com/cotes2020/jekyll-theme-chirpy/#readme
        Source Code: https://github.com/cotes2020/jekyll-theme-chirpy
        Wiki: https://github.com/cotes2020/jekyll-theme-chirpy/wiki
        Bug Tracker: https://github.com/cotes2020/jekyll-theme-chirpy/issues
        Path: /Users/leonidbelenkiy/.gem/ruby/3.3.0/gems/jekyll-theme-chirpy-7.2.1

Anything else?
No response

It seems that you built the site from the source code and lost some project files during the upgrade process, and did not generate the assets yourself.
Please make sure you have read the contributor guide, which details when to report a bug. If you encounter difficulties in usage, you should post them in the community discussion.

It seems that you built the site from the source code and lost some project files during the upgrade process, and did not generate the assets yourself.
Please make sure you have read the contributor guide, which details when to report a bug. If you encounter difficulties in usage, you should post them in the community discussion.

Hi there,
Thank you for your response. I’m curious to know why the issue is closed. I haven’t had a chance to provide any feedback yet.
I’m not building the project from the source code, but rather from the starter. Interestingly, the exact same project is working on 7.1.x and all previous versions, but it’s not working on 7.2.x. Does this mean that my project somehow converted from the starter to a source code-based project?
By the way, I used the published upgrade guide to make the upgrade.


[REVIEW] Error running test scripts

I have the environment setup and dynamo installed. I am not sure I can run the test scripts without the actual physical hardware. But I tried anyway and got an error. I doubt it due to the missing camera though.
(dynamo-review) C:\Users\mel\Documents\GitRepositories\dynamo_realsense-capture\sample_scripts>python testscript.py
Traceback (most recent call last):
  File "testscript.py", line 12, in <module>
    cameraFiles = os.listdir('dynamo/sample_files')
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'dynamo/sample_files'

Hi @melund ,
Would you mind trying this again with the new testscript.py which I uploaded 2 days ago? I had noticed this error yesterday, where I had missed changing the local reference to the sample files. I believe the newest version of this file should be able to find the sample files (which replicate having a camera connected to the system) in the repository. You should be able to run the testscript without cameras connected as the sample files are read in as virtual cameras.
You will also need the "pptk" package (from pip) installed to view the sample data from testscript.py
Thanks!
Abhi

@abhishektha. Thanks. Now the script runs. I got the following output and some figures.
$ python testscript.py
0 devices have been found
C:\Users\mel\Documents\GitRepositories\dynamo_realsense-capture\sample_files\20190418_142057.bag  sees the chessboard!
QWindowsContext: OleInitialize() failed:  "COM error 0xffffffff80010106 RPC_E_CHANGED_MODE (Unknown error 0x0ffffffff80010106)"
C:\Users\mel\Documents\GitRepositories\dynamo_realsense-capture\sample_files\20190418_142125.bag  sees the chessboard!
C:\Users\mel\Documents\GitRepositories\dynamo_realsense-capture\sample_files\20190418_142138.bag  sees the chessboard!
C:\Users\mel\Documents\GitRepositories\dynamo_realsense-capture\sample_files\20190418_142205.bag  sees the chessboard!
C:\Users\mel\Documents\GitRepositories\dynamo_realsense-capture\sample_files\20190418_142217.bag  sees the chessboard!

I guess that is expected when I don't have the cameras.


More cases support partition column pruning

closes https://github.com/NVIDIA/spark-rapids/issues/7436
This is a follow-up for PR #7428, to support partition column pruning for more cases when GPU file scan mixed with CPU project or filter.
Signed-off-by: Liangcai Li<EMAIL_ADDRESS>

build

build

build

build

build


fix: modal functionality

Description
We were missing modal functionality, copied over modal mixin from Dialtone-vue and implemented.
Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[x] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[x] Ensure all gulp scripts successfully compile.
[ ] Update, remove, or extend all affected documentation.
[x] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).

Obligatory GIF (super important!)

Merging this as Julio is gone this week.


Migrated jsonschema.RefResolver to referencing.Registry

Resolves #135
Description
Migrate from jsonschema.RefResolver to referencing.Registry in support of jsonschema 4 upgrade
Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have signed the CLA
[x] This PR includes tests, or tests are not required/relevant for this PR
[x] I have run changie new to create a changelog entry

Successfully installed anyio-4.0.0 black-23.9.1 certifi-2023.7.22 cfgv-3.4.0 distlib-0.3.7 execnet-2.0.2 filelock-3.12.4 h11-0.14.0 httpcore-0.18.0 httpx-0.25.0 identify-2.5.29 idna-3.4 iniconfig-2.0.0 isort-5.12.0 mypy-1.5.1 mypy-extensions-1.0.0 nodeenv-1.8.0 packaging-23.1 pathspec-0.11.2 platformdirs-3.10.0 pluggy-1.3.0 pre-commit-3.4.0 pytest-7.4.2 pytest-xdist-3.3.1 ruff-0.0.260 sniffio-1.3.0 types-Jinja2-2.11.9 types-MarkupSafe-1.1.10 types-PyYAML-<IP_ADDRESS> types-jsonschema-<IP_ADDRESS> types-python-dateutil-<IP_ADDRESS> virtualenv-20.24.5
Finished syncing dependencies
cmd [1] | pytest -n auto tests
================================================================================ test session starts ================================================================================
platform linux -- Python 3.11.4, pytest-7.4.2, pluggy-1.3.0
rootdir: /home/codec/git/dbt-semantic-interfaces
plugins: anyio-4.0.0, xdist-3.3.1
8 workers [133 items]
.....................................................................s..........................................s....................                                         [100%]
========================================================================== 131 passed, 2 skipped in 2.41s ===========================================================================

I have signed the CLA but the workflow seems to be stuck.  Anything I need to do on my end?

I have signed the CLA but the workflow seems to be stuck. Anything I need to do on my end?

I was looking at our list of people who've signed the CLA, and I do see you in there as @codecae. For whatever reason if the submitted GitHub Account Name has an @ at the start, it gets dropped. I'm going to see if I'm allowed to manually edit our list of github account names that have signed the CLA. You may need to sign the CLA again though and use codecae for the GitHub Account Name field instead of @codecae

I wondered if that might be the issue.  I figured it was looking for what the CLA bot posted in the automated to comment

@codecae I'll see about getting the CLA bot message to be more clear! It probably puts the @ in the message to notify the specific users, but that seems confusing without some level of clarification 🙃 Additionally, apparently "bad things happen"™ when we manually edit the list of people who've signed the CLA, so resigning it is probably the best way forward

I just signed it all again and it seemed to work just fine 👍

Should be squeaky clean now... linter seems happy.

Would you prefer a squash to lower the noise floor a bit on the commit history?

Would you prefer a squash to lower the noise floor a bit on the commit history?

Yea we'll probably end up squash merging, just to keep the history clear of cleanup commits

I ran the linter in containers for 3.8-3.11 I think everything should be good now.  Sorry for the small misses here.

I ran the linter in containers for 3.8-3.11 I think everything should be good now. Sorry for the small misses here.

No worries! The number of times the linter has caught me is too many to count. Thank you for sticking with it, this work is incredibly helpful 🙂

Super quick reaction! Thank you 🍾

Thank you again for doing this work! This looks great 🚀

Glad to help!


git-annex special remote for data access

Would need to wrap their ukbfetch tool. Available in semi-source form from http://biobank.ctsu.ox.ac.uk/crystal/refer.cgi?id=645
wget  -nd  biobank.ctsu.ox.ac.uk/crystal/crystal/util/ukbfetch_linkset.tar

wrapping in a Git-Annex special remote

The provided static lib does not link on modern systems:
% make
g++ -Dint_lnx -O   -c -o ukbfetch.o ukbfetch.cpp
g++ -o ukbfetch ukbfetch.o -L. -lufetch -lz
/usr/bin/ld: ./libufetch.a(ufetch.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(reposit.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(ftarget.o): relocation R_X86_64_PC32 against symbol `_ZNSsC1ERKSs@@GLIBCXX_3.4' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(webfetch.o): relocation R_X86_64_32S against symbol `_ZTV9WEB_FETCH' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(bulcom.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(fetutil.o): relocation R_X86_64_PC32 against symbol `strtol@@GLIBC_2.2.5' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(xaes.o): relocation R_X86_64_32S against symbol `_ZTV4XAES' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(xtime.o): relocation R_X86_64_32S against symbol `_ZTV5XDATE' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(xerror.o): relocation R_X86_64_PC32 against symbol `_ZNSsC1ERKSs@@GLIBCXX_3.4' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(xencode.o): relocation R_X86_64_32 against symbol `_ZN7XENCODE10last_errorE' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(xbinob.o): relocation R_X86_64_PC32 against symbol `malloc@@GLIBC_2.2.5' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(rosetta.o): relocation R_X86_64_PC32 against symbol `tolower@@GLIBC_2.2.5' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(authkey.o): relocation R_X86_64_32S against symbol `_ZTV8AUTH_KEY' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(xmd5.o): relocation R_X86_64_PC32 against symbol `memcpy@@GLIBC_2.14' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(aeskey.o): relocation R_X86_64_32S against symbol `t_fl' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(aescrypt.o): relocation R_X86_64_32S against symbol `t_fn' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(comcrypt.o): relocation R_X86_64_32S against symbol `_ZTV8COMCRYPT' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(kipper.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(rosebase.o): relocation R_X86_64_PC32 against symbol `_ZNSsC1ERKSs@@GLIBCXX_3.4' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: ./libufetch.a(aestab.o): relocation R_X86_64_32 against `.text' can not be used when making a PIE object; recompile with -fPIC
/usr/bin/ld: final link failed: nonrepresentable section on output
collect2: error: ld returned 1 exit status
make: *** [Makefile:9: ukbfetch] Error 1

Unclear if there is a workaround.

This makes it run
iff --git a/Makefile b/Makefile
index 31eec40..5387a08 100644
--- a/Makefile
+++ b/Makefile
@@ -6,7 +6,7 @@ LDLIN=-linterp.1
 CXXFLAGS=$(CCXXFLAGS)

 ukbfetch : ukbfetch.o libufetch.a
-       $(CXX) -o ukbfetch $< -L. -lufetch -lz
+       $(CXX) -no-pie -o ukbfetch $< -L. -lufetch -lz

 clean:
        rm *.o

I will close this now. I think the present setup works well enough.


Movies example

https://solid-movies.deno.dev

This will never get merged on its own. But rather as part of dev branch.


error with Fun_with_HBase.xml

Flow created using template is throwing  following error for HBase write  (PutHbaseCell and PutHbaseJson). I have updated only controller setting ,and haven't done any change in workflow created by template
apache.nifi.hbase.PutHBaseJSON PutHBaseJSON[id=6e1f5223-c332-48bb-b261-3f6f50396e0a] Missing row id for FlowFile StandardFlowFileRecord[uuid=b9e3cd66-dca7-4106-b634-d19e6ce608a8,claim=StandardContentClaim [resourceClaim=StandardResourceClaim[id=1463509861921-1, container=default, section=1], offset=49106, length=50],offset=0,name=1086787873266535,size=50]; routing to failure

Hello @ashitabh,
Thank you for bringing this up. I reached out to the creator of the template and this issue actually came up before there was an updated Template made. I've update the template on master of this repo. Just pull the latest commit and let me know if it solves your problem.

thanks , it's working now


Feature/operator overloading

Operator overloading as discussed in #89 and #113.
We've added the most common operations and the ones we know we will use. It is probably easiest to add more overloads when they are needed.
All code is cross-checked twice by me and @ulflind but I wouldn't be surprised if you find something that needs fixing.

Thanks, I will try to take a look at this soon. A bit occupied with selling my house these days.

No problem. Good luck with selling the house.

I only found two operator overloads that might be off, everything else looks good to me and with good test coverage. Awesome!
I'm awaiting your feedback on my comments, then let me know when you think it is ready for merge and I'll take a final look at it.
Future improvement

UnitA / UnitA = Ratio ?

UnitA / int|long|double|decimal = UnitA

This one is tricky, should we preserve .NET round behavior so that Length.FromMeters(3) / (int)2 = 1, 1.5 or 2? Internally we use double representations for most units, so it would by probably default to 1.5d internally, and I think that is the most intuitive, but one could argue dividing by integer should round down but I don't think I like that behavior. Rounding up is even less intuitive as only Convert.ToInt32() and Math.Round() methods achieve that.

It should be ready to merge now (see comments on your comment, typos should be fixed).

UnitA / UnitA already returns a double which is very intuitive to me
Dividing by a doubleis also implemented, it's quite logical that it behaves as it does right now. I would prefer if the compiler didn't implicitly cast long, int and decimal to double and used the existing overload but the end result makes more sense than the alternatives. Since the returned Unit would always be a double it would be quite strange if it was rounded up or down.

You are right of course, I forgot we already had some operator overloads.
I agree with your reasoning and your latest change looks good. Merging in now.

Nuget 3.25 out.


Test to verify scipy present in scipy base images

Conditionally add scipy import test for scipy builds.

Here's the summary:

Wrong variable name was evaluated so the scipy images were pulling from base-notebook instead of scipy-notebook upstream causing a regression
Added conditional test for scipy images to make sure scipy is in fact present to catch this regression condition if it happens again


⚠ Bofrost.de has degraded performance

In 810b1b3, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1077 ms

Resolved: Bofrost.de performance has improved in e09eaf3 after 4 hours, 14 minutes.


FIX for 2.2.0 buglet in two Makefile.am preventing OpenEXR upgrade with older version installed

I have been porting the ilmbase and OpenEXR 2.2.0 packages for FreeBSD and came across one issue with OpenEXR, and that is include file ordering.
If I

have OpenEXR and ilmbase 2.1.0 installed,
upgrade ilmbase to 2.2.0, and
then attempt to build OpenEXR 2.2.0,

it will fail because the OpenEXR 2.2.0 grabs the OpenEXR 2.1.0's header files from the system include directory.
The obvious workaround is "deinstall OpenEXR 2.1.0 before attempting to build 2.2.0", but that subverts all our automation and I believe is a general issue worth fixing.
The culprit apparently is the INCLUDES = statement in the IlmImf/Makefile.am and IlmImfUtil/Makefile.am, these have code similar to, respectively:
INCLUDES = @ILMBASE_CXXFLAGS@ \
           -I$(top_builddir)  \
           -I$(top_srcdir)/config

or
INCLUDES = @ILMBASE_CXXFLAGS@ \
           -I$(top_builddir)  \
           -I$(top_srcdir)/IlmImf  \
           -I$(top_srcdir)/config

Now, on my system ilmbase and OpenEXR share the include path, and both stuff their includes into /usr/local/include/OpenEXR/. This is reflected in<EMAIL_ADDRESS>This also means that the OpenEXR 2.2 build will grab the older 2.1 installed include files.
The fix is simple, move the @ILMBASE_CXXFLAGS@ after the local -I$(top_whichever) options, such as (only for IlmImfUtil/Makefile.am):
INCLUDES = -I$(top_builddir)  \
           -I$(top_srcdir)/IlmImf  \
           -I$(top_srcdir)/config \
       @ILMBASE_CXXFLAGS@

Then the local includes will get preference, and the system includes will only fill in the missing pieces (i. e. ilmbase stuff where required).
Please consider making such changes before the next release.

Looking into the backlog of open OpenEXR issues. This should be resolved with the improvements to cmake.  Closing the issue for now, feel free to re-open or file a new issue if you need further help.


Do not ignore empty collections in ListEditor

We used to ignore empty collections inside a ListEditor which meant that
a list editor could not be used to create lists that contain empty
lists, maps or sets.
Fixes #3868

This passes on Travis... I'm seeing test failures on master locally though?

LGTM. What test failure are you seeing?

FAIL	github.com/attic-labs/noms/go/perf/suite

I have a slight memory of it being problematic 2 years ago

Do we need Emptyable after this?

Not sure. Will look into it.

I think we can remove the Emptyable interface, but leave the Empty()
methods. See also:
http://neugierig.org/software/blog/2019/11/interface-pattern.html
On Tue, Dec 3, 2019 at 8:20 PM Erik Arvidsson<EMAIL_ADDRESS>wrote:

Do we need Emptyable after this?
Not sure. Will look into it.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/attic-labs/noms/pull/3869?email_source=notifications&email_token=AAATUBCETOBZDJK5XC7CM33QW5D4HA5CNFSM4JVDJY52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEF336QA#issuecomment-561495872,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAATUBA2YG57ZORZORHICRLQW5D4HANCNFSM4JVDJY5Q
.

I'm still curious to what might break in Attic with this change. If I understand correctly the attic processing pipeline depended on this behavior. To me that seems like a breach of abstraction and the attic pipeline should have been able to deal with this.

I mean attic doesn't exist anymore so it's irrelevant. But it sounds like Attic UI (or pipeline) was relying on the fact that removing the last item from a collection would also remove the collection itself from its parent, and so-on, recursively.

You can land this whenever you're ready, thanks!


Imgbot broke JPEG

Just faced: https://github.com/MichaIng/DietPi-Docs/pull/794/files
See the Dropbear logo at the bottom, which has its bottom content removed.

Hello, we will review this issue, but it would help if we would have a larger sample of images that are breaking to identify patterns.
For now you can use our ignoredFiles option to exclude the image with the issue from optimization as mention here: https://imgbot.net/docs/#configuration .

For me it is as well the first JPEG I see breaking, so I have no other example. Out of interest, I saved the file again with GIMP, removing some metadata. If this works, it might give an indication.

Sorry for bumping, but just saw same result as @MichaIng. Some 10px from bottomline cropped from jpg.

Are you pertaining to me @MichaIng ?

Of course, GrigoreMihai asked for further examples. I have only one, so if you have another one, that might help. An "I have the same issue" comment doesn't help here, but the images themselves are needed to investigate why this happens 🙂.

@MichaIng due to its nature, I will not share JPGs publicly, sorry

Just faced: https://github.com/MichaIng/DietPi-Docs/pull/794/files
See the Dropbear logo at the bottom, which has its bottom content removed.

Trouble shooting will help , starting over, turning problematic objects off and on 9 times out of 10 the issues is no longer an issue.

Trouble shooting will help , starting over, turning problematic objects off and on 9 times out of 10 the issues is no longer an issue.

I am open to help troubleshooting, but what do you mean with turning off and on the problematic object, in the context of using ImgBot?


[Docker Desktop] Release MSI installer

Tell us about your request
Provide an MSI installer for Community Desktop to make it easier for managed deployments of free Docker Desktop
Which service(s) is this request for?
Desktop
Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?
Managed deployments with an .exe are harder than with an MSI and this will ease the burden for those in an enterprise setting
Are you currently working around this issue?
N/A
Additional context
N/A
Attachments

Having investigated the cost of this and looking at this compared to other things we could work on  such as
https://github.com/docker/roadmap/issues/12
and
https://github.com/docker/roadmap/issues/7

we won't be doing this in the near term. Moving back out of investigation.

Not having an MSI for the Community edition is VERY disappointing news!  And how is there a high cost to develop this?!  You already have one for the more complex Enterprise Edition.

Hi everyone! We are reviewing this topic for 2024 and would love to hear your feedback, in terms of operational context, how MSI helps and any other thoughts on how to improve Docker Desktop installation and package deployments.
Feel free to book some time with me: https://calendly.com/kat-tomrushka/30min

Trying to deploy the Leaky Vessels fix in an enterprise would be so much easier with an MSI.

We are pleased to announce that we have commenced development on the new installer.
Should you have any insights or suggestions you'd like to share, we warmly invite you to leave a comment here, utilize the feedback form, or arrange a brief interview with me. Your input is invaluable to us, and we look forward to hearing your thoughts. Thank you!

The MSI is already shipped and available for business customers!
https://www.docker.com/blog/docker-desktop-msi-installer-login-enforcement-alternatives


Copy files and don’t flatten the directory structure

When I copy files, in my case images, the directory structure is flatten. Is there any possibility to prevent this?
I want to keep the structure, because also I have some duplicate names of images and then the build stops - which makes sense.
Thanks!

mix.copyDirectory('resources/images', 'public/images'); ist the answer

Can't get some file types to be excluded!


fix(TCOMP-408): make test log level info

What is the current behavior? (You can also link to an open issue here)
a complete build creates 160Mo of logs because some tests are using the DEBUG or even TRACE level.
What is the new behavior?
Now all traces are using the INFO level and we have 6Mo of logs ;)
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Pull request test result: failure :x:


[Web-App] Target Reward: connected to the backend

https://www.notion.so/saladtech/Add-Add-to-Chopping-List-Button-to-the-Reward-Page-with-request-d10b569b0cce403fa3c46f3a0f48d5fc?pvs=4
https://www.notion.so/saladtech/Get-the-initial-data-about-the-Target-Reward-and-update-it-according-to-the-update-rules-2-days-7ba83b81ff3c4f7985e10103dd1c8f3f?pvs=4
https://www.notion.so/saladtech/Connect-to-backend-65a726abb63b4ea0a16512b3e301599e?pvs=4
https://www.figma.com/file/neYpmmJ5Y0cKjltKeEE3Si/App-Library?node-id=5223-78336&t=vgaAI6nAsua8QSGa-4

I found a bag with the first reward render
It shows Remove As Target Reward button firstly
https://user-images.githubusercontent.com/41080668/228028280-7485147b-c81c-4e8b-99d5-3c3aa2d676de.mp4

I found a bag with the first reward render It shows Remove As Target Reward button firstly

resolved


Updates icons name in the Database

Following the migration to Quasar 1.x, fontawesome has been updated to 5.x. It may be needed to migrate the database because the icon names has changed

Database has been updated manually.


mc8020

can you update your tool to work with zte mc8020 ?

Please update your tool to work with zte mc801a ?

I apologize, but the only device I have is the mu5001


Selected Date gets Unselected

Ionic version:  (check one with "x")
[ ] 2.x
[ ] 3.x
[x] 4.x
Ion2-calendar mode:  (check one with "x")
[ ] components mode
[x] modal mode
I'm submitting a ...  (check one with "x")
[ ] bug report
[ ] feature request
[x] help me
Current behavior:

When ever I select a date and close the modal the date gets selected but when I reopen the modal the selected date is not hilighted.
Expected behavior:

I want the date to be selected untill I reload/refresh the page.
Steps to reproduce:

Related code:
insert short code snippets here

Other information:
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Ionic:

   Ionic CLI                     : 5.4.5 (/home/d-Evil/.nvm/versions/node/v10.16.3/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.11.4
   @angular-devkit/build-angular : 0.13.9
   @angular-devkit/schematics    : 7.2.4
   @angular/cli                  : 7.2.4
   @ionic/angular-toolkit        : 1.3.0

Cordova:

   Cordova CLI       : 9.0.0<EMAIL_ADDRESS>   Cordova Platforms : android 8.1.0
   Cordova Plugins   : cordova-plugin-ionic-keyboard 2.2.0, cordova-plugin-ionic-webview 3.1.2, (and 23 other plugins)

Utility:

   cordova-res : not installed
   native-run  : 0.2.9

System:

   Android SDK Tools : 26.1.1 (/home/d-Evil/Android/Sdk)
   NodeJS            : v10.16.3 (/home/d-Evil/.nvm/versions/node/v10.16.3/bin/node)
   npm               : 6.11.3
   OS                : Linux 4.15

Hi Papuruth,
I have a similar issue in component mode, whenever I refresh the calendar view (changing style of dayList etc...) and used a "SetTimeOut()".
Thanks for the help!
Best regards,
Radious

I too have the same issue.
Any solution you have found out?
Please help me out, rest of the things are perfectly fine.
Thanks in advance.


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 10:06:29 on 2023.04.22
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 1, errors out: 0
Original problem ID: 19861
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=19861

Problem has been resolved in 3m 0s at 10:09:29 on 2023.04.22
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 19861


Major version bump

MR #149 would switch the json parser from boost to nlohmann. Since we only have two dependencies this is a pretty big change, definitely enough to warrant a major version bump. But while we're there, I might clean some things up.
Here's what I had in mind:

Replace boost dependency with nlohmann
Delete non-templated versions of the classes in generic/
Move templated classes out of generic/ and into the top level, remove the generic:: namespace
Change the namespace of the project, from lwt:: to lw3, or lwt::v3:: or something, to make it possible to run both versions side-by-side
Only support C++17 and up (drop support for C++11, C++14)

In short I would introduce a lot of breaking changes while making it possible for people to keep using the old version, even if they share a codebase with people using the new version. I appreciate any feedback on the best way to do this.

Change the namespace of the project, from lwt:: to lw3, or lwt::v3:: or something, to make it possible to run both versions side-by-side

I like basically everything about this, except for the fact that you're making versioned APIs just so things in Athena won't break, which now will require:

All users who want to track the project development to change their API usage regardless of if they need to (this is a pretty small ask though)
For ltwnn as a project to have to continue to support deprecated APIs as long as they are used in Athena — which is basically forever. This seems like it will now slow development because you'll need to forever test and support both APIs even though the whole point of the new release is to rid yourself of the old. Am I missing something basic here?

I admittedly don't have as much experience dealing with these integration issues with large monolith projects, so I think that @lukasheinrich and @jpivarski can probably give better advice.

Yeah I'd be curious about why @jpivarski decided to put the major version into the API for e.g. uproot, and whether that was a good idea in hindsight.
One thing to keep in mind here is that lwtnn is an extremely low-maintenance project, both for me as the developer and for users. So yes, versioning the API is just so things in Athena won't break, but not breaking the API one of the central goals of the project.

Putting the major version into the package name, i.e. "pip install uproot3" and "pip install uproot4", was a mistake. What I hadn't anticipated was that downstream dependencies would pin to specific versions (in projects that update over time, not just one-time tutorials), and then when "pip install uproot" switched from meaning "uproot3" to meaning "uproot4", there were version + name combinations that didn't work. It didn't matter that it was advertised months in advance, and the diagrams I made of combinations that would work and combinations that would not work didn't help, either. It's just a bad idea: the package namespace must never change.
What probably would have been fine would be to put the old and new APIs within a single package, such that old API users have to
import uproot.v3 as uproot

from a submodule instead of a separate package. I didn't get the impression that anyone had any problems with the
import uproot3 as uproot

one-line change to keep old code alive. Anyone who didn't know that the API change was coming found out about it through one of a small set of error messages that I recognized and could immediately recommend the one-line change; there were no complaints thereafter. So "put old codebase in a submodule" probably would have been fine, whereas "swap package names in PyPI" was bad.
Starting a new GitHub repo has not caused any problems at all. This can be considered a "development detail," which has little to no user-level consequences. On the other hand, rebooting git history cleaned up a lot of mess and sped up "git clone" times.
In a C++ project, the packaging problem may be moot because I don't think there's a global namespace of packages that is universally used among C++ projects. The idea of putting ltwnn in a versioned namespace like lwt::v3:: doesn't sound bad to me, as I've said putting uproot3 in a submodule probably would have been fine. Users who update and get compiler errors would ask, "What happened?" and you can tell them about the one-line change they have to make to rename namespaces. It might be in a lot of files, though (e.g. at the top of every .cpp file).

One thing to keep in mind here is that lwtnn is an extremely low-maintenance project, both for me as the developer and for users. So yes, versioning the API is just so things in Athena won't break, but not breaking the API one of the central goals of the project.

The idea of putting ltwnn in a versioned namespace like lwt::v3:: doesn't sound bad to me, as I've said putting uproot3 in a submodule probably would have been fine. Users who update and get compiler errors would ask, "What happened?" and you can tell them about the one-line change they have to make to rename namespaces.

If this is the best way to update and break APIs inside of a monolith like Athena then I guess moving forward with this should work.
My concern is that this (having people rely on versioning in the API and not rely on versioning a release) ends up keeping the current v2 APIs around in the main codebase forever (and not just on a v2 release branch) because some Athena user might at some point want to use it even though it is fully deprecated. This concern is less practical then the concerns of getting new APIs into Athena to use now, but the idea of having to keep around v2, v3, v4,... APIs forever in the code base seems like a bit of an anti-pattern for a project under version control.
Am I missing something here? It might be that I don't (and I know I don't) fully understand the Athena Externals system for integration of things like ltwnn.


Add an example config file

This is so much intensely in flux that I am pretty sure this is going to become out of date very soon. So let's skip this for a while?

Sure. Do you want me to leave open or close?

I think we should leave it open because we def want this at some point...good to have it there for the medium-term todo list :)

ok! I usually put the sample to be a nice working local copy - do you mind
if I close the PR and just open an issue instead?
On Mon, May 8, 2017 at 10:51 PM, Chris Holdgraf<EMAIL_ADDRESS>wrote:

I think we should leave it open because we def want this at some
point...good to have it there for the medium-term todo list :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/yuvipanda/builderhub/pull/7#issuecomment-300067904,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAB23p2rVgeScq0bvAKOqcvzcDiaNPkKks5r3_7SgaJpZM4NUy-t
.

--
Yuvi Panda T
http://yuvi.in/blog

Opened #10, going to close this now :)

oops! I didn't notice this was a PR, sounds good to me


TODO: hamel to explore GUIs

I need to dig more into these from the README.  I couldn't get it to work, likely am doing something wrong.

Using the GUI
Deploy the training backend with three business functions (launch, train, completion in __init__.py). Then run the Gradio GUI.
modal deploy src
modal run src.gui --config=... --data=...

The *.modal.host link from the latter will take you to the Gradio GUI. There will be three tabs: launch training runs, test out trained models and explore the files on the volume.

I was able to launch it https://sss8j974avg9wq.r5.modal.host/


[MPQEditor] Introduce 'media' for MPQEditor

This commit introduces 'media'  for MPQEditor.
Draft: #1505
Related: #1491
ONE-vscode-DCO-1.0-Signed-off-by: s.malakhov<EMAIL_ADDRESS>

Thanks for your work! 😄

BTW, when I click on that 'X' icon in 'visq path' box, it only reloads the model.circle file on the right side. What does it mean to be?

Thanks for your work! smile
 BTW, when I click on that 'X' icon in 'visq path' box, it only reloads the model.circle file on the right side. What does it mean to be?

It clears visq_view.
By default, the model-view opens in selector mode, but in case visq data is loaded, model_view load the model in visq mode. So to reset to selector mode, we may press the x button. But IMHO in case we don't visq data, it should be disabled.

@stamalakhov
Oh, I think that you have removed the code.
So it's now unrelated but to say, I would like to suggest 'Show Graph' or 'Display Graph' instead of 'Model Graph'?

@stamalakhov

But IMHO in case we don't visq data, it should be disabled.

Oh, It seems that you just have removed the code. So it's now unrelated but to say, but for later, I would like to suggest 'Show Graph' or 'Display Graph' instead of 'Model Graph', for the text next to the checkbox.

Ahhh. OK. I'll rename it.


[Feature Request] Auditing, Soft Delete, Multi Tenant, Global Query Filters using shadow properties

Description
https://trailheadtechnology.com/entity-framework-core-2-1-automate-all-that-boring-boiler-plate/

Hello @Ma3yTa ,
Thank you for reporting, we will look at this feature.
Best Regards,
Jon

Performance Libraries
context.BulkInsert(list, options => options.BatchSize = 1000);
Entity Framework Extensions • Entity Framework Classic • Bulk Operations •  Dapper Plus
Runtime Evaluation
Eval.Execute("x + y", new {x = 1, y = 2}); // return 3
C# Eval Function • SQL Eval Function


LightGBM saveNativeModel() not writing file on Databricks

After successfully training a LightGBMClassifier or LightGBMRanker as the last stage in an MLLib pipeline, and trying to save the native model out to dbfs using this command:
model.stages[-1].saveNativeModel('/dbfs/tmp/lightgbmNativeTemp.model')
The file never gets written. Any idea why this might be happening?

@tyler-romero isn't that a local url?  For dbfs I believe you need to specify dbfs://...

eg see: https://docs.databricks.com/user-guide/dbfs-databricks-file-system.html
we just create a dataset and save it using the spark API:
https://github.com/Azure/mmlspark/blob/master/src/lightgbm/src/main/scala/LightGBMBooster.scala#L112
If you ran this scala code, where would the file get saved?
val rdd = session.sparkContext.parallelize(Seq("testing saving some text somewhere..."))
import session.sqlContext.implicits._
val dataset = session.sqlContext.createDataset(rdd)
val mode = SaveMode.Overwrite
dataset.coalesce(1).write.mode(mode).text(filename)

Oh yeah, you're right! Using dbfs:/tmp/lightgbmNativeTemp.model worked. Thanks!


On login and Register page there is not password visible option which is not a good user experience

I want to add an icon fa-eye which helps user to see the password which he/she is inserting.
enhance user experience and help to check user password visibility while filling password.

after my changes it look like

assinged 👍


[prim_count] Updated comments to reflect all changes in #10378

In #10378 the behavior of prim_count was changed. #10603 didn't catch all cases.
In particular the documentation of clr_i still reflected partially the old behavior.

As I only changed the comment, I have no idea why CI failed/timed out...


Iterate through subscriptions for azure inventory

looks good to me, it organizes code in a cleaner way. It's missing a single line (https://github.com/lacework-dev/scripts/blob/main/bash/lw_azure_inventory.sh#L66) that I hope the PR will merge automatically


Upgrade nns governance did

Motivation
Update nns/governance.did.
Changes

extend SwapParameters with missing fields that needs to be displayed for 1-proposal.
update deploy_new_sns related types
add includeAllManageNeuronProposals param

Tests
Unit tests work.

@mstrasinskis already approved!


Cannot build webgl on multiplatform project

I work on a project where I must build a VR version using steamVR, and a webgl version that uses keyboard + mouse. The problem is that once I import the steamVR package, it adds automatically openVR, which is not handled in webgl but unity still tries to include it. The problem comes from the fact that the elements in the Runtime folder (openvr_api, ucrtbased, XRSDKOpenVR) from the openVR package do not exclude the WebGL platform, and as it is in a scoped package, the user cannot change it.

Thanks for the report. Give this a try: https://github.com/ValveSoftware/steamvr_unity_plugin/releases/tag/2.7.1RC

Closing pending feedback.

Closing pending feedback.


problem with provided rmbt_init.sql

Hi,
Thank you for your support and provide us the needed SQL files.
But now, i get in some troubles with import the rmbt_init.sql file. Below you will se the error messages.

Any suggestions about that syntax error?
br
Bernhard

Hi,
did you start with importing rmbt.sql before rmbt_init.sql?
rmbt.sql contains the empty tables and data structures, while rmbt_init.sql contains an initial set of values.

Hi @cproof,
Thank you for sharing the .sql file.
I tried importing rmbt.sql but got the errors as below.
cat rmbt.sql | psql rmbt -1 -a
--
-- Name: clc12_all_oesterreich_gid_seq; Type: SEQUENCE; Schema: public; Owner: rmbt
--
CREATE SEQUENCE clc12_all_oesterreich_gid_seq
    AS integer
    START WITH 1
    INCREMENT BY 1
    NO MINVALUE
    NO MAXVALUE
    CACHE 1;
ERROR:  syntax error at or near "AS"
LINE 2:     AS integer
            ^
ALTER TABLE clc12_all_oesterreich_gid_seq OWNER TO rmbt;
ERROR:  current transaction is aborted, commands ignored until end of transaction block
--
-- Name: clc12_all_oesterreich_gid_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: rmbt
--
ALTER SEQUENCE clc12_all_oesterreich_gid_seq OWNED BY clc12_all_oesterreich.gid;
ERROR:  current transaction is aborted, commands ignored until end of transaction block

This is new to me, maybe I missed something.
Hoang

Which version of PostgreSQL are you using?
CREATE SEQUENCE ... AS ... is supported in PostgreSQL versions >=10

Well, I was using PostgreSQL 9.6 on Fedora.
Now I am removing it and installing PostgresSQL 10.3.
Thank you for the suggestion.

same here - after upgrading the database the errors are gone.

Thank you for the feedback, I'll update the README accordingly.
While the database itself does not require any PostgreSQL 10-specific functionality, it seems that the pg_dump utility distributed with PostgreSQL 10 creates SQL that only can be re-imported by PostgreSQL 10.


build: use system speex when possible

Following #658 (comment), the speex library is now handled like a normal dependency: cubeb will link against the system version if available, and fall back to the bundled one if not.
I've also added a BUNDLE_SPEEX option, so that you can force the use of the bundled library if needed (e.g. creating a standalone libcubeb on a system where libspeex is available).
I also had to move the bundled library to a separate folder. As src is always added as an include path, the headers in src/speex would conflict with system headers. And it also clears the relationship between cubeb and speex. I choose the "subprojects" name to follow the Meson convention, since CMake does not have one. A bit OT, but if you're curious you can see their rationale here
Lastly, I added cubeb_log.cpp to the list of sources of test_resampler, as I was getting linking errors when building with BUILD_SHARED_LIBS=true
Fixes #658

Strange, I'm not getting that EXPORT issue on my machine... Working on it.

Fixed :D

Thanks, this is much cleaner.  Appreciate all the build system cleanups!


Is Android support on the roadmap?

I tried out the app on Android and initially got a blank screen.
After digging around a little bit, I noticed it was just a style issue. The mirroredVideo transform in the video styles is causing no video to display on Android.
https://github.com/jitsi/jitsi-meet-react/blob/master/features/base/media/components/native/styles/Styles.js#L15
You could put a Platform.OS check around that to not flip the video on Android.
Once I fixed that, I was able to see my local media, but I never saw my Android stream on the meet.jit.si website.
Is there Android support coming in the near future, or is there currently work happening on it?
Thanks,
Bryan

Thanks for reporting that!
We're working on Android support.


add primary image

The need RDF structure and code accessing it (NeedBuilder etc) require adding images. One image must be settable as the primary image.

It should be possible to define a square crop-area in the image-picker in create-post. We assume that there'll be large images (e.g. of a couch, a portrait with surroundings) that won't work well when sized down in the square-image-component. This way users can specify the most significant portion of the image. Ideally there should be preview-function in the picker, that shows the image at the size it later will appear at.
In the absence of this mechanism, we might also consider zooming just a bit (e.g. 10%) on any attached photos.

Thinking about this when we are not planning to do it is a waste of time.


Decal Fade Does Not Work

Whilst hunting around decals I noticed that the fade does not work. Try setting fadeTime higher, lower, or equal makes no difference.
Here's what it says the variable should do.
https://github.com/GarageGames/Torque3D/blob/master/Engine/source/T3D/decal/decalData.cpp#L153-L156
And here's the only place it gets used:
https://github.com/GarageGames/Torque3D/blob/master/Engine/source/T3D/decal/decalManager.cpp#L1093

Found out decals do fade out --- but only fade with vertColor enabled. Talk about esoteric!
Anyhow, issue closed.


[Enhancement] Rectify some behaviors when auto creating tablet

When the backnum is smaller, try to creating more tablets

if (backendNum <= 12) {
    bucketNum = 2 * backendNum;
} else if (backendNum <= 24) {
    bucketNum = (int) (1.5 * backendNum);
} else if (backendNum <= 36) {
    bucketNum = 36;
} else {
    bucketNum = Math.min(backendNum, 48);
}

Change the behavior when user specify the tablet num (1) If the user has specified the tablet num, StarRocks will comply the number, ignore the Config.enable_auto_tablet_distribution (2) If enable_auto_tablet_distribution = true, AUTO Tablet Distibution
also take effect on exist table when adding new partitions

ColocateTable should comply the original tablet num when creating table. ColocateTable should keep the tablet num is same among partitions. So the auto tablet distribution is not suitable for this case.

Remove the dynamic_partition.buckets After the AUTO Tablet Distibution, the dynamic_partition.buckets is not necessary. We can auto determine the number of tablet

What type of PR is this：

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

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

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

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

Bugfix cherry-pick branch check:

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

[x] 3.0
[x] 2.5
[ ] 2.4
[ ] 2.3

run starrocks_fe_unittest

Need backport to 2.5  LTS version？


error: undefined symbol: cpuinfo_emscripten_init

When trying to use CPUInfo on Emscripten, I get the following linker error:
error: undefined symbol: cpuinfo_emscripten_init
warning: To disable errors for undefined symbols use `-s ERROR_ON_UNDEFINED_SYMBOLS=0`

Indeed, no file in this repository provides an implementation for function cpuinfo_emscripten_init.
I've seen that XNNPACK guys contributed this function, but where is the implementation? I've seen that their bazel file mentions some src/emscripten/init.c file, but I cannot find it (even their patch file does not contain it).

@Maratyszcza

I'll include src/emscripten/init.c in the next patch, but keep in mind that it is not sufficient to build XNNPACK for WebAssembly with CMake

I am not trying to build XNNPACK for WebAssembly. I am using cpuinfo in a different project.

Keep in mind that most information about CPU is not exposed in browser environment, so cpuinfo mostly guesstimates this data.

Of course. Even though its guesstimates, it's still better than nothing.

It looks like file src/emscripten/init.c cannot be added because CPUINFO_SUPPORTED_PLATFORM is false for build with Emscripten, which results to error: undefined symbol: cpuinfo_emscripten_init

I made a patch to solve this problem, but I do not know exactly what side effects it can lead.
Patch: undef_symb_emsc.txt

This issue is still occurring with CMake. The suggested patch to include Emscripten here appears to work for my usage in a different downstream project: https://github.com/pytorch/cpuinfo/blob/85e931e36af24a3ec73b146b9fe8423b4b2a67db/CMakeLists.txt#L80-L85
(so CPUINFO_SUPPORTED_PLATFORM remains TRUE)
Are there other changes that would be needed to accept that patch? Maybe some test updates or adding "Emscripten" here too?
https://github.com/pytorch/cpuinfo/blob/85e931e36af24a3ec73b146b9fe8423b4b2a67db/README.md#L11-L12


Removed "max" from time range enum

See here as to why I removed the "max" option from "time interval" enum
https://www.notion.so/Yahoo-Finance-Low-Latency-Rapid-API-61a3f7aa451d4558bc3d89f38dd39494


Support options?

I want to pass options to git tag (The one I want is --annotate).
http://git-scm.com/docs/git-tag
https://github.com/sindresorhus/dargs might come in handy for this.

okay
2015-04-03 18:35 GMT+08:00 Steve Mao<EMAIL_ADDRESS>
I want to pass options to git tag (The one I want is --annotate).
http://git-scm.com/docs/git-tag
https://github.com/sindresorhus/dargs might come in handy in for this.
--
Reply to this email directly or view it on GitHub
https://github.com/cutsin/git-tag/issues/3.

--
moonless.net


Release Candidate 0.9.0-rc2

This patch marks release candidate 0.9.0-rc2.

Codecov Report

Merging #838 into release/0.9.0 will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           release/0.9.0    #838   +/-   ##
=============================================
  Coverage           8.79%   8.79%
=============================================
  Files                 25      25
  Lines               2979    2979
=============================================
  Hits                 262     262
  Misses              2681    2681
  Partials              36      36

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 2ca0266...e612d8e. Read the comment docs.


Fix СacheItem and PrefixedCache

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
-

👍


Crash on exit with sf::Style::None

When I run the example hello world app, and change the style to sf::Style::None, the app crashes on exit inside SFML.  I traced it down to the destructor for NonLegacyRenderer.  In NonLegacyRenderer.cpp at line 308 a context is created with sf::Context context.  If I comment that out it no longer crashes.
Should the destructor be creating a context at application exit?  I don't believe any of the gl delete calls need it.

Just tested with current master and SFML 2.5, cannot reproduce.


.csv results output does not play well with Excel or Google Sheets

Both Excel and Google Sheets expect that .csv means comma delimited, and by default import the file improperly.
If it was named .txt, or actually made comma delimited, this would be resolved.
I'm happy to do a PR to implement either fix, if this fix or something like it is desired.

Hi!
Sure, go ahead with the PR. The class responsible for export to csv CsvExporter
Thanks in advance,
Adam

@jackmott, Excel take the list delimiter from your regional settings. You can check this setting (TextInfo.ListSeparator) for different cultures with help of CultureInfoExplorer.
I like semicolon like a list separator instead of comma because comma can be also NumberFormat.NumberDecimalSeparator. In case of semicolon, you are sure that it is a list separator.
Anyway it is a good idea to have the separator as a parameter. It would be cool to add it as an argument to the CsvExporter constructor (with a default value) and CsvExporterAttribute.

Now we support RFC 4180:

Fields containing line breaks (CRLF), double quotes, and commas should be enclosed in double-quotes.
Default separator will be chosen based on your CurrentCulture
You can also specify separator manually (comma or semicolon)


Fix inflight middleware for api-monolith

Changes

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

Current dependencies on/for this PR:

main

PR #433

PR #434   👈

This stack of pull requests is managed by Graphite.


Use local CCryptoBoringSSL_arm_arch.h ARM header

Motivation:
Fix the build on these AArch64 platforms.
Modifications:
Use the local renamed header.
Result:
The linux assembly files build on Android AArch64 again and all tests pass.
Checklist

[x] I've run tests to see all new and existing tests pass
[x] I've followed the code style of the rest of the project
[x] I've read the Contribution Guidelines
[ ] I've updated the documentation if necessary - no need

The recent BoringSSL update in #113 broke building this package on Android AArch64 and likely iOS too, so I looked and figured you meant to change this header.

Superseded by #115.


Bug fix: inserting Array of nullable primitive

Description:
Unable to insert the data into array of nullables
E.g.
CREATE TABLE default.t
(
    `a` Int8,
    `arr` Array(Nullable(Int8))
)
ENGINE = MergeTree
ORDER BY a

Trying to push an array(Scala code):
    val driver = new ClickHouseDriver()
    val connection = driver.connect("jdbc:clickhouse://localhost:8123", new Properties())
    val statement = connection.prepareStatement("insert into default.t (a, arr) values (?, ?)")

    val a = Array(1.toByte, 2.toByte, null).map(_.asInstanceOf[AnyRef])
    val arr = connection.createArrayOf("Array(Nullable(Int8))", a)

    statement.setByte(1, 1.toByte)
    statement.setArray(2, arr)
    statement.addBatch()
    statement.executeBatch()

    connection.close()

Error:
class [Ljava.lang.Object; cannot be cast to class [B ([Ljava.lang.Object; and [B are in module java.base of loader 'bootstrap')
java.lang.ClassCastException: class [Ljava.lang.Object; cannot be cast to class [B ([Ljava.lang.Object; and [B are in module java.base of loader 'bootstrap')
	at com.clickhouse.client.data.ClickHouseRowBinaryProcessor$MappedFunctions.writeArray(ClickHouseRowBinaryProcessor.java:57)
	at com.clickhouse.client.data.ClickHouseRowBinaryProcessor$MappedFunctions.serialize(ClickHouseRowBinaryProcessor.java:486)
	at com.clickhouse.jdbc.internal.InputBasedPreparedStatement.addBatch(InputBasedPreparedStatement.java:333)
	at com.blackmorse.spark.clickhouse.types.Int8Tests.$anonfun$new$4(Int8Tests.scala:37)
...

Reason:
when using (e.g) Array(Nullable(Int8)) type, ClickHouseArrayValue but ClickHouseRowBinaryProcessor still expects ClickHouseByteArrayValue.

Thank you @Blackmorse! Actually this has been covered in my local changes.
Basically, widen unsigned types is probably not the best way, because it consumes more memory and has side effects in type conversion. I added UnsignedLong, UnsignedInteger, UnsignedShort, and UnsignedByte classes to better handle unsigned primitive types along with some changes in *Value classes, and more tests to ensure they work as expected. A few options were added too in case people prefer the old way.
I've completed the read part last night, and I should be able to complete the write part in a day or two.

Hi, @zhicwu
Do you have any idea when you can apply you local code changes mentioned before? This issue is affecting my software, so maybe it's worth merging it now and not to wait for huge changes from your side?
Thanks

Hi, @zhicwu Do you have any idea when you can apply you local code changes mentioned before? This issue is affecting my software, so maybe it's worth merging it now and not to wait for huge changes from your side? Thanks

Hi @Blackmorse, I'm sorry for blocking your work. I must confess that I didn't spend any time on this project in the past weeks due to work on hand.
Are you expecting a patch release in maven central? As you probably noticed, there are some more changes in develop branch and the legacy driver got removed. So if all you need is the latest release plus this PR, I'd suggest you to build and push new artifact to local maven repository.
If it's fine to use nightly build(v0.3.3-SNAPSHOT) and wait for a few more days, I can commit some changes in local in a day or two, which will surely fix the issue along with performance improvement(in addition to PR #1087). However, this involves breaking changes to reduce serialization cost - if you're using interfaces ClickHouseDeserializer, ClickHouseSerializer and ClickHouseDataProcessor etc., your code will be impacted.
Lastly, I'm sure there's always good reason to use nullable types, but another alternative approach I can think of is to use Array(Int8), which avoids boxed type and null flag in serialization.

Fixed in #1124.


git: Unable to install git unless it already exists in the system

Hello, I'm trying to make linuxbrew work on debian/ubuntu machines where I do not have root privileges. The only relevant package installed is build-essential. My goal is to have brew up and running in order to install all the packages I need in userspace.
I installed linuxbrew by downloading the install script and running it with:
$ wget "https://raw.githubusercontent.com/Homebrew/linuxbrew/go/install"
$ ruby -e "$(cat install)"

The installation succeded, but in order to install anything, I need git of course. The problem is that when I try to install it, brew will loop forever printing ==> Installing git.
This is the output:
$ brew install git --verbose --debug 2>&1
/home/youtux/.linuxbrew/Library/brew.rb (Formulary::FormulaLoader): loading /home/youtux/.linuxbrew/Library/Formula/git.rb
/home/youtux/.linuxbrew/Library/brew.rb (Formulary::FormulaLoader): loading /home/youtux/.linuxbrew/Library/Formula/xz.rb
/home/youtux/.linuxbrew/Library/brew.rb (Formulary::FormulaLoader): loading /home/youtux/.linuxbrew/Library/Formula/expat.rb
/home/youtux/.linuxbrew/Library/brew.rb (Formulary::TapLoader): loading /home/youtux/.linuxbrew/Library/Taps/homebrew/homebrew-dupes/tcl-tk.rb
==> Installing git
/home/youtux/.linuxbrew/Library/brew.rb (Formulary::TapLoader): loading /home/youtux/.linuxbrew/Library/Taps/homebrew/homebrew-dupes/tcl-tk.rb
==> Installing git
/home/youtux/.linuxbrew/Library/brew.rb (Formulary::TapLoader): loading /home/youtux/.linuxbrew/Library/Taps/homebrew/homebrew-dupes/tcl-tk.rb
==> Installing git
/home/youtux/.linuxbrew/Library/brew.rb (Formulary::TapLoader): loading /home/youtux/.linuxbrew/Library/Taps/homebrew/homebrew-dupes/tcl-tk.rb
==> Installing git
[... to infinity]

Could it be the case that brew is trying to call the git executable to load the homebrew-dupes tap, but it keeps failing because there is no git installed?

See https://github.com/sjackman/docker-linuxbrew/blob/91f509802167f10a1ba9394c3750197b9a6eb9b6/linuxbrew-standalone/Dockerfile#L6-L8
Try
# Install git without tcl-tk to prevent the error:
# Tapping homebrew/dupes. You must: brew install git
RUN brew install git --with-brewed-curl --with-brewed-openssl --without-tcl-tk

I think that perhaps --without-tcl-tk should be the default on Linux. The downside is that the GUI gitk won't be built. What do you think?

In that case you wouldn't benefit from the binary version already on Bintray, am I right? Or is that only an homebrew (for Mac OS) thing?
Maybe the brewed-curl and brewed-openssl options should be the default on Linux, too.

In that case you wouldn't benefit from the binary version already on Bintray, am I right? Or is that only an homebrew (for Mac OS) thing?

Bottles are only created automatically for Mac. Linux can use bottles, but they're not created automatically.

Maybe the brewed-curl and brewed-openssl options should be the default on Linux, too.

Yes, I think that would be a good idea.

FWIW, I have git 1.7.1 on my system (RHEL 6.5 x64), but it is older than the minimum recommended version.  Attempting to update git with linuxbrew results in a compliation error with homebrew/dupes/tcl-tk, so it sounds like there are multiple issues with tcl-tk being pulled in by git.

I've change the tcl-tk dependency of git from recommended to optional.


CurrentImplementationApiVersionSelector while versioning by URL path

Is the CurrentImplementationApiVersionSelector working while using URL path versioning? In case of header versioning everything works fine but in case of URL path versionig always the first version(1.0) of the controller is selected even if the another version(2.0) is specified as DefaultApiVersion.
Controllers:
[ApiVersion("1.0", Deprecated = true)]
[Route("api/{version:apiVersion}/Uri")]
public class UriController : ApiController
{
    [HttpGet]
    public string Get()
    {
        return String.Format("Hello from Uri 1.0");
    }
}

[ApiVersion("2.0")]
[Route("api/{version:apiVersion}/Uri")]
public class Uri2Controller : ApiController
{
    [HttpGet]
    public string Get()
    {
        return String.Format("Hello from Uri 2.0");
    }
}

[ApiVersion("3.0")]
[Route("api/{version:apiVersion}/Uri")]
public class Uri3Controller : ApiController
{
    [HttpGet]
    public string Get()
    {
        return String.Format("Hello from Uri 3.0");
    }
}

WebApiConfig:
        config.AddApiVersioning(options =>
        {
            options.ReportApiVersions = true;
            options.DefaultApiVersion = new ApiVersion(2, 0);
            options.AssumeDefaultVersionWhenUnspecified = true;
            options.ApiVersionSelector = new CurrentImplementationApiVersionSelector(options);

        });

        var constraintResolver = new DefaultInlineConstraintResolver()
        {
            ConstraintMap =
            {
                ["apiVersion"] = typeof( ApiVersionRouteConstraint )
            }
        };
        config.MapHttpAttributeRoutes(constraintResolver);

There are a couple of different issues going on here so let me try to break up the response into pieces.
URL Path Versioning
When you version your API in the URL path, you can't logically have a default version. The API version is instrinsically part of the path. In your example, you have the route template api/{version:apiVersion}/Uri. If an API version is not specified using this method, the URL becomes api//Uri.
Most service authors that use URL path versioning prefix the API version segment value with the letter 'v'. This would make the route template api/v{version:apiVersion}/Uri. Now, if an API version isn't specified, the path will become api/v/Uri.  I think it's pretty obvious that this won't exist.
The method in which the requested API version is internally set is - ever so slightly - different that any other method. All other methods go through the IApiVersionReader to extract the API version from the incoming request message. Trying to understand and parse the URL path in the same manner would be difficult and brittle. Since ASP.NET already provides a structured way to parse route templates, URL path versioning uses a route constraint instead. This allows you to craft your URLs however you want and just indicate which segment the API version should be extracted from.
You can use the route template as you defined it, but there is no way to assume a default because there are no matching candidates.
Default Version Selection
It may not be intrinsically obvious, but the DefaultApiVersion and ApiVersionSelector options are somewhat mutually exclusive. The purpose of the DefaultApiVersion is to simply define an assumed version without hard-coding the value for all fallback cases because every service always has some logical version number, even if it's not formally defined. The IApiVersionSelector is the extension point to select the appropriate API version given a request and the discovered API version model. The infrastructure does all the hard work of collecting the available API versions and you select the best one.
In your case, you elected to use the CurrentImplementationApiVersionSelector and have the following API versions defined:

1.0 (implemented, but deprecated)
2.0
3.0

This selector will always choose 3.0 from these choices. The only time it would ever use the default configured API version of 2.0 is if there were no candidate API versions to select from. For example, if your versions were all pre-release:

1.0-alpha
2.0-beta
3.0-rc

Any version with a status is not considered implemented. Additionally, deprecated does not mean not implemented.
If your intent was to have all clients that don't request a version start on 2.0, then you can just set the DefaultApiVersion. The default value for the ApiVersionSelector is an instance of the DefaultApiVersionSelector, which just always uses the value of the configured DefaultApiVersion.
Faking a Default API Version with URL Paths
There is one way that you can give the impression of an implicitly-version URL path. To enable this, you need to make multiple routes per controller.  API versioning stays out of the way of routing and only gets involved with resolving the appropriate controllers and actions.
For example, if your controllers were updated with additional routes:
[ApiVersion( "1.0", Deprecated = true )]
[Route( "api/uri" )]
[Route( "api/{version:apiVersion}/uri" )]
public class UriController : ApiController { /* ommitted */ }

[ApiVersion( "2.0" )]
[Route( "api/uri" )]
[Route( "api/{version:apiVersion}/uri" )]
public class Uri2Controller : ApiController { /* ommitted */ }

[ApiVersion( "3.0" )]
[Route( "api/uri" )]
[Route( "api/{version:apiVersion}/uri" )]
public class Uri3Controller : ApiController { /* ommitted */ }

Your controllers will be resolved using the following URLs:

URL
Version
Controller

api/uri
3.0
Uri3Controller

api/1/uri
1.0
UriController

api/2/uri
2.0
Uri2Controller

api/3/uri
3.0
Uri3Controller

api/uri?api-version=1.0
1.0
UriController

api/uri?api-version=2.0
2.0
Uri2Controller

api/uri?api-version=3.0
3.0
Uri3Controller

The last 3 entries are there because the default configuration uses an IApiVersionReader that extracts the API version from the api-version query string parameter. If you want to remove this behavior, you can implement a reader that always returns null.
public class IgnoreApiVersionReader : IApiVersionReader
{
    public string Read( HttpRequestMessage request ) => null;
}

You may have noticed that the example used the names UriController, Uri2Controller, and Uri3Controller. In setting up an example that would simulate your scenario, I found an edge case bug.  I'll create a new issue for this bug and correlate it back to this thread. For now, using different type names will make this setup work.
I hope that helps.

You well explained the problem with URL path versioning and DefaultApiVersion. Multiple routes on controller makes it bit confusing so i'm considering to choose e.g Custom Header versioning as this one fits better my scenario. Anyway thanks a lot for answer and solution. Cheers!


improve cli error message for file structure mishaps

got the following error when the problem was an erroneous src folder inside of the api directory. let me to check generators.yml, but that wasn't the issue. when I deleted the erroneous src folder, fern check worked again.
[Error: ENOENT: no such file or directory, open '/Users/dsheridan/Coding/fern-hookdeck/.fern/src/generators.yml'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/dsheridan/Coding/fern-hookdeck/.fern/src/generators.yml'
}

deep: fern cli should be more descriptive if there is a malformed api definition

this is outdated


Add filesystem module

Initial draft of print_tree() function

Codecov Report

Merging #16 (41a0033) into main (2ec4511) will decrease coverage by 2.68%.
The diff coverage is 27.27%.

@@            Coverage Diff             @@
##             main      #16      +/-   ##
==========================================
- Coverage   96.35%   93.66%   -2.69%
==========================================
  Files          12       14       +2
  Lines         548      568      +20
==========================================
+ Hits          528      532       +4
- Misses         20       36      +16

Flag
Coverage Δ

unittests
93.66% <27.27%> (-2.69%)
:arrow_down:

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

Impacted Files
Coverage Δ

openpipe/constant.py
100.00% <ø> (ø)

openpipe/data.py
100.00% <ø> (ø)

openpipe/filesystem.py
0.00% <0.00%> (ø)

openpipe/log.py
100.00% <ø> (ø)

openpipe/naming.py
96.15% <ø> (ø)

openpipe/sanitization/core.py
100.00% <ø> (ø)

openpipe/sequence.py
92.15% <ø> (ø)

openpipe/shot.py
90.74% <ø> (ø)

openpipe/show.py
98.66% <ø> (ø)

openpipe/show_scheme/core.py
96.93% <ø> (ø)

... and 4 more

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 6247a67...41a0033. Read the comment docs.


Review bpo-13386: Document documentation conventions for optional args

This is an old issue which I believe is within the remit of the docs WG. (Please correct me if I am misunderstanding what the WG does).

It seems, from at least a brief overview of the documentation that this most likely effects (builtins, io, os, etc), that modern usage of positional-only arguments is more limited than in the past, and keyword notation is used more consistently for functions that actually take such, at least more so than in the past, where I can recall lots of functions that took keywords but still used [] and number of instances of ]s nested many levels deep, which I found noisy, ugly and hard to read and parse—in fact, I even recall opening an issue about it back in the day due to my confusion over it.
However, this still seems worth reviewing, since there still seems to be a number of instances where [] notation is used when keyword=default notation should be used instead, e.g. in the socket docs for functions that I can confirm do indeed take keyword arguments. It might be worth going over this more broadly.
Also, to note, we now have / to indicate positional-only parameters in the function signature, which (at least to me) reads a lot cleaner and clearer than the old bracket notation, not to mention is much more consistent with both the actual Python signature, and the documentation of most if not all non-stdlib functions that do truly use them. But that's a much bigger change, and would need to be explained somewhere prominent such that docs readers are more likely to see them, perhaps along with keyword-only notation (e.g. by linking the FAQ entry).

This is now https://github.com/python/cpython/issues/57595, discussion should happen on that issue as noted in the May 2022 meeting.
A


 For sure it's a cut/paste error.

@karoldeland : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Looks good. Thanks @karoldeland


Create known DSP Disconnected test cases

Test cases to cover:

[ ] Test python package installs in pipeline via a a custom pip repo (internal repo, e.g. users using solutions like this )
[ ] Test minio connection behind self signed certs case, test should ensure custom bundle mounts on dspa's work as intended

As per @jgarciao , we currently have the ability to spin up real disconnected clusters (ease of this process still unknown)

Migrated to Jira: https://issues.redhat.com/browse/RHOAIENG-1687


Python implementation of Graph Algorithms

Ground rules:

Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
Pull Requests sent without claiming and referencing the Issue will not be entertained.
Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

The following Algorithms need to be added:

BFS
DFS
Kruskal's
Prim's
Dijkstra's
Floyd-Warshall Algorithm

I would like to do the DFS. Thank you.

Issue has been created separately in the Issues tab. Kindly take a look!


Inspector for upstream

So this is the bundled "remote inspector support" pull request for issue #6. You might not want to merge this in immediately and probably have some comments, but I want to get this out there and discussed. Here are my comments:

Only supports Qt 4.8
Requires some patches to QtWebkit (depends on my upcoming pull request #173) or my clone of qtwebkit-2.2 (https://gitorious.org/~lfranchi/webkit/lfranchis-qtwebkit)
The harness mechanism is a bit ugly, I'm not very happy with it. However I haven't been able to get it to work any other way---ideas appreciated, and if you can come up with a better way that works I'm happy to implement it.

I think this is fine enough for the initial stage, excellent work!
As for the harness, my only ideas so far are either (1) custom file system (2) custom network access manager. The object is to "fake" the resources seen by the corresponding web frame. Makes sense?

Yeah, i see what you mean. Not knowing much about the internals of the Inspector (man there's a lot of indirection in there...) I wasn't sure what to fake exactly. The issue I was having was that "injecting" a script into a frame wouldn't have it show up as a resource.
We could I guess fake the QNAM to pretend that there's a real file/script like the harness does right now... but then that seems quite complex to fake what we have already. Your thoughts?

In this case, not much we can do. I don't have any further as of now, I need to dig deeper...


Multiple path options in 1 quest

Where else have you looked for answers to this question?
Documentation
Share your question with as much detail as possible.
If I wanted to give players the choice to attack the castle or defend the castle, how would this be done within the confines of this plugin? My goal is to have a quest that players need to pick a side and they will get rewards based on side picked.

Quest block requirement https://pikamug.gitbook.io/quests/beginner/requirements


extra_parameters  not passing correctly for vRA version  7.X

Resulting in the following error:
Error:  Failed to complete #create action:  [unable to submit request:  the data specified within the request is invalid., Composition Exception.

Yep, we are working on this. It's from an upstream issue. :(

Basiclly we need to figure out how to add extra-params to this: https://github.com/chef-partners/vmware-vra-gem/blob/master/lib/vra/catalog_request.rb#L79-L85
Please reopen this in the vmware-vra-gem, this isn't specific to kitchen-vra.


JSON parser is not finished

JSON parser is not finished, requires completion to parse correctly JSON data received from Google Drive API referencing to files metadata...etc.

Maybe this repo created by me can help

Ty @Dariasteam, I will try to integrate your JSON parser into SyncMe framework ;)

wrong recipient?
On 1 September 2016 at 23:23, Dariasteam<EMAIL_ADDRESS>wrote:

Maybe this repo https://github.com/Dariasteam/JSON-cpp created by me
can help
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AdrianBZG/SyncMe/issues/19#issuecomment-244200681,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALQoJXAKk5aZo1vOwRkm1rC0gPo5m5DSks5qlzRbgaJpZM4H-qqJ
.

@ArtyMcLabin probably, sorry!


Illuminate\Validation\Rule::enum builder public methods do not expose methods expect() and only()

Laravel Version
v10.44.0
PHP Version
8.1
Database Driver & Version
No response
Description
Illuminate\Validation\Rule::enum builder public methods do not expose methods expect() and only().
While following https://laravel.com/docs/10.x/validation#rule-enum documentation to user Rule::enum to validate a input I think I found something wrong.

As you can see in docs the sintax Rule::enum(Enum::class)->expect([Enum:SOME_CASE]) or ->only([Enum:SOME_CASE]) is provided but when I try to use this, those methods just are not been exposed in public interface

Steps To Reproduce
Create a new request class and add a Rule::enum(Enum::class)->expect([Enum:SOME_CASE]) or ->only([Enum:SOME_CASE]).

Looking at the commit those were added only 2 weeks ago to 10.46.0 I believe, you are on 10.44.0.
https://github.com/laravel/framework/commit/8d47be393e43ffeacd49556471110454f868da5f