[WIP] Updated Packer to v1.5.1

To solve #41, I have applied the changes mentioned in the Packer documentation, however there are still several problems:

When using the plugin it produces a permission denied error (it seems that this is not the only case, see wata727/packer-post-processor-amazon-ami-management#59 and hashicorp/packer#8527).
crash.log
1970/01/01 00:00:00 [INFO] Packer version: 1.5.1 [go1.13.5 linux amd64]
1970/01/01 00:00:00 [DEBUG] Discovered plugin: arm-image = /usr/local/bin/packer-builder-arm-image
1970/01/01 00:00:00 using external builders [arm-image]
1970/01/01 00:00:00 Attempting to open config file: /root/.packerconfig
1970/01/01 00:00:00 [WARN] Config file doesn't exist: /root/.packerconfig
1970/01/01 00:00:00 Setting cache directory: ~REDACTED~/packer_cache
1970/01/01 00:00:00 Plugin could not be found at  (exec: "": executable file not found in $PATH). Checking same directory as executable.
1970/01/01 00:00:00 Current exe path: /usr/local/bin/packer
1970/01/01 00:00:00 Creating plugin client for path: /usr/local/bin
1970/01/01 00:00:00 Starting plugin: /usr/local/bin []string{"/usr/local/bin"}
1970/01/01 00:00:00 Plugin could not be found at /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell (exec: "/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell": stat /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell: no such file or directory). Checking same directory as executable.
1970/01/01 00:00:00 Current exe path: /usr/local/bin/packer
1970/01/01 00:00:00 Creating plugin client for path: /usr/local/bin/packer
1970/01/01 00:00:00 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell"}
1970/01/01 00:00:00 Waiting for RPC address for: /usr/local/bin/packer
1970/01/01 00:00:00 packer-provisioner-shell plugin: [INFO] Packer version: 1.5.1 [go1.13.5 linux amd64]
1970/01/01 00:00:00 packer-provisioner-shell plugin: Attempting to open config file: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: Setting cache directory: ~REDACTED~/packer_cache
1970/01/01 00:00:00 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
1970/01/01 00:00:00 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin190395704
1970/01/01 00:00:00 packer-provisioner-shell plugin: Waiting for connection...
1970/01/01 00:00:00 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin190395704
1970/01/01 00:00:00 packer-provisioner-shell plugin: Serving a plugin connection...
1970/01/01 00:00:00 Plugin could not be found at /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell (exec: "/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell": stat /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell: no such file or directory). Checking same directory as executable.
1970/01/01 00:00:00 Current exe path: /usr/local/bin/packer
1970/01/01 00:00:00 Creating plugin client for path: /usr/local/bin/packer
1970/01/01 00:00:00 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell"}
1970/01/01 00:00:00 Waiting for RPC address for: /usr/local/bin/packer
1970/01/01 00:00:00 packer-provisioner-shell plugin: [INFO] Packer version: 1.5.1 [go1.13.5 linux amd64]
1970/01/01 00:00:00 packer-provisioner-shell plugin: Attempting to open config file: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: Setting cache directory: ~REDACTED~/packer_cache
1970/01/01 00:00:00 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
1970/01/01 00:00:00 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin084891713
1970/01/01 00:00:00 packer-provisioner-shell plugin: Waiting for connection...
1970/01/01 00:00:00 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin084891713
1970/01/01 00:00:00 packer-provisioner-shell plugin: Serving a plugin connection...
1970/01/01 00:00:00 Plugin could not be found at /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell (exec: "/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell": stat /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell: no such file or directory). Checking same directory as executable.
1970/01/01 00:00:00 Current exe path: /usr/local/bin/packer
1970/01/01 00:00:00 Creating plugin client for path: /usr/local/bin/packer
1970/01/01 00:00:00 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell"}
1970/01/01 00:00:00 Waiting for RPC address for: /usr/local/bin/packer
1970/01/01 00:00:00 packer-provisioner-shell plugin: [INFO] Packer version: 1.5.1 [go1.13.5 linux amd64]
1970/01/01 00:00:00 packer-provisioner-shell plugin: Attempting to open config file: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: Setting cache directory: ~REDACTED~/packer_cache
1970/01/01 00:00:00 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
1970/01/01 00:00:00 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin290431505
1970/01/01 00:00:00 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin290431505
1970/01/01 00:00:00 packer-provisioner-shell plugin: Waiting for connection...
1970/01/01 00:00:00 packer-provisioner-shell plugin: Serving a plugin connection...
1970/01/01 00:00:00 Plugin could not be found at /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell (exec: "/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell": stat /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell: no such file or directory). Checking same directory as executable.
1970/01/01 00:00:00 Current exe path: /usr/local/bin/packer
1970/01/01 00:00:00 Creating plugin client for path: /usr/local/bin/packer
1970/01/01 00:00:00 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell"}
1970/01/01 00:00:00 Waiting for RPC address for: /usr/local/bin/packer
1970/01/01 00:00:00 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin435717925
1970/01/01 00:00:00 packer-provisioner-shell plugin: [INFO] Packer version: 1.5.1 [go1.13.5 linux amd64]
1970/01/01 00:00:00 packer-provisioner-shell plugin: Attempting to open config file: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: Setting cache directory: ~REDACTED~/packer_cache
1970/01/01 00:00:00 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
1970/01/01 00:00:00 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin435717925
1970/01/01 00:00:00 packer-provisioner-shell plugin: Waiting for connection...
1970/01/01 00:00:00 packer-provisioner-shell plugin: Serving a plugin connection...
1970/01/01 00:00:00 Plugin could not be found at /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell (exec: "/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell": stat /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell: no such file or directory). Checking same directory as executable.
1970/01/01 00:00:00 Current exe path: /usr/local/bin/packer
1970/01/01 00:00:00 Creating plugin client for path: /usr/local/bin/packer
1970/01/01 00:00:00 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell"}
1970/01/01 00:00:00 Waiting for RPC address for: /usr/local/bin/packer
1970/01/01 00:00:00 packer-provisioner-shell plugin: [INFO] Packer version: 1.5.1 [go1.13.5 linux amd64]
1970/01/01 00:00:00 packer-provisioner-shell plugin: Attempting to open config file: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: Setting cache directory: ~REDACTED~/packer_cache
1970/01/01 00:00:00 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
1970/01/01 00:00:00 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin996160860
1970/01/01 00:00:00 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin996160860
1970/01/01 00:00:00 packer-provisioner-shell plugin: Waiting for connection...
1970/01/01 00:00:00 packer-provisioner-shell plugin: Serving a plugin connection...
1970/01/01 00:00:00 Plugin could not be found at /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell (exec: "/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell": stat /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell: no such file or directory). Checking same directory as executable.
1970/01/01 00:00:00 Current exe path: /usr/local/bin/packer
1970/01/01 00:00:00 Creating plugin client for path: /usr/local/bin/packer
1970/01/01 00:00:00 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell"}
1970/01/01 00:00:00 Waiting for RPC address for: /usr/local/bin/packer
1970/01/01 00:00:00 packer-provisioner-shell plugin: [INFO] Packer version: 1.5.1 [go1.13.5 linux amd64]
1970/01/01 00:00:00 packer-provisioner-shell plugin: Attempting to open config file: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: Setting cache directory: ~REDACTED~/packer_cache
1970/01/01 00:00:00 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
1970/01/01 00:00:00 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin565080631
1970/01/01 00:00:00 packer-provisioner-shell plugin: Waiting for connection...
1970/01/01 00:00:00 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin565080631
1970/01/01 00:00:00 packer-provisioner-shell plugin: Serving a plugin connection...
1970/01/01 00:00:00 Plugin could not be found at /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell (exec: "/usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell": stat /usr/local/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell: no such file or directory). Checking same directory as executable.
1970/01/01 00:00:00 Current exe path: /usr/local/bin/packer
1970/01/01 00:00:00 Creating plugin client for path: /usr/local/bin/packer
1970/01/01 00:00:00 Starting plugin: /usr/local/bin/packer []string{"/usr/local/bin/packer", "plugin", "packer-provisioner-shell"}
1970/01/01 00:00:00 Waiting for RPC address for: /usr/local/bin/packer
1970/01/01 00:00:00 packer-provisioner-shell plugin: [INFO] Packer version: 1.5.1 [go1.13.5 linux amd64]
1970/01/01 00:00:00 packer-provisioner-shell plugin: Attempting to open config file: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: [WARN] Config file doesn't exist: /root/.packerconfig
1970/01/01 00:00:00 packer-provisioner-shell plugin: Setting cache directory: ~REDACTED~/packer_cache
1970/01/01 00:00:00 packer-provisioner-shell plugin: args: []string{"packer-provisioner-shell"}
1970/01/01 00:00:00 packer-provisioner-shell plugin: Plugin address: unix /tmp/packer-plugin954022891
1970/01/01 00:00:00 packer-provisioner-shell plugin: Waiting for connection...
1970/01/01 00:00:00 Received unix RPC address for /usr/local/bin/packer: addr is /tmp/packer-plugin954022891
1970/01/01 00:00:00 packer-provisioner-shell plugin: Serving a plugin connection...
1970/01/01 00:00:00 ui: ???????: Failed to load source type

  on raspbian.pkr.hcl line 1, in source "arm-image" "raspbian":
   1: source "arm-image" "raspbian" {

fork/exec /usr/local/bin: permission denied

1970/01/01 00:00:00 ui: arm-image: output will be in this color.
1970/01/01 00:00:00 ui:
1970/01/01 00:00:00 Build debug mode: false
1970/01/01 00:00:00 Force build: false
1970/01/01 00:00:00 On error:
1970/01/01 00:00:00 Preparing build: arm-image
1970/01/01 00:00:00 waiting for all plugin processes to complete...
1970/01/01 00:00:00 /usr/local/bin/packer: plugin process exited
1970/01/01 00:00:00 /usr/local/bin/packer: plugin process exited
1970/01/01 00:00:00 /usr/local/bin/packer: plugin process exited
1970/01/01 00:00:00 /usr/local/bin/packer: plugin process exited
1970/01/01 00:00:00 /usr/local/bin/packer: plugin process exited
1970/01/01 00:00:00 /usr/local/bin/packer: plugin process exited
1970/01/01 00:00:00 /usr/local/bin/packer: plugin process exited
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0xd770bd]

goroutine 1 [running]:
github.com/hashicorp/packer/packer.(*CoreBuild).Prepare(0xc0001763c0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/Users/mmarsh/Projects/packer/packer/build.go:153 +0x4cd
github.com/hashicorp/packer/command.(*BuildCommand).RunContext(0xc0002c82a0, 0x47fa500, 0xc0002ce040, 0xc0000b2170, 0x1, 0x1, 0xc0002ce040)
	/Users/mmarsh/Projects/packer/command/build.go:237 +0x7ae
github.com/hashicorp/packer/command.(*BuildCommand).Run(0xc0002c82a0, 0xc0000b2170, 0x1, 0x1, 0x0)
	/Users/mmarsh/Projects/packer/command/build.go:55 +0x201
github.com/mitchellh/cli.(*CLI).Run(0xc00031c280, 0xc00031c280, 0x1, 0x1)
	/Users/mmarsh/go/pkg/mod/github.com/mitchellh/cli@v1.0.0/cli.go:255 +0x1da
main.wrappedMain(0x0)
	/Users/mmarsh/Projects/packer/main.go:238 +0x853
main.realMain(0x0)
	/Users/mmarsh/Projects/packer/main.go:124 +0xbb
main.main()
	/Users/mmarsh/Projects/packer/main.go:34 +0x22

The auto-generated builder.hcl2spec.go file should have the following changes, however I don't know how to set the appropriate annotations so I don't need to manually edit the file.
builder-hcl2spec-image_type.patch
--- a/pkg/builder/builder.hcl2spec.go	1970-01-01 00:00:00.000000000 +0000
+++ b/pkg/builder/builder.hcl2spec.go	1970-01-01 00:00:00.000000000 +0000
@@ -29,3 +29,3 @@
 	OutputFile             *string              `mapstructure:"output_filename" cty:"output_filename"`
-	ImageType              utils.KnownImageType `mapstructure:"image_type" cty:"image_type"`
+	ImageType              *utils.KnownImageType `mapstructure:"image_type" name:"image_type" cty:"image_type"`
 	ImageMounts            []string             `mapstructure:"image_mounts" cty:"image_mounts"`
@@ -69,3 +69,3 @@
 		"output_filename":            &hcldec.AttrSpec{Name: "output_filename", Type: cty.String, Required: false},
-		"image_type":                 &hcldec.AttrSpec{Name: "utils.KnownImageType", Type: cty.String, Required: false},
+		"image_type":                 &hcldec.AttrSpec{Name: "image_type", Type: cty.String, Required: false},
 		"image_mounts":               &hcldec.AttrSpec{Name: "image_mounts", Type: cty.List(cty.String), Required: false},

The vendor directory needs to be updated, I haven't included it to avoid polluting the PR.

looks good, can this be merged, or still WIP?

Apparently the crash is due a bug in Packer that will be solved by hashicorp/packer#8543.


Optimized code

Description of Change

Checklist

[x] Added description of change
[x] Added file name matches File name guidelines
[x] Added tests and example, test must pass
[x] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[x] Relevant documentation/comments is changed or added
[x] PR title follows semantic commit guidelines
[x] Search previous suggestions before making a new one, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.

Notes:

@Panquesito7  @kvedala Please Merge this commit if approved.

@ayaankhan98  Please Merge this commit if approved or suggest any changes.


Please make your job citable

Hi guys,
I'm doing some fusion algorithm research and has some work based on your code, so could you make the repo more friendly to be cited? The instruction is here.
Many thanks!

Done, its now in the README


ReplyTo is case sensitive in calls to sendinblue

Fixed in our fork but just incase it's useful to merge and update npm, this fixes replyTo functionality which currently silently fails (just falls-back to the from address)

Well observed, thanks for the update ;-)


Support assert_display_exit() for apps for Nano built on NBGL

Description
The goal of this PR is to support assert_display_exit() for apps for Nano built on NBGL
Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[*] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)
[ ] Tests
[ ] Documentation
[ ] Other (for changes that might not fit in any category)

