New hover card

Maybe it would be nice to redesign hovercard to neobrutalism as well.
Probably we can add it to landing page.
Currently would be interesting add to showing art under address created or collected.

Ref

https://hic.af/

In the case of the landing page, there are no addresses/profiles to hover over. We were talking about making something for collections because I think I already have something. But there is a profile that would need it in the gallery item. Does that make sense?

After a chat with @yangwao I think we have an idea of how it could be made.
The first thing would be to tweak nft card a bit. Adding something like "details" or "info" would work just fine. The position could be under the network.
Card:

flexible
reusable for other cases, so for example creator hover card would have the same layout/design as a single nft hovercard.
simple with insights after hovering

Use cases:
Card brief info - no need to open the gallery item. There could be something like - properties, and the highest offer and if the card will be on explore page, information about the collection could be there too. For example floor.
Address info - created, collected
Collection insights on explore collections page.

Premise here to show second-order information which are not needed when you are browsing first order view
Hover card would be used on top of view of
- profile

you want to know more about a particular address on-chain activity
showing

collected - showing amount of on-chain buys address has made
created - the amount of NFTs created/minted
total sales, sales short - the amount of in some highest currency address has made
3 pictures with the highest sale
- collection view

hint collection numbers https://beta.kodadot.xyz/rmrk/collection/0a8ce195286c168f19-DONKEY
you want to know more about particular collection statistics
unique owners
highest sale
floor price
total volume in base currency
3 pictures with highest sale/offer
NFT view

collection - unique owners
traits rarity score open rarity score
highest offer in the collection
3 highest sold NFTs

where would you imagine nft view to be?
I mean the hovercard is for extending information on the card - could be collection or owner.
What is the use case for nft view? You don't usually have somewhere to hover for more info.
For example, here you hover over the collection and you get more info

I can also imagine the use for user view, right here:

Do you want to add another property to the nft card to create a place for hover over?

@exezbcz @yangwao is this something that is ready to pick up?

@exezbcz @yangwao is this something that is ready to pick up?

Hey, not yet, i will ping you once its ready

hey @prachi00 here are the designs

nft hover card tbd

figma: landing page handoff

@exezbcz is this name a url? If yes, what happens when it is clicked as currently it isnt clickable. Also, the hover state?

yup, it should redirect you to the profile. For hover states please see #4111 section links.

you want to know more about a particular address on-chain activity

oh, I see now we forgot to add Twitter to the design.
making follow up issue from this one?

Any chance that we can add a "Copy address" feature? I use it very often when hovering profile cards

Member

yup, i will make it. It should also be in the wallet icon hover.

Follow up for making for user hover card

add a Twitter link to the design
copy address feature


Build failure: kanidm

Steps To Reproduce
Steps to reproduce the behavior:

build kanidm

Build log
https://hydra.nixos.org/build/245589915

Additional context
Add any other context about the problem here.
Notify maintainers
@erictapen @Flakebi @mweinelt @adamcstephens
Metadata
NixOS, 24.05 (Uakari), 24.05.20231227.f930306

Add a :+1: reaction to issues you find important.

It seems like maybe rust is now erroring on warnings?
error: unused import: `implementation::*`
  --> unix_integration/nss_kanidm/src/lib.rs:24:9
   |
24 | pub use implementation::*;
   |         ^^^^^^^^^^^^^^^^^
   |
note: the lint level is defined here
  --> unix_integration/nss_kanidm/src/lib.rs:1:9
   |
1  | #![deny(warnings)]
   |         ^^^^^^^^
   = note: `#[deny(unused_imports)]` implied by `#[deny(warnings)]`


Small item icons appear warped on low DPR displays

Describe the bug
on screens with a low DPR such as 1.25 or 1.0 small item icons look bad because they are rendered using nearest neighbor.
Profile/Location
skill icons and category icons
Screenshots

Browser:

any browser that supports image-rendering (caniuse)
a display with a low DPR

Additional context
the reason image-rendering is set in the first place is to help 16x 2d textures not be blurry
Suggested Solution:
the best way to solve this is probably a bunch of DPR media queries deciding when an image is large enough for nearest neighbor
Credit:
originally posted on Discord

#593 is a temporary solution a better solution should possible when container queries become supported https://caniuse.com/css-container-queries


testing: -bench does not honor the import path wild cards

What version of Go are you using (go version)?
go version go1.7.4 darwin/amd64
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN="/Users/lex/dev/go/bin"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/lex/clients/packt/dev/go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.7.4_2/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.7.4_2/libexec/pkg/tool/darwin_amd64"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/vl/zj0n4b_9015_22chhpcjjw4h0000gn/T/go-build724604650=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"

What did you do?
My project directory looks like this:
book
+ chapter1
   + 01_fib
   + 02_recursive
   chapter1.go
+ chapter2
( etc...)

I would like to run tests for all chapters from the root (book) directory.
go test ./... works as expected, running all tests found in all subdirectories.
$ go test  ./...
?   	bitbucket.org/lsheehan/fp-in-go	[no test files]
?   	bitbucket.org/lsheehan/fp-in-go/chapter1	[no test files]
ok  	bitbucket.org/lsheehan/fp-in-go/chapter1/01_fib	2.860s

go test -bench ./... does not.  Here's what it does:
$ go test -bench ./...
?   	bitbucket.org/lsheehan/fp-in-go	[no test files]

I can, however, move into the directory that contains the tests and get good results from the benchmark test:
... chapter1/fib $ go test -bench=.
1
BenchmarkFibFunc-8   	100
10000
1000000
3000000
 3000000	       570 ns/op
PASS
ok  	bitbucket.org/lsheehan/fp-in-go/chapter1/fib	5.100s

This is working as intended.
-bench takes an argument, a regex to match against benchmarks in the _test.go files.
Your non working example passes ./... as that regex which doesn't match anything and will only run in the current directory.
try
go test -bench=.  ./...

Yup. Works like a charm when called properly.  Thank you for sharing your wisdom with articles like: https://dave.cheney.net/2013/06/30/how-to-write-benchmarks-in-go


add a way for the server to accept an error response for a given transaction from the private api

inside the private API we often perform checks before completing actions, such as if a chat exists before sending a message to it. When these checks don't pass, we don't send any data back to the server so a REST API request appears to never complete, which is incorrect. We should send an error response back instead

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @tneot01 in #server-development.

i found the underlying issue and have fixed it i believe. The issue was 2 fold. First, the ErrorMiddleware wasn't even used. Not sure how that happened. I checked git blame but it just showed me adding the Metrics Middleware, not removing anything related the the Error Middleware, which wasn't even being used. The second issue was the metrics middleware was wrapped in a try/catch making it catch any errors that the ErrorMiddleware was supposed to catch

Fixed, branch: zach/326/transaction-error-support. Just return an error key at the same level as transactionId and data


[Exclusivity] Look through block arguments to find noescape closures

Update static enforcement to look through noescape blocks to find an underlying
noescape closure when a closure is converted to a block and passed as an
argument to a function. This fixes a false negative when the closure performs
an access that conflicts with an already in-progress access.
These new diagnostics are warnings for source compatibility but will
be upgraded to errors in the future.
rdar://problem/32912660

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 38f2515410517f47fdfe9d70ff72d610f8e3dc14

Updated to weaken an assertion caught by the linux bot. We shouldn't always expect to find a block storage header initialization

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - 38f2515410517f47fdfe9d70ff72d610f8e3dc14

Build failed
Swift Test Linux Platform
Git Sha - 38f2515410517f47fdfe9d70ff72d610f8e3dc14

@swift-ci Please test

@swift-ci Please test source compatibility

@swift-ci Please test source compatibility

This doesn't introduce any new warnings on the source compatibility suite.

@swift-ci Please smoke test and merge


Put gimp image file in repo

For the cover.jpg,
https://github.com/thewhitetulip/web-dev-golang-anti-textbook/blob/master/cover.jpg
would it not be better to put the original Gimp image file in the repo so that people can edit it?

I'll upload it tonight. Meanwhile how did you know I used gimp?

@benkasminbullock Can you comment on that PR?

perl -MImage::Info -e "print Image::Info::image_info('cover.jpg')->{Comment}"

Created with GIMP

Cool. Got to try Perl 6!


2.2 Release for LinuxAmd64 not available, go building fails

Dear authors,
I am trying to set up mattermail to use it together with Mattermost2.2.
Unfortunately, the link to the 2.2 release does not work and I am running into errors while trying to compile the 2.2 version directly. E.g. with Go 1.6.1 I am getting the following error message:
go install
mattermail-2.2
./mattermail.go:248: client.LoginByEmail undefined (type *model.Client has no field or method LoginByEmail)
./mattermail.go:311: client.UploadFile undefined (type *model.Client has no field or method UploadFile, but does have model.uploadFile)
While with go1.2.1to go1.5 I am getting the following error:
package runtime/debug: unrecognized import path "runtime/debug"
I would be glad if you could recommend a go version or upload a release version 2.2.
Thanks in advance
Marco

I think the problem is the Mattermost version, in Mattermail repo you need:
git checkout release-2.2
glide install
make build-linux

but if you prefer I published version 2.2 again:
https://github.com/rodrigocorsi2/mattermail/releases/tag/v2.2

Thank you very much for the fast action and uploading a 2.2 release.
However, I am getting now the following error:

Error on check new email: imap: unexpected completion status
("ZFBUA17 NO [BADCHARSET (US-ASCII)] The specified charset is not
supported.")
 Try again in 30s
For some reasons new messages are not accepted as recent messages but
show up as existing messages.

I tried it also with the recent Mattermail version 3 and I did not get
the error, but of course I could not publish anything to Mattermost.
Here is the full error log:

INFO Mattermost Incoming Email	19:47:21 MatterMail version: 2.2-dev
DEBG Mattermost Incoming Email	19:47:21 Debug mode on
INFO Mattermost Incoming Email	19:47:21 Checking new emails
DEBG Mattermost Incoming Email	19:47:21 CheckNewMails
DEBG Mattermost Incoming Email	19:47:21 CheckImapConnection: DialTLS
IMAP Mattermost Incoming Email	19:47:21 Connected to [2a00:1398:9:f612::42]:993 (Tag=ZFBUA)
IMAP Mattermost Incoming Email	19:47:21 S: * OK The Microsoft Exchange IMAP4 service is ready.
IMAP Mattermost Incoming Email	19:47:21 Server greeting: The Microsoft Exchange IMAP4 service is ready.
IMAP Mattermost Incoming Email	19:47:21 C: ZFBUA1 CAPABILITY
IMAP Mattermost Incoming Email	19:47:21 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=NTLM AUTH=GSSAPI UIDPLUS MOVE ID CHILDREN IDLE NAMESPACE LITERAL+
IMAP Mattermost Incoming Email	19:47:21 S: ZFBUA1 OK CAPABILITY completed.
INFO Mattermost Incoming Email	19:47:21 Connected with "imap.kit.edu:993"
IMAP Mattermost Incoming Email	19:47:21 C: ZFBUA2 LOGIN
IMAP Mattermost Incoming Email	19:47:21 S: ZFBUA2 OK LOGIN completed.
IMAP Mattermost Incoming Email	19:47:21 C: ZFBUA3 CAPABILITY
IMAP Mattermost Incoming Email	19:47:21 S: * CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=NTLM AUTH=GSSAPI UIDPLUS MOVE ID XPROXY3 CHILDREN IDLE NAMESPACE LITERAL+
IMAP Mattermost Incoming Email	19:47:21 S: ZFBUA3 OK CAPABILITY completed.
IMAP Mattermost Incoming Email	19:47:21 C: ZFBUA4 SELECT "INBOX"
IMAP Mattermost Incoming Email	19:47:21 S: * 10 EXISTS
IMAP Mattermost Incoming Email	19:47:21 S: * 0 RECENT
IMAP Mattermost Incoming Email	19:47:21 S: * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
IMAP Mattermost Incoming Email	19:47:21 S: * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
IMAP Mattermost Incoming Email	19:47:21 S: * OK [UNSEEN 6] Is the first unseen message
IMAP Mattermost Incoming Email	19:47:21 S: * OK [UIDVALIDITY 14] UIDVALIDITY value
IMAP Mattermost Incoming Email	19:47:21 S: * OK [UIDNEXT 25] The next unique identifier value
IMAP Mattermost Incoming Email	19:47:21 S: ZFBUA4 OK [READ-WRITE] SELECT completed.
IMAP Mattermost Incoming Email	19:47:21 C: ZFBUA5 UID SEARCH CHARSET UTF-8 UNSEEN
IMAP Mattermost Incoming Email	19:47:21 S: ZFBUA5 NO [BADCHARSET (US-ASCII)] The specified charset is not supported.
EROR Mattermost Incoming Email	19:47:21 UIDSearch:
INFO Mattermost Incoming Email	19:47:21 Error on check new email: imap: unexpected completion status ("ZFBUA5 NO [BADCHARSET (US-ASCII)] The specified charset is not supported.")
 Try again in 30s
DEBG Mattermost Incoming Email	19:47:51 CheckNewMails
DEBG Mattermost Incoming Email	19:47:51 CheckImapConnection: Connection alive
IMAP Mattermost Incoming Email	19:47:51 C: ZFBUA6 SELECT "INBOX"
IMAP Mattermost Incoming Email	19:47:51 S: * 10 EXISTS
IMAP Mattermost Incoming Email	19:47:51 S: * 0 RECENT
IMAP Mattermost Incoming Email	19:47:51 S: * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
IMAP Mattermost Incoming Email	19:47:51 S: * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
IMAP Mattermost Incoming Email	19:47:51 S: * OK [UNSEEN 6] Is the first unseen message
IMAP Mattermost Incoming Email	19:47:51 S: * OK [UIDVALIDITY 14] UIDVALIDITY value
IMAP Mattermost Incoming Email	19:47:51 S: * OK [UIDNEXT 25] The next unique identifier value
IMAP Mattermost Incoming Email	19:47:51 S: ZFBUA6 OK [READ-WRITE] SELECT completed.
IMAP Mattermost Incoming Email	19:47:51 C: ZFBUA7 UID SEARCH CHARSET UTF-8 UNSEEN
IMAP Mattermost Incoming Email	19:47:51 S: ZFBUA7 NO [BADCHARSET (US-ASCII)] The specified charset is not supported.
EROR Mattermost Incoming Email	19:47:51 UIDSearch:
INFO Mattermost Incoming Email	19:47:51 Waiting new messages
DEBG Mattermost Incoming Email	19:47:51 IdleMailBox
DEBG Mattermost Incoming Email	19:47:51 CheckImapConnection: Connection alive
IMAP Mattermost Incoming Email	19:47:51 C: ZFBUA8 SELECT "INBOX"
IMAP Mattermost Incoming Email	19:47:51 S: * 10 EXISTS
IMAP Mattermost Incoming Email	19:47:51 S: * 0 RECENT
IMAP Mattermost Incoming Email	19:47:51 S: * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
IMAP Mattermost Incoming Email	19:47:51 S: * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
IMAP Mattermost Incoming Email	19:47:51 S: * OK [UNSEEN 6] Is the first unseen message
IMAP Mattermost Incoming Email	19:47:51 S: * OK [UIDVALIDITY 14] UIDVALIDITY value
IMAP Mattermost Incoming Email	19:47:51 S: * OK [UIDNEXT 25] The next unique identifier value
IMAP Mattermost Incoming Email	19:47:51 S: ZFBUA8 OK [READ-WRITE] SELECT completed.
IMAP Mattermost Incoming Email	19:47:51 C: ZFBUA9 IDLE
IMAP Mattermost Incoming Email	19:47:51 S: + IDLE accepted, awaiting DONE command.
IMAP Mattermost Incoming Email	19:48:41 S: * 1 RECENT
IMAP Mattermost Incoming Email	19:48:41 C: DONE
IMAP Mattermost Incoming Email	19:48:41 S: * 11 EXISTS
IMAP Mattermost Incoming Email	19:48:41 S: ZFBUA9 OK IDLE completed.
DEBG Mattermost Incoming Email	19:48:41 CheckNewMails
DEBG Mattermost Incoming Email	19:48:41 CheckImapConnection: Connection alive
IMAP Mattermost Incoming Email	19:48:41 C: ZFBUA10 SELECT "INBOX"
IMAP Mattermost Incoming Email	19:48:41 S: * 11 EXISTS
IMAP Mattermost Incoming Email	19:48:41 S: * 0 RECENT
IMAP Mattermost Incoming Email	19:48:41 S: * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
IMAP Mattermost Incoming Email	19:48:41 S: * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
IMAP Mattermost Incoming Email	19:48:41 S: * OK [UNSEEN 6] Is the first unseen message
IMAP Mattermost Incoming Email	19:48:41 S: * OK [UIDVALIDITY 14] UIDVALIDITY value
IMAP Mattermost Incoming Email	19:48:41 S: * OK [UIDNEXT 26] The next unique identifier value
IMAP Mattermost Incoming Email	19:48:41 S: ZFBUA10 OK [READ-WRITE] SELECT completed.
IMAP Mattermost Incoming Email	19:48:41 C: ZFBUA11 UID SEARCH CHARSET UTF-8 UNSEEN
IMAP Mattermost Incoming Email	19:48:41 S: ZFBUA11 NO [BADCHARSET (US-ASCII)] The specified charset is not supported.
EROR Mattermost Incoming Email	19:48:41 UIDSearch:
INFO Mattermost Incoming Email	19:48:41 Error on check new email: imap: unexpected completion status ("ZFBUA11 NO [BADCHARSET (US-ASCII)] The specified charset is not supported.")
 Try again in 30s
DEBG Mattermost Incoming Email	19:49:11 CheckNewMails
DEBG Mattermost Incoming Email	19:49:11 CheckImapConnection: Connection alive
IMAP Mattermost Incoming Email	19:49:11 C: ZFBUA12 SELECT "INBOX"
IMAP Mattermost Incoming Email	19:49:11 S: * 11 EXISTS
IMAP Mattermost Incoming Email	19:49:11 S: * 0 RECENT
IMAP Mattermost Incoming Email	19:49:11 S: * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
IMAP Mattermost Incoming Email	19:49:11 S: * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
IMAP Mattermost Incoming Email	19:49:11 S: * OK [UNSEEN 6] Is the first unseen message
IMAP Mattermost Incoming Email	19:49:11 S: * OK [UIDVALIDITY 14] UIDVALIDITY value
IMAP Mattermost Incoming Email	19:49:11 S: * OK [UIDNEXT 26] The next unique identifier value
IMAP Mattermost Incoming Email	19:49:11 S: ZFBUA12 OK [READ-WRITE] SELECT completed.
IMAP Mattermost Incoming Email	19:49:11 C: ZFBUA13 UID SEARCH CHARSET UTF-8 UNSEEN
IMAP Mattermost Incoming Email	19:49:11 S: ZFBUA13 NO [BADCHARSET (US-ASCII)] The specified charset is not supported.
EROR Mattermost Incoming Email	19:49:11 UIDSearch:
DEBG Mattermost Incoming Email	19:49:11 IdleMailBox
DEBG Mattermost Incoming Email	19:49:11 CheckImapConnection: Connection alive
IMAP Mattermost Incoming Email	19:49:11 C: ZFBUA14 SELECT "INBOX"
IMAP Mattermost Incoming Email	19:49:11 S: * 11 EXISTS
IMAP Mattermost Incoming Email	19:49:11 S: * 0 RECENT
IMAP Mattermost Incoming Email	19:49:11 S: * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
IMAP Mattermost Incoming Email	19:49:11 S: * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
IMAP Mattermost Incoming Email	19:49:11 S: * OK [UNSEEN 6] Is the first unseen message
IMAP Mattermost Incoming Email	19:49:11 S: * OK [UIDVALIDITY 14] UIDVALIDITY value
IMAP Mattermost Incoming Email	19:49:11 S: * OK [UIDNEXT 26] The next unique identifier value
IMAP Mattermost Incoming Email	19:49:11 S: ZFBUA14 OK [READ-WRITE] SELECT completed.
IMAP Mattermost Incoming Email	19:49:11 C: ZFBUA15 IDLE
IMAP Mattermost Incoming Email	19:49:11 S: + IDLE accepted, awaiting DONE command.
IMAP Mattermost Incoming Email	19:52:01 S: * 1 RECENT
IMAP Mattermost Incoming Email	19:52:01 C: DONE
IMAP Mattermost Incoming Email	19:52:01 S: * 12 EXISTS
IMAP Mattermost Incoming Email	19:52:01 S: ZFBUA15 OK IDLE completed.
DEBG Mattermost Incoming Email	19:52:01 CheckNewMails
DEBG Mattermost Incoming Email	19:52:01 CheckImapConnection: Connection alive
IMAP Mattermost Incoming Email	19:52:01 C: ZFBUA16 SELECT "INBOX"
IMAP Mattermost Incoming Email	19:52:01 S: * 12 EXISTS
IMAP Mattermost Incoming Email	19:52:01 S: * 0 RECENT
IMAP Mattermost Incoming Email	19:52:01 S: * FLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)
IMAP Mattermost Incoming Email	19:52:01 S: * OK [PERMANENTFLAGS (\Seen \Answered \Flagged \Deleted \Draft $MDNSent)] Permanent flags
IMAP Mattermost Incoming Email	19:52:01 S: * OK [UNSEEN 6] Is the first unseen message
IMAP Mattermost Incoming Email	19:52:01 S: * OK [UIDVALIDITY 14] UIDVALIDITY value
IMAP Mattermost Incoming Email	19:52:01 S: * OK [UIDNEXT 27] The next unique identifier value
IMAP Mattermost Incoming Email	19:52:01 S: ZFBUA16 OK [READ-WRITE] SELECT completed.
IMAP Mattermost Incoming Email	19:52:01 C: ZFBUA17 UID SEARCH CHARSET UTF-8 UNSEEN
IMAP Mattermost Incoming Email	19:52:01 S: ZFBUA17 NO [BADCHARSET (US-ASCII)] The specified charset is not supported.
EROR Mattermost Incoming Email	19:52:01 UIDSearch:
INFO Mattermost Incoming Email	19:52:01 Error on check new email: imap: unexpected completion status ("ZFBUA17 NO [BADCHARSET (US-ASCII)] The specified charset is not supported.")
 Try again in 30s

