Fix bug when repo remained bare if multiple branches pushed in single push

Fixes #4919
Also closes #3704 (now it's impossible to un-bare repo with tag push)
Bug happened because CommitsBefore method was intended to use in webhooks only, but it was used to determine if pushed branch is not empty (has at least one commit). But in PR https://github.com/go-gitea/git/pull/88 it was changed to ignore commits that have multiple branches (to avoid pushing the same commits twice if other branch is created).
Now i just check this conditions to un-bare repo and set default branch to first pushed branch:
(1) repo is bare
(2) new branch is non-empty (idk if it's possible to push empty branch to bare repo, but extra cautions won't harm)
(3) branch is branch, not tag (which also affects default branch change and makes #3704 impossible too)

Codecov Report

Merging #4923 into master will increase coverage by 0.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #4923      +/-   ##
==========================================
+ Coverage   37.41%   37.42%   +0.01%
==========================================
  Files         305      305
  Lines       45239    45241       +2
==========================================
+ Hits        16926    16933       +7
+ Misses      25868    25865       -3
+ Partials     2445     2443       -2

Impacted Files
Coverage Δ

models/action.go
58.75% <50%> (-0.04%)
:arrow_down:

models/repo_indexer.go
52.11% <0%> (+1.27%)
:arrow_up:

modules/process/manager.go
81.15% <0%> (+4.34%)
:arrow_up:

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 ea20ada...4ca7cfa. Read the comment docs.

@SagePtr  Please send back port to release/v1.5


Ionic 3 - Firebase storage images not working

I have set up the image loader within my ionic 3 app - all works beautifully
The minute i try and load any firebase stored images (Firebase storage) - It stops working and returns an error to the Xcode console which is of no use:
ERROR: ERROR [object Object]
This is only happening on the physical device. On the laptop in chrome, it works fine, just not on IOS.
Any have any idea why this happens?

Im not able to reproduce this error without further informations. Can you paste your code how you resolve the image URL from firebase?

I have no problem loading firebase storage images!

I can confirm loading images from Firebase works fine on iOS 12.2.


Plugin refuse to work with space in home path

Describe the bug
A clear and concise description of what the bug is.
The plugin refuses to generate because my home path contains a space
To Reproduce
Steps to reproduce the behavior:

Have a home path with space inside (typically Windows with accounts of full names)
Run :CMakeGenerate

Expected behavior
The project should successfully configure
Screenshots

Other info

OS: Windows 10
Vim/Neovim version: 0.4.4
Vim-CMake version (5th line in :help cmake): 0.3.0

Additional context

Hi, thanks for reporting the problem.
I've tried to reproduce it on Linux, and there is actually no issue. I created a project inside a directory with path /home/cdelledonne/Developer/Directory with spaces/Test project, then ran ":CMakeGenerate" from inside of Test project, and I got a normal, successful output:
cmake -DCMAKE_BUILD_TYPE=Debug -S . -B Debug
-- The C compiler identification is GNU 10.2.1
-- The CXX compiler identification is GNU 10.2.1
-- Check for working C compiler: /usr/lib64/ccache/cc
-- Check for working C compiler: /usr/lib64/ccache/cc - works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/lib64/ccache/c++
-- Check for working CXX compiler: /usr/lib64/ccache/c++ - works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/cdelledonne/Developer/Directory with spaces/Test project/Debug

The problem must be with Windows refusing to run the bash script that powers the Vim-CMake console (the script being scripts/console.sh). As mentioned in the README, Windows is not supported yet. I haven't thought of a way to run this bash script on Windows, as my knowledge of it is quite limited.
I'm closing this issue as the problem is different than what is described. Please feel free to open a feature request and ask for support for Windows. Maybe somebody has some suggestions as to how to approach it. Perhaps you could even look into it, if you feel like it.

EDIT: actually the directory with spaces creates trouble when the plugin itself is inside a path with spaces. I'm reopening the issue as I should look into this as well. But the problem with Windows remains.

Thank you very much for putting effort to investigate this! I really appreciate it 👍

I'll rename the title of this issue to reflect the actual issue 👍

Can confirm it works! 👍

Out of curiosity, on which platform/terminal did you test it?

I tested it on Windows 😉 . I mainly use the Windows Terminal.


Problem with double lineshifts

Julia throws an error when there are two consecutive blank lines inside a block being sent by SendTextPlus. If I manually copy-paste the same lines (with double line shift) into the terminal, there is no error.
This works:
if true
    println("Hello")

end

This returns ERROR: syntax: unexpected end:
if true
    println("Hello")

end

I don't think there is any easy fix.
Also, I don't think it is a good practice to put two consecutive blank lines.

If you have using Terminal/iTerm on Mac, 0.6.9 now handled by enabling the bracketed paste mode.


Fix version reporting in console, closes #257

ParaTest has the version number hard-encoded.
Previously when reporting the version via --version that hard-encoded
version number was presented in the output (e.g. 1.0.1).
As technically the version changes with git commit and not every git
commit is tagged and not even every tagged commit contains the appropriate
change to the hard-encoded version number within
\ParaTest\Console\ParaTestApplication::VERSION

the wrong version is reported.
This commit addresses the issue by first looking up the installed version
of the package "brianium/paratest" from within composer's installed.json
file which contains the currently installed version (based on the git tag,
see Packagist) and if not found (e.g. you have checked out the development
version in a git clone) the version number will be taken from git directly.
If everything of these look-ups fail, the fallback is to the current
behavior of taking the version from the constant.
Refs:

#257

With these changes, example output from development version (clone):
$ bin/paratest --version
ParaTest 1.0.1-10-g89f72e2

And when installed via composer:
$ vendor/bin/paratest --version
ParaTest dev-patch/give-version-257

It shows the inline alias version.

Awesome 👍
Should we change the hardcoded (default) version to 1.x then? That would make the output always correct until release 2.0.0 (correct even if not complete at the worst case like phar installs).

From what I know from other projects, it's OK to make it a place-holder like @package_version@ (e.g. Composer does it that way IIRC).
When you start to provide a phar package, a build process can replace it.
Strings like the suggested "1.x" tend to be misleading in case things go havoc (too close to a "real" version when output so not obvious enough to the reader). It also has the benefit that these are easy to replace, so open up a good migration path.
For example, that special version as it is right now can be taken as-is for the moment, you pull in the pr and after some experience how it works out (it's hard to test, so usage will show up issues here you want to patch when found) - then after some time, you can consider to move to a place-holder-value there. I think that is a sane suggestion.

btw. and a bit off-record: How did you manage to merge the coverage? Just yesterday I was looking on how to invoke a PHP script within a test-suite. I was able to keep the parameters (in the end) for remote debugging, but code-coverage is quite a different beast as PHPUnit knows nothing about that child-process code-coverage.

Thanks for the contribution.
The merging is a feature of php-code-coverage itself. I had to deliver a small fix that it works correct when you import an exported coverage but apart from that, it's as easy as $coverage1->merge($coverage2).
I think it just adds all lines from $coverage2 to $coverage1 and if a line already exists, a covered line is preferred.
Getting coverage of generic php subprocesses would be hard. But as paratest is executing multiple phpunit instances, we let each phpunit subprocess generate its own coverage and just need to collect these coverage exports...and merge them.

Bit late to the show, but relying on having git available, might not be the best thing to do.
For example, I install things using my own tools on OSX, or inside a docker container. When I actually run the code, it'll be in a separate container, where the git-executable is not available.

@Multiply: In case the git command fails, there is the fallback to the current behavior.

@julianseeger: Thanks for the infos. As my scenario is also about Phpunit, that kind of infomration is really helpful. Thanks.


Uart wrapup

multi-pin, multi-peripheral support via the config structs and shared DMA

Test Procedure
I ran each of the examples/uart tests on the Daisy Patch.
All RX examples were fed by a Field running the Blocking TX example.
All TX was verified with my logic analyzer.
If it's not mentioned here, it worked fine.
Blocking TX DMA RX / DMA TX Blocking RX
These examples are written with a simple dma flag to avoid the blocking call being interrupted by the dma call.
If you try to write it in a more normal manner

The DMA interrupts the blocking call.
It calls the end dma cb, where it tries to start a new DMA.
This waits forever for HAL_UART_STATE_BUSYRX/TX
Since we interrupted the blocking call, that flag will never be ready!

I tried using the ScopedIrqBlocker in the BlockingTx/Rx to avoid being interrupted by the DMA.
However, this causes the blocking call to get stuck forever. I think there's an internal cb which readies gets the blocking call ready which we're blocking in addition to the dma.
Unless we have a good way to block the DMA cb, but not whatever HAL cb we need here, I think the flag based method I used in the tests is OK for now. This is sort of an edge case anyways.
TODO

[ ] Changelog

I tried using the ScopedIrqBlocker in the BlockingTx/Rx to avoid being interrupted by the DMA.
However, this causes the blocking call to get stuck forever.

This is because the blocking functions use HAL_Delay() which waits for the SysTick variable to increment, and if IRQs are blocked, that will never increment.
I don't think it would be the worst to require that a peripheral use only one method-type (i.e. DMA or blocking) for both rx/tx since the peripheral is linked, but I am open to other solutions.
That said, it seems like a limitation of how the HAL's state machine within the UART peripheral is configured.

Each of these was tested on USART_1 and USART_3, along with concurrent audio passthrough.
Blocking Receive

Tested using the Blocking_Receive example. Data was sent from Blocking_Transmit.

Blocking Transmit

Tested using the Blocking_Transmit example. Data was received by Dma_Receive.

DMA Receive

Tested using the Dma_Receive example. Data was sent from Blocking_Transmit.

DMA FIFO Receive

Tested using the Dma_Fifo_Receive example. Data was sent by the Dma_Transmit example. I think this is quite a friendly way to interface with the UART. Definitely my favorite.

DMA Transmit

Tested using the Dma_Transmit example. Data was sent received by the Dma_Receive example, and its correctness verified over USB (it was very speedy)

Blocking Transmit + DMA Receive

Tested using the Blocking_Transmit_Dma_Receive example, sent to a blocking passthrough program with different RX, TX buffers to verify.

Dma Transmit + Blocking Receive

Tested using the Dma_Transmit_Blocking_Receive example, sent to a blocking passthrough program with different RX, TX buffers to verify.

Blocking Transmit + FIFO Receive

Tested using the Blocking_Transmit_Fifo_Receive example. This one was fun :).

DMA^2

For some reason, I ran into trouble getting this working with my simple blocking passthrough patch. I may need to revisit this one to ensure it works as expected.

MIDI

MIDI functionality was tested using the DaisyExamples Patch MIDI example compiled with the latest libDaisy. I sent a simple ascending series of note on messages, and it seemed to rise in pitch as expected.

One notable issue that I don't think is mentioned anywhere is the USART_1 - USB conflict. It seems like any USB usage will prevent USART_1 from working as expected in rather unexpected ways. We should probably make a note of that somewhere in the documentation.
Overall, from my testing, it seems like the functionality is solid.

Just about ready to merge this
just two small things:

[ ] the changelog entries are in the old (now-released) section. So I'm a bit concerned they'll get thrown in there. Let's just do a premerge on that, and make sure the new entries are in the (current) unreleased section.
[ ] let's remove the vscode files from the uart example that has them.


is support async？

is support async？

I guess you want async support for write, right ?
This is not implemented. But should be quite easy with resteasy which drives the communication to influxdb. Feel free to send a pull request.

I plan to make the write available in a async flavour in the 0.9.0_support branch.

the actual version 2.0-SNAPSHOT has batch support built in, so i close this issue.


Disks the same slot, but different controllers (i.E. ide0 for cloud-init and scsi0 for boot-drive) cause disk-deletions and nondeterministic behavior

Create new Virtual Machine in Proxmox (without Terraform!):
 * General:
  * Any name, I choose "TF-RESET-TEST"
  * ID doesnt really matter, i choose 3500
 * OS:
  * "Do not use any media"
  * Guest OS Type: Other, Version: -
 * System:
  * Leave all to default
  * Check that SCSI Controller is set to VirtIO SCSI Single
 * Disks:
  * Bus: SCSI / 0
  * Storage: I choose our Proxmox Ceph
  * Size: 5G
  * No SSD Emulation
  * Backup enabled
  * No Discard
  * IO Thread enabled
 * CPU:
  * 1 Socket
  * 1 CPU
  * Leave architecture on "default"
 * Memory:
  * Ballooning active
  * Size: 2048
 * Network:
  * Choose your standard settings for testing machines

After creation, add an Cloud-Init Drive at ide0 on the same target as the
usual Disk
Add a second Disk at 5G to your machine at scsi1 with the same settings as
the other Disk

Go to your local console and create a new directory and add the main.tf:
terraform {
  required_providers {
    proxmox = {
      source  = "telmate/proxmox"
      version = "2.9.14"
    }
  }
}

provider "proxmox" {
  pm_api_url      = "https://#IP:8006/api2/json"
  pm_tls_insecure = true
  pm_user         = "#USER@pve"
  pm_password     = "#PASS"
}

And now - Import!:
terraform init

echo 'resource "proxmox_vm_qemu" "TF-RESET-TEST" {
  # (resource arguments)
}' > TF-RESET-TEST.tf

