net: TestNotTemporaryRead timeouts on aix/ppc64

Hi,
I'm trying to resolve timeouts occurring on aix/ppc64 with net.TestNotTemporaryRead.
https://build.golang.org/log/45540cc03c1d37057e8f725d7f2dd431652ddf4c
https://build.golang.org/log/37d60c3b3cd46cf39d118f84e695049d390da40e
...
This timeout occurs because Accept() seems to be stuck in a infinite loop if the server is already closed. It's only a guess because I can't trigger the bug manually on my local machine. However, a similar behaviorr can be easily made with: https://play.golang.org/p/0IXrHf87i-2.
It does work on linux/amd64 but it times out on aix/ppc64. This might not be the root of this bug but a possible workaround can be to increase the delay on the server.
However, I've several questions:

Why is the client doing Accept() and the server doing Dial() ? Is it supposed to be the opposite or it doesn't matter ? This is the case for some others tests of net_test.go.
What behavior Go is expected when an accept() is made when the server is already closed (but the port is still listened) ?
Should it succeed or not ? On aix/ppc64, accept syscall returns EAGAIN (because of O_NONBLOCK flag) and on linux/amd64 it does succeed.

I've also discovered that the behavior of connect is slightly different on AIX than on Linux (I don't know about others OSes). I've tried with the following C code (taken from #6828): accept_after_connect.c.txt. The first connect doesn't return EINPROGRESS as on Linux. It doesn't seem a bug as a connection can result from the listen syscall.
Does Go want EINPROGRESS to be returned ? (*netFD).connect will wait with netpoll if it is.

Another recent timeout in this test, again on the aix-ppc64 builder:
https://build.golang.org/log/ac2fca1f71734020ee6533f578ccbbcf89fe8cd8

Yes, it seems the new sleep time is still not enough... This test isn't fully compatible with AIX behavior which is slightly different if an accept is made after a listen. However, I won't have time to work on it before 1.13 release. Is it possible to mark it as flaky until a better fix is made ?

Is it possible to mark it as flaky until a better fix is made ?

Yep, see testenv.SkipFlaky.
if runtime.GOOS == "aix" {
	testenv.SkipFlaky(t, 29685)
}

This failure mode does not appear to be specific to AIX.
greplogs --dashboard -md -l -e 'goroutine \d+ \[chan receive, \d+ minutes\]:\n(.+\n\t.+\n)*net\.withTCPConnPair'
2022-02-09T22:58:35-2bf5ae0/openbsd-arm64-jsing
2021-08-14T15:14:43-50f4ebb/illumos-amd64
2021-04-16T03:16:11-cf2396c/illumos-amd64
2019-08-25T04:39:15-1a7c15f/illumos-amd64-joyent
2019-07-10T21:26:21-80cca23/aix-ppc64
2019-07-10T18:26:53-9d56dd8/aix-ppc64
2019-07-06T13:25:59-13327f2/aix-ppc64
2019-06-26T20:10:05-fc26cba/aix-ppc64
2019-06-25T19:10:58-fa0537b/aix-ppc64
2019-06-25T17:51:54-816ce1a/aix-ppc64
2019-06-25T13:27:07-e28f0d9/aix-ppc64
2019-06-24T18:23:08-fafc92d/aix-ppc64
2019-06-21T17:24:29-41b9e99/aix-ppc64
2019-06-21T14:52:06-3f1422c/aix-ppc64
2019-06-19T19:23:51-26954bd/aix-ppc64
2019-06-10T16:19:39-8f296f5/aix-ppc64
2019-06-09T16:23:11-323212b/aix-ppc64
2019-06-06T11:40:17-5ec1406/aix-ppc64
2019-06-06T00:11:29-c00ff65/aix-ppc64
The stack traces in the more recent openbsd and illumos failures have more runtime details in them, but as far as I can tell they are essentially the same as the older aix-ppc64 traces. Here's the one from openbsd-arm64-jsing:
goroutine 2061 [IO wait, 14 minutes]:
runtime.gopark(0x400040ed18?, 0x9d748?, 0xe0?, 0x1d?, 0x258f4d?)
	/home/gopher/build/go/src/runtime/proc.go:366 +0xe8 fp=0x400040ece0 sp=0x400040ecc0 pc=0x47818
runtime.netpollblock(0xb?, 0x0?, 0x0?)
	/home/gopher/build/go/src/runtime/netpoll.go:522 +0x16c fp=0x400040ed20 sp=0x400040ece0 pc=0x40a6c
internal/poll.runtime_pollWait(0x4e83d45d8, 0x72)
	/home/gopher/build/go/src/runtime/netpoll.go:302 +0xa4 fp=0x400040ed50 sp=0x400040ed20 pc=0x70b84
internal/poll.(*pollDesc).wait(0x40003f8300?, 0x16e0c?, 0x0)
	/home/gopher/build/go/src/internal/poll/fd_poll_runtime.go:83 +0x2c fp=0x400040ed80 sp=0x400040ed50 pc=0x9820c
internal/poll.(*pollDesc).waitRead(...)
	/home/gopher/build/go/src/internal/poll/fd_poll_runtime.go:88
internal/poll.(*FD).Accept(0x40003f8300)
	/home/gopher/build/go/src/internal/poll/fd_unix.go:614 +0x1d8 fp=0x400040ee20 sp=0x400040ed80 pc=0x9c1c8
net.(*netFD).accept(0x40003f8300)
	/home/gopher/build/go/src/net/fd_unix.go:172 +0x28 fp=0x400040eee0 sp=0x400040ee20 pc=0x1413f8
net.(*TCPListener).accept(0x400000e888)
	/home/gopher/build/go/src/net/tcpsock_posix.go:139 +0x2c fp=0x400040ef20 sp=0x400040eee0 pc=0x15e0cc
net.(*TCPListener).Accept(0x400000e888)
	/home/gopher/build/go/src/net/tcpsock.go:288 +0x30 fp=0x400040ef60 sp=0x400040ef20 pc=0x15cec0
net.withTCPConnPair.func1()
	/home/gopher/build/go/src/net/net_test.go:427 +0x48 fp=0x400040efd0 sp=0x400040ef60 pc=0x1b14a8
runtime.goexit()
	/home/gopher/build/go/src/runtime/asm_arm64.s:1259 +0x4 fp=0x400040efd0 sp=0x400040efd0 pc=0x760b4
created by net.withTCPConnPair
	/home/gopher/build/go/src/net/net_test.go:426 +0x110

goroutine 609 [chan receive, 14 minutes]:
runtime.gopark(0x4000184060?, 0x15e38?, 0x58?, 0xde?, 0x1d230?)
	/home/gopher/build/go/src/runtime/proc.go:366 +0xe8 fp=0x400015ddd0 sp=0x400015ddb0 pc=0x47818
runtime.chanrecv(0x4000133140, 0x400015dee8, 0x1)
	/home/gopher/build/go/src/runtime/chan.go:577 +0x58c fp=0x400015de60 sp=0x400015ddd0 pc=0x1727c
runtime.chanrecv1(0x2af000?, 0x2?)
	/home/gopher/build/go/src/runtime/chan.go:440 +0x14 fp=0x400015de90 sp=0x400015de60 pc=0x16cb4
net.withTCPConnPair(0x4000456820, 0x26e888, 0x26e880)
	/home/gopher/build/go/src/net/net_test.go:445 +0x1b0 fp=0x400015df30 sp=0x400015de90 pc=0x1b1210
net.TestNotTemporaryRead(0x0?)
	/home/gopher/build/go/src/net/net_test.go:546 +0x3c fp=0x400015df60 sp=0x400015df30 pc=0x1b20fc
testing.tRunner(0x4000456820, 0x26e890)
	/home/gopher/build/go/src/testing/testing.go:1439 +0x110 fp=0x400015dfb0 sp=0x400015df60 pc=0xe0ac0
testing.(*T).Run.func1()
	/home/gopher/build/go/src/testing/testing.go:1486 +0x30 fp=0x400015dfd0 sp=0x400015dfb0 pc=0xe1830
runtime.goexit()
	/home/gopher/build/go/src/runtime/asm_arm64.s:1259 +0x4 fp=0x400015dfd0 sp=0x400015dfd0 pc=0x760b4
created by testing.(*T).Run
	/home/gopher/build/go/src/testing/testing.go:1486 +0x328


feat: add support for super reactions

Please describe the changes this PR makes and why it should be merged:
If applicable, please reference Discord API Docs PRs or commits that influenced this PR:

https://github.com/discord/discord-api-docs/pull/6056

MESSAGE_REACTION_ADD also has updates, which aren't in this PR. Is this usable yet or still subject to changes?

Screenshots

We only add what is documented (or will be documented). Suggest changes in the docs PR.

https://github.com/discord/discord-api-docs/pull/6056

Ah, I misplaced the repo this was on, thanks.

Hey @Mateo-tem, are you able to split this pull request up so we have something to merge?

Hey @Mateo-tem, are you able to split this pull request up so we have something to merge?

Yes! I'll do that in a moment 🫡


Issue #1144 - Added ISSUE_TEMPLATE.md for new issue creation

fix: #717 created template for creating a new issue by contributors (what they observed and what should be instead of that, how others can reproduce the same issue like this, system log).

Codecov Report

Merging #1145 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1145   +/-   ##
======================================
  Coverage    3.98%   3.98%
======================================
  Files         123     123
  Lines        5569    5569
  Branches      536     536
======================================
  Hits          222     222
  Misses       5332    5332
  Partials       15      15

Continue to review full report at Codecov.

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

Thanks for the PR! Happy to merge pending the suggested changes. :)

I had updated it again.


Bedtime for rutherling

Hey, Charles worked on this, too, as he has so often done throughout the day!


Does ROCm 2.7.2 support APU V1000? especially V1807B?

We are working with a V1807b based platform with RX Vega11 integrated GPPU. We would like to know if ROCm support this APU.
thanks!

Seems no, but you can use OpenCL instead.
From README.md

The integrated GPUs in AMD APUs are not officially supported targets for ROCm. As described below, "Carrizo", "Bristol Ridge", and "Raven Ridge" APUs are enabled in our upstream drivers and the ROCm OpenCL runtime. However, they are not enabled in our HCC or HIP runtimes, and may not work due to motherboard or OEM hardware limitations. As such, they are not yet officially supported targets for ROCm.

Please check latest ROCm Documentation and ROCm 5.7.1 to see if your query has been resolved.  If resolved, please close the ticket.  Thanks.

Original ticket is more than a year old and the person that opened the ticket has not responded to the latest request.  If this is still an issue, please file a new ticket and we will investigate.  Thanks!


Update README and parameterize PCI subsystem vendor ID

It is important that all parties shipping virtio-win drivers use their
own vendor-specific HW ID to avoid driving somebody else's device.
This is especially critical for WHQL'ed drivers distributed with Windows
Update, as these could be installed without any explicit user action.
A new build warning is introduced to make this requirement more
discoverable (suggested by @dlunev, thanks!)
Note that NetKVM has not been plugged into the new build infrastructure
yet so it is not handled by these commits.

