Envoy Sidecar 503 Persists Unexpectedly

Description:
Envoy is configured as a sidecar, targeting a single upstream via loopback.  Downstream service and upstream use http keepalive, preserving the socket between requests.  When the upstream container is forcefully restarted by Docker (i.e. OOM), 503 is reported to Downstream for the entire duration of the upstream container restart.  The socket upstream is dead, but there doesn't appear to be a way to force the downstream socket to close.  The downstream service would need cumbersome logic to not only retry (the test is already doing this), but specifically restart the session toward Envoy sidecar to handle this.  I think I'm missing something in the configuration, but I've tried many different configurations, some of them impact closure timing of either the upstream or downstream socket.  None of them seem to propagate an upstream socket disconnect to the downstream socket (or http keepalive), even if all upstream hosts are dead in the cluster (and the Envoy knows this with the alternate configuration attempted).
Is there a specific configuration where the Envoy instance is configured to understand that it is a sidecar serving a single upstream endpoint and behave differently?  Even with a service mesh where the downstream endpoints might be able to react, this seems meaningful in a sidecar to minimize the work that downstream entities have to do.
Setup:
Although I simplified the below Envoy config for testing purposes.  We use the Envoy sidecar to:

offload JWT validation on incoming traffic.
To route HTTP to either the main application container, or to other sidecar(s) that have specialized functions such as offloading http subscription & notification functions.
lua filter that handles readiness and liveness probe routing as well as jwt scope validation.

We don't use Envoy as a part of a service mesh at this time.  Each Envoy sidecar is directly configured to perform these offloading functions.
I noticed that other Envoy sidecar implementations don't use the http connection manager (particularly in a service mesh), but it is needed in our usage.
In our real environment where the issue was discovered, a Quarkus app is communicating from within our AKS cluster to another service on the same cluster.  The target app has 3 instances/pods, each comprised of an Envoy container and an application container.  Envoy 1.16, but tested on Envoy 1.19.
In two private developer PCs, running kubernetes baked into Docker Desktop and microk8s respectively, the client/downstream app has been replaced with the below test Python app.  The upstream service has been replaced with the linked quarkus-example to simplify.  Tested on Envoy 1.16 and 1.18 latest.
Envoy Config:
apiVersion: v1
kind: ConfigMap
metadata:
  name: quarkus-example-envoy-alpinev1.16-config
data:
  envoy.yaml: |
    admin:
      access_log_path: /dev/null
      address:
        socket_address:
          address: <IP_ADDRESS>
          port_value: 9001
    static_resources:
      listeners:
      - name: listener0
        address:
          socket_address:
            address: <IP_ADDRESS>
            port_value: 9090
        filter_chains:
        - filters:
          - name: envoy.filters.network.http_connection_manager
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
              access_log:
              - name: envoy.access_loggers.file
                typed_config:
                  "@type": type.googleapis.com/envoy.extensions.access_loggers.file.v3.FileAccessLog
                  path: "/dev/stdout"
                  log_format:
                    json_format:
                      v: "1"
                      "@timestamp": "%START_TIME%"
              stat_prefix: ingress_http
              route_config:
                name: local_route
                virtual_hosts:
                - name: local_service
                  domains: ["*"]
                  routes:
                  - match:
                      prefix: /
                    route:
                      cluster: __DEPLOY_KUBERNETES_APPNAME__

              http_filters:
              - name: envoy.filters.http.cors
              - name: envoy.filters.http.router

      clusters:
      - name: __DEPLOY_KUBERNETES_APPNAME__
        connect_timeout: 0.25s
        load_assignment:
          cluster_name: __DEPLOY_KUBERNETES_APPNAME__
          endpoints:
          - lb_endpoints:
            - endpoint:
                address:
                  socket_address:
                    address: <IP_ADDRESS>
                    port_value: 8080

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: quarkus-example
  namespace: default
spec:
  selector:
    matchLabels:
      app: quarkus-example
  replicas: 2
  template:
    metadata:
      labels:
        app: quarkus-example
        redeploylabel: sixes
    spec:
      # securityContext:
      # runAsUser: 911
      containers:
        - name: quarkus-example
          image: localhost:5000/quarkus-example
          imagePullPolicy: Always
          env:
          - name: ENVOY_UID
            value: "0"
          ports:
            - name: http
              protocol: TCP
              containerPort: 8080

        - name: envoy
          image: envoyproxy/envoy:v1.18-latest
          imagePullPolicy: Always
          ports:
            - containerPort: 9090
          volumeMounts:
            - name: envoy-config-volume
              mountPath: /etc/envoy
              readOnly: false
            - name: pod-temp-cache
              mountPath: /tmp
      volumes:
        - name: envoy-config-volume
          configMap:
            name: quarkus-example-envoy-alpinev1.16-config
        - name: pod-temp-cache
          emptyDir: {}

---
apiVersion: v1
kind: Service
metadata:
  name: quarkus-example
  namespace: default
  labels:
    app: quarkus-example
spec:
  type: ClusterIP
  ports:
    - port: 80
      protocol: TCP
#      targetPort: 8080
      targetPort: 9090
  selector:
    app: quarkus-example

Test:
Have tested in kubernetes that comes with Docker desktop, as well as in microk8s.  Live system presenting the issue is AKS.

Deploy any upstream service that implements an http endpoint.  I used both Quarkus-Example and a Python Flask app to make sure this wasn't related to just Quarkus.
Deploy an Envoy sidecar for that service with the above Envoy configuration.
Use a test client that preserves the http session between http requests.  The below Python code will do it.
Run the client to watch 200 vs. 503 responses.
Execute kubectl exec -it quarkus-example-<POD ID> -c quarkus-example -- /bin/sh -c "kill 1" to kill the application container, but not the Envoy container.  note: you may have to execute against the other deployed pod and you may have to execute more than once to get a long enough restart time from Docker.
Result: client service receives 503 for the entire duration that the application container is down for a restart.
Expected result: The downstream socket is closed by Envoy which would allow the downstream client to open a new socket which would be directed to the alternate Envoy by k8s.  Even if this requires outlier detection and disabling healthy panic, so that Envoy knows that it has no remaining upstream path.  I tried the following, but 503 was still returned and downstream socket remained up.

Alternate outlier configuration attempted, which changes the response body, but not the response code:
outlier_detection:
  split_external_local_origin_errors: true
  consecutive_local_origin_failure: 1
  max_ejection_percent: 100

common_lb_config:
  # disable healthy panic
  healthy_panic_threshold:
    value: 0

Simple Python Client:
import requests
import time
from datetime import datetime

s = requests.Session()

while True:
  try:
    r = s.get('http://localhost:8181/hello/')
  except:
    print("something went wrong")
    exit()
  print(r.status_code, " - ", r.content, " - ", datetime.now())
  time.sleep(1)

note: Docker's built in k8s didn't allow direct connection to service port 80 on my PC, so I port forwarded 8181 to 80.  kubectl port-forward service/quarkus-example 8181:80

retry_on connect-failure,gateway-error is probably what you want
https://www.envoyproxy.io/docs/envoy/latest/faq/load_balancing/transient_failures

Thank you lambdai,
The link that you provided is for load balancing.  In my case, this is a non-service-mesh implementation of a sidecar that has only one upstream.  One of the configurations that we attempted was to allow the upstream lb cluster to go completely OOS with outlier detection and lb_config.  Essentially, trying to tell the Envoy sidecar that it only had one upstream rather than an actual cluster to choose from.  This changed the behavior slightly.  Before testing this configuration the 503 response only contained the connection error.  After this configuration, the response body indicated that there were no available upstreams, but the socket between downstream and Envoy sidecar remained up.
If you meant retries within the sidecar until the app container is available, this isn't our desired outcome.  In one instance in our real environment it took 12 seconds for the app container to fully start.  We want the downstream socket to disconnect, so that the retry from the downstream will be routed to another POD that is healthy.
In continuing the investigation, we also tried a lua filter to listen for the upstream connection closure and close the downstream connection.  The close option on the downstream was not available.

I haven't been able to update this as I was pulled to another matter for our current sprint.  This is still plaguing us.  How does one mark this as help wanted?  We will be implementing a Service Mesh soon, which should hide this issue, but I think fixing this or implementing it, or finding a configuration to work around the issue would make things more efficient, even in a service mesh.  Less retries in the service mesh.


podEnergyStatLabels need updates

Describe the bug
A clear and concise description of what the bug is.
NodeMetricsStatLabels, podEnergyStatLabels that are kept for the model server are from very old version. Some metrics are not used anymore. Some metrics are missing.

value with total_ prefix is not used anymore.
there is no meaning to add prefix curr_, node_ in the label (it will be removed when training).
cgroup features are missing. The feature list should not be hardcode as below.

