text:
Send signal of parameter tree settings when initializing detector

Hi,
I would like to initialize my detector with the Parameter tree settings saved. Is there already a function to loop through all the parameter tree and send their respective values?
Otherwise, I think I will make one.  It could also be given as an input when initializing detector (aka a fixed parameter in comon_parameters)

But cannot you do that with a preset?
I mean that you open a dashboard and define a preset with your detector and the settings you would like. You then just have to load this preset at startup.

I want to find the good parameters, then load them as a preset.
This will update correctly the parameter tree but not necessarily the instrument.
I just wanted to insure that all the parameters I set up in my preset where being sent to the apparel in case someone changed it.
I would like to loop through all the parameters with the commit settings. But I think, I will just use a function in the ini_detector such as
[self.commit_settings(p) for p in parameters]
or maybe make subvariable for the relevant parameters.
[self.commit_settings(p) for p in relevant_parameters]

Yes that sounds good ;)

I retrieved a nice function that I found when randomly moving in pymodaq's folders. This seem well adapted to iterate through all children.
'from pymodaq.utils.parameter import utils'
'[self.commit_settings(param) for param in utils.iter_children_params(self.settings)]'
with a custom settings, one could add
'from pymodaq.utils.parameter import utils'
'relevant_parameters_name = ['p1','p2',...]'
'[self.commit_settings(param) for param in utils.iter_children_params(self.settings) if param.name() in relevant_parameters_name]'

yes this is the one you should use!
What you want to do is fine if these relevant parameters are simple ones. What I mean is that sometimes, one parameter value would change the values of others parameters (or their options such as visible or enabled), in that case applying values as you propose could lead to various issues. So be careful...
I guess saving/loading params from a local file could be easily enabled either from within the plugin or from the main ui. Another approach would be to load them from a config file that can be tailored for each user on the machine. The only drawback of both methods compared to load from the preset is that it is not automatic and you will have to do it for each control module once init in the dashboard.
Maybe you could do it for your detector as you wish and once you're staisfied (or not) with the usage come back here to comment on it so we can implement it or something else for all control modules!

PR #222 answer this issue, I'm closing it. Thanks @Ashwolaa  for raising this and the work you've done on it also!

authors: Ashwolaa quantumm seb5g

repo: PyMoDAQ/PyMoDAQ


text:
Unable to use PyTzInfo

Question / Clarification
🌍 Environment

Your operating system and version: Ubuntu 21.04
Your python version:3.9.5
How did you install python (e.g. apt or pyenv)? Did you use a virtualenv?: system
Your Rust version (rustc --version): rustc 1.52.1 (9bc8c42bb 2021-05-09)
Your PyO3 version: 0.13.2
Have you tried using latest PyO3 main (replace version = "0.x.y" with git = "https://github.com/PyO3/pyo3")?: no

Details
As described at https://github.com/PyO3/pyo3/issues/884#issuecomment-622774188 and in tests here, I assumed should be able to "subclass" PyTzInfo and use it in PyDateTime::new, but I'm getting
error[E0308]: mismatched types
  --> src/lib.rs:84:22
   |
84 |                 Some(&tz_info)
   |                      ^^^^^^^^ expected struct `Py`, found struct `TzClass`
   |
   = note: expected reference `&Py<PyAny>`
              found reference `&TzClass`

What am I doing wrong?
partial code:
fn chrono_py_err(e: ParseError) -> PyErr {
    PyErr::new::<PyValueError, _>(PyValueError::new_err(e.to_string()))
}

#[pyclass(extends=PyTzInfo)]
struct TzClass {
    seconds: i32
}

#[pymethods]
impl TzClass {
    #[new]
    fn new(seconds: i32) -> Self {
        TzClass {seconds}
    }

    fn utcoffset<'p>(&self, py: Python<'p>, _dt: &PyDateTime) -> PyResult<&'p PyDelta> {
        PyDelta::new(py, 0, self.seconds, 0, true)
    }

    fn tzname(&self, _py: Python<'_>, _dt: &PyDateTime) -> String {
        String::from("+01:00")  // TODO
    }

    fn dst(&self, _py: Python<'_>, _dt: &PyDateTime) -> Option<&PyDelta> {
        None
    }
}

...
            let offset_seconds = dt.offset().local_minus_utc();
            let tz_info = TzClass::new(offset_seconds);
            let dt = PyDateTime::new(
                py,
                ...
                Some(&tz_info)
            )?;

Full example of my (very naive) attempt at solving this: https://github.com/samuelcolvin/rtoml/pull/25

Indeed; this is a similar problem to the changes being looked at in #1588.
In particular, there's two related pain points:

PyDateTime::new takes Option<&Py<PyAny>> rather than Option<&PyTzInfo>.
&PyCell<TzClass> implements Deref<Target = PyAny>; I think it makes sense for it to implement Deref<Target = PyTzInfo> (i.e. #[pyclass] should deref to the super type rather than directly to PyAny)

For now you can work around this by using Some(&tz_info.into_py(py)) instead of Some(&tz_info). Let's keep this issue open as I'm very tempted to improve the situation for either 0.14 or 0.15.

Humm, I've tried that but I'm getting
error[E0599]: the method `into_py` exists for struct `TzClass`, but its trait bounds were not satisfied
  --> src/lib.rs:83:31
   |
22 | struct TzClass {
   | --------------
   | |
   | method `into_py` not found for this
   | doesn't satisfy `TzClass: AsPyPointer`
...
83 |                 Some(&tz_info.into_py(py)),
   |                               ^^^^^^^ method cannot be called on `TzClass` due to unsatisfied trait bounds
   |
   = note: the following trait bounds were not satisfied:
           `TzClass: AsPyPointer`
           which is required by `&TzClass: pyo3::IntoPy<Py<PyAny>>`

I've updated the above PR with your suggestion in case seeing the error in CI helps, but I have no idea how to go about fixing this.

Unngh, sorry. How about Some(&Py::new(py, tz_info)?.into())?
The APIs on Rust <-> Python interface boundary need some love when even I'm getting them wrong 🤦♂

Nope, I'm getting
error[E0277]: the trait bound `TzClass: AsRef<PyAny>` is not satisfied
  --> src/lib.rs:96:45
   |
96 |                 Some(&Py::new(py, tz_info)?.into()),
   |                                             ^^^^ the trait `AsRef<PyAny>` is not implemented for `TzClass`
   |
   = note: required because of the requirements on the impl of `From<pyo3::Py<TzClass>>` for `pyo3::Py<PyAny>`
   = note: required because of the requirements on the impl of `Into<pyo3::Py<PyAny>>` for `pyo3::Py<TzClass>`

error: aborting due to previous error

What is working if it helps, is the following extremely ugly workaround:
let locals = PyDict::new(py);
locals.set_item("datetime", py.import("datetime")?)?;
locals.set_item("seconds", offset_seconds.to_object(py))?;
let code = "datetime.timezone(datetime.timedelta(seconds=seconds))";
let tz_info = py.eval(code, None, Some(&locals))?;

Then Some(&tz_info.into_py(py)) as you suggested before.
But obviously a solution without dropping back to python would be good (not yet sure how slow the above is).

Ok, last try: Some(&Py::new(py, tz_info)?.to_object(py))
... I think that at least one of the other methods not working is a design flaw. Sorry that you've had to suffer this.

Okay, that works, thanks so much.
(at least it wasn't me missing something obvious)

#1588 changed Datetime::new to take Option<&PyTzInfo>, so I'm going to close this issue as resolved.

source: gharchive/issue

authors: davidhewitt samuelcolvin

license_type: permissive

license_source: github-api


text:
Document pyo3-build-config "config files"

In #1758 I added a PYO3_CONFIG_FILE environment variable which can be used to provide custom configuration for PyO3's build script.
I wanted to let this be "undocumented" in 0.14.2 so that we can have some time to learn about it before making it a stable documented feature. For 0.15, it would be nice to commit to a design and document it, as I think it can be useful for users (especially when cross-compiling).
(See https://github.com/PyO3/pyo3/pull/1758#issuecomment-894617068 for previous discussion.)

(While doing this, it might be a good idea to update Architecture.md to explain the purpose pyo3-build-config)


text:
Segmentation fault

test.py:
from orbit.core.bunch import Bunch
bunch = Bunch()

When I run python test.py I get
zsh: segmentation fault  python test.py

Or when I run mpirun -n 2 python test.py I get
===================================================================================
=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
=   PID 5610 RUNNING AT mac126462
=   EXIT CODE: 11
=   CLEANING UP REMAINING PROCESSES
=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Segmentation fault: 11 (signal 11)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions

However, the following works fine:
from orbit.core.bunch import Bunch
from orbit.utils.orbit_mpi_utils import bunch_pyorbit_to_orbit
bunch = Bunch()

This is still MPI related, correct? Since, I assume, the pyorbit was compiled with MPI.

I'm not sure; I did install with MPI using https://github.com/austin-hoover/pyorbit/commit/356fff2a456737ff5438b79b2e2d797ae4bddb98.
But I'm reproducing this error on a different machine where PyORBIT was not installed with MPI. (On our SNS server, I'm getting Segmentation fault (core dumped).)

I have PyORBIT3 on my Ubuntu workstation. I have the same problem even without MPI installed:
(.mes) shi@pc0126990:~/SHISHLO/AccPhysics/PyORBIT3$ python
Python 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.

from orbit.core.bunch import Bunch
bunch = Bunch()
del bunch
Segmentation fault

PyORBIT2 does not have this error:
Python 2.7.6 (default, Mar 11 2024, 10:31:00)
[GCC 11.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.

from bunch import Bunch
bunch = Bunch()
del bunch

So this was the test I was checking all things out.
https://github.com/PyORBIT-Collaboration/PyORBIT3/blob/main/examples/meson/imports_test.py
Can you try to run it and see if it segfaults too?

I tried - no problem:
import orbit.core.orbit_mpi
import orbit.core.spacecharge
import orbit.core.trackerrk4
import orbit.core.teapot_base
import orbit.core.linac
import orbit.core.orbit_utils
import orbit.core.aperture
import orbit.core.foil
import orbit.core.field_sources
import orbit.core.rfcavities
import orbit.core.impedances
import orbit.core.fieldtracker
import orbit.core.collimator
import orbit.core.error_base
from orbit.core.bunch import Bunch
b = Bunch()
print(b)
del b

Fixed by #28

authors: austin-hoover azukov shishlo

license: MIT


text:
Implementation of Efficient-Net and Efficient-Det in Pytorch Lightning

🚀 Feature
Implementation of Efficient-Net and Efficient-Det in Pytorch Lightning
Motivation
These two algorithms are the state of the art in Image classification and Object detection. Providing an implementation in Pytorch LIghtning will attract many data scientist to adopt this promising framework
Alternatives
https://paperswithcode.com/paper/efficientdet-scalable-and-efficient-object

when you say implementation means everything including the network from scratch, or just mixing lightning with e.g torchvision SOTA models ?

It is not actually provided in TorchVision. We can only find 8it in Torch Hub. It will be attractive that we find some easy way to use these algorithms in Lightning. Thanks for your support.

Hi guys, is this still on? I can have a helping hand in starting the 6th of May.

I think so far, there is no-one working on this, so if you want to, we'd appreciate that :)

Will do that, but gimme some time. I'm on another finishing project. I'll let get back here asap I promise.

Hi, so regarding the migration from pytorch to pytorch lightning for Efficient Net:
https://paperswithcode.com/paper/efficientdet-scalable-and-efficient-object
Do you guys have any requirements or certain standard for the code? I recon that the work here is intended for example rather than solely for implementation so I think there is a need for self-documenting code that's easy to digest perhaps?
Please list, add, edit or delete the ideas that deemed necessary/uneccessary. I'll start working on it this week - 25th of May
List of requirements:

[ ] Working and reproducible Efficient Net using Pytorch Lightning

Work on CPU and GPU
Work on Pytorch 1.4
Work on Latest Pytorch Lightning

[ ] Perform benchmarking as sanity check for accuracy and reproducibility on original work
[ ] Checkpoints models / pretrained weights on the said dataset

@iqDF Sorry for the late reply. Of course you can ping  me whenever you need :) I recently get spammed with github notifications, so I mussed have missed this one :) As for documentation: Yes, a few doctest examples would be nice.
And for the hparams, just include a default that matches the hparams you used to achieve the reported results :)

@iqDF how is it going here?

@Borda Hi I almost thought this was abandoned due to delay inactivity in the forum. Anyway here is the progress:

Currently I have used several detection models (efficient det included) in pytorch  + lightning for my kaggle project.
The implementation needs to be tidy up. I use it for competition currently but tidying up should be quick, but I'll take my time for one week.
Performance wise, I'll just use pretrained one from https://github.com/google/automl

everyone is busy, but seeing this landed would be great, I personally would love to try it...
if you start a draft PR we can help you with some work... :]

@williamFalcon @Borda I would like to implement EfficientNet.
Do I just need to implement just model with nn.Module or full train/val/test loop with LightningModule (including DataModule)?

Hi people. What's the state of the EfficientDet implementation? I took a look at this WIP branch but it only seems to have the BiFPN module implemented. As you know EfficientDet is EfficientNet + BiFPN... If we can implement this it would attract lots of users since EfficientDets are still SOTA in object detection while being very lightweight to fit into edge devices.

Hi people. What's the state of the EfficientDet implementation? I took a look at this WIP branch but it only seems to have the BiFPN module implemented. As you know EfficientDet is EfficientNet + BiFPN... If we can implement this it would attract lots of users since EfficientDets are still SOTA in object detection while being very lightweight to fit into edge devices.

@oke-aditya I'm sure your PRs like #475 are waiting for our reviews for so long, but let me mention you here since you might be interested in this one.

@oke-aditya I'm sure your PRs like #475 are waiting for our reviews for so long, but let me mention you here since you might be interested in this one.

😅 No worries @akihironitta reviewing takes time.
I think efficient net will be added to torchvision soon. Once efficient net is supported by torchvision adding efficient det will be easier.
Since efficient net, ResNet, ResNext, mobilenet all are classification models directly from torchvision, it might make sense to add classification trainer ?
There are other recent classification approaches such as DeiT (FB research)
Lambda Networks etc
So maybe a Classification API is worth adding for bolts ?

😅 No worries @akihironitta reviewing takes time.
I think efficient net will be added to torchvision soon. Once efficient net is supported by torchvision adding efficient det will be easier.
Since efficient net, ResNet, ResNext, mobilenet all are classification models directly from torchvision, it might make sense to add classification trainer ?
There are other recent classification approaches such as DeiT (FB research)
Lambda Networks etc
So maybe a Classification API is worth adding for bolts ?

authors: Borda JVGD akihironitta bilel-bj edgarriba iqDF justusschock oke-aditya ydcjeff


text:
DeepSpeed model checkpoint saves all the checkpoints even when ModelCheckpoint.save_top_k=1

🐛 Bug
When using DeepSpeed with ModelCheckpoint, even when I set save_top_k to 1, the checkpoint directory named last.ckpt contains all the checkpoints, instead of just the top 1. This causes the checkpoints to take way more disk space.
This behavior is due to the DeepSpeed strategy saving each checkpoint in last.ckpt with a distinct the tag containing global_step (default for DeepSpeed). These are never deleted.
For example, if I save a checkpoint every 1000 steps and train for 400k steps, the directory last.ckpt will contain: global_step_999, global_step_1999, ..., global_step_399999, which takes way too much disk space.
Expected behavior
When saving checkpoints with DeepSpeed, last.ckpt should only contain the last global step instead of all the global steps if save_last_k is set to 1.
Environment

