About Implementation of 3D hand pose

Hi Mediapipe guys.
After temporarily finishing the face detection project, I focus on the hand detection and tracking project.
I still do some demo based on your aar package customization.
It is similar with this project, but we build our project on USB camera.
https://github.com/jiuqiant/mediapipe_multi_hands_tracking_aar_example
My tar-built script is:
load("//mediapipe/java/com/google/mediapipe:mediapipe_aar.bzl", "mediapipe_aar")

mediapipe_aar(
    name = "mp_multi_hand_3d_tracking_aar",
    calculators = ["//mediapipe/graphs/hand_tracking:multi_hand_mobile_calculators"],
)

My launching command is:
bazel build -c opt --fat_apk_cpu=arm64-v8a,armeabi-v7a --define 3D=true //mediapipe/examples/android/src/java/com/google/mediapipe/apps/aar_examples:mp_multi_hand_3d_tracking_aar
The hand pose project can be run.
I used the callback as @jiuqiant illustrated to get x, y, z 's coordinate. However, the z value is always 0.
The camera is RGB camera.
My question is how can I visualize the depth and really measure the depth?
Thanks & Regards!
Momo

Hi @jiuqiant and @fanzhanggoogle .
How can I build the 3D hand pose aar package and use in RGB camera.?
Currently, in my 2D RGB camera project, my retrieved z coordinate value is 0.0.
It looks like it is expected to visualize the depth, but cannot obtain the depth value.
Thanks & Regards!

My hardware is UVC-Camera. It is parallel to the taken object.

I am not sure, whether the rgb-depth camera, other 3D cameras or multiple 2D cameras are the essential hardware device for the 3D hand pose estimation on Mediapipe.

My taken hands under the camera are some hands playing piano, I think it is out-of-training-dataset samples. Will mediapipe think the depth is 0.0 if the scene are not built in point-cloud during training?

My Java code is imitated and transferred from:
https://github.com/jiuqiant/mediapipe_multi_hands_tracking_aar_example
I notice in the APK build script,
https://github.com/google/mediapipe/blob/ae6be10afe59a6a99d8a68007784706ac98720dd/mediapipe/examples/android/src/java/com/google/mediapipe/apps/multihandtrackinggpu/BUILD
The script is :
genrule(
name = "model",
srcs = select({
"//conditions:default": ["//mediapipe/models:hand_landmark.tflite"],
":use_3d_model": ["//mediapipe/models:hand_landmark_3d.tflite"],
}),
outs = ["hand_landmark.tflite"],
cmd = "cp $< $@",
)
How can I make multihandtrackinggpu.binarypb to call hand_landmark_3d.tflite instead of hand_landmark.tflite during inference time?

Hello, @eknight7 , @jiuqiant @fanzhanggoogle .
I forcedly set the default hand pose model as hand_landmark_3d.tflite.
It can work currently.
Thanks for your patience.
Maybe this can be closed.
Wish you are all good during epidemic.
Regards!
Momo


508 Bug: 'Here" Link Description

https://ecmps-tst.app.cloud.gov
There's a link named 'here' in the what's new section, needs to be updated to something that's more descriptive

Chris to send us a description to update in content API

As per #5569, the here link already updated for all the environments.

Testing complete, link is now unique


Atlassian.Sourcetree version 3.4.5

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

You will need to edit folder from manifests/a/Atlassian/Sourcetree/3.4.5/ to manifests/a/Atlassian/Sourcetree/<IP_ADDRESS>/

@KaranKad working on it


[master] Enable package-source-build to create previously-source-built tarball

Fixes https://github.com/dotnet/source-build/issues/1647
I don't know if there are any blockers to turning this back on--giving it a try in CI.

Obsolete: package-source-build is enabled in @crummel's 5.0 dev branch currently: https://github.com/crummel/dotnet_core-sdk/blob/3c82615fcce91da1ccffb335c228492ec7b9908b/eng/source-build/repos/known-good.proj#L70


Optional Notifier for Conditions

What does your feature do?
When creating a condition can we have an option whether to notify an individual about that particular condition? This will bypass the chat spam caused by not filling a condition that isn't detrimental. I.e. Leaving a world to do something else while a quest is active.
How would people use it?
https://camo.githubusercontent.com/23267d859c71ffcb3cd6f4123060c813a2d75817eb8c8a1f535f17c7f4fc2338/68747470733a2f2f692e696d6775722e636f6d2f455379363872492e706e67
Add it as an option when editing conditions:
1 - Set name
2 - Entity
3 - Player
4 - World
5 - Check placeholder
6 - Fail the Quest: No
7 - Notify if conditions not met: Yes
8 - Save
9 - Exit

Obviously Yes by default and it would function identically as it does now.

Set your quest to fail if the condition is not met.


Code cleanup: Improve gomega matchers in pkg/virt-launcher/virtwrap

What this PR does / why we need it:
Improves matching for errors, length, and substrings.
Release note:
None

/retest

/lgtm
no reason to block this PR because a single test is illogical. that could be handled separately.

/retest

/sig code-quality

/retest

/retest

/retest

@EdDev, can you please take another look?

/retest

/retest

/retest

I think the main change from the last time I reviewed it is the usage of custom matcher at Use ContainSubstring() matchers in virt-launcher/virtwrap tests commit.
I would have preferred not to complicate the tests by introducing that one, it looks much worse than what exists now. It also feels less syntactic and with more logic, which may fit a following PR.
Said that, I do not want to block on it. Thank you for the effort!

