after i upgrade to Flutter 1.7.8+hotfix.4 • channel stable, after clicking on TextField the keyboard can't load

Steps to Reproduce

...
...
...

Logs

Which device OS?

I tested it on android Pie
On Thu, 25 Jul 2019, 8:06 pm Robbie Boyd<EMAIL_ADDRESS>wrote:

Which device OS?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/36918?email_source=notifications&email_token=AH3IMWUNEE3FYWQ47RJWXK3QBGQOJA5CNFSM4IGW4OR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2ZM3TI#issuecomment-515034573,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH3IMWQHKHGSU4HKRJONPDTQBGQOJANCNFSM4IGW4ORQ
.

We're not seeing this issue. Please provide the output of flutter doctor and a small self-contained app that demonstrates the problem and we'll look into it. Note also: https://gist.github.com/ is a useful way to share the code.

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, v1.7.8+hotfix.4, on Microsoft Windows [Version 10.0.17763.615], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[√] Android Studio (version 3.4)
[√] VS Code, 64-bit edition (version 1.36.1)
[√] Connected device (1 available)
• No issues found!

This is when i clicked on Textfield
W/InputMethodManager(10092): startInputReason = 3
I/InputMethodManager(10092): showSoftInput
I/InputMethodManager(10092): mServedView =com.optistech.meetingv2flutteradmin;view =com.optistech.meetingv2flutteradmin;flags =0
I/HwSecImmHelper(10092): mSecurityInputMethodService is null
E/SpannableStringBuilder(10092): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
E/SpannableStringBuilder(10092): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
E/SpannableStringBuilder(10092): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
E/SpannableStringBuilder(10092): SPAN_EXCLUSIVE_EXCLUSIVE spans cannot have a zero length
I/HwSecImmHelper(10092): mSecurityInputMethodService is null
D/HwAppInnerBoostImpl(10092): asyncReportData com.optistech.meetingv2flutteradmin,2,1,1,0 interval=236

Thanks for the console log messages! Unfortunately to address this issue we'll really need a test case (we haven't seen the problem in internal testing): https://github.com/flutter/flutter/issues/36918#issuecomment-515087656

I have the same issue, and in my case, the problem happens if the TextField is inside nested navigator widget.

I'm getting the same error only on fields that are inside a page that was presented by Navigator.
[✓] Flutter (Channel stable, v1.7.8+hotfix.4, on Mac OS X 10.13.6 17G7024, locale en-PT)
    • Flutter version 1.7.8+hotfix.4 at /Users/victor/development/flutter
    • Framework revision 20e59316b8 (2 weeks ago), 2019-07-18 20:04:33 -0700
    • Engine revision fee001c93f
    • Dart version 2.4.0

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
    • Android SDK at /Users/victor/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 10.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.1, Build version 10B61
    • CocoaPods version 1.7.3

[✓] iOS tools - develop for iOS devices
    • ios-deploy 1.9.4

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 37.0.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] Connected device (1 available)
    • VOG L29 • 22X7N19315033169 • android-arm64 • Android 9 (API 28)

• No issues found!

@HansMuller @vagrantrobbie tested flutter master and dev versions and cloned / ran project: https://github.com/flutter/plugins/tree/master/packages/webview_flutter/example
Console doesn't have anything interesting, posting flutter doctor  -v output:
[✓] Flutter (Channel master, v1.8.4-pre.116, on Mac OS X 10.14.6 18G84, locale en-EE)
    • Flutter version 1.8.4-pre.116 at /Users/mlamp/_DEV/flutter
    • Framework revision 0564f0a812 (2 hours ago), 2019-08-06 20:08:09 +0200
    • Engine revision 7f67b9f0dc
    • Dart version 2.5.0 (build 2.5.0-dev.1.0 8cd01287b4)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
    • Android SDK at /Users/mlamp/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 10.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.3, Build version 10G8
    • CocoaPods version 1.7.2

[✓] Android Studio (version 3.4)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 36.1.1
    • Dart plugin version 183.6270
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1343-b01)