terraform import proxmox_vm_qemu.TF-RESET-TEST #NODE-NAME/qemu/3500

terraform state show -no-color proxmox_vm_qemu.TF-RESET-TEST > TF-RESET-TEST.tf

first of all, remove the entries, that are only information sources and can't be
set:
sed '/storage_type/d' -i TF-RESET-TEST.tf
sed '/unused_disk/d' -i TF-RESET-TEST.tf
sed '/reboot_required/d' -i TF-RESET-TEST.tf
sed '/id/d' -i TF-RESET-TEST.tf
terraform fmt

Check if all disks are there... They most likely wont...
This ist some other funny behavour already discussed in topics like

https://github.com/Telmate/terraform-provider-proxmox/issues/700
https://github.com/Telmate/terraform-provider-proxmox/issues/503
https://github.com/Telmate/terraform-provider-proxmox/issues/132

It seems that only the disk in slot 0 is having a troubles being recognized.
The disk in slot1 has no issues whatsoever:
resource "proxmox_vm_qemu" "TF-RESET-TEST" {
  agent                  = 0
  balloon                = 0
  bios                   = "seabios"
  boot                   = "order=scsi0;ide2;net0"
  cores                  = 1
  cpu                    = "host"
  define_connection_info = false
  force_create           = false
  full_clone             = false
  hotplug                = "network,disk,usb"
  id                     = "#NODE/qemu/3500"
  kvm                    = true
  memory                 = 2048
  name                   = "TF-RESET-TEST"
  numa                   = false
  onboot                 = true
  oncreate               = false
  qemu_os                = "other"
  reboot_required        = false
  scsihw                 = "virtio-scsi-single"
  sockets                = 1
  tablet                 = true
  target_node            = #NODE
  unused_disk            = []
  vcpus                  = 0

  disk {
    backup             = true
    cache              = "none"
    file               = "vm-3500-disk-1"
    format             = "raw"
    iops               = 0
    iops_max           = 0
    iops_max_length    = 0
    iops_rd            = 0
    iops_rd_max        = 0
    iops_rd_max_length = 0
    iops_wr            = 0
    iops_wr_max        = 0
    iops_wr_max_length = 0
    iothread           = 1
    mbps               = 0
    mbps_rd            = 0
    mbps_rd_max        = 0
    mbps_wr            = 0
    mbps_wr_max        = 0
    replicate          = 0
    size               = "5G"
    slot               = 1
    ssd                = 0
    storage            = "medium0"
    type               = "scsi"
    volume             = "medium0:vm-3500-disk-1"
  }

  network {
    bridge    = "vmbr0"
    firewall  = true
    link_down = false
    macaddr   = "3E:27:EC:30:03:EF"
    model     = "virtio"
    mtu       = 0
    queues    = 0
    rate      = 0
    tag       = 1327
  }
}

When you see both drives, you encountered an nondeterministic behavior. You can
still reproduce the error, if you try to terraform plan and therefore
refresh your state. At some point you will encounter this error or the other way
round, you will reach a state, where both drives are recognized correctly.
One of the issues lead me to think, that the proxmox provider is having issues
recognizing that slot number can be equal on different drive controllers.
Since cloud-init defaults to ide0 and the first drive is on scsi0 it may
think, that one slot has 2 drives and therefore can't manage the state for
that.
To validate the issue, delete the local state:
terraform state rm proxmox_vm_qemu.TF-RESET-TEST

Now detach the drive in scsi0 and re-add it in as scsi2. Also, detach the
CD-Drive (since it is in ide2).
Now re-import and re-fix your Terraform File:
terraform import proxmox_vm_qemu.TF-RESET-TEST #NODE/qemu/3500
terraform state show -no-color proxmox_vm_qemu.TF-RESET-TEST > TF-RESET-TEST.tf
sed '/storage_type/d' -i TF-RESET-TEST.tf
sed '/unused_disk/d' -i TF-RESET-TEST.tf
sed '/reboot_required/d' -i TF-RESET-TEST.tf
sed '/id/d' -i TF-RESET-TEST.tf
terraform fmt

And you will see both devices recognized correctly and at any given point with every plan and refresh.
This nondeterministic behavior can cause serious issues with discs getting deleted by accident or resetting orders of discs and other troubles.
I have worked around this issue by deleting the disk-section of every machine and adding a lifecycle_ignore-section:
lifecycle {
  ignore_changes = [
    disk
  ]
}

This has been tested with Terraform 1.4.4 and Proxmox Version 7.3.

After some further testing, it turn out, that using 2 different controllers (i.E. ide and scsi) for disks will result in the same nondeterministic behavior, no matter if you import a machine or you create it via terraform itself. Changing something in the disks, after you created the initial machine will always result in failure.
If you change the controller of the drive from scsi to ide however, will fix all issues. So the initial statemant stays true, but there is a workaround by using only ide as disk controller.

We are having similar issue when cloning from the template which has ide0 cloud-init drive and scsi0 HDD drive.
Cloning from this template randomly creates "good" and "bad" VMs. It seems like there is a race condition in the provider's parallel API calls.
template image
# qm config 8000
...
ide0: ceph:vm-8000-cloudinit,media=cdrom
...
scsi0: ceph:base-8000-disk-0,size=5324M
...

Good working VM (same slot number and different VM disk names)
# qm config 261
...
ide0: ceph:vm-261-cloudinit,media=cdrom,size=4M
...
scsi0: ceph:vm-261-disk-0,size=10G
...

Bad not working VM (same slot number and same VM disk names). This VM won't boot.
# qm config 261
...
ide0: ceph:vm-261-cloudinit,media=cdrom,size=4M
...
scsi0: ceph:vm-261-cloudinit,size=10G
...

The template image is build using Packer. There is no option to set up the slot for the cloud-init drive which could solve the problem.
Another solution would be to use the Terraform parameters
proxmox_vm_qemu > disk > file
or
proxmox_vm_qemu > disk > slot
neither of them works, they seem to be ignored.
Finally we found a temporary fix by deleting the ide0 disk and created a new one on ide2 by
qm set 8000 --delete ide0
qm set 8000 --ide2 ceph:cloudinit

cloning from such template works flawlessly.

not stale

Do you have a workaround for this @jsaalfeld ?
I started these days with terraform and proxmox at home and came into this issue here too.
Thanks. :)

I ignore disks for now, unfortunately. Didn't find anything else

not stale


Enable running one test on each binding

Goal
Simplify maintenance by running one test multiple times, exposing each binding at a time.
Motivation
At the moment, each test is run once. A test can specify with which binding it is to get run. But as Qt.py is meant to enable the same code to run, regardless of binding, it would also be helpful to enable running a test with each binding.

This is done!
To run a single test on each binding
This is default, and a tests are written as a plain-old-function.
def test_me():
  print("Running 4 times, now on: %s" % os.getenv("QT_PREFERRED_BINDING"))

Run a single test on a single binding
Use a conditional to "mask off" a test from other bindings. The test will be invisible for when the time comes to run tests under a binding you didn't specify.
if binding("PyQt4"):
  def test_me():
    print("Running exclusively on %s" % os.getenv("QT_PREFERRED_BINDING"))

Example


Add RepVGG TensorFlow implementation

The re-parameterization files are left, working on them currently.

Use present-tense, imperative-style for writing commit messages: "Add initial files..." from the next time.
Code quality is proper.
Add images of results / train loss graphs etc. later on in the documentation, when done.
Explain the purpose of the functions that you have created using comments, for better understanding.

The code for Re-parameterization doesn't work properly, especially when layers with Identity shortcuts are involved.

The code for Re-parameterization doesn't work properly, especially when layers with Identity shortcuts are involved.

Fix it, compare metrics before and after reparam in Readme


Binding parameterised circuit a second time remembers previous bound values

Information

Qiskit Terra version: 0.12.0
Python version: 3.7.7
Operating system: macOS Mojave 10.14.6

