profile
viewpoint

africlouds/ChatterBot 0

ChatterBot is a machine learning, conversational dialog engine for creating chat bots.

africlouds/docker-erpnext 0

Dockerized ERPNext

africlouds/docker-frappe 0

Dockerized image of Frappe

issue closednodemailer/wildduck

How to send a mail with multiple recipients, but the recipient only sees that the recipient is just himself

How to send a mail with multiple recipients, but the recipient only sees that the recipient is just himself.

closed time in 15 minutes

jet10000

issue commentnodemailer/wildduck

How to send a mail with multiple recipients, but the recipient only sees that the recipient is just himself

It's called BCC: https://en.wikipedia.org/wiki/Blind_carbon_copy

Just use the BCC field in your email client.

jet10000

comment created time in 15 minutes

issue openednodemailer/wildduck

How to send a mail with multiple recipients, but the recipient only sees that the recipient is just himself

How to send a mail with multiple recipients, but the recipient only sees that the recipient is just himself.

created time in 17 minutes

create barnchfrappe/frappejs

branch : dependabot/npm_and_yarn/socket.io-2.4.0

created branch time in 11 hours

PR opened frappe/frappejs

chore(deps): bump socket.io from 2.2.0 to 2.4.0

Bumps socket.io from 2.2.0 to 2.4.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/socketio/socket.io/releases">socket.io's releases</a>.</em></p> <blockquote> <h2>2.4.0</h2> <p>Related blog post: <a href="https://socket.io/blog/socket-io-2-4-0/">https://socket.io/blog/socket-io-2-4-0/</a></p> <h3>Features (from Engine.IO)</h3> <ul> <li>add support for all cookie options (<a href="https://github.com/socketio/engine.io/commit/19cc58264a06dca47ed401fbaca32dcdb80a903b">19cc582</a>)</li> <li>disable perMessageDeflate by default (<a href="https://github.com/socketio/engine.io/commit/5ad273601eb66c7b318542f87026837bf9dddd21">5ad2736</a>)</li> </ul> <h3>Bug Fixes</h3> <ul> <li><strong>security:</strong> do not allow all origins by default (<a href="https://github.com/socketio/socket.io/commit/f78a575f66ab693c3ea96ea88429ddb1a44c86c7">f78a575</a>)</li> <li>properly overwrite the query sent in the handshake (<a href="https://github.com/socketio/socket.io/commit/d33a619905a4905c153d4fec337c74da5b533a9e">d33a619</a>)</li> </ul> <p>:warning: <strong>BREAKING CHANGE</strong> :warning:</p> <p>Previously, CORS was enabled by default, which meant that a Socket.IO server sent the necessary CORS headers (<code>Access-Control-Allow-xxx</code>) to <strong>any</strong> domain. This will not be the case anymore, and you now have to explicitly enable it.</p> <p>Please note that you are not impacted if:</p> <ul> <li>you are using Socket.IO v2 and the <code>origins</code> option to restrict the list of allowed domains</li> <li>you are using Socket.IO v3 (disabled by default)</li> </ul> <p>This commit also removes the support for '' matchers and protocol-less URL:</p> <pre><code>io.origins('https://example.com:443'); => io.origins(['https://example.com']); io.origins('localhost:3000'); => io.origins(['http://localhost:3000']); io.origins('http://localhost:'); => io.origins(['http://localhost:3000']); io.origins('*:3000'); => io.origins(['http://localhost:3000']); </code></pre> <p>To restore the previous behavior (please use with caution):</p> <pre lang="js"><code>io.origins((_, callback) => { callback(null, true); }); </code></pre> <p>See also:</p> <ul> <li><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS">https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS</a></li> <li><a href="https://socket.io/docs/v3/handling-cors/">https://socket.io/docs/v3/handling-cors/</a></li> <li><a href="https://socket.io/docs/v3/migrating-from-2-x-to-3-0/#CORS-handling">https://socket.io/docs/v3/migrating-from-2-x-to-3-0/#CORS-handling</a></li> </ul> <p>Thanks a lot to <a href="https://github.com/ni8walk3r"><code>@ni8walk3r</code></a> for the security report.</p> <h4>Links:</h4> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/socketio/socket.io/blob/2.4.0/CHANGELOG.md">socket.io's changelog</a>.</em></p> <blockquote> <h1><a href="https://github.com/socketio/socket.io/compare/2.3.0...2.4.0">2.4.0</a> (2021-01-04)</h1> <h3>Bug Fixes</h3> <ul> <li><strong>security:</strong> do not allow all origins by default (<a href="https://github.com/socketio/socket.io/commit/f78a575f66ab693c3ea96ea88429ddb1a44c86c7">f78a575</a>)</li> <li>properly overwrite the query sent in the handshake (<a href="https://github.com/socketio/socket.io/commit/d33a619905a4905c153d4fec337c74da5b533a9e">d33a619</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/socketio/socket.io/commit/873fdc55eddd672960fdbc1325ccb7c4bf466f05"><code>873fdc5</code></a> chore(release): 2.4.0</li> <li><a href="https://github.com/socketio/socket.io/commit/f78a575f66ab693c3ea96ea88429ddb1a44c86c7"><code>f78a575</code></a> fix(security): do not allow all origins by default</li> <li><a href="https://github.com/socketio/socket.io/commit/d33a619905a4905c153d4fec337c74da5b533a9e"><code>d33a619</code></a> fix: properly overwrite the query sent in the handshake</li> <li><a href="https://github.com/socketio/socket.io/commit/3951a79359c19f9497de664d96a8f9f80196a405"><code>3951a79</code></a> chore: bump engine.io version</li> <li><a href="https://github.com/socketio/socket.io/commit/6fa026fc94fb3a1e6674b8a2c1211b24ee38934a"><code>6fa026f</code></a> ci: migrate to GitHub Actions</li> <li><a href="https://github.com/socketio/socket.io/commit/47161a65d40c2587535de750ac4c7d448e5842ba"><code>47161a6</code></a> [chore] Release 2.3.0</li> <li><a href="https://github.com/socketio/socket.io/commit/cf39362014f5ff13a17168b74772c43920d6e4fd"><code>cf39362</code></a> [chore] Bump socket.io-parser to version 3.4.0</li> <li><a href="https://github.com/socketio/socket.io/commit/4d01b2c84cc8dcd6968e422d44cb5e78851058b9"><code>4d01b2c</code></a> test: remove deprecated Buffer usage (<a href="https://github-redirect.dependabot.com/socketio/socket.io/issues/3481">#3481</a>)</li> <li><a href="https://github.com/socketio/socket.io/commit/82271921db9d5d2048322a0c9466ffcb09b2a501"><code>8227192</code></a> [docs] Fix the default value of the 'origins' parameter (<a href="https://github-redirect.dependabot.com/socketio/socket.io/issues/3464">#3464</a>)</li> <li><a href="https://github.com/socketio/socket.io/commit/1150eb50e9ce4f15cbd86c51de69df82f3194206"><code>1150eb5</code></a> [chore] Bump engine.io to version 3.4.0</li> <li>Additional commits viewable in <a href="https://github.com/socketio/socket.io/compare/2.2.0...2.4.0">compare view</a></li> </ul> </details> <br />

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