Note that NetKVM has not been plugged into the new build infrastructure
yet so it is not handled by these commits.

Also, ivshmem is missing. Currently, it uses Red Hat vendor and device ID.

Also, ivshmem is missing. Currently, it uses Red Hat vendor and device ID.

Good point. Ivshmem is new and experimental but that makes it even more important for the HW ID to be as specific as possible. I'll add a commit to address this, thanks!


Source locations for alternation pipes and char class ranges

Add source location info to the AST for alternation pipes, and for the - character in custom char class ranges. In addition, add some extra test cases for alternations, including some that test the expected source locations are parsed.

@swift-ci please test Linux

@swift-ci please test Linux


Color in material doesn't seem to parse.

Using this test urdf:
let urdf = r#"<robot name="test">"
  <joint name="j1" type="fixed">
    <parent link="l1"/>
    <child link="l2"/>
  </joint>
  <joint name="j2" type="fixed">
    <parent link="l1"/>
    <child link="l2"/>
  </joint>
  <link name="l1">
    <visual>
      <geometry>
        <sphere radius="1.349"/>
      </geometry>
      <material name="">
        <color rgba="1.0 0.65 0.0 0.01" />
      </material>
    </visual>
    <inertial>
      <mass value="8.4396"/>
      <inertia ixx="0.087" ixy="0.14" ixz="0.912" iyy="0.763" iyz="0.0012" izz="0.908"/>
    </inertial>
  </link>
  <link name="l2">
    <visual>
      <geometry>
        <cylinder radius="3.349" length="7.5490"/>
      </geometry>
      <material name="red ish">
        <color rgba="1 0.0001 0.0 1" />
      </material>
    </visual>
  </link>
</robot>"#;

I parse calling your read_from_string function, the color value is always a None. Here is a debug output of each of the visual objects after the parse:
&l.visual = [
    Visual {
        name: Some(
            "",
        ),
        origin: Pose {
            xyz: Vec3(
                [
                    0.0,
                    0.0,
                    0.0,
                ],
            ),
            rpy: Vec3(
                [
                    0.0,
                    0.0,
                    0.0,
                ],
            ),
        },
        geometry: Sphere {
            radius: 1.349,
        },
        material: Some(
            Material {
                name: "",
                color: None,
                texture: None,
            },
        ),
    },
]
&l.visual = [
    Visual {
        name: Some(
            "red ish",
        ),
        origin: Pose {
            xyz: Vec3(
                [
                    0.0,
                    0.0,
                    0.0,
                ],
            ),
            rpy: Vec3(
                [
                    0.0,
                    0.0,
                    0.0,
                ],
            ),
        },
        geometry: Cylinder {
            radius: 3.349,
            length: 7.549,
        },
        material: Some(
            Material {
                name: "",
                color: None,
                texture: None,
            },
        ),
    },
]

Thanks for the report! This is another regression introduced in https://github.com/openrr/urdf-rs/pull/64.  I confirmed urdf-rs 0.6 (that uses serde-xml-rs) doesn't have this problem.