I agree.
/approve
/hold
I think we can do something like
shouldContain := func(xml, subDomain string){
ExpectWithOffset(1, xml).To(ContainSubstring(subDomain), xml)
}
```1

I have removed the commit which adds ContainSubstring() matcher.

/retest

/retest

/retest

/retest

/hold cancel

/retest

/retest


Fix handling of build.py --pkgarch.

--pkgarch overrides the architecture which is used in subsequent runs to
build different packages (deb,tar.gz,rpm) and the architecture is used
to index the build information kept in a dict, which of course fails if
it has been overridden. This commit resets the overridden architecture
after each run of fpm to initial, in order to fix the packaging.

Looks good. Thanks, @bwolf!


Vulnerability roundup 109: oh-my-zsh-2021-11-11: 1 advisory [9.8]

search, files

[ ] CVE-2021-3727 CVSSv3=9.8 (nixos-21.11)

CVE details
CVE-2021-3727
Vulnerability in rand-quote and hitokoto plugins Description: the rand-quote and hitokoto fetch quotes from quotationspage.com and hitokoto.cn respectively, do some process on them and then use print -P to print them. If these quotes contained the proper symbols, they could trigger command injection. Given that they're an external API, it's not possible to know if the quotes are safe to use. Fixed in: 72928432. Impacted areas: - rand-quote plugin (quote function). - hitokoto plugin (hitokoto function).

Scanned versions: nixos-21.11: 573095944e7.
Cc @nequissimus

This was fixed in 2021-11-11.


[Bug]: With only Edit permissions on Environments, The create and delete environment CTAs are still enabled.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I give only edit permissions on Environments the Create Environment and Delete env CTA is still enabled.
Steps To Reproduce
https://github.com/appsmithorg/appsmith/assets/101863839/31908f2d-ee48-48fa-8762-c39cc2583307
Public Sample App
No response
Environment
Deploy Preview
Issue video log
No response
Version
Cloud

Tested - works fine


Display user group parenthetically like the graph editor

The graph editor displays the selected user group parenthetically to the right of the user name.
This is a good reminder to curators as to what group they are currently annotating for.
Can the display of groups be made the same in the SAE?
Thx.

@vanaukenk
I can put it there, but originally it was put here (pic below) as it showed it was affecting only the form being currently created and not the table view of already created models.

Let me know what you think. I can put on both or remove it on the form..

Thanks @tmushayahama
Maybe having it on both would be best.  I like the visual cue next to the curator name, but I don't think we need to also take it off the form.

The SAE also needs to recognize when a user has more than one group in the YAML file. I have two groups, "MGI" and "GO Central". In the graph editor, you can see both when I click on my groups with tick boxes to change the selection.

However, in the SAE, when I click on the pull down, I only have one group.

I also like how the Graph group pull down menu still shows my existing info instead of covering it up. Is that possible in the SAE?
Here's a model I created, though I don't know if you'll see my groups when you are logged in:
http://<IP_ADDRESS>:8910/workbench/simple-annoton-editor/?model_id=gomodel:5a7e68a100000324


iterable weirdness

I'm guessing this is new:
shared void run() {
  print({ 1, 2 }.filter((Integer x) => true));          // prints "1"
  print({ 1, 2 }.filter((Integer x) => true).sequence()); // error
}

console:
jvasileff@orion:simple$ ceylon compile-js simple && ceylon run-js simple
Note: Created module simple/1.0.0
1

/private/tmp/simple/modules/simple/1.0.0/simple-1.0.0.js:12
le:m$1.mtt$([{t:m$1.Integer}]),Return$Callable:{t:m$1.$_Boolean}})).sequence()
                                                                    ^
TypeError: Object 1 has no method 'sequence'
    at run (/private/tmp/simple/modules/simple/1.0.0/simple-1.0.0.js:12:218)
    at [eval]:1:282
    at Object.<anonymous> ([eval]-wrapper:6:22)
    at Module._compile (module.js:456:26)
    at evalScript (node.js:536:25)
    at startup (node.js:80:7)
    at node.js:906:3

I realize this is a bug, but still... is using sequence instead of sequence() on purpose?

Ah, no, good catch. I updated the description to add the ().

I just ran this with sequence and got JsCallable string; with sequence() I get [1,2]

Huh, so I guess you also get {1, 2} for the first one. I'm running a build from Monday night, but can try again once I update.

So, were you able to reproduce this?

I haven't recompiled yet. I'll try now.

@chochos sorry, this works perfectly well with a fresh build.


prop getActions return functions to execute action

This includes the prop getActions, which will return to a function a json to execute _forceRightSwipe, _forceLeftSwipe and _forceUpSwipe.
The return looks like:
{
  yup: this._forceRightSwipe.bind(this),
  nope: this._forceLeftSwipe.bind(this),
  maybe: this._forceUpSwipe.bind(this),
}

It can be used like:
render () {
  let swipeActions
  return (
    <View>
      <SwipeCard getActions={actions => { swipeActions = actions } />
      <TouchableHighlight onPress={() => swipeActions.yup()}>
        <Text>EXECUTE YUP ACTION</Text>
      </TouchableHighlight>
    </View>
  )
}

This probably helps on Issue #62.
Note: I took the liberty to include the swipe as using on PR #70. It's easy to remove if not approved.
Note 2: I took off the function () => { alert('tapped') } from default prop onClickHandler. Seemed as possible problem someone might have.

Should we close this PR?


Cannot Find Smart Irrigation

trying to add it from configuration - > add integratrion

that is weird, I just tried and can see it just fine.

Sorry, I think I didn't restart HA.....
After a restart I can see it


error: reference to 'detail' is ambiguous

I just switched to the header only version 3 and get the following errors when compiling my 64-bit application:
tinyutf8.h:732:49: error: reference to 'detail' is ambiguous
  utf8_string( const char* str , size_type len , detail::read_codepoints_tag );
                                                 ^~~~~~

This is the result of the gcc -v command:
Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=C:/CodingXP/mingw730_32/bin/../libexec/gcc/i686-w64-mingw32/7.3.0/lto-wrapper.exe Target: i686-w64-mingw32 Configured with: ../../../src/gcc-7.3.0/configure --host=i686-w64-mingw32 --build=i686-w64-mingw32 --target=i686-w64-mingw32 --prefix=/mingw32 --with-sysroot=/c/mingw730/i686-730-posix-dwarf-rt_v5-rev0/mingw32 --enable-shared --enable-static --disable-multilib --enable-languages=c,c++,fortran,lto --enable-libstdcxx-time=yes --enable-threads=posix --enable-libgomp --enable-libatomic --enable-lto --enable-graphite --enable-checking=release --enable-fully-dynamic-string --enable-version-specific-runtime-libs --enable-libstdcxx-filesystem-ts=yes --disable-sjlj-exceptions --with-dwarf2 --disable-libstdcxx-pch --disable-libstdcxx-debug --enable-bootstrap --disable-rpath --disable-win32-registry --disable-nls --disable-werror --disable-symvers --with-gnu-as --with-gnu-ld --with-arch=i686 --with-tune=generic --with-libiconv --with-system-zlib --with-gmp=/c/mingw730/prerequisites/i686-w64-mingw32-static --with-mpfr=/c/mingw730/prerequisites/i686-w64-mingw32-static --with-mpc=/c/mingw730/prerequisites/i686-w64-mingw32-static --with-isl=/c/mingw730/prerequisites/i686-w64-mingw32-static --with-pkgversion='i686-posix-dwarf-rev0, Built by MinGW-W64 project' --with-bugurl=https://sourceforge.net/projects/mingw-w64 CFLAGS='-O2 -pipe -fno-ident -I/c/mingw730/i686-730-posix-dwarf-rt_v5-rev0/mingw32/opt/include -I/c/mingw730/prerequisites/i686-zlib-static/include -I/c/mingw730/prerequisites/i686-w64-mingw32-static/include' CXXFLAGS='-O2 -pipe -fno-ident -I/c/mingw730/i686-730-posix-dwarf-rt_v5-rev0/mingw32/opt/include -I/c/mingw730/prerequisites/i686-zlib-static/include -I/c/mingw730/prerequisites/i686-w64-mingw32-static/include' CPPFLAGS=' -I/c/mingw730/i686-730-posix-dwarf-rt_v5-rev0/mingw32/opt/include -I/c/mingw730/prerequisites/i686-zlib-static/include -I/c/mingw730/prerequisites/i686-w64-mingw32-static/include' LDFLAGS='-pipe -fno-ident -L/c/mingw730/i686-730-posix-dwarf-rt_v5-rev0/mingw32/opt/lib -L/c/mingw730/prerequisites/i686-zlib-static/lib -L/c/mingw730/prerequisites/i686-w64-mingw32-static/lib -Wl,--large-address-aware' Thread model: posix gcc version 7.3.0 (i686-posix-dwarf-rev0, Built by MinGW-W64 project)

Hi! Could you post the whole error message here? That is, in order to know what ambiguates „detail“.
Thanks a lot and sorry for the inconvenience 😉
Jakob
Von: githubuser0xFFFF
Gesendet: Donnerstag, 9. Mai 2019 10:40
An: DuffsDevice/tiny-utf8
Cc: Subscribed
Betreff: [DuffsDevice/tiny-utf8] error: reference to 'detail' is ambiguous(#22)
I just switched to the header only version 3 and get the following errors when compiling my 64-bit application:
tinyutf8.h:732:49: error: reference to 'detail' is ambiguous
utf8_string( const char* str , size_type len , detail::read_codepoints_tag );
^~~~~~
This is the result of the gcc -v command:
Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=C:/CodingXP/mingw730_32/bin/../libexec/gcc/i686-w64-mingw32/7.3.0/lto-wrapper.exe Target: i686-w64-mingw32 Configured with: ../../../src/gcc-7.3.0/configure --host=i686-w64-mingw32 --build=i686-w64-mingw32 --target=i686-w64-mingw32 --prefix=/mingw32 --with-sysroot=/c/mingw730/i686-730-posix-dwarf-rt_v5-rev0/mingw32 --enable-shared --enable-static --disable-multilib --enable-languages=c,c++,fortran,lto --enable-libstdcxx-time=yes --enable-threads=posix --enable-libgomp --enable-libatomic --enable-lto --enable-graphite --enable-checking=release --enable-fully-dynamic-string --enable-version-specific-runtime-libs --enable-libstdcxx-filesystem-ts=yes --disable-sjlj-exceptions --with-dwarf2 --disable-libstdcxx-pch --disable-libstdcxx-debug --enable-bootstrap --disable-rpath --disable-win32-registry --disable-nls --disable-werror --disable-symvers --with-gnu-as --with-gnu-ld --with-arch=i686 --with-tune=generic --with-libiconv --with-system-zlib --with-gmp=/c/mingw730/prerequisites/i686-w64-mingw32-static --with-mpfr=/c/mingw730/prerequisites/i686-w64-mingw32-static --with-mpc=/c/mingw730/prerequisites/i686-w64-mingw32-static --with-isl=/c/mingw730/prerequisites/i686-w64-mingw32-static --with-pkgversion='i686-posix-dwarf-rev0, Built by MinGW-W64 project' --with-bugurl=https://sourceforge.net/projects/mingw-w64 CFLAGS='-O2 -pipe -fno-ident -I/c/mingw730/i686-730-posix-dwarf-rt_v5-rev0/mingw32/opt/include -I/c/mingw730/prerequisites/i686-zlib-static/include -I/c/mingw730/prerequisites/i686-w64-mingw32-static/include' CXXFLAGS='-O2 -pipe -fno-ident -I/c/mingw730/i686-730-posix-dwarf-rt_v5-rev0/mingw32/opt/include -I/c/mingw730/prerequisites/i686-zlib-static/include -I/c/mingw730/prerequisites/i686-w64-mingw32-static/include' CPPFLAGS=' -I/c/mingw730/i686-730-posix-dwarf-rt_v5-rev0/mingw32/opt/include -I/c/mingw730/prerequisites/i686-zlib-static/include -I/c/mingw730/prerequisites/i686-w64-mingw32-static/include' LDFLAGS='-pipe -fno-ident -L/c/mingw730/i686-730-posix-dwarf-rt_v5-rev0/mingw32/opt/lib -L/c/mingw730/prerequisites/i686-zlib-static/lib -L/c/mingw730/prerequisites/i686-w64-mingw32-static/lib -Wl,--large-address-aware' Thread model: posix gcc version 7.3.0 (i686-posix-dwarf-rev0, Built by MinGW-W64 project)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi,
I think, I found the problem. My application also uses the log4cplus library with the namespace log4splus. This library also a namespace detail (log4cplus::detail). If my application cpp file contains the using namespace log4cplus line then there is an ambiguity between the log4cplus detail namespace and the tinyutf8 detail.
I fixed this in my application by removing the using namespace log4cplus line.

I will rename the namespace detail to something more distinct 😃

That's great to hear!

Fixed in 5d2d1a162eacdd5fb7e217f8ba974cc9ccd7b03d


Question: in app review android message required

Hello, thanks for this great library !
i tested it on internal test android, but the message is required to review the app.
In your description you said that the message should be optional.
Is there any modification i need to do ?
Regards

Ok i push my update on production and the message is now "optional" 👯

Ok i push my update on production and the message is now "optional" 👯

Thank you for info


Navigation controller is jumping unexpectedly

I have integrated TLYShyNavBar with UITableView in my project. After a couple weeks I found that there is one very basic bug. Navigation controller is keep on jumping unexpectedly for a fix number of cell. Most of the time if TableView height is almost equal to the ViewController.
Just run the demo project and change in TLYTableViewController.m file
numberOfSectionsInTableView   and numberOfRowsInSection
numberOfSectionsInTableView  = 1
numberOfRowsInSection = 13 or 14 (for 12 and 15 it's working fine)
- (NSInteger)numberOfSectionsInTableView:(UITableView *)tableView
{
    return 1;
}

- (NSInteger)tableView:(UITableView *)tableView numberOfRowsInSection:(NSInteger)section
{
    return 13;
}

Very strange, I will try looking into it as soon as I find the time.

Thanks :)

@ikousik give this a shot https://github.com/telly/TLYShyNavBar/pull/123

@szweier have tried but issue is not fixed.It's jumps with section 1 and 13 rows.

Which view are you picking from the demo?

@ikousik also, what simulator are you using, what OS.

I just ran on 5 and 6 and I don't see jumping for 13

Looks like the issue is that when the frame changes it thinks it can fit the cells which then jumps back down.  Not sure how to fix this one at the moment.

Yea sorry about that it looks like this fixes the alignment issue on other devices rather than specifying a frame but it doesn't address the issue you are seeing.
Sent from my iPhone

On Feb 23, 2016, at 1:58 PM, 200 Ok<EMAIL_ADDRESS>wrote:
@szweier have tried but issue is not fixed.It's jumps with section 1 and 13 rows.
—
Reply to this email directly or view it on GitHub.

@mazyod my PR fixed one part of this issue but not the entire problem. It looks like there's a deeper issue with adjusting the frame resulting in the jumping.

@Mazyod I have uploaded one video in youtube please look into this.Video.
Xcode version - Version 7.2.1 (7C1002)
Issue is coming If Section is 1 and no of row is 11 for iPhone 4s, 13 for iPhone 5 and 15 for iPhone 6

Yea this seems to be happening when the table view frame becomes large enough to fit the cells again. In my opinion it's an edge case but would still be interesting to find a solution for. Granted I'm new to this code base so I'm not sure where to start to find this one just yet.

@szweier  any update ?

@Mazyod issue is not fixed. why did u close the issue?


rsz: avoid resizing registers

Beginning of the work for #5577.

Running Secure-CI.

QoR study showed that different PDKs may have different behaviors when it comes to area efficiency for FF resizing. This will be revisited when rewriting the core sizer.


Fix edit location form commit, edit obs image upload

In the edit observation form:
The issue was the image voting interface, which is now made of post_buttons that each create a mini form. (Rails does not want you to write to the db via GET, and voting originally did that. We do that still in a few other places.) Its presence induces a browser to automatically close out the enclosing form tag, and open a new one around the button.
So, any form embedding thumbnails, for now, will have to do without image votes in the form context.  I feel that is actually preferable, because it’s not a context where people should be trying to vote on images.  (Maybe someone is editing their own obs, and wants to "vote" on their own image, but those people will have to wait for another template, like the very next one, show.)
In the edit location form:
Despite locations not yet being CRUDified on master, Rails somehow figured out this was an edit form and added its automatic method: :put special sauce to the form. This explicitly sets method: :post.

Coverage: 92.721%. Remained the same when pulling 42840a3c112015a73cf899b5220b822135765941 on nimmo-jan-10-bugfixes into c7fbc36ad0eecb88a50fe69580639ec3a3c79671 on master.

The form refactor was a part of the 2-hour debugging process, wherein i forgot everything i wrote in the thumbnail helper. Keeping the refactor though! Trying to scan nested templates is awful.

I can't see the "real" changes amid all of the (very helpful!) closing if comments.  And the extra partials seem to be a good idea.  If it works, it works, it's fine with me!

sorry for the wild goose chase... 😅 that's cause there are no real changes!
After I eliminated every possible other option, turned out to just be the thumbnail votes.

I agree with @pellaea. And the changes work for me, so I'm going to deploy this.
Re erb files. Like Jason, I'm beginning to hate them in general. They are long, full of cryptic formatting stuff and complicated logic. There must be a better way. Does Trailblazer address this?

Alan reported a new issue in create obs, with undefined location. It doesn't create the obs. I'm heading out for a bit and can debug later, but can either of you check the issue? Should write a test to cover this too. Re: TB, it does seem to have a separate layer to put view logic, yes. Believe all layers are separate gems, so it's opt-in. On Jan 10, 2023, at 4:26 PM, Joseph D. Cohen @.***> wrote:
I agree with @pellaea. And the changes work for me, so I'm going to deploy this.
Re erb files. Like Jason, I'm beginning to hate them in general. They are long, full of cryptic formatting stuff and complicated logic. There must be a better way. Does Trailblazer address this?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: @.***>

Nimmo:
Thanks for putting out the image and location "freez" fires.
I'll look into the issue that Alan reported
On Tue, Jan 10, 2023 at 4:47 PM andrew nimmo @.***>
wrote:

Alan reported a new issue in create obs, with undefined location. It
doesn't create the obs. I'm heading out for a bit and can debug later, but
can either of you check the issue? Should write a test to cover this
too. Re: TB, it does seem to have a separate layer to put view logic, yes.
Believe all layers are separate gems, so it's opt-in. On Jan 10, 2023, at
4:26 PM, Joseph D. Cohen @.***> wrote:
I agree with @pellaea. And the changes work for me, so I'm going to deploy
this.
Re erb files. Like Jason, I'm beginning to hate them in general. They are
long, full of cryptic formatting stuff and complicated logic. There must be
a better way. Does Trailblazer address this?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because you modified the open/close state.Message ID:
@.***>
—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1276#issuecomment-1378088589,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAALDFDM3YNHIFYJ76GS5N3WRX7ILANCNFSM6AAAAAATXFFVT4
.
You are receiving this because your review was requested.Message ID:
@.***>


"section" tool doesn't seem to see data below y==0

I have some data in the negative portions of the cartesian plane, which is legal in GDS/OAS. While I can see these data on the 3D view, the section tool seems to only look for data in Y>=0 though X<0 data does seem to show up. Note, this is Y axis as viewed in Klayout or other top-down 2D GDS/OAS tool.

I see odd behavior on the lower left of the example GLTF too:

and when I move slightly to the right, it all disappears, even the substrate:

I've been debugging this a LOT over the past few days. It turns out that if I apply the clipping planes (i.e. what was previously just .near and .far) to the main camera, effectively sectioning the 3D view, and then rotate the camera to view the geometry from a side angle, I can see the shapes are effectively "hollow".

a little further into the chip:

even more angle to the view:

to the extreme of viewing this particular shape normal to the clipping plane, where it essentially disappears due to the "walls" of the shape having 0 thickness, and the shapes being hollow surfaces with no "filling".
Asking chatGPT what could be done, it suggested a composer, or custom shaders. I tried the composer first, but it didn't produce anything obviously useful. Attempting to use the shaders has been quite difficult, as just getting a comparable rendering as the reference_mesh.material provides has so far been elusive, though I'm getting closer. Enabling the shader to also "fill in" the clipped plane is something I've been working on, but have been trying to focus on getting renders that are at least matching the existing results before trying to develop the novel aspects.


PSet tweaking changes

(Text to be updated properly)
Fixes #10181
Status
In development
Description
Reimplement pset tweaking to not depend on CMSSW framework
Is it backward compatible (if not, which system it affects?)
NO
External dependencies / deployment changes
https://github.com/cms-sw/cmssw-wm-tools

Test this please

Test this please

test this please

test this please

@khurtado Kenyi, can you please fix the conflicts in this PR?

please test this

test this please

Thanks for rebasing and squashing those commits, @khurtado . Now I'm actually able to patch 1.4.7.patch2 with this PR. Applying it to a fresh installation in vocms0262 and running further tests.

@khurtado we haven't yet run all the test workflows, but I see at least 3 of them with 100% failure rate in vocms0262 (alancc7-cloud2). Could you please have a look at them?

Yes, I will take a look. It seems an issue with the PYTHONPATH environment
when calling the preScript.
On Fri, Apr 23, 2021 at 7:47 AM Alan Malta Rodrigues <
@.***> wrote:

@khurtado https://github.com/khurtado we haven't yet run all the test
workflows, but I see at least 3 of them with 100% failure rate in vocms0262
(alancc7-cloud2). Could you please have a look at them?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dmwm/WMCore/pull/10179#issuecomment-825603047, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACNKLITGJX6KX3RVH4SZ5DLTKFM5FANCNFSM4U23JA3A
.

@amaltaro I just pushed a fix to the stepChain issue. Could you resubmit the workflows that were failing (except for the scl5 workflow, of course)

@amaltaro I fixed fixed 3 issues in total:

StepChain workflows issue
skipPileupEvents bug
runLimits bug

These are affecting:

All StepChain workflows
amaltaro_TaskChain_PUMCRecyc_Agent147PSet_Val_210422_153202_9942
amaltaro_TaskChain_LumiMask_multiRun_Agent147PSet_Val_210422_153149_640

When you get the chance, could you please patch the agent with these changes and resubmit these workflows?

@khurtado Kenyi, thanks for providing these fixes. I have just applied your commits 3 to 5 to vocms0262, and injected all the Integration workflows. You can search for workflows matching _Agent147PSet_Val_210426_.
I'm going to clone and assign one of those 4 python3 workflows as well, just to be on the safe side.

Awesome! Thank you.

@khurtado Kenyi, tests are all looking good now. Can I ask you to squash the last 3 commits into the first one please?
BTW, there are 2 or 3 workflows which didn't manage to run a single job since yesterday. You might want to have a look if there is anything we can do to get them into running in condor. Thanks

@amaltaro Done! W.r.t the workflows, one seems to have FNAL as the only site whitelisted and we know that takes like 3 days. But the other one is assigned to both CERN and FNAL, so I don't know why it's not running at CERN at this point.

@khurtado Thanks Kenyi. Could you please squash commits 3 and 4 into the 1st one? I will likely cherry-pick these for the branch 1.4.7_wmagent to run a final validation before pushing it in for RelVal (likely on Monday/Tuesday).
@mapellidario just to make your re-review easier, here is the current 4th commit where Kenyi made the python3 changes you requested: https://github.com/dmwm/WMCore/pull/10179/commits/3f2ba535d5d76cdbf95a1cea1b321b33c8531711
AFAIK, even if he squashes those, you can still access this commit if you have the correct url, thus pasted above ;)

@amaltaro Done.

@khurtado Kenyi, I had a quick look at the replay logs and I believe we are passing a unicode string for the repack jobs. Here is the error message/traceback extracted from the logs provided by Jhonatan:
2021-05-02 08:37:57,869:INFO:Scram:    Invoking command: cmssw_wm_create_process.py --output_pkl /srv/job/WMTaskSpace/cmsRun1/PSet.pkl --funcname repack --funcargs /srv/job/WMTaskSpace/cmsRun1/process_funcArgs.json
2021-05-02 08:38:47,324:INFO:Scram:Subprocess stdout was:
Failed to create a repack process.
Traceback (most recent call last):
  File "/cvmfs/cms.cern.ch/share/overrides/bin/cmssw_wm_create_process.py", line 102, in <module>
    main()
  File "/cvmfs/cms.cern.ch/share/overrides/bin/cmssw_wm_create_process.py", line 93, in main
    process=create_process(args, func_args)
  File "/cvmfs/cms.cern.ch/share/overrides/bin/cmssw_wm_create_process.py", line 40, in create_process
    raise ex
ValueError: write_L1Accept_RAW.root is not a valid <class 'FWCore.ParameterSet.Types.string'>

While we keep working on this master branch PR, I'm going to cherry-pick these commits to 1.4.7_wmagent such that we can start working on the relval agent validation. I think the potential changes to fix it for T0 will be isolated enough, so we can just move on with our plan discussed a couple of weeks ago. Please let me know what your thoughts are.

Given how critical and deep these changes are in our system, I'd suggest to define a more meaningful commit message as well.

@khurtado Kenyi, I was mistaken during our chat. This PR still needs to be updated with a better PR/commit message. Can you please update it before your day is over? Thanks

@amaltaro I changed the title and tried to detail the changes more. Let me know if I'm missing anything

Thanks @khurtado . Could you please reword the commit message as well? Thanks

@amaltaro Ah, I forgot that. I just reworded the commit message.

As discussed with @amaltaro on Monday, we are pushing this PR now that the commit message and description has been updated.

Thank you very much, Kenyi!


SAM-2505 Calculated question: Correct answer is graded as wrong when the...

... answer uses comma as decimal separator instead of using the point

Hi @raulsv, how does this modification handle a USA student entering "1,234.56" as the answer?

Thanks Sam, grading will not work if the student enters "1,234.56". So we need to find a fix for that so that it allows at the same time to have "1,234.56"(USA locale) and "1.234,56" (Spain locale). Any suggestions?

I think the only way to do this is normalize the format when the user introduces the answer. In that moment you know the user's locale and you could change the decimal/thousands separator, if is different from USA.
During the correction process you are not able to know if "3,145" is 3145 or 3.145 because you don't know the locale used to introduce the answer.
So, no matter what the user's locale was, in the database you will have the number with "." as decimal separator and "," as thousands separator.
Change previous database data is not mandatory, the answers of the previous tests will not change, and the new answers will work. If you want to re-grade some specific test you must change database value assuming some locale for the response.

Please, open again the PR when you have a good solution for this.


Highlight multi-word grammars.

Can you highlight multiword grammars? For example:
my word = "hi";

Shouldn't the both words be highlighted?

Fixed in commit 4b779628b300f71d56558030bf698d9fe190b695 and release 1.0.4.


The OKD4 web console run for 3 days and crash

I just followed the guide to install OKD 4.5 cluster by Graig Robinson.  the OKD web console ran for 3 day and crashed.
the
all I can see is the message below:
{
"kind":  "Status",
"apiVersion": "v1",
"metadata": {
},
"status": "Failure",
"message":  "forbidden: User "system:anonymous" cannot get path "/"",
"reason":  "Forbidden",
"details":  {
}
"code":  403
}

Describe the bug

Version

How reproducible

Log bundle

Please attach log bundle


Improve the testcoverage of DragAndDropStatisticComponent

Test Coverage
main/webapp/app/exercises/quiz/manage/statistics/drag-and-drop-question-statistic: 0% -> 88.89%

Hi, we don't know what to test for this PR, can someone please add testing steps?

Hi, we don't know what to test for this PR, can someone please add testing steps?

I fear there is not much to test here. The important part is checking that the test run correctly on the build agents and the coverage report is correct (up to over 80%). One thing that could be done is running the test locally, I can click a run button next to the tests to do that/test them locally:

Resolved the issues.


feat: include only some files

Adds a function include exported that you can call after importing which will limit the files that are considered for changes, and require them to be present before reloading. Implementing it this way makes it backward  compatible and non-intrusive.
I found this helpful in my extension where I was manually copying manifest.json after webpack build completed - it didn't exist right away when other webpack entry files ae written, which causes an extension reload error.

I partially figured this out anyway by enabling the copyUnmodified: true option with the CopyPlugin and using webpack --watch for development, but it still fails on a fresh start of webpack --watch, so I think this addition might be useful anyway.
const { include } = require("crx-hotreload");
include(["manifest.json"]);

Fixes #7, except does not support exclude.

@AndersDJohnson Thanks for the PR!
In particular, it is not clear whether that line is necessary, as it seems redundant to me and should be removed:
if (includes.length && !includes.every(i => files.some(f => i === f.name))) return;

If there are no files is in includes, then won't that expression simply return an empty string:
return files
                .filter(f => includes.length ? includes.includes(f.name) : true)
                .map (f => f.name + f.lastModifiedDate).join ()

Also, I am not sure that it is right to do that thing:
 if (!timestamp || !lastTimestamp || (lastTimestamp === timestamp)) {

I suggest to change it to:
 if ((lastTimestamp === undefined) || (lastTimestamp === timestamp)) {

Because the purpose of the previous !lastTimestamp expr was to check if we are executing it the very first time (when the lastTimestamp is undefined). But that non-strict check is not good if we are now returning empty strings from timestampForFilesInDirectory, which is a valid value for a timestamp (if there are no files).
I haven't checked anything I just write, so pardon for my silliness in advance :)

@xpl I'm not sure if it's written correctly or minimally, but I think the !includes.every is ensuring that all the included files exist in the current list of files before generating a truthy timestamp that will cause a reload, since we should require all the included files to exist before reloading - whereas the .filter just removes any files that were not explicitly included from the timestamp (so as not to cause reloads when changing or being created or deleted), but if multiple files were included, the .filter may still allow through some that do currently exist, so that we may still get a truthy timestamp, while leaving out others included that aren't guaranteed to exist at this stage in the timeout loop.

@AndersDJohnson Thanks for the explanation. I somehow missed your initial premise that you need to ensure that all those files should actually exist before reloading, and thought that you simply want to implement a filtering for the file list needs to be watched, so I was confused of that additional checks' meaning.
Then I need to understand better the actual use case of that. Is it only for manifest.json or there could be issues with other files? Because if it's only because of manifest.json then maybe it is simpler to just hardcode the check for that file — as it seems that an extension cannot be loaded without that file anyway?

@xpl Hard-coding for manifest.json could solve some use cases, and I'd be fine if we at least hard-coded that. But anyone else with a multi-step build process (e.g., generating different sizes of logos with a separate tool than the one that builds your JS) may experience similar issues where the extension reloads before they want it to do so.

@AndersDJohnson

anyone else with a multi-step build process (e.g., generating different sizes of logos with a separate tool than the one that builds your JS) may experience similar issues where the extension reloads before they want it to do so.

But then they would need to enumerate all those generated files explicity in includes, which could be painful? Because if there are multiple generated files, then they might get changed not simultaneously, and then the extension might get reloaded too early anyway?
That would work if a build tool first erases all files and then re-emits them — then your includes would ensure that the extension gets reloaded only after all the files are back. But what if a build tool just overwrites the files inplace sequentially? Then the reloading might occur before the build completes.
Do you have any information on how that is usually executed by various build tools?

Yes for this to work for those use cases, I was assuming the files would be erased first, such as with the CleanWebpackPlugin.
I wonder if there is another way?

@AndersDJohnson

I wonder if there is another way?

We could implement some debouncing logic (like in _.debounce from lodash), postponing the reloading for 0.5-1s when a change detected — until files stop changing. That won't help if your build tool is painfully slow (changing files with a larger pauses inbetween changes), but maybe will help in most cases.
The downside is that it would complicate the implementation and will also hurt the UX, as the reaction time of the reloading trigger would be slower, you would need to wait an additional second every time...

I created a simple version for myself that only uses a local exclude list (in hot-reload.js itself). Seems to work okay!
const ignoreList = [
  'popup.js',
  'popup-controller.js',
  'popup.html',
  'popup.css',
  'other',
];

// get the list of all files in the extension directory (recursively)
const filesInDirectory = dir => new Promise(resolve => dir.createReader().readEntries(entries => Promise.all(entries.filter(e => (e.name[0] !== '.' && !ignoreList.includes(e.name[0]))).map(e => (e.isDirectory
  ? filesInDirectory(e)
  : new Promise(res => e.file(res)))))
  .then((files) => {
    const myFiles = files.filter(f => !ignoreList.includes(f.name));
    return [].concat(...myFiles);
  })
  .then(resolve)));


Upgrade acorn in dependencies

I was hoping to use async/await now that it's fully supported by Chrome (without browser flags), but browserify was giving me a syntax error. @pluma helped point me to acorn and the various dependencies that depend on it. I've submitted pull requests to upgrade the acorn version used by all the node-browserify dependencies I could find.

substack/astw#10
substack/browser-unpack#15
substack/node-detective#67
substack/node-syntax-error#18

npm test passes in all repos. Let me know if I missed one and I'm happy to submit another PR.

Note that ecmaVersion default to 7(2016) in acorn and that some packages like detective gives it's own default 6(2015) instead of acorns. You need 8(2017) for async/await.

Can we get this merged?

Everything is up to date. On a clean install of browserify you should be able to use async/await.

Verified! Thanks :)


Prepare for Release 0.9.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
29 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.09%) to 74.393%

Files with Coverage Reduction
New Missed Lines
%

foundationdb/src/directory/mod.rs
2
93.39%

foundationdb/src/directory/directory_partition.rs
9
82.26%

foundationdb-bindingtester/src/main.rs
18
87.25%

Totals

Change from base Build<PHONE_NUMBER>:
-0.09%

Covered Lines:
4349

Relevant Lines:
5846

💛  - Coveralls


self consumed messsage not sent to test queue after upgrading to v3.1.5 (only 1 subscriber)

Describe the bug

Cloud contracts on provider side for messages
testing according to this page https://cloud.spring.io/spring-cloud-contract/reference/html/project-features.html#features-messaging-integrations
@AutoConfigureMessageVerifier used in base classes
upgraded from v3.0.2 to v.3.1.5 (same behaviour with 3.1.4 as well)
the message is also self consumed by the producer (to scale via messaging middleware)

Generated test will fail due to message != null assertion fails.
When removing the self listening to that message, it works like a charm.
Sample

setup producing of a message with spring cloud stream (functional binding instead of annotations)
write cloud contract producer test for it
configure your application to also listen to this (write a simple echo listener and bind it with a Consumer)
re-run your cloud contract test (this should fail now)

Ps: the message is consumed by another app as well, hence not a cloud contract for the producing app itself (which would not make sense)

Can you upload a sample so that we can check it out?

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Invalid OIDC back-channel logout token

Description:
When using OIDC back-channel logout the Identity Server sends a logout token that lacks the required property events (which according to the specification must contain the member http://schemas.openid.net/event/backchannel-logout). Instead it sends a property with the name event (notice the missing s) with no value.
The documentation  documents the correct behavior so I assume this is a regression of some sorts.
A typical logout token from Identity Server 5.9.0 looks like this:
eyJ4NXQiOiJaalJtWVRNd05USmpPV1U1TW1Jek1qZ3pOREkzWTJJeU1tSXlZMkV6TWpkaFpqVmlNamMwWmciLCJraWQiOiJaalJtWVRNd05USmpPV1U1TW1Jek1qZ3pOREkzWTJJeU1tSXlZMkV6TWpkaFpqVmlNamMwWmdfUlMyNTYiLCJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJqZW5zYiIsImF1ZCI6IkRIS3NRd2Exdlhwa1V4WDk3NXN0bU9KdV92NGEiLCJpc3MiOiJodHRwczpcL1wvbG9jYWxob3N0Ojk0NDNcL29hdXRoMlwvdG9rZW4iLCJldmVudCI6e30sImV4cCI6MTU4MTk2MDEyNywiaWF0IjoxNTgxOTYwMDA3LCJqdGkiOiI2Y2ZmNzYyNC1mNDE1LTRlNzAtYjRiZC0yYWU0YjI2N2M1ODMiLCJzaWQiOiJhMWM1OTEzNi1iN2YwLTRjODgtOTZiYS1hMzkzYzA5YjkzZTAifQ.fUd_GV63llpPlN-rW_WSJMqCTCOiLFr0mzrEcGiKSAEIL_J03dMVIrsQcmGKb9wmTHzN1K91njh-3qXUO6cBig-nE8loc25zBbPKdOTzStYZXFM0xicnr79xcNLL2c7hOm3fZovVqDHnWcV2wyKLkGTkcJh7fSMERz7lSSl2ziqNLy804dhivgj5TnwFMLtWJnzwG8zqrWiV6TkDRaDmrxkAUZHv_baX_W7OIovz-VruokHQ-CHLl0t1HvwlmlBLqs3srw5gXsG_ucndeSdh2vgCjwJnt76jYhGiprArJMLjeK9foOKS_CCFt_JaSZA-FyyaDzK9JoRqZou1qtqAMw
...which parsed gives the following payload:
{ 	"sub": "jensb", 	"aud": "DHKsQwa1vXpkUxX975stmOJu_v4a", 	"iss": "https://localhost:9443/oauth2/token", 	"event": {}, 	"exp":<PHONE_NUMBER>, 	"iat":<PHONE_NUMBER>, 	"jti": "6cff7624-f415-4e70-b4bd-2ae4b267c583", 	"sid": "a1c59136-b7f0-4c88-96ba-a393c09b93e0" }
Suggested Labels:
Type/Bug
Component/OIDC
Affected Product Version:
5.9.0
Steps to reproduce:

Register an OIDC client that supports back-channel logout
Log into the client using OIDC towards the Identity Server
Perform a logout from the Identity Server
Observe the logout token being posted to the OIDC client

Related Issues:
https://github.com/wso2/product-is/issues/4590

Hi @jborgland,
Thanks for reporting the issue. We could locally reproduce this behavior. We will analyze the root cause of this [1].
[1]https://github.com/wso2-extensions/identity-inbound-auth-oauth/blob/master/components/org.wso2.carbon.identity.oidc.session/src/main/java/org/wso2/carbon/identity/oidc/session/backchannellogout/DefaultLogoutTokenBuilder.java#L126

@ThaminduR will be looking into this


Encrypt token data (as well as signing it)

Previously we used JWT tokens as part of an authentication mechanism to
create or manage subscriptions. Only GOV.UK with the shared secret could
decode a token, thus confirming the origin of the data within. However,
only the signature of the token is protected by the shared secret; the
rest of the payload can be decoded to plaintext without.
This replaces the use of JWT with Rails' MessageEncryptor, which signs
and encrypts the payload, thus protecting all of it from exposure in
logs and analytics. Since the exact characters in the token vary with
the same payload, the testing approach now involves decoding the token
in order to verify its content.
Since the token is Base64 encoded, we need to escape the token string,
to avoid the '+', '=' and '/' characters, which are reserved as part of
URLs but can be present in the initial token.
https://github.com/rails/rails/blob/b9ca94caea2ca6a6cc09abaffaad67b447134079/activesupport/lib/active_support/message_encryptor.rb#L179
https://en.wikipedia.org/wiki/Base64

I've tested this working with email-alert-frontend locally 🆗


Compilation failing on Mac

Dear Dr. Conroy,
I installed fsps and tried running the makefile according to the instructions in doc/install.  I got the following error:
emolter% make
gfortran -O -cpp -o compsp.o -c compsp.f90
/var/folders/n5/1jbgx2wd1bb0jklpmpgj8qz00000gp/T//ccTPwlZr.s:167:suffix or operands invalid for `movq'
(the final line, the one with the error, repeated itself 13 times)
My gfortran is up-to-date with version 6.1.0.  The line I added to my .tcshrc is the following:
setenv SPS_HOME /Users/emolter/Python/fsps
What can I do to get the makefile to work?
Thanks!
Ned

