https and http to https redirect is not working with Kubernetes using traefik as ingress controller.

I am trying to make https and https redirect work with ingress, however to no avail since quiet sometime now. My ingress rule is as follows:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: "demo-ingress"
  namespace: "demo"
  labels:
  annotations:
    kubernetes.io/ingress.class: traefik
    traefik.frontend.rule.type: PathPrefix
    traefik.ingress.kubernetes.io/frontend-entry-points: http,https
    traefik.ingress.kubernetes.io/redirect-entry-point: https
spec:
  rules:
  - host: samplehost.example.com
    http:
     paths:
     - path: /
       backend:
         serviceName: ui
         servicePort: 80
     - path: /solr/
       backend:
         serviceName: cache
         servicePort: 8983
     - path: /VNF_DASHBOARD_BE/
       backend:
         serviceName: be
         servicePort: 80
  tls:
   - secretName: demo-tls-cert

Errors at traefik pods are as follows:
time="2019-07-10T03:34:43Z" level=error msg="Undefined entry point(s) 'https' for frontend http-https_samplehost.example.com/"
time="2019-07-10T03:34:43Z" level=error msg="Undefined entry point(s) 'https' for frontend http-https_samplehost.example.com/VNF_DASHBOARD_BE/"
time="2019-07-10T03:34:43Z" level=error msg="Undefined entry point(s) 'https' for frontend http-https_samplehost.example.com/solr/"
time="2019-07-10T03:34:43Z" level=error msg="error creating Frontend Redirect: unknown target entrypoint \"http\". Skipping frontend http-https_samplehost.example.com/..."
time="2019-07-10T03:34:43Z" level=error msg="error creating Frontend Redirect: unknown target entrypoint \"http\". Skipping frontend http-https_samplehost.example.com/VNF_DASHBOARD_BE/..."
time="2019-07-10T03:34:43Z" level=error msg="error creating Frontend Redirect: unknown target entrypoint \"http\". Skipping frontend http-https_samplehost.example.com/solr/..."

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.


Savings-Account: Fix copy/paste error from positive to negative test.

This is a duplication of #1190.  It has been a few weeks since the original post, and over a week since the last comment was posted.  I ran across this same issue today while working on this exercise.  It appears that the typos have been fixed on the main branch already, so I just included the number fixes (i.e. making the test honest about testing a negative balance).

Thank you @k3dB !  There were so many different ways to go with that last change.  That was one I had not considered.


Adding metrics for custom resources

PR contains following changes-

Configurations for scraping custom resource metrics related to Percona Kubernetes Operators
Configurations for scraping kubelet metrics.

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

Codecov Report

Merging #116 (cebe56d) into main (2a2047d) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main    #116   +/-   ##
=====================================
  Coverage   5.18%   5.18%
=====================================
  Files         10      10
  Lines       2756    2756
=====================================
  Hits         143     143
  Misses      2589    2589
  Partials      24      24

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Type commands

Added commands parameter to type method
Added clear method to empty terminal
Added unit tests
Updated documentation
Removed commands parameter from constructor

Resolves #32.

Coverage decreased (-3.05%) to 76.947% when pulling c503403232e9ae1d1560e9977612aa6118dc908b on type-commands into 83254d70a99903b7ef96d97ec7a0beb22b86d1cb on main.


Changed Pixel Avatars to Pixel Devs and Social Links Image

All the references to Pixel Avatars (Social links and descriptions) were changed to pixel devs
Also, changed the image (in og and twitter social links) to the one @eknobl created

Thanks @7i7o ! Merging


[PE-D] Adding the same person after they have been removed after a session result in an error

From UG:
"If session or schedule was previously called, the person at the specified INDEX will be removed from the list."
Comment:
It seems that the person still exist in the list, it is just that the person is not shown. After adding the same person again with different case no, the person that was previously removed appear again.

This could prove to limit the app to support only up to 1 million people without manually removing the person using delete command but more importantly the person is not actually removed from the system.

Labels: type.FunctionalityBug severity.High
original: kanjitp/ped#6

Edit UG: "If session or schedule was previously called, the person at the specified INDEX will be removed from the list." -> "list" should be changed to schedule or display or something that is not list


Intermittent Realm Accessed from Incorrect Thread after Realm version upgrade

