Retry Raw Http Requests as well

Retry Raw Http Requests
Description
We are currently facing some storage driver exceptions when uploading many small files. Stacktrace (parts removed):
self._driver.upload_object_via_stream( File "/usr/local/lib/python3.8/site-packages/libcloud/storage/drivers/s3.py", line 754, in upload_object_via_stream return self._put_object(container=container, object_name=object_name, File "/usr/local/lib/python3.8/site-packages/libcloud/storage/drivers/s3.py", line 900, in _put_object result_dict = self._upload_object( File "/usr/local/lib/python3.8/site-packages/libcloud/storage/base.py", line 837, in _upload_object response.parse_error() File "/usr/local/lib/python3.8/site-packages/libcloud/storage/drivers/s3.py", line 147, in parse_error raise LibcloudError('Unknown error. Status code: %d' % (self.status), libcloud.common.types.LibcloudError: <LibcloudError in <class 'libcloud.storage.drivers.s3.S3StorageDriver'> 'Unknown error. Status code: 429'>
This change also enables retrying the raw requests. Together with #1588 (for which we have a workaround), this would solve our issue completely and we could keep using libcloud.
I only added a call to retrying the raw requests.
Status
done, ready for review
Checklist (tick everything that applies)

[X] Code linting (required, can be done after the PR checks)
[X] Documentation
[X] Tests
[ ] ICLA (required for bigger changes)

After further looking into the code, it appears the retry does not work for the status exceptions as requests does not automatically raise them. instead we should wrap the retry handler around the "raise_for_status" as well. For now I will make this a draft only and see if we can fix it correclty

I am not super with the current solution if someone has a better idea let me know. Otherwise this would at least give the ability to handle these status code exceptions. I also think the parsing of the 429 into the RateLimitedError is currently not done correctly/not working, but with #1588 we could work around it.
Maybe we need a predicate for the exceptions instead of only the types configurable though @RunOrVeith.

#1588 has been merged so now you can hopefully sync up your changes with latest trunk without too many issues.

@Germandrummer92 Do you have any idea when you will have a chance to work on this PR?
Ideally we would include those changes in the next release, but if it will take a while I will just do new release this week and we can include those changes in the next one.

@Kami Will try and get it done in the next few days. But also fine with putting it in the next release.

@RunOrVeith @Kami
I think like this it's a much smaller and cleaner change and shouldn't break anything while still retrying raw requests and correctly mapping the exceptions before they are checked in the retry class.
re: the change in test_ovh: this test also fails for me on the current trunk code? maybe ovh changed their response code recentlyhere? (obviously parsing the exception message is maybe not the best idea :D)

Yes, but there is another important change:
Before the retry was only wrapping the raw requests request which actually doesn't raise any exception, since we don't explicitly call raise_for_status, instead now it also wraps the creation of the responseCls (line  677 in common/base.py), in which the actual exception is raised (line 166 in common/base.py).
So I actually think the retry wasn't very helpful before since the http exceptions weren't thrown.
I will take a look at the failing tests now, they worked for me locally

@Germandrummer92 Thanks for clarifying. And I already have a fix locally and will merge it shortly :)

I made a couple of small changes (07062df83f8867e11dc73c54a1e5ed3a44115294, 2c3e38087e18de9f452e856d10fdf8ccc5c8b926) and merged it into trunk. Thanks!


Add Remove Channel For Bot

pls add function remove channel for bot
i can't leave from channel

Are you looking for bot.part_channels, or did you mean something else?

Oh sorry after I started reading Twitch docs, and i learned but I forgot to close this issue


[Event Request] New IntegrationEvent in Codeunit 80 "Sales-Post", function PostSalesLine

Hello,
please insert new IntegrationEvent in Codeunit 80 "Sales-Post", function PostSalesLine.
All parameters should get the VAR Parameter.
    local procedure PostSalesLine(var SalesHeader: Record "Sales Header"; var SalesLine: Record "Sales Line"; var EverythingInvoiced: Boolean; var TempInvoicePostBuffer: Record "Invoice Post. Buffer" temporary; var TempVATAmountLine: Record "VAT Amount Line" temporary; var TempVATAmountLineRemainder: Record "VAT Amount Line" temporary; var TempItemLedgEntryNotInvoiced: Record "Item Ledger Entry" temporary; HasATOShippedNotInvoiced: Boolean; var TempDropShptPostBuffer: Record "Drop Shpt. Post. Buffer" temporary; var ICGenJnlLineNo: Integer; var TempServiceItem2: Record "Service Item" temporary; var TempServiceItemComp2: Record "Service Item Component" temporary)
    var
        SalesShptLine: Record "Sales Shipment Line";
        SalesInvLine: Record "Sales Invoice Line";
        SearchSalesInvLine: Record "Sales Invoice Line";
        SalesCrMemoLine: Record "Sales Cr.Memo Line";
        SearchSalesCrMemoLine: Record "Sales Cr.Memo Line";
        TempPostedATOLink: Record "Posted Assemble-to-Order Link" temporary;
        InvoicePostBuffer: Record "Invoice Post. Buffer";
        CostBaseAmount: Decimal;
        IsHandled: Boolean;
    begin
        with SalesLine do begin
            if Type = Type::Item then begin
                CostBaseAmount := "Line Amount";
                OnPostSalesLineOnBeforeTestUnitOfMeasureCode(SalesHeader, SalesLine, TempSalesLineGlobal);
                // Skip UoM validation for partially shipped/received documents and lines fetch through "Get Shipment Lines"
                if ("No." <> '') and ("Qty. Shipped (Base)" = 0) and ("Shipment No." = '') and ("Return Qty. Received (Base)" = 0) and ("Return Receipt No." = '') then
                    TestField("Unit of Measure Code");
            end;
            if "Qty. per Unit of Measure" = 0 then
                "Qty. per Unit of Measure" := 1;

            // Start kvs.dde
            IsHandled := false;
            OnBeforeCallTestSalesLine(SalesLine, SalesHeader, IsHandled);
            if not IsHandled then
            // Stop kvs.dde
              TestSalesLine(SalesHeader, SalesLine);
            OnPostSalesLineOnAfterTestSalesLine(SalesLine, SalesHeader, WhseShptHeader, WhseShip, PreviewMode);

MS will want the full signature of the event publisher, showing types of each argument and whether it must be var.

The code was refactored and this line was removed so no need for event to handle it


It's maths

Added calc as an alias but not maths smh
Please describe the changes this PR makes and why it should be merged:
Semantic versioning classification:

[ ] This PR changes the adds extra commands to the bot
[x] This PR improves existing commands
[ ] This PR only includes non-code changes, like changes to documentation, README, or images to memes / reactions

What's 1+1 if this is maths 😉

it's 4

whoops, added it~


Missing files

Hi,
I tried this on Umbraco 11.2 and Umbraco Forms 11.03.
Installed fine but when when tied to add the field to a form it gaves a 404 error missing file \App_Plugins\Our.Umbraco.Honeypot\FieldTypes\Honeypot.html
In Visual Studio I can see the file but it looks like a link to the file in the package.
I solved it by coping the file from the package.
Same for file \Views\Partials\Forms\Themes\default\FieldTypes\FieldType.Honeypot.cshtml
After that it seams to be working

Thanks!
Not sure how I have not notice this 😅

Fixed in: https://github.com/madsoulswe/Our.Umbraco.Honeypot/releases/tag/release%2F1.1.4

Can confirm that 1.1.4 fixed the issue


wrong IP set in SIP/SDP Header on opensuse Leap 15.1

Hi, first of all thanks for this awesome image!
We've been using it for quite some time now in different versions and scenarios. It's really great!

On a recent deployment of freepbx-14-latest however, I noticed something odd. Maybe it's OS related, but I'm putting this up here and try to investigate the issue and hopefully report back with more info so others can find it. I start by describing the problem followed by how I've set everything up.
Problem
When deployed to a fresh OpenSuse Leap 15.1 host with 1 NIC attached to the local network of <IP_ADDRESS>/24, outgoing SIP/SDP headers have the docker virtual network IP address set (look image down below) instead of the host IP which has SIP & RTP ports published to the network. This leads to no audio in both ways when calling one extension to another as no RTP packets can "reach" the PBX due to wrong headers being set in subsequential requests. So this is not really a NAT issue as both extensions are on the same subnet.
Setup
Network

Range:     <IP_ADDRESS>/24
Gateway IP: <IP_ADDRESS>
FreePBX Host IP: <IP_ADDRESS> / Published Ports 5060/udp, 18000-19000/udp
Extension 1 IP: <IP_ADDRESS>
Extension 2 IP: <IP_ADDRESS>

FreePBX / Asterisk Configuration
General SIP Settings
-->NAT Settings
External Address is set
Local Network = <IP_ADDRESS>/24
This config leads to the following packet flow:

Now, if I edit the asterisk config files and set
local_net=<IP_ADDRESS>/24
external_media_address=<IP_ADDRESS>
external_signal_address=<IP_ADDRESS>
SDP headers are set correctly. Allthough this doesn't help much as I have no place to put the "real" external IP for NAT'ng to the trunk left.
Different variant of
local_net=<IP_ADDRESS>/24
media_address=<IP_ADDRESS>
external_media_address=EXTERNALIP
external_signal_address=EXTERNALIP
doesn't do the trick ether. In this configuration the SIP/SDP address is overwritten and set to the external IP.
Theory
I do have the suspicion that this is OS related. I have the same setup up and running in another location allthough the FreePBX host OS is CentOS there. Maybe there is problem with the docker bridge or virtual network interface.
If anyone has an any idea on how this is possible or how to fix it, feel free to hit those keyboard buttons.

I had a similar issue, managed to get audio to work by removing my local network from NAT Settings, Local Network. It's just the docker network in there now and audio works (<IP_ADDRESS>/16).

I haven't been able to figure out a way to get the SDP address to be correct for internal calls.  It is always the docker address.
I tried to keep my scenario a bit pure by disabling direct-media.  Meaning that all RTP flows must go through the FreePBX Server.  With this configuration there seems no way to do any local NAT (container -> Network) manipulation of the SDP address.
@RowanTaubitz did you verify your SDP did not have the 172.18.0.x address?  When direct-media is enabled it will probably work, but for example if you want to do call recording you always have to shift the stream back to the FreePBX server.

Ok.  I found a way to do this, but I personally still have an issue with the contact header host part being the containers IP.
To solve the sdp issue though:
/etc/asterisk/pjsip.endpoint_custom_post.conf
[101](+)
media_address=<IP_ADDRESS>

You can add a media_address per extension.   In this case my extension is 101

It seems there is an identical issue with SIP traffic. I have seen my extension also try to connect to the docker IP with port 5060. But not in general.
At the moment incoming calls are working will with the provided workaround. But with outgoing calls is a hangup after 32 seconds.
16237[2022-10-29 22:22:36] VERBOSE[470388][C-00000017] bridge_channel.c: Channel PJSIP/36-00000029 left 'simple_bridge' basic-bridge <4a18f0df-3dd3-4354-b757-2fa6ed76aac4>
16238[2022-10-29 22:22:36] VERBOSE[470436][C-00000017] bridge_channel.c: Channel PJSIP/External-0000002a left 'simple_bridge' basic-bridge <4a18f0df-3dd3-4354-b757-2fa6ed76aac4>
16239[2022-10-29 22:22:36] VERBOSE[470388][C-00000017] app_macro.c: Spawn extension (macro-dialout-trunk, s, 27) exited non-zero on 'PJSIP/36-00000029' in macro 'dialout-trunk'
16240[2022-10-29 22:22:36] VERBOSE[470388][C-00000017] pbx.c: Spawn extension (from-internal, 01xxxxxxxx, 10) exited non-zero on 'PJSIP/36-00000029'
16241[2022-10-29 22:22:36] VERBOSE[470388][C-00000017] pbx.c: Executing [h@from-internal:1] Macro("PJSIP/36-00000029", "hangupcall") in new stack

This issue with NAT and docker can be solved using the network type macvlan instead of bridge and using an IP address without any NAT.
Create docker network
# docker network create -d macvlan -o parent=eth1 --subnet <IP_ADDRESS>/24 --gateway <IP_ADDRESS> --ip-range=<IP_ADDRESS>/26 VoIP
docker-compose.yaml
services:
  freepbx-app:
    .........
    networks:
      default:
        ipv4_address: <IP_ADDRESS>

networks:
  default:
    external: bridge
      name: VoIP

Make sure to keep the "internal" network (e.g., proxy-tier); remove "bridge" from external: bridge. This yaml-cutout works for me:
services:
  freepbx-app:
    [...]
    networks:
      VoIP:
        ipv4_address: XXX.XXX.XXX.XXX
      proxy-tier:

[...]

networks:
  proxy-tier:
    external:
      name: net-nginx-proxy
  VoIP:
    external:
      name: VoIP


Add override namespace to pyproject.toml/uv.toml

Summary
See #3834 .
This PR adds a new namespace, override-dependencies, to pyproject.toml/uv.toml.
This namespace assumes that the dependencies you want to override are written in the form of requirements.txt.
a example of pyproject.toml
[project]
name = "example"
version = "0.0.0"
dependencies = [
  "flask==3.0.0"
]

[tool.uv]
override-dependencies = [
  "werkzeug==2.3.0"
]

This will improve usability by allowing you to override dependencies without having to specify the --override option when running uv pip compile/install.
Test Plan
added test to crates/uv/tests/pip_compile.rs.

I skimmed through the diff and it looks good. To get the tests passing you need to run cargo dev generate-json-schema and commit the json change. Mark your PR as ready for review and/or comment when you want a proper review.

@konstin
Thanks for the advice!
I was able to update the uv.schema.json successfully!
Over the next few days I added a feature to the output of the uv pip compile to show that it was overridden from the workspace configuration.
Here is an excerpt of the output from uv pip compile.
``txt
werkzeug==2.3.0
# via.
# --override (from workspace)
# flask.

However, the implementation has become more complicated with the addition of this feature.
Please review when you have time.

I've removed the warnings changes in this PR to keep this to only adding overrides-dependencies, if you want you can make a separate PR for the warnings changes.

@konstin - How does this intersect with the existing overrides feature?

We chain them, so you can use both atm: https://github.com/astral-sh/uv/blob/5c776939d2e1bf388fb0beda1d1ec149ac4ae6e5/crates/uv/src/commands/pip/compile.rs#L406-L415


Update schemas

@marstamm @philippfromme could I get an approval here? Then I could make https://github.com/bpmn-io/bpmn-js-element-templates/pull/14 ready for review before my FTO 🙂

Should we add a test case/expand existing test cases for this feature? (e.g. make one of the options optional: https://github.com/bpmn-io/element-templates-validator/blob/main/test/fixtures/multiple-connectors.json#L39)

@marstamm I added tests for it


refactor: Create EditableTask class

Types of changes
Internal changes:

[x] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
[x] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)

Description

Convert type EditableTask to class EditableTask
Move related code from EditTask modal to Editable Task class

Motivation and Context

Remove logic from Edit Task modal
Encapsulate behaviour in Editable Task

How has this been tested?

Smoke test in demo vault

create task with just a description from an empty line, close modal, verify that the task has been written correctly
modify every field, close modal, verify that the task has been written correctly
remove all field data except description, close modal, verify that the task has been written correctly

Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[ ] My change has adequate Unit Test coverage.

hence the smoke test

Terms

[x] My contribution follows this project's contributing guide
[x] I agree to follow this project's Code of Conduct

@ilandikov If you use the 'Commit suggestion' feature, you might want edit the default commit message - I don't think I could control that in the review.

Encapsulation
Usability-wise, I feel like the the parameters passed in to .applyEdits() are a little bit of a smell, and a little bit of a risk...

Yup, I've already done this in my local branch =)

Tests and Behaviour
In order to understand how to use the class, I tried adding a couple of tests - see below.
In both cases, I'm curious about the time on the date. Likely the behaviour is unchanged, and so not an issue with this PR - but I wanted to share the findings.

This is exactly the bug I found here, thanks for making an expressive test, I haven't thought about that. I've added the test to this PR.
I think with that we are good to merge =)

Awesome - thanks very much indeed for doing this!


VR IPs are assigned to the VMs if I do not mark as used in DB.

ISSUE TYPE

Bug Report

COMPONENT NAME
VR

CLOUDSTACK VERSION
ACS 4.xx-4.15

CONFIGURATION
Basic zone with multiple subnets/CIDR

OS / ENVIRONMENT
CentOS7 - VMware 6.5

SUMMARY
This is a very old issue/bug (4.9). VR IPs are assigned to the VMs if I do not mark as used in DB.

STEPS TO REPRODUCE
1. Assign new IP CIRD
2. Deploy VMs
3. At any point I can get the used IPs by VR to be assigned on a new VM. if I try to change/assign the IP manually for a VM from cloudstack, I see the VR IP as free, if is not assigned to a VM. Because it is used by VR, it will not work on a VM ( IP conflict )

Any of these IPs: x.63, x.143, x.127, x.63, x.191 are available in cloudstack to be used by VMs in case i do not mark them as used in database.

root@r-1563-VM:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 1e:00:fb:00:00:2f brd ff:ff:ff:ff:ff:ff
    inet 149.XXX.XXX.53/28 brd 149.XXX.XXX.63 scope global eth0
       valid_lft forever preferred_lft forever
    inet 91.XXX.XXX.137/28 brd 91.XXX.XXX.143 scope global eth0
       valid_lft forever preferred_lft forever
    inet 51.XXX.XXX.66/26 brd 51.XXX.XXX.127 scope global eth0
       valid_lft forever preferred_lft forever
    inet 217.XXX.XXX.51/27 brd 217.XXX.XXX.63 scope global eth0
       valid_lft forever preferred_lft forever
    inet 217.XXX.XXX.182/27 brd 217.XXX.XXX.191 scope global eth0
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 02:00:4a:32:01:03 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth1
       valid_lft forever preferred_lft forever
root@r-1563-VM:~#

EXPECTED RESULTS

The IPs which are assigned to the VR should not be free, available for VMs.

ACTUAL RESULTS

VR IPs are still available for new provisioning

@ccycv can you suggest exact steps of reproduction, and on which ACS version did you reproduce them?

@ccycv Could you also share if this happens during the deployment of the first VM in the network i.e., the case when the VR is first deployed before the VM comes up?

@ccycv this does not look like reproducible on 4.15, can you try testing latest 4.15 or share steps to reproduce on 4.15?

I have tested in all the ACS versions, I thought this is going to be fixed, the reproduce steps are :

Assign new IP CIRD
Deploy VMs
At any point I can get the used IPs by VR to be assigned on a new VM. if I try to change/assign the IP manually for a VM from cloudstack, I see the VR IP as free, if is not assigned to a VM. Because it is used by VR, it will not work on a VM ( IP conflict ).


SUTD CyclingGeng

Name of Student Organisation*
SUTD CyclingGeng
Cluster
Sports
Classification
Interest Group
Description
SUTD CyclingGeng is home to some of the loosest, fastest, most fun-loving fellas around that just plain love cycling. From clocking 100K round-islands in crocs, blasting through janky mountain-biking trails, to chasing those Strava KOMs/PRs through TMCR, we may go flat out some days (because we have no pacing strategy... yet) but we sure have a good time all days. Grab your bike, grow with our family, ride your best life. Regardless if you are a dyed-in-the-wool aero machine, hyper-technical mountain biker, PCN warrior or somewhere in-between, as long as you love cycling, CyclingGeng may just be your ride.

Race calendar (road racing team): Mondays, Wednesdays and Fridays 6.30pm-8.30pm
Alt calendar: TBC
(Being a young IG a lot of these details are still work in progress, don't worry too much about it for now. What's crucial is your love of cycling! Bear with us as we work these details out along the way :) )
Student Organisation Introduction Video
NA
Name / Contact of President
Timothy Wee - President
<EMAIL_ADDRESS>@weeotim
Lim Fuo En - Treasurer/2IC
<EMAIL_ADDRESS>@FeMan1999
Other Relevant Links
Website: https://sutdcyclinggeng.carrd.co/

Hey @unclerogercolander thanks for submitting the student club details for cyclinggeng! Pretty cool.
This is good.

Hey @unclerogercolander thanks for submitting the student club details for cyclinggeng! Pretty cool.
This is good.

thanks for your work bro, appreciate it :)

