Warning about removal of extras

Qiskit 0.44 (with terra 0.25) needs to have an warning about the fact that Qiskit 0.45 (with terra 0.45) will stop having application as extras. This entry is more of a reminder about that.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
16 unchanged lines in 4 files lost coverage.
Overall coverage increased (+0.06%) to 85.908%

Files with Coverage Reduction
New Missed Lines
%

crates/accelerate/src/sabre_swap/mod.rs
1
99.77%

crates/qasm2/src/expr.rs
1
93.76%

crates/qasm2/src/lex.rs
2
91.65%

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

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
71215

Relevant Lines:
82897

💛  - Coveralls

Let's leave this PR open as a reminder, but in practice we'll effectively need to completely rewrite the release note during the writing of the main prelude, so it might not make too much sense to actually merge it.
We also possibly need to discuss (if we haven't already) what extras we are going to make part of the qiskit package that aren't there yet - qiskit-terra has quite a few, some of which we might want to use this same opportunity to drop (with appropriate warnings).

I've included the basic contents here in: https://github.com/Qiskit/qiskit-metapackage/pull/1785 as part of the final metapackage release note. Starting in the next release Qiskit 0.45.0 we'll be doing everything from this repository.


feature-tabBar-width Handle tabBar width set in this.props.styles, re…

…nder indicator properly
Issue: Currently you are able to style the width of your topBar in the style prop, but the indicator doesn't adjust to the change.
// TabBar style prop
style: {
  backgroundColor: '#FFF',
  height: 50,
  left: '20%',
  width: '80%',
},

Sorry I couldn't get to this earlier. Can you rebase this?


Fix street retrieval with recent version of nominatim.

Thanks for all those changes :)
As you can see, this plugin is stalled since years (as we totally switched to import from BAN/BANO).


[LS] Fix several issues and add serveral completion/codeaction improvements

Purpose