Goals
We use a wrapper around Realm to abstract away some of the write/read logic throughout our application as a way to modularize and simplify our code. We recently upgraded realm from 3.17.3 -> 5.0.1
Expected Results
Our realm wrappers will grab an instance of realm and perform a write transaction on that instance with a Dispatch Item on an autorelease pool and throw it onto our static utility queue to complete the transaction. This worked perfectly prior to upgrading realm.
Actual Results
(print statements for getting realm and writing on realm threads to verify that they're indeed the same, crash happens in the realm.beginWrite() immediately after the latter print statement where we just verified thread safety)
Getting realm on thread <NSThread: 0x60000053f340>{number = 27, name = (null)}

=============
Performing action on thread <NSThread: 0x60000053f340>{number = 27, name = (null)}
2020-06-08 09:22:39.985484-0700 Dev[77025:6312770] *** Terminating app due to uncaught exception 'RLMException', reason: 'Realm accessed from incorrect thread.'
*** First throw call stack:
(
0   CoreFoundation                      0x00007fff23e3cf0e _exceptionPreprocess + 350
1   libobjc.A.dylib                     0x00007fff50ba89b2 objc_exception_throw + 48
2   Realm                               0x000000010a0b1bbd Z18RLMSetErrorOrThrowP7NSErrorPU15__autoreleasingS0 + 505
3   Realm                               0x000000010a0853fd Z26RLMRealmTranslateExceptionPU15__autoreleasingP7NSError + 488
4   Realm                               0x000000010a086d54 -[RLMRealm beginWriteTransactionWithError:] + 44
5   Core                                0x0000000107cc049b $s4Core14RealmUtilitiesC5writeyAA7RequestCyytGy0B5Swift0B0VKcFZAA11CancellableVyAA8ResponseOyytGccfU_yycfU_yyXEfU + 667
6   Core                                0x0000000107cc073f $ss5Error_pIgzo_ytsAA_pIegrzo_TR + 15
7   Core                                0x0000000107cc23e4 $ss5Error_pIgzo_ytsAA_pIegrzo_TRTA.28 + 20
8   libswiftObjectiveC.dylib            0x000000010bad4c7e $s10ObjectiveC15autoreleasepool8invokingxxyKXE_tKlF + 46
9   Core                                0x0000000107cc01a6 $s4Core14RealmUtilitiesC5writeyAA7RequestCyytGy0B5Swift0B0VKcFZAA11CancellableVyAA8ResponseOyytGccfU_yycfU + 230
10  Core                                0x0000000107c69670 $sIeg_IeyB_TR + 48
11  libdispatch.dylib                   0x000000010bb534dc _dispatch_block_async_invoke2 + 83
12  libdispatch.dylib                   0x000000010bb44e8e _dispatch_client_callout + 8
13  libdispatch.dylib                   0x000000010bb477a3 _dispatch_continuation_pop + 552
14  libdispatch.dylib                   0x000000010bb46bbb _dispatch_async_redirect_invoke + 771
15  libdispatch.dylib                   0x000000010bb56399 _dispatch_root_queue_drain + 351
16  libdispatch.dylib                   0x000000010bb56ca6 _dispatch_worker_thread2 + 135
17  libsystem_pthread.dylib             0x00007fff51c089f7 _pthread_wqthread + 220
18  libsystem_pthread.dylib             0x00007fff51c07b77 start_wqthread + 15
)
libc++abi.dylib: terminating with uncaught exception of type NSException

thread #36, queue = 'realm_write_queue', stop reason = signal SIGABRT

frame #0: 0x00007fff51b6133a libsystem_kernel.dylib__pthread_kill + 10 frame #1: 0x00007fff51c0be60 libsystem_pthread.dylibpthread_kill + 430
frame #2: 0x00007fff51af0b7c libsystem_c.dylibabort + 120 frame #3: 0x00007fff4f9f7858 libc++abi.dylibabort_message + 231
frame #4: 0x00007fff4f9e8cbf libc++abi.dylibdemangling_terminate_handler() + 262 frame #5: 0x00007fff50ba8c0b libobjc.A.dylib_objc_terminate() + 96
frame #6: 0x00007fff4f9f6c87 libc++abi.dylibstd::__terminate(void (*)()) + 8 frame #7: 0x00007fff4f9f6c29 libc++abi.dylibstd::terminate() + 41
frame #8: 0x00007fff50ba8bab libobjc.A.dylibobjc_terminate + 9 frame #9: 0x000000010bb44ea2 libdispatch.dylib_dispatch_client_callout + 28
frame #10: 0x000000010bb477a3 libdispatch.dylib_dispatch_continuation_pop + 552 frame #11: 0x000000010bb46bbb libdispatch.dylib_dispatch_async_redirect_invoke + 771
frame #12: 0x000000010bb56399 libdispatch.dylib_dispatch_root_queue_drain + 351 frame #13: 0x000000010bb56ca6 libdispatch.dylib_dispatch_worker_thread2 + 135
frame #14: 0x00007fff51c089f7 libsystem_pthread.dylib_pthread_wqthread + 220 frame #15: 0x00007fff51c07b77 libsystem_pthread.dylibstart_wqthread + 15

Steps to Reproduce
See code sample below, but this is basically an intermittent but fairly frequent crash with the architecture we're using for our realm write transactions (so you have to do a couple of write transactions and eventually it happens).
Code Sample
//realm write function
public static func write(_ action: @escaping (_ realm: Realm) throws -> Void) -> Request {
return Request(action: { (completion) -> Cancellable in
        let item = DispatchWorkItem {
            autoreleasepool {
                let realm = RealmUtilities.realm //SEE NEXT CODE SNIPPET FOR HOW THIS WORKS
                print("""
                    =============
                    Performing action on thread \(Thread.current)
                    =============
                    """)
                realm.beginWrite() //CRASH OCCURS HERE
                print("print statement immediately after realm.beingWrite()") //NEVER RUNS (if you set breakpoints for all OBJ-C and Swift Errors you will also validate that beginWrite is where we throw the realm thread exception)
                do {
                    try action(realm)
                    try realm.commitWrite()
                    completion(.success(()))
                } catch {
                    realm.cancelWrite()
                    completion(.error(error))
                }
            }
        }

        RealmUtilities.writeQueue.async(execute: item) //SEE BELOW CODE SNIPPET FOR HOW THIS WORKS
        return Cancellable { item.cancel() }
    })
}

//how we get realm instance
public static var realm: Realm {
do {
print("""
~~~~~~~~~~~~~
Getting realm on thread (Thread.current)
~~~~~~~~~~~~~
""")
return try Realm(configuration: realmConfiguration)
} catch {
ErrorHandler.shared.handleError(
"loading Realm",
error: error,
alertUser: false)
DDLogError("Error loading Realm, attempting to recover by nuking the database.")
nukeRealm()
do {
return try Realm(configuration: realmConfiguration)
} catch {
//error handling
}
}
//utility queue for all write transactions
public class RealmUtilities {
...
static private let writeQueue = DispatchQueue(label: "realm_write_queue", qos: .utility, attributes: .concurrent)
...
}
##Explanation and observations
So even though we seem to be accessing realm from the same thread for the write as the thread we get the realm instance on, we are still getting this crash with error realm was accessed from incorrect thread. Curiously, this crash goes away (or at least I haven't been able to reproduce a crash with it yet) if we change the queue from asyn to sync. Having ALL realm write transactions be synchronous is obviously not ideal, but it may give some insight into the issue.
Version of Realm and Tooling
Realm framework version: v3.17.3 -> v5.0.1 (even tried downgrading to v4.4.0 and still had this issue, haven't yet tried versions older than that)
Realm Object Server version: N/A
Xcode version: 11.5
iOS/OSX version: 13.5.1
Dependency manager + version: Carthage v0.33.0

I am also seeing these crashes.
Can it be related to queue-confined realms/notifications?
I use notifications on a separate queue. In RLMCollection.mm I found method that is responsible for subscribing - RLMAddNotificationBlock
If queue is used, config from original Realm is taken (including original scheduler), passed on the queue block to create another queue-confined Realm:
RLMRealmConfiguration *config = realm.configuration;
    dispatch_async(queue, ^{
        std::lock_guard<std::mutex> lock(token->_mutex);
        if (!token->_realm) {
            return;
        }
        NSError *error;
        RLMRealm *realm = token->_realm = [RLMRealm realmWithConfiguration:config queue:queue error:&error];
        if (!realm) {
            block(nil, nil, error);
            return;
        }
        RLMCollection *collection = [realm resolveThreadSafeReference:tsr];
        token->_token = RLMGetBackingCollection(collection).add_notification_callback(CollectionCallbackWrapper{block, collection, skipFirst});
    });

In realm init I see configuration = [configuration copy];, but this only creates RLMRealmConfiguration copy. Then if queue is passed, another scheduler is created and assigned to the same Realm::Config
    Realm::Config& config = configuration.config;

    RLMRealm *realm = [[self alloc] initPrivate];
    realm->_dynamic = dynamic;

    // protects the realm cache and accessors cache
    static std::mutex& initLock = *new std::mutex();
    std::lock_guard<std::mutex> lock(initLock);

    try {
        if (queue) {
            if (queue == dispatch_get_main_queue()) {
                config.scheduler = realm::util::Scheduler::make_runloop(CFRunLoopGetMain());
            }
            else {
                config.scheduler = realm::util::Scheduler::make_dispatch((__bridge void *)queue);
            }
            if (!config.scheduler->is_on_thread()) {
                throw RLMException(@"Realm opened from incorrect dispatch queue.");
            }
        }
        realm->_realm = Realm::get_shared_realm(config);
    }
    catch (...) {
        translateSharedGroupOpenException(error);
        return nil;
    }

So it gets replaced in original cached Realm too on original thread. Then I get a crash on some other operation on that thread, because new scheduler says it is queue-confined.
@bmunkholm @jsflax what do you think? I am not a great c++ programmer, so it is just a theory

I rewrote our helpers to use the same queue to create Realm, fetch results and subscribe to notifications and crash is gone 🎉

[configuration copy] does a deep copy of the RLMRealmConfiguration object, so the assignments to config.scheduler below should only be modifying the newly created Realm::Config. However, I think I do see what the problem is; [RLMRealm realmWithConfiguration:realm.configuration error:nil] will incorrectly reuse the first Realm's scheduler.


⚠ Bofrost.at has degraded performance

In 02d7c55, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1155 ms

Resolved: Bofrost.at performance has improved in c9299d4 after 6 minutes.


Updating docs site for date and datetime-local input options

Congrats on the 1.0 launch!
I noticed the docs site was missing the input options added in https://github.com/allmarkedup/lookbook/pull/116
I'm adding the param options here

Thanks @jonrohan! And not sure how those input options didn't get copied across... must have pulled them from before the PR was merged. Appreciate you adding them back in again :-)


PDF to PNG

Support PNG image format
Currently the  extraction of images from a pdf lacks of png support. It's require a method to export png images in a pdf to an png image file.

This may be helpful
https://stackoverflow.com/questions/10024908/how-to-extract-flatedecoded-images-from-pdf-with-pdfsharp


Phantom repositories picking up builds and causing failures on Docker Cloud

We have a situation where a repository that doesn't exist, let's call it my_repo_2 is picking up builds for my_repo.
Since my_repo_2 doesn't actually exist, this causes a failure in linked Github projects.
The link github docker cloud link will show: https://cloud.docker.com/swarm/myorg/repository/docker/myorg/my_repo_2/general
You can access that link, but attempting to 'Edit repository' just takes you to the Docker Cloud onboarding screen.

ping @manishtomar

@mkubilus i'm sorry that you're having an issue with Docker Cloud. do you mind reaching out to our colleagues at<EMAIL_ADDRESS>with more details so that we can better assist you? thanks!

Thanks @jmwong for the comment. @dmp42 Please close this.


Testing- Process Page- Work with Us/ Funding

Process Page Guide

Self-Assign this ticket corresponding to a group of pages
Add your name to the owner in content sprint page to a group of pages. To see action pages only filter the qa task column.

Test away!
Work with us/Content/Writing Style Guide

[x]  Phone browser 1
[x]  Phone browser 2
[x]  Desktop browser 1
[x]  Desktop browser 2

Work with us/Content/Reviewer Guide

[x]  Phone browser 1
[x]  Phone browser 2
[x]  Desktop browser 1
[x]  Desktop browser 2

Work with us/Content/installation guide

[x]  Phone browser 1
[x]  Phone browser 2
[x]  Desktop browser 1
[x]  Desktop browser 2

Work with us/Content/Pallette

[x]  Phone browser 1
[x]  Phone browser 2
[x]  Desktop browser 1
[x]  Desktop browser 2

Work with us/Content/content-guide

[x]  Phone browser 1
[x]  Phone browser 2
[x]  Desktop browser 1
[x]  Desktop browser 2

Work with us/Content/Icons

[x]  Phone browser 1
[x]  Phone browser 2
[x]  Desktop browser 1
[x]  Desktop browser 2

Work with us/Content/Visual Style Guide

[ ]  Phone browser 1
[ ]  Phone browser 2
[ ]  Desktop browser 1
[ ]  Desktop browser 2

Work with us/Meetups/Getting Started Guide

[x]  Phone browser 1
[x]  Phone browser 2
[x]  Desktop browser 1
[x]  Desktop browser 2

Work with us/Meetups/Events Formats Guide

[x]  Phone browser 1
[x]  Phone browser 2
[x]  Desktop browser 1
[x]  Desktop browser 2

Work with us/Meetups/Promotion Guide

[x]  Phone browser 1
[x]  Phone browser 2
[x]  Desktop browser 1
[x]  Desktop browser 2

Work with us/Meetups/Budget Guide

[ ]  Phone browser 1
[ ]  Phone browser 2
[ ]  Desktop browser 1
[ ]  Desktop browser 2

Work with us/Hackathons/Guide to Hacking

[ ]  Phone browser 1
[ ]  Phone browser 2
[ ]  Desktop browser 1
[ ]  Desktop browser 2

Work with us/Governance and risk meetings/Take notes/Formatting guide

[ ]  Phone browser 1
[ ]  Phone browser 2
[ ]  Desktop browser 1
[ ]  Desktop browser 2

Work with us/Governance and risk meetings/Take notes/Governance call template

[ ]  Phone browser 1
[ ]  Phone browser 2
[ ]  Desktop browser 1
[ ]  Desktop browser 2

Funding/Development grants/grantee playbook

[ ]  Phone browser 1
[ ]  Phone browser 2
[ ]  Desktop browser 1
[ ]  Desktop browser 2

Work with us/Content/Reviewer Guide - Links are broken

Work with us/Content/installation guide - not finding a page named this in the spreadsheet.

Work with us/Content/Pallette not found, reviewed Resources/technical-content/Pallette - this page has several broken links which need to be updated.

Work with us/Content/content-guide not found, reviewed Resources/technical-content/content-guide -

Pre-Publication Checklist, styling feedback/suggestion: list is long with lots of space and no bullets, consider adding actual check boxes to specific tasks (so that its more clear what is an item vs a description of the item) or some other styling changes to improve readability.
Do's &  Don't, styling suggestion: consider putting these side by side in 2 columns for improving visual on desktop

Work with us/Content/Icons not found, reviewed Resources/technical-content/Icons -

no icons appear (in any browser)

Work with us/Meetups/Getting Started Guide

All links except feedback form ones are broken/incomplete
style suggestions: bullet lists have too much internal spacing, Planning list is very long and would benefit from bullets, numbers, or other markers

Work with us/Meetups/Events Formats Guide

styling suggestion, remove excess space within the bullet lists

under "Setting Up An Event Page" heading, styling suggestion: remove subbullets (maybe all bullets?) for this list, but keep the font weight. For example,
"Name A good name describes the theme, main topic, or general ethos of the talk."
-additional style suggestion: remove some spacing between bullets within other lists

Work with us/Meetups/Budget Guide in the spreadsheet links to Work with us/Meetups/Promotion Guide

Work with us/Hackathons/Guide to Hacking

community chat link is broken
Styling brackets under "Grants" heading are not functioning

Work with us/Governance and risk meetings/Take notes/Formatting guide

broken code under "Weekly Meeting" , "Password Protection" , "We Also Explore a Rage of Themes" Headings, example

under "What Happens" heading, styling suggestion: remove spacing between bullets within a list
under heading "Past Meetings" links are not functioning, styling suggestion: remove subbullets (maybe all bullets?), but keep type weight. For example, "Transcripts View transcripts of past meetings"

Work with us/Governance and risk meetings/Take notes/Governance call template

under the heading "Video", styling suggestion: consider putting a sample video that would appear here (?)

Funding/Development grants/grantee playbook

under heading "Social Media Presence", Twitter embed isn't functioning

The above comments will be updated after I review the pages in the correct space. Sorry for the confusion.

Work with us/Content/installation guide - not finding this


Add feedback and source section to about screen

Maybe I should add you as a moderator to /r/GetDank. What's your reddit username?

It's Thanel right?

Yes, that's correct.

Done!

@saket Also, do you still have old screenshots and description from the play store saved somewhere?

Yep. This folder has screenshots I used on Play Store as well as screenshots that show how the app shaped up over time: https://drive.google.com/open?id=1CswL6DQ8vNvqWc3fHuq7y6-PVSjZNlkJ


Export data into csv

As requested by tobyweston in the issue #24, I post here the point 1:
1/ Would be nice to have the possibility to export the data (tab.txt or csv).
Toby:
1/ I have something I've been using to debug things. It's on a branch but https://github.com/tobyweston/temperature-machine/blob/bf81f043d5fc2cc802b1ae9ee7760101c354eb90/src/test/scala/bad/robot/temperature/ConvertJsonToCsv.scala will create a CSV from JSON. If you can wait for a bit, I'll be merging it back to master and can make it usable / add it in properly. If not, you can hack about with it to get you started.

I could try the 'ConvertJsonToCsv.scala' but would  need some guidance to know how to run this file (I'm a newbie to Raspian and raspberry...). Thank you in advance.


feat(package): rename package to use @ibm-cloud scope

PR summary
Suggested by Phil Adams as part of SDK review:

change ibm-continuous-selivery package name to continuous-selivery, and
move it to @ibm-cloud organisation scope
update README according to the above changes
add migration section to README
bump version in readme to v0.3.0 to match the release that will be generated by this change

PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

Reference PR from platform-services: https://github.com/IBM/platform-services-node-sdk/pull/118

:tada: This PR is included in version 0.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Do not reject MGMT_ACTIVE_SET with TLVs affecting connectivity if not from commissioner

Only reject MGMT_ACTIVE_SET that includes TLVs affect connectivity
Do not store TLVs that affect connectivity after receiving MGMT_ACTIVE_SET

Here there are 2 places that are not compliant with spec.

Leader would store TLVs that affect connectivity in pending dataset if they are from thread device but not commissioner. But seems that current implementation is not suitable for it.
The commissioner would not include TLVs that affect connectivity (Register), how do we check the device is on-mesh commissioner, through commissioning session id? Seems not good. And device state does not design for representing 2 roles (commissioner and router)? Changing it to one bit represents on role, is it good enough?

Current coverage is 73.16% (diff: 87.50%)

Merging #803 into master will decrease coverage by 0.01%

@@             master       #803   diff @@
==========================================
  Files           107        107
  Lines         16033      16038     +5
  Methods        2183       2183
  Messages          0          0
  Branches       1910       1911     +1
==========================================
+ Hits          11734      11735     +1
+ Misses         3669       3667     -2
- Partials        630        636     +6

Powered by Codecov. Last update c28042c...3ae86e3

@lluwang, Section <IP_ADDRESS>.2 seems to indicate that messages from the Commissioner need to set the IPv6 Source Address to the Commissioner ALOC.  Maybe we can use that?

9.2.17-Orphaned End Device fails due to the same reason. Leader_1 will issue an MGMT_ACTIVE_SET message to itself with new Active Timestamp and Pan Id (this tlv will affect the connectivity), should move to Pending Operational Dataset instead of Reject.


ciao-cli: Improve template functionality

This PR adds two new functions to the template language understood
by ciao-cli:

tojson outputs the specified object in json format, e.g., {{tojson .}}

filter operates on an slice or array of structures.  It allows the caller
to filter the input array based on the value of a single field.
The function returns a slice containing only the objects that satisfy the
filter, e.g.
ciao-cli image list -f '{{$x := filter . "Protected" "true"}}{{len $x}}'
outputs the number of protected images maintained by the image service.

The image list command was also modified to called the template utility
functions in template.go.  This was necessary to ensure that our new
functions are available to the image list command.
Finally, a the createTemplate function was using the wrong name for the
templates it created.
Signed-off-by: Mark Ryan<EMAIL_ADDRESS>

Coverage increased (+0.05%) to 64.908% when pulling 96aeb64028aed764c597ce9ec259725d0a575450 on markdryan:master into cc089c2ca1e9adbf3b6a5150806f0a98f47597a1 on 01org:master.

Going to make a quick change to the way errors are handled.  Don't merge yet.

Coverage increased (+0.05%) to 64.908% when pulling 96aeb64028aed764c597ce9ec259725d0a575450 on markdryan:master into cc089c2ca1e9adbf3b6a5150806f0a98f47597a1 on 01org:master.

Coverage increased (+0.04%) to 64.892% when pulling 6c254bcb0d5c8e28503d9f333162453c2225d5f6 on markdryan:master into cc089c2ca1e9adbf3b6a5150806f0a98f47597a1 on 01org:master.

Should be good to go now.


Support for Mixtral with vLLM

Hi, I'm trying your quantized Mixtral and it's amazing!! Huge congrats! This is super useful!
I've been able to try it without vLLM but it seems it's not possible to load with vLLM yet. I guess adding this support is already in your backlog; I just wanted to point out that I'm looking forward to it, and thank you for this amazing work!
Best,
Haritz

Very happy to hear that @HaritzPuerto !
I think we will need to scratch everything we did for VLLM in this repo and either do a PR to directly integrate HQQ into the main VLLM repo or have a separate VLLM forked repo.


Tilemap color offset should still be loaded reguardless of a json file

Right now the tilemap color offset image isn't loaded if there is a json file. This should always happen since the color offset isn't part of the tile json file.

This has been fixed.


missing ../fonts/nucleo-icons.svg

../fonts/nucleo-icons.svg is referenced in /assets/css/paper-dashboard.css, but is missing in the repository and the currently available npm package (2.0.0).

@DennisNissen  some return?

@DennisNissen  thanks

Any update on this? Still missing on 2.0.0 and 2.0.1


Starter app not working, with error 'You must specify |clientID| for |GIDSignIn|'

Hello @morganchen12 and @ulukaya !
This is a continuation of https://github.com/firebase/friendlychat-web/issues/156.
I am doing the Firebase authentication tutorial here: https://codelabs.developers.google.com/codelabs/firebase-ios-swift/#4
I see the error:
FriendlyChatSwift[5221:437165] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'You must specify |clientID| for |GIDSignIn|'

I read the messages in #156 and inserted the code
func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
        FirebaseApp.configure();
        GIDSignIn.sharedInstance().clientID = FirebaseApp.app()?.options.clientID
        return true
    }

in the AppDelegate.swift file, but still see the error.
Would you know why?

Can you share your GoogleService-Info.plist file, with keys redacted?

@morganchen12 Yes! Please see:

Hi @morganchen12 and @ulukaya, please see above ^ !

@amchew can you upload your project in its current state to a git repo so I can poke around? There's nothing wrong with your GoogleService-Info.plist file.

@morganchen12 Yup! Here is the repo: https://github.com/amchew/friendlychat-ios

Hey @morganchen12 ! I ran pods update and ran my build again and still see the error:
FriendlyChatSwift[3285:112147] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'You must specify |clientID| for |GIDSignIn|' unfortunately.

It turns out this (probably) wasn't pods-related. There's a curly-brace error in your project, so your application(_:didFinishLaunchingWithOptions:) method isn't being called. Here's the diff to fix your code:
         print("Error \(error)")
         return
       }
+    }
   }

   func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplicationLaunchOptionsKey: Any]?) -> Bool {
     FirebaseApp.configure()
-    GIDSignIn.sharedInstance().clientID = FirebaseApp.app()?.options.clientID
-    //GIDSignIn.sharedInstance().delegate = self
     return true
   }
 }