@luca-della-vedova
Thanks for the investigation! Since the main branch already has a breaking change (https://github.com/openrr/urdf-rs/pull/92), there is no problem with making a new breaking change.

Now that is not the solution but I wonder if yaserde tries to deserialize the urdf, doesn't find the origin element even though it is currently required

If this is the cause of this problem, it seems that yaserde is behaving quite badly in not treating the lack of the required element as an error.

Thank you for looking into this. I can confirm adding the required origin element fixes this behavior. I'm building a new library that depends on this so feel free to ping me to ask for help with changes here. I'm happy to test any new changes.

I wonder if we should reconsider what fields are mandatory and what are options, for example we currently set origin, or even name, as mandatory, i.e. here then default to the origin if this is not provided, which kinda follows the specification where it states:
<origin> (optional: defaults to identity if not specified)

This creates a bit of an issue since it is not possible, for a user, to figure out if a pose in the origin was specified or if it was just the derived default.
This creates a bit of confusion in deserialization use cases like the above, since there is a lot of empty data that is autogenerated, and is actively harmful in serialization since a round trip will add a lot of unnecessary defaults and noise to the URDF file.
Should we reconsider and make all these fields Option instead? We can (and should) still implement Default so users can unwrap_or_default() the option if needed, which is a bit of API noise but technically more correct.
What do y'all think?

@tylerjw can you give a try to this branch and see if it works for you?

Tested and got it to compile with some small changes around the GeometryTag type. It seems effort is a required argument to limit tags?
UrdfError(Other("missing field `@effort`"))

I followed the specification http://wiki.ros.org/urdf/XML/joint which says that while lower and upper are optional, effort and velocity are required, are there a lot of urdfs in the wild that don't have one of the two and are successfully parsed by other parsers?

I think it is likely you are correct and my test urdfs are malformed. I'll go look at the actual urdf files we have for robots to see if this is the case. The ones in my tests are copied from the C++ parsers tests in ROS.

Fixed in 0.9.0 (#98, #107).
We allowed for missing effort, but we might actually want to consider allowing for missing velocity as well, since all the missing effort URDFs I have actually found seem to be missing velocity as well.

https://github.com/RussTedrake/underactuated/blob/c81f09ec415d03d3eca9b156635f1c3ed50eda12/underactuated/models/littledog/LittleDog.urdf#L112
https://github.com/RussTedrake/manipulation/blob/431da7b9cc8e2e25024c3174f0710c3c1eb7b737/manipulation/models/mobile_iiwa14_primitive_collision.urdf#L65
https://github.com/yjy0625/equibot/blob/dc70059191beb29903d78fc4d0193392be5134fc/equibot/envs/sim_mobile/assets/closing/template.urdf#L193
https://github.com/bulletphysics/bullet3/blob/e9c461b0ace140d5c73972760781d94b7b5eee53/data/prismatic.urdf#L46


k_cycle_get_32() returns 0 in native_posix

Describe the question
seems when API:k_cycle_get_32() runes platforms of native_posix, there will just get return value 0.
and it's OK to run at others platforms.
Running at qemu_x86 platform result as follow:

Running at native_posix platform result as follow:

Implement Code:
`	/for-loop to get some average operations time spent/
for (i = 0; i < const_times; i++) {
	start_time =  k_cycle_get_32();
	printk("start_time1 = %u\n", start_time);
	rb_get_min(&test_tree1);
	start_time = k_cycle_get_32() - start_time;
	spent_time[0][0] += start_time;

	start_time =  k_cycle_get_32();
	printk("start_time2 = %u\n", start_time);
	rb_get_max(&test_tree1);
	start_time = k_cycle_get_32() - start_time;
	spent_time[0][1] += start_time;

	start_time = k_cycle_get_32();
	printk("start_time3 = %u\n", start_time);
	rb_insert(&test_tree1, &tx_node[0]);
	start_time = k_cycle_get_32() - start_time;
	spent_time[0][2] += start_time;

	start_time = k_cycle_get_32();
	printk("start_time4 = %u\n", start_time);
	rb_remove(&test_tree1, &tx_node[0]);
	start_time = k_cycle_get_32() - start_time;
	spent_time[0][3] += start_time;
}`

Configuration files:

and by the way, it's unstable on both platforms of qemu_nois2 and qemu_x86_64.

@Zhaoningx Most likely what you are seeing is that while the CPU does not go to sleep, time does not pass in native_posix:
https://docs.zephyrproject.org/latest/boards/posix/native_posix/doc/index.html#important-limitations
I'm guessing the reason why you are getting 0 out of k_cycle_get_32() is because you are running that code right after boot and before having ever set the CPU to sleep.
If that is the case, that is not a bug. If you call k_sleep(), k_busy_wait() or in any other way perform some operation which does make that thread wait for some time, you should see that k_cycle_get_32() returns you a later time.
Please tell if this clarified the issue for you, and if that is the case, close this issue.

Hi @aescolar, thanks for your review, I have read zephyr doc about native_posix carefully, and I test the condition you mentioned, and I used k_msleep() before invoking the API k_cycle_get_32, as you say, it can returns a later time instead. But, there are something confused me, can I get the time of running several lines code in native_posix without CPU sleeping?
And I'll close this issue later.

can I get the time of running several lines code in native_posix without CPU sleeping?

Hi @Zhaoningx . No unfortunately that is not possible in native_posix due to fundamental reasons: Code itself takes "0" time to execute.

Hi @aescolar, for native posix part,   Can we get cpu cycle with rdtsc like below:
static inline uint64_t get_cycle_count()
{
unsigned int lo,hi;
__asm__ __volatile__ ("rdtsc" : "=a" (lo), "=d" (hi));
return ((uint64_t)hi << 32) | lo;
}

@youhuazhu  - Yes, fundamentally your process is x86_64 linux userspace code and it can execute the rdtsc instruction and it will return a cycle count the reflects real world time.  But you still can't spin on that to "wait" for anything to happen in the Zephyr native_posix implementation.  That's not how it works.
What, exactly, is the problem you are trying to solve?

oh,  yes, we can get the native host cycel count from that way,  you are right,  this cpu cycle not only for Zephyr native_posix implemention, so not accurate, I tried this.
and up to now, I have no good way to solve this issue,
I think we can close this question.  @Zhaoningx

 hi, @aescolar  @youhuazhu @andyross thanks, I know that and close it now.

@youhuazhu @Zhaoningx
If  what you are trying to do is profile your code (when compiled for your x86 host), you can use normal desktop tools. For example, a relatively simple (FOSS) tool you can use is valgrind's callgrind.
valgrind --tool=callgrind --dump-instr=yes --collect-jumps=yes ./zephyr/zephyr.exe
kcachegrind callgrind.out.<pid> &


Release v17.0

Can one of the admins verify this patch?

I'll have another look but I ran a script on the report and I think all updated have a breaking change


'highlight' should (un-/)highlight the whole marked area

hightlight a word in a line
mark the whole line
click highlight

expected behavior
The whole line should be (un-/)highlighted.
observed behavior
it inverts the marked parts, the previously unhighlighted words are highlighted and the other one is normalized.

Ah, this is not isolated to "highlight", bold and italics do it too.
All done in the same function. And a complicated function it is. Sigh .....

OK, fixed. When we change a selection of text, it has to be done block by block. But we now base the whole change on the first character of selection, not first char of each block !

Good it is fixed now. As I am picky, i tried the following:

add some words to a line
mark one word and click highlight, the word gets highlighted
mark this word or a part of it together with unhighlighted text and click highlight - the whole marked area should get highlighted. instead it gets UNhighlighted.

Side note: Can we change the color of marked highlighted text? Currently I need to unmark text to check if it is highlighted.

The test to determine whether we highlight or un-highlight is what the first character of the selection is. Thats the standard way and only way that makes sense IMHO.  So, when you say "together with unhighlighted text", whats important is where that (new to the selection) unhighlighted text is. If its in front of the part you just highlighted, then the first character will be unhighlighted and the action is to highlight the  new selection. On the other hand, if the addition to selection is after the part you previously highlighted, the the first character will be already highlighted and the action will be to unhighlight it all.
If this is not whats happening, its a bug, please detail just what you are doing to demonstrate it.

re your sidenote about color of text. The 'highlight' text color is set in settings.pas, line  number 151.  Hover your mouse over clRed and you can open the unit where the predefined colours are defined.  If necessary, we could make it a user settings.

i agree, Tomboy NG does the same.


Remove binary file cluster-api

This is generated by go build and added by mistake.

This change is


OOP Issue #17: Add variance filter

Unfortunately, fourier transform commit numpy version slipped in this branch.

Maybe you can change the docstrings to Google format before merging?
And someone has to resolve the merge conflicts.


66 safe addresses related to airdrop hunters

Related Safe Addresses

0x07dbf9445b1c3e737dc2bae7ef968338ff45d294
0x19765175d40e26604d4a2c0a16e6216104e48c91
0x275d7548bb71e74534e331a99151e92ce9b5aa4a
0x311bf9e947aace015355bb1a7d9820cccc889d98
0x315762ba1907b55548fa1410e499ba6c3fb97201
0x35cbf700032b0d66e0bc9370362ad20c494e3e2c
0x37f405fad68e7ca5da6aa639cabc59c5b11cfca4
0x385e47769fae49b9460271f92acd87376f22e417
0x3ba285dd1b88a9dbde09a7103891f9edc6d33d39
0x3c2863e5de5a8c2f8e4487db3fb808c415119f06
0x3c369af7494fdd069eef70406ccac632fded673c
0x40a72e6628754b0f4945118cfe195a14ba2cf484
0x43c8d19a98531df699c214621923296a13a25839
0x4570348446c0c5f8ed8f6f2487ebf3ae06ce073b
0x492a0ba72cade4f357914fb972b7b9a88da6e97f
0x4e57fb8e147467576bb3948bf38a866a33737c73
0x58a22a95c4d99a3f42d223cf28acfc79d0e8f538
0x5b36847a2c745598a255ac1b6d62b08a79d245f0
0x5ceea497252dcb65810daa37a1314cf23b385632
0x5f2f9c4bfe2ce795748ded264d0762acdf7621c4
0x6da8c991cad590afab7739c9aa87f54c60a92b7c
0x78efa2550f288fc4cfe8e92fa9582c5e7777b5e9
0x7bbd127291ef8a59514b0f292113db712f2ad1a7
0x7bf98e94179e59333c76071948cdd1162d832c10
0x7eda6eec003c855b3a807d8042647c1de431cc9f
0x8203f5d6370e7e36d383fcaee5d9a477cf083dca
0x89b87d70593b39711d40f4127a380f40b0c1a0b4
0x8de4e93544e3f9fc0cd1f836006f9de7893869f2
0x8fd193ad6591ffe3ca5a2da8955a858470095269
0x91c51634b7349dde6f953179585b2831a50cbd91
0x93a48f4882262f598f7e274f15fc31ea6e831417
0x97563547ff29fbb040e5dec199f31c47659d40b6
0x98d71f59732765a9483c6f612f9fa77da7182766
0x9d8aeb8a9031ef8518239900fc2667f87c981a13
0x9f82cfa1a20b6e66c71a3db1a0d788b477b2f21f
0xa24009391181cf02f2c0c1338a03b2d85b9643dd
0xa28fb8ee3c51cc13bf8b145a210ca614c97e5e35
0xa959d1c07b055930c04fb1f03563edf8bad536bc
0xa9d7f3d5ac4dc1f60ca5c683e6536111c326ce8f
0xaad59f59ea74c135e9fecd83c1d63eb416f08796
0xab41ba919e58f380a324f61b07f60420859f5483
0xac1b95759c1eef80dfa2d18f3affdc8cefe24a3c
0xb1a151a3dc719a514d1e2512cf003a0fac046408
0xb5fb962a1cf3946ad6bec9c876bac967ad7d00a8
0xb5fd31e9dbf81cbe608ec0c711010228aee1ee08
0xb79234d2f7762990c444aa077512005e7a6099dc
0xbd0795e0b0a9e8687166b1216097109faa372361
0xc2ed2b9a9d111935ecfac20ab6a20594eafffdd6
0xc4c3d4c55585ca572a55a12d8c921c84d7a13f54
0xc59ef345c1d02ee58b28af2f2063a5bb07701f30
0xce611537fc156029a8dd072b2c4f12b8a0e5b602
0xcf4266f6abb4e10d3fccbce8fbf2de3a1382ed81
0xd1259c24566bc510ad84176ab7420ff9ddb805d3
0xd1a3e6a40bebd2c6ecc5f17a181801b735c93261
0xd62b9318d3485d6a766ed47a2ac0abe7e8942894
0xd8a2cbcc83e44db2607bd058117ae26cf61137b1
0xd8a47de2bf63d35d61a6242c7216523add8c71e9
0xd965b79122a6b805b2d8ef048fbb25b112bc6f61
0xdd14b6a59d71655467fe731199fc4683a74e9a79
0xdf10e370c0cd105ba318ba470fc0026a5017f397
0xe13cb8759f0129ab5bdc53316ba3720c6131135b
0xe7cff97868893f817945ca6e09c4c95b6b00fe64
0xe80aa86fe310c13d7bb82cbd6fcbf43af7b11381
0xef154804c4ea2fe035bf5163aadb6466d6d1dbed
0xf37ab818e5027c533310d76001b587320ea93c22
0xfa986f13abc69481620a43a659391bbf175891da

-->

# Reasoning

<!--
I found these safes with 1 transaction from 1 wallet,and the wallet is 0xdf21b894a490cbdf49d9de7b9d780b79f7cb0ac7

so I checked this wallet's txs,and then find these safes are from one person
-->

# Methodology

<!--

Example:

The reported addresses were discovered by checking irregularities in the number of Safe transactions made via Dune. Based on the resulting list of Safes, a dataset was built that categorized each Safe transaction. Based on that, an algorithm was used to identify repeating patterns in the order of those interactions.

the main wallet's records:
https://etherscan.io/address/0xdf21b894a490cbdf49d9de7b9d780b79f7cb0ac7

I sorted the excel by the amount of eligible SAFE tokens. I identified that there are some addresses eligible of exactly the same amount of tokens . and i found txs were from 1 same wallet

-->

# Safe Address

<!--

0xbF53F1Ae4a9DEB20dFB715324b13f855CA331b27

-->

This report doesn't contain sufficient info. Just creating mulitple safes from 1 account is not airdrop farming, pls elaborate.

We haven't received any further information on this ticket and therefore deemed this submission invalid.
Unfortunately just the pure fact that Safes...

were created by the same address
have the same owner
conducted the same transactions
received assets from the same address

... is not enough reasoning for a valid submission, as there are legit user behaviour leading to such as well (relayer, scripts, power users, exchanges)
This submission didn't provide sufficient indicators to convince the team that there is some targeted airdrop farming behind the provided addresses. As per the rules, when in doubt we will default in favor of the airdrop recipients in order to not risk any false positives when sorting out airdrop hunters.


Liquidity limit reached message for TKN when there's actually lots of available room for it

The USDT pool has plenty of liquidity that was provided by users, it should allow more than 200K of TKN to be deposited.

This no longer seems to be coming up since the formula update.


Re-do without modification of ts.tracing

Making this PR to do a proper performance comparison to the code in #42323.  (It will probably not have much difference, and therefore likely not for merging.)

(This was only to try the performance impact.)


Bug: ReadAt() returns EOF

Hi, during development on https://github.com/restic/restic/pull/366 I came across strange behaviour: Calling ReadAt() with a small buffer (e.g. 512 byte) and a larger offset (e.g. 32k) in a larger file (e.g. 500KiB) correctly reads the 512 byte, but also returns an EOF error.
According to the spec for io.ReaderAt this may only be the case when the last 512 bytes in the resource are read, but here I read 512 from the middle of the file, so the EOF is wrong.
I wrote a small program which demonstrates this on play.minio.io https://gist.github.com/7dbbef2dd5e78bbf8723
The output is:
$ go run s3bug.go
len = 513767
n 513767, err <nil>
size 513767, err <nil>
ReadAt(len(buf) 512, offset 32000)
m 512, err EOF

I think this is a bug :)
ping @harshavardhana

@fd0 thanks this is a bug.
in GetObjectPartial()
				httpReader, _, err := c.getObject(bucketName, objectName, req.Offset, int64(length))

We'll get back on this soon.

It maybe is a good idea to also add a test for this...

It maybe is a good idea to also add a test for this...

Sure @fd0 we will add, thank you for reporting and taking time to test.


Add XLand-MiniGrid to README

We just released our library for meta-RL in JAX. Would be happy to be mentioned!

Awesome 😎 Congrats to the release! 🎉🤩


How to install v2.2?

I'm using wine (8.10) manually on ubuntu.
I got a (working) wineprefix in ~/games/
Where do i put the *.dll files? just "cp *.dll ~/games/drive_c/windows/system/"?

There is a small guide in the readme if it's able to provide enough info https://github.com/doitsujin/dxvk#how-to-use
For the first line you'd then just modify it to point at your prefix.


A little confusion about how the Ampere works.

Hello, excuse me. I got some question to ask.
Im using 5A ACS712 Chip for my device. One thing i realized is without anything (any load) connected to my device. It's still showing up 30-45mA. I'm a little confused on why is this happening.
Another question is, when i charge my phone it shows the current is around 100-150mA. Meanwhile it should be around 2A/2000mA. Any idea on why is this happening?
Thank you in advance.

Thanks for your question.
There is too little information to analyze your case, so I start with some generic questions.
What processor board do you use?
How is the ACS onnected?
Have you initialized the sensor to 5A?
A low current when nothing connected can be noise.
If you disconnect the device, what current does it report?

Q5 Have you compared your ACS712 measurements with a multimeter?

What voltage do you measure with DMM) between GND and VCC ?

Thanks you!
So, yes. I do have a 1nF Caps on the filter pin. Here's are the schematic, its connected to a relay.

The voltage i got by measuring those pins are 2.534V (both GND - VCC and GND - VIOUT).
I called ACS.autoMidPoint(); on my code already which show 511-512 since it ADC/2. Or it's different from what you mentioned above?

GND VCC  should be sround 5V, that cannot be 2.534V, please measure again
AutoMidpoint seems to return a value as expected.

Ah yes, my bad. It's 5V for GND - VCC pins. Lost focus for a moment.

Think I found the cause
From the datasheet

Please note that the ATMEGA 328 has 1024 levels ADC for 5V
The sensor only uses +- 1V for 5A so around 200 steps of the ADC are used for 5A.
That means that 1 step is around is about 25mA
So the 30-60 mA you see is just one or two bits of the ADC, which is probably noise.
possible solutions:

call setNoisemV(70) in setup - adjust the value so it just removes the noise.
reduce the noise in hardware with a low pass filter => resistor 1K + capacitor (10 uF) between VIOUT and GND
use an external ADC like the ASA1115 which has a higher resolution. Might still need a low pass filter.

The ADS1115 is a 16 bit ADC while the 328 has only 10 bit, that means 64 x precision (in theory).
That means 1V has 12800  steps so 1 step is in the order of 0.1 mV
You won't get all that extra accuracy in practice as such ADC is more sensitive for noise
in theory there is no difference between theory and practice, but in practice there is.