Tim

@unclerogercolander approved! thank you and all the best for the event!


Update DG to differentiate between types of contacts (E.g. Volunteer) and groups

@seah-minlong to update glossary if necessary for both terms


I installed dotnet 6 sdk and runrime as well. But can't find in cmd.

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/install
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Did you open a new command prompt window? The installation process modifies the PATH environment variable and the change is visible only after opening a new command prompt.


Clean up universes

As a quick fix for lean, universes were declared equal, though this is unsound.
One should instead apply functions while running with lean allowing shifting of universes to match the domain and the type of the argument.

There is a case which shows the error in the tests, natnoct from lean (no confusion type for natural numbers).
In this case, a simplified induction is used, which is defined for type families P: Nat ->: Type but applied to a higher type family.
Most errors may be of this form.

Potential fix: for lambdas only have a modified check before application that allows resizing universes.
Implemented in 2d2a435e97ad67615e on the branch resized

Fails for bin_tree.no_confusion, because of bin_tree having modified type.
Should not modify types when replacing symbolic objects, at least when the types are universes

On removing the replacement of types, the simplest test failure was
Sigma-type

should be defined property *** FAILED ***

  ((a : A ) ~> ((ba : (B(_ : A)) (a) ) ~> (((D(_ : Σ(a : A, B(a)))) (a)) (ba)))) → ((((aa) , (bbaa)) : ∑((a :  A) ↦ ((B(_ : A)) (a))) ) ~> (((D(_ : Σ(a : A, B(a)))) (aa)) (bbaa)))
  did not equal
  ((a : A ) ~> ((ba : (B(_ : A)) (a) ) ~> (((D(_ : Σ(a : A, B(a)))) (a)) (ba)))) → (((((a, ba)_1) , ((a, ba)_2)) : ∑((a :  A) ↦ ((B(_ : A)) (a))) ) ~> (((D(_ : Σ(a : A, B(a)))) ((a, ba)_1)) ((a, ba)_2)))

