Finally! I've been waiting for this plugin 💛

I've tried a lot of AI plugins, here's a reddit post where I look at a dozen of them. All but Copilot I ended up removing after a while. This plugin I've had for a week and I'm only getting more excited about its integration in my workflow.
Thank you, please keep up the good work! 🙏

same for me, it saved me a aweful lot of time.
thx!

@alextes is there a reason you archived the reddit post? i hope you haven't switched to cursor 🤣 i watched the cursor intro video you linked in the post and really liked it. we need to help make gp.nvim better to come as close as possible to cursor, or even surpass it ;-) maybe you can at least link gp.nvim in the post, so that some more traffic will be generated here, which maybe could help improve the plugin. i tried about 50-70% of the plugins you mentioned and ended up with gp.nvim :-)

@divramod archiving is automatic 😒 . In retrospect reddit is not a good place to make an overview like that exactly because a post is forced to decay. Still, I was allowed to edit the post still so done! Highly positive entry added.


DateRangePicker behaving weirdly

When playing around with the date range picker i noticed some issues. E.g. if you pick a date that is near the end or the beginning of the month it shows up twice (as seen in the picture). This should not happen and is very confusing at first

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.


"tactile_sensor_2" has IPC component but no render component

when I ran
python peg_insertion_sim_evaluation.py --key=1
and I set
GUI=True
There are some errors:
NFO - Entity "tactile_sensor_2" has IPC component but no render component (user_utils.py:72)
INFO - Entity "tactile_sensor_1" has IPC component but no render component (user_utils.py:72)
INFO - Entity "tactile_sensor_2" has IPC component but no render component (user_utils.py:72)
INFO - Entity "tactile_sensor_1" has IPC component but no render component (user_utils.py:72)
INFO - Entity "tactile_sensor_2" has IPC component but no render component (user_utils.py:72)
INFO - Entity "tactile_sensor_1" has IPC component but no render component (user_utils.py:72)
INFO - Entity "tactile_sensor_2" has IPC component but no render component (user_utils.py:72)
INFO - Entity "tactile_sensor_1" has IPC component but no render component (user_utils.py:72)
INFO - Entity "tactile_sensor_2" has IPC component but no render component (user_utils.py:72)

However, when I set
GUI=False
then, I ran
python peg_insertion_sim_evaluation.py --key=1
The program can correctly run

Thank you for your question. This is not a problem.You can ignore it. You need to press the c key to start the peg moving. Then the content of the --key parameter is the encrypted key that was sent to you when you registered via email.


JSHint and JSCS

Builds on top of #37

@mike-north :+1:  I merged #37 first, rebase if you don't mind :)

@kategengler done


fix typo error

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Appium?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have read the CONTRIBUTING doc
[ ] I have signed the CLA
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

LGTM


Continue to add another employee will prompt

WHEN I choose to continue
THEN I am prompted to add a new employee

wrapped this up with the previous issue


Debugging browser app fails in Avalonia 11.0.7

Describe the bug
Not sure but the underlying error seems to be a mono_assert that kills the runtime because of a missing function, InputHelper.subscribeVisibilityChange.
To Reproduce
mkdir sample
cd sample
dotnet new avalonia.xplat
Change to 11.0.7 in Directory.build.props
Open sln in VS
Change startup project to sample.Browser
Debug sample
The splash screen remains indefinitely and the following is written to the console:
[object Object]
If you inspect the exception object in the browser debugger it shows that the application was aborted due to an assert in mono_wasm_lookup_function.
InputHelper.subsccribeVisiblityChange must be a function but was
Expected behavior
A Welcome to Avalonia! message in the browser.
Environment
.NET 8.0
Debugging with Visual Studio 2022 17.8.4
Edge 121.0.2277.83
It works fine outside of the debugger or if I revert to 11.0.6.

Reset your browser cache for the specific web site.
Also: https://github.com/dotnet/runtime/issues/97097

Thanks, I thought I tried that but apparently not since when I tried now it worked.


fix: card-mod not working

Hey,
I've created this pull request to fix the functionality issue with the card-mod as mentioned in issue #234.
I've added style and card_mod option properties. These are required to consist in config object for card-mod to read them and create styles.
Please review and provide feedback.
And thank you for your amazing work.

So I pushed changes to pass the remaining properties of config using the spread operator and I've tested it and it's working.

You're totally right. Thank you for code reviewing, this operator is completely new for me.


chore: security update

:tada: This PR is included in version 1.15.6-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


redirect to /welcome behind a reverse proxy doesn't work