Abandonned, done elsewhere


Volvo on Call: Fuel and Fuel_2 seem to mix up every few days

Home Assistant release (hass --version): 0..44.2
Python release (python3 --version): 3.4.2
Component/platform: volvooncall
Description of problem: Volvo on Call has two sensors, "sensor.XYZ_fuel" and "sensor.XYZ_fuel_2". Every now and then the values seem to mix up. In Currently "fuel" is the amount of fuel left and "fuel_2" is the per centage left. Yesterday it was the other way around. Could be that it's changing back in a few days again.

Yesterday the amount of fuel left was 56 liters. Then went up (but didn't go to the gas station) to 76 and now it's back to 63. All values are correct but liters and per centages are mixed up.
Expected: Consistent behavior
Problem-relevant configuration.yaml entries and steps to reproduce: Just seems to happen every few days.

Ah, ok. Do you restart HA inbetween?

Haven't restarted it since the 44.2 release. By the way, now it's back to liters again ;-)

Would you be able to test if this change fixes your problem?
https://github.com/molobrakos/home-assistant/commit/3081853ee45aabf0ec3d9a160b54a46e6211198b

Sure. Will make the changes later today and report back in a few days. Thanks!

So far the values haven't been mixed up

Unless you haven't noticed any issues, I'll make a PR of this then.


Non github test runs

Some people might want to run code not from a github repo. In the future it might be nice to upload a file or zip with all files to have them execute. Or a url that isn't a github repo to pull test code from.

provide an URL - handle both a .js as a single file or a zip file for multiple files

The main file will be defined by the user in the multiple file scenario

Single file is assumed not to have any dependencies.


changed code from while to do/while

There are a couple of other such loops in the same file. If you change one of them, the others should also be changed.

ok, I changed the other four too.

Merged, thanks!


Active delegation to DRep info section

Link to figma

As a user, I want to be able to see my active delegation.

It should contain information on the amount of delegated ADA.
It should include the same card component as on the list

OK - in progress state

OK: - delegation


When I trained NTS-Net on my own dataset and stanford dog dataset, the train accuracy can reach 99.8%, but the test accuracy just 85%. Do you same as me

请教一下，如何改成自己的数据集啊


current_line_blame is too CPU intensive

Description
From what I'm understanding, current_line_blame runs an instance of git each time that the cursor moves to another line in order to extract blame information for the new line.
This is a problem for large repositories, where a single execution can spike CPU to 100% for a few seconds.
This becomes a terrible problem when scrolling; if I press j five times, then 5 git processes are spawned each one taking 100% of a CPU core. If I just hold j for a short while, this is what top looks like:

These can take around 20-30s to complete, given that they're all competing for CPU usage.
Neovim version
NVIM v0.9.1
Operating system and version
Linux 6.5.1-0-edge x86_64 Linux
Expected behavior
CPU usage should not spike due to blame calculation
Actual behavior
CPU usage spikes to 100% for each line change on large repositories.
Minimal config
for name, url in pairs{
  gitsigns = 'https://github.com/lewis6991/gitsigns.nvim',
  -- ADD OTHER PLUGINS _NECESSARY_ TO REPRODUCE THE ISSUE
} do
  local install_path = vim.fn.fnamemodify('gitsigns_issue/'..name, ':p')
  if vim.fn.isdirectory(install_path) == 0 then
    vim.fn.system { 'git', 'clone', '--depth=1', url, install_path }
  end
  vim.opt.runtimepath:append(install_path)
end

require("gitsigns").setup({
  current_line_blame = true,
  current_line_blame_opts = {
    delay = 0,
  },
})

Steps to reproduce

git clone https://gitlab.alpinelinux.org/alpine/aports.git (or any other large repository)
Open any file in the repository (e.g.: community/xdg-desktop-portal/APKBUILD)
CPU will now spike once.
Open top in another terminal
Press j or k in neovim. Note how each keypress spawns a git process that takes a few seconds to exit.

Gitsigns debug messages
No response

To solve this we will need to kill unfinished git blame commands when the cursor moves.

@WhyNotHugo can you try #878.
It doesn't cancel any processes, but will prevent git blames from running concurrently.

Given that git blame calculates blame for the whole file, can't its entire output be kept in memory? So when the cursor moves, the blame data can be read from memory, rather than running git blame which needs to do a lot of work.

Gitsigns doesn't fetch the blame for the entire file, it does it per line instead. I don't know if doing it for the entire file will be more efficient or not, but I would guess it wouldn't be.


[SPARK-42602][CORE] Add reason argument to TaskScheduler.cancelTasks

What changes were proposed in this pull request?

This change adds a reason: String to the argument list of TaskScheduler.cancelTasks.
Why are the changes needed?

Currently all tasks killed by TaskScheduler.cancelTasks will have a TaskEndReason "TaskKilled (Stage cancelled)". To better differentiate reasons for stage cancellations (e.g. user-initiated or caused by task failures in the stage), we could add a reason argument in TaskScheduler.cancelTasks.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Updated unit tests.

@cloud-fan, @jiangxb1987, could you review this?


Add documentation on elt vs run - advanced vs normal operation

Perhaps as a part of https://docs.meltano.com/reference/v2-migration it would make sense to have a more detailed section on elt vs run for data replication workloads. This came up in https://github.com/meltano/meltano/issues/6272

FYI @afolson

Still useful but lower priority - perhaps around 3.0 reprioritize.


filezilla: 3.60.1 -> 3.60.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/filezilla/versions.
meta.description for filezilla is: "Graphical FTP, FTPS and SFTP client"
meta.homepage for filezilla is: "https://filezilla-project.org/"
meta.changelog for filezilla is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.60.2 with grep in /nix/store/2a9r83h0fi6rvy6qd57hcqdjk02kywbv-filezilla-3.60.2
found 3.60.2 in filename of file in /nix/store/2a9r83h0fi6rvy6qd57hcqdjk02kywbv-filezilla-3.60.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
filezilla

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2a9r83h0fi6rvy6qd57hcqdjk02kywbv-filezilla-3.60.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A filezilla https://github.com/r-ryantm/nixpkgs/archive/4eff4dd2bef54db5c9bbbee9f0faea4fc9c0c720.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2a9r83h0fi6rvy6qd57hcqdjk02kywbv-filezilla-3.60.2
ls -la /nix/store/2a9r83h0fi6rvy6qd57hcqdjk02kywbv-filezilla-3.60.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

filezilla

Maintainer pings
cc @pSub for testing.

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

1 package built:

filezilla


Status of python sdk

Hi,
Thanks for starting this project. What remains to be implemented and tested to make this sdk stable?
Thanks!

Hi AndriyMulyar. Thank you for your interest.
I'm trying to release an MVP version soon.
Which for me would mean that all the functionality to interact with the FLOW blockchain is there:

being able to decode/encode json cadence values
sending scripts and getting results
sending/signing arbitrary transactions
getting events/transaction/blocks/accounts from the FLOW grpc
having CI that runs tests and examples on PRs
having a lot of tests and good usage documentation

