Project JEDI issue - jvcl

I found issue in JvDesktopAlertStack,but cannot create account in https://issuetracker.delphi-jedi.org/signup_page.php (create but confirm email not received).
How can report this issue?
procedure TJvDesktopAlertStack.UpdatePositions
ignore dapMainFormBottomRight,dapMainFormBottomLeft etc,specifically
on MultiMonitor.

I'll have a look at the email issue, but in the meantime, could you create a test application as a GIST?
Or even better, if you have a suggested fix, create a pull request at github.

Related

Gitlab Issues Webhook Information

So, i have a public project that allows other people in my organization to open issues. I would like labels applied to each issue when it is opened. I have tried the /label method and that only works when the person opens the issue is a part of the project. It seems that Gitlab does not allow this as per this issue: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73710
So, to get around this, I have set up a webhook that triggers a pipeline, parses some text at the end of the issue description (like ISS001)and then uses the Issues API to set the labels.
I have two questions that I can't seem to find a concrete answer to.
In the Webhook payload, does any of that information tell you what template was used? Looking through the payload, I cannot see any indication of that... which is why I am parsing the text at the bottom. In the object_attributes portion of the payload I see:
"id": <What is this?>,
"iid": <Issue Id>,
iid is the issue id, but what is id? I can't find that anywhere.
Is there a way to configure the cicd pipeline to only trigger on issue CREATE.. not update, close, reopen? I have it set as:
only:
- trigger
So no other actions trigger the pipeline but there are a TON of superfluous pipeline runs.
Thank you.

Am I still vulnerable to LightShot security issue even if I only use the COPY button?

It's been known for a while that LightShot has privacy issues as discussed here
but most articles discussing the technicalities mention only about the Upload, Save, or Share.
Will clicking only on the COPY button still expose me to data / screen-scrapers?
I tried mailing LightShot, but I don't think I'll get a response since mailer daemon replied with a full inbox status.

Gmail API Watch Request Not Filtering Label IDs

Issue
Trying to get the Gmail API to send only new messages to Cloud Pub/Sub by using the Gmail APIs Watch function but when setting the labelIds in order to filter to just INBOX, i am still notified of all changes, files sent, drafts etc.
I've looked online and can see that there are people that are experiencing this issue and there is even a bug out for it https://issuetracker.google.com/issues/36759803.
But i find it kind of odd that the entire feature of filtering just doesn't work and its been an issue for 5 years according to the bug report. Makes me think its just me that is doing something wrong. Would be cool to hear from anyone that has got this to work.
Where im at
I'm using the Gmail API, trying to get my Gmail account to publish messages to Cloud Pub/Sub. I've managed to do this however im trying to filter what i get notifications for to just new messages. This is where i have a problem.
According to this Gmail API documentation, it appears all i have to call is the code below and that should be that. I will add however, that im calling the Kotlin equivalent, but i don't think this should matter.
request = {
'labelIds': ['INBOX'],
'topicName': 'projects/myproject/topics/mytopic'
}
gmail.users().watch(userId='me', body=request).execute()
What im calling:
val request = WatchRequest().apply {
labelIds = listOf("INBOX")
topicName = "projects/myproject/topics/mytopic"
}
gmail.users().watch("me", request).execute()
Other things ive tried
I have tried adding labelFilterAction = Include and other variations but they all seem to be ignored.
After trying the ideas listed by ziganotschka, I'm more confident that the issue is not related to specific client libraries.
I managed to speak to someone at Google who in turn contacted the G-mail API team. They said they were aware that this is an issue, that it has been an issue since 2015 and was most likely caused by a change they made back then.
A ticket is still open, but doesn't look like it will be fixed.
Perform the following trouble-shooting actions
Provide a request body including labelIds, labelFilterAction AND topicName as specified here
Try the label "UNREAD" instead of "INBOX"
To discart Kotlin implementation related issues, test your request in a programming language that allows you to pass the request as a JSON body in exactly the same way as specified in the documentation.

User account email verification links not working

I am having a lot of troubles getting verification emails to work, when a user signs up with parse-server (using MailGun & Heroku).
The verification link sent to the user has this form:
https://myapp.herokuapp.com/apps/.............
but it does not work/
I get this, when clicking it:
Cannot GET /apps/.......
And even if I type only this in the web browser:
https://myapp.herokuapp.com/apps/
I still get this:
Cannot GET /apps/
At one point I was suspecting I could have made some confusion between parse-server-mailgun and parse-server-simple-mailgun-adapter (I am in fact not fully aware of the difference between the two), so I tried both but I still got the same kind of error.
Since, I can reach the point where a user account is actually created and a verification email is sent, I suppose I must have only made some detail mistake in my settings; but I can't see where. Any help or relevant hint from some experienced person would be highly apreciated.
In case someone think I should share some code because the explanation above is not enough, please tell me what you need to know to clarifly my point. And I will provide the necessary information.
You should see your publicServerURL to https://myapp.heroku.com/parse

GItlab does not send email on new issue

GItlab does not send email on new issue, but do it for issue closing and comments. How can I enable it?
Any notification rule issue on GitLab are referenced ("featured") in Issue 2669.
A redesign is in progress (issue 1808), but not there yet.
Proposals already exists (issue 2466, issue 1448 ), where you can select the people in a team you want to be notified:
That feature request is managed here: "Improve email/notification system".

Resources