Describe the bug
We use labelstudio behind traefik and rewrite the path. So users go to /prefix/* When there are no tasks, the home page redirects to /welcome not /prefix/welcome
To Reproduce
Steps to reproduce the behavior:

setup like https://github.com/heartexlabs/label-studio/issues/273
have no tasks
go to the base url

Expected behavior
should redirect to /prefix/welcome
Environment (please complete the following information):

OS: aws-linux (eks 1.14)
Browser: all

Should be an easy fix.
just need to add a configuration for the redirect
https://github.com/heartexlabs/label-studio/blob/0c686176510c91a2c7ec7bc7ed0a77af964f9624/label_studio/server.py#L169

Can you try this PR https://github.com/heartexlabs/label-studio/pull/350 ?

I hope you found my fixes are working :-)

It does work. Thank you.
I work with Adam Guymon, he has been communicating with you on your slack channel about a few requests. Thank you for being responsive there.


[Account Control] Limits of engagement and avoiding soft-bans

Hi @shine-jayakumar — I have used your tool for weeks now, amazing results and latest updates just make it even better. The biggest problem is controlling the soft-bans that IG puts for 24h-48h when overusing it.
I took time to research and test it personally and here is some information that could be useful:
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
IG API Limits:
//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
***** Avoid using Instagram on multiple devices simultaneously *****
Post Likes: 1,000 likes /day
Maximum Likes: 350 likes /hour
Story views: 1,000-1500 /day
Like/react to stories: 600-800 /day
Like comments: No official limit, keep number below 2,000
Profile Views: 800 /day
Maximum Profile Views: 140 /hour
Now, under those numbers I have avoided softbans so far. There are a few tricks, like not using more than one device at the time that are very important. The other most popular softban is based on profile views, not really on Likes, if the script visits too many profiles +140-150 per hour it could cause a softban.
I suggest adding a new module for account control, with this limits on the configuration/profile file. Ideally, save locally the engagement/actions made so if the script runs multiple times the actions are recorded and keep the account safe.

Added in v.3.0.4


slang, catch_2_3: upgrade

I can unbundle these, if needed.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

See https://github.com/NixOS/nixpkgs/pull/292709 for the catch2_3 update. We need to make sure it builds on Darwin.

Why so many rebuilds?

See #292709 for the catch2_3 update. We need to make sure it builds on Darwin.

Good to know. I updated catch2_3 because the sv-lang 6.0 CMakeLists.txt file specifies it, but apparently 3.5.2 works still works just fine. Therefore, I've dropped this patch from the PR.

Why so many rebuilds?

🤷🏻 More things transitively use catch2_3 than you might expect, I guess. I didn't think it would be so big, either.

Superseded by #355401.


Add Vertex to Ecosystem page

What changed? Why?
ecosystem.json was updated to include the relevant data and a logo was added to public/images/partners.
Notes to reviewers
This information was also previously submitted via the legacy Google Forms process.
Also I originally opened a PR here but it was closed due to a perceived lack of ToS, noted in this comment.
However, as I stated in my reply, once the user connects their wallet, they are presented with a ToS modal, which also links out to our full ToS. Further, the full ToS is also available as a link in the page's navbar.

Ex. of ToS modal

Ex. of ToS link in navbar

Does that suffice?

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

@tmns
Hello, thanks for the update and work on this. For the requirement, unfortunately, no, it would need to be visible and accessible on the page that is being linked to here in this PR:

Hey @wbnns thanks for the update. So just to be clear, being a link within the nav dropdown doesn't work, it needs to be visible without any interaction from the user?

We are adding Vertex in #1387 👍


[$250] Web - Chat - Error in JS console when right-clicking in the app

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Found when validating PR : https://github.com/Expensify/App/pull/37316
Version Number: v1.4.48-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:

Go to any chat with some attachments
Open JS console and refresh the page
Right click on any attachment
Refresh the page to clear your console
Right-click on a chat message
Observe the console error
Refresh again
Right-click on a chat row in the LHN
Observe the console error

Expected Result:
No errors appear in the JS console.
Actual Result:
Error in JS console when right-clicking.
Error: 'Cannot record touch end without a touch start. Source.
Workaround:
N/A, right-clicking still works functionally.
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/2df5ee67-9d2a-46fd-9d53-eda93192982f

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0122ffd00715c18b6e
Upwork Job ID:<PHONE_NUMBER>749649408
Last Price Increase: 2024-03-07
Automatic offers:

dukenv0307 | Contributor | 0

@trjExpensify I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors.
We think that this bug might be related to #vip-vsb
CC @quinthar

Hey!

#vip-vsb is correct as a chat bug. I can reproduce it reliably.
It doesn't seem to be causing a functional issue. You can still right-click, so it has no impact on usability.
Ideally we don't have JS warnings in the console though. This warning isn't limited to right-clicking attachments, but rather anywhere you right-click in the app (i.e a chat message, LHN chat row etc).
Looks like it's something to do with the recordTouchEnd function and RNW, so I don't see why it can't be external.

CC: @mountiny quick hip check. Shall we proceed to find a fix for this? I'm not aware of a logical reason for not recording a touch start with the right-click action.

I agree with the assessment, I think its best to get rid of the error so I would export this issue for contributors for $250

Sounds good!

What do you think, @mananjadhav?

While @dukenv0307's proposal looks promising, I first tried reproducing it and I can't. I tried on v1.4.50-2, MacOS Chrome and Safari both.
https://github.com/Expensify/App/assets/3069065/d8276d2f-208d-4412-ab70-07e7725b681e

Sorry my bad I was checking the Errors only and not warnings.

additionally check isPrimaryPointerDown(domEvent) only when updating the trackedTouchCount here so it shouldn't affect the recordTouchTrack operation

I am inclined to have this solution, but I can see isPrimaryPointerDown is used only at one place so we might just update the method to isPrimaryOrSecondaryPointerDown.
Going to take a feedback from internal engineer. But @dukenv0307's proposal/alternative works for me.
🎀 👀 🎀 C+ reviewed

I think renaming it to isPrimaryOrSecondaryPointerDown is fine. I've assigned @dukenv0307.

Cool, looking forward to the PR, @dukenv0307!

PR is currently being tested on staging

This was deployed on production 4 days ago but the payout date wasn't updated.

@trjExpensify This is ready for payout.
We don't have any offending PR and we don't need any regression test for this.

@trjExpensify Can you help here?

Yup! Payment summary as follows:

$250 to @dukenv0307 for the fix (Paid!)
$250 to @mananjadhav for the C+ review (feel free to submit a request!)

Thanks!

$250 approved for @mananjadhav


Why Flutter Plugin are not supported Android Studio3.2?

Excuse me. I'm using the Android Studio3.2，but the Flutter Plugin isn't supported Android Studio3.2?
Tips like following:
Unsupported Android Studio version
Canary versions of Android Studio are not supported by the Flutter Plugin.
This is a terriable bug.May fix it quickly.

Not a bug.  Canary versions are for preview and used to test to find out bugs before releasing them as stable versions. Use android studio 3.1 to use flutter plugin for now.


Debugging

Does debugging work yet?
I created a new project, set a breakpoint, then do Debug Run, but the breakpoint doesn't get hit.

Yeah, it's not functional yet. I'll ping this issue when there's something to try.

@devoncarew Is debugging support purely for flutter, or could it also work for console/web apps?

It'll work for console apps as well - flutter and console apps use the same protocol. Web apps would be a totally different ball of wax.

Turned on by default here: https://github.com/dart-atom/dartlang/pull/651


More data needed

from generator.py, amazon_cobuy_graph.txt is needed.
from run_NCF.py, various .pickle files are needed, and I see no way to produce these files by my self.
I think without these files, I cannot reproduce your experiments.

Hi, thanks for your enquiry.
We have uploaded amazon_cobuy_graph.txt to our shared Onedrive folder, under the product_metadata directory.
The pickle files for recommendation can be found in here, as shown in the README.


Data directory not found on module_4_classification

On the notebook for section 4_1_logistic regression.ipynb, the dataset 'admissions.csv' is missing. I couldn't locate the datasets directory

Good catch!
I'm switching over to use the standard Kiva Loans data


不能将类型“() => void”分配给类型“MouseEvent”

Describe the bug

<EMAIL_ADDRESS><EMAIL_ADDRESS>发现只要安装了@types/node 就会报错， 所有的原生组件绑定事件都提示这个类型校验出错; 导致build 之前的vue-tsc 语法检测不能通过
Reproduction
https://github.com/lixiaozhangme/vite3.0-vue-test
Steps to reproduce
npm run dev
System Info
System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 2.88 GB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 14.18.0 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 6.14.15 - /usr/local/bin/npm
  Browsers:
    Firefox: 88.0
    Safari: 15.1
  npmPackages:
    @vitejs/plugin-vue: ^3.0.0 => 3.1.2
    vite: ^3.1.7 => 3.1.7

Used Package Manager
npm
Logs
none
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

pin @types/node to 18.8.0
This is because

pin @types/node to 18.8.0

thanks    It's ok

It's a issue on vue/volar. See https://github.com/johnsoncodehk/volar/issues/1985.


Replace "require" is not always needed

Describe the bug
Some packages (as uniqid) make checks like if(typeof require !== 'undefined') to ensure that we are in node env.
But vite replace that require to _require which is defined and then "module as been externalized"...
I think if it is not function call, there is no need to transform that check.
Reproduction
https://stackblitz.com/edit/vitejs-vite-dpwfwp?file=main.js
https://github.com/adamhalasz/uniqid/pull/48
Steps to reproduce
npm create vite vite-project -- --template vanilla
cd vite-project
npm i
npm i uniqid
echo "import uniqid from 'uniqid'" >> main.js
npm run dev

Then open http://localhost:5173/ in browser and check browser console
System Info
System:
    OS: Linux 5.19 Ubuntu 22.10 22.10 (Kinetic Kudu)
    CPU: (4) x64 Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz
    Memory: 10.53 GB / 15.57 GB
    Container: Yes
    Shell: 5.2.2 - /bin/bash
  Binaries:
    Node: 16.18.0 - /usr/local/bin/node
    npm: 8.19.2 - /usr/local/bin/npm
  Browsers:
    Chromium: 107.0.5304.87
    Firefox: 106.0.5
  npmPackages:
    @vitejs/plugin-vue: ^3.2.0 => 3.2.0
    vite: ^3.2.2 => 3.2.2

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Added steps to reproduce

https://github.com/evanw/esbuild/issues/1966#issuecomment-1022789650

Yeah, this is how esbuild treats require.
It's better to use conditional exports instead of runtime check.


⚠ Mobitopup has degraded performance

In 4a18abe, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 4319 ms

Resolved: Mobitopup performance has improved in 022e0dc after 21 minutes.


[Bug] smtp.icoremail.net:465 fail to send mail alert due to 'does not advertise the STARTTLS extension'

Here is my config:
global:
  resolve_timeout: 15s

route:
  receiver: 'slack-notifications'
  group_wait: 10s
  group_interval: 1m
  repeat_interval: 4h
  group_by: ["alertname", "instance"]
  routes:
    - receiver: 'email'
      group_by: ['alertname', 'cluster', 'instance']

receivers:
  - name: slack-notifications
    slack_configs:
    - send_resolved: true
      api_url: https://hooks.slack.com/services/adadadad123123xxxxxxxx
      channel: '#alert'
      text: '{{ template "slack.text" . }}'
  - name: 'email'
    email_configs:
    - to<EMAIL_ADDRESS>      send_resolved: true
      require_tls: true
      from<EMAIL_ADDRESS>      smarthost: smtp.icoremail.net:465
      auth_username<EMAIL_ADDRESS>      auth_password: xxxx
      html: '{{ template "email.test.html" . }}'
      headers: { Subject: "[Alert] Prometheus Alert Email" }

templates:
  - '/etc/alertmanager/templates/alertText.tmpl'
  - '/etc/alertmanager/templates/alertEmail.tmpl'

Then start service It could not send alert mail with following error:

time="2017-09-08T08:46:47Z" level=error msg="Error on notify: require_tls: true (default), but "smtp.icoremail.net:465" does not advertise the STARTTLS extension" source="notify.go:283"
time="2017-09-08T08:46:47Z" level=error msg="Notify for 1 alerts failed: require_tls: true (default), but "smtp.icoremail.net:465" does not advertise the STARTTLS extension" source="dispatch.go:262"

So, i modify require_tls to false, so I receive message error like

time="2017-09-08T08:29:52Z" level=error msg="Error on notify: *smtp.plainAuth failed: wrong host name" source="notify.go:283"
time="2017-09-08T08:29:52Z" level=error msg="Notify for 1 alerts failed: *smtp.plainAuth failed: wrong host name" source="dispatch.go:262"

When changed to gmail , no error , no exception happened. so , I wander does it not supporting icoremail ?

Using port 465 enters a hardcoded path that attempts to use TLS:
https://github.com/prometheus/alertmanager/blob/master/notify/impl.go#L275-L285
For historical reasons, this port is supported with SSL but port 587 should be used instead if possible.
See the post here: http://blog.mailgun.com/25-465-587-what-port-should-i-use/

@stuartnelson3 , hi, icoremail just provide 465 port with ssl protocol, not TLS!...

SSL was superceded by TLS back in 1999 (name was changed). If your provider is nearly 20 years behind on protecting connections, it might be time to change.

@stuartnelson3 but in china most providers still use ssl，WTF

If someone is interested by this issue, he/she may test #1591 (build artifacts are available here).

@simonpasquier Thanks, that works. I have tested gmail(port 587) and another mail provider (port 465 with ssl), everything goes fine.

@chanjarster Hi，我想问一下你这个邮箱是什么，我用阿里的邮箱465不能发送「err="*smtp.plainAuth failed: wrong host name"」

@linux-xiayun
smtp_smarthost: 'smtp.qiye.aliyun.com:465'
smtp_hello: 'company.com'
smtp_from<EMAIL_ADDRESS>smtp_auth_username<EMAIL_ADDRESS>smtp_auth_password: password
smtp_require_tls: false

Replace the username, company and password to your mail account info.

@chanjarster tks, I have tried but it didn't work. I used tencent email port 587

RFC 8314 requires that SMTP connections to port 465 use TLS (not STARTTLS). STARTTLS on 587 should still be supported but is deprecated.
PLAIN auth was fixed in 352b2ae0 (released in v0.16.0) which allows forced TLS via port 465 to work. It should be possible to use port 465 now.
require_tls (or the global smtp_require_tls) must be set to false to avoid alertmanager attempting STARTTLS. This configuration interaction with forced TLS (port 465) probably should be cleaned up since it's counter intuitive.

Facing similar issue, AWS SES giving below error,
level=error ts=2019-07-04T13:08:51.42960258Z caller=dispatch.go:264 component=dispatcher msg="Notify for alerts failed" num_alerts=1 err="require_tls: true (default), but \"email-smtp.us-east-1.amazonaws.com:465\" does not advertise the STARTTLS extension"

Tried, required_tls: flase, then getting below error,
level=error ts=2019-07-04T13:33:10.9007873Z caller=email.go:147 msg="failed to close SMTP connection" err="write tcp <IP_ADDRESS>:59836-><IP_ADDRESS>:587: use of closed network connection"

Working fine with Gmail SMTP.

@karthikeayan
Looking at the SES documentation, I would try either:

email-smtp.us-east-1.amazonaws.com:587 with required_tls: true for STARTTLS.
email-smtp.us-east-1.amazonaws.com:465 with required_tls: false for SMTPS.

@simonpasquier I have tried both, facing same issue,
level=error ts=2019-07-05T14:41:15.200309877Z caller=email.go:147 msg="failed to close SMTP connection" err="tls: use of closed connection"

Hmm, email.go:147 is when AlertManager tries to close the connection to the server. The server should have received the email though, no?
I'm not sure what would cause this on SES as when I try with Gmail (both with STARTTLS and SMTPS), it doesn't yield any error message and I receive my emails as expected. Googling for the error message, I came across this old issue.

@karthikeayan I've done some tests with the email notifier recently and a few things can be improved (see #1953). In particular the failed to close connection message can happen when the client failed to authenticate to the SMTP server (eg bad credentials) as the remote server may have closed the connection already.

@simonpasquier thank you, will test it once available in next release

@karthikeayan  - just wanted to share I was experiencing the same thing with AWS SES and it ended up being because of the credentials being provisioned for the wrong region.

@ilyache would you mind copy pasting your altermanager config file?

@ilyache thank you! I spent another 2 hours to find this, turns out to be AWS access keys will not work here. We need to create SMTP credentials from AWS Console which is similar to AWS access keys.
"global":
  "resolve_timeout": "5m"
"receivers":
- "name": "org-prometheus-notify"
  "email_configs":
  - "to"<EMAIL_ADDRESS>    "from"<EMAIL_ADDRESS>    "smarthost": "email-smtp.us-east-1.amazonaws.com:587"
# The catch here is aws access key and secret won't work here, we should create SMTP credentials from AWS Console
    "auth_username": "<SMTP_USERNAME>"
    "auth_password": "<SMTP_PASSWORD>"
    "require_tls": true
"route":
  "group_by":
  - "job"
  "group_interval": "5m"
  "group_wait": "30s"
  "receiver": "org-prometheus-notify"
  "repeat_interval": "12h"
  "routes":
  - "match":
      "alertname": "Watchdog"
    "receiver": "org-prometheus-notify"

Tencent mail can work normally using port 587

Closing the issue because there's no evidence that it's a problem with Alertmanager. If you struggle to setup the email integration, please use our user mailing list or IRC channel (#prometheus).

@linux-xiayun
smtp_smarthost: 'smtp.qiye.aliyun.com:465'
smtp_hello: 'company.com'
smtp_from<EMAIL_ADDRESS>smtp_auth_username<EMAIL_ADDRESS>smtp_auth_password: password
smtp_require_tls: false

Replace the username, company and password to your mail account info.

this work for me. i use *.qiye.163.com


Server side compilation

Have you planned to offer Ardublocky on a server with compilation server side and a service to download the hex file. Then the only program needed client side would be burning it with avrdude.
This would make Ardublockly very interesting in the class room, no installation  required of Ardublockly and Arduino IDE on each PC. It would be the MicoBit Makecode experience with Arduino or ESP8266.
I have an hacked server now, next step is to download the hex file with appropriate MIME type for avrdude to be run on reception. Would you like to help me modifying the Python server?
http://qliic.blogspot.ca/2018/02/comment-compiler-un-sketch-arduino-avec.html
Tx for this great project.

@fbelleau
Hi, I'm interested in your project for education; have you published any more info on your server setup ect.

Hi both,
Thanks a lot for your interest in Ardublockly. The application was never designed to be run on a server, but individually on each user computer (in fact, its original use case was for computers that were offline most of the time).
Because of that, the current design would require a quite a few changes and additions to allow multiple users connect to a single instance of the Ardublockly server. Things like the settings are stored server-side as a single text file, and there is no concept of multiple users or sessions, so all that would have to be redesigned or created.
At the moment I would consider this to be out-of-scope for the project in it's current form, as you still need to download and install something on the users' computers, and also because I am not ready to maintain Ardublockly as a service. But please don't let that discourage you in any way! All the code is open source and everybody is more than welcome to fork it and adapt it to their needs! I would be quite cool to see a project like that, and I'm sure there are people that will find it useful too.


Implementation of pennylane optimizers

Implementation of the classical optimizers of the PennyLane library
The following optimizers have been added:

AdagradOptimizer
AdamOptimizer
GradientDescentOptimizer
MomentumOptimizer
NesterovMomentumOptimizer
QNGOptimizer
RMSPropOptimizer
RotosolveOptimizer
SPSAOptimizer.

These have been implemented without changing the existing structure.
In the setup.py, the dependency with PennyLane has been introduced.
Also, a test for these methods is added.

@raulconchello you need to import pytest in the notebook_test file, see https://github.com/entropicalabs/openqaoa/blob/1887f413775385a30f91cd414bed49dcb943120b/tests/test_notebooks.py#L7

Damn! I almost forgot! We also need to update the documentation:

Add pennylane as a requirement here https://github.com/raulconchello/openqaoa/blob/dev_PennyLane_optimization_methods/docs/requirements.txt
Add the classes here: https://github.com/raulconchello/openqaoa/blob/dev_PennyLane_optimization_methods/docs/source/optimizers.rst

Another thing that came to mind: we need to make sure that the optimisers work well also from the point of view of the workflows.
The first step is to add them here: https://github.com/raulconchello/openqaoa/blob/115b5766c38767cbe5d8fdf18f5f6f0225bf8012/openqaoa/workflows/parameters/qaoa_parameters.py#L29
(Again, the fact that we are not doing this but that the tests is using the workflows suggests that the tests have not been running correctly)

Damn! I almost forgot! We also need to update the documentation:

Add pennylane as a requirement here https://github.com/raulconchello/openqaoa/blob/dev_PennyLane_optimization_methods/docs/requirements.txt
Add the classes here: https://github.com/raulconchello/openqaoa/blob/dev_PennyLane_optimization_methods/docs/source/optimizers.rst

Does this mean we install the entire pennylane just to use a small bunch of optimizers? Maybe a bit excessive, so, we could see if pennylane has a sub-repository for only the optimizers

I haven't found a way to just install the optimizers and other functions needed


Update stable version in repo from 1.1.1 to 1.1.2

Think about update stable version to 1.1.2
Version: stable=1.1.1 (87 days old) => latest=1.1.2 (15 days old)
Installs: stable=2152 (48.59%), latest=231 (5.22%), total=4429
Click to use developer portal
Click to edit
Note: This is an automatically generated message and not personally authored by bluefox!

This issue seems to be outdated.
This issue suggests to update the stable version of this adapter to 1.1.2 but the current stable version is already 1.1.2.
So this issue should be closed.
@mcm1957 for evidence


Deprecate blob parallel transfer options getter and setters in favor of common parallel transfer options

These are in the new Options bags

BlobParallelUploadOptions


Add national risk data and tests

This was the easiest way I could think of to construct the rows for the database but happy to implement any suggestions you have!

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 93.028%

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
894

Relevant Lines:
961

💛  - Coveralls

I looked at it again and found a way to simplify and avoid the second loop!  I'll go ahead and merge.


Can't download with 320k

It's seems this software can't download with 320kbps bit rate.

yes, official api has been changed

@henson So sad. Do you plan to fix it?


Add "Virtualization" category

@spadgett , can this go even to 3.9?

@mareklibra Currently release blockers only for 3.9.


Update lsm annotation documentation

Description
updated docs for https://github.com/inmanta/inmanta-lsm/pull/1618
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches iso6 in be72168287d6d87fc4f9d76c69319887b0a80e30


[!] CocoaPods could not find compatible versions for pod "GT3Captcha"

I can't get it to work. This error come from the log:
[!] CocoaPods could not find compatible versions for pod "GT3Captcha":
  In Podfile:
    geetest_plugin (from `.symlinks/plugins/geetest_plugin/ios`) was resolved to 0.1.3, which depends on
      GT3Captcha (~> 0.1.4)

None of your spec sources contain a spec satisfying the dependency: `GT3Captcha (~> 0.1.4)`.

me too

已经修复


[5.2] Sync and Attach problem

Today I encountered my self into a problem, I believe this is some kind of problem.
In my case:
I have a categories and sizes that can belong to many categories, therefore I use a pivot table
category_size: category_id | size_id
The problem: I attached (with $category->sizes()->attach($size_id)) many sizes, many of them may be duplicated for example:
category_id | size_id
1           |  1
1           |  1
1           |  2
2           |  1

The problem happens when I try to sync, for example if I do $category->sizes()->sync([1,2]);
the table remains the same, I mean from the documentation how sync must works is:

Any IDs that are not in the given array will be removed from the intermediate table. So, after this operation is complete, only the IDs in the array will exist in the intermediate table

I don't know if this is a misunderstanding from me or a real problem.

sync() won't remove duplicates, category one is currently attached to sizes [1,1,2], when you sync([1,2]) the final output will still be [1,1,2].
I suggest you do sync([]) before doing sync([1,2]) to remove all records before adding new ones.

But exactly that is what I mean, shouldn't be this the normal behavior?
What I understand by the documentation, only if I specify sync([1,1,2]) should there be duplicates.

Not sure if this is a bug or a feature honstly, I think some people might need sync to work the way it does now.
Ping @taylorotwell

@jmarcher Pivot table may contain additional fields so duplicates are OK.
I would recommend to use 2-column unique key in your migration and properly catch QueryException to avoid duplicates.

What @rkgrep suggested makes good sense. I suggest you do the same.
Here's an example on how to create a 2-column primary key:
$table->primary(['category_id', 'size_id']);

That way duplicates won't be allowed by the database engine.

@rkgrep @themsaid Thanks, in this case is not a problem for me.
I know that the pivot table may have duplicates, my concern is the sync functionality as the documentation says: At the end of the sync() method, the pivot table should only have the ids I passed in the array.
If this is not the intent of sync it may be nice to have a method that does a "real" sync just as @themsaid suggested first calling sync([])

Ping
Any news if this is a feature or a bug?
In both cases I can make a PR solving it or making a new method to remove duplicates

I think it's better that you make a PR that adjusts sync() to do a clean sync, in my opinion sync should remove duplicates.

@jmarcher did you get the chance to work on a PR for this?

Not yet, moved back to Germany and didn't had enough time.

@GrahamCampbell  This still seems to be an issue, can the issue be reopened or should a new one be created?


Issue 116

Fixes #116 macOS signable binary with hardened runtime.

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

Hi Rundong, This is a first version of the updates to make a modified dart sdk, a signable macOS binary and add the hardened runtime so that it can be notarized.
I would start with the create_macos_app.sh file as it outlines the steps involved.
I am still cleaning it up and testing it but this is the procedure I used to produce v1.3.2. I thought you might want to look at it now.

Note, still testing these changes.


fix(Calendar): fix day label drifting. close #11508

Brief Information
This pull request is in the type of:

[x] bug fixing
[ ] new feature
[ ] others

What does this PR do?
fix day label drifting
Fixed issues

#11508: Day label is drifting on the left when calendar range is getting smaller

Details
Before: What was the problem?

If orient is horizontal and range changes, the cell will automatically adjust its width.
But the weekly text margin always to be 50% width of cellSize.

After: How is it fixed in this PR?

I tried to fix it by making daylabel margin always be the cell's height .

Usage
Are there any API changes?

[ ] The API has been changed.

Related test cases or examples to use the new APIs
NA.
Others
Merging options

[ ] Please squash the commits into a single one when merge.

Other information

Sorry for the late review. Is it better to use the smaller dimension like:
margin = numberUtil.parsePercent(margin, Math.min(cellSize[1], cellSize[0]);

Since cellSize[1] may also be too large when calendar layout is vertical


chore(deps): Update tests and dependencies

Codecov Report

Merging #162 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #162   +/-   ##
=======================================
  Coverage   97.72%   97.72%
=======================================
  Files           4        4
  Lines          44       44
  Branches        3        3
=======================================
  Hits           43       43
  Misses          1        1

Impacted Files
Coverage Δ

app.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM - after discussing the prettier issue which I still disagree with... I'm going to approve it.


fix: Omit local variables in rich tracebacks

[x] Add a show_locals option to meltano.core.logging.console_log_formatter so local vars can be omitted to avoid leaking secrets.
[ ] Capture more known errors to avoid print full tracebacks.

Closes #7167

Add a show_locals option to meltano.core.logging.console_log_formatter so local vars can be omitted to avoid leaking secrets.

@edgarrmondragon Does this only apply to logs being sent to the console? It'd be nice if every log handler could redact secrets from their messages.

@edgarrmondragon Does this only apply to logs being sent to the console? It'd be nice if every log handler could redact secrets from their messages.

@WillDaSilva the console_log_formatter can be used with any handler, the console/stream handler is only the suggested use. So, yes, any handler that uses this formatter can omit local variables with this change. Other formatters don't have this problem AFAICT, i.e. they don't print local variables.


Fix rare access violation on out of memory

I don't have small example which reproduce access violation, but I had access violation in one project which is able to recover from std::bad_alloc with standard allocators and with tcmalloc, but was crashing with mimalloc (using vs2015 and vs2019).
Only region.c change was needed to fix a crash, but I've added code in other cases when _mi_mem_commit result was ignored just in case. I don't know enough about mimalloc, maybe some additional deinitialization is needed, but at least my crash is gone with such fix.
I've only tested this fix with mimalloc 1.6.4 and not with dev branch, but i see that other PRs created vs dev branch, so I've did the same.

Ah that is great! Thanks so much :-)

I added a few more improvements around it in the latest dev branch.


Fix README for issue 18

fix for issue #18

This is what people call a editorial change, so I don't think I need to wait that long to let it go through, as it fixes an obvious error.

Agree that this is editorial and in the interest of being practical, these kinds of changes done in good faith do not need significant reviews / process, IMO! Moreover, this change falls outside of the technical reports, and more specifically general operational content / guidance / navigations etc. So, that's generally the Chairs call. It is not coming out of the blue either. You've linked to prior discussion that has rough consensus. Good to go! And, having a PR is good notice but it could be done without it too - depending on other things that may be part of the process or repository set up, e.g., could've made the commit directly into main and linked to the issue in the commit comment. So, it is trackable in any case.
On a related note, for changes pertaining to specifications, I suggest adopting W3C Process's https://www.w3.org/2023/Process-20230612/#correction-classes where PRs indicate which correction class the proposed change is intended to be. It communicates to the reviewer how they should approach their review which can also set expectations on how long the review period could be. It is good information for the changelog in the specification. We have this going in Solid specifications now (which was previously a practise in the PR): https://solidproject.org/ED/protocol#changelog . Bonus: each change entry is machine-readable.


chore(main): release docs-site 1.11.0

:robot: I have created a release beep boop
1.11.0 (2024-06-18)
Features

docs-site: add dune dashboard to dev tools (#17617) (ae0b0f0)
docs-site: add verify in batches explanation (#17600) (0a8a886)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

docs-site-v1.11.0
:sunflower:


Converted from nginx to Unit (nginx) framework

Converted to Unit framework
Unit serves the simplestream file system
Unit also serves the file-upload
Use RPC to notify lxd-image-server code to rebuild instead of relying on File system hooks.  File system hooks do not work well due to new directories being created too fast for the hook library to keep up and does not get notified of changes.
Started work on LxD co-server.  LxD co-server allows serving TLS images and does not require a ca-certificates cert.  Simplelstream servers are required to be HTTPS and therefore must have valid trusted certs, which is a problem.  LxD only requires a password and shared TLS keys.

Good to go!


notepad++ plugin - bundle validation ends up with a schematron violation

Validating the attached file results in a schematron violation of bdl-7 FullUrl must be unique in a bundle, or else entries with the same fullUrl must have different meta.versionId).
However, the fullUrls are unique. The bundle passes a validate when posted to the server (though the bundle also passes a validate when posted to the server if the fullUrls are the same; not sure why?)
testbundle.txt

fixed in release 1.0.7+


🔴 「Google Podcasts」申请适配

Google Podcasts
https://podcasts.google.com/
试过用 NPM 命令打包网站了，但是 M1 Mac 在最后打包的时候会报错，顺着路径也找不到 DMG 包

我出现了和你一样的问题，而且我添加了图标也是一样的报错，我的是mac-Intel，报错情况如下：
$ pake https://www.baidu.com --icon '/Users/iei/Documents/r.icns' --name 'Rebang'
now platform is  darwin
✔ We detected that you have not installed Rust. Install it now? … yes
⠦ Downloading Rustinfo: downloading installer
⠸ Downloading Rustinfo: profile set to 'default'
info: default host triple is x86_64-apple-darwin
warning: Updating existing toolchain, profile choice will be ignored
⠧ Downloading Rustinfo: syncing channel updates for 'stable-x86_64-apple-darwin'
⠴ Downloading Rustinfo: default toolchain set to 'stable-x86_64-apple-darwin'
⠦ Downloading Rust  stable-x86_64-apple-darwin unchanged - rustc 1.65.0 (897e37553 2022-11-02)
Rust is installed now. Great!
To get started you may need to restart your current shell.
This would reload your PATH environment variable to include
Cargo's bin directory ($HOME/.cargo/bin).
To configure your current shell, run:
source "$HOME/.cargo/env"
✔ Downloading Rust
npm WARN deprecated<EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
added 82 packages, and audited 235 packages in 2m
76 packages are looking for funding
run npm fund for details
found 0 vulnerabilities

<EMAIL_ADDRESS>build:release
npm run tauri build --release

<EMAIL_ADDRESS>tauri
tauri build

thread '' panicked at 'called Result::unwrap() on an Err value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/interface/rust.rs:762:69
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
node:internal/process/promises:288
triggerUncaughtException(err, true /* fromPromise */);
^
[Error: ENOENT: no such file or directory, copyfile '/usr/local/lib/node_modules/pake-cli/src-tauri/target/release/bundle/dmg/Rebang_1.0.0_x64.dmg' -> '/Users/ilei/Documents/Rebang.dmg'] {
errno: -2,
code: 'ENOENT',
syscall: 'copyfile',
path: '/usr/local/lib/node_modules/pake-cli/src-tauri/target/release/bundle/dmg/Rebang_1.0.0_x64.dmg',
dest: '/Users/ilei/Documents/Rebang.dmg'
}
Node.js v18.10.0