<details> <summary>Dependabot commands and options</summary> <br />

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

</details>

+72 -94

0 comment

1 changed file

pr created time in 11 hours

issue commentyrestom/POS-Awesome

Rounding Total

Hi,

is that ok if i hide the total qty field?

and where should i calculate the write off value so it can be fetched into the field ?

bobzz-zone

comment created time in 2 days

issue commentyrestom/POS-Awesome

Rounding Total

You can check here: https://github.com/yrestom/POS-Awesome/blob/9f2548c0f10fd1aefa04ce251359ff43f482ee96/posawesome/public/js/posapp/components/pos/Invoice.vue#L349

bobzz-zone

comment created time in 2 days

issue openedyrestom/POS-Awesome

[Feature request]: Change posting Date from Pos Awesome

We need to be able to change posting date from PoS Awesome. This is needed for instances when user needs to post back dated entries.

This should be controlled by an option in PoS profile

created time in 3 days

push eventnodemailer/wildduck

Andris Reinman

commit sha 71363e369f8ca83e2cdcc79f30261a7612941e88

use cursor for deleting messages

view details

push time in 6 days

issue commentyrestom/POS-Awesome

Rounding Total

Hi,

this is not a bugs , but i think its more clasified that feature that must have

image **What To Expect ** we need to add rounding total in this section , and the total below need to be rounded.. so the total can be replaced with the grand total in my country or some country , prices need to be rounded for example in my country it should be 100 is the minimum , becuse if below 100 there is no exchange for the customer

