Sysl Parser and Proto Structure Proposals

This is an issue to capture any issues and ideas for improvements for the way sysl is parsed and stored in a data structure.
Context
Currently, the data model has evolved through various feature requests and become very complex, with some inconsistencies around where and how data is stored. This makes developing code which interacts with the Sysl data structure very complex and verbose, needing to handle a variety of cases.
To speed up development of sysl features, a number of improvements can be made to the data structure, as well as the parser (when the parser is migrated in the future from ANTLR to WBNF) https://github.com/anz-bank/sysl/issues/581.
Pain Points
Endpoint Statements
Return statements are stored as strings rather than structured data, requiring any call statements and return statements to be parsed by feature code, rather than being handled in the parser itself.
Type System
A number of types defined in sysl.pb.go are not used or duplications.

Sequence and List

Names
My App:
    ...

Currently names allow for spaces in the definition, however this is rarely used and most users define names as an UpperCamelCase string instead, and a LongName in square braces
MyApp"My Long Application Name":
   ...

Namespaces
Namespace1::Namespace2::MyApp:
   ...

Sysl also provides a namespacing syntax which is not widely used. This namespacing means that all application names are stored as an array of strings, requiring sysl developers to concatenate the string in almost all use cases.
Type Reference consistency
The type reference system is highly complex, with very little documentation regarding the behaviour. Most applications need to parse these and provide additional information from the context for references within the same app.
For example, the following:
App1:
    someEndpoint(myParam <: myType):
        return string

    !type myType:
        content <: string

is parsed into the following data structure:
param:  {
          name:  "myParam"
          type:  {
            type_ref:  {
              ref:  {
                appname:  {
                  part:  "myType"
                }
              }
            }
          }
        }

The TypeName is found in the AppName field, which is incorrect. More details here https://github.com/anz-bank/sysl/issues/817. This bug is currently handled in sysl-catalog, but should be fixed in the source.
In addition, the param fails to consistently populate the source and context fields, making it very difficult to parse parameters consistently.
Parameter Inconsistency
Currently, Path, Query, Response and Header parameters are stored in an inconsistent manner, which each being a different type. The lack of consistency means that new developers find it hard to understand, from the data-structure alone where to find a parameter when working with the Sysl data type.
Custom Patterns
A number of patterns exist to work around limitations in the type system. E.g ~empty, ~jsontag etc. are all used to indicate information which is unhandled by the parser. These should be documented in one place, so that a user can see exactly what each pattern means in each context.
Special Characters
Currently, special characters such as "." or "-" are not accepted in application names. The current work around required the use of escaping these with "%4e" but this hurts the readability.
Enums
Currently enum definitions are denoted using the colon, ideally it can be modified to use the equal symbol instead, for better clarity
  !enum Code:
    success: 1
    invalid: 2
    tooManyAttempts: 3

Maps
Map definitions are also not supported as a first-class type. Ideally, the syntax could be simplified here
    !type InventoryResponse[json_map_key="item_id"]:
            item_id <: string:
                @json_tag = "item_id"
            quantity <: int:
                @json_tag = "quantity"

Transforms
Remove all the additional types added for the Sysl Transformation language, once migration over to Arrai is complete.
These are just some pain points found when working, to inform the refactoring to be done when we migrate to the WBNF parser

Endpoint Statements: These can probably be enhanced but some statements are just raw string statements. I think we can have specific syntax for return statements (or statements that return some kind of data) for easier parsing.
Names: I didnt know that existed.
I do agree that the sysl data structure is tedious to access and parse, If we were to consolidate the data structure, it would probably mean backwards compatability is required. For alot of the pain points, it kind of looks like many of issues could be a symptom of being afterthoughts in the design of sysl.

Endpoint Statements: These can probably be enhanced but some statements are just raw string statements. I think we can have specific syntax for return statements (or statements that return some kind of data) for easier parsing.

Yeah I think we can still allow for any raw strings, but have a formal syntax for call and return statements. e.g we haven't really documented that the AppName can be dropped when referencing types defined in the same application

I do agree that the sysl data structure is tedious to access and parse, If we were to consolidate the data structure, it would probably mean backwards compatability is required. For alot of the pain points, it kind of looks like many of issues could be a symptom of being afterthoughts in the design of sysl.

Yeah lots of the issues seem to be due to the nature of Sysl having evolved over time to suit various needs. Could probably do it two ways:

Maintain backwards compatability and make the changes that don't break the grammar to the sysl.pb.go struct. Other changes might need to be made using something like syslwrapper
Release Sysl2.0 with some automation for migrating to the new language version. Would probably want to put a lot of thought into what this version of Sysl would look like since we only want to do it once.

Sysl Proto Struct
An additional question I have is what benefits are offered by using a struct generated from a proto file for sysl. Do these benefits outweigh the verboseness and rigidity enforced by the proto-generated code? (Just a bit confused about the original design intent)


Missing models to fix tests

Missing models to fix tests

Are there other issues about this PR ?

Just wondering if we should create a src/events/ folder and host events under \yii\activerecord\events\.
We could also remove 'ActiveRecord' from events name since we're already in yiisoft/activerecord

I was thinking the same.

Awesome, thank you! 🙌


fix: remove event is in range check

Description of change

This logic does not handle the case where the event is recieved with the end set and would always reject these type of events. Since allowing events with end set that are seen for the first time would make the logic always true, remove the logic
The logic existed to try to merge events from polling and the websocket but we don't do that anymore anyways.

Summary by CodeRabbit

Refactor

Improved event processing logic for light and sensor events by removing unnecessary range checks.
Simplified handling of different sensor event types for better performance.

This might not be needed.  I'll leave it on draft

Is needed. We still loose events when bootstrap is resynced if we are unlucky


0.9.0: --init ask most questions two times

[charlike@voltaire simple-get-stream]$ verb --init
? Would you like to use global preferences? No
? What layout would you like to use? empty
? Do you want to add a Table of Contents to README.md? No
? What plugins do you want to use? gulp-format-md
? What tasks or generators do you want to run on this project? readme
? Do you want to run tasks anyway when only non-task flags are passed? Yes
? Do you want to lint for missing reflinks and add them to verb config? Yes
? What layout would you like to use? empty
? Do you want to add a Table of Contents to README.md? No
? What plugins do you want to use? gulp-format-md
? What tasks or generators do you want to run on this project? readme
? Do you want to run tasks anyway when only non-task flags are passed? Yes
? Do you want to lint for missing reflinks and add them to verb config? Yes
? Plugins need to be installed, want to do that now? No
[14:32:28] updated package.json config with:
{ layout: 'empty',
  toc: false,
  plugins: [ 'gulp-format-md' ],
  tasks: [ 'readme' ],
  run: true,
  lint: { reflinks: true } }
[14:32:28] finished ✔

Part of the installed verb's package.json with shasum, it may help (guarantee what i'm using)
  "_resolved": "git://github.com/verbose/verb.git#1d524356ff6fe886a7f183f02de6764de13616e$
  "_shasum": "80d8b728f4595d720acf9d0abadf4a2122ece236",
  "_shrinkwrap": null,
  "_spec": "verbose/verb#dev",

do --config=init, and update to latest


VLAN-Deployment-Groups

As ...
Nelly - Network Engineer
I want ...
an easy and secure way to deploy VLANs to switches and interfaces (Trunks).
So that ...

I can select which VLANs to include in the Deployment-Group out of the VLANs defined in parent group
I can modify VLAN names by just editing the parent groups data (DRY) without touching the deployment group
I can securely remove VLANs from parent VLAN-Group and all deployment groups will be updated automatically.
I can assign more than one deployment groups to single device. So I can define e.g. tagged vlans for Accesspoints, Additional VLANs on site-to-site layer 2 connection that are only used in datacenter (HA Sync), VLANs on edge switches, ...

I know this is done when...

I define a new VLAN-Deployment-Group by adding a unique group-name and a constant reference to an existing VLAN-Group. (The parent VLAN group is not changeable after creation).
I select the VLANs to include in Deployment-Group from the list of VLANs defined in VLAN-Group. All vlans in one deployment-group are unique.
I add Deployment-Groups (0..n) to a virtual-chassis's, devices or interfaces (allowed vlans). Only Deployment-Groups having the same parent are allowed to add to an object.

Adding Deployment-Groups should work like assigning Tags.

I add a device to a virtual-chassis that has deployment-groups assigned.

If the device has also deployment-groups assigned, the parent VLAN-Group needs to be identical in order to allow insertion.
If the device has no deployment-groups assigned, it will be added to the virtual-chassis and inherits the virtual-chassis groups as a reference. So changes to the assigned groups of the virtual-chassis will always be reflected at the device level. The device will inherit all DISTINCT vlans of all Deployment-Groups assigned to the virtual chassis (get_deployed_vlans())

I add a device to a virtual-chassis that has no Deployment group assigned.

The virtual chassis takes over the Deployment-Groups from the device.
The device inherits the Deployment-Groups from the virtual-chassis.

I remove a device from a virtual chassis.

All the current Deployment-Groups from the virtual-chassis will be added to the device. This ensures that no configuration change will happen on the device and its interfaces.

I select the deployed vlans in GraphQL
I use the API to define and query Deployment Group specific data

Optional - Feature groups this request pertains to.

[ ] Automation
[ ] Circuits
[X] DCIM
[X] IPAM
[ ] Misc (including Data Sources)
[X] Organization
[ ] Plugins (and other Extensibility)
[ ] Security (Secrets, etc)
[ ] Image Management
[ ] UI/UX
[ ] Documentation
[ ] Other (not directly a platform feature)

Database Changes

New model VLAN-Deployment-Group
parent_vlan_group:   foreigen key reference parent VlanGroup
name: str
slug: str
description: text
ref_selected_vlans:  foreigen key reference to vlans in parent_vlan_group