这一块我们还是全面兼容一下 避免边界情况

@icelo0
图标试试当前终端所在的相对路径。

我改成相对路径还是一样的，不知道是什么问题。还请帮忙排查一下
$ pake https://www.baidu.com --icon './r.icns' --name 'Rebang'
now platform is  darwin
✔ We detected that you have not installed Rust. Install it now? … yes
⠏ Downloading Rustinfo: downloading installer
⠧ Downloading Rustinfo: profile set to 'default'
info: default host triple is x86_64-apple-darwin
warning: Updating existing toolchain, profile choice will be ignored
⠏ Downloading Rustinfo: syncing channel updates for 'stable-x86_64-apple-darwin'
⠹ Downloading Rustinfo: default toolchain set to 'stable-x86_64-apple-darwin'

⠸ Downloading Rust  stable-x86_64-apple-darwin unchanged - rustc 1.65.0 (897e37553 2022-11-02)

Rust is installed now. Great!

To get started you may need to restart your current shell.
This would reload your PATH environment variable to include
Cargo's bin directory ($HOME/.cargo/bin).

To configure your current shell, run:
source "$HOME/.cargo/env"
✔ Downloading Rust

up to date, audited 235 packages in 2s

76 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

><EMAIL_ADDRESS>build:release
> npm run tauri build --release

