Circuit code gets stripped when running on Qiskit Pulse enabled backend

Informations

Qiskit version: 0.23.1
Python version: 3.7.9
Operating system: MacOS Catalina 10.15.7

What is the current behavior?
Sending a quantum object that executes on pulse-enabled hardware gets all the relevant information stripped.
Here is the circuit one would prepare:
OPENQASM 2.0;
include "qelib1.inc";
qreg q[1];
creg c[1];
creg meas[1];
x q[0];
barrier q[0];
measure q[0] -> meas[0];

Here is the corresponding QObj after assembling the circuit (and before running):
Pulse Qobj: xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxx:
Config: {'init_qubits': True,
 'meas_level': 2,
 'meas_lo_freq': [7.284054663,
                  7.385438514,
                  7.32318003,
                  7.230756417,
                  7.280310863,
                  7.146993373,
                  7.400652534],
 'meas_return': 'avg',
 'memory': False,
 'memory_slot_size': 100,
 'memory_slots': 7,
 'parametric_pulses': ['gaussian', 'gaussian_square', 'drag', 'constant'],
 'pulse_library': [],
 'qubit_lo_freq': [4.8220691969340805,
                   4.75994700374019,
                   4.907311555951348,
                   4.878962331604751,
                   4.870904757614711,
                   4.963969787916278,
                   5.177005068926206],
 'rep_delay': 250.0,
 'rep_time': 1000,
 'shots': 1024}
Header: {'backend_name': 'ibmq_casablanca', 'backend_version': '1.1.5'}
Experiments:
Pulse Experiment:
Header:
{'memory_slots': 7, 'name': 'circuit7'}
Config:
{}
        Instruction: parametric_pulse
                t0: 0
                ch: d0
                pulse_shape: drag
                parameters: {'duration': 160, 'amp': (0.1343577470984396+0j), 'sigma': 40, 'beta': -0.33448266317555875}
        Instruction: parametric_pulse
                t0: 160
                ch: m0
                pulse_shape: gaussian_square
                parameters: {'duration': 22400, 'amp': (0.09236770009241822-0.004945500949053017j), 'sigma': 64, 'width': 22144}
        Instruction: acquire
                t0: 160
                duration: 24080
                qubits: [0, 1, 2, 3, 4, 5, 6]
                memory_slot: [0, 1, 2, 3, 4, 5, 6]

But here is the actual circuit that gets executed on the hardware:
OPENQASM 2.0;
include "qelib1.inc";
qreg q[7];
creg c0[7];
barrier q[0], q[1], q[2], q[3], q[4], q[5], q[6];
measure q[0] -> c0[0];
measure q[1] -> c0[1];
measure q[2] -> c0[2];
measure q[3] -> c0[3];
measure q[4] -> c0[4];
measure q[5] -> c0[5];
measure q[6] -> c0[6];

As one can see above, the CNOT instruction got stripped and all qubits got measured.
Steps to reproduce the problem

Prepare the circuit:

from qiskit import *

qc = QuantumCircuit(1)
qc.x(0)
qc.measure_all()

IBMQ.delete_account()
IBMQ.save_account("API-KEY-HERE", overwrite = True)
IBMQ.load_account()

provider = IBMQ.get_provider(
    hub = "ibm-q-xxxxx",
    group = "xxxxxx",
    project = "openpulse",
)
backend = provider.get_backend(device_name)
instance_map = backend.defaults().instruction_schedule_map
basis_gates =  backend.configuration().basis_gates
measurement_map = backend.configuration().meas_map
measurement_level = 2
optimization_level = 0
n_samples = 1024

circuits = [qc]
transpiled_circuits = transpile(
    circuits,
    backend = backend,
    basis_gates = basis_gates,
    optimization_level = optimization_level
)

schedules = schedule(
    transpiled_circuits,
    backend = backend,
    inst_map = instance_map,
    meas_map = measurement_map
)

qobjects = assemble(
    schedules,
    backend = backend,
    meas_level = measurement_level,
    shots = n_samples
)

if not isinstance(qobjects, list):
    qobjects = [qobjects]

jobs = []
for qobject in qobjects:
    job = backend.run(qobject)
    jobs.append(job)

# Get results from jobs
counts = []
for job in jobs:
    result = job.result(timeout = 3600)
    counts.append(result.get_counts())

return counts

Run the code above then look into the IBMQ interface for the particular job being run.
Then look at the circuit that's actually being executed.

What is the expected behavior?
The circuit that was sent is the one that gets executed.
Not one where all the relevant info is stripped.
Suggested solutions
None.

Circuit calibrations resolve, are available in Qiskit and will be released on backends soon https://qiskit.org/documentation/stubs/qiskit.circuit.QuantumCircuit.html#qiskit.circuit.QuantumCircuit.add_calibration.

Circuit calibrations resolve, are available in Qiskit and will be released on backends soon https://qiskit.org/documentation/stubs/qiskit.circuit.QuantumCircuit.html#qiskit.circuit.QuantumCircuit.add_calibration.

@taalexander I'm not sure I follow. In the example above, I'm not trying to add a new gate definition given a custom schedule. But I may be missing something. Can you elaborate on your reply?

@taalexander I'm not sure I follow. In the example above, I'm not trying to add a new gate definition given a custom schedule. But I may be missing something. Can you elaborate on your reply?

The circuit information is not available as you are sending a lower-level "pulse" representation to the backend, the notion of circuits has disappeared. It is now possible to represent circuits with calibrations for gates, as demonstrated by add_calibration. In this format, the circuit will be communicated to the backend along with the tied gate calibrations.

The circuit information is not available as you are sending a lower-level "pulse" representation to the backend, the notion of circuits has disappeared. It is now possible to represent circuits with calibrations for gates, as demonstrated by add_calibration. In this format, the circuit will be communicated to the backend along with the tied gate calibrations.

If you don't want any pulse at all don't use the scheduler, as demonstrated below:
from qiskit import *

qc = QuantumCircuit(1)
qc.x(0)
qc.measure_all()

IBMQ.delete_account()
IBMQ.save_account("API-KEY-HERE", overwrite = True)
IBMQ.load_account()

provider = IBMQ.get_provider(
    hub = "ibm-q-xxxxx",
    group = "xxxxxx",
    project = "openpulse",
)
backend = provider.get_backend(device_name)
instance_map = backend.defaults().instruction_schedule_map
basis_gates =  backend.configuration().basis_gates
measurement_map = backend.configuration().meas_map
measurement_level = 2
optimization_level = 0
n_samples = 1024

circuits = [qc]
transpiled_circuits = transpile(
    circuits,
    backend = backend,
    basis_gates = basis_gates,
    optimization_level = optimization_level
)

qobjects = assemble(
    transpiled_circuits,
    backend = backend,
    meas_level = measurement_level,
    shots = n_samples
)

if not isinstance(qobjects, list):
    qobjects = [qobjects]

jobs = []
for qobject in qobjects:
    job = backend.run(qobject)
    jobs.append(job)

# Get results from jobs
counts = []
for job in jobs:
    result = job.result(timeout = 3600)
    counts.append(result.get_counts())

return counts

If you don't want any pulse at all don't use the scheduler, as demonstrated below:
from qiskit import *

qc = QuantumCircuit(1)
qc.x(0)
qc.measure_all()

IBMQ.delete_account()
IBMQ.save_account("API-KEY-HERE", overwrite = True)
IBMQ.load_account()

provider = IBMQ.get_provider(
    hub = "ibm-q-xxxxx",
    group = "xxxxxx",
    project = "openpulse",
)
backend = provider.get_backend(device_name)
instance_map = backend.defaults().instruction_schedule_map
basis_gates =  backend.configuration().basis_gates
measurement_map = backend.configuration().meas_map
measurement_level = 2
optimization_level = 0
n_samples = 1024

circuits = [qc]
transpiled_circuits = transpile(
    circuits,
    backend = backend,
    basis_gates = basis_gates,
    optimization_level = optimization_level
)

qobjects = assemble(
    transpiled_circuits,
    backend = backend,
    meas_level = measurement_level,
    shots = n_samples
)

if not isinstance(qobjects, list):
    qobjects = [qobjects]

jobs = []
for qobject in qobjects:
    job = backend.run(qobject)
    jobs.append(job)

# Get results from jobs
counts = []
for job in jobs:
    result = job.result(timeout = 3600)
    counts.append(result.get_counts())

return counts

@taalexander Ohhh, now I have an idea about what you meant with add_calibration, thank you!
So if I understand correctly, in order to get accurate results, we need to add these calibrations manually even for predefined gates?
Because essentially, even after the pulses are sent to the device, all one gets is essentially a more or less measurement of all qubits in their ground state (corresponding exactly to the circuit that shows that no useful computation got done).

@taalexander Ohhh, now I have an idea about what you meant with add_calibration, thank you!
So if I understand correctly, in order to get accurate results, we need to add these calibrations manually even for predefined gates?
Because essentially, even after the pulses are sent to the device, all one gets is essentially a more or less measurement of all qubits in their ground state (corresponding exactly to the circuit that shows that no useful computation got done).

It is not necessary to add them if the defaults are fine. They are only useful if you are designing your own custom gates with pulses. Otherwise, you can just use bare circuits and not worry about pulses at all.

It is not necessary to add them if the defaults are fine. They are only useful if you are designing your own custom gates with pulses. Otherwise, you can just use bare circuits and not worry about pulses at all.

@taalexander Yeah, that's the problem though: I'm working directly with pulses and the basic test (before sending my own custom pulses) was to run a simple NOT gate on a single qubit and make sure it works (after getting the NOT gate scheduled at the pulse level). Unfortunately, it doesn't!
I expected that, even if working with pulses, predefined gates should work right out of the box but I'm not getting the expected result.
Either I'm not doing something wrong or there might be a bug in Qiskit/IBMQ integration.
What do you think?

@taalexander Yeah, that's the problem though: I'm working directly with pulses and the basic test (before sending my own custom pulses) was to run a simple NOT gate on a single qubit and make sure it works (after getting the NOT gate scheduled at the pulse level). Unfortunately, it doesn't!
I expected that, even if working with pulses, predefined gates should work right out of the box but I'm not getting the expected result.
Either I'm not doing something wrong or there might be a bug in Qiskit/IBMQ integration.
What do you think?

I now understand the problem. All qubits must be measured with pulse due to the current meas_map reported. Please trace over the unused qubits with https://qiskit.org/documentation/stubs/qiskit.ignis.verification.marginal_counts.html. In your initial qasm file there is not cx gate.

I now understand the problem. All qubits must be measured with pulse due to the current meas_map reported. Please trace over the unused qubits with https://qiskit.org/documentation/stubs/qiskit.ignis.verification.marginal_counts.html. In your initial qasm file there is not cx gate.

@taalexander Many thanks, that did the trick! And I appreciate the additional info as well.

@taalexander Many thanks, that did the trick! And I appreciate the additional info as well.


UK/GB Flag

Thanks for your library!
Currently the codes "uk" and "gb" reference gb.svg which is non-existent whereas uk.svg exists and contains the correct flag.

Fixed in 1.0.2


Generator: Incorrect File Extension in Imports for Generated Client

Problem Description
The generated client currently includes .js file extensions in the imports of local files like the descriptors.js and types.js. This causes issues with frameworks like Next.js, which do not handle these imports correctly. As a result, users are forced to manually remove the .js extension from these imports.
Steps to Reproduce