-}

Running pod update doesn't actually update your pods because we set the project platform version to iOS 7, which is unnecessary. I'll fix that.
Thanks for reporting!


Breaking change introduced in v1.1.0

Hi buf team, with last week's release of v1.1.0 I believe a breaking change was introduced that has made our CI stop pushing to BSR. In particular:
if [ "${GITHUB_REF_TYPE}" != "branch" ]; then
  echo "reference type is not branch, skipping" >&2
  exit 0
fi

This is skipping for us, since in our workflow we don't push on branch, but for particularly formatted tags on master 🤔
In the interim, I've reverted our GHA workflow to specifically use v1.0.1 instead of v1 but of course we'd love to keep up with the latest changes.
My questions are:

Was this an intended breaking change?
Can we get a fix or an option to bypass the check?

Thanks!

Hi @KenxinKun! thanks for raising this, sorry we have disrupted you - this is never our intention. Give me a bit to triage this and get back to you with an answer.


CHEBI:141966 and CHEBI:146230, discrepancy in structures

Hi Adnan and Gareth,
I have just submitted CHEBI:146230 (−)-voacangine(1+), and I find a discrepancy in the structure compared to CHEBI:141966 that is the conjugated base. It is the chirality of one H bond that differs. I base my structure on two recent papers adn a ChEMBL molecule, and I must admit that I have not verified all the references linked to CHEBI:141966. I have linked the two compounds as they are both labeled (-).
Please help me figure out what is wrong and where,
Cheers,
Kristian

Hi,
I think you are right. I have corrected the structure of CHEBI:141966.


Attribute table widget gets out of sync with LocalLayer widget

This may not be the custom widget issue, maybe a general WAB-Dev (have not yet tested if I get same results). Problem occurs when using the GUI to modify attribute tables, and I believe is tied to having possibly too many tables, or secure tables?
When I start to modify fields to show on attribute table, on about the 6th attribute table in the list, pulls fields from a totally different table (first layer on list?).  Problem is repeatable.   Seems config file and attribute table displayed is correct.  More an issue on the GUI pulling in the data.
(See attached image) Table to modify is "Controlled-Use Areas", fields in edit window are from "UCU Codes" (first layer in list).  Several of the layers in the table will display the same incorrect fields.
\client\server\apps##\configs\AttributeTable\config_Attribute_Table.json  can be modified to be correct and app will reflect the changes, but AttributeTable edit dialog will still be incorrect.
Is this a LocalLayer/Attribute issue, or a WAB.  if WAB, I can start a tech incident. Posted here first, in case this is a known issue from the widget.

Have you seen this behavior?
Thanks

If this is the same issue that I've been seeing, I'm finding this to be somewhat of a WAB issue.  If you don't mind re-configuring your fields, in order to get the Attribute Table Widget to refresh, I believe you can go into the config.json file of your application, find the entry for the Attribute Table widget (It should look something like the json snippet below):
{
   "uri": "widgets/AttributeTable/Widget"
   ...
}

And remove the "config:<config_file.json>" line from this snippet, which should look something like
"config": "configs/AttributeTable/config_Attribute Table.json"

Then try re-configuring the Attribute Table widget in builder.  It should prompt a full refresh of your services and layers, though you'll need to reconfigure your fields again.


refactor: use Lua [[]] multiline string syntax

Just try to help you do some little chores.