><EMAIL_ADDRESS>tauri
> tauri build

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/interface/rust.rs:762:69
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: ENOENT: no such file or directory, copyfile '/usr/local/lib/node_modules/pake-cli/src-tauri/target/release/bundle/dmg/Rebang_1.0.0_x64.dmg' -> '/Users/ilei/Documents/Rebang.dmg'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'copyfile',
  path: '/usr/local/lib/node_modules/pake-cli/src-tauri/target/release/bundle/dmg/Rebang_1.0.0_x64.dmg',
  dest: '/Users/ilei/Documents/Rebang.dmg'
}

Node.js v18.10.0

@Tlntin
修改成小写后我依旧报错，如下：
$ pake https://www.baidu.com --icon ./r.icns --name baidu
now platform is  darwin
✔ We detected that you have not installed Rust. Install it now? … yes
⠴ Downloading Rustinfo: downloading installer
⠴ Downloading Rustinfo: profile set to 'default'
info: default host triple is x86_64-apple-darwin
warning: Updating existing toolchain, profile choice will be ignored
⠇ Downloading Rustinfo: syncing channel updates for 'stable-x86_64-apple-darwin'
⠦ Downloading Rustinfo: default toolchain set to 'stable-x86_64-apple-darwin'

⠧ Downloading Rust  stable-x86_64-apple-darwin unchanged - rustc 1.65.0 (897e37553 2022-11-02)