What is the current behavior?
Suppose we have a circuit made up of two sub-circuits, one of which contains parameterised gates. To be efficient, we want to reuse this general circuit many times with differently bound parameters. The first time, there are no problems. The second time, the new parameter is bound at the higher level (i.e. sub_circuit1 + sub_circuit2) but when the circuit is run it executes the old parameter from the first time. This can be seen at transpilation as shown below.
Steps to reproduce the problem
from qiskit import QuantumCircuit, transpile, QuantumRegister
from qiskit.circuit import Parameter

num_qubits = 2
qr = QuantumRegister(num_qubits)
first_qc = QuantumCircuit(num_qubits)

second_qc = QuantumCircuit(num_qubits)

for i in range(num_qubits):
    param = Parameter("theta{}".format(str(i)))
    first_qc.rx(param, i)

full_qc = QuantumCircuit(qr)

full_qc.append(first_qc, qr)
full_qc.append(second_qc, qr)

binding_dict_1 = {}
binding_dict_2 = {}
for param in full_qc.parameters:
    binding_dict_1[param] = 1
    binding_dict_2[param] = 2

run_1_qc = full_qc.bind_parameters(binding_dict_1)

# This print shows correct binding at high level
print(run_1_qc)

# This print shows correct binding at lower level
print(transpile(run_1_qc, optimization_level=0, basis_gates=['cx', 'u1', 'u2', 'u3']))

run_2_qc = full_qc.bind_parameters(binding_dict_2)

# This print shows correct binding at high level
print(run_2_qc)

# This print shows INCORRECT binding at lower level
print(transpile(run_2_qc, optimization_level=0, basis_gates=['cx', 'u1', 'u2', 'u3']))

What is the expected behavior?
Every time you bind a parameterised circuit it should have no memory of previous bindings. This is because quantumcircuit.bind_parameters() makes a deepcopy of the original circuit so there should be no memory left.
Suggested solutions
Currently we fix this by transpiling the parameterised circuit before binding. However, we believe this shouldn't be required to get the expected behaviour.
from qiskit import QuantumCircuit, transpile, QuantumRegister
from qiskit.circuit import Parameter

num_qubits = 2
qr = QuantumRegister(num_qubits)
first_qc = QuantumCircuit(num_qubits)

second_qc = QuantumCircuit(num_qubits)

for i in range(num_qubits):
    param = Parameter("theta{}".format(str(i)))
    first_qc.rx(param, i)

full_qc = QuantumCircuit(qr)

full_qc.append(first_qc, qr)
full_qc.append(second_qc, qr)

binding_dict_1 = {}
binding_dict_2 = {}
for param in full_qc.parameters:
    binding_dict_1[param] = 1
    binding_dict_2[param] = 2

run_1_qc = transpile(full_qc, optimization_level=0, basis_gates=['cx', 'u1', 'u2', 'u3']).bind_parameters(binding_dict_1)

print(run_1_qc)
print(transpile(run_1_qc, optimization_level=0, basis_gates=['cx', 'u1', 'u2', 'u3']))

run_2_qc = transpile(full_qc, optimization_level=0, basis_gates=['cx', 'u1', 'u2', 'u3']).bind_parameters(binding_dict_2)

print(run_2_qc)
print(transpile(run_2_qc, optimization_level=0, basis_gates=['cx', 'u1', 'u2', 'u3']))

Hi @bjader, thanks for reporting this! This is indeed a bug, and you rightly identified that the deepcopy we preform during bind_parameters was missing some state, resulting in errors on subsequent bindings. Transpiling prior to binding is one workaround, but there is an additional fix for this issue on the master branch (by I think a combination of #3729 and #3874) which will be included in the upcoming release.
Running your first example from master, I get
         ┌────────────────┐┌───────────┐
q0_0: |0>┤0               ├┤0          ├
         │  Circuit0(1,1) ││  Circuit1 │
q0_1: |0>┤1               ├┤1          ├
         └────────────────┘└───────────┘
         ┌──────────────────┐
q0_0: |0>┤ U3(1,-pi/2,pi/2) ├
         ├──────────────────┤
q0_1: |0>┤ U3(1,-pi/2,pi/2) ├
         └──────────────────┘
         ┌────────────────┐┌───────────┐
q0_0: |0>┤0               ├┤0          ├
         │  Circuit0(2,2) ││  Circuit1 │
q0_1: |0>┤1               ├┤1          ├
         └────────────────┘└───────────┘
         ┌──────────────────┐
q0_0: |0>┤ U3(2,-pi/2,pi/2) ├
         ├──────────────────┤
q0_1: |0>┤ U3(2,-pi/2,pi/2) ├
         └──────────────────┘

I'm going to close this issue as fixed on master, but feel free to comment or reopen if there are any questions.


jQuery "bind" should be "on"

Presumably this is familiar to you but for completeness:

As of jQuery 1.7, the .on() method is the preferred method for attaching event handlers to a document. For earlier versions, the .bind() method is used for attaching an event handler directly to elements.

http://api.jquery.com/bind/

I don't want this minor update to break backwards compatibility with previous versions of jQuery.  There a lot of people stuck on legacy jQuery due to being on older frameworks that consume updated versions of this plugin through their framework plugin managers.  I'd prefer to use on, but in versions of jQuery that have on it's the same thing as bind (bind doesn't have it's own logic any more, it just passes it's arguments to on).

Fair enough. Could come in a major version update though. I guess it's
just worth noting.
Thanks for the response.
On Thu, 14 May, 2015 at 9:02 , Jack Moore<EMAIL_ADDRESS>wrote:

Closed #720.
—
Reply to this email directly or view it on GitHub.

Thank you.


MINOR: fixed memory pollution by removing unnecessary creation of HashSet in KafkaConsumer

MINOR: fixed memory pollution by removing unnecessary creation of HashSet (assignment and subscription functions), changed modifiable to non-modifiable state while committing offsets (commitSync and commitAsync functions).
All changes made in in KafkaConsumer.

Making a copy is important as we can run into deadlocks if the user synchronizes on the received map.  Someone actually reported one such issue.

Closing this one because of reasons @ijuma gave us. If someone will find it useful please reopen it again. Thanks


Add typescript >= 4.6.3 as an optional peer dependency for each package in the monorepo

We expect that consumers that are using a package in this repo are using TypeScript >= 4.6.3, which supports the import { type X } syntax. See: https://github.com/MetaMask/metamask-extension/pull/19659#discussion_r1272209469

Closing as all core packages are using >4.6.3 for typescript.


UL and LI

This is simple: on the web it should render to a native UL / LI, whereas on Native we need to make that look very similar.

I'd like to work on this

Seems like potentially there is overlap with ListItems.
Could you reuse https://tamagui.dev/docs/components/list-item/1.0.0 and add some new style props perhaps?
i.e.
listStyle : 'ordered' | 'unordered' | 'styled'
Maybe a bad idea, just throwing it out there.

@mphill it's not a bad idea...

When using the ListItem component, I am currently getting the recommendation from Lighthouse:

List items () are not contained within ,  or  parent elements.

It would be helpful if Tamagui supplied a declarative way to wrap ListItems in list elements in cross-platform code.


What about shadows?

Current implementation doesn't support shadows yet.

@Rainer-Lang - Shadows are added in version 1.2.1.

Thank you so much


possible to support https://github.com/bytedance/terarkdb

pls support this as storage backend
https://github.com/bytedance/terarkdb

No, it will not be supported.
First, it is a RocksDB based KV store, storing Raft logs in KV stores is always wasteful. We have a much better storage engine for the logs, it is available at -
https://github.com/lni/dragonboat/tree/master/internal/tan
This engine, called tan, doesn't force you to have keys, why would you need to touch or construct trillions of keys when the leader just want to stream continuous entries to followers. It doesn't do compactions, as the log entries in raft are mostly append only. You also avoid some write amplification when you stop writing logs twice - you don't need to log your log. Its memtable is another redundant component when we already have an in memory log storage inside the raft implementation - inserting into that skiplist based memtable eats a huge chunk of your CPU cycles when you have millions of entries per second.
I'd be willing to be bet that tan is at least 20-30% faster than your suggested library when used for storing raft logs.
Secondly, that suggested library is C++ based.

Think @kolinfluence you should add it.


Provisioner test refactor (related to #1986)

toil.test.provisioners.awsProvisionerTest should be refactored so that a single test suite can be used interchangeably with different provisioners.
I also think toil.test.utils.utilsTest should be refactored so that it runs for each provisioner, but that work hasn't been approved yet. (I haven't begun work on the latter, pending approval.)

Duplicate of #1986.


error to train VOC2007

Pulled latest codes, saw following error during training (ubuntu 16.04/keras2.0.8/tensorflow 1.2):
"File "/home/ai/krn/keras_retinanet/preprocessing/pascal_voc.py", line 149, in load_image
regression_targets         = np.append(regression_targets, np.expand_dims(labels, axis=1), axis=1)
File "/home/dsu/tf/local/lib/python2.7/site-packages/numpy/lib/function_base.py", line 5152, in append
return concatenate((arr, values), axis=axis)
ValueError: all the input arrays must have same number of dimensions".
Earlier, saw error: "
File "/home/ai/krn/keras_retinanet/preprocessing/pascal_voc.py", line 148, in load_image
labels, regression_targets = anchor_targets(image, boxes_batch[0])
TypeError: anchor_targets() takes at least 3 arguments (2 given)", which was resolved by adding 3rd-parameter len(self.classes).

Thanks for reporting this issue! Seems Pascal training wasn't kept up to date. Should be fixed by commit https://github.com/delftrobotics/keras-retinanet/commit/d52ee112b4a14c6447b8b2293086bc71d18836d7 .

need to fix next 2 lines as well (simply copy from coco.py, the issues will go away.)

Thanks, I'll make those changes.


liberror.h is not thread-safe

Got bit by this while flashing two devices in parallel, with main culprit being the set_last_err_string() function. Caused various heap corruptions at the end of flashing process.
I resolved this by protecting the uuu_get_last_err_string() and set_last_err_string() functions with mutex.

Do you have pull request?

For a good measure i've also wrapped g_last_err_id in std::atomic

Pull request merged


feat: Introduce SSR context

Sometimes you need a function defined only in server context – i.e. to log errors inside of SSR. This PR allows one to define context in RequestEvent as follows:
hooks.server.ts
const handle: Handle = async ({ event, resolve }) => {
  const logger = new Logger();
  event.context = new Map();
  event.context.set('logger', logger);
  return await resolve(event);
});

some +page.svelte
import { browser } from '$app/environment';
const logger = browser ? new ClientLogger() : getContext('logger');
logger.info('yes');

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[ ] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. Changesets that add features should be minor and those that fix bugs should be patch. Please prefix changeset messages with feat:, fix:, or chore:.