All of the above except the last point is actually covered already. I'm hoping to get that last point covered in the following weeks.
There are certainly still bugs and instabilities, but at the moment there are no known bugs or instabilities :sweat_smile:. There is a CI pipeline in place to run all the tests (there aren't that many right now) and all of the examples on the most recent emulator version on every release (an on PRs). Which means there is little chance of something really breaking getting released.
I have been using the flow-py-sdk for my own projects and I'm also trying to create a public showcase project, so I know for a fact it can be used.
I would appreciate any feedback from anyone using or wanting to use this SDK. Feedback would make development much faster :smile:.

Awesome, thank you for the detailed response.
On Thu, May 27, 2021, 9:18 AM Janez Podhostnik @.***>
wrote:

Hi AndriyMulyar. Thank you for your interest.
I'm trying to release an MVP version soon.
Which for me would mean that all the functionality to interact with the
FLOW blockchain is there:

being able to decode/encode json cadence values
sending scripts and getting results
sending/signing arbitrary transactions
getting events/transaction/blocks/accounts from the FLOW grpc
having CI that runs tests and examples on PRs
having a lot of tests and good usage documentation

All of the above except the last point is actually covered already. I'm
hoping to get that last point covered in the following weeks.
There are certainly still bugs and instabilities, but at the moment there
are no known bugs or instabilities 😅. There is a CI pipeline in place
to run all the tests (there aren't that many right now) and all of the
examples on the most recent emulator version on every release (an on PRs).
Which means there is little chance of something really breaking getting
released.
I have been using the flow-py-sdk for my own projects and I'm also trying
to create a public showcase project, so I know for a fact it can be
used.
I would appreciate any feedback from anyone using or wanting to use this
SDK. Feedback would make development much faster 😄.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/janezpodhostnik/flow-py-sdk/issues/16#issuecomment-849627594,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJ4TBTCP75WGDS4IQLWCGLTPZBDTANCNFSM45TQAIDQ
.


fix: tag script

Codecov Report

Merging #52 into next will decrease coverage by 0.11%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##             next      #52      +/-   ##
==========================================
- Coverage   76.84%   76.72%   -0.12%
==========================================
  Files         181      181
  Lines        5191     5199       +8
  Branches      633      634       +1
==========================================
  Hits         3989     3989
- Misses        933      941       +8
  Partials      269      269

Impacted Files
Coverage Δ

packages/metrics/src/MetricsClient.ts
73.97% <100%> (ø)
:arrow_up:

packages/hook/src/index.ts
42.85% <0%> (-57.15%)
:arrow_down:

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 e2f3d4b...f0d1e86. Read the comment docs.


Contao4 compatibility

not tested yet...

You have tagged a Contao 4 compatible release already, which causes this extension to be shown as compatible and installable in the Contao Manager for example. However, this extension cannot be installed in Contao 4. See https://community.contao.org/de/showthread.php?68615-Contao-4-und-contao-full-background-images&p=455380&viewfull=1#post455380 for example.
Your composer.json is missing the contao-community-alliance/composer-plugin dependency, since this is still a Contao Module, not a Contao Bundle. Also your composer.json is unnecessarily restrictive, since you are only requiring Contao ^4.3 even though the extension in its current state should be compatible with Contao 3 as well.
Furthermore, what exactly is this fork for? This fork is causing unnecessary confusion and I think it would be better to fix any problems in the original repository. Not in this fork.

Thanks for your reply. These are my first steps working with packagist/symfony bundle extension and I try to gain experience in trial and error, as there indeed is no clear instruction on how to make extensions or edit them.
Before I make a pull request which doesnt work, I try to fork it and test it.

Before I make a pull request which doesnt work, I try to fork it and test it.

That's fine of course. But don't create any release tags, just test it without them ;). Also if the extension works without any changes in Contao 4, all that has to be done is edit the composer.json


Fire visualizers don't update properly

Description

these are pretty old-code iirc so they probably need a rewrite.
Reproduction

Screenshots

Additional context

dont think this happens anymore


Missing error details when module initialization throws during SSR

Description
I'm investigating an issue in my employer's app where we see an increase in 500 errors in New Relic, but these errors do not have any context or stack traces. Looking through our application logs, we see Next.js logging the actual error objects directly to console.error, but the NR agent doesn't seem to capture this info.
As a test, we added some code locally to purposely throw, during a request to the / route, during the top-level execution of one of our modules. That code is:
if (process.env.NEXT_PHASE !== 'phase-production-build') {
  // emulate an error thrown as a side-effect of module initialization.
  // process.env check is to make sure the build passes, to make sure this is a runtime error
  // and not a build error
  throw new Error('this error is not captured by New Relic');
}

We then traced the execution path through Next.js code to determine where these errors were being passed to console.error, and determined the error is caught (and logged) inside of renderToResponseImpl. The error is then passed to the renderErrorToResponse method.
My suspicion is that this package, newrelic-node-nextjs, is missing instrumentation of the renderErrorToResponse method, which would unlock the ability to capture the Error object associated with the failed request and 500 error.
Expected Behavior
If an exception is thrown as a side-effect of module initialization in the dependency graph for a Next.js app, that error is reported to New Relic.
Troubleshooting or NR Diag results
Steps to Reproduce

Get a Next.js app setup with the "Pages Router" (as opposed to "App Router") and newrelic-node-nextjs
In the top-level of pages/index.tsx, throw an error using the sample code provided in this ticket
Run a build
Run the app in Production mode, and navigate to the / route in your browser
Confirm a generic 500 was reported to New Relic

Your Environment

next version: 14.2.2
@newrelic/next version: 0.9.0
node version: 20.11.0

Additional context

@DrewML sorry for your troubles. Thanks for the repro, I'll triage and provide an update.

Thanks @bizob2828! Super appreciated.

@DrewML the Next.js instrumentation doesn't automatically handle errors. This example application demonstrates how to handle errors here.  If you use this application you will see errors getting logged.


Fix native tests with VFS retention enabled on Windows

On Windows, CppIncrementalBuildIntegrationTest and CLanguageIncrementalCompileIntegrationTest seem to fail when VFS retention is enabled. The tests that fail are not consistent, though.
For example, for this build, first

CppIncrementalBuildIntegrationTest.recompiles binary when implementation header file changes [visual c++ 2019 (16.0.0)]
CppIncrementalBuildIntegrationTest.can have a cycle between header files [visual c++ 2019 (16.0.0)]
CLanguageIncrementalCompileIntegrationTest.recompiles only source file that includes changed header file [visual c++ 2019 (16.0.0)]

failed, while in the re-run

CppIncrementalBuildIntegrationTest.recompiles binary and does not relink when public header file changes in a way that does not affect the object files [visual c++ 2019 (16.0.0)]
CLanguageIncrementalCompileIntegrationTest.recompiles changed source file only [visual c++ 2019 (16.0.0)]
CLanguageIncrementalCompileIntegrationTest.recompiles source file when transitively included header file is changed [visual c++ 2019 (16.0.0)]

failed.
In the first round, all three tests had error message like this:
Couldn't start watching<PHONE_NUMBER>00090C for 'C:\tcagent1\work\a16b87e0a70f8c6e\subprojects\language-native\build\tmp\test files\CLanguageIncrementalCompileIntegrationTest\recompiles_only_sou...ader_file\fzb8', error = 6

for the project directory in the log.
The tests in the second run didn't have the message.
first run
second run

cc: @gradle/build-cache

CppLanguageIncrementalBuildIntegrationTest has the same problem.

See #12179 for the Couldn't start watching errors.


Bump to docker 1.7.0

No luckly, I failed to startup docker 1.6.2 with overlayfs . would you please tested it ?

Before the switch we are using aufs
root@builder-33:~# docker info
Containers: 0
Images: 0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 0
 Dirperm1 Supported: true
Execution Driver: native-0.2
Kernel Version: 4.0.5-235
Operating System: Ubuntu 15.04
CPUs: 4
Total Memory: 1.975 GiB
Name: builder-33
ID: IAKG:TMLD:G6VA:PGIM:Z7Z6:WYZT:GBLJ:3Q5U:S5J6:7LFT:KGFN:BQVM

Updating config file
root@builder-33:~# sed -i s/aufs/overlay/ /etc/systemd/system/docker.service
root@builder-33:~# cat /etc/systemd/system/docker.service
[Unit]
Description=Docker Application Container Engine
Documentation=https://docs.docker.com
After=network.target docker.socket
Requires=docker.socket

[Service]
ExecStart=/usr/bin/docker -d -H <IP_ADDRESS>:4243 -H fd:// --storage-driver=overlay
MountFlags=slave
LimitNOFILE=1048576
LimitNPROC=1048576
LimitCORE=infinity

[Install]
WantedBy=multi-user.target

Restart docker and remove old /var/lib/docker with aufs data
root@builder-33:~# service docker stop
Warning: docker.service changed on disk. Run 'systemctl daemon-reload' to reload units.
root@builder-33:~# systemctl daemon-reload
root@builder-33:~# rm -rf /var/lib/docker/
root@builder-33:~# systemctl start docker

Test to run an image and check the new driver is overlay
root@builder-33:~# docker run armbuild/busybox echo hello world
Unable to find image 'armbuild/busybox:latest' locally
Pulling repository armbuild/busybox
d91e5575e4cc: Download complete
511136ea3c5a: Download complete
73089b67ca16: Download complete
Status: Downloaded newer image for armbuild/busybox:latest
hello world
root@builder-33:~# docker info
Containers: 1
Images: 3
Storage Driver: overlay
 Backing Filesystem: extfs
Execution Driver: native-0.2
Kernel Version: 4.0.5-235
Operating System: Ubuntu 15.04
CPUs: 4
Total Memory: 1.975 GiB
Name: builder-33
ID: IAKG:TMLD:G6VA:PGIM:Z7Z6:WYZT:GBLJ:3Q5U:S5J6:7LFT:KGFN:BQVM

Hi @moul
thank you for updating your Docker 1.5 image to 1.6 (and hopefully 1.7). I wasn't that successful updating to Docker 1.7 on my own, since Docker refuses to start a container (Error response from daemon: Cannot start container c1b529a3cba6eafa82bf88ef978fcc84158d1f7f06bc31cd2ef570e40f308086: socket operation on non-socket). Which changes did you apply to the default Dockerfile and how did you manage the fact that zfs support isn't available in trusty an ARM (zfs support is available in utopic, but make build fails in utopic)?
Cheers
Uli

I based my work on your script, I switched to ubuntu vivid for the build (zfs is available)
See detail here: https://github.com/armbuild/docker-armhf/blob/master/build.sh#L14-L17
I have the same issue, and @hypriot too, I'm investigating, and here is an issue on official Docker repo: https://github.com/docker/docker/issues/14184

Thank you


DNS Rebind Check breaks spam blocklists

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug
Email spam filtering often uses real-time blocklists published in DNS. They work like this:
% host <IP_ADDRESS>.zen.spamhaus.org
<IP_ADDRESS>.zen.spamhaus.org has address <IP_ADDRESS>
<IP_ADDRESS>.zen.spamhaus.org has address <IP_ADDRESS>
<IP_ADDRESS>.zen.spamhaus.org has address <IP_ADDRESS>

These DNS blocklists are described in RFC5782, and they always return A records with IP addresses in the 127/8 range to indicate membership in the blocklist.
It took me a long time to figure out that OPNsense was silently dropping these A records from replies to my DNS queries because of the DNS Rebind Check feature.
To Reproduce

Configure Unbound as a recursive DNS resolver for your network.
Enable (un-disable) DNS Rebind Checks under System: Settings: Administration.
Run host <IP_ADDRESS>.zen.spamhaus.org from a machine on your network.

Expected behavior
I expected the host command to return a number of A records with 127/8 addresses for this spam blocklist test entry as shown above.
I got a DNS response with an empty answer section instead. (And spamassassin is badly crippled on my mail server because it can't use these blocklists)
Describe alternatives you considered
I was able to work around the problem by disabling DNS Rebind Check and instead adding my own config file to /usr/local/etc/unbound.opnsense.d/ with just the RFC1918 networks and link-local stuff:
private-address: <IP_ADDRESS>/8
private-address: <IP_ADDRESS>/12
private-address: <IP_ADDRESS>/16
private-address: <IP_ADDRESS>/16
private-address: fd00::/8
private-address: fe80::/10

Additional context
Please note that the Unbound documentation advises against adding 127/8 as a private-address precisely because it breaks spam blocklists.
There's a couple of changes you could make to improve the situation:

Don't add 127/8 as a private-address as recommended by Unbound. I think the localhost network has a smaller attack surface for DNS Rebind attacks that the RFC1918 networks, and browsers can detect bogus 127/8 A records themselves. (Although I don't know if they do that).
Alternatively, add an option to allow 127/8 A records when DNS Rebind Check is enabled for people running their own mail servers.
I suppose I could also add all of my spam blocklist domains to "Private Domains" under Services: Unbound DNS: Blocklist. I am still confused abut this setting: It doesn't seem to have anything to do with the DNSBL lists you can configure in that pane. Should it go next to the "DNS Rebind Check" setting way over in  System: Settings: Administration? Unbound lists private-address and private-domain next to each other because they are related.

Environment
OPNsense 22.1.10-amd64

At a first glance I tend to agree, also for consistency reasons. For DNSmasq we seem to exempt localhost by default
https://github.com/opnsense/core/blob/dedb11793547e270aa65cab8778eda4fc6663ebe/src/etc/inc/plugins.inc.d/dnsmasq.inc#L109
For Unbound we don't
https://github.com/opnsense/core/blob/ebdf49363e86267588a87f0bfc7a1b963f86ca8b/src/etc/inc/plugins.inc.d/unbound.inc#L156
Let's keep this open for a while to see if there are concerns about changing this behaviour. We might need to double check the rest of the static list as well.

I don't mind removing localhost (IPv4 and IPv6) although it's strange that this went fine since 2016.

https://github.com/opnsense/core/commit/3edd472aaa007a9f080c3f9d863d4c774114f1b5 removes 127/8, but adds the network to the model in case someone wants to add them anyway (against Unbound's advice).


Add Download/Print Option for Booked Tickets

It would provide convenience and flexibility, especially in situations where digital access may not be readily available.I would be delighted to contribute to the implementation of this feature. @Pranjal360Agarwal

Please assign this to me as a GSSOC contibutor.

It would provide convenience and flexibility, especially in situations where digital access may not be readily available. I GSSOC 2023 Contributor would be delighted to contribute to the implementation of this feature. @Pranjal360Agarwal

yeah that will be a great feature, go with it!! @Vedansh-777


Fixed workshop entrance detection for GER client

Multi-mode submersibles are currently not working when you set the client language to German because AR fails to detect the workshop entrance.
This is because the name string for the workshop entrance object ingame is "Eingang zu anderen Zimmern" while the current Excel lookup resolves to "Eingang[p] zu anderen Zimmern". The string comparison then fails of course.
Since I could not find a Dalamud- or game-specific solution to filter the "[p]" out, which I believe to be some localization/pluralization tag, I added another string to the comparison list that filters out all text in square brackets from the Excel lookup via Regex.
I tested this to work in all languages available to me (JP, EN, GER, FR).
Other solutions could be:

Just adding the hardcoded string "Eingang zu anderen Zimmern" to the comparison list like done for Lang.BellName. In contrast to that the string is not entirely different from the Excel Row like in that case so I thought my solution would be more future proof.
Extracting the logic of adding a filtered string to the comparison into a helper function in Lang.cs. As this is AFAIK the only occurence of this issue so far, I did not yet see a need for that function.

I am happy to change to an alternative solution, if you have an different preference / more input.

Thank you!


Allow overriding a cluster-wide default allocation setting for specific tables/partitions

Problem Statement
Use case
There is a three-node cluster that is already in operation and contains data. Now, a fourth node should be added later on as a cold node (with a slow disk). Initially and in the future by default, all data should remain on the hot nodes. The nodes are configured with node.attr.storage=hot/cold.
Problem
Before adding the cold node, every table needs to be configured with ALTER TABLE x SET ("routing.allocation.require.storage" = 'hot'); to prevent reallocation to the newly added cold node. Depending on the number of tables, this can be tedious work, and is also error-prone (easy to forget when creating new tables in the future).
As another approach, there is the cluster-wide cluster.routing.allocation.require.storage that could be set to hot as a default value and then get overridden on a table/partition-level with ALTER TABLE for those tables/partitions that should transition to the cold node. But this doesn't work, it's not possible to override the cluster-wide setting:
-- allocates to hot nodes due to cluster allocation setting
CREATE TABLE t1 (a INTEGER);

-- try to reallocate/override previous allocation
ALTER TABLE t1 SET ("routing.allocation.require.storage" = 'cold');

-- nothing has changed, all shards are still on the hot nodes
SELECT decisions FROM sys.allocations WHERE table_name = 't1'
-- returns for the cold node: node does not match cluster setting [cluster.routing.allocation.require] filters [storage:"hot"]

Possible Solutions
Have a cluster-wide default allocation setting that can be overridden for specific tables/partitions.
ElasticSearch has a node.roles implementation: https://www.elastic.co/blog/elasticsearch-data-lifecycle-management-with-data-tiers
Considered Alternatives
No response

ElasticSearch has a node.roles implementation: https://www.elastic.co/blog/elasticsearch-data-lifecycle-management-with-data-tiers

A potential alternative for this would be to add tags to data.paths which can be used in a similar way in combination with the allocation includes/excludes.
Opposed to node specific roles it would have the advantage that a single node could have mixed disk types. Making it more flexible while still allowing for the same kind of setup with dedicated slow storage nodes.

We said we'd only allow overriding the cluster setting with a table/index setting. Anything else in regards to storage/node paths is out-of-scope.


Unable to run ksync watch

$ sudo ksync watch
Password:
INFO[0000] new pod detected                              pod=app-7cf4c9bdfd-bbfd4 spec=fancy-dory
INFO[0000] new pod detected                              pod=app-7cf4c9bdfd-bbfd4 spec=usable-gator
INFO[0000] listening                                     bind=<IP_ADDRESS> port=40322
INFO[0000] new pod detected                              pod=app-7cf4c9bdfd-bbfd4 spec=sharp-hare
FATA[0015] Get http://localhost:8384/rest/system/config: dial tcp <IP_ADDRESS>:8384: connect: connection refused

I ran ksync watch on my client (MacBook) and got the error above. It seems that ksync is trying to connect to <IP_ADDRESS>:8384, but nothing is using this port.
Some information that may help:
 ~> ksync version
ksync:
	Version:    Release
	Go Version: go1.12.1
	Git Commit: c27ce95
	Git Tag:    0.3.6
	Built:      Mon Mar 18 17:06:42 +0000 2019
	OS/Arch:    darwin/amd64
service:
	Version:    Release
	Go Version: go1.12.1
	Git Commit: c27ce95
	Git Tag:    0.3.6
	Built:      Mon Mar 18 17:02:16 +0000 2019
 ~> kubectl version --short
Client Version: v1.14.3
Server Version: v1.14.3
 ~> kubectl get pods -n default
NAME                   READY   STATUS    RESTARTS   AGE
app-7cf4c9bdfd-bbfd4   1/1     Running   0          76m
 ~> kubectl get pods -n kube-system | grep ksync
ksync-2b6vk                             2/2     Running   0          30m
ksync-8456k                             2/2     Running   0          31m
ksync-sqvmm                             2/2     Running   0          30m
 ~>

It sounds like the wrong kubeconfig is being used. I suspect the sudo is what is throwing it for a loop. Shouldn't need to run with sudo at all. Or, use the KUBECONFIG env var. Please reopen the issue if I'm totally off base =)