Rust is installed now. Great!

To get started you may need to restart your current shell.
This would reload your PATH environment variable to include
Cargo's bin directory ($HOME/.cargo/bin).

To configure your current shell, run:
source "$HOME/.cargo/env"
✔ Downloading Rust

up to date, audited 235 packages in 2s

76 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

><EMAIL_ADDRESS>build:release
> npm run tauri build --release

><EMAIL_ADDRESS>tauri
> tauri build

thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }', src/interface/rust.rs:762:69
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: ENOENT: no such file or directory, copyfile '/usr/local/lib/node_modules/pake-cli/src-tauri/target/release/bundle/dmg/baidu_1.0.0_x64.dmg' -> '/Users/ilei/Documents/baidu.dmg'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'copyfile',
  path: '/usr/local/lib/node_modules/pake-cli/src-tauri/target/release/bundle/dmg/baidu_1.0.0_x64.dmg',
  dest: '/Users/ilei/Documents/baidu.dmg'
}

Node.js v18.10.0

@Tlntin 能分享下命令么? 我用来练练手, 另外换个icon, 多谢


Implement animations

Ok so I know this sounds crazy but it's not as bad as you think it is :laughing: I made two GIFs with different applications but both feel jankier than it feels in real. The blend (opacity) animation does feel nice, but I must admit the display-height animation feel a bit janky no matter what because it's limited to increasing by a line at each step :/