Awesome, thank you! I'll likely merge this along with #8 later today, as there are some conflicting lines. string.format is definitely the right way to go here, I appreciate it :)

Nvm, will merge now and fix the conflict in the draft PR before I finish it 👍


Unable to see Matter devices & services option on Pixel 4a (Android 13)

I've followed the procedure described here:
https://developers.home.google.com/matter/verify-services
Basically I upgraded Google Services to the latest version and re-installed Google Home App.
Despite that, I don't see the
Matter devices & services option in Settings > Google > Devices & sharing
Any idea what to do please ?

Thanks for reporting this issue. Investigating...

Hmm, we had a few other reports of this issue, and re-installing the Google Home App solved the issue.
Which version of GHA is currently running on your phone?

My phone is running version <IP_ADDRESS> of GHA
Indeed, after uninstalling GHA and re-installing it, the Matter devices option appears in Settings > Google > Devices & sharing


Update .env.example

My discord keys are set a numeric values too. I'm not sure if we need this change.

My discord keys are set a numeric values too. I'm not sure if we need this change.

Thanks for the PR @AtulACleaver . These are numbers not strings, so the quotes are not required. I will close this (you still get the green squares 🟩 )

Thanks for the PR @AtulACleaver . These are numbers not strings, so the quotes are not required. I will close this (you still get the green squares 🟩 )


[Bug report][enhancement] sim.checkOutput() does not provide real output information

Describe the bug
Mismatch: model tut2 numSpikes is 400 but expected value is 931
Reproducing the bug
Steps to reproduce the behavior:

Download and Open 'tut2.py'
Run the example. It will work smoothly
Change netParams.stimSourceParams['bkg'] = {'type': 'NetStim', 'rate': 10, 'noise': 0.5} to netParams.stimSourceParams['bkg'] = {'type': 'NetStim', 'rate': 10, 'noise': 0}(i.e., change the noise)
Plots are generated but the error is raised

Expected behavior
I would expect that checkOutput would do a revision of my simulation parameters or something more insightful regarding the output, as the name suggests
System information

OS and version: macOS Catalina (macbook pro mid 2012)
NetPyNE version: <IP_ADDRESS>
NEURON version:  7.8.2 HEAD (09b151ec) 2020-12-16
Python version: 3.9.3

Additional context
Checking the implementation of sim.checkOutput('tut2'), it only serves for replicating the exact same experiment. It does not provide any more help, nor information regarding the simulation output.
I feel that this function does not provide enough information if one wants to test or play around with the tutorials, as this output (and for other tutorials) is fixed. Also, this behavior is not explained in the tutorial webpage

Hi @jpalma-espinosa , thanks for the bug report.  The function sim.checkOutput is only meant to be used internally by NetPyNE (for code testing/continuous integration).
I added a docstring to checkOutput and added a comment explaining its purpose to each tutorial and example where it was utilized.


Added alternative app.js with external support

See #6

Using async/await is not specific to this NPM package. You can use async/await with any function that returns a promise, as well as then/catch. It has nothing to do with this package, so there's no need to mention it in the Readme ;)

Could you therefore add it to all packages?
All of them might find it interesting.


Add reply sorting in-thread