Create function code action now supports creating undefined functions in start actions (when creating strands)
Create variable code action supports intersection types fully (it was fixed mostly by #30226, this includes addressing some edge cases)
Add completion support for init function in classes
Add completions for records (mapping constructor) at function parameters.

Fixes #29738
Fixes #29522
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Closing this to create a new PR since this fails due to a caching issue.


mux API: generate_new_seed

This method should be private, right?  @cjacoby Any objection to changing that prior to 1.0?

👍 no objection; I think it makes the Mux API less confusing


time.Parse month out of range

I want to parse string to time.Time
so, I use time.Parse :
start, err := time.Parse("2006-01-02 15:04:05", "2019-8-12 00:00:00")
then I got an error : parsing time "2019-8-12 00:00:00": month out of range

fixed,it should be 2019-08-12 00:00:00


First issue

Hello!
@dmalenik

[x] One
[x] Two
[ ] Three

So
My name is
Capital of

Hello
No!

Hello @dmalenik!

Left the comment

Hello world!


Employee   from saas hq

Most everything is in /employees directory and /actions. I copied over my /crm directory to yours just because I was in there using it as a reference for employee stuff. There seems to be fair bit of difference between our CRM directories bit it's not crucial. Mostly fluff.


[trace-agent] CLI support added for unofficially supported deprecated flags/switches

What does this PR do?

In PR https://github.com/DataDog/datadog-agent/pull/18492 we added backward-compatibility support for official flags that were now deprecated. Unfortunately, the unofficially supported --pid (single hyphen were the documented switches -pid) was left out. This PR adds support for it once again.
We also take the opportunity to fix a couple other flags so they remain backward-compatible even if only unofficially supported previously.
Motivation

Customer was impacted by using the unofficial --pid flag instead of -pid (both now deprecated).
Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Manually launch the trace-agent and make sure the old flags are still well supported:

-pid <file>
--pid <file>
-cpuprofile <file>
--cpuprofile <file>
-memprofile <file>
--memprofile <file>

As well as the newer ones:

--pidfile <file>
--cpu-profile <file>
--mem-profile <file>

Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[x] A release note has been added or the changelog/no-changelog label has been applied.
[x] Changed code has automated tests for its functionality.
[x] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[x] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

/merge

/remove


Performance: Faster replace tree

Right now, whenever a manipulation happens, the entire tree is replaced.
It would be better to only bother replacing nodes that are currently in the node cache.

I'm thinking this would create too much complexity for not much benefit. I'm going to close this for now as "won't fix".

The performance is actually becoming somewhat of an annoyance for me. It takes maybe ~5 mins to do a release of this library because the code manipulation is slow and I'm manipulating a large file (Node.ts).
I thought of how to solve this without too much complexity:

When inserting into the cache, make sure the parent already exists in the cache... if not, keep looping up the tree until a wrapped parent is reached.
When replacing the tree, only bother with children that have been wrapped previously.

So point #1 is what makes doing this very easy.
Additionally, it might be nice to add a .forget() method (or .destroy() method) to every node that will call .dispose() internally. That would allow people who need it to get maximum performance on large files. It's easy to do so might as well provide that option.

Implemented in 0.97.0 along with .forget(). I'm glad I ended up implementing this... it wasn't too bad and my releases are back to being pretty fast now. Some data on how fast my release script takes to run on my computer now:
==
setSyntaxKindOverloads code generation times
==
Original: 9min 38s
This change with forgetting nodes: 2min 21s
Overall increase: 346% faster

@dsherret I wrote a code generator using this library (to generate interfaces and classes for an external database mapping).  I've noticed that as the size of the code I'm generating grows, it seems to get exponentially slower.  In one project I'm using, my generated asset is up to about 5k lines (writing about 15 classes to a single file).
I'm sure that my approach has something to do with it.  For simplicity, I'm writing everything to a single file.
My code looks something like this:
let source = ast.addSourceFileFromStructure(config.outPath, {});
for(schema in retrieveSchemas()){
   let props = generatePropertyDef(schema)
   sourceFile.addInterface({properties: props, ...})
   let class = sourceFile.addClass({properties: props, ...})
   class.addConstructor()
   ...
}
source.save();

I've done some very simple profiling and it seems the vast majority of the time in spent in the addInterface & addClass methods.  The more properties that are passed it, the slower it goes.
Do you have any suggestion to how I might be able to speed this code up?  I'm sure I'm not using this library in the most efficient manor.

I'll reply back tomorrow (just going to sleep now). I added a bit of information here: https://dsherret.github.io/ts-simple-ast/manipulation/performance
In summary: the more nodes that become wrapped, the more nodes that need to be tracked and replaced between manipulations.
You should be able to get a decent performance boost by using those "forget blocks," or by manually forgetting nodes you don't need anymore. There's still lots of performance improvements that can be made internally in the library that I'll be working on over the next while though.

Actually, it doesn't seem like myClass in the example above has a forget() method?


Suggestion - Rename IFormFile.OpenReadStream to IFormFile.GetInputStream()

In MVC5 app, we were passing around HttpPostedFileBase.InputStream reference from controller action to a helper, which uploads files to remote storage (and generates CDN links etc.).
With MVC Core, we are achieving the same by using IFormFile.OpenReadStream() which returns the reference to the underlying stream.
It would probably make sense to have this method renamed to GetInputStream() or GetReadStream to depict what it returns.

We're not going to be renaming this method at this point.

Thanks @davidfowl. With File.OpenRead analogy, OpenReadStream probably is a better choice. I thought I should suggest anyway. 😄


sc-uws vs uws

If I'm using sc-uws can I safely remove uws and stop using it?

Yes. Essentually sc-uws is just a fork of the uws, with no python bindings and better errors :bowtie:


Made RequestReadTimeout and whether to sendState configurable

Made RequestReadTimeout and whether to send State configurable.

Codecov Report

Merging #1034 into master will increase coverage by 0.07%.
The diff coverage is 91.66%.

@@             Coverage Diff              @@
##             master    #1034      +/-   ##
============================================
+ Coverage     77.06%   77.13%   +0.07%
- Complexity      898      903       +5
============================================
  Files           106      106
  Lines          3239     3249      +10
  Branches        449      450       +1
============================================
+ Hits           2496     2506      +10
  Misses          567      567
  Partials        176      176

Impacted Files
Coverage Δ
Complexity Δ

...rk/cloud/config/client/ConfigClientProperties.java
89.91% <100%> (+0.72%)
42 <4> (+4)
:arrow_up:

...fig/client/ConfigServicePropertySourceLocator.java
64.49% <75%> (+0.52%)
23 <0> (+1)
:arrow_up:

Continue to review full report at Codecov.

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

Also authorization property is deprecated. Is it a good time to remove it?

Yes, it's a good time to remove authorization.

Let me know , if we need to add any documentation for the new properties.

Yes please add documentation for the new properties

@spencergibb are the changes alright?


[Cloud functions>] Unable to call function FUNCTION_NAME

Describe the bug
Getting "Unable to call function FUNCTION_NAME" when running Flutter code on iOS device.
Expected behavior
The function returns the output of a cloud function routine.

Closing this due to lack of clarification. If still experiencing the issue, please create a new one with steps on how to reproduce.


First non-stable release.

Considering API to be stable and now merging branches. Check Tags inside dev's release for further information.

Merging dev into master, first stable pre-release. working again on dev. Master's contains the last stable version, it's functional but not enogh to be used on production or being import. Feel free to contribute!


onevm backup do not validate all required attributes

Description
only the existance of the backup info and the backup frequency is validated
https://github.com/OpenNebula/one/blob/051b36e0d91746d8e7ffc77cfb365d36e337ec9e/src/oca/ruby/opennebula/virtual_machine_ext.rb#L266
To Reproduce
Create a VM Template with backup frequency but no marketplace selected
Run onevm backup $VMID
$ onevm backup 1 --market 100
2021-04-16 13:03:15 INFO  : Saving VM as template
2021-04-16 13:03:15 INFO  : Powering off VM
2021-04-16 13:03:15 INFO  : Processing VM disks
2021-04-16 13:03:24 INFO  : Adding and saving regular disk
2021-04-16 13:03:24 INFO  : Processing VM NICs
2021-04-16 13:03:24 INFO  : Updating VM Template
2021-04-16 13:03:24 INFO  : Powering on VM
2021-04-16 13:03:35 INFO  : Importing template 4 to marketplace
2021-04-16 13:03:35 INFO  : Processing VM disks
2021-04-16 13:03:35 INFO  : Adding disk with image 4
2021-04-16 13:03:35 INFO  : Importing image to market place
2021-04-16 13:03:35 FATAL : Wrong type NilClass. Not allowed!
2021-04-16 13:03:35 FATAL : #<RuntimeError: Wrong type NilClass. Not allowed!>

Expected behavior
Expected to have an error raised that the backup could not be executed due to reason
the expected error reason for this case should be "missing marketplace id"
Details

Affected Component: [ruby bindings]
Hypervisor: [KVM]
Version: [6.0.0]

Additional context
As you could see in the pasted example, the --market $MARKET_ID argument doesn't work too... (the NilClass is the missing binfo[:market]...)
Also, should this do clean up after such failure? In the above example, there are VM Templates and Image files left behind...
Also, I'd expect the --verbose argument to provide true verbose logging...

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

PRs to merge in 6.0 and master:

code
docs


Check DirectiveInfo shared pointer is valid.

Issue #, if available:
SampleApp crashed by AudioPlayer invalid shared_ptr.
Description of changes:
Check DirectiveInfo shared pointer is valid.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

my bad.


🌋 E|F ➾ Simple GUI Flow for Contract Origination

Product Board Link
No response
🚥 Status

[X] 🔮 Product/Feature Design
[ ] ✍🏻 Architecture/Implementation Planning
[ ] 🏗 Under Construction
[ ] ⛳ Feature Complete
[ ] ⛵ GTM / Release

✅ To Do
No response
📐 Feature Description
Taqueria should provide a dead simple graphical interface through which users can easily originate a contract to a sandbox or testnet. Ideally, they will be able to select from a list of known testnets, provide their initial storage, and have a faucet file in the project directory
For feature design and feedback, please reach out to @claudebarde!
🚩 Problem or Use Case
Even experienced developers are currently using the web IDE's for Ligo/SmartPy for contract origination to a testnet because they make it so easy. Taqueria should provide something at least that simple and powerful
🔭 Scope
🏎 In Scope:

Implementing a new UX/UI, or modifying/extending an existing one to support easy originations
Exploring and implementing network discovery or shipping with a know list
Providing multiple ways to provide storage
E2E UX integration with existing UI (displaying operation/result onchain would be ideal)

🙅♂ Out of Scope:

Work on CORE

⚖ Acceptance Criteria
✨ Features:

[ ] Prototype of UI interface with basic origination flow

🔗  Related Issues and Subtasks
No response
🦄 Sizing
5
Code of Conduct

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

@claudebarde, if you have any particular requests or ideas for this feature, please add them to the ticket!


Add no-analytics flag

I would suggest adding the --no-analytics flag so CI runs don't skew their analytics results. If you agree and merge this note that when v0.26.0 is released the --no-analytics=true flag has been changed to just --no-analytics.

Good suggestion! I will probably add a condition later on once v0.26 is released.


Update MIERUNE LLC -> MIERUNE Inc.

Could you please update the name in the "Sustaining Member" page from "MIERUNE LLC" to "MIERUNE Inc." ?
Page URL:
https://www.qgis.org/en/site/about/sustaining_members.html
Cf
https://www.mierune.co.jp/aboutus?lang=en

Hi @Yfuruchin - thank you for the correction.
The sustaining memberships are generated from a database. I just corrected the entry in our database. In a couple of hours it should be updated in the website - there is a cronjob for regular exports from the DB for the website.

Done --> https://changelog.qgis.org/en/qgis/member/drvbrt/


Feat/test non deployed pool

Description
Add an explicit unit test for the non-deployed pool case
Limitations & risks
Possible diff with Sepolia bug (https://www.tdly.co/shared/simulation/2c1a5852-4360-4e80-ad44-ade065dd9289f): Anvil having a difference for empty address handled in try/catch block, difference in how these are handled between various solc version
Check-list

NA Tests are covering the new feature
[x] Code is natspec'd
[x] Code is linted and formatted
[x] I have run the test locally (and they pass)
[x] I have rebased to the latest main commit (and tests still pass)

Interactions
These changes will impact the following contracts:

Directly:
na
Indirectly:
na

screenshot: call correctly revert and default to returning the weight and no delegate address


Feat/periodic aggregation

Summary
Removed the database implementation from project-daedalus2.
Details
Moved the currently working database implementation back to telestion-core and updated config.json
CLA

[x] I have signed the individual contributor's license agreement and sent it to the board of the WüSpace e. V. organization.

We can merge this PR to have a clean working database implementation, but now again back in telestion-core.
I fixed the imports and changed the config.json.
If the PR in telestion-core is merged and daedalus2 uses the new telestion-core, everything should be working as before.

And should we resolve the merge conflicts together in the near future? ^^

The indentation is all over the place.
I think, we need some sort of an indentation check for the application site of the project...
For now, can you please indent your modified files in a persistent way?

I don't know where that indentation is coming from, because in my editor everything is looking fine.
Is there any settings issue on my side?

@fussel178 i reviewed the requested changes and tried to fix the indentation. Please see, if the indentation is now correct. Seemed to be a problem with my editor conflicting with the projects .editorconfig
I also resolved the conflicts, because the only conflicts were the correction of the imports for our database verticles, which should be in telestion-core.

DO NOT MERGE:
Blocked until https://github.com/wuespace/telestion-core/pull/273 is both merged and released.

Closing, because code now resides in https://github.com/wuespace/telestion-extension-mongodb.


Lifx White 800 not working

Describe The Bug:

It looks like the Lifx white 800 is not supported
To Reproduce:

Have set up adaptive lighting in the home app. No colour changing. Tried to change colour manually in the app and no changing either. Lifx app still changes colour.
Expected behavior:

Expect to see colour change over the day
Logs:
DEBUG - 58000014f35ce128d073d510844600004c49465856320054e87248d87b80da166b00000000000000ffff64190000ffff46616d696c7920526f6f6d204c616d70000000000000000000000000000000000000000000000000 from <IP_ADDRESS>
DEBUG - 24000034f35ce12800000000000000000000000000000054000000000000000002000000 to <IP_ADDRESS>
DEBUG - 29000014f35ce128d073d510844600004c49465856320054e8caa9f07c80da1603000000017cdd0000 from <IP_ADDRESS>
DEBUG - 29000014f35ce128d073d510844600004c49465856320054e81292f27c80da1603000000057cdd0000 from <IP_ADDRESS>
DEBUG - 24000014f35ce128d073d510844600000000000000000055000000000000000065000000 to <IP_ADDRESS>
DEBUG - 58000014f35ce128d073d510844600004c49465856320055e8644e027d80da166b00000000000000ffff64190000ffff46616d696c7920526f6f6d204c616d70000000000000000000000000000000000000000000000000 from <IP_ADDRESS> ```

**Plugin Config:**

```json

{
    "name": "Lifx Plugin",
    "duration": 0,
    "brightnessDuration": 500,
    "colorDuration": 500,
    "default": "<IP_ADDRESS>",
    "broadcast": "<IP_ADDRESS>",
    "lightOfflineTolerance": 3,
    "messageHandlerTimeout": 45000,
    "resendPacketDelay": 150,
    "resendMaxTimes": 3,
    "updates": true,
    "debug": false,
    "autoDiscover": true,
    "platform": "LifxPlugin"
}

Screenshots:

Environment:

Plugin Version: 0.2.2
Homebridge Version: 1.4.0
Node.js Version: 16.14.0
NPM Version:  8.3.1
Operating System: macOS

Hi,
could you help me a little further to understand exactly where the problem lies.
A screenshot of this would already help me a lot:

How's this?

I have the original box, Model BUL-11-A19e27-W. They are old, pre-homekit. Lifx app says firmware is up to date. and is v1.22 on the lifx app. The app advanced setting has Advanced Kelvin Control off. Anything else?

Oh, and to confirm, my Lifx mini cool is working absolutely fine - thanks v much.

Hi, can I provide any more information?

Hi @thefern69,
still having this issue with the current version of the plugin?
Let me get this straight. You can't change the color temperature in the home app? Only brightness? Is that correct?

@calvarium apologies for the delay in replying. Yes, it looks like it is working fine. Thanks v much for your help and for the plugin - keep up the good work.


Add PASTE to Scanpy ecosystem.

LGTM!
Don't worry about the test failures, those are due to a networkx update changing how plots look, which we'll deal with.


[Design] Packaging and project management

Robocop and Robotidy use 'old' style packaging tools such as setuptools (with setup.py), twine and nox for poor version of the environment management. We should decide on and use more modern ways of maintaining the package.
The initial choice is uv: https://docs.astral.sh/uv/
Similarly to ruff, it's rapidly growing tool (thanks to start up invenstors) that already matches existing popular model tools such as poetry. With similiar features it additionally offers better performance and support for official PEPs (such as group dependencies).

The basic structure will be:
src/robocop
docs
tests
pyproject.toml file - all project related configuration

Main difference is that package source will be stored under src/ directory.


fix: add migrations

Django use BigAutoField as primary key now.

@ramwin Thanks for the contribution! Can we also address this lint failure?

HINT: Configure the DEFAULT_AUTO_FIELD setting or the DynamicModelsConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.db.models.BigAutoField'.

I added the DEFAULT_AUTO_FIELD config, how can I test it and restart the workflows?


Fix copying snippet id to clipboard for Chrome

Patch to fix the issue that Chrome can't copy to the clipboard unless the document has focus, by waiting until after writing to the clipboard has finished to create the alert window.
Forum post: https://forum.babylonjs.com/t/introducing-the-gui-editor-alpha/24578/35

Oops, I forgot to add a line to the What's New Update. I'd add it but I'm not sure if I should add it to the top of the GUI section or if maybe a new GUI Editor section is going to be created?


Changes to fix many failing tests for MySQL and PostgreSQL

Hi @enebo
Here are more changes to fix many AR tests.
Also, Rails 7.1 introduced  and new config to handle strict strings for SQLite which the jdbc driver does not support it.
I open a feature request ticket in their repo.
https://github.com/xerial/sqlite-jdbc/issues/1153

@JesseChavez The other thing pending is another issue on sqlite-jdbc asking to remove mandatory dependency for slf4j.  That is preventing us to be at the latest version.


Remove Python interdependency (Fixes #1808)

Description

[x] Source branch in your fork has meaningful name: python-interdependency

Installing jsbeautifier and cssbeautifier at the same time fails, because the cssbeautifier setup.py tries to
import jsbeautifier.__version__ (which is not installed at that time).
As long as both are separate packages, it makes sense for them to have their own version information (even if they are kept in sync).
This way, the packages can be installed separately and in any order without problems.
Fixes Issue: #1808, https://github.com/thp/urlwatch/issues/526
Before Merge Checklist
These items can be completed after PR is created.
(Check any items that are not applicable (NA) for this PR)

NA JavaScript implementation
[ ] Python implementation (NA if HTML beautifier)
NA Added Tests to data file(s)
NA Added command-line option(s) (NA if
[ ] README.md documents new feature/option(s)

..and apart from the interdependency fix, this is more "correct" (because the installed jsbeautifier version could be a different version than the installed cssbeautifier version, right now it will always show the jsbeautifier version for cssbeautifier too, even if cssbeautifier is in fact newer or older).

Gotcha. I'll give that a shot as the manual version still gave me trouble. Definitely something upstream.
$ python3 -m pip install jsbeautifier
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting jsbeautifier
  Using cached https://www.piwheels.org/simple/jsbeautifier/jsbeautifier-1.11.0-py3-none-any.whl
Collecting six>=1.13.0 (from jsbeautifier)
  Downloading https://files.pythonhosted.org/packages/ee/ff/48bde5c0f013094d729fe4b0316ba2a24774b3ff1c52d924a8a4cb04078a/six-1.15.0-py2.py3-none-any.whl
Collecting editorconfig>=0.12.2 (from jsbeautifier)
  Downloading https://www.piwheels.org/simple/editorconfig/EditorConfig-0.12.2-py3-none-any.whl
Installing collected packages: six, editorconfig, jsbeautifier
  Found existing installation: six 1.12.0
    Not uninstalling six at /usr/lib/python3/dist-packages, outside environment /usr
    Can't uninstall 'six'. No files were found to uninstall.
Successfully installed editorconfig-0.12.2 jsbeautifier-1.11.0 six-1.15.0

$ python3 -m pip install cssbeautifier
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting cssbeautifier
  Using cached https://files.pythonhosted.org/packages/0f/64/f3cdac9461be42f6c359810ba4cbe23363d1edfafad7a3d49b5fe8a58d2a/cssbeautifier-1.11.0.tar.gz
    Complete output from command python setup.py egg_info:
    running egg_info
    creating pip-egg-info/jsbeautifier.egg-info
    writing pip-egg-info/jsbeautifier.egg-info/PKG-INFO
    writing dependency_links to pip-egg-info/jsbeautifier.egg-info/dependency_links.txt
    writing entry points to pip-egg-info/jsbeautifier.egg-info/entry_points.txt
    writing requirements to pip-egg-info/jsbeautifier.egg-info/requires.txt
    writing top-level names to pip-egg-info/jsbeautifier.egg-info/top_level.txt
    writing manifest file 'pip-egg-info/jsbeautifier.egg-info/SOURCES.txt'
    error: package directory 'jsbeautifier' does not exist

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-35u12eo0/cssbeautifier/

@thp
Made one additional change related to the release script, but otherwise this looks good to me.

Thank you for the fix :)


Vue.js not detected when app loads asynchronously?

This may be a known limitation of the extension, but let me explain my situation.
I've got a "classic" web app and I want to start replacing pages/sections with Vue. I have a page where, on a button click, an AJAX request is made to load some additional content which appears over top (the AJAX call and DOM addition is taking place via jQuery). The content of this overlay is what I'm looking at replacing with Vue and I have it working in development. vue.js itself (the library) is loaded on every page, but a Vue app is only initialized as a result of this AJAX request.
The Vue.js extension never detects Vue. Is this because it's loading asynchronously and isn't present when the page first renders? Is there any way to give the extension a kick and have it try to detect an app after the page has loaded?
Other things that could be causing an issue:

vue.js is concatenated along with all my other JS in one application.js file
This JS file is loaded in the , not in the

I'm using the full vue.js file from the distro, not the min so I should be development mode.
Thanks for any help!

Does clicking the refresh button work? if not, could you provide a simple repro on an HTML file, please?

Nope, refresh doesn't help.
Since the setup involves making an Ajax request to start Vue, it might be hard to reproduce in a single HTML file. I might be able to put something together on jsfiddle, so at least you'd have all the pieces, but I've never seen the Vue devtools work there. But, you could copy the pieces and run them locally.
Are you a Ruby guy? I could probably put together a single-file Sinatra app that does everything...

@posva Like I say, maybe this is completely normal behavior and it's just my implementation of Vue on this page—does the toolbar constantly check the page after load to see if a Vue instance has been initialized at any point in the future? Or does it just make one check at something like DOMLoaded and then give up?

no, please, post a boiled down html file, you should be able simulate async
with setTimeout 😉
On Thu, Nov 16, 2017 at 8:32 PM Rob Cameron<EMAIL_ADDRESS>wrote:

@posva https://github.com/posva Like I say, maybe this is completely
normal behavior and it's just my implementation of Vue on this page—does
the toolbar constantly check the page after load to see if a Vue instance
has been initialized at any point in the future? Or does it just make one
check at something like DOMLoaded and then give up?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-devtools/issues/455#issuecomment-345037389,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAoicdoXpuwz0bJBFrqAiZWumHeTYyFfks5s3I3agaJpZM4Qcew0
.

--
Eduardo San Martin Morote

@posva Done!

    <title>Vue Test</title>

Lorem ipsum dolar sit amet...

It's working correctly for me. I think you just need to hit the refresh button. It checks at the beginning once but sometimes you need to use the refresh button 🙂

Ahh, interesting! So if I already have Chrome devtools open when the page loads, and the Vue app starts, it doesn't show anything. However, if I close and then re-open devtools it appears—I normally have devtools open all the time so I never thought about it.
I made a screen recording to prove I'm not crazy: http://recordit.co/0XMXOaHftQ
That works for me, now I know, thanks!

oh, yeah that's also possible. You have to open the devtools after you load the page, sorry, didn't think about sayinng that 😅


Error with extension modules in cryptography package when compiling in --module mode

Environment Details
Nuitka version, full Python version, flavor, OS, etc. as output by this exact command.

python -m nuitka --version

1.8.3
Commercial: None
Python: 3.11.5 (main, Sep 11 2023, 13:54:46) [GCC 11.2.0]
Flavor: Anaconda Python
Executable: /home/gustavo/miniconda3/envs/compile/bin/python
OS: Linux
Arch: x86_64
Distribution: Ubuntu (based on Debian) 22.04.3
Version C compiler: /usr/bin/gcc (gcc).

How did you install Nuitka and Python

I am using conda 23.7.4.
I created a new env with conda create -n 'compile' 'python~=3.11', resulting in Python 3.11.5.
I followed up by installing Nuitka through pip with pip install nuitka, resulting in nuitka 1.8.3 (as above).

The specific PyPI names and versions

python -m pip freeze

cffi==1.16.0
cryptography==41.0.4
Nuitka==1.8.3
ordered-set==4.1.0
pycparser==2.21
zstandard==0.21.0

MWE

Create a file called mymodule.py with the following content:

from cryptography import x509
print(x509)

Check it works properly. Run:

python -c 'import mymodule'

It should print the following:
<module 'cryptography.x509' from '.../miniconda3/envs/compile/lib/python3.11/site-packages/cryptography/x509/__init__.py'>

Compile mymodule.py as with Nuitka:

python -m nuitka --module --include-package=cryptography mymodule.py

This will output the following:
Nuitka-Options:INFO: Used command line options: --module --include-package=cryptography mymodule.py
Nuitka:INFO: Starting Python compilation with Nuitka '1.8.3' on Python '3.11' commercial grade 'not installed'.
Nuitka:INFO: Completed Python level compilation and optimization.
Nuitka:INFO: Generating source code for C backend compiler.
Nuitka:INFO: Running data composer tool for optimal constant value handling.
Nuitka:INFO: Running C compilation via Scons.
Nuitka-Scons:INFO: Backend C compiler: gcc (gcc).
Nuitka-Scons:INFO: Backend linking program with 78 files (no progress information available for this stage).
Nuitka-Scons:INFO: Compiled 77 C files using ccache.
Nuitka-Scons:INFO: Cached C files (using ccache) with result 'cache hit': 77
Nuitka:INFO: Keeping build directory 'mymodule.build'.
Nuitka:INFO: Successfully created 'mymodule.cpython-311-x86_64-linux-gnu.so'.

And will generate two output files: mymodule.cpython-311-x86_64-linux-gnu.so and mymodule.pyi.

Try to run the Nuitka compiled module. Move the output files to another directory (lets call it binaries) and run in that directory:

python -c 'import mymodule'

This will output the following:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File ".../binaries/mymodule.py", line 1, in <module mymodule>
    from cryptography import x509

  File ".../binaries/cryptography/x509/__init__.py", line 7, in <module cryptography.x509>
  File ".../binaries/cryptography/x509/certificate_transparency.py", line 11, in <module cryptography.x509.certificate_transparency>
ModuleNotFoundError: No module named 'cryptography.hazmat.bindings._rust'

Extra Info.
The cryptography package uses Rust bindings for this module. I guess the error is related to Nuitka not including the file .../miniconda3/envs/compile/lib/python3.11/site-packages/cryptography/hazmat/bindings/_rust.abi3.so in the output file mymodule.cpython-311-x86_64-linux-gnu.so.

When compiling to a module or a package, you should not include other packages, certainly not ones that use extension modules, that will just not work.

@kayhayen thanks for the clarification.
To make sure I understood it, the proper way to do it would be to compile mymodule.py as a module without --include-package=cryptography and then just make sure to have cryptography in the python environment which will eventually import the compiled version of mymodule?
Thanks!

Yes, building a wheel will be your best choice. Create one first (but not with poetry as that doesn't work yet) without Nuitka and enable it as described in the User Manual. Wheels are also a standard for deployment wheels with data files, etc.


where is the predict_batch option?

there's no "predict_batch" option in the web interface...

models/{model_name}/predict_batch (POST)
Performs inference on specified model and a list of images, and returns bounding boxes

The predict_batch is not visible on the swagger interface but a request can be sent to that endpoint using requests in python or any other suitable method (curl, etc..)
The input for this endpoint are:
model_name :str and
input_data : List[UploadFile]

in what format the list of images should be? can you be more specific?
and if I want to run inference on the entire batch, something like 100 pictures, in order to compare the performance of two trained nets (two weight files). is this the right tool to compare performance?

The format should be UploadFile please refer to official fastapi doc. https://fastapi.tiangolo.com/tutorial/request-files/
If you want to compare 2 models you can use this method or if you run into trouble you can write a script that send a request to /detect or /predict_image endpoint for each image and then compare the output of both.


deprecate legacy methods

What does this expire date mean in qtt? When I do a search over the code I see 17 instances of deprecated methods with expired deprecation date but they still exist.
The commit seems out of date due to another commit earlier. Rebase is needed.

Before the specified data the decorator will issue a warning, after the specified data it will throw an error. @QFer


Panning property of WaveChannel32 not working as expected

I'm building an application where the Pan property of a WaveChannel32 is controlled by a WPF slider control.
The WaveStream that feeds the WaveChannel32 reads from a stereo 512kbps .wav file and the WaveChannel32 is added to a MixingSampleProvider (there are multiple tracks that have independent panning controls).
The slider has range -1 to 1. When the slider is centered (pan=0), the result is as expected. However, if the slider is moved slightly in either direction, the sound is panned almost completely in that direction. The desired effect is smooth panning from left to right.
I've thought about having two mono audio sources for each audio source where one is panned all the way left and the other to the right and then having the pan slider simply control the volume between the two. I hope there's a better solution than that.

WaveChannel32 is a very old class that I only leave in NAudio because so many old tutorials suggest using it. But the preferred way is to use PanningSampleProvider which has a configurable panning strategy so you can get the exact behaviour you want. There are four strategies in the box plus the ability to create your own.

That works, Thanks!


Fixed #32646 -- Add request.json() shortcut

It would be nice to have a request.json() shortcut.
https://code.djangoproject.com/ticket/32646

Closing as per ticket.


sticky truncate the document/flashy document when using a sidebar

my top sticky navbar was working perfectly until i introduced a right overlay sidebar. the problem is the sticky module somehow setting the height of the pusher incorrectly in a way which hide a small portion of the page bottom content. the sticky trigger this message " Context has padding, specifying exact height for container ".
in a very short document it create a flashy document when scrolling.
my html structure

            ....

    ...

 ...

js
$('.mobile-menu')
	.sidebar()
	.sidebar('setting', 'transition', 'overlay')
	.sidebar('attach events', '.mobile-menu-trigger');

$('.ui.sticky').sticky({
	context: '#sticky-wall',
});

i didn't change any css for the pusher and sticky expect the z-index property.
once i remove the sidebar structure it works properly again, any clues ?

by removing the ' overflow: hidden ' from the pusher solved the problem, any thoughts ?

Hi @MazenDesigns, sorry for the delay. I’ll take a look at it if you create a test case—you can fork this JSFiddle.


Signposting for incomplete withdrawals needs improvement

View Withdrawals toast button only takes me to portfolio page and not to the withdraws table

It would be good if it opened the withdraws tab/table
Also all of this is changing with the work on the new transaction list, and we need to make sure this stuff is still surfaced clearly.

This will be covered by Matt's transaction list PR


Give arguments like -e to machine for swarm containers (proxy environment)

Hi,
I didn't find an issue about that, and it's my first post, sorry if it's already exists or if the issue is not "right".
Problem:
My problem is I start VM's using docker-machine in proxy environment, so my containers need some http_proxy to work.
When i start my containers, i put these variables, but if I want to use docker-machine --swarm, my swarm containers won't have these variables, so for example I can't use the token discovery system (cause they won't have internet).
Solution:
For example it could exist an option for docker-machine to specify swarm containers options: docker-machine create ... --swarm --swarm-parameters -e http_proxy=myproxy
Will start swarm agent with the -e variable.
Thanks for helping/advices.

Is it what engine-opt does ?

You are asking for preset environment variables to be passed to each container upon launch?  Machine doesn't do that currently nor do I think it should.  That is a container launch time setting.
--engine-opt allows setting Docker Engine options -- i.e. storage backend, graph directory, etc.

So i should not use --swarm when i create my machine and start my swarm containers by myself ?

Even if you run swarm by itself it still will not pass a default environment variable for every container.  That would be in the system that launches containers.  I'm not sure I'm fully understanding your question.  Are you trying to set a host level environment variable or just pass a set of default variables to each container?

I don't want that docker-machine does it for every containers, just for the swarm containers when i use --swarm.
I understand what you understood, i want my variable for the swarm containers themselves, not for the containers that i start in the cluster (for that as you said i do it myself).
The variables are just for my swarm agents & swarm managers containers.
If I start my swarm containers by myself on my machines, i can give my variables to the docker deamon, if I use --swarm, I can't right ? Cuase docker-machine does the "docker run swarm" for me.

Ah I see.  So just allowing to pass environment variables to the Swarm containers.  I don't see huge objections to this.
/cc @nathanleclaire thoughts?

So just to be clear, you want to set HTTP_PROXY for only the Swarm containers, not every container? Why not every container, out of curiosity?

Yup my need is for only the Swarm containers.
Actually I may need it for every container, but for the containers I start myself I can do it by myself, the problem is I can't use the --swarm option (with token discovery method) if I can't tell to docker-machine this variable, I have to start my swarm containers by myself, and I suppose it's a little bit sad to do something manually when docker-machine is also able to do ^^

I think this falls into the general class of issues where specifying HTTP_PROXY for the daemon is needed.  Do you agree @pacaletx @ehazlett ?

It's in the same area yes.

I would like to configure it for all containers.  Is that easier to do?

I would like to configure it for all containers. Is that easier to do?

If you're going to be using such a wide-ranging proxy, why not set it at the firewall level?

I don't have control of the firewalls but I do of the servers.  I agree with your statement that the specify HTTP_PROXY for daemon is needed

I also would like to be able to give swarm environmental variables.
For example: https://github.com/gliderlabs/logspout allows ignoring logging from individual containers based on environmental variables. I do not want the swarm logs to pushed up.

We now have a PR merged into master for this.  All engine environment variables --engine-env, will be propagated to the Swarm containers as well.


{Storage} GA release for --allow-blob-public-access and --min-tls-version

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

add to S173


Add an EVMBridgedData View in MetadataViews

Instructions
Issue To Be Solved
Need an EVMBridgedData view to contain the information of this token on the EVM side.
Suggest A Solution
Example:
access(all) struct EVMBridgedData {

        /// The EVM contract address of the corresponding ERC20 contract address
        ///
        access(all) let contractAddress: EVM.EVMAddress

        /// The Cadence type associated with the ERC20 contract address
        ///
        access(all) let associatedType:Type

        init(address: EVM.EVMAddress, type: Type) {
            self.contractAddress = address
            self.associatedType = type
        }
}

It is best to implement this View in Templates:
https://github.com/onflow/flow-evm-bridge/tree/main/cadence/contracts/templates
Context
Discord conversation:
https://discord.com/channels/613813861610684416/1240279845473226853

Thanks for this suggestion! Is the intention for this view to be used solely by bridged NFT/tokens?
I ask because any existing Cadence project would not be able to implement this view until their bridged EVM address is known, in which case they would need to update their contracts. But if the intention is to determine if an asset is onboarded to the bridge and therefore "bridgeable", then we can't rely on projects to do so in a timely manner or really at all, defeating the reliability of this view as a proxy for that info.
Another consideration - there is the potential that projects at some point create their own self-rolled bridges. In that case, which EVM address does the project list - the bridge-deployed EVM address or the project-deployed EVM address served by the self-rolled bridge?
What I would hate to have happen is for us to introduce a standard view that implies it can be used as a source of truth for state that's actually validated elsewhere. Or alternatively that the view's data can be taken optimistically and validated against what we currently call ground truth only to end up in future where the source of that truth changes with no way to redirect that validation path.
For instance, let's say I've resolved this view on some NFT - how do I know that it's true? I could ask the bridge, is this type and EVM contract associated? But what if the developers decide to create their own bridged NFT and provide an their bridge's EVM address? Then I ask the public infrastructure bridge the same question and get back false...the generalized validation pattern has proven to be unreliable.
That's not to say I'm against this view, just trying to think through any implications. If we introduce this view, I think it's also important that we include verification pattern that does not rely on the central bridge.
Instead of asking the bridge, I could just ask the listed EVM contract for its associated type (or type identifier). This means I wouldn't have to rely on any bridge for validation because the two sides just point to each other.
For instance, take the view above with a solidity interface:
interface ICrossVM {
    function getCadenceIdentifier() external view returns (string);
    function getCadenceContractAddress() external view returns (string);
}

This could also work against any imposter contracts in a way that prevents reliance on any bridge in particular. The contract above mirrors the existing ICrossVM.cdc contract interface used in the bridge templates, something I meant to implement in the bridged EVM contracts but didn't end up doing.

Thanks for this suggestion! Is the intention for this view to be used solely by bridged NFT/tokens?
I ask because any existing Cadence project would not be able to implement this view until their bridged EVM address is known, in which case they would need to update their contracts. But if the intention is to determine if an asset is onboarded to the bridge and therefore "bridgeable", then we can't rely on projects to do so in a timely manner or really at all, defeating the reliability of this view as a proxy for that info.
Another consideration - there is the potential that projects at some point create their own self-rolled bridges. In that case, which EVM address does the project list - the bridge-deployed EVM address or the project-deployed EVM address served by the self-rolled bridge?
What I would hate to have happen is for us to introduce a standard view that implies it can be used as a source of truth for state that's actually validated elsewhere. Or alternatively that the view's data can be taken optimistically and validated against what we currently call ground truth only to end up in future where the source of that truth changes with no way to redirect that validation path.
For instance, let's say I've resolved this view on some NFT - how do I know that it's true? I could ask the bridge, is this type and EVM contract associated? But what if the developers decide to create their own bridged NFT and provide an their bridge's EVM address? Then I ask the public infrastructure bridge the same question and get back false...the generalized validation pattern has proven to be unreliable.
That's not to say I'm against this view, just trying to think through any implications. If we introduce this view, I think it's also important that we include verification pattern that does not rely on the central bridge.
Instead of asking the bridge, I could just ask the listed EVM contract for its associated type (or type identifier). This means I wouldn't have to rely on any bridge for validation because the two sides just point to each other.
For instance, take the view above with a solidity interface:
interface ICrossVM {
    function getCadenceIdentifier() external view returns (string);
    function getCadenceContractAddress() external view returns (string);
}

This could also work against any imposter contracts in a way that prevents reliance on any bridge in particular. The contract above mirrors the existing ICrossVM.cdc contract interface used in the bridge templates, something I meant to implement in the bridged EVM contracts but didn't end up doing.
cc: @lmcmz

I think it is for any token. Cadence native tokens can be updated in the contract after obtaining the EVM address.
This is an optional view and not necessarily required to be implemented at the beginning.
Regarding the second question, I think it involves how to verify the token after giving these info.
Maybe we can add the address of the bridge and the type information of the bridge in this view?
like this:
access(all) struct EVMBridgedData {
       access(all) let contractAddress: EVM.EVMAddress
       access(all) let associatedType:Type
       access(all) let bridgeCadence: Address
       access(all) let bridgeEVM: EVM.EVMAddress

        init(address: EVM.EVMAddress, type: Type, bridge: Address, bridgeEVM: EVM.EVMAddress) {
            self.contractAddress = address
            self.associatedType = type
            self.bridgeCadence = bridge
            self.bridgeEVM = bridgeEVM
        }
}

Then implement some standard interfaces for Bridges for additional info.

This is an optional view and not necessarily required to be implemented at the beginning.

If it's optional, how can it be a reliable filter for bridgeable assets? In the original thread, it was mentioned this view would be used to determine if something is onboarded for bridging so it's not clear to me how relying on an optional view is more useful than just asking the source of truth relevant to the intent of the script/transaction.

Maybe we can add the address of the bridge and the type information of the bridge in this view

I feel this doesn't solve the problem of verifying associations - an imposter could just point to a bridge contract they own which "validates" their lie of associated types. For example, let's say they're some ERC20 token X on EVM. An imposter deploys a Cadence contract claiming to be the bridged token X - call it bridgedX - as well as an imposter bridge contract according to whatever the bridge contract standard is. Then a wallet provider or DEX, seeing this view resolved from a token, looks at the evmAddress, sees the actual X token and then asks the bridge address to validate that the bridgedX type & X EVM contract associations. The imposter bridge of course just validates the lie and now the wallet provider and therefore user has been fooled.
 If they both point to each other, then the association is trustworthy. However, because we've said this requires contract updates and input from projects, we've determined this is unreliable.
Platforms and wallets will need to choose which bridge providers they trust and integrate with and therefore use as a reliable source of truth for associations.

I agree that a cross-VM bridge standard will be useful, but I think that it's best to take that on as patterns of implementation and use case needs emerge organically.
Again, I don't think that the contents of the view are objectionable, I just want to get to the crux of the intent - the core of what we're trying to achieve with it - and get clear on what it can and cannot be relied on. It's clear there's no way we can trust a bridged token to be honest as there's obvious incentive to lie about such a thing and I don't see a way around asking either the corresponding contract and/or a trusted bridge the true association. If we're saying that validity is not a concern here, then good enough, we just need to be clear on that in docs and communications.

Emm, maybe we mentioned validity too early, because that was not the original intention.
The reason why I proposed that this view can be optional is also for this reason. Optional means that if this view exists, then this token can be marked as a token containing bridge information, that's all, If it doesn't exist, then it does not contain detailed bridge information. As for verification, verification is something outside of this view.
Just like NFTCollectionData, if the contract creator behaves maliciously, they can also set arbitrary values. You can only perform validity checks again after resolving the NFTCollectionData.
After you obtain the View information, you can choose to believe it or choose not to believe it and proceed with further verification. This is the responsibility of the ViewResolver's user.
Just to clarify, the purpose of this view is to be a standard information provider
So its core purpose is: we can obtain this part of information through the standard way of ViewResolver instead of querying through additional API with extra contract importing.

However, speaking from my usage, I'm also fine without this view.
For the TokenList's requirements of bridge's info, I can obtain the accurate information through CrossVM interface and then convert it into additional structs for return. and then provide the accurate VM bridge Info as a JSON file to the Flow Wallet.
But I still think it would be better to have this view, so that I can do a quick filter.


using window services pour la redirection

POC

 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.mahdibenromdhane seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@mahdibenromdhane  You can go ahead with the remaining changes.
I'll put back the PR to the In Progress pipeline.


Request for Feedback: Getting SimpleCov to work with Spring

Hello!
I think I've figured out a good way to get SimpleCov working with Spring. For my Rails application, preloading the app would require some classes in my ./app directory, and this would cause some inaccurate coverage to be reported (any lines that were required during preloading were missing in the coverage.) I figured out how to fix this issue by starting SimpleCov in config/spring.rb, storing the preloaded coverage before forking the process, and then merging the coverage together in SimpleCov.result. Here's the code I'm using. (And here's a longer write-up about how I investigated this issue.)
I was wondering what you think about these changes, and if it might be possible to add some of these changes to SimpleCov?
I'm also not sure if this is just a bug in the Coverage library for my version of Ruby (2.5.5), where the coverage is being reset after the Ruby process is forked.
Thanks for your time!

@ndbroadbent sorry for the long silence - it's not always easy to make time for OSS :)
Thanks for your time investigating this and working on this! :green_heart:
I believe the behaviour when forking is inherently tied to how the coverage library works but not certain.
I'm not sure I 100% understand your approach but basically you carry coverage over. Wouldn't that mean if I ran rspec spec/models and then rspec spec/controllers later the coverage result would include both although I just ran one of them?
(not super familiar with when Spring forks, it has caused me enough pain over time that I usually disable it)


Add internal state of heapster to validate endpoint.

Sample output:
Heapster Version: 0.5
Source type: Kube
Using kubelet port "10250"
Supported kubelet versions [v0.3]
Healthy Nodes:
kubernetes-minion-1.c.vishnuk-cloud.internal
kubernetes-minion-2.c.vishnuk-cloud.internal
No node errors
No pod errors
Sink type: Influxdb
client: Host "<IP_ADDRESS>:8085", Database "k8s"
Data buffering duration: 10s
Number of write failures: 4

Just nit, otherwise LGTM

This will be very useful @rjnagal. Awesome.
Ignore the integration tests until I fix them.

Updated with added pod ID and other fixes.

LGTM


squash: use soft queue to buffer unsquashed Diffstate

Now there are some diffstates still can not squash, such as StoreEvent, which will affect squash of related event.
Previous we use hardware queue to buffer such event for strict order. For less gates consumed, larger queue size and easier order control, now we try to buffer such event by soft queue.
In hardware, we should continue squashing related event while submit unsquash ones. Software logic should also correspond to this, may be depends on some MACRO.
We also fix wrong process order of StoreEvent. Since all StoreEvent submitted before has been enqueued. Check should be after all InstrCommits.

Now, StoreEvent is most important reason for squash break. And it seems more easy to handle, only related to instrCommits.
We will first try to deal with StoreEvent. And try more common logic for more events.

We deal with unsquashed DiffState in PR #405. So close this PR


Add value for CannotBeMerged in Status

With the recent changes from gitlab, seems like they added this value as possible.
Fixes #157

The format check seems to be failing with modification other than mines

Codecov Report

Merging #158 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #158   +/-   ##
=======================================
  Coverage   70.84%   70.84%
=======================================
  Files         170      170
  Lines        2367     2367
=======================================
  Hits         1677     1677
  Misses        690      690

GitLab documentation on this is very sparse I think. But there seem to be a cannot_be_merged state mentioned in the API and in code I only see references where cannot_be_merged_rechecking it gets translated into checking so not sure if that is only used on UI for GitLab or also for the API or if it was changed in an update.
But I do expect that cannot_be_merged would be also a valid response. So I believe that should be added too.
https://docs.gitlab.com/ee/api/merge_requests.html

As @sandercox says a PR can be in either cannot_be_merged or  cannot_be_merged_recheck or cannot_be_merged_rechecking


[Feature] New Data Modeling

This PR change the management of data requests. Following the guidelines, the Schematics was used to model the Weather object.

Weather object instance now looks like this:

{
   "city": {
      "name": "London",
      "country": "GB",
      "coordinates": [
         51.5085,
         -0.1257
      ]
   },
   "description": "Clouds",
   "long_description": "Broken Clouds",
   "temperature": {
      "value": 5.54,
      "unit": "celsius degree"
   },
   "feels_like": {
      "value": 2.76,
      "unit": "celsius degree"
   },
   "max_temperature": {
      "value": 6.11,
      "unit": "celsius degree"
   },
   "min_temperature": {
      "value": 5.0,
      "unit": "celsius degree"
   },
   "wind": {
      "speed": {
         "value": 3.6,
         "unit": "meters per second"
      },
      "degree": {
         "value": 100.0,
         "unit": "degrees"
      }
   },
   "visibility": {
      "value": 10000.0,
      "unit": "meters"
   }
}

Note: The feels_like, max_temperature and min_temperature are collected and returned only if they are not equal to the main temperature.

The Resources and Requests has been changed to be compatible at new Weather object model.

Because of the new modeling, I chose not to include the branch develop in the branch list to run the tests via GitHub Actions. They will probably to break.
This problem will be solved in the next PR, where I will refactor the tests and generate coverage reports.

Because of the new modeling, I chose not to include the branch develop in the branch list to run the tests via GitHub Actions. They will probably to break.
This problem will be solved in the next PR, where I will refactor the tests and generate coverage reports.

@rarygc, this is not the correct approach. The scope of this PR is the one of adding data modeling as a technical enhancement and adding new fields as a new feature, already tested and guaranteed not to break previous features, so it should also update the tests accordingly (even if it means refactoring them). No changes should be ever accepted with breaking tests, nor should them be disabled.
If doing this conflicts with another ongoing PR, you can just re-prioritize in order to avoid rework.

@rarygc, this is not the correct approach. The scope of this PR is the one of adding data modeling as a technical enhancement and adding new fields as a new feature, already tested and guaranteed not to break previous features, so it should also update the tests accordingly (even if it means refactoring them). No changes should be ever accepted with breaking tests, nor should them be disabled.
If doing this conflicts with another ongoing PR, you can just re-prioritize in order to avoid rework.

@dluiscosta
All right, got it!
So I’m going to open a new PR with the new modeling, including the tests refactor.
Thanks for the  guidance!

This PR is ready to be reviewed and merged with the develop branch.
The API test suite has also been refactored to be compatible with the new model.
The following issues will be resolved:

[x] Issue #3
[x] Issue #6


Python 3.10 compatibility

Conda-forge is currently doing the migration of packages for CPython 3.10, the PR for cvxpy is here.
Things build and run quite alright, with only a single test failure that seems to be due to changed error messages:
================================== FAILURES ===================================
______________________ TestAtoms.test_elemwise_arg_count ______________________

self = <tests.test_atoms.TestAtoms testMethod=test_elemwise_arg_count>

    def test_elemwise_arg_count(self) -> None:
        """Test arg count for max and min variants.
        """
        with self.assertRaises(Exception) as cm:
            cp.maximum(1)
>       self.assertTrue(str(cm.exception) in (
            "__init__() takes at least 3 arguments (2 given)",
            "__init__() missing 1 required positional argument: 'arg2'"))
E       AssertionError: False is not true

cvxpy\tests\test_atoms.py:298: AssertionError

Fixed on master.


Houdini: make validations use currentFrame if frameStart doesn't exist

Changelog Description
Hard coded "frameStart" value can cause a bug when "frameStart" is missing when user render current frame (trange == 0)
Additional Info 1
Hard coded "frameStart" leaded to this  issue https://github.com/ynput/OpenPype/issues/5488
when validator was checking geo at frame 0 and imported file hadn't any geo at frame 0 but it workd fine in the current frame
Additional Info 2
Some Product-types crash when rendering the current frame range like BGEO.
which is another issue https://github.com/ynput/OpenPype/issues/5507

Testing notes:

create and instance  (e.g abc)
publish

Code seems fine.
Note that it's always worrying if the user is on a different frame and the "validation" suddenly doesn't work or does work so I'm still hesitant making it rely on the 'current frame' of the user instead of something static to ensure whatever it does is completely reproducable from the instance alone. We'd like to avoid situations where we need to tell the user "go to another current frame and then publish; then it'll work" for whatever reason.

We'd like to avoid situations where we need to tell the user "go to another current frame and then publish; then it'll work" for whatever reason.

It makes sense!
I recall your previous explanations and I'm more aware now! Thanks!
Do you have any recommendations other than falling to 0 ? if not I will close this PR.

Only thing I can come up with is:

"start of current timeline" or
"start frame of current asset"

Not sure if any of those is much better.
To me it sounds more reasonable somehow to enforce NOT using a 'Render current frame' that just happens to start publishing a different frame if the user happened to have gone to the next frame in the timeline and that whenever that is used a validator catches it and says: "Your publish range is set to "Current frame". It's required to be more explicit about what frame you'd like to extract. bla-bla-bla." - which then offers a repair option to just change the ROP node to Render Range with start and end set to whatever the current frame was. So if I was on frame 1004, it'd just set 1004-1004 explicitly.
From that moment onwards it'd also mean that future publishes actually end up using that frame explicitly and we can then still rely more accurately on "frameStart" since it'd be explicitly set on the instance from that point in time. If that's enforced - then I suppose for any case where frameStart would still not be defined we can indeed rely on hou.intFrame() making the rest of this PR fine from that perspective.
However, I welcome any opinions from others since I'm solely coming at it from a pipeline-perspective and having a 'reliable reproducable scene' instead of what is maybe considered artist friendly.
@fabiaserra @mkolar @antirotor @krishna8008 any thoughts?

a validator catches it and says: "Your publish range is set to "Current frame". It's required to be more explicit about what frame you'd like to extract. bla-bla-bla."

This idea sounds reasonable, and it can be disabled from settings


Fix _dev_version being included in wheel

Building wheels does not honor MANIFEST.in, that is only used for source dists.
To exclude the _dev_version.py from wheels, it has to be a package excluded in find_package

@kosack sorry, forgot to change the path of the repo root after moving the file.


1 sides motors won't drive

ez::Drive chassis(
    // These are your drive motors, the first motor is used for sensing!
    {1, 11},     // Left Chassis Ports (negative port will reverse it!)
    {9, -19},  // Right Chassis Ports (negative port will reverse it!)
    20,      // IMU Port
    4.125,  // Wheel Diameter (Remember, 4" wheels without screw holes are actually 4.125!)
    600,   // Wheel RPM
    1.4); // Gear ratio

Usually left motors won't drive. Will work on it.
Edit:
It works in blocks but not in PROS. Same ports

Fixed with changing to LemLib


Add close function to Audio|Video Source

After reading Lukas's comment, I was also unsure during implementation whether the Python side should be made async, so I’m leaving this as an open question.
Should we await self._join_handle or self._join_fut ? If the answer is yes, I think it would be better to implement this as an async aclose and include the logic to wait for them. What do you think? @davidzhao @theomonnom

Yes please, let's create a aclose function instead, we don't need to await the join handle but it is great to keep it async to be future proof on future changes we can do

Ok, I made it async!


run tests in CI

Hi, I just noticed you only build docs in CI but do not run any tests.
Would you be interested in a PR to run tests in CI?
Would you also be interested to add a configuration for tox so anybody could run tests locally for all supported Python versions more easily?
P.S.: Thanks for taking care of this project!

Your advice is great 🌹, I'm looking forward to the PR.

This is awesome! :+1:


Rare and intermittent ?client? side error that Ive noticed.

Basic Information
Mission version: 0.955
Map used: Malden
Mods used: None
Dedicated or local game? Both
GitHub or Workshop mission file? Workshop
Individual Things
Did you edit anything within the mission files? No
Short Issue Description
Random and very rare script error popup while playing on a dedicated server.  Tried on a client/server  happened as well I believe.
Steps to Reproduce the Issue
Unknown likely linked to respawn UI interaction.
Screenshots, Serverlog or any other helpful Information
Script Error as follows.
21:53:28 Error in expression <
respawn_object setposATL ((choiceslist select _oldsel) select 1);
_startdist = >
21:53:28   Error position: <select _oldsel) select 1);
_startdist = >
21:53:28   Error Zero divisor
21:53:28 File mpmissions__CUR_MP.Malden\scripts\client\spawn\redeploy_manager.sqf, line 108

I can't remember who, but this message showed up for someone before, but couldn't be reproduced directly.
Could be that it was Applejakerie.
I'll have a look into that. It's linked to the respawn / redeploy dialog, yes.

There is another issue also I noticed in the logs... and its quite the spammy one.  Soon as the mission file notice is posted..
2:22:09  Mission id: 2887486e72aa9e6d441b4885efa15f81aa374f99
2:22:11 Bad conversion: bool
2:22:11 Bad conversion: bool
(repeat 600times then)
2:22:10 "[KP LIBERATION] [DEBUG] Respawn script started for: sycholic"
pretty much on repeat...

These aren't "Liberation related" messages in the log.
This Bad conversion: bool appears on many missions (and only on local playing, not in a dedicated server log). Basically it's the same as these strange convex or Error: Bone messages in the log. Nothing to worry about concerning my information.

Ah... okay. I never seen that one before.  thanks for the fast replies and keep up the great work.

Found a way to trigger the Error Zero divisor error pretty regularly.... hit escape in the spawn menu after joining in from the lobby.

https://github.com/Wyqer/kp_liberation/commit/8b9c6fc4ac0e95902013e9505a1e7966b845e04c
I put the hashtag at the wrong position, so it wouldn't link directly -.-
Well, I couldn't reproduce that error via local game from the editor with a fresh save.
Started and on the first respawn screen, after the intro, hitting escape only reopens the respawn screen immediately. No errors on this side. The edit could maybe fix a general thing which could be connected to your issue, but I can't test it on my side.
Maybe you try it again after replacing the file in your pbo.

No luck with reinstall. it happens for both the steam workshop pbo and source code.   here's a screenie.  https://steamuserimages-a.akamaihd.net/ugc/847090634557558944/C6939138C7FE89D1130B80CD714417D92B6F6738/  this also will only show if you have -showScriptErrors for client launch (but I think you know that already)

Yes and if you start a mission from the editor you'll have automaticly activated script error showing.
So you start a fresh save, start it as mp game from the editor (I guess), select a slot, join the mission and after the cinematic you select join the fight and hit escape as soon as the deploy dialog appears?
And then you get that error?

So, no one's been able to isolate in which script(s) this might ba happening?


Number of samples per bin should be default option for colour in 2 and 3d histograms

Import : 2d and 3d plots —> Make point colour or marker size “number of samples in the bin”

Hi,
I think we should make this issue 'high priority', this is really an essential feature.
Thanks,
Sascha


Fix onLayoutChildren

Fix to View is not  updated by onItemChanged if target view is in visible area.

Very thanks!!! I'll release this ASAP!


Started using direct ByteBuffers for our performance tests

This takes advantage of our work to speed up platform channels.  It's expected this will drop the times of the 1MB binary test down ~45%.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Don't merge until https://github.com/flutter/engine/pull/26515 has rolled into the framework.

The roll happened in https://github.com/flutter/flutter/pull/83742, this is good to merge.


[11/7/24 spoiler] Suggestions not properly factoring double yellow letters

With initial guess leave for solution event, the suggested solutions included words with only one e despite there being two es in both the guess and the solution

With initial guess gauge for solution going, this same problem occurred (unfortunately did not capture a screenshot of this yesterday)


Define path to package.json

Is your feature request related to a problem? Please describe.
The project I am working on uses kotlin for the backend and therefore the ui is in a seperate folder and the package.json is therefore not in the root of the project. This is why I am getting errors when running the tests.

Describe the solution you'd like
My suggestion for this solution would be either one of these two options:

Auto detect package.json
Option to manually define the path to package.json

Is there any update on how to run the vitest runner, if the web folder is not in root?

You can try using VS Code workspace as a workaround for now

Close this in favor of #101


Syntax highlighter stops working after using Obsidian/markdown quotes inside admonition

How to reproduce the bug

Add 3 test lines inside the admonition:

Use Obsidian/markdown quote feature(>) on the second line. BUG: Notice that syntax highlighter stopped working on all the lines even below the quoted one.

Other interesting detail
Putting a code block returns highlighting back to normal.

Versions

Obsidian 0.12.10
Admonition 6.2.2

I think this is the default behavior for the hypermd CodeMirror syntax highlighter inside a code block. Not sure I'll be able to fix this unfortunately.

@valentine195
I reported the bug to the Obsidian developers, and they answered:

This is third-party plugin problem. We don’t provide user support for user problems of third party plugins.
It’s up to the third party author to debug the issue and if the issue is due to Obsidian core report to the dev.

Is there something I can do to help this issue to be fixed?

Hi,
By CodeMirror issue, I meant that this behavior occurs in the hypermd language highlighter (which is what this plugin uses).

@valentine195
I am utterly confused as to where exactly this bug is and who is responsible.
I reported this bug to the CodeMirror developers, but they are confused as well:

marijnh 9 hours ago
I don't know what hypermd is, but there's no support for it anywhere in this library.

I think HyperMD may be this.
https://github.com/laobubu/HyperMD
But yes, I understand that it's annoying. However, HyperMD is the language highlighter that Obsidian uses to highlight its markdown in edit mode. This same behavior happens in that language highlighter, which means there's nothing I can do, because this plugin just uses that language highlighter.

I just want to know where this bug is located and want to report it to the appropriate party.
It was confusing, because you mentioned CodeMirror, but the bug had nothing to do with them.
Thank you for pointing me in the right direction. :+1:

It was confusing, because you mentioned CodeMirror, but the bug had nothing to do with them.

Yep... I didn't realize HyperMD was a separate thing 🤷🏼 Sorry about that!

Yep... I didn't realize HyperMD was a separate thing 🤷🏼 Sorry about that!

No problem, mate. :-)
Thank you for the quick replies and a great job with a lovely plugin that became an essential part of my everyday life! :-)