(I only half-expect you to take this one seriously, I don't expect people to be enthusiastic with animations, feel free to decline ^^)

Nice job! Looks super cool, but we need to ensure it won't introduce any performance regression before doing the merge.

Nice job! Looks super cool, but we need to ensure it won't introduce any performance regression before doing the merge.

Yes! This is really just a POC. The opacity animation works nice, but the height animation needs to be handled correctly. The height can be changed mid-animation by the display.shrink* methods, that's why I commented them for this. I'll need to model it that in a way that is clearer and ensure the animation adapts to any new requested height. I'll probably need to hide the nvim_win_set_config(s:display_windi calls behind a s:display_set_config that will check the animation status before applying the height. I'll complete the tags PR first though.

This looks very sweet!  Would you be up for looking at it again with fresh 2022 eyes?

@HaleTom I don't have as much time for OSS these days :| Also I'm not interested enough in continuing this PR, I have other stuff to play with right now (integrating kitty graphics into neovim), but whoever wants to continue the work is welcome to take it.

Hey just wanted to say it's awesome, thanks @romgrk

Closing, stale.


As a developer i would like to edit the yaml files so they follow project guidelines

User Story
As a developer i would like to edit the yaml files so they follow project guidelines
Description of the solution you'd like
After changing our git strategy, as a result of the 1. project review, the workflows of this project should be edited so they fit the outlined guides from session 03.
Definition of Done

[x] Remove mergeToMainWorkFlow
[x] Clean up the release workflow, so it no longer uses matrix.
[x] The build and test workflow should still work as expected.

We still use matix, because it is best


Create test.md

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azureps-cmdlets-docs/ResourceManager/test.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Make ROCm device wavesize and wavebits into compile time constants

(Feedback from AMD user)
At several points in the examples, globals are created for WAVESIZE and WAVEBITS:
https://github.com/numba/roc-examples/blob/master/numba_roc_examples/reduction/reduction.py#L7
https://github.com/numba/roc-examples/blob/master/numba_roc_examples/radixsort/roc_scan.py#L5
https://github.com/numba/roc-examples/blob/master/numba_roc_examples/kerneldensity/roc_imp.py#L17
These are in principle properties of the device, and should probably be constants in the numba.roc module that can be used directly without the user needing to define them.

Reopening because #3280 is only part of the solution.  The ultimate goal is to not have WAVESIZE need to be defined by the user as a global constant to use it in their kernel.  For example, we would want this to work:
@roc.jit(device=True)
def shuffle_down(val, width):
    tid = roc.get_local_id(0)
    roc.wavebarrier()
    idx = (tid + width) % roc.wavesize
    res = roc.ds_permute(idx, val)
    return res

Where roc.wavesize becomes 64 (or whatever the value needs to be) at kernel compile time.  This is similar to how cuda.warpsize works.

Closing due to https://github.com/numba/numba/pull/6991


Previously selected background remains highlighted.

As we switch between various background options, the background that was previously selected remains highlighted. For example, if I select 'Esri World Imagery' after 'Bing aerial imagery', the latter is still highlighted.

It should be something like this:

Oh yeah that's by design.  It's because the user can switch quickly between those 2 backgrounds with ⌘B.  I know it's a bit strange though.  A nicer solution might be a visual indicator, but we don't have a lot of room on the pane for additional UI, it's already pretty cramped.
Let me know what you think @vershwal ..

I checked ⌘B and it works well to switch between any two backgrounds and then it makes sense. But as a user, I didn't realize it at first.


Permission denied

I'm really not sure if this belongs here, with Concourse itself, or if I did something wrong, so sorry in advance.
We have concourse running on AWS with concourse-up, but pipelines are failing with this:
runc create: exit status 1: container_linux.go:264: starting container process caused "process_linux.go:339: container init caused \"rootfs_linux.go:56: mounting \\\"/var/vcap/data/baggageclaim/volumes/live/31a2cf2b-96d8-4a45-7f54-678bc14b60ee/volume\\\" to rootfs \\\"/var/vcap/data/garden/graph/aufs/mnt/8da3238024d4ca66aa84fba1c718807b4cd727eb8ea11728325b3de7bd53e8ff\\\" at \\\"/var/vcap/data/garden/graph/aufs/mnt/8da3238024d4ca66aa84fba1c718807b4cd727eb8ea11728325b3de7bd53e8ff/scratch\\\" caused \\\"mkdir /var/vcap/data/garden/graph/aufs/mnt/8da3238024d4ca66aa84fba1c718807b4cd727eb8ea11728325b3de7bd53e8ff/scratch: permission denied\\\"\""

The permission denied error here seems to indicate some kind of setup failure, but I don't really know where to look. Any ideas?

Coming to work today, I find the build has run again, this time successfully. ¯_(ツ)_/¯


Snapshot fails by sending instVarAt: 0 due to GemStone class version skew

If you try to replicate a GemStone service whose class version is not the current version, mismatch of instance variable names can cause [] in RsrServiceSnapshot class >> reflectedVariablesFor:do: to send instVarAt: 0 to the service, which fails with an OffsetError.
This happens when the instance variable names of the template class (which is looked up by name, and thus always the current version) contains a name that does not name an instance variable in the class version actually being replicated.
Replicating non-current versions is likely to be problematic in any case, but should really only fail if the reflected instvars do not match on the two sides of the connection. I believe that error also fails with an easier-to-diagnose message.
One way to avoid this problem is to not resolve the template class by name, but instead search up the class hierarchy of the service until a class with the correct template class name is found. That solution would impose a limitation that the service actually be a kindOf: its template class, but I don't immediately see a situation where a situation that violated that constraint would be desirable. It would be currently possible, but a considerable amount of bother for little or no gain.

Instead, I suggest we pursue the idea of template registration.
If you wish to use a Service w/ RSR, you need to register the client and server classes under a template name. (See end of message for possible selectors.) The client and server classes would need to be related and share a common ancestor in the Service hierarchy. The common ancestor would server as the basis for computing the set of inst vars that are replicated. All inst vars below the common ancestor would be private.
When attempting to replicate a Service, we would ensure it has been registered. If it hasn't, we would signal an error locally.
When reifying a Service, if an compatable template has not been registered, we would signal an error remotely.
When classes change version, the existing registered version would continue to replicate. The new class version would error locally until it was properly registered.
registerTemplate: aTemplateSymbol
client: clientClass
server: serverClass

ensureTemplateRemoved: aTemplateSymbol

hasTemplate: aTemplateSymbol

clientForTemplate: aTemplateSymbol

serverForTemplate: aTemplateSymbol

template: aTemplateSymbol
ifAbsent: aBLock
"Returns an info holder containing the client, server, and details like the set of inst vars replicated"

templateForServiceClass: aServiceClass
ifAbsent: aBlock
"Returns an info holder containing the client, server, and details like the set of inst vars replicated"

We would have to register a template on both sides of the connection before replication? With a new connection, how would service class registration be initiated on the server side?
A registration requirement adds significant complexity to using RSR, and I'm not seeing much benefit.

I wouldn't say 'significant'. In the past, we discussed this very mechanism as a way of supporting handshake mechanisms at the level of a Service.
The problem with the strategy of looking up classes by traversing their class hierarchy is that you could end up switching the class version.

RSR's current implementation does walk up through the superclass chain rather than looking up a class by name. This issue appears to be resolved.
RsrTemplateResolverWithClassVersions >> testVersionClassAfterCreatingService appears to be a sufficient test to validate this case.


Minimal Video Support

Added support for choosing existing photos from the phone & recording new videos through the in-app camera. I've also updated the demo application to show this mode.
By default, video support is disabled. Video support can be turned on via Picker.setVideosEnabled(true). This simply makes the albums load both photos and videos. Video thumbnails are denoted with the "play" icon. Photos and images can be selected together. ImageEntry.isVideo will return true if the selected item is a video.
When videosEnabled is turned on, when clicking on the top-right camera icon to launch the camera, the user will be prompted to choose between the Photo Camera and the Video Camera. Depending on the choice, the cwac-cam2 library will launch a photo camera or video camera. If videosEnabled is false (by default), the photo camera will launch by default without a prompt for a choice.
Note: Videos recorded with the cwac-cam2 library when the phone is held in portrait position, will end up with sideways recorded videos. This is due to the cwac-cam2 library not finishing their work around calling setOrientationHint() call in ClassicCameraEngine.

Can you create a new branch and do the pull request there ? It seems there's some problems i could help fix

@yazeed44 OK, created another PR that is on a different branch other than master


[WIP] Generate weekly jobs for specific platforms

This will automatically generate jobs for Azure, GCP, vSphere, Hypershift, OVN, OSD, single-node
Individual OpenShift versions can specify generateCustomConfigs: true. The repository configuration should then list custom configurations under customConfigs. The releaseBuildConfiguration key should include at least tests key
with the list of tests to be run.
For custom configurations, tests are not generated from Makefile targets but rather taken directly from the configuration. The resulting build configuration is then enriched with images, base images, and dependencies for test steps.

I'm testing the generated configs in https://github.com/openshift/release/pull/46579

/lgtm


The users/search endpoint is not supported

Currently the endpoint users/search API link is not supported. Only user/search is. user/search contains a bug limiting it to only first 1000 users. Bug link
Please add.

Thanks! Will be added in next release.

@MrRefactoring 10x. When will the next release will be shipped?

I would like to close the issue #179 and make release

@roman-acumen released in version 2.16.0


LM loss is nan

I use the offsite-tuning code to run scripts/figure4/layerdrop.sh, here is a mistake：
RuntimeError: expected scalar type Half but found Float
then， I modify the code: offsite_tuning/utils.py, line 659:
change the code：model.adapter = layers[:l] + layers[r:]
to:  model.adapter = layers[:l].half() + layers[r:].half()
it run ok，but，Another error has occurred：
Epoch 0 - Step 19 - LR: 1.90e-09 - LM loss: nan - KD loss: 0.0000:   1%
the LM loss is nan.
the system is ubuntu22.04, gpu is nvidia T4, 16G.
model is: facebook/opt-1.3b
datasets: wikitext-2-raw-v1
train_module: adapter
Can you help me find the cause of the problem？
thanks.

should use Nvida RTX3090 or higher gpu

should use Nvida RTX3090 or higher gpu


[RESTEASY-2102] Renaming resteasy-validator-provider-11 to resteasy-v…

…alidator-provider (but keeping existing jboss modules name to be able to still deploy on existing containers), upgrading to Hibernate 6 / BV 2.0

In jboss-modules/build.xml
line 187
I don't see that you have changed the directory name.
This would also require a rename of directory.
jboss-modules/src/main/resources/modules/org/jboss/resteasy/resteasy-validator-provider-11
And I would think you would want to change file
jboss-modules/src/main/resources/modules/org/jboss/resteasy/resteasy-validator-provider-11/main/module.xml
contents accordingly.
I don't see that here. Have I missed something?

The problem is that the way resteasy distribution is installed on top of an existing wfly container does not allow removing a module, we can only add a new one or modify existing ones. So we have no way to remove the old resteasy-validator-provider-11. Moreover, that module is referenced by the org.jboss.as.jaxrs module, which we can't modify from resteasy distribution as it includes the jaxrs subsytem jar (well, we could if we had a more advanced installation mechanism as we have in JBossWS project...)
So, what I decided to do is to let wildfly keep on using the original resteasy-validator-provider-11 module name, while the actual artifact from RESTEasy is changed to resteasy-validator-provider in the jar filename and Maven artifact name.
Does this make more sense now?

ok

@rsearls @ronsigal , after our discussion and consultation with Brian, I've added an additional commit here to also change the name of the wildfly module; the old module is turned into an alias one, referring to the new one.

Ok.


feat: use monorepo queries

Try out Leather build a2b839a — Extension build, Test report, Storybook, Chromatic

Connected to this PR in monorepo: https://github.com/leather-wallet/mono/pull/113

Sorry, I prob just really created a lot of conflicts for you with my last merge. If helps, I can rebase this for you?


Adding Greece to global Azure 2023

Thanks @noopman, it's great to join this awesome event for one more year!


chore: release 4.1.2

:robot: I have created a release *beep* *boop*
4.1.2 (2019-06-11)
Bug Fixes

link to new googleapis.dev docs (#477) (9dfcda0)

This PR was generated with Release Please.

Release is at https://github.com/googleapis/nodejs-bigquery/releases/tag/v4.1.2

The release build has started, the log can be viewed here. :sunflower:

:egg: You hatched a release! The release build finished successfully! :purple_heart:


Problems with JS/jQuery imports

Laravel Mix Version: 2.1.11
Node Version: 8.10.0
NPM Version (npm -v): 6.1.0
OS: Ubuntu 18.04.1

Description:
I have a lot of JS imports in my main JS-file. Many of them are modules that essentially are just split-up jQuery functions for specific things. Such as init of this and that slider, etc. It's split up so it's easier to maintain.
Even though jQuery is added to my mix.config like so:
mix.js('src/js/main.js', 'js/')
   .sass('src/sass/main.scss', 'css/', {
       outputStyle: 'nested'
   })
   .autoload({
       jquery: ['$', 'jQuery', 'jquery', 'window.jQuery'],
       'popper.js/dist/umd/popper.js': ['Popper'],
   })
   .extract(['jquery', 'popper.js', 'bootstrap']);

...I still have to import jQuery manually in main.js, like so:
// jQuery
window.$ = $;
window.jQuery = window.$ = require('jquery');

Most of my modules work fine. But I get the odd $(...)<import> is not defined, where <import> being an imported npm package, eg, owl.Carousel. These modules are set up the exact same way. However, the only fix to these specific owl.Carousel-errors is to have jQuery in my <head>-tag, which isn't optimal.
I know I can import npm packages in two ways:

Regular ol' school: var Package = require('package');
And ES6: import * as Package from 'package';

But again, I get the odd Module is not defined errors.
Is there anything I'm doing wrong here, or am I stretching Mix too far?
Thanks!

Please share the exact code that you are using for the Carousel library.
I suspect you have imported eat code from node_modules and Babel loader does not trabspile vendor code by default.

@ankurk91: Here's the hopefully relevant code: https://gist.github.com/moso/502a005f1dd53dfb66f47d779457984b

First is the main.js with all the imports.
Next is package.json with some of the info omitted. But there you can see packages, versions, etc.
Third is an example of one of those init modules, just made to keep things seperated.
And lastly we have webpack.mix.js for the Mix config.

Thanks!

Laravel mix uses webpack under the hood.
Several issue has been reported for this before. see
https://github.com/OwlCarousel2/OwlCarousel2/issues/1866
Can you try to update your main.js code with
// main.js
// use ES6 import for jQuery too
import jQuery from 'jquery';
window.$ = window.jQuery = jQuery;

I believe you have these lines in your blade already
<script src="{{ mix('js/manifest.js') }}"></script>
<script src="{{ mix('js/vendor.js') }}"></script>
<script src="{{ mix('js/app.js') }}"></script>


.get should optionally renew key ttl

Getting value from the cache should renew it's expiration value to the same ttl as previously set.

+1

This would be a big API change. I would be ok with a touch method if you want to build one.

A touch method should be acceptable, sure.


feat/restricted-mouse-clicks

Since the beginning of botty there were few reports that equipped items or charms were lost. In all of these cases, the reason is most likely some config errors.
But just to make sure this does not happen check before every click if inventory is open and restrict clicking to not click in equipped area and in the restricted inventory area (depending on num_loot_columns)

Well, I tried to replace the TemplateFinder method with ScreenObjects but unfortunately ran into circular imports I didn't want to resolve. Also ran into the same trying to use inventory/personal.py's function for determining reserved/restricted inventory but also ran into circular import. Ended up extending your changes in config.py and modified the codebase to utilize it.
custom_mouse.py tests work, let me know what you think. @aeon0

I think that circular import hints that sth isn't right with how we structured the code right now.
ScreenObject should probably be in its own file and the is_visible and detect_screen_object are probably better off in the TemplateFinder()?

I think that circular import hints that sth isn't right with how we structured the code right now. ScreenObject should probably be in its own file and the is_visible and detect_screen_object are probably better off in the TemplateFinder()? But we can merge this now and do that in a different PR.
Putting the rois in the config like this is good imho.

I think you're right. Part of the issue is mouse is imported in pretty much every file. :P Open to ideas for sure.


the circular images and the logo, the "join the community" text, and the button" seem like they're leaning more towards the bottom that being centered in the middle

It looks like it's actually centered


[BUG] cursor in Firefox is in wrong place

I'm submitting a

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report
[ ] Enhancement
[ ] Feature request
[ ] Documentation issue or request

Description
When I click in the ngx-editor my cursor is shift in top

Version Information
ngx-editor: 3.3.0
angular: 5.2.9

Browser

[ ] Chrome - x.x.x
[x]  Mozilla Firefox - 60.0.1
[ ] Opera - x.x.x
[ ] Microsoft Edge - x.x.x

Trying to override below css that is working for me
.ngx-editor-textarea::before {
content: normal !important;
}


Error in sub-languages md file

Hi there,
I'm happy to use your plugin on my website:
https://dohaison.github.io/InfoSysID
Everything works fine on the main En page.
However, I tried to support new languages on my page, e.g., vi-vn. To do that, I created a new branch and put translated markdown file into this branch without index.html.
https://github.com/DoHaiSon/InfoSysID/tree/vi
All other content works fine but your plugin is not. It appears like this: last update time: {docsify-updated}
Could you help me debug this error? The below URL is the repo of my page:
https://github.com/DoHaiSon/InfoSysID
Thank you for everything!

Hello, I have completed the test.
It is because the vi branch request response does not have a last-modified field, which is also a problem often encountered in rendering failures when deployed on various static website service platforms.

If you want to add multi-language documents, it is recommended to store different language documents in different directories of a branch according to the following directory structure
.
└── docs
    ├── README.md
    └── de
        └── README.md
    └── es
        └── README.md
    └── vi
        └── README.md
    └── en
        └── README.md

Dear pfeak,
That makes sense. I re-constructed my repo into a single branch, and it worked fine.
Thank you so much!


Advantage on tool rolls don't work

I'm not sure exactly when, but the dnd5e.preRollToolCheck changed the arguments it passes. It means that checking for advantage doesn't work anymore. I didn't test messages yet, but it might affect those too.

Looks like it was changed back in dnd5e v2.2.0 when tool proficiencies were added to the actor.


Libvirt-php stub

Stub from source code of libvirt-php and documentation
Fix spelling
Include default values
Group by module and ordering the functions

@inode64 please execute docker-compose -f docker-compose.yml run php /usr/local/bin/php /opt/project/phpstorm-stubs/generate-stub-map and commit the resulting PhpStormStubsMap.php

When click on url Details from "Code Inspection"  error 500 shows up
I can't see the errors to fix them

Reopen in other pull :-(


Cant clear syntax error popup

Version (which release did you use?)
4f07a44cc15fe09b6603630d3547e68a6d55193f development release
Describe the bug
A clear and concise description of what the bug is.
To Reproduce

Drop a semicolon from a line in config file, save file.

Fix semicolon, (reload nog?)

Expected behavior
Syntax error popup disappears.
Actual behavior
Syntax error popup remains until I log out or restart my computer. Even if Nog is quit.

While the alt-q bind works sometimes, I think there is still a bug with nog not resolving focus after a configuration error. Half the time it will accept and clear the popup, the rest of the time it refuses to accept any input (workmode on/off, close tile, etc) and there's no way to 'focus' it.

I encountered the same issue @taylan97 mentions above and when I went through the commits and it seems it was introduced with the changes for #185. I opened #189 to address it, so this might not be worth re-opening but just letting @taylan97 know #189 will be used to track this.
I'm hoping I can get this resolved soon.


Use range dependencies

The latest rust-bitcoin release does not require any changes to use with this crate. If we use range dependencies for bitcoin_hashes and and bitcoincore-rpc then users can use this crate with whichever versions they want. Implies being able to use rust-bitcoin v0.31 or v0.32

Woops, I did this already in #158 - face palm.


[CINFRA] Collection Group Supervision

Scope & Purpose
This PR adds a minimal working version of the supervision for collection groups. It is far from perfect and will be optimized in future PRs. The primary goal is to make it work.

Remaining tests are unrelated.


MINOR: Removed additional space from indentation of ReferenceAssemblies HashSet.

Hi @Matthew-Bonner, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

@Matthew-Bonner sure I'll merge this.  :shipit:

648f00c


Include settings in Powertoys Run search results

Description of the new feature / enhancement
In regular windows search, if you type in a specific setting, you are able to open to that specific settings menu instantly. In Powertoys Run, you can search for the whole settings app, but you can't access specific settings.
Scenario when this would be used?
This is useful for quickly searching for a setting without exiting a fullscreen app.
Supporting information

Hi, there is already a Settings plugin for PT Run.
The default activation key is $.
https://learn.microsoft.com/en-us/windows/powertoys/run#direct-activation-commands
/needinfo


- Customize header height

The height of header slot of <AccordionItem> is pretty large, user might want to reduce its height.
Here is what I did to customize the height:
          :global(#currentFiltersWrapper h2, #currentFiltersWrapper h2 button ) {
            height: 20px;
            @apply mb-2;
          }

Maybe header-height and header-margin-bottom could be an option in the component? (the names are just examples)

New version of Accordion and AccordionItem implemented.
You can take look at the Color option section in Accordion docs how to customize items.
You can as well drop directly to AccordionItem the class prop.

<Accordion
  activeClasses="bg-blue-100 dark:bg-gray-800 text-blue-600 dark:text-white focus:ring-4 focus:ring-blue-200 dark:focus:ring-blue-800"
  inactiveClasses="text-gray-500 dark:text-gray-400 hover:bg-blue-100 dark:hover:bg-gray-800">
  <AccordionItem class="!py-2">
    Header 2-1

Lorem ipsum dolor sit amet, consectetur adipisicing elit. Illo ab necessitatibus sint explicabo ...

  </AccordionItem>
  <AccordionItem class="!py-2">
    Header 2-2

Lorem ipsum dolor sit amet, consectetur adipisicing elit. Illo ab necessitatibus sint explicabo ...

  </AccordionItem>
</Accordion>

I suppose the new version has no tag yet ?

I just publshed v0.27.5.

Now, add class on <AccordionItem> can adjust header style, event without the ! from tailwind.
e.g
<AccordionItem id="1" open={false} color class="py-2">


vim_configurable: restore ability to override python for modules

Motivation for this change
It seems as Python will be fetched from $PATH in Vim 8.1:
stat("/home/ma27/bin/python", 0x7ffe57a317b0) = -1 ENOENT (No such file or directory)
stat("/run/wrappers/bin/python", 0x7ffe57a317b0) = -1 ENOENT (No such file or directory)
stat("/home/ma27/.nix-profile/bin/python", 0x7ffe57a317b0) = -1 ENOENT (No such file or directory)
stat("/nix/var/nix/profiles/default/bin/python", 0x7ffe57a317b0) = -1 ENOENT (No such file or directory)
stat("/run/current-system/sw/bin/python", {st_mode=S_IFREG|0555, st_size=291, ...}) = 0
readlink("/run/current-system/sw/bin/python", "/nix/store/ggjkqbvwnv7dflkmdgmmp"..., 4096) = 72

This breaks in cases where you want to use a modified Python derivation
for the VIM plugins you use in vim_configurable:
let
  vim_configurable' = vim_configurable.override {
    # python with modules for ensime
    python = python.withPackages (ps: with ps; [ sexpdata websocket_client ]);
  };
in
  vim_configurable'.customize {
    # ...
  }

With VIM 8.0 this worked perfectly fine, now it's necessary to install
the modified python in $PATH to actually use it, otherwise an error
like this arises:
[ensime] A dependency is missing, please `pip2 install sexpdata websocket-client` and restart Vim.
Press ENTER or type command to continue

However it should be possible to pass the modified Python to the
modules, the easiest workaround is to write a wrapper which prefixes
$PATH to have the Python derivation available.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

I'll run nox-review locally just to be sure %)

Success on x86_64-linux (full log)
Attempted: vim_configurable
Partial log (click to expand)
Try 'basename --help' for more information.
/nix/store/3i6ghp533b3wi2r4190abwlz8g4p44q9-vim_configurable-8.1.0001/share/vim/vim81/tools/demoserver.py: interpreter directive changed from "/usr/bin/python" to "/nix/store/l9j2jsc9flrbmpf799nw9wdq59gpwms8-python-2.7.14/bin/python"
/nix/store/3i6ghp533b3wi2r4190abwlz8g4p44q9-vim_configurable-8.1.0001/share/vim/vim81/tools/ref: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
/nix/store/3i6ghp533b3wi2r4190abwlz8g4p44q9-vim_configurable-8.1.0001/share/vim/vim81/tools/vimspell.sh: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
/nix/store/3i6ghp533b3wi2r4190abwlz8g4p44q9-vim_configurable-8.1.0001/share/vim/vim81/tools/vimm: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
/nix/store/3i6ghp533b3wi2r4190abwlz8g4p44q9-vim_configurable-8.1.0001/bin/gvimtutor: interpreter directive changed from "/bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
head: error writing 'standard output': Broken pipe
/nix/store/3i6ghp533b3wi2r4190abwlz8g4p44q9-vim_configurable-8.1.0001/bin/vimtutor: interpreter directive changed from " /bin/sh" to "/nix/store/xn5gv3lpfy91yvfy9b0i7klfcxh9xskz-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/3i6ghp533b3wi2r4190abwlz8g4p44q9-vim_configurable-8.1.0001...
/nix/store/3i6ghp533b3wi2r4190abwlz8g4p44q9-vim_configurable-8.1.0001

Success on aarch64-linux (full log)
Attempted: vim_configurable
Partial log (click to expand)
/nix/store/b1qa158dbkiygmy9jagx5k4yj5nmvwzh-vim_configurable-8.1.0001/bin/vimtutor: interpreter directive changed from " /bin/sh" to "/nix/store/l4w7xwjy2nmk31fl5kgyy7gg8z7l9n8z-bash-4.4-p19/bin/sh"
/nix/store/b1qa158dbkiygmy9jagx5k4yj5nmvwzh-vim_configurable-8.1.0001/share/vim/vim81/tools/vimspell.sh: interpreter directive changed from "/bin/sh" to "/nix/store/l4w7xwjy2nmk31fl5kgyy7gg8z7l9n8z-bash-4.4-p19/bin/sh"
/nix/store/b1qa158dbkiygmy9jagx5k4yj5nmvwzh-vim_configurable-8.1.0001/share/vim/vim81/tools/vimm: interpreter directive changed from "/bin/sh" to "/nix/store/l4w7xwjy2nmk31fl5kgyy7gg8z7l9n8z-bash-4.4-p19/bin/sh"
/nix/store/b1qa158dbkiygmy9jagx5k4yj5nmvwzh-vim_configurable-8.1.0001/share/vim/vim81/tools/ref: interpreter directive changed from "/bin/sh" to "/nix/store/l4w7xwjy2nmk31fl5kgyy7gg8z7l9n8z-bash-4.4-p19/bin/sh"
basename: invalid option -- 'w'
Try 'basename --help' for more information.
/nix/store/b1qa158dbkiygmy9jagx5k4yj5nmvwzh-vim_configurable-8.1.0001/share/vim/vim81/tools/demoserver.py: interpreter directive changed from "/usr/bin/python" to "/nix/store/vhz9s1dzzbndz032dysnixj8mxyfl30s-python-2.7.14/bin/python"
/nix/store/b1qa158dbkiygmy9jagx5k4yj5nmvwzh-vim_configurable-8.1.0001/share/vim/vim81/macros/less.sh: interpreter directive changed from "/bin/sh" to "/nix/store/l4w7xwjy2nmk31fl5kgyy7gg8z7l9n8z-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/b1qa158dbkiygmy9jagx5k4yj5nmvwzh-vim_configurable-8.1.0001...
/nix/store/b1qa158dbkiygmy9jagx5k4yj5nmvwzh-vim_configurable-8.1.0001

cc @LnL7 @FRidh

In neovim this is done by python_host_prog and python3_host_prog but I suppose this is not possible with vim.

It seems as the issue doesn't exist in neovim as it allows an extra property named pythonDependencies to specify additional python modules (see pkgs/applications/editors/neovim/wrapper.nix line 33)

There might be user who don't want the python passed to during build time and instead use the python set by virtualenv/nix-shell. Is there a better way to distinguish the python version used by vim internally from the python executable in $PATH?

When you build the code for vim_configurbale I posted above with VIM 8.0 everything works perfectly fine which means that the python derivation from the override was used for vim modules previously.
First of all the question is when do we want to use Python from the derivation and when the one from $PATH? Unfortunately I don't know too much about Vim's internals, so I'm not sure if there's an easy way to fix this :sweat_smile:

There might be user who don't want the python passed to during build time and instead use the python set by virtualenv/nix-shell.

Yeah, I'm not sure if creating the wrapper unconditionally is a good idea. Creating a wrapper yourself is pretty straightforward, while disabling it would be pretty tricky.

Yeah, I'm not sure if creating the wrapper unconditionally is a good idea. Creating a wrapper yourself is pretty straightforward, while disabling it would be pretty tricky.

I absolutely understand your point. The reason why I filed this patch was to retain the behavior with VIM 8.0 where the python argument from vim_configurable.override was used for VIM scripts.
Admittedly I'm not sure how to proceed here, so do you think it's easier/better to create the wrapper locally or should we somehow provide this functionality in nixpkgs? Unless I'd close this for now %)

As I'm currently using an altered python in $PATH (which contains sixpdata and websocket_client modules for ensime) I stumbled across another issue: what if I'm in a nix-shell (with a different python) and I simply want to edit a file with my VIM? Then the setup breaks again as VIM uses the Python from $PATH and yields an error message before opening (and makes ensime unusable).
As I already said, I'm open for further discussion (we can even make this behavior optional, right?), I'm just not sure if we want to use the "new" behavior of VIM 8.1 or keep the behavior of VIM 8.0 where the python from vim_configurable.override { python = ... } was used for plugins.

ping @LnL7

Success on x86_64-linux (full log)
Attempted: vim_configurable
Partial log (click to expand)
/nix/store/za5xymm6hzll89apifwn3kjjblgjj8rr-vim_configurable-8.1.0001/share/vim/vim81/tools/demoserver.py: interpreter directive changed from "/usr/bin/python" to "/nix/store/xlc7ld1xd57ha3x9mbx11c84j290va0f-python-2.7.15/bin/python"
basename: invalid option -- 'w'
Try 'basename --help' for more information.
/nix/store/za5xymm6hzll89apifwn3kjjblgjj8rr-vim_configurable-8.1.0001/share/vim/vim81/tools/ref: interpreter directive changed from "/bin/sh" to "/nix/store/m47apl3hq3i52fzy2cz24378p0xn4lyx-bash-4.4-p19/bin/sh"
/nix/store/za5xymm6hzll89apifwn3kjjblgjj8rr-vim_configurable-8.1.0001/share/vim/vim81/tools/vimm: interpreter directive changed from "/bin/sh" to "/nix/store/m47apl3hq3i52fzy2cz24378p0xn4lyx-bash-4.4-p19/bin/sh"
/nix/store/za5xymm6hzll89apifwn3kjjblgjj8rr-vim_configurable-8.1.0001/share/vim/vim81/tools/vimspell.sh: interpreter directive changed from "/bin/sh" to "/nix/store/m47apl3hq3i52fzy2cz24378p0xn4lyx-bash-4.4-p19/bin/sh"
/nix/store/za5xymm6hzll89apifwn3kjjblgjj8rr-vim_configurable-8.1.0001/bin/vimtutor: interpreter directive changed from " /bin/sh" to "/nix/store/m47apl3hq3i52fzy2cz24378p0xn4lyx-bash-4.4-p19/bin/sh"
/nix/store/za5xymm6hzll89apifwn3kjjblgjj8rr-vim_configurable-8.1.0001/bin/gvimtutor: interpreter directive changed from "/bin/sh" to "/nix/store/m47apl3hq3i52fzy2cz24378p0xn4lyx-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/za5xymm6hzll89apifwn3kjjblgjj8rr-vim_configurable-8.1.0001...
/nix/store/za5xymm6hzll89apifwn3kjjblgjj8rr-vim_configurable-8.1.0001

Success on aarch64-linux (full log)
Attempted: vim_configurable
Partial log (click to expand)
/nix/store/azvwcm4fy9ng848ydha3wlw4zvwk6344-vim_configurable-8.1.0001/bin/vimtutor: interpreter directive changed from " /bin/sh" to "/nix/store/vnb8q2h7951gd551nm2vq2g6n8296g5b-bash-4.4-p19/bin/sh"
/nix/store/azvwcm4fy9ng848ydha3wlw4zvwk6344-vim_configurable-8.1.0001/share/vim/vim81/tools/vimspell.sh: interpreter directive changed from "/bin/sh" to "/nix/store/vnb8q2h7951gd551nm2vq2g6n8296g5b-bash-4.4-p19/bin/sh"
/nix/store/azvwcm4fy9ng848ydha3wlw4zvwk6344-vim_configurable-8.1.0001/share/vim/vim81/tools/vimm: interpreter directive changed from "/bin/sh" to "/nix/store/vnb8q2h7951gd551nm2vq2g6n8296g5b-bash-4.4-p19/bin/sh"
/nix/store/azvwcm4fy9ng848ydha3wlw4zvwk6344-vim_configurable-8.1.0001/share/vim/vim81/tools/ref: interpreter directive changed from "/bin/sh" to "/nix/store/vnb8q2h7951gd551nm2vq2g6n8296g5b-bash-4.4-p19/bin/sh"
basename: invalid option -- 'w'
Try 'basename --help' for more information.
/nix/store/azvwcm4fy9ng848ydha3wlw4zvwk6344-vim_configurable-8.1.0001/share/vim/vim81/tools/demoserver.py: interpreter directive changed from "/usr/bin/python" to "/nix/store/1xkxxrd2sd8q78icm687ac8si9miak45-python-2.7.15/bin/python"
/nix/store/azvwcm4fy9ng848ydha3wlw4zvwk6344-vim_configurable-8.1.0001/share/vim/vim81/macros/less.sh: interpreter directive changed from "/bin/sh" to "/nix/store/vnb8q2h7951gd551nm2vq2g6n8296g5b-bash-4.4-p19/bin/sh"
checking for references to /build in /nix/store/azvwcm4fy9ng848ydha3wlw4zvwk6344-vim_configurable-8.1.0001...
/nix/store/azvwcm4fy9ng848ydha3wlw4zvwk6344-vim_configurable-8.1.0001


Fix publish on tag push, try 2.

Use custom pgp passphrase.
Handle the case when TRAVIS_TAG exists sys.env but is empty.
Only run pgp setup for sonatype release.

The only way to test this is to merge. Let's first double check that sbt shell fires up OK.


Runtime error in a pipeline function is not apparent when running mutation

 Issue by FredyC
Thursday Aug 17, 2017 at 14:52 GMT
Originally opened as https://github.com/graphcool/api-bugs/issues/235

What is the current behavior?
Running just a regular mutation over a type while there is a request pipeline which contains an error ends up with an error message from which it's not apparent where the problem is...

A function returned an unhandled error. Please check the logs for executionId 'eu-west-1:simple:cj6gh8qnshfmj0146nep4r84d

Please share the relevant part of your GraphQL schema and all functions, permissions or other project settings for easier reproduction
Setup a simple request pipeline function with a runtime error that runs with mutation, eg. createUser.
What is the expected behavior?
For starters, it would be nice if error message included the name of the function which failed. To me, this error message wasn't clear that it's actually my custom function failing there (I completely forgot I have it there).
Furthermore, the error message tells you to check the logs for executionId while it's not possible to really find log message by that ID anywhere, not even mentioning a case when there multiple different functions that could be causing a problem.
For a stretch goal, it would be lovely seeing an actual error message from function run in the response payload.

Thanks @FredyC
Thee are several topics here

[ ] Returning the function name is not desired as it is internal to your system, and you might not want to expose it.

[ ] We should improve the error message to make it clear that it is a custom function that failed.

[ ] We should make it possible to search across all logs (by id or message)

[ ] The executionId is eu-west-1:simple:cj6gh8qnshfmj0146nep4r84d but should just be cj6gh8qnshfmj0146nep4r84d

Ok. Just to the first point, I meant the name of my function, not your internal function :) But if it would be possible to search through all logs by ID (from all functions) then it doesn't matter that much. Ideally, if that ID could be just clickable in error message to take me to logs with filtered ID.