After removing ~/.ksync/ and rerun ksync init, this error doesn't appear.

Huh, well, glad it got fixed!


Nfs dynamic provisioning helm chart update

Added latest helm chart for nfs dynamic provisioner.
Before when we deploy nfs dynamic and while creating PVC it struck in pending state and selflink related issue we get.


ZabraUtility Build issue in IOS

I tried to run a new project importing this library in the pubspec.yaml ( zebrautility: ^0.0.38 ) and the project didn't compile.
This is the error:
Undefined symbols for architecture x86_64:
"OBJC_CLASS$_EAAccessory", referenced from:
objc-class-ref in zebrautility(Printer.o)
"OBJC_CLASS$_EASession", referenced from:
objc-class-ref in libZSDK_API.a(Zebra_EADSessionController.o)
"OBJC_CLASS$_EAAccessoryManager", referenced from:
objc-class-ref in libZSDK_API.a(MfiBtPrinterConnection.o)
objc-class-ref in zebrautility(Printer.o)
ld: symbol(s) not found for architecture x86_64
already added
There is libZSDK_API.a file in the ios folder for this repose. Please open your Xcode project add manually this library to your Xcode.
but getting the issue please help
thanks in advance.

Do you run your project in the simulator?
You cannot run a project with Zebra libraries in the simulator.

Thanks for the answer @hrshs
Yes I am trying to run in a simulator
Now I am trying to run on the real device it's working.

Any solutions to this problem?? I have the same issue.

After copying the .a file in the ios folder the error persists, any solution?

same problem