I'm gonna close this, hopefully HyperMD will fix it.


Should BGP be enabled for this setting?

Hi all, this doc starts with prerequisites and there is no comment around BGP setting. In the middle page, it describes BGP path for VPNs, but in the screenshots, all the BGP settings are not checked.
Should BGP be enabled for this IPsec on private peering(ER)?
Thanks

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

ID: 56e6b95b-6755-01d7-6e2d-72dfeb474a1a
Version Independent ID: ef384f98-fe94-688e-12b2-841bb404cdbe
Content: Site-to-Site VPN connections over ExpressRoute private peering - Azure VPN Gateway
Content Source: articles/vpn-gateway/site-to-site-vpn-private-peering.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@hanchoi , thank you for your feedback. We have assigned this to the content owner/author for review.
@cherylmc , for your review.

#assign:deeharris-23

Hi @deeharris-23 , could you kindly review this request and answer?
Regards,
Aiden

#please-close


Detaching kernel in Windows 10 (using libusb0)

Hello,
Will it ever be possible to disconnect my USB device using detach_kernel_driver()?
pyusb is installed on a Windows 10 platform using libusb0 (installed with Zadig)
I can send and receive commands to the device. However, I cannot disconnect the device in a graceful way. Only by physically disconnecting the USB cable.
Finally, I used to code for this particular device using MATLAB and the USB driver that was supplied with their installation (hidapi-1.1.jar) and I know it is possible to disconnect from the device via software.

