Receive message on XCode console but push not displayed on iPhone

I'm creating a test application, but I can not see the push notifications on the device. Messages triggered through the Firebase console arrive to the App, but the application can not display them.
The console shows that the App has connected correctly to the Firebase (token) and that there are incoming messages:
2019-02-19 17:50:55.142387-0300 HelloWorld[1548:294033]  - <AppMeasurement>[I-ACS036002] Analytics screen reporting is enabled. Call +[FIRAnalytics setScreenName:setScreenClass:] to set the screen name or override the default screen class name. To disable screen reporting, set the flag FirebaseScreenReportingEnabled to NO (boolean) in the Info.plist
2019-02-19 17:50:55.150727-0300 HelloWorld[1548:293991] DiskCookieStorage changing policy from 2 to 0, cookie file: file:///private/var/mobile/Containers/Data/Application/AA4ADB8A-8F2C-459B-989A-7A7C948A9B51/Library/Cookies/Cookies.binarycookies
2019-02-19 17:50:55.232013-0300 HelloWorld[1548:293991] Apache Cordova native platform version 4.5.5 is starting.
2019-02-19 17:50:55.232094-0300 HelloWorld[1548:293991] Multi-tasking -> Device: YES, App: YES
2019-02-19 17:50:55.237580-0300 HelloWorld[1548:293991]