PyTorch Lightning Version (e.g., 1.5.0): 1.5.9
PyTorch Version (e.g., 1.10): 1.10.1
Python version (e.g., 3.9): 3.8
OS (e.g., Linux): Ubuntu 20.04
Any other relevant information: deepspeed 0.5.10

cc @awaelchli @ananthsub @ninginthecloud @rohitgr7 @SeanNaren @carmocca @jjenniferdai

hey @tridao
mind share a reproducible script to reproduce this behavior using BoringModel? It might not work on colab, but you can prepare one locally and upload it there or share the notebook directly.
ideally, all the checkpoints along with file paths are managed by ModelCheckpoint so old ones should be deleted once they are not required based on the configuration. DeepspeedStrategy.save_checkpoint call is managed by ModelCheckpoint indirectly.

I've updated the bug report above to include the code to reproduce the issue.
Thanks for your help!

repo: PyTorchLightning/pytorch-lightning


text:
Fix csv extension check

What does this PR do?
Fix csv extension check due to a common mistake in Python tuple literal.
if extension.lower() in ('csv'):
	...

Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

It seems that there is no test originally, do I need to write a new test?

source: gharchive/pull-request


text:
添加了 geonodedaili.py 爬取代理

您好，我是一名在日留学生，最近需要用到一些代理ip服务，于是找到了您的库。
我贡献了一个新的爬取网站，资源很全。
但是我在我自己写的那个类里重写了crawl和fetch方法，因为需要修改爬取间隔时长，同时想传递比较准确的header的参数。(这个网站的代理资源几乎都可用，同时爬起来也很容易被检测到，所以需要修改请求时间间隔和header。)

或者说我是不是可以直接把header通过crawl函数调用的fetch函数传递进去？这样就不用重写fetch函数了。
期待您的回复。

我在日本这边试了下time.sleep(.5)也能一个不漏爬完，但是不知道中国国内访问速度怎样。

多谢 @MGMCN 您的贡献，因为本身 crawl 函数预留的功能有限，比如增加时延等功能，所以我觉得重写一下也 make sense 的。我运行了下，感觉挺不错的，非常有用！Merge 了

authors: Germey MGMCN

license: mit

license_source: bigquery


text:
Set up a deployment server for the project

We need a VPS to deploy the project to and a domain to access it over the Internet.

I have created the server. The API is available at http://chitchat-api.vndprojects.com/ . We can change the domain in the future.

repo: PythonBulawayo/ChitChat


text:
AFG3000: Add support for arbitrary waveform generation

Hello again.
This PR adds support for uploading arbitrary waveform data to the AFG3000 series devices. It also contains an example notebook demonstrating this functionality. Tested on a real AFG3252.
I have one comment and one question:

The waveform data is expected to be in the range 0..1, which is then scaled to the range voltage_low1...voltage_high1. Now, for example if voltage_low1 is -0.5V and voltage_high1 is +0.5V, 0.5 gets mapped to 0V which might be a bit confusing. But I think this is still the most sensible way to do it if the voltage range is asymmetric.
Should we check for overflow in the waveform data? Now if the data goes outside of 0..1, it wraps around, which is probably undesired. Should we issue a warning or an exception?

Note that the commit history also contains a failed attempt at reading back the waveform data from the AFG memory, mostly as a curiosity.

@mgunyho

Now, for example if voltage_low1 is -0.5V and voltage_high1 is +0.5V, 0.5 gets mapped to 0V which might be a bit confusing. But I think this is still the most sensible way to do it if the voltage range is asymmetric.

could you explain why? in particular, why 0.5 gets mapped to 0 and not to 1? i thought that +0.5 is on the right side of the range, hence it should be mapped to 1, no? or perhaps there's a typo in your example, perhaps you meant "voltage_low1 is +0.5V and voltage_high1 is -0.5V" (low votlage is higher than high voltage)?

So the values we upload to the waveform are in the range 0..1, so 0.5 (note: not a voltage!) is in the middle of the range. The center of the range -0.5V..+0.5V is 0V, so that's why 0.5 is 0V. (Maybe using +-0.5V as an example range was confusing.)

please disable the execution of the notebook

Ach, I always forget that! Done.

So the values we upload to the waveform are in the range 0..1, so 0.5 (note: not a voltage!) is in the middle of the range. The center of the range -0.5V..+0.5V is 0V, so that's why 0.5 is 0V. (Maybe using +-0.5V as an example range was confusing.)

aah! understood, thank you! then it's all correct :)
but do you think it would be beneficial to also add function that would take an array of actual voltages, and then normalize it using voltage high/low settings and send the normalized 0..1-ranged data to the instrument? perhaps this will be less confusing for users (even though they still have to be aware of voltage high/low settings that they are using)

Codecov Report

Merging #132 (8240f15) into master (fe59328) will decrease coverage by 0.16%.
The diff coverage is 0.00%.

:exclamation: Current head 8240f15 differs from pull request most recent head a0e1ea1. Consider uploading reports for the commit a0e1ea1 to get more accurate results

@@            Coverage Diff             @@
##           master     #132      +/-   ##
==========================================
- Coverage   19.24%   19.07%   -0.17%
==========================================
  Files         123      123
  Lines       14629    14607      -22
==========================================
- Hits         2816     2787      -29
- Misses      11813    11820       +7

Impacted Files
Coverage Δ

...codes_contrib_drivers/drivers/Tektronix/AFG3000.py
0.00% <0.00%> (ø)

...b_drivers/tests/QDevil/test_real_qdac2_ieee_std.py
33.33% <0.00%> (-9.53%)
:arrow_down:

...ontrib_drivers/tests/QDevil/real_qdac2_fixtures.py
30.90% <0.00%> (-3.58%)
:arrow_down:

...contrib_drivers/tests/QDevil/sim_qdac2_fixtures.py
78.78% <0.00%> (-1.22%)
:arrow_down:

...trib_drivers/drivers/ZurichInstruments/ZIHDAWG8.py
55.33% <0.00%> (-0.88%)
:arrow_down:

...odes_contrib_drivers/tests/test_Keysight_M3201A.py
15.22% <0.00%> (-0.76%)
:arrow_down:

...ivers/drivers/Keysight/SD_common/memory_manager.py
79.64% <0.00%> (-0.36%)
:arrow_down:

...contrib_drivers/drivers/ERAInstruments/erasynth.py
0.00% <0.00%> (ø)

...contrib_drivers/tests/test_rohdeschwarz_HMC804x.py
100.00% <0.00%> (ø)

... and 8 more

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

add a function that would take an array of actual voltages

Hm, this sounds like a good idea, I'll do that later today or tomorrow. Let's not merge before that.

Should we then skip the 0..1 range completely? So we would have upload_waveform_raw() that uploads raw code values 0..16382 and upload_waveform that directly takes voltages and does the rescaling. And then I think it would make sense to throw an error if voltage values are outside of the voltage_low/high.

Should we then skip the 0..1 range completely? So we would have upload_waveform_raw() that uploads raw code values 0..16382 and upload_waveform that directly takes voltages and does the rescaling. And then I think it would make sense to throw an error if voltage values are outside of the voltage_low/high.

agree :)

I started implementing this, but I realized that maybe passing the values as voltages doesn't actually make sense. When you upload a waveform, it's not associated with either of the channels, so we can't know what the voltage limits are. It's possible to output the same waveform on channel 1 and channel 2 with different limits by setting voltage_low1 to be different from voltage_low2! So I think this 0..1 solution is the least confusing way to do it.

I added the bounds checks, IMO this can be merged now.

So I think this 0..1 solution is the least confusing way to do it.

indeed, that's fair!

authors: astafan8 codecov-commenter mgunyho


text:
Outline?

Would there be a performant way of adding an outline?
Checking all neighboring pixels with IsPixelInLine_float seem to be a lot of work.

You could paint the line five times, displacing it 1 pixel up, down, left and right, and then the center.