What do you mean by disconnect the device?
And for HID device, it is recommended you use HIDAPI (and cython-hidapi Python binding) under Windows. It is not recommended to use pyusb. How do you disconnect the device with hidapi and its Java binding)?

Bummer.
Okay, so let me answer you last question first. And please bear with me since I only know so much (or so little) about USB communication. After the MATLAB package is installed (in order to communicate with the LEGO EV3 device), two files seem to be used in the communication class: hidapi-1.1.jar and mwhidapi.class.
The USB communication class constructor method looks something like this:

    function obj = CommUSB
        % constructor

        % Adding EV3 to java path
        jPath = javaclasspath('-dynamic');
        ev3path = fileparts(which('legoev3'));
        if ~ismember(ev3path, jPath)
            javaaddpath(ev3path);
        end
        hidjarpath = fullfile(ev3path, 'hidapi-1.1.jar');
        if ~ismember(hidjarpath, jPath)
            javaaddpath(hidjarpath);
        end

        try
            obj.USBHandle = mwhidapi;
        catch
            error('Connect USB Failed ');
        end
        obj.Status = 1;

    end

Once a handle to an instance (I believe) of the mwhidapi class is assigned to the USBHandle property (or attribute), four methods are available:

open()
close()
read()
write()

So, answering your first question, what I mean by disconnecting a device is to have a close() method so the device can then be later opened by some other software.
I have been using this communication class for many years as the foundation of many robotics projects with the LEGO EV3 using MATLAB. I really want to port everything to Python.
As a side note, I did install the cython-hidapi package and, while the read and write methods seem to be working, the reply message never changes despite the fact I'm sending distinct write messages. With pyusb, on the other hand, it works just fine! I get the exact replies I'm expecting to get. The only thing that's missing is that good old close() method...
Finally, why using pyusb isn't recommended?
Thank you so much,
Eduardo