Now that the header is always visible on all platforms, it seems like a nice place to put the sorting options.
The behavior is not perfect (e.g. it's a bit slower than I would have liked) but seems like we can ship and iterate.
Test Plan
https://github.com/user-attachments/assets/15424c68-9d71-44b2-9067-5401eb4e4a35
https://github.com/user-attachments/assets/3df43707-d3fd-4508-a3b0-b5914973c725

Pushed tree view setting as well.


next_code_type is always null

I want to use ResendAuthenticationCode but next_code_type is always null

next_type is defined by the server. If it is null, then all possibilities available for code sending are exhausted and client can't ask the server to resend the code.

Do I have other ways to request SMS?

No. The SMS was already sent, so user can enter the code after the SMS is received.

When my account is not registered, I can't receive the SMS. When my account is registered, I can receive the SMS.

Do you use TDLib 1.5.0?

yes

Then the answer from https://github.com/tdlib/td/issues/728 still applies.

I still have not received it<EMAIL_ADDRESS>did not reply to me

Could you collect TDLib log with verbosity level 4 and send it to @tdlib_bot in Telegram?

It can be a protection from automatic account registration and subsequent spam. You can write to<EMAIL_ADDRESS>your phone number and description of the problem, if you believe that this is an erroneous ban.


not all lanes of all platforms are listed when running fastlane

New Issue Checklist

[x] Updated fastlane to the latest version
[x]  I have read the Contribution Guidelines

Issue Description
Given multiple platforms in a fastfile, either only the ones from the default platform are presented to the user (if a default platform is defined)  or fastlane does not find any lanes (see output).
I use fastlane to manage cross platform builds, so having two platforms in the same fastfile is very useful.
'fastlane lanes' correctly lists all lanes, so doing something like the "--- Step: default_platform ---" step across platforms would be very nice.
Complete output when running fastlane, including the stack trace and command used
/Users/admin/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/user_interaction.rb:334: warning: constant ::TimeoutError is deprecated

Looking for related GitHub issues on fastlane/fastlane...

➡  Lanes table
   https://github.com/fastlane/fastlane/pull/4076 [closed] 6 💬
   08 Apr 2016

[!] It looks like you don't have any lanes to run just yet. Check out how to get started here: https://github.com/fastlane/fastlane 🚀

Configuration Files
Please copy the complete content of your Fastfile and any other configuration files you use below:
Fastfile:
platform :ios do
  desc "An iOS Lane"
  lane :laneForIOS do
  end
end

platform :android do
  desc "An Android Lane"
  lane :laneForAndroid do
  end
end

Environment
fastlane version (run fastlane -v):
fastlane 1.98.0
Do you use bundler to execute fastlane (i.e. bundle exec fastlane)?
yes
Do you use a Ruby environment manager (e.g. chruby, rbenv, rvm)?
rbenv

Hi @Lutzifer Thanks for reaching out. Can you share your full input and output? I want to take a look. Thanks!

you can simply take the fastfile and then run fastlane
I don't know what to add more, but will try.

Hi @Lutzifer Thanks for following up. Can you provide the full command you entered and all output of fastlane up to the error? Thanks!

Ok, i'll try to be more specific:
Case 1: Fastfile with default platform
Fastfile:
default_platform :ios

platform :ios do
  desc "An iOS Lane"
  lane :laneForIOS do
  end
end

platform :android do
  desc "An Android Lane"
  lane :laneForAndroid do
  end
end

Command and Output:
$  bundle exec fastlane
/Users/admin/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/user_interaction.rb:334: warning: constant ::TimeoutError is deprecated
[22:51:49]: ------------------------------
[22:51:49]: --- Step: default_platform ---
[22:51:49]: ------------------------------
[22:51:49]: Welcome to fastlane! Here's what your app is setup to do:
+--------+----------------+------------------------------+
|                 Available lanes to run                 |
+--------+----------------+------------------------------+
| Number | Lane Name      | Description                  |
+--------+----------------+------------------------------+
| 1      | ios laneForIOS | An iOS Lane                  |
| 0      | cancel         | No selection, exit fastlane! |
+--------+----------------+------------------------------+
Which number would you like run?

Case 2: Fastfile without default platform
Fastfile:
platform :ios do
  desc "An iOS Lane"
  lane :laneForIOS do
  end
end

platform :android do
  desc "An Android Lane"
  lane :laneForAndroid do
  end
end

Actual Command and Output:
$  bundle exec fastlane
/Users/admin/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/user_interaction.rb:334: warning: constant ::TimeoutError is deprecated

Looking for related GitHub issues on fastlane/fastlane...

➡  not all lanes of all platforms are listed when running fastlane
   https://github.com/fastlane/fastlane/issues/5437 [open] 3 💬
   2 hours ago

➡  Lanes table
   https://github.com/fastlane/fastlane/pull/4076 [closed] 6 💬
   08 Apr 2016

[!] It looks like you don't have any lanes to run just yet. Check out how to get started here: https://github.com/fastlane/fastlane 🚀

Expected/More useful output:
$  bundle exec fastlane
/Users/admin/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/gems/commander-4.3.5/lib/commander/user_interaction.rb:334: warning: constant ::TimeoutError is deprecated
[22:51:49]: ------------------------------
[22:51:49]: --- Step: default_platform ---
[22:51:49]: ------------------------------
[22:51:49]: Welcome to fastlane! Here's what your app is setup to do:
+--------+----------------+------------------------------+
|                 Available lanes to run                 |
+--------+----------------+------------------------------+
| Number | Lane Name      | Description                  |
+--------+----------------+------------------------------+
| 1      | ios laneForIOS | An iOS Lane                  |
| 2      | android laneForAndroid | An Android Lane                  |
| 0      | cancel         | No selection, exit fastlane! |
+--------+----------------+------------------------------+
Which number would you like run?

I'm seeing the same thing and would also like to see all available lanes when executing fastlane.
This is my output, when I comment out default_platform:
$ fastlane
[09:44:05]: -------------------------------------------------
[09:44:05]: --- Step: Verifying required fastlane version ---
[09:44:05]: -------------------------------------------------
[09:44:05]: fastlane version valid

[!] It looks like you don't have any lanes to run just yet. Check out how to get started here: https://github.com/fastlane/fastlane �

@stovmascript Thanks for following up. Does fastlane lanes provide the correct output? I'm marking this to see if someone from the community is interested in submitting a PR.

Yup, that's what I'm currently using to get an overview of all available
lanes.
On Sep 13, 2016 8:40 PM, "Todd Burner"<EMAIL_ADDRESS>wrote:

@stovmascript https://github.com/stovmascript Thanks for following up.
Does fastlane lanes provide the correct output? I'm marking this to see
if someone from the community is interested in submitting a PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fastlane/fastlane/issues/5437#issuecomment-246780594,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANmiEpbxwUDAXrlOyAZLXssuugyDXLfKks5qpu4QgaJpZM4JPniv
.

@stovmascript Thanks! The common usage command is fastlane lanes, but since we have the behavior for running just fastlane it should work there. I think we'd love to see a community PR! Thanks for pointing this out, hope you have a great day!


FR: allow users to update their own email addresses.

I don't see a way for a user to update their own email address in 0.9.22.

Fixed in v1.2.3


Add a lexer for Schemas for Minecraft Add-ons and 4 examples

Schema is a formal language for the game Minecraft official staff and docs to show data file structures and interface formats, and also for Minecraft Add-ons creators to communicate or teach with each other.
Reference: https://learn.microsoft.com/en-us/minecraft/creator/reference/content/schemasreference/
Community usage example: https://www.mcbe-dev.net/addons/data-driven/manifest.html
This lexer is summarized from official and some community examples for maximum coverage.
Four examples are provided for lexer tests.

Quick look: Please run pytest --update-goldens to add golden test output, and I think the name is a tad too generic, can you please rename the lexer to MinecraftSchemaLexer or something because I doubt that this is the only language ever that will claim the schema name.

Please make it clear that this is Minecraft related, i.e. call the file minecraft.py, the lexer name 'Minecraft Schema', the alias 'minecraft-schema', the class 'MinecraftSchemaLexer' etc.

Oops, I duplicated @Anteru 's request, never mind.

Please make it clear that this is Minecraft related, i.e. call the file minecraft.py, the lexer name 'Minecraft Schema', the alias 'minecraft-schema', the class 'MinecraftSchemaLexer' etc.

Thanks for your suggestion, but I see that there exist MCFunctionLexer and SNBTLexer in mcfunction.py. Is it better to merge them into one file and name it minecraft.py, or just like my changes - simply renaming Schema to MCSchema?

I'd prefer all Minecraft-related lexers to move into a single minecraft.py file. You can create a separate PR for that if you want or keep it in this PR if that's easier for you.

I'd prefer all Minecraft-related lexers to move into a single minecraft.py file. You can create a separate PR for that if you want or keep it in this PR if that's easier for you.

Thanks, I'll repull a request for that. Btw, I see the git action failed but have some difficulty understanding the reason. If you were convenient to have a look?


PX4Flow to Pixhawk configurations to get stable LPE

Dear all,
I am working on indoor small drone where GPS is not allowed. I have followed the tutorials on Px4 documentations in connecting the PX4Flow to Pixhawk. Here is what I have done:

From list of options for Firmware in QGC, I flashed Pixhawk using Master in QGC.
I downloaded github directory containing Px4Flow files: https://github.com/PX4/Flow
I flashed the downloaded files and flashed it using this instructions: https://pixhawk.org/dev/px4flow
I connected Px4Flow to Pixhawk as follows:

I noticed that the SENS_FLOW_ROT is set to 270 degrees in QGC but the documentation says make it 0 degrees based on this:

So I set the SENS_FLOW_ROT to 0 degrees using the documentation

I set the SYS_MC_EST_GROUP to EKF2 and the POS_CTRL mode was bad. It did not stay hovering.

I would like to tried LPE with the community suggestion. I did not have stable hover before, but since I have just flashed these codes for Pixhawk and Px4Flow using masters I feel that I am doing that part correct. @andre-nguyen @ChristophTobler suggested me to check for orientation. Could someone assist me with getting this setup to work using LPE in POS_CTRL mode. I would really appreciate if I could get a stable hover like so: https://www.youtube.com/watch?v=CccoyyX-xtE
Thank you

https://pixhawk.org/dev/px4flow is outdated and I guess we need to remove that page or link it correctly. We are sorry for that.
Please make sure you have the following things working correctly

As we have already told you on Gitter, SENS_FLOW_ROT needs to be 270 degrees if you use master.
Flow output: fwd +y, rev -y, right -x, left +x
Is your quad tuned correctly?
Does the distance sensor work?
Does altitude hold work?
What is your flow quality?
Is optical flow enabled in LPE_FUSION?
If you use EKF2, have you set EKF2_AID_MASK to use optical flow?
If you use EKF2, have you set EKF2_HGT_MODE to use the range finder?

And please provide a log of a flight.

Have a look at this guide

@ChristophTobler Lets move everything into Devguide and update the Optical Flow page to reflect latest LPE params.
https://dev.px4.io/optical-flow-outdoors.html is outdated in terms of LPE params.

@mhkabir I agree. I guess it is also a bit confusing that we have two pages in the dev guide: https://dev.px4.io/flow_lidar_setup.html, https://dev.px4.io/optical-flow-outdoors.html. I think we should just have one page for optical flow with all estimators on there.
I'll create one with EKF2 (and maybe INAV with the warning that it is outdated). Can you then add the LPE part?

Based on the suggestions, I have reset all params and recalibrate the Pixhawk in QGC:

[ ]  SENS_FLOW_ROT needs to be 270
Complete

[ ] Flow output: fwd +y, rev -y, right -x, left +x, Does the distance sensor work?
M1:OPTICAL_FLOW_RAD.integrated_y, M1:OPTICAL_FLOW_RAD.integrated_x, and  M1:OPTICAL_FLOW_RAD.distance
Complete
https://www.youtube.com/watch?v=11pUv1R0G-M&feature=youtu.be
Is your quad tuned correctly?

Does altitude hold work?
What is your flow quality?
Is optical flow enabled in LPE_FUSION?
If you use EKF2, have you set EKF2_AID_MASK to use optical flow?
If you use EKF2, have you set EKF2_HGT_MODE to use the range finder?

Is LPE still the recommended position estimator to be used with PX4FLOW?
Is there a list of the LPE parameters to be used with PX4FLOW?

@jgoppert @mhkabir @ChristophTobler , what are your suggestions?

You have to tune your quad obviously. Otherwise it won't fly (well) at all. Have you ever flown it manually?

@ChristophTobler, I have flown it many times. We had drift issues in manual flights.

Then please provide a log here: http://logs.uaventure.com/

@tomatac Yes, LPE is still the recommended one. @mhkabir is updating the parameters here https://github.com/PX4/Devguide/pull/98

@ChristophTobler Here is what I'll do:
1st flight: Manual flight and control the quad using only the RC Transmitter. Log it
2nd flight: Altitude hold mode flight and log it as well.

Also send a log for position control please; I want to see what goes wrong.

I'll do that. Thanks

@vinhk I just realized that your pixhawk is running ekf2 (default). That's also why you can't see LPE_FUSION but all EKF2_* parameters, right?
@mhkabir I guess we need to mention that in the dev guide (flow related, but also generally).

@ChristophTobler, I do see all of EK2_* parameters.

@mhkabir @ChristophTobler Even after I change it to LPE, there is no LPE_FUSION in QGC.

@vinhk yes. LPE is not supported on a Pixhawk

It is usable just fine. You need to use the px4fmu-v2_lpe target, because we do not have enough flash for both estimators on the Pixhawk with old STM32.

@mhkbir does that mean that I need to flash the px4 firmware masters from GitHub or from QGC masters?

@vinhk you would need to flash it yourself using the source code from Github. Or you could just use EKF2

@ChristophTobler I'll flashed it using Github this time. Please give me all the parameters to enable in QGC so I can test it properly for EKF2 to work with Pixhawk using Px4Flow.

@vinhk You flashed it using make px4fmu-v2_lpe (LPE) or make px4fmu-v2_default (EKF2)? For EKF2 you need to set the two parameters I mentioned https://github.com/PX4/Firmware/issues/6864#issuecomment-288001037

@ChristophTobler Previously, I used QGC. Instead of using the default firmware, I used Masters from the list of Px4 firmware.

@mhkabir Please give me all parameters I need to set in QGC if I flashed the firmware using make px4fmu-v2_lpe as well.

px4fmu-v2_lpe is in the zip file on the github release page.

@jgoppert I just flashed Px4 firmware masters from Github and use make px4fmu-v2_lpe upload. I can see LPE_FUSION 247 on QGC.  I also set SYS_MC_EST_GROUP to local_position_estimator, attitude_estimator_q on QGC. What is the next step?

is LPE_FUSION 247 correct to use PX4Flow without Lidar only sonar that came with Px4Flow indoors?

LPE_FUSION should be 162
On 23-Mar-2017 9:48 PM, "Vinh K"<EMAIL_ADDRESS>wrote:

is LPE_FUSION 247 correct to use PX4Flow without Lidar only sonar that
came with Px4Flow indoors?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PX4/Firmware/issues/6864#issuecomment-288774015, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFTNrDc1OsdHGFoRwz5BQPASEHe6oBdyks5roptdgaJpZM4MjBPy
.

@mhkabir I'll do that.

@mhkabir
162: 1010 0010
OFF bit 0 fuse GPS, requires GPS for alt. init
ON  bit 1 fuse optical flow
OFF bit 2 fuse vision position
OFF bit 3 fuse vision yaw
OFF bit 4 fuse land detector
ON  bit 5 pub agl as lpos down
OFF bit 6 flow gyro compensation
ON  bit 7 fuse baro
Why is the flow gyro compensation OFF?
Do you know if there is any document or post that explains the best practices on setting these parameters?

@tomatac You have that opposite. 1010 0010. It start from: GPS, Optical Flow, Vision Position, ... etc.
In this case flow gyro is on based on the 1010 0010

Did you try using QGC?

Thank you @dagar! I will try using the QGC now that I know that we need a different firmware file (px4fmu-v2_lpe in the zip file on the github).
The question remains: what are best practices on setting these parameters for position estimation using only PX4FLOW and no GPS?
If the Default is: 247: 1111 0111
ON  bit 0 fuse GPS, requires GPS for alt. init
ON  bit 1 fuse optical flow
ON  bit 2 fuse vision position
OFF bit 3 fuse vision yaw
ON  bit 4 fuse land detector
ON  bit 5 pub agl as lpos down
ON  bit 6 flow gyro compensation
ON  bit 7 fuse baro
Are these the best settings: 242: 1111 0010 ?
OFF bit 0 fuse GPS, requires GPS for alt. init
ON  bit 1 fuse optical flow
OFF bit 2 fuse vision position (?)
OFF bit 3 fuse vision yaw (?)
ON  bit 4 fuse land detector (?)
ON  bit 5 pub agl as lpos down
ON  bit 6 flow gyro compensation
ON  bit 7 fuse baro (?)
I am not sure on: fuse vision position, fuse vision yaw, fuse land detector, fuse baro.
Does anybody have a recommendation based on flight experience using only PX4FLOW and no GPS?

I use EKF2 and I Set SENS_FLOW_ROT to 270 degrees ，EKF2_AID_MASK to use optical flow ，EKF2_HGT_MODE to use the range finder，and the Alttitude and Position mode is working well, but I use make px4fmu-v2_lpe upload,i can't make the alttitude mode hold ,what's the problem with LPE?

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


Support for Linux and Windows platform

Platforms
Windows, Linux
Description
Two major plaforms are missing the implementation of compressing image via Uint8List or actual file. Image.memory() isn't efficient in dealing with larger number of Uint8List data and has a larger memory footprint on the app as we add more Uint8List data in the runtime.
Why
There are many windows flutter dev facing the same issue when dealing with image data efficiently, Adding support to Windows and Linux would complete the impl for all major OS helping the application serve a wider audience.

Will be awesome to have this feature

actually so I created simple_native_image_compress so that you just send the path string and gets image as Uint8List in return and it also supports both Windows and Linux

actually so I created simple_native_image_compress so that you just send the path string and gets image as Uint8List in return and it also supports both Windows and Linux.

@hwkim1127  I tried to use your packages but got this. Can you help me how I can fix this
[        ]   SEVERE : Cargokit BuildTool failed with error : [C:\work\flutter\androp\build\windows\x64\plugins\simple_native_image_compress\simple_native_image_compress_cargokit.vcxproj] [        ]   C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for 'C:\work\flutter\androp\build\windows\x64\CMakeFiles\d2cadfdd70b453df3c30d8e1388e44e4\native_image_compress.dll.rule;C:\work\flutter\androp\build\windows\x64\CMakeFiles\e6a54e3983 6c32c0b6f5f3d9c57e0960\simple_native_image_compress_cargokit.rule' exited with code -1. [C:\work\flutter\androp\build\windows\x64\plugins\simple_native_image_compress\simple_native_image_compress_cargokit.vcxproj]

actually so I created simple_native_image_compress so that you just send the path string and gets image as Uint8List in return and it also supports both Windows and Linux.

@hwkim1127 I tried to use your packages but got this. Can you help me how I can fix this
[ ] SEVERE : Cargokit BuildTool failed with error : [C:\work\flutter\androp\build\windows\x64\plugins\simple_native_image_compress\simple_native_image_compress_cargokit.vcxproj] [ ] C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for 'C:\work\flutter\androp\build\windows\x64\CMakeFiles\d2cadfdd70b453df3c30d8e1388e44e4\native_image_compress.dll.rule;C:\work\flutter\androp\build\windows\x64\CMakeFiles\e6a54e3983 6c32c0b6f5f3d9c57e0960\simple_native_image_compress_cargokit.rule' exited with code -1. [C:\work\flutter\androp\build\windows\x64\plugins\simple_native_image_compress\simple_native_image_compress_cargokit.vcxproj]

did you install rust? I actually updated the README so that you can setup the requirements


Backport: services via gateway, minus API changes

This is a halfway step to #5557 that hoists over its internal changes while keeping the existing API unchanged.

@marcosnils @sipsma Unfortunately this doesn't resolve the Cloud issue with services showing as failed. Now they show as running, which is maybe 1% better and even technically correct (explained below), but it's still not what we want. I have an idea in mind but it'll require a small tweak to every SDK.
It doesn't work because services stop asynchronously. The client disconnects, which will stop them all via plain old ctx cancellation, but since the client has already disconnected it can't receive any more progress. So the client can never see a Completed status for services as long as their stopping is triggered by disconnecting.
What I have in mind is to add some kind of Query { close: Void! } (strawman) API that clients call just before closing, which will release all of the client's background resources and wait. In this case, that would mean stopping all services and emitting Completed statuses along the way. Any thoughts (including "ew no")?
It's a bit unusual, and is another subtle thing each SDK would have to remember to implement. Are there any other scenarios where this API would come in useful?
Another option could be to implement some sort of internal shutdown protocol, but there'd still need to be a clear and obvious way for that to be invoked by clients backed by all connection types.
Yet another option could be to leave this as-is but add some sort of metadata on the vertex that Cloud detects in order to recognize "oh, this is a service, so I know that it was just left running in the background." The upside here is that SDKs don't have to change, and closing can still be async, likely allowing for snappier DX. Fixing this in Cloud kind of defeats the purpose of this PR though, since a similar workaround could probably be implemented without it, and these changes are already included in #5557.

Went with above API for max async, but still open to other ideas. Just want to have something ready to release if we want it. Marked the API "Experimental" so we can change or remove it whenever. Took a swing at Go, Elixir (@wingyplus :bow:), and NodeJS implementations. Could use help with Rust and Python.

Confirmed that the above change resolves the issue: this build shows its two services as completed. The user code just needs to close the client, which it should be doing already, and the SDK's close() needs to call Stop.
I went with a configurable timeout just to make it easier for SDKs to implement. I've set it to 10 seconds in the SDKs I've updated so far.

SDK implementation status for the above Query { stop } API:

[x] Go
[x] NodeJS
[x] Elixir
[x] Python
[ ] Rust
[ ] Dotnet
[ ] Java?

Really just guessing my way through most of these to get a head start. Requesting reviews now.

Sorry @vito, I should have given an heads up that I spent a bit of time today taking care of the Python bit. I'll replace it in a minute.

@helderco All good, feel free to replace it! :pray:

@vito re various SDKs:

Dotnet is the most experimental one, nothing to do there
Java is yet to be merged - https://github.com/dagger/dagger/pull/5504 - nothing to do there (blocked on me)
Rust is something that @kjuulh can help with post-merge, no need to block

The reverts were from a GUI, weren't signed-off, I'm going to force push to fix.

Yep, I will handle the follow up inconsistencies for rust, if the tests don't complain that is.

@vito what should be the behavior in dagger run and in Zenith? Should the SDK call stop in both cases?

@helderco That's a good question. It seems that we should only call stop when we know the ClientID is going away for good. Otherwise you might end up stopping the services started by a separate client in the same session, before they're actually done being used.  If we naively call stop in this case, one concurrent client would stop all the other client's services.
So with that rule, it seems most correct to not call stop in the DAGGER_SESSION_PORT case, because you can't be sure that the session is completed.
For Zenith/Dagger-in-Dagger, we can work with the above constraint by having it automatically do the equivalent of the stop API in the same place where the session is created (the shim).
In that case I think the current Go, NodeJS, and Elixir SDKs implementations are not right as they will unconditionally stop no matter what the internal connection type is.
Thinking about it more, if we're now saying this only needs to happen only in the case where a dagger session is spawned, I wonder if we can just handle it there, without adding a whole new API? Basically the client closing would send a signal to the process somehow, which would trigger all the stopping, and we'd wait for that to complete, which should be roughly already what's happening. I'm pretty sure I looked into this already, but I don't remember why I backed out. :sweat_smile: Looking into it now.

Pushed a prospective switch to a new internal HTTP endpoint, /shutdown, which gets called on (engine/client.Client).Close. I'm on shoddy internet, so relying on CI to tell me if it works. :sweat_smile: I reverted all the sdk/ changes, but they're still in the history if you want to salvage any part of your changes @helderco (it looked like part of that was refactoring)

Yeah, I'll keep all of it except for just the stop call but I'll do it in another PR. 😁

@TomChv Thanks for taking a look! SDKs no longer need updating - I'll minimize those comments to avoid confusion.
This PR is ready for review + testing, but I'm going to add some unit tests for the extra-tricky service lifecycle synchronization since @sipsma noticed some bugs there. They're theoretically fixed now, but I would like to have higher confidence in it.

Fully ready now! Backfilled unit tests for the tricky service lifecycle and did some follow-up cleanups.

LGTM from the integration testing perspective.

I tested this on Go, Python, Node.js SDKs using the examples/sdk/*/db-service example with an engine from this PR brought up with ./hack/dev compared to the v0.8.4 engine.
In each case I got the old undesirable "running" behavior from v0.8.4 and the desired behavior from this PR build.
I ran some unrelated things for good measure. Looks good!
Node.js

Golang

Python

@TomChv any blocker to you giving this the 👍


Expose verkey rotation

Signed-off-by: Miroslav Kovar<EMAIL_ADDRESS>

Codecov Report

Merging #478 (3d428c2) into main (7e731f5) will decrease coverage by 0.04%.
The diff coverage is 32.50%.

@@            Coverage Diff             @@
##             main     #478      +/-   ##
==========================================
- Coverage   56.03%   55.98%   -0.05%
==========================================
  Files         155      155
  Lines       14699    14744      +45
  Branches     4173     4194      +21
==========================================
+ Hits         8237     8255      +18
+ Misses       2218     2215       -3
- Partials     4244     4274      +30

Flag
Coverage Δ

integration-aries-vcx
42.64% <32.50%> (-0.03%)
:arrow_down:

unittests-agency-client
26.47% <ø> (ø)

unittests-aries-vcx
49.56% <0.00%> (-0.04%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

aries_vcx/src/libindy/utils/signus.rs
38.29% <32.43%> (-28.37%)
:arrow_down:

aries_vcx/src/libindy/utils/ledger.rs
28.78% <33.33%> (+0.77%)
:arrow_up:

...vcx/src/protocols/issuance/issuer/state_machine.rs
65.57% <0.00%> (+0.34%)
: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 7e731f5...3d428c2. Read the comment docs.


Gibbon doesn't work with Faraday 2.x

Hi Gibbon maintainers!
In my last Gem update I accidentally bumped Faraday to 2.x because Gibbon's version constraint is >= 1.0.
Unfortunately, this breaking change in Faraday 2.x doesn't work for Gibbon because it uses the conn.request :basic_auth syntax. The error I get when trying to call #upsert is:
/app/vendor/bundle/ruby/3.0.0/gems/gibbon-3.4.2/lib/gibbon/api_request.rb:134:in `handle_error': :basic_auth is not registered on Faraday::Request @title=nil, @detail=nil, @body=nil, @raw_body=nil, @status_code=nil (Gibbon::MailChimpError)
/app/vendor/bundle/ruby/3.0.0/gems/faraday-2.1.0/lib/faraday/middleware_registry.rb:57:in `lookup_middleware': :basic_auth is not registered on Faraday::Request (Faraday::Error)

Putting gem 'faraday', '~> 1.8' in my Gemfile works for now but others may have the same issue.
Thanks for looking at it!

Hi @pedantic-git, thanks for the heads up. Will investigate soon. There is a closed issue for 3.4.1 you might read for context, but it won't help your situation.

My apologies -- someone recently merged a PR to address this, but as I was on holiday I did not release an updated build. I'll do so now. https://github.com/amro/gibbon/pull/318

Thanks again for the bug report. Please try Gibbon 3.4.3, which should address your concern

Thank you! Sorry for not checking if there were already closed issues before reporting - it was late!


[feat][tiered-storage] ADD offload_time_threshold policy

Fixes https://github.com/apache/pulsar/issues/17361
Motivation
Add auto trigger offload by time policy.
Documentation
Check the box below or label this PR directly.
Need to update docs?

[x] doc-required
(Your PR needs to update docs and you will update later)

[ ] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

@hangc0276 @codelipenghui PTAL

@tjiuming Please also help open new issue to track the feature support on namespace/topic level policy, thanks.

@codelipenghui @zymap PTAL

/pulsarbot run-failure-checks

@codelipenghui @zymap PTAL

@codelipenghui @zymap please help review again

@tjiuming Please check the check-style issue

Great Job @tjiuming

Hi @tjiuming, besides configurations (already included in this PR), did you plan to add more information to Pulsar docs about this feature?

Hi @tjiuming, besides configurations (already included in this PR), did you plan to add more information to Pulsar docs about this feature?

@momo-jun I'll open a doc PR after the issue fixed and RestAPI CLI PR merged


fix(region): private cloud sku create

这个 PR 实现什么功能/修复什么问题:

[x] 功能、bugfix描述
[x] 冒烟测试
[ ] 单元测试编写

是否需要 backport 到之前的 release 分支:

release/3.6

/area region
/cc @zexi

Codecov Report

Merging #9593 (3d757e2) into master (159c1bc) will increase coverage by 10.59%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #9593       +/-   ##
===========================================
+ Coverage    5.90%   16.50%   +10.59%
===========================================
  Files         843       87      -756
  Lines      130900     9120   -121780
===========================================
- Hits         7736     1505     -6231
+ Misses     122463     7483   -114980
+ Partials      701      132      -569

Flag
Coverage Δ

aFlag
16.50% <ø> (+10.59%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/util/ansible/playbook.go

pkg/compute/models/schedtags.go

pkg/cloudcommon/policy/policy.go

pkg/monitor/alerting/rule.go

pkg/cloudcommon/db/quotas/register.go

pkg/baremetal/tasks/reprepare.go

pkg/compute/models/hostdrivers.go

pkg/compute/models/zoneresource.go

pkg/mcclient/options/dns_trafficpolicy.go

...kg/monitor/tsdb/driver/influxdb/response_parser.go

... and 741 more

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 159c1bc...3d757e2. Read the comment docs.

/lgtm
/approve


Vue.version

Vue.version update to 1.0.9

Thanks for the PR - this has been fixed as part of the build script updates.


Flickering after special language switch

As one of the translators for Noto I'm probably much more often switching languages than most of the normal users, and I only found this by accident, but as this here is one of the less pleasant situations to encounter:
After returning from English to one's own language by selecting Follow System, Noto flickers wildly — same like we've had already one year ago, back then triggered by rotating the device — while it is constantly switching between English and German at quarter second intervals, rendering Noto unusable for the moment. This can only be stopped by swiping it out of the app switcher.
For replicating this, it is necessary to leave the settings after choosing a particular language. Only then return to the languages section and choose Follow System.
Switching by selecting a language explicitly doesn't have this effect, only by choosing Follow System.
You can see another, shorter flickering on every 2nd(! Yup!) switching to other languages, although less aggressive and only flickering 2-3 times.

I'm very familiar with this bug, and it's been happening for a while. However, I couldn't find a right way to fix it yet, which made me to ignore it for now, since there's a workaround.

Good news, a fix will be applied, and be in the next release!

Yess, stable!!


Add Context in Router

When I put the context together with all authenticated routes and the screen goes white.

@Feeh03114 please, can you provide a repo with a minimal example simulating the error?

@Feeh03114 you can take a look at the official react router dom example where the provider is used in the element prop, so you can't use it at the same level of a Route, because router dom needs a route, otherwise you get the
Error: [AppProvider] is not a <Route> component.
All component children of <Routes> must be a <Route> or <React.Fragment>

error!
Example of right usage:
<Route
  path="/"
  element={
    <SomeProvider>
      <SomePage />
    </SomeProvider>
  }
/>

or you can pass the Router as children of your Provider:
<SomeProvider>
  <Router
    main={
      <Route
        path="/"
        element={<SomePage />}
      />
    }
  />
</SomeProvider>


Improve article cond-mat/0505185

Exact location of issue
A link https://arxiv.org/abs/cond-mat/0505185 is to the source article, point to the hash: S3.T2.12.
Problem details
A clear and concise description of what the bug is.

Wrong table displayed.

Desktop (please complete the following information)

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36

(Optional) Screenshots

Thank you for the report!
Two ways to see this problem:

LaTeXML tries to follow the low-level visual display of the printed page, and adds transform directives that rotate the table for a landscape page. However, it gets the height wrong, so the table collides with the nearby text.

This perspective (and checking whether the interplay with flexbox figures is correct) needs latexml development to be resolved.

Landscape pages don't really transfer to the ar5iv viewer application, and shouldn't be preserved from the source.

This perspective is usually easy to enforce via CSS rules, and I think I ought to be able to also cover this case - some transforms are already disabled in ar5iv-css.

Resolved with the latest CSS update. Here is a link to the Table 2 in question:
https://ar5iv.labs.arxiv.org/html/cond-mat/0505185#S3.T2
Thank you for the report @CreatorZZY !


Display thumbnails for published teacher network documents

This PR displays the published document thumbnails for the documents in each class that appears in the My Classes and My Network sections in the left panel.  Changes include:

show thumbs for published personal and problem docs in teacher network

PT Stories:
https://www.pivotaltracker.com/story/show/178762452
Deployed branch for testing:
https://collaborative-learning.concord.org/branch/add-network-published-thumbs/?demo

@kswenson changes look good!  Documents are loading!


Attributes don't display on a dedicated client

My guess is that attribute data (AttributeDataLoader) isn't synced to the client, so no attributes display on tooltips. Not sure how I'd like to fix this yet.

still not fixed sadly(

I've started a fix in 1.1.0 beta (GitHub, CurseForge). This should mostly work, but it was a huge update, so I expect things to break.


feat: support bitwise and boolean aggregate functions

Which issue does this PR close?
Closes #6275
Rationale for this change

What changes are included in this PR?

Are these changes tested?
Yes

Are there any user-facing changes?
Yes

Thanks @izveigor  -- I will try and review this PR in the next day or two


Occasional "broken pipe" error in ember server

Occasionally, I am getting following error when running wrk on http4s server with ember backend
java.io.IOException: Broken pipe
	at java.base/sun.nio.ch.FileDispatcherImpl.write0(Native Method)
	at java.base/sun.nio.ch.SocketDispatcher.write(Unknown Source)
	at java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source)
	at java.base/sun.nio.ch.IOUtil.write(Unknown Source)
	at java.base/sun.nio.ch.IOUtil.write(Unknown Source)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishWrite(Unknown Source)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(Unknown Source)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(Unknown Source)
	at java.base/sun.nio.ch.EPollPort$EventHandlerTask.run(Unknown Source)
	at java.base/sun.nio.ch.AsynchronousChannelGroupImpl$1.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)
	at delay @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.$anonfun$write$1(SocketPlatform.scala:137)
	at async @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.go$2(SocketPlatform.scala:131)
	at flatMap @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.go$2(SocketPlatform.scala:141)
	at modify @ fs2.internal.Scope.close(Scope.scala:262)
	at flatMap @ fs2.Compiler$Target.flatMap(Compiler.scala:162)
	at deferred @ fs2.concurrent.Topic$.apply(Topic.scala:144)
	at acquire @ fs2.Stream.go$11(Stream.scala:1922)

Setup:

Scala 2.13.8
Cats Effect 3.3.8
Fs2 3.2.5
Http4s 0.23.11

Mentioned error is not logged by logger and is thrown time to time (seems randomly). I wonder what could have caused it? Setup of process running wrk is as follows, wrk opens one connection to http4s server, and 100 instances of wrk script are run in parallel on same linux container. Each wrk process connects to different url path on same server.

I have the same issue. For me it happens when my scala-js frontend creates a <video> tag with its src pointing to a static url that is handled by http4s.
I created the endpoint like this...
  val httpApp: Kleisli[IO, Request[IO], Response[IO]] =
    Router(
      "api"    -> apiService,
      "assets" -> Logger.httpRoutes(logHeaders = true, logBody = false)(
        fileService[IO]("assets")),
      ),
    ).orNotFound

...and the embedded video like this.
<video src="http://localhost:8080/assets/recordings/week%201/02%20Supervised%20learning%20part%201/index.mp4#t=63"
  controls="true"
  type="video/mp4"
  style="width: 90%;">
</video>

These are the two requests and below are the errors.
I noticed that those errors are written directly to stderr and are not captured by logback.
Fun fact - I tried to reproduce the log-to-stderr behavior in a minimal-project and there the error is silently handled. I have no idea why.
I'm able to capture the error like this, but I couldn't find a way to silence it without redirecting stderr to /dev/null. It's a bit annoying, since the log shows plenty of errors but everything works fine and the browser doesn't show any error.
      .withErrorHandler { case th: Throwable =>
        logger.error(th)("Error") *> InternalServerError("Houston, we have a problem " + th.getMessage)
      }

Does anyone have an idea what causes the app to log to stderr (and doesn't in another app that's almost identical)?
[io-compute-2] INFO  o.h.s.m.Logger - HTTP/1.1 GET /assets/recordings/week%201/02%20Supervised%20learning%20part%201/index.mp4 Headers(Host: localhost:8080, Connection: keep-alive, Pragma: no-cache, Cache-Control: no-cache, sec-ch-ua: ".Not/A)Brand";v="99", "Google Chrome";v="103", "Chromium";v="103", Accept-Encoding: identity;q=1, *;q=0, sec-ch-ua-mobile: ?0, User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36, sec-ch-ua-platform: "macOS", Accept: */*, Sec-Fetch-Site: same-site, Sec-Fetch-Mode: no-cors, Sec-Fetch-Dest: video, Referer: http://localhost:12345/, Accept-Language: de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7, Cookie: <REDACTED>, Range: bytes=0-)
[io-compute-2] INFO  o.h.s.m.Logger - HTTP/1.1 206 Partial Content Headers(Last-Modified: Thu, 30 Jun 2022 14:11:32 GMT, Content-Length: 14541784, Content-Type: video/mp4, ETag: "181b4f3e854-dde3d8", Accept-Ranges: bytes, Content-Range: bytes 0-14541783/14541784)

[io-compute-13] INFO  o.h.s.m.Logger - HTTP/1.1 GET /assets/recordings/week%201/02%20Supervised%20learning%20part%201/index.mp4 Headers(Host: localhost:8080, Connection: keep-alive, Pragma: no-cache, Cache-Control: no-cache, sec-ch-ua: ".Not/A)Brand";v="99", "Google Chrome";v="103", "Chromium";v="103", Accept-Encoding: identity;q=1, *;q=0, sec-ch-ua-mobile: ?0, User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36, sec-ch-ua-platform: "macOS", Accept: */*, Sec-Fetch-Site: same-site, Sec-Fetch-Mode: no-cors, Sec-Fetch-Dest: video, Referer: http://localhost:12345/, Accept-Language: de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7, Cookie: <REDACTED>, Range: bytes=2916352-)
[io-compute-13] INFO  o.h.s.m.Logger - HTTP/1.1 206 Partial Content Headers(Last-Modified: Thu, 30 Jun 2022 14:11:32 GMT, Content-Length: 11625432, Content-Type: video/mp4, ETag: "181b4f3e854-dde3d8", Accept-Ranges: bytes, Content-Range: bytes 2916352-14541783/14541784)

java.io.IOException: Broken pipe
	at java.base/sun.nio.ch.FileDispatcherImpl.write0(Native Method)
	at java.base/sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
	at java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:113)
	at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:79)
	at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:50)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishWrite(UnixAsynchronousSocketChannelImpl.java:591)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(UnixAsynchronousSocketChannelImpl.java:195)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(UnixAsynchronousSocketChannelImpl.java:213)
	at java.base/sun.nio.ch.KQueuePort$EventHandlerTask.run(KQueuePort.java:312)
	at java.base/sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
	at delay @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.$anonfun$write$1(SocketPlatform.scala:137)
	at async @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.go$2(SocketPlatform.scala:131)
	at flatMap @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.go$2(SocketPlatform.scala:141)
	at delay @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.$anonfun$write$1(SocketPlatform.scala:137)
	at async @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.go$2(SocketPlatform.scala:131)
	at flatMap @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.go$2(SocketPlatform.scala:141)
	at modify @ org.http4s.ember.server.internal.Shutdown$$anon$1.<init>(Shutdown.scala:83)
java.io.IOException: Connection reset by peer
	at java.base/sun.nio.ch.FileDispatcherImpl.read0(Native Method)
	at java.base/sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
	at java.base/sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:276)
	at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:233)
	at java.base/sun.nio.ch.IOUtil.read(IOUtil.java:223)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishRead(UnixAsynchronousSocketChannelImpl.java:395)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(UnixAsynchronousSocketChannelImpl.java:191)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(UnixAsynchronousSocketChannelImpl.java:213)
	at java.base/sun.nio.ch.KQueuePort$EventHandlerTask.run(KQueuePort.java:312)
	at java.base/sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
	at delay @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.$anonfun$readChunk$1(SocketPlatform.scala:123)
	at async @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.readChunk(SocketPlatform.scala:117)
	at flatMap @ fs2.io.net.SocketCompanionPlatform$BufferedReads.$anonfun$read$1(SocketPlatform.scala:85)
	at delay @ fs2.io.net.SocketCompanionPlatform$BufferedReads.$anonfun$withReadBuffer$1(SocketPlatform.scala:54)
	at flatten$extension @ org.http4s.ember.server.internal.Shutdown$$anon$1.<init>(Shutdown.scala:71)
	at modify @ org.http4s.ember.server.internal.Shutdown$$anon$1.<init>(Shutdown.scala:83)
	at flatten$extension @ org.http4s.ember.server.internal.Shutdown$$anon$1.<init>(Shutdown.scala:71)
	at apply @ org.http4s.ember.server.EmberServerBuilder.$anonfun$build$2(EmberServerBuilder.scala:179)
java.io.IOException: Broken pipe
	at java.base/sun.nio.ch.FileDispatcherImpl.write0(Native Method)
	at java.base/sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47)
	at java.base/sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:113)
	at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:79)
	at java.base/sun.nio.ch.IOUtil.write(IOUtil.java:50)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.finishWrite(UnixAsynchronousSocketChannelImpl.java:591)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.finish(UnixAsynchronousSocketChannelImpl.java:195)
	at java.base/sun.nio.ch.UnixAsynchronousSocketChannelImpl.onEvent(UnixAsynchronousSocketChannelImpl.java:213)
	at java.base/sun.nio.ch.KQueuePort$EventHandlerTask.run(KQueuePort.java:312)
	at java.base/sun.nio.ch.AsynchronousChannelGroupImpl$1.run(AsynchronousChannelGroupImpl.java:112)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:829)
	at delay @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.$anonfun$write$1(SocketPlatform.scala:137)
	at async @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.go$2(SocketPlatform.scala:131)
	at flatMap @ fs2.io.net.SocketCompanionPlatform$AsyncSocket.go$2(SocketPlatform.scala:141)
	at modify @ org.http4s.ember.server.internal.Shutdown$$anon$1.<init>(Shutdown.scala:83)
	at flatten$extension @ org.http4s.ember.server.internal.Shutdown$$anon$1.<init>(Shutdown.scala:71)
	at apply @ org.http4s.ember.server.EmberServerBuilder.$anonfun$build$2(EmberServerBuilder.scala:179)
	at acquire @ fs2.Stream$NestedStreamOps$.$anonfun$parJoin$19(Stream.scala:4043)

@FloWi what's your version of http4s and Cats Effect? If things are working normally but an errors is being logged to stderr it could be Cats Effect's new "unhandled error handling" feature.

Lol - when I was checking the versions, I noticed a difference between my two projects. I overlooked that difference when comparing both versions.
The one with the "wrong" behavior was using http4s version 0.23.12 (since I created it last week with your g8 template). The version I created yesterday used 0.23.23 works as expected and doesn't spam stderr 🎉. I saw that Ross upgraded the g8 template this week ;-)

Btw: thanks for working on http4s, @armanbilge and others. I really enjoy working with it. The documentation is awesome compared to other open source projects!

@retriku do you still have this issue with the latest Cats Effect as well? Seems to me it was the changes in Cats Effect v3.3.8 which caused this behavior and has since been improved. See:

https://github.com/typelevel/cats-effect/pull/2868
which was released in https://github.com/typelevel/cats-effect/releases/tag/v3.3.8

Laika reports frequent broken pipe errors when using SSE.

https://github.com/planet42/Laika/pull/311


Add gpt-4o-mini to model list

It looks like tasks that use gpt-3.5-turbo should just switch to gpt-4o-mini. See https://openai.com/index/gpt-4o-mini-advancing-cost-efficient-intelligence/

Note: some early tests show that gpt-4o-mini is not very good and not sure if we want to make it available.


Add jpeg_quality parameter to log_image

Closes https://github.com/rerun-io/rerun/issues/2175
What
You can now do log_image("image", image, jpeg_quality=75) to compress your logged images so they take up less space on disk and in RAM.
I also updated the UI so you can actually tell whether or not a tensor was compressed.
This makes a many of our example data lot smaller. For instance, tracking_hf_opencv goes from 753 MB to 101MB.
Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct

PR Build Summary: https://build.rerun.io/pr/2418

Docs preview: https://rerun.io/preview/5ac2759/docs
Examples preview: https://rerun.io/preview/5ac2759/examples

OpenCV isn't the nicest dependency to have. For example, sometime one must use opencv-python-headless when it interferes with some UI toolkits, etc. Could we consider alternative package, e.g. Pillow?

Good idea - pillow we can probably depend on directly too; it is a pretty light dependency. Let's see if it supports jpeg compression…

Pillow is supposed to be pretty slow. Did you test speed at all? simplejpeg looks like it might be a better fit.

Unfortunately, they dont back their bold (and indeed tempting) claims with proper binaries for Apple silicon. I tried to install the package, it installed from source, and failed :(

Yes, this costs the user a bit of CPU at log-time. We could alleviate this by throwing the jpeg encoding in a background thread and wait for that thread on shutdown, but I don't want to do such a risky change right now. I've warned the user about the CPU cost in the docstring.

.github/workflows/reusable_build_and_test_wheels.yml needs fixing. I share @jleibs's perplexity around that part btw (line 242):
      - name: Install wheel dependencies
        if: needs.set-config.outputs.RUN_TESTS == 'true'
        # First we install the dependencies manually so we can use `--no-index` when installing the wheel.
        # This needs to be a separate step for some reason or the following step fails
        # TODO(jleibs): pull these deps from pyproject.toml
        # TODO(jleibs): understand why deps can't be installed in the same step as the wheel
        shell: bash
        run: |
          pip install deprecated numpy>=1.23 pyarrow==10.0.1 pytest==7.1.2

      - name: Install built wheel
        if: needs.set-config.outputs.RUN_TESTS == 'true'
        # Now install the wheel using a specific version and --no-index to guarantee we get the version from
        # the pre-dist folder. Note we don't use --force-reinstall here because --no-index means it wouldn't
        # find the dependencies to reinstall them.
        shell: bash
        run: |
          pip uninstall rerun-sdk
          pip install rerun-sdk==${{ steps.expected_version.outputs.EXPECTED_VERSION }} --no-index --find-links dist

Couldn't we just do that?
pip uninstall rerun-idk
pip install local/path/to/dist/rerun_xxx.whl


Nonstandard flag processing

https://github.com/zmap/zdns/blob/master/zdns/main.go#L18
The calls to flag.* and associated validation are usually done in func init(), leaving func main() for the main program flow/loop.

How would that work given that main passes the flags to the modules?


circleci-cli: 2018-05-12 -> 0.1.0

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Success on x86_64-linux (full log)
Attempted: circleci-cli
Partial log (click to expand)
no Makefile, doing nothing
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/rmhqpak9ih96d7kyvnhvhdv90cp4hlyf-circleci-cli-0.1.0
strip is /nix/store/fzsyclvxz1p2ia83caniy93v8cwarg0j-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/rmhqpak9ih96d7kyvnhvhdv90cp4hlyf-circleci-cli-0.1.0/bin
patching script interpreter paths in /nix/store/rmhqpak9ih96d7kyvnhvhdv90cp4hlyf-circleci-cli-0.1.0
/nix/store/rmhqpak9ih96d7kyvnhvhdv90cp4hlyf-circleci-cli-0.1.0/bin/circleci: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/8i8hqj3hg3axirbp7f990s1x50mnmq73-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/rmhqpak9ih96d7kyvnhvhdv90cp4hlyf-circleci-cli-0.1.0...
/nix/store/rmhqpak9ih96d7kyvnhvhdv90cp4hlyf-circleci-cli-0.1.0

Success on aarch64-linux (full log)
Attempted: circleci-cli
Partial log (click to expand)
no Makefile, doing nothing
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/82wxfb1zj2kbj44x2rfw9h9zw7alc28z-circleci-cli-0.1.0
strip is /nix/store/h0nc84ybvb8g724fwysvcghh1675wjli-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/82wxfb1zj2kbj44x2rfw9h9zw7alc28z-circleci-cli-0.1.0/bin
patching script interpreter paths in /nix/store/82wxfb1zj2kbj44x2rfw9h9zw7alc28z-circleci-cli-0.1.0
/nix/store/82wxfb1zj2kbj44x2rfw9h9zw7alc28z-circleci-cli-0.1.0/bin/circleci: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/xlv8nwq2cbxm2yancb3yk3424ziyb91q-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/82wxfb1zj2kbj44x2rfw9h9zw7alc28z-circleci-cli-0.1.0...
/nix/store/82wxfb1zj2kbj44x2rfw9h9zw7alc28z-circleci-cli-0.1.0