References to assigned Deployment-Groups for

VirtualChassis
Device
Interface

External Dependencies
No response

This appears to be a good use case for dynamic groups however vlans and vlan groups aren't supported in dynamic groups yet. We're going to need to determine if dynamic groups, custom relationships and possibly custom validators would satisfy all of the requirements above.

@bryanculver Is there a time horizon for adding VLANs to Dynamic groups?

@bryanculver Is there a time horizon for adding VLANs to Dynamic groups?

Dynamic Groups should come to more models in 2.X with the work in #1483. We can prioritize models but we're working on fixing the filter sets which is the blocker for adding it to more models.

VLANs can be assigned to dynamic groups now.


Add translation stage to IBM backend and update DD to use

Summary
This PR builds on #480 and #420 to enable translation plugins for provider backends by default. This is a powerful feature that will solve usability issues with new-style control-flow.
As this is based on #420 for reviewing purposes look at - https://github.com/Qiskit/qiskit-ibm-provider/pull/483/files/4b446b04e25912f0de6a45a49e37532ed896a4bc..25f35228c0aad6ce3000fca7fc4aca2261c27a75
Details and comments
Currently the plugin is named ibm_dynamic_circuits but applies transformations that are generally good for IBM backends. The IBMBackend currently does not differentiate between dynamic/non-dynamic circuit backends but this might be desirable in the long run. Perhaps, in the near term we could rename ibm_dynamic_circuits to ibm or something along these lines (or keep both and have them be identical).

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

259 of 271 (95.57%)  changed or added relevant lines in 6 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.9%) to 51.073%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_ibm_provider/ibm_backend.py
1
2
50.0%

qiskit_ibm_provider/transpiler/passes/scheduling/dynamical_decoupling.py
4
5
80.0%

qiskit_ibm_provider/transpiler/passes/scheduling/scheduler.py
107
111
96.4%

qiskit_ibm_provider/transpiler/passes/scheduling/block_base_padder.py
144
150
96.0%

Files with Coverage Reduction
New Missed Lines
%

qiskit_ibm_provider/transpiler/passes/scheduling/block_base_padder.py
1
95.73%

qiskit_ibm_provider/transpiler/passes/scheduling/scheduler.py
1
97.64%

Totals

Change from base Build<PHONE_NUMBER>:
0.9%

Covered Lines:
2975

Relevant Lines:
5825

💛  - Coveralls


Update README.md

hi @shivamkakkar4 Thank you so much for the your contribution 🎉

Hi @shivamkakkar4 there are some changes requested in the PR, if no activity is found within 7 days, this PR will be closed.


AtomicInteger#getAndIncrement() or AtomicInteger#incrementAndGet() already does what this increment() method does

https://github.com/eugenp/tutorials/blob/fa6fc0b9c1f0e876c1844f540887788fecb9f3ca/core-java-modules/core-java-concurrency-advanced/src/main/java/com/baeldung/concurrent/atomic/SafeCounterWithoutLock.java#L12
Doesn't AtomicInteger#getAndIncrement() or AtomicInteger#incrementAndGet() already do what this increment() method does,(atomically increment the counter by 1)?
Why do we need this method implementation for it to be a 'thread safe' counter?
If one looks at the source code of AtomicInteger for any of these two methods (since in this case the return value is not returned/used) they already retry the increment until it succeeds thereby guaranteeing that the call to the increment method always increases the value by 1
Below is are the source references,
https://github.com/AdoptOpenJDK/openjdk-jdk11/blob/19fb8f93c59dfd791f62d41f332db9e306bc1422/src/java.base/share/classes/java/util/concurrent/atomic/AtomicInteger.java#L180
https://github.com/AdoptOpenJDK/openjdk-jdk11/blob/19fb8f93c59dfd791f62d41f332db9e306bc1422/src/java.base/share/classes/jdk/internal/misc/Unsafe.java#L2334
Reproducing it here below,
    // AtomicInteger#getAndIncrement() snippet..
    public final int getAndIncrement() {
        return U.getAndAddInt(this, VALUE, 1);
    }

   // Unsafe#getAndAddInt() snippet..
    public final int getAndAddInt(Object o, long offset, int delta) {
        int v;
        do {
            v = getIntVolatile(o, offset);
        } while (!weakCompareAndSetInt(o, offset, v, v + delta));
        return v;
    }

Thanks
Muthu

Hey, @softwarebrahma.
Thanks for the feedback. AtomicInteger#getAndIncrement() and AtomicInteger#incrementAndGet() are indeed the standard way of using atomic variables.
We'll take this to the team and update the article if necessary.

Hey, @softwarebrahma.
Thanks for the feedback. AtomicInteger#getAndIncrement() and AtomicInteger#incrementAndGet() are indeed the standard way of using atomic variables.
We'll take this to the team and update the article if necessary.

Cool thanks @ulisseslima. I like & trust @eugenp & the team's stuff as are many others & its important it remains accurrate.

Hi @softwarebrahma - Thanks for your feedback. We adjusted the code and also updated the referring article.


Translucent surfaces rendered in wrong order

On map Watah, these translucent walls on the opposite side of the room appear to be rendered on top of the closer ones. Judging by r_debugSort they both have sort order SS_BLEND0.

Might be related to #1079. IIRC they should be sorted by distance back to front.

Closing as duplicate.


fix: DH-17076 LayoutHints on TreeTables were not being applied

Related to DH-17076
Needed a Core patch: https://github.com/deephaven/deephaven-core/pull/5543
Tested using both the Python and Groovy snippets from the ticket
Fixes #2035

@mattrunyon order shouldn't matter here, I added feature detection as well.


Add brushes as resources to the scene manager

As it turns out, creating brushes is actually quite expensive with a lot of rendering backends. So we definitely want to only create them once and then just attach them to the individual entities.

I think we should globally cache solid color shaders because there's likely to be a lot of them that are mostly identical. The other shaders all depend on width and height so tbey should probably belong to a local cache, but for the color shaders I see no harm in just having a lazy_static lru cache somewhere with a reasonable size.

although checking again it appears the solid color shaders are also by far the least computationally expensive, to the point where caching it is probably not even worth it.


Add higher-order component option

Enable use of react-suitcssify with pure functional components

Add higher-order component option (thanks @pbomb)
Update demo and documentation
Update React version and add to peerDependencies
Other minor tweaks

Looks good to me! :shipit:


Github test workflows now targets main branch instead of master

closes: #54

Codecov Report

Merging #55 (f2f6ef7) into main (03661ad) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #55   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           18        18
  Lines          498       498
  Branches        75        75
=========================================
  Hits           498       498

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 03661ad...f2f6ef7. Read the comment docs.


Modifying The Footer Section

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
There is no proper alignment, some elements overlap each other as well as some icons are in correct size
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Heyy I want to work on this issue Assign me under GSSOC'24