Your help will be appreciated very much again.
--
Marco A. Harrendorf<EMAIL_ADDRESS>KIT - IEKP
Am Montag, den 06.06.2016, 10:57 -0700 schrieb Rodrigo:

I think the problem is the Mattermost version, in Mattermail repo you
need:
git checkout release-2.2
glide install
make build-linux

but if you prefer I published version 2.2 again:
https://github.com/rodrigocorsi2/mattermail/releases/tag/v2.2

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/rodrigocorsi2/mattermail/issues/18#issuecomment-22
4037016

Hi @mharrend !
This bug was fixed in the new version, I'm not planning to update the release-2.2, but if you want you can try this:
change this line in mattermail.go:
cmd, err := imap.Wait(m.imapClient.UIDSearch(specs...))

to:
cmd, err = imap.Wait(m.imapClient.Send("UID SEARCH", append([]imap.Field{"CHARSET", "US-ASCII"}, specs...)...))

When you test, please tell me if works, I don't have Mattermost 2.2 to test. :+1:

Hello,
+1 thank you very much, your patch worked and I am trying to backport
the option to choose via subject to which channel a message should be
posted.
Should I make a PR after my changes?
Thanks
Marco A. Harrendorf<EMAIL_ADDRESS>KIT - IEKP
Am Montag, den 06.06.2016, 15:07 -0700 schrieb Rodrigo:

When you test, please tell me if works, I don't have Mattermost 2.2
to test. :+1:

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/rodrigocorsi2/mattermail/issues/18#issuecomment-22
4103583

I really appreciate your help, if you want to bring all resources to version 2.2 I think you need to copy version 3.0.11 and change some points:
file mattermail.go, function PostFile:
1 - client.Login to client.LoginByEmail
2 - remove the block // Get Team
3 - client.UploadPostAttachment to client.UploadFile
Before making the PR run the command make link to check your code
Thank you!

Hey @mharrend!
Please test the branch release-2.2.1
https://github.com/rodrigocorsi2/mattermail/tree/release-2.2.1

Dear @rodrigocorsi2,
thank you very much for the release-2.2.1. It seems to work.
However, I ran into some small problem with the glide.yaml
configuration.
After I cloned the release-2.2.1 github repo I typed glide install and
make build.
But I had to go to the vendor/github/rodrigocorsi2/mattermail folder
which was created by glide first and manually checkout the release-
2.2.1 before I could build the release-2.2.1 executable.
I am a newbie to glide but I assume in the glide.yaml file one has to
state the branch if it is not the master branch.
Best regards,
Marco
Marco A. Harrendorf<EMAIL_ADDRESS>KIT - IEKP
Am Mittwoch, den 08.06.2016, 16:50 -0700 schrieb Rodrigo:

Hey @mharrend!
Please test the branch release-2.2.1
https://github.com/rodrigocorsi2/mattermail/tree/release-2.2.1

You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/rodrigocorsi2/mattermail/issues/18#issuecomment-22
4765074


C# - MergeNestedIfAction

MergeNestedIfAction looks like not implemented and not provided by Roslyn, so I'll try to implement this one.

Great, thank you.

Pull request: https://github.com/icsharpcode/RefactoringEssentials/pull/57

Merged. Thanks


Add a d3 quadFeature

This will render similar to the gl quadFeature, with the exception that when an image quad is not a parallelogram, the image is still drawn as one.  The gl renderer skews an image using two different transforms making the quad contain the full image, but with a transform discontinuity along one of the diagonals when the quad is not a parallelogram.  The d3 render will skew the image with a single transform, and non-parallelograms will be render somewhat incorrectly.
Initially, this was implemented with polygons for both color quads and image quads, but polygons using images have to use defs to define an svg pattern, and were substantially slower than using images (one virtue of using polygons is that non-parallelogram quads were rendered with the correct area, though the image was still incorrectly transformed).
The d3 tile layer has been switched to use the quad feature.  This is slightly faster than using the plane feature (perhaps a 10% speed up), but still much slower than canvas or gl.
The quad tests were dropped when the webpack refactor was done.  They have been added back in.

This resolves issue #540 and is needed by issues #541 and #548.

[Current coverage][cc-pull] is 74.00%