const logger = browser ? new ClientLogger() : getContext('logger');

I feel like there's not enough context here to understand this PR and there should probably be an associated issue. Why can you do new ClientLogger() but can't do new ServerLogger()?

@benmccann in case of very simple logging requirements, yes, maybe one can do that. But the moment you will need to transfer such logs to i.e. Sentry, with request context, timings, etc., you will question yourself: why can't you just pass already initialized logger from server side?
Expanding on the example you would have something like this:
hooks.server.ts
const initLogger = async ({ event, resolve }) => {
  event.locals.logger = new QuiteComplicatedServerLogger({ endpoint, format, ... });
  return await resolve(event);
};

const quiteComplicatedThingWhichRequiresLoggerA = async ({ event, resolve }) => {
  try { await explode(); } catch (cause) { event.locals.logger(new Error('Unexpected explosion', { cause })); }
  return await resolve(event);
};
const quiteComplicatedThingWhichRequiresLoggerB = ...;
const quiteComplicatedThingWhichRequiresLoggerC = ...;

const handle: Handle = sequence(
  initLogger,
  quiteComplicatedThingWhichRequiresLoggerA,
  quiteComplicatedThingWhichRequiresLoggerB,
  quiteComplicatedThingWhichRequiresLoggerC,
  async ({ event, resolve }) => {
    event.context = new Map();
    event.context.set('logger', event.locals.logger);
    return await resolve(event);
  }
);

Otherwise one would have to pass all options of QuiteComplicatedServerLogger to svelte code.
So as Svelte has Server-side component API which allows passing context it seemed to us as the most logical choice. If there are other ways to pass functions and/or objects with associated methods into client code during SSR, I'm would gladly learn that.

Coming back to this I still don't know how I feel about this. It's a interesting idea/solution, but it only gets you halfway to where you want - you'd still need to make sure the you setup everything correctly in the caller site. Wondering if there's more that should be added to make this a more complete feature, or if this is a nice low-level building block.


[Popover/Menu] Trying to get a ref to the paper element breaks Popover/Menu

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
If you try to get a ref to the Paper element in Menu using <Menu PaperProps={{ ref: paperRef }}> it will break the menu (same for Popover which Menu is based on) and positioning will no longer work.
Expected Behavior 🤔
It should be possible to get a ref to the Paper element without breaking the Menu/Popover
Steps to Reproduce 🕹
https://codesandbox.io/s/stupefied-frog-pkrbo?file=/src/Demo.tsx

Use  <Menu PaperProps={{ ref: paperRef }}>

Context 🔦
I am trying to virtualize a menu with a headless virtual list library (react-virtual). I need a ref to the paper element (which is Menu's scroll container) so the virtualization library can do its work.
This doesn't seem too complex to fix. Popover just assigns its ref and lets PaperProps override it. Instead Popover needs to do the same thing as the className right after it. Use a fork ref for PaperProps.ref and paperRef and pass that to ref after {...PaperProps}.
https://github.com/mui-org/material-ui/blob/8fc684f67393eee40776bd66a71eaccae12b7ef8/packages/material-ui/src/Popover/Popover.js#L370-L374
Your Environment 🌎

`npx @material-ui/envinfo`
  System:
    OS: Linux 5.4 Ubuntu 20.10 (Groovy Gorilla)
  Binaries:
    Node: 16.2.0 - ~/.nvm/versions/node/v16.2.0/bin/node
    Yarn: 1.22.5 - /mnt/c/Program Files (x86)/Yarn/bin/yarn
    npm: 7.13.0 - ~/.nvm/versions/node/v16.2.0/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    @emotion/styled:  10.0.27
    @material-ui/core: ^4.11.2 => 4.11.2
    @material-ui/icons: ^4.11.2 => 4.11.2
    @material-ui/lab: ^4.0.0-alpha.57 => 4.0.0-alpha.57
    @material-ui/pickers: ^3.2.10 => 3.2.10
    @material-ui/styles:  4.11.2
    @material-ui/system:  4.11.2
    @material-ui/types:  5.1.0
    @material-ui/utils:  4.11.2
    @types/react: ^17.0.0 => 17.0.0
    react: ^17.0.1 => 17.0.1
    react-dom: ^17.0.1 => 17.0.1
    styled-components:  5.2.1
    typescript: ^4.1.2 => 4.1.2

Thanks for the report.
We have a built-in utility called useForkRef which should be able to resolve this issue.


fix(stream/materialize): enforce update_cache when modify fixed_changes

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?

Checklist

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

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

Documentation

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

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

Is there a test that can cover this?

#14166 can pass so the consistency is not broken.
The PR just fix a location that update_cache is updated while fixed_changes is not updated, which introduced a meaningless operation. I guess it's hard to test that.


Using d3-force and d3-quadtree with create-react-app

CRM strictly requires ES5 modules while d3-force and d3-quadtree are known to have ES6 code. Any suggestions on using these modules with CRM?
Thanks!
Parul

Sorry, I’m not familiar with create-react-app’s requirements.


Fixed AVR include

Without this fix compilation failed for non-AVR MCUs.

Thanks for your input. The purpose of the #else is to include the avr/dtostrf.h for non-AVR MCUs. I've tested it with ESP8266/ESP32 but it seems from your suggested fix it is causing a problem with other(?) MCU(s).
Could you let me know what MCU and version of IDE you are complaining it for so I can try to replicate your issue?
Thanks


first pass of corrections for golangci-lint

Signed-off-by: baude<EMAIL_ADDRESS>

/hold
/lgtm

/lgtm

/hold cancel


Support alternative Travis factors

Add support for os, language, and python Travis factors, as well as for environment factors as well.
This includes, supercedes, and ultimately fixes #34. Fixes #4, Fixes #25, and references #19.

@rpkilby , @jayvdb : If you have the time, would you mind doing a review? This is probably the biggest new feature to tox-travis ever. Thanks @rpkilby for doing the most difficult initial work on this patch.

@ryanhiebert, I have some time this afternoon - will look at it as soon as I get the chance.

I did the unthinkable and reverted this by force pushing, and re-merged it as two squashed commits. One with @rpkilby 's work, and another with mine, so that it's clear in the git history that @rpkilby played a big part in getting this done.


Write index.yaml file atomically

This refactors the already-existing AtomicWriteFile utility
to a central location and uses it to write index files
atomically.
This is done to avoid having half-written index files break
client requests.
Drive-bys:

Add test for AtomicWriteFile.
Add test IndexFile.WriteFile.

Is there an issue or existing proposal attached to this?

@technosophos Thanks for looking at this! No, I didn't file an issue because I thought the problem was fairly transparent: it's the usual problem when clients access a half-written file and break. I'm happy to file an issue if that helps. Please let me know if you need me to do this or if this PR and its description is enough.

Yeah -- please file an issue and link to it. We're trying to get a little better at our bookkeeping.

@technosophos Sure; that's done now (see #7954).

You may also want to remove atomicWriteFile in favour of this package, which was introduced in #7720.

I believe it was #7988 that this was supposed to correct, so I am taking the liberty of updating the original issue post, and then I am merging this for 3.3.0

Based on #7987, I have marked this for inclusion on 3.2.1 instead of 3.3.0, as it is a bug fix by that definition.


signed_in? returns false

Hi, signed_in? keeps returning false always. Is this because of lack of updates to the gem or something? Thanks @karmi :)

Hi @steverob, yes, that might well be, I don't even remember the repository :) I'd like to help you, but it's really ancient, I think you'll have to dig yourself...

Haha :) thanks @karmi. I was thinking the same thing and I'm gonna update this for the latest clearance :)
--
Regards
Steve Robinson

On Jul 12, 2016, at 9:43 PM, Karel Minarik<EMAIL_ADDRESS>wrote:
Hi @steverob, yes, that might well be, I don't even remember the repository :) I'd like to help you, but it's really ancient, I think you'll have to dig yourself...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@karmi so weird -

This gives 401 even if env[:clearance].signed_in? returns true.
@jgarth I am working on your fork only - #1 :) Do share your thoughts.
Thanks!!

Hey @steverob, sorry to disappoint but I haven't used clearance (and clearance_http_auth) in four years… no idea why it's not working anymore. Good luck :)

Haha :) sure sure. Just curious, you guys still using rails or moved on?
--
Regards
Steve Robinson

On Jul 13, 2016, at 9:05 PM, Joachim Garth<EMAIL_ADDRESS>wrote:
Hey @steverob, sorry to disappoint but I haven't used clearance (and clearance_http_auth) in four years… no idea why it's not working anymore. Good luck :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@steverob Still using Rails for sure! :)

Awesome @karmi :)
--
Regards
Steve Robinson

On Jul 13, 2016, at 10:25 PM, Karel Minarik<EMAIL_ADDRESS>wrote:
@steverob Still using Rails for sure! :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


branch name in conda env in jenkinsfile

Title: Summary, imperative, start upper case, don't end with a period

Description

Category:
JIRA issue: MIC-XYZ
Research reference:

Changes and notes

Verification and Testing

removed


Many stored 'Query and Filter' returning errors

Typically the error is:

1054 (42S22): Unknown column 'objects.latestrmag' in 'field list'

For example: https://lasair-iris.roe.ac.uk/query/202/

That query was copied from the old Lasair, which has a different schema. The attribute is now called 'rmag'. Correct schema document is here https://lasair-iris.roe.ac.uk/schema

Are these queries stored in the database? If so, can you point me to where and I will fix all those queries that are broken?

Dave -- All the queries should now run cleanly, can you check please?
Log in to lasair-iris, and go to https://lasair-iris.roe.ac.uk/querylist/my/, then click each and click the button "Run this query".

Super!!!


Add about section or tutorial mode

Maybe put some info on the "Game" tab, or add "tutorial" mode (see ionic-stencil-conference-app)

Added blanket message on Create Hero screen and "Game" tab of Play Screen. In 1.1, adjust these messages based on client - mobile safari can use window.navigator.standalone to detect if in Home Screen mode; android looks like it has it's own setup.


Add ChanUpgradeOpen core handler.

Description

closes: #3745
Commit Message / Changelog Entry
feat: Add ChanUpgradeOpen core handler

see the guidelines for commit messages. (view raw markdown for examples)

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[ ] Targeted PR against correct branch (see CONTRIBUTING.md).
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the module structure standards and Go style guide.
[ ] Wrote unit and integration tests.
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/).
[ ] Added relevant godoc comments.
[ ] Provide a commit message to be used for the changelog entry in the PR description for review.
[ ] Re-reviewed Files changed in the Github PR explorer.
[ ] Review Codecov Report in the comment section below once CI passes.