For HID devices, libusb project recommends using HDIAPI, therefore pyusb is not recommended and you should use cython-hidapi. You can raise the issue to cython-hidapi or HIDAPI project.
https://github.com/libusb/libusb/wiki/FAQ#Does_libusb_support_USB_HID_devices

The libusb0 backend is not really recommended and you should give libusb-1.0 backend a try. You need to download libusb Windows binary from here and put libusb-1.0.dll to get pyusb working with libusb-1.0 backend.
https://github.com/libusb/libusb/releases
However, in that case, please do not use libusb0.sys device driver, rather you should try first with the default HID driver since  libusb-1.0 Windows backend support HID devices as well but there are some limitations.

Anyway, back to pyusb if you still want to use pyusb.

I can send and receive commands to the device. However, I cannot disconnect the device in a graceful way. Only by physically disconnecting the USB cable.
So, answering your first question, what I mean by disconnecting a device is to have a close() method so the device can then be later opened by some other software.

What do you mean by that? What is your pyusb code? It should work based on what you say.

I think I understand your issue already.
Your other software is using the default Windows HID driver. So when you switch to libusb0.sys driver, you will not be able to use the other dsoftware as that software relies on native Windows HID API.
When you use HIDAPI or its Java bindings, you will not need to switch driver (as it still uses native Windows HIDAPI). Therefore the other software will of course still work.
Therefore you have two possible solutions. I will recommend the HIDAPI/cython-hidapi method.