Ah i see the issues now.
Will try the possible resolution soon and see what i got.
Thanks for time and of course the answer! Will inform you soon about the update of my device.

Tried out changing the NoisemV and the numbers im getting is much better and realistic than before. For now, the problems is fine at all no need to continue as im getting a better realistic numbers overall. Also i used setMidPoint(512) so the midpoint wont fluctuate.
Thanks for your time!

Sorry in advance as the question is irrelevant to the ACS712 library.
You mentioned to use a low-pass filter of 1K resistor + 10 uF capacitor. The filter will have a cut-off frequency of ~16 Hz.
How did you come up with the values of resistor and capacitor? I am asking as I need a low pass filter for my 20A ACS712 sensor.
Thank you and again excuse me for the irrelevant question.

@panbak
Was just a starting point for a possible solution. Did not calculate them.
In the datasheet page 11++ there is information about filtering.

Thank you! Also I don't understand what the second parameter is when calling ACS712  ACS(25, 5.0, 4095, 185); Is it the sensor operating voltage?

float volts = 5.0  is the voltage of the internal ADC
For an UNO and NANO this is typically 5.0 volts, for an  ESP32 this is 3.3V.
This voltage is used to calculate the _mVpstep that is used with the analogRead() to measure the sensors output.
Might need explanation in the readme.md file

something like this
Interface
Base

ACS712(uint8_t analogPin, float volts = 5.0, uint16_t maxADC = 1023, uint8_t mVperA = 100) constructor.
It defaults a 20 A type sensor, which is defined by the default value of mVperA. See below.
Volts is the voltage used by the (Arduino) internal ADC.
maxADC is the maximum output of the internal ADC.
mVperA is defined by the sensor used.
These two values are used to calculate the voltage output of the ACS712 sensor.


"Report Issue" link doesn't work for non-signed in users.

This seems to be a limitation of GitLab. In order to fix this, we have two options.

We can move to GitHub, who prompts users with a signup page.
We can build an issue form into the application.

Option 1 is easy, it only affects a few links and me, at the moment. Option 2 is harder, but also allows anonymous  issues to be filed. It also makes it a little harder to track who actually filed the issue.

The decision, as you can see, was to move to GitHub. We might still want to consider making a new issue form, but this will work for now.


relativeTo parameter is not working

Hi,
I'm a bit confused by this loader, I'll try to set up a very straightforward config where all my HTML files are located into a templates folder (see the folder structure below). Thus if I have correctly understood the way this module works, I defined the following config:
webpack.config.js
{
     test: /\.html$/,
     use: [
         {
             loader: 'ngtemplate-loader?relativeTo=' + (path.resolve(__dirname, '../templates')),
        }
    ]
}

Folder structure
    .
    ├── app
    ├── templates
    └── ...

When I try to require my templates/root.html from my angular entry point app/main.js with the following command:
const rootTpl = require('root.html');

I get the following error:
ERROR in ./app/main.js
Module not found: Error: Can't resolve 'root.html' in '[__dirname]/app'

I don't understand why it tries to resolve the path of my root.html from /app instead of /templates.
Any idea about what is wrong with my configuration? Maybe I'm missing something obvious.
I'm using angular 1.5.11, webpack 3.10.0 and ngtemplate-loader 2.0.1.

require('./root.html') maybe?


[SPARK-16312][Follow-up][STREAMING][KAFKA][DOC] Add java code snippet for Kafka 0.10 integration doc

What changes were proposed in this pull request?
added java code snippet for Kafka 0.10 integration doc
How was this patch tested?
SKIP_API=1 jekyll build
Screenshot

@koeninger @zsxwing it'd be great if you can take a look, thanks!

Test build #67735 has started for PR 15679 at commit 9dc8e0f.

Test build #67735 has finished for PR 15679 at commit 9dc8e0f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Oh there's a on-going 2.0.2 RC cut. It'd be great if we can make this into 2.0.2. So also cc @srowen to take a look, thanks!

Test build #67760 has started for PR 15679 at commit 400ae12.

Test build #67760 has finished for PR 15679 at commit 400ae12.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

@koeninger thanks. These were extracted from my local compiled example projects -- no compiled kafka010 examples yet in the Spark repo, right?

Thanks for working on this, couple minor things to fix but otherwise looks good.

Test build #67766 has started for PR 15679 at commit bd622e1.

Test build #67767 has started for PR 15679 at commit 8be3c8b.

Test build #67766 has finished for PR 15679 at commit bd622e1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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

Merged build finished. Test PASSed.

Test build #67767 has finished for PR 15679 at commit 8be3c8b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

LGTM

merged to master/2.0

@srowen @koeninger thanks for the review!


Completion list shown when typing interface member names

A little annoying since the results are essentially always wrong/useless.

Not seeing this anymore in the latest in master.


feat(ApolloQueryPipe): Support both results from decorator and service

It allows to use ApolloQueryPipe with @Apollo and Angular2Apollo.watchQuery().
<ul>
  <li *ngFor="let post of data | apolloQuery:'posts'">
      {{ post.title }}
  </li>
</ul>

I like it!

@Urigo I'm glad you like it!


Proposal: Add a byte before each transaction that indicates its type

We currently wrap PFB containing transactions with the share index so that other validators and rollups can check for blob inclusion. This is done by wrapping the normal sdk.Tx with a stuct that has the relevant metadata. When decoding transactions, we have to have some mechanism to check that the transaction has the described metadata before we can parse the contents of that tx. We currently use a hacky mechnism that forces an additional check during the decoding process.
Instead of using the hacky mechanism, we should add a single byte before each transaction, which determines the type. Then parsers of transactions can check this byte and know how to parse the rest of the transaction.

Raw notes from sync:

a user creates and signs a normal transaction. Before publishing their transaction to the mempool, they prefix their transaction with a special byte that indicates the type of the transaction. Something like:

const (
	IndexWrappedTx = 0x01
	BlobTx         = 0x02
	NormalTx       = 0x03
)

block proposers can tamper with the type byte of a transaction prior to inclusion in a block but the state machine will try to de-serialize a transaction with the incorrect type and this should result in a no-op.
CheckTx should include a switch statement that is based on the first byte of the transaction
raw pseudocode in this Go playground

The motivation for this issue was to make it easier for clients to parse PFB transactions. See:

Then parsers of transactions can check this byte and know how to parse the rest of the transaction.

After a synchronous discussion, we decided to pursue https://github.com/celestiaorg/celestia-app/issues/1173 so we're putting this issue on pause. We can keep this issue open in case we revisit this proposal.


Crashes when calling CloudKit log-in.

In order to obtain a "web auth token", Apple's CloudKit (https://developer.apple.com/library/content/documentation/DataManagement/Conceptual/CloudKitWebServicesReference/SettingUpWebServices/SettingUpWebServices.html#//apple_ref/doc/uid/TP40015240-CH24-SW1) sends a redirect, which uses HTTP status code 421.  However, KituraNet 's HTTPStatusCode has no case for 421, so it's init.(rawValue:) method returns nil.  While KituraNet should support all known status codes, this would have been fine, had a force-unwrapped optional not been used in ClientResponse's var status didSet.    Please fix the ASAP.  In conjunction with the lack of support for ECDSA, it makes logging in to iCloud impossible with the current Kitura tools.
The appropriate code for the didSet would be:
didSet {
statusCode = HTTPStatusCode(rawValue: status) ?? .unknown
}
Force-unwrapped optionals should never be used in code which needs to be reliable, and a web service needs to be reliable.  The only exception is functions with no inputs.  Not just no arguments, no inputs of any kind.  Completely isolated functions (computed properties) which always produce exactly the same value and have a unit test hooked up to verify that they produce that value.  This is the only safe way to force-unwrap an optional.

This was fixed by the PR #193.
Kitura-net with the tag 1.7.5 includes this fix.


Trouble building lucet-wasi (467 errors)

I'm having a really difficult time building lucet-wasi on Arch Linux.
After reading #78 I installed the dependencies I could (hwloc, llvm, lld using pacman), and I also tried my best to install wasi-sdk, which wouldn't compile no matter how much I tried, so I had to take the .deb and use debtap to create an arch pkg.
The commands I ran were:
git clone --recurse-submodules git@github.com:fastly/lucet.git
cd lucet/lucet-wasi
cargo build

I also tried cargo +nightly build --verbose. I've done a lot more than this, but I'm trying to pare the noise down. I'm out of things I know how to try.
A couple screenshots that might help... Errors with cargo build:

Errors building wasi-sdk:

Any help is appreciated...

Regarding wasi-sdk: since you are running Arch Linux, you don't need it, as the distribution already provides an up to date LLVM toolchain with support for webassembly.
Clone this subset instead: https://github.com/CraneStation/wasi-sysroot
pacman -S clang llvm lld is all you need to compile this (if you get an error about llvm-ar not being found, this is because you installed clang but not the whole llvm package).
make install will install the WASI sysroot in /usr/local which may be a bit intrusive. Edit the main Makefile and change INSTALL_DIR in order to change this.
lucet-wasi has the /opt/wasi-sdk path hard-coded, but that can be changed by setting a WASI_SDK environment variable. The examples need other variables: WASI_CC and WASI_LD, that you can simply set to the path to the normal clang and llvm-ld binaries installed on your system.
The Lucet tools themselves are only tested using Rust-stable (currently 1.33.0).
Some will break if surprising ways (such as __wasi* symbols not being found) if WASI_SDK is not defined. So, define that one :)
HIH.