tests pending on merging of ack.

Opening this up for review, mainly have Qs on the test structuring.

rebased/force pushed as a force of habit, sorry for the mucked review process.


Tooltip autohide prop

Adds autohide prop to tooltip. When autohide is false, hovering over tooltip content will not close the tooltip.
example use case: UI needs to allow users a chance to copy content from tooltip content.

Thought this already existed when I commented over here.


Create 0000-01-02-Nuwandhi.md

created a branch, created a file and made a commit, and opened a pull
request

Name changed


client http_socket improvements and testing

This pull request makes improvements upon the work done in https://github.com/sensu/sensu/pull/1488 and adds much needed tests.

Waiting on https://github.com/sensu/sensu-settings/pull/54

Going to pick this back up in the AM :+1:

Ready for review :+1:


Tables not getting created in version 1.4 when instant run is enabled

So, I am using v1.4 of the SugarORM and tables are not getting even after re-install of the app.
I had to disable the instant run to create tables. Has this been addressed?

This is the Nth issue about this. I had the same trouble.
It's been fixed, but you need to use the master branch, 'cause this will be the same in 1.5.
@satyan maybe it's time for a patch release 1.5.1 ?

+1


Example project is broken

running these on the included map makes the example work, should the extra files be included so example runs without needing to do this?

The example is without the necessary files just to demonstrate how the process works, i.e. it's an opportunity to run the conversion yourself on the example.
Probably, this is not the best idea and it's necessary to include final files 🧐

Maybe just some text higher up in the readme to explain they need to run the editor extension on the specific files before being able to run the example is needed?

Running the Example
To run the example project, you first need to run two editor extension functions on a map file provided. With the project open in Defold, right click on the level.map file then click on Prepare Map Components Folder. This will create a variety of files next to the .map file. Next right click on the .map file and click Convert Map to Collection. You can now run the example.

Sounds great, I think I can rewrite some paragraphs with these statements.

Finally updated the manual. Thanks for the text.


'[Not] available for hire' message as optional.

It would be nice if this message was optional to be displayed.

Agreed. It seems odd.