Use Windows Device manager to set the device to go back to use WIndows HID driver. Then use libusb-1.0 API and pyusb (you need libusb-1.0.dll from libusb project).
Use Windows Device manager to set the device to go back to use WIndows HID driver. The use Cython-HIDAPI and try to figure out the issue there.

Your other software is using the default Windows HID driver. So when you switch to libusb0.sys driver, you will not be able to use the other dsoftware as that software relies on native Windows HID API.

YES!

When you use HIDAPI or its Java bindings, you will not need to switch driver (as it still uses native Windows HIDAPI). Therefore the other software will of course still work.

YES!
Okay.
For solution 1: When I download and extract the libusb-1.0 files, there are a few folders containing the libusb-1.0.dll. Which one I should get it from (I presume MinGW32?) and where should I place it (System32?). Do I need to use Zadig for the driver installation?
For solution 2: I'll collect some more info and raise the issue with the cython-hidapi folk.
But still, for the close() method thing... Shouldn't I have something similar in pyusb? Below is some test code using Cython-Hidapi:

import hid
# Opening EV3 device
ID_VENDOR_LEGO = 0x0694
ID_PRODUCT_EV3 = 0x0005
device = hid.device()
device.open(ID_VENDOR_LEGO, ID_PRODUCT_EV3)
# Getting EV3 brick serial number
device.write(b'\n\x00\x00\x00\x00\x10\x00\xd3\x0c\x02\x10`')
reply = device.read(1025)[0:24]
print(reply)
data = "".join(map(chr,reply[5:reply.index(0,5,-1)]))
print(data)
# Getting EV3 brick name
device.write(b'\t\x00\x00\x00\x00\x08\x00\xd3\r\x08`')
reply = device.read(1025)[0:24]
print(reply)
data = "".join(map(chr,reply[5:reply.index(0,5,-1)]))
print(data)
# Closing EV3 device
device.close()