(IntegrationSpec.scala:667)

Issue seems to be that if a special symbol such as a projection is wrapped in an inner symbol, then changing it has no effect on the full symbol, unless we go through types.

If we allow replacement with different types, we should have types replaced. The question is why this is needed.

A full stack trace, showing error during replace, perhaps an incorrect index.
provingground.HoTT$FuncLike.apply(HoTT.scala:1400),
  provingground.HoTT$FuncLike.apply$(HoTT.scala:1399),
  provingground.HoTT$SymbolicFunc.apply(HoTT.scala:1593),
  provingground.induction.TypFamilyPtn$FuncTypFamily.typ(TypFamily.scala:180),
  provingground.induction.TypFamilyPtn$FuncTypFamily.typ(TypFamily.scala:165),
  provingground.induction.TypFamilyPtn$DepFuncTypFamily.typ(TypFamily.scala:247),
  provingground.induction.TypFamilyPtn$DepFuncTypFamily.typ(TypFamily.scala:231),
  provingground.induction.IndexedInductiveDefinition$Funcs.<init>(InductiveCaseDefinition.scala:141),
  provingground.induction.IndexedInductiveDefinition$Funcs$.apply(InductiveCaseDefinition.scala:139),
  provingground.induction.IndexedInductiveDefinition$Funcs.subs(InductiveCaseDefinition.scala:175),
  provingground.induction.IndexedInductiveDefinition$Funcs.subs(InductiveCaseDefinition.scala:139),
  provingground.HoTT$Subs.replace(HoTT.scala:183),
  provingground.HoTT$Subs.replace$(HoTT.scala:154),
  provingground.induction.IndexedInductiveDefinition$Funcs.replace(InductiveCaseDefinition.scala:139),
  provingground.HoTT$LambdaLike.subs(HoTT.scala:1752),
  provingground.HoTT$LambdaLike.subs$(HoTT.scala:1745),
  provingground.HoTT$LambdaTerm.subs(HoTT.scala:1771),
  provingground.HoTT$LambdaTerm.subs(HoTT.scala:1771),
  provingground.HoTT$Subs.replace(HoTT.scala:183),
  provingground.HoTT$Subs.replace$(HoTT.scala:154),
  provingground.HoTT$LambdaTerm.replace(HoTT.scala:1771),
  provingground.HoTT$.lambda(HoTT.scala:2011),
  provingground.HoTT$RichTerm.$colon$tilde$greater(HoTT.scala:2731),
  provingground.induction.TypFamilyMap$DepFuncTypFamilyMap.iterDepFunc(TypFamily.scala:583),
  provingground.induction.TypFamilyMap$DepFuncTypFamilyMap.iterDepFunc(TypFamily.scala:534),
  provingground.induction.IndexedInductiveDefinition.iterDepFunc$lzycompute(InductiveCaseDefinition.scala:178),
  provingground.induction.IndexedInductiveDefinition.iterDepFunc(InductiveCaseDefinition.scala:178),
  provingground.induction.IndexedConstructorSeqMap.induc(IndexedConstructorSequence.scala:90),
  provingground.induction.IndexedConstructorSeqDom.induc(IndexedConstructorSequence.scala:546),

Confirmed that this is an index related issue
provingground.induction.IndexedInductiveDefinition#Funcs#dom:142 ind: SymbTyp(Name("$argjxz"), 0) :: SymbolicFunc(Name("$argjyc"), SymbTyp(Name("$argjxz"), 0), Universe(0)) :: HNil
provingground.induction.IndexedInductiveDefinition#Funcs#dom:142 ind: SymbTyp(Name("$argjxz"), 0) :: SymbolicFunc($argjyc, SymbTyp(Name("$argjxz"), 0), Universe(0)) :: HNil
provingground.induction.IndexedInductiveDefinition#Funcs#dom:142 ind: SymbTyp(Name("$argjxz"), 0) :: SymbolicFunc($argjyc, SymbTyp($argjxz, 0), Universe(0)) :: HNil
- should be defined properly *** FAILED ***
  provingground.HoTT$ApplnFailException: function (Σ) ($argjxz) with domain(optional) Some(($argjxz) → (𝒰 _0)) cannot act on given term $argjyc with type ($argjxz) → (𝒰 _0)
  at provingground.HoTT$FuncLike.apply(HoTT.scala:1400)
  at provingground.HoTT$FuncLike.apply$(HoTT.scala:1399)
  at provingground.HoTT$SymbolicFunc.apply(HoTT.scala:1593)
  at provingground.induction.TypFamilyPtn$FuncTypFamily.typ(TypFamily.scala:180)
  at provingground.induction.TypFamilyPtn$FuncTypFamily.typ(TypFamily.scala:165)
  at provingground.induction.TypFamilyPtn$DepFuncTypFamily.typ(TypFamily.scala:247)
  at provingground.induction.TypFamilyPtn$DepFuncTypFamily.typ(TypFamily.scala:231)
  at provingground.induction.IndexedInductiveDefinition$Funcs.<init>(InductiveCaseDefinition.scala:143)
  at provingground.induction.IndexedInductiveDefinition$Funcs$.apply(InductiveCaseDefinition.scala:139)
  at provingground.induction.IndexedInductiveDefinition$Funcs.subs(InductiveCaseDefinition.scala:178)
  ...

and we see a similar error in the other case that does not involve special types.

It is correct semantics to have type replacement, the above are not bugs.
should have a workaround for universe parameters, for example more permissive formal application.

bin_tree.no_confusion has been corrected in ad2d9a02102
A more complicated error is seen in decidable.rec_on_true, perhaps because of non simplification if universes do not match.

