case-insensitive import collision - Sirupsen vs sirupsen

What version of Go (go version) and dep (git describe --tags) are you using?
go version go1.8.3 linux/amd64
v0.3.0-89-gc0338b8

What dep command did you run?
docker run -it --rm  golang:1.8 bash
root@348d3fadc17b:/go#
root@348d3fadc17b:/go#
root@348d3fadc17b:/go# mkdir -p src/test/repo
root@348d3fadc17b:/go# cd src/test/repo
root@348d3fadc17b:/go/src/test/repo#
root@348d3fadc17b:/go/src/test/repo#
root@348d3fadc17b:/go/src/test/repo# cat > main.go <<EOF
package main

import _ "github.com/bradleyfalzon/dep-case-collision"
import _ "github.com/sirupsen/logrus"

func main() {}
EOF
root@348d3fadc17b:/go/src/test/repo# go get github.com/golang/dep/cmd/dep
root@348d3fadc17b:/go/src/test/repo# dep init
  Using master as constraint for direct dep github.com/bradleyfalzon/dep-case-collision
  Locking in master (5263ba3) for direct dep github.com/bradleyfalzon/dep-case-collision
  Locking in 1.0.2 (a3f95b5) for transitive dep github.com/Sirupsen/logrus
  Locking in master (c84c1ab) for transitive dep golang.org/x/sys
  Using ^1.0.2 as constraint for direct dep github.com/sirupsen/logrus
  Locking in 1.0.2 (a3f95b5) for direct dep github.com/sirupsen/logrus
root@348d3fadc17b:/go/src/test/repo# ls
Gopkg.lock  Gopkg.toml  main.go  vendor
root@348d3fadc17b:/go/src/test/repo# go run main.go
package main: case-insensitive import collision: "test/repo/vendor/github.com/Sirupsen/logrus" and "test/repo/vendor/github.com/sirupsen/logrus"

What did you expect to see?
I expected the program to run.
What did you see instead?
package main: case-insensitive import collision: "test/repo/vendor/github.com/Sirupsen/logrus" and "test/repo/vendor/github.com/sirupsen/logrus"

Context

At some stage github.com/Sirupsen/logrus renamed to github.com/sirupsen/logrus (they lowercased the first S in Sirupsen).
A whole series of project continue to import github.com/Sirupsen/logrus, in this case github.com/bradleyfalzon/dep-case-collision imports the old github.com/Sirupsen/logrus
Some new projects have switched to the newer name github.com/sirupsen/logrus, in this case it's our main package.

Is there anything dep can do about this?
I would like to note, go get can't handle this either:
root@348d3fadc17b:/go/src/test/repo# go get -v .
github.com/bradleyfalzon/dep-case-collision (download)
github.com/Sirupsen/logrus (download)
Fetching https://golang.org/x/crypto/ssh/terminal?go-get=1
Parsing meta tags from https://golang.org/x/crypto/ssh/terminal?go-get=1 (status code 200)
get "golang.org/x/crypto/ssh/terminal": found meta tag main.metaImport{Prefix:"golang.org/x/crypto", VCS:"git", RepoRoot:"https://go.googlesource.com/crypto"} at https://golang.org/x/crypto/ssh/terminal?go-get=1
get "golang.org/x/crypto/ssh/terminal": verifying non-authoritative meta tag
Fetching https://golang.org/x/crypto?go-get=1
Parsing meta tags from https://golang.org/x/crypto?go-get=1 (status code 200)
golang.org/x/crypto (download)
Fetching https://golang.org/x/sys/unix?go-get=1
Parsing meta tags from https://golang.org/x/sys/unix?go-get=1 (status code 200)
get "golang.org/x/sys/unix": found meta tag main.metaImport{Prefix:"golang.org/x/sys", VCS:"git", RepoRoot:"https://go.googlesource.com/sys"} at https://golang.org/x/sys/unix?go-get=1
get "golang.org/x/sys/unix": verifying non-authoritative meta tag
Fetching https://golang.org/x/sys?go-get=1
Parsing meta tags from https://golang.org/x/sys?go-get=1 (status code 200)
golang.org/x/sys (download)
github.com/sirupsen/logrus (download)
can't load package: package test/repo: case-insensitive import collision: "github.com/Sirupsen/logrus" and "github.com/sirupsen/logrus"

But fortunately there's a workaround by moving one of the copies to $GOPATH (or removing one from vendor and go getting it):
root@9e25dfa49b7a:/go/src/test/repo# go run main.go
package main: case-insensitive import collision: "test/repo/vendor/github.com/Sirupsen/logrus" and "test/repo/vendor/github.com/sirupsen/logrus"
root@9e25dfa49b7a:/go/src/test/repo# mv vendor/github.com/Sirupsen $GOPATH/src/github.com/
root@9e25dfa49b7a:/go/src/test/repo# go run main.go
root@9e25dfa49b7a:/go/src/test/repo# echo $?
0
root@9e25dfa49b7a:/go/src/test/repo#

I don't know what the solution is here, in part I'm posting it because the workaround is good enough for me and might help others, but I'd like to know what's dep's thoughts on this, and probably the go team too.

Thanks @sdboyer and sorry for the dupe! I had searched elsewhere for this issue, but not the place I was posting the issue! Sorry for the noise.


Users are missing in the Microsoft Teams Company Communicator app's send delivery report.

Please refer to old cases created for this. We need to clarify below details.
https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/1511
https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/1482
https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/1442
As you confirmed, regarding ConversationID field in user data table?
=> Conversation Id is the field gets updated from Teams side to store the conversation between the User and the bot, it may get updated when the user deletes the chat or other scenarios due to which the user record gets skipped when the sync happens when authors are trying to send out new messages.
i) We wanted to know, at what scenarios user record get skipped when sync happens due to which the message is not getting delivered to few users?
ii) Also you mentioned  user deletes the chat message, but in user application we didn't find delete chat message option.
iii) Last and most import query we would like to know that, the user's whom the messages did not getting delivered are same in every send delivery report or it's changing?

Hi @SachinWandale111
i) We wanted to know, at what scenarios user record get skipped when sync happens due to which the message is not getting delivered to few users?
When we attempt to send messages to a large audience, there may be issues with the Teams API, such as throttling or the call might fail due to any network related issues or user might block the chat or delete it there are other factors as well which we also unaware as it happens in the backend of Teams where we have limited visibility.
ii)Also you mentioned user deletes the chat message, but in user application we didn't find delete chat message option.
There user can delete the chat incoming from the user bot which is available and please find attached screenshot as reference

iii) Last and most import query we would like to know that, the user's whom the messages did not getting delivered are same in every send delivery report or it's changing?
This is unpredictable, and we don't have any metrics to assess it. It will depend on sync and Teams API

Hi @peddivyshnavi ,
Thanks for sharing details, we are checking on it and update you if we have any further queries.

Hi @peddivyshnavi
As you mentioned in above image,  user can delete the chat incoming from the user bot which is available, but we didn't see such option. Why?

We apologize for the delay in our response and will get back to you as soon as possible.

Hi @SachinWandale111
Could you please check within your tenant settings because this is available for everyone

We are closing this ticket due to no response. Feel free to open a new GitHub issue if you encounter any problems.


Plugin deleted from RuneLite?

Me and a lot of friends used this plugin daily. We've sadly noticed today that the plugin is gone from the plugin hub and our runelites. Will it be coming back or is it permanently gone?

Bump, I am also not showing it in the plugin hub

Have also noticed the same thing.

Yeah it got removed temporary because of the high memory usage (regarding the large json file to determine drop rate)
Didn't find the time yet to fix it, i'll look into it soon. My apologies for the inconvience!

Any update?

Love this plugin. It is way better than every other drop notification plugin by far. I wish it was still available.

Love this plugin. It is way better than every other drop notification plugin by far. I wish it was still available.

Will be, I'm working on it atm :)

Going to commit the new version now. So should be back up once RL accepts the PR.


Crashing issues

Hey,
Currently attempting to use Waterfall. Once a 1.7 client gets around users (a decent amount of them 30+) it'll kick them.
I have my config waterfall.yml to simply allow 1.7, 1.8 & 1.9.
No plugins are causing this as once I put the good ol' Bungee, it doesn't kick it. Once I switch WF on, it kicks me.
Thanks :)

Waterfall doesn't support 1.7 - so either you're running an old build (unsupported) or you're using Travertine (repost this issue in the correct repo).


Install docs need some attention in the readme

As was pointed out on a reddit thread, the install docs make a lot of assumptions about the knowledge of the user. Provide actual installation documentation in the readme.

I wrote up a little bit in my comment. I can format it further if you like. I'm a cli-comfortable but docker/git noob so probably the appropriate reading level.

Can’t be helpful without throwing some snark in, hey


Bluetooth: has: Add stubs for handling control point requests

This adds server stubs for handling the preset control point requests.
Signed-off-by: Mariusz Skamra<EMAIL_ADDRESS>

rebased


Added tests for the Button component

Hi Ryan, I wanted to get my feet wet with some tests for the Button component.

I added some more button tests and cleaned things up a bit.


 But it works fine on my job computer (W10).

Windows 11 is a pain, they mess with anything they like, like alt+spacebar
a well used shortcut in many 3d apps.
Now my graphics keep gittering due to some new transparency driver rubbish.
Stay on 10 until they clutch it from your cold dead hands
On Sat, 25 May 2024, 07:37 lombervid, @.***> wrote:

That has been happening to me for some time on my home computer (W11). But
it works fine on my job computer (W10).
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/213230#issuecomment-2130918807,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABTBZ42XYR2ARRXCVJWGCWDZEAWR5AVCNFSM6AAAAABID2UNQKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZQHEYTQOBQG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Could you please invoke the "Developer: Toggle Keyboard Shortcuts Troubleshooting" command from the command palette, reproduce the problem and then share the output. That should suffice to see whether the command is being invoked or not. Thanks!