Generate the client using the provided tool.
Notice that the imports of local files in the generated code include .js extensions.
Attempt to use the generated client in a Next.js project.
Observe the errors related to import paths with .js extensions.

Example
Here is an example of the problematic import statement:
import * as descriptors from "./descriptors.js";

This needs to be manually corrected to:
import * as descriptors from "./descriptors";

Proposed Solution
Update the client generation logic to omit the .js file extension in the imports of local files. This change should ensure compatibility with frameworks like Next.js and improve the overall usability of the generated client.

I'm confused tbh., since I've never had any issues with this. Is this maybe some kind of ESM vs. CJS thing?

Yes, exactly. The .js endings in internal imports are usually required for ESM-based projects. But if you change the TypeScript moduleResolution to bundler (which Next.js does out-of-the-box) this is no longer required and even breaks the generated files.


[10.1.x] ISPN-11819 Prevent ContainerInfinispanServerDriver erroneous state with provided server directory

https://issues.redhat.com/browse/ISPN-11819
Master: https://github.com/infinispan/infinispan/pull/8312

Waiting for the master PR get merged than I will update the source code

@diegolovison Master is in, please update

@ryanemerson Done. Let's wait for CI.
Thanks

Thanks @diegolovison


Found that lora: only works with object: and segment: but not with region:

Feature Idea
Would be fantastic to have an option to call different lora: inside of region: prompts, like inside of object: and segment: prompts. It was implemented in Regional Prompt extension for AUTOMATIC1111, very useful.
Other
Anyway, the article "Advanced Prompt Syntax" would be more complete and more extended, as Swarm prompting is very interesting and different from other's GUIs, really love SwarmUI for prompt options. object: command is not explained at all, was investigating what really means Strengh option of object: and in my case seems not affecting at all, a bit confused about what number to use.

regional loras is waiting on the ComfyUI patch_hooks branch to be finished https://github.com/comfyanonymous/ComfyUI/tree/patch_hooks
region/object are intentionally undocumented as they need better development and a proper UI rather than just documenting the cursed placeholder prompt syntax


Added Kreechure NFTs

[x] I will not ping the Discord about this pull request.

Please provide the following information for your token.
Please include change to the src/lib/.json and in the PR
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Are these PRs reviewed on some schedule that can be published to set expectations? This particular PR was submitted 16-days ago and contains the NFT details on all current Kreechures. Players/Users are excited to be able to see their Solana NFT, Kreechure, in their wallets, like Phantom wallet, but are unable to until this PR is merged.

This PR needs to be re-done because the diff is too large to review. Did you lint it or something? There should be a linter command you can run to un-do it.

I can break the PR up into multiple, smaller, submissions; however, it's
not too larger due to a linter. This PR includes nearly 2000 Kreechure NFTs
like the 2 that already exist on the token list. The file can be downloaded
to review if not viewable in browser.
On Fri, Jun 11, 2021, 2:51 PM Francesco Agosti @.***>
wrote:

This PR needs to be re-done because the diff is too large to review. Did
you lint it or something? There should be a linter command you can run to
un-do it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/solana-labs/token-list/pull/222#issuecomment-859775350,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKLJ2OATNEG7ODQVLM33QTTSJLJRANCNFSM45OPPG3A
.

Uff. Maybe its better if you go directly to the Metadata standard https://www.notion.so/Metadata-064594b7d7df4468a4993b161c9a2719

I can for future Kreechures; however, these have already been
created/minted and for most of them, provided to players/users and sent to
their wallets. I have already created a PR for two Kreechures which was
previously reviewed and approved. I submitted these based on that
successful test.
Not sure if the new standard would allow me to add that metadata on
existing NFTs.
On Fri, Jun 11, 2021, 3:25 PM Francesco Agosti @.***>
wrote:

Uff. Maybe its better if you go directly to the Metadata standard
https://www.notion.so/Metadata-064594b7d7df4468a4993b161c9a2719
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/solana-labs/token-list/pull/222#issuecomment-859792900,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKLJ2J23HMBOZTA6WQLSS3TSJPMHANCNFSM45OPPG3A
.

Uff. Maybe its better if you go directly to the Metadata standard https://www.notion.so/Metadata-064594b7d7df4468a4993b161c9a2719

I agree json list should not be used here. 2000 items is way too many. Please creates metadata on-chain: https://www.notion.so/Metadata-064594b7d7df4468a4993b161c9a2719

Roger that.
On Fri, Jun 11, 2021, 7:21 PM B @.***> wrote:

Closed #222 https://github.com/solana-labs/token-list/pull/222.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/solana-labs/token-list/pull/222#event-4880460778, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKLJ2JZMVTJAMF3JY6KXPLTSKLA5ANCNFSM45OPPG3A
.


Typo "Azure DNS's"→"Azure DNS"

https://learn.microsoft.com/en-us/azure/architecture/example-scenario/integration/app-gateway-internal-api-management-function
https://github.com/MicrosoftDocs/architecture-center/blob/main/docs/example-scenario/integration/app-gateway-internal-api-management-function-content.md
#PingMSFTDocs

Learn Build status updates of commit 26a8c60:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/example-scenario/integration/app-gateway-internal-api-management-function-content.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

#Sign-Off


Fail to build a .Net Core 2.2 project with Azure DevOps with on-premises agent

We are using the Azure DevOps to host and build our code. We are starting to build new services on .Net Core and since 2.2 is out, decided to go that route. But after installing .Net Core SDK 2.2.101 on the build agent (on premises), creating a vanilla asp.net core empty project (New Project -> pushed to git, absolutely no changes), it looks like it wants to compile it against the 2.1, even though the TargetFramework is netcoreapp2.2.
For building we are using the Visual Studio Build task. Using dotnet build is not an option as we'll need multiple targets for some of the common components we are sharing between .net framework and .net core projects we have.
2018-12-19T15:41:51.1962553Z ##[error]C:\Users\VssAdministrator\.nuget\packages\microsoft.aspnetcore.app\2.1.0\build\netcoreapp2.1\Microsoft.AspNetCore.App.targets(14,5): Error : This version of Microsoft.AspNetCore.App is only compatible with the netcoreapp2.1 target framework. Please target netcoreapp2.1 or choose a version of Microsoft.AspNetCore.App compatible with netcoreapp2.2.
The .net core installed on the agent (output from dotnet --list-sdks):
2018-12-19T15:29:54.1887058Z 2.1.201 [C:\Program Files\dotnet\sdk]
2018-12-19T15:29:54.1887424Z 2.1.202 [C:\Program Files\dotnet\sdk]
2018-12-19T15:29:54.1887788Z 2.1.400 [C:\Program Files\dotnet\sdk]
2018-12-19T15:29:54.1887954Z 2.1.402 [C:\Program Files\dotnet\sdk]
2018-12-19T15:29:54.1888059Z 2.1.403 [C:\Program Files\dotnet\sdk]
2018-12-19T15:29:54.1888137Z 2.1.500 [C:\Program Files\dotnet\sdk]
2018-12-19T15:29:54.1888211Z 2.2.101 [C:\Program Files\dotnet\sdk]

Same behavior can be observed on the Hosted VS2017 agent, but you need to install the .Net Core SDK 2.2.101 first using the .NET Core SDK Installer task.
Setting the version for Microsoft.AspNetCore.App explicitly in the csproj file resolves the exception, but does not solve the problem, as stranger errors pop up down the line.
Could not reproduce the problem on a developer machine. Might be related to the version of the Visual Studio installed.

p.s. added here as seems like a .Net Core issue, rather than a Azure DevOps but I might be wrong...

It seems that something in your Azure DevOps setting (or in the platform itself) decided to use wrong MS.AspNetCore.App package. If it compiles locally, I would dig into the differences of used SDKs and other tools. Contacting Azure DevOps support may be one of the ways to narrow it down.
This may be also helpful: https://www.hanselman.com/blog/AzureDevOpsContinuousBuildDeployTestWithASPNETCore22PreviewInOneHour.aspx
If you find evidence this is a problem in .NET Core itself (SDK or runtime), please let us know and we can reopen.
Closing as this is likely problem in Azure DevOps.

UPDATE: for the benefit of anyone having the same issues
found the problem, it was due to the NuGet restore task using the 4.3 version (because I cloned the build definition from another project, doh..). Updated to latest and it worked OK.

we are using NuGet restore 4.8.1 still the same.


'T265 SLAM_ERROR Speed' resulting in failure mode and unresponsible device

Required Info

Camera Model
T265

Firmware Version
<IP_ADDRESS>6

Operating System & Version
Ubuntu 18.04

Kernel Version (Linux Only)
5.0.0-1052-oem-osp1

Platform
PC

SDK Version
v2.35.2

Language
C++ & ROS

Segment
Hand held

Using ROS Melodic I get the following output when starting the T265 node.
[ INFO] [1591981920.259104175]: Initializing nodelet with 16 worker threads.
[ INFO] [1591981920.471577114]: RealSense ROS v2.2.13
[ INFO] [1591981920.471612092]: Running with LibRealSense v2.35.2
[ INFO] [1591981920.478615668]:
[ INFO] [1591981920.486262725]: Device with serial number<PHONE_NUMBER>48 was found.

[ INFO] [1591981920.486320643]: Device with physical ID 2-1-7 was found.
[ INFO] [1591981920.486347414]: Device with name Intel RealSense T265 was found.
[ INFO] [1591981920.486957809]: Device with port number 2-1 was found.
[ INFO] [1591981920.489201928]: No calib_odom_file. No input odometry accepted.
[ INFO] [1591981920.489235312]: getParameters...
[ INFO] [1591981920.527738468]: setupDevice...
[ INFO] [1591981920.527781454]: JSON file is not provided
[ INFO] [1591981920.527809131]: ROS Node Namespace: camera
[ INFO] [1591981920.527828359]: Device Name: Intel RealSense T265
[ INFO] [1591981920.527844207]: Device Serial No:<PHONE_NUMBER>48
[ INFO] [1591981920.527868807]: Device physical port: 2-1-7
[ INFO] [1591981920.527889432]: Device FW version: <IP_ADDRESS>6
[ INFO] [1591981920.527907176]: Device Product ID: 0x0B37
[ INFO] [1591981920.527922001]: Enable PointCloud: Off
[ INFO] [1591981920.527935434]: Align Depth: Off
[ INFO] [1591981920.527948678]: Sync Mode: Off
[ INFO] [1591981920.527974979]: Device Sensors:
[ INFO] [1591981920.528027997]: Tracking Module was found.
[ INFO] [1591981920.528080011]: (Depth, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1591981920.528106882]: (Color, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1591981920.528128741]: (Infrared, 1) sensor isn't supported by current device! -- Skipping...
[ INFO] [1591981920.528142959]: (Infrared, 2) sensor isn't supported by current device! -- Skipping...
[ INFO] [1591981920.528156352]: (Fisheye, 0) sensor isn't supported by current device! -- Skipping...
[ INFO] [1591981920.528183123]: num_filters: 0
[ INFO] [1591981920.528198344]: Setting Dynamic reconfig parameters.
[ INFO] [1591981920.540546060]: Done Setting Dynamic reconfig parameters.
[ INFO] [1591981920.541010314]: fisheye1 stream is enabled - width: 848, height: 800, fps: 30, Format: Y8
[ INFO] [1591981920.541311773]: fisheye2 stream is enabled - width: 848, height: 800, fps: 30, Format: Y8
[ INFO] [1591981920.541341333]: setupPublishers...
[ INFO] [1591981920.543211426]: Expected frequency for fisheye1 = 30.00000
[ INFO] [1591981920.569771259]: Expected frequency for fisheye2 = 30.00000
[ INFO] [1591981920.585444268]: setupStreams...
[ INFO] [1591981920.585500626]: insert Fisheye to Tracking Module
[ INFO] [1591981920.585526293]: insert Fisheye to Tracking Module
[ INFO] [1591981920.585549320]: insert Gyro to Tracking Module
[ INFO] [1591981920.585565542]: insert Accel to Tracking Module
[ INFO] [1591981920.585580747]: insert Pose to Tracking Module
[ INFO] [1591981920.619027792]: SELECTED BASE:Pose, 0
[ INFO] [1591981920.620535062]: RealSense Node Is Up!