text:
Adding older submissions on LeetCode automatically

I installed this extension , and I submitted a solution to the problem , but only that question was pushed to the git repo, I don't think all the problems which were pushed earlier on leetcode will pushed to leetcode untill I go ahead and resubmit every one of them.
I hope you do something to automate that process such that all the problems which were solved earlier before I installed this extension could be added as well .

see #77

authors: QasimWani singh-kashish

repo: QasimWani/LeetHub


text:
求在腾讯云上怎么安装

请问在腾讯云轻量应用服务器（应该和普通云服务器差不多）上能安装吗？是不是登录了实例以后按照步骤复制指令进去就行了？

没啥区别

repo: QingdaoU/OnlineJudge


text:
Allow Optimizers as input to VQEProgram

Summary
Fixes #289.
Details and comments
Dictionaries are still supported since some tutorials first need to be updated to use optimizers.

So this is a feature rather than any bug fix then. I see you put a high priority label on the issue which is why I am asking. As a feature this would go out in the next release unless somehow its creating critical problems/issues out there now. I assume you will be updating the optimization repo equivalently. If we need these to stay the same out there so users can use the one in Nature and/or the one in Optimization the same way then I guess things need to be coordinated/sorted out, since I presently would have expected a Nature release in advance of the next Optimization one - unless we start talking bug fix releases.

It would be better to get this out before the next feature release, right, so it seems more like a bugfix 😉 I synced with @pbark and looks like we can do a minor release soon.

authors: Cryoris woodsp-ibm

repo: Qiskit/qiskit-nature


text:
Documentation mistake in U2 gate

In https://qiskit.org/documentation/stubs/qiskit.circuit.library.U2Gate.html#qiskit.circuit.library.U2Gate the given decomposition into RX(pi/2) and virtual Z gates does not match the matrix representation given (even up to a global phase).
I have seen Y90's implemented for Ignis experiments as U2(0,0), which would match the matrix representation in the docs (up to a global phase), so I'm assuming the matrix is correct and the decomposition needs to be updated to:
u2(phi,lambda) = Z_(phi + pi/2) X_(pi/2) Z_(lambda)

PR in progress

repo: Qiskit/qiskit-terra


text:
Remove cyclic-definition handling from Clifford.from_circuit

Summary
This reliance on RecursionError could lead to CPython crashing, when the user had raised the recursion limit beyond what their operating system could actually support in terms of Python frames.  This was particularly an issue with Windows when in a context that jedi is active (such as in an IPython session, or if seaborn was imported), since jedi unilaterally sets the recursion limit to 3000, while CPython tends to overflow the stack on Windows at around 2700 frames.
Recursive definition fields are not valid data in the Qiskit model, as the definition is supposed to be hierarchical, and a decomposition in terms of gates that do not involve the current one in any form.  For defining equivalences that may involve cycles, one should use the EquivalenceLibrary objects that Terra manages, and the transpiler takes advantage of via the BasisTranslator.

Details and comments
Close #10415.  @itoko, you might want to look at this, since I don't know if you had a use-case in mind for the original recursion handling.
This should fix the CI problems that #8967 and #10208 have encountered.

Pull Request Test Coverage Report for Build 5578885867

5 of 7 (71.43%)  changed or added relevant lines in 1 file are covered.
15 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.02%) to 86.041%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/quantum_info/operators/symplectic/clifford_circuits.py
5
7
71.43%

Files with Coverage Reduction
New Missed Lines
%

qiskit/quantum_info/operators/symplectic/clifford_circuits.py
4
87.8%

crates/qasm2/src/lex.rs
5
90.89%

crates/qasm2/src/parse.rs
6
97.58%

Totals

Change from base Build 5578566903:
-0.02%

Covered Lines:
72296

Relevant Lines:
84025

💛  - Coveralls

authors: coveralls jakelishman


text:
Enable the new efficient MCX decompose

Summary
This PR enables #11993 as QuantumCircuit.mcx.
We can reduce the number of CNOT gates as follows.
from qiskit import QuantumCircuit

def bench_mcx(n: int):
    qc = QuantumCircuit(n)
    qc.mcx(list(range(n - 1)), n - 1)
    #print(qc.decompose(reps=1))
    print(n, qc.decompose(reps=4).count_ops()["cx"])

for i in range(6, 10):
    bench_mcx(i)

main
6 92
7 188
8 380
9 764

this PR
6 84
7 140
8 220
9 324

Details and comments

I try to fix errors, but I cannot fix all errors. Need help by experts.

Thanks for spotting this, that's indeed an easy win! 🙂 Regarding the errors:

The decomposition failures are expected, since the MCX definition is now more efficient, the references need updating. I think you can just do this in place.
The QASM failures happen because the circuit now places an MCXGate(name="mcx") which, for 3 controls, is decomposed into C3XGate(name="mcx"). I think the naming conflict causes the strange QASM output. Two possible solutions would be renaming C3XGate(name="c3x") but this could have other repercussions or just accept the new QASM output and fit a regex to cover the number. But maybe @jakelishman has a better idea 🙂

Thanks for handling this @t-imamichi !
One can fix the failing test test/python/transpiler/test_decompose.py as follows:
replace this line: https://github.com/Qiskit/qiskit/blob/87aa89c19387ef7ff4177ef5144f60119da392e3/test/python/transpiler/test_decompose.py#L219
by: decom_circ = self.complex_circuit.decompose(["mcx"], reps=2)
replace this line: https://github.com/Qiskit/qiskit/blob/87aa89c19387ef7ff4177ef5144f60119da392e3/test/python/transpiler/test_decompose.py#L239
by: decom_circ = self.complex_circuit.decompose(["mcx", "gate2"], reps=2)

Thank you for your suggestions, @Cryoris and @ShellyGarion. I tried to update C3X name and C4X name, and found that it affects test_decompose.py. It raises errors even with reps=2 suggested by Shelly.

my suggestion works with your current PR (without any further changes)

Yes, I confirmed it. But the combination does not work unfortunately. I pushed a commit JFYI.

Changing C3X and C4X names do not seem a good idea. There is an unpredicted error as follows.
test.python.qasm3.test_export.TestCircuitQASM3ExporterTemporaryCasesWithBadParameterisation.test_no_include
-----------------------------------------------------------------------------------------------------------

Captured traceback:
~~~~~~~~~~~~~~~~~~~
    Traceback (most recent call last):

      File "/Users/runner/work/qiskit/qiskit/test/python/qasm3/test_export.py", line 2166, in test_no_include
    res = Exporter(includes=[]).dumps(circuit).splitlines()

      File "/Users/runner/work/qiskit/qiskit/qiskit/qasm3/exporter.py", line 181, in dumps
    self.dump(circuit, stream)

      File "/Users/runner/work/qiskit/qiskit/qiskit/qasm3/exporter.py", line 195, in dump
    builder.build_program()

      File "/Users/runner/work/qiskit/qiskit/qiskit/qasm3/exporter.py", line 487, in build_program
    main_statements = self.build_current_scope()

      File "/Users/runner/work/qiskit/qiskit/qiskit/qasm3/exporter.py", line 850, in build_current_scope
    nodes = [self.build_gate_call(instruction)]

      File "/Users/runner/work/qiskit/qiskit/qiskit/qasm3/exporter.py", line 1060, in build_gate_call
    gate_name = ast.Identifier(self.global_namespace[instruction.operation])

      File "/Users/runner/work/qiskit/qiskit/qiskit/qasm3/exporter.py", line 270, in __getitem__
    return self._data[f"{key.name}_{ctrl_state}_{key.params}"]

    KeyError: 'cx_1_[]'

KeyError: 'cx_1_[]'

You can ignore this error, it's a bug in the qasm3 exporter. It's been looked at here: https://github.com/Qiskit/qiskit/pull/12481

I succeeded in passing both test_decompose.py and test_export.py by changing name of C3X and C4X. But I'm not sure this is a right way. It might be a breaking change perhaps.