Thanks for the answer @hrshs Yes I am trying to run in a simulator
Now I am trying to run on the real device it's working.

Can you explain how did you add libZSDK_API.a file to your iOS project?


Update Mesos guide

I've had these changes uncommited and untested for a little while, and someone asked on Slack the other day. I've tested this and it works fine.

If someone else wishes to re-test it, it's probably still a good idea.

@abuehrle are you happy with this?

Let me have a look and I will give it a test tomorrow. ( working on that cloud formation template at the moment. )

If you are going to update the file, why don't you figure out a way to not ship the weave script with the file?  Won't one of your "includes" work for that?
@lukemarsden

If you are going to update the file, why don't you figure out a way to not ship the weave script with the file?

I deliberately haven't change this here, as it would make the change bigger.

Won't one of your "includes" work for that?

No. Includes are only for markdown.

I would not ship the weave script with the file.  It will just get out of date very quickly.

@abuehrle Luke and I have discussed this, and it would not make sense to pin some of the dependencies and not pin others. Here we have pinned Mesos packages, so it's makes sense to pin weave as well. Also, please note that functionality of example and features shown here do not depend on a recent version. This guide is in maintenance mode, and doesn't adhere to latest best practice, i.e. we will soon replace it with something that uses CNI plugin, demonstrates Scope and uses Socks Shop as the example app. If you are happy with the copy overall, let's just merge and publish it as it is.

I am just testing this, and I didn't have weave run for me.

I won't spend too much time on this, if you are rewriting it, then.

I am just testing this, and weave didn't install properly.

In what way exactly?


Unclear configuration UI for CSV target

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/749
Originally created by @dmor on 2019-06-27 17:25:38

When I configure the target CSV I am presented with a dialogue box with two fields to fill in named "delimiter" and "quotechar" but I am not sure if I can just leave them as is, or if I need to fill them in. If I do need to fill them in what are acceptable choices? It would be awesome if this was more clear to the user.
Possible Solutions:

a tooltip
a dropdown instead of free text

View 3 previous comments from the original issue on GitLab


Update issue templates

On mobile rn, but I think it looks good, feel free to merge. In case something needs to be tweaked, we will just make another PR


New package: ArrayFire.ArrayFire version 3.9.0

Pull request has been created with komac v2.3.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Hi @DeveloperPaul123,
This application doesn't seem to include a /bin folder. It only has .make files, libraries, and artifacts.

Is the user expected to compile the application after install?
Is there a precompiled version available?

Hi @stephengillie ,
You are correct in your observation. The installer is for a GPU library, so it's meant to be consumed by developers in their own project. The vendor (ArrayFire) provides installers on their website so I thought it would be convenient to have it available on winget so we can easily install this library and the associated runtimes on other dev machines or our CIs.
The version included is pre-compiled as it includes only headers (defines the interface) and the dll libraries (contains the executable code).
Hope that helps.
If this doesn't align with the types of packages typically included in winget that's no problem.

Hope that helps.

Yes, very much so. Thank you for the detailed explanation.

If this doesn't align with the types of packages typically included in winget that's no problem.

Our pipelines were written for Windows Forms, and so updates to this application will likely get the same label. If I forget, or other moderators need proof, feel free to link to your comment above.


bug fix min_enclosing_triangle.cpp

https://github.com/Itseez/opencv/issues/4992
to compare current and fixed results you can use https://github.com/sturkmen72/opencv_samples/blob/master/bugtest_minEnclosingTriangle.cpp

@IceRage could you check this modification

First of all I do apologize for the late reply.
Secondly, regarding the proposed change, by relaxing the constraints and setting the sideCValid flag to true when all sides are flush (i.e. VALIDATION_SIDES_FLUSH is true) invalid triangles which do not have a minimal area could be accepted as solutions. Therefore an alternative fix should be considered.
As a side note the condition (or invariant) that must hold for a minimal area triangle is that the midpoint of each side of the triangle must touch the enclosed polygon. For more details about this condition please see Theorem 1.1. and the corresponding proof given by Klee and Laskowski in the following paper:
V. Klee and M. C. Laskowski, “Finding the smallest triangles containing a given convex polygon,” Journal of Algorithms, vol. 6, no. 3, pp. 359–375, Sep. 1985.

@IceRage, @sturkmen72, so, what's the decision? As I see, without the patch the function sometimes returns no triangle (which is not very good, but happens rather rarely). With the patch the function does return triangle all the time (?), but it can be larger than minimal sometimes. Is that correct?
Does the following temporary solution make sense?:

add a flag to the function isValidMinimalTriangle, whether or not include the check added in the patch (validationFlag == VALIDATION_SIDES_FLUSH)

first run the algorithm with this flag turned off and if it fails to find a triangle, run the algorithm with this flag turned on. So that we always get a triangle but in some rare cases it may be not the optimal one.

@vpisarev The algorithm should theoretically always return a minimal area enclosing triangle. Although I did not check, I assume the current problem is due to floating point approximation errors. Would it be to late if I would try to investigate and potentially fix the bug in the week 21-27 December 2015? If yes, then I would personally choose solution number 2 in your reply.

@IceRage, I think, it's never too late :) it's just that your fix will go to 3.2, whereas 3.1 will have the current version, which is already pretty good and fails very rarely.

@vpisarev, @IceRage FYI

Points:
[126, 218;
181, 335;
256, 339;
288, 291;
318, 243;
354, 169;
336, 145;
230, 137;
171, 134]
computed  area with current minEnclosingTriangle function  ( green lines ): 68339
computed  area with fixed minEnclosingTriangle function ( blue lines ): 40024.9

@vpisarev, @sturkmen72
Reducing the EPSILON value used to compare floating point numbers in modules/imgproc/src/min_enclosing_triangle.cpp from 1E-5 to 1E-6 fixes the bug and the correct minimal area enclosing triangle is returned for the unit test described in issue #4992.
Therefore the bug was due to approximation errors.
However when reducing the value of EPSILON other examples do not work (e.g. the previously working unit test Imgproc_MinTriangle.accuracy fails).
A quick and dirty fix could be to start with a low value of EPSILON (e.g. 1e-7), run the main algorithm, and if no triangle was found, then multiply EPSILON by 10 and repeat, otherwise return. An alternative solution would be to go through the code and compute the value of EPSILON which should work for "all" cases, but this is tedious. A potentially better solution could be to use multi-precision arithmetic libraries (e.g. The GNU Multiple Precision Arithmetic Library).

it is stated in the GSoC_2016 page
"convexHull is implemented with Sklansky’s second, 1982 algorithm, which is incorrect in some case, and suboptimal complexity-wise"
maybe the source of the problem is convexHull that used in the beginning of minEnclosingTriangle code

Transferred to new PR


getWindowHandles failing with images plugin with Appium 2.0

With Appium 2.0 and using images plugin, getWindowHandles failing with appium-flutter-driver.
Logs
[HTTP] --> GET /wd/hub/session/e5309135-9b66-4eef-97d5-65d325fa9c54/window/handles
[HTTP] {}
[debug] [FlutterDriver@ac47 (e5309135)] Would have proxied command directly, but a plugin exists which might require its value, so will let its value be collected internally and made part of plugin chain
 Calling AppiumDriver.getWindowHandles() with args: ["e5309135-9b66-4eef-97d5-65d325fa9c54"]
Plugins which can handle cmd 'getWindowHandles': images
Plugin images is now handling cmd 'getWindowHandles'
Executing default handling behavior for command 'getWindowHandles'
Encountered internal error running command:
Error: The default behavior for this command was to proxy,