Issue Description
It appears that the sensor can go into some kind of deadlock if the sensor is covered for a while, simulating a dark environment.
What happened was that the reported pose started to accelerate in a given direction after covering the sensor for a while. In most cases where the coverup only lasts for a second or so the internal SLAM algorithm was able to recover. But for the situations where I kept the sensor covered for >10 s it would end up going into some sort of failure mode reporting the following:
13/06 01:16:31,414 WARNING [140391512708864] (tm-device.cpp:1289) SLAM_ERROR Speed
[ERROR] [1591982196.599509329]: Ignoring transform for child_frame_id "camera_pose_frame" from authority "unknown_publisher" because of a nan value in the transform (-nan -nan nan) (-nan -nan nan nan)

The only way to recover from this was to restart the node (i.e. restart the pipeline).
ROSbag can be provided at request.

Hi @mindThomas , I am also facing the same issue. Once in a while. But causes the tracking to get corrupt and unusable.
I assume no one from intel will never address this. Too bad. It had potential.

hey, @mindThomas ,did you solve this problem finally. If you get the solution, could you leave a message to help me with the same problem? Thank you very much.


save category mappings to new Category MappingsTable

Please assign back review once you fix the form validators for category


Appending an int to a string does not append to the string

Clang points out that appending an int to a string does not append to the string.

Good catch, thanks @elfprince13!


[UI] Remove github oauth scope from UI

UI adds the github oauth scope during login to the redirect URL that api sends https://github.com/rancher/ui/blob/master/lib/shared/addon/oauth/service.js#L7
From now on the api will send scopes along with clientID and UI won't add any scopes
For: https://github.com/rancherlabs/managed-rancher/issues/353

Reopening, as per @mrajashree findings detailed here https://github.com/rancher/rancher/issues/27028#issuecomment-634304117