Also FYI I'm running OS X 10.11.6, if that helps at all.

Hi Ned
I’ve never tried compiling with such a recent version of gfortran - I know it works with 4.9.2 and similar versions.  I’d recommend first trying to compile with gfortran v4.9.2 to rule any other possible issues out.
cheers,
Charlie

On Aug 23, 2016, at 11:01 PM, emolter<EMAIL_ADDRESS>wrote:
Dear Dr. Conroy,
I installed fsps and tried running the makefile according to the instructions in doc/install https://github.com/cconroy20/fsps/blob/master/doc/INSTALL. I got the following error:
emolter% make
gfortran -O -cpp -o compsp.o -c compsp.f90
/var/folders/n5/1jbgx2wd1bb0jklpmpgj8qz00000gp/T//ccTPwlZr.s:167:suffix or operands invalid for `movq'
(the final line, the one with the error, repeated itself 13 times)
My gfortran is up-to-date with version 6.1.0. The line I added to my .tcshrc is the following:
setenv SPS_HOME /Users/emolter/Python/fsps
What can I do to get the makefile to work?
Thanks!
Ned
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/cconroy20/fsps/issues/13, or mute the thread https://github.com/notifications/unsubscribe-auth/AHEQeoeg3YZHdMDrhFF51xJFUk7RnUhtks5qi7PsgaJpZM4Jrlxr.