Some of the output
@ apf.domOpt.get
res20: Typ[Term] = ∏(_ : 'u){ induc_{ decidable('u) ; (_ : decidable('u)) ↦ 𝒰  }('x)('w)(_) }

@ apf.argType
res21: Typ[Term] = ('u → 'w(_))

@ val dt = p.defnMap(trepplein.Name("decidable", "is_true"))
dt: Term = decidable.is_true

@ dt.typ
res25: Typ[U] = ∏('c : Prop){ ('c → decidable('c)) }

@ val df = p.defnMap(trepplein.Name("decidable", "is_false"))
df: Term = decidable.is_false

@ df.typ
res27: Typ[U] = ∏('d : Prop){ (('d → false) → decidable('d)) }

@ apf.domOpt.get
res28: Typ[Term] = ∏(_ : 'u){ induc_{ decidable('u) ; (_ : decidable('u)) ↦ 𝒰  }('x)('w)(_) }

@ val d = p.defnMap(trepplein.Name("decidable"))
d: Term = decidable

@ d.typ
res30: Typ[U] = (Prop → 𝒰 )

This is a separate issue, regarding formal application with propositions.


AutoSizer always returns 0, 0 in a simple sized div

Hi !
In its simplest form, AutoSizer always returns 0, 0. The surrounding node is a div with dimensions. Nothing fancy here, just reproduced the most basic example.
Here is a test case :
https://plnkr.co/edit/rMCYuKhdRLVVKTUJzbQF?p=preview

Hmmm, okay it seems to return 0, 0 first and then the correct dimensions, although in the DOM the div has its width and height set as 0.
I guess this is the expected behavior ? (If so, would be great to see that mentioned in docs !).

Hi @jide,
Have you seen this docs page: https://github.com/bvaughn/react-virtualized/blob/master/docs/usingAutoSizer.md#why-is-my-autosizer-setting-a-height-of-0
If you have ideas on how to improve the docs, please submit a PR 😄

I had the same problem using AutoSizer within the flex container.  This solution almost helped, I had to add height: 100vh for it to work.

    <AutoSizer>
     ....
    </AutoSizer>

Thanks for sharing your solution @sajinshrestha
I suspect in your case that you may have a parent of the flexbox div that doesn't have a height set. Which in this case will cause the descendants to remain collapsed. Easy way to debug this is to walk up the DOM tree and set an obvious style like background color. If you don't see anything change when you set your style, you know the element is collapsed. 😄

@bvaughn Thank you for expanding on this.

I suspect in your case that you may have a parent of the flexbox div that doesn't have a height set.

Correct, so I was trying to set the height by using height: 100% but that didn't work.
height: '100vh' did the trick. Thanks.

@bvaughn - This issue has returned with the latest deployment - we have pinned our package to 9.21.0 in order to make it work

@bvaughn Not only is this issue back, the error messages are not helpful.
We are getting 0 width and 0 height passed into out function, and it's exploding things.
Please open this ticket.

I was struggling with the same thing a lot, so created new library that is much more easier and has different approach for virtual lists. react-virtual-overflow
It automatically calculates visible rect of container, so you also dont need to track overflows on page. It also doesn't add any magic divs.


Use something like zxcvbn to indicate password strength

Currently, when a user sets or resets their password, we do not restrict their password in any way. We also do not indicate the strength of their password.
At the least, we wish to indicate to the user the strength of their password. We're thinking we could use zxcvbn or a library like it to do so.
We may also wish to add password restrictions rather than just warnings, such that the user cannot choose a password that fails to satisfy certain restrictions. I think we would consider at least a restriction on password length ("the password must be at least X characters"). If we add such a restriction, we may need to update Backend as well.

In addition to the user's password, we now also use passphrases in two places:

Configuring backups
Enabling encryption

For these, I think we should similarly consider indicating passphrase strength or possibly adding passphrase restrictions.


Implement new operations for an entity

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Expected/desired behavior
Hi ! I'm currently trying ngrx-data but I'm stuck for a few hours trying understand how to implement customs loadNewerSince and loadOlderFrom operations for my entity.
Where to create the new actions, configure the query parameters of HTTP requests created, ... ?
The current docs don't explain explicity how to achieve my goal.
I think this issue https://github.com/johnpapa/angular-ngrx-data/issues/22 may be related to my questions but unfortunately there is no update since december.
Any advices would be welcome :)
Thanks for your library @johnpapa @wardbell !
OS and Version?

Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)

Versions

Mention any other details that might be useful

Thanks! We'll be in touch soon.

I close this issue because I now have a better understanding of how ngrx-data services work together.
For those who are interested, here is what my service looks like:
import { Injectable } from '@angular/core';
import { map, mergeMap, first } from 'rxjs/operators';
import { Observable } from 'rxjs';
import {
    EntityCollectionServiceBase,
    EntityCollectionServiceElementsFactory,
    QueryParams,
} from 'ngrx-data';

import { Message } from '../models/message.model';

@Injectable({ providedIn: 'root' })
export class MessagesService extends EntityCollectionServiceBase<
    Message
> {
    constructor(
        serviceElementsFactory: EntityCollectionServiceElementsFactory
    ) {
        super('Message', serviceElementsFactory);
    }

    getLatest(count = 15): Observable<Message[]> {
        return this.entities$.pipe(
            first(),
            // Get the newest message id in collection
            map(messages => messages.shift().id),
            // Create the query params
            map(
                (currentNewestId): QueryParams => ({
                    count: count.toString(),
                    since: currentNewestId,
                })
            ),
            // Fetch newest messages
            mergeMap(queryParams => super.getWithQuery(queryParams))
        );
    }

    getOlder(count = 15): Observable<Message[]> {
        return this.entities$.pipe(
            first(),
            // Get the oldest message id in collection
            map(messages => messages.pop().id),
            // Create the query params
            map(
                (currentNewestId): QueryParams => ({
                    count: count.toString(),
                    from: currentNewestId,
                })
            ),
            // Fetch older messages
            mergeMap(queryParams => super.getWithQuery(queryParams))
        );
    }
}

So this issue becomes a duplicate of #22


chore: upgrade lodash when available

there is a medium security vulnerability in a lodash function
Prototype Pollution
Vulnerable module: lodash
Introduced through<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Detailed paths
Introduced through: @mindconnect/mindconnect-nodejs@mindsphere/mindconnect-nodejs#c6084de5bad0303d94b9d2104ecc6e29d53e5798 ›<EMAIL_ADDRESS>Remediation: Open PR to patch<EMAIL_ADDRESS>Introduced through: @mindconnect/mindconnect-nodejs@mindsphere/mindconnect-nodejs#c6084de5bad0303d94b9d2104ecc6e29d53e5798 ›<EMAIL_ADDRESS>›<EMAIL_ADDRESS>Remediation: Open PR to patch<EMAIL_ADDRESS>Overview
lodash is a modern JavaScript utility library delivering modularity, performance, & extras.

Affected versions of this package are vulnerable to Prototype Pollution. The function zipObjectDeep can be tricked into adding or modifying properties of the Object prototype. These properties will be present on all objects.

This function is not used by the library. We ill upgrade lodash once the new lodash version is released.
https://github.com/lodash/lodash/pull/4759

https://snyk.io/test/github/mindsphere/mindconnect-nodejs?targetFile=package.json


admin group assignment on /private

i'm probably missing something here, but i'm getting incorrect group ownership on /private/var/db for an example here. the pkg builds and installs fine, but the os is picky about ownership here. i don't see any lines in luggage.make that set ownership to root:admin for this path, yet they are at build time. example:
this makefile drops admin account and group plists under dslocal: https://gist.github.com/1676696
ownership looks fine to me in the makefile. it matches what's on disk.
building results in this:
Warning: Group ID 80 does not match 0 of root volume for "/private". Make sure to have disk permissions repaired with Disk Utility.
Warning: Group ID 80 does not match 0 of root volume for "/private/var". Make sure to have disk permissions repaired with Disk Utility.
Warning: Group ID 80 does not match 0 of root volume for "/private/var/db". Make sure to have disk permissions repaired with Disk Utility.
ownership under pkgroot confirms this. i don't see where this ownership gets set. i'm using the latest luggage pulled straight from the repo.
any ideas?
it's an issue because it causes stalls or just plain failure to boot without fixing the ownership on a newly imaged box.

it seems like the way to resolve this is to redefine l_root as:
l_root: package_root
@sudo mkdir -p ${WORK_D}
@sudo chmod 755 ${WORK_D}
@sudo chown root:wheel ${WORK_D}
that builds without errors. i don't know if it would be worth merging in that change.

Changed to root:wheel in 8ab05689c787bd92187e345dd1f1b029354830b9


ItemRepeater Random Heights issue when use Scrollviewer

CommitID: 8d1f7a71e0dfecada479eb42372966395b02db6b

Unfortunately this is a problem with the upstream ItemsRepeater. I reported it in Jan but there's been no movement on it since then https://github.com/microsoft/microsoft-ui-xaml/issues/1829
I diagnosed the problem as you can see in that thread, but I'm unsure of what the correct fix should be.

I just replied again in the microsoft ui thread. Its open for over 12 month now there 😒
I have really complicated lists in the application I am planning to develop and hardly need a working ItemsRepeater for performance reasons.


Respawning always in one world

Hi,
I have 2 worlds each with own nether and end. My creative world is called "world" and my survival world is called "survival". I want the users to respawn in their beds in the world they die or at the worldspawn of the world they died if they didn't use a bed. But everytime someone dies they are respawned at the world spawn point of world "world" even if they die in world "survival" and used a bed.

Anyone knows what I'm doing wrong? I've read something online about respawn priorities with multiverse and worldguard/essentialsx?
Edit:
Looks like EssentialsXSpawn is overwriting the spawn setting of Multiverse. Removed it and spawning in beds now works.

I had this same issue; how did you fix it?

pues ami si mueren se quedan bugeados, no pueden reaparecer. ose muerte dentro de muerte. no hacen Respawn en ningun sitio.

This is a common issue. It can be resolved by setting respawn-listener-priority in EssentialsX's config.yml to either lowest or none (none is what works for me). I'll add this info to our wiki.


local variable 'twname' referenced before assignment

I'm getting an error while running script
Traceback (most recent call last):
  File "scylla.py", line 1181, in <module>
    main()
  File "scylla.py", line 1097, in main
    cprint(Twitter(args.twitter).RetrieveAccountInformation(), 'green', attrs=['bold'])
  File "scylla.py", line 867, in RetrieveAccountInformation
    '''.format(str(twname), str(data['Bio: ']),
UnboundLocalError: local variable 'twname' referenced before assignment

What could be the issue?

Line 807 fails: twname = soup.title.text.split("|")[0].   soup.title is None, therefore the variable is not defined.  At line 867 ('''.format(str(twname), str(data['Bio: ']),), an attempt is made to use it, but there is no such variable.


Move Verifying Installation section to Installation doc

Is this a bug report?
No
Have you read the Contributing Guidelines?
Yes
Environment
N/A
Steps to Reproduce
N/A
Expected Behavior
The section should be in https://docusaurus.io/docs/en/installation.html
The first paragraph in will need to be updated too.
Actual Behavior
It is in https://docusaurus.io/docs/en/site-preparation.html#verifying-installation
Reproducible Demo

Go to https://docusaurus.io/docs/en/site-preparation.html#verifying-installation
Read that section
If agreed that it should be part of the Installation doc instead, move it there.

Hello @JoelMarcey i just make a pr about this but i seem a bit lost on what needs to be updated in the first paragraph.

Hi @gedeagas
The first paragraph in https://docusaurus.io/docs/en/site-preparation.html says:

After installing Docusaurus, you now have a skeleton to work from for your specific website. With a few changes, you can verify that Docusaurus was installed correctly by running the site locally.

The second sentence there would be out of place, I think, if you are moving the verification of the install to the installation page. So maybe that just should be removed?
Actually you can take this paragraph from down below on that page:

The website/blog-examples-from-docusaurus and docs-examples-from-docusaurus folders contain example blog and document markdown files. As shown below when you verify that the example site runs correctly, if you wish to run Docusaurus with these files, you need to rename the folders to website/blog and docs, respectively.

and move it to the top of  https://docusaurus.io/docs/en/site-preparation.html and have the first paragraph be something like:

After installing Docusaurus, you now have a skeleton to work from for your specific website. You may have already renamed the example blog (website/blog-examples-from-docusaurus and document (docs-examples-from-docusaurus) directories when you [verified the installation](LINK TO THE NEW LOCATION). The following discusses the rest of the Docusaurus structure in order for you to prepare your site.

Ah, I got it now 😃
Thank you for your insight @JoelMarcey.

Fixed by https://github.com/facebook/Docusaurus/commit/c8781bedced205cd2a5c876af62623795d7aaf81 and https://github.com/facebook/Docusaurus/commit/9931ed86d28a3ea64c9878536a4d2f91765f1d26


Failed to publish feature layer to a 10.3.1 portal for ArcGIS

The GRG widget is not able to publish to a 10.3.1 portal for ArcGIS.
Error that is received by the user when attempting to publish the GRG feature layer:
"ERROR: Error in opening workspace from sde connection string" error
The feature layer is created in portal, but the layer is empty. The error mentioned above happens on the client side

@elinz fixed this issue by validating the license for ArcGIS Data Store, I was able to verify. I can now publish feature layers and view them in the test portal.


⚠ Secret Website 4 has degraded performance

In 069eebc, Secret Website 4 ($SECRET_WEBSITE_4) experienced degraded performance:

HTTP code: 200
Response time: 12469 ms

Resolved: Secret Website 4 performance has improved in 6a2cac6.


Respond to https://hypothes.is/a/Opl-doD3Eeq8qjescxuUZA

Respond to hypothes.is annotation Opl-doD3Eeq8qjescxuUZA on https://jrnold.github.io/r4ds-exercise-solutions/exploratory-data-analysis.html (user<EMAIL_ADDRESS>created: 2020-04-17T22:03:11.610263+00:00, updated: 2020-04-17T22:06:54.090188+00:00)

Thanks a bunch for posting this. I was banging my head on the wall.
Any idea how to clean up the x-axis? mine is displaying each .1 carat
Any idea why the first one doesnt work?

Link: https://hyp.is/xw9aam_lEeqi0LsuAfUCfQ/jrnold.github.io/r4ds-exercise-solutions/exploratory-data-analysis.html

Posted comments:

https://hyp.is/xw9aam_lEeqi0LsuAfUCfQ/jrnold.github.io/r4ds-exercise-solutions/exploratory-data-analysis.html
https://hyp.is/xw9aam_lEeqi0LsuAfUCfQ/jrnold.github.io/r4ds-exercise-solutions/exploratory-data-analysis.html


USB: Mass Storage fixes

Codecov Report

Merging #6425 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6425      +/-   ##
==========================================
+ Coverage   53.06%   53.06%   +<.01%
==========================================
  Files         430      430
  Lines       41060    41060
  Branches     7911     7911
==========================================
+ Hits        21787    21788       +1
+ Misses      16049    16048       -1
  Partials     3224     3224

Impacted Files
Coverage Δ

samples/philosophers/src/main.c
98.43% <0%> (+1.56%)
:arrow_up:

Continue to review full report at Codecov.

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


[Bug] [BanyanDB] Metrics breaks periodically

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache SkyWalking Component
BanyanDB (apache/skywalking-banyandb)
What happened
Since we switched demo database to BanyanDB, most things work well, but I noticed this kind of metric breaking.

Meanwhile, this only happens on minute level,

All services/pods of demo env seem normal

But we noticed this error happens periodically too in the OAP pod logs.

I also checked the BanyanDB client codes, although we don't expose the configuration to BanyanDB provider(@lujiajing1126 we should expose), but the default value is 50m.
But this error log says, ~5m. So, @hanahmily @lujiajing1126 @ButterBright Is the server missing the configurations? And could you check whether there is other reason to make metrics breaking.
What you expected to happen
Make metrics continuously flush into the storage.
How to reproduce
I didn't reproduce this, but observe this on demo env.
Anything else
No response
Are you willing to submit a pull request to fix on your own?

[ ] Yes I am willing to submit a pull request on my own!

Code of Conduct

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

Seems like a client side problem, the 50MB didn't take effect.

I didn't check that deeply. But it seems existing in the default constructor. Doesn't it?

I checked the client, and it seems that the error cannot be from the BanyanDB client.

The error is related to the 'getCompressedBody' function, but the client should always use the 'getUncompressedBody' instead. BTW, maxInboundMessageSize is 50MB even though the client doesn't use it here.

@wankai123 Let us bump up otel collectoe first. This seems irrelevant with DB.


Sema: Report public conformances to non-publicly imported protocols

Exportability checking for non-public imports relies on classic access-level checks for some of the work. However while conforming to a local internal protocol from a public type is allow we should disallow it for imported types, even when imported as internal.
Track exportability issues on conformances to protocols separately from the general category. Use that information to improve the diagnostics and report these issues for access-level on imports.
rdar://128420980

@swift-ci Please smoke test

Thank you!

@swift-ci Please smoke test

@swift-ci Please smoke test

Rebased following the revert from #74302. I left behind some of the expected errors for once the revert is reverted in a separate commit.
@swift-ci Please smoke test

@swift-ci Please smoke test


Start On Boot

Hi, can you add a feature to start tether when device starts

With the recent changes to services that start on boot in Android 15, this is unlikely to be supported :(
Sorry about that.


cert-manager "successfully" create certificate but no secret is actually created

Bugs should be filed for issues encountered whilst operating cert-manager.
You should first attempt to resolve your issues through the community support
channels, e.g. Slack, in order to rule out individual configuration errors.
Please provide as much detail as possible.

Describe the bug:
I have setup my ingress following http://docs.cert-manager.io/en/latest/reference/ingress-shim.html with a ClusterIssues (letsencrypt staging).
cert-manager emits the following event:
Normal  CreateCertificate  4m13s                cert-manager              Successfully created Certificate "tls-cert-staging.xxxx.com"

But no secret is created and thus nginx-ingress can't find it.
Expected behaviour:
A secret must either be created or an error printed somewhere in the logs instead of a message of successful creation.
Steps to reproduce the bug:
Here is my ingress resource (as given to k8s):
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: blue-green-staging
  labels:
    app.kubernetes.io/name: blue-green
    app.kubernetes.io/instance: bg
    helm.sh/chart: blue-green-1.0.0
    app.kubernetes.io/managed-by: Tiller
  annotations:
    certmanager.k8s.io/cluster-issuer: "letsencrypt-staging"
    kubernetes.io/ingress.class: nginx
spec:
  rules:
    - host: "staging.xxxx.com"
      http:
        paths:
          - path: /
            backend:
              serviceName: blue-green-staging
              servicePort: http
  tls:
    - secretName: "tls-cert-staging.xxxx.com"
      hosts:
        - "staging.xxxx.com"

Describe on this resource gives me:
Name:             blue-green-staging
Namespace:        default
Address:          a.b.c.d
Default backend:  default-http-backend:80 (<none>)
TLS:
  tls-cert-staging.xxxx.com terminates staging.xxxx.com
Rules:
  Host                                            Path  Backends
  ----                                            ----  --------
  staging.xxxx.com
                                                  /   blue-green-staging:http (<none>)
Annotations:
  certmanager.k8s.io/cluster-issuer:  letsencrypt-staging
  kubernetes.io/ingress.class:        nginx
  kubernetes.io/tls-acme:             true
Events:
  Type    Reason             Age                  From                      Message
  ----    ------             ----                 ----                      -------
  Normal  CREATE             4m13s                nginx-ingress-controller  Ingress default/blue-green-staging
  Normal  CreateCertificate  4m13s                cert-manager              Successfully created Certificate "tls-cert-staging.xxxx.com"
  Normal  UPDATE             40s (x2 over 3m49s)  nginx-ingress-controller  Ingress default/blue-green-staging

And the logs of cert-manager are showing every two seconds:
I1023 14:32:52.348545       1 controller.go:171] certificates controller: syncing item 'default/tls-cert-staging.xxxx.com'
I1023 14:32:52.349163       1 helpers.go:194] Setting lastTransitionTime for Certificate "tls-cert-staging.xxxx.com" condition "Ready" to 2018-10-23 14:32:52.348976907 +0000 UTC m=+17582.640458718
I1023 14:32:52.354108       1 controller.go:168] ingress-shim controller: syncing item 'default/blue-green-staging'
I1023 14:32:52.354400       1 sync.go:140] Certificate "tls-cert-staging.xxxx.com" for ingress "blue-green-staging" already exists
I1023 14:32:52.354745       1 sync.go:143] Certificate "tls-cert-staging.xxxx.com" for ingress "blue-green-staging" is up to date
I1023 14:32:52.354960       1 controller.go:182] ingress-shim controller: Finished processing work item "default/blue-green-staging"
I1023 14:32:52.355444       1 controller.go:185] certificates controller: Finished processing work item "default/tls-cert-staging.xxxx.com"