It looks like this is part of the theme. User-defined themes (Issue #33) would solve this.


[Redesign] Create Landing page UI component and template

Overview
https://github.com/wayfair/awesome-learning/wiki/Awesome-Learning-2020-Redesign
Details
We need to create a UI component and template for our new landing page.
https://www.figma.com/file/Q2AvwPeBaAZWhnP9fYNBiW/Awesome-Learning-Redesign?node-id=18%3A0
Engineering Criteria

#180 is dependent on this ticket. The GraphQL query in this file should be written here, then passed into the Featured Course component.
This ticket is responsible for updating our existing template and UI component for the redesign. You don't need to add anything new yet.
Rename index-template.js to landing-template.js, so that the name of the template corresponds with the name of the UI component. Make sure that existing references to the old template name are changed to the new template name.
Remove the existing content in Landing.js. This will eventually be replaced with other Landing page components that will be engineered and integrated separately.

I can work on this.

@chynh You got it, thanks!

Closed by #194 , thank you for picking this up again @chynh !


update changelog & release procedure

Hey @martindurant - what are your plans for a release?
Here is a little helping hand - but please don't feel too rushed if you have some other business to finish.

This is a fine change

@martindurant Do you think you can issue a release so this change can be used with installations of s3fs done from pypi ? (the changelog was updated, but the release wasn't issued)


implementing query parameter encoder/decoders (LocalDate, ZonedDate)

Was looking through some issues when I found this conversation in #2670:

@LukaJCB - #2724 added support for Instant. What other types would you find useful - ZonedDateTime and LocalDate?

In this PR, I added support for LocalDate. I have something in my fork for ZonedDateTime, but maybe that'll come later since I'm having trouble testing it correctly.
I hope this is a useful contribution!

Looks like there are dependency/compilation issues for adding ZonedDateTime, fails for anything below Scala 2.13 and anything other than JDK 1.8, maybe we can exclude this decoder/encoder for now?

Sorry, I started reviewing this, and I don't know where it ended up.
We have an import org.http4s.internal.CollectionCompat.CollectionConverters._.  If you need to bridge the gap between the collections API in other ways, they can be added to CollectionCompat in the two source directories, but I think that will fix the remaining issue.
Otherwise, looks good!

It also looks binary compatible, so we can cherry-pick this back to 0.21.

Thanks for the feedback, I'll work on this over my boring weekend 😉

Looks like a Flakier than it's worth on CI test failed on the latest run. Other than that, looks like the tests related for my change passed.


Unable to run the GDMP Demo Project in godot 4.2.2.stable

Hi,
I am new to Godot and i am trying to run the GDMP Demo project. I have added the addons folder (v0.4) in the root folder, and enabled the GDMP plugin but i am facing the errors as shown below.
        I am unsure why the MediaPipeFaceDetector and relevants Mediapipe dependencies is not resolving.

Operating System: Ubuntu 22.04
Thanks

Hi, can you try running Godot editor in terminal, then open the demo project to see what the error output look like? Most likely it's due to missing library dependencies such as OpenCV.

Well, crashing the official editor isn't what I expected.
Can confirm that GDMP v0.4 that built from ubuntu 22.04 somehow doesn't work on the same release, tested from ubuntu 22.04 docker image running godot in headless mode, though the crash messages are a bit different:
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.2.2.stable.official (15073afe3856abd2aa1622492fe50026c7d63dc1)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
ERROR: FATAL: Index p_index = 1 is out of bounds (size() = 0).
   at: get (./core/templates/cowdata.h:158)
Illegal instruction (core dumped)

I think there's not much I can help with this problem unfortunately, but as a workaround you can try building the library from source in environment that are isolated from host, there is flatpak_env.sh script to help you switch to Freedesktop runtime if flatpak is installed on your machine.

GDMP will use Freedesktop SDK that are independent of specific distro version, as well as building OpenCV from source in the next v0.5 release. While using prebuilt v0.4 libraries on Ubuntu 22.04 crash Godot immediately, building from source with latest commit works as expected (with some Bazel defines for XNNPACK added since the compiler is a bit dated). I think this issue is no longer relevant so I'm closing this, please reopen if there are still problems building from source on Ubuntu 22.04.


Initial support for Cherokee as a demonstration implementation for a tone and cadence language

Initial support for Cherokee as a demonstration implementation for a tone and cadence language

I'm getting a 'RuntimeError: CUDA error: device-side assert triggered' that I can't figure out.
python run_training_pipeline.py --gpu_id 0 --finetune --resume_checkpoint Models/FastSpeech2_Meta/best.pt chr
Preparing
Prepared a FastSpeech dataset with 1352 datapoints in Corpora/chr-w.
Training model
100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████| 135/135 [00:18<00:00,  7.42it/s]
Traceback (most recent call last):
  File "run_training_pipeline.py", line 78, in <module>
    pipeline_dict[args.pipeline](gpu_id=args.gpu_id,
  File "/home/muksihs/git/IMS-Toucan/TrainingInterfaces/TrainingPipelines/FastSpeech2_Cherokee_West.py", line 45, in run
    train_loop(net=model,
  File "/home/muksihs/git/IMS-Toucan/TrainingInterfaces/Text_to_Spectrogram/FastSpeech2/fastspeech2_train_loop.py", line 195, in train_loop
    plot_progress_spec(net, device, save_dir=save_directory, step=step_counter, lang=lang, default_emb=default_embedding)
  File "/home/muksihs/miniconda3/envs/toucan_conda_venv/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 28, in decorate_context
    return func(*args, **kwargs)
  File "/home/muksihs/git/IMS-Toucan/TrainingInterfaces/Text_to_Spectrogram/FastSpeech2/fastspeech2_train_loop.py", line 48, in plot_progress_spec
    spec, durations, *_ = net.inference(text=phoneme_vector,
  File "/home/muksihs/git/IMS-Toucan/TrainingInterfaces/Text_to_Spectrogram/FastSpeech2/FastSpeech2.py", line 350, in inference
    before_outs, after_outs, d_outs, pitch_predictions, energy_predictions = self._forward(xs,
  File "/home/muksihs/git/IMS-Toucan/TrainingInterfaces/Text_to_Spectrogram/FastSpeech2/FastSpeech2.py", line 241, in _forward
    encoded_texts, _ = self.encoder(text_tensors, text_masks, utterance_embedding=utterance_embedding, lang_ids=lang_ids)  # (B, Tmax, adim)
  File "/home/muksihs/miniconda3/envs/toucan_conda_venv/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/muksihs/git/IMS-Toucan/Layers/Conformer.py", line 123, in forward
    xs, masks = self.encoders(xs, masks)
  File "/home/muksihs/miniconda3/envs/toucan_conda_venv/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/muksihs/git/IMS-Toucan/Layers/MultiSequential.py", line 18, in forward
    args = m(*args)
  File "/home/muksihs/miniconda3/envs/toucan_conda_venv/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/muksihs/git/IMS-Toucan/Layers/EncoderLayer.py", line 123, in forward
    x = residual + self.dropout(self.conv_module(x))
  File "/home/muksihs/miniconda3/envs/toucan_conda_venv/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/muksihs/git/IMS-Toucan/Layers/Convolution.py", line 53, in forward
    x = self.pointwise_conv2(x)
  File "/home/muksihs/miniconda3/envs/toucan_conda_venv/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1102, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/muksihs/miniconda3/envs/toucan_conda_venv/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 301, in forward
    return self._conv_forward(input, self.weight, self.bias)
  File "/home/muksihs/miniconda3/envs/toucan_conda_venv/lib/python3.8/site-packages/torch/nn/modules/conv.py", line 297, in _conv_forward
    return F.conv1d(input, weight, bias, self.stride,
RuntimeError: CUDA error: device-side assert triggered
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.

I'm not sure why it works at all and only crashes so late, you are using<PHONE_NUMBER>71 as the language ID for cherokee west and<PHONE_NUMBER>43 for cherokee east, but the language IDs only go up to 100. When you add a new language, the language ID should increase by 1 up to the maximum that you specify when you instantiate the model. For the provided multilingual checkpoint that was pretty randomly chosen to be 100.

There are several problems:

You add the tone and length characters to the inventory of the aligner, which will cause the aligner to fail. They should only be visible to the TTS, not to the aligner.
You use utf8 encodings of strings as the language IDs, which is not viable as the input to an embedding layer, since there need to be as many placeholder tensors as there are IDs.
You treat all tone and all length characters as silence when passing them to the TTS. The TTS only sees what's in the papercup feature vector and nothing else. This causes two problems: 1) They are treated as silences, which they are not, silence does not coincide with any of those markers. 2) There is no distinction between any of the markers, all of them look the exact same when they are passed to the TTS. The second problem cannot be fixed without adding new dimensions or values for existing dimensions to the feature vector, which breaks all compatibility to previous models.

I will make a branch with support for tone and length characters in the phoneme string. It will not be in the main branch however, because it breaks compatibility with the pretrained model. Once there is a pretrained model available that knows tone and length markers, it will become the main branch. Making this branch will take some time, the semester is about to start, so I have to spend 100% of my time on teaching right now.
I'll close this PR and recommend that you either wait for the "official" implementation if it's not urgent, or you continue experimenting in your fork.

OK, thanks for the explanations.
I was thinking when looking at the code and saw that the language id is a single tensor, I did not realize it was getting mapped into inputs based on tensor value.


Example 3 - Does not filter properly by date.

When running the following example, results up until current date are returned...
$Date = [DateTime]::Today.AddDays(-90)
Get-ADComputer -Filter 'PasswordLastSet -ge $Date' -Properties PasswordLastSet | FT Name,PasswordLastSet

However, enclosing the filter with "", changing the filter to PwdLastSet -LT, and converting the time to FileTime does work.
$Date = [DateTime]::Today.AddDays(-90)
Get-ADComputer -Filter "PwdLastSet -lt $($Date.ToFileTime())" -Properties PwdLastSet, PasswordLastSet

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 6b8337d2-8c17-df81-3184-128e17d9d163
Version Independent ID: fa6e2a23-2a2d-16f7-079b-e2f5bdd8d938
Content: Get-ADComputer (addsadministration)
Content Source: docset/windows/addsadministration/get-adcomputer.md
Product: w10
Technology: powershell-windows
GitHub Login: @andreabarr
Microsoft Alias: v-anbarr

This can be disregarded, I read the original example wrong. I was thinking it was meant to return objects older than 90 days. Simply flipping the -GE to -LE gave the opposite results.


wiki:

Related Issues

wiki: #69795 (closed)
wiki: #70476
- #68535 (closed)
- #18957 (closed)
- #64529 (closed)
- #70077 (closed)
.  #17781 (closed)
. #26423 (closed)
. #44665 (closed)
. #66738 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)


ubuntu gui scrollbar issue

0.1.3 is still not giving me the ability to scroll when built on Ubuntu 14.04.  When running as a server in firefox I can scroll just fine, which leads me to believe the issue is not with the htdocs.  Can any of the other linux builders confirm that the issue still exists?  Any ideas what would be causing this issue?  I have tried looking into it, and even if I force a scroll bar to show up it wont allow scrolling.  It seems my googlefu has been defeated.  I will keep looking into it, but it will take me a while to get my c++, and understandingof qt up to the point where I can be of assistance.

ok, I'll build a ubuntu version to take a look of this issue.
Is this a legacy issue ?


Feature/cards use grid

Removed some useless card styling and made the component more generic. Updated documentation to include use with our grid system.

Codecov Report

Merging #29 into develop will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff            @@
##           develop      #29   +/-   ##
========================================
  Coverage    94.29%   94.29%
========================================
  Files          124      124
  Lines         1963     1963
========================================
  Hits          1851     1851
  Misses         112      112

Impacted Files
Coverage Δ

src/App/Documentation/components/Card/index.js
100% <100%> (ø)
:arrow_up:

src/App/components/Card/index.js
75% <100%> (ø)
:arrow_up:

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 b0341a1...3dac571. Read the comment docs.

Well, the cards were quite wide, not to sure what to do though 🤔

Not quite sure what you're responding to here 🤔


Demo dashboard design

Description
Design a demo dashboard so that users can quickly

understand the value of Dev Lake
how to use Dev Lake if they want to use

Describe the solution you'd like

design a series of selected scenarios(in the form of questions similar to Gitprime), metrics and charts

make a set of Grafana dashboards

Reliance
It'll block #557
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Finished.


I'd like to be able to add my own log transports

I see that I have the ability to add a logger property to the config object passed in to the hypernova initializer. However, it looks like this only gives me the ability to override these defaults:
{
  level: 'info',
  colorize: true,
  timestamp: true,
  prettyPrint: process.env.NODE_ENV !== 'production',
}

What I'd really like to be able to do is pass in my own transports to Winston so I can hook in to my remote logging service. Any plans to add this feature?

We can probably add a transports key to the config object. PR's welcome.

Thanks!

@goatslacker so, did this happen already? I can't get any logging from my setup.

gave a try, feedback is welcome -> airbnb/hypernova#117

just saw a PR from a couple of months ago -> https://github.com/airbnb/hypernova/pull/104
so my PR might be obsolete https://github.com/airbnb/hypernova/pull/117

Fixed in https://www.npmjs.com/package/hypernova/v/2.2.6 .  Thanks everyone!


Respecting Original Contributions: An Appeal to Retain Git History

Dear Excelize,
I've noticed that your project incorporates code from the https://github.com/exceljs/exceljs library. However, the entire Git history has been removed, which subsequently erased information about the original authors of the project. I would like to emphasize the importance of recognizing and appreciating the efforts and contributions of those who have dedicated their time and energy to develop this library over the years.
Maintaining the project's history not only pays homage to its creators but also serves as a key to understanding the evolution of the code and the rationale behind various changes. It is invaluable information for other developers who might want to use or further develop your project.
With all due respect, I understand that each project might have its reasons for certain decisions. Nonetheless, I urge you to consider restoring this history or, at the very least, acknowledging the original authors in your documentation or on your project's main page. Collaboration and recognition within the open-source community play a pivotal role and help foster a healthy ecosystem for all its users.
Thank you for your attention, and I wish you success in your ongoing development endeavors.
Best regards,
Pawel Siemienik

@Siemienik
Thanks for the reminder, I didn't mean to create a new project, it's just that I didn't know how to do it at first, and thought I was going to have to create a new project to continue. I did state in the readme.md where this project originated from, and it says so in this screenshot below, so I'm not sure if that matches, or if I need to do something more?


Maven Repository

The maven repo from the sample app (https://maven.sumup.com/repositories) is returning a 503
Is this still the right path? If so, when can we expect a fix?

Looks to be resolved now

Yeah, just saw that. Onwards!


Feature: Dual Edge Support

TODO Before merging/shipping:
Check to make sure that after the analyzer is updated, the option is available immediately. The test user reported that they had to use the reset button before the new option was shown. Ticket 73321

Tim found a bug in the Logic2 App, we didn't show the new option without clicking reset.
We have a PR that fixes this (mostly, 1840)


Command "winget list" ignores "--source" option

Brief description of your issue
I want to list all packages installed with WinGet. According to the documentation, I can use the --source option. But at least on my machine WinGet ignores this option.
Steps to reproduce
Run the following command:
winget list --source winget

Expected behavior
Only list packages that have the source winget. WinGet should follow the info in winget list --help.
Actual behavior
WinGet lists all packages.

Environment
Windows Package Manager v1.1.13405
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19042.1415
Package: Microsoft.DesktopAppInstaller v1.16.13405.0

Nvm found https://github.com/microsoft/winget-cli/issues/1155

Duplicate of https://github.com/microsoft/winget-cli/issues/1819


fix: make llmq_test_instantsend great again

Issue being fixed or feature implemented
Running 3 nodes on RegTest as platform does uses do not let to create llmq_test_instantsend quorum:
1. switch to `llmq_test_instantsend`:
+        self.extra_args = [["-llmqtestinstantsenddip0024=llmq_test_instantsend"]] * 5

2. removed cycle-quorum related code:

-        self.move_to_next_cycle()
-        self.log.info("Cycle H height:" + str(self.nodes[0].getblockcount()))
-        self.move_to_next_cycle()
-        self.log.info("Cycle H+C height:" + str(self.nodes[0].getblockcount()))
-        self.move_to_next_cycle()
-        self.log.info("Cycle H+2C height:" + str(self.nodes[0].getblockcount()))
-
-        self.mine_cycle_quorum(llmq_type_name='llmq_test_dip0024', llmq_type=103)

3. added new quorum:

+        self.mine_quorum(llmq_type_name='llmq_test_instantsend', llmq_type=104)

and eventually it stucked, no quorum happens

2024-01-13T19:18:49.317000Z TestFramework (INFO): Expected quorum_0 at:984
2024-01-13T19:18:49.317000Z TestFramework (INFO): Expected quorum_0 hash:6788e18f0235a5c85f3d3c6233fe132a80e74a2912256db3ad876a8ebf026048
2024-01-13T19:18:49.317000Z TestFramework (INFO): quorumIndex 0: Waiting for phase 1 (init)
<frozen>

What was done?
Updated condition to enable "llmq_test_instantsend":

it is RegTest and DIP0024 is not active
it is RegTest, DIP0024 is active, and specified as llmqTypeDIP0024InstantSend

How Has This Been Tested?
Run unit and functional tests.
Beside that functional test feature_asset_locks.py now uses this quorum for instant send and that's an arrow that hit 2 birds: we have test for command line option -llmqtestinstantsenddip0024 and code of feature_asset_locks.py is simplified.
Breaking Changes
yes, that's a bugfix that fix quorum appearance llmq_test_instantsend on regtest.
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation
[x] I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

Label guix-build is set to get a docker image for platform

test message

Guix Automation has began to build this PR tagged as v20.1.0-devpr5832.8512c1cb. A new comment will be made when the image is pushed.

Guix Automation has began to build this PR tagged as v20.1.0-devpr5832.2c60a16d. A new comment will be made when the image is pushed.

Guix Automation has completed; a release should be present here: https://github.com/dashpay/dash-dev-branches/releases/tag/v20.1.0-devpr5832.2c60a16d. The image should be on dockerhub soon.

@markin-io confirm it works
@UdjinM6 @PastaPastaPasta please review to get it to nightly builds


Importing config vars from a .csv file

Hello, having had a look through the documentation (Import vars from separate files) and examples, it appears as though importing vars from external files is limited to yaml, txt, Python and Javascript files.
Are there any plans to allow import from a csv file, where each column header is a variable name, and each row is one single complete configuration?  We feel this would be particularly helpful when composing "scenarios" where you have complex setup config to apply to each test.

Hey @alexclaydon, is it possible this import from CSV functionality does what you want?
It works at the tests level rather than vars, but you can include it in your promptfoo config like this:
tests: my_tests.csv

And the CSV includes a bunch of vars mapped to columns.

Thanks Ian!
First of all, we're loving promptfoo and are going all in on it - thanks for all of your excellent work!
Having thought about this issue for a few days and discussed with a colleague, we realised that I should have framed it differently.  Please allow me to provide some additional context on the use-case to flesh out the issue as we see it.  It's always possible that we've misunderstood the paradigm.
We're making extensive use of "scenarios" in our setup, like so:
description: ...
providers: ...
prompts: file://prompt_templates.txt  # prompt template containing nunjucks tags for `topic` and `description`

scenarios:
  - config:
    - vars:
        topic: "Liabilities for Business Losses"
        description: file://case01.txt
    - vars:
        topic: "Liabilities for Data Losses"
        description: file://case02.txt
    - vars:
        topic: "Liabilities for Other Losses"
        description: file://case03.txt

    tests: './data.csv'  # contains 4 columns: `text` (str), `definitions` (str), `data_loss` (bool), `business_loss` (bool)

The crux of the issue for us is that, in scenarios, it doesn't seem to be possible to specify assertions to be applied (ceteris paribus) to each row under the config section - they must be in-lined row-by-row in the .csv data file instead.
Accordingly, if we want to check, for example, whether some output matches the value of one of the bool columns in our data spreadsheet, we need to go down each row and change the name of that column to __expected and its value from "TRUE" to (for example) "equals: TRUE".  Given that our data spreadsheets are often the main interface between technical and non-technical teams, that's quite tricky for us.
Ideally, we'd prefer to write a one-line "wrapper" assertion, leveraging vars set out in the .csv file (and elsewhere), and just drop it into the config section instead, where it would then be applied on a row by row basis.
I hope that all makes sense and would really appreciate any guidance you might be able to provide!

Just had an additional thought on your response above which might clear things up for us a bit.
  Does that imply that I can access column names / vars from within the config file in an assert immediately following tests: my_tests.csv, like so (or something similar)?
description: 'Extraction'

prompts: ['{{ clause }}']

providers:
  - id: 'python:../shims/extract.py'
    label: 'Extraction'
    config:
      evaluateOptions.maxConcurrency: 1
      evaluateOptions.showProgressBar: true

tests:
  - '../testdata/data.csv'
  - assert:
    - type: icontains-any
      value: '{{ entities }}'  # where the `.csv` file contains at least `clause` and `entities` columns

I've been trying to put that together today, and had a look through the examples directory, but wasn't able to find anything on-point.
If this kind of thing is possible, that would enable us to conveniently "wrap" asserts around row data as I described above - so a complete solution!

I think the right construction here is:
defaultTest:
  assert:
    - type: icontains-any
      value: '{{ entities }}'

tests: '../testdata/data.csv'

The defaultTest object will apply to all test cases, and should be able to pick up columns from your CSV.

Thank you Ian!
The confirmation that this is supposed to work is very helpful.  I had actually tried this approach, but without success.  I think I now know why: it appears to relate to the way arrays are handled.
Since this particular assert is icontains-any, I had set up my .yaml file exactly as you have it above. I then tried setting up the entities column in my .csv file a few different ways: (i) including / excluding square brackets ([]), (ii) including / excluding single and double quote marks around each string in the array, and (iii) trying both commas and semi-colons as delimiters.  All of those approaches failed with a message to the effect that this particular assert requires an array.
In addition, I tried enclosing the value of the value field in my .yaml file in square brackets, as follows:
defaultTest:
  assert:
    - type: icontains-any
      value: ['{{ entities }}']

tests: '../testdata/data.csv'

That seemed to resolve the above error about the assert requiring an array, but also resulted in the actual value of the entities column being returned as a single string (enclosed in an array), no matter what I tried.
Could you advise on the correct approach here?  Unless I missed it, there seems to be a bit of a gap in the documentation here.  I would be very happy to submit a documentation PR if we could get to the bottom of this and if that would be helpful?
Cheers

Ok, I see the problem!  I went through the whole troubleshooting and debugging process (e.g. using __expected, wrapping in brackets) all of which you already explained in great detail :)
I think the best way to fix this is add comma-delimited string support for icontains-any and similar assertion types.  That way you'll be able to do:
defaultTest:
  assert:
    - type: icontains-any
      value: {{ entities }}

tests: '../testdata/data.csv'

and you can include an entities column in your CSV, and it will work as intended.
#755 implements this (although it naively splits on any comma, and won't respect CSV-style quotes like "hello, world")

Perfect!  Thanks so much for this, really appreciate the attention.  That's the final piece of the puzzle for us on pushing Promptfoo to adoption across our whole team, incredibly helpful!

Sorry for the delay here @alexclaydon - it's merged and will be in the next release!

Not at all - we really appreciate you talking the time on this!

@typpo  thank you for this explanation, it helped me to be able to use csv files to test on large datasets.
It would be nice if it would be possible to display the values of "entities" in the UI instead of just: {{entites}}, look at the image below:


ChainId
3737
Chainlist
https://chainlist.org/chain/3737
Contract deployed

[X] I confirm that the contracts are deployed

Version of contracts deployed
v1.3.0
Relevant information
ChainID: 3737
RPC endpoint: https://rpc.crossbell.io
Block explorer: https://scan.crossbell.io/
PR: https://github.com/safe-global/safe-deployments/pull/205

https://github.com/safe-global/safe-deployments/pull/205


Add comment headers to each source file

Comment headers to each source file should be added. Most importantly, the authors of each file should be credited in each file. This will help especially as others contribute to the project.

I'd like to help with this.
I was thinking of what to include in the headers. I agree with author, and I suppose description is also required.
I also looked at syntastic as an example

"============================================================================
"File:        drafter.vim
"Description: Syntax checking plugin for syntastic.vim
"Maintainer:  LCD 47 <lcd047 at gmail dot com>
"License:     This program is free software. It comes without any warranty,
"             to the extent permitted by applicable law.
"             See http://sam.zoy.org/wtfpl/COPYING for more details.
"
"============================================================================

Do you think we need filename and license too?

I think the license is the same throughout the project, so that's probably a bit redundant. "File" is kind of redundant, too. You should know which file it is you are looking at. Something like "Maintainer" isn't a bad shout. I've just been writing "Author" so far. A short description is always good.
I've been thinking that each file should identify the principal authors, and I guess git history provides a full list of everyone who ever worked on something. I'm happy as long as everyone gets credited for work that they do properly.


Missing converging return paths warning

Consider the example below:
script;

fn main(cond: bool) -> u64 {
    while cond {
        return 0;
    };
}

I expect to get a warning saying that not all paths actually return. A return after the loop is missing.

Removing ; after the while gets rid of the problem.


chore: docs publish and tsconfig fix

:tada: This PR is included in version 2.3.1-beta.1 :tada:
The release is available on:

npm package (@develop dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update automatically-mapped-vars.md

The products name / category fields were incorrectly labeled.

The products name / category fields were incorrectly labeled.

Duplicates #112

Closing as duplicate.


refresh function missing

so i get this error but i have a refresh function there as its the same function that loads the original data.
Error: Mandatory prop "refreshFunction" missing.
Pull Down To Refresh functionality will not work
as expected. Check README.md for usage'
<InfiniteScroll
   dataLength={this.props.posts.length}
   next={() => this.props.dispatch(nextPage())}
   loader={
Loading...
}
   refreshFunction={this.refresh()}
   endMessage={

         Yay! You have seen it all

   }
   pullDownToRefresh
   pullDownToRefreshContent={

↓ Pull down to refresh

   }
   releaseToRefreshContent={

↑ Release to refresh

   }
>

and then my function is
this.props.dispatch(getFeed())

why won't it recognise that function

i confirm it doesn't work with this current version 5.0.4


http://ipinfo.io/ provider added

Thanks Evgeny, your pull request looks good! Thanks for adding IP Info provider.


Cython Statistics for SSA Trajectories

Merging WP-dev into dev. This branch has a bunch of fast cython functions as part of the SSAResults class that calculate statistics from stochastic simulations:

empirical_distribution(self, double burn_in, list species_inds, double tend, list max_counts_list)
first_moment(self, double start_time, double final_time, list species_inds)
standard_deviation(self, double start_time, double final_time, list species_inds)
second_moment(self, double start_time, double final_time, list species_inds1, list species_inds2)
correlations(self, double start_time, double final_time, list species_inds1, list species_inds2)

The first of these has been tested extensively. The others less so.

@ayush9pandey just created an examples notebook as well.

Great! Let's merge this once the check is complete.

Looks like some version error with Python 3.7


feat: port Data.Fintype.Sum

Apart from the comment about Classical, LGTM

bors d+

bors r+


docker  quick start ,whilelist isn't working!

docker  quick start ,whilelist isn't working!
this simple "https://ocr-example.herokuapp.com/" is well.
from docker pull image. do not working

Thank you. Nice catch. I guess it's related to this issue https://github.com/otiai10/gosseract/issues/145
I'll update the docker image and let you know.

Closed by f9ef881cb8fb1f20b0ca807af61b41a813a069d9

Closed by f9ef881cb8fb1f20b0ca807af61b41a813a069d9


Issues to connect Azure Devops and Power Bi

Hi everyone!! just joined the community, hoping to interact more with you guys. So apparently, I have some problem to extract the data from Azure Devops into the power Bi. In the Get Data option, I already took the option Azure Devops (Boards Only) and it did extract the data, but some of them is missing, the tags.
And the missing one is very important for me, i couldn't extract the tags element in the Azure Devops and i did do it multiple times, but the tags just wont show up in the Power Bi query editor. I'm hoping that you guys can help me out, thanks in advance!!

Hi @amenjimen - Try these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

Also, you might want to check with the dev community to see whether we support your scenario - or to suggest a feature, if necessary. To make sure it gets in front of the right people, please ask your question here.
If you come across any documentation issues, please bring them to this board.


Update auth, dynamodb, s3, sqs to 2.17.143

Updates

software.amazon.awssdk:auth
software.amazon.awssdk:dynamodb
software.amazon.awssdk:s3
software.amazon.awssdk:sqs

from 2.17.66 to 2.17.143.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #854.


Fix font.glyph lifetimes allow proxy glyphs in cache

One thing I noticed about Cache::queue_glyph was that it called glyph.standalone() for each queued glyph to convert it to a 'static lifetime. I wondered why this was necessary, and when it wasn't if the performance would be improved.
Allowing the cache's queue to take glyphs with a generic lifetime is fairly simple, but I had to stare at the error messages for a while to work out why it wasn't working. There was a signature error in Font::glyph:
Before
impl<'a> Font<'a> {
    pub fn glyph<C: Into<CodepointOrGlyphId>>(&self, id: C) -> Option<Glyph> {...}
}

After
impl<'a> Font<'a> {
    pub fn glyph<C: Into<CodepointOrGlyphId>>(&self, id: C) -> Option<Glyph<'a>> {...}
}

Spot the difference? Before the signature means the Glyph takes the lifetime of the reference to the font, rather than the lifetime of the font data. This was compounded by the fact a reference to the font was used in the GlyphInner struct. This isn't necessary, as Font is a cheap-clone type anyway (a reference, or an Arc).
With this change we can see another small improvement to cache performance, in addition to the optimisation earlier today:
name                                                    control.stdout ns/iter  change.stdout ns/iter  diff ns/iter  diff %  speedup
gpu_cache::cache_bench_tests::cache_bench_tolerance_1   3,048,049               2,878,432                  -169,617  -5.56%   x 1.06
gpu_cache::cache_bench_tests::cache_bench_tolerance_p1  5,288,473               5,067,874                  -220,599  -4.17%   x 1.04

Moreover, this has a larger affect downstream. In my crate gfx_glyph I'm seeing 15-24% reduction in cache interaction latency after all standalone() calls are removed (allowed by this patch).
The change from Cache -> Cache<'font> means this isn't totally backward compatible though, so should be part of the next version, ie 0.3.

In fact if we compare the performance to the beginning of today (ie 5f8b01bca063bed36adcc8d1b4c2112f3aa552c3), the two PRs have made a nice difference:
 name                                                    control.stdout ns/iter  change.stdout ns/iter  diff ns/iter   diff %  speedup
 gpu_cache::cache_bench_tests::cache_bench_tolerance_1   3,306,225               2,913,608                  -392,617  -11.88%   x 1.13
 gpu_cache::cache_bench_tests::cache_bench_tolerance_p1  6,921,851               5,130,891                -1,790,960  -25.87%   x 1.35

Let me know if you have concerns about this, because the only downside I can see is bumping the version to 0.3.

The Font::glyph change is backward compatible as the glyph lifetime will be greater than before.
Cache -> Cache<'font> is not fully back compatible, hence the version bump.

Current user struct fields may need to be refactored Cache<'static>.
Users of a Cache<'static> with a non-static Font<'a> should instead refactor to Cache<'a> for performance improvements.
OR keep Cache<'static> and use cache.queue_glyph(glyph.standalone()) for functionality as before.

I think for all cases refactoring is easy and performance is either improved or unaffected.

I'll close this PR in a couple of days.

Sorry, I missed this PR in my notifications. It looks good to me, and we can collect changes for a version 3

@jackpot51 Thanks for taking a look. When do you think version 0.3.0 will be published?

It can be soon, to incorporate this change


Rubocop Refactoring

See https://github.com/jcraigk/phishin/blob/master/.rubocop_todo.yml

Link is dead because.rubocop_todo.yml doesn't seem to exist anymore. Has this issue already been closed or is the file just missing from the repo?

Oh yep this has already been done, thanks for pointing it out.


CDS static load performance

When loading large CDS static configs with embedded static hosts (see attached), it seems to take ~87ms on my workstation per cluster at startup. This is prohibitive at large cluster sizes, e.g. at 1k it takes ~87s, 10k is > 10 mins. No analysis yet on why this is happening, creating this issue to track further investigation.
envoy_1k.log
envoy_1k_clusters_1k_virtual_hosts.json.gz
envoy_10k_clusters_10k_virtual_hosts.json.gz

So, those initial numbers were on a fastbuild binary. With opt, I see ~32s for 1k, so ~32ms per cluster.

I have to wait about 15s when dealing with 1,500 CDS hosts. Unfortunately I haven't had any chance to debug the issue.

Without looking into this in detail, I think this is likely related or a dup of https://github.com/envoyproxy/envoy/issues/1824. I will fix.

I'm no longer working on the project, but I did discover that switching hostnames to IP addresses caused Envoy to boot in 2s instead of 15s.

@jmarantz is there remaining work on this or should we resolve as complete (for now)?

There are more performance gains on the table (prototyped already) but not clear if it's worth it, e.g. the 10k case can still ~double in speed, from ~3 seconds to ~1.5 seconds IIRC, but at the cost of either adding & maintaining an alternative tag-extraction mechanism alongside regex (compatible) or removing regexes (possibly breaking some integrations).  I'm not sure if the current situation is fast enough in practice.
One thing more significant still on the table is config-reload performance which could be a lot faster with a tag-extraction cache, and also potentially runs concurrently with requests.  Could open up a separate issue for that though.

@jmarantz I'm inclined to close this is fixed. How about opening new tracking issues on the remaining perf enhancements so that we can triage if what we have so far is good enough? I think you have done so much amazing improvement that it's probably ok for now. Awesome work! :)


remove Peter Uhe (pfu599) from accessdev administrator

resolution_fixed   |    by<EMAIL_ADDRESS>
Need to update puppet/hieradata/project.yaml
Are there any implication elsewhere?
(I am just trying out accessdev admin with Say and using this as a example item for consideration)

Issue migrated from trac:152 at 2024-01-31 17:39:23 +1100

<EMAIL_ADDRESS>commented

Fixed in 4edd9c4

<EMAIL_ADDRESS>changed status from new to closed

<EMAIL_ADDRESS>changed resolution from `` to fixed

Scott Wales<EMAIL_ADDRESS>changed owner from `` to Scott Wales<EMAIL_ADDRESS>

Scott Wales<EMAIL_ADDRESS>committed [4]

In [changeset:"4edd9c452bfe2ddb5e6b400a2791ecd702f682f9/puppet"]:
#CommitTicketReference repository="puppet" revision="4edd9c452bfe2ddb5e6b400a2791ecd702f682f9"
Remove Peter Uhe from admins

Thanks for your help Peter

Fixes #152


Hard to find out the model location after model convert

What is the current experience of ilab you've found issue with?

How do you think the described experience should be?

There are a lot of output during the model convert, no obvious information to tell the model location after conversion.
What is the benefit of the change you are proposing?

If applicable, how would backwards-compatability be handled?

Additional context

   https://github.com/instructlab/instructlab/pull/2819


/events items do not always include .silenced

Identified in https://github.com/sensu/uchiwa/issues/567
sensu-api /events does not include .silenced & .silenced_by for items coming from older sensu-client.
Expected Behavior

## Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->

## Possible Solution
<!--- Not obligatory, but suggest a fix/reason for the bug, -->
<!--- or ideas as to the implementation of the addition or change -->

## Steps to Reproduce (for bugs)
<!--- Provide a link to a live example, or an unambiguous set of steps to -->
<!--- reproduce this bug. Include code or configuration to reproduce, if relevant -->
1.
2.
3.
4.

## Context
<!--- How has this issue affected you? What are you trying to accomplish? -->
<!--- Providing context (e.g. links to configuration settings or log data) helps us come up with a solution that is most useful in the real world -->

## Your Environment
<!---


fix: global package install on macOS with Homebrew nodejs

Description
@npmcli/config added on #51, and npmcliConfig.load() would set some env variables, and this behavior cannot be turned off with configuration. It will fail when installing global modules for nodejs installed with homebrew on macOS.
And I didn't find that useful of those env, so set it back to the original env after load() to avoid this problem.

Linked Issues
#51

npmcliConfig.load() would set some env variables

Can you elaborate on it a bit more?

@antfu @npm/config set env on
https://github.com/npm/cli/blob/b405da1672e05d55bd22e476091891c443bcbeab/workspaces/config/lib/index.js#L301
would set env like
  npm_config_userconfig: '/Users/dreamacro/.npmrc',
  npm_config_i: 'true',
  npm_config_g: 'true',
  npm_config_registry: 'https://registry.npmjs.org/',
  npm_config_home: 'https://www.npmjs.org',
  npm_config_prefix: '/opt/homebrew/Cellar/node/20.8.0',
  npm_config_metrics_registry: 'https://registry.npmjs.org/',
  npm_config_globalconfig: '/opt/homebrew/Cellar/node/20.8.0/etc/npmrc',
  npm_config_global_prefix: '/opt/homebrew/Cellar/node/20.8.0',
  npm_config_local_prefix: '/Users/dreamacro',
  npm_node_execpath: '/opt/homebrew/Cellar/node/20.8.0/bin/node'

before load the npm root -g is /opt/homebrew/lib/node_modules, after load become /opt/homebrew/Cellar/node/20.8.0/lib/node_modules, the npm install -g is affected by that env but on homebrew nodejs on macOS it's wrong.


Support for ASUS ROG Devices (e.g. Gladius 2, Gladius 2 Wireless,...)

It would be very cool, if support for ASUS ROG Devices like Gladius 2 or Gladius 2 Wireless could be added. There is an driver project on github (https://github.com/kyokenn/rogdrv), that could help to implement.

Yes, sure. @kyokenn what do you think? We can't do it for now as we don't have the hardware.

I'm just a Python developer. I'm not that good at C/C++ and I'm not familiar with the API. So I would need some help with it, some debug tools for the library and some dummy driver where I could start.

The driver with the most features is the hidpp20 driver, but also quite complicated I guess. The easiest one is probably the etekcity driver, albeit without LED support.
libratbag has a ratbag_device class, and more important a ratbag_profile class, which should include all informations about dpi, buttons, leds, etc. The driver should be able to read these informations from the device, and should be able to commit the set of these variables on the device if wished by the user. It's not easy, but maybe you can fiddle around with the etekcity driver and we can help if you have a problem.

I wonder if it's not better to get the devices emulated in https://github.com/libratbag/ratbag-emu and then write the driver.

I own a ROG Gladius ii Core and can post any needed diagnostic data you need about it.

Distribution: Pop!_OS 21.10

uname -srmo
Linux 5.13.0-7619-generic x86_64 GNU/Linux

ratbagd --version
0.15

sudo ratbagd --verbose=raw

Initializing libratbag
ratbag debug: New device: Razer Razer USB Audio Controller
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: No data file found for 1532:0520
ratbag debug: New device: ASUSTeK ROG GLADIUS II CORE
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: No data file found for 0b05:18dd
ratbag debug: New device: ASUSTeK ROG GLADIUS II CORE
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: No data file found for 0b05:18dd
ratbag debug: New device: ASUSTeK ROG GLADIUS II CORE
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: No data file found for 0b05:18dd
DBus server ready

More information:

Amazon: https://www.amazon.com/ASUS-Lightweight-Ergonomic-ROG-Exclusive-Switch-Socket/dp/B07V6WWGST
Maximum DPI: 6200

If you need anything else, feel free to ping me. Thanks for your nice work :)