https://github.com/sustainable-computing-io/kepler/blob/c8f0528980944d3952f001ac09cd4e285cebe73e/pkg/collector/prometheus_collector.go#L40-L80
Should use the metric name list from ContainerMetricNames.
https://github.com/sustainable-computing-io/kepler/blob/c8f0528980944d3952f001ac09cd4e285cebe73e/pkg/collector/metric/utils.go#L53
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

https://github.com/sustainable-computing-io/kepler/commit/3a31c95a5a3f3e28aee9e24bc6fc8e0ed5f20318
Need to rebase and merge this commit to dynamically set the label instead of fixed list.
Or, move to individually export metric one by one instead of string labels (overhead needs to be investigated).


fetchMixDeps: sha256 -> hash

Description of changes
small PR to make fetchMixDeps use hash instead of sha256
@NixOS/beam I'm not sure if we are supposed to be backward compatible and continue to support sha256.
@SuperSandro2000 coming after you mentioned switching a function to hash
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
23.11 Release Notes (or backporting 23.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.

Result of nixpkgs-review pr 235733 run on x86_64-linux 1

As of right now the function should support both sha256 and hash

Result of nixpkgs-review pr 235733 run on x86_64-linux 1


Move Pod from ClusterRole to Role

I am guessing you verified this with the roles in the manifests right?

No. I'm relaying on our chart testing test suite.
In our operator code the definition is scoped to namespace only https://github.com/redpanda-data/redpanda-operator/blob/6c288ea2d50c57e2fe8cde38c624554c348b8036/src/go/k8s/internal/controller/redpanda/redpanda_decommission_controller.go#L37


Fix build

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@fd3562f). Click here to learn what that means.
The diff coverage is 50%.

@@            Coverage Diff             @@
##             develop     #146   +/-   ##
==========================================
  Coverage           ?   91.36%
==========================================
  Files              ?        3
  Lines              ?      139
  Branches           ?       10
==========================================
  Hits               ?      127
  Misses             ?       12
  Partials           ?        0

Impacted Files
Coverage Δ

...main/scala/com.snowplowanalytics/forex/Forex.scala
93.75% <50%> (ø)

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 fd3562f...ec345de. Read the comment docs.


Use YuNet of fixed input shape to avoid 'parseShape' error

I ran the latest version of face_detection_yunet on AGX, with OpenCV 4.5.5, with backend CUDA and target CUDA, and received error -220, unsupported format or combination of formats, onnx_importer.cpp:199.  I was using the face_detection_yunet_2022mar.onnx file.  Don't know if this is related to above or not.

@bwmcin There is a tracking issue https://github.com/opencv/opencv_zoo/issues/31 for the simular problem. Let me reproduce it and see what the problem is.


AppVeyor