Pull Request Test Coverage Report for Build 9658863540
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
13 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.01%) to 89.744%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
1
93.64%

crates/qasm2/src/parse.rs
12
97.15%

Totals

Change from base Build 9650973845:
-0.01%

Covered Lines:
63767

Relevant Lines:
71054

💛  - Coveralls

Following the qiskit dev meeting, it was suggested that the gates names will remain "mcx" (and not "c3x" or "c4x") in order to keep the current API, and the name changes can be done in qiskit 2.0 release. Only the tests should be updated accordingly.
Could you please change the names, tests and add release notes?

I reverted the C3X and C4X names. But due to the name conflict of C3X, C4X and MCX (all "mcx"), qasm2/test_export.py fails as follows (a random suffix is appended, e.g., mcx_4685682992). I don't know how to deal with it. Could you suggest a solution or take it over?
FAIL: test_mcx_gate (test.python.qasm2.test_export.TestQASM2Export)
test.python.qasm2.test_export.TestQASM2Export.test_mcx_gate
----------------------------------------------------------------------
testtools.testresult.real._StringException: Traceback (most recent call last):
  File "/Users/ima/tasks/4_2024/qiskit/terra/test/python/qasm2/test_export.py", line 396, in test_mcx_gate
    self.assertEqual(qasm2.dumps(qc), expected_qasm)
  File "/opt/homebrew/Cellar/python@3.10/3.10.14/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py", line 845, in assertEqual
    assertion_func(first, second, msg=msg)
  File "/opt/homebrew/Cellar/python@3.10/3.10.14/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py", line 1226, in assertMultiLineEqual
    self.fail(self._formatMessage(msg, standardMsg))
  File "/opt/homebrew/Cellar/python@3.10/3.10.14/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/case.py", line 675, in fail
    raise self.failureException(msg)
AssertionError: 'OPEN[394 chars]; }\ngate mcx_4685682992 q0,q1,q2,q3 { mcx q0,[56 chars][3];' != 'OPEN[394 chars]; }\nqreg q[4];\nmcx q[0],q[1],q[2],q[3];'
  OPENQASM 2.0;
  include "qelib1.inc";
  gate mcx q0,q1,q2,q3 { h q3; p(pi/8) q0; p(pi/8) q1; p(pi/8) q2; p(pi/8) q3; cx q0,q1; p(-pi/8) q1; cx q0,q1; cx q1,q2; p(-pi/8) q2; cx q0,q2; p(pi/8) q2; cx q1,q2; p(-pi/8) q2; cx q0,q2; cx q2,q3; p(-pi/8) q3; cx q1,q3; p(pi/8) q3; cx q2,q3; p(-pi/8) q3; cx q0,q3; p(pi/8) q3; cx q2,q3; p(-pi/8) q3; cx q1,q3; p(pi/8) q3; cx q2,q3; p(-pi/8) q3; cx q0,q3; h q3; }
- gate mcx_4685682992 q0,q1,q2,q3 { mcx q0,q1,q2,q3; }
  qreg q[4];
- mcx_4685682992 q[0],q[1],q[2],q[3];?    -----------
+ mcx q[0],q[1],q[2],q[3];

Hi @t-imamichi, I pushed a small fix for the qasm tests using regex to match the randomized gate ID, hopefully everything passes now 🙂

Pull Request Test Coverage Report for Build 9676110521
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
5 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.03%) to 89.747%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
5
91.86%

Totals

Change from base Build 9661630219:
0.03%

Covered Lines:
63769

Relevant Lines:
71054

💛  - Coveralls

Hi @t-imamichi, I pushed a small fix for the qasm tests using regex to match the randomized gate ID, hopefully everything passes now 🙂

thanks! this looks good, the tests are OK now, only some lint errors (line too long)

Thank you for your supports, @ShellyGarion and @Cryoris. I fixed the lint errors and added reno.
Could you review it?

Pull Request Test Coverage Report for Build 9689789453
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.002%) to 89.782%

Files with Coverage Reduction
New Missed Lines
%

qiskit/transpiler/passes/synthesis/unitary_synthesis.py
2
88.2%

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

Totals

Change from base Build 9683280067:
-0.002%

Covered Lines:
63814

Relevant Lines:
71077

💛  - Coveralls

Something may go wrong around qpy compatibility. But I have no idea what to do.

Something may go wrong around qpy compatibility. But I have no idea what to do.

merged!

thanks!

authors: Cryoris ShellyGarion coveralls mtreinish t-imamichi

repo: Qiskit/qiskit


text:
pep-0599 superseded by pep-0600

Issue reported in Qiskit Slack

Summary
pep-0599 referenced in manylinux 2014 link superseded by pep-0600
Issue reported in Qiskit Slack
Details and comments
Updated doc to ref pep-0600
Trivial, did not put in any relnote for this

Ah, thanks. I'll close this.


text:
fix: machine-learning-qiskit-pytorch.ipynb deprecapted package fix

Introduces changes to the machine-learning-qiskit-pytorch.ipynb notebook by removing the qobj statement and replaced with t_qc. Using a qobj for run() is deprecated as of qiskit-aer 0.9.0 and transpiled circuits should now be passed directly using backend.run(circuits, **run_options).
Changes made as requested by @frankharkins on qiskit/platypus - PR 2133

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

authors: CLAassistant nuvinga

repo: Qiskit/textbook


text:
PKG package is not honoring default_prefix value

Check if the PKG package is honoring the path defined by default_prefix.

it is using the name of the package for now, so I am closing it for now because we don't need to address this

repo: Quansight/omnisci-datascience-installer


text:
Failing Kubernetes Tests [bug]

CI Test "Kubernetes Tests" fails currently, possibly flaky

I see:
Can't find any online and idle self-hosted runner in the current repository, account/organization that matches the required labels: 'self-hosted'
Waiting for a self-hosted runner to pickup this job...

Looks like a problem with CI Run. Let's look at AWS and see if that fixes it anyway.

Seems to be resolved, closing

authors: Adam-D-Lewis danlester

repo: Quansight/qhub


text:
RollingWindow errors made more verbose

Let's once and for all eliminate all RollingWindow posts on the forums 😉 !
Description
RollingWindow error messages are now more verbose and explicit depending on the type of error:

Window is empty (Count == 0)
i is outside allowable range (i < 0 || i > Size-1)
i is not populated yet (i > Count-1)

(see issue for more details)
Related Issue
#3306
Motivation and Context
I'd like to see a world where no users are ever confused about why their rolling windows don't work.
Requires Documentation Change
None that I know of.
How Has This Been Tested?
Ran the following algorithm:
namespace QuantConnect.Algorithm.CSharp
{
	public class BasicTemplateFrameworkAlgorithm : QCAlgorithm
	{
		public Indicators.RollingWindow<double> winEmpty;
		public Indicators.RollingWindow<double> winPop;
		public Indicators.RollingWindow<double> winAlmostPop;

		public override void Initialize()
		{
			winEmpty = new RollingWindow<double>(3);
			winPop = new RollingWindow<double>(5) { 0.3, 0.4, 0.5, 0.6, 0.7 };
			winAlmostPop = new RollingWindow<double>(5) { 0.1, 0.2, 0.3, 0.4 };

			// case 1: no entries in the window yet
			//Log(winEmpty[1]);

			// case 2: i outside allowable range of i's
			//Log(winPop[56]);

			// case 2b: i less than 0
			//Log(winPop[-3]);

			// case 3: i not yet populated
			//Log(winAlmostPop[4]);

			// case 4: correct
			//Log(winPop[2]);
		}
	}
}

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] 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.
[ ] ~I have added tests to cover my changes.~ Should not be needed as it doesn't change how rolling windows work.
[ ] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Nice PR :)