I want to work on this issue and solve
assign me under GSSOC`24

I have already completed half of it. Can you choose a different issue?


Add arangojs 8+ support (7+ is still supported either)

slightly fixed imports
move arangojs to peerDependencies to ensure compatibility with both 7 and 8 versions

Thank you!

@eonae v1.6.0 has been published with your changes and the example repository has been updated https://github.com/TimMikeladze/arango-migrate-example


Precomputed Sigs

Error when supplying precomputed sigs from data frame and text file

Error when supplying recomputed sigs with text file. When a text file is supplied with N samples separated by tabs on the first line and error is thrown when subsequent lines contain N + 2 tabbed spaces due to signature name and type.

Fixed this at some point - closing.


Add ranking matching models

Description
Add several ranking matching models for retrieval-based multi-turn response selection:

Sequential Matching Network (SMN) [Wu et al., 2017]

Deep Attention Matching Network (DAM) [Zhou et al., 2018]

Deep Attention Matching Network with Universal Sentence Encoder (DAM-USE-T). This is our new proposed neural ranking architecture based on [Zhou et al., 2018] and [Cer D. et al., 2018].
The model DAM-USE-T outperforms the current state-of-the-art models on the Ubuntu Dialogue Corpus v1 [Lowe et al., 2015] and Ubuntu Dialogue Corpus v2 [Lowe et al., 2017] with the test metrics: 0.7957/0.8932/0.9734 and 0.7446/0.8677/0.9738 accordingly.

UPD: added pre-trained models (SMN, DAM, DAM-USE-T) for both Ubuntu Corpus v1 and v2 datasets. There are 6 models in total, see ranking configs, for example, pre-trained model DAM-USE-T for Ubuntu-v1 is  here
References
Ryan Lowe, Nissan Pow, Iulian Serban, and Joelle Pineau. 2015. The ubuntu dialogue corpus: A large dataset for research in unstructured multi-turn dialogue systems. arXiv preprint arXiv:1506.08909.
Ryan Thomas Lowe, Nissan Pow, Iulian Vlad Serban, Laurent Charlin, Chia-Wei Liu, and Joelle Pineau. 2017. Training end-to-end dialogue systems with the ubuntu dialogue corpus. Dialogue and Discourse 8(1).
Xiangyang Zhou, Lu Li, Daxiang Dong, Yi Liu, Ying Chen, Wayne Xin Zhao, Dianhai Yu and Hua Wu. 2018. Multi-Turn Response Selection for Chatbots with Deep Attention Matching Network. Proceedings of the 56th Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers), pages 1118-1127, ACL. http://aclweb.org/anthology/P18-1103
Yu Wu, Wei Wu, Ming Zhou, and Zhoujun Li. 2017. Sequential match network: A new architecture for multi-turn response selection in retrieval-based chatbots. In ACL, pages 372–381.
Daniel Cer, Yinfei Yang, Sheng-yi Kong, Nan Hua, Nicole Limtiaco, Rhomni St. John, Noah Constant, Mario Guajardo-Cespedes, Steve Yuan, Chris Tar, Brian Strope, Ray Kurzweil. 2018a. Universal Sentence Encoder for English. Proceedings of the 2018 Conference on Empirical Methods in Natural Language Processing: System Demonstrations. Pages 169–174. http://aclweb.org/anthology/D18-2029

Just take a while, MatchingPredictor and MatchingPredictorUSE are useless now, because of removed *_interact.json configs for SMN/DAM/DAM-USE-T.
Going to remove them too.

Closed due to inactivity. Reopen when will ready to continue.


Python 2.4 compatibility

Unfortunately upgrading/rebuilding VIM is not an option for me. Hopefully the changes are small enough that the support can be merged in master.

Finally merged! Going into next release. Thanks for the contribution :)


ci: add tests tags to linter config

What this PR does / why we need it:
This PR adds integration_tests and e2e_tests build tags to linter config so that tests files are also checked upon linting.

Need re-approval cuz my commit's signature somehow got lost 🤦 @shaneutt


Falcon OpenAPI request and response factories

Implemented OpenAPI request and response factories. I unfortunately don't have the time to write tests for them right now, but I figured I'd share the code already as it might help someone.

@larsderidder thank you for the contribution. Closing in favor of #215.


Cannot analyse avalon_mm_vvc.vhd with current git versions of nvc and ghdl

When the current version of uvvm, tag v2024.09.19, is compiled by current versions of nvc or ghdl the file avalon_mm_vvc.vhd does not compile.
Uvvm v2_2024.08.16 can be compiled without issues with both nvc ot ghdl.
Am I missing something?

nvc --std=2008 --work=/Users/Peter/.nvc/lib/bitvis_vip_avalon_mm.08 -L/Users/Peter/.nvc/lib -a --relaxed ../src/avalon_mm_vvc.vhd
** Error: type of actual BOOLEAN does not match formal LAST_CMD_IDX_EXECUTED
type INTEGER
> ../src/avalon_mm_vvc.vhd:242
|
242 |     update_vvc_activity_register(global_trigger_vvc_activity_register, vvc_status, ACTIVE, entry_num_in_vvc_activity_register, last_cmd_idx_executed, v_cmd_queues_are_empty, C_SCOPE);
|                                                                                ^^^^^^^^^^^^^^^^^^^^^^
** Error: type of actual BOOLEAN does not match formal LAST_CMD_IDX_EXECUTED
type INTEGER
> ../src/avalon_mm_vvc.vhd:250
|
250 |     update_vvc_activity_register(global_trigger_vvc_activity_register, vvc_status, INACTIVE, entry_num_in_vvc_activity_register, last_cmd_idx_executed, v_cmd_queues_are_empty, C_SCOPE);
|                                                                                ^^^^^^^^^^^^^^^^^^^^^^

ghdl -a --work=bitvis_vip_scoreboard --std=08 -frelaxed -fsynopsys -Wno-hide -Wno-shared /Users/Peter/Downloads/UVVM/bitvis_vip_scoreboard/src/generic_sb_support_pkg.vhd /Users/Peter/Downloads/UVVM/bitvis_vip_scoreboard/src/generic_sb_pkg.vhd /Users/Peter/Downloads/UVVM/bitvis_vip_scoreboard/src/predefined_sb.vhd
ghdl -a --work=bitvis_vip_avalon_mm --std=08 -frelaxed -fsynopsys -Wno-hide -Wno-shared /Users/Peter/Downloads/UVVM/bitvis_vip_avalon_mm/src/avalon_mm_bfm_pkg.vhd /Users/Peter/Downloads/UVVM/bitvis_vip_avalon_mm/src/transaction_pkg.vhd /Users/Peter/Downloads/UVVM/bitvis_vip_avalon_mm/src/vvc_cmd_pkg.vhd /Users/Peter/Downloads/UVVM/uvvm_vvc_framework/src_target_dependent/td_target_support_pkg.vhd /Users/Peter/Downloads/UVVM/uvvm_vvc_framework/src_target_dependent/td_vvc_framework_common_methods_pkg.vhd /Users/Peter/Downloads/UVVM/bitvis_vip_avalon_mm/src/vvc_sb_pkg.vhd /Users/Peter/Downloads/UVVM/bitvis_vip_avalon_mm/src/vvc_methods_pkg.vhd /Users/Peter/Downloads/UVVM/uvvm_vvc_framework/src_target_dependent/td_queue_pkg.vhd /Users/Peter/Downloads/UVVM/uvvm_vvc_framework/src_target_dependent/td_vvc_entity_support_pkg.vhd /Users/Peter/Downloads/UVVM/bitvis_vip_avalon_mm/src/avalon_mm_vvc.vhd /Users/Peter/Downloads/UVVM/bitvis_vip_avalon_mm/src/vvc_context.vhd
/Users/Peter/Downloads/UVVM/bitvis_vip_avalon_mm/src/avalon_mm_vvc.vhd:242:151:error: can't associate "v_cmd_queues_are_empty" with constant interface "last_cmd_idx_executed"
update_vvc_activity_register(global_trigger_vvc_activity_register, vvc_status, ACTIVE, entry_num_in_vvc_activity_register, last_cmd_idx_executed, v_cmd_queues_are_empty, C_SCOPE);
^
/Users/Peter/Downloads/UVVM/bitvis_vip_avalon_mm/src/avalon_mm_vvc.vhd:242:151:error: (type of "v_cmd_queues_are_empty" is boolean)
/Users/Peter/Downloads/UVVM/uvvm_vvc_framework/src_target_dependent/td_vvc_entity_support_pkg.vhd:332:14:error: (type of constant interface "last_cmd_idx_executed" is integer)
/Users/Peter/Downloads/UVVM/bitvis_vip_avalon_mm/src/avalon_mm_vvc.vhd:250:153:error: can't associate "v_cmd_queues_are_empty" with constant interface "last_cmd_idx_executed"
update_vvc_activity_register(global_trigger_vvc_activity_register, vvc_status, INACTIVE, entry_num_in_vvc_activity_register, last_cmd_idx_executed, v_cmd_queues_are_empty, C_SCOPE);
^
/Users/Peter/Downloads/UVVM/bitvis_vip_avalon_mm/src/avalon_mm_vvc.vhd:250:153:error: (type of "v_cmd_queues_are_empty" is boolean)
/Users/Peter/Downloads/UVVM/uvvm_vvc_framework/src_target_dependent/td_vvc_entity_support_pkg.vhd:332:14:error: (type of constant interface "last_cmd_idx_executed" is integer)
ghdl:error: compilation error
nvc --version
nvc 1.14.0 (1.14.0.r25.g8b6a0378) (Using LLVM 18.1.8)
ghdl --version
GHDL 5.0.0-dev (4.1.0.r238.g0afa60d11) [Dunoon edition]
Compiled with GNAT Version: 14.1.0
llvm 18.1.8 code generator
macos 14.7 (intel)

An argument to update_vvc_activity_register is missing. The update_vvc_activity_register has 8 arguments.
procedure update_vvc_activity_register(
signal   global_trigger_vvc_activity_register : inout std_logic;
variable vvc_status                           : inout t_vvc_status;
constant activity                             : in t_activity;
constant entry_num_in_vvc_activity_register   : in integer;
constant executor_id                          : in natural;
constant last_cmd_idx_executed                : in integer;
constant command_queue_is_empty               : in boolean;
constant scope                                : in string := C_VVC_NAME
);
Only 7 are given:
update_vvc_activity_register(global_trigger_vvc_activity_register, vvc_status, ACTIVE, entry_num_in_vvc_activity_register, last_cmd_idx_executed, v_cmd_queues_are_empty, C_SCOPE);
update_vvc_activity_register(global_trigger_vvc_activity_register, vvc_status, INACTIVE, entry_num_in_vvc_activity_register, last_cmd_idx_executed, v_cmd_queues_are_empty, C_SCOPE);
executor_id seems to be missing.

It seems there was some old code which was not removed during the release.
Can you try commenting out the process p_activity_register_update in line 234?

Thank you very much for your reply.
After commenting out the process p_activity_register_update the issue is resolved.

It seems that the code released with v2024.09.19 does not compile with any compiler.
Do you expect fixed code to be re-cheked and tagged with a new tag?

The 2024.09.19 release has been reverted and release 2024.10.08 has been published.


Git calls are not checked for result

Which leads to very annoying scenario, when hook fails, commit fails, vump reports commit has been created and tags current commit :roll_eyes:

Fixed in v2


bug/optional-not-saving #91

Description
At some point defaultChecked was changed to checked. checked was being bound to the prop values, which will not change. It's now state driven.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

Unit tested
Click tested

Checklist:

[x] My code follows the javascript standard style
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation and versioning
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have rebased onto master and there are no code conflicts

Annoyingly (not your fault) I think we've both fixed this in different ways. See https://github.com/XGovFormBuilder/digital-form-builder/pull/96. I've incidentally fixed it while refactoring component-type-edit to create the component model.
I've added your test case to that PR and it all passes. Is it ok if we close this one on that basis?

@andymoody sgtm :)


Investigate linux build using Visual studio

It should be possible to build and run using visual studio now. This will eliminate the need for maintaining the linux based project files.

Switched to cmake.. Non issue now


[Back-port branch-2]: HBASE-24112 [RSGroup] Support renaming rsgroup

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  0s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 29s
branch-2 passed

+1 :green_heart:
checkstyle
1m 22s
branch-2 passed

+1 :green_heart:
spotbugs
2m 37s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m  8s
the patch passed

+1 :green_heart:
checkstyle
1m 18s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
10m 58s
Patch does not cause any errors with Hadoop 2.10.0 or 3.1.2.

+1 :green_heart:
hbaseprotoc
0m 59s
the patch passed

+1 :green_heart:
spotbugs
2m 53s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 25s
The patch does not generate ASF License warnings.

35m 28s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1520

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle cc hbaseprotoc prototool

uname
Linux 1eb1d2f36b7f 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 62a488b946

Max. process+thread count
94 (vs. ulimit of 12500)

modules
C: hbase-server hbase-rsgroup U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 34s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 30s
branch-2 passed

+1 :green_heart:
compile
1m 19s
branch-2 passed

+1 :green_heart:
shadedjars
4m 26s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 57s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m  8s
the patch passed

+1 :green_heart:
compile
1m 15s
the patch passed

+1 :green_heart:
javac
1m 15s
the patch passed

+1 :green_heart:
shadedjars
4m 25s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 57s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
119m 12s
hbase-server in the patch passed.

+1 :green_heart:
unit
2m 50s
hbase-rsgroup in the patch passed.

145m 28s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1520

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux b3fe90fb5e64 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 62a488b946

Default Java
1.8.0_232

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/testReport/

Max. process+thread count
3708 (vs. ulimit of 12500)

modules
C: hbase-server hbase-rsgroup U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  0s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 53s
branch-2 passed

+1 :green_heart:
compile
1m 42s
branch-2 passed

+1 :green_heart:
shadedjars
6m 37s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 26s
hbase-rsgroup in branch-2 failed.

-0 :warning:
javadoc
0m 47s
hbase-server in branch-2 failed.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 21s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 16s
the patch passed

+1 :green_heart:
compile
1m 46s
the patch passed

+1 :green_heart:
javac
1m 46s
the patch passed

+1 :green_heart:
shadedjars
6m 37s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 49s
hbase-server in the patch failed.

-0 :warning:
javadoc
0m 25s
hbase-rsgroup in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
126m 51s
hbase-server in the patch passed.

+1 :green_heart:
unit
3m  2s
hbase-rsgroup in the patch passed.

162m 12s

Subsystem
Report/Notes

Docker
Client=19.03.8 Server=19.03.8 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1520

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 942aa44bfae4 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / 62a488b946

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-rsgroup.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-rsgroup.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/testReport/

Max. process+thread count
3960 (vs. ulimit of 12500)

modules
C: hbase-server hbase-rsgroup U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1520/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


ESP32-C6 CZ version of workshop

Add CZ version of a workshop

It was necessary to disable series in layouts/_default/single.html


Cannot use Canvas(frame: CGRect)

Hi,
I have problem using the classes defined in MaLiang.
I have installed the pods and imported MaLiang inside the project.
Then I have make sure that the Maliang folder is in my project's Pod folder. This much is working.
But for some unknown reason, the Canvas class cannot be detected properly. It doesn't show the Canvas(frame:CGRect). Also the Brush is different and Bundle has conflict, not with my code but with some core codes from Xcode. I have tried Clean and re-build, also reinstall pods. All doesn't work
Do you know whats wrong?

What is the version of your Xcode and Swift?
MaLiang requires Swift 4.1, witch comes along with Xcode 9.3.

Yes I have used the version 9.3

Here are some screenshots. Showing:

The Podfile is installed and all files are inside Pod
Imported MaLiang without problem
Canvas(Frame) still cannot detected. And I have tried to build it but still failed.

I always clean and build again after every new pod install and import
See the files below:

As I can see, there's no problem, maybe there's something wrong with your Xcode's build system or auto completion system...
Try to enable the new build system and build again?

Hi, I have trying to figure this thing out for many days now. And I just found out that the Pod files you provided in Cocoapods is outdated.
You can see that in the MaLiang's example there is this part of the code inside MLView.swift
// MARK: - Initialize
public override init(frame: CGRect) {
super.init(frame: frame)
setup()
}
But in the Cocoapods version that I have installed doesn't have. You can see the attached file.
So can you update that? or do you have other suggestions?

Thank you

@zenkog What's the version of MaLiang you have installed?  You can check it in your podfile.lock, The latest version in Cocoapods is 1.1.3.  I think you have installed an old version.

Hi, I have tried to reinstall it but its always the old version. Then I found out that if you check in Cocoapod website you can see that your MaLiang Code is stored there is version 0.1.0. See the screenshot. this is why cannot upgrade. please check it.

So I also tried to specify the version by:
pod 'MaLiang', '~> 1.1.3'
But it failed upon update:

use pod update MaLiang to update it

After "pod update MaLiang", its only updating to ver 0.5.0.
How to get the ver 1.1.3 ?


Add Categories.

Heyo, I want to thank you for your hard work on this app, I like it very much and if without it I don't think I can survive for long on the novels sites.
I just recommend having a categories option like tachiyomi app to add some novels for next to read, finished, etc. And thanks.

Duplicate of #45


Hook all methods with the given class.

Hi, how I can hook all methods with the given class.
And how I can enum if a class have multiple methods with same name but different type a() ; a(android.content.Context); a(java.lang.String,boolean)
Thanks.

Hey unfortunately House does not support hook all methods with given class for now; but this would def be a cool feature;
For your second question; House enum and hook func will return all overloaded function under a class, I am not sure what are you trying to achieve; if you want to intercept a specific one, you can try inspect under intercept tab, and type the classname & method name, house will return a dropdown list of all overloaded ones and you can pick the target one.
Hope that answers your question.

I want to hook some variables in the class. Is it possible?

I don't know honestly, but Frida repo or IRC might be a good place to ask.

And can you add function can re-execute a class or method with n times. It's is nice because some app have encrypt or generation dynamic data, we can execute it n times to get the return data.

Hey, that is totally customizable; House is a tool that generate a base frida script for you; but I would not add features for specific cases such as this one; you can use the script House already generated and add an counter loop; should be just couple lines of javascript; there is no point for me to add a special feature for that.

I don't think this works on a non root phone if we repack the apk with frida?


feat(neo-tree):shortcuts for opening neotree at buffer location

Added shortcuts for opening neotree at the location of the opened buffer.
Helpful for concentrating on a certain folder and manually using . in neotree  to cd into a dir again and again.

Not a fan of this. Closing...
Thank you anyway!


Remove unneed 'volatile' keyword

No volatile keyword need right ?
if there is an issue, it should be done with mutex / atomic

merging because there is no need of volatile keyword here


random.Generator.binomial infinite loop

I noticed the binomial method is implemented for the numpy Generator class, even though it's not listed in the supported distributions in the documentation.
When generating numbers with a large N (the first argument = 700), the method enters into an infinite loop.
For very small N (=10), it generates exactly the same sequence as pure numpy.
For intermediate values of N (=301), the results are similar but deviate from numpy.
I'm using numba 0.59
This should reproduce the error (pick different values of n to test the 3 cases):
n = 700
import numpy as np
from numba import njit, objmode

def get_bins_np(gen, n):
    return gen.binomial(n, 0.1, 100)

@njit
def get_bins_obj(gen, n):
    with objmode(x='int64[:]'):
        x = gen.binomial(n, 0.1, 100)
    return x

@njit
def get_bins(gen, n):
    return gen.binomial(n, 0.1, 100)

gens = [np.random.default_rng(0), np.random.default_rng(0), np.random.default_rng(0)]

x1 = get_bins_np(gens[0], n)
print(x1[:10])
x2 = get_bins_obj(gens[1], n)
print(x2[:10])
print(np.array_equal(x1, x2))
x3 = get_bins(gens[2], n)
print(x3[:10])
print(np.array_equal(x1, x3))
print((x1.mean() - x3.mean())/x1.mean())

I'm implementing this bootstrap sampling library with numba, so I had to go with objmode for now.

I can confirm the program appears to "hang". I looked at this via the htop tool and observed:

@kc611 could you kindly take a quick look here? IIRC you are the original author here and this issue will benefit from your input, thank you.

I think there's a bug here in the case == 52 branch:
https://github.com/numba/numba/blob/4318ee4aeaaad99fa5965d8b723fc0c91581cab9/numba/np/random/distributions.py#L644-L676
If the branch on (A > ...) is false, then the execution should fall through to case == 60 (as it does in the C code in NumPy), but it does not, the case remains in state 52, and the while(1) loop is re-entered with this same state, the case == 52 branch is hit again and the same sequence happens repeatedly, hence it hangs.
CC @kc611 do you agree with this assessment?

@kc611 I agree, there are two separate problems, the bug in https://github.com/numba/numba/issues/9493#issuecomment-2079769913 and also the incorrect values which I've filed as #9734. I'm adding both to the 0.61 milestone as I have patches locally, they are thankfully just minor changes.


Change specification enumerations to ALLCAPS

Coverage increased (+0.06%) to 76.192% when pulling 83dc1531549e53d24a713b2f4c0809f52dae6305 on tpw/spec-allcaps into 331540293ac0b55f80d034294d0f573dd8e2545d on master.


In case something goes wrong try to be helpful

Provide links to github issues and discord.

@admc


Instrumentation for performance metrics like Apollo Optics

Hi :) First of all, congrats to an awesome library.
I saw Apollo Optics for performance monitoring. There are clients for nodejs and ruby, both based on the general agent description.
When adding a PHP agent, I was wondering where would be a good place to hook into instrumentation. As far as I can see mostly a wrapper around field resolvers to time them would be handy.
Any ideas or tips how to add this instrumentation?
PS: I'm not affiliated with Apollo.

Hey thanks!
I looked into node agent and it seems to modify original schema by looping through all fields and wrapping their resolvers with optics functions. Technically you can do the same with graphql-php schema.
But on the other hand iterating over hundreds or thousands of fields is not the best way to do it in PHP. So it might make sense to provide hooks before/after field execution on library level.
PR for this feature is welcome!
If you decide to prepare such PR I suggest you to wrap this call with before and after callbacks and introduce static method on Executor to set these callbacks (like setFieldHooks(callable $beforeResolve, callable $afterResolve)).
Prefer static at this point because we may refactor executor later and it will be way easier to maintain backwards compatibility for simple static hooks. But if you have other opinion - I am open to discussion.

One more thing to keep in mind for your optics agent is that resolvers may return promises. So promiseAdapter must be also passed to hooks (in addition to other arguments) in order to check for isThenable and act appropriately.

Thanks a lot for your input :) I think for now I don't have the time to work on this.
I might pick it up in a few months!

@adri @vladar I've got Instrumentation setup for WPGraphQL. I've followed the proposed spec here: https://github.com/apollographql/apollo-tracing
You can see my implementation here: https://github.com/wp-graphql/wp-graphql-insights
It's super early (just worked on it a few days last week), but it follows the same approach as the node instrumentations I've seen where it wraps the entire schema. So far, I've not seen any noticeable performance differences with the tracing enabled vs disabled. . .but, I haven't done any significant testing. . .
I'm not sure what the best approach would be to create something that works for any implementation of this library though. I'm making use of WordPress hooks/filters to accomplish my implementation.
Feel free to use anything I've done in my implementation, or even make suggestions on how my implementation could be better.
Thanks!

For anyone interested, there is another proposal on how to enable apollo tracing for any existing schema: see https://github.com/webonyx/graphql-php/issues/289#issuecomment-399633709 PRs are welcome!


Computational Biology / CS and Pre Med

Jason walker could help. And so could Bret Barkley

and Kenan Rustamov
and Tao sheng

wow so many people

so many

@varughese should we ask jay to write this now

jay aint gonna write this bro

alright I'll ask tao


chore(sdk): remove dependency on afgo root module

Depends on https://github.com/hyperledger/aries-framework-go/pull/3603

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (fde0b6a) 89.59% compared to head (82bcd00) 89.59%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #463   +/-   ##
=======================================
  Coverage   89.59%   89.59%
=======================================
  Files          88       88
  Lines        3230     3230
=======================================
  Hits         2894     2894
  Misses        219      219
  Partials      117      117

Impacted Files
Coverage Δ

cmd/wallet-sdk-gomobile/did/wellknown.go
100.00% <ø> (ø)

pkg/credentialsigner/signer.go
65.57% <ø> (ø)

pkg/did/wellknown/wellknown.go
90.38% <ø> (ø)

pkg/common/doc_loader.go
94.59% <100.00%> (ø)

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


Deeplink doesn't work when the app is killed or inactive in iOS

Hi,
I have problem with the deeplink in iOS.  The deeplink won't open the correct page only if the app is killed or inactive (only the initial page/screen).  But it works perfectly on the app that run in the background or the active one.
After debugging, I found that didFinishLaunchingWithOptions in iOS file is not called when the app is killed.
iOS emulator version: iOS 15.2
Flutter version: 2.2.3
Any solution?
Thanks.

@munyaaa
You are on older version of stable. Please upgrade to latest (2.8.1) and try again to see if it works.
If not, please provide a complete minimal code sample along with steps to replicate that we can use to verify this behavior.
Thanks.

@darshankawar
Inside AppDelegate.swift, after did the NSLog the didFinishLaunchingWithOptions is not called.
override func application(
    _ application: UIApplication,
    didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
) -> Bool {
    flutterViewController = window.rootViewController as? FlutterViewController
    deepLinkChannelService.setUpDeepLinkChannel(view: flutterViewController)
    handleDeeplinkUtil.handleDeeplinkWhenAppIsKilled(launchOptions, deepLinkChannelService: deepLinkChannelService)
    return super.application(application, didFinishLaunchingWithOptions: launchOptions)
}

This the function inside HandleDeeplinkUtil
func handleDeeplinkWhenAppIsKilled(_ launchOptions: [UIApplication.LaunchOptionsKey: Any]?, deepLinkChannelService: DeepLinkChannelService) {
    if let deepLink = remoteNotification[DeepLinkConstants.DEEP_LINK_KEY] as? String {
    let isDeepLinkOpened = deepLinkChannelService.onDeepLinkReceived(deepLinkUrl: deepLink)
}

please provide a complete minimal code sample along with steps to replicate

@munyaaa


Define required collections for SBG 1 workflows

Define the collections required to run the various applicaiton packages and store their outputs.
Environment agnostic (e.g. we will create them in dev, test, prod, etc) from an automated script.

Datasets Needed:

SBG-L1B-PRE
SBG-L2A_RFL
SBG-L2A_RSRFL
SBG-L2A_CORFL
SBG-L2B_FRCOV
SBG-L2B_VEGBIOCHEM


Quick second key press is ignored

When quickly pressing two buttons one after another, only the first one is affecting the game. Giving bigger delay between them helps, but that delay is pretty annoyingly big. After playing for 15 minutes, it's the mostly annoying thing which discourages me from trying more.

Issue reproduces with different keys only. Pressing one key quickly performs much better.

You actually gave me a good idea on how to improve the controls. Thank you! I'll see what I can do...

Tried to fix it in v1.1 https://github.com/tsoding/eepers/releases/tag/v1.1 Please let me know if it feels better for you

Fixed, thank you!


Support for dll

Thank you for the great effort. Everything builds like a charm. I was wondering about what additional effort is required to make shared libraries possible. I have to integrate Caffe with a huge .net project. The only way I can properly interop is by building a managed dll wrapper around it. I tried the following

defined the usual __declspec(dllexport)/import based on CMAKE header CAFFE_EXPORTS.
Added this definition to every Register Class and Instantiate class. This works without GPU. If GPU support is added the forward and backward GPU functions throw weird error saying dllimport is not allowed in definition, even though the macro is defined as dllexport in all those files.
I was wondering if you have a working solution.
Kind Regards,
Rick

Hi Rick.
I saw that you reported the problem in an earlier PR. I think that the changes I made to the CMake build would make building dlls possible (given that we put the CAFFE_EXPORT macro in every file which I did not do) but did not have time to try.
Can you confirm that the GPU problem is there with my fork too?
If you want to submit me a PR so that I can try your changes and send you some feedback on what could be done to have GPU support I would be willing to help.
Otherwise, I guess you could wrap a static library in an other pure C++ DLL (or mixed CLR) and than interop with this one instead?

Thank you. I will make the same changes in your visual studio branch and see how it goes.


Piper/handle already waiting error during bonding

Fixes #737
What was wrong?
Looks like we semi-regularly encounter situations where we're trying to bond with the same peer which causes an AlreadyWaiting exception to bubble.
How was it fixed?

Catch the AlreadyWaiting exception in bond and return False indicating that bonding failed
Do a check prior to pinging to check if we're already waiting for a pong.
Use context manager for managing self.ping_callbacks to ensure the event is always cleared.

Cute Animal Picture

This doesn't actually appear to have solved the problem but I need to investigate more in the morning when I'm fresh.

replaced by #765


Updating VNET dependencies

Updating VNET dependencies to allow Azure Monitor and additional certificate URLs

@alfantp : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @carldc - Thanks for your review. In the public repo, the article author, the service PM, or a member of the content team needs to review and sign off before a PR can be merged. Thank you.
@yegu-ms - Could you review the proposed update to your article? Thanks.

#sign-off

I put the DNS domain names in the remaining list item (updated in this PR) in italics for consistency; merging now.


python310Packages.ytmusicapi: 0.22.0 -> 0.24.0

Description of changes
https://github.com/sigma67/ytmusicapi/releases/tag/0.24.0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Perhaps mopidy-ytmusic gets updated and we don't need to patch.
https://github.com/OzymandiasTheGreat/mopidy-ytmusic/issues/68


How do I let GraphZahl generate the documentation?

In the README there's a png that shows that GraphZahl can generate schema documentation for GraphiQL.

Now in my project where I'm tinkering a bit with GraphZahl, I'm not using GraphiQL. I'm literally just running XCTests and debugging using print statements. 😅
And I'd like to be able to print this documentation that GraphZahl generates, because I'd like to be able to see what GraphZahl makes of my classes. But I can't figure out how. Can you tell me how?

Sure thing!
So this is actually a feature of GraphQL in general. But GraphQL allows type introspection. GraphiQL gets this documentation via this.
If you run the following query you can get it as JSON:
query IntrospectionQuery {
  __schema {
    queryType {
      name
    }
    mutationType {
      name
    }
    types {
      ...FullType
    }
  }
}

fragment FullType on __Type {
  kind
  name
  description
  fields(includeDeprecated: true) {
    name
    description
    args {
      ...InputValue
    }
    type {
      ...TypeRef
    }
    isDeprecated
    deprecationReason
  }
  inputFields {
    ...InputValue
  }
  interfaces {
    ...TypeRef
  }
  enumValues(includeDeprecated: true) {
    name
    description
    isDeprecated
    deprecationReason
  }
  possibleTypes {
    ...TypeRef
  }
}

fragment InputValue on __InputValue {
  name
  description
  type {
    ...TypeRef
  }
  defaultValue
}

fragment TypeRef on __Type {
  kind
  name
  ofType {
    kind
    name
    ofType {
      kind
      name
      ofType {
        kind
        name
        ofType {
          kind
          name
          ofType {
            kind
            name
            ofType {
              kind
              name
              ofType {
                kind
                name
              }
            }
          }
        }
      }
    }
  }
}

PS: I just ran graphiql in the browser and saw what query it was sending ;)

GraphZahl is also actually using GraphQLSwift under the hood. But it doesn't make this very visible on purpose.
If you go to GraphQLSchema+resolve.swift and set a breakpoint you can also see it directly with the debugger

On the other hand GraphQL Playground can create a graphql schema file.
This could be a useful feature to include

If you run the following query you can get it as JSON:

Thank you, that made it clear to me that I need to start using GraphiQL, because that JSON is huge and I can't use it to quickly look whether it has detected one of my class properties and how it sees it.

Yeah that's sadly the case.
This also relates to #4 since we want developers to know early when a function or property of theirs looks like it should be included but couldn't


Add message server integration tests for client/connection/channel handshake setup messages

Summary
They are missing from modules/core/keeper/msg_server_test.go. Needed for code coverage of integration tests. Example test case:

create a chan open init that fails in app callback
create a chan open init that succeeds in the call after

This tests capability creation persistence

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

Capabilities are gone! And handshakes are being moved away from, so this issue is no longer useful. Closing!


[OG Predicators PR] - Data ordering and op pruning

Adding data ordering and op pruning from OG Predicators repo.

@wmcclinton did you mean to open this PR on the fork instead?

Yes, I think he very much did!


[Bug] Settings do not work in conjunction with each other

Enabling both 'Clean on app startup' and 'Exit after clean up' will result in the latter setting being ignored.

Actually, this is not a bug. Description of 'Exit after clean up' setting states: 'Exit after Clean button is clicked and clean up is completed'. Therefore, you have to perform manual clean up if you want it to exit automatically. Otherwise, using both settings at once may prevent the user from accessing the UI.

"Otherwise, using both settings at once may prevent the user from accessing the UI."  Lol... that's what I was kind of hoping to do!  ;)
Of course it makes it near impossible to change the settings again... but clearing the Cache Cleaner app's data would take care of that!

I am afraid that the vast majority of users would not be able to do that and would rather call the app useless.

I concur!


Feature Proposal: Listen to other topics -> Broadcast channel?

As already proposed in #80 (but closed due to non-feasibility with the old PubSubClient), there should be an interface to subscribe to other devices/nodes.
My use case is to have a broadcast channel to send alarms and messages to all other devices.
In detail: I have a central OpenHAB server running with a local MQTT. The OpenHAB server should be able to publish MQTT message to all connected (Homie-)device, e.g. to trigger an alarm. I have some nodes with buzzer and display so they could show even some alarm messages.
You may even define a Broadcast channel in the Homie convention, e.g. $broadcast/<level> and $alarm/<type> ?
So, in my idea, any HomieNode shall be able to subscribe to broadcasts and alarms and gets called back.
Personally I would prefer an extra input-handlers e.g. virtual void handleBroadcast(EBCstLevel level, String text).
Update 2016-09-01: So, in my current proposal there is no way for a Homie Node to directly publish on a broadcast channel.
If I get some feedback here, I will develop a proposed solution in my local fork.

What about a way for you to subscribe to any topics you want? This way you can do pretty much everything. The current AsyncMqttClient implementation only allow one callback for messages, so you cannot override it, as Homie already handles messages. But I plan (https://github.com/marvinroger/async-mqtt-client/issues/21) to allow multiple callbacks. Would it be alright for you?
The broadcast channel is not a bad idea, but people will probably want more and more MQTT related-stuff anyway, so a complete access to the underlying MQTT client would solve all these problems.

I think, broadcast channels should be part of Homie (the ESP implementation and the convention), but subscription to arbitrary topics should not. It's always good to have a quite strict API to force people to follow the convention.
So to allow arbitrary subscription, Homie should only offer a pointer (or reference) to the AsyncMqttClient instance, so anybody can bypass Homie and implement there own callback (as soon as
https://github.com/marvinroger/async-mqtt-client/issues/21 is implemented).
I will be on a business trip and then on holidays during the next weeks. When I return I will develop my local fork to add support for a broadcast channel.

The abitrary topics part would not be part of the convention, and yes to achieve arbitrary subs, you can use Homie.getMqttClient() which returns a reference to AsyncMqttClient.
Let's implement a broadcast channel, then!

Have great holidays, by the way. :wink:

Broadcast channel in the Homie convention.

Why devices/$broadcast/#? Would devices/all/# or devices/broadcast/# be more natural?

Everything "special" in Homie starts with a $. Think parsing. When you parse the topic, you only have to check if the subtopic starts with a $ to know it is a special one.

Why devices/$broadcast/ and not just $broadcast/ ? A broadcast is not a device, so $broadcast should not be in a subtree of devices. If you do not want to place it at toplevel, maybe you could introduce a new top-level hierarchie $homie/ (or homie/).

Well, actually devices/ is the base topic and is configurable, so you can use pretty much any root topics you want. I'll indeed maybe change the default topic from devices/ to homie/.

I started to implement, now I wonder how the _mqttPayloadBuffer is ever deleted in BootNormal?

Marvin, could I suggest that the readme.io documentation is updated to clarify where in the MQTT topic namespace broadcasts will be published?
I would prefer anchoring it from the configured base root. Imagine your MQTT server has several generations of firmware running; hardcoding homie/ as the broadcast path would force you into running several MQTT brokers, with some judicious replication of selected topics.


Circular Import Error in wagtail.cotrib.forms.models for a FormPage in 2.11

Issue Summary
When upgrading from a previous version of Wagtail, the form pages are not working anymore. I'm getting a circular import error for code that previously worked. The ONLY change was upgrading to 2.11
Steps to Reproduce

Update virtual env to use Wagtail 2.11
Startup runserver
Now getting the following error:

ImportError: cannot import name 'FORM_FIELD_CHOICES' from partially initialized module 'wagtail.contrib.forms.models' (most likely due to a circular import) (/home/user/sandbox/clients/client/project/web/env/envname/lib/python3.8/site-packages/wagtail/contrib/forms/models.py)
My expectation is that the code would run as before.

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: yes

Technical details

Python version: 3.8.
Django version: 3.1.3.
Wagtail version: 2.11.
Browser version: Version 86.0.4240.111

Hi @davemerwin - thanks for the report. Please can you include the full traceback of the error?

Here's the fill stack trace
(client2) user@user:~/sandbox/clients/client/client/web$ python manage.py runserver
Watching for file changes with StatReloader
Exception in thread django-main-thread:
Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/usr/lib/python3.8/threading.py", line 870, in run
self._target(*self._args, **self._kwargs)
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/utils/autoreload.py", line 53, in wrapper
fn(*args, **kwargs)
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/core/management/commands/runserver.py", line 110, in inner_run
autoreload.raise_last_exception()
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/utils/autoreload.py", line 76, in raise_last_exception
raise _exception[1]
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/core/management/init.py", line 357, in execute
autoreload.check_errors(django.setup)()
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/utils/autoreload.py", line 53, in wrapper
fn(*args, **kwargs)
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/init.py", line 24, in setup
apps.populate(settings.INSTALLED_APPS)
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/apps/registry.py", line 114, in populate
app_config.import_models()
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/apps/config.py", line 211, in import_models
self.models_module = import_module(models_module_name)
File "/usr/lib/python3.8/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 671, in _load_unlocked
File "", line 783, in exec_module
File "", line 219, in _call_with_frames_removed
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/wagtail/contrib/forms/models.py", line 16, in
from wagtail.admin.mail import send_mail
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/wagtail/admin/mail.py", line 10, in
from wagtail.admin.auth import users_with_page_permission
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/wagtail/admin/auth.py", line 8, in
from django.contrib.auth.views import redirect_to_login as auth_redirect_to_login
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/contrib/auth/views.py", line 10, in
from django.contrib.auth.forms import (
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/contrib/auth/forms.py", line 21, in
UserModel = get_user_model()
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/contrib/auth/init.py", line 157, in get_user_model
return django_apps.get_model(settings.AUTH_USER_MODEL, require_ready=False)
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/apps/registry.py", line 209, in get_model
app_config.import_models()
File "/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/django/apps/config.py", line 211, in import_models
self.models_module = import_module(models_module_name)
File "/usr/lib/python3.8/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "/home/user/sandbox/clients/client/client/web/profiles/models.py", line 20, in
from products.models import AccountToProduct
File "/home/user/sandbox/clients/client/client/web/products/models.py", line 27, in
from wagtail.contrib.forms.models import (
ImportError: cannot import name 'FORM_FIELD_CHOICES' from partially initialized module 'wagtail.contrib.forms.models' (most likely due to a circular import) (/home/user/sandbox/clients/client/client/web/env/client2/lib/python3.8/site-packages/wagtail/contrib/forms/models.py)

Thanks for the extra detail. I've now been able to replicate this independently by the following steps:

Create a new project with wagtail start myproject

./manage.py startapp customuser and add 'customuser' to the bottom of INSTALLED_APPS

Edit customuser/models.py as follows:
from django.contrib.auth.models import AbstractUser

class CustomUser(AbstractUser):
    pass

Add AUTH_USER_MODEL = 'customuser.CustomUser' to settings

Run ./manage.py makemigrations and ./manage.py migrate

Add from wagtail.contrib.forms.models import FORM_FIELD_CHOICES to the top of customuser/models.py

Run ./manage.py check

Looks like this is happening because importing wagtail.contrib.forms.models is setting off a chain of imports starting with wagtail.admin.mail, then Wagtail's authentication helpers, then django.contrib.auth which tries to import the custom user model, leading to a circular import if the original import of wagtail.contrib.forms.models was in the same place as that custom user model. Investigating further now...

@davemerwin What version of Wagtail were you running before upgrading to 2.11?

@gasman I was using 2.5.1

Cheers - looks like this bug was introduced in 2.7, so that checks out. Have now submitted a fix in #6522.


A Flutter logo widget

Instead of a PNG, the Flutter gallery widget is now drawn in code.
There's now a FlutterLogoDecoration class that paints the flutter logo
anywhere you can use a Decoration (e.g. AnimatedContainer).
There's now a FlutterLogo class that honors the IconTheme.
The About dialog box API now takes a Widget for the applicationIcon,
instead of an ImageProvider. It uses IconTheme to make the icon the
right size instead of using an Image widget.
Add padding, duration, and curve properties to the DrawerHeader.
Make the child of a DrawerHeader optional.
Clean up UserAccuntsDrawerHeader a bit.
Add some useful properties and methods to EdgeInsets.
Add some debug logic to RenderDecoratedBox to catch unpaired
save/restore calls when possible.
Make GestureDetector fill its parent if it has no children. Fixes
https://github.com/flutter/flutter/issues/5380

I've addressed every comment except the gesture detector change; I'll do that then once that's landed will land this one.

It's not as if I have anything to add after the GIANT GOLD STAR but LGTM.


DOCS: Single quotes /docs/getting-started.md

Description:

update quotes in getting started example to be matching single quotes
https://react-charts.tanstack.com/docs/getting-started

Before:
const data: Series[] = [
   {
     label: 'React Charts",
     data: [

After:
const data: Series[] = [
   {
     label: 'React Charts',
     data: [

:tada: This PR is included in version 3.0.0-beta.35 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Technical issues around GitHub-based content management (placeholder)

From @joncison on December 18, 2018 13:42
Use this thread to list (refer to) specific actions, and for general technical discussion, around the mooted GitHub-based content management architecture (see https://github.com/bio-tools/biotoolsRegistry/issues/355 and https://github.com/bio-tools/biotoolsRegistry/issues/242)
Copied from original issue: bio-tools/biotoolsRegistry#399

hey @ypriverol - here's the (pinned) issue that is simply a list of threads (maintained in comment of 25 Jan) around the integration of tools metadata - currently just from my/bio.tools perspective. I agree the consideration of I/O/parameters is important, please feel free to add that (or anything else)


Add default value for audio driver

Can now use .audio.device=default similar to .video.display=default
You can still pick another driver, such as alsa or oss, if you want.

This probably needs a testing template, as well. If nothing else, you need to add linux-modules-extra and alsa-utils.

Added example:
 0 - Front Left
 1 - Front Right
Time per period = 3.017038
 0 - Front Left
 1 - Front Right
Time per period = 3.049002

This example uses "sudo", since there is not yet a good way to add the user to the "sound" group

https://github.com/lima-vm/lima/issues/1686


minor: missing open parenthesis

Resolves documentation errors.
Also note that the links that you have provided to the documentation need to be updated (branch name should be develop, or you should push the master branch, if that exists)
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines, including the relevant style guides.
[x] Read and understand the Code of Conduct.
[x] Read and understood the licensing terms.
[x] Searched for existing issues and pull requests before submitting this pull request.
[x] Filed an issue (or an issue already existed) prior to submitting this pull request.
[x] Rebased onto latest develop.
[x] Submitted against develop branch.

Description

What is the purpose of this pull request?

This pull request:

Fixes a minor problem with the documentation: missing opening parenthesis in the code example in the README

Related Issues

Does this pull request have any related issues?

None.
Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

@stdlib-js/reviewers
... only updating the README!

@bguiz Thanks!

@bguiz And yeah, we are aware about the links. We'll be pushing a master branch in the near future, but are waiting to finish a few features before doing so.


Allow filtering by any value in list

Currently filtering requires all the filter parameters to be present and it only allows one value for each filter key. This enables passing in multiple values for a key and then filtering by whether any of them are present.
This is being added so we can restrict the drop down for organisation choice in the new sign up - currently services and service groups are also appearing.

Any concerns about security for this introduction?

I think it should be safe - the attribute on which you can filter is locked down in code and it's no different from the existing functionality in the kind of matching strings you can pass in.


Error computing embeddings

When running the compute_embedding.py I get this error.
Using backend: pytorch
Downloading gin_supervised_contextpred_pre_trained.pth from https://data.dgl.ai/dgllife/pre_trained/gin_supervised_contextpred.pth...
Pretrained model loaded
Total data:  172988
  0%|                                                                                | 0/172988 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "/home/ec2-user/SynNet/scripts/compute_embedding.py", line 143, in <module>
    embeddings.append(model(smi))
  File "/home/ec2-user/miniconda3/envs/rdkit/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1051, in _call_impl
    return forward_call(*input, **kwargs)
TypeError: forward() missing 2 required positional arguments: 'categorical_node_feats' and 'categorical_edge_feats'

When trying to run the compute_embedding_mp.py I get the following error
Using backend: pytorch
Downloading gin_supervised_contextpred_pre_trained.pth from https://data.dgl.ai/dgllife/pre_trained/gin_supervised_contextpred.pth...
Pretrained model loaded
Total data:  172988
Traceback (most recent call last):
  File "/home/ec2-user/SynNet/scripts/compute_embedding_mp.py", line 29, in <module>
    embeddings = pool.map(gin_embedding, data)
NameError: name 'gin_embedding' is not defined

I think this can be resolved by changing gin_embedding to model but that then results in the above error.

This has now been fixed. To summarize the problem, the 'model()' should have been replaced by the 'mol_embedding()' function (which creates the GIN embeddings from the pretrained model). I have replaced it now with the right function names, and moved this and related functions to syn_net/utils/predict_utils.py, as the mol_embedding() function is used by both scripts/compute_embedding.py and scripts/compute_embedding_mp.py


Create a manifest file with no envs

We need to override environmental variables at deployment time. If a
variables is specified in the manifest file it isn't being overriden.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #33   +/-   ##
=======================================
  Coverage   63.25%   63.25%
=======================================
  Files          21       21
  Lines         430      430
  Branches       39       39
=======================================
  Hits          272      272
  Misses        150      150
  Partials        8        8

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 b872ca1...4f3d43d. Read the comment docs.


battery.remaining_percent returns negative value

Hi there!
I'm running on SITL setup with latest releases : PX4 (1.11.0) + mavsdk_server (0.30.1) + mavsdk-python (0.12.0).
My pre-flight-checks are failing due to the negative value that is returned for battery.remaining_percent.
Just by running mavsdk-python/examples/telemetry.py you will notice the following.
Waiting for mavsdk_server to be ready...
Connected to mavsdk_server!
Position: [latitude_deg: 47.3977504, longitude_deg: 8.5456064, absolute_altitude_m:<PHONE_NUMBER>652344, relative_altitude_m: -0.08500000089406967]
**Battery: -0.009999999776482582**

It wasn't the case with my earlier setup which uses a slightly older versions of (PX4 + mavsdk_server + mavsdk-python) components.
Appreciate your attention!
cheers,
Ram

Could it be that PX4 sends that value? Do you have a way to check that from the PX4 side? I guess we may have an error somewhere on the way (numbers get translated), but it would be nice to know what PX4 sends in that case :+1:.

Battery stuff has changed a bit, so yes we should check what PX4 is sending now.


Fix Cognito email case sensitivity

Use configuration to set if emails should be case sensitive.

Fixes #57
To consider: Deploying this will cause the user pool to be re-created. All users will have to log in again. Anyone who hasn't refreshed the app will get "not authorized" errors displayed.

Don't need this any more as the register API normalises this for us.


refactor soul-spring-boot-starter test classes

// Describe your PR here; eg. Fixes #issueNo
refactor soul-spring-boot-starter test classes

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #955 (8be4934) into master (c9f50d8) will increase coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #955      +/-   ##
============================================
+ Coverage     76.70%   76.75%   +0.05%
+ Complexity     2038     2037       -1
============================================
  Files           331      331
  Lines          7507     7507
  Branches        832      832
============================================
+ Hits           5758     5762       +4
+ Misses         1307     1303       -4
  Partials        442      442

Impacted Files
Coverage Δ
Complexity Δ

...soul/client/tars/TarsServiceBeanPostProcessor.java
19.44% <0.00%> (-9.73%)
5.00% <0.00%> (-3.00%)

...soul/client/sofa/SofaServiceBeanPostProcessor.java
38.70% <0.00%> (+17.74%)
7.00% <0.00%> (+2.00%)

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 c9f50d8...8be4934. Read the comment docs.

Codecov Report

Merging #955 (8be4934) into master (c9f50d8) will increase coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #955      +/-   ##
============================================
+ Coverage     76.70%   76.75%   +0.05%
+ Complexity     2038     2037       -1
============================================
  Files           331      331
  Lines          7507     7507
  Branches        832      832
============================================
+ Hits           5758     5762       +4
+ Misses         1307     1303       -4
  Partials        442      442

Impacted Files
Coverage Δ
Complexity Δ

...soul/client/tars/TarsServiceBeanPostProcessor.java
19.44% <0.00%> (-9.73%)
5.00% <0.00%> (-3.00%)

...soul/client/sofa/SofaServiceBeanPostProcessor.java
38.70% <0.00%> (+17.74%)
7.00% <0.00%> (+2.00%)

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 c9f50d8...8be4934. Read the comment docs.


fix: Fix typo in lib/pluginRunner

Thanks!

v5.0.2 released https://github.com/taskrabbit/node-resque/releases/tag/v5.0.2

Would it  be possible to patch version 4?

https://github.com/taskrabbit/node-resque/issues/217


Support multiple migrations-directories

Is your feature request related to a problem? Please describe.
The plugin only considers migrations in the database/migrations directory. If migrations are spread out in several directories, e.g. when using Laravel Modules, some Model stubs are generated without @property definitions. This results in many false positive UndefinedMagicPropertyAssignment errors.
Describe the solution you'd like
First, a warning message would be nice when a table can't be found (here).
Second, a way to specify multiple directories for migrations would be nice. I'm not sure what would be the best way to do this.
Describe alternatives you've considered
Temporarily moving all migrations into database/migrations before running Psalm fixes the issue, but it is rather inconvenient.
Additional context
Our directory structure looks like this:
database/
    migrations/
modules/
    MobuleA/
        database/
            migrations/
    MobuleB/
        database/
            migrations/

Hello @marcusrettig
To support migrating from a specific migration directory you can customize your module's service provider by overriding boot() function and adding this line of code:
$this->loadMigrationsFrom("YOUR_SPECIFIC_MODULE_MIGRATIONS_DIRECTORY");


Set up a grafana/prometheus node

Basic DevOps EPIC
Background
We need somewhere to put metrics.
Done when

[x] Node provisioned.
[x] prometheus setup
[x] grafana 🍌 setup

Live at https://grafana.palomachain.com/


Show all entries in its own line

In my vault I have files that have two or more headings with the same/similar term like this:

When using file search they both appear in the results, but when opening the file I alway jump to the first instance of the search term:

It'd be great to circle through the items in the search modal to choose at which position to open the file

Thank you for your FR, @tim-hilde :)
For Another Quick Switcher, headings are meant to be a filter target, and there was never an intention to enable jumping to them. Therefore, there are no plans to address this at the moment.

I would seriously love this feature too! Please reconsider adding this :)


Implement passport based oauth in backend

TODO LIST

[ ] add github oath
[ ] add google oauth
[ ] add email password auth

So continue with Supabase or not?

So continue with Supabase or not?

for now, we can continue with the supabase if some people outside our team want to contribute they  can implement this. in the long term, we will shift to a standalone server one day.


tmuxinator not working with tmux 1.9a

i've updated tmux from version 1.8 to 1.9a using homebrew...
but tmuxinator stopped creating the panels or windows correctly
simple workaround is to use brew switch tmux 1.8

It worked only when I restart the machine.
Using tmux 1.9a on Ubuntu 4.12


4.x: Improved parsing of HTTP/1 prologue and headers.

Description
Improved parsing of HTTP prologue and headers.

comparison through long words instead of bytes (faster CPU handling)
the "fast path" for requests that do not need headers is improved, Connection header has optimized processing, as it is always used by Helidon webserver, and original code always had to use LazyString.stripOws which was sub-optimal; new version does a fast check for close and keep-alive connection options and bypasses this
lazy headers are not copied when creating Headers, so the stripOws method is only called when the header is requested by user (or when validation is turned on)

Relevant improvements (JMH tests run on my machine):
==================== HttpPrologueParsingJmhTest.techEmpower (+8.27%)
                              Baseline ████████████████████████████████████████████████████████████████████████████████████████████ 58250706.875 ops/s
                               Current ████████████████████████████████████████████████████████████████████████████████████████████████████ 63503835.499 ops/s


Better Figure Segmentation through Edge Detection?

This may sound weird, but is it possible to use edges of regions to redefine figure segmentation to make it more accurate?

@DonaldTsang Have you tried other models?
Like https://github.com/backseason/PoolNet/issues which supports joint training with edge datasets.

Technology is kicking in fast https://github.com/KichangKim/DeepDanbooru/issues/5#issuecomment-820300209


turtle depends on a deprecated library, system-filepath.

I tried to replace optparse-applicative with Turtle.Options which is simpler.
However, its dependence on system-filepath deterred me from adoption.

That particular deprecation is highly contested.

The main reason that turtle uses system-filepath is that it's the only path library that:

treats paths as a new type and not a synonym for String/ByteString
has an IsString instance for paths

However, perhaps I should just take ownership of system-filepath so that it can no longer be deprecated.  Would that resolve your issue?

I think it would.

@Gabriel439 Just to put it on the table: path is now my favorite library for dealing with paths. The IsString instance is missing (for good reason), but I could see an argument for turtle adding an orphan instance for a polymorphic Path given that turtle is for scripting.

 I'm just looking at the suggestion of path now, but it does seem actively maintained, at least.

Unfortunately, system-filepath breaks cross-compilation due to using build-type: Custom, which means bench is broken by transitivity.
(I have no interest in what solution is picked so long as that is resolved :))

You could replace system-filepath with http://hackage.haskell.org/package/path


Provide open API specs for pending proofs

This is as a reference for the app team. We may want to keep this unmerged until it's actually implemented.

Closing as this is already a part of #377


Can't save a Python notebook with caps on

Environment data

VS Code version: 1.52.1
Jupyter Extension version (available under the Extensions sidebar): v2020.12.414227025
Python Extension version (available under the Extensions sidebar): v2021.1.502429796
OS (Windows | Mac | Linux distro) and version: Windows
Python and/or Anaconda version: Python 3.8.7
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Jupyter server running: Local

Expected behaviour
Can save a Python notebook when the caps lock is on.
Actual behaviour
Can't save a Python notebook when the caps lock is on.
Steps to reproduce:

Create a new blank Jupyter Notebook
Write anything just to be able to save
Enable the caps lock with your keyboard
Try to save with Ctrl+S, or save as with Ctrl+Shift+S (same result via the menu)

Logs
No log at all is added when I try to save. Nothing is triggered.
Note

I can save the changes when closing the tab, thanks to the prompt about unsaved changes.
My VS Code isn't broken. Saving works with other types of file. Only notebooks encounter this bug.

Thanks for filing @Drarig29. I was able to repro this behavior on the webview notebook. We'll discuss this in an upcoming meeting. In the meantime, this issue is not present on the new native notebooks, You can try it out if you use VS Code Insiders. (https://code.visualstudio.com/insiders/)

Thanks for filing @Drarig29. I was able to repro this behavior on the webview notebook. We'll discuss this in an upcoming meeting. In the meantime, this issue is not present on the new native notebooks, You can try it out if you use VS Code Insiders. (https://code.visualstudio.com/insiders/)

Thanks for your feedback. This issue will be addressed once VS Code adds native support for editing notebooks. Feel free to try the new experience in VS Code Insiders. The new experience is the default.

Thanks for your feedback. This issue will be addressed once VS Code adds native support for editing notebooks. Feel free to try the new experience in VS Code Insiders. The new experience is the default.


Kubelet: Add rkt as a runtime option

Sadly, as I finished this I realized we need to add built-time labels...so I'm gonna do that :)
/cc @yujuhong @dchen1107 @yifan-gu @jonboulle

This is now ready for review, PTAL @yujuhong @dchen1107

LGTM

LGTM.

LGTM

Filed a bug for the shippable failure: #7788

Shippable passed. Merging.

I believe this broke the standard GCE-Debian build. Or, at least, this or #7343. I'm rolling this one back first, sorry.

No problem @zmerlynn! Let us know when the coast is clear and we'll retry. I'd be surprised if this PR is the cause, but there is always a first :)


Mouse cursor extremely large after upgrade to Ubuntu 24.04

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

[X] WSL 2
[ ] WSL 1

Kernel Version
Linux version <IP_ADDRESS>-microsoft-standard-WSL2 (root@941d701f84f1) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.37) #1 SMP Fri Mar 29 23:14:13 UTC 2024
Distro Version
Ubuntu 24.04
Other Software
No response
Repro Steps
I have been using Ubuntu 22.04 for months and the mouse cursor has been a regular size. Yesterday (2024-10-01), I ran sudo do-release-upgrade within the Ubuntu environment and upgraded to Ubuntu 24.04. The upgrade appeared to be successful. After that, I rebooted my computer and upon launching konsole, I found that my mouse cursor is extremely large when it is over the body of a Linux GUI application window. The cursor is large when over all of the applications that I tried (konsole, kdiff3 and emacs).
Expected Behavior
I expect the mouse cursor to be a reasonable size when using a Linux application
Actual Behavior
See the attached video.

When mouse cursor is over the windows desktop (or a windows application) it is a normal sized arrow (white with black outline)
When mouse cursor is over the Linux application window decorations it is a normal sized arrow (grey with a black outline)
When mouse cursor is over the Linux application body, it is a huge arrow (black with a white outline)

https://github.com/user-attachments/assets/9bd4cd1e-b737-417a-ba06-f1b3b1394d5e
Diagnostic Logs

I have 3 monitors connected to my computer and all are set to scale 100% in Windows

>wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.22621.3880

Same problem

Same here with a fresh installation of Ununtu 24.04, no upgrade from previous version of Ubuntu.
The cursor ist large when it enters any GUI application in WSL like Chrome, Firefox, IntelliJ Idea.

wsl --version
WSL-Version: <IP_ADDRESS>
Kernelversion: <IP_ADDRESS>-2
WSLg-Version: 1.0.61
MSRDC-Version: 1.2.5326
Direct3D-Version: 1.611.1-81528511
DXCore-Version: 10.0.26091.1-240325-1447.ge-release
Windows-Version: 10.0.22631.4317

Same problem scalling 100% in windows.
(tried on Ubuntu latest, Debian latest)
>wsl --version
Version WSL : <IP_ADDRESS>
Version du noyau : <IP_ADDRESS>-2
Version WSLg : 1.0.65
Version MSRDC : 1.2.5620
Version direct3D : 1.611.1-81528511
Version de DXCore : 10.0.26100.1-240331-1435.ge-release
Version de Windows : 10.0.22631.4317

https://github.com/microsoft/wslg/issues/61


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-29-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4490

Questions ?
Please refer to the Backport tool documentation


Exposure logging activation under MicroG

When I try to activate exposure logging in Coronalert 1.7.0 under MicroG <IP_ADDRESS>315 it doesn't work: I can slide the slider on the screen below, but when I go back, exposure logging is not activated.
Interestingly, if I do the same with Corona-Warn-App 1.3.1, it does work. And then exposure logging is also active in Coronalert. Switching it off in CWA, also switches it off in Coronalert.
Note that there is also a feature here: under Google Play Services you can only have the app for a single country active and under MicroG, at least CWA and Coronalert run in parallel.

I don't think that's something that will be supported officially any time soon. Anyhow, did you see this reply to a similar issue? It appears to address the issue and provide a solution.

I did see the reply, but the issue is different. I have MicroG + signature spoofing + fake store, MicroG self-checking OK on all items.
The developers might know why Coronalert behaves differently than upstream (CWA).