bobzz-zone

comment created time in 7 days

issue openedyrestom/POS-Awesome

[Feature request]: Customer Group Change

We need to be able to change Customer Group when creating customers at PoS

created time in 7 days

issue commentyrestom/POS-Awesome

Rounding Total

Can you provide more details about this issue and it will be better if you use this issue template:

IMPORTANT Before reporting a bug:

A properly detailed bug report can save a LOT of time and help to fix issues as soon as possible.

  • ->

Versions

  • Frappe: <!-- ex: V12.13.0 -->
  • Erpnext: <!-- ex: V13.14.0 -->
  • POS Awesome: <!-- ex: V01.0.2 -->

Stacktrace / full error message

(paste here)

Steps to reproduce

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

What is Expected?

What is actually happening?

Additional context

Add any other context about the problem here.

Screenshots

If applicable, add screenshots to help explain your problem.

bobzz-zone

comment created time in 7 days

push eventyrestom/POS-Awesome

Youssef Restom

commit sha 9f2548c0f10fd1aefa04ce251359ff43f482ee96

Update issue templates

view details

push time in 7 days

issue closedyrestom/POS-Awesome

[Bug] Printing Receipts only shows {{body}}

if you select any item and after the payment, when you press the print, it opens a new window and shows {{body}} only at the top left corner of the screen.

closed time in 7 days

Botanium

issue commentyrestom/POS-Awesome

Rounding Total

@yrestom any update on tis ?.. or a clue where i can imporve it ?

bobzz-zone

comment created time in 7 days

created tagyrestom/POS-Awesome

tagVersion-1-0-2

POS Awesome is an open-source Point of Sale for Erpnext using Vue.js and Vuteify

created time in 8 days

push eventyrestom/POS-Awesome

Youssef Restom

commit sha c0735de4389befcb02dabdbe1c9ee6de2325c8b5

fix: remove unused payment's method from sales invoice

view details

Youssef Restom

commit sha 939affe5118eac1223627ddd3580c7fd2f95cdd6

update: README.md

view details

Youssef Restom

commit sha 25029c9ca6e73bd624d88e2bae3f9c5203e603e8

fix: POS not working on IOS 14

view details

Youssef Restom

commit sha 98fb77a99ad5471c43fcdcc8d435a4c5a551cc6e

fix: get batch in V13

view details

Youssef Restom

commit sha 473c7120a580f571a929ce9011cb7fc7c3680f07

Merge branch 'hot-fix1' of github.com:yrestom/POS-Awesome into hot-fix1

view details

Youssef Restom

commit sha e4b1c1208e90ff262be89dae11b576a8b78d2e6a

feat: currency format

view details

Youssef Restom

commit sha f363292f0fd69f01ff41b5ab7816ab4d7f5d1587

Version 1.0.2

view details

Youssef Restom

commit sha 5de77eb58fffd494f571e6098aa3391a88ee4168

Merge pull request #27 from yrestom/hot-fix1 Hot fix1

view details

push time in 8 days

PR merged yrestom/POS-Awesome

Hot fix1
  • fix: remove unused payment's method from sales invoice
  • update: README.md
  • fix: POS not working on IOS 14
  • fix: get batch in V13
  • feat: currency format
+573 -537

0 comment

9 changed files

yrestom

pr closed time in 8 days

PR opened yrestom/POS-Awesome

Hot fix1
  • fix: remove unused payment's method from sales invoice
  • update: README.md
  • fix: POS not working on IOS 14
  • fix: get batch in V13
  • feat: currency format
+573 -537

0 comment

9 changed files

pr created time in 8 days

push eventyrestom/POS-Awesome

Youssef Restom

commit sha f363292f0fd69f01ff41b5ab7816ab4d7f5d1587

Version 1.0.2

view details

push time in 8 days

issue closedyrestom/POS-Awesome

[Bug] Number Format

Hi,

i see that the number on the pirce not fomatted , it should formatted so it will shown separator ex : 100000 -> 100.000

thanks