:white_check_mark: Build MarkdownPS 1.0.1 completed (commit https://github.com/Sarafian/MarkdownPS/commit/fd758dd5a4 by @)


Object literal with spread property does not correctly overwrite properties

var o1 = { foo: 0 };
var o2 = { ...o1, foo: "" };
var foo = o2.foo;

foo is number | string, instead of string.

Hunting/blaming around the source makes me think @mroch might have some upcoming changes/wip here?

Any news on this?

See also: #6108, #6800, and probably many more; the problem has been cropping up quite a bit and cause erroneous typing rejections when the object types aren't inferred.

@samwgoldman made a PR that fixes this: https://github.com/facebook/flow/pull/7298

This has the expected behavior on master


Test pointpillars model on different -number of layers and points per second-  lidar data from it's training data

What kind of preprocessing i need to do in point cloud  to get good detection results when i test pointpillars pretrained on lyft dataset on velodyne vlp 32 c lidar data ,
The inference code is working but the model detect many false positive objects
Thank,

You may need to confirm whether  your own data's coordinate system is the same as the pre-trained model's coordinate system. And we recommend that you use your own data to train an new model, more details you can refer to this

Close due to inactivity.


run formatting, add mix.exs docs arguments & bump some deps

closes #14
This also adds source_url and docs keys that includes readme and defaults to readme as default page which is more information imo.

Thanks @techgaun!


Update http4s-client, http4s-core to 0.21.24

Updates

org.http4s:http4s-client
org.http4s:http4s-core

from 0.21.18 to 0.21.24.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch

Superseded by #279.


continuing anyway - failed to get ocsp response: OCSP responder query failed (http://ocsp.int-x3.letsencrypt.org): ocsp.int-x3.letsencrypt.org could not be resolved (110: Operation timed out), context: ssl_certificate_by_lua*,

SSL stopped working in between I am using https://github.com/Valian/docker-nginx-auto-ssl.
curl -6 -IL ocsp.int-x3.letsencrypt.org gives cannot connect to server . Normal curl is  working .

curl -6 -IL ocsp.int-x3.letsencrypt.org
HTTP/1.1 200 OK
Server: nginx
Content-Length: 0
Cache-Control: max-age=25508
Expires: Wed, 06 Nov 2019 18:24:22 GMT
Date: Wed, 06 Nov 2019 11:19:14 GMT
Connection: keep-alive

your IPv6 setup is broken.

It was working fine, and suddenly stops working , I am using GCP to run the docker, tried setting resolver <IP_ADDRESS> ipv6=off. Still same error is coming.

; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> @<IP_ADDRESS> ocsp.int-x3.letsencrypt.org
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

dig @2001:4860:4860::8888 ocsp.int-x3.letsencrypt.org AAAA
; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> @2001:4860:4860::8888 ocsp.int-x3.letsencrypt.org AAAA
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

You just have a broken network... it's not up to this project maintainers to help you on this...
Can you resolve any other domain ? Can you check your docker runner has not shut off the DNS port  somehow ?

I am not able to resolve it using <IP_ADDRESS> but able to when i used <IP_ADDRESS>
dig @<IP_ADDRESS> ocsp.int-x3.letsencrypt.org
; <<>> DiG 9.11.3-1ubuntu1.9-Ubuntu <<>> @<IP_ADDRESS> ocsp.int-x3.letsencrypt.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33083
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;ocsp.int-x3.letsencrypt.org.	IN	A
;; ANSWER SECTION:
ocsp.int-x3.letsencrypt.org. 1156 IN	CNAME	ocsp.int-x3.letsencrypt.org.edgesuite.net.
ocsp.int-x3.letsencrypt.org.edgesuite.net. 5550	IN CNAME a771.dscq.akamai.net.
a771.dscq.akamai.net.	19	IN	A	<IP_ADDRESS>
a771.dscq.akamai.net.	19	IN	A	<IP_ADDRESS>
a771.dscq.akamai.net.	19	IN	A	<IP_ADDRESS>
;; Query time: 19 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Wed Nov 06 12:00:10 UTC 2019
;; MSG SIZE  rcvd: 190

I think I figured it out, GCP has issues with using <IP_ADDRESS> as DNS resolution. And I have to manually specify resolver <IP_ADDRESS> ipv6=off; in nginx.conf http section.

https://github.com/Valian/docker-nginx-auto-ssl/issues/32 Solved the issue. Thanks for the help. It was definitely a network mishap from GCP I guess.


✨ Implement a default cover for the Radial theme

Summary
Created a default cover for the Radial theme.
Checklist

[ ] I have fully tested all of the added features
[ ] I have fully documented all of the relevant code

Additional Notes

In the future please use our commit style. Check the contribution guide to see what that looks like.


Differentiate error codes for different failure cases

In collaboration with Karma - see the list at
https://github.com/karma-runner/karma/issues/1976

This would make it a lot easier to integrate with other tools - ie gradle, jenkins, etc, to be able to get an idea of what happened without lots of extra test result parsing work.


Tracking

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Device/Platform oriented tracking
Bug fixes
DB ex-/import scripts
WSL adjustments for developer
QOL changes for frontend development
EMBA updates

What is the current behavior? (You can also link to an open issue here)
bugs and stuff
What is the new behavior (if this is a feature change)? If possible add a screenshot.
1.New tracking application

improvements to EMBA analysis arguments from uploader application

Version history visualization

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
❗ DB schema changes

Without sudo the installer failes hard and does not complain the missing privs:


Allow setting repo user and hostname

Allows sourcing info about repo user/hostname from
both the config file and flags for maintenance.
Since user/hostname mostly matters for maintenance
don't add the flags for all commands.
Do allow config file parameters for them since
that has a lot of repo-level information already.
Currently not setup to persist these values in the
config file

Does this PR need a docs update or release note?

[ ] :white_check_mark: Yes, it's included
[x] :clock1: Yes, but in a later PR
[ ] :no_entry: No

Type of change

[x] :sunflower: Feature
[ ] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Supportability/Tests
[ ] :computer: CI/Deployment
[ ] :broom: Tech Debt/Cleanup

Issue(s)

#3569

Test Plan

[x] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

LGTM - we should follow up with a change that persists in config file right?


Multi participants chat avatar

Details
The primary goal was to get the avatarUrls of the participants in the group chat to the ChatLinkRow.js and render an icon for the group chat using them.
So I changed the prop icon ( the URL string of single DM participant )  to icons  ( an array of all avatar URLs of participants in a chat) in ChatSwitcherOptionPropTypes.js.
And in the  PersonalDetail.js, In the getFromReportParticipants, I got the avatar urls of all participants and saved to the icons options.
The ChatLinkRow component is used in 2 parts throughout the application: SidebarLink.js and ChatSwitcherList.js.
In both parts,  i changed the icon option passed to the ChatLinkRow component to icons.
In the ChatLinkRow component, with the avatarUrls of the participants, I rendered the group icons with the circular counter depending on the number of participants. I wrote a few lines of codes for styling the new group icons in the styles.js .
Fixed Issues

Fixes https://github.com/Expensify/Expensify.cash/issues/1064 #
Tests

Once you are logged in, Begin a chat with 2 or more additional participants.
You see that there are avatars displayed for the chat participants.
It'll probably be misaligned because of this other issue https://github.com/Expensify/Expensify.cash/issues/1031. So refresh.
When a chat has 3 participants, the avatars of the 2 other participants are shown.
When a chat has 4 or more participants, the avatar of the user whose username comes first and a circular counter for the number of chat participants is shown

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

I have read the CLA Document and I hereby sign the CLA

Hey @oshioked - I put together a quick design guide for you to use to try and match the exact styles we want.

Figma file is here: https://www.figma.com/file/oSLkN3QfBGzpaTaPnRnQND/Row-Styles?node-id=151%3A695

Hey @shawnborton! Thank you for the guide. I've fixed it to match the required style. Please verify.

Hi @oshioked - have you updated the screenshots in the first comment above?

Hi @oshioked - have you updated the screenshots in the first comment above?

Yeah. I just did that. Check it out.

Thanks for the updated screenshots. It looks as though the counter number is not quite vertically centered within the gray circle. Can you take another look at that?

A simple way to do that might be to give the counter a lineHeight: 24 - the same height as the smaller avatar circles.

@shawnborton I noticed that after updating the screenshot too. I thought I'd get away with that. Lol.
No worries. I just inspected it and it turns out it's a line height problem. Fix coming right up.

A simple way to do that might be to give the counter a lineHeight: 24 - the same height as the smaller avatar circles.

Done. Thanks.

Awesome, thanks for the quick work. I took this for a spin and I don't think I like how the background color of the counter circle changes if the row is active or not - that's my fault for suggesting that. Instead, let's make the background color gray3 for both cases, with textReversed (white) as the text color of the counter.

Hi @shawnborton. I've fixed the circular counter to meet the changes.

Updated

Hey @oshioked thanks for your work on this. Just a heads up we have merged another PR that implemented this feature. At this point, I'm going to close this one out since it's no longer needed. Feel free to tackle another issue if you'd like.

Hey @oshioked thanks for your work on this. Just a heads up we have merged another PR that implemented this feature. At this point, I'm going to close this one out since it's no longer needed. Feel free to tackle another issue if you'd like.


Added test to airport db implementation

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (e6d4496) 72.26% compared to head (d883ccf) 77.46%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #26      +/-   ##
==========================================
+ Coverage   72.26%   77.46%   +5.19%
==========================================
  Files          14       14
  Lines         750      750
==========================================
+ Hits          542      581      +39
+ Misses        208      169      -39

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[Paused] Market guide scrolling issue

Original issue #1583
You can open the guide by clicking help in the bottom corner of the exchange.

Closed without solution


"Please enter wallet password" request not needed?

When I start my validator I'm asked:
Please enter your wallet password:
The code for this seems to come from here
What is this used for? The validator keys are stored in the corresponding file under /validators

Yes it reads the password into memory to be able to pipe it to the actual client. The client (like prysm) itself needs to run as a non-interactive daemon so that it does not affect or connect to the current tty.

Your 'yes' refers to my question that it's not needed or something else?
So I'm using lighthouse and I don't know why I'm asked to enter a wallet password.

It is needed to get the password for the wallet unless you're providing the password within a file and pointing to it. I.e. the validator needs to read it on startup

Oh I see you're being asked for the password earlier than required. I will check.

I imported my validators pointing to a pw file. Lighthouse stores the password for each validator in a file. When the import is done there is no need to ask lighthouse users for any password as the password is used from the file lighthouse generated during the validator import.
I can't check the file name right now. But it is the the validator folder.

Here you find the official documentation of lighthouse about the validator password storage. They store the name and password of each validator in the validators_definition.yml .
So the prompt should only appear when there is a validator in the validator_definitions.yml where the password field is empty. Otherwise skip it because every validator has a password set.
The prompt otherwise blocks automated restarts of the service.

As a workaround you can provide the password file option pointing to a dummy file.
So if you defined --validator-wallet-password to point to a file it will not prompt and send that file which should then be ignored. That might be a workaround until we repair this.


 Switch to crypto.rand to prevent that.

Thank you, I used math/rand for testing, and forgot to change to crypto/rand before committing. I changed it to crypto/rand now


Hide empty sidebar

Collapsing the sidebar:
Collapsed Sidebar.webm

For some reason, the first time attempting to open "Add Pet", I need to click twice on the "+" button:
Clicking Twice.webm
Subsequent attempts require only one click.

Fix: show "Add Pet" on single click
The first time launching the app, that is, you have no pets and the sidebar is collapsed, you need to click the "+" button twice for the "Add Pet" view to appear.
Subsequent times required only a single click.
My assumption is that it has to do with deciding which side of a split view to show as a full view.
It starts showing the sidebar side, the "No Pets Yet" view, then it should show "Add Pet", which is in the content side.
To decide whether to switch sides or not, I check model.content.model().visible_pane against Panes::AddPet.
However, I think content is only updated after model, so the view wouldn't see the updated value ::AddPet.
The next time you click "+", it would check again and this time it would coincidentally have the correct value (from the previous update).
That's how I think it works, at least.
Sending a dummy message from content to app forces it to see the correct value, requiring only a single click always.
This solves the issue, but ideally it would just send this message when the sidebar is collapsed, but I couldn't think of anything worth the trouble of implementing.
The solutions I though of required messaging between these components anyway.
Not worth the trouble.
Better to have this simple workaround.

I fixed the issue:
Single Clicking.webm
I think it had to do with whether to show the sidebar side or the content side of the split view as a full view.
It initially shows the sidebar side ("No Pets Yet"), then should show "Add Pet", which is in the content side.
It checks whether content is currently showing "Add Pet" via .visible_pane.
More precisely, app does this via model.content.model().visible_pane, but I think content is only updated after app is, so it would effectively miss the first click.
The second click should make app check it again, and visible_pane would coincidentally have ::AddPet as value (from the first click) and it would work.
I just made content message app when "Add Pet" is the current view, so it shows the correct view.


ASim fixes

Fixes #

Fixed ASim DnsEmpty ARM by removing the  duplicate EventSeverity column
Fixed Barium and Iridium rules to call imDns correctly with parameter response_has_ipv4

Proposed Changes

Changed imDns Host collumn value to Dvc in Barium rule to correct entity mapping
Changed watchlist alias of ASimDisabledParsers in ARM to be plural as since alle rules call _GetWatchlist('ASimDisabledParsers')

Thanks @rjaakke! Your conrtibution to ASIM is very welcomed. Keep it coming.
@YaronFruchtmann is the expert and will review, but two comments from me:

Are you sure Dvc is the value you want to map to host? It includes the DNS server information rather than the client issuing the DNS request. I think that SrcIpAddr is a better value. DNS events usually do not have hostname information for the source system.
Thanks for noticing the duplicate EventSeverity. I think @YaronFruchtmann fixed it a few days back, so you might be working not of the most recent branch.

~ Ofer

Hi Ofer,
I reverted host mapping.
The duplicate EventSeverity was indeed fixed in the parser but the ARM template wasn't updated.


[INFRA/eyes][Feature] support github action cache for docker images

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Every run of skywalking-eyes takes 1min to build the docker image. I guess GHA cache can be utilized to speedup that...
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

@xxchan If you are not going to submit a pull request for this, I think this is not a planned feature for maintainers. I am going to move this to discussion. If you want contribute, please let me know.

Ok please move to discussion. I'm willing to do that but not recently.


Fix build on nightly rustc

Hi.
https://github.com/rust-lang/rust/pull/42125 is going to turn some old compatibility "private-in-public" warnings in rustc into hard errors.
crates.io testing discovered that published version of this crate is affected by one of those errors.
This PR updates the code to build successfully with https://github.com/rust-lang/rust/pull/42125

@dpc
Could you also publish a new minor version with this fix on crates.io?

Done. Thanks!


Hey man. Forked the project.

I just wanted to let you know I forked this for fun.
I just quickly and poorly frankensteined together an object-oriented version from other stuff I had lying around.
Lots of bad python-code, and generally bad coding (I'm just a hobbyist script-kiddie),
And I also maaaaay have had a glass or two of wine...
But maybe there's some cool tkinter things or tricks in it you find useful.
Some new features are:

Styling/black color scheme

Uses a class. Just uncomment the line with self.styler in the __init__  of MainWindow if you don't wanna use it.

The entry fields are scrollable

Note: It doesn't like all diagonal scrolling on touchpad.
It causes jittering because every other event is the opposite "button".
And I've only tried touchpad scrolling on Linux. I think the or-check catches Windows events but not sure

Shift up / down selects the word the text cursor is in or selects all text if something is selected
You have undo/redo now
It cobbles together the path from the executable's folder and the given filename
You can only save the file if you have a filename

also it checks if the executable exists, but not if the directory can be written to

File is saved using with open, and I added an error-message on failure

Check it out it if you liked tkinter, and anyways ty for the fun :)

That's hilarious. This is great, thanks!
This is some completely unmitigated "dirty underwear" code that I decided to upload on a lark because I'm making a blog that I've barely shared with anyone yet, and here you found it randomly and put some actual effort into it. Amazing.
https://aaronsavage.net/2024/02/21/i-wish-id-learned-tkinter-sooner/
Maybe I'll kick this around a little more and we'll end up with something others will find useful. I didn't think anyone would even look at the code, let alone fork it. If I were going to take this seriously, it would need a few features that would take a bit more work, like editing existing shortcut files while preserving their unaffected fields, and some way to preview the icons. I'd also really like it if I could integrate it into a file manager. As a minimum, I could make it take a filename as an argument so people could "Open With..." to pre-populate the fields. It wouldn't be all that much work to make something legit, and you've got it off to a good start here.
Open source is a beautiful thing.

Yeah, I was just farting around looking at tkinter stuff, cause I've been playing around with the kit lately myself.
Then your project popped up in most recent, and was just a perfect little idea for an evening and a real nice start.
Yeah, also the idea about letting it take a file as an argument is real good.
Reading the lines and finding the corresponding fields should be somewhere between easy and doable.
But there are a lot of possible keys in a desktop-file I think (= a lot of fields?), so some way to dynamically add fields?
Maybe using like a Combobox to select/add specific key-fields, and a Frame+Scrollbar for to put them in?
Maybe a more hobby-friendly version is based around selecting some templates of "types of" desktop-files, then creating frames with fields for the templates?
E.g. like one template for a game-shortcut, and one for a metadata-desktop-file used when making plasmoids, and so forth.
Anyways something a little more fleshed out and dynamic like that could be a very nifty tool.
Making a ~/.local/kservices5 .desktop-file for user-added right-click-context-menu-entry that accepts a file-URL is at least real easy to make  on KDE. Dunno about other distros, but I suspect they're not putting up roadblocks
(Well, maybe gnome does, cause it feels like an Apple-thing to do :P)
I've done some tweaking just now btw - discovered some blunders (there are for sure more), so I highly recommend a very critical read-through before you use it to build something serious.
To illustrate the quality of my work and your possible foundation: It is literally made by a drunk fool, and there are poop jokes in the source code.


Add topic filter in "more topics" view in left sidebar

In a stream with many topics, it can be difficult to find an old topic you want to go back to.
To solve this, we should add a search box to the "more topics" left sidebar view, just below the name of the stream.

When the user clicks on "more topics", their cursor should be automatically placed into the search box. Typing into it should dynamically filter the list of topics in the stream using the same function as the filtering in Recent Topics (currently topic_in_search_results). The filter should not reorder the list of topics.

@zulipbot claim

Watching @m-e-l-u-h-a-n's progress eagerly!...

I have made PR #18724 for this. It got little delayed as I was busy with lot of other issues.


Stuck while compiling on windows

OS: Windows x64
GHC: 8.4.4 and 8.6.5
While compiling, the following warning is shown:
src\Text\Printer\Integral.hs:656:1: [;1mwarning:[;1m[;1m
Forall'd constraint `Ord �' is not bound in RULE lhs
  Orig bndrs: [�, p, $dOrd_amc3, $dIntegral_amc4, $dPrinter_amc5]
  Orig lhs: let {
              $dPrinter_amcc :: Printer p
              [LclId]
              $dPrinter_amcc = $dPrinter_amc5 } in
            let {
              $dIntegral_amcb :: Integral �
              [LclId]
              $dIntegral_amcb = $dIntegral_amc4 } in
            let {
              $dPositionalSystem_amc9 :: PositionalSystem Binary
              [LclId]
              $dPositionalSystem_amc9
                = Text.Printer.Integral.$fPositionalSystemBinary } in
            let {
              $dReal_aow8 :: Real �
              [LclId]
              $dReal_aow8 = GHC.Real.$p1Integral @ � $dIntegral_amc4 } in
            let {
              $dOrd_aowb :: Ord �
              [LclId]
              $dOrd_aowb = GHC.Real.$p2Real @ � $dReal_aow8 } in
            let {
              $dOrd_amca :: Ord �
              [LclId]
              $dOrd_amca = $dOrd_aowb } in
            number'
              @ Binary
              @ �
              @ p
              $dPositionalSystem_amc9
              $dOrd_amca
              $dIntegral_amcb
              $dPrinter_amcc
  optimised lhs: number'
                   @ Binary
                   @ �
                   @ p
                   $dPositionalSystem_amc9
                   $dOrd_amca
                   $dIntegral_amc4
                   $dPrinter_amc5

Then compiling somehow doesn't progress.
Logs can be seen here https://ci.appveyor.com/project/steve-chavez/postgrest/builds/25506383.
text-printer used to work normally on GHC 8.0.2 on windows.
Any pointers would be greatly appreciated.

On ubuntu 32 bit I get an error with text-printer as well https://circleci.com/gh/PostgREST/postgrest/3313?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link. Though this one quits.

The problem also occurs when building text-printer stand-alone with GHC 8.6.5 / stackage lts-13.27: https://ci.appveyor.com/project/robx/text-printer/builds/25781889
Changing the alpha to a doesn't help. Removing the offending SPECIALIZE pragmas does:
https://ci.appveyor.com/project/robx/text-printer/builds/25782098

same behaviour with GHC 8.4.4 / stackage lts-12.26:
https://ci.appveyor.com/project/robx/text-printer/builds/25782417

I have fixed the warning in dd8a404, see if it helps with the compiler hangup.

Indeed, that fixes it. I'll go ahead and file a bug report with ghc.

GHC bug report: https://gitlab.haskell.org/ghc/ghc/issues/16917

The fix is on Hackage (version <IP_ADDRESS>), I'm closing the issue. BTW, it would help GHC devs if you could provide a reduced test case (start with number' and strip all dependencies to other parts of the library).


feat: Mass list add again feature

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context

[x] Closes #7326

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot 📸

[x] My fix has changed something on UI;

Copilot Summary

🤖 Generated by Copilot at cbf6239
This pull request adds the ability to discard items from the listing cart without deleting them, and to clear the discarded items when the listing cart modal is closed. It also updates the UI components and the reactive stores to handle the discarded state and the price adjustments of the items. It affects the files ListingCartItem.vue, ListingCartMultipleItemsCart.vue, ListingCartItemDetails.vue, listingCart.ts, ListingCartModal.vue, and ListingCartSingleItemCart.vue.

🤖 Generated by Copilot at cbf6239

Sing, O Muse, of the skillful coder who devised
A clever way to manage the listing cart, where stored
The items that the users wished to sell for a fair price
But could discard or change at will, with ease and grace.

nice job!

pay 50 usd

😍 Perfect, I’ve sent the payout
💵 $50 @ 3.82 USD/DOT ~ 13.089 $DOT
🧗 13QUj3pZyFNfYj4AM336hRdyLQbevj5H3sR4PKmLEXLdwZhh
🔗 0x221a28668adc2203a662b88b24fef2a1c44dafae78d272542f8e336eafd17b77
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Roboto Slab?

Will Roboto Slab ever be included here?

I would like to set it up with its own source repo :)


VAT fails with ShaderMaterial

VAT doesn't work with a ShaderMaterial, PG that reproduces the error: https://playground.babylonjs.com/#11GAIH#153
BJS - [17:55:14]: Error: VERTEX SHADER ERROR: 0:45: 'matricesIndices' : undeclared identifier

This is because NUM_BONE_INFLUENCERS is not defined. This patch defines it.

In fact there is a bug in your PG, you must define finalWorld for the code injected by #include<bonesVertex> to work.
If you look at the console log at the first error log, you will see it is:
BJS - [22:50:35]: Error: VERTEX SHADER ERROR: 0:34: 'finalWorld' : undeclared identifier

The error with matricesIndices is not the true error: when a shader does not compile, Babylon is trying to remove some features   from the shader and recompile (it is the "fallback" mechanism). If it still does not work it still try to remove some other features and so on, a number of times. So, when you get a shader compilation error, you should always locate the very first error because the others can be different because of the code removed.
Also, you must use finalWorld matrix to transform the vertex. See https://playground.babylonjs.com/#11GAIH#155
Even after these corrections the PG still does not work because of a bug in ShaderMaterial: the uniforms/samplers used by BVA are not defined. The block at lines 731-739 should be replaced with:
if (mesh) {
    const bvaManager = (<Mesh>mesh).bakedVertexAnimationManager;

    if (bvaManager && bvaManager.isEnabled) {
        defines.push("#define BAKED_VERTEX_ANIMATION_TEXTURE");
        if (this._options.uniforms.indexOf("bakedVertexAnimationSettings") === -1) {
            this._options.uniforms.push("bakedVertexAnimationSettings");
        }
        if (this._options.uniforms.indexOf("bakedVertexAnimationTextureSizeInverted") === -1) {
            this._options.uniforms.push("bakedVertexAnimationTextureSizeInverted");
        }
        if (this._options.uniforms.indexOf("bakedVertexAnimationTime") === -1) {
            this._options.uniforms.push("bakedVertexAnimationTime");
        }

        if (this._options.samplers.indexOf("bakedVertexAnimationTexture") === -1) {
            this._options.samplers.push("bakedVertexAnimationTexture");
        }
    }

    MaterialHelper.PrepareAttributesForBakedVertexAnimation(attribs, mesh, defines);
}

@Popov72 could you have a final check ?

Thanks @Popov72, you are always awesome :)


Bugfix/coords not deep copy

This pull request fixes a bug that prevented making a complete deep copy of a DataArray or Dataset, because the coords weren't being deep copied. It took a small fix in the IndexVariable.copy method. This method now allows both deep and shallow copies of coords to be made.
This pull request corresponds to this issue https://github.com/pydata/xarray/issues/1463.

[x] Tests added
[x] Fully documented, including whats-new.rst for all changes and api.rst for new API

Hello @pletchm! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file xarray/tests/test_dataarray.py:

Line 3307:9: E123 closing bracket does not match indentation of opening bracket's line
Line 3308:37: E241 multiple spaces after ','

In the file xarray/tests/test_dataset.py:

Line 1933:9: E123 closing bracket does not match indentation of opening bracket's line

I'm perplexed by why the build and tests are failing on this. I'm going to try 3 things:

Make a new branch from master and PR (making sure my fork master is synced up with the upstream master) to see if the tests/build pass without any additional commits
Commit my non-test changes and see if the build/tests pass
Commit my tests and see if the build/tests pass
Then I'll rebase my 2 commits into 1 commit.

seems like a same issue again:
import xarray as xr

xarr1 = xr.DataArray(
    np.zeros([2]),
    coords=dict(x=[0.0, 1.0]), # important to use 'float' here! with 'int' it is working fine
    dims=("x")
)
print(xarr1.x.data[0]) # 0.0

xarr2 = xarr1.copy(deep=True)
xarr2.x.data[0] = 45
print(xarr1.x.data[0]) # gives 45


Run isort on homekit

Description:
https://github.com/home-assistant/home-assistant/pull/27867 was merged but predates the new isort rules. This fixes homekit isort.
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the [development checklist][dev-checklist]

This should fix the CI failures on dev.


Make QueryCache respect Accountable queries on eviction and consisten…

…cy check
Root cause
onQueryCache increases ramBytesUsed for specified amount, that is being calculated with respect to query being Accountable or not.
Unfortunately, onQueryEviction does not the same. If some heavy accountable query has ramBytesUsed() greater than QUERY_DEFAULT_RAM_BYTES_USED, the delta ghostBytes = ramBytesUsed() - QUERY_DEFAULT_RAM_BYTES_USED remains in total LRUQueryCache#ramBytesUsed forever.
Hit rate drops to 0
since total sum of ghost bytes monotonously increases with each cached accountable query (>QUERY_DEFAULT_RAM_BYTES_USED), eventually it becomes greater than maxRamBytesUsed, and each newly cached query immediately evicts from the cache.
Current behavior of LRUQueryCache for some real service in production [though not fully optimized]

Service restarted.
Reached maxRamBytesUsed. Started eviction. From now on size of cached queries decreases to compensate increasing ghost bytes.
Total amount of ghost bytes is greater than maxRamBytesUsed. If any new query was cached, it evicted at the same time. Cache size is 0. Hit rate is 0.

After fix

Can you run ./gradlew tidy at the root of the project to make sure the formatting is all correct?

Thanks for reviewing! I ran tidy and made some refactoring

I am also facing the same issue  after the upgrade of  elastic to 8.10 from 8.7.
Then we upgraded to  8.12, still we are seeing a similar behaviour . Any suggestions please?

@gtroitskiy @romseygeek
Is the bug fixed on 8.12 Elasticseach?


Add user with role and passowrd

Can not find option to add new user under user module.
Although can add employee but they are not showing under user module with authentication.

u can add user in employe module  because in laraadmin employee module work
like user module
On Thu, Mar 23, 2017 at 12:30 PM, sheikh303<EMAIL_ADDRESS>wrote:

Can not find option to add new user under user module.
Although can add employee but they are not showing under user module with
authentication.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AWLoufypDv90sPqPZLD03bBR3P1HpkM1ks5rohicgaJpZM4MmT2o
.

Thanks a lot for the quickest response :)
Added few employees, Now I want them to login to the backend. but since
they are not users table they dont have password nor received any
invitation email to join the system.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD.  http://www.ergo-ventures.com/
+8801938855538
Skype: sheikh303
On 23 March 2017 at 13:03, azarzaza<EMAIL_ADDRESS>wrote:

u can add user in employe module because in laraadmin employee module work
like user module
On Thu, Mar 23, 2017 at 12:30 PM, sheikh303<EMAIL_ADDRESS>wrote:

Can not find option to add new user under user module.
Although can add employee but they are not showing under user module with
authentication.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/
AWLoufypDv90sPqPZLD03bBR3P1HpkM1ks5rohicgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288634060,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhPtvCIDSzEv2j_xYT6d4uykiD527X3ks5rohlHgaJpZM4MmT2o
.

please configure your mail address then only you received the password
through mail
On Thu, Mar 23, 2017 at 12:36 PM, sheikh303<EMAIL_ADDRESS>wrote:

Thanks a lot for the quickest response :)
Added few employees, Now I want them to login to the backend. but since
they are not users table they dont have password nor received any
invitation email to join the system.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538
Skype: sheikh303
On 23 March 2017 at 13:03, azarzaza<EMAIL_ADDRESS>wrote:

u can add user in employe module because in laraadmin employee module
work
like user module
On Thu, Mar 23, 2017 at 12:30 PM, sheikh303<EMAIL_ADDRESS>wrote:

Can not find option to add new user under user module.
Although can add employee but they are not showing under user module
with
authentication.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/
AWLoufypDv90sPqPZLD03bBR3P1HpkM1ks5rohicgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288634060>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhPtvCIDSzEv2j_
xYT6d4uykiD527X3ks5rohlHgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288634591,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWLouU0EW77DFuGSJBgECed1Xe9rrwG8ks5rohoNgaJpZM4MmT2o
.

Yes. mail is configured. I can receive email when I try forgot password.
But not received any invitation email after creating a employee user.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD.  http://www.ergo-ventures.com/
+8801938855538
Skype: sheikh303
On 23 March 2017 at 13:08, azarzaza<EMAIL_ADDRESS>wrote:

please configure your mail address then only you received the password
through mail
On Thu, Mar 23, 2017 at 12:36 PM, sheikh303<EMAIL_ADDRESS>wrote:

Thanks a lot for the quickest response :)
Added few employees, Now I want them to login to the backend. but since
they are not users table they dont have password nor received any
invitation email to join the system.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538 <01938-855538>
Skype: sheikh303
On 23 March 2017 at 13:03, azarzaza<EMAIL_ADDRESS>wrote:

u can add user in employe module because in laraadmin employee module
work
like user module
On Thu, Mar 23, 2017 at 12:30 PM, sheikh303<EMAIL_ADDRESS>wrote:

Can not find option to add new user under user module.
Although can add employee but they are not showing under user module
with
authentication.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183, or mute
the
thread
<https://github.com/notifications/unsubscribe-auth/
AWLoufypDv90sPqPZLD03bBR3P1HpkM1ks5rohicgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288634060>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhPtvCIDSzEv2j_
xYT6d4uykiD527X3ks5rohlHgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288634591>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouU0EW77DFuGSJBgECed1Xe9rrwG8ks5rohoNgaJpZM4MmT2o>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288634902,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhPts8veU7OhTDRk2wra1nbqnuYd9Ixks5rohpvgaJpZM4MmT2o
.

you can check the employee controllers does the mail is correctly
configured
On Thu, Mar 23, 2017 at 12:58 PM, sheikh303<EMAIL_ADDRESS>wrote:

Yes. mail is configured. I can receive email when I try forgot password.
But not received any invitation email after creating a employee user.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538
Skype: sheikh303
On 23 March 2017 at 13:08, azarzaza<EMAIL_ADDRESS>wrote:

please configure your mail address then only you received the password
through mail
On Thu, Mar 23, 2017 at 12:36 PM, sheikh303<EMAIL_ADDRESS>wrote:

Thanks a lot for the quickest response :)
Added few employees, Now I want them to login to the backend. but since
they are not users table they dont have password nor received any
invitation email to join the system.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538 <01938-855538>
Skype: sheikh303
On 23 March 2017 at 13:03, azarzaza<EMAIL_ADDRESS>wrote:

u can add user in employe module because in laraadmin employee module
work
like user module
On Thu, Mar 23, 2017 at 12:30 PM, sheikh303 <
<EMAIL_ADDRESS>wrote:

Can not find option to add new user under user module.
Although can add employee but they are not showing under user
module
with
authentication.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183, or mute
the
thread
<https://github.com/notifications/unsubscribe-auth/
AWLoufypDv90sPqPZLD03bBR3P1HpkM1ks5rohicgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288634060>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhPtvCIDSzEv2j_
xYT6d4uykiD527X3ks5rohlHgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288634591>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouU0EW77DFuGSJBgECed1Xe9rrwG8ks5rohoNgaJpZM4MmT2o>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288634902>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPts8veU7OhTDRk2wra1nbqnuYd9Ixks5rohpvgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288638124,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWLoubRh37MPbN1hnXOcmT-Z0hNSQJ0Uks5roh81gaJpZM4MmT2o
.

/**
* Store a newly created employee in database.
*
* @param  \Illuminate\Http\Request  $request
* @return \Illuminate\Http\Response
*/
public function store(Request $request)
{
if(Module::hasAccess("Employees", "create")) {
        $rules = Module::validateRules("Employees", $request);

        $validator = Validator::make($request->all(), $rules);

        if ($validator->fails()) {
            return

redirect()->back()->withErrors($validator)->withInput();
}
        $insert_id = Module::insert("Employees", $request);

        return redirect()->route(config('laraadmin.adminRoute') .

'.employees.index');
    } else {
        return redirect(config('laraadmin.adminRoute')."/");
    }
}

Not seeing any email trigger in the method or any storing in user's module
Please suggest.
On Thursday, 23 March 2017, azarzaza<EMAIL_ADDRESS>wrote:

you can check the employee controllers does the mail is correctly
configured
On Thu, Mar 23, 2017 at 12:58 PM, sheikh303<EMAIL_ADDRESS>wrote:

Yes. mail is configured. I can receive email when I try forgot password.
But not received any invitation email after creating a employee user.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538 <01938-855538>
Skype: sheikh303
On 23 March 2017 at 13:08, azarzaza<EMAIL_ADDRESS>wrote:

please configure your mail address then only you received the password
through mail
On Thu, Mar 23, 2017 at 12:36 PM, sheikh303<EMAIL_ADDRESS>wrote:

Thanks a lot for the quickest response :)
Added few employees, Now I want them to login to the backend. but
since
they are not users table they dont have password nor received any
invitation email to join the system.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538 <01938-855538> <01938-855538>
Skype: sheikh303
On 23 March 2017 at 13:03, azarzaza<EMAIL_ADDRESS>wrote:

u can add user in employe module because in laraadmin employee
module
work
like user module
On Thu, Mar 23, 2017 at 12:30 PM, sheikh303 <
<EMAIL_ADDRESS>wrote:

Can not find option to add new user under user module.
Although can add employee but they are not showing under user
module
with
authentication.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183, or
mute
the
thread
<https://github.com/notifications/unsubscribe-auth/
AWLoufypDv90sPqPZLD03bBR3P1HpkM1ks5rohicgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288634060>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtvCIDSzEv2j_
xYT6d4uykiD527X3ks5rohlHgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288634591>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouU0EW77DFuGSJBgECed1Xe9rrwG8ks5rohoNgaJpZM4MmT2o>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288634902>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPts8veU7OhTDRk2wra1nbqnuYd9Ixks5rohpvgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288638124>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLoubRh37MPbN1hnXOcmT-Z0hNSQJ0Uks5roh81gaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288643218,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhPtomOwnpf-ZzGC4HjOlcW1xOQOt6Uks5roiYogaJpZM4MmT2o
.

which version of laravel do u using

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288679820,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhPtj3jYt-0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o
.

please work with fresh laraadmin that should be fine for working
On Thu, Mar 23, 2017 at 4:22 PM, sheikh303<EMAIL_ADDRESS>wrote:

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288679820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhPtj3jYt-
0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288682868,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWLouY3ldC99tz02mB7ansq84ktCa_6zks5rok8HgaJpZM4MmT2o
.

i think ur working with old one latest one having email send feature
On Thu, Mar 23, 2017 at 4:24 PM, Mohamed Azarudeen<EMAIL_ADDRESS>wrote:

please work with fresh laraadmin that should be fine for working
On Thu, Mar 23, 2017 at 4:22 PM, sheikh303<EMAIL_ADDRESS>wrote:

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288679820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtj3jYt-0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288682868,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWLouY3ldC99tz02mB7ansq84ktCa_6zks5rok8HgaJpZM4MmT2o
.

could you please guide me to update to latest one
I followed the installation guide accordingly
On Mar 23, 2017 4:55 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

i think ur working with old one latest one having email send feature
On Thu, Mar 23, 2017 at 4:24 PM, Mohamed Azarudeen<EMAIL_ADDRESS>wrote:

please work with fresh laraadmin that should be fine for working
On Thu, Mar 23, 2017 at 4:22 PM, sheikh303<EMAIL_ADDRESS>wrote:

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288679820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtj3jYt-0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288682868>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouY3ldC99tz02mB7ansq84ktCa_6zks5rok8HgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288683330,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhPtiWq1stFFgrQfKs6jrKxQ5pTUb78ks5rok-GgaJpZM4MmT2o
.

Use the composer to install and for ur work use 5.2 laravel version
On Mar 23, 2017 4:50 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

could you please guide me to update to latest one
I followed the installation guide accordingly
On Mar 23, 2017 4:55 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

i think ur working with old one latest one having email send feature
On Thu, Mar 23, 2017 at 4:24 PM, Mohamed Azarudeen <
<EMAIL_ADDRESS>wrote:

please work with fresh laraadmin that should be fine for working
On Thu, Mar 23, 2017 at 4:22 PM, sheikh303<EMAIL_ADDRESS>wrote:

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288679820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtj3jYt-0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288682868>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouY3ldC99tz02mB7ansq84ktCa_6zks5rok8HgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288683330>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtiWq1stFFgrQfKs6jrKxQ5pTUb78ks5rok-GgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288688783,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWLouYAr3FkA_fdnq6h1SPkBbVCgXsRVks5rolV8gaJpZM4MmT2o
.

Just checked. My laravel version is 5.2.45.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD.  http://www.ergo-ventures.com/
+8801938855538
Skype: sheikh303
On 23 March 2017 at 18:15, azarzaza<EMAIL_ADDRESS>wrote:

Use the composer to install and for ur work use 5.2 laravel version
On Mar 23, 2017 4:50 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

could you please guide me to update to latest one
I followed the installation guide accordingly
On Mar 23, 2017 4:55 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

i think ur working with old one latest one having email send feature
On Thu, Mar 23, 2017 at 4:24 PM, Mohamed Azarudeen <
<EMAIL_ADDRESS>wrote:

please work with fresh laraadmin that should be fine for working
On Thu, Mar 23, 2017 at 4:22 PM, sheikh303<EMAIL_ADDRESS>