Looks like Travis fails at something random?
***** QuantConnect.Tests.Algorithm.AlgorithmLiveTradingTests.SetHoldingsTakesIntoAccountPendingMarketOrders
20190707 13:29:13.987 ERROR:: SecurityTransactionManager.WaitForOrder(): Order did not fill within 5 seconds.
***** QuantConnect.Tests.Algorithm.AlgorithmPlottingTests.TestGetChartUpdatesWhileAdding
20190707 13:29:18.003 ERROR:: BrokerageTransactionHandler.Run():  System.Threading.ThreadAbortException
  at System.Threading.CancellationToken.ThrowIfCancellationRequested () [0x00008] in <a6f810169ec746eeb2789b925e2858c0>:0
  at System.Threading.SemaphoreSlim.WaitUntilCountOrTimeout (System.Int32 millisecondsTimeout, System.UInt32 startTime, System.Threading.CancellationToken cancellationToken) [0x00004] in <a6f810169ec746eeb2789b925e2858c0>:0
  at System.Threading.SemaphoreSlim.Wait (System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x000ca] in <a6f810169ec746eeb2789b925e2858c0>:0
  at System.Collections.Concurrent.BlockingCollection`1[T].TryTakeWithNoTimeValidation (T& item, System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken, System.Threading.CancellationTokenSource combinedTokenSource) [0x00067] in <1a0168907d2042858c12ff7b2c118a26>:0
  at System.Collections.Concurrent.BlockingCollection`1[T].TryTake (T& item, System.Int32 millisecondsTimeout, System.Threading.CancellationToken cancellationToken) [0x00006] in <1a0168907d2042858c12ff7b2c118a26>:0
  at QuantConnect.Util.BusyBlockingCollection`1+<GetConsumingEnumerable>d__15[T].MoveNext () [0x000b8] in <cd6c850a00dd44c7be6f2bd270fc1f6b>:0
  at QuantConnect.Lean.Engine.TransactionHandlers.BrokerageTransactionHandler.Run () [0x00032] in <eb49cc7d50ee4989b96761a77fa14d60>:0

repo: QuantConnect/Lean


text:
Making notebooks from rsts without clearing outputs

One of the things I loved about Jupytext is that, when you edit the Markdown file and then reload the corresponding notebook, you don't lose the outputs or what's currently stored in kernel memory.
So if I make a small edit at the bottom of a markdown file and then go back to the notebook, I don't need to run all the cells again.  I just refresh and off I go.
In contrast, we lose everything when we make ipynbs from rsts, and hence need to run again from the top.  That's almost prohibitive in some notebooks, making our editing system close to non-functional in such settings.
@AakashGfude @mmcky Could we please get together soon and discuss this?

@jstac the outputs (or notebooks) using sphinx-build states are not checked (only the source RST files) so we would need to engineer this into the extension to get this kind of behaviour. The build process only checks RST's in the process and then rebuilds notebooks fresh each time. I think this task would be better suited to the RST to IPYNB converter that we have as an additional project (in similar fashion to JupyText, or perhaps teach JupytText RST)

@AakashGfude let's review this after lunch today.

@AakashGfude if we have ipynb notebooks available and a user doesn't use make clean do you think we could just replace all the incoming blocks and keep the outputs in place. The issue here would be we would need to know which code-blocks or code-cells changed (if any) and then re-run from that point forward.

@jstac I have tagged this for v0.6 milestone which follows pdf support v0.5. Just flagging this as this is tagged with high-priority? Is that OK?

Sure, thanks @mmcky .  I flagged it as high priority because it's something that would be super useful, but it's a side track from what you're trying to do now so please put it aside, in the way that you suggest.
I've removed the high priority flag.

authors: jstac mmcky

repo: QuantEcon/sphinxcontrib-jupyter


text:
Fix issues in this repo for k4n8 and k6n10

correct exit codes to be non-zero when make steps fail in ql_symbiflow wrapper, like at: https://github.com/QuickLogic-Corp/symbiflow-arch-defs/blob/54803801d8f94a79f7b5c7b9ffa284a83182f5a2/quicklogic/common/toolchain_wrappers/ql_symbiflow#L568

correct error in usage of [ in bash if we use && in https://github.com/QuickLogic-Corp/symbiflow-arch-defs/blob/54803801d8f94a79f7b5c7b9ffa284a83182f5a2/quicklogic/common/toolchain_wrappers/ql_symbiflow#L266

minor aesthetic change in generated Makefile.symbiflow

This is a WIP, and more changes might be needed after testing.

@mkurc-ant @kgugala : The CI failures with the eos-s3 may be valid failures, as the previously, the ql_symbiflow wrapper would not return a non-zero exit value even if any make step failed.
This PR fixes that, and hence the failures in CI may be visible now.
Please review and check if this is the case, or if there is anything in the PR that is causing real CI failures.

@mkurc-ant @kgugala : This seems to be a valid error, and it was being masked due to the zero return value from the ql_symbiflow wrapper.
The latest commit merged on the master also shows the errors: https://github.com/QuickLogic-Corp/symbiflow-arch-defs/runs/4379018876?check_suite_focus=true#step:6:61

@coolbreeze413 You are right. I have examined the logs and I can see two issues which probably have been masked out by the zero return value:
In installed toolchain tests during fasm2bels stage. Probably there is some inconsistency in the wrapper scripts when it comes to specifying a package for PP3 and a pinmap for k4n8:
2021-12-05T21:46:30.3075350Z 6: Running fasm2bels
2021-12-05T21:46:30.3075749Z 6: Traceback (most recent call last):
2021-12-05T21:46:30.3077047Z 6:   File "/home/runner/work/symbiflow-arch-defs/symbiflow-arch-defs/quicklogic-arch-defs/bin/python/fasm2bels.py", line 1107, in <module>
2021-12-05T21:46:30.3078451Z 6:     f2b = Fasm2Bels(db, args.device_name, args.package_name)
2021-12-05T21:46:30.3080347Z 6:   File "/home/runner/work/symbiflow-arch-defs/symbiflow-arch-defs/quicklogic-arch-defs/bin/python/fasm2bels.py", line 72, in __init__
2021-12-05T21:46:30.3081490Z 6:     ", ".join(db["package_pinmaps"].keys())
2021-12-05T21:46:30.3082813Z 6: __main__.Fasm2BelsException: ERROR: 'chandalar_pinmap.csv' is not a vaild package for device 'eos-s3'. Valid ones are: WR42, PD64, PU64

And in the CMake script which runs the toolchain tests:
2021-12-01T10:46:05.5915486Z 14: CMake Warning (dev) at /home/runner/work/symbiflow-arch-defs/symbiflow-arch-defs/quicklogic/common/cmake/run_toolchain_test.cmake:76 (SET):
2021-12-01T10:46:05.5916347Z 14:   Syntax error in cmake code at
2021-12-01T10:46:05.5916700Z 14:
2021-12-01T10:46:05.5917613Z 14:     /home/runner/work/symbiflow-arch-defs/symbiflow-arch-defs/quicklogic/common/cmake/run_toolchain_test.cmake:76
2021-12-01T10:46:05.5918322Z 14:
2021-12-01T10:46:05.5918654Z 14:   when parsing string
2021-12-01T10:46:05.5918971Z 14:
2021-12-01T10:46:05.5919682Z 14:     \\\S*\[[0-9]*\]\s
2021-12-01T10:46:05.5919973Z 14:
2021-12-01T10:46:05.5920337Z 14:   Invalid escape sequence \S
2021-12-01T10:46:05.5920708Z 14:
2021-12-01T10:46:05.5921213Z 14:   Policy CMP0010 is not set: Bad variable reference syntax is an error.  Run
2021-12-01T10:46:05.5922113Z 14:   "cmake --help-policy CMP0010" for policy details.  Use the cmake_policy
2021-12-01T10:46:05.5922778Z 14:   command to set the policy and suppress this warning.
2021-12-01T10:46:05.5923662Z 14: This warning is for project developers.  Use -Wno-dev to suppress it.

Let us work on fixing those.

@mkurc-ant Thanks!
I have merged the master and updated the PR.
The final changes done are:

correct exit codes to be non-zero when make steps fail in ql_symbiflow wrapper, like at: https://github.com/QuickLogic-Corp/symbiflow-arch-defs/blob/54803801d8f94a79f7b5c7b9ffa284a83182f5a2/quicklogic/common/toolchain_wrappers/ql_symbiflow#L568

correct error in usage of [ in bash if we use && in https://github.com/QuickLogic-Corp/symbiflow-arch-defs/blob/54803801d8f94a79f7b5c7b9ffa284a83182f5a2/quicklogic/common/toolchain_wrappers/ql_symbiflow#L266

correct checking expansion of *.v so that it doesn't throw an error if *.v is already expanded correctly at https://github.com/QuickLogic-Corp/symbiflow-arch-defs/blob/4acf609042f3b71c686a988440d926ed32e92d82/quicklogic/common/toolchain_wrappers/ql_symbiflow#L230

add explicit exit codes to all exit statements

minor aesthetic change in generated Makefile.symbiflow

Please review the final changes, if they look ok, we can merge them now, so that the latest arch-defs can be used for automated testing with correct exit codes.
We can debug the issues in the eos-s3 CI in parallel.
What do you think?

@coolbreeze413 I've managed to narrow down the issue with CI (I hope) See the linked PR.

@mkurc-ant Thanks! I think it looks good.
Let's wait for the CI in #711 to complete, and if it is green, merge that first, and then I will update this PR for remaining changes, and we can merge this next.

merged #711, and merged master here.
Final remaining changes in this PR:
The final changes done are:

correct error in usage of [ in bash if we use && in https://github.com/QuickLogic-Corp/symbiflow-arch-defs/blob/54803801d8f94a79f7b5c7b9ffa284a83182f5a2/quicklogic/common/toolchain_wrappers/ql_symbiflow#L266

correct checking expansion of *.v so that it doesn't throw an error if *.v is already expanded correctly at https://github.com/QuickLogic-Corp/symbiflow-arch-defs/blob/4acf609042f3b71c686a988440d926ed32e92d82/quicklogic/common/toolchain_wrappers/ql_symbiflow#L230

add explicit exit codes to all exit statements

minor aesthetic change in generated Makefile.symbiflow

@mkurc-ant : This PR is now green, and the remaining changes in the PR are simple ones.
Please review, and if ok, we can merge this one as well.

repo: QuickLogic-Corp/symbiflow-arch-defs

license: ISC


text:
Support for QuickPay API v10

ActiveMerchant (AM) currently supports QuickPay API v7 and we need to also support v10 - that is both versions should be supported at the same time. Which version to use should be configurable for every AM user.
I'm not sure how to do this. A Shopify guy mentioned that "AM requests a md5 checksum and it should be possible to use the same mechanism to ask for API-version".

already done

authors: benee ta


text:
[Feature Request] ability to disable the usage of @everyone, @here, and role mentioning in config

No one likes unwarranted @everyone pings, and anyone can do it with no permissions.

This is an issue with the webhook library it currently uses, not much we can really do sadly. This is fixed in the complete BlockBot rewrite that is being worked on.

repo: QuiltServerTools/BlockBot


text:
Feature: analysis jobs items crud

This pull request supersedes #288
This feature branch adds in support for Analysis Jobs' Items. In particular, this branch has the code, logic, and tests, for CRUD operations. It DOES NOT include actual integration with Analysis Jobs; that is when an AnalysisJob is created it should also create AnalysisJobsItems - that functionality will come in a later request.
This pull request also unifies the analysis results controller with the new analysis_jobs_items controller. All results, whether system or AnalysisJob generated are accessible via the same REST endpoint with same properties available.
This work lays out the foundation for resolving #192.
Fixes #274.

Coverage decreased (-1.2%) to 84.539% when pulling 931066b5eb30925e34e659bdff91e5b55abce764 on feature-analysis-jobs-items-crud into 16d1de08ec0ba134b14d9e6a6bbeaaa08b23e261 on develop.

Coverage increased (+0.4%) to 86.096% when pulling fbe08eede6c23fb316198760e23afa9816e637f5 on feature-analysis-jobs-items-crud into 16d1de08ec0ba134b14d9e6a6bbeaaa08b23e261 on develop.

authors: atruskie coveralls

repo: QutBioacoustics/baw-server


text:
Audio2Csv fails with certain characters in file name

audio2csv fails with the following characters in the file name. Below are the paths that I tried and the log files.
/temp/in/dir_/REC_C_20180616_185529🤷♂🤷♂_1_1.wav to /temp/out/
This failed, here is the log:
log_20181102T012216Z.txt
However, I tried it with different characters in the filename, and it worked
/temp/in/dir_/REC_C_20180616_185529_1_1.wav to `/temp/out/``
This worked, here is the log:
log_20181102T013828Z.txt
And I tried the following (only one of that character):
/temp/in/dir_/REC_C_20180616_185529🤷♂_1_1.wav
This failed, here is the log:
log_20181102T014439Z.txt