Validated this using Github in new installs for
Rancher version v2.4-head (05/28/2020) 24c684289
Rancher version master-head (05/28/2020) 56a464049
I also smoke tested Google Auth  continued working (I was able to enable the auth and login afterwards.
Before in Rancher v2.4.3 installs the userattribute store shown none with the following kubectl command (for local and Github users):
kubectl get userattribute -o custom-columns='Name:UserName,Email:UserPrincipal.extraInfo.Email,Location:UserPrincipal.extraInfo.Location,Company:UserPrincipal.extraInfo.Company,Username:UserPrincipal.loginName'
Name   Email    Location   Company   Username
       <none>   <none>     <none>    <none>
       <none>   <none>     <none>    <none>
       <none>   <none>     <none>    <none>
       <none>   <none>     <none>    <none>

In v2.4-head and master-head the Github email and other details are stored now:
Name            Email          Location   Company   Username
test-39669      <none>         <none>     <none>    test-39669
test-53070      <none>         <none>     <none>    test-53070
izaacorguser1<EMAIL_ADDRESS>                      izaacorguser1
Izaac Zavaleta<EMAIL_ADDRESS>Tempe, Arizona  Rancher Labs @rancher
 izaac

I've opened a separate issue found during upgrade scenario test #27321


/EnableCodeCoverage with testSettings

Behavior of DataCollectors with runsettings and testsettings

CMD Args
Proposed Behaviour

/EnableCodeCoverage + testsettings
CodeCoverage is enabled through TPV2 and Tests are executed through TMI adapter

/collect:”FriendlyName + testsettings
Error Message shown to user: --Collect|/Collect:"FriendlyName " is not supported if test run is configured using testsettings.

/collect:”Event Log” + runsettings (link to testsettings)
Error Message shown to user: DataCollector with friendlyName="Event Log" in runsettings in not supported if test run is configured using testsettings.

Runsettings (with EventLog DC config) + testsettings path within Runsettings
Error Message shown to user: DataCollector with friendlyName="Event Log" in runsettings in not supported if test run is configured using testsettings.

/collect:”EventLog” + runsettings (with eventlog)
Keep only one entry of Event log data collector in runsettings and continue

@PBoraMSFT @pranavkm @sudiptadmsft


I didn't see anything in the readme about it removing my Ubuntu (WSL) installation

This script removed my WSL installation which had a lot of my own scripts and configuration files. Now it's all gone and i wasn't aware it was going to remove it. In what universe is WSL bloat?

The script runs with a "remove all except what's in this list" logic, when you run it it gathers the list and has a few pre req items kept on so they don't get removed (the store). Ubuntu WSL isn't something that comes pre installed with Windows so it's not going to be on that pre req list and needs to be added with the Customized blacklist option. Next time just make sure Ubuntu WSL was on the blacklist so it didn't get removed before debloating. We won't keep a list of apps that some people think "are not bloatware" because that would be a long extensive list and could include anything.
Also refer to lines 1 and 2 of the README

The script runs with a "remove all except what's in this list" logic, when you run it it gathers the list and has a few pre req items kept on so they don't get removed (the store). Ubuntu WSL isn't something that comes pre installed with Windows so it's not going to be on that pre req list and needs to be added with the Customized blacklist option. Next time just make sure Ubuntu WSL was on the blacklist so it didn't get removed before debloating. We won't keep a list of apps that some people think "are not bloatware" because that would be a long extensive list and could include anything.
Also refer to lines 1 and 2 of the README


Type issues

Could not find a declaration file for module '@hyperplay/next-auth-steam'. <EMAIL_ADDRESS>implicitly has an 'any' type.
  There are types at<EMAIL_ADDRESS>but this result could not be resolved when respecting package.json "exports". The '@hyperplay/next-auth-steam' library may need to update its package.json or typings.ts(7016)

Node: v20.12.0
NPM: 10.5.0
TSConfig:
{
  "compilerOptions": {
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "target": "ESNext", //Added this for esm top level await
    "moduleResolution": "bundler",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "plugins": [
      {
        "name": "next"
      }
    ],
    "paths": {
      "@/*": ["./src/*"],
      "@/database": ["./prisma/database"],
      "@/auth": ["./auth"]
    }
  },
  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
  "exclude": ["node_modules"]
}

Yeah it's giving me same problem just use https://github.com/Nekonyx/next-auth-steam


Add first UI elements

Pull Request Test Coverage Report for Build 835431938

0 of 39 (0.0%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-3.6%) to 7.018%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/Liquid-Core.package/LiquidModel.class/instance/addAnswer..st
0
3
0.0%

packages/Liquid-Core.package/LiquidModel.class/instance/answerList..st
0
3
0.0%

packages/Liquid-Core.package/LiquidModel.class/instance/answerList.st
0
3
0.0%

packages/Liquid-Core.package/LiquidModel.class/instance/question..st
0
3
0.0%

packages/Liquid-Core.package/LiquidModel.class/instance/question.st
0
3
0.0%

packages/Liquid-Core.package/LiquidModel.class/instance/initialize.st
0
7
0.0%

packages/Liquid-Core.package/LiquidModel.class/instance/buildQuestionWith..st
0
8
0.0%

packages/Liquid-Core.package/LiquidModel.class/instance/buildWith..st
0
9
0.0%

Totals

Change from base Build 832510039:
-3.6%

Covered Lines:
8

Relevant Lines:
114

💛  - Coveralls


Add basic support for static ips

The connman configuration is modified as explained in the following blog
post: https://resin.io/blog/how-to-configure-a-static-ip-address-with-resin-io/
Support for this feature is said to be "basic" since it misses advanced
settings like configuring a static ip for ethernet but not for wifi, or
having different static ip settings for certain network configurations.
More advanced configuration support will come in the future, since
deciding on a data structure that supports such flexibility would
introduce breaking changes in various Resin.io components, and thus
needs discussion.
The way it works now, if the network is configured to ethernet, the
static ip is applied to the ethernet section, and if the network wifi,
we configure the static ip for both wifi and ethernet sections.

LGTM


updated to work 47.2.16 forge

The Issue
Doesn't work with forge 47.2.16
The Proposal
Make it work with forge 47.2.16
Possible Side Effects
You can use Connector with forge 47.2.16
Alternatives
Its a forge version bump not an intricate api.
Additional Notes
I'm doing this PR for other parties who need it on 47.2.16. A tempoary fork was posted on curseforge until this is accepted.

Why not just use 47.2.17+?
It works with those

Why not just use 47.2.17+? It works with those

If I hazard a guess, the parties I'm doing this PR on the behalf didn't try 47.2.17+ and are unaware of this? I'll poke them and ask them to try out with that.

@Waterpicker still looking for information on this PR

Closing due to insufficient information

works great on forge 47.2.20. idk why  we need that commits.

works great on forge 47.2.20. idk why we need that commits.

I don't even know why a fork is made. Everyone is confused by that as well

And on his report he are not update with lastest of connector so I have the feeling of make a fork for make a fork and publish it on curseforge


Complete SA implementation

11/16/23
I noticed that a lot of the MILP decision variables are never being updated with the update_milp funtion. That is just because the RouteEvent vector just does not track that data.
Rather than getting into more technical debt and try to work with the two sets of data  at the same time, rewrite the Primitives to use MILP data.
Once a solution is generated, then we can package it nicely in the RouteEvent vector.


Fix serialization of Link/BackLink and OpenAPI schema generation

Includes and continues upon #1019. Closes #1008. Fixes #199, #982. Possible fix for #1056.
Fixes serialization of Link/BackLink when used in FastAPI routes.
Fixes OpenAPI JSON schema generation to make it work with FastAPI.
Adds forward ref evaluation in some places.

When this fix can be released?


Directory switch when selecting a resource

When I run the SSH Exec Doc everything is fine, in that I am running the doc from my Default Directory in Azure. However, when I click on the Disk resource on the left hand side and a new tab is opened, I for some reason get a 401 error that says Limited or No Access. "You are not a member of this tenant and do not have access to this directory or any subscriptions/resources within." In the upper right hand corner I can see my account is classified as a Restricted Tenant. If I exit and sign out and then sign back in again to the Azure portal, my default directory status is restored and I can even see the RG that was created from the Exec Docs. Please note: I am using the Visual Studio Enterprise Subscription so that may be part of the issue. I am using my personal account but it is linked to the VS subscription (per Azure Bootcamp instructions).

Issue is incorrect domain in links.

Duplicate as #50


[WIP] Chained scrollbars

Ok this isn't quite complete, but here's my initial stab at implementing chained scrollbars - for #4.
So the way I've currently bashed it is as suggested in that issue - use the markdown parser to attribute source lines to elements in the output.
Then, when you scroll, down, it'll look and see how far down you've scrolled down as a %age of viewport height, find what element's at that position in the view, and try and align the corresponding input line / output element to the same Y position.
Kinda hard to explain. Currently I've left some helper elements in for the time being to see what's going on. Basically whatever's under the red line in each view should correspond. The line moves so that when you're at the very top, both views are scrolled to the top, and when you're at the very end, both views are at the end.
If anyone has any thoughts on this then do let me know, otherwise I'll just keep experimenting to see if I can make this as smooth as possible (and also have a way of disabling it, as suggested in the issue) because it definitely won't be able to get everything right.

nice,
Still some strange jumping arround when you edit and have a large amount of text with some whitespace/newlines between them.
Maybe a idea to jump to the line you're editing and than disable the scrolling for the time beeeing until you move to an other line. Any progress on this issue.


error TS2420: Class 'RedditContent' incorrectly implements interface 'Promise'.

Trying to compile the following:
main.js
import snoowrap from 'snoowrap'

const reddit = new snoowrap({
  // Hiding this
})

tsconfig
{
  "compilerOptions": {
    "module": "commonjs",
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "target": "es6",
    "noImplicitAny": true,
    "moduleResolution": "node",
    "sourceMap": true,
    "outDir": "dist",
    "baseUrl": ".",
    "paths": {
      "*": ["node_modules/*"]
    }
  },
  "include": [
    "src/**/*"
  ]
}

And I receive the following error:
error TS2420: Class 'RedditContent<T>' incorrectly implements interface 'Promise<T>'.
  Property 'then' is missing in type 'RedditContent<T>'.

3 export default class RedditContent<T> implements Promise<T> {

I've tried that exact same tsconfig as well as the code. Not getting any TS errors.
Since that code isn't implementing Promise but rather extending it I don't see how that error could occur - it's not changed since 2018

That's interesting. I'll continue investigating and get back.

This is so embarrassing, I'll close this issue and apologize for wasting your time.
(The issue was entirely on my end, I had accidentally parsed it in a very reckless S&R, shame on me..)


[FEATURE]: Post Bio & display on user profile

Feature Summary

Users need to be able to save changes when editing their bio, on their profile page. Once their bio has been saved, it should be visible to other users when viewing their page

[ ]  when a user clicks "save changes" via the "Add Bio" modal on the user's profile, the input's value should be added to db.
[ ]  When visiting a users profile page, if they have a bio, their bio should be fetched and displayed.

Code of Conduct

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

I will be requesting a change to the prisma schema, allowing bio's to be posted to the db, and then taking care of this ticket.

Can I please be unassigned from this? I need to continue learning nextjs before I'll be able to finish this

I think now we have this feature @mmcbride2929. You can close this issue.
@scape76


Joining multiple levels below adds padding around parentheses

Notes

I'm using Neovim v0.3.2-996-g55c518588.
let g:splitjoin_normalize_whitespace = 0 was tested to no avail.
By joining one level at a time, instead of the whole at once, it appears to work well.

Structure 1
foo(
  \/ ------------------------------------ CURSOR HERE
  bar(
    baz(3,4,5),
    biz(2,3)
  )
)

When typing gJ, with the cursor at bar, I get the following result :heavy_check_mark:
foo(
  bar(baz(3,4,5), biz(2,3))
)

Structure 2
\/ ------------------------------------ CURSOR HERE
foo(
  bar(
    baz(3,4,5),
    biz(2,3)
  )
)

When typing gJ, with the cursor at foo, I get the following result :red_circle:
foo(bar( baz(3,4,5), biz(2,3) ))

Notice the extra paddings around the inner parentheses.
Expectation
I'd expect to be able to configure this behavior, or at least have it be consistent throughout the whole formatting. Either
foo(bar(baz(3,4,5), biz(2,3)))

or
foo( bar( baz(3,4,5), biz(2,3) ) )

Depending on plug-in preferences in regards to joining parentheses or commas.

I'm wondering if this is due to
Note that |gJ| is a built-in mapping that is used for joining lines while
preserving whitespace. However, if no splitting/joining is possible at this
point, the plugin will fall back to the default mapping.

In which case, it would be nice if we could provide our own fallback callback mechanism like this answer instead of having to be bound to gJ.

No, it's not the gJ fallback. The way the plugin joins function arguments is by going over each line and considering it an individual argument. It joins them up with spaces, then, taking care of a potential trailing comma. Here's the entire code for this particular branch (for ruby, at least): https://github.com/AndrewRadev/splitjoin.vim/blob/315cfcc1775b343944d8479a08eb3462e4279771/autoload/sj/ruby.vim#L1049-L1063
Basically, the plugin doesn't "work recursively", in a way. If you were to join the inner "bar" function, and then the outer "foo" function, that'd work just fine, but if you try joining "foo", it'll simply consider the lines as separate arguments.
The only way to do what you'd like is to parse the structure of the code, and I would really rather not attempt to do that. Splitjoin does parse argument lists, but only ones that are contained within a single line. It gets much more complicated when you try to parse multiline stuff (another plugin of mine, sideways, does that, but there's a lot of code there I'd rather not port). Not to mention in this case, it's not just an argument list -- it's any arbitrary expression. Even if I did try parsing multiline argument lists, that wouldn't be enough to figure out the correct structure. I'd need a full expression parser.
What I'd recommend is to join the nested expressions first, and then join the parent ones. That's what I'd do for any other kind of structure as well, hashes and stuff. I know it's not ideal, but I can't really think of a reasonable way to implement the functionality otherwise. If you have any ideas, I'm open to hear you out.

I agree that you'd need an AST parser to untangle nested code using the "text-processing" approach. And as this plugin already covers a lot of cases, I also agree that it's not worth to pile this on.
I'll reword the issue to make it easier to find later, and then close it. Thank you!


As a dashboard viewer, I want to know the average cost per each permit.

To do this we try to get the average total fees charged for a permit in a 30 day period.
month/ avg total fees charged for a permit. This would return a dollar amount.
However, the Building data set does not have a cost associated with a permit so we are blocked on this until the V2 data sets come in.

@sarasti In this data set, there's a column listed as "estimated value." What does that represent?

From Sarasti: "On my phone but it's usually cost to do that actual work - it's an estimate of what you are paying the contractor to do the actual work."

After consultation with @mathias-gibson we're going to push this in the "not know maybe later" bucket. I'll do this by removing it from the milestone.

We actually did this now and it's implemented in the dashboards, yay!


[FIXES #1777] Make accessing pendingLaunches lock free

My objection to #1777 is that it is introducing more locking. The ultimate aim is to make
node provisioning and queue maintenance completely lock free. Thus adding more locks than
is strictly required is a bad plan.
We cannot completely remove provisioningLock at this time as it is used to ensure that
only one provisioning activity can take place for a given label at a time.
This change ensures that the provisioningLock is only used by the NodeProvisioner for
its internal thread guarantees and is thus no-longer used accidentally by any
external threads

@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.


Fix standalone compilation under gcc 10.x

Opened per request of CMS colleagues, this PR fixes compilation issues with gcc versions 10.x (partially fixing compilation under CMSSW 12.x.y).
Only the standalone part is fixed as there are some ROOT dictionary compilation issues related to CMSSW 12.x.y. These issues do not appear in standalone compilation, so they are deemed as CMS software bugs at the moment. A later PR could be issued to fix specific issues if CMSSW-type compilation needs any fixes, but it is unnecessary at the moment.

I am traveling, so Jeff should be in a position to review and sign off if needed

Apparently neither Jeff nor I are allowed to review this code. Can this be fixed?

I confused code owner and review rights for myself, but Jeff needs to get review rights.

I confused code owner and review rights for myself, but Jeff needs to get review rights.

@gritsan: It appears as @jdavis36 already has maintenance rights. I did not see you, so I added you as well now.

BTW, it looks like the most straightforward solution is to the CMSSW 12 problem is to remove CMSSW-specific computation. This doesn't mean anything critical will change on the user side; we can copy the MELA library to ${CMSSW_BASE}/lib ourselves (it already has the same name as what CMSSW would produce through scram). Same goes with the python directory - though I may eventually remove it later anyway.
If you agree to decommission CMSSW-specific compilation, I will update this PR. Otherwise, I will open a new one so that you can see the suggested change explicitly later.


fix spelling mistakes & bash script

change lora_droppout -> lora_dropout;
add 'bash' at the beginning of script

@microsoft-github-policy-service agree


Add python environment to travis

Adds python environment to travis build. This may not work from the first try, apologies in advance :)

OK, this looks good to me now.

All good :+1:


app store pipeline broken

`"[20:48:32]: Login successful
[!] Couldn't find app 'ca.bc.gov.myrangebc' on the account of '***' on App Store Connect
##[error]Error: fastlane failed with return code: 1"`
@jleach if you get time soon can you help me look at this?  I can't access the azure pipeline ( don't think) to address it and I have some stuff I need to get in to test.

Hey,
Ya. I can take a look a bit later today.
J.

On Oct 10, 2019, at 4:45 PM, Micheal W. Wells<EMAIL_ADDRESS>wrote:
`"[20:48:32]: Login successful
[!] Couldn't find app 'ca.bc.gov.myrangebc' on the account of '***' on App Store Connect
##[error]Error: fastlane failed with return code: 1"`
@jleach https://github.com/jleach if you get time soon can you help me look at this? I can't access the azure pipeline ( don't think) to address it and I have some stuff I need to get in to test.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/bcgov/range-ios/issues/160?email_source=notifications&email_token=AAC7N23TAQ6ED5YT3CBFSOLQN65C7A5CNFSM4I7TIH72YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HRCJORQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC7N2ZBNLAKQHWVSUIIK53QN65C7ANCNFSM4I7TIH7Q.


Lap4 se 114

Changes Implemented:

Removed “Filter” Text from the top of "Categories"
Added a dropdown icon (chosen from Icon8) to the assets>icons folder and rendered it on the right side of Categories
Added a bubble tag that displays the currently selected category below the Categories section.

The branch does not have any merge conflicts with develop at this point.

Try to avoid comments in code. there is one comment.

That is true. Since some comments are reminders for the next velocity I will keep them for now though, and will make sure to remove them after dealing with them.

The branch does not have any merge conflicts with the develop branch, it adds simple features to the category dropdown, and it has been reviewed by another teammate and has been approved.


feat: improve error reporting for invalid magic links

Overview
This PR enhances error visibility for invalid magic link handling in the UI. Currently, an invalid magic link would throw a generic error message Ignoring invalid fragment identifier, which provided minimal context and made debugging challenging.

It took us sometime to identify the issue and this PR introduces more descriptive error handling to help quickly understand the root cause with invalid magic links.
Results:

Thank you!

Published to NPM in https://github.com/aws-samples/amazon-cognito-passwordless-auth/releases/tag/v0.14.3


Fixed Unitary Event Analysis plot

Fixes #24
Fixes the unreported bug when Js values contain NaNs, leading to (possibly) shifted unitary event red marks. The fix was to change t_winpos[j] -> t_winpos[js_nonnan][j] so that sig_idx_win and t_winpos indices become aligned.
Added an example to the documentation.
Refactored the all-mighty code for axes plotting routines.

Requires https://github.com/NeuralEnsemble/elephant/pull/387, which simplifies the API significantly by storing the input parameters.
Potential improvements, disregarded in this PR:

rename Js_dict to a more meaningful name;
use viziphant.events.add_event function to plot events instead of custom error-prone script, included in the function body.

UEA elephant tutorial example.
For the comparison, see https://elephant.readthedocs.io/en/latest/tutorials/unitary_event_analysis.html
import matplotlib.pyplot as plt
import neo
import numpy as np
import quantities as pq

import elephant.unitary_event_analysis as ue
from viziphant.unitary_event_analysis import plot_ue

block = neo.io.NeoHdf5IO("dataset-1.h5").read_block()
sts1 = block.segments[0].spiketrains
sts2 = block.segments[1].spiketrains
spiketrains = np.stack((sts1, sts2), axis=1)

bin_size = 5 * pq.ms
winsize = 100 * pq.ms
winstep = 10 * pq.ms

Js_dict = ue.jointJ_window_analysis(spiketrains,
    bin_size=bin_size, winsize=winsize, winstep=winstep)

fig = plot_ue(spiketrains, Js_dict=Js_dict, significance_level=0.05)
plt.show()

2. UEA workshop example
import matplotlib.pyplot as plt
import quantities as pq

import elephant.unitary_event_analysis as ue
from viziphant.unitary_event_analysis import plot_ue

winsize = 100 * pq.ms
binsize = 5 * pq.ms
winstep = 5 * pq.ms
method = 'analytic_TrialByTrial'

plot_params = {
    'events': {'TS-ON': [0 * pq.ms]},
    'unit_real_ids': [sts_for_uea[0][0].name[-5:],
                      sts_for_uea[0][1].name[-5:]],
    'hspace': 0.6,
    'figsize': (10, 12),
    'fsize': 12,
    'ms': 5,
    'lw': 1
}

uriana = ue.jointJ_window_analysis(sts_for_uea, bin_size=binsize,
                                   winsize=winsize, winstep=winstep,
                                   method=method, pattern_hash=[3])

fig = plot_ue(sts_for_uea, Js_dict=uriana, significance_level=0.05,
              **plot_params)

Left: new implementation.
Right: previous (master branch).

3. UEA Poisson processes with 3 neurons
import matplotlib.pyplot as plt
import numpy as np
import quantities as pq

import viziphant
from elephant.spike_train_generation import homogeneous_poisson_process
from elephant.unitary_event_analysis import jointJ_window_analysis, \
    hash_from_pattern

np.random.seed(10)

spiketrains1 = [homogeneous_poisson_process(rate=20 * pq.Hz, t_stop=2 * pq.s)
                for _ in range(5)]
spiketrains2 = [homogeneous_poisson_process(rate=50 * pq.Hz, t_stop=2 * pq.s)
                for _ in range(5)]
spiketrains3 = [homogeneous_poisson_process(rate=20 * pq.Hz, t_stop=2 * pq.s)
                for _ in range(5)]

spiketrains = np.stack((spiketrains1, spiketrains2, spiketrains3), axis=1)
ue_dict = jointJ_window_analysis(spiketrains, bin_size=5 * pq.ms,
                                 win_size=100 * pq.ms, win_step=10 * pq.ms,
                                 pattern_hash=hash_from_pattern([1, 0, 1]))
viziphant.unitary_event_analysis.plot_ue(spiketrains, Js_dict=ue_dict,
                                         significance_level=0.34,
                                         unit_real_ids=['1', '2', '3'])
plt.show()


vector stores as discussed

Thanks for this excellent library!

Could you revert the changes in build.clj, deps.edn & pom.xml?
Then I'll merge to main & make a release.

Thanks for your contribution!

Fixes #74


Problem when run run_evaluation.sh

I change agent = transfuser_ agent and agent_ config=best_ model.pth you provided, but the following error occurred. According to the prompt, the torch version should be too low. I upgraded the torch version but reported another error.
Problem reading checkpoint. Route id 60 larger than maximum number of routes 32
========= Preparing RouteScenario_0 (repetition 0) =========
> Setting up the agent
Could not set up the required agent:
> version_ <= kMaxSupportedFileFormatVersion INTERNAL ASSERT FAILED at /pytorch/caffe2/serialize/inline_container.cc:132, please report a bug to PyTorch. Attempted to read a PyTorch file with version 3, but the maximum supported version for reading is 2. Your PyTorch installation may be too old. (init at /pytorch/caffe2/serialize/inline_container.cc:132)
frame #0: c10::Error::Error(c10::SourceLocation, std::string const&) + 0x33 (0x7f971843c193 in /home/harli/anaconda3/envs/transfuser/lib/python3.7/site-packages/torch/lib/libc10.so)
frame #1: caffe2::serialize::PyTorchStreamReader::init() + 0x1f5b (0x7f96cb7319eb in /home/harli/anaconda3/envs/transfuser/lib/python3.7/site-packages/torch/lib/libtorch.so)
frame #2: caffe2::serialize::PyTorchStreamReader::PyTorchStreamReader(std::string const&) + 0x64 (0x7f96cb732c04 in /home/harli/anaconda3/envs/transfuser/lib/python3.7/site-packages/torch/lib/libtorch.so)
frame #3:  + 0x6c6536 (0x7f9713663536 in /home/harli/anaconda3/envs/transfuser/lib/python3.7/site-packages/torch/lib/libtorch_python.so)
frame #4:  + 0x295a74 (0x7f9713232a74 in /home/harli/anaconda3/envs/transfuser/lib/python3.7/site-packages/torch/lib/libtorch_python.so)
frame #5: _PyMethodDef_RawFastCallDict + 0x24c (0x5629eeae871c in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #6: _PyObject_FastCallDict + 0x6e (0x5629eeab8f5e in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #7:  + 0x12f041 (0x5629eeace041 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #8: PyObject_Call + 0x66 (0x5629eeab97b6 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #9:  + 0xc239e (0x5629eea6139e in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #10: _PyObject_FastCallKeywords + 0x54c (0x5629eeb1ec7c in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #11:  + 0x1802d1 (0x5629eeb1f2d1 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #12: _PyEval_EvalFrameDefault + 0x48a2 (0x5629eeb66602 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #13: _PyEval_EvalCodeWithName + 0x79e (0x5629eeab80de in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #14: _PyObject_FastCallDict + 0x312 (0x5629eeab9202 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #15:  + 0x186bef (0x5629eeb25bef in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #16: _PyObject_FastCallKeywords + 0x54c (0x5629eeb1ec7c in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #17: _PyEval_EvalFrameDefault + 0x47e5 (0x5629eeb66545 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #18: _PyEval_EvalCodeWithName + 0x273 (0x5629eeab7bb3 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #19: _PyFunction_FastCallKeywords + 0x693 (0x5629eead8223 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #20:  + 0x1800c5 (0x5629eeb1f0c5 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #21: _PyEval_EvalFrameDefault + 0x48a2 (0x5629eeb66602 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #22: _PyFunction_FastCallKeywords + 0x187 (0x5629eead7d17 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #23:  + 0x1800c5 (0x5629eeb1f0c5 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #24: _PyEval_EvalFrameDefault + 0x621 (0x5629eeb62381 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #25: _PyObject_FastCallDict + 0x1b6 (0x5629eeab90a6 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #26:  + 0x186bef (0x5629eeb25bef in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #27: _PyObject_FastCallKeywords + 0x54c (0x5629eeb1ec7c in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #28: _PyEval_EvalFrameDefault + 0x47e5 (0x5629eeb66545 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #29: _PyFunction_FastCallKeywords + 0x187 (0x5629eead7d17 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #30:  + 0x1800c5 (0x5629eeb1f0c5 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #31: _PyEval_EvalFrameDefault + 0x621 (0x5629eeb62381 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #32: _PyFunction_FastCallKeywords + 0x187 (0x5629eead7d17 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #33:  + 0x1800c5 (0x5629eeb1f0c5 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #34: _PyEval_EvalFrameDefault + 0x621 (0x5629eeb62381 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #35: _PyFunction_FastCallKeywords + 0x187 (0x5629eead7d17 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #36: _PyEval_EvalFrameDefault + 0x3f5 (0x5629eeb62155 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #37: _PyEval_EvalCodeWithName + 0x273 (0x5629eeab7bb3 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #38: PyEval_EvalCode + 0x23 (0x5629eeab8ee3 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #39:  + 0x227802 (0x5629eebc6802 in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #40: PyRun_FileExFlags + 0x9e (0x5629eebd094e in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #41: PyRun_SimpleFileExFlags + 0x1bb (0x5629eebd0b3b in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #42:  + 0x232c3a (0x5629eebd1c3a in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #43: _Py_UnixMain + 0x3c (0x5629eebd1ccc in /home/harli/anaconda3/envs/transfuser/bin/python)
frame #44: __libc_start_main + 0xf3 (0x7f979e49c0b3 in /lib/x86_64-linux-gnu/libc.so.6)
frame #45:  + 0x1d7555 (0x5629eeb76555 in /home/harli/anaconda3/envs/transfuser/bin/python)

I use torch==1.4.0

I update torch==1.9.1 then
> Registering the global statistics
Exception ignored in: <function LeaderboardEvaluator.del at 0x7fb41cdf0440>
Traceback (most recent call last):
File "/home/harli/transfuser-main/leaderboard/leaderboard/leaderboard_evaluator.py", line 124, in del
self._cleanup()
File "/home/harli/transfuser-main/leaderboard/leaderboard/leaderboard_evaluator.py", line 157, in _cleanup
self._agent_watchdog.stop()
File "/home/harli/transfuser-main/scenario_runner/srunner/scenariomanager/watchdog.py", line 72, in stop
self._timer.cancel()
AttributeError: 'NoneType' object has no attribute 'cancel'

I had updated the model checkpoint for transfuser earlier, which is trained on a newer version. Thanks for pointing this out, I'll update the dependencies.
Regarding the other error, try changing CHECKPOINT_ENDPOINT in run_evaluation.sh. If the results file of an earlier finished evaluation of the same name already exists and RESUME=True, then this error could occur. Let me know if this works.

Thank for your reply, I have solved this problem.

I also met this error, but directly change the pytorch version seems that the car didn't move. when torch==1.9.0 and run_evaluation.sh in docker.

And I also test on the master branch with modify team_agent to transfuser and then run evaluation which I found the agent will not move on first task with some python warning?

But the success on the second task which is quite wried.


Vulnerable Axios Version Used

Summary
NPM is throwing "Axios Cross-Site Request Forgery Vulnerability" when running npm audit
See: https://github.com/advisories/GHSA-wf5p-g6vw-rhxx .
# npm audit report
axios  0.8.1 - 1.5.1
Severity: moderate
Axios Cross-Site Request Forgery Vulnerability - https://github.com/advisories/GHSA-wf5p-g6vw-rhxx
No fix available
node_modules/axios
  alchemy-sdk  *
  Depends on vulnerable versions of axios
  node_modules/alchemy-sdk

Details
https://github.com/advisories/GHSA-wf5p-g6vw-rhxx
Impact
Not sure of security implication with regards to alchemy-sdk.
Somewhat blocking deployments for me as "npm audit fix --force" is built into my pipeline. I have manually disabled auditing for now but this is a security risk.
Also reported this under the Security Advisories tab a few weeks ago but have not received any response there.

👍  It would be great if it could be fixed.

Please update

Sorry for the delay! This has been fixed in v3.1.2


CSV output in results directory

https://github.com/LesnyRumcajs/grpc_bench/issues/86

@LesnyRumcajs do we still care about csv?

@LesnyRumcajs do we still care about csv?

Most likely not, seems nobody cares about this feature for now. I'll close both the issue and PR.


[6.x] Install dependencies with yarn when using yarn

I actually had this code laying around in a branch and forgot to PR it. ¯\(ツ)/¯
I can backport this to v5 too if you like.
Fixes #2614

I'm pretty sure the windows failure is not a real failure but some problem with the runner. :/

This PR forced us to automatically install dependecies with yarn when my package-lock.json is based on npm.
I'm using both yarn and npm but for different projects.
Is there a way to force using npm instead of yarn when both are installed?

You're using both yarn and npm? How does that work? Can you give more details on your setup?


[JOSS] Paper minor corrections

Minor corrections suggestions by @ashwinvis:
“48 ... data for analysis by making intensive use of the pandas (The pandas development team, 2023) and geopandas (Jordahl et al., 2020) functionalities” (Vergauwen et al., 2024, p. 2) (pdf)
*use of the functionalities from pandas (..) and geopandas (..) libraries.
“52 data is imported into the Toolkit Dataset” (Vergauwen et al., 2024, p. 3) (pdf)
into a Toolkit Dataset class instance
“61 Modeldata” (Vergauwen et al., 2024, p. 3) (pdf)
Modeldata class instance
Finally could you make the typography consistent between
Toolkit Dataset
Toolkit Modeldata
Toolkit-Analysis
?

Ref: https://github.com/openjournals/joss-reviews/issues/5916

Can you add my FWO number to the publication?
My number is 11PBN24N.

Refer to the documentation (version) for more details:
Further reading and citations needed here
Since MetObs-Toolkit implements quite a few methods, it would be important to link to other sources which may describe them in detail. If you think that these methods might be subject to change, it might be sufficient to cite the references in the online documentation and link this software paper to the documentation instead. See how scikit-image does it.
“55 to examine data types, irregular timestamps, max-min thresholds, repetitions criteria, spike tests, allowed variation in time windows and spatial tests” (Vergauwen et al., 2024, p. 3) (pdf)
These, IMHO, are quite involved methods. What are the formal basis behind these QC methods or are they based on intuition? Some reuses TITAN (titanlib) while the rest are implemented from the scratch (which means citing TITAN alone will not be sufficient). .
“59 ... gap filling is applied by using interpolation methods” (Vergauwen et al., 2024, p. 3) (pdf)
Gap filling and bias correction is another involved topic. What is the basis behind the methods used? Further reading and citations needed here.

Finally could you make the typography consistent between
Toolkit Dataset Toolkit Modeldata Toolkit-Analysis ?

When referring to a class of the toolkit i used recursive.


Extend windmill.proto protocol used by google-cloud-dataflow-java runner

Extend windmill.proto protocol used by google-cloud-dataflow-java runner.

R: @scwhittle

This pull request is for issue #23262

LGTM
R: @reuvenlax can you merge?


How to get transmission map?

Thank you for your fantastic repository. I'd like to know how to generate transmission map? The author used GDCP to generate them. Do you have the code for GDCP? Could you share it with me via a file-sharing service or email? My email is<EMAIL_ADDRESS>Thank you so much.

Hi, you can find the matlab code to generate transmission map in the author's repo here


Start new petitions with id >= 100000

So that the new petition ids don't overlap with the old petition ids, start the petion id sequence from 100000. To do this we need to flatten the migrations and convert to using SQL for the schema format to record the sequence values.
https://www.pivotaltracker.com/story/show/95512706

:+1:

LGTM :+1:

cool


KAFKA-16535; Implement KRaft add voter handling

This change implements the AddVoter RPC. The high-level algorithm is as follow:

Check that the leader has fenced the previous leader(s) by checking that the HWM is known, otherwise return the REQUEST_TIMED_OUT error.
Check that the cluster supports kraft.version 1, otherwise return the UNSUPPORTED_VERSION error.
Check that there are no uncommitted voter changes, otherwise return the REQUEST_TIMED_OUT error.
Check that the new voter's id is not part of the existing voter set, otherwise return the DUPLICATE_VOTER error.
Send an API_VERSIONS RPC to the first (default) listener to discover the supported kraft.version of the new voter.
Check that the new voter supports the current kraft.version, otherwise return the INVALID_REQUEST error.
Check that the new voter is caught up to the log end offset of the leader, otherwise return a REQUEST_TIMED_OUT error.
Append the updated VotersRecord to the log.
The KRaft internal listener will read this uncommitted record from the log and add the new voter to the set of voters.
Wait for the VotersRecord to commit using the majority of the new set of voters. Return a REQUEST_TIMED_OUT error if it doesn't commit in time.
Send the AddVoter successful response to the client.

The leader implements the above algorithm by tracking 3 events: the ADD_VOTER request is received, the API_VERSIONS response is received and finally the HWM is updated.
The state of the ADD_VOTER operation is tracked by LeaderState using the AddVoterHandlerState. The algorithm is implemented by the AddVoterHandler type.
This change also fixes a small issue introduced by the bootstrap checkpoint (0-0.checkpoint). The internal partition listener (KRaftControlRecordStateMachine) and the external partition listener (KafkaRaftClient.ListenerContext) were using "nextOffset = 0" as the initial state of the reading cursor. This was causing the bootstrap checkpoint to keep getting reloaded until the leader wrote a record to the log. Changing the initial offset (nextOffset) to -1 allows the listeners to distinguish between the initial state (nextOffset == -1) and the bootstrap checkpoint was loaded but the log segment is empty (nextOffset == 0).
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

The test failures look unrelated to me.

@jsancio ./raft/src/test/java/org/apache/kafka/raft/KafkaRaftClientReconfigTest.java.orig still seems to be part of the PR. Can you remove it?

committed, thanks!


[QUESTION] Broken hook after full velero restore ?

We are using velero in order to backup/restore our cluster.
The operator, the webhook and the vault instance are deployed in the same namespace.
A third party app, using vault secret is in a second namespace.
We perform a backup of both namespaces.
I then delete both namespaces and perform a restoration.
Bank vault seems to be up and running.
Unfortunalty the webhooks does not seem to apply anymore => My third party app does not load the secrets (even when deploying a new pod).
I have to perform a helm upgrade in order to make everything work again.
Did you ever try this use case ?

Hi @sparqueur,
the Velero integration has been tested only with the operator and vault instances, so not with the webhook. This can be an ordering issue as well (the webhook gets deployed back after your application pods). Are you backing up the Pods as well, or just the deployment itself?

Hi,
It is not release a restore order. Even when I first restore vault namespace, the webhook is broken.
Strange behavior : It only when I delete the vault namespace ! If i delete all objects inside the namespace but keep it and then restore the content, everything works fine.
Really strange :'( . It might be a kubernetes behavior

I fixed my problem. It was an incomplete velero backup/restore configuration.
In order to make it work I had to set "includeClusterResources" to "true" in backup / restore objects as I was specifying "includedNamespaces"

I'm glad @sparqueur that it works now, I would check the example backup manifest we suggest: https://github.com/banzaicloud/bank-vaults-docs/blob/5a4d1110d2228e6eefdc1af034ce444a89ddaa2a/docs/backup/backup.yaml


Duplicate "subscription-id" in integration runtime example

Just a minor typo, there are two "subscription-id" parameters in the IntegrationRuntimes_CreateLinkedIntegrationRuntime example.

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

ID: 724f5939-6d35-1a7f-e339-8f4ba30a8661
Version Independent ID: 94358cb1-88ad-6006-090d-b50f8ff40a75
Content: az datafactory integration-runtime linked-integration-runtime
Content Source: latest/docs-ref-autogen/datafactory/integration-runtime/linked-integration-runtime.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

need to check whether this is code gen issue


feat(object_filter): add detected object filter

Description
Because of too many detection of unknown objects, the computing costs are exploding.
In order to suppress too many objects, I'm adding a detected object filter based on vector map or x-y position.

Original:

Filter by xy position:

Filter by vector map:

Related links

Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

@miursh can you implement this into object_validator pkg?

@tkimura4 @takayuki5168 I split it into 2 separate nodes (object_lanelet_filter and object_position_filter), and set object_lanelet_filter to default. https://github.com/autowarefoundation/autoware.universe/commit/25b1e4d31bd5dd1cfa0c47b1e97a8bdc6f05637a#diff-ec672d382f513c4582d3001c802efcd852cee80343c0556e419e9ed5c737fbf7
Please let me know if you have any concerns.


Battery Widget Themed fix: center widget vertically

this just brings the battery icon up by 2 pixels so that is is centered vercially on the 24px widget band

Great, thanks!


Fatal error Call to a member function toArray()

I am getting this error for toArray()
Verifying ReCap Server connection - PHP Fatal error:  Call to a member function
toArray() on a non-object in ..\Console-PHP-master\oAuth4ReCap.php on line 153
I am trying on windows 7. I was able to run oAuthLog but when I try to create a scene by running Recap.php I am getting this error.

This error happens in the oAuth code. Which version of the oauth.dll was installed? so I can try on my end as well. One of our engineer reviewed the samples last week, so we are curious why it happened to you.

I was using following on windows 7
PHP 5.4
Oauth 1.2.2
Should I try with PHP 5.6 and Oauth 1.2.3 instead?
On Wed, Jun 15, 2016 at 8:32 AM Cyrille<EMAIL_ADDRESS>wrote:

This error happens in the oAuth code. Which version of the oauth.dll was
installed? so I can try on my end as well. One of our engineer reviewed the
samples last week, so we are curious why it happened to you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Developer-ReCap-Autodesk/Console-PHP/issues/2#issuecomment-226076303,
or mute the thread
https://github.com/notifications/unsubscribe/ACiH_C_IAtcSqe8KT_QOLIQOAdIPn7LCks5qL2tagaJpZM4Ix3-b
.

I installed php 5.6 VC11 x64 Thread Safe (2016-May-26 18:22:23) from http://windows.php.net/download#php-5.6
Installed php_oauth-1.2.3-5.6-ts-vc11-x64.zip from http://windows.php.net/downloads/pecl/releases/oauth/1.2.3/
Configured my php.ini file accoringly
Installed Guzzle
php -f oAuthLog.php // success
php -f ReCap.php -- -c create  // sucess
Do
php -f ReCap.php -- -h
to know all the options you can call.
After I download php 5.4.9 http://windows.php.net/downloads/releases/archives/php-5.4.9-Win32-VC9-x86.zip
Installed http://windows.php.net/downloads/pecl/releases/oauth/1.2.2/php_oauth-1.2.2-5.4-ts-vc9-x86.zip
to be in the same context you were. Working fine too, so I am not sure what is your issue.
Hope that helps.

php 5.6 VC11 x64 Thread Safe and php_oauth-1.2.3-5.6-ts-vc11-x64.zip worked for me too
thanks
I will close this issue.
Can we use the auto-crop feature which is available in recap web app with this api also?

The API does allow you to define a bounding box, but there is no auto-crop feature yet on the API. It is a good suggestion.

I can see such an option on the recap360 web app. Its called smart crop and
user can choose to turn it on or off.
I will try to use bounding box in the meanwhile but with smart crop the
user do not have to give any input.
I can see the result was better than with the web api because of smart crop
option.
If its there on the web app then I guess it should be possible to provide
this feature on the web api also.
Or is it the case that the recap360 web app and recap web api are using
different solutions?
On Sun, Jun 19, 2016 at 2:49 AM autodesk-adn<EMAIL_ADDRESS>wrote:

The API does allow you to define a bounding box, but there is no auto-crop
feature yet on the API. It is a good suggestion.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Developer-ReCap-Autodesk/Console-PHP/issues/2#issuecomment-226965480,
or mute the thread
https://github.com/notifications/unsubscribe/ACiH_DutgQulwINgUS2R8SEGfihV-yhYks5qNGDYgaJpZM4Ix3-b
.

I understand - what I am saying is that it is not yet available in the API. I'll ask the dev team to expose it. And version 3.1 of the API runs on a different machine. Version 3.2 which is in private beta, is a different story.

Ok, to have autocrop you need to be on version 3.2 which is available from our Forge developer portal. Go to http://developer.autodesk.com, apply to the ReCap API to get your keys, and then the documentation will tell you how to use the new autocrop API.


all: build failing on plan9/amd64

plan9/amd64 build has been failing for a while now. Example builder failure: https://build.golang.org/log/47e948a0c5cefb99a35446a0e1dda27ef7b818c5. It's also failing for me locally on my machine.

What version of Go are you using (go version)?
master: ba0fab3cb731fe9a383bd61c3480cccfe32bb1f4
What did you do?

cpu% cd src
cpu% ./make.rc

What did you expect to see?
Successful build
What did you see instead?
Building Go cmd/dist using /usr/fhs/go-plan9-amd64-bootstrap
Building Go toolchain1 using /usr/fhs/go-plan9-amd64-bootstrap.

Building Go toolchain2 using go_bootstrap and Go toolchain1.
sys: trap: invalid opcode pc=0x38d2c8
PC=0x38d2c8

goroutine 1 [running, locked to thread]:
cmd/internal/objabi.init()
	/home/big/go/src/cmd/internal/objabi/util.go:24 +0x3a8 fp=0x28044910 sp=0x28044908 pc=0x38d2c8
fmt.(*pp).handleMethods(0x28084ea0, 0x76, 0x2808f601)
	/home/big/go/src/fmt/print.go:626 +0x314 fp=0x28044b80 sp=0x28044910 pc=0x2d1154
fmt.(*pp).printArg(0x28084ea0, 0x5d2600, 0x28024650, 0x76)
	/home/big/go/src/fmt/print.go:709 +0x216 fp=0x28044c18 sp=0x28044b80 pc=0x2d1736
fmt.(*pp).doPrint(0x28084ea0, 0x28022550, 0x1, 0x1)
	/home/big/go/src/fmt/print.go:1157 +0x105 fp=0x28044ca0 sp=0x28044c18 pc=0x2d5f05
fmt.Sprint(0x28022550, 0x1, 0x1, 0x28024650, 0x280244f8)
	/home/big/go/src/fmt/print.go:249 +0x57 fp=0x28044cf0 sp=0x28044ca0 pc=0x2ce177
cmd/go/internal/cfg.init()
	/home/big/go/src/cmd/go/internal/cfg/cfg.go:248 +0x6c7 fp=0x28044ee8 sp=0x28044cf0 pc=0x38f067
runtime.doInit(0xa04ba0)
	/home/big/go/src/runtime/proc.go:5627 +0x8f fp=0x28044f18 sp=0x28044ee8 pc=0x2443ef
runtime.doInit(0xa05580)
	/home/big/go/src/runtime/proc.go:5622 +0x5c fp=0x28044f48 sp=0x28044f18 pc=0x2443bc
runtime.doInit(0xa07c40)
	/home/big/go/src/runtime/proc.go:5622 +0x5c fp=0x28044f78 sp=0x28044f48 pc=0x2443bc
runtime.main()
	/home/big/go/src/runtime/proc.go:192 +0x228 fp=0x28044fe0 sp=0x28044f78 pc=0x237ac8
runtime.goexit()
	/home/big/go/src/runtime/asm_amd64.s:1374 +0x1 fp=0x28044fe8 sp=0x28044fe0 pc=0x264f21

ax    0x38d2c8
bx    0x648de0
cx    0x28024650
dx    0x0
di    0x0
si    0x101
bp    0x28044b70
sp    0x28044908
r8    0xa22030
r9    0x38d2c8
r10   0x5b8360
r11   0x1
r12   0x0
r13   0x65
r14   0x200
r15   0x200
ip    0x38d2c8
flags 0x10246
cs    0x2b
fs    0x0
gs    0x0
go tool dist: FAILED: /home/big/go/pkg/tool/plan9_amd64/go_bootstrap install -gcflags=all= -ldflags=all= -i cmd/asm cmd/cgo cmd/compile cmd/link: exit status: 'go_bootstrap 7175: sys: trap: invalid opcode pc=0x38d2c8'

@gopherbot add labels OS-Plan9, NeedsInvestigation
/CC @0intro

The last successful run I see on the dashboard is from CL 241275, back on 13 July 2020.
It's not clear to me whether the failures since then are due to a problem with the builder or a regression in the Go toolchain itself.

(And builder was often very flaky even before then. If we want this configuration to stay green, we really need the builder to be up and completing CLs reliably...)

This one isn't an issue with the builder, but a regression in the Go toolchain.

Did some bisection: I suspect that the issue is in a9a1217112aa8f5e01fe2f3e5f203ac880dbd566

@cherrymui : currently trying to understand exactly what's going on in this change and why it breaks in 9front.

Thanks for the report and investigation. CL https://go-review.googlesource.com/c/go/+/261644 should fix this.

Awesome -- thanks! The fix mostly makes sense to me, though I wonder why Plan 9 needs the symbol rounded up.


cli: test and publish Debian package

Upload a package in Debian contrib/non-free that:

ask users for permission
pull and install the probe
check signatures!
run weekly checks and install updates automatically. (Stagger checks to do rolling deployments)
support some EOL flag to disable unsupported hosts permanently?

When asking for updates, send basic info about the host so we can deploy updates only where supported.
Reuse the same update protocol for other OSes?

https://github.com/ooni/probe-cli/pull/117

Making good progress. We've just merged https://github.com/ooni/probe-cli/pull/117, which creates the package and publishes it on bintray. Now I am going to add this new package to the e2etesting suite such that it runs every day.

With https://github.com/ooni/e2etesting/pull/27 merged, we periodically ensure the debian package is WAI.

We've made good progress with @FedericoCeratto in Sprint 25. There is more work to do in Sprint 26.

We have further improved the package with @FedericoCeratto here: https://github.com/ooni/probe-cli/pull/162. We now have a package that can be installed and can in the background. The package is triggered by a timer that fires off daily. The user needs to accept data collection while the package is being installed, otherwise there's not running in background.

I suppose we can call this done! 🎉🎉🎉


[SPIKE] Develop solution for Tip Callout Component (9689)

Problem statement
Engineering needs to decide what is the best solution for creating a re-useable component for the Tip Callout feature that is used on several areas of the website. This decision will define the solution for #9689.
What you need to know
Tip Callout Component is used on several areas of the website. There are pros and cons of creating our own custom component vs using an existing USWDS component.
Acceptance criteria

[ ] Align on solution with engineering

Consensus was reached around how to solve/approach this solution from an engineering perspective.
Will be wrapping around an existing Trussworks component.


allow multiple declarations

this link is broken
multiple declarations mean functions are overloaded

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

What does this fix? Can you add a test?

There are function overloads in this file, so a function has multiple declarations.  But the original code only allowed each function to be declared once. I’m not sure how to test it

@zhmushan Here is an example: https://github.com/denoland/deno_website2/blob/591b49b8de66c0f87f8fe48195978c76f87c88dd/src/doc.test.ts#L5-L19


New feature request - CCXT

Hi,
I was wondering if we could look at adding CCXT so i can have support for my preferred exchange and many others.
Link: https://github.com/ccxt/ccxt
I can see in #621 they talk about ccxt and maybe adding it, but i can find no actual mention to including it.
If for what ever reason you don't want to add ccxt, can I ask we look at adding BCT Markets so i can trade in AUD. Limited coins, only BCT, ETH, ETC, XRP but they support AUD.
Website: https://www.btcmarkets.net
API: https://github.com/BTCMarkets/API
also requested in #571
Thanking you in advance for your time,
zenbot user

We are already using ccxt for some exchanges :-)