Compilation worked with version 4.9.2, but not with 4.9.3 or later.  Thanks for the help!

Just to add another data point, I can successfully compile with gfortran 5.3.0 on OSX 10.10.5


error: could not find a torrent with the criteria

Hi, I followed the tutorial and setup Daemon Mode by running cross-seed on Docker.
But when a torrent finished, the log print error like this :

qbittorrent version: v4.4.2
docker image version:latest
system: DSM 6.2.3-25423
How can I fix this?
thx for helping!

I have much better results searching for infoHash instead of name

do you use Subfolder content layout?

I have much better results searching for infoHash instead of name

In tutorial, 'infoHash' only for Transmission. Can it work on qBittorrent?
Should I write something like :
curl -XPOST http://localhost:2468/api/webhook --data-urlencode "infoHash =%I"
or
curl -XPOST http://localhost:2468/api/webhook --data-urlencode "infoHash =%J"
?
There are two params in qb for infoHash：%I for infoHash v1, %J for infoHash v2.

do you use Subfolder content layout?

Yes! I need Subfolder. What should I do?

It'll work in qbit, use infohas v1


update contributors file

Motivation:
Now, shortly before 2.0 is a good time to update the contributors list.
Modifications:
Ran the contributor generation script (ASCII'd my name)
Result:
All contributors get their proper credit.

Why ASCII your name when we just got efficient UTF-8 strings?

Why ASCII your name when we just got efficient UTF-8 strings?

stuff breaks, such as git's .mailmap :(

Doesn't that imply you have to ASCII me as well?

@helje5 so far we didn't .mailmap coalesce your name yet :). I have used both spellings in various places so want to coalesce them. You have been more consistent


Unified assessment model

Having separate models for each kind of assessment is no good.
Let's build a unified model.
Pairing with @marimuraki!

:heart: thank you @alexsoble for pairing with me & showing me more about tests, specs, etc. It was fun! :blush:

@alexsoble: Here are the assessments from X2. Starred :star: are the assessments we should pull in the assessment model.

ACCESS :star:
WIDA-ACCESS :star: (same as ACCESS, simply named differently in X2 for earlier years)
MELA-O :star: (replaced by ACCESS)
MEPA :star: (replaced by ACCESS)
DIBELS :star:
MCAS :star:
MAP :star: (replaced by STAR)
STAR (currently pulling in from STAR export)
CTBS
GRADE
IDEA
IPT
Pre-IPT
SABE
SATI
SATII
W-APT

@marimuraki — Makes sense! Until we write a whitelist for X2AssessmentImporter it is going to import all of them.


New exception to support DV not connected

To support https://github.com/microsoft/Power-Fx-Dataverse/issues/455.

✅ No public API change.


When I request data during initialization, changing state will cause routing animation to jam

problem
The data may be large, and updating the state at this time will cause the route jump animation to be blocked before it is completed. How to get data after routing animation
code
class _Next extends State<Next> {
  List<Widget> ad = List<Widget>();

  Future<String> future ;

  Future<String> fas() async {
    HttpClient httpClient = new HttpClient();
    HttpClientRequest request = await httpClient.getUrl(Uri.parse("http://www.baidu.com"));
    HttpClientResponse response = await request.close();
    return response.transform(utf8.decoder).join();
  }

  @override
  void didChangeDependencies() {
    future = fas();
    // TODO: implement didChangeDependencies
    super.didChangeDependencies();
  }

  @override
  Widget build(BuildContext context) {
    print("build");
    // TODO: implement build
    return Scaffold(
      appBar: AppBar(
        title: Text("test"),
      ),
      body:ListView(
        children: <Widget>[
          FutureBuilder<String>(
            future: future,
            builder: (context, AsyncSnapshot<String> snap){
              if(snap.connectionState == ConnectionState.waiting){
                return Text("loading");
              }else if( snap.connectionState == ConnectionState.done){
                return Text(snap.data);
              }else{
                return Text("loading");
              }
            },
          )
        ],
      ),
    );
  }
}

How do I do it, thank you！

Questions like these are better suited for Q&A sites like StackOverflow or on one of the flutter community sites at https://flutter.dev/community


Configurable correlation id

Make logging the correlation id optional.
Context
We add a unique request-id to the MDC context for each incoming request. This allows us to see all log statements resulting from a call.
If interesting, we also add a hash of the authorization and our own trace id.
Possible Implementation
Boolean configuration value
Your Environment
Kubernetes / Stackdriver - single log file.

What exactly is your intent? Sounds a lot like https://github.com/zalando/tracer to me.

Basically Logbook uses 'correlation' to connect a request to a response log statement. We a making log statements inbetween the request and response (on the same server, in the same log output bucket) and so now add 'our own correlation' to the root of the JSON log statement.
So in other words I'd like the 'correlation' Logbook is adding to not be a child in the request/response logging JSON tree, but rather added to the MDC so that it is present in the root of the logged JSON tree and thus present on all log statements between Logbook request and response filters.

The correlation feature in logbook is purely to connect request and response. The primary use case is described in Logbook + Scalyr.
What you describe is almost to the nail what Tracer offers. Those are two different aspects, hence why we split them up into different projects.


ClientModel Prototype: Updates to paging and collection APIs

API change check
APIView has identified API level changes in this PR and created following API reviews.
System.ClientModel

Closing in favor of https://github.com/Azure/azure-sdk-for-net/pull/44825


Add node 21 to CI

https://nodejs.org/en/blog/announcements/v21-release-announce

@SleeplessByte Yes. I think we should keep the LTS (18) and latest (21) versions in CI. I guess many users installing nodejs first time might install the latest version.

The latest version when uneven often just doesn't work for various reasons. I don't think we will be able to solve the issues that they run into.
Can we mark the 21 one as "allowed to fail"?
I do think we should add 20!


Add support for git-crypt

Resolves #67
This PR adds support for git-crypt, to better align with the official git resource.
I've added a git_crypt_key source configuration param, that - when provided - will cause the repo to be unlocked using git-crypt during the get step.
Apart from the unit tests, I would like to include e2e tests but I didn't find an obvious way to do it, since the repo used by the tests is archived. However, I've tested this in a personal pipeline at https://concourse.our.buildo.io/teams/buildo/pipelines/gitcrypt
Notice how build 3 (which lacks the git_crypt_key parameter) prints the encrypted content of the file, while build 6 (which has the git_crypt_key parameter set) prints the decrypted content.
I've tried to adhere to the project's style as much as possible, but this is the first Go code I've ever written that goes beyond an hello world so I'll appreciate stylistic comments ^^

Have you had a chance to test this at work now @gabro (dev tag of the image has this PR in it)?


Neo4j adapter for fortune

Neo4j as a data store can open up a number of options for us in terms of analysing our data. This could be as a primary data store, or as a secondary store synced from a different adapter, e.g MongoDB.
As a first pass we should prototype an adapter to insert into and read from a neo4j instance.
Should we use an npm es package? Which one? Or the raw HTTP interface?
Is there a bulk insert API?
How should we do updates?

I think the most powerful way of interacting with Neo4J is using the Cypher query language http://neo4j.com/docs/2.0/cypher-refcard/?mkt_tok=3RkMMJWWfF9wsRogu6%2FAZKXonjHpfsX94%2B0uWKG%2FlMI%2F0ER3fOvrPUfGjI4ESMZlI%2BSLDwEYGJlv6SgFTbfGMadv1LgNXRQ%3D
There are a number of Node.js modules available http://neo4j.com/developer/javascript/ .
The most usable, I have found to be is https://github.com/philippkueng/node-neo4j
An update is slightly complex in Neo4J and basically can be achieved the same way as an insert. The MERGE keyword (explained here http://graphaware.com/neo4j/2014/07/31/cypher-merge-explained.html) is the function I have used in the past, basically it checks to see if the node exists, if not it inserts or updates it. Without using the MERGE it can be tricky to ensure that nodes and their relationships are unique (which is not always a requirement in graph databases) .

I have started the technical specification , feel free to comment
https://docs.google.com/document/d/1BgC1oD0gv9FqYl7qhL5C54Eh4USiCt3K4jxc-PKRnRM/edit?usp=sharing

Fork for this task https://github.com/avrono/fortune.git - ignore first spec - will create a generic adapter for Neo4J

updated draft spec
https://docs.google.com/a/neuralm.com/document/d/1LODmlDk3Ca_NFbiHneMExl07XIOVqac3Mee5mk5oxRM/edit?usp=sharing

can possibly use the Rest API directly http://neo4j.com/docs/stable/rest-api.html


Value not being set if mask prop not provided

I ran into this issue after creating a generic input field for a project using redux form, the field can either have a mask or not.

@andrewgierens This should no longer be happening in v3. Please check it out and if the issue is still happening, feel free to open a new PR


DELETED events ignored on subscription

In my project, DELETED events are not showing up in my custom endpoint (passed via graphql-binding, but they are firing on the prisma backend.
For reference, here's my resolver:
export const user = {
  subscribe: (parent, args, ctx: Context, info) => {
    return ctx.db.subscription.user(args, info)
  },
}

And the subscription:
subscription UserChange {
  change: user {
    mutation
    node {
      id
      name
      #...
    }
  }
}

Using the same subscription directly on Prisma works as expected.

Made a very simple repo, and it didn't have this problem. I'm going to close this and look into my more complex stack to see if the problem is somewhere in there. I'll reopen if this ends up being related to graphql-binding.

Thanks @frankdugan3.
Some parameters you can try to play with:

running the same subscription from the Playground
running the same subscription using https://gist.github.com/marktani/5df524523693c88be425bfb623ca8b8a
running the same subscription with/without GraphQL Variables
running the subscription without any filter


Remove coberturaReport task reference from CONTRIBUTING.md

Remove reference to gradle task coberturaReport, which does not
exist.
BugzID: 43882
reviewer @alfinkel
reviewer @mikerhodes

+1

And there's no trace of it in the gradle files any longer?

Not that I could find

Okay, +1.


Set up MongoidHistory for Pregnancy object and associated embedded docs

One of the things we're interested in is tying particular changes to particular users. To do that, we should set up MongoidHistory so that we can see what users were making what changes.
https://github.com/aq1018/mongoid-history#usage
It looks like it requires some additional setup to link actions to a given user -- control-f 'adding userstamp on history trackers' for more info.

Underway via @charleshuang80 and @Kevin-Wei

https://github.com/colinxfleming/dcaf_case_management/pull/165 we did it on patient though @colinxfleming

Doing it on patient is right on. Thanks a ton!
On Tue, Mar 15, 2016, 8:08 PM Kevin Wei<EMAIL_ADDRESS>wrote:

#165 https://github.com/colinxfleming/dcaf_case_management/pull/165 we
did it on patient though @colinxfleming https://github.com/colinxfleming
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/colinxfleming/dcaf_case_management/issues/149#issuecomment-197074533

Spun handling this for embedded documents into its own issue; closing.


@type/mime has to be published for v3 otherwise types are wrong when you use express types... :(

Express is installing @type/mime for some reason. Then I cannot use this package because I use version 3 and types from version 1.
I cannot install the newest @type/mime because is version 2, so also incorrect types.
The reason this happens is because the @types/mime is hoisted to the root of the node_modules because my root project doesn't need any @type/mime.
=> Found "<EMAIL_ADDRESS>info Reasons this module exists
   - "@types#express#@types#serve-static" depends on it
   - Hoisted from "@types#express#@types#serve-static#@types#mime"

Only solution I can see is to publish a v3 so I can force v1 from express to not be in the root node_modules.
Or maybe publish mime-v3? Is a crazy problem...

For now I have to downgrade to v2 so I can force install types at v2. So they are in sync. Not great :(

Can you provide a recipe for reproducing this problem?  Not really sure what issue you're referring to here.

I think @stevemarksd means using mime in typescript. The latest version of @types/mime is v2, but latest version of mime is v3, they don't match, so there will be many errors when developing typscript project.

Cc: @sandersn @david-fong @peterblazejewicz (the last 3 people who touched @types/mime)
Can one of you comment on what the appropriate action is here?
Would it make sense to add one of you as a collaborator to this project so you could maintain a types definition file here rather than in the DefinitelyTyped project?  I'm happy to do that, but I've been reluctant to "own" responsibility for maintaining the types file here until I have the time to do a full TS port (which is not high on my list of priorities).

Big picture: this is a types-only problem. @types/express depends on @types/serve-static which depends on @types/mime. There are no source packages involved. The required action is an update to @types/serve-static and @types/mime on Definitely Typed.
The immediate problem is that @types/mime is behind at 2.0, but mime is at 3. So @types/mime needs to update.
Except that the actual problem is that @types/serve-static is behind at 1.13, but serve-static is at 1.15. And<EMAIL_ADDRESS>(indirectly) depends on<EMAIL_ADDRESS>so both @types/serve-static and @types/mime are behind their source packages.
@stevemarksd if you want to have your types match your source packages -- and you should, because mime looks to have changed its API significantly between 1 and 3 -- you need to stay with<EMAIL_ADDRESS>If you want to use<EMAIL_ADDRESS>you need to try to update DT's types for serve-static and mime.
@broofa I recommend keeping types on Definitely Typed unless your package is written in Typescript or strictly checked JSDoc. You can ship your own types separately, but it's much more error-prone, as well as harder to test.
Mime's source is small and already half-jsdocced, so I'd recommend // @ts-check instead of a full TS port anyway. Then you could generate the types from from the .js later if you wanted.

I was wrong, the types haven't changed significantly from mime 2 to 3. I opened https://github.com/DefinitelyTyped/DefinitelyTyped/pull/61509 to update the types.

Closing.  mime@4 (published as mime@beta currently) has TS types built in.


Make physics debug respect shape outline setting inside editor

Make physics debug respect shape outline setting inside editor instead of always returning true no matter the actual setting.
I noticed that Godot already has a ProjectSetting to control if the polyline for shape outlines should be drawn, just that it did not react to the setting. This is a point of performance discussion with the TileMap debug here https://github.com/godotengine/godot/pull/90106.
As mentioned in dev chat I do not understand why this was forced to be always true inside the Editor, maybe someone else knows why. That setting "debug/shapes/collision/draw_2d_outlines" is enabled by default so nothing changes for users that did not turn it off deliberately.
If a user goes in the ProjectSettings to disable the shape outlines in the debug settings the expectation is likely ... to not have shape outlines drawn ... instead of only no outlines at runtime with debug enabled on only some shapes.

As mentioned in dev chat I do not understand why this was forced to be always true inside the Editor, maybe someone else knows why.

According to the original discussion in https://github.com/godotengine/godot/pull/46416 the outlines were considered less of a performance issue in the editor because they typically don't get redrawn on every frame.


Main

Hi Marc,
Thanks for getting in touch. However, this is a false binary. SAP is committed to support; the level of support depends the license agreement that each customer or user has signed. In the case of free products, SAP has always made it clear that support is Community support. This is not new; it is simply a clarification of the existing agreement.
However, since I enjoy both working with the product and interacting with Community members, and since several issues have cropped up more than once, I will provide support where I can.
Best wishes,
Julie Plummer.
ABAP PM

:-). That's very kind, thank you, Marc. I have to say, it's very much a team effort!
You have a great Christmas season too! 🎄
Best wishes.


Updating 10 packages after google-cloud-core==0.27.0

dns
error_reporting
language
logging
monitoring
resource_manager
runtimeconfig
speech
translate
vision

Also updating bounds on these in google-cloud uber-package.
Release notes will be forthcoming as comments on this PR.


server: add terminate_handler to log on uncaught exception

Adds a terminate_handler to log a backtrace if possible.
This does do something I don't particularly like: the third-party dependency "backward" is not squashed at compile time with --define signal_trace=disabled since this isn't hidden behind that flag and uses that library.  That library also does memory allocation and exceptions in an unknown/crashing state.   It's used already, so I thought it best to keep using it.
Risk Level: Low
Testing: Added (then removed) an uncaught exception, saw this show up in the trace.
Docs Changes: N/A
Release Notes: N/A
Fixes #1378

@gumpt thanks for working on this. We definitely need this to be guarded by --define signal_trace=disabled as in production environments some folks are not going to want this behavior (including Lyft). Can we guard this in similar ways as to the existing backtrace functionality?

That should do it, and CI seems happy.

@dnoe can you review? @gumpt it would be nice to have a death test for this. I would take a look at similar tests that @dnoe wrote already for the backtrace code.

Sorry, this dropped off my radar and got buried in GH emails when I was on vacation last week. Will review by this afternoon.

Think that addresses all of the new feedback.  Thanks for not letting this die on the vine!


Fixed for support PHP7.2

$rule['tag'] must be array if we want to count

Coverage decreased (-0.6%) to 94.018% when pulling e807c6fec6dc9961cc8adc14fafaf42e24885ac6 on kuba1999:patch-1 into 96634727ec973ee0a57c5060139bfd747f079b67 on paquettg:master.

This has been merged into a dev branch without any further activity. If you want to use PHP 7.2 or later, read https://github.com/paquettg/php-html-parser/pull/126#issuecomment-356625323.

This has been fixed in 2.0.0


feat(category)!: create breadcrumbs and add createTree method

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/develop/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?
[x] Yes
[ ] No

DaffCategoryFactory now requires DaffCategoryBreadcrumbFactory as a constructor argument. It is recommended to DI the factory
Other information

check children product IDs, add test for it


enlistment of all platforms

Signed-off-by: Nikhil<EMAIL_ADDRESS>Description
Updated the platform list for installing Meshery.
Before

After Updating
Added

AKS
Minikube
KinD
Helm Chart
Google Kubernetes Engine
AWS Elastic Kubernetes Service

This PR fixes #470
Notes for Reviewers
I used https://layer5.io/service-mesh-management/meshery/getting-started for reference.

Signed commits

[x] Yes, I signed my commits.

Nice @NikhilSharma03 I'll ping other reviewers so that they'll check

Thank you @alphaX86 . Yeah Sure.

Hello! Very nice, @NikhilSharma03 😄

Thank you @leecalcote 😄.

@NikhilSharma03 will you kindly have a look at the formatting in mobile view?

@leecalcote Sorry actually I was waiting for approval that the list is correct so I can start working on the responsiveness part. But got busy with getNighthawk and forgot 😅.
After Changes

Note For Reviewer
Let me know if there are any other changes we can make. Thank you.

@NikhilSharma03 this is very nice now! 😁
@leecalcote out of context, does Meshery support k3s cluster for now?

@NikhilSharma03 this is very nice now! 😁
@leecalcote out of context, does Meshery support k3s cluster for now?

Regarding k3s, @nunix is our resident authority.

The demos I've done in the past, were done in majority on k3d.
Now, being on Windows, this means there's a setup beforehand to be done, but K3s should not have any issues running Meshery.
Let's have an hands-on session in the coming weeks, so we check together what roadblocks are there (if any)

I was taught to use k3s using a VM via Vagrant so I hope that won't be problem in setup....

@leecalcote Can you please review? Thank you.

@NikhilSharma03, not a huge issue, but heads-up (scrollbars):

Will make sure to fix that in the next PR.


Disable Intro screen

I saw (:lt.objs.intro/show-intro) when looking in user.behaviors, I want to hide the intro, I tried to put it here:
:- {
     :app [(:lt.objs.intro/show-intro)]

     :editor []}

This did not disable the welcome screen. Any thoughts?

For anyone looking to disable the intro screen in later versions of Light Table, you simply need to add the following snippet to your user.behaviors file:
[:app :-lt.objs.intro/show-intro]

Works, although i'd suggest at some point they rename that to:
lt.objs.intro/hide-intro

@MarcelHekkert we can just create an alias for that, right?
(def -lt.objs.intro/show-intro lt.objs.intro/hide-intro)


Subsystem tagger

Go over all the CVE yamls and tag each vulnerability according to its subsystem. Normalize the subsystem to be all lower-case so we can combine as best we can.

Done now!


[hotfix] Fix typos for supporting distributed training

This PR fixes the distributed training problem mentioned in https://github.com/hpcaitech/ColossalAI/issues/2407.

I see, but is it normal? As gloo backend is usually for distributed CPU training. @feifeibear
The default backend is nccl, which makes claim "dist.get_backend() != 'gloo'" True, and group_cpu is always used in such a case. To be more specific, gpc.init_global_dist and gpc.init_parallel_groups() lead to connection issue. However, with above changes, distributed GPU training works fine.

@feifeibear do we still need this CPU process group? Many users encounter environment issues when init this group.

Hi @haofanwang . In our design, get_group() returns the default group (which can be nccl, gloo, etc). Meanwhile, as the default group usually is used by gpu communication, we need get_cpu_group() to return a gloo group for cpu communication. In your case, just specify the default backend and group as gloo, and then get_cpu_group() will redirect you to the default group. However, you are duplicating the gloo group. The change is sadly not how it is supposed to work.

@kurisusnowdeng @haofanwang Can we close this PR? It looks like the problem has been solved.


ng test running in watch mode by default

ng test command runs test in watch mode. Watch mode should only enabled if user provides -w flag

I tripped over this in our CI environment too. Added --watch false to get passed it for now. Not a fan of defaulting boolean flags to true.

I changed autoWatch to false in karma.conf.js as workaround...

Yes, autoWatch is true by default in karma. If that's not what you want, you should change that value and ng test will us it.
Cheers!

+1 watch by default is not desirable


Fix node db cache and e2e workflow improvements

5cccf82387fbac4e3cdae831d51a667dd086471f
Attempt to fix node db caching

53566437298ceb0126464ede4b8b27f4276e1617
More granular steps in e2e workflows

087f7a504da50887f88370745a112b5a18e73cf5
Use Linux workflow cache if other not available

0d752a0938cf3136b6d0c9d1eed2d2a4e53a2a13
Docker workflow adjustments

e2b2ef59a14496381336851825a81ac11aa7e944
update README

Comments
Improvements made here and in #3027 bring significant improvements in speed and reliability of e2e tests. Tests on MacOS and Linux used to take 2-3h overall and on Windows even up to 6h (which often led to exceeding GH actions timeout). This was mainly due to incorrect use of node db caching which caused a lot of time spend of syncing node db against testnet. Improved execution times are as follows:

Linux
MacOS
Windows
Docker

1h
1h 6m
1h 31m
1h

Due to node db caching, which is happening properly now on every run, node db syncing time is cut from few hours to few minutes :tada:. Majority of the remaining test suite time is still spend on syncing fixture wallets, but it is good test on it's own so there seems to be no need for further improvements. Execution times seem to be satisfactory for nightly e2e tests and also in the need for an ad-hoc e2e run.
Issue Number
ADP-1196

bors r+


Adjustment of Minimum Required Ruby Version for Versions 12.5.x

Firstly, I want to extend my congratulations to the entire team for the incredible work that has been accomplished with this gem.
I'd like to ask about the possibility of publishing a new version, specifically 12.5.x, wherein the minimum required Ruby version is reverted back to >= 2.5.0.
Upon reviewing the Changelog, I noticed that this change was implemented in version 12.5.0, citing alignment with rails/webpacker. However, the latest published version of webpacker (5.4.4) maintains a minimum required Ruby version of >= 2.4.0.
Currently, I have systems still running on Ruby 2.5.0. While upgrading to the latest version is indeed on our roadmap, it hasn't yet been expedited. Reverting the Ruby requirement, perhaps in version 12.5.3, would facilitate our transition from version 12.4.0 and enable us to leverage the performance enhancements of React 18.
If necessary, I am willing to create the pull request for this adjustment.

@gregoryfm would your company be open to signing up for Sponsorship for React on Rails Pro (includes a lot more), and we could keep issuing official releases for you? If you think so, please book a time to meet.

Hey @justin808 thanks for your reply. While we acknowledge the value and effort you guys put into the React on Rails/Cypress projects. At the moment, we're in a period of temporary efforts in cost management, and as such, we're unable to commit to sponsorships. We'll definitely reassess this situation in the future.
Do you reckon would it be possible to push a 12.5.3 version with the Ruby minimum required back to 2.5.0?

Hey @justin808, do you think it's possible to publish this update?

Why not just use your fork as a dependency in the project?

If fork is too difficult, we can consider reopening.


a corner case of truncated response

Conditions to reproduce the bug:

a postgres function  returns a table;
the function returns only one row;
the table has a column named exactly the same as the function.

Steps to reproduce:

create a function:

create function public.test() returns table(test text, value int) language sql as $$
values ('hello', 1);
$$;

expected result:

[{"test": "hello", "value": 1}]

the truncated response  of (curl localhost:3000/rpc/test -XPOST -d''):

"hello"

Tested against both postgrest-0.4 (centos 6) and postgrest-0.4.2 (centos 7).
Thanks!

Interesting, thanks for reporting. That's behavior is how functions used to work more generally, so this is probably some old logic bleeding through on the corner case.

that will be still "hello"

This was already fixed in #895 refactor commit, I've added a test case with the reported test() returns table(test text.. function.


property "height" freezes the browser

Hi, Thanks alot for the plugin! very helpufl!
I'm having a problem when i add the "height" property to the watched properties, chrome and FireFox just get stuck while loading the page, any idea why?
here is my code:
    var elem2watch = $j('.myClass');

    elem2watch.watch({
        properties: "display,height",

        callback: function(data, i) {
            var propChanged = data.props[i];
            var newValue = data.vals[i];

            var elem2watch = this;
            var elem2watch$j = $j(this);

            // do what you need based on changes
            // or do your own checks
            // console.log('elem2watch :',elem2watch);
            // console.log('data :',data);
            // console.log('i :',i);
            console.log('changed css');

            if( ($j(elem2watch).css('display') === "block") )
            {
              // some more code that works if "height" is not included to the watched prop
            }
        }
    });

Sorry I didn't attend to this.
I gave this try in 1.20.0. I change the sample to be resizable, and resizing the height.
I added the resizable:
  el.draggable().closable().resizable();

and then also added height to the monitored properties:
        // Hook up CSS and Class watch operation
        el.watch({
            properties: "top,left,height,opacity,display,attr_class",
            callback: watchShadow
        });

I didn't see any issues when resizing the left box. The right box resizes right along with the left and mirroring. I don't see any slow downs or delay.
Keep in mind that you'll want to be quick about whatever you are doing in response to those events because there could be quite a lot of them firing in very quick order and that can have adverse affects on performance. One trick might be to use setTimeout() for the longer operations or use a debounce() routine to slow down the event firing.


Respects XML encoding

Indentation support other XML encodings than UTF-8. Encoding taken from xml-declaration but defaults to utf-8 if declaration is missing.

Thanks for this


Just Question

Hi,
What's your add value to ByteTrack ?
Thank you in advance

We added an adversarial attack method TraSw. Please refer to README.


NuGet version is old

Great control, but the NuGet version is 2.4.5 which seems to be over a year older than the current version (2.5.4).  Any chance of a NuGet update soon?

As above, only older... 2.4.5 was published to Nuget on July 08 2015 - would it be possible to get an update to the current version - or add Nuget to automatic publishing for new versions alongside npm?


LuCI openwrt-19.07: "Override MTU" Field Auto-Populates with Saved Login Username "root"

On an EA6350v3 running OpenWrt 19.07-SNAPSHOT r10554-26c0bec13b / LuCI openwrt-19.07 branch (git-19.263.64892-befe994), in the LuCI Interfaces>Common Configuration>Advanced Settings, the "Override MTU" field is populating with the login username "root" saved in my Firefox browser (69.0.1 running on Manjaro linux). Clearing my saved login in Firefox clears the problem - its just an annoyance, but one not present in 18.06.4 on my EdgeRouter-X or EA8500.

I have this too in Use gateway metric

Probably a firefox bug, but this happened to me only in luci :(


feat: improve dispatcher performance

backport from https://github.com/aio-libs/aiohttp/pull/7829

This library doesn't fix the miss case, we need aiohttp 3.10 for that
before
% python3 url_dispatcher.py
resolve_time_first_url: 0.001995124970562756
resolve_time_last_url: 2.294156291987747
resolve_time_miss: 2.204503499902785

after
% python3 url_dispatcher.py
resolve_time_first_url: 0.0018852080102078617
resolve_time_last_url: 0.0018728750001173466
resolve_time_miss: 2.205604300701324


net/wireguard: hotfix for latest master

wrong templating when using multiple endpoints
moved disable routes to server since it's a global configuration, not client related.

yes please :)

Merged, thanks!


rtl

hi hello
There is a small problem when homeassistant is configured in the Hebrew language
It does not display videos or images
If I add to the card
the following code
card_mod:
style: |
ha-card {
direction: initial;
}
It displays the video and images
But there is still a frigate-card-submenu problem edge in the menu
thanks

The issues are not super clear. Lets make sure I understand.

It does not display videos or images

So without that styling, you see nothing? OK, I can test this.

But there is still a frigate-card-submenu problem edge in the menu

Can you include a screenshot of what you mean?

Hi, I've been trying to fix this all day with cardmod, thank you very much, it works great and wonderful.


feat: add github.com/twpayne/chezmoi

It looks like the CI failure is unrelated to this PR:
   • reading https://raw.githubusercontent.com/goreleaser/goreleaser/master/.goreleaser.yml
   ⨯ treewalker failed         error=unable to parse: yaml: unmarshal errors:
  line 64: field archives not found in type config.Project
make: *** [build] Error 1
The command "make ci" exited with 2.

yes, this is broken :/

Do you have a rough idea of how much knowledge is needed to fix it? Is it a reasonable external contribution, or better done by someone very familiar with the two projects?

I rather not fix this right now... I'll be working on finishing adding multiple archives to goreleaser, which will break this a ton... so maybe its easier to just fix/redo it later.
btw cc/ @client9 do you still think in maintaining this?

OK, thanks for the update. I'm happy to wait on this so you can fix it properly. Goreleaser is awesome - thanks!

I just updated it because more things were broken :/

⨯ treewalker failed         error=unable to parse: failed to set defaults: found 2 builds with the ID 'chezmoi', please fix your config

can you fix this though?
seems like you have 2 build with the same id, if you run it against the latest goreleaser it will fail...

check https://github.com/goreleaser/godownloader/commit/c5edc589fff7b0cacf818a46d6cdd2ac8b4dbaaf @twpayne

bah.. was just going to dig in...
will take a look anyways..
On Tue, Apr 30, 2019 at 11:54 AM Carlos Alexandro Becker <
<EMAIL_ADDRESS>wrote:

Merged #111 https://github.com/goreleaser/godownloader/pull/111 into
master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/goreleaser/godownloader/pull/111#event-2310419162,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABVAW4YYAO67KVQUTW2LTLPTCIWJANCNFSM4HJDIGHQ
.

seems like you have 2 build with the same id, if you run it against the latest goreleaser it will fail...

Yes, https://github.com/twpayne/chezmoi has two builds (one CGO, one without CGO) to work around Go's inconsistent behavior. User bug reports are https://github.com/twpayne/chezmoi/issues/125 and https://github.com/twpayne/chezmoi/issues/65.
It sounds like I need to update chezmoi to use the latest goreleaser. Please don't spend time investigating before then.


Python: Intermediate callback in subscribers, to map None msg in ca…

…llbacks to ByteArray of length 0 b"", see #1103
I'd rather solve this from cpp instead of Python here, but maybe someone has an idea.
@rex-schilasky @FlorianReimold @hannemn

That actually looks stupid, but I think it is the proper solution. What else did you have in mind?

Hm, probably we could. But giving some random pointer to non-owned memory feels extremely unsafe, even if we pass a length of 0.

Hello, I am the one that post #1103 (with an other github account).
This seems to do the trick to create an empty bytearray:
PyByteArray_FromStringAndSize(NULL, 0);

Ah thanks for the heads up, I think we can try this one. We've used PyBuildValue everywhere, but I don't know why we wouldn't be able to use PyByteArray_FromStringAndSize instead...


set_cpu_nms

To understand the set NMS operation, I run the sub main func in utils/set_nms_utils , changing keep = py_cpu_nms(boxes,nms_thresh) as keep = set_cpu_nms(boxes,nms_thresh) , the ERROR encounters as follow:
"set_nms_utils.py", line 29, in set_cpu_nms
numbers = dets[:, 5]
IndexError: index 5 is out of bounds for axis 1 with size 5
Please Help solve this \ ( * ^ * ) /

I slove this by simple way: set more boxes for detection.


Interactive window does not scroll down automatically when commands are sent from the editor

Version: 1.65.1 (system setup)
Commit: 8908a9ca0f221f36507231afb39d2d8d1e182702
Date: 2022-03-08T02:06:27.846Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043
When sending commands from the editor to the interactive window for instance with right click  / Run Selection/Line in Interactive Window, this latter does not always scroll down to show the most recent output, especially when there's an error. As we can see in the second screen shot we need to move the focus (i.e. click) in the interactive window and then manually pull the scrolling bars down to see what is at the the bottom. This move back and forth from the editor to the IW defeats the purpose of notebook like IDE.

Thanks for the issue. It's already been fixed in our insiders build.
An older version of this was logged here: https://github.com/microsoft/vscode-jupyter/issues/9259

There's also a workaround, set this to true and it will always scroll:
"jupyter.alwaysScrollOnNewCell": true

Till the insiders build is released I'll be using the work around. Thanks for the tip!

There's also a workaround, set this to true and it will always scroll:
"jupyter.alwaysScrollOnNewCell": true

Could you tell me where I have to type this command please?

Ok thanks for this. I have turned this setting on but it hasn't really helped. The terminal will scroll down somewhat, but not to the bottom of the window so I can see the output without manually scrolling.  This will be a bit of a pain to sue now. Do you know when the insiders build will be released please?

Output is actually a separate issue: #9305
That one is not going to be fixed anytime soon because we need changes in VS code core to get it to work.


"myArray should now equal [["John", 23], ["cat", 2], ["dog", 3]]." is incorrect

myArray is initialised as an array with one array, but the test to pass shows it must be an array of arrays, which is beyond the power of push().

You can push an array onto an array with push. In the future please list what challenge you are working on when filing a bug. Thanks and happy coding!


Memory system

Hi! How do you implement a memory storage system? I mean how variables are accessed from different parts of the program

Hi! Thanks for asking! 'tis like this: BFFuck divides the tape into two parts: The registers (playfield) and the memory (where the variables are stored). BFFuck keeps a dictionary valdict, that maps variables to their position in the tape. The registers are used as temporary values for operating brainfuck algorithms.

Thanks for explanation!


⚠ Samsung has degraded performance

In 3728156, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2389 ms

Resolved: Samsung performance has improved in fdff8d3.


Codec

I have tried to look everywhere I can think of to find the CodecPriority attribute and the ExcludedCodec attribute as described in the documentation on this page, but I am not seeing this anywhere. To the extent that this attribute may exist at all, it seems it is not a mutable attribute.
Could this be addressed in the documentation? Our SBC provider is telling us to change the codec Teams is sending, but this mysterious "CodecPriority" attribute is not mentioned in any other place I can find on MicrosoftDocs.

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

ID: ad7d5051-1177-c5cf-bf28-8639d7b6fbd1
Version Independent ID: 2a9aa4e1-3767-cd46-50fe-f9dd8b0997be
Content: Connect your Session Border Controller (SBC) to Direct Routing - Microsoft Teams
Content Source: Teams/direct-routing-connect-the-sbc.md
Service: msteams
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


there is an error that [unrecognized import path "golang.org/x/crypto/pbkdf2"] when running go get to download the dependencies

you can make dir golang.org/x
you can git clone https://github.com/golang/crypto.git

@future-challenger Where should I create that directory?!

you can make dir golang.org/x
you can git clone https://github.com/golang/crypto.git

@future-challenger I've added cloned library to /usr/local/go/src/golang/x/HERE and /usr/local/go/src/HERE, but the error still exist!


The suggested az command returns region names in an invalid format for usage in the arm template

e.g. az command includes among its suggestions West US 2 which the arm template then rejects with an error message like
[{"code":"InvalidName","message":"Invalid ServerFarm name 'foobar-test-plan-West US 2'. ServerFarm name must not contain empty space."}]
... which makes sense to reject.

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

ID: 553649bf-0f84-4e95-40f5-70afbccbfdb7
Version Independent ID: 139ae9ae-7418-8fdb-adfe-77c2640b1bde
Content: Template resource location - Azure Resource Manager
Content Source: articles/azure-resource-manager/templates/resource-location.md
Service: azure-resource-manager
Sub-service: templates
GitHub Login: @mumian
Microsoft Alias: jgao

@DFalkner99
Thanks for your feedback! We will investigate and update as appropriate.


How to use latest version of JSQSystemSoundPlayer pod

I used pod JSQMessagesViewController and when i check pod out dated, i saw that
- JSQSystemSoundPlayer 2.0.1 -> 2.0.1 (latest version 4.4.0)
Thanks.

Hi @itman85 ! 😄
That's right, JSQMVC uses an older version of JSQSystemSoundPlayer — there's no functional differences between 2.0.1 and 4.4.0, just some renaming/refactoring of the public API.
JSQMVC 8.0 will fix this.


Operational solution is common field

Changes and Description
Backend

Operational Solution has a new field isCommonSolution

If this is listed as linked to the need in the possible_need_solution_link, it returns true, else false
-Postman queries updated
Unit test to assert Logic

FrontEnd
How to test this change

PR Author Review Checklist

[ ] Met the ticket's acceptance criteria, or will meet them in a subsequent PR.
[ ] Added or updated tests for backend resolvers or other functions as needed.
[ ] Added or updated client tests for new components, parent components, functions, or e2e tests as necessary.
[ ] Updated the Postman Collection if necessary.

PR Reviewer Guidelines

It's best to pull the branch locally and test it, rather than just looking at the code online!
Check that all code is adequately covered by tests - if it isn't feel free to suggest the addition of tests.
Always make comments, even if it's minor, or if you don't understand why something was done.

Most of these changes make sense, just adding some comments around the clarity of the code!
The only other thing I'd note, is that the naming of this is slightly confusing: Are we saying that anything that IsCommonSolution is one that's a solution for a possible operational need? If so, we might be able to work on the naming to clarify that a bit more, but I want to make sure my understanding is correct first!

@ClayBenson94 The 'Common' solution comes from here for reference. It refers to only the default set of 'common' solutions for that particular need. None can be user-added/removed. If adding an 'other' solution or a solution that has preset details, those would go in "Other" solutions.

Thanks @patrickseguraoddball  and @ClayBenson94, yes, I think some of the confusion here is that I named the field with how it is referenced on the front end form, but we don't use the same terminology in backend.
@patrickseguraoddball , I have to double check the behavior with the the treat_as_other solutions like contract. For needs that have a solution, I would expect it to show up  like this. It is checking to see if the solution type is linked as a possible solution for the need. I don't think it would make sense to change that field value in the backend return value, because it really is a common solution. Do you think it would make sense to key off other fields as well here? ( EG if is_other and is_common_solution and id is not null, put them in the other solution section?)


bump kube-prometheus-stack to 14.x for hivemq-operator chart

Motivation
Keep the dependencies in sync between swarm and operator chart
Probably we should bump the Chart version here - not sure if we use here minor or patch bumps - suggestions?

@cla-bot check


[Bug, REST]: no graph edges exist only on REST Proxy

It seems getinfo is sending back (via REST)
{"error":"no graph edges exist","code":2}

No error using gRPC.
Tried to restart... nothing fix it.

Is this a fresh lnd node? We don't read from the graph database at all for getinfo. Also can you fill in the rest of the issue template for issues? It helps a bunch of repetitive back and forth on our end w.r.t asking questions about the commit, etc.

So here is the strange thing: This error was sent by the REST proxy but NOT by gRPC. (lncli was working fine)
I can't really reproduce, but I noticed it happened when I started LND while my node was not full synched. Somehow lnd got stuck.
I workaround this problem now by using a tool which delay lnd start until my node is fully synched and started. (https://github.com/btcpayserver/lnd/blob/dockerfile2/docker-entrypoint.sh#L52)
I could not reproduce since then.
I think there was several issue:

Why would REST Proxy send the error, but not gRPC?
Why the sync of LND was stuck?

They are probably related.
Anyway for now, I can't reproduce easily, and found a workaround which seems to work until now.
Feel free to close this issue.

Somehow lnd got stuck.

Stuck as in? At times lnd can stop getting new blocks from bitcoind if the zmq notification queue fills up and we miss a block notification as a result. A combo of #1579 and #1439 will resolve this.

I don't have the logs in hands, but when you first start LND, there is a period where it sync and show progress with block heights, something like "Synched up to block 380000".
It turns out that it was blocked to a certain height around 400000. Restart did not worked, we unstucked it by deleting the data folder of LND.


Execute Step 1 of the transition from DID-based message types to HTTP ones per RFC 0348

Aries messaging is going to transition from using "did:sov:...;spec/" as the namespace prefix on message type strings to using "http://didcomm.org/". The transition process is documented here in a community transition RFC that allows frameworks to migrate to the new format independently.
Please review the process and implement only step 1 of the process:

Step 1: Agent builders MUST update all agent code bases and deployments to accept incoming message types in the old (did) and new (https) formats. During this step, agents MUST default to sending out messages in the old format.

Each agent builder SHOULD notify the community they have completed Step 1 by submitting a PR to update their entry in the implementations accordingly.

Note that no messages should come out of ACA-Py in the new format, only in the old format.

Don't forget this one, @nrempel ! :-)