Without images plugin, the command works as expected
HTTP] --> GET /wd/hub/session/5266c4a7-5233-49c5-b9ba-e9a42af8fc7c/window/handles
Driver proxy active, passing request on via HTTP proxy
[FlutterDriver] Executing proxied driver command 'proxyReqRes'
[debug] [WD Proxy] Matched '/wd/hub/session/5266c4a7-5233-49c5-b9ba-e9a42af8fc7c/window/handles' to command name 'getWindowHandles'
[debug] [Protocol Converter] Did not know how to rewrite the original URL '/wd/hub/session/5266c4a7-5233-49c5-b9ba-e9a42af8fc7c/window/handles' for W3C protocol
[debug] [WD Proxy] Proxying [GET /wd/hub/session/5266c4a7-5233-49c5-b9ba-e9a42af8fc7c/window/handles] to [GET http://<IP_ADDRESS>:18155/wd/hub/session/46d3d878429d989535156d292c287917/window/handles] with no body
[debug] [WD Proxy] Got response with status 200: {"value":["CDwindow-E52369C84F3123E00079C89E6AF1DDDC"]}
[HTTP] <-- GET /wd/hub/session/5266c4a7-5233-49c5-b9ba-e9a42af8fc7c/window/handles 200 8 ms - 66

Expected Behavior
The behavior for getWindowHandles with and without the images plugin should be the same
Environment
Appium v2.0.0-beta.35 and Appium flutter driver v1.9.0
This issue was created on Appium: https://github.com/appium/appium/issues/18315 and they asked to create an issue here.

Please try out with the latest version. Maybe it already has a fix
https://github.com/search?q=repo%3Aappium%2Fappium-flutter-driver proxyCommand&type=code


Create the first few Potions of the game

[x] Create the POTION tag
[x] Create the drink command
[X] Create some potions to fill the dungeons
[X] Create some healing potions

Closing this one as completed.


[MINOR][INFRA][3.3] Add ANTLR generated files to .gitignore

What changes were proposed in this pull request?

Add git ignore entries for files created by ANTLR.
This is a backport of #35838.
Why are the changes needed?

To avoid developers from accidentally adding those files when working on parser/lexer.
Does this PR introduce any user-facing change?

No
How was this patch tested?

By making sure those files are ignored by git status when they exist.

Is this not necessary on the master branch?

Actually, this is a backport requested by @pan3793

https://github.com/apache/spark/pull/35838#issuecomment-1120111003

Although I'm still neutral for this backporting request, cc @MaxGekk since he is the release manager of Apache Spark 3.3.

Guess this is fine. I am okay.

Meh, it's just .gitignore entries. If it's at all relevant for 3.3, seems OK

Merged to 3.3


client.get hangs and never calls callback

I'm currently experiencing some odd behavior where every so often, some of the calls to client.get hang and the callback function is never called. I've turned on NODE_DEBUG=redis, but the logs aren't showing me anything more helpful, just that a call to client.get was made
Send barreleye.redistogo.com:[port] id 1: *2
$3
get
$70
[key]

I have a ton of debug logs that would fire if the callback comes back, but instead nothing happens and Heroku logs an H12 for a 30 second timeout.
heroku[router] at=error code=H12 desc="Request timeout" method=GET path="/all" host=[app] request_id=[id] dyno=web.2 connect=0ms service=30001ms status=503 bytes=0

Here is what my code looks like
debug(key + ": Checking session in redis");
client.get(key, function(err, response) {
  if (err) {
    debug(key + ": Client.get err=" + err);
  }

  // Cache hit
  if(response) {
    debug(key + ": Cache hit=" + response);
    // handle valid cache
  }

  debug(key + ": No response found");
}

Any idea what would cause client.get to not call the callback? If it helps I'm using Heroku and Redis To Go, and our Redis instance appears to be healthy, using under the limit memory and connections.

@lambertsteven what parser do you use? I guess this might be a duplicate of #875
If the hiredis parser fixes your issue: do you have a reproducible test case? That would be really helpful! I was not able to reproduce that issue yet.

Unfortunately, being able to reproduce the problem is one of our biggest problems. It doesn't happen consistently, and it seems to happen after about an hour or so after restarting the app. Restarting the app seems to clear the issues, but they always come back. It doesn't matter if the request rate is low or high at the time, its about the same amount of chance that the call will hang.
I don't think we're using the hiredis parser, so I guess that means we're using the javascript parser. It looks like this might be related to #875, but it's hard to tell at first glance since we only use client.get and multi.set/exec.
We're using redis 2.2.5.

@lambertsteven your issue should be resolved with #903. Would you be so kind and verify that?

Verifying now, will let you know if it fixed the problem. Thanks for looking into this for us.

The problem doesn't seem to be resolved, we're still getting intermittent timeouts on client.get. We'll use the hiredis parser tomorrow and see if that resolves the issue.

@lambertsteven hm, strange. Please uncomment this line and see if you get any return values.

Alright, so we finally resolved the issue (we hope). We had some code that was using cache = client.multi(), and just using it to call cache.set(key, value) and cache.expire(key, ttl), then calling cache.exec(). This was then throwing an error once in a while in our client.get calls that would say that multi calls cant be nested, and also causing the redis cache to put the value QUEUED into the database instead of the value we expected. It only manifested itself after an hour or so of heavy use. Thanks for working on this, as I'm sure your fix helped solve the problem.

multi has multiplied my complications :)


added to UI

Hey Joyce, I'm getting to review this, but a tip. Please leave a descriptive message in your PRs that describes the work that was done. I know that it doesn't seem necessary because you and I discuss it, but it's a good practice to leave a detailed description of the work you do (also in case I need reminding).

I may not fully understand how the solvation analysis works, but it looks like the solvation changes between frames and so the boolean selection will change between frames.
Because of this, I think you can store the boolean selection on the frames of the trajectory rather than on the topology.
Currently inside of Molecular nodes, I create a 'topology' object, which is an object which contains a vertex for each atom. Each vertex then also contains a number of attributes, which it seems like you have figured out and been able to add successfully.

Along with the topology (in my example ppr) a collection is created ppr_frames inside of which a model is created for each frame of the trajectory that is imported. The same principle applies, with each atom getting a vertex, and each vertex containing attributes that are relevant. For the trajectory, the only thing that changes between frames of the animation in comparison to the topology object are the positions, so currently I only give the vertices a position attribute, which can be used to animate the topology object.

There is no reason why you can't store more attributes on each frame of the animation. I could store all of the same attributes for each frame, but this would be superfluous data, increase save file sizes and import time. For an attribute that would change frame to frame however, such as a boolean selection that defines the solvation shell, this attribute could be stored on the frame objects themselves, rather than having to add multiple boolean attributes to the topology itself.

The node which animates through the trajectory could then output a boolean selection, which is the current frame's solvation_shell, or in theory any other custom per-frame attribute (selection or otherwise).

I'm not sure how the solvation is calculated, whether on a frame-by-frame basis or all at once. If it is done per frame, you get the boolean selection and add that selection to the frame object like so:
    for ts in traj:
        frame = create_object(
            name = name + "_frame_" + str(ts.frame),
            collection = coll_frames,
            locations = univ.atoms.positions * world_scale
        )
        if solvation_shell:
            add_attribute(frame, 'solvation_shell', get_current_frame_solvation(), "BOOLEAN")

I might be off in how the solvation is done, but hopefully this has helped explain how some of this works. Happy to answer more questions about this also!


Reduce HTTP request payload

Using /META-INF/container.xml instead of /mimetype to guess whether given book is packaged or not reduces HTTP request payload because /META-INF/container.xml is cached.

It's  better if the response is cached to JavaScript object and reused later, but this patch doesn't make anything worse.

@KitaitiMakoto, what you say is right absolutely. Thanks.
(At first, I used container.xml. But I changed it later. And now, I've forgotten the reason, perfectly....)

thx!

@satorumurmur
FYI

I've forgotten the reason

I thought the reason might be related to content-type HTTP header.


chore: migrate to rescript

Spent a few minutes migrating this. Used rescript convert src/**/*.re. This converted everything except class types as mentioned in #42. I've converted the classes to the new object spread syntax.
Haven't tested whether this works, as I currently don't use this at work, maybe someone else can test this draft PR and bring it to the finish line.
scripts in Package.json should probably be updated further, e.g. format.

Hi! I finally had time to migrate my app to latest rescript dependencies and test this PR on a real project.
It work well thank you 😊
The only missing part that I think it's still useful are the @obj options functions in Navigators (bottomaTabBarOptions()in BottomTabs, materialTopTabBarOptions() in MaterialTopTabs, …) because it's not yet possible to create Object without specifying option('a) attributes.

Thanks for this PR. I tried conversion a few months ago, but virtual class where being dropped entirely... It seems here there is something to cover this.
@Freddy03h if you have time, we can merge this in a wip branch & you can continue contributing from here. Sounds good to you ?

@Freddy03h up to continue the migration? or @cem2ran do you have time for this?


Live cross validating fields on credit card form

I'm trying to validate a credit card date to make sure it hasnt expired.
I have two fields cardMonth and cardYear. I would like for both fields to validate when either one is modified.
This is my current schema and shared date validation method.
Cart.isCardDateValid = (month, year) ->
  currentDate = new Date()
  currentMonth = currentDate.getMonth()
  currentYear = currentDate.getFullYear()
  currentYearShort = parseInt(currentYear.toString().substr(2,2))

  if year > currentYearShort
    return true
  else if year == currentYearShort and month >= currentMonth
    return true

Cart.CheckoutSchema = new SimpleSchema
  cardMonth:
    type: Number
    custom: ->
      unless Cart.isCardDateValid @value, @field("cardYear").value
        return "cardExpired"
      unless @value >= 1 && @value <= 12
        return "cardInvalidMonth"

  cardYear:
    type: Number
    custom: ->
      unless Cart.isCardDateValid @field("cardMonth").value, @value
        return "cardExpired"
      unless @value.toString().length == 2
        return "cardInvalidYear"

And in my template.
+quickForm schema="Cart.CheckoutSchema" validation="keyup"

This works when submitting. But doesn't work as I enter values. I have to click in and then click off the other field for it to validate.
How can this be done cleanly?

The issue here is that on keyup and blur, we revalidate only the current field for performance reasons. A workaround for your situation would be to define your own keyup and blur handlers that call AutoForm.validateForm. For now I will close this, but if enough people need this, maybe some way to force additional fields to be validated on keyup could be added.

+1 on this feature request
I too have a pair of fields that validate against each other.  Would expect that if I reference a field/siblingField in a custom validator function, the validator would rerun when the referenced field changes value.


ENHANCEMENT Allow menu to be extendable from DNProject

Allows an extension class to add their own menu items and to remove
existing ones if necessary.

I think it looks good enough to support adding more menu items, which we will have to do unless we want to bundle everything into deploynaut base module, which I don't like at all.
In the end I think we will have to do some UI refactoring around the navigation and presentation. Deploynauts look and feel could need some :heart:

Nice job. :)


User-defined schema in MilvusVectorStore

Description
This PR introduces two new optional fields in the MilvusVectorStore constructor, in order to explicitly define fields to include in the created Milvus collection. Defining fields in the schema (non-dynamically) allows to create indexes for these fields, which is crucial for speeding up queries in production.
Fixes #16123, #15987
New Package?
Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

[ ] Yes
[x] No

Version Bump?
Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

[x] Yes
[ ] No

Type of Change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Added new unit/integration tests
[ ] Added new notebook (that tests end-to-end)
[x] I stared at the code and made sure it makes sense

Suggested Checklist:

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added Google Colab support for the newly added notebooks.
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] I ran make format; make lint to appease the lint gods

This merge, unfortunately brokes MilvusVectorStore , v 0.2.4.
You can check it by yourself , using the example provided in the docs

@logan-markewich , He is a PR that fix this, and this other bug I reported  few days ago. It integrates the changes proposed by @petros94 , and fixes the issue with the index creation.
Here is a jupyter notebook to show the fixed version.


CDAT Migration: Refactor aerosol_budget

Description

Closes #673

Todo

[x] Refactor aerosol_budget_driver.py
[x] Refactor aerosol_budget_plot.py

[x] Add formulas to formulas.py
[x] Add derived variables to derivations.py

Hybrid to pressure functionality

[x] Add "hyai" and "hybi" to HYBRID_SIGMA_KEYS and expand accepted values
[x] Add p0, a_key, and b_key to _hybrid_to_pressure()
[x] Add logic to _hybrid_to_pressure() to update units based on p0

[x] Update call to get_name_yrs_attr() in aerosol_aeronet_driver.py
[x] Add changes from #804 and #805

5/8/24 Fixes

[x] Fix Elevated Emission (Tg/yr) -- much larger on dev -- due to using xarray .sum() instead of Python sum() on a tuple of variables, update `
[x] Fix Burden -- units seem smaller on dev (unit conversion?) -- fixed, I think fixing derivation formulas fixed this
[x] Fix Lifetime (Days) -- uses Burden for calculation
[x] Fix Sulfate Elevated Emission (Tg/yr) -- due to sum
[ ] Fix large differences in burden and lifetime values -- different units still?

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

If applicable:

[ ] New and existing unit tests pass with my changes (locally and CI/CD build)
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have noted that this is a breaking change for a major release (fix or feature that would cause existing functionality to not work as expected)

#804 and #805 is related to this PR. We need to carry over any code changes here.

@mahf708 in my test, I ran into one problem with aerosol budget table:
2024-04-12 13:42:45,788 [INFO]: aerosol_budget_driver.py(run_diag:147) >> Variable: bc
2024-04-12 13:42:45,877 [ERROR]: core_parameter.py(_run_diag:269) >> Error in e3sm_diags.driver.aerosol_budget_driver
Traceback (most recent call last):
  File "/home/ac.zhang40/y/envs/edv2110/lib/python3.10/site-packages/e3sm_diags/parameter/core_parameter.py", line 266, in _run_diag
    single_result = module.run_diag(self)
  File "/home/ac.zhang40/y/envs/edv2110/lib/python3.10/site-packages/e3sm_diags/driver/aerosol_budget_driver.py", line 148, in run_diag
    metrics_dict_test[aerosol] = generate_metrics_dic(
  File "/home/ac.zhang40/y/envs/edv2110/lib/python3.10/site-packages/e3sm_diags/driver/aerosol_budget_driver.py", line 82, in generate_metrics_dic
    elvemis = data.get_climo_variable(f"{aerosol}_CLXF", season)
  File "/home/ac.zhang40/y/envs/edv2110/lib/python3.10/site-packages/e3sm_diags/driver/utils/dataset.py", line 161, in get_climo_variable
    variables = self._get_climo_var(filename, *args, **kwargs)
  File "/home/ac.zhang40/y/envs/edv2110/lib/python3.10/site-packages/e3sm_diags/driver/utils/dataset.py", line 386, in _get_climo_var
    derived_var = func(*variables)
  File "/home/ac.zhang40/y/envs/edv2110/lib/python3.10/site-packages/e3sm_diags/derivations/acme.py", line 1654, in <lambda>
    (("bc_a?_CLXF",), lambda *x: molec_convert_units(sum(x), 12.0)),
  File "/home/ac.zhang40/y/envs/edv2110/lib/python3.10/site-packages/e3sm_diags/derivations/acme.py", line 175, in molec_convert_units
    if var.units == "molec/cm2/s":
AttributeError: 'int' object has no attribute 'units'

I'm wondering if this is caused by some new change of the output?

Viewer

Dev viewer: https://portal.nersc.gov/project/e3sm/cdat-migration-fy24/673-aerosol-budget/viewer/aerosol/index.html
Main viewer: https://portal.nersc.gov/project/e3sm/cdat-migration-fy24/main/viewer/aerosol/index.html

CSV File Diff Comparison (VS Code)
"ANN" comparison -- no highlighted diffs

"JJA" comparison -- no highlighted diffs


[d4hines] make minimum block time configurable

Depends

[ ] #648

Problem
Right now, Deku throttles itself to produce blocks every second. Users may want to configure this throttle.
Update:
As @EduardoRFS suggested in #692, this PR additionally implements a short-circuit to the delay if there are any pending operations and changes the default block delay to 5 seconds.
Solution
Add an option at the command line to configure the throttle.

Stacked PR Chain: d4hines

PR
Title
Status
Merges Into

#691
fix: fix prometheus with tilt

-

#647
feat: block rate and transaction rate metrics  d4hines/block-rate-and-tps

#691

#658
chore: refactor cli terms                      d4hines/batch-operations

#647

#681
chore: refactor config out of node state

#658

#668
👉make minimum block time configurable

#658

#539
Benchmarking: ticket transfers                 d4hines/ticket-transfer-benchmarking

#658

@EduardoRFS , I did what you suggested in the fixup commits.

Our CI is broken, but we have fixes downstream of this change - merging without green CI.


beta, not preview on checkpoint-blobstore

Docs Build status updates of commit da8f5c0:
:clock10: Full build: the average full build time is 11 min(s), this is based on the last 3 build(s) for this repository.
:warning: This is a FULL build due to the 'master' branch being a new branch in Docs Build service and is still building, or there are build errors in 'master' branch so the cache for incremental build is not available. Normally no action is required on your part, but if the full build persists, please contact your repository admin to manually perform a full build on the 'master' branch. For more detailed info, please click here.


Remove sandbox's Python 2 builtins.file support

Summary of changes

If I'm not mistaken, this looks like support for Python 2's https://docs.python.org/2.7/library/functions.html#file that never got cleaned up. Where _file should always be None nowadays.
Pull Request Checklist

[ ] Changes have tests
[ ] News fragment added in newsfragments/.
(See documentation for details)

Oh nice, this reduced changes in https://github.com/pypa/setuptools/pull/4192


Missing functionality: useWatchContractEvent missing in Vue?

Check existing issues

[X] I checked there isn't already an issue for the bug I encountered.

Describe the bug
It seems that useWatchContractEvent exists in the React library but not the Vue one, and watching for contract events is important functionality.
Link to Minimal Reproducible Example
No response
Steps To Reproduce
No response
What Wagmi package(s) are you using?
@wagmi/vue
Wagmi Package(s) Version(s)
0.0.40
Viem Version
2.13.4
TypeScript Version
5.5.4
Anything else?
No response

Needs to be implemented. Moving to discussion as a feature request.


Error in dcn

Thanks for your great works! I first train the nusc_centerpoint_voxelnet_01voxel.py and it works, but when I turn to nusc_centerpoint_voxelnet_0075voxel_dcn_flip there is an error in dcn:

error in deformable_im2col: no kernel image is available for execution on the device

But the Installation works, my platform:
Ubuntu 18.04
RTX 3090
CUDA 11.1
Python 3.7.11
Pytorch 1.9.0
By the way, is it necessary to install cudnn for setup?

hi, first of all, I suggest using this config https://github.com/tianweiy/CenterPoint/blob/master/configs/nusc/voxelnet/nusc_centerpoint_voxelnet_0075voxel_fix_bn_z.py
it doesn't need to build dcn with better results and faster training speed (66.8 vs 65.4). You can also do flip testing using this config (and get the extra improvement).
For your original question, I guess they are some code change needed for coda 11.1 (as the original code is a few years old now).

But the Installation works

You mean bash setup.sh works ? Are you installing in the same environment as your 3090 ? (for instance, you may need to set cuda_visible_devices if you get two different gpus on your server)

Thanks for your reply! The new config you mentioned could run on my platform. Following your suggestion, I re-build the code and find I downgrade the CUDA arch to 7.5 with:

export TORCH_CUDA_ARCH_LIST="7.5"

to build spconv and apex before run bash setup.py, which results in the error. After canceling the setting, the bash setup.py still works, but I need some modification to build spconv and could only install spconv-1.0. Meanwhile, when I run the dcn config again, the original error disappears but there is a new error:

File "/root/code/CenterPoint/det3d/ops/dcn/deform_conv.py", line 92, in backward
cur_im2col_step)
RuntimeError: view size is not compatible with input tensor's size and stride (at least one dimension spans across two contiguous subspaces). Use .reshape (...) instead.

Yeah, I suggest just using the new config. It is better and faster

Ok, thanks for your reply!


Contract setup Completed is the same for taker and maker

Either of the roles has to record the outcome of the setup, which should be the same for them.
In order to handle this in our event model we need Completed in the model so it is not role specific.

bors r+

@klochowicz Seems there is still something not quite right with the timeouts :(

bors retry


Suggestion: Increase the automatic width of the left connection bar

Hello, can the connected storage bar on the left adjust the width by itself? Otherwise, you have to move the mouse to it every time to show the connection name, which is very unintuitive, thank you.

Hi @Merbeleue,
by right-click on connection you can customize icon and label to have a more intuitive list of connections.
You can also drag & drop connections to sort them or to create and customize folders.

However, in many connection situations, you have to use the mouse to identify the names one by one, which is very unintuitive, and the width on the left cannot be adjusted.

Click on the "all connections" link?  That dialog also allows you to search for the name.


Ambassador Pledge not available for download

Ambassador Pledge should be available for download before user is required to upload a signed copy.

It is part of chapter 24 https://oceanacademy.io/ocean101/chapter-24


allow optional claim specs when verifying JWT access tokens

When verifying a JWT or a Bearer token currently only the nbf and exp claims are checked as this is the default. I'd like to also verify things like iss and maybe aud. Allowing callers to provide the claim specs seemed to be the easiest approach.

Thanks, Hans!

well, actually: thanks @bodewig; I'll add you to the AUTHORS right away!


Build(deps): Bump @patternfly/react-table from 4.113.1 to 4.113.2 (#4897)

Pull request opened by the merge tool on behalf of #4897

Merged in 57d2806a8e2ac4e24b794d5c59c313c9ccd406cd


Fix CI for arduino-cli 0.28

Signed-off-by: acuadros95<EMAIL_ADDRESS>

@mergify backport foxy galactic main


google/recurrentgemma-9b-it support

The scores are promising and might be a great addition

Sorry currently transformer based models are what we support in the mean time


Unable to resolve dependency tree with React 18/Next.js

I'm starting a project with Next.js
npx create-next-app my-project
Then i install
npm i little-state-machine
But when i try to install little-state-machine-devtools i have the problem
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: undefined@undefined
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR!   peer<EMAIL_ADDRESS>|| ^17 || ^18" from<EMAIL_ADDRESS>npm ERR!   node_modules/little-state-machine
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!     peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/little-state-machine-devtools
npm ERR!       little-state-machine-devtools@"*" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/little-state-machine-devtools
npm ERR!   little-state-machine-devtools@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.

This is my package.json:
{
  "name": "test",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "next": "12.1.6",
    "react": "18.1.0",
    "react-dom": "18.1.0"
  },
  "devDependencies": {
    "eslint": "8.15.0",
    "eslint-config-next": "12.1.6"
  }
}

How can i solve this with React 18/Next.js?

@bluebill1049 is there anyway you check this?, i'm having peer dependency problems with React 18

Here's a PR that should work for react 17 & possibly 18:
https://github.com/bluebill1049/little-state-machine-dev-tools/pull/55

Here's a PR that should work for react 17 & possibly 18: #55

Thanks, but i already changed solutions. It broke many of my projects that used little-state-machine package 😢


[WebUI] Homepage

Don't use plain css, we have material UI for this
Homepage should be only rendered if there are no collections

@trean please take over

@generall done, check please if it's what you wanted


Huge delay or not opening camera Iphone SE

From @ppun51 on June 22, 2016 16:41
Which Plugin does this impact: Xamarin Plug IN 2.30
Please fill out either the bug or feature request section and remove whatever section you are not using.
No Bug number for this issue
Version Number of Plugin:
Device Tested On: Iphone SE
Simulator Tested On: No
Some times opening camera with Huge delay or not opening camera.
When open camera,  all of buttons are freeze with black screen until I touch middle of screen.
Do you have anyone have this issue?
I am about to test it with Iphone 6S.
Is there any limit for this plug in to supports?
Copied from original issue: jamesmontemagno/Xamarin.Plugins#342

I cant' fix specific device issues as I have had problems with any iOS device local.


Project link
Click here
Domain
Add 'x' inside [ ] to cross check box.

[ ] App with Flutter
[ ] App with Java
[ ] App with Kotlin
[x] Web with Html,css javascript
[ ] Web with React

Please describe your feature.
In drag n drop currently we can only drag n drop image already present in the website, try to add functionality so that users can drag and drop any image they want from external storage and can delete them as well.
Describe the solution you'd like
NA
Additional context
NA

Sorry to say , please don't contribute as it is excluded from Hacktoberfest 2022.

Can i work on this issue?

@PiyushIngale007 Sure, you can, but i hope you know this repo is not in hacktoberfest anymore.

Okay. Assign this issue to me


Nuclear Peace Text

The text of the event seems to be broken as seen in the picture.
_ requested us to agree... (who?), Nuclear Peace between Germany and Germany;

This is a core feature. The text is "Nuclear Peace between $FROMCOUNTRY$ and $COUNTRY$". So the event receiver will have $COUNTRY$ to what ever name the country has. And  $FROMCOUNTRY$ to Germany.


Update pnpm version to 8.6.9

What
Update pnpm version to 8.6.9 (latest)
Why
Seeing issues in #3355 where the wrong dependency is pulled in locally. Not repro-ing on new version of pnpm.
How Tested
Build locally works. CI should verify this.

It looks like the new package versions has somehow caused the API generation to get rebuilt in an unexpected way.

API CHANGES FOUND in beta flavor - PLEASE RUN " rush build -t @azure/communication-react"
Changes:
M packages/communication-react/review/beta/communication-react.api.md
M packages/react-components/review/beta/react-components.api.md
M packages/react-composites/review/beta/react-composites.api.md
Error: Process completed with exit code 1.

It looks like the new package versions has somehow caused the API generation to get rebuilt in an unexpected way.

Updated - removed the weird types reference that we don't know why is there in the first place...

Breaking change check not coping well with the face the base branch is build with a newer pnpm version. This may fix it #3356 but may have to skip breaking change check for this PR


Unable to build for 'osnma-longan-nano'

Good day!
I have tried to follow the instructions exactly but unfortunately have been unable to build the crate for 'osnma-longan-nano'
Here is some output that I hope might both illustrate the error and hopefully provide enough detail to point out where I have gone wrong.   Many thanks!!
k4kdr@3010i5:~/galileo-osnma/osnma-longan-nano$ cargo build --release
   Compiling subtle v2.4.1
   Compiling cfg-if v1.0.0
   Compiling base64ct v1.4.1
error[E0463]: can't find crate for `core`
  |
  = note: the `riscv32imac-unknown-none-elf` target may not be installed
  = help: consider downloading the target with `rustup target add riscv32imac-unknown-none-elf`

For more information about this error, try `rustc --explain E0463`.
error: could not compile `subtle` due to previous error
warning: build failed, waiting for other jobs to finish...
error: build failed

k4kdr@3010i5:~/galileo-osnma/osnma-longan-nano$ rustup target add riscv32imac-unknown-none-elf
info: component 'rust-std' for target 'riscv32imac-unknown-none-elf' is up to date

k4kdr@3010i5:~/galileo-osnma/osnma-longan-nano$ rustup component list --installed
cargo-x86_64-unknown-linux-gnu
clippy-x86_64-unknown-linux-gnu
rust-docs-x86_64-unknown-linux-gnu
rust-std-riscv32imac-unknown-none-elf
rust-std-x86_64-unknown-linux-gnu
rustc-x86_64-unknown-linux-gnu
rustfmt-x86_64-unknown-linux-gnu

k4kdr@3010i5:~/galileo-osnma/osnma-longan-nano$ rustup show
Default host: x86_64-unknown-linux-gnu
rustup home:  /home/k4kdr/snap/rustup/common/rustup

installed targets for active toolchain
--------------------------------------

riscv32imac-unknown-none-elf
x86_64-unknown-linux-gnu

active toolchain
----------------

stable-x86_64-unknown-linux-gnu (default)
rustc 1.59.0 (9d1b2106e 2022-02-23)

k4kdr@3010i5:~/galileo-osnma/osnma-longan-nano$ rustup toolchain list
stable-x86_64-unknown-linux-gnu (default)

Ok, problem solved.   I removed the version of rust that I  had previously installed from the Ubuntu repository and reinstalled from  https://www.rust-lang.org/tools/install
... now the build completes successfully.

I think the problem here is that you had two copies of rustc. One installed system-wide by apt, and the other one installed to $HOME/.cargo/bin by rustup. Only the rustup one had support for rv32imac. However, depending on which order you have the folders in your $PATH, when you call rustc you may get one or the other. It looks like cargo was actually calling the system-wide rustc. You can see which one you get with which rustc. Probably you should have $HOME/.cargo/bin first in your $PATH to avoid weird problems like this one.

Good. I think this issue can be close now (you can close it yourself).

Will do!


Pokemon GO Live Map Status = Waiting

Hi all,
My scanner is not working, the status is not operational but waiting.

Tried re-installing, but did not work.

I got the same, this happen to me because I use a new PTC account an never login to the game, so I login to the game, choose a nickname etc, and then I log in again in the map and work :)

@skylex77 Thanks, but it's not working. Made a new PTC account and done the necessary steps, but not working,

[ search_worker_0][        models][ WARNING] table pokestop has no column named active_pokemon_id... Retrying, is what I get on console

Actually, now I see SOME accounts of mine work and some don't. Ban perhaps?

I am facing the same issue, even after creating new PTC account. Its showing as waiting since morning and also there are few ones that are not leaving the screen - they are showing some 500+hrs for expiry and those are the only ones shown. Any idea what to do?

Have you all checked the login server statuses?
http://ispokemongodownornot.com/
looks like US logins are down for both Google and PTC

@Fryhole8816 Don't think so. I have tried it with two PTC account (one made recently, logged in, caught a starter etc.) and if it was banned, then you couldn't play login with the PTC account, see pokestops, etc. The issue started happening since the 500+hrs ''bug''. @gautamjain28 It might be the servers as well @AVellucci, but I'm located in Europe so it should work fine..

I'm having issue as well in US the up and down site show its OK

Removing the pokemon folder in roaming worked for me, issue solved

Now site shows PTC login is down.

close

I can sign into a Pokemon Trainer account I use to play but the one I use for the map is telling me thanks for the overwhelming support, please try again later (or something to that effect)
Temp Bans?

I have a few accounts have the same problem Try to log in through app and saw "can't retrieve data". So yes, they are banned. Can anybody teach me how to change search delay manually for this program.

I have slowly been loosing accounts too.  They are catching on some how.

I have the same issue, started right around the same time as this post.

Created new PTC account and issue went away. I would guess that it is a wave of bans. the way the accounts behave must be unique compared to a real player. for example the account is logged in but never captures pokemon or never accesses pokestops.

I am not sure about the ban theory. I created a second PTC account and API key and still says Waiting. Also deleted the roaming folder first just in case. My spare google account works fine with the old api key (not sure if they ban api keys too). So the problem is somewhere in the PTC login process I think. Will just use Google while I wait it out.

Hi, i'm having the same issue in France.
I have tried with a new ptc account too, doens't work.
I don't know if it's related but i was using an android app (pokescanner). It was working fine until 2 hours ago, now it doesn't work anymore. doesn't show anything

Probably banned. Both of mine were banned. Won't be using this anymore.


Set react-docgen resolver to support styled-components

Currently, the PropsTable component does not recognize components made with styled-components.
react-styleguidist has the option to set a custom react-docgen resolver to fix this, as shown here: https://github.com/styled-components/styled-components/issues/945
Could we have something similar here? Or even better, to support styled-components by default?

I was looking for a way to solve this and saw that this project uses babel-plugin-react-docgen which doesn't support using custom resolvers.
Now, the author is open to accepting a PR for that, which wouldn't be very hard...
but it wouldn't be of any use since I'm having problems configuring plugins with the modifyBabelRc option;
export default {
  wrapper: 'doczWrapper',
  propsParser: false,
  modifyBabelRc: conf => {
    conf.plugins.push(['react-docgen'])
    return conf
  },
}

This throws an error while building:
Module build failed (from ./node_modules/happypack/loader.js): TypeError: Property name expected type of string but got null
I don't know why.
I had to set propsParser: false because the babel config I get from modifyBabelRc doesn't have any plugins on it, so if I add the babel-plugin-react-docgen, docz then adds it again, resulting in a duplicated plugin error.
So to summarize, the first problems to solve are

Config frommodifyBabelRc doesn't have any plugins on it
Error from happypack when manually adding babel-plugin-react-docgen (as shown in the snippet above)

Yeah, I can't use it with Styled Components yet...

Having the same issue, would be happy to collaborate on this @Emilios1995.

@Emilios1995 you should not add babel-plugin-react-docgen as it's already in Docz. I am using react-emotion styled-components and was able to get PropTypes descriptions by doing this:
const StyledBadge = styled('div')`
  ${baseStyles};
  ${colorStyles};
  ${circleStyles};
`;

/* Adding this line makes react-docgen work for styled-components */
const Badge = props => <StyledBadge {...props} />;

Badge.propTypes = {
  /**
   * Callback for the click event.
   */
  onClick: PropTypes.func,
  /**
   * Ensures text is centered and the badge looks like a circle.
   */
  circle: PropTypes.bool,
  color: PropTypes.oneOf(values(colorNames))
};

@Emilios1995 could please you use the example as base to test?
I will close the issue, if the error continue with your case, reopen again.
https://github.com/pedronauck/docz/tree/master/examples/styled-components

@Emilios1995 you should not add babel-plugin-react-docgen as it's already in Docz. I am using react-emotion styled-components and was able to get PropTypes descriptions by doing this:
const StyledBadge = styled('div')`
  ${baseStyles};
  ${colorStyles};
  ${circleStyles};
`;

/* Adding this line makes react-docgen work for styled-components */
const Badge = props => <StyledBadge {...props} />;

Badge.propTypes = {
  /**
   * Callback for the click event.
   */
  onClick: PropTypes.func,
  /**
   * Ensures text is centered and the badge looks like a circle.
   */
  circle: PropTypes.bool,
  color: PropTypes.oneOf(values(colorNames))
};

this seems like a simple workaround, maybe @pedronauck can close this issue.
P.S. is there a way to integrate this solution directly into Docz ? or may be we add custom resolvers to react-docgen setting in Docz?
This way nobody will have to type extra things, but also enabling styled-components support ;)

This is not a "simple" solution.
I am in the process of documenting a project done with styled components with a big set of components already implemented, changing all the components right now is not a viable solution.
Is there any work around other than wrapping the Styled Component?

@ilyanoskov @antoniojps this is not really an option: doing so will break any styled-component functionality, as none of the properties from the styled-components will be available in the new wrapping component.