See: https://github.com/carlos8f/zenbot/search?utf8=✓&q=ccxt&type=


Hide/fade sights if outside certain range

[x] Wait for A_OverlayAlpha to be complete or supported in GZDoom
[x] Add sight fading by inverse offset amount
[x] simply hide sights outside certain range

As it stands, the sights for the pistol can swing wildly all over the screen, which looks weird. One solution is to fade or hide the sights if the offset exceeds a certain amount. This will have to be done in DECORATE and will require some re-working of the overlay logic.
Additionally A_OverlayAlpha (the easiest and prettiest solution!) is only supported in ZDoom devbuilds, so I think this should wait until that feature is complete and ported to GZDoom as well. Of course ZScript may be complete by then, so in theory everything could be done in DECORATE.

Implemented simple sight hiding. Not as pretty as it could be, but functions well enough.

This enhancement is resolved by b5017caec4e5284ce01838fe1e60293378068b32


High resolution real scene training

Hello, I had a problem trying to train high resolution NeRF using real-life images to get a better mesh. Beta always changed to none after a few steps. My  high resolution data processing is the same as the one you provided. And my parameters is the same as "tnt_highres_grids_courtroom.conf". Could you please give me some advice?

Hi,
How do you set the camera poses? Is your camera poses normalised? And could you share an image of your dataset?