wrote:

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288679820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtj3jYt-0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288682868>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouY3ldC99tz02mB7ansq84ktCa_6zks5rok8HgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288683330>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtiWq1stFFgrQfKs6jrKxQ5pTUb78ks5rok-GgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288688783>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWLouYAr3FkA_
fdnq6h1SPkBbVCgXsRVks5rolV8gaJpZM4MmT2o>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288700375,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhPtjs4ssB8p5BbqOmgKoiSwVbhmjSgks5romJugaJpZM4MmT2o
.

K use it composer to install laravel 5.2 then use composer require to add
the laraadmin package. Then add the laraadmin class to config file
On Mar 23, 2017 9:32 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

Just checked. My laravel version is 5.2.45.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538
Skype: sheikh303
On 23 March 2017 at 18:15, azarzaza<EMAIL_ADDRESS>wrote:

Use the composer to install and for ur work use 5.2 laravel version
On Mar 23, 2017 4:50 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

could you please guide me to update to latest one
I followed the installation guide accordingly
On Mar 23, 2017 4:55 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

i think ur working with old one latest one having email send feature
On Thu, Mar 23, 2017 at 4:24 PM, Mohamed Azarudeen <
<EMAIL_ADDRESS>wrote:

please work with fresh laraadmin that should be fine for working
On Thu, Mar 23, 2017 at 4:22 PM, sheikh303 <
<EMAIL_ADDRESS>

wrote:

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288679820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtj3jYt-0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288682868>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouY3ldC99tz02mB7ansq84ktCa_6zks5rok8HgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288683330>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtiWq1stFFgrQfKs6jrKxQ5pTUb78ks5rok-GgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288688783>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWLouYAr3FkA_
fdnq6h1SPkBbVCgXsRVks5rolV8gaJpZM4MmT2o>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288700375>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtjs4ssB8p5BbqOmgKoiSwVbhmjSgks5romJugaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288768338,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWLouVCyHlCvZnew9uvjI463ezLE1Tjsks5ropeYgaJpZM4MmT2o
.

Please refer laraadmin document
On Mar 23, 2017 10:40 PM, "Mohamed Azarudeen"<EMAIL_ADDRESS>wrote:

K use it composer to install laravel 5.2 then use composer require to add
the laraadmin package. Then add the laraadmin class to config file
On Mar 23, 2017 9:32 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

Just checked. My laravel version is 5.2.45.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538
Skype: sheikh303
On 23 March 2017 at 18:15, azarzaza<EMAIL_ADDRESS>wrote:

Use the composer to install and for ur work use 5.2 laravel version
On Mar 23, 2017 4:50 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

could you please guide me to update to latest one
I followed the installation guide accordingly
On Mar 23, 2017 4:55 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

i think ur working with old one latest one having email send feature
On Thu, Mar 23, 2017 at 4:24 PM, Mohamed Azarudeen <
<EMAIL_ADDRESS>wrote:

please work with fresh laraadmin that should be fine for working
On Thu, Mar 23, 2017 at 4:22 PM, sheikh303 <
<EMAIL_ADDRESS>

wrote:

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288679820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtj3jYt-0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288682868>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouY3ldC99tz02mB7ansq84ktCa_6zks5rok8HgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288683330>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtiWq1stFFgrQfKs6jrKxQ5pTUb78ks5rok-GgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288688783>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWLouYAr3FkA_
fdnq6h1SPkBbVCgXsRVks5rolV8gaJpZM4MmT2o>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288700375>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhPtjs4s
sB8p5BbqOmgKoiSwVbhmjSgks5romJugaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288768338,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWLouVCyHlCvZnew9uvjI463ezLE1Tjsks5ropeYgaJpZM4MmT2o
.

I followed the steps exactly mentioned in the following documentation. yet
didn't get the functionality as you mentioned for employee module.

http://laraadmin.com/docs/1.0/installation
http://laraadmin.com/docs/1.0/upgrades

Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD.  http://www.ergo-ventures.com/
+8801938855538
Skype: sheikh303
On 23 March 2017 at 23:13, azarzaza<EMAIL_ADDRESS>wrote:

Please refer laraadmin document
On Mar 23, 2017 10:40 PM, "Mohamed Azarudeen"<EMAIL_ADDRESS>wrote:

K use it composer to install laravel 5.2 then use composer require to add
the laraadmin package. Then add the laraadmin class to config file
On Mar 23, 2017 9:32 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

Just checked. My laravel version is 5.2.45.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538 <01938-855538>
Skype: sheikh303
On 23 March 2017 at 18:15, azarzaza<EMAIL_ADDRESS>wrote:

Use the composer to install and for ur work use 5.2 laravel version
On Mar 23, 2017 4:50 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

could you please guide me to update to latest one
I followed the installation guide accordingly
On Mar 23, 2017 4:55 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

i think ur working with old one latest one having email send
feature
On Thu, Mar 23, 2017 at 4:24 PM, Mohamed Azarudeen <
<EMAIL_ADDRESS>wrote:

please work with fresh laraadmin that should be fine for working
On Thu, Mar 23, 2017 at 4:22 PM, sheikh303 <
<EMAIL_ADDRESS>

wrote:

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288679820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtj3jYt-0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288682868>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouY3ldC99tz02mB7ansq84ktCa_6zks5rok8HgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288683330>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtiWq1stFFgrQfKs6jrKxQ5pTUb78ks5rok-GgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288688783>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWLouYAr3FkA_
fdnq6h1SPkBbVCgXsRVks5rolV8gaJpZM4MmT2o>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288700375>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhPtjs4s
sB8p5BbqOmgKoiSwVbhmjSgks5romJugaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288768338>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouVCyHlCvZnew9uvjI463ezLE1Tjsks5ropeYgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288792568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhPtva1cpx2dFTAF1sMxOrG346yMJrtks5roqg2gaJpZM4MmT2o
.

Over here mail functionality working
On Mar 23, 2017 11:12 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

I followed the steps exactly mentioned in the following documentation. yet
didn't get the functionality as you mentioned for employee module.

http://laraadmin.com/docs/1.0/installation
http://laraadmin.com/docs/1.0/upgrades

Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538
Skype: sheikh303
On 23 March 2017 at 23:13, azarzaza<EMAIL_ADDRESS>wrote:

Please refer laraadmin document
On Mar 23, 2017 10:40 PM, "Mohamed Azarudeen"<EMAIL_ADDRESS>wrote:

K use it composer to install laravel 5.2 then use composer require to
add
the laraadmin package. Then add the laraadmin class to config file
On Mar 23, 2017 9:32 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

Just checked. My laravel version is 5.2.45.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538 <01938-855538>
Skype: sheikh303
On 23 March 2017 at 18:15, azarzaza<EMAIL_ADDRESS>wrote:

Use the composer to install and for ur work use 5.2 laravel version
On Mar 23, 2017 4:50 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

could you please guide me to update to latest one
I followed the installation guide accordingly
On Mar 23, 2017 4:55 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

i think ur working with old one latest one having email send
feature
On Thu, Mar 23, 2017 at 4:24 PM, Mohamed Azarudeen <
<EMAIL_ADDRESS>wrote:

please work with fresh laraadmin that should be fine for
working
On Thu, Mar 23, 2017 at 4:22 PM, sheikh303 <
<EMAIL_ADDRESS>

wrote:

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza" <
<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288679820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtj3jYt-0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288682868>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouY3ldC99tz02mB7ansq84ktCa_6zks5rok8HgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288683330>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtiWq1stFFgrQfKs6jrKxQ5pTUb78ks5rok-GgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288688783>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWLouYAr3FkA_
fdnq6h1SPkBbVCgXsRVks5rolV8gaJpZM4MmT2o>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288700375>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhPtjs4s
sB8p5BbqOmgKoiSwVbhmjSgks5romJugaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288768338>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouVCyHlCvZnew9uvjI463ezLE1Tjsks5ropeYgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288792568>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtva1cpx2dFTAF1sMxOrG346yMJrtks5roqg2gaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288802538,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWLouZ-5_zVlUhuh9zdX3aK0loa0szbRks5roq8LgaJpZM4MmT2o
.

Send me the snap of employees controller store function
On Mar 23, 2017 11:22 PM, wrote:

Over here mail functionality working
On Mar 23, 2017 11:12 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

I followed the steps exactly mentioned in the following documentation. yet
didn't get the functionality as you mentioned for employee module.

http://laraadmin.com/docs/1.0/installation
http://laraadmin.com/docs/1.0/upgrades

Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538
Skype: sheikh303
On 23 March 2017 at 23:13, azarzaza<EMAIL_ADDRESS>wrote:

Please refer laraadmin document
On Mar 23, 2017 10:40 PM, "Mohamed Azarudeen"<EMAIL_ADDRESS>wrote:

K use it composer to install laravel 5.2 then use composer require to
add
the laraadmin package. Then add the laraadmin class to config file
On Mar 23, 2017 9:32 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

Just checked. My laravel version is 5.2.45.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538 <01938-855538>
Skype: sheikh303
On 23 March 2017 at 18:15, azarzaza<EMAIL_ADDRESS>wrote:

Use the composer to install and for ur work use 5.2 laravel version
On Mar 23, 2017 4:50 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

could you please guide me to update to latest one
I followed the installation guide accordingly
On Mar 23, 2017 4:55 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

i think ur working with old one latest one having email send
feature
On Thu, Mar 23, 2017 at 4:24 PM, Mohamed Azarudeen <
<EMAIL_ADDRESS>wrote:

please work with fresh laraadmin that should be fine for
working
On Thu, Mar 23, 2017 at 4:22 PM, sheikh303 <
<EMAIL_ADDRESS>

wrote:

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza" <
<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288679820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtj3jYt-0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288682868>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouY3ldC99tz02mB7ansq84ktCa_6zks5rok8HgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288683330>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtiWq1stFFgrQfKs6jrKxQ5pTUb78ks5rok-GgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288688783>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWLouYAr3FkA_
fdnq6h1SPkBbVCgXsRVks5rolV8gaJpZM4MmT2o>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288700375>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhPtjs4s
sB8p5BbqOmgKoiSwVbhmjSgks5romJugaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288768338>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouVCyHlCvZnew9uvjI463ezLE1Tjsks5ropeYgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288792568>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhPtva1c
px2dFTAF1sMxOrG346yMJrtks5roqg2gaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288802538,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWLouZ-5_zVlUhuh9zdX3aK0loa0szbRks5roq8LgaJpZM4MmT2o
.

Employees and Users controllers are attached. Please find in attached
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD.  http://www.ergo-ventures.com/
+8801938855538
Skype: sheikh303
On 23 March 2017 at 23:52, azarzaza<EMAIL_ADDRESS>wrote:

Send me the snap of employees controller store function
On Mar 23, 2017 11:22 PM, wrote:

Over here mail functionality working
On Mar 23, 2017 11:12 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

I followed the steps exactly mentioned in the following documentation.
yet
didn't get the functionality as you mentioned for employee module.

http://laraadmin.com/docs/1.0/installation
http://laraadmin.com/docs/1.0/upgrades

Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538 <01938-855538>
Skype: sheikh303
On 23 March 2017 at 23:13, azarzaza<EMAIL_ADDRESS>wrote:

Please refer laraadmin document
On Mar 23, 2017 10:40 PM, "Mohamed Azarudeen"<EMAIL_ADDRESS>wrote:

K use it composer to install laravel 5.2 then use composer require
to
add
the laraadmin package. Then add the laraadmin class to config file
On Mar 23, 2017 9:32 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

Just checked. My laravel version is 5.2.45.
Thanks & Regards,
Sheikh Faiyaz Moorsalin
Assistant General Manager
ERGO VENTURES PVT. LTD. http://www.ergo-ventures.com/
+8801938855538 <01938-855538> <01938-855538>
Skype: sheikh303
On 23 March 2017 at 18:15, azarzaza<EMAIL_ADDRESS>wrote:

Use the composer to install and for ur work use 5.2 laravel
version
On Mar 23, 2017 4:50 PM, "sheikh303"<EMAIL_ADDRESS>wrote:

could you please guide me to update to latest one
I followed the installation guide accordingly
On Mar 23, 2017 4:55 PM, "azarzaza"<EMAIL_ADDRESS>wrote:

i think ur working with old one latest one having email send
feature
On Thu, Mar 23, 2017 at 4:24 PM, Mohamed Azarudeen <
<EMAIL_ADDRESS>wrote:

please work with fresh laraadmin that should be fine for
working
On Thu, Mar 23, 2017 at 4:22 PM, sheikh303 <
<EMAIL_ADDRESS>

wrote:

clone it directly from your repo. few days ago.
will check and confirm you in few hours
On Mar 23, 2017 4:39 PM, "azarzaza" <
<EMAIL_ADDRESS>wrote:

which version of laravel do u using
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#
issuecomment-288679820>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtj3jYt-0F3uiOicbSRnjw6CG2UiIks5rokvkgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/
issues/183#issuecomment-
288682868>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouY3ldC99tz02mB7ansq84ktCa_6zks5rok8HgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288683330>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
ABhPtiWq1stFFgrQfKs6jrKxQ5pTUb78ks5rok-GgaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288688783>,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/AWLouYAr3FkA_
fdnq6h1SPkBbVCgXsRVks5rolV8gaJpZM4MmT2o>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288700375>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhPtjs4s
sB8p5BbqOmgKoiSwVbhmjSgks5romJugaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-
288768338>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AWLouVCyHlCvZnew9uvjI463ezLE1Tjsks5ropeYgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#
issuecomment-288792568>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhPtva1c
px2dFTAF1sMxOrG346yMJrtks5roqg2gaJpZM4MmT2o>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-
288802538>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWLouZ-5_
zVlUhuh9zdX3aK0loa0szbRks5roq8LgaJpZM4MmT2o>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dwijitsolutions/laraadmin/issues/183#issuecomment-288806077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhPtqKhzhbhWD20ZqKznywzGFttuiXNks5rorFogaJpZM4MmT2o
.

I'm using rap2hpoutre/create-user-command at the command line for this.

I have the same issue, i cant update user password .. any updates?

tested and looks from my side @becology1100

What is the solution should i test ?
I have no button to update users and in employe page i have no fields to update password too ?
do you got a solution for that ?
thanks :)

have you see this menu ?
update password in users detail, from tab "Account Setting"
https://s26.postimg.org/ju8l9c8fd/Screen_Shot_2017-09-23_at_4.19.11_PM.png

NO, only time line and general info

I think there is something wrong on your side.
Pls recheck you laraadmin. @becology1100

I think there should be a way to directly created users from the users module

but since I have access to my database, I will just replicate the first account

@sheikh303 I faced the same problem and found the issue (in my case) at the line 114 from the EmployeesController.php:
if(env('MAIL_USERNAME') != null && env('MAIL_USERNAME') != "null" && env('MAIL_USERNAME') != "") {
    // Send mail to User his Password
    Mail::send('emails.send_login_cred', ['user' => $user, 'password' => $password], function ($m) use ($user) {
<EMAIL_ADDRESS>'LaraAdmin');
    $m->to($user->email, $user->name)->subject('LaraAdmin - Your Login Credentials');
});
} else {
    Log::info("User created: username: ".$user->email." Password: ".$password);
}

If you are not using username in order to use your SMTP service, the notification sent to the user will be overlooked.
Hope this helps,
Best

This issue has been for a while now and I've encountered it myself. Here's what I did:
Turns out, env('MAIL_USERNAME') is not being read on the controller so I assigned $_ENV['MAIL_USERNAME'] to a variable and replaced all the instances of env('MAIL_USERNAME').
Here's my final line 113-115:
$mail_username = $_ENV['MAIL_USERNAME'];

if($mail_username != null && $mail_username != "null" && $mail_username != "") {

Hope this helps!

Hi, this is a nice package but I think that the developers have stopped working on it. Maybe you can try this package: https://github.com/Muhammadinaam/speed-admin. It supports Laravel 8+.


ENH: Support spatial normalization to alternative modalities

Builds off #457
Requires https://github.com/nipreps/niworkflows/pull/911
Adds a new parameter to init_register_template_wf(), image_type, to allow setting alternative registration targets for spatial normalization.
Also adds a tweak to the antsRegistration call to disable histogram_matching (which is enabled in most of the preset settings used), for cases where the reference anatomical and template target differ in modality.

@mgxd This is passing our tests, and I'm confident it won't break non-nibabies use cases. Merge when you're comfortable.


API Response for query's that run too long

URL for relevant page?
https://docs.influxdata.com/influxdb/v1.7/administration/config/#query-timeout-0s
What products and version are you using?
1.6.x
Where did you look before opening the issue?
Documentation and internal resources (InfluxData)
In cases of query's that run too long what is the HTTP API response going to be?
The 4xx codes listed only cover 403 forbidden. 5xx responses focus on an error.
This information is helpful for certain organizations that run metrics based on HTTP responses.

@andrew-influx -- you could try it and see what happens... that would be helpful in terms of reproduction.

@andrew-influx If you can test it and let me know the outcome, I'll add it to the documentation I'm creating about monitoring and tracking slow queries.


one executeble or script

Hello how can i convert it to one executable or ps1 script or one py script, so i don't need to use requrments.txt

Hi,
You can use pyinstaller for a getting a single exe file by following here