closed time in 8 days

bobzz-zone

issue commentyrestom/POS-Awesome

[Bug] Number Format

fixed: https://github.com/yrestom/POS-Awesome/commit/e4b1c1208e90ff262be89dae11b576a8b78d2e6a

bobzz-zone

comment created time in 8 days

push eventyrestom/POS-Awesome

Youssef Restom

commit sha e4b1c1208e90ff262be89dae11b576a8b78d2e6a

feat: currency format

view details

push time in 8 days

push eventyrestom/POS-Awesome

Youssef Restom

commit sha 98fb77a99ad5471c43fcdcc8d435a4c5a551cc6e

fix: get batch in V13

view details

Youssef Restom

commit sha 473c7120a580f571a929ce9011cb7fc7c3680f07

Merge branch 'hot-fix1' of github.com:yrestom/POS-Awesome into hot-fix1

view details

push time in 8 days

issue closednodemailer/wildduck

spf: sending host was not verified

Hi, not sure if this is a wildduck issue, a haraka issue , a DNS config issue or even an issue at all. Correct me if necessary.

I've used the install script to setup wildduck Hence for spf I've go this myfirstdomain.com IN TXT v=spf1 a:mail.myfirstdomain.com a:myfirstdomain.com ip4:12.34.56.78 ~all

Then I've added a new domain : myseconddomain.com And I've reused the same config for spf myseconddomain.com IN TXT v=spf1 a:mail.myfirstdomain.com a:myfirstdomain.com ip4:12.34.56.78 ~all

When I send mail from myfirstdomain.com to myseconddomain.com in wildduck-webmail I can see the hint "Mailed by: sending host was not verified" I've got the same result if I send mail from myseconddomain.com to myfirstdomain.com Is this normal? Maybe this is because wildduck is both sender & receiver here and thus does not need to make this control? Or did I got it wrong with the spf configs?

closed time in 9 days

DuredhelFinceleb

issue commentnodemailer/wildduck

spf: sending host was not verified

Use an external service Mail Tester to see if in general everything is set up properly. If you are sending from the same machine then you might have some funky routing issues, eg. like sening from/to 127.0.0.1 or via AWS private interface that are not included in the SPF record.

DuredhelFinceleb

comment created time in 9 days

issue openednodemailer/wildduck

spf: sending host was not verified

Hi, not sure if this is a wildduck issue, a haraka issue , a DNS config issue or even an issue at all. Correct me if necessary.

I've used the install script to setup wildduck Hence for spf I've go this myfirstdomain.com IN TXT v=spf1 a:mail.myfirstdomain.com a:myfirstdomain.com ip4:12.34.56.78 ~all

Then I've added a new domain : myseconddomain.com And I've reused the same config for spf myseconddomain.com IN TXT v=spf1 a:mail.myfirstdomain.com a:myfirstdomain.com ip4:12.34.56.78 ~all

When I send mail from myfirstdomain.com to myseconddomain.com in wildduck-webmail I can see the hint "Mailed by: sending host was not verified" I've got the same result if I send mail from myseconddomain.com to myfirstdomain.com Is this normal? Maybe this is because wildduck is both sender & receiver here and thus does not need to make this control? Or did I got it wrong with the spf configs?

created time in 13 days

issue commentnodemailer/wildduck

open ports

About port 80, yes it has to stay open (unless you're OK with doing DNS-01challenges) It is possible to change nginx config to redirect all requests to 443 save those used by acme.sh

server {
    listen 80 default_server;
    listen [::]:80 default_server;
    server_name  _;
    root /var/www/html;
    location /.well-known/acme-challenge/ {
       try_files $uri =404;
    }
    location / {
        return 301 https://$host$request_uri;
    }
}

Refer to this for a full discussion https://community.letsencrypt.org/t/renewing-via-port-443/106771/3

DuredhelFinceleb

comment created time in 13 days

created tagnodemailer/wildduck

tagv1.32.2

Opinionated email server

created time in 13 days

push eventnodemailer/wildduck

Andris Reinman

commit sha 374c96f07887305138a9a7575e88b4fff9dfc278

updated user delete task

view details

Andris Reinman

commit sha c29e5c867f8d5ea903f565d165273a1aafdeccb5

updated commit hash

view details

push time in 13 days

more