Merging [#581][cc-pull] into [master][cc-base-branch] will increase coverage by 0.88%

@@             master       #581   diff @@
==========================================
  Files            82         83     +1
  Lines          7216       7300    +84
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           5276       5402   +126
+ Misses         1940       1898    -42
  Partials          0          0

Powered by Codecov. Last updated by [85af24d...1c233f4][cc-compare]
[cc-base-branch]: https://codecov.io/gh/OpenGeoscience/geojs/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/OpenGeoscience/geojs/compare/85af24d49ab43491f1c7145a1637df3cc46f0886...1c233f40fbf3cbe98aee5e5f334b02bdd72f0f6a
[cc-pull]: https://codecov.io/gh/OpenGeoscience/geojs/pull/581?src=pr

Not directly related to this branch: I am having issues with data:
[ 63%] Downloading grid.jpg
-- Data is here: https://data.kitware.com/api/v1/file/560a89518d777f7bfaadd3dd/download
CMake Error at Girder_FetchScripts/fetch_26e86857de2e8c4c4fc808dfd6b12e95_grid.jpg.cmake:7 (message):
  Error downloading grid.jpg: "Unsupported protocol"

You probably need to compile cmake with SSL support.

thanks @jbeezley didn't have this issue before. Is it because we switched to https on data recently?

that was indeed the problem, my cmake was built without openssl.

@manthey LGTM :+1: @jbeezley do you bless this change too?

Yup, LGTM.


Soft Tabs Malfunction ~ Size is always 1 space, every language

Prerequisites

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging

The nature of this problem does not allow me to do this.

Description
When tab type is set to soft, size being set to Anything and Soft Tabs checkbox Editor configuration option being either checked or not checked, the tab size of every single existing file is automatically auto indented to one space tab size and manipulating any other options doesn't effect the problem.
Steps to Reproduce

Install latest KDE Neon GNU/Linux distribution (Either should be fine)
Install atom / atom beta (ditto behavior)
Possibly copy my editor setup using my config, or even my styles

Expected behavior: Tab size isn't autoindented to 1 space and using the autoindent editor command makes an effect after changing the tab size and/or type.
Actual behavior: Tab size is stuck at 1 space. Using hard tabs and only manually indenting all of every file will yield me the desired tab size at the expense of having to use hard tabs.
Reproduces how often: Indefinitely
Versions

 atom --version && apm --version && atom-beta --version
Atom    : 1.19.0
Electron: 1.6.9
Chrome  : 56.0.2924.87
Node    : 7.4.0
apm  1.18.2
npm  3.10.10
node 6.9.5 x64
python 2.7.12
git 2.7.4
Atom    : 1.20.0-beta0
Electron: 1.6.9
Chrome  : 56.0.2924.87
Node    : 7.4.0
uname -romi
4.10.0-32-generic x86_64 x86_64 GNU/Linux
lsb_release -a
No LSB modules are available.
Distributor ID: neon
Description:    KDE neon Developer Edition
Release:        16.04
Codename:       xenial
kf5-config --version
Qt: 5.9.1
KDE Frameworks: 5.37.0
kf5-config: 1.0
plasmashell --version
plasmashell 5.10.4
kwin --version
kwin 5.10.4
krunner --version
krunner 5.10.4
kded5 --version
kded5 5.37.0

Additional Information
Please offer me any other workarounds. I bet it'll take a while to propagate a fix to lowly Linux and this issue addles my workflow :(
Note that I launch atom with this script called molecule to overcome frustrating issue #8455
Feel free to inquire about additional OS or editor information needed. I can offer extensive detail about customizations to the interface as KDE is quite customizable.
Thank you for such a awesome code editor!

I cannot reproduce this anymore.


replace dnsutils example image

Related:

Part of: https://github.com/kubernetes/k8s.io/issues/1522

The gcr.io/kubernetes-e2e-test-images repo is deprecated and will
eventually go away. Use an equivalent image from the project-owned
k8s.gcr.io repo
There is a blog post that also references the old repo, but we are
leaving that untouched as historical reference. The images it lists
are appropriate for the version of kubernetes that was available at
the time. To update the list would be to re-engineer the effort for
the latest version of kubernetes, which seems slightly out of scope
here. (ref: https://github.com/kubernetes/website/blob/main/content/en/blog/_posts/2020-01-15-Kubernetes-on-MIPS.md)

/cc @kubernetes/sig-docs-zh-reviews

Thanks @spiffxp .
/lgtm

/lgtm
/approve


NoSuchMethodError in labellab_mobile app

app build complete but when image selected from gallery it gives error
To Reproduce
Steps to reproduce the behavior:

build the app (I build on android )
Click on 'camera icon' and take a picture
now come back and click on collection icon
select a photo

Can I know where have you hosted the server? This happens because currently, the server saves images in its instance storage only. You can bypass this error by using a local server. But if you hosted the server in a platform like Heroku, classification fails as it cannot store images in its instance.

@Shrawan907 also, have you deployed the labellab backend and configured the mobile app according to the readme docs


TypeScript SSR: className not match

babel-plugin-styled-components is the solution for matching client and server classNames. However, if I use Typescript, what can I do to solve this issue?
Version
2.1.2
Steps to reproduce

Set up a Typescript project with React + React Router. Share routes code for client & server
Achieve SSR with styled-components following documentation

Expected Behavior
There's no warning from browser console said className not match
Actual Behavior
Got console warning:
Warning: Prop `className` did not match. Server: "sc-kAzzGY ldrcMw" Client: "sc-bxivhb dleuTs"

(Because I'm using React 16 beta, the error message is slightly different from React 15)

Unfortunately, there is no way to get reliable class names without some sort of build step. Can you not use Babel plugins with TypeScript?

@mxstbr I just found a problem today (with next.js), It cause by babel-plugin-styled-components cannot transform result from Typescript
// Typescript file, before compile
import styled from 'styled-components'
const Input = styled.input`
  width: 100px;
`

Result
// result
const styled_components_1 = require("styled-components");
const Input = styled.default.input ` // <<< babel plugin doesnt see this one
  width: 100px;
`;

It look like transformer passing styled.default.input and the result is broken
Workaround for this problem is
// typescript file
import styledComponent from 'styled-components'
const styled = styledComponent

const Input = styled.input`
  width: 100px;
`

so when Typescript compile this snippet it wiil result
const styled = styled_components_1.default;
const Input = styled.input ` // <<<<< babel plugin will see this and does it job
  width: 100px;
`;

Mind submitting an issue over at the babel plugin repo? Thanks!

I think it should be easy to check the method for .default. :+1:

Is this fixed? Still happening to me.

@serranoarevalo can you provide simple repo to reproduce ?

@serranoarevalo @zapkub There's several approaches to integrating the babel-plugin with TypeScript and unfortunately none of them lie in our range (i.e. concerns)
What I'd recommend is the use of @babel/preset-typescript, since Babel now supports TypeScript transpilation.
See: https://github.com/styled-components/babel-plugin-styled-components/issues/41#issuecomment-410747606
Marking this as a duplicate of: https://github.com/styled-components/babel-plugin-styled-components/issues/41


Error - Project import doesn't work

Hi!
I have faced a weird error that is related to project import feature. When I try to import the project, it gives me the following error:
**An error occurred
Unable to deserialize**

Please help, because there were a lot of mocked data!

Hi @adlet-nyussupov.
My apologies for the late response. This issue should have been resolved in the latest release. Would it be possible for you to give it another try?
Best regards,
Karl Dahlgren

Hi @karldahlgren !
Yes I used a new version of the CastleMock and It seems that the problem was resolved. Thank you!


Cant update disk size

Hi,
We are unable to update the disk size for MySQL instance using the mysql terraform module, upon further inspection, I found that the disk_size variable is ignored in the Terraform lifecycle.
Would like to understand the purpose or how to update the disk size of an instance using this module?
P.S: I also found the similar lifecycle rule in Postgres terraform module as well
Thanks!

We ignore the disk_size changes because it would cause drift with Cloud SQL's native auto-resize functionality: https://github.com/terraform-google-modules/terraform-google-sql-db/pull/18

That makes sense, thanks for providing the information. I opened a PR #149, which adds a note on this so that it's clear for others


Add Ubuntu Jammy CI (#32)

🎉 New feature
Part of https://github.com/ignition-tooling/release-tools/issues/566
Summary
We support Jammy for Fortress onwards, and we're ready to test it in CI.
Test it
Run GitHub Actions CI.
Checklist

[X] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[X] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

@osrf-jenkins retest this please


[draft] Investigate gtest segfault in CI

Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.

[ ] C++ Guidelines
[ ] Doxygen docs
[ ] Unit tests
[ ] No unwanted commits/changes
[ ] Descriptive title/description

[ ] PR is single purpose
[ ] Related issue listed

[ ] Comments in source
[ ] No typos
[ ] Update changelog
[ ] Not work-in-progress
[ ] External references or docs updated
[ ] Self review of PR done
[ ] Any breaking changes?

Closing. This was resolved by other means.


All the tasks are recreated if we add a new endpoint.

Description
We are using the module to create the DMS instance, endpoint, and tasks. if we are adding a new endpoint for a new task requirement.
At the time of applying the changes, the endpoint will be create but all the current tasks also recreating. There is no change in task configuration. we are just adding a new endpoint.

[ Done ] ✋ I have searched the open/closed issues and my issue is not listed.

Versions

Module version [Required]: v2.2.0

Terragrunt version 0.57.0

Provider version(s):
hashicorp/aws >= 5.32

Reproduction Code [Required]

Steps to reproduce the behavior:

Steps

Create new dms instance, endpoint and tasks using this module
Add new endpoint to configuration
Try to apply the changes.

Expected behavior
The new endpoint only need to be created.

Actual behavior
New endpoint are creating but same time we can see the all the tasks are recreating.

Terminal Output Screenshot(s)
  # aws_dms_replication_task.this["track_to_s3"] must be replaced
-/+ resource "aws_dms_replication_task" "this" {
      + cdc_start_position        = (known after apply)
      ~ id                        = "development-import-mysql-tracking-to-s3" -> (known after apply)
      ~ replication_task_arn      = "arn:aws:dms:us-east-2:xxxxxxxxx:task:xyz" -> (known after apply)
      ~ replication_task_settings = jsonencode(
          ~ {
              ~ ControlTablesSettings               = {
                  - historyTimeslotInMinutes      = 5
                    # (6 unchanged attributes hidden)
                }
              ~ Logging                             = {
                  - CloudWatchLogGroup  = "dms-tasks-redshift-datasync"
                  - CloudWatchLogStream = "dms-task-syz"
                  - EnableLogContext    = false
                    # (2 unchanged attributes hidden)
                }
                # (12 unchanged attributes hidden)
            }
        )
      ~ source_endpoint_arn       = "arn:aws:dms:us-east-2:xxxxxxxxxxx:endpoint:xyz" # forces replacement -> (known after apply) # forces replacement
      ~ status                    = "running" -> (known after apply)
        tags                      = {
            "Environment" = "development"
            "Task"        = "development-import-mysql-tracking-to-s3"
            "Terraform"   = "true"
        }
      ~ target_endpoint_arn       = "arn:aws:dms:us-east-2:xxxx:endpoint:xyz" # forces replacement -> (known after apply) # forces replacement
        # (6 unchanged attributes hidden)
    }

Additional context

This is just down to the DMS API - you can see from these two lines:
~ source_endpoint_arn       = "arn:aws:dms:us-east-2:xxxxxxxxxxx:endpoint:xyz" # forces replacement -> (known after apply) # forces replacement
...
~ target_endpoint_arn       = "arn:aws:dms:us-east-2:xxxx:endpoint:xyz" # forces replacement -> (known after apply) # forces replacement

Any time you change a source or target endpoint for a task, the API requires the task to be replaced.

This is just down to the DMS API - you can see from these two lines:
~ source_endpoint_arn       = "arn:aws:dms:us-east-2:xxxxxxxxxxx:endpoint:xyz" # forces replacement -> (known after apply) # forces replacement
...
~ target_endpoint_arn       = "arn:aws:dms:us-east-2:xxxx:endpoint:xyz" # forces replacement -> (known after apply) # forces replacement

Any time you change a source or target endpoint for a task, the API requires the task to be replaced.

In our case we have't make any changes to current tasks. Just added a new endpoint but still in That case all the current tasks force to replace.

+1

+1


Surface area calculated 10x too big in kettle.py

100 cm in a meter so there are 100*100 cm^2 in a m^2, so divide by 10000 instead of 1000.
Surface area was calculated 10 times too big, resulting in way too high
heat loss through the kettle surface.

You're right, thanks for the correction.
Additionally, I forgot to multiply by pi in the calculation of the kettle's lateral area.
 The kettle.py model fitted perfectly to my data after changing the 1000 divisor. Now it doesn't, the model looses heat faster than in reality.


Dev branch - Default model selection not working

Bug Report
There seems to be a bug in dev branch. Default model is not getting selected. Instead Arena Model is displayed.
Installation Method
Ubuntu 22.04
Docker build using dev branch
Environment

Open WebUI Version: docker built from dev branch

Ollama (if applicable): latest

Operating System: Ubuntu 22.04

Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]

Unable to reproduce.


Refactor User Profile header as UITableViewCell

Design

[ ] Add the user country

[x] Current: 5 Days left -- for v1 all Campaigns should have the same end date. The gross thing here is we need to pick a random campaign that does have an end date set, and just use it here, since we don't have a global "end" variable. #450

[ ] Refactor header as a UITableViewCell

Edited this issue to entail refactoring our current implementation, as #66 does a better job of the various states of the profile.


fix typo

define NOBADALLOC as mock up
MSVC 2015 compiler support
fix typo

I can split the PR into three separate requests if necessary.

Looks good to me 👍


Make ls ignore vim backup files

Fixes
Checklist

[x] I have made a change to this repository, be it functionality, testing, documentation, spelling, or grammar.
[x] I updated my branch with the master branch.
[ ] I have added the necessary testing to prove my fix is effective/my feature works (or I did not modify functionality).
[ ] I have added necessary documentation about the functionality in an appropriate .md file.
[ ] I have appropriately commented any code I have modified

Short description of what this PR does:
In case user has vim set up to create backup files in the current directory, make the ls command ignore backup files (ending in '~' by default).
I find this helpful with my setup, but it obviously won't be of benefit to everyone. Probably won't cause any problems, though. I don't imagine anyone uses '~' at the end of a filename for any other purpose (and for some reason, also stores them in the notes directory).
Yeah, take it or leave it. :-)

Nice! I'm definitely on board with the goal, good suggestion.
Unfortunately it will break things though, because it looks like the default version of ls on a Mac doesn't support --ignore (or -I): https://stackoverflow.com/questions/11213849/how-to-ls-ignore-on-osx.
I think this would work everywhere if implemented with grep -v instead. Would that work for you? AFAIK that should do the same thing. Any downsides you're aware of?

Ah, yes, I was worried that -I might not be supported everywhere. I had
originally planned on using grep -v before I discovered that ls had
its own --ignore option.
As far as I know, grep -v is standard and should be supported on all
*nix platforms, so that's probably the way to do it. :-)
Excerpts from Tim Perry's message of April 1, 2020 5:46 am:

Nice! I'm definitely on board with the goal, good suggestion.
Unfortunately it will break things though, because it looks like the default version of ls on a Mac doesn't support --ignore (or -I): https://stackoverflow.com/questions/11213849/how-to-ls-ignore-on-osx.
I think this would work everywhere if implemented with grep -v instead. Would that work for you? AFAIK that should do the same thing. Any downsides you're aware of?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/pimterry/notes/pull/76#issuecomment-607228112

@pimterry as excluding files are popping up often.
what's your opinion on having .notesignore file like .gitignore and maybe a flag called --ignore-file to provide ignore file with other name.
Additionally, It will  be good if notes respected the .gitignore file and ignore all files defined in there.

I've now updated this to use grep -v instead, added a quick test, and merged it. Thanks @eshapard! Nice improvement :+1:.

@rmNULL I'm open to some kind of ignore config, if you or others would find that useful. I'd be surprised if we needed a special command line argument for it, I expect it's very nearly always the same set of patterns, and for one-off ignoring you can just pipe to grep -v.
I think we should still ignore some standard things (like this) by default either way. We already have the config file, so I expect we'd either want to extend that somehow, or link out from that, maybe with an IGNORE_FILE param that points to a gitignore-formatted file, so users can point to .gitignore or .notesignore or wherever. I'm probably not going to jump on that any time soon, but feel free if it'd be useful to you.


Virus Warning

I know its been mentioned before and i have read the discussions here why this is happening but the Virus alert blocks are now much worse with Version 1.6.2. It is now 21 alerts (rising from the previous 15) on VirusTotal. Both Google Chrome and Firefox are specifically blocking the download of both the MSI and ZIP files and with Github warning that IE will soon not be supported, we are rapidly going to lose the capacity to get RDP Wrap to work. Kaspersky, Malwarebytes and many more of the 21 packages actually name the virus software that they think is present in the code. There must be something that you can do to calm down their fears?

They would fear much more if they see issue with that name...
Duplicate of #277 (let's continue discussing there).


very small doc issue

AMICI_guide.pdf
2.1.2 Options
.maxsteps should be 1e4, not 1e-8.
Should noforward and noadjoint be in the table?

this will be update upon the next generation of the documentation


Schematics + documentation : Having outputhash none by default for production build

Hi guys,
I'm new in microfrontends and I find it very cool, so first of all, nice job to make it works with so many frameworks support !
I basically struggled a moment to make my Angular app working in production mode until I find this interesting post : https://github.com/single-spa/single-spa/issues/443
Out of that, why the schematics and/or documentation wouldn't be updated with this --output-hashing none parameter ?
Thanks you again and best regards,
Célian GARCIA

I'm open to changing that. For the recommended setup we usually turn off webpack chunk hashing in favor of using the CI pipeline to insert a hash as a directory, for easier imports with systemjs.
Would gladly accept a PR for this

This was implemented in https://github.com/single-spa/single-spa-angular/pull/169 and released in 4.0.0. See https://github.com/single-spa/single-spa-angular/releases/tag/v4.0.0

Great ! Indeed it's even better to put it in the angular.json config, I'll do so in my projects too, thanks !


ProfileConfigurator: throws error in Interactive Book

@patrickfrohmann The issue occurred only if the author had not added any choices. The H5P question type contract then would cause functions to be called that expected choices to be present. Fixed in https://github.com/codefluegel/h5p-profile-configurator-xr/pull/1


Delete (DataProvider = Pallet) at pallet-staking

Cloud delete DataProvider = Pallet<Self>  at  frame/staking/src/pallet/mod.rs#L86 and  .frame/staking/src/pallet/mod.rs#L93, that i can impl my cutom ElectionProvider

CC @kianenigma @emostov

Can you explain why you need this? There is a reason that we added that constraint, which is explained right above the line:
// we only accept an election provider that has staking as data provider.

All in all, removing the bound might allow for more misconfiguration and footguns to happen.

Sorry, i know how to do this.


Should give warning if user chooses no password

When a new SecretStore is created, it prompts for password, the user is allowed to have no password, but we should emit warning.
PS> Get-SecretInfo
Creating a new SecretStore vault. A password is required by the current store configuration.
Enter password:

Enter password again for verification:

WARNING: The SecretStore vault is configured without a password which is less secure.

We now disallow empty passwords, and emit an error if one is provided (when password authentication is configured).


Cache Organization details

Organizations are unlikely to change during the run of the agent, so it should be fairly safe to keep them cached. Ideally this reduces load on Github for large numbers of repositories in the same organization

I think so - there doesn't seem to be any appetite for the change (anymore), and it's not thoroughly tested enough that we should put it in willy-nilly


feat: use overrides instead of --legacy-peer-deps

Resolves the peer dependency conflict issue caused by #509.

Thanks!


Can you add support for groq.com?

Can you add support for groq.com?
Thanks.

Hi Groq is on our task list but our plan is to implement support for Claude V3 first. Will work on Groq afterwards.

Great!


Comparison with git-annex?

Hi,
This looks interesting.  Having followed Joey Hess's git-annex project for a few years, I wonder how it compares with it.  What do you think?

I have not used git-annex, so the following analysis may be slightly erroneous. I did my best; let me know if you have other questions :)

git-annex uses Git, obviously. It assumes that you are interested in some sort of version control, at least for metadata even if not for file contents.
Madeline has no integration or support whatsoever for Git. It is a tool for moving files between two directory trees and nothing more. This obviously means it is simpler: just an 800-line Python script.

git-annex has support for storing multiple copies of files in different remote storage locations, and keeping track of where they are. I believe you can also have a file both locally and remotely.
Madeline is a tool for moving files between exactly two directory trees and nothing more. The fact that it is disallowed to ever have a copy of the same file in both locations is not a limitation, but an explicit feature.

I think that Madeline would be better than git-annex for the use case of moving directories with a large number of descendent filesystem entries to a remote volume so that local backups with Borg are faster. That is my use case.
If you are already using git-annex for something, though, then git-annex is probably a better tool for it than Madeline.


Use forked react-native-picker-select

Details
Coming from this comment, we forked react-native-picker-select and we should update App to use our fork.
Fixed Issues
$ https://github.com/Expensify/App/issues/8268
Tests

Pull this changes and run:

rm -rf node_modules/
rm -rf package.lock.json
npm i
react-native start --reset-cache

Start the app
Login and navigate to Settings > Preferences
Verify that you can select any value from the dropdown.
Test several dropdown in the app and make sure they all work as intended.

[X] Verify that no errors appear in the JS console

PR Review Checklist

Contributor (PR Author) Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] iOS / native
[x] Android / native
[x] iOS / Safari
[x] Android / Chrome
[x] MacOS / Chrome
[x] MacOS / Desktop