[✓] VS Code (version 1.36.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.3.0

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 10 (API 29) (emulator)

• No issues found!

Also little demo:

Duplicate of https://github.com/flutter/flutter/issues/19718
The keyboard support landed just recently and is not yet on stable, you can try switching to the master channel.
Note that the keyboard support is still experimental and there are a few known bugs (see the README for the webview plugin).
(and is still experimental with known bugs),


Request for help using versioningit in conda-forge

Comment:
I am using versioningit to dynamically set the version in this package, but when it is pulled from conda-forge, the version is set to the default (0.0.0).
I am trying to fix this in https://github.com/conda-forge/grits-feedstock/pull/10. I have set the recipe to pull the whole repo (so the git info is also pulled for versioningit) and added  versioningit to the host requirements as noted in: https://versioningit.readthedocs.io/en/stable/notes.html#restrictions-caveats
However, my test still does not pass (see recipe/run_test.py). Any guidance would be greatly appreciated!

Resolved! I thought I had pushed the change from tarball to repo, but I hadn't...


Architecture subsection of Explanation section

Improve the Introduction and Explanation sections project

Section
Sub-section
Technical Writer

Explanations
Architecture
Joseph Mawa

This  is Architecture sub-section of the Explanations section

@chris-4444 I would like you to once go through the PR, and approve when you think it's ready to get merged.


Fixed all SwiftLint(0.31.0)-related warnings

:rocket: It seems like SwifterSwift was using some outdated SwiftLint syntax for disable next and they were added in wrong places (not just above the line they were intended to apply to).
Checklist

[x] I checked the Contributing Guidelines before creating this request.
[ ] New extensions are written in Swift 4.
[ ] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+.
[ ] I have added tests for new extensions, and they passed.
[ ] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[ ] All extensions are declared as public.
[ ] I have added a changelog entry describing my changes.

          1 Warning

:warning:
The source files have been modified. Please consider adding a CHANGELOG entry if necessary.

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 536 tests, with 0 failures (0 unexpected) in 18.195 (20.215) seconds

:book:
tvOS: Executed 502 tests, with 0 failures (0 unexpected) in 10.071 (11.856) seconds

:book:
macOS: Executed 366 tests, with 0 failures (0 unexpected) in 1.179 (1.503) seconds

  Generated by :no_entry_sign: Danger

Thank you for contributing to SwifterSwift! I've invited you to join the SwifterSwift GitHub organization - no pressure to accept! If you'd like more information on what that means, check out our contributing guidelines. Feel free to reach out if you have any questions! 😃


can't stop uv loop

#include <thread>
#include <libuv/uv.h>
uv_loop_t *loop;
bool stop = false;

void run()
{
	while (!stop) {
		uv_run(loop, UV_RUN_DEFAULT);
	}
}
void print_progress(uv_async_t *handle) {

}
int main()
{
        loop = new uv_loop_t;
	uv_loop_init(loop);
	uv_async_t *async = new uv_async_t;
	uv_async_init(loop, async, print_progress);

        std::thread t(run);

        while (1)
	{
		char c = getchar();
		if (c == 'q' || c == 'Q')
			break;
	};
	stop = true;
	uv_stop(loop);
	t.join();
	uv_close((uv_handle_t*)async, NULL);

        uv_loop_close(loop);

	delete async;
	async = NULL;
	delete loop;
	loop = NULL;

	return 0;
}

Version: 1.12.0
Platform: Windows

Just a simple sample. But the thread can't be stopped after  adding an async to the loop.
Why?

Please post questions to https://github.com/libuv/help/issues, this tracker is strictly for reporting bugs.


About page doesn't flow well

I think that using a card-based layout where each employee is given a card with a picture and some info is more appealing (visually) and works better on mobile devices than the current solution.
Information about cards can be found at this site, or the basic usage is pasted below:

               Card Title
I am a very simple card. I am good at containing small bits of information.               I am convenient because I require little markup to use effectively.

               This is a link               This is a link

This is a card based approach!


Atomic CSR read-write difficult to implement efficiently

Our experience in designing the SweRV core has found that atomic read-write CSR instructions are inefficient, because their two destinations creates trouble with the pipeline design.
We would like to see a new "Z" extension that includes solely those CSR instructions covered by the pseudo-instructions: CSRR, CSRW, CSRWI, CSRS, CSRSI, CSRC and CSRCI.
Why does software have to see the old value when it is modifying the value of a CSR?  Could the CSR instructions not covered by the above pseudo-instructions be deprecated?

The software rationale is that the instructions, as specified, are atomic with respect to interrupts and other events that can change the CSR's value.  Splitting it up into the constituent parts would destroy the atomicity property.
The microarchitectural rationale is that having two destinations does not create a structural hazard, since the CSRs are (almost necessarily) a different bank of registers from the x-registers.  Most of the designs I have worked on implement the CSR read-modify-write sequence in a separate unit at the pipeline's commit stage, so there is little interaction with the design of the integer pipeline.

Why does software have to see the old value when it is modifying the value of a CSR?

Trap handlers currently depend on being able to swap a *scratch CSR with a general-purpose x register in one instruction.
Aside from that, it is sometimes convenient (though not an imperative) to be able to read the old value to save it for later restoring, at the same time one is changing a CSR.
You may have a valid point about the implementation impact (I can't say for sure), but the current spec for CSRs is probably too entrenched now to change in this way, regardless.

If you perform CSR reads in the same pipeline stage you perform writes, or if you stall until older CSR writes to complete, there's no need to bypass CSR writes.  It sounds like you came to the same conclusion, and rather than calling it "not great", I'd call it a perfectly reasonable thing to do.  The performance of CSR reads isn't a first-order concern, and removing bypass paths that don't contribute much to IPC is standard operating procedure.
By similar logic, executing CSR accesses at commit need not complicate register renaming in an OoO pipeline.
Atomicity is an issue, because with the reduced set of operations proposed, some things that used to take only one CSR access now take two, and an interrupt can occur in between.
In any case, JohnH is right to remark that "the current spec for CSRs is probably too entrenched now to change in this way."  Lots of software is distributed in binary form that makes use of them.  Minutiae in the privileged architecture would've been designed differently if these instructions weren't assumed to be present.

btw, when you say "atomicity" are you referring to the ability to do an atomic swap (gpr,csr) that is possible with these dual-dest CSR instructions?  Or something else?
Presumably you could disable interrupts IE=0, do 2 simpler instructions, and then re-enable IE=1.  Would that eliminate the atomicity problem w.r.t. interrupts?  btw, these 4 instructions would still run faster than the complex dual-dest CSR.  Especially as pipe gets deeper.  unpiping is typically a presync / postsync operation given no bypasses. presync since data you need may be in flight.  postsync since you write at commit.
btw, curious to know how the dual-dest CSR made it into the ISA?   was it there from day 1 or did it get introduced at some point?
IMO, this dual-dest CSR stuff should be removed from the ISA.  It really doesn't fit in with the rest of the RISCV instructions.
You sure it's too late?
:-)

Yeah, the disable-interrupts + non-atomic sequence + re-enable-interrupts sequence generally suffices.  But often software doesn't know whether interrupts are currently enabled (e.g. because of nested locking), and even the sequence to disable/re-enable interrupts becomes more expensive if you don't have the full CSRRx instructions! :-( The sequence looks something like this:
csrrci t0, sstatus, 2 # disable interrupts and remember old interrupt-enable state in t0
... # critical section
csrw sstatus, t0 # restore interrupt-enable state

But without csrrci it becomes something like
csrr t0, sstatus
csrci sstatus, 2
... # critical section
andi t0, t0, 2 # can't simply use csrw sstatus, t0, because sstatus might
csrs sstatus, t0 # have been changed between instructions 1 and 2

You can make the case that even this is acceptable.  But either way, the extra cruft starts to pile up, with an attendant increase in code size.
As to when they were introduced, the CSRRW instruction was added in July 2013 (under a different name), and the full battery of CSR instructions was added in a Sept. 2013 revision.  So, not quite day one, but over five years ago.  So... yes, I'm pretty sure :)

Ok so be it.  I suspect for future high end  RISCV cores you will see the dual dest CSR microcoded into 2 simpler micro ops.  HW will guarantee atomicity with respect to interrupts.  But all pipelined.  Assuming no synchronization is needed for the CSR operation.

Yes, I think that is plausible - at least for the scratch CSRs, which are attractive to rename.


centos 环境 使用pip安装依赖报错

1、pip install -i https://pypi.org/simple -r requirements.txt
2、pip install -i https://mirrors.aliyun.com/pypi/simple/ -r requirements.txt
两个命令尝试过，都报如下错误：
Looking in indexes: https://mirrors.aliyun.com/pypi/simple/
Collecting SwissArmyTransformer>=0.3.6 (from -r requirements.txt (line 1))
Using cached https://mirrors.aliyun.com/pypi/packages/35/72/33d121b3a54fa1bb42fb3f5796e47be650dfe9247b83aba09a0cefafc378/SwissArmyTransformer-0.3.6-py3-none-any.whl (2.4 MB)
Requirement already satisfied: torch>1.10.0 in /home/tushen/anaconda3/envs/python39/lib/python3.9/site-packages (from -r requirements.txt (line 2)) (2.0.0)
Collecting torchvision (from -r requirements.txt (line 3))
Downloading https://mirrors.aliyun.com/pypi/packages/41/9e/8809e45a084680394e8d219fcf8a2c0eed2dddf1ec0a7968f4052826a6e9/torchvision-0.15.2-cp39-cp39-manylinux1_x86_64.whl (6.0 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 6.0/6.0 MB 280.2 kB/s eta 0:00:00
Requirement already satisfied: transformers>=4.27.1 in /home/tushen/anaconda3/envs/python39/lib/python3.9/site-packages (from -r requirements.txt (line 4)) (4.27.1)
Requirement already satisfied: mdtex2html in /home/tushen/anaconda3/envs/python39/lib/python3.9/site-packages (from -r requirements.txt (line 5)) (1.2.0)
Requirement already satisfied: gradio in /home/tushen/anaconda3/envs/python39/lib/python3.9/site-packages (from -r requirements.txt (line 6)) (3.28.0)
Collecting deepspeed (from SwissArmyTransformer>=0.3.6->-r requirements.txt (line 1))
Using cached https://mirrors.aliyun.com/pypi/packages/9e/6a/ce4e9afcf36f242f55bf2c91fa1366b26f0f40653d98a96c0f64b7154c12/deepspeed-0.9.2.tar.gz (779 kB)
Preparing metadata (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py egg_info did not run successfully.
│ exit code: 1
╰─> [8 lines of output]
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "/tmp/pip-install-2kfzckpb/deepspeed_c3e7c332f93d4376aa90c71fd1a48d84/setup.py", line 81, in
cuda_major_ver, cuda_minor_ver = installed_cuda_version()
File "/tmp/pip-install-2kfzckpb/deepspeed_c3e7c332f93d4376aa90c71fd1a48d84/op_builder/builder.py", line 41, in installed_cuda_version
assert cuda_home is not None, "CUDA_HOME does not exist, unable to compile CUDA op(s)"
AssertionError: CUDA_HOME does not exist, unable to compile CUDA op(s)
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
× Encountered error while generating package metadata.
╰─> See above for output.
note: This is an issue with the package mentioned above, not pip.
hint: See above for details.

你需要先安装cuda，可以搜一下conda 安装cudatoolkit的方法。

现在安装可以了。谢谢您


Change ? to another symbol

It seems like Dotty will get native type lambdas. The plan there is to use F[_] as a short-hand syntax for the type lambda [X] => F[X] and F[?] to be the wildcard syntax which unfortunately is different to how the ? is used in kind-projector.
In https://github.com/lampepfl/dotty/issues/5379 there's a discussion of doing the swap incrementally in Scala 3.0 - 3.3, but imo that would lead to unnecessary churn and confusion, so I was wondering if kind-projector could preemptively replace the ? by another symbol so that until Dotty is out the ? is free to use for wildcards.
Maintainers' opinions are welcome here or in the above ticket 😃

Thank you for letting us know! I think the proposed syntax (F[?] for existential, F[_] for [X] => F[X]) is more intuitive. It will probably be a long and painful transition for projects, but I view it positively overall.
The question for kind projector is, what symbol do we use (alongside ?) in shorthand syntax for type lambdas.
In math, – (en-dash) is commonly used for this purpose, as in

Hom(A,–) maps each object X in C to the set of morphisms, Hom(A, X).

The problem is that the en-dash is not a valid Scala identifier. Also, it is not easily typed on a keyboard.
So I suggest to use -- (double minus), which is also the TeX way to typeset an en-dash.

See #91 where I went with *.


Transactions: if you enable the TransactionCoordinator force delete topic leaves the broker in bad state

Describe the bug
I found this problem while testing Pulsar 2.9.0rc3 and running the unit tests of Pulsar JMS (http://github.com/datastax/pulsar-jms).
When you enable the TransactionCoordinator deleting a topic forcefully leaves the broker in such a bad state that it is no more possible to consume data from other topics.
To Reproduce

Start one Broker and setup Transactions
Create one topic in public/default
Create one subscription on the topic
Delete the topic with "force" = true
Create another topic with a different name (in the same namespace)
Create one subscription on the second topic
Produce a message to the second topic
Try to receive a message from the second topic, Consumer.receive() will hang forever

Expected behavior
The second topic works well
Additional context
The problem is present in 2.9.0rc3 but NOT in Pulsar 2.8.1
Running on JDK8/Mac

@congbobo184 PTAL

@congbobo184  it may be a regression introduced by #11934
Here I see that a message is being sent,
that's the main difference in the deleteTopic code path in case of force=true and transactions enabled
https://github.com/apache/pulsar/blob/8551868468327cc04ca6d4e9fe4bcb718ad38cbc/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentTopic.java#L1135

@gaoran10 PTAL as well


fix: Stripe payment not working

The previous exchange rate conversion API has been tested and is no longer free. It now requires an API Key.
This PR has been replaced with the currently available free exchange rate conversion API.

how to set up stripe? I can't find any tutorial or doc

@TheMrJC what is the stripe webhook callback url? I can't find any doc about this.

@TheMrJC what is the stripe webhook callback url? I can't find any doc about this.

Read the official Stripe documentation carefully.

@TheMrJC what is the stripe webhook callback url? I can't find any doc about this.

Read the official Stripe documentation carefully.

I think the webhook url should be provided by v2board side
e.g. if v2board site is host at https://domain.com
the webhook should be a specific path, e.g. https://domain.com/payment/stripe/notice ?
But I can't find any doc about the callback path,  and there are several payments method for stripe, are they share the same webhook url? or different path for each method?

@TheMrJC what is the stripe webhook callback url? I can't find any doc about this.

Read the official Stripe documentation carefully.

I think the webhook url should be provided by v2board side
e.g. if v2board site is host at https://domain.com
the webhook should be a specific path, e.g. https://domain.com/payment/stripe/notice ?
But I can't find any doc about the callback path,  and there are several payments method for stripe, are they share the same webhook url? or different path for each method?

After you add the payment method in v2board, you will find that a callback address is automatically generated.

@TheMrJC what is the stripe webhook callback url? I can't find any doc about this.

Read the official Stripe documentation carefully.

I think the webhook url should be provided by v2board side
e.g. if v2board site is host at https://domain.com
the webhook should be a specific path, e.g. https://domain.com/payment/stripe/notice ?
But I can't find any doc about the callback path,  and there are several payments method for stripe, are they share the same webhook url? or different path for each method?

After you add the payment method in v2board, you will find that a callback address is automatically generated.

ok~~  thanks, finally got the url
the trick is to get a webhook secret, you need to fill a webhook url in advance. so I will keep finding the url before add a payment method.

@missuo I tried this new stripeCheckout.php, but it only shows error with 500 status, is there any way to show the error details?

I got one interesting question, if set a price with a small number, e.g. ￥0.1 or ￥1，the api/v1/user/order/checkout will fail with an error.
How to debug this?  the error message does not show details.  is this a stripe problem or v2board setting?

I can assure you that this PR fixes the bug where Stripe can't process payments. As for the issues you mentioned, you should try to solve them yourself. @lslzl3000

1.7.4版本，在輸入信用卡號的時候，出錯。umi.js?v=<IP_ADDRESS>1103823832:1  Unsupported prop change on Elements: You cannot change the stripe prop after setting it. 無法提交並閉環支付

Hello I tried to install two front panels in one VPS by Aappnel The problem I encounter is that users' traffic is recorded irregularly in both databases and both fronts. That is, if user number 9 is online from the first panel, it will show him online in the second panel, even if no node or subscription is defined for the second panel. Can you guide me how to install several fronts on one VPS without any problems?
I am using V2Board v1.7.2
I couldn't open a new request, that's why I left a comment here
Thank you for helping me

数据库备份了，面板迁移到新服务器，然后导入数据库，之前部分老用户，无法登录，报错我们遇到一些问题，该如何解决？


Add missing requireIPv6PodCIDR setting

Signed-off-by: Neil Wilson<EMAIL_ADDRESS>

test-me-please

net-next hit https://github.com/cilium/cilium/issues/12511.

net-next hit https://github.com/cilium/cilium/issues/12511.

retest-net-next

retest-net-next

retest-runtime

retest-runtime

retest-gke

retest-gke


feat: add --ssl-insecure-skip-verify flag which we can set in test sc…

…enarious and prevents sso proxy pods failing to start

Default behaviour is still the recommended secure way but this gives us the option in CI scenarios to skip the check and verify the environment.

/lgtm


chore: fix module path used to determine terraform plugin SDK version

A recent change to differentiate terraform-plugin-sdk traffic from terraform-plugin-framework traffic used the wrong Go module path for the SDK.  This fixes it so we can accurately track plugin-sdk version usage.

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

Comparison is base (a2797d8) 63.11% compared to head (5dea417) 55.48%.
Report is 57 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #579      +/-   ##
==========================================
- Coverage   63.11%   55.48%   -7.64%
==========================================
  Files          94       93       -1
  Lines       18250    18136     -114
==========================================
- Hits        11519    10063    -1456
- Misses       6299     7747    +1448
+ Partials      432      326     -106

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


Test error               ValueError: too many values to unpack (expected 2)

loading pretrained crnn model from pretrained/crnn.pth
loading pre-trained moran model from pretrained/moran.pth
recognizer_path: None
loading pretrained crnn model from pretrained/crnn.pth
Traceback (most recent call last):
File "E:\BasicSTISR-master\BasicSTISR-master\main.py", line 45, in
main(config, args)
File "E:\BasicSTISR-master\BasicSTISR-master\main.py", line 14, in main
Mission.train()
File "E:\BasicSTISR-master\BasicSTISR-master\interfaces\super_resolution.py", line 188, in train
cascade_images, pre_mask = model_list[0](cascade_images, label_vecs_final.detach())
ValueError: too many values to unpack (expected 2)

"tatt", "tpgsr", "tbsrn"       Using these algorithms will cause an error. Changing TSRN to this will allow normal training.


[Removal]: Wide Bronze Pigeon

Hotspot Name
Wide Bronze Pigeon
Hotspot b58 Address
11rtLKSiqDg1YchzohYnNUXFjfaHvQxsRkwh7wCmuhTUrM2HcZx
Discord Handle
No response
Hotspot Manufacturer
PantherX
Removal Reason
I bought it from second hand, and the hotspot has been stopped about two months, I have no idea why it appeared in denylist, you can check the status.
Modifications
No
Extra forwarders
No
Extra antennas
No
Additional Information
No response

the issue has been kept open for about 1 months, can anyone review the case, any comments?  @abhay  @madninja  @Vagabond   @PharkMillups  @6CornerDefender


LDAP Authentication not working

Summary

Kong version : 2.5.0
A concise summary of the bug.

I'm trying to setup the LDAP Authentication in Kong Gateway but i'm getting always : "message":"Invalid authentication credentials"
I'm using an online LDAP test server https://www.forumsys.com/tutorials/integration-how-to/ldap/online-ldap-test-server/
This server is accessible by ldapsearch but not with kong.
Steps To Reproduce

Install kong using docker image with postgres DB
Create service and route
Check that route is accessible without authentification
Setup LDAP Authentication:
curl -X POST http://localhost:8001/routes/{ROUTE}/plugins \  --data "name=ldap-auth"  \  --data "config.hide_credentials=true" \  --data "config.ldap_host= ldap.forumsys.com" \  --data "config.ldap_port=389" \  --data "config.start_tls=false" \  --data "config.ldaps=false" \  --data "config.base_dn=dc=example,dc=com" \  --data "config.verify_ldap_host=false" \  --data "config.attribute=cn" \  --data "config.cache_ttl=60" \  --data "config.header_type=ldap"
Try to access route using the credentials : euler:password (for exemple, you can see in the logs of ldapsearch i attached that this credentials are accessible)

`curl -i -X GET   --url http://localhost:8000/   --header 'Host: example.com' -H 'Authorization: ldap ZXVsZXI6cGFzc3dvcmQ='
HTTP/1.1 401 Unauthorized
Date: Wed, 21 Jul 2021 09:16:17 GMT
Content-Type: application/json; charset=utf-8
Connection: keep-alive
Content-Length: 52
X-Kong-Response-Latency: 178
Server: kong/2.5.0
{
"message":"Invalid authentication credentials"
}`
Additional Details & Logs
ldapsearch_logs.txt

This issue has been solved. The problem was in the config.attribute (i configured it to cn and i was giving uid.

I am facing the same issue. I changed the attribute to uid and it still did not work.
Can you please share what resolved your issue.
I have attached the configurations added on Kong Manager


Added contributing guidelines. Solves #157

Would you include information about linting as well?

Looks good to me.

Lets update this guide when we have real solution for linting task.

@tarlepp we have already have linting with gulp tslint.

Agree with @mgechev. It's here

Ok, so all should be ok now - right?

Looks good to me!

@tarlepp can you squash and push again ?

@tarlepp can you squash your commits into one ?

Damn, my git skills aren't so good - Tried to squashs those three commits to one, but now success. I'll make new clean PR for this later today.


[proposal] allow hooks_riverpod to wider access to flutter_hooks and riverpod classes and functions

I don't know if this is intended, but
hooks_riverpod: ^0.13.1 requires flutter_hooks: ^0.16.0 to access

HookWidget
useEffect
StateController

and probably many more,
it would be convenient to have these accessible from a single package
(sorry, for the wrong labels)

It could be easier to use, but not modular.


[EOSF-655] Use t-plus helper to add provider based logic to naming things.

Needs: https://github.com/CenterForOpenScience/ember-osf/pull/228
Tests will fail until that is merged and pinned here.
Ticket
https://openscience.atlassian.net/browse/EOSF-655
Purpose
Give the ability to change the "preprint" wording to something providers might prefer, such as "papers".
Changes
t helper is no longer used. Instead, t-plus takes its place. Also, any mention of preprints in user-facing strings (the ones seen on translation.js) uses {{preprintWords.preprint}} over preprint, {{preprintWords.Preprints}} over Preprints and so on.
Side effects
All new strings need to be defined using preprintWords, and t-plus needs to be used over t.

Try regenerating yarn.lock

Should be good once updated to use ember-osf with extended t helper.


Feature/add readme

The readme now talks about the general idea of the project as well as some details about implementation.
-Updated ReadMe

Great update. Glad we got everything done for our check in!


Tests are broken

From: http://build-eu-00.elastic.co/view/LS Plugins/view/LS Inputs/job/logstash-plugin-input-udp-unit/9/
Bundle complete! 2 Gemfile dependencies, 34 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.
Using Accessor#strict_set for specs
Run options: exclude {:redis=>true, :socket=>true, :performance=>true, :couchdb=>true, :elasticsearch=>true, :elasticsearch_secure=>true, :export_cypher=>true, :integration=>true, :windows=>true}
..F

Failures:

  1) LogStash::Inputs::Udp receive should receive events been generated
     Failure/Error: client.send("msg #{i}")
     SocketError:
       send: name or service not known
     # ./spec/support/client.rb:28:in `send'
     # ./spec/inputs/udp_spec.rb:32:in `events'
     # ./spec/inputs/udp_spec.rb:31:in `events'
     # ./spec/spec_helper.rb:12:in `input'
     # ./spec/inputs/udp_spec.rb:30:in `events'
     # ./spec/inputs/udp_spec.rb:42:in `(root)'

Finished in 0.631 seconds (files took 1.47 seconds to load)
3 examples, 1 failure

finally found the issue: register doesn't actually make the socket listen on the udp port, that happens during run, so it's possible that the test is sending data to a socket that hasn't been open yet

cool, good finding man! thanks a lot for taking this.

fixed by #12


Load Projects into Database

Art Club
Book Club
Front Desk - Family
Front Desk - Men
Front Desk - Women
On-Call Interpreter
One Time Group - Kid's Activity
One Time Group - Warehouse/Deep Clean
Palmer Court - Book Club
Palmer Court - Donation Room
Palmer Court - Special Events
Palmer Court - Study Night
Playroom
Preschool
Singles Program
Speaker's Bureau Assignment
Special Classes
Special Events
Teen Night Out
Warehouse

Loaded on Heroku through django administration


Move pkg/install/ to pkg/cluster/ and update the interface to be a cluster manager instead of installer

Which issue this PR addresses:
Related to #856
What this PR does / why we need it:
Moves pkg/install/'s Installer to be pkg/cluster/ manager and adds Interface. The cluster manager is created by cluster.New().
Test plan for issue:
This doesn't come with tests right now, but should be covered by others.
Is there any documentation that needs to be updated for this PR?
Don't think so?

@mjudeikis rebased

/azp run e2e

/azp run e2e


Prepare for wheel publishing (alpha patch version of 0.0.1)

Summary
Prepare the project so that we can publish a wheel with the library (as part of #175). Attempt to make sure we can still proceed with both building the library and the surrounding CLI.
In order to make this buildable as a wheel, I needed to restructure the code. So, the first commit moves files around and only changes 2 markdown links. The files are moved to get to a src/ layout. There are more benefits for a src/ layout than a flat
layout, such as:

documentation is easier to generate
we won't accidentally test against code that is different than what users would see
we can include only the source in the wheel, reducing PyPI bandwidth
it makes it clearer which parts of the repo go into the wheel and which ones are ancillary. Incidentally, we might now want to move the SLSA parts to another repo and maybe rename this one? We can do this at a later time.

Since we would need to change README.model_signing.md anyway once the API is ready, I have not updated it besides just fixing the image pointer.
I have deleted old files from when this was a POC. Since we're working on releasing the library, we no longer need those. The code in these files is already implemented in the library. What these files used to test is now in the test files.
The alternative to not moving the files to the root of the folder would have been to duplicate LICENSE, etc. inside the model-signing directory, so that packaging tools would see it. But we still needed to move files around to get to the src/ layout and to make documentation work correctly. So, it did not make sense to also duplicate LICENSE.
The second commit adds necessary stuff to pyproject.toml to build the wheel. I decided to use hatch -- that is, hatchling for the build backend and hatch as project manager.
The main benefit -- likely, not present in this PR -- is that using hatch allows us to have multiple environments for different usage scenarios. We can have one environment for tests, one for type checking, etc.
Another benefit is that hatch allows us to build C/C++ extensions (via plugins), so when we need to get extra performance or drop to C/C++ (e.g., for #201) we can just do it.
For this commit/PR, I just focused on making sure that hatch build builds the wheel and the tarball. As a bonus, hatch shell drops us into a virtual environment with the package locally installed, in an editable fashion: we can just edit the files and can immediately test the code without having to reinstall the wheel somewhere else. So, we get the benefits of testing exactly the wheel that is shipped to the users without having to have a separate virtual environment to install the wheel in, without having to manually manage that.
The wheel that gets built is minimal. Here's the corresponding tarball's contents (output of tar tf):
model_signing-0.0.1a0/model_signing/__init__.py
model_signing-0.0.1a0/model_signing/hashing/__init__.py
model_signing-0.0.1a0/model_signing/hashing/file.py
model_signing-0.0.1a0/model_signing/hashing/hashing.py
model_signing-0.0.1a0/model_signing/hashing/memory.py
model_signing-0.0.1a0/model_signing/manifest/__init__.py
model_signing-0.0.1a0/model_signing/manifest/manifest.py
model_signing-0.0.1a0/model_signing/serialization/__init__.py
model_signing-0.0.1a0/model_signing/serialization/serialization.py
model_signing-0.0.1a0/model_signing/serialization/serialize_by_file.py
model_signing-0.0.1a0/model_signing/serialization/serialize_by_file_shard.py
model_signing-0.0.1a0/model_signing/signature/__init__.py
model_signing-0.0.1a0/model_signing/signature/encoding.py
model_signing-0.0.1a0/model_signing/signature/fake.py
model_signing-0.0.1a0/model_signing/signature/key.py
model_signing-0.0.1a0/model_signing/signature/pki.py
model_signing-0.0.1a0/model_signing/signature/signing.py
model_signing-0.0.1a0/model_signing/signature/sigstore.py
model_signing-0.0.1a0/model_signing/signature/verifying.py
model_signing-0.0.1a0/model_signing/signing/__init__.py
model_signing-0.0.1a0/model_signing/signing/as_bytes.py
model_signing-0.0.1a0/model_signing/signing/empty_signing.py
model_signing-0.0.1a0/model_signing/signing/in_toto.py
model_signing-0.0.1a0/model_signing/signing/signing.py
model_signing-0.0.1a0/model_signing/signing/sigstore.py
model_signing-0.0.1a0/.gitignore
model_signing-0.0.1a0/LICENSE
model_signing-0.0.1a0/README.model_signing.md
model_signing-0.0.1a0/pyproject.toml
model_signing-0.0.1a0/PKG-INFO

This would require rebase on #279, #240 given that we have moved files around. It closes #192 given that all tests have been migrated. It closes #68 due to the same. Similarly, closes #182.
Given that the code has moved around, all CI fails at this point. Next steps (which is why this is draft right now) is to fix it.
Release Note
NONE (will add when ready to publish, also with CHANGELOG.md)
Documentation
NONE (will add when ready to publish, there's some TODO now to merge README.md files)

Can we exclude the .gitignore?

Yes, I somehow thought that that is the default, but it's not. Will rebase.

Can we exclude the .gitignore?

Yes, I somehow thought that that is the default, but it's not. Will amend + force push/rebase.

The answer is probably no:
https://hatch.pypa.io/latest/plugins/builder/sdist/#default-file-selection

The following files are always included and cannot be excluded:
/pyproject.toml
/hatch.toml
/hatch_build.py
/.gitignore or /.hgignore
Any defined readme file
All defined license-files

I was just going to paste that. Yeah, cannot be removed from sdits

also can i selfishly request this patch so the VSCode pytest integration still works with the new layout? As an added bonus it restores the ability to do pytest . to run the tests (for anyone with muscle memory).
diff --git a/pyproject.toml b/pyproject.toml
index 7b02f97..7691c99 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -62,6 +62,9 @@ installer = "pip"
 parallel = true
 randomize = true

+[tool.pytest.ini_options]
+pythonpath = "src"
+
 [tool.ruff]
 line-length = 80
 target-version = "py311"

(wrong click on the close button, sorry)

Ohh, good catch. Yes!


Should the name Label for Counter metrics always end in "_total"

While working on some of the OTel Collector test failures I found the PRW exporter ensuring that the __name__ attribute for all counter metrics ended in "_total" if it existed.  This definitely doesn't seem to be expected by these compliance tests, given the counter test uses a counter with no suffix and asserts that its __name__ label also has no suffix.
That said, there are indications that counter __name__ attributes should always end in "_total".  Is this a requirement?  If so is it the responsibility of the client to ensure it is satisfied? The receiver? The remote write exporter? Any guidance and advice is appreciated.

Hi @Aneurysm9! Sorry for the slow reply, I missed this.

That said, there are indications that counter name attributes should always end in "_total". Is this a requirement?

The naming requirements are not enforced, no - there are plenty of misnamed metrics out there and we need agents to correctly propagate them.

If so is it the responsibility of the client to ensure it is satisfied? The receiver? The remote write exporter?

We've discussed this and I think with the move to open metrics the client libraries will probably start enforcing this themselves - but we need to be really careful about backwards compatibility here, so we're not doing anything in a rush.


Fix TypeError in svds

Fix TypeError reported at #5000.  Because of inaccurate eigsh, the added tests fail at numpy_cupy_allclose.

pfnCI, test this please.

Jenkins CI test (for commit cc395d8e067fc1382c7c7d71f19b08a7b5641882, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit cc395d8e067fc1382c7c7d71f19b08a7b5641882, target branch master) succeeded!


Import Fail

I have an iPhone 7 and just downloaded the App and tried to import a paper wallet. I did the following: Upper Right Corner->Settings->Import Wallet
The app IMMEDIATELY closes, with no errors, nothing. I have done this twice. My LTE from the paper wallet has not shown up, and the failure repeats.(created from Zendesk ticket #3025) gz#3025

Agent comment from<EMAIL_ADDRESS>in Zendesk ticket #3025:It actually seems to be doing something, see attached image. It's been stuck like that for over an hour.

On Thursday, November 17, 2022 at 01:35:42 PM PST, Jim Flanagan (Litewallet Support<EMAIL_ADDRESS>wrote:1668724718826blob.jpg
°°°

Agent comment from Jim Flanagan in Zendesk ticket #3025:Hello CVS,
I assume that the paper wallet address starts with a 1 or a 3 and this is the old format.
The new format is a L or an M wallet.
Let me see what the easiest way is to convert your old format to a new one.
I know CRYPTOPAY had a feature like this but am not sure if it worked with a paper wallet.
Let me confirm and I will get back to you.
Jim Flanagan
Litewallet Support
°°°

Agent comment from Jim Flanagan in Zendesk ticket #3025:CVS
I have this wallet, I have never used it to do this particular thing, but after researching it a bit may be the easiest solution.
I will send you a link with step-by-step instructions.
Then you can send your Litecoin off that app and back to your Litewallet.
NOTE: Always be safe with your coins and apps you use. Never give anyone your private info or share your QR code.
https://intercom.help/bity-help-center/en/articles/5609700-how-do-i-import-my-litecoin-ltc-from-a-paper-wallet-to-a-software-wallet
Please let me know if this helps
Jim Flanagan
Litewallet Support
°°°

Agent comment from<EMAIL_ADDRESS>in Zendesk ticket #3025:I’m killing the app.

Sent from my iPhone

On Nov 17, 2022, at 3:00 PM, Jim Flanagan (Litewallet Support<EMAIL_ADDRESS>wrote:image0.png
°°°

Agent comment from<EMAIL_ADDRESS>in Zendesk ticket #3025:thanks, will give this a try. And yes my address starts with a 6vS
Chuck
On Thursday, November 17, 2022 at 03:41:43 PM PST, Jim Flanagan (Litewallet Support<EMAIL_ADDRESS>wrote:
°°°

Agent comment from<EMAIL_ADDRESS>in Zendesk ticket #3025:I got what I needed to be done through Electrum-LTC. Sorry, it did not work out with Litewallet.
Chuck
On Thursday, November 17, 2022 at 03:41:43 PM PST, Jim Flanagan (Litewallet Support<EMAIL_ADDRESS>wrote:
°°°

In addition to scanning the private key. Could we allow users to enter into a text/field box. I know when I sweep funds I prefer copy/paste more than scanning.


Properly resolve JS-only scoped packages with defined entry points (release-2.5)

Fixes #18630 which regressed at #18326.
When we look for a node module of the form foo/bar it's correct to look in foo for a package.json but not foo/bar/package.json. This is not the case for @foo/bar; we do need to look for @foo/bar/package.json.
Essentially any scoped package name @foo/bar needs to be treated as if they are fully atomic, hence the change in getNameOfTopDirectory

Looks similar to #18580?

Yep


How to build lxde image for De1-soc

Hi, thinkoco
I've followed your guide: https://github.com/thinkoco/c5soc_opencl/blob/master/documents/HowToBuildSDImage.md to build lxde image. But when I boot the image to de1 and use VGA to connect the monitor but there is no desktop environment. But when I copy your root files in your lxde image to my image, i get desktop environment. So I want to ask that did you config anything in your root files??
And one more thing that when i install rsyslog i got this error?

So I've removed rsyslogy and there is any problem with my image if i don't install rsyslog?
Thanks you!

Hi @thinkoco, seemly I've solved my problem so I'll close this issue


GSC conversion for REST API

Description of the problem
Unable to convert Flask server docker container using GSC
Steps to reproduce

Hi,
I am trying to do a simple conversion of docker images running Flask server with REST API using GSC but fail, reproduced steps as below
app.py
from flask import Flask, jsonify, request
app=Flask(__name__)
#we are importing our function from the colors.py file

@app.route("/",methods=['GET','POST'])
def index():
    if request.method=='GET':
#getting the url argument
        url = request.args.get('url')
        result={'Result': "GET result"}
        return jsonify(result)
    else:
        return jsonify({'Error':"This is a GET API method"})
if __name__ == '__main__':
    app.run(debug=True,host='<IP_ADDRESS>', port=5000)

ubuntu18.04-flask.dockerfile
# Sets the base image for subsequent instructions
FROM ubuntu:18.04
# FROM python:3.7-slim-stretch
# Sets the working directory in the container
WORKDIR /app
RUN apt-get update -y
RUN apt-get upgrade -y
RUN apt-get install -y python3
RUN apt-get install -y python3-distutils python3-pip python3-apt

# Copies the dependency files to the working directory
COPY requirements.txt /app/requirements.txt
# Install dependencies
RUN pip3 install -r requirements.txt
# Copies everything to the working directory
COPY . /app
RUN chmod 777 ./app.py
# Command to run on container start
CMD [ "python3" , "./app.py" ]

requirements.txt
click==7.1.2
Flask==1.1.2
itsdangerous==1.1.0
Jinja2==2.11.3
MarkupSafe==1.1.1
Werkzeug==1.0.1

Build the docker image
docker build -t ubuntu18.04-flask-demo -f ./ubuntu18.04-flask.dockerfile .
Convert the build (using generic manifest)
./gsc build --insecure-args ubuntu18.04-flask-demo test/generic.manifest
./gsc sign-image ubuntu18.04-flask-demo enclave-key.pem
Run the converted docker
docker run -d --device=/dev/sgx_enclave    -v /var/run/aesmd/aesm.socket:/var/run/aesmd/aesm.socket -p 5000:5000 gsc-ubuntu18.04-flask-demo
Expected results
Calling at localhost should return response
curl localhost:5000
{
  "Result": "GET result"
}

Actual results
The docker container hanging with these logs only
Gramine is starting. Parsing TOML manifest file, this may take some time...
-----------------------------------------------------------------------------------------------------------------------
Gramine detected the following insecure configurations:

  - loader.insecure__use_cmdline_argv = true   (forwarding command-line args from untrusted host to the app)

Gramine will continue application execution, but this configuration must not be used in production!
-----------------------------------------------------------------------------------------------------------------------

Emulating a raw syscall instruction. This degrades performance, consider patching your application to use Gramine syscall API.
 * Serving Flask app "app" (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: on
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)
 * Restarting with stat
Emulating a raw syscall instruction. This degrades performance, consider patching your application to use Gramine syscall API.
 * Debugger is active!
 * Debugger PIN: 138-003-840

Additional information

SGX is installed in the VM (Azure DC sv3)

Questions:

Can I use some pre-configured docker images (like python:3.7-slim-stretch) or it has to be ubuntu:18.04 and then install python3 in the docker image?
Is it possible to run a docker container (with Flask server) and also provide arguments in the docker run command ? something like this:
docker run -p 5000:5000 -it --device=/dev/sgx_enclave  -v /var/run/aesmd/aesm.socket:/var/run/aesmd/aesm.socket  gsc-<some-converted-image> '$ARG'
Do you have some working examples with Python Flask server (or any RESTFUL API) I can refer to?

Thanks a lot

Can I use some pre-configured docker images (like python:3.7-slim-stretch) or it has to be ubuntu:18.04 and then install python3 in the docker image?

Yes you can. You can use any Ubuntu-based Docker image as your base image in the ubuntu18.04-flask.dockerfile file. The only requirement is that Gramine's base image (specified in config.yaml of GSC) is compatible with your Dockerfile's base image.

Is it possible to run a docker container (with Flask server) and also provide arguments in the docker run command ? something like this:
docker run -p 5000:5000 -it --device=/dev/sgx_enclave  -v /var/run/aesmd/aesm.socket:/var/run/aesmd/aesm.socket  gsc-<some-converted-image> '$ARG'

Yes. For this, you need to use the --insecure-args option during the gsc build step. Which you already do. So it should just work.

Do you have some working examples with Python Flask server (or any RESTFUL API) I can refer to?

Unfortunately no. But I don't see any specific problems with REST API or with Flask -- I mean, I don't think your problem is about network connectivity. Your problem is most probably with some manifest option that is missing from your minimal test/generic.manifest.
So the next step for you:

Please show us your config.yaml GSC file.
Please tell us which GSC commit you're using (cd gsc && git show --summary).
Please try to re-build your application with gsc build --debug, to get debug information. This will force GSC and Gramine to print a lot of info. You can analyze this log yourself and find the potential issues, or you can attach the log here, so we can take a look.

Additionally, would it be possible to add the gsc to main path so that I can run it anywhere instead of inside gsc folder? Perhaps a soft link would work?

You can just copy it yourself, if you want to. Something like ln -sf gsc /usr/local/bin should work. We didn't implement the installation procedure, because nobody seemed to care (until your request now :)).

Here's the log file

The log file has this as the last syscall executed:
pselect6(0, 0, 0, 0, 0x4aa11bc0, 0) ...
This is the way to sleep for some time (we can't see for how much time because we only see the pointer to the "time struct", which is at address 0x4aa11bc0). Are you sure your program is not just sleeping for like several minutes?
Other than that, I didn't find anything special in the log...

This is the way to sleep for some time (we can't see for how much time because we only see the pointer to the "time struct", which is at address 0x4aa11bc0). Are you sure your program is not just sleeping for like several minutes?

That's kind of strange, as my python program given above didn't make any sleep time, or maybe the Flask library does that without my understanding.
Anyways, should I include all necessary python libraries in the trusted files of the manifest, just to make sure it can read/write the libraries ?
Thank you

Anyways, should I include all necessary python libraries in the trusted files of the manifest, just to make sure it can read/write the libraries ?

This actually shouldn't be necessary, as GSC does it by itself.
If you think that reading/writing some files (libraries) can be a root cause, then you can try sgx.file_check_policy = "allow_all_but_log" manifest option.

I've tried with the given manifest option, but it was the same result, the app hanging but not receiving GET request from the curl command.
Also recently, when I tried to build new gsc images, there's an error appears:

Program protoc-c found: YES (/usr/bin/protoc-c)
Program protoc found: NO
meson.build:262:4: ERROR: Program 'protoc' not found or not executable
A full log can be found at /gramine/build/meson-logs/meson-log.txt
NOTICE: You are using Python 3.6 which is EOL. Starting with v0.62.0, Meson will require Python 3.7 or newer
Failed to build unsigned graminized docker image gsc-python3.7-flask-demo-unsigned.

Do you have any suggestion for this ?
Thank you

Please update your GSC to the latest version. We recently made a change to core Gramine and to GSC.

I tried app.run(debug=False,host='<IP_ADDRESS>', port=5000) without debugger.
It can work.
Gramine is starting. Parsing TOML manifest file, this may take some time...
-----------------------------------------------------------------------------------------------------------------------
Gramine detected the following insecure configurations:

  - sgx.debug = true                           (this is a debug enclave)
  - loader.insecure__use_cmdline_argv = true   (forwarding command-line args from untrusted host to the app)
  - sgx.allowed_files = [ ... ]                (some files are passed through from untrusted host without verification)

Gramine will continue application execution, but this configuration must not be used in production!
-----------------------------------------------------------------------------------------------------------------------

 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)
<IP_ADDRESS> - - [29/Jul/2022 08:05:12] "GET / HTTP/1.1" 200 -

$ curl localhost:5000
{"Result":"GET result"}

I tried app.run(debug=False,host='<IP_ADDRESS>', port=5000) without debugger. It can work.
Gramine is starting. Parsing TOML manifest file, this may take some time...
-----------------------------------------------------------------------------------------------------------------------
Gramine detected the following insecure configurations:

  - sgx.debug = true                           (this is a debug enclave)
  - loader.insecure__use_cmdline_argv = true   (forwarding command-line args from untrusted host to the app)
  - sgx.allowed_files = [ ... ]                (some files are passed through from untrusted host without verification)

Gramine will continue application execution, but this configuration must not be used in production!
-----------------------------------------------------------------------------------------------------------------------

 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)
<IP_ADDRESS> - - [29/Jul/2022 08:05:12] "GET / HTTP/1.1" 200 -

$ curl localhost:5000
{"Result":"GET result"}

Hi @llly ,
Yes it seems removing the debugging option made the Flask server code running (at least with the GET).
Thank you for the suggestion!

Since it seems to work, I will close this issue.


Created initial drake parser and added drake examples.

Please comment the add_AST_script method describing what it's supposed to do.

@jhorey I've added comments to add_AST_script()


All URI starting with /status, /ping, /pma, /adminer etc. are treated as special locations

Say someone writes a page or post about the game Ping Pong or a television animation Pingu or an urban dictionary about PMA (Positive Mental Attitude). It'd be likely that page slug would start with "ping" or "pma". In such a case, visiting that page would give an unexpected result.
I've added pull request #964 to address this.

Fixed by #964


Alexa event node not firing reliably any more

I am using the node-red-contrib-alexa-remote2-applestrudel palette 5.0.27. This has been working reliably for ages. Lately I noticed I had to say voice commands, which I intercept via the alexa event node and process in NR, I have to repeat multiple times before they trigger. I thought it was the usual alexa trouble. But after investigating a little, it seems there is a problem. My account is initialised, and the alexa event node says listening. So far so good. But quite often, when I say 'Alexa', it does not change to the green 'event fired' under the node. So then there is no output from that node. I can hear the custom Alexa response I have set in the Alexa app - routines, so she heard and understood it, but its not triggering the alexa event node. This is not all the time. If I try multiple times, eventually the event node fires, and triggers the flows.

Same problem here .....

I see the same, pity as was really well integrated into my home. Now unreliable.

Is there anything in the issues of the depending libraries @bbindreiter ?
Has anyone already clues what it could be?
Were there changes in the API on the Amazon side?
Anyone has it working (maybe with another system.. home assistant?)
I also had that pretty nicely integrated and now everything falls apart :'(
Maybe it's time to implement another Voice to Text engine and throw Alexa out ;)

And suddenly it just works again.  Although this seemed to be a bigger outage than usual.
Unfortunately Alexa, the reverse engineered API we use and the node-red addon is a house of cards that can collapse any minute. Amazon can shut us down if they want to.
I personally don't use the event node anymore.

I've been experiencing this for the past week or so and I'm still using the old node-red-contrib-alexa-cakebaked
The node says it's "Listening" but never really listens for anything lol
Sounds like it may be something on Amazons API though?

I've been experiencing this for the past week or so and I'm still using the old node-red-contrib-alexa-cakebaked
The node says it's "Listening" but never really listens for anything lol
Sounds like it may be something on Amazons API though?

I'm getting the same issue with node-red-contrib-alexa-remote2-applestrudel.
I have to go into the node and redeploy and then it will work ok for a while. Is their a way to possibly 'reboot' the node automatically?

Same issue with the "listening" node - sometimes very slow or no response on starting events
node-red-contrib-alexa-remote2-applestrudel palette 5.0.27
sometimes it helps to refresh the cookie or the athentikation...but not reliable...
any news here?

I've been triggering the alexa init node with option Initialise every hour for years now. Seems to work

I've been triggering the alexa init node with option Initialise every hour for years now. Seems to work

I'm doing the same. But in the moment it doesn't help...

@1st initializing does not solve the issue and
I think is this is the prize for getting these sollutions "for free".
I think the main problem ist that someone (who has knowhow in coding....) should maintain the node according to chaches made (in this case) by Amazon on the Alexa "API".
Sometimes it is just a small adaption makes the node run proberly again. (made this experience with other nodered nodes)
I wish I had the know how to do this - but unfortunately i have not :(
I think it would be a good idea to have something like a "pay" option for programmers to engage them to get nodes running properly again....

I'm getting the same issue with node-red-contrib-alexa-remote2-applestrudel.

Same here

I have to go into the node and redeploy and then it will work ok for a while. Is their a way to possibly 'reboot' the node automatically?

When you say redeploy what do you mean? And are using the proxy method, all the cookie method?

I think it would be a good idea to have something like a "pay" option for programmers to engage them to get nodes running properly again....

I think that is a bit of a slight on the great programmers that work for things like node red, and home assistant. You're not going to suddenly get access to better programmers simply because of money. Unless Amazon releases their own version, and the chances of that are pretty much non-existent.

As bbindreiter "does not use anymore event node" can he (or any other) suggest any alternative, if any, to capture the sentence Alexa understood  ?

The method I've used myself before was to set up an alexa routine which sets a simulated smart bulb (dimmable light) to a certain dimm level and then I just used this percentage to control things in node red. Which required a seperate routine for each command in the alexa app.
The alexa event / on device activity had the big advantage that I could just summarize all commands for node red in one routine in the alexa app with different phrases, as what was said is handed over by the node directly and not only a dimm value.
Is there anything we can possibly provide to support debugging to get the event listener running again?

Thanks for pointing that out, that was enough for me to get my flows and scripts working, as i just linked the alexa other node to a button entity, and then in my scripts i have it push that button and then that gives me the name in the script as i used to use it.

Does that work for devices with the same name, but in different rooms, eg. saying: "turn on lights" in  2 different places?

Does that work for devices with the same name, but in different rooms, eg. saying: "turn on lights" in 2 different places?

Well, if it is just about the lights you would create 2 simulated (or real) lights and just group them with the respective alexa device in the alexa app. lights on/off is built in, so the echo would turn on/off all lights within the same group anyway, as set up in the alexa app.
For everything which is not a light, you can use either the "Alexa Other" node from applestrudel to get on which echo the last activity happened. So you would get from your simulated light bulb to the alexa other-node to determine where it was set from.
Or you can use this script which offers similar options, just directly in bash. Which I've used before I found the applestrudel implementation.

Never looked at the 'other' node. Just put one in my flow and tested and it does indeed bring through the summary (what she heard) and the name (the echo device).
Are we saying this still works reliably even if the listener stops?
If that is the case, how can we go about using this in flows?
I have a couple of use cases that have become unreliable.
First one - Lamps On (or Off). With Room Aware
Goal is to be able to say that command and it is picked up and passes through both the command and the device to operate the lamp in the relevant room.
Currently the Alexa Event node sends a payload to a sensor (called Last Alexa) to record the device in question.

Then in Alexa Routines App, I have a routine for lamps. This will listen for various messages that might resemble turning the lamp on or off. "lamps on", "lamps off", lamp on", "lamp off" etc etc. That routine will toggle an artificial toggle switch.
The Switch (called Room Aware Lamp Toggle) is toggled and that will wait a moment, catch the "last alexa" from the sesnor created in the first part of the flow, and then pass on the message to toggle the lamp for that room.

I have a similar routine for other items, like light scenes.
Second one, one off phrases, not room specific.
I also have a routine in alexa that listens for items but does nothing with them. To avoid any alexa response.
EG I have one to turn my tv to CCTV input. "Alexa show cameras".
What happens is the routine fires nothing. but because it is a routine, it doesnt bong and say not known, unrecognised or whatever...
Node Red flow hears it via the Event node, takes the "msg.payload.description.summary" and if it is a recognised command, in a list, it passes through to an action.

So this other node, how would that be best used?

I have done a little testing with the Alexa other node. Even when the listening node doesnt react, when I trigger the alexa other node with a inject, it shows me the voice command and the alexa device the command came from. Very useful.
I thought I could trigger the alexa other node with a input from the listening node. Unfortunately that doesnt work, as the listening node does not send anything when it doesnt want to listen. So we need to find another way. I thought of injecting the other node every few seconds. Problem is, its still showing the last command, not a blank. So that would trigger a possible event time and time again with every inject.
So what we need is a reliable trigger, which injects the other node to then process the data from the other node. Still thinking about it, if I have an idea I'll post it in this thread

I think I might have an idea. I use Homeseer as my home automation system, but it might work with other systems too. I will create a virtual switch in Homeseer. All routines will then trigger the switch (turn it on). This I can pick up in Node Red, to inject the other node. After triggering, I can turn the virtual switch off again, ready for the next time a routine gets triggered. That could work... will test when I have a little time on my hand

So, I think I found a way to replace it for my scenario:
The issue with the "other"-node is, that it needs a trigger to poll the last activity and echo which was addressed. So, the solution is quite easy actually. Like @richsimpson so far I also had one routine with all possible phrases in it, which did nothing, just to keep alexa quiet and check the command via the event node myself.
Now: I keep it excatly like this, just that I replace the event node with the "other"-node and let this node trigger by a simulated light bulb. In the routine with all my phrases I just switch that light bulb always off. That fires then an event to the "other" node with "Get activities". Even the object with comes back is similar, only difference is that it is an array, so command and echo device is in:
msg.payload[0].description.summary
and
msg.payload[0].name
I also have the impression that this works much faster, as not even the sound finishes and the response comes already.

I think I might have an idea. I use Homeseer as my home automation system, but it might work with other systems too. I will create a virtual switch in Homeseer. All routines will then trigger the switch (turn it on). This I can pick up in Node Red, to inject the other node. After triggering, I can turn the virtual switch off again, ready for the next time a routine gets triggered. That could work... will test when I have a little time on my hand

Have been testing this, and it works really well, similar to @tjareson setup. The only slight niggle I have, I think as I am setting a smart home device, Alexa says OK every time a routine gets triggered. Thats ok, with the exception some actions trigger a Alexa voice response reporting temperatures or other stuff back to me. So she would for example say OK - your westerstation is reporting a temperature of...
I cannot (so far) suppress that OK.

Alexa says OK every time a routine gets triggered.

That's strange, I don't have that behaviour. Does it also happen with all other commands? Maybe it is a setup within the alexa app? I've set Voice Responses to "Brief Mode".

Alexa says OK every time a routine gets triggered.

That's strange, I don't have that behaviour. Does it also happen with all other commands? Maybe it is a setup within the alexa app? I've set Voice Responses to "Brief Mode".

I dont know if I have set her to brief mode, and normally I like the OK as confirmation that she has got the command. I have tested, and unless I have set a custom response in the Alexa app, she will always say OK. Unfortunately I cannot set a blank custom response.

Thanks for pointing that out, that was enough for me to get my flows and scripts working, as i just linked the alexa other node to a button entity, and then in my scripts i have it push that button and then that gives me the name in the script as i used to use it.

Does that work for devices with the same name, but in different rooms, eg. saying: "turn on lights" in 2 different places?

What im using it for at the moment, is i say "Turn on the TV" and if im near my lounge alexa, then it pulls the name from that and turns the tv on on the lounge, while if the alexa in the bedroom hears it, then the bedroom tv turns on.

Happy with the results of using the 'other' node. After fixing various things in my flows I have been seeing reliable performance. Bit of work to update stuff, but always enjoyable to tinker and improve stuff.
I now have:
Routines for:
LAMPS (on , off)  - detects the echo/room called and changes lamp in that room.
SCENES (activates room scene) - detect the echo/room called and works for that room.
HEATING (warmer/cooler/boost/set temperature/set mode) - detects the echo/room called and works for the TRV in that room.
GENERAL (any magic words I add to that generic/ignore routine. show cameras, show sky, reboot internet, boost hot water)  - control any individual event/scene/routine that I want.
Input is from the Alexa hub/Nodes which is how I publish my devices to Amazon Echo.

From that the, output of the hub can go off to the individual devices.

But also the output from the echo commands lands in the specific artificial devices set up ( Room Aware Lamp Toggle and so on). At that point I complete a sensor used elsewhere in Home Assistant for both the Last Device called (from one of my magic phrases, not for general use) and the summary of what was called.

Each of the different types of commands will send out put to an individual section where I handle the command and convert to an event. Eg toggle the lamp. Where an on or off command simply toggles the lamp. On the assumption that if you are in the room and lamp is on, you would only ask if you want it off. But in reality and alexa lamp on or an alexa lamp off would just toggle it. Saying alexa lamp off over again would just turn lamp on then off repeatedly.

it is slightly quicker  using the 'other' node,  because before it would have to do parse the sentence, but this way it is just turning on a light: a light name which it expects.

I've just updated to 5.0.34 and its started working ok- not sure if that's just a coincidence!

@Mikee1234K @tjareson
As you have been using the alexa other/activities to identify the device called, are you currently seeing any issues, just opened an issue I have with it. Had been rock solid since our August exchanges ...
https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel/issues/156


=~= not doing its thing on a simple Option; maybe an extensionality problem for additive types?

In the before file, Verus fails to prove this extensional equality:
        assert( post.iptr(ptr) =~= PagedJournal_v::JournalRecord::discard_old_journal_rec(self.iptr(ptr), lsn) );

In the after file, I "fix" it by beginning a manual proof of extensional equality on the branches of the Option. Once I prove that the Option legs match, Verus is happy.
2023-07-24-15-01-48.zip
2023-07-24-15-01-54.zip

It seems verus usually needs
        assert(post.iptr(ptr).is_Some() == PagedJournal_v::JournalRecord::discard_old_journal_rec(self.iptr(ptr), lsn).is_Some());

to prove extensional equality. Can you spell out the argument why this is true? (which definitions / lemmas this comes from)


hunspell: adopt; modernize; add tests

Description of changes
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

rebase onto staging due to the number of rebuilds this triggers

Was able to build this for all tier 1 platforms against master


add support to not override the changes in debug tab, like environment variables, etc.

in designer, when we make some changes in debug tab, such as add some environment variables, and update some requests, and if we click design tab to take a look, and then click debug tab, all old changes in debug tab will be overridden by initial debug settings.
as usually user will add more and more environment variables to be used in more and more requests added in debug tab, which would also be used in test tab.
that would be frustrated that all changes are lost just if we switch back to design tab to take a look and switch back to debug tab, thanks for the better software.

Hi @douhaolee
Have you tried our newest release located here: https://github.com/Kong/insomnia/releases

Closing due to inactivity


More robust initial value parsing.

Hi, look at that, I think that's better because I was having trouble for the initial precision of number:
if it was a number with just one decimal, like 585.0, it was parsed as 58,50 €, now It works fine!

Thanks!


Update set-password-to-never-expire.md

Made changes to the connection cmdlet
Fixes https://github.com/MicrosoftDocs/microsoft-365-docs/issues/12511

@JohanFreelancer9 Please copy review

@kwekuako Please merge this PR. Thanks


patch: Adding new Service credentials secret type

:tada: This PR is included in version 2.0.7 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Pub/Sub admin operation default deadline should be 60s

Right now the deadline defaults to infinity as declared by gRPC (https://github.com/grpc/grpc/blob/master/src/ruby/lib/grpc/generic/client_stub.rb). We should set this to 60s so it can more quickly be retried by clients if a server is unreachable or unavailable. This also mirrors the deadlines set by Java/C#.

While GRPC sets the default timeout to infinity, the GAPIC layer sets a total timeout to 60 seconds for most operations. For example:
https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-pubsub/lib/google/cloud/pubsub/v1/publisher_client_config.json#L64
Are these considered an "admin operation"? Or are you referring to different calls?

Ah, thanks, didn't see these overrides.


Motherboard temperature incorrect

Describe the bug
The Motherboard temperature as reported by this addon is incorrect. Temperature according to Unraid dashboard is about 48C. The addon reports 117C. All other reported temperatures are correct.
Expected behavior
Expect the motherboard temperature to be equal to the unraid dashboard.
Screenshots
screen shots of the displayed temps added

Unraid (please complete the following information):

Version 6.12.13

Home Assistant (please complete the following information):

Version
core: 2024.12.5
supervisor: 2024.12.0
OS: 14.1
frontend: 20241127.8

Home Assistant installation type (please complete the following information):

[ ] Docker / Container
[x] Virtual Machine
[ ] Raspberry Pi

Priority of Request

[ ] High
[ ] Medium
[x] Low

Additional context

appears I wasn't on the most recent version. this is fixed already


Anchor protocol staking error

The transaction requested has failed due to the following reason:
pubKey does not match signer address

Hello @jackykoyan , A support ticket has been opened for you with Support ticket number TM5466. You should talk to an ANHOR PROTOCOL Dev on the LIVE SUPPORT PAGE So that your issue can be looked into. Thank you. CLICK HERE


Skip record when Output#format returns nil

Current Output API can't skip invalid record with custom format.
Old API uses emit for such purpose but new API doesn't have it.
Omitting invalid record in format is good for reducing formatting cost.

@tagomoris Could you check this patch?


Fail to create the Windows2019 image

Description
Fail to cerate the Windows2019 image on a new created VM(clean).
Unsuccessful exit code returned by the installation process: 2003.
Steps follow on this:https://github.com/actions/virtual-environments/blob/main/docs/create-image-and-azure-resources.md
Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016
[X] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
Windows Server 2019
Is it regression?
No response
Expected behavior
No response
Actual behavior
No response
Repro steps
Local machine or Azure VM can be used as a build agent.
Download packer from https://www.packer.io/downloads, or install it via Chocolately.
choco install packer
Install the Azure Az PowerShell module - https://docs.microsoft.com/en-us/powershell/azure/install-az-ps.
Install-Module -Name Az -Repository PSGallery -Force
Install Azure CLI - https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-windows?view=azure-cli-latest&tabs=azure-cli.
Invoke-WebRequest -Uri https://aka.ms/installazurecliwindows -OutFile .\AzureCLI.msi; Start-Process msiexec.exe -Wait -ArgumentList '/I AzureCLI.msi /quiet'; rm .\AzureCLI.msi
Download Virtual-Environments repository.
Set-Location c:
git clone https://github.com/actions/virtual-environments.git
Import GenerateResourcesAndImage script from /helpers folder, and run GenerateResourcesAndImage function via Powershell.
Set-Location C:\virtual-environments
Import-Module .\helpers\GenerateResourcesAndImage.ps1
GenerateResourcesAndImage -SubscriptionId {YourSubscriptionId} -ResourceGroupName "myTestResourceGroup" -ImageGenerationRepositoryRoot "$pwd" -ImageType Ubuntu1604 -AzureLocation "East US"
Where:
•	SubscriptionId - The Azure subscription Id where resources will be created.
•	ResourceGroupName - The Azure resource group name where the Azure resources will be created.
•	ImageGenerationRepositoryRoot - The root path of the image generation repository source.
•	ImageType - The type of the image being generated. Valid options are: "Windows2016", "Windows2019", "Ubuntu1604", "Ubuntu1804", "Ubuntu2004".
•	AzureLocation - The location of the resources being created in Azure. For example "East US".
The function automatically creates all required Azure resources and kicks off packer image generation for the selected image type.
Please, check synopsis of GenerateResourcesAndImage for details about non-mandatory parameters.

Hello @jiaweis2021!
Could you please the entire build log of yours?

@mikhailkoliada Hello, this image is created by CMD, this is the entire log. Not build in DevOps pipeline.

@jiaweis2021 please provide packer log. You can enable it as described here if it is not
https://www.packer.io/docs/debugging#debugging-packer

@mikhailkoliada Hello, this image is created by CMD, this is the entire log. Not build in DevOps pipeline.

It looks like you forgot to modify your GenerateResourcesAndImage.
You're trying to build Ubuntu 16.04 instead of Windows Server 2019.

@jiaweis2021, I am planning to close this thread. If you have any concerns feel free to open one.


chore: update CONTRIBUTING.md

Summary
Update CONTRIBUTING.md

Test Plan

Thank you for reviews! I updated based on your comments.


Question: How do i use HTTPS with elysia?

i have tried using it but i get a "TypeError: The listener must be a function"

Found a way!
const app = new Elysia({     serve: {         certFile: 'client-cert.pem',         keyFile: 'client-key.pem'     } });;
:)


Support mobile devices

Description
This feature/fix allows to...
Code samples
Laragear::sample();

While I appreciate the PR, no description = no merge. It makes my job of maintaining this harder.