Unable to find all elements

https://github.com/kennethreitz/requests-html/commit/29acbaabc743922335ff3183ce9108af16cf6f48
This commit breaks the find function.
Eg. https://kb.juniper.net/InfoCenter/index?page=content&channel=SECURITY_ADVISORIES
find('#browse_cat', first=True).find('tbody', first=True).find('tr') only returns the first tr child with this commit.

some problem here. can't find all elements
http://www.richvest.com/index.php?m=cb
find('#cb_hq tr') only returns the first tr child

Related to #279, I will be fixing this.


Update to 1.19.3

~This a temp solution because the migration of the carpet api is not yet complete.~ Now use MagicLib Compat API.

Note that you don't need to migrate to the new settings api for 1.19.x, it'll just warn in the log until then.
And if you need help with that feel free to ask in the carpet discord, there's also a migration guide in the wiki.

亲测可以load上

Untested use for Minecraft 1.19.3 version has been uploaded. Download via GitHub Actions: plusls-carpet-addition-1.19.3-0.2.5-beta+5fa8bc5

Thank you @Hendrix-Shen 💖

求1.19.2的jar

求1.19.2的jar

https://hendrixshen.lanzouy.com/b0c4srcti 密码:plusls

考虑到 GitHub Actions 构建文件需要登录账号，并且90天过期，将转移到 Nyan-Work/plusls-carpet-addition 发布 prerelease。
Considering that GitHub Actions build artifacts require a login and expire in 90 days, they will be moved to the Nyan-Work/plusls-carpet-addition release prerelease.

最新的1.19.3PCA无法指令识别到，不知道什么原因，求解

Hello @Hendrix-Shen, could you provie an build for 1.20.2 please? 😊


fix!: Ban Fields in for loop indices and bitwise ops

Description
Problem*
Resolves https://github.com/noir-lang/noir/issues/3639
Resolves https://github.com/noir-lang/noir/issues/4193
Summary*
Uses the new TypeVariableKind::Integer in for loops and bitwise operations to prevent Field types from being used there.
Removes the old delayed_type_checks hack.
Additional Context
Documentation*
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Note the PR body is repeated, not sure if you meant to state that it resolves two different issues:
Resolves https://github.com/noir-lang/noir/issues/3639
Resolves https://github.com/noir-lang/noir/issues/3639

@kevaundray those issues are correct, the other PR didn't quite resolve them since it implemented the new type variable kind but the new kind was unused until this PR

There is a typing issue in sort_via in std, I commented sort_via and run the println in ssa_gen/codegen_for:
      println!(
            "Type of start index is {:?} type of iterator is {:?} type of end index is {:?}",
            self.builder.type_of_value(start_index),
            index_type,
            self.builder.type_of_value(end_index)
        );

And it still gave:
Type of start index is Numeric(NativeField) type of iterator is Numeric(Unsigned { bit_size: 32 }) type of end index is Numeric(NativeField)
in https://github.com/noir-lang/noir/pull/4290 example

@sirasistant good catch, I found a bug when unifying TypeVariableKind::Integer where we still succeeded previously on Fields: https://github.com/noir-lang/noir/pull/4376/commits/6bc4e2364019c23fde88eb6c50f67713bd33bd17

Wow, ok. So after the change it turns out we were using Fields in for loops in a lot of places. So this is actually quite the breaking change:
error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon/bn254.nr:21:15
   │