[x] I verified there are no console errors (if there’s a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained “why” the code was doing something instead of only explaining “what” the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named “index.js”. All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose and it is

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn’t already exist
[ ] The style can’t be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.

PR Reviewer Checklist

[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] iOS / native
[ ] Android / native
[ ] iOS / Safari
[ ] Android / Chrome
[ ] MacOS / Chrome
[ ] MacOS / Desktop

[ ] I verified there are no console errors (if there’s a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained “why” the code was doing something instead of only explaining “what” the code was doing.
[x] I verified any copy / text shown in the product was added in all src/languages/* files
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by tagging the marketing team on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named “index.js”. All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] Any functional components have the displayName property
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose and it is broken down into smaller components in order to separate concerns and functions

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn’t already exist
[ ] The style can’t be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.

QA Steps
Same as test steps.

[ ] Verify that no errors appear in the JS console

Screenshots
Web
https://user-images.githubusercontent.com/22219519/159592078-cf992a46-2f63-4e8a-9237-f744278b796d.mov
Mobile Web
https://user-images.githubusercontent.com/22219519/159592109-f76a5790-3fb6-4a51-bc6f-169911c869b3.mov
Desktop
https://user-images.githubusercontent.com/22219519/159592137-ba0d66eb-5600-44b0-989f-f135ccb33b3a.mov
iOS
https://user-images.githubusercontent.com/22219519/159739147-d37f22ef-59fb-4ffb-a622-e48b7cda27d4.mov
Android
https://user-images.githubusercontent.com/22219519/159739093-841a91ac-5a93-4136-9d44-31d73d021dc2.mov

Trying to test this out locally, thanks for your patience! 🙇

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by @robertjchen in version: 1.1.47-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


An error in the source code of the page

Hello,
please check also this issue:

There seems to be something missing in the source code of the page.
Kind regards,
Anne H., QC

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

ID: e1016af4-7bf5-718b-90f1-f26dbc3ad1ea
Version Independent ID: 04f4b8a1-860d-e69c-6540-80f91e6c3708
Content: Tutorial: Analyze Azure HDInsight Apache Spark data with Power BI
Content Source: articles/hdinsight/spark/apache-spark-use-bi-tools.md
Service: hdinsight
GitHub Login: @sreekzz
Microsoft Alias: v-sreeiyer

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

@QueryCoordinator
Thank you for bringing this to our attention.
I've delegated this to content author @sreekzz, who will review it and offer their insightful opinions.


EC issue follow up

Here:

https://github.com/jupyter-governance/ec-team-compass/issues/19

Thanks Eric! I can't be there at this Thursday's Executive Council office hours but if there are any open questions you can feel free to join that call. Otherwise I can take a look at this next Tuesday or Wednesday when I'll be back from some personal time off.

We've now merged the docs working group charter. Thanks everyone!


Setting ifa enabled:false breaks application

Setting ifa enabled to false causes the app to not be able to boot.
// environment.js
ifa: {
  enabled: false,
},

// ember-cli-build.js
fingerprint: {
  enabled: true, // or false; doesn't matter
  generateAssetMap: true
}

Get the following error in the browser when booting the application:
Uncaught (in promise) SyntaxError: Unexpected token _ in JSON at position 0

If I'm reading the code correctly, this is happening because:

The meta placeholder string is appended here: https://github.com/adopted-ember-addons/ember-cli-ifa/blob/master/index.js#L38

but is never replaced because ifa is not set to enabled: https://github.com/adopted-ember-addons/ember-cli-ifa/blob/master/index.js#L61-L63

and then the initializer tries to JSON.parse the bad string here: https://github.com/adopted-ember-addons/ember-cli-ifa/blob/master/addon/utils/get-asset-map-data.js#L17

Hi @danwenzel,
I came across your issue. I'm not sure if you have it resolved yet?
IIUC, if this content of the meta tag was actually <meta name="ember-cli-ifa:assetMap"> then the value of metaTag.content in https://github.com/adopted-ember-addons/ember-cli-ifa/blob/master/addon/utils/get-asset-map-data.js would be an empty string and JSON.parse would not have been called.
The error message of Unexpected _ token seems to suggest that the meta tag was containing the placeholder value ('__ember-cli-ifa__AssetMapPlaceholder__'), which is defined here: https://github.com/adopted-ember-addons/ember-cli-ifa/blob/master/index.js#L6
I'm curious whether you are having this issue in production or in development and whether the setting
// environment.js
ifa: {
  enabled: false,
},

is applied in production or in development?

Thanks for the nudge, @xuanluong ! It looks like this issue was resolved via v0.10.0.  Closing


lammps Installation problem❓ [QUESTION]

I am able install nequip, lammps and torch separately.
when i try to patch and reinstall the lammps i got the following error.
how to solve it ?
CMake Error in CMakeLists.txt:
Target "lammps" contains relative path in its
INTERFACE_INCLUDE_DIRECTORIES:
"MKL_INCLUDE_DIR-NOTFOUND"

CMake Error in CMakeLists.txt:
Target "lammps" contains relative path in its
INTERFACE_INCLUDE_DIRECTORIES:
"MKL_INCLUDE_DIR-NOTFOUND"

CMake Error in CMakeLists.txt:
Imported target "torch" includes non-existent path
"MKL_INCLUDE_DIR-NOTFOUND"

in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

The path was deleted, renamed, or moved to another location.

An install or uninstall procedure did not complete successfully.

The installation package was faulty and references files it does not
provide.

CMake Error in CMakeLists.txt:
Imported target "torch" includes non-existent path
"MKL_INCLUDE_DIR-NOTFOUND"

in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

The path was deleted, renamed, or moved to another location.

An install or uninstall procedure did not complete successfully.

The installation package was faulty and references files it does not
provide.

-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.

Closing this since Deleep in personal communication reported this was not an issue anymore.

Hi @deleep225 @simonbatzner, Could any of you weigh in about the reasons/solutions for this? I think I am having the exact same issue on Mac. It seems it misses some MKL libs but I am not sure. Thanks!

Hi Chenru,
you need to install mkl libraries.
After installing my libraries were installed in the path below.
-DMKL_INCLUDE_DIR=/usr/include/
command for installation
cmake ../cmake -DCMAKE_PREFIX_PATH=python -c 'import torch;print(torch.utils.cmake_prefix_path)' -DMKL_INCLUDE_DIR=/usr/include/
On Tue, Feb 8, 2022 at 6:47 PM Chenru Duan @.***> wrote:

Hi @deleep225 https://github.com/deleep225 @simonbatzner
https://github.com/simonbatzner, Could any of you weigh in about the
reasons/solutions for this? I think I am having the exact same issue on
Mac. It seems it misses some MKL libs but I am not sure. Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/mir-group/nequip/issues/151#issuecomment-1033287974,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKLUWCWE5PFWP5KDKOX7NLDU2HISXANCNFSM5NUVKPLA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @chenruduan, yes, just like @deleep225 said, you need to install the MKL libraries, on my system it was
conda install mkl-include

and then set it in the cmake command, so first get the dir where mkl.h lives:
find $HOME -name  mkl.h

and then set:
cmake ../cmake -DCMAKE_PREFIX_PATH=`python -c 'import torch;print(torch.utils.cmake_prefix_path)'` -DMKL_INCLUDE_DIR=path/to/that/dir/

Let me know if that works.

@simonbatzner @deleep225 Thank you both! With that, I got the configuration step passed!


Adding Corolla FingerPrint

Description Adding a Corolla Cross Finger Print
Verification Test on my car and run python -m compileall value.py to verifcation crash

I will close pull request because i dont create unit tests

"Verification Test on my car and run python -m compileall value.py to verifcation crash"
There were a couple improper indentations in your commit.


Make pub run faster

"pub run" is currently very slow when running local executables. We should do what we can to mitigate this, including:
* Precompiling immutable transformers to snapshots on "pub get"
* Precompiling immutable dependencies to source
* Lazily load assets from untransformed dependencies
* Don't load transformers at all if we can prove that they won't be used
* Stop rewriting package imports (blocked on issue #12474)
* Load files directly rather than over HTTP (blocked on issue #16368)

This issue has been moved to dart-lang/pub#1121.


goog.Uri resolve decodes query data

See https://github.com/google/closure-library/pull/434 for context

@irock I ran all internal tests against this and there were multiple failures. As expected, people are relying on the encoding. We can leave this issue open to track the issue, but I'm not sure it's worth the effort to land the fix. I'd recommend just working around it in your code.

This issue is being closed as a preparation step before archiving the repository.  See the README for more detail.


ListItem: Fix NPE in getText() and reuse text element for setText()

Sure I'll get back with a new version. Also I'm not so sure about getText() returning null if empty value, do you have any policies for the project for handling nulls? Maybe "" is better, or if null use some kind of @Nullable annotation.

I am fine with that. Thanks!


Add com.snowplowanalytics.snowplow.badrows/bq_repeater_parsing_error/jsonschema/1-0-0

Closing in favor of https://github.com/snowplow/iglu-central/issues/1020


Disclosing critical information stored in $_SERVER

Hi,
Exception handling tools such as filp/whoops are dumping $_SERVER, possibly disclosing critical information put there by phpdotenv. This is a security issue that could easily be fixed. What's the point in having this values in $_SERVER in the first place? If you setup environment variables properly they are not polluting $_SERVER. More over, environment variables should be read from $_ENV or obtained using getenv(), not $_SERVER although it may seem handy.
As an example when a run ICANBOOGIE_INSTANCE=dev php -S localhost:8000, ICANBOOGIE_INSTANCE is not in $_SERVER but can be read from $_ENV or obtained using getenv().
Your tool is introducing a double standard.
What do you think?

I work on a related project have a few thoughts on this:

You should never dump errors like whoops does in production. Definitely in development, maybe staging, never production.
Many error reporting tools allow you to whitelist/blacklist variables from being output. I know sentry does, and whoops should support the same. CakePHP has blanked out anything it detects as a password field and has done so for a while, and I assume other frameworks do as well.
phpdotenv should probably not automatically output vars, and allow developers the option of configuring how they want to output them. That's probably a BC-break, but would allow you to bypass this sort of issue.
Even if you don't use $_SERVER for env vars, it's likely your tool will try $_ENV, defined constants, or any number of other options that a tool like dotenv might output. Again, allowing configurability here is useful, but there isn't a "sane" default other than forcing the developer to make a conscious decision.
A security notice in the readme is probably a great idea.

Don't know how @vlucas feels about this, but those are my thoughts.

@olvlvl Tools like whoops only prints exceptions stack traces and dumps superglobals when in development mode. Even if phpdotenv excludes variables from $_SERVER, whoops still dumps $_ENV in development mode, so it likely would not make a difference.
That said, phpdotenv could definitely provide an option in a non BC-breaking way that would not write to $_SERVER.

@vlucas +1 for phpdotenv could definitely provide an option in a non BC-breaking way that would not write to $_SERVER if that is a major concern of yours. It would be great to see!
I do not print debugging information to the screen in Production, however, I do like to log $_SERVER settings when I catch exceptions. If I do that when using phpdotenv, I'm now printing all my creds to my logs, which are being transmitted out to 3rd party sites like LogEntries and PaperTrail.

From my point of view, it would definitely be an improvement if $_SERVER was not polluted with credentials.

+1

https://github.com/vlucas/phpdotenv/issues/76#issuecomment-167806230


Improved scanning

Proposed solution for #15
The regular expression is a bit complicated, but to break it down into human terms, it matches matching quotes (either ' or ", but not both unless the other is inside the string), followed by a pipe, followed by _, __, transRaw, transRawPlural, or localeUrl, optionally followed by parentheses that must match in number (i.e. (() would not match, but (()) would).
I created a unit test, but the ones currently there do not pass on a fresh install:
$ php artisan winter:test -p Winter.Translate
Running tests for plugin: Winter.Translate
PHPUnit 9.5.10 by Sebastian Bergmann and contributors.

.EEE.......EE............                                         25 / 25 (100%)

You can test the regex here as well: https://regex101.com/r/tBvGae/1/

@multiwebinc also make sure the regex matches when the filter is in a chain.
e.g.  {{ "my string" | _ | default("hello world") }}

@mjauvin Check now.
https://regex101.com/r/tBvGae/2

Ok, I kept seeing things that would complicate the regex even more (e.g. nested strings within another function, escaped quotes within the string, translatable strings in concatenation, etc), so I figured out how to use the built-in Twig functions instead of regular expressions.

I added stripslashes() because when you have a tag like {{ 'That\'s nice'|_ }}, the translator will literally see That\'s nice as the string. Twig handles that correctly and doesn't output the slash, but it doesn't make sense to store the slashes in the database.

@multiwebinc that's awesome! Especially using Twig instead of Regex, great idea!
Did you add a unit test for the stripslashes usage?

@LukeTowers Take a look now.

The proposed solution looks very interesting, I'm just worried about its efficiency. Can you run comparison between the previous code and this one against a big enough number of pages with many translation strings?

@mjauvin I assume that scanning for translatable strings would mostly be done only occasionally, like when you add a new page, so I don't think the speed is that relevant unless we're seeing a massive difference between the two, like making the server hang for several seconds or something that could somehow be used as a DDoS if users were able to upload their own content to the server.
However, I did a test as you requested. I used https://www.lipsum.com/ to generate "150 paragraphs, 13245 words, 89523 bytes of Lorem Ipsum". Then wrapped every 3rd paragraph like {{ '$paragraph'|_ }}, and looped the scanner 1000 times, and on my relatively low-end desktop computer, it took 1.897 seconds using Twig and 0.487 seconds with regular expressions (using the regex from this commit.
Here's my code in case you want to review it:
    public function testLoremIpsum()
    {
        $split = explode("\n", $this->loremIpsum);

        $string_to_test = '';
        foreach ($split as $key => $value) {
            if ($key %3 === 0 && strlen(trim($value))) {
                $string_to_test .= "{{ '$value'|_ }}\n";
            }
            else {
                $string_to_test .= $value . "\n";
            }
        }

        $start = microtime(true);
        $scanner = new MessageScanner();
        for ($i=0; $i<1000; $i++) {
            $scanner->getMessages($string_to_test);
        }
        $elapsed_twig = microtime(true) - $start;

        $start = microtime(true);
        for ($i=0; $i<1000; $i++) {
            $this->getMessagesWithRegex($string_to_test);
        }
        $elapsed_regex = microtime(true) - $start;

        dd($elapsed_twig, $elapsed_regex);
    }

    protected function getMessagesWithRegex($content)
    {
        $regex = '#{{\s*(["\'])((?:(?:(?!\1)).)+)\1\s*[|]\s*(?:_{1,2}|transRaw(?:Plural)?|localeUrl)\s*(?:\((?:[^)(]+|\((?:[^)(]+|\([^)(]*\))*\))*\))?\s*(?:[|](?:.*))?}}#U';
        preg_match_all($regex, $content, $match);
        return $match[2] ?? [];
    }

As we can see, using Twig is about 3-4 times slower than regex, which is probably in the range of what I would have expected. I would consider ~2 seconds to scan a relatively large page 1000 times to be within reason, especially considering the increased scanner accuracy over regular expressions.
For a real-world example, on the site I am currently working on, I scanned 45 pages in my template using the Twig scanner from within the backend, which found 433 translatable strings, and the request took 449 ms to complete. Of course, this is not simply scanning a string stored in memory like in the example above, but having to load up Laravel, October, and all dependencies, etc, then recurse through the theme directory, read the files, and then scan them for Twig strings, so the bottleneck likely isn't even the scanner in my case.

fine with me then.

@multiwebinc thanks for all your hard work on this, it's fantastic!

@LukeTowers My pleasure. Glad I could help.


Depend on individual Groovy libraries instead of groovy-all

Gradle used to depend on groovy-all.jar that contained everything from Groovy, including all its shaded third-party dependencies. Gradle used to expose this JAR as part of its API, too.
Since version 2.5, Groovy does not publish such a JAR anymore, and instead provides only a POM that declares a dependent on most (but not all) Groovy JARs.
For Gradle 5.0 we tried to switch to the new approach, i.e. to make Gradle depend on individual Groovy JARs (see https://github.com/gradle/gradle/pull/6324). However, this has proven difficult.
Ultimately, we chose to go with a workaround, and reproduce a groovy-all.jar of sorts: with some more code from Groovy than the official groovy-all.pom would declare, and without any of the third-party dependencies. (See https://github.com/gradle/gradle-groovy-all.) This is a hack that got us onto Groovy 2.5, but we should do better.
This issue is about cleaning up this mess, and getting us to depend on actual Groovy libs and their dependencies.
Some of the problems encountered in https://github.com/gradle/gradle/pull/6324:

[ ] with many new libraries on the classpath we had issues with forking workers on Windows because of command-line length reaching 32 KB

This is a pre-requisite to upgrading to Gradle 3.0, so let's keep this open.

This has been solved for Gradle 7.0 by #16193.

Yay! \o/


Hang in wait_all() in distributed run

Jan-Tobias Sohns wrote:
I further simplified my code, to extract my problem. I run this code 8
nodes of our cluster with 1 locality per node.
#include <hpx/hpx_init.hpp>
#include <hpx/hpx.hpp>
#include <hpx/include/actions.hpp>
#include <hpx/runtime/serialization/serialize.hpp>
#include <hpx/include/iostreams.hpp>

#include <math.h>
#include <vector>
#include <list>
#include <set>
#include <stdio.h>
#include <stdlib.h>
#include <iostream>

#include <boost/ref.hpp>
#include <boost/format.hpp>
#include <boost/thread/locks.hpp>
#include <boost/serialization/vector.hpp>

void out(std::vector<uint> vec)
{
     hpx::cout << "out called " << hpx::find_here() << std::endl <<
hpx::flush;
}
HPX_PLAIN_ACTION(out, out_action);

int main(int argc, char* argv[])
{
     // Initialize and run HPX.
     return hpx::init(argc, argv);
}

int hpx_main(boost::program_options::variables_map& vm)
{
     // find locality info
     std::vector<hpx::naming::id_type> locs = hpx::find_all_localities();
     uint locid = hpx::get_locality_id();
     // create data
     std::vector<uint> vec;
     for (unsigned long j=0; j < 300000; j++)
     {
         vec.push_back(1);
     }
     // send out data
     for (uint j = 0; j < 8; j++)
     {
         std::vector<hpx::future<void> > fut1;
         for (uint i = 0; i < locs.size(); i++)
         {
             typedef out_action out_act;
             fut1.push_back(hpx::async<out_act>(locs.at(i), vec));
             hpx::cout << "Scheduled out to " << i+1 << std::endl <<
hpx::flush;
         }
         wait_all(fut1);
         hpx::cout << j+1 << ". round finished " << std::endl << hpx::flush;
     }
     hpx::cout << "program finished!!!" << std::endl << hpx::flush;
     return hpx::finalize();
}

And this is my output:
Scheduled out to 1
out called {0000000300000000,<PHONE_NUMBER>000000}
out called {0000000500000000,<PHONE_NUMBER>000000}
Scheduled out to 2
Scheduled out to 3
Scheduled out to 4
Scheduled out to 5
Scheduled out to 6
Scheduled out to 7
Scheduled out to 8
out called {0000000400000000,<PHONE_NUMBER>000000}
out called {0000000100000000,<PHONE_NUMBER>000000}
out called {0000000800000000,<PHONE_NUMBER>000000}
out called {0000000600000000,<PHONE_NUMBER>000000}
out called {0000000700000000,<PHONE_NUMBER>000000}
out called {0000000200000000,<PHONE_NUMBER>000000}
1. round finished
Scheduled out to 1
Scheduled out to 2
Scheduled out to 3
Scheduled out to 4
Scheduled out to 5
Scheduled out to 6
Scheduled out to 7
Scheduled out to 8
out called {0000000100000000,<PHONE_NUMBER>000000}

then i get stuck in an endless loop until my job times out.
This same code runs completely if i take 8 localities on a single node,
or decrease my "vec"-size to 3000.
I need to send data of this size, because I'm trying to do image
compositing.

Our regression tests show that the code you supplied runs fine on master (see: here).

I could not reproduce this issue on supermic using multiple MPI versions
(mvapich2/2.0 and impi/<IP_ADDRESS>) in debug and release compiled with
intel compiler version 15.0.0 and boost 1.55.0.

Tim Biedert wrote:

Now I have “good” news:  I have recompiled HPX 0.9.12 (git) using OpenMPI 1.8.5 (instead of Intel MPI 2016), and now the example seems to work as expected.  As Jan already said, using 0.9.12 with Intel MPI 2016 before did not resolve the issue. So the problem seems to be MPI related.

Closing this...


[5.0] Add "whereNot" To Collection

Replaces #7177.

I commented on the other PR, and I'll put that comment here too:
All 4 of these methods (and more) can be handled by this single method.
...and with a saner interface if you ask me.
@taylorotwell any chance you'd reconsider on that one?

I think we should re-consider that and do it in 5.1. :)

@GrahamCampbell it is a backwards compatible change, so we can do it in 5.0.

Oh right. :0

Looks, like this commit didn't make it into 5.0, right? There is no whereNot in the current 5.3.

@FractalizeR in 5.3, you can do where('foo', '!=', 'bar')

Yeah, I know. Just with WhereNot it's more declarative.

@FractalizeR  "where not foo bar" is more intuitive than "where foo != bar"???
🤔


Add patch for rocm_bf16

https://github.com/vllm-project/vllm/pull/2790/files

ROCm 6.x resolved it.
https://github.com/supersonictw/uruha/commit/c684acc48f28612c75faa5d631205f83fa11f5dd


rkt: add a flag to enable rkt support

Kubernetes v1.3 will have full rkt support; see the rktnetes v1.3 milestone.
We need to make this as easy to enable as the Calico support or anything else. It should just be a single configuration option on vagrant, aws, etc.
We should be able to start experimenting with this ASAP as much of the support is in k8s master. So, we should start tracking k8s v1.3 pre-releases and getting this into shape.

Hi,
This issue just became even more important as it is a hard requirement for Stackanetes. Fully supporting OpenStack services on top of Rktnetes, following the coreos-kubernetes docs is expected by the end of July.
Right now, we can't simply swap docker with rkt on a Kubernetes worker node because rkt isn't available in hyperkube and thus, the kuberlet-wrapper can't run kubelet in rkt-fly. I understand that @pbx0 has started some work around that [1] but faced some issues with rkt (permissions) while trying to run kube-proxy [2]. Intel apparently suffers from the same issue since April [3]. It has been worked around by making it a systemd service though. I tried quickly to run the kubelet directly on CoreOS 1068, without kubelet-wrapper, but it simply won't run: breaking in the very first steps (getting rkt's version). Not exactly sure yet if the version is too old or if this is an actual bug - I am sure @yifan-gu knows.
What's the current status on this? Is there anyone working on this actively? I believe that it is quite important to get that done ASAP as it will significantly increase the user base of rktnetes and rkt - and thus, we'll get a lot more feedbacks.
It is also blocking our very first tasks on Stackanetes as it is complicated to run any k8s manifests with rktnetes. Is there any recommendation right now?
$ /usr/bin/kubelet \
>   --container-runtime=rkt \
>   --api-servers=https://XXX.YYY.ZZZZ.WWW \
>   --network-plugin-dir=/etc/kubernetes/cni/net.d \
>   --network-plugin= \
>   --register-node=true \
>   --allow-privileged=true \
>   --config=/etc/kubernetes/manifests \
>   --hostname-override=XXX.YYY.ZZZZ.WWW \
>   --cluster-dns=<IP_ADDRESS> \
>   --cluster-domain=cluster.local \
>   --kubeconfig=/etc/kubernetes/worker-kubeconfig.yaml \
>   --tls-cert-file=/etc/kubernetes/ssl/worker.pem \
>   --tls-private-key-file=/etc/kubernetes/ssl/worker-key.pem

[...]

failed to create kubelet: failed to run [version]: exit status 2

stdout: NAME:
	version - Print the version and exit

USAGE:
	rkt version

DESCRIPTION:
	Print the version of rkt, and various build and configuration information.

GLOBAL OPTIONS:
      --debug[=false]			print out more debug information to stderr
      --dir=/var/lib/rkt		rkt data directory
      --insecure-options=none		comma-separated list of security features to disable. Allowed values: "none", "image", "tls", "ondisk", "http", "pubkey", "all"
      --local-config=/etc/rkt		local configuration directory
      --system-config=/usr/lib/rkt	system configuration directory
      --trust-keys-from-https[=false]	automatically trust gpg keys fetched from https
      --user-config=			user configuration directory

stderr: Error: unknown flag: --insecure-skip-verify

@Quentin-M The kubelet baked into the CoreOS image is deprecated and too old to use. See:  https://groups.google.com/forum/#!topic/coreos-dev/DJeuZZeqz1s
$ kubelet --version=true
Kubernetes v1.1.2+1abf20d

I have rktnetes w/ kubelet-wrapper mostly working but still in the process of testing it and getting to the point where I can just make it a flag you set in this repo. Its definitely high-priority over here to have this before the 1.3 release. rkt 1.9 will likely be required and I still need to revisit the kube-proxy problem. Right now I also run it just as a systemd unit without rkt.
If you can wait a few more days I can help you setup rktnetes with kubelet-wrapper. Right now you'll at minimum need this to be fixed in rkt: https://github.com/coreos/rkt/issues/2792

@pbx0 Thank you so much for your answer and very valuable information. I'd love your help and would be glad to help you test this too! Ping me anytime (incl. weekends too).

closed in https://github.com/coreos/coreos-kubernetes/pull/551