Anything else we need to know?:
Environment details::

Kubernetes version (e.g. v1.10.2): v1.10.7-gke.6
Cloud-provider/provisioner (e.g. GKE, kops AWS, etc): GKE
cert-manager version (e.g. v0.4.0): 0.5.0
Install method (e.g. helm or static manifests): helm

/kind bug

I tried changing the name of the secret to "tls-secret-1" and the first time the word appears in the log, it says:
I1024 07:31:11.426673       1 sync.go:140] Certificate "tls-secret-1" for ingress "blue-green-staging" already exists
I1024 07:31:11.426806       1 sync.go:143] Certificate "tls-secret-1" for ingress "blue-green-staging" is up to date

This is really strange, no?

After a bit more research, I found the following, calling kubectl describe certificates.certmanager.k8s.io tls-cert-staging.xxx.com:
Name:         tls-cert-staging.xxx.com
Namespace:    default
Labels:       <none>
Annotations:  <none>
API Version:  certmanager.k8s.io/v1alpha1
Kind:         Certificate
Metadata:
  Cluster Name:
  Creation Timestamp:  2018-10-24T07:55:06Z
  Generation:          1
  Owner References:
    API Version:           extensions/v1beta1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Ingress
    Name:                  blue-green-staging
    UID:                   1f13c82f-d762-11e8-99af-42010a84017e
  Resource Version:        261228
  Self Link:               /apis/certmanager.k8s.io/v1alpha1/namespaces/default/certificates/tls-cert-staging.xxx.com
  UID:                     1f16d922-d762-11e8-99af-42010a84017e
Spec:
  Dns Names:
    staging.xxx.com
  Issuer Ref:
    Kind:       ClusterIssuer
    Name:       letsencrypt-staging
  Secret Name:  tls-cert-staging.xxx.com
Status:
  Conditions:
    Last Transition Time:  2018-10-24T07:56:30Z
    Message:               Resource validation failed: spec: Invalid value: "no issuer specified for Issuer '/letsencrypt-staging'": no issuer specified for Issuer '/letsencrypt-staging'
    Reason:                ConfigError
    Status:                False
    Type:                  Ready
Events:                    <none>

I suppose this is the error I was looking for, but it's not clear what is the problem.
The issuer, in the kube-system namespace (where cert-manager and nginx-ingress are installed), is defined as:
apiVersion: certmanager.k8s.io/v1alpha1
kind: ClusterIssuer
metadata:
  name: letsencrypt-staging
spec:
  # The ACME server URL
  server: https://acme-staging-v02.api.letsencrypt.org/directory
  # Email address used for ACME registration
  email<EMAIL_ADDRESS>  # Name of a secret used to store the ACME account private key
  privateKeySecretRef:
    name: letsencrypt-staging
  # Enable the HTTP-01 challenge provider
  http01: {}

Ah, it looks like your ClusterIssuer resource is invalid.
Notably, it should look more like:
.
apiVersion: certmanager.k8s.io/v1alpha1kind: ClusterIssuermetadata:
name: letsencrypt-stagingspec:
acme:
# The ACME server URL
server: https://acme-staging-v02.api.letsencrypt.org/directory
...
Your example is missing the 'acme' key, hence the error 😬
On Wed, 24 Oct 2018 at 08:58, Victor Noël<EMAIL_ADDRESS>wrote:

After a bit more research, I found the following, calling kubectl
describe certificates.certmanager.k8s.io tls-cert-staging.xxx.com:
Name:         tls-cert-staging.xxx.com
Namespace:    default
Labels:
Annotations:
API Version:  certmanager.k8s.io/v1alpha1
Kind:         Certificate
Metadata:
Cluster Name:
Creation Timestamp:  2018-10-24T07:55:06Z
Generation:          1
Owner References:
API Version:           extensions/v1beta1
Block Owner Deletion:  true
Controller:            true
Kind:                  Ingress
Name:                  blue-green-staging
UID:                   1f13c82f-d762-11e8-99af-42010a84017e
Resource Version:        261228
Self Link:               /apis/certmanager.k8s.io/v1alpha1/namespaces/default/certificates/tls-cert-staging.xxx.com
UID:                     1f16d922-d762-11e8-99af-42010a84017e
Spec:
Dns Names:
staging.xxx.com
Issuer Ref:
Kind:       ClusterIssuer
Name:       letsencrypt-staging
Secret Name:  tls-cert-staging.xxx.com
Status:
Conditions:
Last Transition Time:  2018-10-24T07:56:30Z
Message:               Resource validation failed: spec: Invalid value: "no issuer specified for Issuer '/letsencrypt-staging'": no issuer specified for Issuer '/letsencrypt-staging'
Reason:                ConfigError
Status:                False
Type:                  Ready
Events:
I suppose this is the error I was looking for, but it's not clear what is
the problem.
The issuer, in the kube-system namespace (where cert-manager and
nginx-ingress are installed), is defined as:
apiVersion: certmanager.k8s.io/v1alpha1kind: ClusterIssuermetadata:
name: letsencrypt-stagingspec:
The ACME server URL
server: https://acme-staging-v02.api.letsencrypt.org/directory
Email address used for ACME registration
email<EMAIL_ADDRESS>Name of a secret used to store the ACME account private key
privateKeySecretRef:
name: letsencrypt-staging
Enable the HTTP-01 challenge provider
http01: {}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jetstack/cert-manager/issues/992#issuecomment-432552811,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMbP7zZeXslCDbQDGfl2hD674Zg-qaSks5uoB22gaJpZM4X1u-q
.