**Operating system: ** MacOS Sierra Mac Pro

AP.exe version: 18.10.2.6

The data used can be found: Y:\WesternGhatsCentralIndia\201809\SAT_MANG_3\Recordings\REC_C_001\REC_C_2018-06-16\REC_C_20180616_145526.wav (This was the file that was renamed with the bad character to test #201)
The command I used:
mono AnalysisPrograms.exe -l 7 audio2csv "/temp/in/dir_with_unicode__/REC_C_20180616_185529🤷♂_1_1.wav" "ConfigFiles/Towsey.Acoustic.yml" "/temp/out"
The config file I used:
Towsey.Acoustic.yml that shipped with that release.

Originally posted by @peichins in https://github.com/QutEcoacoustics/audio-analysis/pull/201#issuecomment-435245354

This is a problem with System.Drawing that occurs while drawing a line. Need to debug further.
We might be able to just bypass fixing this if we stop using System.Drawing - see #158

Another related but separate problem with the Windows Console is that because GDI is used to render Console’s text, and GDI does not support font-fallback, Console is unable to display glyphs for codepoints that don’t exist in the currently selected font!

https://blogs.msdn.microsoft.com/commandline/2018/11/15/windows-command-line-unicode-and-utf-8-output-text-buffer/

authors: atruskie peichins

repo: QutEcoacoustics/audio-analysis


text:
[Intention] Deprecate AppVeyor in favour of Azure Pipelines

We intend to deprecate AppVeyor and replace it with Azure pipelines.
New pipelines builds will allow testing on Mac, Linux, and allow for building containers.

Closing, completed somewhere in b5a43e8c2b02f6218d5d5df0552482373cb3115d...e8fd301082bcc2a51588bb004c04505854b18e75


text:
buildQueryString: decode URI + test

Description
When building a query string with buildQueryString,  decode URI components to get human readable urls, like in the actual Maps release.
Why
previsouly, buildQueryString would return an encoded representation of a string like admin:osm:relation:71525@Paris.

As buildQueryString is meant to build url-safe query strings, the encoding done by URLSearchParams is a feature. In what case do you want decoded values?

In order to keep the actual behavior.
Take for instance this url: https://www.qwant.com/maps/routes/?origin=admin:osm:relation:7444@Paris&mode=driving#map=11.98/48.8591710/2.3129699
urlSearchParams.toString() would return origin=admin%3Aosm%3Arelation%3A7444%40Paris&mode=driving%23map%3D11.98%2F48.8591710%2F2.3129699"

In order to keep the actual behavior.

would return origin=admin%3Aosm%3Arelation%3A7444%40Paris&mode=driving%23map%3D11.98%2F48.8591710%2F2.3129699"

Sorry, I still don't see the problem and what behavior wouldn't work with that.
buildQueryString is used to build URL parts, so it's is job to encode strings safely. If you want to rely on the URL values later, I understand you'd like have to decode them, but it should be done when reading it, like in parseQueryString.
But I guess I'm missing the point.

authors: G-Ray bbecquet

repo: QwantResearch/erdapfel


text:
长度外推超过4000个字符后会输出乱码

是否已有关于该错误的issue或讨论？ | Is there an existing issue / discussion for this?

[X] 我已经搜索过已有的issues和讨论 | I have searched the existing issues / discussions

该问题是否在FAQ中有解答？ | Is there an existing answer for this in FAQ?

[X] 我已经搜索过FAQ | I have searched FAQ

当前行为 | Current Behavior
输入长文本让模型进行总结
期望行为 | Expected Behavior
模型正常输出内容
复现方法 | Steps To Reproduce
用vllm推理框架，输入长文本让模型进行总结，文本长度超过四千左右时，模型会输出乱码，config.json中  "use_dynamic_ntk"和 "use_logn_attn"都为true，请问这种情况是什么原因导致的呢?还需要更改哪些配置吗
运行环境 | Environment
- OS:
- Python:
- Transformers:
- PyTorch:
- CUDA (`python -c 'import torch; print(torch.version.cuda)'`):

备注 | Anything else?
No response

您好，

vllm中有实现DynamicNTK，但使用的config有所不同，据称需要配置"rope_scaling": {
   "type": "dynamic",
   "factor": 2.0
}

vllm中实现的DynamicNTK与Qwen实现的不完全一致，对结果可能会有一定影响，参见此issue

2. DynamicNTK与Qwen实现的不完全一致，对结果可能会有一定影响，

好的，我试试，非常感谢您的回复

现在新版本0.2.4还有这个问题吗？

authors: PeterXiaTian jklj077 parkLGW

repo: QwenLM/Qwen


text:
docs: added an example for creating a dynamic Leaflet map

Added an example of a Leaflet map component, a route, props, and JSON and GeoJSON files to create an initial reactive map.
Overview

What is it?

[ ] Feature / enhancement
[ ] Bug
[ ] Docs / tests / types / typos

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Use cases and why

One use case

Another use case

Checklist:

[ ] My code follows the developer guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

looks great. after you finish the Requested Changes we can get it in

authors: PatrickJS gimonaa

repo: QwikDev/qwik


text:
titanfall 1 suport

Is it possible to add support in titanfall 1 ?

Duplicate of #73

authors: abarichello manotroll


text:
Update dialog

It will always shows the update dialog while starting the software, even though it is the newest version, how to solve this?

It must not be the newest version if it keeps showing the update dialog. But if it does, just click NO.


text:
Docker compose fixes

Small fixes:

fixed persistence path for monitors (enables data persistence between restarts for monitors)
reduced unnecessary Kafka logging
increased Kafka health check timeout
allow backend to query the Google play store
fixed gateway health check

I haven't seen any other timeouts, that's why it's just the Kafka containers.

Alright. I meant the kafka-2 and kafka-3 containers still have 5 s timeout. But as long as we have healthy containers i think it is not necessary.

authors: blootsvoets nivemaham

repo: RADAR-CNS/RADAR-Docker


text:
New test branch

Integrated google analytics

Next time please name the merge request properly (i.e. in this case add Google Analytics)

repo: RCSSA/RCSSA-Web


text:
[DBAAS-58] Updated the operator per the API doc

Description
Updated the apis and controllers per the updated API doc.
And updated the operator to use operator-sdk 1.8.0.
Verification Steps

N/A
Type of change

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

Checklist (Definition of Done)

[ ] All acceptance criteria specified in JIRA or in issue number have been completed
[ ] Unit tests added that prove the fix is effective or the feature works
[x] Documentation added for the feature
[ ] all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

This PR includes the changes from https://github.com/RHEcosystemAppEng/dbaas-operator/pull/11

repo: RHEcosystemAppEng/dbaas-operator


text:
feat: add tc recommendations to EXHORT

Integrate Trusted content  recommendations into EXHORT' response payload.

Enrich response payload with Trusted Content recommendations fetched from TC Service' /recommend endpoint
For each dependency' purl, if recommendation exists, add the corresponding recommendation purl.
If recommendations are not found, then response body of exhort should remain the same without changes.

Remark: TC service' endpoint -  /recommend is under ongoing development, so integration changes caused by it might follow.

I have one concern about the overall approach. Wouldn't it be simpler to call the trustedContent before the providers and then keep the response in the exchange so that in the response handling we can have a common code to aggregate individually not only for recommendations but also for remediations as there will be where we have the CVEs information.

I have one concern about the overall approach. Wouldn't it be simpler to call the trustedContent before the providers and then keep the response in the exchange so that in the response handling we can have a common code to aggregate individually not only for recommendations but also for remediations as there will be where we have the CVEs information.

Let's discuss it tomorrow.

@ruromero As discussed, all the changes that you've requested are here, Please review and approve.

authors: ruromero zvigrinberg

repo: RHEcosystemAppEng/exhort


text:
🛑 CEOTR Home Page loads is down

In b08911a, 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 01cb586 after 2 minutes.

repo: RKTowse/upptime


text:
🛑 CEOTR Home Page loads is down

In 1a48d76, 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 948ed7c after 45 days, 17 hours, 29 minutes.


text:
🛑 CEOTR Home Page loads is down

In 7e1d49f, 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 4acf5e9 after .


text:
🛑 CEOTR Home Page loads is down

In 373add4, 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 f8cbf16 after 2 minutes.


text:
🛑 CEOTR Home Page loads is down

In 897d533, 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 ee52549 after 2 minutes.


text:
🛑 CEOTR Home Page loads is down

In d24dfe9, 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 9d644b7 after 2 minutes.


text:
🛑 CEOTR Home Page loads is down

In f6f46e7, 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 897d4a8 after 2 minutes.


text:
🛑 Sensor Tracker login is down

In 91e2e3e, 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 242ae01 after 1 minute.


text:
🛑 CEOTR Home Page loads is down

In 1fb90ee, 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 d8c9312 after 2 minutes.


text:
🛑 Sensor Tracker login is down

In 83b4e28, 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 40edcbe after .


text:
🛑 CEOTR Home Page loads is down

In c4742e3, 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 3c5e53d.


text:
🛑 CEOTR Home Page loads is down

In aaadd63, 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 a3df702 after 2 minutes.


text:
🛑 Sensor Tracker login is down

In a6a4be8, 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 4454a48 after 1 minute.


text:
🛑 CEOTR Home Page loads is down

In 8ae6297, 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 69e75c0 after 2 minutes.


text:
🛑 CEOTR Home Page loads is down

In 6a066b7, 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 9bb0289 after 2 minutes.


text:
🛑 Sensor Tracker login is down

In 5a77fec, 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 938da9d.


text:
🛑 Sensor Tracker login is down

In 2c993e0, 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 1e79a3e after .


text:
🛑 Sensor Tracker login is down

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

HTTP code: 502
Response time: 106 ms

Resolved: Sensor tracker login is back up in 2a30102.


text:
🛑 Sensor Tracker login is down

In 873f99d, 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 988f570 after .


text:
🛑 CEOTR Home Page loads is down

In f57cd31, 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 a807eda after 42 days, 18 hours, 33 minutes.


text:
🛑 Sensor Tracker login is down

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

HTTP code: 502
Response time: 50 ms

Resolved: Sensor tracker login is back up in 4b7857f after 42 days, 20 hours, 5 minutes.


text:
Manual tests on comments making sure that comments get placed in the right place and are saved correctly.

Component and Data Design

already done


text:
[question] : Is this supported for ROS2 Humble ?

I am working on a project with ROS2 ( Humble ) and arduino, will this library work for Humble? The only other alternative I could find was  microROS but this library has some better readable code( similarity in syntax with ROS2) than it.

Does it work with ROS 2 Humble?

Plz if this library work for you let me know!
And for the alternative microROS it works with arduino uno ?

authors: caulesti lonebots moun20