@BingHanOfUESTC The monocular depth is scaled hard-coded here https://github.com/autonomousvision/monosdf/blob/main/code/model/loss.py#L190
You could try to tune the weight for depth loss.

@niujinshuchong Thanks a lot!


[Hold] fixed spaces collapsing in Messages

Details

https://github.com/Expensify/Expensify.cash/issues/3859#issuecomment-872606868
Fixed Issues

$ Fixes #3859
Tests

Do npm install to get the latest packages used.
Open E.cash local server.
Go to any conversation and send the following message.

0 space
 1 spaces
  2 spaces
   3 spaces
    4 spaces

QA Steps

Log in to e.cash and navigate to a conversation
Send the following text

0 space
 1 spaces
  2 spaces
   3 spaces
    4 spaces

Output should contain the same amount of spacing as added.

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web | Desktop

Mobile Web

iOS

Android

did you do 'npm install'?

@parasharrajat Ah forgot, make sure you include that in your testing instructions if there were changes to expensify-common.

@jasperhuangg  Please, let me know if you are facing some issues while testing.

@parasharrajat Still waiting on you to look into this.

Sorry @jasperhuangg, I thought you are still facing the issue so I waiting to get a response over it.
Anyways, I have updated it. Thanks.

@jasperhuangg Done. Thanks.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