@munnerz arg, I'm ashamed :)
Thanks!

@victornoel  im more assamed you are asshamed cas im the same typo as you :)

@victornoel  im more assamed you are asshamed cas im the same typo as you :)


 OrderedMap constructor changed in LibGDX 1.9.4 (I think). If you're using LibGDX 1.9.3 (or older), use gdx-kiwi <IP_ADDRESS>.3. If you're using the latest LibGDX, switch to beta release - gdx-kiwi <IP_ADDRESS>.3-b1.

It does compile with kiwi 1.8
my bad, i should have looked for beta releases first.
i suppose you can close the issue.
thank you =)

@czyzby I did get another error with autumn on android packaging tho
http://pastebin.com/3jHE3chg

seems to be resolved when adding
packagingOptions {
exclude 'META-INF/robovm/ios/robovm.xml'
}
to android/build.gradle

Yes, this is a common issue. Android does not handle duplicate files very well, but in order to enable RoboVM reflection of some classes, robovm.xml is required in pretty much every library. That's why our gdx-setup includes this conguration in the Android Gradle file.


2D pure localization slow on same map.

As reported by @gladxu in https://github.com/googlecartographer/cartographer_ros/issues/557, 2D pure localization fails on exactly the same map.
roslaunch cartographer_ros offline_backpack_2d.launch bag_filenames:=${HOME}/Downloads/cartographer_paper_deutsches_museum.bag

roslaunch cartographer_ros demo_backpack_2d_localization.launch bag_filename:=${HOME}/Downloads/cartographer_paper_deutsches_museum.bag map_filename:=${HOME}/Downloads/cartographer_paper_deutsches_museum.bag.pbstream

In rviz, one can see that good constraints are found, but they are long delayed, the work queue is too long. Therefore, the currently reported localization is way off due to the drift in between.

In this case, the constraint builder spends more time on scan matching, so work queues up.
Localization on exactly the same map is a special case with a large number of matches.
One way to tune this would be sample fewer potential constraints in general for localization.
I will do more evaluation, but localization has more work with MaybeAddGlobalConstraint than usual SLAM so maybe the default value could be lower
SPARSE_POSE_GRAPH.global_sampling_ratio =
    0.2 * SPARSE_POSE_GRAPH.global_sampling_ratio

This scenario can be solved with tuning as follows,
SPARSE_POSE_GRAPH.global_sampling_ratio = 0.001
SPARSE_POSE_GRAPH.constraint_builder.sampling_ratio = 0.1

so closing the issue.

Might be useful to add this to the tuning guide.

@cshuet ping :-)

@cshuet ping :-) do you agree?

Agreed. @gaschler will update the guide.


Cannot display value. No PropertyDrawer for {V}

I enjoyed being able to edit the values for SO in the editor. Now I can't. What is a property drawer, how do I use them, and why?

If the type you're trying to inspect is one you've made yourself, you have to create a Property Drawer for it, since I can't just ask Unity to draw the one it uses in the inspector. Here's a guide on what Property Drawers are: https://docs.unity3d.com/2018.3/Documentation/ScriptReference/PropertyDrawer.html
I did recently change how SO-A detects Property Drawers, so it could be that you've stumbled onto a recently introduced bug. Did you install using the package manager? If so, that might be the most likely cause.

Probably a regression. Happens to me on a freshly cloned repo even with FloatVariables.

Ahhh I think I know what's wrong, the new system is much better at detecting user-made property drawers, but I probably forgot to include Unity's. Should be an easy fix :)

Fixed, thanks for the report :)


Feature/profile page

Description

Create a basic profile page
Move to ProfileActivity by clicking the profile button (Navigation drawer)

Issue Resolved

Fix issue #23

Screenshots

Checklist
Please make sure to review the following before submitting your PR:

[x] I have read the contribution guidelines.
[x] I have read the code of conduct.
[x] I have reviewed my submission in detail.

done

Lgtm, great work 🎉


Use knative-eventing

Signed-off-by: Matthias Wessendorf<EMAIL_ADDRESS>

@matzew  Looks good, but, there's some stuff that we do for cleaning up resources not in CR namespace.

Can't verify anytrhing right now. Image registry is down

/lgtm
/approve

Doing the follow up in a separate PR now


Remove SQL->DS replay from all tests

This change is

Looking at the test results, this doesn't seem to have helped with the transaction invalidation problem.

Succeeded, going to try removing the (hopefully unnecessary) DualDatabaseTest annotations