21 │     for _r in 0..rf / 2 {
   │               ---------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon/bn254.nr:22:18
   │
22 │         for i in 0..state.len() {
   │                  --------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon/bn254.nr:25:18
   │
25 │         for i in 0..state.len() {
   │                  --------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon/bn254.nr:33:15
   │
33 │     for _r in 0..rp {
   │               -----
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon/bn254.nr:34:18
   │
34 │         for i in 0..state.len() {
   │                  --------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon/bn254.nr:43:15
   │
43 │     for _r in 0..rf / 2 {
   │               ---------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon/bn254.nr:44:18
   │
44 │         for i in 0..state.len() {
   │                  --------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon/bn254.nr:47:18
   │
47 │         for i in 0..state.len() {
   │                  --------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon/bn254.nr:70:14
   │
70 │     for k in 0..msg.len() {
   │              ------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon/bn254.nr:96:14
   │
96 │     for i in 0..input.len() {
   │              --------------
   │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:105:14
    │
105 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:114:14
    │
114 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:123:14
    │
123 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:132:14
    │
132 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:141:14
    │
141 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:150:14
    │
150 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:159:14
    │
159 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:168:14
    │
168 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:177:14
    │
177 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:186:14
    │
186 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:195:14
    │
195 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:204:14
    │
204 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:213:14
    │
213 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:222:14
    │
222 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/poseidon/bn254.nr:231:14
    │
231 │     for i in 0..input.len() {
    │              --------------
    │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon.nr:37:14
   │
37 │     for r in 0..(ark.len() / state.len()) {
   │              ---------------------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon.nr:38:18
   │
38 │         for i in 0..state.len() {
   │                  --------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon.nr:44:22
   │
44 │             for i in 1..state.len() {
   │                      --------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon.nr:67:14
   │
67 │     for k in 0..msg.len() {
   │              ------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon.nr:94:14
   │
94 │     for i in 0..x.len() {
   │              ----------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/poseidon.nr:96:18
   │
96 │         for j in 0..x.len() {
   │                  ----------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/hash/mimc.nr:11:14
   │
11 │     for i in 1..constants.len() {
   │              ------------------
   │

error: The type Field cannot be used in a for loop
    ┌─ std/hash/mimc.nr:120:17
    │
120 │     for elem in array {
    │                 -----
    │

error: The type Field cannot be used in a for loop
    ┌─ std/array.nr:122:14
    │
122 │     for i in 0..a.len() {
    │              ----------
    │

error: The type Field cannot be used in a for loop
  ┌─ std/merkle.nr:9:14
  │
9 │     for i in 0..n {
  │              ----
  │

error: The type Field cannot be used in a for loop
   ┌─ std/sha512.nr:95:14
   │
95 │     for k in 0..msg.len() {
   │              ------------
   │

error: The type Field cannot be used in a for loop
    ┌─ std/ec.nr:164:14
    │
164 │     for i in 0..N_BITS {
    │              ---------
    │

error: Expected type Field, found type u64
   ┌─ std/array.nr:18:48
   │
18 │             let pos = find_index(sorted_index, i);
   │                                                -
   │

error: Types in a binary operation should match, but found Field and u64
   ┌─ std/array.nr:19:20
   │
19 │             assert(sorted_index[pos] == i);
   │                    ----------------------
   │

error: expected type [Field; N], found type [u64; N]
   ┌─ std/array.nr:34:87
   │
34 │     unconstrained fn get_sorting_index<Env>(self, ordering: fn[Env](T, T) -> bool) -> [Field; N] {
   │                                                                                ---------- expected [Field; N] because of return type
   ·
52 │         result
   │         ------ [u64; N] returned here
   │

error: The type Field cannot be used in a for loop
   ┌─ std/array.nr:59:21
   │
59 │         for elem in self {
   │                     ----
   │

error: The type Field cannot be used in a for loop
   ┌─ std/array.nr:71:18
   │
71 │         for i in 1 .. self.len() {
   │                  ---------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/array.nr:82:21
   │
82 │         for elem in self {
   │                     ----
   │

error: The type Field cannot be used in a for loop
   ┌─ std/array.nr:93:18
   │
93 │         for i in 1 .. self.len() {
   │                  ---------------
   │

error: The type Field cannot be used in a for loop
    ┌─ std/array.nr:102:21
    │
102 │         for elem in self {
    │                     ----
    │

error: The type Field cannot be used in a for loop
    ┌─ std/array.nr:111:21
    │
111 │         for elem in self {
    │                     ----
    │

error: The type Field cannot be used in a for loop
   ┌─ std/collections/bounded_vec.nr:47:18
   │
47 │         for i in 0..array.len() {
   │                  --------------
   │

error: Types in a binary operation should match, but found Field and u64
   ┌─ std/collections/bounded_vec.nr:60:29
   │
60 │             exceeded_len |= i == append_len;
   │                             ---------------
   │

error: Types in a binary operation should match, but found Field and u64
   ┌─ std/collections/bounded_vec.nr:81:29
   │
81 │             exceeded_len |= i == self.len;
   │                             -------------
   │

error: The type Field cannot be used in a for loop
   ┌─ std/slice.nr:38:21
   │
38 │         for elem in other {
   │                     -----
   │

error: The type Field cannot be used in a for loop
   ┌─ std/cmp.nr:24:18
   │
24 │         for i in 0 .. self.len() {
   │                  ---------------
   │

error: The type Field cannot be used in a for loop
    ┌─ std/cmp.nr:201:18
    │
201 │         for i in 0 .. self.len() {
    │                  ---------------
    │

@sirasistant I've found the core issue in #4290 is a result from a bug in the monomorphizer. I've pulled out the fix here: https://github.com/noir-lang/noir/pull/4386. In the general case though, this PR will still be required to prevent Fields in for loops.

cc @noir-lang/developerrelations we have put up warnings for this breaking change for quite some time now, but flagging for early heads up as this might still break quite some code from the community once merged and released.

Should we make len() return type be an usize (u64)?

@sirasistant I made that change in this PR but I'm open to debate on whether we should keep it or not.

Ah cool, I haven't look at the code yet. That sounds good to me :D

Spoke in person but for posterity, this is because we ignore the lockfile in the "MSRV check" workflow as this ensures that we'll be able to publish to crates.io because we want to know if this will fail before we push out a new version.
We shouldn't block non-release PRs on this however. I'll update this to run on master and raise issues in future.


Various fixes and cleanups

juCi++ should now work quite well on Wayland
Fixes to debugging when using Ninja
Spellchecking code moved to src/source_spellcheck
Remote debugging

The debian stable segmentation fault happens in lldb::SBDebugger::Initialize(); it seems. I manage to reproduce it when running lldb_test through juCi++ on debian stable. However, running lldb_test or make test in a shell does not produce this segmentation fault. Not sure if we can do anything about this, other than disable lldb_test on debian stable and it's old lldb version.

@zalox tests are not run on appveyor. https://ci.appveyor.com/project/zalox/jucipp-6hwdu/build/1.0.31 should have failed.

@zalox Another test issue: lldb is not installed on the archlinux docker image that travis is using.

Fixing the various platform issues on this PR Tomorrow morning.

Is it possible to cross-compile juCi++ in debian with the mingw64-toolchain? If so we should consider adding such build to travis.

No idea, cross-compiling is new to me. Remote debugging is not yet working though, but should soon.

@zalox appveyor is failing. Probably due to updates on MSYS2? The latest commit works on my own upgraded MSYS2.

@eidheim I restarted the build. Seems to be working now.

Look here https://github.com/cppit/jucipp/blob/master/appveyor.yml#L8-L11, we update msys2 before doing anything, so we shouldn't see any problems due to outdated packages.

@zalox this PR is ready for review and merge:)


Add Coffeyville Community College

@albrecht-carlos First stage of verification passed, official domain for Coffeyville Community College is coffeyville.edu as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@albrecht-carlos Thank you for your patience while waiting for a review and processing your request. Pull request merged. Please start applying for JetBrains educational subscription at https://www.jetbrains.com/shop/eform/students in an hour, to allow the changes to propagate through JetBrains systems.


Accept multiple conditions for alb-listener-rule

For the alb-listener-rule module, is it possible to use multiple domains w/ paths? For example, let's say I need.
host_headers to take in either subdomain1.xyz or subdomain2.xyz along with
path_pattern to accept /api, /auth
It seems when i try to pass both in Terraform tells me I can only use conditional block

I've split http_header, host_header, and path_pattern into individual condition blocks so they can be used together.


Too many "Transmission Error - EventCode = 4" and scheduling a different message size

Hi.
I am working with the board DISCO-L072CZ-LRWAN1.
Recently, I tried to send bigger messages than the simple lorawan example. I changed the tx and rx buffers accordingly, but when the device is going to send the message, it throws many times "Transmission Error - EventCode = 4" and other times it schedules a different message size. Sometimes it sends the correct size and message.
Console:

Sending: {m_c=0.05,m_p=5.49,mx_p=5.49,t_r=92.92,t_f=94.04,d_st=1}
11 bytes scheduled for transmission
Message Sent to Network Server
Sending: {m_c=0.03,m_p=3.63,mx_p=3.63,t_r=33.20,t_f=77.77,d_st=0}
56 bytes scheduled for transmission
Transmission Error - EventCode = 4
Sending: {m_c=0.05,m_p=6.22,mx_p=6.22,t_r=102.42,t_f=98.56,d_st=1}
57 bytes scheduled for transmission
Message Sent to Network Server
Sending: {m_c=0.05,m_p=5.89,mx_p=5.89,t_r=96.54,t_f=96.86,d_st=1}
56 bytes scheduled for transmission
Message Sent to Network Server
Sending: {m_c=0.05,m_p=6.08,mx_p=6.08,t_r=94.04,t_f=95.90,d_st=1}
56 bytes scheduled for transmission
Transmission Error - EventCode = 4
Sending: {m_c=0.05,m_p=5.51,mx_p=5.51,t_r=114.67,t_f=102.67,d_st=1}
58 bytes scheduled for transmission
Transmission Error - EventCode = 4
Sending: {m_c=0.05,m_p=5.66,mx_p=5.66,t_r=91.63,t_f=97.43,d_st=1}
53 bytes scheduled for transmission
Transmission Error - EventCode = 4
Sending: {m_c=0.05,m_p=5.40,mx_p=5.40,t_r=118.70,t_f=104.60,d_st=1}
11 bytes scheduled for transmission
Message Sent to Network Server
Sending: {m_c=0.05,m_p=5.62,mx_p=5.62,t_r=128.05,t_f=108.39,d_st=1}
58 bytes scheduled for transmission
Message Sent to Network Server
Sending: {m_c=0.05,m_p=6.05,mx_p=6.05,t_r=126.60,t_f=107.26,d_st=1}
58 bytes scheduled for transmission
Message Sent to Network Server
Sending: {m_c=0.05,m_p=5.64,mx_p=5.64,t_r=96.38,t_f=95.98,d_st=1}
56 bytes scheduled for transmission
Transmission Error - EventCode = 4
Sending: {m_c=0.05,m_p=5.46,mx_p=5.46,t_r=121.68,t_f=106.53,d_st=1}
58 bytes scheduled for transmission
Transmission Error - EventCode = 4
Sending: {m_c=0.05,m_p=5.79,mx_p=5.79,t_r=91.06,t_f=0.32,d_st=1}
53 bytes scheduled for transmission
Transmission Error - EventCode = 4
Sending: {m_c=0.05,m_p=5.46,mx_p=5.46,t_r=104.68,t_f=60.28,d_st=1}
11 bytes scheduled for transmission
Transmission Error - EventCode = 4

Note that even if the device schedules a smaller message size (11 bytes) the transmission error still occurs, so, the size may not be the problem.
Thanks in advance for your help and have happy holidays.

ARM Internal Ref: IOTCELL-1620

@hasnainvirk Thank you for your quick reply.
I used the mbed trace to acquire more information as you requested. The log file is too big, so I attached it to the issue. It looks to have 2 kind of problems: 1 for scheduling, and 2 for not receiving ACK.
Scheduling:
> 53 bytes scheduled for transmission
>
> [DBG ][LSTK]: Transmission completed
>
> [DBG ][LSTK]: Awaiting ACK
>
> [DBG ][LMAC]: RX1 slot open, Freq = 904900000
>
> [DBG ][LMAC]: RX2 slot open, Freq = 923300000
>
> [DBG ][LMAC]: ACK_TIMEOUT Elapses, Retrying ...
>
> [DBG ][LMAC]: Trading datarate for range
>
> [DBG ][LMAC]: TX: Channel=61, TX DR=0, RX1 DR=10
>
> [ERR ][LMAC]: Allowed FRMPayload = 11, FRMPayload = 53, MAC commands pending = 0
>
> [ERR ][LSTK]: Failed to schedule transmission
>
>  Transmission Error - EventCode = 4
>
>  Sending: {m_c=0.00,m_p=0.52,mx_p=0.52,t_r=30.46,t_f=21.03,d_st=0}
>
> [INFO][LMAC]: Cannot transmit 56 bytes. Possible TX Size is 11 bytes
>
> [INFO][LMAC]: RTS = 11 bytes, PEND = 45, Port: 15
>
> [DBG ][LMAC]: Frame prepared to send at port 15
>
> [DBG ][LMAC]: TX: Channel=28, TX DR=0, RX1 DR=10

ACK:

>  11 bytes scheduled for transmission
>
> [DBG ][LSTK]: Transmission completed
>
> [DBG ][LSTK]: Awaiting ACK
>
> [DBG ][LMAC]: RX1 slot open, Freq = 914300000
>
> [DBG ][LMAC]: RX2 slot open, Freq = 923300000
>
> [DBG ][LMAC]: ACK_TIMEOUT Elapses, Retrying ...
>
> [DBG ][LMAC]: Trading datarate for range
>
> [DBG ][LMAC]: TX: Channel=7, TX DR=0, RX1 DR=10
>
> [DBG ][LSTK]: Transmission completed
>
> [DBG ][LMAC]: RX1 slot open, Freq = 912300000
>
> [DBG ][LMAC]: RX2 slot open, Freq = 923300000
>
> [DBG ][LMAC]: ACK_TIMEOUT Elapses, Retrying ...
>
> [DBG ][LMAC]: TX: Channel=52, TX DR=0, RX1 DR=10
>
> [DBG ][LSTK]: Transmission completed
>
> [DBG ][LMAC]: RX1 slot open, Freq = 903700000
>
> [DBG ][LMAC]: RX2 slot open, Freq = 923300000
>
> [DBG ][LMAC]: ACK_TIMEOUT Elapses, Retrying ...
>
> [DBG ][LMAC]: Trading datarate for range
>
> [DBG ][LMAC]: TX: Channel=55, TX DR=0, RX1 DR=10
>
> [DBG ][LSTK]: Transmission completed
>
> [DBG ][LMAC]: RX1 slot open, Freq = 912700000
>
> [DBG ][LMAC]: RX2 slot open, Freq = 923300000
>
> [ERR ][LSTK]: Retries exhausted for Class A device
>
>  Transmission Error - EventCode = 4

As you suggested, I changed the tx buffer size in the mbed_app.json, but it still throws the errors.
The changes in the config file are:
"target_overrides": {
        "*": {
            "platform.stdio-convert-newlines": true,
            "platform.stdio-baud-rate": 115200,
            "platform.default-serial-baud-rate": 115200,
            "lora.over-the-air-activation": true,
            "lora.duty-cycle-on": true,
            "lora.phy": "US915",
            "lora.tx-max-size": 255,
            "lora.device-eui": "{ my device eui }",
            "lora.application-eui": "{ my app eui }",
            "lora.application-key": "{ my app key }",
            "mbed-trace.enable": true
        },

I also set "main_stack_size":      2048, due to the ST Board RAM (and I have a thread working too).
Regarding to the additional specifications:

The Mbed OS I'm not sure the specific version but I forked it from master Mbed OS just 12 days ago. I did the max_sys_rx_error hack posted in the board problem, because the targets were presenting this error.
Region of operation: US 915. I am located in Colombia, LA.
Network Server: Private LoRaServer. (It works fine)
Message type: Common uplink.
Message length: around 55-60 bytes.
Data rate and other parameters: not yet defined, I have only 1-4 nodes connected to my Laird gateway, so, no restrictions set yet.

Thank you in advance and happy new year.
lorawan-log-255.log

@sagilar There are a few things that I wish to highlight here.
Problem 1 As you are in US, you must check how many channels your Base Station (Laird Gateway) supports.
I can see from the trace that you are hopping over all 72 channels. I doubt that there is a Base Station that supports all 72 channels at the moment.  A quick google search tells me that most of the Laird models support 8 channels. So the first thing you need to do is to check what FSB (Frequency sub-band) Base Station is configured with. Then you need to set that same FSB to the device.  Check this text to learn more about setting an FSB to Mbed LoRaWAN stack https://github.com/ARMmbed/mbed-os/blob/master/features/lorawan/FSB_Usage.txt
Problem 2 I would not trust setting max-sys-error to 100ms or something. This value is too large and doesn't make any sense. Currently we use 5ms because that's the timing error what we expect
due to the use of event queue. This value is used in an algorithm that calculates the times to open RX windows. If you give too large values, the radio starts to receive way too early and remains in receive mode for a very long period of time defeating all the purposes of a low powered WAN. Plus this also means that we essentially don't really know what exactly the timing drift is for our system and may ruin all time sensitive operations. The sole purpose of this value being configurable is that cheaper crystals cannot be precise so we can handle a ms or two in software that's it. We can't rely on it to mask out faulty crystals in their entirety.
I would recommend use the default value and sort your crystal issue rather than masking it with too large max-sys-error.  I suppose you are using DISCO_LRWAN1 board. So follow the same link you gave me for correction.
Problem 3 Data rate has gone too low sometimes, i.e., DR0 and your packet cannot be sent as at DR0 you can send only 11 bytes.
Let me explain what's happening here. Most of the times, the device did not hear from the Network Server, no ack (I suppose you sent at a wrong channel, nobody was listening). And you have ADR on. So the device tries to get more range as it thinks that it is out of range. It acquires range by lowering data rate but then it cannot send your message out because the current data rate doesn't allow. Unfortunately, at the moment there is no Fragmentation support in the stack (it's coming :), spoiler alert ) .
You can disable adaptive data rate and set a fixed data rate that you are sure that your message will go out. The algorithm that trades data rate for range, doesn't apply if you have ADR disabled.
Disable ADR and set a custom data rate after Joining.
If you have anymore questions, please ping me freely.


How to make it work in MacOS

Awesome work!
Is there a way to make this work on MacOS?
New-Object : Exception calling ".ctor" with "0" argument(s): "The chromedriver file does not exist in the current directory or in a directory on the PATH environment variable. The driver can be downloaded at http://chromedriver.storage.googleapis.com/index.html."
At /Users/mkellerman/.local/share/powershell/Modules/Selenium/1.1/Selenium.psm1:4 char:5
+     New-Object -TypeName "OpenQA.Selenium.Chrome.ChromeDriver"
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (:) [New-Object], MethodInvocationException
+ FullyQualifiedErrorId : ConstructorInvokedThrowException,Microsoft.PowerShell.Commands.NewObjectCommand

You cannot call a method on a null-valued expression.
At /Users/mkellerman/.local/share/powershell/Modules/Selenium/1.1/Selenium.psm1:34 char:5
+     $Driver.Navigate().GoToUrl($Url)
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull

I made it work on Ubuntu which should be similar for MacOS.
Step 1: Install the latest version
As of this writing, you will need the beta version, "1.3.0". In a PowerShell terminal, type the following:
Update-Module Selenium -AllowPrerelease
Step 2: Fix the permission problem on the module's binaries

Open a terminal window
Navigate to the location where the PowerShell modules are installed for your system. For this example, let's assume the module was installed at "~/.local/share/powershell/Modules/Selenium/1.3.0/".
cd ~/.local/share/powershell/Modules/Selenium/1.3.0/
Execute the following command to add the "Execute" permission
For Mac OS:
chmod +x assemblies/macos/chromedriver
chmod +x assemblies/macos/geckodriver
For Linux:
chmod +x assemblies/linux/chromedriver
chmod +x assemblies/linux/geckodriver

That's it!! .. or at least that is all it took for me running on Ubuntu. I haven't tested on MacOS but it should have the same result.
I didn't have time to try to do a pull request to help the maintainers but at least this may help the next person tripping over the same problem. For the maintainers, Good luck overcoming the permissions problem. I am sure i am not the only one looking forward to the next commit version that does not require the above hack.

@mkellerman MacOS should work I know I added and tested it.
The only issue we have at the moment with Linux and MacOS is when installing from PSGallery the execution permissions do not transfer to UNIX.
So you will have to run chmod +x on the Macos assemblies.
chmod +x assemblies/macos/chromedriver chmod +x assemblies/macos/geckodriver
Let me know if you need further assistance.


Add Gradle Security Recipe Converting HTTP -> HTTPS

@Test
fun updateUnwrappedInvocationToUseHttpsSingleQuote() = assertChanged(
    before = """
        repositories {
            maven { url 'http://repo.spring.example.com/libs-release-local' }
        }
    """,
    after = """
        repositories {
            maven { url 'https://repo.spring.example.com/libs-release-local' }
        }
    """
)

Update all  repository declaration sites to use HTTPS

Merged with 659b09aaff3635077532fb4802e0dd0bf890008f. Happy to talk about a few of the polishes a bit later when you have a chance. Notably use of ListUtils.mapFirst.


make generate was deleted

What happened?
Since commit a604844380250b2ab6dc0f043c0b71a6785529ad make generate is missing in the Makefile.
How to generate the *.deepcopy.go files?

make manifests


UE4 changes: Added fused-mad pass and a few fixes for DXC related issues.

Hi all,
One of my former colleagues implemented a fused-multiply-add pass, made a few fixes to improve robustness (related to DXC generated SPIR-V), and I made some minor adjustments to the PR.
We would like to get these changes into the origin repository to simplify our sync iteration.
Any feedback is welcome.
Thank you and kind regards
Lukas

Hi @s-perron, of course we need to address certain fixes on a case to case basis, but at the end of the day we do have a very large foundation of shaders that help us to reveal bugs in the shader compiler pipeline from which each of us can benefit. We just need to figure out whether a bug comes from our shaders or from one of our compiler dependencies. I'd be glad if you can help us track down what fixes are workarounds and should be moved to a different project and which one are reasonable fixes to SPIRV-Tools.
While I'm responsible for this PR, the original changes were developed by one of my former colleagues and I took over his work. My apologies for the cases were I missed some adjustments for the pull request.
Thanks and kind regards
Lukas

Sorry, by PR I meant pull request not project.  I want to review them separately.  Also, have tests for each fix, so we can easily identify regressions.

@s-perron I made several adjustments according to your review feedback. Let me know if I missed something you want to be changed. Apart from that: you mentioned you'd prefer to have that in multiple PRs. I thought the number of files might be okay for one PR, but if you still prefer a separation I can do that after I got everything else straightened out.
Thanks.
Lukas

I'll take a look tomorrow.

I'd be happy to get some help with the unit tests as they seem to be a bit more advanced that just providing a small SPIR-V module.
I'll take care of the remaining change requests, but it might take some time as I can't work on them every day.
Thank you

For the ADCE unit tests, you want to write a test where the module does not change.  A good template for this kind of test is https://github.com/KhronosGroup/SPIRV-Tools/blob/master/test/opt/aggressive_dead_code_elim_test.cpp#L3928.
For your test, all you need to do is copy that whole "TESTF" block to the end of the file.  Change LiveNestedSwitch to a name that is meaningful for your tests.  Change the contents of text to be the spir-v for the small module the exercises your code.  Note that if the instructions are one per line, and are fully left justified.  The test will fail with any other format.
The unit tests for the folding changes are a little different.  We've built some infrastructure so that when looking at the test, it is obvious what you are trying to fold.  In your case, we will want to add something to the float constant floating test suite: https://github.com/KhronosGroup/SPIRV-Tools/blob/master/test/opt/fold_test.cpp#L1502.  I'm guessing that we will end up with similar to https://github.com/KhronosGroup/SPIRV-Tools/blob/master/test/opt/fold_test.cpp#L1581.  You have some instruction where at least one of the parameters is defined by OpConstantNull.
The unit tests for FusedMultiplyAddPass will end up with two flavors.  You can start by coping the boiler plate from another pass, say strength_reduction_test.cpp.  You can delete the first two using statements, and rename the third.
The two tests that you will need to write will be the "no change" tests just like those in ADCE.  For the tests where things change, you can use a match test.  The BasicReplaceMulBy16 test in the strength reduction is a good example to look at.  It has some explaination.  The basic idea is that you give the input module in the "text" variable.  Comment with "CHECK:" are command to the pattern matches that says what patterns to look for in the output.  These commands are the same as LLVM filecheck.
Let me know if you need more information.  If you add tests to the PR even if they do not work, I can help you debug the problems.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: LukasBanana:x: marksatt-pitbullYou have signed the CLA already but the status is still pending? Let us recheck it.

@LukasBanana Are you still working on this?

Hey @s-perron, my apologies for the long delay, I had to hold this for a while now due to other tasks. Now that the focus of my tasks shifted more towards Vulkan/DXC again, I will probably have more time to address the change requests. Since you requested to have this split into multiple PRs anyway, I think it's fine if you close this PR for now and I'll open new smaller PRs as soon as I have the requested adjustments ready.

Okay.  I will close this and wait for the new PRs.


Try out a new interface for Umem and Frames

This should make it easier to handle Frames living in Umem similar
to a Box<[u8]>. Frames now own the MmapArea in which they live via
a shared Arc.
This is not yet finished as all the tests and dev1_to_dev2 examples
still need to be converted to the new interface. But it should give
an a idea of how a new interface could look like.

MmapArea is sharedly owned by:

all Frames
the Umem that created the area

Umem is sharedly owned by:

all Sockets that were created with it

a Socket is sharedly owned by:

its TxQueue
its RxQueue

This should make sure that there are no dangling Frames or *Queues.

Closing this re https://github.com/DouglasGray/xsk-rs/issues/7#issuecomment-1030942194. I appreciate the PR nonetheless!


Update README.md and index.md

Ammend files with personalised info for Salsey
Change CI badge for README correctness

Codecov Report

Merging #53 (4ea5260) into master (ac0bbb3) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #53   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


I can't use custom login button

I couldn't use it with custom button. It wants auth provider, but useGoogleLogin cannot be used in auth provider. Can you help me? It would be nice if the client id could be sent as options in useGoogleLogin.

Hello @koraykavruk,
Thank you for being the first one to open an issue :D,
We need to add GoogleOAuthProvider component (step number 3 in how-to-use) and pass clientId as a props, which is normal context provider similar to store provider of redux as an example.
you can add provider any where you like to add it is just context provider which will provide all values to its descendent
if you provided in App component for example
export default function App() {
  return (
    <GoogleOAuthProvider clientId="xxxx">

@react-oauth/google

        <LoginPage />

    </GoogleOAuthProvider>
  );
}

function LoginPage() {
  const login = useGoogleLogin({
    onSuccess: tokenResponse => {
      console.log(tokenResponse);
    },
  });

  return (

      <button onClick={() => login()}>Login with google✌</button>

  );
}

useLogin is used in component LoginPage, which is rendered inside GoogleOAuthProvider, it can be at any level of react components tree
if you provided around  in react entry file. for example index.js in create-react-app
ReactDOM.createRoot(document.getElementById('root')!).render(
  <GoogleOAuthProvider clientId='xxxx'>
    <React.StrictMode>
      <App />
    </React.StrictMode>
  </GoogleOAuthProvider>,
);

and you can use the hook inside you  component for example because you are rendered inside the provider.
unfortunately changing useGoogleLogin api to have clientId, will require changes in the hole package which will increase its size and I consider the size to be small as possible (check bundlephobia).
and the effort of adding the  is a small step.


Implement an add application workflow

Implements the saving functionality of adding an application.

Looks good! When I run it, it still gives a warning about "non-serializable values", but other than that it looks like it works. Do you think the warning is significant enough to warrant waiting for a merge, or do you think I can merge now?

I believe the last commit should fix the issue.  Let me know if you still see it.

Looks good :)


when producer's cursor overflow, BlockingWaitStrategy#waitFor is there a dead cycle?

when producer's cursor overflow, BlockingWaitStrategy#waitFor is there a dead cycle?
When there is a situation：
producer's cursor is cursorSequence.get() will equal (Long.MAX_VALUE + 1 = -9223372036854775808),
but consumer's sequence expect  (Long.MAX_VALUE - 1 =<PHONE_NUMBER>854775806)
The following conditions will never be met
if (cursorSequence.get() < sequence)
{
synchronized (mutex)
{
while (cursorSequence.get() < sequence)
{
barrier.checkAlert();
mutex.wait();
}
}
}
    while ((availableSequence = dependentSequence.get()) < sequence)
    {
        barrier.checkAlert();
        ThreadHints.onSpinWait();
    }

===========================================================

At 1B events per second, this will take roughly 270 years to occur. So we don't worry about it.


Custom code-block colours

The current JSON code-fences use an unfortunate green/red colour combo, which I'd like to change!
The colours are defined in pygments.css. Unsure of the best approach to extending this / overwriting these in nextstrain.css but if someone could provide the framework I'll happily change some colours 😄
An example:

The supported way to do this with Sphinx and Pygment is to set the Sphinx option, pygments_style, controlling the Pygments style to use: either one of the builtin styles or a custom, plugin-provided style. A custom style would be part of this nextstrain-sphinx-theme package and registered as a Pygments plugins in our setup.py here.
The unsupported way would be to override the specific CSS used for highlighting in Sphinx's HTML output, e.g. something like:
.highlight-json .nt { color: purple } /* NT = Name.Tag = JSON object field */

Upside is we can restyle JSON highlighting without affecting other highlighted blocks that may contain Name.Tag tokens (produced by Pygments lexers).
Downsides are that this will break if the Pygments JSON lexer changes or the CSS generation changes, and it won't apply to non-HTML output. (Not sure if these get any use currently, though I believe RTD is producing them.) Other downside is we can't restyle whole families of lexed tokens, like the Name family, but only individual token types directly, like Name.Tag.

Builtin styles! Yay! Now to choose one... I've always liked solarized-light and I think a (subtle) background colour for code blocks would be a good idea.

Here's how https://github.com/nextstrain/docs.nextstrain.org/pull/113 looks after adding pygments_style = 'solarized-light' to the docs.nextstrain.org config - much better in my opinion!

I attempted to add this to our theme (i.e. this repo) via changing https://github.com/nextstrain/sphinx-theme/blob/eb4f16c77c99992808bf45a36ebbe1abfa6d61bf/lib/nextstrain/sphinx/theme/theme.conf#L5 to 'solarised-light'  but the rendered HTML test pages from this repo still used the default style. I couldn't actually find the docs on how to develop this theme locally -- I was using python3 -m pip install -e . and make html which I'm guessing isn't right?

Hmm. I've always found Solarized Light to be a bit low contrast in many cases, e.g. as in here

I attempted to add this to our theme (i.e. this repo) via changing [theme.conf] to 'solarized-light' but the rendered HTML test pages from this repo still used the default style. I couldn't actually find the docs on how to develop this theme locally -- I was using python3 -m pip install -e . and make html which I'm guessing isn't right?

That's the right thing to do… and it works for me (see screenshot above). Maybe you need a make clean first? The change to theme.conf won't be picked up as a change to the build dependencies.

Another example of where I think Solarized Light is low contrast and (de)emphasizes the wrong things:


Eloquents attach association doesn't prevent sql injection

When
// inject single quote in array
$partIds = ["1'", "2'"];
$model->cars()->attach($partIds);
Query will crash, so vulnerabilities will able to attack by sql injection

Seems fine. You need a better example.

@mantas-done Can you test by pass role ids in request role_ids[]=1%27&role_ids[]=2%27
Then use like this
$user->roles()->attach($request->get('role_ids'))
Thanks for checking

No crash or sql injection.

@mantas-done , are you test on Laravel Framework or Lumen? what laravel version you test?
I'm using : "laravel/lumen-framework": "5.8.*",

Laravel 5.8 isn't supported anymore (from yesterday). https://laravel.com/docs/master/releases

@mantas-done , okay, I got it thanks

When you say it crashed, what error did it give?

@rs-sliske
[2020-02-27 08:59:29] local.ERROR: PDOException: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'category_id' at row 1 in /var/www/html/mms_service_announcement_source/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:117 Stack trace: #0 /var/www/html/mms_service_announcement_source/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php(117): PDOStatement->execute(NULL) #1 /var/www/html/mms_service_announcement_source/vendor/illuminate/database/Connection.php(458): Doctrine\DBAL\Driver\PDOStatement->execute() #2 /var/www/html/mms_service_announcement_source/vendor/illuminate/database/Connection.php(657): Illuminate\Database\Connection->Illuminate\Database\{closure}('insert into an...', Array)
#3 /var/www/html/mms_service_announcement_source/vendor/illuminate/database/Connection.php(624): Illuminate\Database\Connection->runQueryCallback('insert into an...', Array, Object(Closure)) #4 /var/www/html/mms_service_announcement_source/vendor/illuminate/database/Connection.php(459): Illuminate\Database\Connection->run('insert into an...', Array, Object(Closure))
#5 /var/www/html/mms_service_announcement_source/vendor/illuminate/database/Connection.php(411): Illuminate\Database\Connection->statement('insert into an...', Array) #6 /var/www/html/mms_service_announcement_source/vendor/illuminate/database/Query/Builder.php(2646): Illuminate\Database\Connection->insert('insert into an...', Array)
#7 /var/www/html/mms_service_announcement_source/vendor/illuminate/database/Eloquent/Relations/Concerns/InteractsWithPivotTable.php(259): Illuminate\Database\Query\Builder->insert(Array)
#8 /var/www/html/mms_service_announcement_source/app/Repositories/AnnouncementRepository.php(67): Illuminate\Database\Eloquent\Relations\BelongsToMany->attach(Array)
#9 /var/www/html/mms_service_announcement_source/app/Http/Controllers/V1/AnnouncementController.php(83): App\Repositories\AnnouncementRepository->create(Array)
#10 [internal function]: App\Http\Controllers\V1\AnnouncementController->store(Object(Laravel\Lumen\Http\Request))`

that error doesnt indicate sql injection, it is just that you dont have any validation to ensure that the values are correct type/size


[BUG] mj-raw does not output raw input

Reproduction Steps:
Sandbox:
https://codesandbox.io/s/jv15p3pj9
Output HTML:
http://codebins.com/bin/4ldqokt
Expected behavior:
I expect everything inside mj-raw to not be touched
Observed behavior:
For some reason MJML is transforming it to like this, with nothing inside the for loop rendering an empty output:
      {% for line_item in line_items %}

    {% endfor %}

Screenshots and GIFs
Input:

Output:

MJML version:
3.3.5

Saw the comment here https://github.com/mjmlio/mjml/issues/996
Encoding html entities fixes this issue for 3.3.5. I understand it's fixed in v4

Hi
Then we can close it 👍

Observed parsing issue using freemarker syntax inside
<mj-raw>
     <#if template.variable??>
         ${template.variable}
      </#if>
</mj-raw>

Expected behavior:
All the code inside mj-raw tag should not be touched and render correctly.
I've tried to wrap the freemarker code inside a
 but no success.
You can try the code on mjml try it live.
Error :
element parse error : Error : invalid tagName: #if
end tag name: #if does not match the current start tag name: mj-raw

MJML 4

Can you share the whole template because it's working here
On Thu, Mar 8, 2018 at 8:44 PM, asaidi<EMAIL_ADDRESS>wrote:

Observed parsing issue using freemarker syntax inside

     <#if template.variable??>
         ${template.variable}

Expected behavior:
All the code inside mj-raw tag should not be touched and render correctly.
I've tried to wrap the freemarker code inside a  but no success.
You can try the code on mjml try it live https://mjml.io/try-it-live/.
Error :
element parse error : Error : invalid tagName: #if
end tag name: #if does not match the current start tag name: mj-raw
MJML 4
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/mjmlio/mjml/issues/998#issuecomment-371601385, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAizzTJuHXLChAFWiF_No_bC4F9pyGnwks5tcYodgaJpZM4SKzyf
.

--
Cordialement,
Maxime BRAZEILLES

<mjml>
  <mj-body>
    <mj-container>
      <mj-section>
        <mj-column>
          <mj-raw>
            <#if template.variable??>
              ${template.variable}
            </#if>
          </mj-raw>
        </mj-column>
      </mj-section>
    </mj-container>
  </mj-body>
</mjml>

There's no more mj-container in MJML4. Can you double check your version ?
On Thu, Mar 8, 2018 at 9:10 PM, asaidi<EMAIL_ADDRESS>wrote:

            <#if template.variable??>
              ${template.variable}

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/mjmlio/mjml/issues/998#issuecomment-371608984, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAizzVQynkmLCurK2yRNf_tYYWKw6iM4ks5tcZAggaJpZM4SKzyf
.

--
Cordialement,
Maxime BRAZEILLES

Uninstalled MJML and re-installed it. Works fine now.
mjml-core: 4.0.0
mjml-cli: 4.0.0

ps: mj-container is still used in the MJML4 doc, it's confusing.
Thanks

I still see the issue when using mj-raw inside td tag
For
<mjml>
  <mj-body>
    <mj-table>

            <ms-text>Text</ms-text>

            <mj-raw>
              DO NOT PARSE
            </mj-raw>

    </mj-table>

  </mj-body>
</mjml>

Outputs:

        <ms-text>Text</ms-text>

        <mj-raw>
         <![CDATA[
              DO NOT PARSE
         ]]>

There's no need to add an mj-raw inside a ending tag as mj-table

But MJML breaks my template code otherwise

  ${ENV,var="HEROKU_APP"}

Becomes (notice spaces around HEROKU_APP):

  ${ENV,var="HEROKU_APP"}

You can try on MJML 4.1 latest beta it should be fixed now

It's normal as you're using double quotes inside double quotes which isn't valid in HTML or any language for the matter. Use single quotes inside double quotes
${ENV,var="HEROKU_APP"}


Breadcrumbs outline filtering mode is problematic

I don't know, how better to name this component, but here's the picture:

…it makes me wondering, why this outline is NOT set to "filter" by default?
The items in the outline are sorted in the order of their appearance in the file, which makes it well likely that similar symbols may be spaced by a lot of unrelated lines and will not be immediately reachable.
Worse yet, setting outline mode to "filter" will not be remembered. And knowing not the name of the feature, I can't say if it is at all configurable in the settings. Any help?

So, this is breadcrumbs. Thanks, changed the title to be more relevant.


Adaptive Batching v2

TODO: Add tests

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1176/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1189/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1197/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1198/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1199/
Test FAILed.

@Corey-Zumar Is this ready for review yet?

@dcrankshaw I'll add some documentation and have it ready for review within the hour. Tests still need to be written. I've merged the branch associated with #393 into this PR; that explains the large diff. This will be easier to review once #393 is merged.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1293/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1295/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1296/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1454/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1514/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1516/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1517/
Test FAILed.

@dcrankshaw If you have time to take a look, dlib needs to be included as a static library rather than an interface library (the debug build fails with the interface library setup). I was running into export issues at link time when attempting to link a statically-defined dlib to libclipper.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1528/
Test FAILed.

Okay I'll take a look

@Corey-Zumar fixed the static lib issue. I'll keep on eye on the tests tonight and try to get this merged. Are there any known outstanding issues or are we just waiting for the PR to get through jenkins?

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1532/
Test FAILed.

@Corey-Zumar Do you still need to write tests for this? Jenkins is failing because container_tests.cpp is calling functions that no longer exist.

@dcrankshaw yes, I still need to write a couple tests. Will aim to do that tonight.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1541/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1542/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1544/
Test FAILed.

jenkins test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1550/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1551/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1554/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1555/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1557/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1558/
Test FAILed.

jenkins test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1559/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1562/
Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1563/
Test FAILed.

jenkins test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1564/
Test FAILed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Clipper-PRB/1565/
Test PASSed.


Subscription got deleted by mistake

Hi,
our Teams call logging had been running without issues for a month or so, then one time the update-subscription got a 404 back from MS Graph - even though the subscription did exist - so the update-subscription function deleted it from the blob store and we stopped getting anymore logs once it expired
here's the logs from Splunk...
teams-calls-20211010.csv
is it possible to change the logic of the update-subscription function so it only remove subscriptions from the blob store if they are passed their expiry date? this would stop what looks like a temporary blip in MS Graph leaving you without any logs
cheers,
SK

https://github.com/splunk/azure-functions-splunk/pull/3


fix issue 971: to have ability to ignore all assert when expected value is null

Check List:

Fixes #971
Unit tests : YES
Javadoc with a code example (on API only) : YES
I'm sorry for my disturbance. I have already made a same pull request,so you can just ignore this pull request and close it.Actually, it's a course practice which demands me to make a pull request and the teacher has some specific requirements on the pull request. My last pull request didn't meet the requirements so I make a new one. I'm sorry for my disturbance again and you can just ignore this pull request and close it.

@wuqihan837 I suggest you to look for easier contributions, this one might be too complicated.


Enable-SPOCommSite not working

Running the below command doesn't show any error, but it also doesn't convert the site completely into a Communication site. For example, page Full-Width section is missing, top navigation is still shown, and horizontal navigation is not in place. The only change is that a new homepage is created with one Full-Width section, but it's not possible to add additional Full-Width sections in this new homepage
Enable-SPOCommSite -SiteUrl https://contoso.sharepoint.com
Microsoft.Online.SharePoint.PowerShell Module version is 16.0.21213.12000

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5cc9a3da-e451-85a0-a093-ca081c662e20
Version Independent ID: a6989bf6-418d-a2c6-0323-d23b629fcd26
Content: Enable-SPOCommSite (SharePointOnlinePowerShell)
Content Source: sharepoint/sharepoint-ps/sharepoint-online/Enable-SPOCommSite.md
Product: sharepoint-server-itpro
GitHub Login: @trent-green
Microsoft Alias: trgreen

Hello @ahamin01 how are you? hope you are doing good
So I can reproduce to understand if we need to adjust documentation (we are limited only to documentation fixes), can you please confirm you have followed this requirements https://docs.microsoft.com/en-us/sharepoint/modernize-classic-team-site
Thank you

@ahamin01 Hello, could you see my last comment here? Thanks

Hello @get-itips,
Yes, indeed. I followed that article and ensured that all the below points are met. I am even testing this on new sites, but with no hope

The site template is STS#0
The site is top-level site in the site collection.

The SharePoint Server Publishing Infrastructure is not enabled and has never been enabled on the site (I even tested running the command on new site).

The cmdlet does some stuff, but not all. For example, it creates a new page and makes it the home page of the site, but somehow Full-Width sections are not available to be added to the site pages :-(

Hello @ahamin01
Thanks for clarifying, in that case, as here we are limited to documentation changes and improvements, the best would be to open a support request from your tenant, support services will be able to help you in your specific scenario.
Thank you

@get-itips Thank you very much for the contribution and sharing this explanation. @ahamin01 Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed to close it as here we are limited to documentation fixes and improvements only.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


feat: add perfect number

Added perfect numbers with test.

Thank you for the review, I have implemented your suggestion.

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

:exclamation: No coverage uploaded for pull request base (master@c8a4b98). Click here to learn what that means.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #221   +/-   ##
=========================================
  Coverage          ?   96.27%
=========================================
  Files             ?       97
  Lines             ?     1797
  Branches          ?      347
=========================================
  Hits              ?     1730
  Misses            ?       67
  Partials          ?        0

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


[camera] Fixed captured image stretching issue on some low end android devices

Description
This PR fixes an issue where the captured image using the camera plugin comes out as stretched/inappropriate aspect ratio on some low end android devices.
I encountered this issue few weeks ago, with devices like Vivo, and redmi devices.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x ] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

I believe this change is important not only on low-end devices. The general rule of thumb is that the aspect ratio of capture and preview should match.
Even if there is no stretching (which is a device bug), the user expects the captured picture to match the viewfinder. If the aspect ratios differ, the picture will either have extra unintended content, or crop out some content. Worse, there is no guarantee which case will happen for given resolutions (different devices can handle this differently).
Second, switch of aspect ratio often results in extra delay, lost focus, bad exposure compensation – even if the capture comes out formally correct.

I'm going to close the PR because the CLA is not signed. Feel free to ping me when the CLA is signed and I'll re-open the PR. Or you can open a new PR after signing the CLA.

I'm going to close the PR because the CLA is not signed. Feel free to ping me when the CLA is signed and I'll re-open the PR. Or you can open a new PR after signing the CLA.

@cyanglaz Hey I signed the CLA.
Could you please re-open the PR ?

The Android camera implementation just went through a major overhaul; is this PR still needed in the current implementation?
If so, this will need to be updated to resolve the conflicts with master, as well as have tests added per repository policy (see the link in the checklist), before it can be reviewed.

@techievbv You'll also need to follow the instructions in the comment above to confirm your CLA.

Thank you for your contribution. I'm going to close this PR for now since there are outstanding comments, just to get this off our PR review queue. Please don't hesitate to submit a new PR if you have the time to address the review comments. Thanks!


Failed Setup.

This error originated from a custom integration.
Logger: custom_components.ripple_energy.coordinator
Source: helpers/update_coordinator.py:315
integration: Ripple Energy
First occurred: 17:22:29 (12 occurrences)
Last logged: 17:27:44
Hi,
I found this integration for HA and very grateful for it.  Unfortunately it's not working for me.  I'm guessing the API have been modified since this release?
I'm a member of Kirk Hill and Derril Water if that info is any help.
Unexpected error fetching Kirk Hill data: 'timestamp'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 315, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ripple_energy/coordinator.py", line 43, in _async_update_data
await self.asset.update_data()
File "/usr/local/lib/python3.12/site-packages/pyrippleapi/generation_asset.py", line 175, in update_data
await self.get_telemetry(generation_data["generation"])
File "/usr/local/lib/python3.12/site-packages/pyrippleapi/generation_asset.py", line 122, in get_telemetry
self._latest_telemetry["timestamp"],
~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
KeyError: 'timestamp'

Yes, looks like that is the version I have.

The screenshot is just showing the latest version available rather than what's installed. I assume if you found this integration recently so you are probably on the latest version.
I will need some information from you to help fix this:
Can you check this file on your homeassistant installation
/homeassistant/custom_components/ripple_energy/manifest.json
The last value in the JSON in the version you currently have installed.
If the version is 2024.2.1 then can you please check what's in this file
/homeassistant/custom_components/ripple_energy/const.py
The last value is a list which contains all the supported Ripple assets, it should just be ASSETS = ["Graig Fatha"]
As above the integration only supports Graig Fatha currently for a couple of reasons, it's currently the only operational asset from Ripple, and this is the only project I'm invested in so I don't have access to see what the API response for Kirk Hill and others look like.
I'm happy to add support for Kirk Hill etc if you are able to provide me the API response you get from ripple. You can do this by following the below steps, I just need a dump of the information contained in the "generation_assets" array.
`Get your Ripple API key
Login to your Ripple Dashboard
In a new tab, paste in https://rippleenergy.com/rest/member_data/
Back in your Ripple Dashboard, click on the word Energy at the bottom left of the screen, this will copy your API key to your clipboard
Return to the other tab and paste in your API key after member_data/`

Ah, sorry. I didn't realise there wasn't support for anything other than Graig Fatha.  Makes sense.  I just found your work on github and gave it a go!
If you're happy to add support for the projects I'm a member of then I'm happy to help.  See the output below and let me know if you want me to test anything.  Both projects only provide the basic initial data at present but obviously Kirk Hill should be imminent.
Let me know if I can help further.

Ripple output.json

Reference

Hi Ryan,
Thanks also for the work on this HA integration. I'm also a Ripple member waiting for Kirk Hill to come online and I installed this integration over the weekend. As I expected at the moment there were no devices or entities are appearing as yet, but I've just read through this issue and see that you need details of the Kirk Hill generation assets array before you can add support.
I think that this will include what you need:
"generation_assets": [{"name": "Kirk Hill", "type": "Windfarm", "status": "N/A", "total_capacity": 18.8, "total_capacity_units": "MW", "member_capacity": 1512.957, "member_capacity_units": "W", "member_expected_annual_generation": 4.8, "member_expected_annual_generation_units": "MWh", "generation": {"generation_unit": "kWh", "latest_telemetry": {}, "latest": {}, "today": {"from": "2024-05-13T00:00:00Z", "to": "2024-05-13T10:47:35.149Z", "contains_estimate": false, "generated": 0.0, "earned": 0.0}, "yesterday": {"from": "2024-05-12T00:00:00Z", "to": "2024-05-13T00:00:00Z", "contains_estimate": false, "generated": 0.0, "earned": 0.0}, "this_week": {"from": "2024-05-13T00:00:00Z", "to": "2024-05-13T10:47:35.149Z", "contains_estimate": false, "generated": 0.0, "earned": 0.0}, "last_week": {"from": "2024-05-06T00:00:00Z", "to": "2024-05-13T00:00:00Z", "contains_estimate": false, "generated": 0.0, "earned": 0.0}, "this_month": {"from": "2024-05-01T00:00:00Z", "to": "2024-05-13T10:47:35.149Z", "contains_estimate": false, "generated": 0.0, "earned": 0.0}, "last_month": {"from": "2024-04-01T00:00:00Z", "to": "2024-05-01T00:00:00Z", "contains_estimate": false, "generated": 0.0, "earned": 0.0}, "this_year": {"from": "2024-01-01T00:00:00Z", "to": "2024-05-13T10:47:35.149Z", "contains_estimate": false, "generated": 0.0, "earned": 0.0}, "last_year": {"from": "2023-01-01T00:00:00Z", "to": "2024-01-01T00:00:00Z", "contains_estimate": false, "generated": 0.0, "earned": 0.0}, "total": {"from": "2000-01-01T00:00:00Z", "to": "2024-05-13T10:47:35.149Z", "contains_estimate": false, "generated": 0.0, "earned": 0.0}}, "forecast": []}]
Thanks so much for taking this on - I'm sure that there will prove to be a large overlap between Ripple investors and HA users, all of whom will appreciate your work.

Thanks both for the info, this should now be fixed in the new version (2024.5.1). Let me know if still not working.

Hi Ryan,
I pulled the latest version (2014.5.1) and the setup failed, even after removing the previous version from HA, and reinstalling.
The error log is as follows:
This error originated from a custom integration.
Logger: custom_components.ripple_energy.coordinator
Source: helpers/update_coordinator.py:315
integration: Ripple Energy
First occurred: 16:27:35 (7 occurrences)
Last logged: 16:28:31
Unexpected error fetching Kirk Hill data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 315, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/ripple_energy/coordinator.py", line 43, in _async_update_data
await self.asset.update_data()
File "/usr/local/lib/python3.12/site-packages/pyrippleapi/generation_asset.py", line 178, in update_data
await self.get_generation(generation_data["generation"])
File "/usr/local/lib/python3.12/site-packages/pyrippleapi/generation_asset.py", line 145, in get_generation
self._generation_data["latest_earned"] = data["latest"]["estimated_savings"]
~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
KeyError: 'estimated_savings'

I've just pushed another version, 2024.5.2 which should fix this new error, let me know if you can now setup or if you are still getting errors.

2024.5.2 appears to be working fine for me.
1 device and 21 entities (6 of which are disabled by default) have appeared for Kirk Hill.
The data that I'd expect to see is there, but obviously no generation as yet - we'll know more next month.
Thanks very much Ryan!

Great thanks for confirming, you should get another 2 entities once Kirk Hill is operational also.


Integration Test Framework: Solve "port mapping quota" related to NodePort services

Cron job that cleans up port mappings are not in use.  Have to fix the cron job and then close if this continues to fix the issue


NavigatorIOS crash while navigating between components

Hi guys,
Really liking the hard work and thought going into React Native and thought i'd share any bugs I find while testing.
This happened while navigating between components using NavigatorIOS. Not really much more to say...
return UIApplicationMain(argc, argv, nil, NSStringFromClass([AppDelegate class]));
react-native/React/Views/RCTNavigator.m:387
2015-05-11 17:32:45.555 fitnessApp[1884:73204] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Cannot change subviews from JS without first locking.'
*** First throw call stack:
(
0   CoreFoundation                      0x000000010e9b2c65 __exceptionPreprocess + 165
1   libobjc.A.dylib                     0x000000010de24bb7 objc_exception_throw + 45
2   CoreFoundation                      0x000000010e9b2aca +[NSException raise:format:arguments:] + 106
3   Foundation                          0x000000010da39a57 -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 169
4   fitnessApp                          0x000000010d69e06c -[RCTNavigator insertReactSubview:atIndex:] + 684
5   fitnessApp                          0x000000010d6b6bff -[RCTUIManager _manageChildren:moveFromIndices:moveToIndices:addChildReactTags:addAtIndices:removeAtIndices:registry:] + 2703
6   fitnessApp                          0x000000010d6b5f79 __108-[RCTUIManager manageChildren:moveFromIndices:moveToIndices:addChildReactTags:addAtIndices:removeAtIndices:]_block_invoke + 153
7   fitnessApp                          0x000000010d6b03a3 __27-[RCTUIManager addUIBlock:]_block_invoke + 131
8   fitnessApp                          0x000000010d6b92a0 __29-[RCTUIManager flushUIBlocks]_block_invoke + 352
9   libdispatch.dylib                   0x00000001117dc186 _dispatch_call_block_and_release + 12
10  libdispatch.dylib                   0x00000001117fb614 _dispatch_client_callout + 8
11  libdispatch.dylib                   0x00000001117e3a1c _dispatch_main_queue_callback_4CF + 1664
12  CoreFoundation                      0x000000010e91a1f9 CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE + 9
13  CoreFoundation                      0x000000010e8dbdcb __CFRunLoopRun + 2043
14  CoreFoundation                      0x000000010e8db366 CFRunLoopRunSpecific + 470
15  GraphicsServices                    0x000000011250ca3e GSEventRunModal + 161
16  UIKit                               0x0000000110413900 UIApplicationMain + 1282
17  fitnessApp                          0x000000010d629c3f main + 111
18  libdyld.dylib                       0x000000011182f145 start + 1
19  ???                                 0x0000000000000001 0x0 + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException

which navigation caused this? push/pop/replace/etc?

There are some less disastrous issues with NavigatorIOS that I believe are tied to the locking (or lack thereof) of several functions. I'm going to try to address this issue: https://github.com/facebook/react-native/issues/476#issuecomment-99501667. if you can repro your issue I'd love to see if it is solved by the same thing.

Yeah replace & friends (that modify the stack in-place) are fairly broken at the moment :/ but I'm looking into fixing them.
Let me know if you can reproduce this, preferably by modifying the UIExplorer example in Examples/UIExplorer/Navigator

Closing because no follow-up about reproducing.


rustfmt crashes inside ./x.py test

I am trying to run the rustc tests, but rustfmt is crashing like given below. I am on macOS Monterey, XCode 13.3, on an M1 Macbook Pro.

$ ./x.py test
Updating only changed submodules
Submodules updated in 0.01 seconds
Building rustbuild
Finished dev [unoptimized] target(s) in 0.10s
Building stage0 tool tidy (x86_64-apple-darwin)
Finished release [optimized] target(s) in 0.11s
tidy check
Checking which error codes lack tests...
629 error codes
highest error code: E0787
Found 504 error codes
Found 0 error(s) in error codes
Done!
372 features
fmt check
rustfmt(7389,0x20133a600) malloc: *** error for object 0x6000036d4600: pointer being freed was not allocated
rustfmt(7389,0x20133a600) malloc: *** set a breakpoint in malloc_error_break to debug
Running "/Users/code/git/rust/build/x86_64-apple-darwin/stage0/bin/rustfmt" "--config-path" "/Users/code/git/rust" "--edition" "2021" "--unstable-features" "--skip-children" "--check" "/Users/code/git/rust/library/std/src/collections/hash/set.rs" "/Users/code/git/rust/library/std/src/collections/hash/set/tests.rs" "/Users/code/git/rust/library/std/src/collections/hash/map/tests.rs" "/Users/code/git/rust/library/std/src/sync/condvar.rs" "/Users/code/git/rust/library/std/src/sync/poison.rs" "/Users/code/git/rust/library/std/src/sync/barrier/tests.rs" "/Users/code/git/rust/library/std/src/sync/mutex/tests.rs" "/Users/code/git/rust/library/std/src/prelude/v1.rs" failed.

I realize things can be somewhat muddy given the subtrees/modules, but when you encounter an issue working in the rust-lang/rust repository it's typically best to report the issue in that same repository.
We're not doing any work with raw pointers in rustfmt, so I'd assume this is actually surfacing up from the compiler internals of which rustfmt is a consumer.
I'm going to reach out to the infra team to suggest that they transfer the issue, though I'd also encourage you to post some more specifics about your local environment where you're experiencing the issue, including the git details of your local rust-lang/rust repo

Based on chat in Zulip I'm going to close as a functional dupe of https://github.com/rust-lang/rust/issues/92173.
Seems you should be able to work around this by enabling jemalloc in your local config.toml file

Thank you, and apologies if this was misfiled. I was under the (probably wrong) assumption that the way the crash happens in stage0 rustfmt that it was a precompiled rustfmt that crashes. None of the suggestions in https://github.com/rust-lang/rust/issues/92173 worked for me and it didn't describe rustfmt, therefore I opened an issue here.

I'm seeing the same issue with my codebase after upgrading the toolchain to 1.60 (even though rustfmt version hasn't changed). The issue disappears if I downgrade to 1.59. That makes me wonder if it's a rustc issue in disguise.


Uninformative error message when query not found

Version: sparql-anything-v0.8.2.jar
This issue is not an important one. It could be a small cosmetic improvement.
When I tried to sa.run() a query as below, it failed because I mistyped the filename, with the error as below. I think the error message could be more informative, eg FileNotFoundError.
In [4]: sa.run(q='query1.sparql')
[main] INFO com.github.sparqlanything.cli.SPARQLAnything - SPARQL anything
---------------------------------------------------------------------------
JavaException                             Traceback (most recent call last)
Cell In[4], line 1
----> 1 sa.run(q='query1.sparql')

File ~\miniconda3\Lib\site-packages\pysparql_anything\sparql_anything.py:30, in SparqlAnything.run(self, **kwargs)
     23 """
     24 The run method replaces the regular command line execution.
     25 @param **kwargs The keyword arguments are the same as the regular
     26     flags for the Sparql Anything CLI, minus the hyphen.
     27 See the User Guide for an example.
     28 """
     29 command = cmd.RunCommand(kwargs, self.receiver)
---> 30 command.execute()

File ~\miniconda3\Lib\site-packages\pysparql_anything\command.py:159, in RunCommand.execute(self)
    157 """ instructions for a run request """
    158 args = super()._combine()
--> 159 self.receiver.main(args)

File ~\miniconda3\Lib\site-packages\pysparql_anything\engine.py:39, in Engine.main(self, args)
     37 def main(self, args):
     38     """ Wrapper for the SPARQL Anything main method. """
---> 39     self.reflection.main(args)

File jnius\\jnius_export_class.pxi:876, in jnius.JavaMethod.__call__()

File jnius\\jnius_export_class.pxi:1059, in jnius.JavaMethod.call_staticmethod()

File jnius\\jnius_utils.pxi:79, in jnius.check_exception()

JavaException: JVM exception occurred: Lexical error at line 1, column 14.  Encountered: <EOF> after prefix "query1.sparql" org.apache.jena.query.QueryParseException

Hi James,
I could implement a preliminary check on whether the file exists that returns a FileNotFoundError.
The JavaException however comes from SPARQL Anything and is simply thrown onto the terminal by PySPARQL.
@enridaga Thoughts? Should I go ahead and implement what I suggested above?


Upgrade to react-intl v5

Feature Request
As part of terra-application v2, react-intl needs to be upgraded to v5. As part of this upgrade terra-base and terra-i18n will be deprecated with their functionality moving to terra-application-base.
Description

The work for this has been started here: https://github.com/cerner/terra-application/tree/react-intl-take-2
There has also been work on updating the loaders here: https://github.com/cerner/terra-aggregate-translations
We might want to discontinue generating the loader file and dynamically import locale data in terra-application-base as well. This would significantly simplify the logic around loading the locales.
Additional Context / Screenshots
@ Mentions

Closed with #124


Possibly a color coding issue due to preprocessor directives

Wrong color coding for me:
First image: IEnumeble<Tuple... (line 78).

Second Image: colors of all preprocessor directives.

Hope this can help you make OmniSharp even better!
Best Regards,
Giacomo

One major reason I still use Visual Studio instead of VSCode is because of this issue ...and it has been reported multiple times.

@XeonG, I'm sure the team will fix it. :)

lol right, MS still can't even manage to implement the basics of scroll wheel cycling tabs let alone support a multiline tabbar... https://github.com/microsoft/vscode/issues/13902
despite other developers writing the code for it to, they can't even be bothered to implement it in the main codebase..

@XeonG As with everything, there is a cost to fixing bugs and making enhancements and we have to spend our resources wisely. This particular issue is a limitation of the textmate theme and will be resolved once we upgrade to providing semantic classification. The benefit of focusing on semantic classification as opposed to textmate is that it is a complete solution for the classification issues we have.

@XeonG As with everything, there is a cost to fixing bugs and making enhancements and we have to spend our resources wisely. This particular issue is a limitation of the textmate theme and will be resolved once we upgrade to providing semantic classification. The benefit of focusing on semantic classification as opposed to textmate is that it is a complete solution for the classification issues we have.

There are fixes and implementation to support both mousewheel tab cycling on the tabbar and also support for multiline tabbar functionality... how long could it possibly take to implement that with some customization options... seriously frankly I'm not even sure how it has taken this long... requests for those features have been around since vscode near came out..  user have become accustomed to such features in other software for 2 decades now.. its not new, though according to some of your staff behind stalling such things https://github.com/microsoft/vscode/issues/13902  its like some hard to add new thing.

Closing this as by design for now, since the only way to really support this is with semantic colorization, which LSP does not currently support. However, the good news is that semantic colorization will be coming to LSP (date unknown, but it won't be forever), and once that does, Roslyn has what it needs to provide the level of colorization needed here. So I'll close this out on that basis.


After upgrade, context error

版本信息

Flutter版本：[举例：v3.22.1]
flutter_smart_dialog版本：[举例：v4.9.7+7]

描述bug/需求
Just using showToast normally. After SDK Upgrades, Pub Upgrades, now every function triggers this.

问题demo
await SmartDialog.showToast('test', displayTime: Duration(seconds: 3));
PS: FlutterSmartDialog.init builded, Observer added. And works just fine before. I can't downgrade.

please give a simplified demo that can reproduce the problem and can be run directly

If you have an urgent need, you can temporarily reduce it to 4.9.6 version, 4.9.7 version has a big change

please give a simplified demo that can reproduce the problem and can be run directly

import 'package:flutter/material.dart';
import 'package:flutter_localizations/flutter_localizations.dart';
import 'package:flutter_smart_dialog/flutter_smart_dialog.dart';

void main() {
  WidgetsFlutterBinding.ensureInitialized();
  runApp(const AppTeste());
}

class AppTeste extends StatefulWidget {
  const AppTeste({super.key});

  @override
  State<AppTeste> createState() => _AppTesteState();
}

class _AppTesteState extends State<AppTeste> {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      useInheritedMediaQuery: true,
      navigatorObservers: [
        FlutterSmartDialog.observer,
      ],
      builder: FlutterSmartDialog.init(),
      localizationsDelegates: GlobalMaterialLocalizations.delegates,
      supportedLocales: const [Locale('pt', 'BR'), Locale('en', 'US')],
      theme: ThemeData(
        visualDensity: VisualDensity.adaptivePlatformDensity,
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.blue.shade900, surface: Colors.white, surfaceContainerHighest: Colors.white),
        useMaterial3: true,
        cardTheme: const CardTheme(surfaceTintColor: Colors.white, color: Colors.white),
        bottomSheetTheme: const BottomSheetThemeData(surfaceTintColor: Colors.transparent),
      ),
      debugShowCheckedModeBanner: false,
      home: const Test(),
    );
  }
}

class Test extends StatefulWidget {
  const Test({super.key});

  @override
  State<Test> createState() => _TestState();
}

class _TestState extends State<Test> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: SizedBox(
        height: MediaQuery.of(context).size.height,
        width: MediaQuery.of(context).size.width,
        child: Align(
          alignment: FractionalOffset.center,
          child: ElevatedButton(
            onPressed: () async {
              await SmartDialog.showToast('Test', displayTime: const Duration(seconds: 3));
            },
            child: const Text('Test'),
          ),
        ),
      ),
    );
  }
}

Little problem using the Builder  from MaterialApp, when the FlutterSmartDialog.init(), in my main code, it has DevicePreview.appBuild in the builder inside, removing it and after read through the 4.x.x Doc, find out the msg in show  functions should be emppty when use Custom with Builder.


[BUG] Profiling tool's task duration calculation is different than the Spark UI's calculation

Describe the bug
A clear and concise description of what the bug is.
In the profiling tool's output for "Job + Stage level aggregated task metrics", for a specific stage it has 3 tasks.
The duration_max/duration_min/duration_avg = 118/37/71.3(ms).
However the Spark UI shows the duration for those 3 tasks are: 88ms, 40ms and 17ms.
This is because, The tool calculate the duration based on event SparkListenerTaskEnd."Task Info"'s  "Finish Time" - "Launch Time".
However the Spark UI's duration is based on the event SparkListenerTaskEnd's Task Metrics named "Executor Run Time".
Here is one example(snippet of sample spark event log)
{
  "Event": "SparkListenerTaskEnd",
  "Stage ID": 40,
...
  },
  "Task Info": {
    "Task ID": 24,
...
    "Launch Time":<PHONE_NUMBER>994,
...
    "Finish Time":<PHONE_NUMBER>112,
...
 "Task Metrics": {
  ...
    "Executor Run Time": 88,

1623655483112-1623655482994=118 which is what profiling tool will use.
However Spark UI uses "Executor Run Time": 88.
Of course, this difference is very small and normally if task duration is at seconds level, there should be very obvious difference.
But it is always better to match Spark UI's metrics.
Steps/Code to reproduce bug
Please provide a list of steps or a code sample to reproduce the issue.
Avoid posting private or sensitive data.
Run the profiling tool on a spark event log with very small tasks(ms level). Then the difference is more obvious.
Expected behavior
A clear and concise description of what you expected to happen.
The profiling tool's task duration matches the Spark UI.
Environment details (please complete the following information)

Environment location: [Standalone, YARN, Kubernetes, Cloud(specify cloud provider)]
Spark configuration settings related to the issue

Profiling tool 21.06/21.08 ver.
Additional context
Add any other context about the problem here.

To be clear we just using the Spark TaskInfo duration. The taskInfo duration is the task launch time - finish time.  Launch time is from the scheduler point of view, so it will be longer than the executor run time metric task time.
But spark isn't using the executor run time metric either for the web ui, it actually calculates it with:
val launchTime = taskInfo.launchTime.getTime()
val finishTime = taskInfo.duration.map(taskInfo.launchTime.getTime() + _)
          .getOrElse(currentTime)
val totalExecutionTime = finishTime - launchTime
val executorOverhead = serializationTime + deserializationTime
val executorRunTime = if (taskInfo.duration.isDefined) {
          math.max(totalExecutionTime - executorOverhead - gettingResultTime - schedulerDelay, 0)
 } else {
          metricsOpt.map(_.executorRunTime).getOrElse(
            math.max(totalExecutionTime - executorOverhead - gettingResultTime - schedulerDelay, 0))
}

That should be really close to the executorRunTime metric because its removing all the serialization and scheduler overhead stuff.  You can see the else case uses the executorRunTime is duration isn't defined.
Both of these metrics can be interesting and we actually print both off. Duration and then we specifically have an executorRuntime_sum.
I think the thing we need to decide is what is this tool going to print.  Is it going to print the raw metric information or is it going to give metrics like the UI.  Or perhaps it should do both depending on who is looking at it.
I still don't necessarily consider this a must fix because we are just printing the metrics spark returns to us and we didn't really define what that is.  So the metric is valid its just not the same as the UI.

I am fine if we decide not to consider this as a bug since we used a little different way to calculate the duration.

Let me close the issue if we decide not to fix this or consider it as a bug.

I'd prefer to leave this open and decide what we want, like mentioned both stats might be nice to have.


Clarified that CheckInDay dimension contains an integer (1) instead o…

…f a string (Monday)

Docs Build status updates of commit e39040d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Advertising/hotel-service/reporting.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Quagga not consistently able to scan

The Quagga JS scanner is not consistently able to scan the bar code where as any off the shelf scanner is able to scan.
Could anyone please assist what might causing inconsistency in scanning. Notice sometimes there is an issue with the focus of the camera but not sure if related.
Appreciate any pointers with troubleshooting or root cause

https://github.com/ericblade/quagga2/assets/170431661/9e2eb03f-accb-4187-82ef-e6878cf10539
https://github.com/ericblade/quagga2/assets/170431661/35a583b6-64e5-4b9d-945c-91b782016331

Hi there!  Difficult to say without any information about what your program code is, or what sorts of barcodes (especially with a sample) you are trying to scan.  Please provide further information, and I'll see what I can do :)


python 3.9 support

As per our - not yet documented (https://github.com/quantumlib/Cirq/issues/3347) - python policy we should support 3 versions of python at a time. In Oct 2020, the stable version of Python 3.9.0 was released, we should support it.
This means adding 3.9 to the test matrix in .github/workflows/ci.yml python-version: [ '3.7', '3.8' ] for Ubuntu, Windows and MacOS builds, and working out all the dependency kinks.
@kevinsung started to pave the way with the issues he opened, someone just needs to work through them.

Due to https://github.com/quantumlib/Cirq/issues/3769 it looks like this depends on numba releasing version 0.53.0.


Let the app catch the Fn key press event

As a user, I may find my Fn button useless for me, and thus I may want to use it for switching language/layout.
Currently, it is absent in the list of keys to use.

The fix does not allow to combine with Fn key except for the cases when Fn is pressed last in the sequence.

Dropped this eventually, because it turned out to not work anywhere but Lenovo devices.


SoundCloudAudioSourceManager refactorings and scrubbing fixes

Had to fix the scrubbing and as I started I fixed some more. Merge it, if u want to.

Not really applicable anymore due to many changes to SC source.


Does not work on Windows 2008 R2 without SP1

The OS version of Windows 2008 R1 SP1 is 6.1.7601, donut works great from this version to latest Windows 2019. But on OS slightly older, it just won't run.
Environment

Windows 2008 R2 without SP1, no patch installed, aka 6.1.7600
donut 0.9.3 (master branch, built today)

Problem

shellcode is executed but .NET code does not run

Steps to reproduce the issue
Download lib.txt and rename it to lib1.cs, compile with:
C:\Windows\Microsoft.NET\Framework\v2.0.50727\csc -target:library lib1.cs

Create shellcode
%> donut-master\donut.exe -c Lib1.Class1 -m Test lib.dll

  [ Donut shellcode generator v0.9.3
  [ Copyright (c) 2019 TheWover, Odzhan

  [ Instance type : Embedded
  [ Module file   : "lib.dll"
  [ Entropy       : Random names + Encryption
  [ File type     : .NET DLL
  [ Class         : Lib1.Class1
  [ Method        : Test
  [ Target CPU    : x86+amd64
  [ AMSI/WDLP     : continue
  [ Shellcode     : "loader.bin"

Create header from loader.bin
xxd -i loader.bin > loader.h

Create main.c
#include <windows.h>
#include "loader.h"

int main(int argc, char **argv)
{
	LPVOID *buffer = VirtualAlloc(NULL, sizeof(loader_bin), MEM_COMMIT, PAGE_EXECUTE_READWRITE);
	memcpy(buffer, loader_bin, loader_bin_len);

	HANDLE hThread = (void*) _beginthread((void (*) (void*))buffer, 0, 0);
	WaitForSingleObject (hThread, -1);

	return 0;
}

Run on Windows 2008 R2 (No SP1), shellcode runs but no effect; Run on any other OS (2008 SP1, 2012 - 2019) with .NET 3.5 enabled, it works.
What I have tried
I tried to build the loader in debug mode, but DPRINT seem to use msvcrt API instead of  OutputDebugString, so it won't work as shellcode unless you resolve the hash for it.
While fixing this issue, can you also make the loader "debuggable"? The Makefile.msvc is also weird, it only build the loader in release mode.

So far, it looks the loader exited instead of crashing, no access violation is observed.

Looks like you have a injector in the repo, I tried to inject into calculator:

No thread created:

Unfortunately I don't have a copy of Windows 2008 to test on, but what I would like to know is if this is a 32 or 64-bit build of 2008? Makefile.msvc and Makefile.mingw both support building debug versions of the loader for x64 versions of Windows. For 32-bit, you would need to change the Makefile to use aplib32.lib or aplib32.a depending on the compiler used. In most cases, the debug build should display any errors encountered when attempting to load and execute a file.

Build a .NET EXE and try run it on Windows 2008 6.1.7600, does it work?
Build the debug version of loader, copy the instance and loader to Windows 2008 and try run it, what output is displayed?

Read 12. Debugging The Generator and Loader

Weird, Failed to resolve CreateThread?
C:\Users\Administrator\Desktop>loader loader.bin
Running...
DEBUG: loader/loader.c:47:DonutLoader(): Resolving address of CreateThread
DEBUG: loader/loader.c:57:DonutLoader(): FAILED

Full output: output.txt
FYI: I'm uploading en_windows_server_2008_r2_standard_enterprise_datacenter_web_retail_x64_dvd_x15-50365.iso for testing, you can install a VM after that.

Use the instance created by the generator. You are using the shellcode.

I have uploaded the installer ISO here:
hxxp://<IP_ADDRESS>/en_windows_server_2008_r2_standard_enterprise_datacenter_web_retail_x64_dvd_x15-50365.iso

Here's what I've tried:
Add Main method to lib.cs and make it a executeable, confirm it can run.
In peb.c add debug output:
    {
      // search the export table for api
      addr = FindExport(inst, dte->DllBase, ulHash, ulIV);
      DPRINT("FindExport of %016: %p", ulHash, addr);
    }

But the hash computed is different from loader:
c:\donut-master>donut lib.exe
...
DEBUG: donut.c:909:build_instance(): Hash for kernel32.dll    : CreateThread       = 12EAA7867FE6A9B5
...

c:\donut-master>loader loader.bin
Running...
DEBUG: loader/loader.c:47:DonutLoader(): Resolving address of CreateThread
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: peb.c:142:xGetProcAddress(): FindExport of : E6A9B5EB6E1B85D2
DEBUG: loader/loader.c:57:DonutLoader(): FAILED

I've tried the exactly same step on Window 8, Windows 2012 and Windows 2008 R2 (No SP1), same result, but the injector works on Windows 8 and Windows 2012, so the loader itself seems buggy.

The hash for CreateThread doesn't match because you're not using the 'instance' file created by the debug version. Try "loader instance" instead of "loader loader.bin"

Found the problem:
DEBUG: donut.c:909:build_instance(): Hash for mscoree.dll     : CLRCreateInstance      = D3A05213209196AC

So Windows 2008 R2 uses deprecated ClrCreateManagedInstance

Thank you for the report. It will be fixed in v1.0.

I've patched donut and disabled RtlDecompressBufferEx, installed NET Framework 3.5 SP1 Update for Windows 7 and Windows Server 2008 R2 for x64-based Systems (KB982526) and it worked for now.

I also encountered the same problem. This problem not only occurs in PE compiled by C#, but also in PE compiled by C

@funnywolf mixed assemblies?

@CaledoniaProject Updated loader.c to continue execution if CLRCreateInstance isn't available. It's only a temporary fix for now. Will likely be changed again for v1.0. Also using RtlDecompressBuffer instead of RtlDecompressBufferEx which means Xpress Huffman is no longer an option. Compression for v1.0 will be much different. Thanks for testing.

Confirmed to work on Windows 2008 R2 SP0, when KB982526 is not installed :-)