Ah crap, didn't see the HOLD on this. I opened up a revert https://github.com/Expensify/Expensify.cash/pull/3969. Sorry for any inconvenience @parasharrajat!

🚀 Deployed to staging         in version: 1.0.77-6🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

Chat - Spaces are not displayed after sending the message
Expected Result:
Spaces should be displayed in the message after it's sent
Actual Result:
No spaces are displayed in the conversation after sending the message
Actions Performed:

Log in to e.cash and navigate to a conversation
Send the following text
0 space
1 spaces
2 spaces
3 spaces
4 spaces

Platform:
iOS ✔
mWeb ✔
Android ✔
Web ✔
Build:
1.0.78-0
Notes/Images/Video:

https://user-images.githubusercontent.com/43996225/125723624-51227edb-b65c-46e0-9284-59c9d7cfcec9.mp4

This PR is reverted. So the original issue still exists.

@jasperhuangg We're good to check off this PR from the list if the PR was reverted right? CC @roryabraham

🚀 Deployed to production         in version: 1.0.79-4🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


remove description of Google Docs Folder in GOVERNANCE.md

the url "https://goo.gl/Alfj8r" is already invalid, so remove the description.

@lixiaobing10051267 it's definitely still valid url (and I see the folders there)

It still works for me as well, and redirects to https://drive.google.com/drive/folders/0B4016P0_3PSqQ3YzYmtFc3JfVlk as full URL. Perhaps we should change to the non-short URL instead?