if this passes this time (and again, i'll retrigger it) we maybe could be good to go

kokoro run 1 succeeded, restarting

See #1384


add CORS "Access-Control-Expose-Headers" support

The "Access-Control-Expose-Headers" header lets a server whitelist headers that browsers are allowed to access.

FYI, the CORS feature will be deprecated in the future in favor of the excellent Flask-CORS library, see #367, #229 and #184.


Add state and user_scope variables to Slack auth URI

The state variable was missing in Slack URI.
Added the user_scope variable as well.

📦 Published PR as canary version: Canary Versions

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

:rocket: PR was released in<EMAIL_ADDRESS>:rocket:


remove prefix from services

test  #557
should be merged if  #269 got addressed

https://ci.woodpecker-ci.org/repos/3780/pipeline/6440/25 - looks still broken :D

it does not crash anymore but we still will likely need  #1959

Codecov Report
Patch and project coverage have no change.

Comparison is base (b3f65d9) 39.28% compared to head (4639a43) 39.28%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1960   +/-   ##
=======================================
  Coverage   39.28%   39.28%
=======================================
  Files         177      177
  Lines       10742    10742
=======================================
  Hits         4220     4220
  Misses       6228     6228
  Partials      294      294

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


Make it easier to find / work with ByteView

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
While working with StringViewArray's downstream in DataFusion, I found it was not always clear that ByteView exists for creating/destructuring  the u128s so I wanted to write some additional documentation.
While doing so, I also found it quite awkward to write the examples (specifically setting the prefix)
let view = ByteView {
   length: 12,
   // convert 4 byte &str to u32
   prefix: u32::from_le_bytes(prefix.as_bytes().try_into().unwrap()),
   buffer_index: 3,
   offset: 42,
};

Describe the solution you'd like
I would like better documentation and a builder style API
Describe alternatives you've considered

Additional context

label_issue.py automatically added labels {'arrow'} from #6479


Code modularization and clarity

This PR is intended to resolve #25 and #32.
The base platformer and questions have been extracted, with unique assets for each language.

LGTM ! Great work @Devansh-bit


fix mesh from outer nested message definition

Description
Fixes #1786
Type of change

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

Checklist:

[ ] I have followed the CONTRIBUTING doc and the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests and linter rules pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

If I understand what should we do here correctly, every generated type that doesn't match exactly with configured in user setting should use absolute package path.
The Request.Nested type in the io.xtech package and the Nested type in the io.xtech.request package must have different names.
Currently, we don't have a strategy for this, so it makes conflicts on production use cases.

To avoid the problem, we can strictly distinguish between package resolutions and type resolutions and use underscore in generated type names. (e. g. IoXtechRequest_Nested vs IoXtech_RequestNested)
However, this is a breaking change and it should be dealing with the namingConvention transform and others.

Thank you for the PR!
See https://github.com/Urigo/graphql-mesh/pull/2260/commits/51cd54f182abc18d39329671527673c6f5c4429f


Support pg_search extension

pg_search is a great extension for full-text search using BM25 algorithm, so it will have Elastic-level search quality and powerful performance(benchmark).

Please consider to support this extension, Thanks.

We'd love to be supported in pglite!

Hey, yes we 100% want to support pg_search, it's perfect for the embedded FTS use case.
We've not yet tackled any pgrx (Rust API for Postgres extensions) based extensions, but it's high on the list, with pg_search the first we will take on. I'm hopeful that pgrx extensions shouldn't be too hard to get working as Rust has very good WASM support.
@philippemnoel I'll let yo know as soon as we start working on it.


Wild Nidoran Female can't compute moves in battle

At level 4, it gets spawned with no moves.

Looks like it's got the wrong math.ts data!


tls.createSecurePair is being runtime-deprecated

Ref: https://github.com/nodejs/node/pull/11349
Used in:
mysql-2.13.0.tgz/lib/Connection.js:353:    var securePair         = tls.createSecurePair(credentials, false, true, rejectUnauthorized);

and tests.
Related: #737, https://github.com/sidorares/node-mysql2/pull/367.

Since it I in a block for old versions, we shouldn't be affected, right?

At least for the no test code.

@dougwilson You are correct, I somehow missed that feature detection is also present here, sorry.
Closing this. I'm also guessing that #737 can be closed.

Cool, just wasn't sure from reading the Node.js issue :) Yes, it is a large block. The older Node.js versions are getting on the chopping block for this module in the near future, so one day it'll be gone from the source :D Thanks for the warning on this deprecation.


Type VideoInfo["basic_info"] should overlap with type Video

Describe your suggestion
Instead of having one have thumbnails and the other one thumbnail, it would be called the same, and instead of one having author.name and the other having one called author, they could both just have channel etc... so that they could both be used in the same scenario to get data without having to parse one to the other.
Other details
No response
Checklist

[X] I am running the latest version.
[X] I checked the documentation and found no answer.
[X] I have searched the existing issues and made sure this is not a duplicate.
[X] I have provided sufficient information.

Also missing channel thumbnail in videoinfo

I disagree with trying to line the objects up, firstly this would be a breaking change for probably most YouTube.js users and secondly because they work completely differently.
While the channel name and id are available for both getBasicInfo and getInfo, the channel thumbnail and verified status are only available for getInfo (that's why you can get them from the secondary_info property, instead of the basic_info one).


ESP32-C5 RMII Ethernet Pins (IDFGH-14082)

Is your feature request related to a problem?
No response
Describe the solution you'd like.
I have a working commercial solution using the ESP32 and the IP101GRR IC, but would like to upgrade this to use the ESP32-C5 so it can have 5GHz WiFi as well as Ethernet.
For the ESP32 the RMII pins were fixed, will this be the case for the ESP32-C5 as well? I cannot find much in the ethernet documentation. Please let me know if RMII will be supported on the ESP32-C5 and what pins should be used. I have already received some samples of the ESP32-C5-NF4
Describe alternatives you've considered.
No response
Additional context.
No response

ESP32-C5 doesn't have internal EMAC hence no RMII interface. Currently, only ESP32 and ESP32-P4 have internal EMAC. If you want to have Ethernet capability with C5, you would need to use one of SPI Ethernet module we support. However note that SPI Ethernet modules have naturally worse performance than internal EMAC (let's say around 18 Mbps for UDP in average).


[WFCORE-1464] ensure LogContexts for sub deployments are unregistered

https://issues.jboss.org/browse/WFCORE-1464

Is this the same change as the one James already marked Ready for Merge? I had tested and was about to merge that one when I saw it was closed. Looked like you closed it because the branch got messed up or something. If this is the same I'll just merge it.

Yes, this is the same.


Support pad 1.x

Updated

Looks nice for me - the failed tests are due to the .28 release - already on it.
Nothing keeps us from merging this.


Provide interfaces for non-node entity types, e.g., Taxonomy

The basic-starter example show cases how to render nodes. We should show case how to render at least one other entity type to demonstrate that none of the code is written specifically for nodes, and could be utilized for other entity types too.

Examples of rendering Taxonomy Term was added in https://github.com/acquia/next-acms/pull/53


Update .bookignore file

We haven't published the updated docs to https://developer.tidepool.org/uploader in a long time, so when I just did this I had to update the .bookignore file for Gitbook.

Going to merge this, as it's not user-facing.


Help i lost most of the folders of my proyect

Describe the bug
so after a bad deploy and then a refresh i lost most of the folder files of my proyect
Link to the Bolt URL that caused the error
https://bolt.new/~/sb1-vtdezq
Steps to reproduce
go to bolt, select https://bolt.new/~/sb1-vtdezq chat, then try to deploy, no code all lost
Expected behavior
i should be able to see this folders

Screen Recording / Screenshot

Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 129
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 55411247,
  "usedJSHeapSize": 52540619,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = AugustoPrz
Chat ID = 3e0f890bb464

Additional context
No response

Hey any luck with restoring your files..? My project is also deleted after 3 days of work.

@AugustoPrz It sounds like you’ve been affected by a bug we identified and fixed earlier today in the rollback feature. Apologies for the frustrating experience! Please follow the instructions in #1104 to reach out, and we’ll work with you to attempt restoring your project. Thanks for your patience as we get this sorted out for you.

🎉 Backups Have Landed on Production!
Open your affected project and in the lower left hand corner of the screen navigate to Settings > Backups to restore your project to any previous state!
Please let us know in #1104 if you have any issues using this brand new feature.


tls.options only applied when using TOML file provider format

Do you want to request a feature or report a bug?
Bug
What did you do?
I wanted to enforce minimum TLS version and limit possible ciphers as described here (https://docs.traefik.io/https/tls/#tls-options). My config file is in YAML format and I wasn't able to do this. After reading through existing issues (https://github.com/containous/traefik/issues/6181, https://github.com/containous/traefik/issues/5507) and community discussions (https://community.containo.us/t/unable-to-set-tls-options/2437) I've split my config file to multiple files, moved tls section to TOML format and it worked instantly.
I don't know if this is YAML related, but for at least one person besides me (https://community.containo.us/t/unable-to-set-tls-options/2437/7) switching from YAML to TOML solved the issue.
Initial config file excerpt
## /etc/traefik/traefik.yml

providers:
  docker: {}

entryPoints:
  web:
    address: ":80"
    http:
      redirections:
        entryPoint:
          to: "websecure"
          scheme: "https"
  websecure:
    address: ":443"
    http:
      tls:
        options: "mintls12@file"
        certResolver: leresolver
        domains:
        - main: example.io
          sans:
          - "*.example.io"
tls:
  options:
    default:
      minVersion: VersionTLS12
    mintls12:
      minVersion: VersionTLS12
      curvePreferences:
        - CurveP521
        - CurveP384
      sniStrict: true
      cipherSuites:
        - "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384"
        - "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305"
        - "TLS_AES_256_GCM_SHA384"
        - "TLS_CHACHA20_POLY1305_SHA256"

Errors seen in log file after startup:
time="2020-06-14T22:48:17Z" level=debug msg="unknown TLS options: mintls12@file" routerName=io-example-web@docker entryPointName=websecure

Working file after split (only changes)
## /etc/traefik/traefik.yml

providers:
  file:
    directory: "/conf/"
    watch: true
  docker: {}

## /conf/tls.toml
[tls.options]

  [tls.options.default]
    minVersion = "VersionTLS12"

  [tls.options.mintls12]
    minVersion = "VersionTLS12"
    curvePreferences = ["CurveP521", "CurveP384"]
    sniStrict = true
    cipherSuites = [
        "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
        "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
        "TLS_AES_256_GCM_SHA384",
        "TLS_CHACHA20_POLY1305_SHA256"
    ]

Normal log message:
time="2020-06-14T23:11:07Z" level=debug msg="Adding route for example.io with TLS options mintls12@file" entryPointName=websecure

Output of traefik version:
Version:      2.2.1
Codename:     chevrotin
Go version:   go1.14.2
Built:        2020-04-29T18:02:09Z
OS/Arch:      linux/amd64

Hello @SPodjasek,
thanks a lot for your interest in the project.
You saw the first issue, as you did put dynamic configuration in the static configuration where its not evaluated. Thus, its working in your second example as its treated correctly as dynamic configuration then.

@SantoDE Thank you very much for this response.
To summarize:
Default config file /etc/traefik/traefik.(to|y)ml is considered static configuration and it's not possible for that configuration to be picked in any way on 'dynamic side'.
So maybe there should be some side note about that in docs?
I mean, my mental flow was that if I set both options in the same file (tls.options & entryPoints using this options), they should be visible and usable to each other - apparently they aren't and IMHO it's a bit confusing.

in the v2, the dynamic configuration and the static configuration must be defined in separated files:

https://docs.traefik.io/v2.2/getting-started/configuration-overview/#the-dynamic-configuration
https://docs.traefik.io/v2.2/getting-started/configuration-overview/#the-static-configuration

Maybe if mine initial, static config file would look just as simple as this:
## /etc/traefik/traefik.yml

providers:
  file:
    directory: "/conf/"
    watch: true
  docker: {}

and every other configuration would be placed in /conf/* directory, despite config file format - it would work for me from the beginning.

Ok, silly me - as a conclusion for anybody reading this in the future:

keep in mind dynamic & static configuration aspects
carefully read comments in configuration examples, if it states # Dynamic configuration don't place it in startup/static config file


elapsed to Milliseconds

Partly closes https://github.com/roadrunner-server/roadrunner/issues/1858

@coderabbitai review

@coderabbitai review

@coderabbitai review


Add typehints and indicate support for typehints in setup.py

this is primarily to fix these warnings that I get from using your library:
server.py:7: error: Cannot find implementation or library stub for module named 'asyncio_throttle'
server.py:7: note: See https://mypy.readthedocs.io/en/latest/running_mypy.html#missing-imports

the changes involved here are twofold: introduce py.typed to indicate we have typehints and move to a package format because you cannot have a py.typed file without it.

no prob. thanks for the library.


Paper reference for MC Tracker?

I see that the multi-camera tracking algorithm is not provided by the DeepStream SDK but rather it has been implemented from scratch by hand. Are there any papers or references that validate and benchmarks the performance of this implementation? https://github.com/NVIDIA-AI-IOT/deepstream_360_d_smart_parking_application/blob/b9b1f9e9aa84e379c573063fc5622ef50d38898d/tracker/code/mctrack/mctracker.py#L1625

I have the same doubt,the readme mentions usage of inter camera clustering which is used to perform the tracking.It would be nice if other references were added that would expalin this concept in more details


fix(*): prevent auth:cancels from colliding

Pushed a few changes that clean up code. We had two incantations of login and cancel, and the [login,cancel]Sess version made it possible to fall into a race condition due to the use of an external deis cli. Since we were just using [login,cancel]Sess, I swapped usage to just use [login,cancel].

LGTM++. Also, how do you pronounce Sess? :smiling_imp:

I am on a mission to remove all things in the world that sound like Seth. First victory: Sess.


Communicate with Moore potential budget changes

Moore budget is all "Consultants" and has no line item for fringe ("benefits"). Since we anticipate paying some folks (via subawards) with summer salary, we are anticipating incurring fringe costs. Please confirm with Moore that this is an ok re-budget.

I think this is done, right? Or, at least, it has not been an issue in the last ~year. Can we close it? (It'd be great if we actually had an artefact from Moore or NumFOCUS providing the confirmation requested, of course...)


[dev-tool] compilation errors with TypeScript 5.7.2

Likely due to the usage of ts-morph internals in our codemods
> tsc && npm run lint && npm run check-format

src/util/admin/migrate-package/codemods/replaceChaiAsPromised.ts:40:14 - error TS2352: Conversion of type 'Node' to type 'Expression' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Property '_expressionBrand' is missing in type 'Node' but required in type 'Expression'.

40             [args[0].compilerNode as ts.Expression],
                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  ../../temp/node_modules/.pnpm/typescript@5.7.2/node_modules/typescript/lib/typescript.d.ts:4831:9
    4831         _expressionBrand: any;
                 ~~~~~~~~~~~~~~~~
    '_expressionBrand' is declared here.

src/util/admin/migrate-package/codemods/replaceChaiAsPromised.ts:48:26 - error TS2345: Argument of type '() => ts.AwaitExpression' is not assignable to parameter of type '(traversal: TransformTraversalControl) => Node'.
  Call signature return types 'AwaitExpression' and 'Node' are incompatible.
    The types of 'kind' are incompatible between these types.
      Type 'SyntaxKind.AwaitExpression' is not assignable to type 'SyntaxKind'.

48           node.transform(() => {
                            ~~~~~~~

src/util/admin/migrate-package/codemods/replaceChaiAsPromised.ts:57:36 - error TS2352: Conversion of type 'Node' to type 'Expression' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Property '_expressionBrand' is missing in type 'Node' but required in type 'Expression'.

57                 args.length > 1 ? [args[1].compilerNode as ts.Expression] : [], // Pass second argument if provided
                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  ../../temp/node_modules/.pnpm/typescript@5.7.2/node_modules/typescript/lib/typescript.d.ts:4831:9
    4831         _expressionBrand: any;
                 ~~~~~~~~~~~~~~~~
    '_expressionBrand' is declared here.

src/util/admin/migrate-package/codemods/replaceSinonStubs.ts:80:39 - error TS2345: Argument of type 'LeftHandSideExpression' is not assignable to parameter of type 'Node'.
  Types of property 'kind' are incompatible.
    Type 'import("/home/meng/git/jssdk/common/temp/node_modules/.pnpm/@ts-morph+common@0.25.0/node_modules/@ts-morph/common/lib/typescript").ts.SyntaxKind' is not assignable to type 'import("/home/meng/git/jssdk/common/temp/node_modules/.pnpm/typescript@5.7.2/node_modules/typescript/lib/typescript").SyntaxKind'.
      Each declaration of 'SyntaxKind.PartiallyEmittedExpression' differs in its value, where '355' was expected but '354' was given.

80         ts.isPropertyAccessExpression(callee.compilerNode) &&
                                         ~~~~~~~~~~~~~~~~~~~

src/util/admin/migrate-package/codemods/replaceSinonStubs.ts:81:47 - error TS2339: Property 'expression' does not exist on type 'never'.
  The intersection 'LeftHandSideExpression & PropertyAccessExpression' was reduced to 'never' because property 'kind' has conflicting types in some constituents.

81         isSinonIdentifier(callee.compilerNode.expression.getText()) &&
                                                 ~~~~~~~~~~

src/util/admin/migrate-package/codemods/replaceSinonStubs.ts:82:29 - error TS2339: Property 'name' does not exist on type 'never'.
  The intersection 'LeftHandSideExpression & PropertyAccessExpression' was reduced to 'never' because property 'kind' has conflicting types in some constituents.

82         callee.compilerNode.name.getText() === "restore"
                               ~~~~

src/util/admin/migrate-package/codemods/replaceSupportsTracing.ts:40:51 - error TS2345: Argument of type 'LeftHandSideExpression' is not assignable to parameter of type 'Node'.
  Types of property 'kind' are incompatible.
    Type 'import("/home/meng/git/jssdk/common/temp/node_modules/.pnpm/@ts-morph+common@0.25.0/node_modules/@ts-morph/common/lib/typescript").ts.SyntaxKind' is not assignable to type 'import("/home/meng/git/jssdk/common/temp/node_modules/.pnpm/typescript@5.7.2/node_modules/typescript/lib/typescript").SyntaxKind'.
      Each declaration of 'SyntaxKind.PartiallyEmittedExpression' differs in its value, where '355' was expected but '354' was given.

40       if (callee && ts.isPropertyAccessExpression(callee.compilerNode)) {
                                                     ~~~~~~~~~~~~~~~~~~~

src/util/admin/migrate-package/codemods/replaceSupportsTracing.ts:42:47 - error TS2339: Property 'expression' does not exist on type 'never'.
  The intersection 'LeftHandSideExpression & PropertyAccessExpression' was reduced to 'never' because property 'kind' has conflicting types in some constituents.

42           ts.isIdentifier(callee.compilerNode.expression) &&
                                                 ~~~~~~~~~~

src/util/admin/migrate-package/codemods/replaceSupportsTracing.ts:43:31 - error TS2339: Property 'expression' does not exist on type 'never'.
  The intersection 'LeftHandSideExpression & PropertyAccessExpression' was reduced to 'never' because property 'kind' has conflicting types in some constituents.

43           callee.compilerNode.expression.text === "expect" &&
                                 ~~~~~~~~~~

src/util/admin/migrate-package/codemods/replaceSupportsTracing.ts:44:31 - error TS2339: Property 'name' does not exist on type 'never'.
  The intersection 'LeftHandSideExpression & PropertyAccessExpression' was reduced to 'never' because property 'kind' has conflicting types in some constituents.

44           callee.compilerNode.name.text === "extend"
                                 ~~~~

src/util/admin/migrate-package/codemods/replaceSupportsTracing.ts:92:26 - error TS2345: Argument of type '() => ts.AwaitExpression' is not assignable to parameter of type '(traversal: TransformTraversalControl) => Node'.
  Call signature return types 'AwaitExpression' and 'Node' are incompatible.
    The types of 'kind' are incompatible between these types.
      Type 'SyntaxKind.AwaitExpression' is not assignable to type 'SyntaxKind'.

92           node.transform(() => {
                            ~~~~~~~

src/util/admin/migrate-package/codemods/replaceSupportsTracing.ts:99:22 - error TS2352: Conversion of type 'Node' to type 'Expression' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Property '_expressionBrand' is missing in type 'Node' but required in type 'Expression'.

99                     [asyncFunction.compilerNode as ts.Expression],
                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  ../../temp/node_modules/.pnpm/typescript@5.7.2/node_modules/typescript/lib/typescript.d.ts:4831:9
    4831         _expressionBrand: any;
                 ~~~~~~~~~~~~~~~~
    '_expressionBrand' is declared here.

src/util/admin/migrate-package/codemods/replaceSupportsTracing.ts:104:18 - error TS2352: Conversion of type 'Node' to type 'Expression' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
  Property '_expressionBrand' is missing in type 'Node' but required in type 'Expression'.

104                 [methodArray.compilerNode as ts.Expression],
                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  ../../temp/node_modules/.pnpm/typescript@5.7.2/node_modules/typescript/lib/typescript.d.ts:4831:9
    4831         _expressionBrand: any;
                 ~~~~~~~~~~~~~~~~
    '_expressionBrand' is declared here.

Found 13 errors in 3 files.

ts-morph v25 now depends on typescript 5.7.2
However, this could happen again in future updates.  Should we

skip type checking for the codemods, or
retire the codemods when ESM migration completes, or
fix codemodes so no internals are used.


Makes the C core build for iOS.

Ah, yes. Travis integration was added we release 0.5. Please try this in the master branch.

Please send another PR against the master, since travis does not work against this branch. WE will rely on the testing against the master.

Merging this as the corresponding changes against master passed in travis.


Combine support for the Decodable QuerySnapshot publisher

Here is a proposal for a Decodable publisher for the upstream QuerySnapshot.
Here is a code snippet using the publisher returned by getDocument()
    let noBooks = [Book]()
    db.collection("books").getDocuments()
       .decode(type: Book.self)
       .collect()
       .replaceError(with: noBooks)
       .assign(to: \.books, on: self)
       .store(in: &cancellables)

@googlebot I signed it!

Thanks for your contribution, @ziadtamim !
We're in the process of adding Combine support to Firebase, and have already started work on this:

The plan is to develop this feature on the combine-main working branch.
We've got a project set up to track work here.
PR #6976 will act as the model implementation - it adds some infrastructure, and is intended to set the style for how Combine support should look like. The initial comment on the PR discusses some decisions we made so far.
There's also a suggestion for adding Combine support to Firestore in this PR: #6960, which is based on #6940
Adding support for Result type will (by way of #6940) allow us to simplify much of the code.

That being said, I will take a closer look and review your PR once I get back to work next week.

@ziadtamim we'd like to delete combine-master in favour of combine-main for clarity (see #7238) - would you mind re-targeting this PR to peterfriese-combine?

@ziadtamim we'd like to delete combine-master in favour of combine-main for clarity (see #7238) - would you mind re-targeting this PR to peterfriese-combine?

@ziadtamim we'd like to delete combine-master in favour of combine-main for clarity (see #7238) - would you mind re-targeting this PR to peterfriese-combine?

@peterfriese Done.

@ziadtamim we'd like to delete combine-master in favour of combine-main for clarity (see #7238) - would you mind re-targeting this PR to peterfriese-combine?

@peterfriese Done.

@ziadtamim we'd like to delete combine-master in favour of combine-main for clarity (see #7238) - would you mind re-targeting this PR to peterfriese-combine?

@peterfriese Done.

@ziadtamim we'd like to delete combine-master in favour of combine-main for clarity (see #7238) - would you mind re-targeting this PR to peterfriese-combine?

@peterfriese Done.

Was considered to extend Firestore.Decoder to adopt the protocol TopLevelDecoder (and TopLevelEncoder)?
Combine already has a builtin decode (and encode) method.
I'm not 100% sure TopLevelDecoder.Input will work with both DocumentSnapshot and QueryDocumentSnapshot, though. Maybe will be necessary to make a dummy protocol.

Sorry this got closed - I was cleaning up and deleted my personal working branch.
Please rebase this work onto combine-main.

This is continued in #7549.


add optional vagrant senairo for local testing and development.

The libvirt and nova roles currently uses the delegated driver
which runs molecule agaisnt localhost. This is requried for
ci as the podman driver cannot be used with this role however
it also means you must use a seperate development vm.
This change readds supprot for using the molecule vagrant plugin
for this role and configures the vagrant senario to use the
prepare, converge and verify playbooks from the default delegated
senario.
Addtionally this change updates yamllint and ansible-lint to not
scan files in a venv i.e. .venv in the root of the edpm-ansible
repo. .venv is already ignored by .gitignore so this also only
affect local development.

recheck #523 merged

ok cool the nova and libvirt molecule roles pass ci.
https://review.rdoproject.org/zuul/build/b49555739ab8416d8ee3669913b70b5d
https://review.rdoproject.org/zuul/build/7ae5415e78ea47aa913f7a785bb5a508
and the testing in ci is only run with the delegated driver so this is working as intended

@SeanMooney i left few comments (and a question :D), once addressed it's lgtm for me!

recheck


Wrong First Name and Surname in Serializing

The first name and last name during serialization (and maybe deserialization) is wrong. The current output of John Doe is:
N:John;Doe;
FN:John Doe

which should be:
N:Doe;John;;;
FN:John Doe

As per the Rfc2426, the value for token N is:
Family; Given; Middle; Prefix; Suffix

Lastly, IMHO, the vCard class should have these additional properties:

Middle Name
Prefix
Suffix

For Frapid framework, we're already using this library and would like to offer a helping hand.

Would you like us to fix these issues and send pull requests?
Once you accept the pull requests, how long would it normally take for it to appear in nuget?

@mixerp Please PR's are very welcome

Fixed in current release. cc @mixerp


Update VC IdP in Access to Court Materials realm

This is a follow-up task to #93.
New instances of VC-AuthN have been deployed as part of #93, this task is to:

[ ] switch the Identity Provider configuration in the acces-to-court-materials realms to use the new instance
[ ] ensure that backwards-compatibility settings are turned on
[ ] decommission the existing, outdated deployments label app=vc-authn-oidc and app=vc-authn-oidc-rev

dev environment has been fully upgraded to use VC-AuthN 2.0.
I am still troubleshooting validating issues in the test environment before fully moving it over to the new service.

All instances of VC-AuthN 2.0 have been upgraded to the latest 2.0.0-rc1 release. The dev environmanet has been fully upgraded to use VC-AuthN 2.0, while test and prod have only been upgraded for the (currently unused) Identity Provider that used to only support revocable credentials.
On hold with further upgrades and testing by partners until a new BC Wallet release addressing slowness and issues with revocable credentials is pushed to the app stores (see https://github.com/bcgov/bc-wallet-mobile/issues/1512).

Production environments have been migrated to the new version as of December 6th.


Medical Icons

Hi,
Significant packages of medical icons in svg are currently lacking. It is a very broad category, but I think it could pay for itself.
If you include this package, many of us would purchase such a package for use.
NB. I did not put specific icons because of the shear numbers that would be required for such a venture. If you are embarking on it, I would be happy to give some advice/collaborate with you as to expectations, types etc.
Please let me know what you think.
Cheers

What is the reason for closing?
Thanks