The only thing that you may find missing is the /usr/lib/clang/8.0.0/lib/wasi/libclang_rt.builtins-wasm32.a file.
Unless you want to recompile clang specifically for this, you can just extract that file from the wasi-sdk Debian package (it's located in opt/wasi-sdk/lib/clang/8.0.0/lib/wasi/) and copy it to the path Arch Linux expects it at.

Speaking of the libclang_rt.builtins-wasm32.a file: you may also want to add a symlink to it in /usr/lib/clang/8.0.0/lib/ as well (not just in the wasi/) subdirectory.
Since wasi is not recognized by tools such as autotools yet, this will let you use the wasm32-unknown-none triple as an alternative to wasm32-unknown-wasi. More software will compile out of the box that way.

Thank you for the detailed responses so far!
The wasi-sysroot compile went well, thanks for the direction. I opted to leave the makefile as-is, and just use the environment variables you mentioned.
So, in the lucet-wasi subfolder, I tried running the following command that I cooked up as best I could follow:
WASI_SDK=/usr/local \
WASI_CC=/usr/bin/clang \
WASI_LD=/usr/bin/lld \
cargo build

I think I got something wrong though. Check it out:

This is likely to happen because build scripts still assume that clang emits webassembly code by default, but this is only true in the Docker image, and with a specific clang. The --sysroot and --target parameters are missing.
Portability is not great yet, but this is something we will improve, especially to support Linux distributions that already ship with an up-to-date LLVM toolchain.

lucet-wasi/build.rs has quite a lot of hard-coded paths that you may want to change.

I was able to compile it on Arch with the following changes to build.rs.
Change /tmp/sysroot to where you installed WASI.
diff --git a/lucet-wasi/build.rs b/lucet-wasi/build.rs
index b51ec31..ddb2cf2 100644
--- a/lucet-wasi/build.rs
+++ b/lucet-wasi/build.rs
@@ -4,9 +4,7 @@ use std::path::{Path, PathBuf};
 use std::process::{Command, Stdio};

 fn main() {
-    let wasi_sdk =
-        Path::new(&env::var("WASI_SDK").unwrap_or("/opt/wasi-sdk".to_owned())).to_path_buf();
-    let wasi_sdk_core_h = wasi_sdk.join("share/sysroot/include/wasi/core.h");
+    let wasi_sdk_core_h = Path::new("/tmp/sysroot/include/wasi/core.h");

     println!("cargo:rerun-if-changed={}", wasi_sdk_core_h.display());

@@ -28,11 +26,10 @@ fn main() {
     let host_builder = bindgen::Builder::default()
         .clang_arg("-nostdinc")
         .clang_arg("-D__wasi__")
-        .clang_arg(format!(
-            "-isystem={}/share/sysroot/include/",
-            wasi_sdk.display()
-        ))
-        .clang_arg(format!("-I{}/lib/clang/8.0.0/include/", wasi_sdk.display()))
+        .clang_arg(
+            "-isystem=/tmp/sysroot/include/"
+        )
+        .clang_arg("-I/usr/lib/clang/8.0.0/include")
         .header(core_h_path.to_str().unwrap())
         .whitelist_type("__wasi_.*")
         .whitelist_var("__WASI_.*");

@jedisct1 Nice, okay, I'll experiment with that when I get some time to do so. But in the meantime, is there an issue tracking portability issues like this? Perhaps it should be referenced.

And thank you so much for your time and attention to detail! You're on the level!


Height source vision: Fallback to rangefinder if available

This implements a fallback mechanism to RangeFinder (if existing) and then to Baro, if vision is selected as primary EKF2 height source in case of vision timeouts.
fixes https://github.com/PX4/PX4-Autopilot/issues/16858

It is generally a good idea and something needed but I asked a few modification because I want it to fit cleanly in the estimator. Vision is "just" another source of aiding and we should be able to follow the standard implementation. If the implementation is not possible because the estimator is too much oriented towards GNSS/baro aiding, let's rework that to make it more universal.

One additional observation while testing: Terrain estimation does not work properly after falling back to rangefinder in vision based height mode.
As an experimental workaround I added to ekf.cpp (122):
if(!(_control_status.flags.rng_hgt && _params.vdist_sensor_type == VDIST_SENSOR_EV)) 		   runTerrainEstimator();
to switch off terrain estimation and keep the estimate constant during fallback time (which is an assumption, but works for altitude control and flow measurements).
This is the current solution:

Unit test issue addressed: https://github.com/PX4/PX4-ECL/issues/997#issue-846448344

Unit test issue addressed: #997 (comment)

If your PR makes a unit test fail because it actually fixes something, you can directly modify it to reflect the changes and make it pass.

One additional observation while testing: Terrain estimation does not work properly after falling back to rangefinder in vision based height mode.

Have you found out why it doesn't work properly anymore?

One additional observation while testing: Terrain estimation does not work properly after falling back to rangefinder in vision based height mode.

Have you found out why it doesn't work properly anymore?

I have not investigated it deeper, but in mode rng_hgt terrain cannot be estimated properly at all - as far as I understood as the rangefinder is the source of distance to bottom and the source of height at the same time. I noticed, that, when falling back to range finder, terrain follows height.

Thanks for your contribution @ecmnet !


Could not load file or assembly 'MahApps.Metro, Culture=neutral' or one of its dependencies. The system cannot find the file specified.

I just downloaded MahApps off of nuget package installer inside of visual studio. And I am definitely missing a step because its too easy but I cant find that other step. I get those errors in the pictures and I thought i solved it in my other project but all the controls just went black and showed nothing being able to interact with. Im pretty sure that i need to download some more stuff or change the directory, im really new to wpf so help is appreciated.
MahApps.Metro version: v2.0.0
Windows build number: Win10 1909 [Version 10.0.18363.836]
Visual Studio: 2021
Target Framework: .Net Core 3.1 (v4.5.2, v4.7.2)

Screenshots

Hi @Learn123-hash
First if all please do not report a bug if there is no bug. You can use discussions or gitter to ask questions like this.
Back to your issue: Please make sure you read the start guide: https://mahapps.com/docs/guides/quick-start . Moreover you may want to download the source code and play around with the sample app.
Happy coding
Tim

@Learn123-hash Do you still have problems with it?

1 - Oh sorry, i answered it because it was the only one having my exact issue.
2 - Those are the only errors i have, in my previous PC i installed MahApps with NuGet and everything was OK, before moving to this PC i uploaded the code to a private GitHub repository and then i cloned it with VS and MahApps wont work, i tried reinstalling it but nothing, i got back to my previous PC and i tried to clone the repository too and there it did work, i dont know what is wrong

Do you have the NET-Runtime all installed?
Maybe try clean and rebuild?

Yes i have .NET installed, im gonna try that rn

It needs to be the exact version you use in your App. So if you target NET 4.8, you need to install 4.8 SDK.

Thanks for your help! looks like cleaning and recompiling worked


Putting animate/plot as arguments rather than separate functions to be manually run?

Would it be better to put the decision of plot vs animate as an argument so that the user only has to run a single line?
Rather than how it currently is where one as to use:
tdse=TDSE(**kwargs)
tdse.plot()

If we put it somewhere as an if statement (presumably a new kwarg within the TDSE class, then an if statement in the running box checking what they input for that, and if it's not one of the options print an error message), that could work. But in turn that might make it a required class, it depends.

Pretty much what i was thinking, it wouldnt be required if we set a default of one (probably animate). I'd like it do be able to have the ability to do both at once which might be more complicated but probably not too bad.
Does someone want to go ahead and add that then?  (I'll happily do it)

I'm in a lecture right now (and have another right after), I'll leave it to you if you want to get it done right away, otherwise i can do it in like an hour and a half.

I have the same lectures, so either way it'll have to wait

I've done this and it can be merged with main @dascroft   (assuming we're all in agreement with this change?)
For this the kwarg is 'Output', and can currently accept either 'gif' or 'plot'

Ah so your removing the argue function?

without the argue block it won't run with the commandline, but the commandline section is also currently causing issues.

Ah, apologies. I only removed that because it was causing crashes so made testing difficult

I see, so the commandline portion will be handled differently to the current setup?

it will still be about the same i think, it's just kinda buggy right now. it's not playing well with the kwargs.
And presumably the others are still working on making a more intuitive version for user input, commandline just has some issues that need ironing out.

I see, alright ill merge with main, as i said mentioned on a previous issue, if you need to reference the old code, you can look at the other branches for it or see the commit history, incase it is needed for re-writing the comline interface. With this pull request, this issue is now closed


Adds cache invalidation when a PWA is added

When a PWA is added / updated, the current  timestamp is added
to the Cache with the key PWA_LIST_LAST_UPDATE. This value
has the timeout of 5 times the Pwa List timeout.
When a pwa list page is added to the Cache, a property
cacheTimestamp with the current timestamp is appended to the
object.
When a page is loaded from the cache, the PWA_LIST_LAST_UPDATE
is also loaded.
If no value is found for that page, the Promise
fails and the value is loaded from the db.
If a value is found
from the key, but not found for PWA_LIST_LAST_UPDATE, the
timestamp has expired and the Pwa can be used, since the expire
time for the timestam is larger than the one for the PWA.
If a value for the timestamp is found and is larger then the
PWA List cacheTimestamp, it means the value is expired and the
Promise fails.
If a value for the timestamp is found and is smaller then the
PWA List cacheTimestamp, the PWA is valid and the Promise resolves.

LGTM


Content: Compile list of orgs for usage on Homepage and Our network

User story
As a prospective ReportStream user, I want to know ReportStream's existing senders, so that I feel more confident partnering with RS.
Background & context
The ReportStream team received confirmation from the CDC that we may reference our existing senders by name, but not by logo. This ticket captures the work of compiling the list for use on the Homepage and Our network pages.
Working links

Doc: TBD

Acceptance criteria

[x] Org listed compiled
[x] Org list approved by stakeholders

Column A in this sheet  can be used for the design

Will create new ticket for homepage content part of this work. Closing this side for now.


[Feature request] Deep Copy

import 'dart:convert';

Map clonedObject = JSON.decode(JSON.encode(object));

just deepCopy method.

Would you like to create a PR?


deps: Unpin intl, to follow Flutter's pinning; trim comments

Unpinning package:intl is required for adding our tests to Flutter's "customer tests", #239:
https://github.com/flutter/tests/commit/a047b7a5e6184969d943f88887bbe32658ed99c1
See comment added in the last commit here for background.
Also cut some unnecessary (or no-longer-necessary) verbose comments that we've had in this file, mostly left by the flutter create template.

LGTM! Merging.


Need "Unable to proxy" error on Sharers side

Right now, only Getters receive the following error screen when they are unable to proxy

This should be a parallel experience for both Sharers and Getters, so that they are both able to analyze their networks and submit feedback to uProxy.

Are we sure we want this?  Sharers may not actually be at their computer when the Getter attempts and fails to start a proxy.  Also the Getter can attempt and fail multiple times and I don't think we would want multiple errors to appear on the sharer side.  Also I think a "something went wrong" error is a bit alarming to see for a user who hasn't taken any action - it might lead them to quit or restart uProxy or do something else irrational

I'd agree with this error happening everytime a connection fails feeling wrong.
Maybe instead of opening this every time a connection fails, have some text saying you can tell the sharer to diagnose their connection through the menu? (and at the extreme end, possibly offer an option to send something to the sharer through uProxy letting them know about that)

I think what we really want is to detect what type of NATs users have before they attempt to start proxying.  Then we can know the NAT types for both users through the logs, and can even display to users when their connection is unlikely to succeed.  Once we have that I don't think this screen is really needed.

This bug was created in reaction to sharers emailing<EMAIL_ADDRESS>that they weren't able to get uProxy to work with a friend, but they couldn't find any indication of the connection failing nor could they figure out how to trouble shoot it.
I like the idea of detecting what type of NATs users have ahead of time so that they won't need to get to this step. In the meantime, what I'm asking for for closed beta is that proxying doesn't fail silently on the sharers side.

Proposed mocks with some slight changes that @lucyhe will call out below:

On the getter side:

On the first failed proxy attempt, show toast with the "pop-out" icon.
Clicking pop-out opens the dialog with: "Oops. We were unable to connect. [Retry] It could be that your networks NAT type is incompatible with uProxy. Would you like to uProxy to analyze your network?
[Yes] [No]"
Clicking Retry will try Start Getting Access again
Clicking Yes starts analysis inline (without opening a new tab). Mocks here: https://github.com/uProxy/uproxy/pull/1180
Depending on NAT type, show more info, e.g. "It looks like you are on a symmetric NAT, which is likely interfering with your ability to connect to friends. More info." and "Would you like to submit your NAT type to the uProxy team, to help us better understand the networks our users are on? Privacy policy.
[Yes] [No]"
Clicking Yes takes user to feedback submission form with the include logs and analysis box checked.

On the sharer side:

Always show only the toast with the "pop-out" icon.
Clicking the icon should open a similar error dialog, without the "Retry" option.

All toasts should time out and be dismissed after 30s or so (maybe less?)
A note on handling multiple toast notifications and how they should interact with the getting/sharing status bar:

@jpevarnek is about to add a toast for when an instance is offline https://github.com/uProxy/uproxy/pull/1231
Reuse the same toast for the "Unable to connect" notifications; also keep paper-toast behavior where multiple toasts simply replace each other (even before the timeout is over).
To make sure UI widgets don't interfere with our current status bars (in case the user is already getting or sharing when the error appears), they should float above the status bars. This means there would be at most 3 bars shown at a time (getting status, sharing status and toast).

Thoughts on how this looks hovering over the status bar?

Looks awesome and thanks for working on this at 1:30 am (eek!!).   The toast looks a little more
red, either that can change or the status bar..   Otherwise this is
amazing..  Thanks!!!
On Thu, Apr 9, 2015 at 1:27 AM, lucyhe<EMAIL_ADDRESS>wrote:

Thoughts on how this looks hovering over the status bar?
[image: image]
https://cloud.githubusercontent.com/assets/8723127/7060894/81086ff4-de57-11e4-96e1-d28ea7f07b32.png
—
Reply to this email directly or view it on GitHub
https://github.com/uProxy/uproxy/issues/1203#issuecomment-91119362.

Looks great Lucy! +1 to using the same background color. Could we also make the pop-out icon 2px larger width/height and have it be the same color as the get icon?

Chatting with @gwpenn and @dborkan and thinking of the text "HELP" instead of the launch icon to make it obvious to the user:

SGTM. The all caps makes it a bit jarring. Maybe "GET HELP" to make it a
verb?
On Thu, Apr 9, 2015 at 10:52 AM, lucyhe<EMAIL_ADDRESS>wrote:

Chatting with @gwpenn https://github.com/gwpenn and @dborkan
https://github.com/dborkan and thinking of the text "HELP" instead of
the launch icon to make it obvious to the user:
[image: image]
https://cloud.githubusercontent.com/assets/8723127/7073187/ab28b556-debf-11e4-9105-6acc78cf5f66.png
—
Reply to this email directly or view it on GitHub
https://github.com/uProxy/uproxy/issues/1203#issuecomment-91309271.

I like that too! Do you think size 12 font is too small:

Looks great to me!
On Thu, Apr 9, 2015 at 2:41 PM, lucyhe<EMAIL_ADDRESS>wrote:

I like that too! Do you think size 12 font is too small:
[image: image]
https://cloud.githubusercontent.com/assets/8723127/7077552/b2c247ee-dedf-11e4-9663-f022d82453b7.png
—
Reply to this email directly or view it on GitHub
https://github.com/uProxy/uproxy/issues/1203#issuecomment-91363956.

@lucyhe any update? :)

Yes! One remaining issue is here: https://github.com/uProxy/uproxy/issues/1256


MDC logging [AJ-444]

In this PR:

~bring in Lombok for its super-easy @Slf4j annotation~
~annotate RecordController and RecordDao with @Slf4j~
add example logging statements to RecordController.queryForEntities() and RecordDao.queryForRecords()
create a MDCFilter servlet filter that adds a request id to MDC logging

look for a request id in the incoming request; use it if found
else, generate a new UUID and use that value

configure a logback-spring.xml file based on https://www.baeldung.com/spring-boot-logging but that also adds the MDC RequestId

@jordansafer I removed support for x-amzn-trace; there's no need to support it now, and we can always add it in later if we need it.
@sagehen03 we discussed a lot of this in person, but here goes:

I split the logic between a ServletRequestListener (look in request headers, add id to MDC, clear MDC on requestDestroyed) and a Filter (if request id in MDC, add it to response headers). We need the Filter since ServletRequestListener can't write to response headers.
we don't need all the logback config now, but it was mostly a big copy/paste; if we find problems with it in Azure or elsewhere we can change it at that point - I'd prefer not to do the work to figure out which parts we want and which we don't.
I removed Lombok and am grabbing Loggers directly from SLF4J now
yes - the async responses jump threads and therefore lose the request id in the logs. This is what I see:

2022-10-11 17:22:43,484 DEBUG [ebd7f518-04e6-4ee4-b41a-f38afe1311ef] org.springframework.core.log.LogFormatUtils: GET "/e558c1e0-4d09-4c2f-90bc-2ac9877dcaee/tsv/v0.2/thing", parameters={}
2022-10-11 17:22:43,485 DEBUG [ebd7f518-04e6-4ee4-b41a-f38afe1311ef] org.springframework.web.servlet.handler.AbstractHandlerMapping: Mapped to org.databiosphere.workspacedataservice.controller.RecordController#streamAllEntities(UUID, String, RecordType)
2022-10-11 17:22:43,499 DEBUG [ebd7f518-04e6-4ee4-b41a-f38afe1311ef] org.springframework.web.context.request.async.WebAsyncManager: Started async request
2022-10-11 17:22:43,499 DEBUG [ebd7f518-04e6-4ee4-b41a-f38afe1311ef] org.springframework.web.servlet.FrameworkServlet: Exiting but response remains open for further handling
2022-10-11 17:22:43,501 DEBUG [] org.springframework.web.context.request.async.WebAsyncManager: Async result set, dispatch to /e558c1e0-4d09-4c2f-90bc-2ac9877dcaee/tsv/v0.2/thing
2022-10-11 17:22:43,501 DEBUG [] org.springframework.core.log.LogFormatUtils: "ASYNC" dispatch for GET "/e558c1e0-4d09-4c2f-90bc-2ac9877dcaee/tsv/v0.2/thing", parameters={}
2022-10-11 17:22:43,502 DEBUG [] org.springframework.core.log.LogFormatUtils: Resume with async result []
2022-10-11 17:22:43,502 DEBUG [] org.springframework.web.servlet.FrameworkServlet: Exiting from "ASYNC" dispatch, status 200

I was wrong about the async result having a second uuid … I definitely saw that at one point but now I'm not sure how I made that happen :(


Ability to flip the whole gridster item

I am trying to use https://github.com/lemming/angular-flip or similar libraries. The problem is that this lets only the content to flip and not the whole gridster item.
Is that even possible by doing some hacks? I have tried adding the same style to the gridster items without any effect.
Any suggestions how I can even approach the problem?

What element are you putting it on?  If you put it on the gridster-item, it should work.  However the flip directive is probably flipping the elements inside the gridster-item, so you probably will want to clear the backround color on the gridster-item in the css: background: none.  Then you can add the background color to the elements inside the gridster item.


NIFI-1613 Initial version, try to improve conversion for different SQ…

Initial version.

New method createSqlStringValue(), placeholder for future logic
New test testCreateSqlStringValue()
Refactored TestConvertJSONToSQL.
Setting up Connection pooling is expensive operation.
So let's do this only once and reuse MockDBCPService in each test.

@ToivoAdams is this ready for review?

I plan to close out this PR in a stale PR sweep soon.

I've taken over the proposed change into #1976


Question: Can you set warnTimeout globally?

I'd like to set the warnTimeout default much lower for all my logic, is that possible?

I guess I should make it possible to change the default.
In the meantime if you wanted to have a way to set the default you could use a custom createLogic function that wraps the original like this to only set warnTimeout to your new default unless it was specified to a specific value.
import {createLogic} from 'redux-logic';
function myCreateLogic(opt) {
  if (typeof opt.warnTimeout === 'undefined') {
    opt.warnTimeout = 20000; // default to 20s
  }
  return createLogic(opt);
}

deployed in v0.13.0


fix: #1666 Button group responsive classes not working properly.

I think this should be fixed in the CSS.

Thank you


Update Mvc functional tests to target latest compatibility version

Update MvcTestFixture to use CompatibilityVersion.Latest. (See https://github.com/aspnet/Mvc/blob/release/2.2/test/Microsoft.AspNetCore.Mvc.FunctionalTests/Infrastructure/MvcTestFixture.cs#L31)
Currently blocked by failing endpoint routing tests

cc @rynowak \ @kichalla

See PR: https://github.com/aspnet/Mvc/pull/8275

Fixed in https://github.com/aspnet/Mvc/commit/8eea0ad44c4d469abc2c2d52f1c79505bd6afaeb


can't deepcopy TQDMCallback object

from keras_tqdm import TQDMCallback
from copy import deepcopy
deepcopy(TQDMCallback())
doesn't work because stderr can't be pickled.
A quick fix is to set output_file=None. Maybe this should be the default?

@phausamann Interesting catch. Should be easy enough to fix if None means stderr.
Just curious, why are you trying to deepcopy the callback? It is part of training, not part of the model itself, so you would normally just create it whenever you train.
Cheers

I use it inside of a KerasClassifier/KerasEstimator wrapper in a scikit-learn pipeline. scikit-learn expects that it is able to set all parameters of the fit method in the constructor of the estimator, i.e. including the callbacks. The keras wrapper deepcopies all of the parameters when fit is called.
It is possible to pass the callback only when calling fit, but in my case it is a lot more convenient to do it when I create the estimator object.

I am getting this  ValueError: All callbacks used during a search should be deep-copyable due to not able to deepcopy the callback


[SDP-852] Receiver registration: phone number input with countries dropdown

What
Updated phone number input to show countries dropdown and validate the number for better UX. Jira ticket: https://stellarorg.atlassian.net/browse/SDP-852
Why
It was not a good user experience to ask users to input the phone number in a specific format without any spaces, dashes, etc.
Known limitations
N/A
Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).
[x] This PR's title starts with the name of the package, area, or subject affected by the change.

Thoroughness

[ ] This PR adds tests for the new functionality or fixes.
[x] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's values.yaml file.
[x] No new CONFIG variables are required -OR- the new required ones were added to the deployments (pr-preview, dev, demo, prd).
[x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's values.yaml file.
[x] No new SECRETS variables are required -OR- the new required ones were added to the deployments (pr-preview secrets, dev secrets, demo secrets, prd secrets).

Release

[x] This is not a breaking change.
[x] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[ ] Does the deployment work after merging?

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr33.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr33.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr33.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr33.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr33.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr33.previews.kube001.services.stellar-ops.com

I've tested it and it worked great. I haven't reviewed the code thoroughly though. Maybe you'd want a pass of @ceciliaromao before merging it.

@quietbits: one small suggestion could be to set the starting country based on some IP information from the user, but that might be too much work, so I'm not sure it's worth it right now.

@quietbits: one small suggestion could be to set the starting country based on some IP information from the user, but that might be too much work, so I'm not sure it's worth it right now.

@marcelosalloum This library might actually support that. I'll try that.

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr33.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr33.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr33.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr33.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr33.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr33.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr33.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr33.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr33.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr33.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr33.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr33.previews.kube001.services.stellar-ops.com

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr33.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr33.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr33.previews.kube001.services.stellar-ops.com


Ask for name and email address

[x] Following CODE_OF_CONDUCT.md.
[x] Checked for duplicate enhancements.

Enhancement
Ask for name and email address.
Default to settings in git config.

:tada: This issue has been resolved in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Object of type QueryResponse is not JSON serializable

I'm unable to serialize the query response
response = index.query(vector=embedding, top_k=5, include_metadata=True)
json.dumps(response)

And I get Object of type QueryResponse is not JSON serializable.
Is there a recommendation on how to serialize this object?

@slicksammy thanks for reaching out! The response itself should not be assumed to be JSON serializable. I recommend unpacking the object first. Let us know if that works for you


Tunnel defaults

Working to resolve https://github.com/cloudnative-coop/wgtunnel/issues/1

Closing as this is a WIP


Consumer groups with tags and distributed configuration

Tags have been added to consumer groups in https://github.com/Kong/deck/pull/823
But despite this addition, it seems a distributed configuration doesn't work with consumer groups.
I've tested it on deck v1.17.2 which is the version that includes the consumer group tags addition.
Reproduction
Create consumer groups from a configuration with select_tags: global.
# In config/consumer-groups.yml
_format_version: "3.0"
_konnect:
  runtime_group_name: default

_info:
  select_tags:
  - global

consumer_groups:
- name: gold
  plugins:
  - name: rate-limiting-advanced
    config:
      limit:
      - 200
      window_size:
      - 60
      window_type: sliding

deck sync -s config/

And then try to create a service from another location with another select tag:
# In my-service/services.yml
_format_version: "3.0"
_konnect:
  runtime_group_name: default

_info:
  select_tags:
  - client-api

services:
- name: client-api
  host: example.domain
  port: 80
  path: /api
  protocol: http

deck diff -s my-service/

It results in the following output. The consumer groups should be deleted from decK's perspective. Whereas other entities such as services and plugins are ignored properly.
creating service client-api
deleting consumer-group gold
Summary:
  Created: 1
  Updated: 0
  Deleted: 1

Investigation
I've investigated decK hoping I could contribute to it by fixing this behavior. But my conclusion is that the error comes from the /v1/consumer-groups endpoint that doesn't filter on tags:
https://github.com/Kong/deck/blob/629712b81ebebf9df4b2b60127cc62e9a4b8cb52/konnect/consumer_group.go#L432
The full endpoint decK is using in my case is:
https://eu.api.konghq.com/konnect-api/api/runtime_groups/[RUNTIME_GROUP_ID]/v1/consumer-groups

I've tried it on the CLI, and it ignores the tags when sent as parameters (?tags=client-api). As opposed to endpoints such as /services which filter correctly on tags.
I could not find any documentation about /v1/consumer-groups, only about /consumer_groups.
Any reason not to use the second one instead? Should the first one be documented?

@gregoirechauvet Thank you very much for this ticket, and your investigation! I have been able to reproduce the issue with your steps. There are indeed 2 different issues:

the tags filtering doesn't work as expected with the konnect endpoint
the tags filter is not added properly by deck (like the other endpoints).

we are going to provide fixes as soon as possible and keep you on touch.
About the different endpoints for consumer groups, this is expected. There are some differences in the implementation between Konnect (saas) vs Kong. Usually, konnect users don't deal with the endpoint directly so that's why it is not documented.

Hi @gregoirechauvet , would you mind testing it again with decK v1.25.0? This version should have fixed this issue.


network: hook net plugin Status() up to NetworkReady and runtime status

Port https://github.com/kubernetes/kubernetes/pull/43474 over to CRI-O
and hook network plugin status up to the runtime NetworkReady() call so
the plugin's status is accurately reported back to the orchestrator.
@rajatchopra gotta be a bit careful about this one RE https://github.com/kubernetes/kubernetes/issues/43815 since I'm not sure kubelet correctly differentiates between runtime readiness reasons.
And in fact it does fail:
11s		4s		5	default-scheduler			Warning		FailedScheduling	no nodes available to schedule pods
So it seems CRI-O and kubelet remote runtimes need finer grained scheduling decisions.  Which is pretty odd, since I've even tried with hostNetwork:true and usually the scheduler allows that with local runtimes...

@dcbw Is this something that we still need?

@dcbw Can we close this or update it?  Trying to clean old PRS

@rhatdan The one should be closed. It's stale.


Using blob as a stream inv12

In v2.1 it was very easy to download blob as a stream and using is it as pandas data frame but it seems like v12 it's not available. I can not load a gzip CSV as a data frame directly.
with BytesIO() as input_blob:
    # Download as a stream
    block_blob_service.get_blob_to_stream(containerName, blobName, input_blob)
    input_blob.seek(0)
    DF = pd.read_csv(input_blob, compression='gzip')

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

ID: 15591874-317e-ce4c-0dff-20d06b625e40
Version Independent ID: be7fed9a-343a-0ec7-a94d-02c354d1ae33
Content: Quickstart: Azure Blob storage library v12 - Python
Content Source: articles/storage/blobs/storage-quickstart-blobs-python.md
Service: storage
Sub-service: blobs
GitHub Login: @mhopkins-msft
Microsoft Alias: mhopkins

Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .

@mkrdip I see you have posted similar query in different repro also informed that your  issue is been fixed.
Thanks for sharing the troubleshooting steps which helped you in fixing the issue. https://github.com/Azure/azure-sdk-for-python/issues/10782
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


v1 docs

Sorry if this has already been asked, but do you have the version 1 docs anywhere.
I have a project using chartjs v1, and need to make some minor tweaks.
Thanks.

https://github.com/chartjs/Chart.js/tree/v1.1.1/docs

Thanks for the rapid response!!!


Control bar hiding properly in IE9 and IE10

Fix related to #1758

Thanks! Could you resubmit without changes to /build/?

Sure. Just for reference when is this fox going to be available once I resubmit it?

@johndyer Also, I noticed that you haven't tag your latest release. If you can tag it please so we can take advantage of the version 2.21.2

@johndyer Thanks for putting the tag. Is there anything else you need for this pull request?

I'll check through the current PRs this week to merger and release. Thanks
again for this!
On Friday, July 1, 2016, Rafael Miranda<EMAIL_ADDRESS>wrote:

@johndyer https://github.com/johndyer Thanks for putting the tag. Is
there anything else you need for this pull request?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/johndyer/mediaelement/pull/1760#issuecomment-230082482,
or mute the thread
https://github.com/notifications/unsubscribe/AANE065kaphXSUIR1u1ThAbJBCH1l2E4ks5qReXZgaJpZM4I7Wew
.

--
John Dyer - http://j.hn/

You are welcome. Thanks for this awesome player

@johndyer Any updates on this?

Sorry about that. I was waiting for your other Pull to have the /build/
changes removed. I'll go ahead and do this one and a few others, but if you
can update the stretching one then I can release them both.
On Tue, Jul 12, 2016 at 8:05 PM, Rafael Miranda<EMAIL_ADDRESS>wrote:

@johndyer https://github.com/johndyer Any updates on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/johndyer/mediaelement/pull/1760#issuecomment-232226771,
or mute the thread
https://github.com/notifications/unsubscribe/AANE0zBMJi_plmqa8pM7N0RvLQn0LsV6ks5qVDnFgaJpZM4I7Wew
.

--
John Dyer - http://j.hn/

@johndyer I fixed the build for the stretching mechanism. Let me know if you are gonna merge that one as well


Documentation: TranslateHttpLoader picks up HttpClient interceptors

Current behavior
The documentation suggests using the TranslateHttpLoader for downloading the the translation files.  If there are HttpInterceptors, such as for Authentication, provided in the application, this can have unwanted side-effects.
Expected behavior
Realistically, you only want to use the TranslateHttpLoader without HttpInterceptors.  This can be achieved using the HttpBackend class, as described here.
How do you think that we should fix this?
Update the documentation to suggest this is a problem, and the alternative is to use the HttpBackend with HttpClient to ignore interceptors, like so:
export function translateHttpLoaderFactory(httpBackend: HttpBackend): TranslateHttpLoader {
    return new TranslateHttpLoader(new HttpClient(httpBackend));
}

...
        TranslateModule.forRoot({
            loader: {
                provide: TranslateLoader,
                deps: [HttpBackend],
                useFactory: translateHttpLoaderFactory
            }
        }),

Minimal reproduction of the problem with instructions
Use an HttpInterceptor in the App that appends an external base url to all calls, thus breaking the location of the TranslateHttpLoader.
import {Inject, Injectable} from '@angular/core';
import {HttpEvent, HttpHandler, HttpInterceptor, HttpRequest} from '@angular/common/http';
import {Observable} from 'rxjs';

import {API_BASE_URL_TOKEN} from '../../shared/config.module';

@Injectable()
export class ApiBaseUrlInterceptor implements HttpInterceptor {
    private readonly apiBaseUrl: string;

    constructor(@Inject(API_BASE_URL_TOKEN) apiBaseUrl: string) {
        this.apiBaseUrl = apiBaseUrl;
    }

    public intercept(request: HttpRequest<any>,
                     next: HttpHandler): Observable<HttpEvent<any>> {
        return next.handle(request.clone({url: `${this.apiBaseUrl}${request.url}`}));
    }
}

Environment

ngx-translate version: 10.0.2
Angular version: 6.1.7

Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:
- Node version: XX
- Platform:

Others:

I have same error.
My AppInterceptor not worked(((

I posted the link to this issue as solution to some other issues I found and studied during my own research. They all seem to point to exactly the same problem in Angular 8 when using Interceptors. This issue here was a godsend that fixed the problem for me :)

In the 404 link -@antonlashan had the answer for me -> creating a custom httpclient did the trick

it works but don't know why folder name has to be i18n mandatory. other name doesn't work  😞  spent 2 hrs on this

Had a similar issue, causing circular dependencies.
Using instead the HttpBackend fixed it.


Added Solution for NQueens Problem no 51 from Leetcode

Problem Description :
https://leetcode.com/problems/n-queens/

@fame2105 Please check your solution and send a pull request again


Chorus Succulent does not spawn with BYG

I was able to confirm by test removing BYG. If Biome's you'll go is installed, chorus succulent is replaced by a different block from that mod; conflicting item IDs I think

I was able to confirm by test removing BYG. If Biome's you'll go is installed, chorus fruit is replaced by a different block from that mod; conflicting item IDs I think

Sorry not chorus fruit, chorus succulents

In my test im using BYG and BetterEnd at the same time, i still can find chorus succulent but it only spawned on the original minecraft highlands biome


Document new severity argument in getIssues API endpoint

I'm gonna merge this so that I can pull this also to https://github.com/pganalyze/pganalyze-web/pull/486


Create a <selectedGuid, referencersPath[]> map to improve performance.

With this we should go from O(m*n) to O(m+n)

hey @jeffjadulco, first of all, thanks for the tool!
Really useful!
At some point at got kind of stuck with a large folder, then I realized that a way to improve the performance was, instead of scanning all the files for each selectedGUID, pre-create a map with all the files that have a reference to those guides.
With this change, I was able to reassign guids to a huge plugin in approx 2h instead of 20h+ (I left my laptop running but after the update and after some experiments I just cancelled the process and run the updated version).
I think that with this change we go from O(n*m) to a O(n+m) complexity.
Check if it makes sense for you to merge this change, (or not :D haha no hard feelings from my side)

Hi @mayofunk, thanks for taking the time to do this!
Finally, someone used this tool on a huge project. I honestly didn't expect that 20 hours 😅. I only used this tool on a moderately sized project, and it always took me around an hour on average.
I tested your changes on this 2D sample project, and it was really fast. Great usage of GetDependencies()!
Will definitely merge this!


[BUG] doom upgrade fails with evil-org no upstream configured

Describe the issue
Start with a brief 1 or 2 sentence summary of issue.
doom upgrade fails with following error:
Wrong type argument: listp, "There were errors:

   - evil-org: ((error Failed to run \"git\"; see buffer *straight-process*) fatal: no upstream configured for branch 'master')"

It's a known issue :

rm -rf ~/.emacs.d/.local/straight/{repos,build}/{evil-org,evil-org-mode}
~/.emacs.d/bin/doom upgrade should work again.

Delete the repos and the packages from .local/straight everytime you have this error

Oh thanks, that worked. 🙇

For future reference, there is an open issue for this: https://github.com/hlissner/doom-emacs/issues/1721#issuecomment-539221633


Uncaught TypeError: Cannot read property 'endsWith' of undefined

Describe the bug
which template:

[X] MaterialDesignFrameworkModule — Material Design
[ ] Bootstrap3FrameworkModule — Bootstrap 3
[ ] Bootstrap4FrameworkModule — Bootstrap 4
[ ] NoFrameworkModule — plain HTML
[ ] Other (please specify below)

A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

recurrent link

Desktop (please complete the following information):

OS: [macOS]

Browser [Google Chrome]

Version [72.0.3626.109]

Angular version

Log output covering before error and any error statements
Uncaught TypeError: Cannot read property 'endsWith' of undefined

Duplicate of #73


Fix non-passive event listener

Summary
Fix the following violations.
https://vue-3-slider-component.netlify.app/?path=/docs/vue-3-slider-component--vue-3-slider-component

[Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952

Detail
A touchstart event causes scrolling action as default.
However, a browser is unable to start scrolling until the event listener has finished,
because the event listener might cancel the action by calling preventDefault().
If the event listener takes too long to execute, this can cause a 'scroll jank'.
By setting the passive option, an event listener declares that it will not cancel the default action,
so the browser can start scrolling asynchronously, without waiting for the listener to finish.
See also https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener#using_passive_listeners

Shipped v0.1.3


make librmb a vendordep

After hours of grueling over this, I finally got this to work (mostly). The next step is to host the maven repository on github pages. Big thanks to pathplanner for the sample project!

Merging this to test the github actions


Fix import version with prebuilt domains

Fixes #
Issue 1051
Proposed Changes
 Even though the serialized name is correct, the change in the model property name causes the request json to be empty.

Testing

Pull Request Test Coverage Report for Build 2529

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 67.44%

Totals

Change from base Build 2517:
0.0%

Covered Lines:
4181

Relevant Lines:
5872

💛  - Coveralls


e2e test the datetime format with regular expression question.

Hi guys,
I am a fresh and facing problem when using the regular expression to test the Datetime format in the page.
The expect display is like "Last update: Apr 17 at 1:21PM"
So I wrote something in specs like:
it('DEPLOYMENT CHART TITLE AND UPDATE AUTOMATICALLY01', function () {
    var titleFormat = function (success) {
         var patrn = /^[L]{1}[ast]{3}\s[update]{6}[:]\s[A-Z]{1}[a-z]{2}\s[0-3]?[0-9]{1}\s[at]{2}\s[0-1]{1,2}[:][0-5]{1}[0-9]{1}[A,P]{1}[M]$/;
         if (!patrn.exec(success)) {
            return false;
         } else{
            return true;
         }
    };
    var depCharTitle = element(by.binding('curTime'));
    expect(titleFormat(depCharTitle.getText())).toBe(true);
  });

I tried to verify the expression manually, it is correct I think.
But the script running result always reture "false".
Can someone help on this? Appreciate it.

@juliemr can you help on this?

Please read the contributing guidelines; these types of questions are ill-suited for GitHub. Thanks!

Looks like you have an issue where depCharTitle.getText() is returning a promise, but you're treating it like a string.

@juliemr thanks  for your response, I fixed it.


PLC2801 false positive when __exit__ is not called

i have a context manager that wraps another context manager, eg:
from contextlib import AbstractContextManager

class Wrapped:
    def __init__(self, cm: AbstractContextManager[None]):
        self.cm = cm

    def __enter__(self):
        self.cm.__enter__() # PLC2801: Unnecessary dunder call to `__enter__`

    def __exit__(self):
        self.cm.__exit__(None, None, None)

playground
in this case, i can't replace the __enter__ call with a with statement because __exit__ is not called in the same place. ruff should be able to detect cases like this where __enter__ is called on its own

I believe this is fixed by #9496


Repeating a complex command

Let's say I have such a mapping
(ryo-modal-key "d i a" 'mark-whole-buffer :then '(kill-region))

If I try to use repeat on this, it repeats only mark-whole-buffer and does not kill-region.

Hi! Sorry it took so (very) long time for a response. I've tried various solutions, but nothing really seem to work. Ryo is using call-interactively for all of the commands (both mark-whole-buffer and kill-region in this case), and I guess those commands "push" to repeat.
I've just written a function called ryo-modal-repeat which should work like repeat, but only for ryo commands. Please try it out (more info in README and docs) and let me know if it works for you!
Also I must say I'm very impressed by your ryo-based config: huge work!

Thanks, this is great news. I tried and it works pretty well.

Also I must say I'm very impressed by your ryo-based config: huge work!

Thank you! It seemed to be the perfect solution for my problems to map any combination of keys I want (mapping things like co or do in evil is a pain) and use the Emacs ecosystem that I like. However, it still has a LOT of things to be done for it to feel nearly as productive as my Vim setup.


timeline tweaks

switch to timeline2
add "# of # collections" to provide visual feedback of filtering

@dcnb I quickly added a count in timeline2-count just to test it out, https://github.com/uidaholib/dloi-csv/tree/timeline2-count


Updated readme

Inspiration section added.

Fixes Issue
This PR fixes the following issues:
#example

Changes proposed
Here comes all the changes proposed through this PR

Check List (Check all the boxes which are applicable)

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Add all the screenshots which support your changes

could you please shift this pr to server branch


Clm/southworks cosmos db changes

Branch tracking the Southworks Cosmos DB Changes: #1035
The way we have builds setup now, external PRs (aka: Forks) don't get validated by the build system. So This is a local branch that will be auto-build.

Pull Request Test Coverage Report for Build 42038

0 of 0   changed or added relevant lines in 0 files are covered.
37 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.5%) to 52.343%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder.Azure/CosmosDbStorageOptions.cs
1
85.71%

/libraries/Microsoft.Bot.Builder.Azure/CosmosDbStorage.cs
36
53.75%

Totals

Change from base Build 42020:
0.5%

Covered Lines:
4881

Relevant Lines:
9325

💛  - Coveralls

I've approved this.


Swift

how i use it for swift ?

hey @muzamilhassan1987 -- this project isn't really supported anymore.
if you want to use CoreData in Swift, i suggest looking at https://github.com/jessesquires/JSQCoreDataKit


Adding Sara Chatroom Integration to Docs

Proposed changes:

...

Status (please check what you already did):

[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

@lunelson I took a stab at creating the custom Layout, but not entirely sure where to go from here. Any pointers on if I'm on the right track?

@lunelson I took a stab at creating the custom Layout, but not entirely sure where to go from here. Any pointers on if I'm on the right track?

@b-quachtran Hey, so I've got this working now with their default chatbot, I recommend you try it out and see now if you can connect it to a real rasa bot.
Right now it just mounts right away, but probably you want to implement something like a button to launch the bot, and have it otherwise be hidden, Also, it should probably be collapsible, which currently it doesn't seem to be. You'll have to look in to the documentation as to how their component can be customized I guess.

Correction: this is only working in development right now, it doesn't seem to come through in the build, I'm not yet sure why

@lunelson Awesome, yes the UI is loading for me in docs. I'll work on getting this integrated with the Sara backend and tweaking a few things like the initial payload. Thanks!

@b-quachtran I assume you closed this because we're going to use the rasa-webchat package instead...

Yes, the rasa-webchat is going to be used instead of the Botfront widget


Update variable speed air-cooled chiller in EnergyPlus dataset

Reminder of issue encountered while working on the change code proposal with the wrong efficiency used in the live version of 90.1.

Fixed with https://github.com/NREL/EnergyPlus/pull/9641


Feat/phone

Codecov Report

Merging #19 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #19   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         3    +1
  Lines           40        45    +5
  Branches        10        11    +1
=========================================
+ Hits            40        45    +5

Impacted Files
Coverage Δ

src/addQueryToUrl.ts
100.00% <100.00%> (ø)

src/checkPhoneNumber.ts
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


feat: add enum for appstate and lint whole repo

[x] add enum for appState to replace pure string.
[x] update maci-cli package version
[x] fix child_process problem
[x] lint whole repo

@kittybest thanks, please fix all the new line at the end of the files problems and run prettier/linter

wait I just run prettier for the whole repo and check in they all have eol-last, but the origin branch version doesn't have eol-last for all file, let me check what happened.


cracklabs.com/prawto is down. Move or copy documentation to github

Yep, the site is still down (apparently it was "recently registered on Namecheap"). Is there anything useful on the site?


Response example rendered incorrectly

Hi,
Firstly, thanks for making this repo! It does everything I want from a Swagger viewer, all in a lightweight package ❤
That said, I've found a small bug in the example response section, where the content from one example flows on top of the next one.

Possible solution
There is a flex: 1 applied to the element. If I remove that, then the example renders much better:

I am unable to recreate this issue on my end, (tested on chrome, firefox and safari)
Can you share the following info

RapiDoc Version you are using
Browser and its Version
OS and Screen Resolution

If you know a possible solution then I will be more than happy to take a PR

The cause of this is the same as in my other issue. If I change the opening tag from <html> to <!doctype html> then the examples render correctly.


I seem to be unable to access snack using any browser on a Mac

Summary
Whenever I try to load snack in a browser (any examples on any pages) it just hangs and loads forever. I've tried resetting my browser, resetting the cache, re-installing chrome, flushing the DNS, restarting and updating the computer with no luck. I've also tried resetting the router and changing my IP.

Above is the javascript error that is coming up.
OS: macOS 12.4
I can confirm another user with the same spec device but different networks and location is having issues as well
What platform(s) does this occur on?
Web
SDK Version
Any examples on any react native pages or just loading snack in general
Reproducible demo or steps to reproduce from a blank project
Going to https://snack.expo.dev/ or any other page with snack examples on it

I'm having the same issue. How did you solve the problem?