oh, for me, I can't access both "https://goo.gl/Alfj8r" and "https://drive.google.com/drive/folders/0B4016P0_3PSqQ3YzYmtFc3JfVlk", but I can access "www.google.com", is it my authorization problem?

I tried in an "incognito" window, so it's not an authorisation problem. Possibly the GFW playing a role?

ok.


Mobile design

Made all input fields bootstrap - while keeping enter key support
Fixed search button wrapping on smaller screen sizes
updated logos

Codecov Report

Merging #123 into dev will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##             dev    #123   +/-   ##
=====================================
  Coverage   89.5%   89.5%
=====================================
  Files         18      18
  Lines        343     343
=====================================
  Hits         307     307
  Misses        36      36

Continue to review full report at Codecov.

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


Laravel-AdminLTE for Livewire V3.0 (beta)

How to use Laravel-AdminLTE for Livewire V3.0 (beta)?

The instructions here does not work for Livewire 3.0? Obviously, you will need to target the required version of Livewire with the composer command.

@desyashasyi Just in case, check if this recently detected bug helps to solve your issue:
https://github.com/jeroennoten/Laravel-AdminLTE/pull/1210

Thank you very much. I solved the problem.

@desyashasyi OK, if you think the solution may help others, please share it here.


Update ASP.NET Core 3.0 to 3.1

Update Image of Create a new ASP.NET Core web application from ASP.NET Core 3.0 to 3.1

@eslamisepehr  thanks


Add support for async generators

Async generators would be awesome for streaming outputs from actions in react-router

If we can support AsyncIterable in general, that would be great!
Using the implementation of Promise recursively, I guess we can technically emulate AsyncIterable although I'm not sure if it incurs any performance issues.

This feature should be possible to implement based on this PR https://github.com/jacob-ebey/turbo-stream/pull/51


Use geo.mirror.pkgbuild.com

geo.mirror.pkgbuild.com is a GeoDNS mirror that points to sponsored mirrors.
This avoids the usage of Arch's infrastructure (mirror.pkgbuild.com) for large downloads.
See https://gitlab.archlinux.org/archlinux/infrastructure/-/merge_requests/522 for details.

Thanks for your contribution!


Extend Logging documentation

Describe the proposed changes
Current documentation about logging in Docker seems confusing. It even causes wrong PR being merged into Ansible's docker_container module: https://github.com/ansible/ansible-modules-core/pull/5482
Documentation says:

Use the --log-driver=VALUE with the docker run command to configure the container’s logging driver. If the --log-driver option is not set, docker uses the default (json-file) logging driver.

However, it's not completely true. If my daemon is running with different log_driver option, all containers without explicit log_driver option will fall back to daemon's log_driver, which is not always json-file.
With this PR I make documentation more explicit, and fix the confusion
Related issue
Related issue or PR in another project
https://github.com/docker/docker/issues/28860
https://github.com/ansible/ansible-modules-core/pull/5482

btw, I'm not native speaker, tried as hard as possible to avoid mistakes, but feel free to correct me

Deploy preview ready!
Built with commit 72a0e94f467c28a0334db60df11cb8b12ef331d8
https://deploy-preview-722--docker-docs.netlify.com


TreeRenderer: add RenderBoundsChanged

The forwarding of renderoubnds relied on the Placed event triggering,
which might not happen when only RenderBounds are invalidated
This PR contains:

[x] Changelog
[ ] Documentation
[ ] Tests

Fixes https://github.com/fusetools/fuselibs-public/issues/1005

Why is interface ITreeRenderer? Should this be an internal class? I know this PR didn't touch that, but perhaps we should consider changing it. It's not somethign we want users implementing.


What is exactly the learning rate warmup described in the paper?

It means that if you specify your learning rate to be say 2e-5, then during training the learning rate will be linearly increased from approximately 0 to 2e-5 within the first 10,000 steps.

Thanks, but why dont they specifically mention 'linear warmup' when they do mention 'linear decay' afterwards?

Actually, they do linear warmup first (as I described in my previous reply) and then do a linearly decrease (i.e.  linear decay)  the learning rate from 2e-5 to 0 over the remaining number of steps (still using my previous reply as an example).Check out this part of the code for implementation details.

Ok @hsm207, thanks a lot! going to close the issue.

hello @hsm207
why warmup is required for  BERT(MLM , from scratch) ?
and generally speaking , the idea of cosine annealing is some thing in contradiction with that , i think

hi @mahdirezaey
This way of adjusting learning rate is called learning rate scheduling. It's been found to help improve performance of deep learning models. The intuition is that when you start training, you are probably far from optimal so you can afford to take big steps i.e. large learning rate. After a while, you probably have an idea of where a reasonable optima is so you should take smaller steps to converge to it.
If you are interested in exploring the history behind this idea, I recommend reading this paper:
https://arxiv.org/abs/1803.09820
and then work backwards by reading the references there.

Another advantage of a high learning rate near the beginning (after warmup, which is another issue) is that it has a regularisation effect as it ends up in a relatively "flat" part of parameter space (ie: the hessian is relatively small). The idea of "super-convergence" tries to utilise this (paper, blog).


WSL Crash often since my last update (Error code: Wsl/Service/0x8007274c)

Windows Version
Microsoft Windows [version 10.0.22621.1413]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 20.04
Other Software
WSLg version: 1.0.49
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.1413
Repro Steps
I start my environment with docker-compose -up then I work on different projet using Visual Code
Finally, after one or 2 hours, WSL starts to become unstable until it crashes
Expected Behavior
No decreased performance
Actual Behavior
Since I've updated my Windows to the latest version few weeks ago, my WSL implementation is getting slower and slower and I have to reboot it with wsl --shutdown at least one time a day ...
When I get in trouble, my Ubuntu terminal says  "Error code: Wsl/Service/0x8007274c"

Diagnostic Logs
Here my logs
WslLogs-2023-03-27_12-10-49.zip

@QAnders - I have started rolling out https://github.com/microsoft/WSL/releases/tag/1.1.6 to all users which should fix this issue.

@QAnders - I have started rolling out https://github.com/microsoft/WSL/releases/tag/1.1.6 to all users which should fix this issue.

Thanks, @benhillis !
I'll apply the update and let you know how it plays out...

So far, so good, @benhillis... I'll keep an eye on it and report back if it dies again!
WSL has stayed "alive" during the night, something it hasn't done in a long while... Version seems right:
C:\Users\AndersWasen>wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.50
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22000.1696

@benhillis , nope, sorry to say WSL has crashed while I was away on lunchbreak... :(
The fix does not solve the issue I have...

Hi @benhillis,
I've tried your fix but unfortunately my WSL is still crashing at some point

Here my logs :
WslLogs-2023-03-31_14-24-51.zip
Thanks to have a look

Same as @quentinsimon I too get another error message now:
Error code: Wsl/Service/0x8007274c

[process exited with code<PHONE_NUMBER> (0xffffffff)]

Previously (prior to the "fix") the Terminal just closed down and no error was shown anywhere.

I'm on 1.1.6 and WSL just won't start anymore. The wsl simply hangs indefinitely (I stopped the process after 15 minutes), as well as any attempt to launch a distro or Docker. If I press ctrl+c while the distro is loading I get [process exited with code<PHONE_NUMBER> (0xc000013a)].
I have also started encountering these issues since the last update. I'm on Windows 10.0.19044.2728.
Any ideas?

1.1.6 was not an improvement for me, only change was basically that I got another error message when WSL crashed...
I've just added 1.1.7 (latest release) and this far it seems better...
https://github.com/microsoft/WSL/releases/tag/1.1.7
Not sure if it is related but I got a weird error now where my clock is set to GMT (I am on GMT+2, CET) and the time synchronization isn't working... This seems to have happened after applying 1.1.7 and restarting... 😲

Noticed there's a v1.2.3 already, applied and restarted, but noticed WSL still crashed after coming back from coffee break and waking up laptop... :(

This morning I got the updates:
2023-01 Update for Windows 11 Version 22H2 for x64-based Systems (KB4023057)
Windows Subsystem for Linux WSLg Preview - 1.0.27
Ok, so, thumbs and fingers crossed but I have now ran the whole day without a crash!
I haven't run this long for a few weeks without a crash so it could finally be fixed...

我在自己的win10上也碰到这个问题, 经过查询发现可能与系统自带的openssl.exe有关, 自带的openssl.exe程序会造成VScode的WSL连接插件经常断线, 接着如果用cmd进入wsl, 发现报错 Wsl/Service/0x8007274c
可以尝试用Git/usr/bin/ 路径下的openssl.exe 来取代 windows默认的openssl, 方法是将Git安装目录下的Git/usr/bin/路径加入系统环境变量path中, 并保持系统默认的openssl的环境变量位置在Git/usr/bin/的下方, 重启cmd后,
输入 ssh -V, 查看返回的ssh版本, 如果是 OpenSSH_9.0p1, OpenSSL 1.1.1q  5 Jul 2022 之类的不含有windows签名的版本就完成了

WSL crash often on Surface Pro X . (Error code: Wsl/Service/0x8007274c)
WSL 版本： <IP_ADDRESS>
内核版本： <IP_ADDRESS>-1
WSLg 版本： 1.0.55
MSRDC 版本： 1.2.4419
Direct3D 版本： 1.608.2-61064218
DXCore 版本： 10.0.25880.1000-230602-1350.main
Windows 版本： 10.0.23521.1000

A little up on that post  @benhillis please 🙏
My WSL environment is still very unstable and sometimes I have to restart my computer twice. I have updated all my libraries and I think I am up to date ...

WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.51
MSRDC version: 1.2.3770
Direct3D version: 1.608.2-61064218
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.2361
Logs :
WslLogs-2023-10-09_11-24-34.zip
Please if somebody could improve the reliability af WSL would be great !!

And we keep going into troubles :(
WslLogs-2023-10-12_16-46-23.zip