Started backup to iCloud! Please be careful.
Your application might be rejected by Apple if you store too much data.
For more information please read "iOS Data Storage Guidelines" at:
https://developer.apple.com/icloud/documentation/data-storage/
To disable web storage backup to iCloud, set the BackupWebStorage preference to "local" in the Cordova config.xml file
2019-02-19 17:50:55.262802-0300 HelloWorld[1548:293991] Using UIWebView
2019-02-19 17:50:55.265299-0300 HelloWorld[1548:293991] [CDVTimer][console] 0.058055ms
2019-02-19 17:50:55.265406-0300 HelloWorld[1548:293991] [CDVTimer][handleopenurl] 0.057936ms
2019-02-19 17:50:55.266610-0300 HelloWorld[1548:293991] [CDVTimer][intentandnavigationfilter] 1.174092ms
2019-02-19 17:50:55.266700-0300 HelloWorld[1548:293991] [CDVTimer][gesturehandler] 0.050068ms
2019-02-19 17:50:55.266828-0300 HelloWorld[1548:293991] Starting Firebase plugin
2019-02-19 17:50:55.266855-0300 HelloWorld[1548:293991] [CDVTimer][firebaseplugin] 0.134945ms
2019-02-19 17:50:55.266875-0300 HelloWorld[1548:293991] [CDVTimer][TotalPluginStartup] 1.685023ms
2019-02-19 17:50:55.327581-0300 HelloWorld[1548:293991] GoogleService-Info.plist found, setup: [FIRApp configureWithOptions]
2019-02-19 17:50:55.341158-0300 HelloWorld[1548:294034] 5.7.0 - [Firebase/Analytics][I-ACS023007] Analytics v.50101000 started
2019-02-19 17:50:55.342705-0300 HelloWorld[1548:294034] 5.7.0 - [Firebase/Analytics][I-ACS023008] To enable debug logging set the following application argument: -FIRAnalyticsDebugEnabled (see http://goo.gl/RfcP7r)
2019-02-19 17:50:55.352934-0300 HelloWorld[1548:293991] [Crashlytics] Version 3.10.7 (130)
2019-02-19 17:50:55.448166-0300 HelloWorld[1548:294050] [NetworkInfo] Signal strength query returned error: Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied", descriptor: <CTServiceDescriptor 0x281358f00, domain=1, instance=1>
2019-02-19 17:50:55.465706-0300 HelloWorld[1548:294034] 5.7.0 - [Firebase/Messaging][I-FCM001000] FIRMessaging Remote Notifications proxy enabled, will swizzle remote notification receiver handlers. If you'd prefer to manually integrate Firebase Messaging, add "FirebaseAppDelegateProxyEnabled" to your Info.plist, and set it to NO. Follow the instructions at:
https://firebase.google.com/docs/cloud-messaging/ios/client#method_swizzling_in_firebase_messaging
to ensure proper integration.
2019-02-19 17:50:55.476043-0300 HelloWorld[1548:294038] 5.7.0 - [Firebase/Messaging][I-FCM002023] The object <AppDelegate: 0x281370940> does not respond to -messaging:didReceiveRegistrationToken:. Please implement -messaging:didReceiveRegistrationToken: to be provided with an FCM token.
2019-02-19 17:50:55.851358-0300 HelloWorld[1548:293991] Unable to connect to FCM. Error Domain=com.google.fcm Code=501 "(null)"
2019-02-19 17:50:55.872142-0300 HelloWorld[1548:293991] Resetting plugins due to page load.
2019-02-19 17:50:56.187876-0300 HelloWorld[1548:294080] [Fabric] failed to download settings Error Domain=FABNetworkError Code=-5 "(null)" UserInfo={status_code=403, type=2, request_id=3da77a3472b0c2f53584580d7f31bd50, content_type=application/json; charset=utf-8}
2019-02-19 17:50:56.291236-0300 HelloWorld[1548:293991] Finished load of: file:///var/containers/Bundle/Application/B7A1D05C-53B4-4093-A755-365DF844BCA5/HelloWorld.app/www/index.html
2019-02-19 17:50:56.294016-0300 HelloWorld[1548:293991] Received Event: deviceready
2019-02-19 17:50:57.132784-0300 HelloWorld[1548:293991] InstanceID token: eGQVhSiAO0Y:APA91bE8iFTCm1gRxoJCykItYqGKTldw3GVsb6jGht-tcxcT00saXTVBto--JahjwnDoDrBJ7yrIU-6KZasQhSF5gFJj9SzJkPXIoyyWsPhmliUL0Mg5REHdd5zm0tcZq-KgqP21WTDz
**2019-02-19 17:51:04.372702-0300 HelloWorld[1548:293991] Connected to FCM.
2019-02-19 17:51:04.383423-0300 HelloWorld[1548:293991] InstanceID token: eGQVhSiAO0Y:APA91bE8iFTCm1gRxoJCykItYqGKTldw3GVsb6jGht-tcxcT00saXTVBto--JahjwnDoDrBJ7yrIU-6KZasQhSF5gFJj9SzJkPXIoyyWsPhmliUL0Mg5REHdd5zm0tcZq-KgqP21WTDz**
2019-02-19 17:51:28.969956-0300 HelloWorld[1548:293991] **Received data message: {
    from =<PHONE_NUMBER>;
    image = "https://firebase.google.com/images/social.png";
    message = "Hello how are you?";
    title = "New Text Message";
}**

See on: "Received data message:.."
[Using]
Plugin version: 2.0.5
Cordova iOS<EMAIL_ADDRESS>Cordova CLI: 8.1.2<EMAIL_ADDRESS>Build System: Legacy Build System

have you resolved issue?

I have the same issue. For me the notifications stopped displaying after I installed the cordova-plugin-deeplinks plugin.
The messages show up in the XCode console and the callback is triggered when the app is open, but the notification is not displayed.
Cordova iOS<EMAIL_ADDRESS>Cordova CLI: 8.1.2<EMAIL_ADDRESS>Build System: Legacy Build System
Plugins:
cordova-plugin-advanced-http 2.0.4 "Advanced HTTP plugin"
cordova-plugin-deeplinks 1.1.0 "Cordova Deeplinks Plugin"
cordova-plugin-file 6.0.1 "File"
cordova-plugin-firebase 2.0.5 "Google Firebase Plugin"
cordova-plugin-geolocation 4.0.1 "Geolocation"
cordova-plugin-googlemaps 2.5.0 "cordova-plugin-googlemaps"
cordova-plugin-splashscreen 5.0.2 "Splashscreen"
cordova-plugin-statusbar 2.4.2 "StatusBar"
cordova-plugin-web-share 1.2.0 "WebShare"
cordova-plugin-whitelist 1.3.3 "Whitelist"
cordova-plugin-wkwebview-engine 1.1.4 "Cordova WKWebView Engine"
When the cordova-plugin-deeplinks plugin is installed, the notification in the XCode console looks like this:
2019-02-27 15:13:30.898157+0100 MyApp[380:45899] Received data message: {
    defBody = "My default body";
    defTitle = "My default title";
    from =<PHONE_NUMBER>14;
    group = GHdUQcSvDi1rkJpRE0wO;
    id = aCg9IjQpVknV4yO9G5xd;
}

When the cordova-plugin-deeplinks plugin is not installed, the notification in the XCode console looks like this:
2019-02-27 16:51:42.472750+0100 MyApp[493:61009] {
    aps =     {
        alert =         {
            body = "My body";
            "loc-args" =             (
                "My",
                "body"
            );
            "loc-key" = "notification_body";
            title = Title;
            "title-loc-args" =             (
                Title
            );
            "title-loc-key" = "notification_title";
        };
        "content-available" = 1;
    };
    defBody = "My default body";
    defTitle = "My default title";
    "gcm.message_id" =<PHONE_NUMBER>834484;
    "google.c.a.e" = 1;
    group = GHdUQcSvDi1rkJpRE0wO;
    id = xescBwo24sqEfci9gO7Y;
    tap = 0;
}

Ok, I solved my problem.
There was a conflict in how the two plugins managed the ios entitlements. After I fixed that, the notifications still didn't show up. I had to remove the app from the device and rebuild and reinstall it to fix the problem. Now the notifications work properly.

have you resolved issue?

No. The problem still continues =/

Ok, I solved my problem.
There was a conflict in how the two plugins managed the ios entitlements. After I fixed that, the notifications still didn't show up. I had to remove the app from the device and rebuild and reinstall it to fix the problem. Now the notifications work properly.

In my case, my project does not have any additional plugins. I am using the demo project, believed that there is no conflicting plugin at the moment.

@buzz-uion ever managed to fix this?
@petert37 Care to elaborate on the ios entitlements? I've spent 3 days on trying to get notifications to work on iOS without any success. Entitlements is the only thing I haven't really looked into yet, but then again, i tried to install a fresh cordova app to test this, so there wouldn't be any conflicts with other plugins.

I have the same issue. Tried to remove other plugins but still not working

@buzz-uion ever managed to fix this?
@petert37 Care to elaborate on the ios entitlements? I've spent 3 days on trying to get notifications to work on iOS without any success. Entitlements is the only thing I haven't really looked into yet, but then again, i tried to install a fresh cordova app to test this, so there wouldn't be any conflicts with other plugins.

The deeplinks plugin created its own Entitlements.plist file and changed XCode settings to use the new file (XCode project settings / Build settings / Code Signing Entitlements). So whatever the firebase plugin put into the entitlements was ignored.
You could check that the XCode settings are set to the default entitlements files (platforms/ios/<ProjectName>/Entitlements-Debug.plist) (and the same with Entitlements-Release.plist).
Also you could check that these files have something like this in them:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
  <dict>
    <key>aps-environment</key>
    <string>development</string>
  </dict>
</plist>

Finally you could check that in XCode Project settigns / Capabilities the Push Notifications are ON
But the notifications only started working for me after I Manually Removed the app from the device and then reinstalled it.


Stuck at net to device

Dear Repository owners,
I would like to use your deepALplus to do experiments with Deep Active Learning.
However, I always get stuck at line 23 in nets.py. It takes ages to execute but should normally be milliseconds:
self.clf = self.net(dim = dim, pretrained = self.params['pretrained'], num_classes = self.params['num_class']).to(self.device)
The script fails after ~20 min with RuntimeError: cuDNN error: CUDNN_STATUS_EXECUTION_FAILED.
Do you have any recommendations? Executing the code in https://github.com/ej0cl6/deep-active-learning works fine for me.
Could this be because of cudnn and cuda versions? Are the certain versions one has to use?
I installed using conda. I used cudnn/8.0_v7.0  and cuda/11.0.2 as well as cudnn/11.7_v8.6 amd cuda/11.7.0 and had the same behavior with both.
Thank you.

Possible reasons:

CUDNN is not installed
2.pytorch and cuda versions do not match. Specifically, the version of cuda and the environment cuda version at pvtorch compile time are inconsistent.
The graphics card is incompatible with the installed CUDA and CUDNN versions, for example, the 2080 requires at least cuda9.2 and above to run well.
The memory is insufficient and the dataloder processes too much data each time
Insufficient video memory, OOM. Sometimes when a program calls cuDNN with insufficient video memory, it may report cuDNN error instead of OOM

If cuDNN error is reported when the code is just running, it should be the first three reasons.
If an error occurs after running for a period of time, it should be 4 or 5.


feat: consider allowing features without localizations and an option to add/remove localization via cli

-- localizations flag on create feature
No localizations in .arb files when adding new feature
Add command to add and rm localizations

only add atm


Before saving the page user should be able to preview.

Framework Version: 0.1.6

No, this is not a right flow to preview the page as it will force creating an entry in database.

@jyoti-webkul  Please close the issue, as the preview functionality is already implemented for that you need to edit a page.
At the time of creation multiple pages are created according to locales and channels selected.


error run fintune.py

Thank you for your work ~
I got an error when running finetune.py
ValueError: Target modules ['q_proj', 'v_proj'] not found in the base model.
Please check the target modules and try again.

You can remove this model, or please refer this site https://github.com/huggingface/peft/blob/main/src/peft/mapping.py
or this issue https://github.com/linhduongtuan/BLOOM-LORA/issues/2


Opni Monitoring Functional Tests

Opni Monitoring Functional Tests

Codecov Report

Merging #54 (ac783e0) into main (44bdb1b) will decrease coverage by 0.81%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #54      +/-   ##
==========================================
- Coverage   62.52%   61.70%   -0.82%
==========================================
  Files          44       44
  Lines        1785     1802      +17
==========================================
- Hits         1116     1112       -4
- Misses        557      576      +19
- Partials      112      114       +2

Impacted Files
Coverage Δ

pkg/sdk/controllers/gateway_controller.go
72.72% <0.00%> (-21.22%)
:arrow_down:

pkg/b2bmac/header.go
87.75% <0.00%> (-7.81%)
:arrow_down:

pkg/management/extensions.go
78.75% <0.00%> (-3.37%)
:arrow_down:

pkg/bootstrap/types.go
11.11% <0.00%> (-3.18%)
:arrow_down:

pkg/noauth/server.go
65.57% <0.00%> (-1.64%)
:arrow_down:

pkg/validation/validation.go
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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


Added skipped test for json DATETIME bug.

Also, added || false on some regexes to create deterministic behavior in old versions of bash.

Can I merge this @andrew-wm-arthur?


Where does it save the redirects?

Hi,
I was wondering where do this plugin save the redirections?

the structure is defined using the blueprint section.
site/blueprints/site.yml
sections:
  # ...other sections
  redirects:
    extends: plugin-redirects3xx

by default it loads from that structure as defined in the bnomei.redirects.map setting callback.
but since its a callback you could overwrite it to just load from a json/yaml file you manage yourself. thats why the php api like site()->appendRedirects(...) exists.


License?

Hi I was wondering if you could specify a license for usage?

Seconding this. Once a suitable license, such as for example the ISC license has been chosen, please include a copy of the license text in a file named LICENSE and be sure to add the year(s), name(s) and e-mail address(es) of the copyright holder in the section dedicated to said information.

@MichaelScript @eriknstr Thanks for reminding me of license. I will add the MIT license to this repo soon.


You need to enable wechat pay on the uos platform to log in

Important：Please file the issue follow the template, or we won't be able to help you to solve the problem.

0. Report Issue Guide

Please run the following command and check whether the problem has been fixed：
rm -rf package-lock.json
rm -rf node_modules
npm install

Please search in FAQ List first, and make sure your problem has not been solved before.

Please search in the issue first, and make sure your problem had not been reported before

1. Versions

What is your wechaty version?

Answer: 0.60.9

Which puppet are you using for wechaty? (puppeteer/padlocal/service...)

Answer: puppeteer

What is your wechaty-puppet-XXX（padchat/puppeteer/） version?

Answer: puppeteer

What is your node version? (run node --version)

Answer: v13.14.0

What os are you using

Answer: uos
2. Describe the bug

Give a clear and concise description of what the bug is.
I tried to scan the code in the terminal and log in

ERR PuppetWeChatBridge onLoad() exception: Error: To continue, enable WeChat Pay first.
(node:4144) UnhandledPromiseRejectionWarning: Error: To continue, enable WeChat Pay first.
    at PuppetWeChat.<anonymous> (/Users/wulong/Desktop/Project/wechatyuos/node_modules/wechaty/dist/src/wechaty.js:271:44)
    at PuppetWeChat.emit (events.js:315:20)
    at PuppetWeChat.EventEmitter.emit (domain.js:485:12)
    at Bridge.<anonymous> (/Users/wulong/Desktop/Project/wechatyuos/node_modules/wechaty-puppet-wechat/dist/src/puppet-wechat.js:202:45)
    at Bridge.emit (events.js:315:20)
    at Bridge.EventEmitter.emit (domain.js:485:12)
    at Bridge.onLoad (/Users/wulong/Desktop/Project/wechatyuos/node_modules/wechaty-puppet-wechat/dist/src/bridge.js:156:18)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(Use `node --trace-warnings ...` to show where the warning was created)

It seems that you need to enable the wechat pay function on your account on the uos platform.
3. To Reproduce

This part is very important: if you can not provide any reproduce steps, then the problem will be very hard to be recognized.

How to create a Minimal, Reproducible Example
Steps to reproduce the behavior:

run '...'
...
...

4. Expected behavior

Give a clear and concise description of what you expected to happen.

5. Actual behavior

If applicable, add screenshots to help explain your problem. But do not paste log screenshots here.

6. Full Output Logs

Set env WECHATY_LOG=silly in order to set log level to silly, then we can get the full log (If you dosen't set log env, log level is info as default, we cannot get the full log)

We need full log instead of log screenshot or log fragments!

Show Logs

$ WECHATY_LOG=silly node yourbot.js

-> PASTE YOUR FULL(DO NOT ONLY PROVIDE FRAGMENTS) LOG MESSAGES HERE

ERR PuppetWeChatBridge onLoad() exception: Error: To continue, enable WeChat Pay first.
(node:4144) UnhandledPromiseRejectionWarning: Error: To continue, enable WeChat Pay first.
    at PuppetWeChat.<anonymous> (/Users/wulong/Desktop/Project/wechatyuos/node_modules/wechaty/dist/src/wechaty.js:271:44)
    at PuppetWeChat.emit (events.js:315:20)
    at PuppetWeChat.EventEmitter.emit (domain.js:485:12)
    at Bridge.<anonymous> (/Users/wulong/Desktop/Project/wechatyuos/node_modules/wechaty-puppet-wechat/dist/src/puppet-wechat.js:202:45)
    at Bridge.emit (events.js:315:20)
    at Bridge.EventEmitter.emit (domain.js:485:12)
    at Bridge.onLoad (/Users/wulong/Desktop/Project/wechatyuos/node_modules/wechaty-puppet-wechat/dist/src/bridge.js:156:18)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(Use `node --trace-warnings ...` to show where the warning was created)

7. Additional context

Add any other context about the problem here.

Yes, you need to enable wechat pay on the UOS platform to log in, which I believe it's required by WeChat.


Support nested inline templates

Say there's a method that accepts an inline template
public static MvcHtmlString DoSomething(
    this HtmlHelper htmlHelper,
    Func<dynamic, HelperResult> content)
{
    return MvcHtmlString.Create(content(null).ToHtmlString());
}

Razor should support nested calls to this method
@Html.DoSomething(
    @

        Hello
        @Html.DoSomething(
            @

                World

)

)

Tracking this in https://github.com/aspnet/Razor/issues/788


Filter events from after the stop indicator

Magic-trace doesn't stop recording exactly when the stop indicator is hit. That can be quite confusing, especially if you get unlucky and the stop event is nowhere near the right hand side of the trace.
To fix this, let's filter out events from the trace that happen after the stop indicator returns.
It's conceivable that people will want the current behavior behind a flag, but I weakly think it's not worth the extra UI complexity.

Looks like this could be useful: search man perf-record for "tracestop".

Ref also -immediate-stop from https://github.com/janestreet/magic-trace/pull/79.


[Bug]: Mouse-over of 'favourites' missing text in Chrome on Linux

Installation Method
Docker
The Problem
Hi all
When I mouse-over 'favourites' on the very top toolbar of the the website I see 'no favourites added'.
On my downloaded docker/podman image, when i moues over I get a blank in the dialogue window.  Here is an image of what I'm seeing:

This seems to only happen in an older version of Chromium (version 121.0.6167.139) (I was testing in this browser) not in Firefox so seems to be some bug in there.
Hope that helps.
Version of Stirling-PDF
0.34.0
Last Working Version of Stirling-PDF
No response
Page Where the Problem Occurred
http://localhost:8080
Docker Configuration
No response
Relevant Log Output
No response
Additional Information
No response
Browsers Affected
No response
No Duplicate of the Issue

[X] I have verified that there are no existing issues raised related to my problem.

@Frooodle is a duplicate of https://github.com/Stirling-Tools/Stirling-PDF/issues/2225


Add in-game input overlay hud element

Should include WASD movement, jump and crouch
+forward +back +moveleft +moveright
+jump +duck
RegisterConCommandTriggeredCallback( string concommand, void functionref( entity ) callback )

progress will be on branch feature/input-display

current idea is to implement an input display that looks like this one from Quake Champions

given that it's around the crosshair, making it as minimal as possible is important so it's not distracting to the runner
a potentially cool idea with this would be to make the spacing of the input display respond to the size of the crosshair depending on which weapon you have equipped since a static overlay will likely overlap with certain crosshairs in ugly ways

got it working, will probably still need some extra custom icons for jumping & crouching though

done in 40d135f998ac1e884a11a816a452d4ba0d13306b


Different wheaters

As a feature request, wouldnt it be nice if the mod had different wheaters? The default fogDensity looks nice but it can get boring quickly because of the limited view you get. It would be nice to have dynamic fogDensity  and snowDensity so sometimes you would get a better view of your world, but keeping the apocalyptic vibes.

No. The mod is primal winter. Not primal-most-of-the-time-but-actually-quite-varied-winter.


Keep a trace of body in request for http.Request

What version of Go are you using (go version)?
go1.6.2 linux/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/keleyroot/go"
GORACE=""
GOROOT="/usr/lib/go-1.6"
GOTOOLDIR="/usr/lib/go-1.6/pkg/tool/linux_amd64"
GO15VENDOREXPERIMENT="1"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0"
CXX="g++"
CGO_ENABLED="1"
(ubuntu 16.04)
What did you do?
I'm am working on a simple API that make HTTP request.
When a user enter this command : "http make", an http POST request with parameters is send to the host he specified. (classic)
Then I want that when the user type : "http info" he got the info of the request he made (url, method, header, body)
So everything works when I do these :
func showRequestHeaders(r *http.Request) {
	fmt.Println(r.Header)
}

func showResponseStatus(r *http.Response) {
	fmt.Println(r.Status)
}

func showResponseHeaders(r *http.Response) {
	fmt.Println(r.Header)
}

func showResponseRequest(r *http.Response) {
	fmt.Println(r.Request) //Here r.Request does not contain the body
}

But when I'm trying to do :
func showRequestBody(r *http.Request) {
	fmt.Println(r)
	fmt.Println(r.Body)
}

Nothing is in the body AFTER the request is sent. I try to add r.ParseForm() but not helping ...
I also try to keep a copy of http.Request like that : m.Request = *req (req is what I get from http.NewRequest and the * is to make a copy and not storing the pointer.) And same with the copy (and here I really don't know why) the map that contains the body disapear after the client.Do
What did you expect to see?
I except to keep a trace of the request body after it's sent.
What did you see instead?
A "nil" or empty map (try Body, Form, PostForm and all of them are empty or nil)
Thank you for your time. Maybe I'm doing something wrong and I'm really sorry if it's the case. Thanks again.

For questions, see https://golang.org/wiki/Questions

See http://stackoverflow.com/questions/39473493/golang-keep-a-trace-of-request-body-inside-http-request


Building a Library and Executable project fails with cannot satisfy -package-id -inplace

When attempting to build a project with both a library and an executable module that depends on it, epm build produces this error:
<command line>: cannot satisfy -package-id epm-lib-with-exec-<IP_ADDRESS>-inplace
    (use -v for more information)

epm-lib-with-exec.cabal:
name:                epm-lib-with-exec
version:             <IP_ADDRESS>
-- synopsis:
-- description:
-- license:
author:              Byron Shelden
maintainer<EMAIL_ADDRESS>-- copyright:
category:            Bug Example
build-type:          Simple
-- extra-source-files:
cabal-version:       >=1.10

library
  -- exposed-modules:
  -- other-modules:
  -- other-extensions:
  build-depends:       base >=4.8 && <4.9
  hs-source-dirs:      src
  default-language:    Haskell2010

executable exec
  main-is:             Main.hs
  hs-source-dirs:      exec-src
  build-depends:       base >=4.8 && <4.9, epm-lib-with-exec
  default-language:    Haskell2010

src/Lib.hs:
module Lib where

dummy :: a -> a
dummy a = a

src-exec/Main.hs:
module Main where

import Lib

main :: IO ()
main = putStrLn $ dummy "Hello, World"

Full output when attempting:
% epm sandbox init
Writing a default package environment file to
/home/bshelden/devel/epm-lib-with-exec/cabal.sandbox.config
Creating a new sandbox at /home/bshelden/devel/eta-cexc/.cabal-sandbox

% epm configure
Resolving dependencies...
Configuring epm-lib-with-exec-<IP_ADDRESS>...
Warning: The 'license-file' field refers to the file 'LICENSE' which does not
exist.

% epm build
Building epm-lib-with-exec-<IP_ADDRESS>...
Preprocessing library epm-lib-with-exec-<IP_ADDRESS>...
In-place registering epm-lib-with-exec-<IP_ADDRESS>...
Preprocessing executable 'exec' for epm-lib-with-exec-<IP_ADDRESS>...
<command line>: cannot satisfy -package-id epm-lib-with-exec-<IP_ADDRESS>-inplace
    (use -v for more information)

Note that the result does not change if I remove the sandbox and try again without it.

I was able to determine that this bug has nothing to do with epm and is a problem with eta. I have a hunch that it has to do with the inplace package database not being read. I'll post any updates.


Which files should be committed

And the debate continues over which files to commit to source, whether the whole node_modules is required, or just what exactly is required. Clearly something is, because when I ignore node_modules, I clone from my Git repository and the installed modules aren't there, much less any of their dependencies.

What problem are you trying to solve? General development? Deployment?
I advise against including node_modules in your git repo. It's unnecessary since any developer or tool should be able to clone your code and install all the node modules from your package.json by running  $ npm install.
For common use cases, including node_modules at best adds bloat and muddies up source history, but can also introduce fun when dealing with native modules.

I want to commit only the necessary files to Git (or other source control) such that I can clone and recall the npm package references.

All the packages you need should be tracked by the package.json. To test this, delete your node_modules folder and run $ npm install again for the project. It should recreate node_modules. If the project no longer works, you need to fix the package.json.
That's why I recommend against including node_moduldes in source control in almost all cases. Any developer or tool should be able to recreate it.

I don't recall the option precisely, but it was something like project only, or something like that. Anyway, I commit the package.json, and even the recursive ones, and this does not restore, or I have missed a file necessary to commit.

If you are working in a single project, chances are you only need the top level package.json. This should list all the dependencies for your project.
You ran npm install again, correct? What does your package.json look like? What files are missing after npm install?

Okay, so there is a "package@version (not listed in package.json)" in my npm section. I want to retain that feature about the project.

That circumvents the purpose of listing dependencies in package.json. What is the reasoning? Is it  private?
If you really need to have a package in node_modules but not in the package.json, you could configure the .gitignore file like this:
node_modules/
!node_modules/package-to-be-included-in-project/

I see, I understand, thanks.


A Pluto version warning

Use like:
PlutoUI.PlutoVersionWarning(v"0.12.1")

will output nothing when the version is higher than 0.12.1, and output a big warning when it is not.
I already wrote this, it just needs to be polished up and put into this package
html"""

"""

What needs to be done here. I m a bit confused can I get a bit of guidance


Tower PC shuts of due to “low battery”

Describe the bug
I just installed the bazzite-deck iso to an ssd when I boot it displays “low battery, please plug in or your pc will shut off” or something along those lines.  I have no battery because it’s a tower
What did you expect to happen?
I expected the installer to finish setting up steam and let me play
Output of rpm-ostree status
Unable to due to not fully installed
Hardware
I5-11500
RX6750 XT
32GB ddr4-3200
4TB SSD
GbE
Extra information or context
No response

on the image picker these were my selections

bazzite-deck was the wrong image, bazzite.iso worked just fine


Pin inmanta version in pytest-inmanta-extensions package

Description
Pin inmanta version in pytest-inmanta-extensions package.

I think you need to bump the version to 3.0.1.
Is the idea to pin to ~=major.minor.patch on all branches so that the patch number is allowed to float but the rest is tied to the version of core? In theory this is fine, but I think this will present difficulties when version bumping for iso4 and master. Iso3 can never be bumped outside of the patch increment range so in this case it's fine.

I don't understand this change request. This is a change on the iso3 branch, which doesn't have the inmanta-core package, but only the inmanta package. The inmanta package uses the <year>.<release>.<patch-nr> versioning schema.

I didn't communicate this very clearly, I apologize.

pytest-inmanta-extensions is currently at 3.0.0 for iso3. We decided to decouple it from inmanta's versioning for iso3 to keep it lower than the ones from iso4 and master. I believe that should be bumped to 3.0.1 because this is a patch on pytest-inmanta-extensions
the second point wasn't so much a change request as it was just as line of thought. I believe this change is fine here, but if we'd want similar changes on iso4 and master I think it would require some additional thought. You can safely ignore this bullet with respect to this pull request.


Update LMEvalJob resource

Short description:
Update LMEvalJob resource
More details:
LMEvalJob has added some new fields (allow_online and allow_code_execution) that are needed in order to use the resource
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

Summary by CodeRabbit

New Features

Introduced optional parameters to control remote code execution and resource downloading in the LMEvalJob class.
Enhanced the serialization of the LMEvalJob class to include new execution and access control attributes.

Documentation

Updated constructor docstring to include descriptions for the new parameters.
Corrected grammatical error in the docstring for the offline parameter.

/verified


Metabolic maps for Xanthomonas

Hi Zack, I want to upload my metabolic maps of Xanthomonas that were developed in collaboration with the SBRG, Jon and the University of Los Andes, Colombia. I just submitted the paper of the metabolic model to the ASM and would be great to reference and made available the maps through this repository.
Thanks,

hi, sorry for the response many months later! i did not have notifications set up here
Can you let me know when your paper is accepted? we could also include the model in BiGG Models, because we like to keep these synchronized


Change approvers to reviewers in front matter

This is a...

[x] Feature Request
[ ] Bug Report

Problem:
In several topics, in the front matter, we have an approvers list. But we want to restrict our approvers list to people in sig-docs-maintainers. And we the people who are automatically suggested as approvers to be restricted to those in sig-docs-maintainers.
Here's an example:
In #7439, we have this suggestion for an approver:
"To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: enisoc
Assign the PR to them by writing /assign @enisoc in a comment when ready."
How is it that enisoc was suggested as an approver?
I suspect it's because enisoc is listed as an aprover in the front matter of custom-resources.md.

title: Custom Resources
approvers:

enisoc
deads2k

Here's another example in #7445:
"We suggest the following additional approvers: davidopp, jbeda, jcbsmpsn, justinsb, lavalamp, liggitt, nikhiljindal, random-liu, thockin
Assign the PR to them by writing /assign @davidopp @jbeda @jcbsmpsn @justinsb @lavalamp @liggitt @nikhiljindal @random-liu @thockin in a comment when ready."
Proposed Solution:
In the front matter, change the name of the list from approvers to reviewers.
Page to Update:
Many pages in the kubernetes.io site.
Go to /docs. grep -r approvers

/assign @steveperry-53
/cc @heckj
/cc @chenopis
/cc @Bradamant3

https://github.com/kubernetes/website/pull/8644 is still open.
/remove-lifecycle stale


Write a dev-guide for AC Uniswap portal

Write an approachable guide that goes over the ideas behind the Aztec Connect Uniswap bridge, and explains how the design works, e.g., how it is aggregating and sending messages cross-chain etc.
The guide should be a good "starter" for someone picking up Aztec.nr.
Consider if best to make a guides section in the docs, or have it somewhere else, similar to there being solidity by example and so on.

A guides section sounds nice.
I know @spalladino is currently working on a dapps/tutorials/ section. So tagging him to take part in a debate about whether guides/ (or tutorials/, I don't mind which) should live at the top-level, or whether each section (contracts/,dapps/, wallets/, sandbox/, cli/, testing/) should have it's own 'tutorials' subdir, e.g. contracts/tutorials/?


HB 20160906

upload of localized readme files

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

It looks like you're a Microsoft contributor (Dominik Brtna (MORAVIA IT A.S.+ (USD))). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;


MINOR: fix message and reduce log level of PartitionGroup enforced processing

Should be cherrypicked back to 2.8

Thanks, @ableegoldman !
I'm planning to merge https://github.com/apache/kafka/pull/10137 today, which also fixes this.

Closing since this issue should be addressed on the side in https://github.com/apache/kafka/pull/10137


[VRM - Bug]: dynamic ess menu not visible anymore

Contact Details
<EMAIL_ADDRESS>VRM portal ID
c0619ab4a1a9
Country / region
Belgium (be)
B max
8
TB max
4
FB max
4
TG max
15
FG max
22
Battery costs
2.7
Buy price
No response
Sell price
No response
feed-in possible
None
feed-in control
None
What happened?
A bug happened!
For some reason, the ess setting menu disappeared in the navigation of the vrm. In the dashboard I can still swith ess on and off.
When did it happen?
Don’t realy know
Screenshots
No response

I have the same problem.
I am running venus os v3.40

I have 3.13, but nobody from victron seems to pick up this problem, are there other ways to contact victron support ?
Wim.

Hey both, I’ll make sure someone looks into this tomorrow / check what is being done on this.

A bug happened!
For some reason, the ess setting menu > disappeared in the navigation of the vrm. In the > dashboard I can still swith ess on and off.

You mean the dynamic ess menu in VRM, right?

I have 3.13

Venus OS v3.13 is quite old; for any trouble shooting; first thing to do will be to update it to the latest version; which at the moment is Venus OS v3.40

Thanks for your answer, yes the dynamic ess menu is not there anymore.

I’m on holliday now, I will do the os firmware upgrade on the 3th of august.


fix: fix make_dmg_config lost  specification

when build macos dmg, make_config.yaml's window size & position have no effect.
this PR fix this.
title: some_app
# window have no effect
window:
  size:
    width: 600
    height: 128
contents:
  - x: 100
    y: 64
    type: link
    path: "/Applications"
  - x: 200
    y: 64
    type: file
    path: some_app.app

LGTM


Cannot start a non-default slurm server and stop server button not working.

i tried using dev to get my work done... but it wouldnt let me start a non-default credential server and then when i tried to stop the server it created the button doesnt seem to work! When I hit stop server it keeps popping up the start server box. Also note that when i tried starting a server it gave me and HTTP error but then it eventually created one but the start server dialogue box still showed up as having an error with creating a cromwell server https://github.com/user-attachments/assets/dc39576e-3de0-4d78-86f6-e708e6658052

Relates to PROOF on DEV as of 12/10/24


Expose Switchboard internals

description
Expose Switchboard internals to facilitate trace forwarding with the trace-forward library
checklist

[x] compiles (cabal v2-build or stack build)
[x] tests run successfully (cabal v2-test or stack test)

bors r+


Optimise the UTxOIndex.fromMap operation.

Issue
ADP-2975
Details
The UTxOIndex.fromMap operation has been implicated as having slow performance in analyses of operations that use the balanceTx function.
This PR:

replaces the existing definition of fromMap (which generates and consumes an intermediate list) with a definition based on Map.foldlWithKey'.
replaces the use of insert with insertUnsafe.
adds property tests to assert the equivalence between fromMap and fromSequence.

Further optimisations are possible, such as completely rewriting fromMap in a way that doesn't require it to repeatedly call insertUnsafe. However, this optimisation is relatively cheap to implement, and should be a strict improvement over master.

This optimisation leads to a moderate performance improvement (latency after / latency before ≈ 0.94).
Latencies before:
    Latencies for 2 fixture wallets with 200 utxos scenario
        postTransactionFee  - 111.1 ms
    Latencies for 2 fixture wallets with 500 utxos scenario
        postTransactionFee  - 223.1 ms
    Latencies for 2 fixture wallets with 1000 utxos scenario
        postTransactionFee  - 419.8 ms

Latencies after:
    Latencies for 2 fixture wallets with 200 utxos scenario
        postTransactionFee  - 103.8 ms
    Latencies for 2 fixture wallets with 500 utxos scenario
        postTransactionFee  - 218.8 ms
    Latencies for 2 fixture wallets with 1000 utxos scenario
        postTransactionFee  - 396.5 ms

bors r+


resolve() should return Windows Reparse Point

Fixes https://github.com/vim/vim/issues/147

I'll add test

https://docs.microsoft.com/en-us/windows/desktop/api/fileapi/nf-fileapi-getfinalpathnamebyhandlea
MSDN says GetFinalPathNameByHandle is supported on Vista or later. I don't understand why appveyor fail.

https://www.codeproject.com/Articles/35202/GetFinalPathNameByHandle-API-Hangs
https://docs.microsoft.com/ja-jp/windows/desktop/api/winbase/nf-winbase-getfileinformationbyhandleex
There is also such a story.

Thank your information. I'll fix in later.

Hmm, I have no idea to build this on MSSDK7.1

I think resolve_reparse_point() should resolve the path only when it is a reparse point.
E.g. GetFileAttributes(path) & FILE_ATTRIBUTE_REPARSE_POINT

Document for resolve() should be also updated.
Does it always returns a fullpath even a symlink is relative?
Using the FSCTL_GET_REPARSE_POINT flag with DeviceIoControl() might be able to get a relative path, but it might not be necessary.

Codecov Report

Merging #3896 into master will decrease coverage by 76.54%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #3896       +/-   ##
===========================================
- Coverage   78.83%    2.29%   -76.55%
===========================================
  Files         105       96        -9
  Lines      142026   131046    -10980
===========================================
- Hits       111970     3006   -108964
- Misses      30056   128040    +97984

Impacted Files
Coverage Δ

src/buffer.c
3.45% <ø> (-77.1%)
:arrow_down:

src/evalfunc.c
0% <ø> (-88.42%)
:arrow_down:

src/crypt_zip.c
0% <0%> (-100%)
:arrow_down:

src/libvterm/src/vterm_internal.h
0% <0%> (-100%)
:arrow_down:

src/sha256.c
0% <0%> (-97.96%)
:arrow_down:

src/gui_gtk_f.c
0% <0%> (-97.88%)
:arrow_down:

src/arabic.c
0% <0%> (-96.65%)
:arrow_down:

src/libvterm/src/rect.h
0% <0%> (-96.56%)
:arrow_down:

src/libvterm/src/mouse.c
0% <0%> (-96.43%)
:arrow_down:

src/crypt.c
0% <0%> (-95.08%)
:arrow_down:

... and 93 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 889da2f...a46f448. Read the comment docs.

LGTM 👍

BTW, it is not related on this issue. my travis got double-free
https://travis-ci.org/mattn/vim/jobs/488366344#L3283
Executing Test_1_set_secure()issing on display ":99.0".
': double free or corruption (out): 0x0000000001cb3360 ***
Vim: Caught deadly signal ABRT
Vim: Finished.
Aborted (core dumped)
make[1]: *** [test_gui.res] Error 134
make[1]: Leaving directory `/home/travis/build/mattn/vim/src/shadow/testdir'
make: *** [scripttests] Error 2
make: Leaving directory `/home/travis/build/mattn/vim/src/shadow'
The command "make $SHADOWOPT $TEST" exited with 2.


tabbed interface - take 2

This approach is a bit different than we had discussed in #666 in order to get the change in quickly (but without disruption) as a starting point for adding tabs to the side panel.  Knowing if a tab is empty and should be hidden would require the tabs.js widget to listen for all possible tabs' state changes, which starts to look a bit like a "plugin" type pattern since the listener may know know what to listen to without its own code getting updated with every possible tab.  But this PR stops short of a full plugin implementation since that requires more "big" decisions than I feel comfortable making on my own, although I could easily see a "tabs plugin" directory that builds a tab list based on the tab widgets that exist inside.
Instead, I took a simplified approach so we could get this accepted/merged before we start getting conflicts due to other commits.  If you want to add a tab using this code, there are two steps:

Add additional tabs through the tabs.js state object like so:
tabs: [{id:'tocTab', label:'Indices'}, {id:'annotationsTab', label:'Annotations'}],
Add a "tab" widget that has an id property that matches the id supplied to the tabs.js widget (see annotationsTab.js)

To hide a tab, just remove it from the list referred to in step 1 (the tocTab is currently the only one).  You will not see the tabs until you add one since it hides the tab/label if there is only one tab.  I understand that the "tabs" array I refer to in step 1 could be defined in the configuration window object, but I'm struggling to remember how to set that up.  I don't mind adding it, but need some guidance.

Taking a look at this now.

Great! Let me know if you have any questions or suggestions.

@sdellis The side panel is still visible (without the option to hide it) if you are looking at an object that doesn't have a TOC.
When there is a TOC the animation for minimizing it looks a little weird - anyone else getting that?

Nice catch, @rsinghal.  I will fix that.

Ok, just looking back into this.  The goal was to allow the inclusion of any number of tabs in the panel, which have content panes (aka, widgets like toc.js and annotationsTab.js).
What I got stuck on, and what is necessary to know if a pane is empty, is this:  How does the sidePanel.js know what to listen for if the widgets are not predetermined?  Should there be a tab "plugin" convention that after a tab widget is instantiated, it emits a generic "tabbedContent" event with the widget id, and then the sidePanel can disappear if all tab panes are empty?  I want to be clear that we are not talking about setting the "open" property to false, but removing the option of toggling/maximizing the sidePanel at all.  I have having a hard time tracking down the code that does this currently when there is no toc or other tabs.
Any pointers or feedback?

I just want to follow up on this PR to clarify expectations.  @aeschylus asked me to contribute back the tabbed interface portion of the transcription work as others would like to add tabbed content and this provides a starting point.  I don't have much incentive to build out a "plugin" approach here since my project is done and I have to spend my time on other things at the moment.
I have provided the code we worked on with some additional features that @rsinghal suggested.  Unfortunately, after some attempts I'm having trouble hiding the SidePanel when there's no content in the TOC.  This is almost ready for someone to run with if they want to build out a plug-in approach here, but requires a bit more discussion before further coding can happen.
The purpose was to allow people to add tabbed content, but I don't know what the term "allow" means to the maintainers and what the expectations are. Now there's a merge conflict since a number of PRs have been merged since. I would like to see this either merged or scrapped.

@sdellis Sorry for the delay.  We are at a conference this week, but I plan to work on this later this week and early next week to help you resolve some of the issues you are having.  The side panel is really important and we want to get it into Mirador ASAP.

Thank you, @rsinghal.  Ping me when you're ready, and I'd be happy to work with you to wrap this up.

@sdellis @aeschylus this is nearly ready.  Let's get the tests in before merging with master.

I'm working on the tests for this today. Shouldn't be too long. I will force push them to this branch, so they update the PR here. @sdellis, we can catch up on this on the standup today if you're able to join. Basically we finished off the last bits of weirdness last Thursday.

@aeschylus , I have been really busy today getting things wrapped up before the break for a number of projects and Code4Lib.  I'm sorry I couldn't make the standup.  I will make a point to be on next week, and I will take a look at the code. I'm curious as to how @rsinghal solved it.

@aeschylus What is the status of the tests?

@aeschylus I don't want this PR to get out of sync with master, and since we are going to be refactoring to make testing easier, I don't think it is pressing to have tests in for this before we merge, so I'm going to go ahead with the merge.

:+1:


Can't install sharp

I install Directus extensions in docker container directus/directus:10.2.1 and sharp is a dependency
https://github.com/lovell/sharp-libvips/releases/download/v8.14.2/libvips-8.14.2-linuxmusl-x64.tar.br
#0 33.79<EMAIL_ADDRESS>install: sharp: Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.14.2/libvips-8.14.2-linuxmusl-x64.tar.br
#0 33.79<EMAIL_ADDRESS>install: sharp: Via proxy http://myproxy.com:13128 no credentials
#0 33.80<EMAIL_ADDRESS>install: sharp: Installation error: tunneling socket could not be established, cause=read ECONNRESET
#0 33.80<EMAIL_ADDRESS>install: sharp: Please see https://sharp.pixelplumbing.com/install for required dependencies
...
#0 33.88<EMAIL_ADDRESS>install: Failed
#0 33.88  ELIFECYCLE  Command failed with exit code 1.

besides I'd like to download tar.gz, not tar.br. My command to install packages
pnpm install $EXTENSIONS --config.platform=linux --config.architecture=x64

sharp: Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.14.2/libvips-8.14.2-linuxmusl-x64.tar.br
sharp: Via proxy http://myproxy.com:13128 no credentials
sharp: Installation error: tunneling socket could not be established, cause=read ECONNRESET

This looks like a networking problem between your web proxy and github.com. You'll need to ensure the proxy is capable of and/or permits TLS traffic to/from github.com.


Response Summary and user diagram don't show data

Response Summary and users picture don't show data in dashboard

I checked getServerMapDataV2.pinpoint interface don't respond linkDataArray data

How can resolve the problem?

Hi @Cyyking
What version of hbase are you using? This looks very similar to #4673

@Xylus I have checked the hbase's version is 2.1.0. i am going rebuild the hbase to 1.2.*. Thank for you help.

@Cyyking Awesome, please let me know if it fixes (or doesn't) your issue.
Thanks.


Fix KeyError: 'isHealNetworkActive'

Accessing the controller is_heal_network_active property results in a KeyError for node-zwave-js versions prior to 7.6.0.

In HA 2021.6 beta this results in a blank integration configuration page.

We have bumped the minimum server schema version to 5 in the library and will bump the library in Home Assistant, so users will need to install zwave-js-server 1.7.0 and zwave-js 7.6.0+ for core-2021.6.0.
That should fix this, right?

Schema 5 was added in 1.6.0.

Ok, we should probably have bumped schema version in 1.7.0 to 6. Now we can't use the schema version to force a specific service version.

Either way, accessing the dict keys with get() is agnostic to any server schema changes. All of the other controller properties are setup this way, this particular one is the outlier.

@raman325 I planning to merge this and then bump the library.
If we increase the server schema version to 6 that should fix things too. We can think about following up with that.


License?

Hi,
I spotted you have an empty license file, if it's hard for you to make a choice, which I can understand, you may use choosealicence.com or use the widely used MIT license
Take care..

Oops.. Thank you for indication. I fixed LICENSE file.


Fixup bun lambda post

Started also an example project over here using the aws-sdk: https://gitlab.com/flyck/hype-js/-/tree/main/bun

💪


This doesn't do anything

I'm confused... the extension does nothing because both the Enable and Disable options are disabled. LINQPad is installed to its default path, it is the Pro version, and I'm using VS2013 SP4. I've tried and get the same results on 2 different computers however both are Win7 x64 if that makes a difference. What do I need to do or look at to get this working? Thanks!

Hi,
I apologize, this comment fell through the cracks, I'm seeing it only now.
Anyway if you still need some help, I would need to know a few things:
Enable and Disable get enabled once you click on the solution explorer on a project or file inside a project given that the two projects are of type VB or C#. If you would send me the logs I could look into them. Please refer to this last comment[1] to see where logs are located.
Apologies again for the long delayed answer.
Thanks.
Giovanni
[1] https://github.com/nbasakuragi/LINQBridgeVs/issues/24#issuecomment-106363376


hubble: allow to filter agent events

This PR allows to apply filters on all event types and to filter agent events specifically. Previously (with #14168 in place), agent events were always returned leading to them being interleaved with flow events in Hubble CLI output.
See cilium/hubble#442 for the respective Hubble CLI PR, adding support for hubble observe -t agent.

test-me-please

test-me-please

retest-runtime

I think the part of the code above needs to be updated such that filters are also applied on agent events. This means that with the current code, we're always rewinding the ring buffer all the way until the writer is met instead of stopping early based on the time range or filters. However, as @gandro mentioned in the comment above, we are planning to have an API discussion and this might not be relevant anymore anyway and is not too important as this is more an optimization than anything else.

Thanks @Rolinh for pointing that out. Given the CI run on this PR suceeded and in case there are no further review comments, I'd address this in a follow-up depending on the outcome of the API discussion.

All required CI jobs passed (**K8s-1.20-kernel-4.9 ** was newly added while this PR was in flight). Marking as ready to merge.


How get json from post request (question)

I have route
Post["/"] = _ =>
            {
                 ...
            }

and with curl i send post request
curl -XPOST -H "Content-Type: application/json" http://localhost:7777/ -d '{"ok":true,"result":[{"update_id":698487365,"message":{"message_id":45,"from":{"id":10902074,"first_name":"Radzhab"},"chat":{"id":10902074,"first_name":"Radzhab"},"date":1439460132,"text":"asd"}}]}'
How get this json in response?

@Radzhab  You can do than like:
Post["/"] = _ =>
{
    var jsonString = this.Request.Body.AsString();
    return Response.AsJson(jsonString);
}

Спасибо)

@Radzhab  include this namespace using Nancy.Extensions;

You can also use <Bind> to bind the payload to a class. See the wiki on ModelBinding


Revision of status attribute

Status in our current data model can either be "old" or "current". This needs to be updated to reflect our current understanding of protected area statuses. The following dictates how our the attribute status should function:

If a given record has an SK of "Details", the record can have a status of "established". This is if the protected area is established.
If a given record has an SK of "Details", the record can have a status of "repealed". This is if the protected area is repealed. A protected area in a repealed state is at a dead end. This means, no further changes can be performed and you are not able to add anything to the change log.
If a given record has SK as a date, this implies that the status attribute is "historical". This can be overloaded in the future to track other types of changes to the protected area.

Acceptance Criteria

Data importer is updated
Endpoints that filter via status are updated
Endpoints that add/edit protected areas are updated
Attribute name type with value protectedarea exists on protected area objects in database
Update DUP and A&R to use the new status attribute

Notes
This ticket is blocked by #138 and #26. Doing this change while these tickets are active would cause conflict.
This ticket blocks #28, #30, #27, #132 and #133 and also #59 . The attribute status is needed for these front ends to make sense. Updates to the front end service layer will be required once this ticket is done.

Park Name GET endpoints will need to be updated to reflect the new statuses FYI

@meredithom is #26 still blocking this ticket? Since our chats about the filters sounds like we may be able to move this one to to-do?

Tested on TEST env: Failed

I am still getting records with sk set to "Details" with the status "current"

Tested on TEST using Postman and DynamoDB:

@cameronpettit can you add estimated story points to this one.
Moving to done


Skip import/export tests to get DMS through

Temporarily skip import/export tests in order to get the GeometryService update for security

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (9bfe581) 91.53% compared to head (0f3d24b) 91.10%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #981      +/-   ##
==========================================
- Coverage   91.53%   91.10%   -0.43%
==========================================
  Files          84       84
  Lines        6081     6081
==========================================
- Hits         5566     5540      -26
- Misses        515      541      +26

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Gender is not transferred to Postfinance Checkout

Our customers must register to place an order. The specification of gender is mandatory (M/F). This data is therefore available.
Apparently, this information is not passed on to the checkout and therefore the message to the customer is impersonal.
See image below.

If the gender was passed on, the salutation in this case would have been "Dear Sir". The checkout mail template is intended for this version but obviously does not receive all the information.
Is there anything else to set? The documentation says nothing about this.
Here the source from the Checkout Backend

any news here?

hi @Alcpaone , we will investigate this issue.

hi @Alcpaone , could you please provide us some details on how you setup the gender, where it would be selected and how it would be reflected ?

@thibault-mambour the gener is selectet at the moment of registration and is stored in the shop and also transfered to the WaWi.

After that we can use in all forms like invoice, shipping information, newsletter, delivery bill and more the correct salutation.

@thibault-mambour with release 1.0.20 there was still no email, that was correct from Checkout to the customers. Is there anything we can check / change to match your changements in the realease?

@thibault-mambour interesting, today we had one email from postfinance checkout, where the gender was correct. How is that possible? Where do you take the gender from?

@thibault-mambour we still have a lot of payments with no correct gender. Any news on this issue?

still same Problem with Release 1.0.23

still same Problem with Release 1.0.24


Add a system ordering example

How can Bevy's documentation be improved?
Beginners often struggle to get a cohesive view of how system ordering works in Bevy.
The ecs_guide example is surprisingly good for this, but that's hard to discover.
We want to cover all of the tools talked about here:

So, there are 4 main tools for scheduling systems in Bevy. I'm going to go in order of complexity:
Put you systems in a tuple and then call .chain on them. They will run in the order listed. Very straightforward, but limited to code in the same place and linear orderings.
Use explicit system ordering like avoidance.after(set_velocity). This will do exactly what it says, as long as they're both in the same schedule.
Add your systems to a system set like set_velocity.in_set(VelocityManagement) and then use system ordering like avoidance.after(VelocityManagement). Great for modularity and preserving a tightly scoped public API.
Change which schedule you're adding the systems to. Useful if you need to carefully order things relative to Bevy's built-in systems, or are working with Commands. 90% of the time though, your systems should all just be in either Update (very easy!) or FixedUpdate (if you care about networking or framerate independence).

Personally, I'm in favor of removing the ecs_guide example entirely: its purpose is unclear at this point.

I'm a Bevy beginner and I just don't know where to start, especially for latest versions. There's a few youtube videos online but they just code entire simple games (which is good and I can follow them, but it is far from a comprehensive guide). There's also an unofficial bevy book that's stuck to 0.9 I think. Also the examples are just code and (at least for me) they are not very clear because I'm not very good at just reading and understanding the code. There's a big need for some comprehensive guide that talks about the engine features and doesn't immediatly show code, because even from 0.1 to 0.11 there's so many differences that make some 0.1 code tutorial even confusing. I would like to be able to help creating such guides but I don't know the game engine at all.


expand test coverage for fromager.dependencies

Add some unit tests that pull the dependencies of fromager itself.

This version is leaving debris in the root dir now when tests run, let me resolve that before we merge it.


Resource intake: Incorporate Linch Zhang's suggestions

https://docs.google.com/document/d/1MqCuZ6wC_oRhu-TgkLMl7WA6xZ5Wu2V1oBsWYSDawOg/edit#heading=h.xceajivibi0x
Read this and incorporate suggestions!

Just read these. Sounds like useful feedback on all fronts. Excited to see if y'all have accounted for some of these things already or they do point to possible improvements in the risk model.


Power_outage_memory is not functioning properly

Domoticz 2021.1 build 13360
Zigbee2MQTT version 1.20.0-dev commit: cee9eb1e
Coordinator type  zStack3x0
Coordinator revision 20210708
Frontend version 0.5.18
Latest plugin from today.
I changed the power_outage_memory today on several https://www.zigbee2mqtt.io/devices/TS0121_plug.html#tuya-ts0121_plug devices.
That also changed the kWh to 10, 20 or 30 Watts when then plug is OFF depending on the setting of the power_outage_memory
Before I change the state of power_outage_memory it was "unknown" and at that time the power was 0 Watts when the plug was OFF.
In the MQTT messages the wattage is still 0 Watt, so those messages are OK.
Is it possible to fix this soon? B.t.w. there are no devices with ID of *_pwrmem on these plugs.
Or is there a way to undo the setting?

Found out that on some devices like bulbs the function is On/Off
On other devices like smart plugs the function is a selector switch with On/Off/Restore (last state) but the initial state is nill
So that's probably why there is no device created.
I hope that a solution can be found, because Koenkk and nurikk did find a solution.

I have some debug logging of that device switching on and off again.
What happens is that the values get overwritten by the power_outage_memory value every time.
2021-08-20 13:56:35.721  (zigbee2mqtt - Wasdroger (Power)) Updating device from 1:'20' to have values 0:'0;14720'. 2021-08-20 13:56:35.727  (zigbee2mqtt - Wasdroger (state)) Updating device from 1:'On' to have values 0:'Off'. 2021-08-20 13:56:35.734  (zigbee2mqtt - Wasdroger (Power)) Updating device from 0:'0;14720' to have values 1:'20'.
It looks like the plugin cannot distingue between 'power' and 'power_outage_memory'
Both start with power. I can't solve it (lack of python knowledge), but it looks easy solvable.
Wasmachine.log

I had a quick look to see whether I could understand why it is hapening but didn't manage to find the problem.
one thing you could try is to 'revert' the power_outage_memory change and see whether that gives you back the normal working. Edit adapter.py, search for power_outage_memory (line 179) and comment out the 2 lines below (add a # as first character on that line) leaving only the return statement. Restart the plugin and see whether that makes a difference. If not then the issue is indeed in a different area than the p_o_m handling.

The problem is the fact that there are 2 kind of p_o_m devices

https://www.zigbee2mqtt.io/devices/ZNLDP12LM.html#xiaomi-znldp12lm which has false/true
https://www.zigbee2mqtt.io/devices/TS0121_plug.html#tuya-ts0121_plug which has on/off/restore
The first kind of devices have there *_pwrmem devices created as false/true as a light/switch with on/off
The second kind has nothing created as *_pwrmem devices, and those are creating problems as described.
So commenting out the first type of binary devices does not solve the problem.

True but I don't get the point of replicating p_o_b functionality in zigbee2mqtt. It's a static parameter that can be easily set from the zigbee2mqtt interface. That's where my expectation was that manually reverting this change would resolve that dependency. In the zwavejs2mqtt plugin, we made the decision to only replicate state functionality and leave the rest in the zwavejs2mqtt web interface (so no inclusion in domoticz but in the web interface). Much less maintenance and issues.

As I look at the code: by commenting out those 2 lines in the " def add_binary_device(self, feature):" you will prevent the devices from my first example being created. But the problem is not with those devices, it is with the second type of devices, which are of type enum.

Mistery solved, final solution not yet.
In 'adaptor.py' there is a line for the selector definition.
self._add_selector_device(item['name'][0: 5], item)
that wants to create a device from "power_outage_memory" -> _power but that device already exists from power (kWh) it self.
So I changed the 5 in 6 so it wants to create power from "power_outage_memory" and that went fine.
There is a side-effect that all previous created devices with 'name' of more then 5 characters are new created with 6 char.
So *_effec -> *_effect, *_actio -> *_action  Old devices have to de deleted.
Who will change that with a commit?

why limit it to 6 instead of using the full label (power_outage_memory)?
Any reason why self._add_selector_device(item['name'], item) would not work?

Otherwise the ID can get very long and does display well in the Domoticz GUI.

Yeah maybe but that has then led to this issue. Even choosing 6 characters is not very future proof in case something is changed zigbee2mqtt. Personally, I would not want all of these in the plugin anyway as I'd rather set them from the z2m webpage and forget. Saves maintenance going forward. But that's me.

That's because DeviceID in Domoticz has the type Varchar(25), so it can't be longer than 25 characters

@stas-demydiuk That can't be: using our (moroen and myself) zwavejs2mqtt plugin, I already have many devices that have an id of 36 characters (example: "/161/113/0/Access_Control/Door_state").

How is that possible, or are you using "Name"?

@SargonofAssyria, back to your original issue, hopefully the latest plugin version that I've just pushed should handle that properly, so I wonder if you could upgrade and check.

My Domoticz log file is filled with
2021-09-04 14:11:50.636 Error: zigbee2mqtt: (zigbee2mqtt) 'onMessage' failed 'AttributeError':''NoneType' object has no attribute 'Name''. 2021-09-04 14:11:50.636 Error: zigbee2mqtt: (zigbee2mqtt) Exception traceback: 2021-09-04 14:11:50.636 Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 301 in '/opt/domoticz/userdata/plugins/zigbee2mqtt/plugin.py', function onMessage 2021-09-04 14:11:50.636 Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 135 in '/opt/domoticz/userdata/plugins/zigbee2mqtt/plugin.py', function onMessage 2021-09-04 14:11:50.636 Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 167 in '/opt/domoticz/userdata/plugins/zigbee2mqtt/mqtt.py', function onMessage 2021-09-04 14:11:50.636 Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 215 in '/opt/domoticz/userdata/plugins/zigbee2mqtt/plugin.py', function onMQTTPublish 2021-09-04 14:11:50.636 Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 61 in '/opt/domoticz/userdata/plugins/zigbee2mqtt/devices_manager.py', function handle_mqtt_message 2021-09-04 14:11:50.636 Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 64 in '/opt/domoticz/userdata/plugins/zigbee2mqtt/adapters/base_adapter.py', function handle_mqtt_message

Are there any logs prior to that to understand what is causing the issue?

No that was normal, this is the log from the start of zigbee
2021-09-04 14:10:59.786  Status: zigbee2mqtt: (zigbee2mqtt) Entering work loop. 2021-09-04 14:10:59.786  zigbee2mqtt hardware started. 2021-09-04 14:10:59.787  Status: zigbee2mqtt: (zigbee2mqtt) Started. 2021-09-04 14:11:00.234  Status: zigbee2mqtt: (zigbee2mqtt) Initialized version 3.1.0-beta 2021-09-04 14:11:00.236  zigbee2mqtt: (zigbee2mqtt) Installing plugin custom page... 2021-09-04 14:11:00.257  zigbee2mqtt: (zigbee2mqtt) Installing plugin custom page completed. 2021-09-04 14:11:00.308  zigbee2mqtt: (zigbee2mqtt) Connected to MQTT Server: <IP_ADDRESS>:1883 2021-09-04 14:11:00.411  zigbee2mqtt: (zigbee2mqtt) Zigbee2mqtt bridge is online 2021-09-04 14:11:00.419  zigbee2mqtt: (zigbee2mqtt) Received available devices list from bridge 2021-09-04 14:11:00.718  Error: zigbee2mqtt: (zigbee2mqtt) Hobbykamer: can not process numeric item "local_temperature_> 2021-09-04 14:11:01.659  zigbee2mqtt: (zigbee2mqtt) Joining new devices is disabled on the zigbee bridge 2021-09-04 14:11:01.686  Error: zigbee2mqtt: (zigbee2mqtt) 'onMessage' failed 'AttributeError':''NoneType' object has n> 2021-09-04 14:11:01.686  Error: zigbee2mqtt: (zigbee2mqtt) Exception traceback: 2021-09-04 14:11:01.686  Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 301 in '/opt/domoticz/userdata/plugins/zigbee2mqt> 2021-09-04 14:11:01.686  Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 135 in '/opt/domoticz/userdata/plugins/zigbee2mqt> 2021-09-04 14:11:01.686  Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 167 in '/opt/domoticz/userdata/plugins/zigbee2mqt> 2021-09-04 14:11:01.686  Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 215 in '/opt/domoticz/userdata/plugins/zigbee2mqt> 2021-09-04 14:11:01.686  Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 61 in '/opt/domoticz/userdata/plugins/zigbee2mqtt> 2021-09-04 14:11:01.686  Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 64 in '/opt/domoticz/userdata/plugins/zigbee2mqtt> 2021-09-04 14:11:01.686  Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 177 in '/opt/domoticz/userdata/plugins/zigbee2mqt> 2021-09-04 14:11:01.686  Error: zigbee2mqtt: (zigbee2mqtt) ----> Line 85 in '/opt/domoticz/userdata/plugins/zigbee2mqtt> 2021-09-04 14:11:01.713  Error: zigbee2mqtt: (zigbee2mqtt) 'onMessage' failed 'AttributeError':''NoneType' object has n>

Could you please upgrade and check again

Pulled again, emptied the exception list, now NO errors.
But how do I fill the exception list, it looks like the unit number is now the type???

You need to use zigbee feature name now instead of alias, so for example *_lowbtr will be now *_battery_low

Checked it with .*_effect and it worked. Tnx. I keep testing before I put it into production.

There is a small problem with excluding 'illuminance' and/or 'illuminance_lux' Is there a solution?
I have a lot of devices, a lot of them have to be created again. Is there a logic in the current setup of ID and Unit?
I might be be better of to create a few sql command to rename the ID's and Units from old to new and save a lot of work and keep the history.

What's the issue with illuminance?
DeviceID now equals to device zigbee IEEE address, unit is just first available unit (from 1 to 255) for that device_id. Once the device is created, the plugin adds appropriate alias to configuration. What's the issue with your devices, all previously created devices should continue to work just fine?

illuminance issue is I cannot exclude  one or the other.
When I put in 'illuminance' both are excluded.

As each item in a blacklist is a regex I guess you could try smth like *_illuminance$

@SargonofAssyria, do you still have the original issue or ticket could be closed?

In my test environment I don't have this issue any more. :)


Swingpole launches Lara far into the void if she was not aligned to the poles correctly

I was watching a stream with a controller player ShadowZia (sadly there's no VOD :/ ) and she consistently grabbed the swingpole at a slightly wonky angle, and when let go Lara would fly way further than intended and enters the void instead of the specified OCB values or 2 or 3 blocks. Will try to include clips but it seems consistent whenever Lara's swinging at a slightly "wrong" angle. I propose forcing Lara to face exactly at the angle perpendicular to the swingpole itself.

https://youtu.be/pOIQ_65I1eU
to replicate it I pressed left/right as she's jumping towards to pole and not letting go until she's grabbed the pole.


Ember 1.9.1

I tried running the test suite against Ember 1.9.1 and Handlebars 2.0.0 and experienced a number of errors. The errors occur without the Handlebars upgrade as well
Running
node v0.10.35
npm v2.2.0
OS X v10.10.1
$ grunt test
Running "jshint:library" (jshint) task
>> 39 files lint free.

Running "jshint:tests" (jshint) task
>> 27 files lint free.

Running "lintspaces:all" (lintspaces) task
>> 140 files lint free.

Running "clean:0" (clean) task

Running "clean:1" (clean) task
Cleaning tmp...OK

Running "transpile:amd" (transpile) task

Running "concat:amd" (concat) task
File "tmp/ember-simple-auth-cookie-store.amd.js" created.
File "tmp/ember-simple-auth-devise.amd.js" created.
File "tmp/ember-simple-auth-oauth2.amd.js" created.
File "tmp/ember-simple-auth-testing.amd.js" created.
File "tmp/ember-simple-auth-torii.amd.js" created.
File "tmp/ember-simple-auth.amd.js" created.

Running "concat:browser" (concat) task
File "tmp/ember-simple-auth-cookie-store.js" created.
File "tmp/ember-simple-auth-devise.js" created.
File "tmp/ember-simple-auth-oauth2.js" created.
File "tmp/ember-simple-auth-testing.js" created.
File "tmp/ember-simple-auth-torii.js" created.
File "tmp/ember-simple-auth.js" created.

Running "string-replace:version" (string-replace) task
File tmp/ember-simple-auth-cookie-store.amd.js created.
File tmp/ember-simple-auth-cookie-store.js created.
File tmp/ember-simple-auth-devise.amd.js created.
File tmp/ember-simple-auth-devise.js created.
File tmp/ember-simple-auth-oauth2.amd.js created.
File tmp/ember-simple-auth-oauth2.js created.
File tmp/ember-simple-auth-testing.amd.js created.
File tmp/ember-simple-auth-testing.js created.
File tmp/ember-simple-auth-torii.amd.js created.
File tmp/ember-simple-auth-torii.js created.
File tmp/ember-simple-auth.amd.js created.
File tmp/ember-simple-auth.js created.

Running "transpile:tests" (transpile) task

Running "concat:tests" (concat) task
File "tmp/ember-simple-auth-cookie-store-tests.amd.js" created.
File "tmp/ember-simple-auth-devise-tests.amd.js" created.
File "tmp/ember-simple-auth-oauth2-tests.amd.js" created.
File "tmp/ember-simple-auth-testing-tests.amd.js" created.
File "tmp/ember-simple-auth-torii-tests.amd.js" created.
File "tmp/ember-simple-auth-tests.amd.js" created.

Running "connect:dev" (connect) task
Started connect web server on http://<IP_ADDRESS>:8000

Running "mocha:test" (mocha) task
Testing: http://localhost:8000/test/index.html?
<IP_ADDRESS> - GET /test/index.html? HTTP/1.1 200 1803 - 6 ms
<IP_ADDRESS> - GET /test/vendor/mocha.css HTTP/1.1 200 4242 - 2 ms
<IP_ADDRESS> - GET /test/lib/dependencies-loader.js HTTP/1.1 200 537 - 2 ms
<IP_ADDRESS> - GET /test/lib/shims.js HTTP/1.1 200 312 - 2 ms
<IP_ADDRESS> - GET /test/vendor/sinon-chai.js HTTP/1.1 200 5231 - 3 ms
<IP_ADDRESS> - GET /test/vendor/chai.js HTTP/1.1 200 117322 - 4 ms
<IP_ADDRESS> - GET /test/vendor/mocha.js HTTP/1.1 200 123164 - 4 ms
<IP_ADDRESS> - GET /vendor/loader.js HTTP/1.1 200 1290 - 2 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth.amd.js HTTP/1.1 200 59916 - 2 ms
<IP_ADDRESS> - GET /test/vendor/sinon.js HTTP/1.1 200 146138 - 4 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth-oauth2.amd.js HTTP/1.1 200 16728 - 2 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth-cookie-store.amd.js HTTP/1.1 200 9753 - 2 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth-devise.amd.js HTTP/1.1 200 12851 - 2 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth-torii.amd.js HTTP/1.1 200 4506 - 2 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth-testing.amd.js HTTP/1.1 200 2544 - 2 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth-tests.amd.js HTTP/1.1 200 65227 - 4 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth-oauth2-tests.amd.js HTTP/1.1 200 23085 - 4 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth-cookie-store-tests.amd.js HTTP/1.1 200 6358 - 4 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth-devise-tests.amd.js HTTP/1.1 200 14675 - 4 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth-torii-tests.amd.js HTTP/1.1 200 5694 - 4 ms
<IP_ADDRESS> - GET /tmp/ember-simple-auth-testing-tests.amd.js HTTP/1.1 200 1414 - 3 ms
<IP_ADDRESS> - GET /test/vendor/jquery-2.1.1.js HTTP/1.1 200 247351 - 5 ms
<IP_ADDRESS> - GET /test/vendor/handlebars.js HTTP/1.1 200 100756 - 4 ms
<IP_ADDRESS> - GET /test/vendor/ember-1.9.1.js HTTP/1.1<PHONE_NUMBER> - 6 ms

  Authenticators.Base
    #restore
      ✓ returns a rejecting promise
    #authenticate
      ✓ returns a rejecting promise
    #invalidate
      ✓ returns a resolving promise

  Configuration
    authenticationRoute
      ✓ defaults to "login"
    routeAfterAuthentication
      ✓ defaults to "index"
    routeIfAlreadyAuthenticated
      ✓ defaults to "index"
    sessionPropertyName
      ✓ defaults to "session"
    authorizer
      ✓ defaults to null
    session
      ✓ defaults to "simple-auth-session:main"
    store
      ✓ defaults to "simple-auth-session-store:local-storage"
    localStorageKey
      ✓ defaults to "ember_simple_auth:session"
    crossOriginWhitelist
      ✓ defaults to []
    .load
      ✓ sets applicationRootUrl to the application's root URL
      ✓ sets authenticationRoute correctly
      ✓ sets routeAfterAuthentication correctly
      ✓ sets routeIfAlreadyAuthenticated correctly
      ✓ sets sessionPropertyName correctly
      ✓ sets authorizer correctly
      ✓ sets session correctly
      ✓ sets store correctly
      ✓ sets localStorageKey correctly
      ✓ sets crossOriginWhitelist correctly

  the "simple-auth" initializer
    ✓ has the correct name

  ApplicationRouteMixin
    #beforeModel
      when there is no active route
        ✓ sends the action to the transition
      when there is an active route
        ✓ translates the session's 'sessionAuthenticationSucceeded' event into an action invocation
        ✓ translates the session's 'sessionAuthenticationFailed' event into an action invocation
        ✓ translates the session's 'sessionInvalidationSucceeded' event into an action invocation
        ✓ translates the session's 'sessionInvalidationFailed' event into an action invocation
        ✓ translates the session's 'authorizationFailed' event into an action invocation
        ✓ does not attach the event listeners twice
    the "authenticateSession" action
      ✓ transitions to "Configuration.authenticationRoute"
    the "sessionAuthenticationSucceeded" action
      when an attempted transition is stored in the session
        ✓ retries that transition
        ✓ removes it from the session
      when no attempted transition is stored in the session
        ✓ transitions to "Configuration.routeAfterAuthentication"
    the "invalidateSession" action
      ✓ invalidates the session
    the "authorizationFailed" action
      when the session is authenticated
        ✓ invalidates the session
      when the session is not authenticated
        ✓ does not try to invalidate the session

  AuthenticatedRouteMixin
    #beforeModel
      if the session is authenticated
        ✓ does not abort the transition
        ✓ does not invoke the "authenticateSession" action
      if the session is not authenticated
        ✓ aborts the transition
        ✓ invokes the "authenticateSession" action

  AuthenticationControllerMixin
    the "authenticate" action
      ✓ authenticates the session
      ✓ returns the promise returned by the session

  LoginControllerMixin
    the "authenticate" action
      when both identification and password are set on the controller
        ✓ unsets the password
        ✓ authenticates the session
        ✓ returns the promise returned by the session

  UnauthenticatedRouteMixin
    #beforeModel
      if the session is authenticated
        ✓ aborts the transition
        ✓ transitions to routeIfAlreadyAuthenticated
      if the session is not authenticated
        ✓ does not abort the transition
        ✓ does not call route transitionTo

  Session
    restore
      when the restored data contains an authenticator factory
        when the authenticator resolves restoration
          ✓ returns a resolving promise
          ✓ is authenticated
          ✓ merges its content to the data the authenticator resolves with
          ✓ persists its content in the store
          ✓ persists the authenticator factory in the store
          ✓ does not trigger the "sessionAuthenticationSucceeded" event
          when the authenticator triggers the "sessionDataUpdated" event
            ✓ merges its content to the data the event is triggered with
          when the authenticator triggers the "invalidated" event
            ✓ is not authenticated
            ✓ clears its content
            ✓ clears the store
            ✓ triggers the "sessionInvalidationSucceeded" event
        when the authenticator rejects restoration
          ✓ returns a rejecting promise
          ✓ is not authenticated
          ✓ clears the store
          ✓ does not trigger the "sessionAuthenticationFailed" event
      when the restored data does not contain an authenticator factory
        ✓ returns a rejecting promise
        ✓ is not authenticated
        ✓ clears the store
        ✓ does not trigger the "sessionAuthenticationFailed" event
    authentication
      when the authenticator resolves authentication
        ✓ is authenticated
        ✓ returns a resolving promise
        ✓ merges its content to the data the authenticator resolves with
        ✓ persists its content in the store
        ✓ persists the authenticator factory in the store
        ✓ triggers the "sessionAuthenticationSucceeded" event
        ✓ does not trigger the "sessionAuthenticationFailed" event
        when the authenticator triggers the "sessionDataUpdated" event
          ✓ merges its content to the data the event is triggered with
        when the authenticator triggers the "invalidated" event
          ✓ is not authenticated
          ✓ clears its content
          ✓ clears the store
          ✓ triggers the "sessionInvalidationSucceeded" event
      when the authenticator rejects authentication
        ✓ is not authenticated
        ✓ returns a rejecting promise
        ✓ clears its content
        ✓ clears the store
        1) does not trigger the "sessionAuthenticationSucceeded" event
        ✓ does not trigger the "sessionAuthenticationSucceeded" event
    invalidation
      when the authenticator resolves to invaldiation
        2) is not authenticated
        3) returns a resolving promise
        4) clears its content
        5) clears the store
        6) does not trigger the "sessionInvalidationFailed" event
        7) triggers the "sessionInvalidationSucceeded" event
      when the authenticator rejects invalidation
        ✓ stays authenticated
        8) "before each" hook

  87 passing (1s)
  8 failing

  1) Session authentication when the authenticator rejects authentication does not trigger the "sessionAuthenticationSucceeded" event:
     Uncaught Error: Assertion Failed: error (http://localhost:8000/test/vendor/ember-1.9.1.js:3902)

  2) Session invalidation when the authenticator resolves to invaldiation is not authenticated:
     Error: Assertion Failed: Session#invalidate requires the session to be authenticated
      at http://localhost:8000/test/vendor/ember-1.9.1.js:3902
      at http://localhost:8000/tmp/ember-simple-auth.amd.js:1049
      at http://localhost:8000/tmp/ember-simple-auth-tests.amd.js:972
      at http://localhost:8000/test/vendor/mocha.js:4323
      at http://localhost:8000/test/vendor/mocha.js:4724
      at http://localhost:8000/test/vendor/mocha.js:4815
      at next (http://localhost:8000/test/vendor/mocha.js:4649)
      at http://localhost:8000/test/vendor/mocha.js:4659
      at next (http://localhost:8000/test/vendor/mocha.js:4597)
      at http://localhost:8000/test/vendor/mocha.js:4621
      at http://localhost:8000/test/vendor/mocha.js:4338
      at next (http://localhost:8000/test/vendor/mocha.js:4622)
      at http://localhost:8000/test/vendor/mocha.js:4626
      at timeslice (http://localhost:8000/test/vendor/mocha.js:5733)

  3) Session invalidation when the authenticator resolves to invaldiation returns a resolving promise:
     Error: Assertion Failed: Session#invalidate requires the session to be authenticated
      at http://localhost:8000/test/vendor/ember-1.9.1.js:3902
      at http://localhost:8000/tmp/ember-simple-auth.amd.js:1049
      at http://localhost:8000/tmp/ember-simple-auth-tests.amd.js:979
      at http://localhost:8000/test/vendor/mocha.js:4323
      at http://localhost:8000/test/vendor/mocha.js:4724
      at http://localhost:8000/test/vendor/mocha.js:4815
      at next (http://localhost:8000/test/vendor/mocha.js:4649)
      at http://localhost:8000/test/vendor/mocha.js:4659
      at next (http://localhost:8000/test/vendor/mocha.js:4597)
      at http://localhost:8000/test/vendor/mocha.js:4621
      at http://localhost:8000/test/vendor/mocha.js:4338
      at next (http://localhost:8000/test/vendor/mocha.js:4622)
      at http://localhost:8000/test/vendor/mocha.js:4626
      at timeslice (http://localhost:8000/test/vendor/mocha.js:5733)

  4) Session invalidation when the authenticator resolves to invaldiation clears its content:
     Error: Assertion Failed: Session#invalidate requires the session to be authenticated
      at http://localhost:8000/test/vendor/ember-1.9.1.js:3902
      at http://localhost:8000/tmp/ember-simple-auth.amd.js:1049
      at http://localhost:8000/tmp/ember-simple-auth-tests.amd.js:989
      at http://localhost:8000/test/vendor/mocha.js:4323
      at http://localhost:8000/test/vendor/mocha.js:4724
      at http://localhost:8000/test/vendor/mocha.js:4815
      at next (http://localhost:8000/test/vendor/mocha.js:4649)
      at http://localhost:8000/test/vendor/mocha.js:4659
      at next (http://localhost:8000/test/vendor/mocha.js:4597)
      at http://localhost:8000/test/vendor/mocha.js:4621
      at http://localhost:8000/test/vendor/mocha.js:4338
      at next (http://localhost:8000/test/vendor/mocha.js:4622)
      at http://localhost:8000/test/vendor/mocha.js:4626
      at timeslice (http://localhost:8000/test/vendor/mocha.js:5733)

  5) Session invalidation when the authenticator resolves to invaldiation clears the store:
     Error: Assertion Failed: Session#invalidate requires the session to be authenticated
      at http://localhost:8000/test/vendor/ember-1.9.1.js:3902
      at http://localhost:8000/tmp/ember-simple-auth.amd.js:1049
      at http://localhost:8000/tmp/ember-simple-auth-tests.amd.js:999
      at http://localhost:8000/test/vendor/mocha.js:4323
      at http://localhost:8000/test/vendor/mocha.js:4724
      at http://localhost:8000/test/vendor/mocha.js:4815
      at next (http://localhost:8000/test/vendor/mocha.js:4649)
      at http://localhost:8000/test/vendor/mocha.js:4659
      at next (http://localhost:8000/test/vendor/mocha.js:4597)
      at http://localhost:8000/test/vendor/mocha.js:4621
      at http://localhost:8000/test/vendor/mocha.js:4338
      at next (http://localhost:8000/test/vendor/mocha.js:4622)
      at http://localhost:8000/test/vendor/mocha.js:4626
      at timeslice (http://localhost:8000/test/vendor/mocha.js:5733)

  6) Session invalidation when the authenticator resolves to invaldiation does not trigger the "sessionInvalidationFailed" event:
     Error: Assertion Failed: Session#invalidate requires the session to be authenticated
      at http://localhost:8000/test/vendor/ember-1.9.1.js:3902
      at http://localhost:8000/tmp/ember-simple-auth.amd.js:1049
      at http://localhost:8000/tmp/ember-simple-auth-tests.amd.js:1008
      at http://localhost:8000/test/vendor/mocha.js:4323
      at http://localhost:8000/test/vendor/mocha.js:4724
      at http://localhost:8000/test/vendor/mocha.js:4815
      at next (http://localhost:8000/test/vendor/mocha.js:4649)
      at http://localhost:8000/test/vendor/mocha.js:4659
      at next (http://localhost:8000/test/vendor/mocha.js:4597)
      at http://localhost:8000/test/vendor/mocha.js:4621
      at http://localhost:8000/test/vendor/mocha.js:4338
      at next (http://localhost:8000/test/vendor/mocha.js:4622)
      at http://localhost:8000/test/vendor/mocha.js:4626
      at timeslice (http://localhost:8000/test/vendor/mocha.js:5733)

  7) Session invalidation when the authenticator resolves to invaldiation triggers the "sessionInvalidationSucceeded" event:
     Error: Assertion Failed: Session#invalidate requires the session to be authenticated
      at http://localhost:8000/test/vendor/ember-1.9.1.js:3902
      at http://localhost:8000/tmp/ember-simple-auth.amd.js:1049
      at http://localhost:8000/tmp/ember-simple-auth-tests.amd.js:1022
      at http://localhost:8000/test/vendor/mocha.js:4323
      at http://localhost:8000/test/vendor/mocha.js:4724
      at http://localhost:8000/test/vendor/mocha.js:4815
      at next (http://localhost:8000/test/vendor/mocha.js:4649)
      at http://localhost:8000/test/vendor/mocha.js:4659
      at next (http://localhost:8000/test/vendor/mocha.js:4597)
      at http://localhost:8000/test/vendor/mocha.js:4621
      at http://localhost:8000/test/vendor/mocha.js:4338
      at next (http://localhost:8000/test/vendor/mocha.js:4622)
      at http://localhost:8000/test/vendor/mocha.js:4626
      at timeslice (http://localhost:8000/test/vendor/mocha.js:5733)

  8) Session invalidation "before each" hook:
     Uncaught Error: Assertion Failed: error (http://localhost:8000/test/vendor/ember-1.9.1.js:3902)

>> 8/95 tests failed (1.36s)
Warning: Task "mocha:test" failed. Use --force to continue.

Aborted due to warnings.

At least part of the problem we were experiencing is due to ember-simple-auth/packages/ember-simple-auth/lib/simple-auth/session.js:171 rejecting the promise with the error object. This seems to cause ember to try and log the error and throwing a EmberError when an assertion fails. Removing the error object from the reject call fixes 5 tests.

But that's actually needed so the error propagates correctly ;)

More of an FYI into my investigation. :P

Sure, it's the same in this beforeEach - if the 'error' argument is removed it doesn't fail right there but of course the assertion here fails.

It might need to be fixed in the authenticator libraries? I notice I get the same results if I change ember-simple-auth-oauth2/lib/simple-auth-oauth2/authenticators/oauth2.js:163-165 to
Ember.run(function() {
    reject();
});

previously
Ember.run(function() {
    reject(xhr.responseJSON || xhr.responseText);
});

Yeah, but that cannot be removed as the error needs to propagate.

There seem to be errors with earlier versions of Ember already - I wonder why it was working before... Help would be greatly appreciated with this ;)
The best way to run the test locally is to run grunt server and the open http://localhost:8000/test/ (which can also be run with certain versions of Ember, jQuery etc., e.g. http://localhost:8000/test/?ember=1.8.1&jQuery=2.1.3&handlebars=1.3.0 - see .travis.yml for the full matrix).

As far as I can tell, it's the propagation that is the issue with Ember. It sees the rejected promise with it's reason and tries to publish it. RSVP.onerrorDefault checks if there is an error and, in testing mode, calls Logger.error(error.stack); on the object. Since this object has not stack property, it fails. I have tried overriding onerror and this fixes it when running manually, but I still get the error in test mode due to the testing path in RSVP.onerrorDefault

I see. Can we maybe replace RSVP.onerrorDefault for the runs somehow?

FYI, I'm also getting this error after sessionAuthenticationFailed is fired. I'm on Ember 1.9.1 and Ember Simple Auth 0.7.2. Looks like Logger.error(error.stack); is the default in RSVP.onerrorDefault, not just in testing mode.

@elidupuis didn't mean to imply that it wasn't happening in both modes, but you can override the orerror handler running normally, but not in testing mode.
RSVP.onerrorDefault = function (error) {
      if (error && error.name !== 'TransitionAborted') {
        if (Ember.testing) {
          // ES6TODO: remove when possible
          if (!Test && Ember.__loader.registry[testModuleName]) {
            Test = requireModule(testModuleName)['default'];
          }

          if (Test && Test.adapter) {
            Test.adapter.exception(error);
            Logger.error(error.stack);
          } else {
            throw error;
          }
        } else if (Ember.onerror) {
          Ember.onerror(error);
        } else {
          Logger.error(error.stack);
          Ember.assert(error, false);
        }
      }
    };

To override you can use Ember.onerror = Ember.k

@marcoow not that I can see

@chrisvdp thanks for the tip. I added an Ember.onerror implementation and I'm no longer getting this error.

fixed

How was this issue fixed? I'm still seeing this error.


Fix gizmo activation when click happened not over gizmo control.

Fix issue where gizmo gets activated by moving mouse over the gizmo with mouse button pressed, for example when dragging another UI item.
Also define IMGUI_DEFINE_MATH_OPERATORS only when it was not defined. Avoids warnings when said define is defined by build system.

Thanks rokups!


[embedded] Print function name + class name when missing loc in 'non-final generic fuctions' diagnostic

Just adding a fallback in case we're missing source location when printing this diagnostic:
<unknown>:0: error: classes cannot have non-final generic fuctions in embedded Swift

@swift-ci please test


feat: include anchor tag for problem, video links (FC-0051)

Adding links to problems and videos from the course dashboard will provide useful context when looking at charts of problem responses and video views. One way of achieving this in Superset is to provide the HTML as part of the SQL query result.
An example of the generated anchor tag can be found in the test for the a_tag macro.

@SoryRawyer 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


@squoosh/cli crash in conversion to jxl

Describe the bug
Converting to JXL with cli crashes with error JXL_CHECK: bytes_.get().
PS C:\Temp\test\jxl slow sq> squoosh-cli.cmd --jxl "{}" .\weiß.png
⠋ (node:8188) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 25 unpipe listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)
(node:8188) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 25 error listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(node:8188) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 25 close listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
(node:8188) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 25 finish listeners added to [WriteStream]. Use emitter.setMaxListeners() to increase limit
0/1 ⠹ ▐▨▨▨▨▨╌╌╌╌╌▌ Encoding (24 threads)
 .\weiß.png: 3.53KB/src/node_modules/jxl/lib/jxl/image.cc:102: JXL_CHECK: bytes_.get()
node:internal/process/promises:279
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "unreachable".] {
  code: 'ERR_UNHANDLED_REJECTION'
}

Node.js v17.5.0

To Reproduce
Steps to reproduce the behavior:

run  squoosh-cli.cmd --jxl "{}" .\weiß.png

Expected behavior
A working conversion to jxl, like with cjxl or vips. Like the attached weiss-cjxl.
Version:

OS w/ version: Microsoft Windows [Version 10.0.22000.527]
Browser w/ version: n/a
Node version :v17.5.0
npm version: 8.4.1

Additional context, screenshots, screencasts

weiß-cjxl.zip

Unfortunately, due to a few people leaving the team, and staffing issues resulting from the current economic climate (ugh), the CLI and libsquoosh packages are no longer actively maintained. I know that sucks, but there simply isn't the time & people to work on this. If anyone from the community wants to fork it, you have my blessing. The squoosh.app web app will continue to be supported and improved.


Add an argument for the case that does not include callback_end in the message flow.

The time between callback_end and callback_start may appear to go back.
This makes it difficult to understand, so make it possible to switch between them with an argument.

fixed: v0.2