This is what I get:
2024-06-01 13:42:20.930 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-06-01 13:42:20.931 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-06-01 13:42:20.931 [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
2024-06-01 13:42:20.931 [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
2024-06-01 13:42:20.931 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-06-01 13:42:21.480 [info] [KeybindingService]: + Ignoring single modifier alt due to it being pressed together with other keys.

Doing the same, here's my output:
2024-06-22 14:15:58.974 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-06-22 14:15:58.992 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-06-22 14:15:58.992 [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
2024-06-22 14:15:58.993 [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
2024-06-22 14:15:58.993 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-06-22 14:16:06.042 [info] [KeybindingService]: + Ignoring single modifier alt due to it being pressed together with other keys.
2024-06-22 14:16:06.375 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-06-22 14:16:06.375 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-06-22 14:16:06.375 [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
2024-06-22 14:16:06.376 [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
2024-06-22 14:16:06.376 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-06-22 14:16:06.840 [info] [KeybindingService]: + Ignoring single modifier alt due to it being pressed together with other keys.
2024-06-22 14:16:11.522 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-06-22 14:16:11.543 [info] [KeybindingService]: \ Keyboard event cannot be dispatched
2024-06-22 14:16:11.543 [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
2024-06-22 14:16:11.543 [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
2024-06-22 14:16:11.543 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-06-22 14:16:12.064 [info] [KeybindingService]: + Ignoring single modifier alt due to it being pressed together with other keys.

The commands that should be matched are:

workbench.action.compareEditor.previousChange
workbench.action.compareEditor.nextChange

Can you invoke the "Preferences: Open Keyboard Shortcuts" command from the command palette and search for these two commands. Are you seeing any keyboard shortcuts defined for them? This is what I have on my machine (macOS):

Here's what I've got.

Those default keybindings look correct. Comparing your logs with what I have on my machine, I am not seeing any log entry that states that the "F5" key was pressed. Would you be able to look at the troubleshooting logs again, and just press "F5" and see if that appears in the logs. Is there a chance you have some kind of modifier that you have to press on your keyboard so that the function keys are dispatched?

Gosh now I'm confused 😖
Yes I do have a modifier key, I'm using a Keychron K6 Pro. The Fn1 key is on the bottom row.
BUT. After I looked at the keyboard shortcut list, and then just now tried Alt+F5, it's started working. I'm Alt+F5ing away and it's doing what it should, and the keyboard shortcut logs are distinctly different, you can see it resolve alt+f5.
2024-06-26 13:22:53.235 [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: AltLeft, keyCode: 18, key: Alt
2024-06-26 13:22:53.235 [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: AltLeft, keyCode: 6 ('Alt')
2024-06-26 13:22:53.235 [info] [KeybindingService]: \ Keyboard event cannot be dispatched in keydown phase.
2024-06-26 13:22:53.248 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-06-26 13:22:53.248 [info] [KeybindingService]: | Resolving alt+F5
2024-06-26 13:22:53.248 [info] [KeybindingService]: \ From 2 keybinding entries, matched workbench.action.compareEditor.nextChange, when: textCompareEditorVisible, source: built-in.
2024-06-26 13:22:53.249 [info] [KeybindingService]: / Received  keydown event - modifiers: [alt], code: F5, keyCode: 116, key: F5
2024-06-26 13:22:53.249 [info] [KeybindingService]: | Converted keydown event - modifiers: [alt], code: F5, keyCode: 63 ('F5')
2024-06-26 13:22:53.249 [info] [KeybindingService]: | Resolving alt+F5
2024-06-26 13:22:53.249 [info] [KeybindingService]: \ From 2 keybinding entries, matched workbench.action.compareEditor.nextChange, when: textCompareEditorVisible, source: built-in.
2024-06-26 13:22:53.249 [info] [KeybindingService]: + Invoking command workbench.action.compareEditor.nextChange.
2024-06-26 13:22:53.539 [info] [KeybindingService]: + Ignoring single modifier alt due to it being pressed together with other keys.

Did the act of observing the keyboards shortcut list alter the outcome? This could be a Heisenbug.
So now I'm wondering about @lombervid setup.

These are my shortcuts:

And this is what I got with just F5:
2024-06-28 22:00:00.929 [info] [KeybindingService]: / Soft dispatching keyboard event
2024-06-28 22:00:00.929 [info] [KeybindingService]: | Resolving F5
2024-06-28 22:00:00.930 [info] [KeybindingService]: \ From 3 keybinding entries, matched workbench.action.debug.start, when: debuggersAvailable && debugState == 'inactive', source: built-in.
2024-06-28 22:00:00.930 [info] [KeybindingService]: / Received  keydown event - modifiers: [], code: F5, keyCode: 116, key: F5
2024-06-28 22:00:00.930 [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: F5, keyCode: 63 ('F5')
2024-06-28 22:00:00.930 [info] [KeybindingService]: | Resolving F5
2024-06-28 22:00:00.930 [info] [KeybindingService]: \ From 3 keybinding entries, matched workbench.action.debug.start, when: debuggersAvailable && debugState == 'inactive', source: built-in.
2024-06-28 22:00:00.930 [info] [KeybindingService]: + Invoking command workbench.action.debug.start.

Adding @ulugbekna to assist further. @ulugbekna do you mind taking a look at this one? Thanks!


Allsky failures after applying patch

Having had the same problem as others with installation failing on a freshly imaged RPi 4 due to dependency problems I followed the advice from @linuxkidd and applied this patch prior to install
cd ~/allsky
wget https://patch-diff.githubusercontent.com/raw/thomasjacquin/allsky/pull/596.diff
patch -p1 < 596.diff
This threw some errors as follows
pi@raspberrypi:~/allsky $ patch -p1 < 596.diff
patching file Makefile
Hunk #1 succeeded at 35 with fuzz 2 (offset 6 lines).
Hunk #2 FAILED at 56.
1 out of 2 hunks FAILED -- saving rejects to file Makefile.rej
patching file config_repo/Makefile
Reversed (or previously applied) patch detected!  Assume -R? [n]
Running ./install.sh goes OK now though but the log now shows this
ct  7 14:28:01 raspberrypi allsky.sh[790]:      ***** Starting AllSky *****
Oct  7 14:28:02 raspberrypi allsky.sh[790]: /home/pi/allsky/allsky.sh: line 14: /autocam.sh: Permission denied
Oct  7 14:28:02 raspberrypi allsky.sh[790]: /home/pi/allsky/allsky.sh: line 16: /home/pi/variables.sh: No such file or directory
Oct  7 14:28:02 raspberrypi allsky.sh[790]: /home/pi/allsky/allsky.sh: line 17: /config.sh: No such file or directory
Oct  7 14:28:02 raspberrypi allsky.sh[790]: mkdir: cannot create directory ‘’: No such file or directory
Oct  7 14:28:02 raspberrypi allsky.sh[790]: CAMERA:
Oct  7 14:28:02 raspberrypi allsky.sh[790]: /home/pi/allsky/allsky.sh: line 94: [: : integer expression expected
Oct  7 14:28:02 raspberrypi allsky.sh[790]: /home/pi/allsky/allsky.sh: line 99: /autocam.sh: Permission denied
Oct  7 14:28:02 raspberrypi allsky.sh[790]: /home/pi/allsky/allsky.sh: line 102: /filename.sh: No such file or directory
Oct  7 14:28:02 raspberrypi allsky.sh[790]: jq: error: Could not open file : No such file or directory
Oct  7 14:28:02 raspberrypi allsky.sh[790]: Starting allsky camera...
Oct  7 14:28:02 raspberrypi allsky.sh[790]: /home/pi/allsky/allsky.sh: line 154: /capture_args.txt: Permission denied
Oct  7 14:28:02 raspberrypi allsky.sh[790]: /home/pi/allsky/allsky.sh: line 162: /home/pi/: Is a directory
Oct  7 14:28:02 raspberrypi allsky.sh[790]: '' exited with RETCODE=126
Oct  7 14:28:07 raspberrypi allsky.sh[910]:      ***** Starting AllSky *****
Oct  7 14:28:07 raspberrypi allsky.sh[910]: /home/pi/allsky/allsky.sh: line 14: /autocam.sh: Permission denied
Oct  7 14:28:07 raspberrypi allsky.sh[910]: /home/pi/allsky/allsky.sh: line 16: /home/pi/variables.sh: No such file or directory
Oct  7 14:28:07 raspberrypi allsky.sh[910]: /home/pi/allsky/allsky.sh: line 17: /config.sh: No such file or directory
Oct  7 14:28:07 raspberrypi allsky.sh[910]: mkdir: cannot create directory ‘’: No such file or directory
Oct  7 14:28:07 raspberrypi allsky.sh[910]: CAMERA:
Oct  7 14:28:07 raspberrypi allsky.sh[910]: /home/pi/allsky/allsky.sh: line 94: [: : integer expression expected
Oct  7 14:28:07 raspberrypi allsky.sh[910]: /home/pi/allsky/allsky.sh: line 99: /autocam.sh: Permission denied
Oct  7 14:28:07 raspberrypi allsky.sh[910]: /home/pi/allsky/allsky.sh: line 102: /filename.sh: No such file or directory
Oct  7 14:28:07 raspberrypi allsky.sh[910]: jq: error: Could not open file : No such file or directory
Oct  7 14:28:07 raspberrypi allsky.sh[910]: Starting allsky camera...
Oct  7 14:28:07 raspberrypi allsky.sh[910]: /home/pi/allsky/allsky.sh: line 154: /capture_args.txt: Permission denied
Oct  7 14:28:07 raspberrypi allsky.sh[910]: /home/pi/allsky/allsky.sh: line 162: /home/pi/: Is a directory
Oct  7 14:28:07 raspberrypi allsky.sh[910]: '' exited with RETCODE=126

It's probably easier just to keep the issue here.  I'm trying to do a new install.  I did leave some additional comments in the closing of #590.

HI @KH6JAG
There are potentially two issues at play here:

A use before set variable issue in allsky.sh which has been merged.
If using an RPiHQ camera, a missing variable in the settings_RPiHQ.json.repo file ( in config_repo ).  The fix for this has been merged too now.

For item 1, you can git pull inside the allsky folder and it will apply the new code to your allsky.sh file.
For item 2, you can manually edit allsky/config/settings_RPiHQ.json and add the following line:
   "debuglevel": "1",

Add this anywhere in the mix, above the last parameter ( the last parameter does not have a comma ( , ) after it.  So, don't put it there ).
The manual edit is required because the install routines will not overwrite your existing config files.
Once that's done, try running ./allsky.sh again and report back on any other errors that may pop up.
Thanks!!

the RPi will shut itself down.

This is definitely not a feature or function of the allsky software.
I would suspect, it's shutting down for one of a few reasons:

Insufficient power from the PSU
Overheating
Something oddly configured in the GUI / OS ( like, it tries to sleep, but RPi doesn't support that, so it just dies )
Combination of a GUI and Timelapse generation exhausting all memory and causing it to hard lock up, and look like it's shutdown?

Just some theories at this point.  If you look at the journalctl logs from before the reboot, you may be able to see some more details.

We just submitted a fix for the gazillion errors.  It updated allsky.sh, so please grab the newest version.
@adymac101 if this fixes the problem with allsky.sh errors, please close the issue.
Thanks

Follow-up Results:
I did a git pull and install
The RPiHQ already had the “debuglevel” : “1”, edit.  I’m guessing that it had already been updated by the time I started the recommended actions.
When I started the program, the live image was not available.  I checked the config file and did the edit for “RPiHQ”
Rebooted still no image.  I changed to a different RPi4.  Used the same camera but different CSI cable
Now working correctly.
I switched back to the original RPi4 but this time using the new CSI cable.  I’m still investigating why the RPi was shutting down.  I will also re-check operation using the ASI120.
Thanks for all your efforts.  This camera setup will be part of a multi-school weather network that the students put together.  I was ready to go live with the program because I had been using the previous version without any difficulty.  When I tried to install the updated version, the fun began.
Please close the issue

That's great news, @KH6JAG !  Thanks for hanging in there with us as we worked through everything.
If there camera ends up having a public link, please come back and share it with us.


Sql interpolation improvements

The PR is created based on a fork I'm using atm. Please let me know if it needs to be splitted into separate PRs.
Changes:

Drop zio-config and zio-logging dependencies (as no longer needed with the latest version of ZIO2)
Interpolation of Sql values (for convenience to interpolate SQL segments like table/column names, but it might help with #98)
Use Debug level logging (I think zio-jdbc is too low-level library to use anything but LogLevel.Debug. On the other hand, it's useful to capture SQL, this use case leads to the idea in https://github.com/zio/zio/issues/7778)
Closing statements and resultsets
Type-safe SqlInterpolator (i.e. support custom types for PreparedStatement parameters), fixes #51
Support Option[A] to use .setNull for None values

Tech debt:

Builtin instances of Sql.Setter probably need testing against JDBC drivers
Need to review the case with JdbcEncoder[Option[A]] where A is a tuple

@domartynov Thank you!


Padding is added also to 8 bytes block

When using the padding keyword, in case of 8 bytes input data the payload to encrypt is doubled the length unless using only the data provided.
This is an edge case because in every other situation (input data less than 8 bytes or its multiple) the padding works fine and the output is calculated accordingly.

When using the padding keyword, in case of 8 bytes input data the payload to encrypt is doubled the length unless using only the data provided. This is an edge case because in every other situation (input data less than 8 bytes or its multiple) the padding works fine and the output is calculated accordingly.

This padding schema does require extra 8 bytes for encryption. Otherwise, there will be a problem to trail out the padding part at the end of the data from the ciphertext.


outputparser.NewStructured is restrictive & not robust enough

right now, outputparser.NewStructured  is based on an internal struct (https://github.com/tmc/langchaingo/blob/main/outputparser/structured.go#L36) that's restrictive to only strings and output values, but I  think it should be user-defined, a good example is from vector store here (https://github.com/tmc/langchaingo/blob/main/vectorstores/options.go#L30)
I can create a PR if this is the right way to go
Workaround
for now, I defined a custom prompt with the fields I need with a custom OutputParser  and fed the prompt directly to the chain.

Yeah I agree -- making this more flexible would be welcomed.


Investigate GitHub actions failures

I've been running the github actions again, but the latest problem confuses me.  The line it's executing is:
run: python fix-entries.py --convert-files --validate-sbml

The last message we get is from the final biomodels in the source code; 'Csikasz-Nagy2006.xml'.  And then it errors out, claiming the run was cancelled:
2022-02-16T05:05:54.8400010Z   warnings.warn(termcolor.colored('`{}` could not be converted to valid SBML file.'.format(filename)),
2022-02-16T05:06:02.8505083Z /opt/hostedtoolcache/Python/3.9.10/x64/lib/python3.9/site-packages/biomodels_qc/convert.py:128: FileCouldNotBeConvertedWarning: `/tmp/tmpzmfi3dns/Csikasz-Nagy2006.xml` could not be converted. Please check that the file is a valid SBML file.
2022-02-16T05:06:02.8506469Z   warnings.warn(termcolor.colored('`{}` could not be converted. Please check that the file is a valid SBML file.'.format(
2022-02-16T06:45:22.3627231Z ##[error]The operation was canceled.
2022-02-16T06:45:22.3763770Z Post job cleanup.
2022-02-16T06:45:22.6289345Z Post job cleanup.

It looks to me like it finished at 5:06 and then got stuck, and was killed at 6:45.  The official timeline for the run says that it took 6 hours 28 seconds total, which indicates to me that it hit some sort of timeout at six hours.  (The run started at 00:45, I guess in GMT.)
My only ideas at this point are to kill the parallelization code on the theory that this is what got confused at the end, and to turn off SBML validation to make it go slightly faster (and since the SBML validation seems to fail for unknown reasons--all the models are valid as far as I can tell despite getting the 'Please check that the file is a valid SBML file' for every single one).
Any other ideas of things to try or why the run might have hung are welcome!

The fix-ci.yml file now works! For the record, there was confusion between dividing the runs by 40 vs. running them in groups of 40.  In the end, I went with 26 groups of 40 each.
test-ci.yml also works, and reveals a variety of errors.  Fixing those, but this issue can now be closed.


Transcribe docker reference parsing and introduce dockerFile detector

Needs tests. I wrote up some, feel free to copy from here

Note on naming: Docker -> Container
Also look for Containerfile


Firebase version has upgraded to 9.2.0. Please release upgraded version using 9.2.0

If i use 9.2.0 in my app, then on using Firebase-UI (which uses 9.0.2) I get the following
FATAL EXCEPTION: main
Process: XXXXXXXXX, PID: 4362
java.lang.NoSuchMethodError: No virtual method zztw()Ljava/util/Set; in class Lcom/google/android/gms/common/internal/zzg; or its super classes (declaration of 'com.google.android.gms.common.internal.zzg' appears in /data/app/XXXXXXXXX-2/base.apk)

We really need this cant use this library with play services 9.2.0

I don't know why, but this stackoverflow question didn't solve this issue. Please update the to 9.2.0

@gouravd while we're working on the next version, if you want to use Firebase 9.2.0 libraries with FirebaseUI-Android, try this in your build.gradle file:
android {
    // ...

    configurations.all {
        resolutionStrategy.force 'com.google.firebase:firebase-auth:9.2.0'
        resolutionStrategy.force 'com.google.android.gms:play-services-auth:9.2.0'
    }
}

I think that will resolve your issue for now.

@samtstern When is the new build coming with firebase 9.2.0 ?

@kirtan403 I just went ahead and released version 0.4.2 which should solve this issue by upgrading the underlying dependency.

@samtstern Awesome!


Improve invalid replicasPerPartition error message

Add a better error message for when replicasPerPartition is not set or
invalid, as opposed to having "java.lang.NumberFormatException: null"

Current coverage is 45.91% (diff: 0.00%)

No coverage report found for master at 50b70d0.

Powered by Codecov. Last update 50b70d0...dfc3bf5

lgtm, pls modify the unit test to cover this case.

I will merge this in my next PR

Already merged.


Incorrect building generation

Describe the bug
When used together with the "EFW: Forgotten Place" mod, it's unclear why buildings labeled with "MWC" are being generated
Reproducibility

[X] I reproduced this issue with as few other mods as possible installed.
[ ] I am unable to reproduce this issue consistently.

Screenshots and/or videos
No response
Logs
no logs
Debug Logs
No response
Crash Reports
No response
MWC Version
0.1.3
Forge Version
1.12.2 forge <IP_ADDRESS>60
Red Core Version
0.6 dev 3
MixinBooter Version
9.1
Java Version
1.8
Java Virtual Machine
Hotspot
Operating System
windows 11
GPU Vendor
NVIDIA
Code of Conduct

[X] I agree to follow this project's Code of Conduct

https://github.com/Cubed-Development/Modern-Warfare-Cubed/assets/130232431/018c5809-4975-40c2-851a-d7139dec6fd9

Mod link "https://www.curseforge.com/minecraft/mc-mods/efw-forgotten-place/comments"

We do not have building generation, you should report the issue to them


improve the PR comment workflow text: #363

Description
I have update the PR comment workflow text now
(  Great job, @${{ github.actor }}! 🎉 Thank you for submitting your pull request. Your contribution is valuable and we appreciate your efforts to improve our project.We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines'
)
will commented when first PR is submited.

Closes #363

Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]
Checklist

[x] I have gone through the contributing guide
[x] I have updated my branch and synced it with project main branch before making this PR
[ ] I have performed a self-review of my code
[x] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[ ] I have commented my code, particularly in hard-to-understand areas.

Additional context:
[Include any additional information or context that might be helpful for reviewers.]

I was not able to check it on my local repository because this is only for first Pull request submission.

@Anshika14528 I think we have to prompt for all PRs

Fo that you can something use likethis:
name: PR Target Workflow
on:
  pull_request_target:

jobs:
  PR-Greeting:
    name: Pull Request Target
    runs-on: ubuntu-latest
    steps:
      - name: Add the PR Review Policy
        uses: thollander/actions-comment-pull-request@v2
        with:
          comment_tag: pr_review_policy
          message: |
            Great job, @${{ github.actor }}! 🎉 Thank you for submitting your pull request. Your contribution is valuable and we appreciate your efforts to improve our project.We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our [contributing guidelines](https://github.com/Anshika14528/RAPIDOC-HEALTHCARE-WEBSITE-/blob/main/CONTRIBUTING.md)'

Ok i will do this

Thankyou for your  contribution!!

@varshith257 sir, Do you want me to create new issue for that?

@Anshika14528 Submit changes requested in another PR

Ok

Please give some label to this PR also

@varshith257 sir, Do you want me to create new issue for that?

I think there's no need . Submit the PR by tagging the same issue. I have reopened it

Ok , Thankyou


STAR-1872: Parallelize UCS compactions per output shard

This splits compactions that are to produce more than one
output sstable into tasks that can execute in parallel.
Such tasks share a transaction and have combined progress
and observer. Because we cannot mark parts of an sstable
as unneeded, the transaction is only applied when all
tasks have succeeded. This also means that early open
is not supported for such tasks.
The parallelization also takes into account thread reservations,
reducing the parallelism to the number of available threads
for its level. The new functionality is turned on by default.
Major compactions will apply the same mechanism to
parallelize the operation. They will only split on pre-
existing boundary points if they are also boundary
points for the current UCS configuration. This is done
to ensure that major compactions can re-shard data when
the configuration is changed. If pre-existing boundaries
match the current state, a major compaction will still be
broken into multiple operations to reduce the space
overhead of the operation.
Also:

Introduces a parallelism parameter to major compactions
(nodetool compact -j <threads>, defaulting to half the
compaction threads) to avoid stopping all other compaction
for the duration.

Changes SSTable expiration to be done in a separate
getNextBackgroundCompactions round to improve the
efficiency of expiration (separate task can run quickly
and remove the relevant sstables without waiting for
a compaction to end).

Applies small-partition-count correction in
ShardManager.calculateCombinedDensity.

The patch is now ready for review.

I need to port over some changes that came from the development of the OSS version.
I think it would be easier for all of us if we continue the review on the OSS version (CASSANDRA-18802 and CASSANDRA-20092) -- it is quite a bit simpler. We can then come back to the additions here, with any updates that come from that review.

Applied comments, ported over changes from the OSS branch (simple sstable scanners, separate ids for partial transactions, new tests), and rebased.
Please take another look. As explained above, it may be easiest to look at the two OSS tickets first, where there are fewer code changes and the complexity around aggregates and thread reservations is not needed.


Vision Document

This doesn't have to be long or complex, but a few sentences in VISION.md describing what the overall goal of Harvey is will help a lot once folks start contributing back.

Good idea, gonna try to tackle that one soon!


Private URL for GitHub in dependency file

The dependencies listed in .gitmodules use the ssh URL which requires the user to be able to log in as "sstarcher".  This creates an error "Unexpected error while defensively updating submodules" when you try to install the helm plugin.
According to this article:
https://stackoverflow.com/questions/8197089/fatal-error-when-updating-submodule-using-git
they should instead use the public URL.
For example, this:
url = git@github.com:sstarcher/helm-release-tags.git
should probably be this:
url = https://github.com/helm-release-tags.git

It would require you to have any SSH key that is valid for GitHub, but you are correct it would be better to use HTTP.  I'll get that fixed thanks for catching this issue.


Node version 20.0.0 doesn't work even though its the minimum required

The built in .env file support starts from 20.6.0
Changed minimum version to 20.6.0

Thanks for the contribution 🙌


Update font to better font

I suggest Nunito font should be downloaded and installed on the client..
https://fonts.google.com/specimen/Nunito?preview.text_type=custom

I`ll check out the font and see what it can be integrated into


Provide changelog

Hi @tjoskar, Great module 👍, Can you provide Changelog file for future updates?
I would like to prepare a PR to add window.service.ts, window.service.spec.ts and Universal support

I added a changelog: https://github.com/tjoskar/ng2-lazyload-image/blob/master/changelog.md Feel free to add new features there :)


x/pkgsite: add checks to all.bash for JS compile errors

At the moment, the all.bash does not check for any common JS issues, such as an undefined variable or type errors. We should add steps to help catch these issues to the all.bash.
/cc @andybons @jba @jamalc

We now have these checks as part of the work from #40960.


[Feature Request] Implement direct download from S3

If report data is huge, server process consumes much memory and takes a lot of time to download from S3.
This patch allows client user to download directly from S3, via pre-signed url.
pre-signed url is available only for 1 minite.

Thanks! There are some refactoring space remained, but I'll improve them after merging the PR

Thanks!! :rocket:


List of methods that can be exported to Godot

Add a list of methods to the documentation that can be exported to Godot (ex: _input(), _ready(),...) and most importantly the parameter/argument types.
There is the Godot documentation but this is not for the Rust structs. https://docs.godotengine.org/en/stable/classes/class_node.html#method-descriptions
Although not hard now. I was first struggling to find the right types that the parameters should have in Rust. Maybe add something like this to the doc page here:
https://docs.rs/gdnative/0.9.1/gdnative/attr.methods.html
Or links to Godot docs. As searching in rust docs (https://docs.rs/gdnative/0.9.1/gdnative/index.html?search=_input) does not turn of anything (useful).
Created this issue after posting it on Discord.

@Bromeon I'll go ahead and work on this one. I think it's a natural extension to the work from documenting the #[export] tag :)
For now, I'll assume that we are primarily interested in virtual methods like _ready() that are lacking documentation and I will also assume that the main point of interest will be documenting things in Node and Control (to mention the _gui_input method). I'll also go ahead and link the relevant documentation so that we don't have to duplicate documenting "what it does" and can focus on "how to call it"
Please feel free to let me know if you have any other points you'd like me to mention. I'll try to get a PR in by early next week.

Yes, the focus are Node and Control methods, which are called by the engine. Things like _ready(), _process(), _enter_tree(), _input(), etc.
I agree that the signature, a one-liner explaining what it does and a link to the Godot docs would be good.
For example:

fn _physics_process(&self, owner: &Node, delta: f32);

Called during physics update, with a fixed timestamp.
See Godot docs for more information.

The question is where we want to add these docs?

@Bromeon I'll proceed by using that sample as the template for this change.
With regards to where it should be added, I was thinking that the NativeClass docs under #[export] would be the most fitting.
The reason is that I believe the biggest risk to not documenting is that a user may not be aware of which function names are reserved for Godot to call via notifications.
For example: If a user thinks "oh, I need a private method that processes some data occasionally, I'll just call it _process(&mut self, _owner: &Node, data; Instance<MyDataClass>) I'll connect this to the data instance as a signal callback", they will be a bit shocked to see 60+ errors per second as Godot fails to call the method due to incorrect parameter types.
That was just my line of thinking though.


fix(odk): XMLForm without h namespace

Closes: https://jira.ehealthafrica.org/browse/AET-526
Note: this fix only applies for h (http://www.w3.org/1999/xhtml) namespace.
The rest of expected namespaces are:

ev http://www.w3.org/2001/xml-events
jr http://openrosa.org/javarosa
odk http://www.opendatakit.org/xforms
orx http://openrosa.org/xforms
xsd http://www.w3.org/2001/XMLSchema

After examining the documentation, I'm pretty sure that <html> etc is actually invalid. So I'm surprised that this form works in ODK Collect, and I'm no longer sure whether we should actually support it. 🤔

The problem with the parser is that sometimes they remove the namespace making h:html and html being equal. Actually, this happens in the pyxform library and that's why I made my own parser to check the conditions... and more reasons. :woman_shrugging:

I guess that makes some kind of sense, as long as you check that removing the namespace won't leave you with clashes.

This workaround allows the use of of xforms that do not conform current XForm specifications.


exclude npm from meteor-desktop dependencies

Make meteor-desktop work with global npm installation or the one from meteor.
Npm is currently the biggest dependency and to be honest it is an overkill to have it in the deps.

Task moved to Taiga.


Cocoapods don't work

pod install
Analyzing dependencies
Fetching podspec for FastttCamera from ../FastttCamera.podspec
[!] Unable to find a specification for Masonry (= 0.6.1)

Have you solved it?


Detecting Microsoft Edge  Javascirpt Sample Code Error

This sample code is wrong,  navigator.userAgentData.brands is an array in my browser(Edge 92.0.902.84 ).
The loop should be for (brand_version_pair of navigator.userAgentData.brands)
function isChromium() {
    for (brand_version_pair in navigator.userAgentData.brands) {
        if (brand_version_pair.brand == "Chromium"){
            return true;
        }
    }
    return false;
}

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

ID: 77e7cee1-a4cc-cb21-abf9-19e7eb1333ed
Version Independent ID: 67677a5d-e51c-5aff-d5fc-b2effddb8fe2
Content: Detecting Microsoft Edge from your website - Microsoft Edge Development
Content Source: microsoft-edge/web-platform/user-agent-guidance.md
Product: microsoft-edge
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thanks for catching this and reporting the issue! I'll put up a PR to address this shortly.


Release Google.Cloud.NetworkConnectivity.V1 version 2.7.0

Changes in this release:
New features

Change netstandard2.1 target to netstandard2.0 (commit 82bea85)

Created release for Google.Cloud.NetworkConnectivity.V1-2.7.0


Support for linux and windows platforms

It would be nice if the app can be run under windows or linux OSes just like other electron-based apps.

Have you tried to build and run it on Win or Linux?
I havn't tested it myself, but . PRs are much appreciated 😄

That'd be great. I havn't tried to build and run on Win or Linux.
If you have the chance to test it out, please do.
If any changes are necessary to make it work, PRs are welcome 😄


GOG Galaxy 2 is registered with one Steam account but loads up the game from a different Steam account.

I have two Steam accounts.
One account starts with a 'C'.  It's my main account.
My other account starts with a 'P'.
Both accounts have a copy of the game "PAYDAY 2".
Also, I have Family Sharing enabled, but that probably doesn't matter.
Earlier today, I played "PAYDAY 2" on my 'P' account.  I thought I was playing it from Family Sharing, but most likely I was just playing the copy that my 'P' account owned.  I obtained three achievements and then logged off.
I don't want to play "PAYDAY 2" on my 'C' account because the game has nearly 1,000 achievements and I might end up not liking the game.
Instead of logging out of 'C' on Steam and then logging in on 'P', playing for 30 minutes, and then logging back in on 'C' using Steam Guard codes and crap, I thought it would make my life a lot easier to use GOG Galaxy for my 'P' account.  So I installed GOG Galaxy 2 and I linked my 'P' Steam account.  After it was linked, it showed the five games that my 'P' account owns, so it didn't count the games from Family Sharing.  That's fine.  I don't care.  It also showed the three achievements that I already got on my 'P' account.  Cool.  But then when I launched the game, it had launched my 'C' account's "PAYDAY 2".  In other words, it's the same exact thing as opening up Steam on my 'C' account and clicking Play, even though I specifically used my 'P' account to sign in on GOG Galaxy 2.
I can't use your program because of this.  Hopefully you understand.  Thanks.

Hey, please open this issue in Steam integration repository: https://github.com/FriendsOfGalaxy/galaxy-integration-steam
I'm closing it as not related to this repository.


URL-Resolution is broken on Windows

I am currently playing around with the library and found a bug. Urls are not constructed correctly on windows. On other platforms, a URL might look like this:
https://example.com/app/testModels

However, on windows, we get this:
https://example.com/%5Capp%5CtestModels

As you might have already guessed, %5C is the \ character. I took a look at your code and found the problem. In UriUtilsX.operator/ (https://github.com/flutterdata/flutter_data/blob/master/lib/src/utils/extensions.dart#L75), you use path_helper.normalize, which, as far as I can see, is the normalize method of the path package.
The problem here is, that path will try to automatically detect the platform you are running on and use different path stlyes depending on that:

We've tried very hard to make this library do the "right" thing on whatever platform you run it on, including in the browser. When you use the top-level functions, it will assume the current platform's path style and work with that. If you want to explicitly work with paths of a specific style, you can construct a p.Context for that style.

The solution here is easy: Simply use the posix context, e.g.:
  Uri operator /(String path) {
    return replace(path: path_helper.posix.normalize('/${this.path}/$path'));
  }

Thanks @Skycoder42 . I cannot test on Windows but tests pass on Mac/Linux.


Some questions about paper

As claiming in the paper, the proposed methods tracks the object in occlusion and uses a new datasets for videos training and propagation.
So I have two questions about this:

Do this methods lead to higher FP ? Because the paper have not shown this metric.
I notices that crowded  human datasets is used in model training. So, compared the proposed  synthetic data,  which data can bring much gains?
Thank you for your outstanding works. I am interesting in this paper and want to know more about the details. I am looking forward to getting your responds.

Hi,
thanks for you interest in our work!

We avoid false positives by additionally training a box visibility classifier, and only outputting visible detections at test time.
CrowdHuman dataset increases visible person detection accuracy, but training on synthetic data allows us to learn to localize people behind occlusions. These two factors are complementary, and both necessary for achieving top results.


HDDS-4440. HDDS-4440-s3-performance branch Merge to Master PR - draft

What changes were proposed in this pull request?
Draft PR for feature branch merge to master.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-4440
How was this patch tested?
CI workflow.

Thanks @neils-dev for updating the patch. Seems like there is a conflict due to HDDS-6346.

Yes, I added that to the master so that the patch was not lost.  It was for the master branch.
I'm updating with a new commit to simplify the unit test for start/stopping the grpc service and resync with Master.
Should be resolved with latest commit. - Thanks!

Thanks @neils-dev for addressing my comments and updating the branch.  I'm fine with the change, let's see if @kerneltime (or anyone else) has further comments.

Why is this marked as a draft? Also, please rebase.

Why is this marked as a draft? Also, please rebase.

Latest commit to re-sync with master branch resolving conflicts.
I think we started the PR 'marked' as draft to provide a PR for discussion on the feature prior to merging to master.
Thanks @adoroszlai and @kerneltime for your comments and help!

Why is this marked as a draft?

Because we want to avoid a merge via this PR, as that would squash commits.  The PR is only for discussion about code changes.  Feature branch should be merged via command-line.  CI checks are run in Neil's fork.

HDDS-4440 feature branch was merged, this can be closed.


Scroll commands that don't conflict with Mission Control on Mac

Thanks for the great plugin; I'm enjoying it so far.
Posting this as an assist to other mac devs using this plugin.
The mac defaults Ctrl+Up and Ctrl+Down for this plugin conflict with built-in keyboard shortcuts on macOS, where the Control + Up Arrow and Control + Down Arrow keyboard shortcuts are used to navigate between spaces and Mission Control. Specifically, Control + Up Arrow opens Mission Control, displaying all open windows and spaces, while Control + Down Arrow shows all windows of the frontmost application.
See also Mac keyboard shortcuts - Apple Support.
I really wish there was an AI-assisted way to suggest new good keyboard shortcuts.  I remapped scroll up and scroll down to ctrl+opt+up and ctrl+opt+down, respectively. Hopefully I can live with that.
from keybindings.json:
[
    {
        "key": "ctrl+alt+down",
        "command": "quickStage.scrollDown",
        "when": "QuickStageVisible"
    },
    {
        "key": "ctrl+down",
        "command": "-quickStage.scrollDown",
        "when": "QuickStageVisible"
    },
    {
        "key": "ctrl+alt+up",
        "command": "quickStage.scrollUp",
        "when": "QuickStageVisible"
    },
    {
        "key": "ctrl+up",
        "command": "-quickStage.scrollUp",
        "when": "QuickStageVisible"
    }
]

@codekiln
ooph! 🤦🏻♂
nice catch.
I think, I removed those keybindings on my machine, and didn't think to check for global conflicts when writing this.
i think I'm just going to change these to (Option). I don't think there is any need to get more complicated than that?

shortcuts changed with 0.3.11 thanks for pointing this out!
they are now set to Option + Arrow Keys.


refactor prober_manager to update the runtime state

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #115937
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/assign @SergeyKanzhelev @gjkim42

@matthyx
Thanks.
Either this or https://github.com/kubernetes/kubernetes/issues/115937#issuecomment-1454511383 (not adding fields to kubecontainer.ContainerStatus) should be picked.
I personally prefer not to add fields to kubecontainer.ContainerStatus as it can minimize the changes to the existing code.

@matthyx
Thanks.
Either this or kubernetes#115937 (comment) (not adding fields to kubecontainer.ContainerStatus) should be picked. I personally prefer not to add fields to kubecontainer.ContainerStatus as it can minimize the changes to the existing code.

Will you be available to discuss that during the workgroup meeting?

Will you be available to discuss that during the workgroup meeting?

I am not sure as it will be too late for me. I'll be there if available.

I am not sure as it will be too late for me. I'll be there if available.

Alright, in any case I have added the point to the meeting, and I will discuss that on your behalf if you're not here.


Installation of Grafana failed

Describe the bug
I failed to install Grafana using the installation script provided in the official documentation, and it shows errors related to PodSecurityPolicy.
Reproduce steps

helm repo add grafana https://grafana.github.io/helm-charts
helm install grafana --version 6.11.0
-f https://raw.githubusercontent.com/gocrane/helm-charts/main/integration/grafana/override_values.yaml
-n crane-system
--create-namespace grafana/grafana

Error log
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [resource mapping not found for name: "grafana" namespace: "crane-system" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"
ensure CRDs are installed first, resource mapping not found for name: "grafana-test" namespace: "crane-system" from "": no matches for kind "PodSecurityPolicy" in version "policy/v1beta1"
ensure CRDs are installed first]

Environment (please complete the following information):

K8S(RKE2) Version: v1.27.2+rke2r1
Helm Version: v3.12.1

k8s version is too high for policy/v1beta1. you could try use larger version grafana for installation.

k8s version is too high for policy/v1beta1. you could try use larger version grafana for installation.

thanks, i have tried installing the latest version of Grafana, and the issue has been resolved.


[Bug Report] Incorrect result when using fp32_dest_acc_en and performing addition operations between float32 CBs.

Describe the bug
While debugging an issue where enabling fp32_dest_acc_en causes the error to increase in ops like sum, I discovered a problem with add_tiles.
For the sum operation in the h or w direction, reduce_tiles is used, but for the n or c direction, the sum between tiles is calculated using add_tiles.

This is a pattern used in several ops like mean, norm, layer_norm, and should be fixed as soon as possible.

The issue occurs when both the input and output CBs are float, and fp32_dest_acc_en is set to true.
To reproduce the issue, I modified moreh_softmax. Below are the link and the code details:
Link:
Reader: https://github.com/tenstorrent/tt-metal/blob/hyungsuk/bug_add_tiles/ttnn/cpp/ttnn/operations/moreh/moreh_softmax/device/kernels/reader_moreh_softmax_w.cpp
ComputeKernel: https://github.com/tenstorrent/tt-metal/blob/hyungsuk/bug_add_tiles/ttnn/cpp/ttnn/operations/moreh/moreh_softmax/device/kernels/moreh_softmax_w.cpp
// Reader
    cb_reserve_back(cb_scalar, 1);
    float* ptr = reinterpret_cast<float*>(get_write_ptr(cb_scalar));
    ptr[0] = 2.013671875f;
    cb_push_back(cb_scalar, 1);

    cb_reserve_back(cb_scalar, 1);
    ptr = reinterpret_cast<float*>(get_write_ptr(cb_scalar));
    ptr[0] = 2.013671875f;
    cb_push_back(cb_scalar, 1);

// Compute

    constexpr auto cb_scalar = tt::CBIndex::c_2;
    constexpr auto cb_tmp = tt::CBIndex::c_3;

    binary_op_init_common(tt::CBIndex::c_0,  tt::CBIndex::c_1); // incorrect output 4
    // binary_op_init_common(cb_scalar,  cb_scalar, cb_tmp); // correct output 4.02734

    constexpr int dst0 = 0;

    cb_reserve_back(cb_tmp, 1);
    cb_wait_front(cb_scalar, 2);

    tile_regs_acquire();
    reconfig_data_format(cb_scalar, cb_scalar);
    add_tiles_init(cb_scalar, cb_scalar);
    add_tiles(cb_scalar, cb_scalar, 0, 1, dst0);
    tile_regs_commit();

    tile_regs_wait();
    pack_reconfig_data_format(cb_tmp);
    pack_tile(dst0, cb_tmp);
    tile_regs_release();

    cb_push_back(cb_tmp, 1);

    cb_wait_front(cb_tmp, 1);
    UNPACK(
        DPRINT << "OUTPUT TEST " << TSLICE(cb_tmp, 0, SliceRange{ .h0 = 0, .h1 = 1, .hs = 1, .w0 = 0, .w1 = 1, .ws = 1 });
    )

The above code calculates 2.013671875 + 2.013671875.
Since both input CBs are of type float32 and fp32_dest_acc_en is set to True, the correct result should be 4.02734.
However, in binary_op_init_common, when different CBs are provided as input and output CBs, the result is 4 instead of the expected 4.02734.
For short ops, it's possible to provide the correct cb_id directly to binary_op_init_common. However, for more complex ops that use multiple CBs, binary_op_init_common is only called once, and reconfig_data_format is called before the FPU operation.
To Reproduce
Steps to reproduce the behavior:

Go to https://github.com/tenstorrent/tt-metal/tree/hyungsuk/bug_add_tiles
Run cmd 'pytest ./tests/ttnn/unit_tests/operations/test_moreh_softmax.py '
See error

Expected behavior

I want the correct calculation result to be output in the above example.
If this is not a bug, then I would like the following:

Since we often mix bfloat16 and float CBs, a method to convert to float during the process, even if initialized as bfloat16, would be desired.
I would like to know the correct way to use both bfloat16 and float CBs.

Screenshots
If applicable, add screenshots to help explain your problem.
Please complete the following environment information:

OS: [e.g. Ubuntu 20.04] Ubuntu 22.04.4 LTS
Version of software (eg. commit b2f75b7658ed9c6a6239866955304bef6a4d864f)
ARCH:  wormhole_b0

Additional context
Add any other context about the problem here.

@rdjogoTT @bbradelTT  who is the best PoC to take a look at this?

@hschoi4448 which mean are you referring to?
As far as I can tell, ttnn.mean does not use add_tiles

The configuration for mixed precision is relatively tricky.
@rtawfik01
Who on the LLK team would be able to take a look and double check CB creating and identify the right calls and parameters to make in the kernels?

I can take a look, probably next sometime next week.

@hschoi4448 which mean are you referring to?
As far as I can tell, ttnn.mean does not use add_tiles

The "mean" I am referring to is moreh_mean.
morh_mean: calculates the sum across the n and c dimensions using a for loop where add_tile is employed for tile-wise accumulation within the loop.
https://github.com/tenstorrent/tt-metal/blob/d53c07111902ecca685bcf43959611e63e4f3d52/ttnn/cpp/ttnn/operations/moreh/moreh_mean/device/kernels/moreh_mean_nc.cpp#L44
add_tiles is also used in various other operations.
moreh_layer_norm_backward_gamma_beta_grad:
use add_tiles to compute the gradients for gamma and beta.
https://github.com/tenstorrent/tt-metal/blob/d53c07111902ecca685bcf43959611e63e4f3d52/ttnn/cpp/ttnn/operations/moreh/moreh_layer_norm_backward/device/kernels/moreh_layer_norm_backward_gamma_beta_grad_kernel.cpp#L136
moreh_softmax:
https://github.com/tenstorrent/tt-metal/blob/d53c07111902ecca685bcf43959611e63e4f3d52/ttnn/cpp/ttnn/operations/moreh/moreh_softmax/device/kernels/moreh_softmax_c_large.cpp#L79
moreh_softmax_backward:
https://github.com/tenstorrent/tt-metal/blob/d53c07111902ecca685bcf43959611e63e4f3d52/ttnn/cpp/ttnn/operations/moreh/moreh_softmax_backward/device/kernels/moreh_softmax_backward_c_large.cpp#L62C41-L62C47
moreh_adamw:
https://github.com/tenstorrent/tt-metal/blob/d53c07111902ecca685bcf43959611e63e4f3d52/ttnn/cpp/ttnn/operations/moreh/moreh_adamw/device/kernels/moreh_adamw.cpp#L96
etc..
@rdjogoTT

Thanks for the clarification @hschoi4448

@hschoi4448 I've taken a look, and the issue is due to reconfig_data_format skipping the configuration of a few of the FPU registers that control input data formats. The reason we skip these registers is to minimize perf impact of reconfiguring between data formats.
The ideal solution is one that I have been working on in https://github.com/tenstorrent/tt-metal/issues/13653, which is to transition to passing the CB ids to reconfig_data_format as template parameters rather than runtime parameters, so that we can reconfigure only the necessary registers without wasting cycles checking formats at runtime. However, this is still not ready, and will take substantial work to test.
I can propose a workaround for now: I previously added a flag to the function in order to force the registers to be updated, so if you call the function as: reconfig_data_format<true>(cb_scalar, cb_scalar); it should pass your test.
If this workaround is sufficient for now then I won't spend time working on a solution. I can make note of this test case and revisit it with the new API to ensure it works correctly. Let me know what you think.

Thank you!
Using reconfig_data_format<true>(cb_scalar, cb_scalar); produced the correct value, 4.02734.
Does setting to_from_int8 to true in reconfig_data_format work correctly in all cases?
If so, it seems fine, even if performance drops a bit for now.
On our side, accurate values take higher priority than performance.
This is because, if we get accurate values, we can split the work into two phases:

ensuring functional correctness and
optimizing performance.

However, if the values are inaccurate for the sake of performance, we constantly have to verify during development whether test failures are due to accuracy issues or our mistakes, which makes our life much harder.

@hschoi4448 I've taken a look, and the issue is due to reconfig_data_format skipping the configuration of a few of the FPU registers that control input data formats. The reason we skip these registers is to minimize perf impact of reconfiguring between data formats.
The ideal solution is one that I have been working on in #13653, which is to transition to passing the CB ids to reconfig_data_format as template parameters rather than runtime parameters, so that we can reconfigure only the necessary registers without wasting cycles checking formats at runtime. However, this is still not ready, and will take substantial work to test.
I can propose a workaround for now: I previously added a flag to the function in order to force the registers to be updated, so if you call the function as: reconfig_data_format<true>(cb_scalar, cb_scalar); it should pass your test.
If this workaround is sufficient for now then I won't spend time working on a solution. I can make note of this test case and revisit it with the new API to ensure it works correctly. Let me know what you think.

great, thank you @rdjogoTT !

@hschoi4448 setting to_from_int8 should work for all cases. I understand the need for accuracy, and I hope to fix the data_format_reconfig API soon to improve performance as well.


redux-saga does not do anything: not listening the dispatches (or is not running the saga function)

I have a saga to handle login, which will listen for LOGIN_REQUEST (state/auth/saga.js):
function* handleLogin(action) {
    // ...

    console.log("handleLogin saga OK")

    try {
        // ...

    } catch (e) {
        // ...
    }
}

function* loginSaga() {
    console.log("loginsaga ok")
    yield takeLatest(LOGIN_REQUEST, handleLogin)
}

export {
    loginSaga,
}

a point here: the login.log of loginSaga is executed when the app is rendered, but the console.log of the handleLogin function is not executed when the action is dispatched, which shows that the saga seems to be configured correctly but not running function after dispatch
Now, I import this into a root file (state/rootSaga.js):
import {
    loginSaga
} from './modules/auth/saga';

function* rootSaga() {
    yield all(
        [
            loginSaga(),
        ]
    )
}

export default rootSaga;

After that, I do the same thing doc says, but using reduxdevtools (state/configureStore.js):
// saga imports
import createSagaMiddleware from 'redux-saga';
import rootSaga from './rootSaga';

const configureStore = () => {
    const persistedState = loadState()
    const sagaMiddleware = createSagaMiddleware();

    // all middleares with redux dev tools
    const middlewares = [
        sagaMiddleware,
    ]

    const composeEnhancers = composeWithDevTools(
        applyMiddleware(
            ...middlewares
        )
    )

    const store = createStore(
        rootReducer,
        persistedState,
        composeEnhancers
    );

    sagaMiddleware.run(rootSaga)
    return store
};

export default configureStore;

I can not seem to figure out where I'm going wrong, I know only that the dispatch seems to be not being heard by the middleware, or the loginSaga is not running the function.
source code: https://github.com/marcosroot/webstation.dev-client/tree/master/src/state

I am running into the same issues. None of the dispatches are being heard. It seems to be related to  #1887

this started to work magically, then I dispatched the same action into useEffect, into another component (the original is dispatched when submitting a form)

FWIW I ran into an issue like this and moving where I was calling sagaMiddleware.run made it work. From https://github.com/redux-saga/redux-saga/issues/1120 I surmise that the action that I cared about was being dispatched before the sagas were being run.

I have the same problem with versions >= 1.0.0. If I downgrade to <= 0.16.2 it works ok.

thanks @pulpfree , i didnt understand rearranging solution from @lindboe -looks like better approach but my luck of knowledge  i guess, that works after so many hours

hmm this didn't really do it for me. @pulpfree , did you have to downgrade something else besides redux-saga?

@dotslashbin ensure that your root is setup as below, the yield all was the key.
function* rootSaga() {
    yield all(
        [
            loginSaga(),
        ]
    )
}

Thank you very much! I finally got it. There was also an issue with the "connect" function on my component. So, the problem wasn't actually this.

@dotslashbin ensure that your root is setup as below, the yield all was the key.
function* rootSaga() {
    yield all(
        [
            loginSaga(),
        ]
    )
}

Thanks man! After viewing this I put a comma at the end of the last saga in the array, and it worked! I proceeded with removing the comma cause it just does not make sense, and it continued to work... What kind of bug is this!? I lost a full day of coding because of this :(

I'm glad you go through with it man! yeah, sometimes you need 1 day to
solve something really simple. It's important that you have your linters in
check.
Anyway, now I am using redux-toolkit.You should give it a try too. It has a
lot of advantages which I think is great for large scale projects.
On Tue, May 31, 2022 at 11:00 PM Lenin De La Rosa @.***>
wrote:

@dotslashbin https://github.com/dotslashbin ensure that your root is
setup as below, the yield all was the key.
function* rootSaga() {
yield all(
[
loginSaga(),
]
)
}
Thanks man! After viewing this I put a comma at the end of the last saga
in the array, and it worked! I proceeded with removing the comma cause it
just does not make sense, and it continued to work... What kind of bug is
this!? I lost a full day of coding because of this :(
—
Reply to this email directly, view it on GitHub
https://github.com/redux-saga/redux-saga/issues/1896#issuecomment-1142250878,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFBVVH5OULJLU2NUSTD4U3VMYSSNANCNFSM4IFTJLXQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Bug(subgraph-radio): Node P2P port functionality isn't working

Existing p2pNodePort functionality only allows exposing a single P2P port, but this chart specifies two:
https://github.com/graphops/launchpad-charts/blob/main/charts/subgraph-radio/values.yaml#L106-L112
All of the init container machinery also only supports a single port:
https://github.com/graphops/launchpad-charts/blob/main/charts/subgraph-radio/templates/subgraph-radio/statefulset.yaml#L68-L74
I think we need to reimplement this functionality by referencing another p2pNodePort-enabled chart

fixed by #130 applied the same to #131


[SPARK-23268][SQL]Reorganize packages in data source V2

What changes were proposed in this pull request?

create a new package for partitioning/distribution related classes.
As Spark will add new concrete implementations of Distribution in new releases, it is good to
have a new package for partitioning/distribution related classes.

move streaming related class to package org.apache.spark.sql.sources.v2.reader/writer.streaming, instead of org.apache.spark.sql.sources.v2.streaming.reader/writer.
So that the there won't be package reader/writer inside package streaming, which is quite confusing.
Before change:

v2
├── reader
├── streaming
│   ├── reader
│   └── writer
└── writer

After change:
v2
├── reader
│   └── streaming
└── writer
    └── streaming

How was this patch tested?
Unit test.

LGTM, also  cc @rdblue

Thanks! Merged to master/2.3


docs: remove unused GOTRUE_DB_MAX_POOL_SIZE var

What kind of change does this PR introduce?
docs update
What is the new behavior?
Remove unused GOTRUE_DB_MAX_POOL_SIZE env var

closing since this is used here: https://github.com/supabase/auth/blob/374a9c2171ad2a1b1e9cb2903e87739ce4913db9/internal/storage/dial.go#L72

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
8208

Relevant Lines:
12487

💛  - Coveralls


Outline on horizontal bar chart is not correct

The outline around bars is incorrect for horizontal bars. It extends around the left, top, and right, like a normal bar chart should. Instead, the horizontal bar should have an outline around the top, right, and bottom.
Horizontal (Bug) Example: https://jsfiddle.net/pzx1LtqL/1/
Normal (Working) Example: https://jsfiddle.net/fm99oqqn/1/

+1
the borderSkipped:'left' option seems to have no effect

@ThaJay borderSkipped works: https://jsfiddle.net/tmp3cj5q/1/

Thanks, obviously I got the configuration object structure wrong


Uncaught TypeError: Cannot read property 'top' of undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 0.174.0
System: Mac OS X 10.10.2
Thrown From: minimap package, v3.3.3
Stack Trace
Uncaught TypeError: Cannot read property 'top' of undefined
At /Users/matijaabicic/.atom/packages/minimap/lib/minimap-view.coffee:353

TypeError: Cannot read property 'top' of undefined
  at MinimapView.module.exports.MinimapView.updateScrollY (/Users/matijaabicic/.atom/packages/minimap/lib/minimap-view.coffee:353:64)
  at MinimapView.updateScrollY (/Users/matijaabicic/.atom/packages/minimap/lib/minimap-view.coffee:1:1)
  at MinimapView.module.exports.MinimapView.updateScroll (/Users/matijaabicic/.atom/packages/minimap/lib/minimap-view.coffee:368:6)
  at MinimapView.updateScroll (/Users/matijaabicic/.atom/packages/minimap/lib/minimap-view.coffee:1:1)
  at /Users/matijaabicic/.atom/packages/minimap/lib/minimap-view.coffee:268:8

Commands

Config
{
  "core": {},
  "minimap": {
    "plugins": {
      "find-and-replace": true,
      "git-diff": true,
      "selection": true
    }
  }
}

Installed Packages
# User
autocomplete-plus, v0.21.0
color-picker, v1.2.5
jshint, v1.1.0
minimap, v3.3.3
minimap-color-highlight, v3.0.1
minimap-find-and-replace, v3.0.0
minimap-git-diff, v3.0.4
minimap-highlight-selected, v3.0.0
minimap-selection, v3.0.0

# Dev
No dev packages

/cc @atom/core

Same as #195


[0.3] manifest: Add explicit port number to external hostname

Need to backport this change to release branch.

oh yeah, I just tried to merge straight from main.  I'll clean it up.

hmm I don't think I can change the branch to m fork.  I'll close and create a new PR.


Cancelling a recurring timer that I have lost track of

Is there a good way to cancel a recurring timer for which I've lost track of the timerId? (Without upgrading the canister in question)
Just curious about if this is possible right now as I ran into this issue earlier today.

Even if you knew what the Id is, how would you force the canister to cancelTimer <Id>?

I have an API endpoint that essentially does this
public shared ({ caller }) func cancelTimer() : async Result.Result<(), Text> {
    switch (timer) {
      case (?timerId) {
        cancelTimer(timerId);
        timer := null;
        #ok;
      };
      case null #err("No timer to cancel");
    };
  };

You could install an (almost) identical canister that also records the timer creations in an ordered data structure, and then makes that queryable. This should give you the Id. If this doesn't work (due to dynamic timer creation from internal data) then I lament, but you have to reinstall.

Instead of reinstalling, my current solution is just to stop the canister and then restart it.

@ggreif I'm running into a weird issue with recurring timers now. Here are the steps I take to get into this spot:

Create a function "A" which starts a recurring timer that executes every few (5-10) seconds (in my case the job is making an inter-canister call, but maybe this isn't important).
Call function "A"
Stop the canister that contains the timer.
Wait for a 30-60 seconds.
Restart the canister containing the timer. (timer should not be running).
Call function "A" again (attempting to start up a new timer that executions the same function).

After step 6, it seems like multiple timer executions will kick off back to back, almost like the old timer starts running again until it has "caught up" with the current time, at which point (once "caught up") the rapid executions will stop, and the "newly created timer" will take over.

Interesting findings, but I think it is easy to explain and needs some adjustments to the library.
stopping the canister seems to reset the global timer
no timer gets cancelled when the a canister is stopped
to prevent jitter, recurring timers will add the delay to the desired expiration time (not the wall time of the expiration callback)
This means that if a timer is present, the whole timer machinery doesn't restart after recommencing the canister. This is a bug. Coming out of the "stopped" state we have to set the global timer if needed. Also we should "cut out" all recurrent expirations that would have happened while being stopped, so that no n ✕ jobs get started without need.

Are you describing a mixture of current behavior and desired behavior with these 3 points?

1. stopping the canister seems to reset the _global_ timer

2. no timer gets cancelled when the a canister is stopped

3. to prevent jitter, recurring timers will add the delay to the desired expiration time (_not_ the wall time of the expiration callback)

Another interesting finding I came across today.

However, stopping and restarting a canister twice WILL kill the timer.

There is a replica test that verifies that stop-start of a canister doesn't change the global timer.

your "sometimes" finding
your twice finding
both are somewhat bizarre and I am trying to come up with a test case for both.

@ByronBecker I heard that versions of dfx are out there that set up a local replica that has timer bugs. Try to upgrade to 0.13.1 if possible.

@ByronBecker is a repro still possible? Do you think. there is still a bug hiding somewhere?


🐛 Panic internal error: entered unreachable code in lint/correctness/use_exhaustive_dependencies.rs

Environment information
CLI:
  Version:                      1.9.4
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_PATH:               unset
  BIOME_LOG_PREFIX_NAME:        unset
  BIOME_CONFIG_PATH:            unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           unset
  JS_RUNTIME_NAME:              unset
  NODE_PACKAGE_MANAGER:         unset

Biome Configuration:
  Status:                       unset

Workspace:
  Open Documents:               0

What happened?
timeout -v 150 biome lint TEST___FILE.ts

crashes with
Source Location: crates/biome_js_analyze/src/lint/correctness/use_exhaustive_dependencies.rs:610:13
Thread Name: biome::worker_1
Message: internal error: entered unreachable code

File - compressed.zip
Expected result
No crash
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Thanks so much for the detailed reports! It may take us a bit to get back to all of them, but rest assured they're on our radar!

In this case, Biome is failing to detect that Point is imported, so this is a bug in the semantic model. Specifically this line is returning false:
https://github.com/biomejs/biome/blob/4721b6c7852c2c58e417ab61d6f4fb761a073489/crates/biome_js_analyze/src/lint/correctness/use_exhaustive_dependencies.rs#L488

In the sample, this line is getting parsed as JS_BOGUS_STATEMENT, and not JS_IMPORT:
import type {Point} from '.geomet';


Bug_Accordion> Expand Collapse All> Control prop 'isInverse'> Preview is not getting changed upon toggling the True/False

Describe the bug
Dark background and light text is not displayed when 'isInverse' is 'True'.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://storybook-preview-290--upbeat-sinoussi-f675aa.netlify.app/?path=/story/accordion--expand-collapse-all'
Click on 'Controls'
Select the 'isInverse' control prop
Toggle it into 'True/False'
Verify that preview is not getting changed

Expected behavior
Dark background and light text should display when 'isInverse' is 'True'.
Screenshots
https://somup.com/c3no6pTVs1
Desktop :

OS: [Win 10]
Browser [chrome]
Version [Version 98.0.4758.82 (Official Build) (64-bit)]

The issue is fixed.
see screen-cast : https://www.screenpresso.com/=irbac
Hence, Closing the ticket.
Thanks!


Cannot drop outside items inside a sortable container

We have a use case where we have a sortable container and one can reorder items inside but we want to also be able to drop items from the outside into it. For the best UX one would expect that while the user is dragging some outside object over the sortable container, the items will be shifted apart to make space for the new one in the place where his cursor is. If he drops the new item, it will be placed there. If he drags away from the sortable container, the items should be "merged" again.
I guess our use case could be fixed by you triggering a couple of new events - dragNewItemOver, dragNewItemOut - in your code. Then we would be free to add/remove the dragged object to the sortableObjectList.
Additionally, the sortEndAction should not be triggered for dragged items that are not part of the sortableObjectList, because the user might not have added the item in the list.

I'm currently working on a PR that will allow items to be freely dropped from one container to another.  There is also another PR #52 that exposes an event similar to what you're looking for I think.  Having items shift around to make space is also on my todo list.  I'll see what I can do to accommodate some of those event ideas.

Just wondering what the status of this is? We have a similar use case, where we'd like to have a #sortable-objects container and be able to drag items from outside into it and the sortable-objects would then reorder around the newly placed item depending on where it's dropped.

Not sure if this was true before, but I'm getting the following errors when dragging an outside item inside a sortable container:
ember.debug.js:19829 TypeError: Cannot read property 'get' of undefined
    at Class.moveObjectPositions (drag-coordinator.js:129)
    at Class.moveElements (drag-coordinator.js:147)
    at Class.draggingOver (drag-coordinator.js:68)
    at Class.dragOver (draggable-object.js:120)
    at Class.trigger (ember.debug.js:44830)
    at Class.superWrapper [as trigger] (ember.debug.js:42849)

On this line:
// Move if items are in different sortable-objects component
var aList = aSortable.get('sortableObjectList');

Is there any progress on this issue @dgavey?


Feature: Add activity type in reward trigger

Added

activityType is now passed to the RewardsFacet contract

Updated

The RewardsFacet ABI has been updated to the latest version of the contract

/release-pr


Dapr Commands

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

Merging first, will test post merge


[BUG] - Bug summary title

Describe the bug
create-script doesn't work because parse_data is wrong.
To Reproduce

Install landscape-api python module
export LANDSCAPE_API_KEY, LANDSCAPE_API_SECRET and LANDSCAPE_API_URI like described in documentation
Create a file with a script that should be uploaded
python3 -m landscape_api create-script Test2 300 $PATH_TO_YOUR_SCRIPT

You get an error:
Couldn't parse value '$PATH_TO_YOUR_SCRIPT' as data

Expected behavior
Script gets uploaded to landscape API
Environment:

Ubuntu 22.04
Python 3.10.12

Suggested fix:
    def parse_data(self, parameter, value):
        return value

I already fixed it and will create a PR

I am not allowed to push to this repository, but the fix I wanted to suggest also checks if the file exists:
   def parse_data(self, parameter, value):         if not os.path.exists(value):             raise FileNotFoundError(value)         return value


Make status of TempEntityClass optional

The status field of the TempEntityClass is required, but this is overriden in
the forms.py. This makes it possible to create entities without a status via
the webinterface, but not via the API.
I propose to make the status field optional (using blank=True). Another
option would be to remove the field completely- is it being used by anyone?
Or did I understand correctly, that the TempEntityClass will be dropped
completely and it does not make sense to propose changes at this time?

This issue could become irrelevant / or at least is affected by: https://github.com/acdh-oeaw/apis-core-rdf/issues/6

We can't delete it before TempEntityClass has been fully migrated as some projects might use it still. And since TempEntityClass lives in apis-core, every project would be affected.


Is it possible to change colors/style of timeslot component?

You can add your own stylesheet to override the default ones. If you inspect the DOM, you'll see the class names used by react-available-times, e.g. .rat-AvailableTimes_component, .rat-TimeSlot_component.


Write the function for the admin to get all pending passes.

Write the controller for the admin to get all pending outpasses, accepted outpasses and rejected outpasses in controllers> admin.controller.js.
Note :

For Pending outpasses, search for forms with isAccepted : null in the database and return the result.
For Accepted outpasses, search for forms with isAccepted : true in the database and return the result.
For Rejected outpasses, search for forms with isAccepted : false in the database and return the result.

Make sure to pull before starting your work.
For any doubts or difficulty, you can ping me on discord, I'll try to help you out as soon as possible.
All the Best!!

claim (I'm a girl)

Assigned to @Mannxxx
You have 24 hours to complete this task!!


Update Chromium versions for api.IDBRequest.error

16221

 Quality gate: NA
Details

 Quality gate: NA
Details

 Quality gate: NA
Details

 Quality gate: NA
Details

 Quality gate: NA
Details

 Quality gate: NA
Details


TensorRT engine binding error

System information*

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No.
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Jetson TX2, Linux4Tegra Xenial 16.04
TensorFlow installed from (source or binary): Source
TensorFlow version (use command below): 1.8.0
Python version: 2.7.12
Bazel version (if compiling from source): 0.18.0
GCC/Compiler version (if compiling from source): gcc5
CUDA/cuDNN version: 9.0/7.1.5
GPU model and memory: Jetson tx2 8GB

You can collect some of this information using our environment capture script
You can also obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the current behavior:
I have frozen a graph that contains the following operations:

tf.layers.conv2d(*args, **kwargs)
tf.layers.batch_normalization(net, **batch_norm)

I will try to provide a minimal graph that have this problem.
Describe the expected behavior:
I create a trt_graph by using the function trt.create_inference_graph and it creates a graph successfully  but whenever I try to make an inference I encounter:
2018-10-22 15:29:17.537843: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1053] Created TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with│
 363 MB memory) -> physical GPU (device: 0, name: NVIDIA Tegra X2, pci bus id: 0000:00:00.0, compute capability: 6.2)                                            │
2018-10-22 15:29:20.426303: F tensorflow/contrib/tensorrt/shape_fn/trt_shfn.cc:76] TensorRT engine cannot find binding: ModelBase/Conv2dBatchNorm/Relu
Aborted (core dumped)

Any guideline on how to provide a better log issue?
Thanks

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Exact command to reproduce
Mobile device

Hi @ymodak I've attached a small minimal module that reproduces the problem in the Jetson TX2, let me know if I can be of help.
There are two python modules one that creates the tensorrt graph and serializes it. the other try to run inference on an image. .
tensorrt_problem.tar.gz

We have encounter other issues with performance on jetson tx2 while using (on house compiling) tensorflow 1.10 or 1.11, do you provide wheels for python2.7 for the jetson tx2.

Any updates?

Hi @Davidnet,
Did you check
https://docs.nvidia.com/deeplearning/dgx/install-tf-jetsontx2/index.html ?

We are working on producing the packages.

Nagging Assignee @samikama: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

I am closing this since the update will come with the next pip package for TX2.


BOM

Hi,
Do you have a BOM with references directly usable on digi-key or farnell for example?

I am sorry, no.

Could you make one for us?
On Wed, Oct 7, 2020, 9:13 AM Peter Misenko<EMAIL_ADDRESS>wrote:

I am sorry, no.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bobricius/armachat/issues/5#issuecomment-704926470,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI6GU5IHMWRQVUBTINBNSLLSJRSOLANCNFSM4SGSOC4A
.

I will try to compile whatever I order, hopefully there won't be too much trial and error...


[charsheet_3-5_full] New D&D 3.5 sheet - whit additional parts

Changes / Comments
New D&D 3.5 sheet based on the one made by Diana P., but with some additional part (Turn Undead, Psionic Power, Invocations, and some enhanced feature (split class level for every classes, attack section for NPC is now dynamic)
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[X] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[X] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.

The request is still open, I made a mistake.
Sorry

Hey there @hoyer555 , I'm sorry to have to inform you that your PR will be denied. While there have been duplicate public sheets allowed in the past, going forward Roll20 wants to limit this practice. Your collaboration with existing sheets should not be restricted to translations, in fact in the spirit of community engagement, you should be able to push all sorts of features that would make running the game a better experience. Please get in touch with the authors of the existing 3.5ed sheets and check with them about adding your ideas on top of it. Thanks for all the work you do!


Add special installs to setup

Fix #114

Codecov Report

Merging #116 (ec33c0d) into master (09626f2) will decrease coverage by 1.07%.
The diff coverage is 53.84%.

@@            Coverage Diff             @@
##           master     #116      +/-   ##
==========================================
- Coverage   91.18%   90.11%   -1.08%
==========================================
  Files          22       22
  Lines        1792     1790       -2
==========================================
- Hits         1634     1613      -21
- Misses        158      177      +19

Impacted Files
Coverage Δ

dotmotif/executors/__init__.py
100.00% <ø> (ø)

dotmotif/executors/test_grandisoexecutor.py
100.00% <ø> (ø)

dotmotif/ingest/__init__.py
51.06% <ø> (-3.84%)
:arrow_down:

dotmotif/executors/test_neuprintexecutor.py
20.83% <25.00%> (-12.50%)
:arrow_down:

dotmotif/__init__.py
94.25% <50.00%> (-2.18%)
:arrow_down:

dotmotif/tests/test_dm_flags.py
84.90% <75.00%> (+0.29%)
:arrow_up:

dotmotif/executors/test_dm_cypher.py
100.00% <100.00%> (ø)

dotmotif/executors/NeuPrintExecutor.py
0.00% <0.00%> (-41.94%)
:arrow_down:

dotmotif/executors/NetworkXExecutor.py
91.47% <0.00%> (-1.56%)
:arrow_down:

dotmotif/executors/GrandIsoExecutor.py
82.85% <0.00%> (+2.85%)
:arrow_up:

Continue to review full report at Codecov.

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


[BugFix] Fix NLJoin crash when enable runtime_adaptive_dop

output_amplification_factor in NLJoinBuildOperator will be called when enable runtime_adaptive_dop. but _input_channels will be clear when all builder has set_finishing.
so the solution is add a close method for each build channel
Fixes https://github.com/StarRocks/StarRocksTest/issues/2692
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

@mergify backport branch-3.0

https://github.com/Mergifyio backport branch-3.1


BETA TEST - Logon Using Linkedin Fails on FreeCodeCamp.org

When attempting logon authentication via LinkedIn, invalid redirect_uri. URL doesn't match API key.

Looks like @QuincyLarson Has fixed this. Thanks!


gnome-control-center: provides access to the tracker gsettings schemas

Motivation for this change
gnome-control-center needs access to the tracker gsettings schemas to
enable the settings button in the search panel.
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Ported to 3.22 as e54650e92.


bpf: Fix compilation of bpf_ct_tests

b905f0d ("bpf: Compile test with tunneling disabled") broke the compilation of bpf/tests/bpf_ct_tests as shown below:
In file included from tests/bpf_ct_tests.c:41:
In file included from /home/ubuntu/go/src/github.com/cilium/cilium/bpf/lib/conntrack.h:14:
In file included from /home/ubuntu/go/src/github.com/cilium/cilium/bpf/lib/ipv4.h:10:
In file included from /home/ubuntu/go/src/github.com/cilium/cilium/bpf/lib/metrics.h:13:
/home/ubuntu/go/src/github.com/cilium/cilium/bpf/lib/maps.h:96:14: error: use of undeclared identifier 'TUNNEL_ENDPOINT_MAP_SIZE'
        .max_elem       = TUNNEL_ENDPOINT_MAP_SIZE,
                          ^
In file included from tests/bpf_ct_tests.c:41:
In file included from /home/ubuntu/go/src/github.com/cilium/cilium/bpf/lib/conntrack.h:14:
/home/ubuntu/go/src/github.com/cilium/cilium/bpf/lib/ipv4.h:31:14: error: use of undeclared identifier 'CILIUM_IPV4_FRAG_MAP_MAX_ENTRIES'
        .max_elem       = CILIUM_IPV4_FRAG_MAP_MAX_ENTRIES,
                          ^
2 errors generated.

The error was not detected because this test doesn't run in CI.
This pull request fixes it by restoring the set of compile options used for bpf_ct_tests before b905f0d.
Fixes: https://github.com/cilium/cilium/pull/14451

@kkourt Done.

This change is not covered in CI and all team reviews are in, so I think it's ready to merge.