The "equivalent" code using pyusb is:

import usb.core
# Finding EV3 device
ID_VENDOR_LEGO = 0x0694
ID_PRODUCT_EV3 = 0x0005
device = usb.core.find(idVendor=ID_VENDOR_LEGO, idProduct=ID_PRODUCT_EV3)
print(device)
# Connecting to device
EP_IN  = 0x81
EP_OUT = 0x01
device.set_configuration()
reply = device.read(EP_IN, 1024, 100)[0:5]
print(reply)
# Getting brick serial number
device.write(EP_OUT, b'\n\x00\x00\x00\x00\x10\x00\xd3\x0c\x02\x10`', 100)
reply = device.read(EP_IN, 1024, 100)[0:24]
print(reply)
data = "".join(map(chr,reply[5:reply.index(0,5,-1)]))
print(data)
# Getting brick name
device.write(EP_OUT, b'\t\x00\x00\x00\x00\x08\x00\xd3\r\x08`', 100)
reply = device.read(EP_IN, 1024, 100)[0:24]
print(reply)
data = "".join(map(chr,reply[5:reply.index(0,5,-1)]))
print(data)

The correct output is:
[17, 0, 0, 0, 2, 48, 48, 49, 54, 53, 51, 52, 55, 48, 101, 53, 56, 0, 0, 0, 0, 0, 0, 0]
001653470e58
[9, 0, 0, 0, 2, 69, 86, 51, 0, 126, 126, 126, 126, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
EV3
Which I can only achieve using the other MATLAB-based software or pyusb. When I use cython-hidapi I get a repeat answer from the last time the other software send a command! I can run the two-command file for the cython-hidapi version ad-nauseum and the reply doesn't change. Unless I go back to the other MATLAB-based software (or pyusb) and send a new command, which then will get "stuck" when I run the hidapi version. But this I believe is an issue for them to help me with.

For solution 1: When I download and extract the libusb-1.0 files, there are a few folders containing the libusb-1.0.dll. Which one I should get it from (I presume MinGW32?) and where should I place it (System32?). Do I need to use Zadig for the driver installation?

No need to use Zadig. But rather you have to revert the action by Zadig and go back to the original Windows HID driver. You can do that with Windows Device Manager.
https://github.com/pbatard/libwdi/wiki/FAQ#Help_Zadig_replaced_the_driver_for_the_wrong_device_How_do_I_restore_it
As for the libusb-1.0.dll file, for 64bit Python, please use the one from "libusb-1.0.24\MinGW64\dll" or "libusb-1.0.24_bin\VS2019\MS64\dll"(you may need redistribution files of VS2019). I like the one from VS2019 as it is smaller.
If for 32bit Python, then use the one from "libusb-1.0.24\MinGW32\dll" or "libusb-1.0.24_bin\VS2019\MS32\dll".
You can put the dll file in the same directory of your Python.exe file (eg: if using virtual environment, it will be under "venv\Scripts" directory.

As for the different between pyusb and cython-hidapi, I am not that familiar with cython-hidapi (I am however relatively familar with HIDAPI). I believe Windows HID API is more limited and may be more stringent with regard to your codes.
HID API will talk in terms of reports. You need to use Input/Output/Feature report to talk to the device. You can say it is higher level API compare to libusb (talk in terms of Control/Interrupt transfer with regard to HID devices).

I will close this issue as there is no issue with pyusb in this case.

Thank you for all the tips Sir!
Time for me to go pester the Cython-Hidapi guy ;)


Invoke-Sqlcmd documentation incorrectly says -InputFile parameter disallows spaces

The -InputFile parameter information in the Invoke-Sqlcmd documentation states "Spaces are not allowed in the file path or file name". However, Invoke-SqlCmd executes successfully when the -InputFile parameter is used with a path and a file name that both contain spaces (e.g.: Invoke-SqlCmd -InputFile 'C:\[path containing spaces]\New Text Document.sql' [...]), at least in the following environment.
Client:

SqlServer PowerShell module version: 22.1.1
PSVersion: 7.4.0
OS: Microsoft Windows 10.0.19045 (Windows 10)

Server:

Product: Azure SQL Database Managed Instance
Operating System: Windows Server 2019 Datacenter (10.0)
Version: 12.0.2000.8

Hi @Adam-S-Daniel - thanks for bringing it to my attention. I'll look into it and possibly fix as soon as possible.

I'll try to look into this one while I published the documentation for v22.3.0...

I've removed that part. Thanks. I have a PR out to update the documentation... I expect to go live


will you open the pretrained weights of the model?

glad to make this issue, will you open the pretrained weights of the model?
we have some ideas to achieve via the foundation model BrainML
if so, thx so much
good luck

Yes, the weights are available on huggingface. I have updated the README to include this link as well.


Add deployment to CI

Coverage remained the same at 99.401% when pulling 14caf8cf3320ad09cad55e884419f5489e0ddea3 on add-deployment-to-ci into e500027ea377d1f6bd51bb0ab3281482a34aa3d7 on master.


[Bug]: Can't use 2FA, login challenge not showing up

What happened?
When I enable 2FA, I log-in but 2FA challenge is not showing, I am presented with the panel.
How to reproduce the bug

Install the plug-in on a fresh installation
Create a new filament user
Log-in with the user and enable 2FA with Google Authenticator
Log-out
when I log-in, I am presented with the panel without 2FA being asked

Package Version
0.0.13
PHP Version
8.3.11
Laravel Version
11
Which operating systems does with happen with?
macOS
Notes
No response

@bizr here is the solution to the 2FA solution that can fix this — https://github.com/stephenjude/filament-two-factor-authentication
I am still working on a fix for this package.

@bizr here is the solution to the 2FA solution that can fix this — https://github.com/stephenjude/filament-two-factor-authentication
I am still working on a fix for this package.

Hi @stephenjude  this was marked as closed, but was this fixed in the current release?

No, I am currently reworking the whole package and this release will come with inbuilt 2FA feature just like Laravel Jetstream


Don't test exec on CircleCI

Right now CircleCI uses LXC as the Docker execution driver.
LXC doesn't support exec https://circleci.com/docs/docker/#docker-exec.

Current coverage is 61.87% (diff: 100%)

Merging #587 into master will not change coverage

@@             master       #587   diff @@
==========================================
  Files           130        130
  Lines          2544       2544
  Methods           0          0
  Messages          0          0
  Branches        350        350
==========================================
  Hits           1574       1574
  Misses          828        828
  Partials        142        142

Powered by Codecov. Last update 88d4648...815e874


Term groups provisioning: fix to search by group name with parsed tokens

Fix to first parse tokens in term group name, and check for existing group using parsed name.

Hi @Voyta, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@Voyta, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Thank you for your submission!


hashCode assumes immutable data, breaks hash tables when modified

The hashCode implementation of jsoup fails the following unit test:
    Element root = new Element(Tag.valueOf("root"), "");

    HashSet<Element> set = new HashSet<>();
    // Add root node:
    set.add(root);

    root.appendChild(new Element(Tag.valueOf("a"), ""));
    assertTrue(set.contains(root));

Having a content-dependant hashCode for mutable objects is flawed.
Either the API needs to be designed immutable, or the hashCode/equals must only check for identity.
Apart from that, these functions are also rather expensive. They can be made available under a different name, and of course a compareTo could be added to check for content identity.

I'm coming around to this - think the best path will be to revert the .equals and .hashcode back to identity, and move the .equals into a .compareTo.


Prevent layout shift caused by the AddressSearch dropdown

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

On NewDot, navigate to /bank-account/company
In the address field, start typing an address.
Notice that as the dropdown shows up, it shifts the entire form down.

https://user-images.githubusercontent.com/22219519/139494999-86b7862b-6ca3-4105-881c-a498becc7041.mov
Expected Result:
The form shouldn't shift.
Actual Result:
The form shifts.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround? Yes, layout only.
Platform:

Web
iOS
Android
Desktop App
Mobile Web

Version Number:
Reproducible in staging?:
Reproducible in production?:
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
View all open jobs on GitHub

@Expensify/design is this something we should fix?

Agree, the dropdown should be absolutely positioned on top of the other elements. Maybe we should even give it a bit of a shadow too to create some more visual separation as well.

Thanks for confirming @shawnborton! I'm coming across an edge case when:

The dropdown is too close to the bottom of the screen

The input is inside a nested form.

The library we are using does not expose a way to limit the maximum number of results (so we always display 5 if there are enough matches). One suggestion that I have is to display the dropdown show above the input in those cases. Any thoughts here?

Displaying above is interesting - how might that look on mobile? Are we able to get the text input to be focused and scrolled directly above the keyboard so that there is ample room for the results?

Hmm my suggestion might have issues with shorter forms. If the form is short there isn't enough room for the dropdown above the input and we can't scroll, so the view is either cut at the bottom or at the top. Here's an example:

Now I'm not too sure how to solve this one. Any ideas @shawnborton?

Hmm the only thing I can think of is to always launch the form to the bottom of the input and try to scroll the input towards the top of the viewport as much as possible.

Still not sure how to approach the edge cases here. I'm gonna try to come back to this one next week.

Haven't made any progress here yet. I will try to look into it next week.

I have a suggestion. :chipmunk:  :clown_face:
The issue with the approach we are exploring so far.

This just doesn't work for mobile.
This will not fit the mobile web (we don't know the resolution of the device). This becomes worse when the keyboard is Open.
There would be positioning challenges.

I think we should create a new screen for selecting the address and show the Address selector as it is on that screen.

Show a read-only input in this form whose UI does not change.
When a user clicks it, Open the new page with a single input on the top where the user can select the address and press enter.
On Press of entering, he would come back to this screen and that read-only input would be filled with selected address.

I like that idea, it reminds me of how Google Maps handles adding in addresses for directions.

Sounds like a good idea! I'll do some more thinking on how to handle the manual address input solution we are implementing.

I will try to carve out some time to work on this issue this week!

I actually discussed this 1:1 with @marcaaron. Since nothing is broken and the solution at hand is really involved and hard to maintain, we will just close this for now.


Removes duplicate import statement from modified file

Summary
This pull request fixes an issue accidentally introduced into master wherein a value was imported twice into by same file, causing eslint to fail the application build.
(This issue was caused by two concurrent pull requests which fixed the same problem; the implemented solutions in both branches were identical, but the import statements were in different locations.)

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against db4b6b16e2cd2d264fed6733234a3ca3ae1a9784


fix: #1047 Remove count_documents from delete_documents

Related Issues

fixes #1047

Proposed Changes:
Removed the expensive full-count check to see if the collection is non-empty. Instead finding any single document as a check for non-emptiness.
How did you test it?
Ran:

hatch run lint:all
hatch run test

Notes for the reviewer
This test ensures that the behavior for an empty collection is not the same as the behavior when all document_ids to be deleted are not found.
Checklist

I have read the contributors guidelines and the code of conduct
I have updated the related issue with new insights and changes
I added unit tests and updated the docstrings
I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test:.

 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.