A link to the log is a great idea.
I was actually referring to your function :-) These errors will be displayed to your users, and you might not want them to see your function names

Well, that would be only in case I would blindly show errors that server sends. Not very likely :) User will see there was an error and actual error is sent to Sentry for example.
Either way, I wouldn't consider function name to be a security risk. What can you do with it? :)

@FredyC Well, if your function is named 'secretlySendAllUserActivityToCompanyX' then you might have an issue... :smile:

Well, that would be only in case I would blindly show errors that server sends.

No, everyone can inspect the actual network request containing the raw error message.

Not only that, your GraphQL endpoint could always be called directly, and the error would be returned without any additional client-side handling.

@kbrandwijk I guess that if someone names his function like that, then it's obvious begging for "hack it" :D
I am not a security expert, but I cannot see any harm in knowing a name of a regular function. Besides, there is a lot various names representing application logic within a schema. How can one function name (which you cannot access or see source code) do any harm?

I think we've nitpicked enough at this point 😄 We all agree that working with function logs should be a great experience, and it's not at the moment, so let's focus on improving it 🙂

@FredyC Talk to my penetration testing agency. Any information about the internal logic leaking out is bad. Logging it :+1: . Returning it in the response, :-1:


132  add in cart status to products result

Codecov Report

Merging #143 (a2fc425) into main (bb60cf1) will decrease coverage by 0.99%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #143      +/-   ##
==========================================
- Coverage   97.22%   96.22%   -1.00%
==========================================
  Files           7        6       -1
  Lines         577      610      +33
==========================================
+ Hits          561      587      +26
- Misses         16       23       +7

Impacted Files
Coverage Δ

service/models/wishlist.py
93.93% <0.00%> (-6.07%)
:arrow_down:

service/models/product.py
94.02% <0.00%> (-3.56%)
:arrow_down:

service/error_handlers.py

service/models/model_utils.py
94.23% <0.00%> (+0.11%)
:arrow_up:

service/routes.py
99.20% <0.00%> (+1.43%)
:arrow_up:

Continue to review full report at Codecov.

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


Add conda installation note

Just adding a small note about how to install dask-bigquery with conda

Thanks for adding this @jrbourbeau