text:
Add ability to type and jump to item to SelectE

Related issue
Closes #2885
Overview
Refactors SelectE to use useSelect and now it is possible to type and jump to an option.
Link to preview
https://selecte-typing.netlify.app/?path=/story/select-experimental--default
Reason
This is normal behaviour for a select.
Work carried out

[x] Refactor stories
[x] Refactor SelectE

Thanks @thyhjwb6, it behaves very well - just a couple of observations:
Comparing to the vanilla select here:

The timeout between keystrokes for deciding whether the user is still typing a single word or whether they've started typing a new word seems to be on the small side - not sure if there's a universally accepted 'default' and whether we should increase ours a bit?

If I press 'T' [wait] then press 'T' again it goes through all options starting with 'T', which is inconsistent with the vanilla Select behaviour (which sticks to the first option in the list). I think we should aim for consistency, if possible please.

@k9dh3zij response as follows:

I can look at the timing although this is out-of-the-box from a widely used library Downshift
This behaviour is consistent with how other select components behave as options that begin with the same letter will be scrolled through each time the same letter is pressed. Check the example on W3

@thyhjwb6 Ha! That example on Mozilla broken, it randomly went through to Spider for some reason...
So as it seems this behaviour is consistent with the W3 recommended behaviour (and so it's the vanilla Select that's inconsistent), let's keep as is. The timing was just an observation and I don't have a way of reliably measuring it, so let's not worry unless we get feedback that it's confusing.
👍 from me, thank you! :)

@m7kvqbe1 That looks like design tokens needs to be rebuilt to me.

repo: defencedigital/mod-uk-design-system


text:
Add tasks for a complete deployment of SWF

Add tasks to tasks.yaml so that it can:

Deploy all IAC required for the bundle
Deploy the SWF bundle
Minimize the amount of commands that needed to deploy all the things

Completed

source: gharchive/issue

authors: floridaman zack-is-cool

license_type: permissive

license_source: github-api


text:
Automatic dependencies resolution for callback action method

Use Service Container method invocation and injection.
Example:
Keyboard::make()->buttons([
    Button::make('Generate')->action('generate')->param('id', '42'),
]);

WebhookHandler
public function generate(UserRepository $repository, string $id): void
{
    $user = $repository->find($id); // $id = '42'
    // ...
}

Hi! Thanks for your contribution
Would to mind to add tests to your feature?

Added, but I'm not a big expert on tests

Thanks!
will review it in a few days

@armivit opened #475 to solve conflicts, I've put you as co-author
Thanks for your contribution, and sorry for the late merge :(

source: gharchive/pull-request

authors: armivit fabio-ivona

repo: defstudio/telegraph

license: MIT


text:
Add --open param

Automatically tries to open tunnel URL in the browser if the --open params is set.

Issues with this PR:

Won't work on windows or linux cause
You are bumping the package version.. not your call to make what the new version is :)
not following any of the existing project style for the new code.

This feature would be desired but this PR is not ready.

Hey @defunctzombie just changed the code to also work on linux & windows. Sorry for that.
One question, what do you mean by:

not following any of the existing project style for the new code.

How could I improve the code to follow the module style ?

Take a look at the code style of other files (spacing, indentation, etc).

Commits squashed

:+1:

authors: defunctzombie vrunoa

repo: defunctzombie/localtunnel


text:
Service feature

A way to add auxiliary services that is required by the app in question.
To use you go
service 'redis'

and then maybe
app_params "-e REDIS_URL=redis://<%= envname %>-redis:6347"

To connect to it.
Although kaiser sets up a redis already, you might not want some apps to share redis. Also you might want something besides redis. This PR adds this ability.

@rregino can you help us review this PR, please?

authors: davidsiaw degikko

repo: degica/kaiser


text:
fail to install deisctl

cmd : curl -sSL http://deis.io/deisctl/install.sh | sudo sh -s 1.5.2
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100 1572k  100 1572k    0     0  53036      0  0:00:30  0:00:30 --:--:--  100k
Verifying archive integrity... All good.
Uncompressing Deis Control Utility  100%
Error: Get https://raw.githubusercontent.com/deis/deis/v1.5.2/deisctl/units/deis-builder.service: dial tcp: lookup raw.githubusercontent.com: no DNS servers

Sounds like you don't have any DNS resolution set up. Try to add nameserver 8.8.8.8 and nameserver 8.8.4.4 to your /etc/resolv.conf.

@bacongobbler  thankyou now its working

no problem :)

curl -sSL http://deis.io/deisctl/install.sh | sudo sh -s 1.5.2
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
100 1572k  100 1572k    0     0   245k      0  0:00:06  0:00:06 --:--:--  323k
Verifying archive integrity... All good.
Uncompressing Deis Control Utility  100%
Refreshed deis-builder.service from v1.5.2
Refreshed deis-cache.service from v1.5.2
Refreshed deis-controller.service from v1.5.2
Refreshed deis-database.service from v1.5.2
Refreshed deis-logger.service from v1.5.2
Refreshed deis-logspout.service from v1.5.2
Refreshed deis-publisher.service from v1.5.2
Refreshed deis-registry.service from v1.5.2
Refreshed deis-router.service from v1.5.2
Refreshed deis-store-admin.service from v1.5.2
Refreshed deis-store-daemon.service from v1.5.2
Refreshed deis-store-gateway.service from v1.5.2
Refreshed deis-store-metadata.service from v1.5.2
Refreshed deis-store-monitor.service from v1.5.2
Refreshed deis-store-volume.service from v1.5.2
deisctl is in the current directory and unit files are
in /home/mca/.deis/units. Please move deisctl to a
directory in your search PATH.
See http://docs.deis.io/ for documentation.
mca@mca:/bin$ sudo ln -fs $PWD/deisctl /usr/local/bin/deisctl
[sudo] password for mca:
no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory
mca@mca:/bin$ sudo whoiam
sudo: whoiam: command not found
mca@mca:/bin$ whomi
No command 'whomi' found, did you mean:
Command 'whom' from package 'nmh' (universe)
Command 'whom' from package 'mailutils-mh' (universe)
Command 'whoami' from package 'coreutils' (main)
whomi: command not found
mca@mca:/bin$ whoami
mca
mca@mca:/bin$ sudo whoami
root
mca@mca:/bin$ cd
mca@mca:~$  apt-cache policy samba
samba:
Installed: 2:4.1.6+dfsg-1ubuntu2.14.04.7
Candidate: 2:4.1.6+dfsg-1ubuntu2.14.04.7
Version table:
*** 2:4.1.6+dfsg-1ubuntu2.14.04.7 0
500 http://in.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
100 /var/lib/dpkg/status
2:4.1.6+dfsg-1ubuntu2 0
500 http://in.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
mca@mca:~$  apt-cache policy samba
samba:
Installed: 2:4.1.6+dfsg-1ubuntu2.14.04.7
Candidate: 2:4.1.6+dfsg-1ubuntu2.14.04.7
Version table:
*** 2:4.1.6+dfsg-1ubuntu2.14.04.7 0
500 http://in.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages
100 /var/lib/dpkg/status
2:4.1.6+dfsg-1ubuntu2 0
500 http://in.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
mca@mca:~$
mca@mca:~$ sudo uptime
20:44:18 up 1 day,  1:56,  2 users,  load average: 0.15, 0.16, 0.14
mca@mca:~$ sudo ln -fs $PWD/deisctl /usr/local/bin/deisctl
mca@mca:~$ cd deis/
mca@mca:~/deis$ export DEIS_NUM_INSTANCES=3
mca@mca:~/deis$ make discovery-url && vagrant up
sed -e "s,# discovery:,discovery:," -e "s,discovery: https://discovery.etcd.io/.,discovery: $(curl -s -w '\n' https://discovery.etcd.io/new)," contrib/coreos/user-data.example > contrib/coreos/user-data
Bringing machine 'deis-01' up with 'virtualbox' provider...
Bringing machine 'deis-02' up with 'virtualbox' provider...
Bringing machine 'deis-03' up with 'virtualbox' provider...
==> deis-01: Running triggers before up...
==> deis-01: Checking if box 'coreos-stable' is up to date...
==> deis-01: VirtualBox VM is already running.
==> deis-02: Running triggers before up...
==> deis-02: Checking if box 'coreos-stable' is up to date...
==> deis-02: VirtualBox VM is already running.
==> deis-03: Running triggers before up...
==> deis-03: Checking if box 'coreos-stable' is up to date...
==> deis-03: VirtualBox VM is already running.
mca@mca:~/deis$ vagrant halt
==> deis-03: Attempting graceful shutdown of VM...
==> deis-02: Attempting graceful shutdown of VM...
==> deis-01: Attempting graceful shutdown of VM...
mca@mca:~/deis$ make discovery-url && vagrant up
sed -e "s,# discovery:,discovery:," -e "s,discovery: https://discovery.etcd.io/.,discovery: $(curl -s -w '\n' https://discovery.etcd.io/new)," contrib/coreos/user-data.example > contrib/coreos/user-data
Bringing machine 'deis-01' up with 'virtualbox' provider...
Bringing machine 'deis-02' up with 'virtualbox' provider...
Bringing machine 'deis-03' up with 'virtualbox' provider...
==> deis-01: Running triggers before up...
==> deis-01: Checking if box 'coreos-stable' is up to date...
==> deis-01: Clearing any previously set forwarded ports...
==> deis-01: Clearing any previously set network interfaces...
==> deis-01: Preparing network interfaces based on configuration...
deis-01: Adapter 1: nat
deis-01: Adapter 2: hostonly
==> deis-01: Forwarding ports...
deis-01: 22 => 2222 (adapter 1)
==> deis-01: Running 'pre-boot' VM customizations...
==> deis-01: Booting VM...
==> deis-01: Waiting for machine to boot. This may take a few minutes...
deis-01: SSH address: 127.0.0.1:2222
deis-01: SSH username: core
deis-01: SSH auth method: private key
deis-01: Warning: Connection timeout. Retrying...
==> deis-01: Machine booted and ready!
==> deis-01: Setting hostname...
==> deis-01: Configuring and enabling network interfaces...
==> deis-01: Machine already provisioned. Run vagrant provision or use the --provision
==> deis-01: to force provisioning. Provisioners marked to run always will still run.
==> deis-02: Running triggers before up...
==> deis-02: Checking if box 'coreos-stable' is up to date...
==> deis-02: Clearing any previously set forwarded ports...
==> deis-02: Fixed port collision for 22 => 2222. Now on port 2200.
==> deis-02: Clearing any previously set network interfaces...
==> deis-02: Preparing network interfaces based on configuration...
deis-02: Adapter 1: nat
deis-02: Adapter 2: hostonly
==> deis-02: Forwarding ports...
deis-02: 22 => 2200 (adapter 1)
==> deis-02: Running 'pre-boot' VM customizations...
==> deis-02: Booting VM...
==> deis-02: Waiting for machine to boot. This may take a few minutes...
deis-02: SSH address: 127.0.0.1:2200
deis-02: SSH username: core
deis-02: SSH auth method: private key
deis-02: Warning: Connection timeout. Retrying...
==> deis-02: Machine booted and ready!
==> deis-02: Setting hostname...
==> deis-02: Configuring and enabling network interfaces...
==> deis-02: Machine already provisioned. Run vagrant provision or use the --provision
==> deis-02: to force provisioning. Provisioners marked to run always will still run.
==> deis-03: Running triggers before up...
==> deis-03: Checking if box 'coreos-stable' is up to date...
==> deis-03: Clearing any previously set forwarded ports...
==> deis-03: Fixed port collision for 22 => 2222. Now on port 2201.
==> deis-03: Clearing any previously set network interfaces...
==> deis-03: Preparing network interfaces based on configuration...
deis-03: Adapter 1: nat
deis-03: Adapter 2: hostonly
==> deis-03: Forwarding ports...
deis-03: 22 => 2201 (adapter 1)
==> deis-03: Running 'pre-boot' VM customizations...
==> deis-03: Booting VM...
==> deis-03: Waiting for machine to boot. This may take a few minutes...
deis-03: SSH address: 127.0.0.1:2201
deis-03: SSH username: core
deis-03: SSH auth method: private key
deis-03: Warning: Connection timeout. Retrying...
==> deis-03: Machine booted and ready!
==> deis-03: Setting hostname...
==> deis-03: Configuring and enabling network interfaces...
==> deis-03: Machine already provisioned. Run vagrant provision or use the --provision
==> deis-03: to force provisioning. Provisioners marked to run always will still run.
mca@mca:~/deis$ ssh-add ~/.vagrant.d/insecure_private_key
Identity added: /home/mca/.vagrant.d/insecure_private_key (/home/mca/.vagrant.d/insecure_private_key)
mca@mca:~/deis$ export DEISCTL_TUNNEL=172.17.8.100
mca@mca:~/deis$ deisctl config platform set sshPrivateKey=~/.vagrant.d/insecure_private_key
LS0tLS1CRUdJTiBSU0EgUFJJVkFURSBLRVktLS0tLQpNSUlFb2dJQkFBS0NBUUVBNk5GOGlhbGx2UVZwMjJXRGtUa3lydHZwOWVXVzZBOFlWcitrejRUakdZZTdnSHpJCncrbmlObHRHRUZIekQ4K3YxSTJZSjZvWGV2Y3QxWWVTMG85SFp5TjFROXFnQ2d6VUZ0ZE9LTHY2SWVkcGxxb1AKa2NtRjBhWWV0MlBrRURvM01sVEJja0ZYUElUQU16RjhkSlNJRm85RDhIZmRPVjBJQWR4NE83UHRpeFdLbjV5MgpoTU5HMHpRUHlVZWNwNHB6QzZraXZBSWh5ZkhpbEZSNjFSR0wrR1BYUTJNV1pXRlliQUdqeWlZSm5BbUNQM05PClRkMGpNWkVuRGtiVXZ4aE1tQllTZEVUazFyUmdtK1I0TE96RlVHYUhxSERMS0xYK0ZJUEtjRjk2aHJ1Y1h6Y1cKeUxiSWJFZ0U5OE9IbG5WWUN6UmRLOGpscW04dGVoVWM5YzlXaFFJQkl3S0NBUUVBNGlxV1BKWHR6WkE2OG1LZApFTHM0akpzZHlreStld2RaZU5kczV0amNuSFU1elVZRTI1SytmZkpFRDlxVVdJQ2NMWkRjODFUR1dqSHlBcUQxCkJ3N1hwZ1V3RmdlVUp3VWx6UXVyQXYrL3lTbnhpd3VhR0pmaEZNMUNhUUh6ZlhwaGdWbWwrZlpVdm5KVVR2emYKVEsyTGc2RWRiVUU5VGFyVWxCZi94UGZ1RWhNU2xJRTVrZWIvWnozL0xVbFJnOHlEcXo1dytRV1ZKNHV0bktuSwppcXdaTjBtd3B3VTdZU3lKaGxUNFlWMUYzbjRZakxzd001d0pzMm9xbTBqc3NRdS9CVDB0eUVYTkRZQkxFRjRBCnNDbGFXdVNKMmtqcTdLaHJyWVh6YWdxaG5TZWk5T0RZRlNoSnU4VVdWZWMzSWhiNVpYbHpPNnZkTlExSjlYc2YKNG0rMnl3S0JnUUQ2cUZ4eC9SdjlDTk45NmwvNHJiMTRIS2lyQzJvL29yQXBpSG1IRHNVUnM1clVLRHgwZjlpUApjWE43UzF1ZVBYdUpSSy81aHN1YmFPQ3gzT3dkMnU5Z0Q2T3EwQ3NNa0U0Q1VTaUpjWXJNQU50eDU0Y0dIN1JrCkVqRlp4Szh4QXYxbGRFTEV5eHJGcWtiRTRCS2Q4UU90NDE0cWp2VEd5QUsrT0xEM00yUWRDUUtCZ1FEdHg4cE4KQ0F4Ujd5aEhiSVdUMUFINjYrWFdOOGJYcTdsM1JPL3VrZWFjaTk4SmZrYmt4VVJaaHR4Vi9ISHV2VWhuUExkWAozVHd5Z1BCWVpGTm80cHpWRWh6V29UdG5FdHJGdWVLeHljMytMalpwdW8rbUJsUTZPUnRmZ2tyOWdCVnBoWFpHCllFemtDRDNsVmRsOEw0Y3c5QlZwS3JKQ3MxYzV0YUdqRGdkSW5RS0JnSG0vZlZ2djk2Ykp4Yzl4MXRmZlhBY2oKM09WZFVOMFVnWE5DU2FmLzNBL3BoYmVCUWU5eFMrM21wYzRyNnF2eCtpeTY5bU5CZU5aMHhPaXRJanBqQm8yKwpkQkVqU0J3TGs1cTV0SnFIbXkvaktNSkw0bjlST2x4OTNYUytuanhnaWJUdlU2RnA5dytOT0ZEL0h2eEIzVGN6CjYrakpGODVENUJOQUczREJNS0JqQW9HQkFPQXhadmdzS04rSnVFTlhzU1Q3Rjg5VGNrMmlUY1FJVDhnNXJ3V0MKUDlWdDc0eWJvZTJrRFQ1MzF3OCtlZ3o3bkFtUkJLTk03NTFVLzk1UDl0ODhFRGFjREkvWjJPd251RlFIQ1BERgpsbFlPVUkrU3BMSjYvdlVSUmJIU25ubjhhL1hHK256ZWRHSDVKR3FFSk5Rc3oreFQyYXhNMC9XL0NSa25tR2FKCmtkYS9Bb0dBTldyTEN6NzA4eTdWWWdBdFcyVWYxRFBPSVlNZHZvNmZ4SUI1aTlaZklTZ2NKL2JiQ1VrRnJob0gKK3ZxLzVDSVd4Q1BwMGY4NVI0cXh4UTVpaHhKMFlEUVQ5SnB4NFRNc3M0UFNhdlBhQkgzUlhvdzVPaGUrYllvUQpORTVPZ0VYazJ3VmZaY3pDWnBpZ0JLYktaSE5ZY2VsWHRUdC9uUDNyc0N1R2NNNGg1M3M9Ci0tLS0tRU5EIFJTQSBQUklWQVRFIEtFWS0tLS0tCg==
mca@mca:~/deis$ deisctl config platform set domain=local3.deisapp.com
local3.deisapp.com
mca@mca:~/deis$ deisctl install platform && deisctl start platform
● ▴ ■
■ ● ▴ Installing Deis...
▴ ■ ●
Storage subsystem...
Could not find unit template for store-daemon

after following the all steps this the error i get at end
deis$ deisctl install platform
● ▴ ■
■ ● ▴ Installing Deis...
▴ ■ ●
Storage subsystem...
Could not find unit template for store-daemon

if i check fleet of one of instances its gives this message
fleetctl list-units
####################################################################
WARNING: fleetctl (0.9.1) is older than the latest registered
version of fleet found in the cluster (0.9.2). You are strongly
recommended to upgrade fleetctl to prevent incompatibility issues.
####################################################################
UNIT	MACHINE	ACTIVE	SUB

repo: deis/deis


text:
stopping k8s failed

$ deisctl stop k8s
● ▴ ■
■ ● ▴ Stopping K8s...
▴ ■ ●
K8s proxy and kubelet ...
The service 'deis-kube-proxy' failed while stopping.
The service 'deis-kube-kubelet' failed while stopping.
K8s controller and scheduler ...
The service 'deis-kube-controller-manager' failed while stopping.
The service 'deis-kube-scheduler' failed while stopping.
K8s API Server ...
The service 'deis-kube-apiserver' failed while stopping.
Done.
...
core@ip-10-21-1-87 ~ $ systemctl status deis-kube-scheduler
● deis-kube-scheduler.service - Kubernetes Scheduler
   Loaded: loaded (/run/fleet/units/deis-kube-scheduler.service; linked-runtime; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2015-08-04 22:43:11 UTC; 2min 59s ago
     Docs: https://github.com/GoogleCloudPlatform/kubernetes
  Process: 15654 ExecStart=/opt/bin/kube-scheduler --master=127.0.0.1:8080 --policy-config-file=/opt/bin/scheduler-policy.json (code=exited, status=2)
  Process: 15643 ExecStartPre=/bin/bash -c /opt/bin/wupiao $(/usr/bin/etcdctl get /deis/scheduler/k8s/master):8080 (code=exited, status=0/SUCCESS)
  Process: 15564 ExecStartPre=/bin/bash -c /opt/bin/download-k8s-binary kube-scheduler (code=exited, status=0/SUCCESS)
 Main PID: 15654 (code=exited, status=2)

Aug 04 22:36:30 ip-10-21-1-87.us-west-2.compute.internal kube-scheduler[15654]: I0804 22:36:30.339792   15654 ev...
Aug 04 22:37:07 ip-10-21-1-87.us-west-2.compute.internal kube-scheduler[15654]: I0804 22:37:07.630986   15654 ev...
Aug 04 22:38:25 ip-10-21-1-87.us-west-2.compute.internal kube-scheduler[15654]: I0804 22:38:25.705809   15654 ev...
Aug 04 22:38:25 ip-10-21-1-87.us-west-2.compute.internal kube-scheduler[15654]: I0804 22:38:25.735089   15654 ev...
Aug 04 22:40:44 ip-10-21-1-87.us-west-2.compute.internal kube-scheduler[15654]: I0804 22:40:44.629207   15654 ev...
Aug 04 22:43:11 ip-10-21-1-87.us-west-2.compute.internal systemd[1]: Stopping Kubernetes Scheduler...
Aug 04 22:43:11 ip-10-21-1-87.us-west-2.compute.internal systemd[1]: deis-kube-scheduler.service: main process...NT
Aug 04 22:43:11 ip-10-21-1-87.us-west-2.compute.internal systemd[1]: Stopped Kubernetes Scheduler.
Aug 04 22:43:11 ip-10-21-1-87.us-west-2.compute.internal systemd[1]: Unit deis-kube-scheduler.service entered ...e.
Aug 04 22:43:11 ip-10-21-1-87.us-west-2.compute.internal systemd[1]: deis-kube-scheduler.service failed.
Hint: Some lines were ellipsized, use -l to show in full.

I noticed this today as well.  Not an anomaly, I guess.

The problem is that kube-scheduler and friends return 2 when killed by systemd. If I prepend a dash - to the ExecStart line, then stopping the service doesn't fail, but we also wouldn't hear about actual start failures... Not sure how to fix this one.
It's worth noting that the processes do go away in this case, just that the systemd units report as failed.

authors: krancour mboersma


text:
docs: add GAR

Adds a reference to GAR support.
Closes #157

cc @jonjohnsonjr - does this look good for merge?

Content LGTM, but do you mind waiting a until tomorrow to merge? My fix still hasn't rolled out to a couple regions, so I don't want to claim support quite yet.
Thanks Hideto!

do you mind waiting a until tomorrow to merge?

This should be good to go now.

authors: hideto0710 jdolitsky jonjohnsonjr

repo: deislabs/oras


text:
Fix issue 197 by clearing and restoring ARGV

See #197
Test results are the same on this branch as on master.
I tested manually with https://github.com/josephks/bug_demo and this fix works.  I'm not sure how to write an automated test for this.

Yep, it's not easy to write an automated test for this. I think we can live without it!
Can you change the code to look like this:
with_clean_argv { IRB.start(__FILE__) }

and move all the ARGV handling logic to a separate with_clean_argv private method?

Updated

@josephks Just one more nitpick and I'm happy to merge. Now that this is extracted into a method, you no longer need the explicit begin, the beginning of the method does the same job. Could you remove it?
Thanks! :)

:question: I don't have a begin at the beginning of the method.

Oh sorry, I mean like this
def with_clean_argv
  saved_argv = ARGV.dup
  ARGV.clear
  yield
ensure
  ARGV.concat(saved_argv)
end

I didn't do that on purpose.  I only want to restore ARGV after it has been cleared.  If somehow something went wrong with the dup or the clear then I don't want to restore.

I think if ARGV.dup or ARGV.clear go wrong... the user has bigger problems with her system than this one... :)
Anyways, squash to a single commit and I'll merge and release a new version with the fix. Thanks for your contribution @josephks !!

Squashed

authors: deivid-rodriguez josephks

repo: deivid-rodriguez/byebug


text:
WKHTMLTOPDF

funciona sem o WKHTMLTOPDF?

Opa Alberto, não lembro ao certo. mas creio que se remover as chamadas
do WKHTMLTOPDF
para geração do PDF (São apenas algumas linhas simples no arquivo que faz a
impressão dos dados) funcione sim, porém vai trazer o html do boleto e não
o PDF.

Atenciosamente
Deivison Arthur L. Serpa
Founder & CEO Inovarti - Soluções Avançadas em E-commerce
Cel: (21) 99203-8986
Skype: deivisonarthur
sites e blog:

br.linkedin.com/pub/deivison-arthur/1b/35/468/
http://br.linkedin.com/pub/deivison-arthur/1b/35/468/
https://angel.co/inovarti-advanced-ecommerce-solutions
www.deivison.com.br
www.inovarti.com.br

"A Inovarti http://www.inovarti.com.br/ é uma empresa que aspira
inovação e para nós o full acompanhamento tecnológico garante a evolução e
crescimento de nossos clientes. Alinhamos nossa exclusiva qualidade
diferenciada com as melhores parceiras tecnológica do mercado."
"É melhor esperar que um programador produtivo torne-se disponível do que
esperar que o primeiro programador disponível torne-se produtivo!"
2016-04-12 14:07 GMT-03:00 Alberto Braschi notifications@github.com:

funciona sem o WKHTMLTOPDF?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/deivisonarthur/Inovarti_BoletoBancario_Magento_2016/issues/1

Olá,
Pra mim está exibindo esse erro:
BoletoBancario/controllers/StandardController.php(78): Inovarti_Wkhtmltopdf_Helper_Data->getPdf('...')
E o Wkhtmltopdf foi instalado corretamente no Ubuntu

Amigos que estão com erro e instalaram com apt-get ou yum. Removam o WKHTMLTOPDF
e instalem assim:
cd /root
wget http://download.gna.org/wkhtmltopdf/0.12/0.12.3/wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
tar xvf wkhtmltox-0.12.3_linux-generic-amd64.tar.xz
mv wkhtmltox/bin/wkhtmlto* /usr/bin/
wkhtmltopdf  --disable-smart-shrinking  --lowquality --enable-external-links --enable-internal-links

Sim funciona, basta remover as linhas 78-87 do arquivo app/code/local/Inovarti/BoletoBancario/controllers/StandardController.php, e substituir o $this->getResponse()->setBody($pdf); que estava na linha 88 por $this->getResponse()->setBody($order->getPayment()->getMethodInstance()->getBoleto());
Arquivo app/code/local/Inovarti/BoletoBancario/controllers/StandardController.php final:
https://gist.github.com/eflipsivan/f86813d64813d98053bb4a1bda1b1a2a
Isto irá gerar o boleto como HTML, conforme comentado acima.
Esta foi a única maneira para conseguir gerar o boleto, uma vez que tentar gerar o mesmo diretamente em PDF acarreta no problema relatado pelo @rntdesign e a solução até então proposta pelo @robson-lopes é inviável e insegura :face_with_head_bandage:
Testado num container docker do Centos 7.2

authors: albertobraschi deivisonarthur eflipsivan rntdesign robson-lopes


text:
Prevent component from re-rendering on change

Previously in version 1.0.0 we had lifecycle methods such as shouldUpdate to prevent a component from re-rendering on change. I'm wondering how other folks are handling this now, seeing most of these methods no longer exist.
I have a component displaying a video camera that I don't want to re-render while other changes/updates are being fired from my redux store.

I haven't used the following but @rstacruz created deku-memoize - a higher order component which uses your component's shouldUpdate() method to memoize render().
See discussion in #336.

Well, that's depends if you want to never re-render it of if you want to re-render only if props change.
Never re-render
In the first case, you can simply make a singleton:
import VideoCamera from './components'
const videocamera = h(VideoCamera)
const comp = ({ props }) => h('div', {}, [videocamera])

Now, each time comp will be rendered, videocamera will be the same node and totally skip the diff/update phase.
Re-render only on props change
You can use deku-memoize as already suggested, or reselect. I sincerly prefer the latter and that's becuse I already use it in other parts of my app.
import { createSelector } from 'reselect'
import { getVideoProps } from './selectors'

const VideoCamera = ({ props }) => vnode_tree
const stateToProps = (state) => props
export default createSelector(
    stateToProps,
   (props) => h(VideoCamera, props)
)

In case you have more than one instance in the same vnode_tree and with different inputs, you should have a makeVideoCamera function to create them.

Thank you both @Iazel and @danwad

authors: Iazel chrisbuttery danwad

repo: dekujs/deku

license: mit

license_source: bigquery


text:
Implement Unsplash search by queries

It would be nice to implement the query parameter for unsplash random photo API.
I was thinking about a trivial implementation of the query parameter that always filter for that specific term, or a more complex queries parameters that accepts multiple queries that are randomly selected each refresh.
Single query:
config: {
   query: "birds" // every search will be filtered by birds keyword
}

Multiple queries:
config: {
   // every search will be filtered by one of those keywords, randomly selected or cycled through in order
   queries: [
      "birds",
      "home",
      "sky"
   ]
}

It could be used instead or in conjunction with the collections parameter.

a wonderful idea :)

Do you accept pull requests? I should have a working implementation.

Yep, I do accept pull requests and I've been meaning to put together a contributors doc.
Your code looks great, do you mind adding a description for the queries option to the Configuration Options section in the README.md file and submitting the pull request to the dev branch? Thanks for the feature 👍

Nice work!

authors: delightedCrow samusaran

repo: delightedCrow/WallberryTheme


text:
Visible json path

There is a problem with the code

Solved

repo: delighttechnology/ip-addresses


text:
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 127.0.0.1:8080 while running init_social_graph.py

Hi,
Below error is coming while I run init_social_graph.py.
Traceback (most recent call last):
File "/home/test/.local/lib/python3.6/site-packages/aiohttp/connector.py", line 924, in _wrap_create_connection
await self._loop.create_connection(*args, **kwargs))
File "/home/test/anaconda3/lib/python3.6/asyncio/base_events.py", line 778, in create_connection
raise exceptions[0]
File "/home/test/anaconda3/lib/python3.6/asyncio/base_events.py", line 765, in create_connection
yield from self.sock_connect(sock, address)
File "/home/test/anaconda3/lib/python3.6/asyncio/selector_events.py", line 450, in sock_connect
return (yield from fut)
File "/home/test/anaconda3/lib/python3.6/asyncio/selector_events.py", line 480, in _sock_connect_cb
raise OSError(err, 'Connect call failed %s' % (address,))
ConnectionRefusedError: [Errno 111] Connect call failed ('127.0.0.1', 8080)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "init_social_graph.py", line 74, in
loop.run_until_complete(future)
File "/home/test/anaconda3/lib/python3.6/asyncio/base_events.py", line 468, in run_until_complete
return future.result()
File "init_social_graph.py", line 39, in register
resps = await asyncio.gather(*tasks)
File "init_social_graph.py", line 13, in upload_register
async with session.post(addr + "/wrk2-api/user/register", data=payload) as resp:
File "/home/test/.local/lib/python3.6/site-packages/aiohttp/client.py", line 1005, in aenter
self._resp = await self._coro
File "/home/test/.local/lib/python3.6/site-packages/aiohttp/client.py", line 476, in _request
timeout=real_timeout
File "/home/test/.local/lib/python3.6/site-packages/aiohttp/connector.py", line 522, in connect
proto = await self._create_connection(req, traces, timeout)
File "/home/test/.local/lib/python3.6/site-packages/aiohttp/connector.py", line 854, in _create_connection
req, traces, timeout)
File "/home/test/.local/lib/python3.6/site-packages/aiohttp/connector.py", line 992, in _create_direct_connection
raise last_exc
File "/home/test/.local/lib/python3.6/site-packages/aiohttp/connector.py", line 974, in _create_direct_connection
req=req, client_error=client_error)
File "/home/test/.local/lib/python3.6/site-packages/aiohttp/connector.py", line 931, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 127.0.0.1:8080 ssl:None [Connect call failed ('127.0.0.1', 8080)]

python version-Python 3.6.6

Could you please help me what should I do to correct this.

Have you verified that port 8080 is not used in your machine?

Hi,
Yes it's not. And 8080 port is also open.
I tried with some other port as well just to check.. But still the same
issue.
Please let me know if I can do something to correct it.
Thanks & Regards,
Preyashi Agarwal
On Thu, 16 May 2019, 16:51 Christina Delimitrou, notifications@github.com
wrote:

Have you verified that port 8080 is not used in your machine?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/delimitrou/DeathStarBench/issues/3?email_source=notifications&email_token=AIMJHZUUD5DQVFRO5NSFOH3PVU7THA5CNFSM4HNBG4S2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVRP7WY#issuecomment-493027291,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIMJHZT5YSML4NZSBO4EIJ3PVU7THANCNFSM4HNBG4SQ
.

Was the Nginx webserver running correctly? You could check this by docker ps.

Hi,
The Nginx service is not created yet, because the error comes while I run
scripts/init_social_graph.py script.
I tried debugging the code and the error comes at the line highlighted in
scripts/init_social_graph.py script.
[image: image.png]
Could you please help me, what could be done to correct this?
Thanks & Regards,
Preyashi Agarwal
On Fri, May 17, 2019 at 1:01 AM Yu Gan notifications@github.com wrote:

Was the Nginx webserver running correctly? You could check this by docker
ps.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/delimitrou/DeathStarBench/issues/3?email_source=notifications&email_token=AIMJHZUJ6Q62ZV7IH6DTVJTPVWZBJA5CNFSM4HNBG4S2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVS2UYQ#issuecomment-493202018,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIMJHZVHKGASFKJA2WQVKXDPVWZBJANCNFSM4HNBG4SQ
.

The image didn’t show up. Could you also do docker-compose logs nginx-thrift, which would print out the error message

Hi,
The issue was with my OpenSSL and pip library. Seems there was a version
mismatch.  I fixed it.
It's working fine now.
Thanks a lot for your help. I really appreciate the same.
Can you help me with another query. The values of threads and connections
and throughput while running ./wrk command. What is the acceptable ratio of
these 3. I was thinking of giving 1:1:1 ration(like 10 threads for 10
connections with a throughput of 10 at 30s time). IS this correct?
Thanks & Regards,
Preyashi Agarwal
Thanks & Regards,
Preyashi Agarwal
On Fri, May 17, 2019 at 12:34 PM Yu Gan notifications@github.com wrote:

The image didn’t show up. Could you also do docker-compose logs
nginx-thrift, which would print out the error message
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/delimitrou/DeathStarBench/issues/3?email_source=notifications&email_token=AIMJHZRP5KKSOQDR5VACTBTPVZKHJA5CNFSM4HNBG4S2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVT5WYY#issuecomment-493345635,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIMJHZXJRDL7EWDAGNEZKBTPVZKHJANCNFSM4HNBG4SQ
.

I would suggest you to give number of threads the same as number of cores you give to wrk2. You don’t want either too many connections or too much load per each connection. I would suggest no more than 1000 connections and no more than 1000qps per each connection based on our experience.

Hi, The issue was with my OpenSSL and pip library. Seems there was a version mismatch. I fixed it. It's working fine now. Thanks a lot for your help. I really appreciate the same. Can you help me with another query. The values of threads and connections and throughput while running ./wrk command. What is the acceptable ratio of these 3. I was thinking of giving 1:1:1 ration(like 10 threads for 10 connections with a throughput of 10 at 30s time). IS this correct? Thanks & Regards, Preyashi Agarwal Thanks & Regards, Preyashi Agarwal
…
On Fri, May 17, 2019 at 12:34 PM Yu Gan @.***> wrote: The image didn’t show up. Could you also do docker-compose logs nginx-thrift, which would print out the error message — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#3?email_source=notifications&email_token=AIMJHZRP5KKSOQDR5VACTBTPVZKHJA5CNFSM4HNBG4S2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVT5WYY#issuecomment-493345635>, or mute the thread https://github.com/notifications/unsubscribe-auth/AIMJHZXJRDL7EWDAGNEZKBTPVZKHJANCNFSM4HNBG4SQ .

Hi, can you please share the solution in details? I am stuck with the same problem and I am not being able to find a workaround.

Hi, I'm also facing this issue. Could anyone share your solution?

Hello,
I have this exact same issue. I am running socialMedia on my K8s cluster. When I check the logs of the nginx-thrift pod what I get is:
[error] 12#12: *1 open() "/usr/local/openresty/nginx/pages/favicon.ico" failed (2: No such file or directory), client: 127.0.0.6, server: localhost, request: "GET /favicon.ico HTTP/1.1", host: "10.12.0.149:32112", referrer: "http://10.12.0.149:32112/"

repo: delimitrou/DeathStarBench


text:
[BUG]: Add the helm-charts-version parameter to the install command for all drivers in csm-docs

Bug Description
Add the helm-charts-version parameter to the install command for all drivers.
/csi-install.sh --namespace unity --values ./myvalues.yaml --version latest --helm-charts-version
csm-docs/content/docs/deployment/helm/drivers/installation/unity.md at main · dell/csm-docs (github.com)
Logs
No Logs
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
N/A
Expected Behavior
N/A
CSM Driver(s)
CSI-Powerflex , CSI-Powerscale, CSI-Powerstore, CSI-Powermax
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
N/A
Operating System
N/A

/sync

link: 22587

repo: dell/csm


text:
Support get_backend_for_uri_with_options in Read Path

Description
Goal: I am trying to read a Delta Table from a non-AWS S3 object store (like minio). I seem to be able to read the table metadata but then when reading data I get an error that seems to indicate that my endpoint_override is being ignored and requests are sent to aws instead.
My code looks like this:
from deltalake import DeltaTable
storage_options = {"AWS_ACCESS_KEY_ID": ACCESS_KEY, "AWS_SECRET_ACCESS_KEY":SECRET_KEY, "AWS_ENDPOINT_URL": ENDPOINT_URL, "AWS_REGION": 'us-east-1'}
dt = DeltaTable("s3://warehouse/tpcds_sf1000_dlt/item/", storage_options=storage_options)
print(dt.dt.pyarrow_schema()) # SUCCESS
print(dt.to_pandas().head()) # FAILS

In looking through the code, I wonder if the line here needs to use the "with_options" variant:
https://github.com/delta-io/delta-rs/blob/d10b428f15906dd74f5d33cf592288cdf7dd1e66/python/src/lib.rs#L485
in order to pass through my configs?
Use Case
Delta on S3 object stores like Minio, Swift, FlashBlade, Vast, ECS, etc.
Related Issue(s)

Thanks for reporting this! Our current API is problematic in that we can't retrieve the storage backend once it's been created in the DeltaTable. We'll need to refactor a bit, probably changing the storage backend to use an Arc, instead of an owned Box pointer.
For now, the workaround is to explicitly pass a configured PyArrow filesystem:
from deltalake import DeltaTable
from pyarrow.fs import S3FileSystem

storage_options = {
    "AWS_ACCESS_KEY_ID": ACCESS_KEY,
    "AWS_SECRET_ACCESS_KEY":SECRET_KEY,
    "AWS_ENDPOINT_URL": ENDPOINT_URL,
    "AWS_REGION": 'us-east-1'
}
dt = DeltaTable("s3://warehouse/tpcds_sf1000_dlt/item/", storage_options=storage_options)

pa_fs = S3FileSystem(
    access_key = storage_options["AWS_ACCESS_KEY_ID"],
    secret_key = storage_options["AWS_SECRET_ACCESS_KEY"],
    endpoint_override = storage_options["AWS_ENDPOINT_URL"],
    region = storage_options["AWS_REGION"],
)
print(dt.dt.pyarrow_schema()) # SUCCESS
print(dt.to_pandas(filesystem=pa_fs).head()) # This *should* work

thanks @wjones127 for the quick response.  This helps me get a little further but I think I then run afoul of differing path expectations. After making the change, I get the following error:
pyarrow.lib.ArrowInvalid: Expected an S3 object path of the form 'bucket/key...', got a URI: 's3://warehouse/tpcds_sf1000_dlt/item/part-00000-1805aaca-4959-40a2-87b1-c42385e763e8-c000.snappy.parquet'

I think the problem is coming from here: https://github.com/apache/arrow/blob/master/cpp/src/arrow/filesystem/s3fs.cc#L364
Where here it's expecting a "bucket/key" path without a URI (i.e., no "s3://"), but I could be wrong.
Am I still missing something or is this maybe just not quite functional yet?
If there's any other issues tracking the work needed, I'd be happy to take a look and see if I can't contribute.

Am I still missing something or is this maybe just not quite functional yet?

Darn. I guess that workaround doesn't work. Thanks for reporting that failure too.
We don't yet have integration testing with object stores, but that's high priority in the next few months.

If there's any other issues tracking the work needed, I'd be happy to take a look and see if I can't contribute.

Fixing #696 should make the workaround function. Fixing #690 should make this work without the workaround. You are welcome to submit a PR on either!

Whilst working on #632 I was moving the storage backend behind an Arc as well, so I opened a quick PR with just that included (#697). This will not yet fix the issue, but prepares the rust side for the python side to use a shareble reference to the store, and avoid re-creating it.

@joshuarobinson with the release of 0.6.1 we now - whenever possible - reuse the same backend store also in the read path. Could you check if that works for you?

Hi @roeap
I've just tried again with 0.6.2 and the issue is now fixed!
fyi, manually specifying the pyarrow.filesystem doesn't work, but letting Delta take care of it behind the scenes does work (and is the better option, IMO)

authors: joshuarobinson roeap wjones127

repo: delta-io/delta-rs


text:
Bump arrow deps and bring map support to schema

Description
Let's start merging feature specific branches one by one. This one with map support. I've also bumped the arrow-rs refs to the latest to pick other fixes in upstream.

Although we have an issue with #367. That PR changed semantics for put_obj because not it does not overwrite existing path which is required for _last_checkpoint. And overwrite is default behaviour for S3 also

Blocked by #376

Also blocked by datafusion deps, either version conflict or we have to updated our source code

@mosyp does the fixes you need to pull in exist in arrow's active release branch (https://github.com/apache/arrow-rs/tree/active_release)? If so, pointing to commits in that branch should help fix the datafusion version conflict.

FYI, upstream just started the release vote for arrow 5.2, so if everything goes well, we should be able to pin to 5.2 in 3 days.

@houqp Do you have a power to do later the same for datafusion? Their deps on arrow is what failing the compilation

yeah, I have a PR for datafusion ready to merge once arrow 5.2 is released: https://github.com/apache/arrow-datafusion/pull/869.
Just to double check, we are not blocked on this PR for kdi right? If we need to merge this PR to release KDI, I am cool with that. Otherwise, it's better to keep reference this branch in KDI until 5.2 is out.

@houqp yes, we're not blocked and using this branch in kdi, lo yea, let's keep it as is for now

@mosyp given that arrow 6.x release will still take some time, how about we merge this branch as is into main? I think it's fine to pin arrow by git reference.

authors: houqp mosyp


text:
Creating image for AMI deletion

Related Issues
related: https://github.com/demisto/etc/issues/30073
Description
Added an image based on alpine with the packages boto3, coloredlogs and argparse.
This image will be used in the github actions in order to run the build that will clean old images

Docker Image Ready - Dev
Docker automatic build at CircleCI has deployed your docker image: devdemisto/ami-management:1.0.0.14779
It is available now on docker hub at: https://hub.docker.com/r/devdemisto/ami-management/tags
Get started by pulling the image:
docker pull devdemisto/ami-management:1.0.0.14779

Docker Metadata

Image Size: 29.78 MB

Image ID: sha256:45b9942b27ca6025dd36de5c61152c521728c6553206b1ea1dc431c1202854ee

Created: 2020-12-20T14:11:15.067366396Z

Arch: linux/amd64

Command: ["python3"]

Environment:

PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=C.UTF-8
GPG_KEY=E3FF2839C048B25C084DEBE9B26995E310250568
PYTHON_VERSION=3.8.6
PYTHON_PIP_VERSION=20.3.3
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/5f38681f7f5872e4032860b54e9cc11cf0374932/get-pip.py
PYTHON_GET_PIP_SHA256=6a0b13826862f33c13b614a921d36253bfa1ae779c5fbf569876f3585057e9d2
DOCKER_IMAGE=devdemisto/ami-management:1.0.0.14779

Labels:

org.opencontainers.image.authors:Demisto <containers@demisto.com>
org.opencontainers.image.revision:9f82e61f9df3ae1e27e8f9e2fd988ea3e00d9dc6
org.opencontainers.image.version:1.0.0.14779

authors: dc-builder hod-alpert

repo: demisto/dockerfiles


text:
Task Note / Scratch Note - not linking correctly

Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[x] Workspace.  VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup.  Dendron's Lookup Command
[ ] Views.  Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema.  Dendron Schemas
[ ] Pod.  Data import from / export to Dendron
[ ] Publish.  External Site Publish
[x] Markdown.  Markdown features, such as syntax support and features

Describe the bug
After creating a task note link or a scratch note link, the link in the originating file does not link to the  note after cmd+click-ing the link.
Quick video of the issue https://app.usebubbles.com/aCq5j7vQzDVVUzGqDAAXWe/untitled-bubble
To Reproduce
Steps to reproduce the behavior:
https://app.usebubbles.com/aCq5j7vQzDVVUzGqDAAXWe/untitled-bubble

Make a task note or scratch note
Click on the task note link

Expected behavior
It should link to the task note not make a new file
Screenshots
If applicable, add screenshots to help explain your problem.
https://app.usebubbles.com/aCq5j7vQzDVVUzGqDAAXWe/untitled-bubble
Desktop (please complete the following information)

OS: MacOS
Versions (all that apply to bug):

Dendron Extension: .116
VS Code version: 1.73.0
Dendron CLI:

Additional context
NA
Dendron Log file
Please attach the output of > Dendron:Dev: Open Logs here
dendronlogs.txt

Hi @jbamford - it doesn't look like the Create note for 'Example Task' option is provided by Dendron but by a different extension.  Do you have another markdown related extension installed?
If you use Dendron: Go To command while your cursor is on the link, you should navigate to the note that was just created (task.2022.11.07.example-task.md).  You can run the Dendron: Go To command through Ctrl+Enter, but the shortcut may depend on your setup.  Alternatively, you can Cmd+Click on the link text itself (not the popup panel).

authors: jbamford jonathanyeung

repo: dendronhq/dendron


text:
Having '.md' anywhere inside new note name will break title generation

Please select the area your Bug applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[x] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Describe the bug
When creating a new note, any hierarchy element that starts with 'md' (and is not a domain) will break the auto title generation by using the previous hierarchy element to title the note/stub that starts with 'md' and any subsequent children instead of using the proper ones.
To Reproduce
Steps to reproduce the behavior:

Go to Lookup.
Write learn.mdn.css.text
Frontmatter shows title: Learn for the new note.
Expand tree view to see the whole new hierarchy titled 'learn'.
└── learn
    └── learn
        └── learn
            └── learn

Expected behavior
The note would be titled 'Text' and the tree view would look like this:
.
└── learn
    └── mdn
        └── css
            └── text

Desktop

OS: macOS 10.15
VSCode: 1.57.1
Dendron: 0.47.0

Dendron Log file
Please attach the output of >Dev:Dendron: Open Logs here
dendron.log

That's a bug. Thanks for catching this. We'll look into this for the upcoming release

I think #1972 is probably related to this. I'd guess that there's a regex somewhere which is \.md instead of \.md$.
@kevinslin Any pointers as to where this issue might be in the codebase? I could have a look and see if I can find the faulty regex if you're able to offer a general pointer, like which package this code would be in, etc.

Hi, this has been fixed with Dendron v0.82. Please let us know if it continues to happen, otherwise, this issue will close in a few days.

Looks fixed to me.

authors: Harshita-mindfire LoPawlie chmac kevinslin


text:
Power BI Deneb Vega memory management

Hi,
We have had some incidents where our Power BI report has been crashing. It has mainly been occurring on the iPhone app but also on Power BI desktop. The error on the iPhone (16 prod) is "your device may not have enough memory to load this report". On desktop it is Webview2 out of memory. I understand that this is often attributed to custom visualisations having memory leaks.
Our dashboard uses multiple Vega and Vega-lite visuals across several pages. We are using Deneb 1.6.2.1
and Power BI desktop 2.132.1053.0
What I've noticed is that the WebView2 memory utilisation ratchets up every time a Deneb visualisation is opened (not surprisingly) but it doesn't decrease when the visual is either hidden or I switch to a different page. So, If I keep moving between pages then the memory utilisation gradually increases by at least 100mb each time. The memory seems to be only released when the Power BI file is closed.
None of the visuals use a lot of data. The total size of the Power BI file is 5.5mb
I can't share the Power BI file publicly, but I can confirm that I have observed the above memory pattern when using the following public visualisations:

https://github.com/PBI-David/Deneb-Showcase/tree/main/Particle Simulation Background

Creating a default simple bar chart using Deneb-Vega in Power BI with one category field and one numerical field.

While we can manage this memory issue for the time being, I noticed that the Vega API has a finalise() method that is intended to specifically release the memory when the visual is no longer required. I am wondering if there is anything that can be done future versions of Deneb (assuming it hasn't already been done) to release the memory when a visualisation is no longer active.
I hope this makes sense.
Thank you in advance.

Moving to the correct repo so it can be tracked against Deneb rather than the doc site code.
I'm currently sick, so can't look at this in too much detail, but some quick interim feedback and follow-up questions for when I'm a bit closer to 100% and have some time available:

Is the memory leak Deneb-specific, or is it for any other custom visuals? The visual host (MS environment for all custom visuals) has been known to leak memory in the past, and it would be very helpful if you could confirm this if you have a profiling harness set up and have some time available to check (my time is spread pretty thin for support so anything that can give me more info will be a great help 🙏 - TIA if you can).
Is there a specific reason you're using 1.6 instead of 1.7? 1.7 has a lot of performance enhancements to the underlying code.
Unfortunately, as I don't have access to an iPhone for testing (or your spec) if I can find anything specific, I may need you to help me with validating any builds that try to fix the issue. Note that any potential remediations would be against 1.7 rather than 1.6.

Regarding the .finalize(), we use the react-vega package to handle the spec rendering. If the component is unmounted (e.g. when the visual is destroyed), this should .finalize() the view for us without us having to intervene. We do have access to the view instance, so we may be able to manually .finalize() when the component unmounts rather than assuming this is being taken care of.
As a heads-up, for Deneb v2, I'm ditching react-vega and building a bespoke lifecycle management system for the view. This will auto-finalize each time the view is destroyed (which will also be much less often than in v1). While I don't have an ETA for v2, as it is a complete rewrite and subject to my available free time, the Vega view performance and stability are the core of what I'm building and are already done, so I'm confident that if we can't address on the v1 architecture, we will be able to do more in v2 when it's ready.

Hi,
Thanks for your reply and I hope you are feeling better. Also thank you for your work on Deneb, it has helped me do many things in Power BI that I couldn't otherwise do.
I've spent a bit more time experimenting. I've tried a few other custom visuals and I have now seen the pattern occurring in Card Browser.
I can use both versions 1.7 and 1.6 on Power BI desktop, but I am restricted to only 1.6 when deploying it to a web app in my organisation. We are going to try and get it upgraded. Having said that I had a play with both versions today and I could still observe in in 1.7 as well.
I've also noticed that it runs out of memory on the iPhone app when I am also running the Edge app. Which makes sense because they both use WebView2. So, it looks like it's the same issue as on the desktop. I've played around with it on my iPad and it doesn't run out of memory, even with Edge running.
We can manage for the time being, particularly since it seems to be ok on platforms other than the iPhone. I raised this issue more to provide feedback on what I am observing. I am happy to assist you with validation if I can.
Thanks again and I am looking forward to v2.

authors: dm-p j-aga

repo: deneb-viz/deneb


text:
Workspace.get is deprecated.

atom.workspace.paneContainer has always been private, but it is now gone. Please use atom.workspace.getCenter() instead and consult the workspace API docs for public methods.
Workspace.get (<embedded>:24605:18)
Workspace.save (/Users/xream/.atom/packages/save-workspace/lib/models/workspace.js:46:41)
Save.<anonymous> (/Users/xream/.atom/packages/save-workspace/lib/commands/save.js:38:25)
InputWorkspaceNameView.cancelled (/Users/xream/.atom/packages/save-workspace/lib/input-workspace-name-view.js:70:12)
InputWorkspaceNameView.cancel (/Users/xream/.atom/packages/tab-numbers/node_modules/atom-space-pen-views/lib/select-list-view.js:263:14)
InputWorkspaceNameView.confirmSelection (/Users/xream/.atom/packages/tab-numbers/node_modules/atom-space-pen-views/lib/select-list-view.js:340:21)

@xream when this object is going to be deprecated?
I can't find any reference in docs - https://atom.io/docs/api/v1.6.0/Workspace

I'm using Atom 1.17 beta. Maybe it'll be deprecated in the next stable release.

Please Fix

Same issue

I confirm it's still there.

@AaronVigal @ernest35 @er-vin @xream hey guys! I really appreciate that you are using this plugin and I hope it helps you on daily basis. If this bug is still actual and can be easily reproduced - I will prioritize this issue to be fixed as soon as possible. Thanks! Also, I will be really thankful and it will be easier to find the bug if you will write your steps to reproduce this issue.

It works, it's just that I'm being pestered by Atom's Deprecation Cop. When you install the save-workspace package you see in the status bar the mention "1 deprecation" with details when you click on it.

Agree with @er-vin - the plugin seems to work as expected but Atom's Deprecation Cop flags it as an issue.

+1 fix please.. this package is exactly what I needed!

Fixed with #27 and available in release v.0.5.0
Thank you guys for waiting so long! And please post if you will have any other issues connected to this one or any other.

repo: denieler/save-workspace-atom-plugin


text:
Added setter for Driver.processQueryText

Possible solution for https://github.com/denisenkom/go-mssqldb/issues/498
Details description can be found inside issue #498

No. This is going away.
I would consider exposing the routine that re-writes the query you may optionally call on your queries prior to submitting them in a sub-package. But no more query re-writing behind your  back.

authors: kardianos zygisx

repo: denisenkom/go-mssqldb


text:
Issue for the example

Describe the bug
A clear and concise description of what the bug is.
When I use the example that Provided:
from ad_api.api import sponsored_products
my_credentials = dict(
     refresh_token='************************',
      client_id='************************',
      client_secret='************************',
)
result = sponsored_products.Campaigns(credentials=my_credentials).list_campaigns()
print(result)

Get the error:
     self.credentials = CredentialProvider(account, credentials, verify_additional_credentials).credentials
AttributeError: 'CredentialProvider' object has no attribute 'credentials'. Did you mean: 'load_credentials'?

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.

my_credentials = dict(
refresh_token='your-refresh_token',
client_id='your-client_id',
client_secret='your-client_secret',
profile_id='your-profile_id',
)

repo: denisneuf/python-amazon-ad-api


text:
mathify should not be called if opts.allowMath is false

https://github.com/denoland/deno-gfm/blob/main/mod.ts#L95
https://github.com/denoland/deno_blog/pull/118

This is actually non-trivial with the current setup. Any ideas on how to do this cleanly?

To clarify, math blocks defined as code blocks such as:
```math
```
are non-trivial to cleanly avoid using mathify.

@hashrock, did you fix this with https://github.com/denoland/deno-gfm/pull/72?
(I think you have to repeat the keyword to get it to automatically work, e.g. closes 10, closes 11 instead of closes 10 11.)

@deer
Yeah! Thank you! I learned it today😆

authors: deer hashrock lino-levan

repo: denoland/deno-gfm


text:
[Bug]: plugin does not respect .gitignore

Describe the bug
Hi! 👋
I've noticed that the plugin does not respect .gitignore.
My mac and android both have different files open etc in Obsidian, affecting the .obsidian/workspace file.
Hence, I added .obsidian/workspace to .gitignore, to avoid committing the workspace file as it is transient and device-dependent.
However this is not respected.
Currently, both parties are constantly committing their opinion on the file, also leading to conflicts (but they push through).
Relevant errors (if available)
No response
Steps to reproduce

write a .gitignore containing the line .obsidian/workspace
commit the .gitignore
run git rm --cached .obsidian/workspace, and commit that deletion (file should still exist locally but is now ignored)
obsidian will now check in .obsidian/workspace again, commits, pushes.
this renders .gitignore useless, because files that are already checked in will be tracked regardless of what .gitignore says.

Expected Behavior
.gitignore is respected, and neither party tries to push .obsidian/workspace since the file was never staged.
Addition context
No response
Operating system
macOS
Plugin version
2.5.1

I'm using the system installed git on desktop. So I'm very sure it's respected. I guess it's in the wrong directory or since you can't run git rm --cached .obsidian/workspace on mobile you got the file via mobile on desktop.

Ok let me check!

I'm running into the same problem.
Currently looking for a way to make it work

i wansnt completely clear in step 4: its obsidian on mobile that doesnt like the new commits from desktop: because workspace file is changed locally (mobile) and removed on remote. it does popups with a pull, conflict, push.
the resulting pushed commit will contain the workspace file as it was on mobile.

@ddelange So your issue is that gitignore is working on desktop. So you are able to commit the "deleted" workspace file. But when pulling that commit on mobile, you get a merge conflict because the workspace file has changed. May you try to discard the workspace changes on mobile and then pull?

Thanks @Vinzent03, I can confirm that the plugin does respect .gitignore! Fix was to:

on mobile, disable auto pulling/pushing temporarily, close app
on desktop, git rm --cached .obsidian/workspace, commit again and push
on mobile, open command palette -> Obsidian Git: Open source control view
click the minus next to the workspace file  (under changed files) to discard the changes
pull the removal commit, this time without conflicts
enable auto pull/push again, all good! :tada:

Great! Things are always a bit more complicated if you can only use the gui.

on a similar note, it seems mobile and desktop are fighting over this one
--- a/.obsidian/plugins/obsidian-git/data.json
+++ b/.obsidian/plugins/obsidian-git/data.json
@@ -21,6 +21,6 @@
   "differentIntervalCommitAndPush": false,
   "changedFilesInStatusBar": false,
   "username": "__token__",
-  "showedMobileNotice": false,
+  "showedMobileNotice": true,
   "refreshSourceControlTimer": 7000
 }

Did you correctly pull the true value on mobile? Does the mobile plugin change the true value to false by itself?

sounds like it: desktop is committing&pushing true, mobile is committing&pushing false

You may have to first commit the false on mobile and the true on desktop, and then just pull on mobile. Close Obsidian on mobile and reopen. I think the issue is that the false is still cached in the running obsidian-git plugin instance. And writes its cached settings to the disk, ignoring the previously pulled value.

closed obsidian on android, manually edited data.json to true, started app, app pulled commit with true from desktop, no pushes with false coming from mobile as of yet 🎉

repo: denolehov/obsidian-git


text:
Modelのフィールドを拡充する。

[x] Reviewのフィールド
[x] Issueのフィールド
[x] Documentのフィールド
[x] OutlineNodeのフィールド

昨日中に報告できておらずすみません。昨日に実装した成果が下記となります。
Reviewのフィールド拡充
コミット：https://github.com/denso-create/LightningReview-ReviewFile/commit/cbf2efec5cedf4565bc37e2eac7e2c5afe0e6152
LRのExtensionFrameworkで公開しているプロパティを参考にReviewとしては基本設定タブと予実タブの情報が取得できるように拡充。

追加したプロパティ
EndCondition(終了条件)、ProjectName(プロジェクト名)、ProjectCode(プロジェクトコード)
ActualScale(実績成果量)、IssueCountOfGoal(目標件数)、IssueCountOfActual(実績件数)
保留：xmlの階層が深く取得に時間がかかりそうであり、現時点ではユーザの主な収集対象ではないためTODOとしている
Status(ステータス)、Domain(ドメイン)、ReviewType(レビュー種別)、ReviewStyle(レビュー形式)

Documentのフィールド拡充
コミット：https://github.com/denso-create/LightningReview-ReviewFile/commit/eeb813a369aea385be45a904a6198b90ea5d7e38
LRのExtensionFrameworkで公開しているプロパティを参考に拡充

追加したプロパティ
AbsolutePath (絶対パス)、ApplicationType(アプリケーションタイプ)

コメントの付与
他の実装中にも逐次コメントは記載しておりますが、下記コミットで付与しております。
文字化けしていたので修正：https://github.com/denso-create/LightningReview-ReviewFile/commit/ded0e4da3270dedb243270fc8c5445428aa18c5c
サマリー記載および微修正：https://github.com/denso-create/LightningReview-ReviewFile/commit/713283332fef1004debef43cf8eda57c12617d1e
region追加および並び替え：https://github.com/denso-create/LightningReview-ReviewFile/commit/f71920dae596a824383e0ff87c0d847a5c8ffd48

Issueのフィールド拡充
コミット：https://github.com/denso-create/LightningReview-ReviewFile/commit/3ae31320e4e8c9fc8eae6b83042fe6548a86da86 f854b8e1ee0a7b89870881a2da839c9c4d3fba33
LRのExtensionFrameworkで公開しているプロパティを参考に拡充

追加したプロパティ
CorrectionPolicy(修正方針)
SendingBackReason(差し戻し理由)
OutlineName(関連づいているアウトライン名)
RootOutlineName(関連づいているドキュメント名)
DateReported(報告日)
DueDate(期日)
DateFixed(修正日)
DateConfirmed(確認日)

OutlineNodeのフィールド拡充
V10での子ノードの取得も行えていないため別途課題として登録し、その際に下記プロパティも実装する

保留：xmlから直接取得できる要素ではなく、Outlineはユーザの主な収集対象ではないため、以下のフィールドは未実装
PhysicalLocationXml(物理的位置)
Path(アウトラインパス)
Level(階層の深さ)
Parent(親ノード)

ReviewFileToJsonService.Modelsの拡充
ReviewFileToJsonServiceのModelsについても同じように拡充しました（ReviewとIsasueクラス）
コミット：https://github.com/denso-create/LightningReview-ReviewFile/commit/78816649f120a8cb04dce2459f036d1a55c9f0c6
DateTime型のフィールドの異常系の処理を追加
日付系(期日や修正日時等)の要素を空にした状態のレビューファイルを読み込んだ際に例外が出る場合があるため、そのような場合はnullを返すフェールセーフ処理を追加しました
コミット：https://github.com/denso-create/LightningReview-ReviewFile/commit/5e534bc2d70ca8a34b8f6a595aeb2097de460a01 https://github.com/denso-create/LightningReview-ReviewFile/commit/6732f952289665b2630fbac31530a9fc3d6233eb https://github.com/denso-create/LightningReview-ReviewFile/commit/6732f952289665b2630fbac31530a9fc3d6233eb

上記の通り、優先度の低い未実現のフィールドは以下のタスクに分離済み。
https://github.com/denso-create/LightningReview-ReviewFile/projects/1#card-55167991
https://github.com/denso-create/LightningReview-ReviewFile/projects/1#card-55167842
それ以外は、以下のプルリクで完了済みなのでクローズします。
https://github.com/denso-create/LightningReview-ReviewFile/pull/6

authors: kojimadev kuriyama-dcinc yus-sasaki

repo: denso-create/LightningReview-ReviewFile


text:
Toggle Switch under Shortcuts

Is it possible to add a switch to toggle under the shortcuts section?
My air purifier has the option to lock the physical controls on the machine and I would like to be able to have a toggle to lock and unlock.

Came here to ask this.

authors: DJBenson hopperjef

repo: denysdovhan/purifier-card


text:
Custom PHP environment variables

Hi,
I'm using Bedrock with wordpress to be able to install my plugins using composer. For premium plugins, I am using private-composer-installer to install them. I am injecting multiple environment variables which are the keys to download the plugins.
Currently there are only two variables supported: ACF_PRO_KEY and GRAVITY_FORMS_KEY. Is there any way to add other ones?
For example, I am using these for ACF Pro and WPML.

PLUGIN_ACF_KEY (I could change this one to ACF_PRO_KEY)
PLUGIN_WPML_SUBSCRIPTION_KEY
PLUGIN_WPML_USER_ID

We also use Bedrock by Roots to manage WordPress. We then use Dependabot to manage our WordPress plugins, with great help by the excellent WordPress Packagist.
Currently our main use of PHP environment variables is to manage the plugin Advanced Custom Fields Pro, which depends on a PHP environment variable to be updated as explained by @Gandhi11 above.
Our composer solution for ACF is using PiventIT/ACF-pro-installer by @Qrious. A lot of people is also using PhilippBaschke /acf-pro-installer. On top of using ACF this way, we also have other plugins which depends on a similar workflow.
A week ago we started see a new pull reuqest from Dependabot across our repos, with information regarding the future of Dependabot. The information has the following part which is related to custom PHP enciroment variables in the future.

Your repo is using PHP environment variables. There is no support for this registry type in GitHub-native Dependabot, so these registries were not added to the new config file. We recommend fetching these dependencies via GitHub Actions.

I would love to see a future in which it's possible to still update dependencies that need a PHP env variable in a good way. Anyone who have ideas on a good way forward that would work for a multitude of plugins (maybe using Github Actions as mentioned) would be a great addition to the PHP/WordPress community.
I would love if @asciimike or someone from the Dependabot team would pitch in here, since it would be great to hear their ideas in more detail, on how those who depends on this, could move this forward together.

This situation is undesired in my opinion, certainly because it is a significant step backwards compared to the preview.

It's possible you may have to remove the ACF dependency in your composer.json for normal runs (if it's causing a failure that isn't updating other dependencies), and keep around a composer-dependabot.json

My main issue with this 'solution' is that it complicates the flow of all developers in the teams that need to understand this workaround and remember it at all times when interacting with composer. It is very easy to do it wrong, since a normal composer install appears to work just fine, but you end up missing the packages that need PHP environment variables for installation (i.e. ACF).  Secondly users need to keep both composer.json files in sync, which is an additional burden.

A way forward which would require to manage multiple composer-files to update a few dependencies (in our case) is not a solution that feels great. It would add more work, to something which is aimed at creating less work. We would probably then start ignoring these dependecies from Dependabot. It feels like a step backwards.
I would propose that the enviroment-variable support is added to the native version, since it's working in Dependabot Preview. It would make Dependabot more useful for all of us that need to work with environment variables.
I imagiae that the syntax part could look something like this:
version: 2
updates:
  - package-ecosystem: composer
    directory: "/"
    schedule:
      interval: weekly
    enviroment-variable:
      - ACF_PRO_KEY: ${{secrets.MY_ACF_PRO_KEY}}

Since this was posted, the PHP packaging world has continued to mature and standardize on composer, which includes support for private registries.
For example, the ACF_PRO_KEY env var mentioned above is no longer needed because ACF Pro recently rolled out their own private registry:

https://github.com/pivvenit/acf-pro-installer/issues/222#issuecomment-1410172129
https://www.advancedcustomfields.com/resources/installing-acf-pro-with-composer/

Closing as won't fix because we aren't going to add support for custom environment vars for authentication / secrets purposes. Instead, ask your plugin provider to offer their own private registry... not only will it work out of the box with Dependabot, it'll also work much better with the rest of the PHP/composer tooling ecosystem.

authors: Gandhi11 Qrious jeffwidman viktorbijlenga

repo: dependabot/dependabot-core


text:
Fix fetching bug for requirements.in files

Hi there,
There seems to be a bug in the file_fetcher.rb class when trying to fetch requirements.in files:
If there's also a requirements.txt file in the repository, the download works.
If not, Dependabot doesn't continue to look for requirements.in files and raises a DependencyFileNotFound exception here.
When I add requirements_in_files.any? to the list of checks the download works just fine. Maybe, there's a better fix for this, didn't investigate the issue any further.
Thanks.

👋 Hey @stulle123 thanks for the PR!
A few quick questions:

Can you explain the scenario where you've committed a requirements.in file but not a requirements.txt file? I personally always considered it a best practice to commit both... that's kinda the point of generating a fully pinned requirements.txt file.
The file size limit is because for python we pull in any .txt file, and and only then we try to figure out if it’s a requirements file, because they can have any random name. So we wanted to minimize pulling in large docs files etc... Are you actually hitting the 200KB limit in your jobs? I'd be curious to see the repo if it's public--do you have a Job ID? If you are hitting the limit, then yes, we should raise it, but it'd be best to do that in a separate PR as the two issues here are orthogonal.
Both PR's need tests. If you need help figuring out how to write them give a shout and I'll try to help.

BTW, I noticed this is your first PR on GitHub, so congrats! 🥳 I still remember the first time I opened a PR for an open-source project, a little scary, but I was thrilled when it was merged.

It would be even better if the file size heuristic could be configurable, so that it would be possible to override the default size cap when it's not appropriate.

I was thinking that if we're going to make this configurable, it makes more sense to make the name of the manifest configurable, so that we don't have to make any guesses, fetch files that we don't need at all, or put any size limits on what we fetch.
We'd probably need to keep the current logic for backwards compatibility, though.

Hey @jeffwidman thanks for the quick reply and warm welcome!
Regarding your questions:

I have both requirements.in and requirements.txt files in the repo. Just in the case of an error (e.g., file size of requirements.txt is too big ;-)) it makes sense to "fall-back" to the requirements.in file. IMO, that additional check doesn't hurt much.
Yeah, I'm hitting the limit of the 200KB (that was the reason why I came across the issue above in the first place). Having this configurable as @dws mentioned would be ideal. For now, I can split up the PR, no problem.
Regarding unit tests, can you point to some examples / documentation?

Cheers

Hey @stulle123 thanks for splitting them out here.
For this one, the test should be relatively straightforward. Look in this file: https://github.com/dependabot/dependabot-core/blob/main/python/spec/dependabot/python/file_fetcher_spec.rb
I'd grep for "with only" and you'll see how the tests were written for other file types. Just need to add one saying "with only a requirements.in".
You can run the tests natively using these instructions,  but the easier way to avoid having to muck around with installing the proper ruby libraries locally is to use the docker image. Instructions for booting the image are here, and a few paragraphs in there's a section on running tests within the docker image.

Hey @jeffwidman just added the unit test! Cheers!

@stulle123 sorry to bother you, but looks like this code is failing a lint error about line too long, probably because we tidied up our Rubocop settings in https://github.com/dependabot/dependabot-core/pull/5588.
Do you mind fixing? Should be straightforward.
Also, while you're in there, can you squash to a single commit? that way the test + the change are located in the same commit for anyone in the future doing debugging via git blame.

Hey @jeffwidman Rubocop checks are green now. As you can see I had some troubles with the commit squashing, but I somehow managed.

authors: deivid-rodriguez dws jeffwidman stulle123


text:
Block network requests for tests

Explicitly specify tests that do network requests
Close #105

Self-review: Gram, add flags to skip network-required tests and check it again.

These improvements are project specific. Best decision for DepHell is to forbid connections for all tests and allow only for some of them. pytest-socket is designed to support both ways with accent on allowing for all and forbidding for some. So, I don't think I have anything to contribute.
Thank you for review :)

repo: dephell/dephell


text:
No termd utility present

installed via npm or build locally makes no difference, no termd command can be found

You need to install it globally
npm install -g termd

authors: dephraiim nkh

repo: dephraiim/termd


text:
🛑 Derailed Home is down

In 8940023, Derailed Home (https://derailed.one) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Derailed Home is back up in 6116cb4 after 325 days, 7 hours, 5 minutes.

repo: derailed-org/derailed-oss-status


text:
How can I switch the sounds?

How can I put my own sounds to the program? Thank you

+1

It is not designed to import generic sounds at the moment.
You can clone the repository, add sound files to the project resources and adjust the sound mapping/ resource mapping within the code. Then re-compile the source code.

authors: derdanielb lokize matheusfpinto


text:
Makefile: replace hardcoded paths with computed paths

This makes it easier to build in forks for pull requests; no need to modify the Makefile to build and test in fork.
This works for people developing Go in the usual style; it's not clear to me what the test environment is, but I guess I'll find out.

@dr2chase I don't think that this would be enough of a change, since every other import path in delve would need to be changed as well to point to the fork.
The way I work is I go get delve, then add a new remote to my fork but keep the sources under github.com/derekparker/delve and I haven't had any issues so far. Do you think it could work for your setup as well? (I'm not sure if there are any differences between environments).
Hope it helps.

Ugh, you're right, what was I thinking?
Never mind.

Maybe you were thinking of a future without the GOPATH? :D

repo: derekparker/delve


text:
Seems cannot be installed

$ sudo gem install screengif       # might need sudo
Password:
Building native extensions. This could take a while...
ERROR:  Error installing screengif:
	ERROR: Failed to build gem native extension.

    current directory: /usr/local/lib/ruby/gems/2.5.0/gems/rmagick-2.16.0/ext/RMagick
/usr/local/opt/ruby/bin/ruby -r ./siteconf20180913-55688-1tkobf3.rb extconf.rb
checking for clang... yes
checking for Magick-config... no
checking for pkg-config... yes
checking for outdated ImageMagick version (<= 6.4.9)... no
checking for presence of MagickWand API (ImageMagick version >= 6.9.0)... no
checking for Ruby version >= 1.8.5... yes
checking for stdint.h... yes
checking for sys/types.h... yes
checking for wand/MagickWand.h... no

Can't install RMagick 2.16.0. Can't find MagickWand.h.
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
	--with-opt-dir
	--with-opt-include
	--without-opt-include=${opt-dir}/include
	--with-opt-lib
	--without-opt-lib=${opt-dir}/lib
	--with-make-prog
	--without-make-prog
	--srcdir=.
	--curdir
	--ruby=/usr/local/Cellar/ruby/2.5.1/bin/$(RUBY_BASE_NAME)

To see why this extension failed to compile, please check the mkmf.log which can be found here:

  /usr/local/lib/ruby/gems/2.5.0/extensions/x86_64-darwin-16/2.5.0/rmagick-2.16.0/mkmf.log

extconf failed, exit code 1

Gem files will remain installed in /usr/local/lib/ruby/gems/2.5.0/gems/rmagick-2.16.0 for inspection.
Results logged to /usr/local/lib/ruby/gems/2.5.0/extensions/x86_64-darwin-16/2.5.0/rmagick-2.16.0/gem_make.out

ffmpeg imagemagick gifsicle pkg-config are all latest pretty much.

@chenrui333 See https://github.com/dergachev/screengif/issues/45#issuecomment-307609593

Other commands that may help:
brew install imagemagick@6
brew link --force imagemagick@6
gem install rmagick

sounds good, let me try it.

The command lines above works good for me, closing the issue now.

repo: dergachev/screengif


text:
Angular-SDK-Transition

Transition to Angular SDK from webjs.

@chris4490


text:
Revise the singular and plural forms of variables

Description
This PR renamed the PostMedia to Attachment in order to fix the wrong singular and plural forms of variables.
Closes #203.
Checklist

[x] Targeted PR against correct branch.
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[ ] Wrote integration tests (simulation & CLI).
[x] Updated the documentation.
[x] Added an entry to the CHANGELOG.md file.
[x] Re-reviewed Files changed in the Github PR explorer.

@bragaz looks like the docs links are not setup properly :thinking:

I'm fixing them rn

@bragaz conflicts should be resolved, then we should be good to go

authors: RiccardoM bragaz

repo: desmos-labs/desmos


text:
Trying to get in touch regarding a security issue

Hello 👋
I run a security community that finds and fixes vulnerabilities in OSS. A researcher (@sancho1952007) has found a potential issue, which I would be eager to share with you.
Could you add a SECURITY.md file with an e-mail address for me to send further details to? GitHub recommends a security policy to ensure issues are responsibly disclosed, and it would help direct researchers in the future.
Looking forward to hearing from you 👍
(cc @huntr-helper)

thanks for the message, @psmoros!
@brkp, could you please take care of this.

authors: abdelhai psmoros

repo: deta/space-cli


text:
Add -v shortcut for version flag

-v is a commonly used shortcut for --version in many cli tools.

I don't agree with this shortcut. -v means verbose in nearly all the command line apps.
Right now we don't have a verbose mode but there where some issues talking about it and so it's not crazy that at some point we will want to have it. So I'd keep the -v flag free for that reason and only use it if we implement the verbose mode.

authors: BraisGabin arturbosch

repo: detekt/detekt


text:
Support relative output paths

This addresses #2492 and a part of #3045.
Out of scope items

Actually integrate with SARIF in Github actions
Change the default value for the base path to be the project root
Move SARIF support from experimental to formal
Update docs about enabling SARIF support + Github actions
Update CodeSmell messages where the absolute path is used

Implementation
The implementation was done by putting the relative path and base path as user data of KtFile.
OutputReports read them through the paths stored in Location.
Test
In addition to adding tests in Spek, I also perform manual tests with a local repository.

I'm contemplating about adding more integration tests in this area of detekt

This PR definitely added some integration tests in DetektTaskDslTest.
However, if you indicate end-to-end tests, I only see DetektTaskIntegrationTest in the codebase. And there is no integration test written at the moment.
In my mind, such end-to-end tests should be a separate module or repo that applies detekt gradle plugin, runs against some kotlin code with violations, and validates the error can be reported. This does not exist today but I definitely can help sparkle the discussion

However, if you indicate end-to-end tests, I only see DetektTaskIntegrationTest in the codebase. And there is no integration test written at the moment.
In my mind, such end-to-end tests should be a separate module or repo that applies detekt gradle plugin, runs against some kotlin code with violations, and validates the error can be reported. This does not exist today but I definitely can help sparkle the discussion

Yes, I definitely meant end-to-end tests. Thanks for the hint. End-to-end tests are a separate topic and as you mentioned outside of the scope for this PR.

🤔 I didn't have time to tests it but if you add the workingDir the console report keeps reporting the absolute path. Right?
And, should we wait to merge #3320 before merging this? To ensure that we don't break compatibity.

I think #3320 is ready to go. I will handle the merge once that one is in.

Apologize for the numerous force-push. I was debugging a CI failure that is not reproducible on local.

Apologize for the numerous force-push. I was debugging a CI failure that is not reproducible on local.

There is a new problem that I encountered in this PR.
A) In https://github.com/detekt/detekt/pull/3319#discussion_r549045142, we are suggested to set the default relative path base to the project source dir
B) The implementation goes that the detekt gradle plugin will generate the extra args to invoke DetektCli, which means Main.kt need to be able to recognize the new parameter --report-base-path.
C) However, the tests using GradleRunner/gradle-testkit are actually not dependent on the local versions of detekt, but actually performs resolution through all the repositories.
D) This explains why I was able to pass the test locally because I ran ./gradlew publishToMavenLocal before ./gradlew :detekt-gradle-plugin:test. My maven local contains my change while when we run the pre-merge check on CI, publishToMavenLocal was not run.
So to unblock this PR, we can fix any one of the steps listed here:
A) By default,  we still remain the old absolute path behavior. The new gradle extension for reportBasePath remains empty if there is no provided value.
B) We create a PR to add --report-base-path parameter to CliArgs, release the next Detekt version to maven/jcenter, then merge in this PR.
C) I have been juggling with [testkit with classpath injection] (https://docs.gradle.org/current/userguide/test_kit.html#sub:test-kit-classpath-injection), but still cannot get it to work with the current setup. The most hopeful try is simply adding implementation(project(":detekt-cli")) to dependencies.
We should at least separate the GradleRunner/gradle-testkit tests into at least a separate Test task, more to be discussed in #3324
D) Run publishToMavenLocal in pre-merge-checks so that GradleRunner/gradle-testkit tests will run against the jar from maven local.
Among all the options,
A) is a reasonable choice.
C) #3324 is the correct approach but will block this PR for quite some time.
D) feels a short-term patch if #3324 is not resolved.
B) is our last straw if none of A/C/D are agreed and implemented.
Apologize for the long response. I am seeking thoughts from all the maintainers, especially @BraisGabin since A) is per his request.

There is a new problem that I encountered in this PR.
A) In https://github.com/detekt/detekt/pull/3319#discussion_r549045142, we are suggested to set the default relative path base to the project source dir
B) The implementation goes that the detekt gradle plugin will generate the extra args to invoke DetektCli, which means Main.kt need to be able to recognize the new parameter --report-base-path.
C) However, the tests using GradleRunner/gradle-testkit are actually not dependent on the local versions of detekt, but actually performs resolution through all the repositories.
D) This explains why I was able to pass the test locally because I ran ./gradlew publishToMavenLocal before ./gradlew :detekt-gradle-plugin:test. My maven local contains my change while when we run the pre-merge check on CI, publishToMavenLocal was not run.
So to unblock this PR, we can fix any one of the steps listed here:
A) By default,  we still remain the old absolute path behavior. The new gradle extension for reportBasePath remains empty if there is no provided value.
B) We create a PR to add --report-base-path parameter to CliArgs, release the next Detekt version to maven/jcenter, then merge in this PR.
C) I have been juggling with [testkit with classpath injection] (https://docs.gradle.org/current/userguide/test_kit.html#sub:test-kit-classpath-injection), but still cannot get it to work with the current setup. The most hopeful try is simply adding implementation(project(":detekt-cli")) to dependencies.
We should at least separate the GradleRunner/gradle-testkit tests into at least a separate Test task, more to be discussed in #3324
D) Run publishToMavenLocal in pre-merge-checks so that GradleRunner/gradle-testkit tests will run against the jar from maven local.
Among all the options,
A) is a reasonable choice.
C) #3324 is the correct approach but will block this PR for quite some time.
D) feels a short-term patch if #3324 is not resolved.
B) is our last straw if none of A/C/D are agreed and implemented.
Apologize for the long response. I am seeking thoughts from all the maintainers, especially @BraisGabin since A) is per his request.

Thanks for the reasearch and the detailed report!
Agree with the option A). If the default value adds to much complexity we can merge this witout it and open an issue so we can find the best option to add it. What do you think?
We can add it in the next release if that make the things easier. We could even use a RC version.

Thanks for the reasearch and the detailed report!
Agree with the option A). If the default value adds to much complexity we can merge this witout it and open an issue so we can find the best option to add it. What do you think?
We can add it in the next release if that make the things easier. We could even use a RC version.

If the default value adds to much complexity we can merge this witout it and open an issue so we can find the best option to add it. What do you think?

It sounds like we are on the same page. What I probably need to do next is to prototype #3324. Since that would be impacting future changes and testing for detekt-gradle-plugin.

If the default value adds to much complexity we can merge this witout it and open an issue so we can find the best option to add it. What do you think?

It sounds like we are on the same page. What I probably need to do next is to prototype #3324. Since that would be impacting future changes and testing for detekt-gradle-plugin.

This is good to go for me. My last concern (sorry the PR is big and each time I review it I realiced different things) is the cli flag name: --report-base-path. Right now we use the relative paths just for reporting but this feature is not just about that so, maybe, we could rename it to something more generic as --base-path. What do you think? Any way, this is not a blocking topic.

I don't know other use cases of base path. The input paths can be both absolute and relative based on user.dir, and internally we are always using absolute paths. If we want to expand this idea, we could choose to add a different option specifically.

This is good to go for me. My last concern (sorry the PR is big and each time I review it I realiced different things) is the cli flag name: --report-base-path. Right now we use the relative paths just for reporting but this feature is not just about that so, maybe, we could rename it to something more generic as --base-path. What do you think? Any way, this is not a blocking topic.

I don't know other use cases of base path. The input paths can be both absolute and relative based on user.dir, and internally we are always using absolute paths. If we want to expand this idea, we could choose to add a different option specifically.

This is good to go for me. My last concern (sorry the PR is big and each time I review it I realiced different things) is the cli flag name: --report-base-path. Right now we use the relative paths just for reporting but this feature is not just about that so, maybe, we could rename it to something more generic as --base-path. What do you think? Any way, this is not a blocking topic.

I don't know other use cases of base path. The input paths can be both absolute and relative based on user.dir, and internally we are always using absolute paths. If we want to expand this idea, we could choose to add a different option specifically.

Posted in our slack channel: https://kotlinlang.slack.com/archives/C88E12QH4/p1609854726084000?thread_ts=1609854726.084000&cid=C88E12QH4
A user asking exactly for this feature and it's not related with the reports. So, probably, we should rename the flag.

This is good to go for me. My last concern (sorry the PR is big and each time I review it I realiced different things) is the cli flag name: --report-base-path. Right now we use the relative paths just for reporting but this feature is not just about that so, maybe, we could rename it to something more generic as --base-path. What do you think? Any way, this is not a blocking topic.

I don't know other use cases of base path. The input paths can be both absolute and relative based on user.dir, and internally we are always using absolute paths. If we want to expand this idea, we could choose to add a different option specifically.

Posted in our slack channel: https://kotlinlang.slack.com/archives/C88E12QH4/p1609854726084000?thread_ts=1609854726.084000&cid=C88E12QH4
A user asking exactly for this feature and it's not related with the reports. So, probably, we should rename the flag.

A user asking exactly for this feature and it's not related with the reports. So, probably, we should rename the flag.

That user was me 😀 To clarify, I need to write a custom rule that checks for a project's naming conventions based on the relative path of source files, where the base is the Gradle root project directory. So my assumption would be that after this PR is merged, a call to the PsiFile.relativePath() extension function from the io.github.detekt.psi package would return exactly that relative path when using the detekt plugin for Gradle. Right now, a call to PsiFile.relativePath() just returns the file name (and extension) without any path.
Is my assumption / expectation about the goal of this PR correct?

A user asking exactly for this feature and it's not related with the reports. So, probably, we should rename the flag.

That user was me 😀 To clarify, I need to write a custom rule that checks for a project's naming conventions based on the relative path of source files, where the base is the Gradle root project directory. So my assumption would be that after this PR is merged, a call to the PsiFile.relativePath() extension function from the io.github.detekt.psi package would return exactly that relative path when using the detekt plugin for Gradle. Right now, a call to PsiFile.relativePath() just returns the file name (and extension) without any path.
Is my assumption / expectation about the goal of this PR correct?

Yes, they are. You will need one extra line of configuration in your gradle because of this https://github.com/detekt/detekt/pull/3319#issuecomment-753389072 that we decided that is out of the scope of this PR (but it will be implemented later). But you would be able to get the relative path using a extension function over the KtFile.

Yes, they are. You will need one extra line of configuration in your gradle because of this https://github.com/detekt/detekt/pull/3319#issuecomment-753389072 that we decided that is out of the scope of this PR (but it will be implemented later). But you would be able to get the relative path using a extension function over the KtFile.

authors: BraisGabin chao2zhang schalkms sschuberth


text:
🛑 BBDD Mongo is down

In 9aa032a, BBDD Mongo (https://api.okticket.es/v2/public/api/monitor/mongodb) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BBDD Mongo is back up in 02af316.

repo: dev-okticket/status


text:
postgres-data is missing in .gitignore

Hey 👋
thank you for this great template. I've set it up locally and it just works!
I noticed postgres-data is missing in the .gitignore and the whole DB was commited on my side. Is this on purpose?

Hello @simulieren thanks you for reaching on here!
I'm not sure if I understand at all the Issue!
Guess postgres-data is a file / folder? Didn't noticed it on my side working with Postgres, or not sure i'f im missing something! Because in that case for sure should be added into .gitignore!
Could you please show me some code / image? Or do a Pull Request with the fix?
I'm XO#9732 in Remix Discord in case you wanna reach me on there.
Thanks you!

I've updated remix.init. Now you should not get remix.init folder anymore into your workspace, and the template should not give an error after initializing, complaining about database.
Can you do a fresh npx create-remix@latest --template dev-xo/stripe-stack? Set your database and notice me how it goes!
Still need to add postgrtes-data to .gitignore, but you helped me figure out remix.init folder wasn't removing properly on Postgres version. Thanks you!

@dev-xo I've created a quick PR with the fix. Please feel free to change the PR up, if you feel the need to. 😄
The postgres-data folder is created when starting a local PostgreSQL server with the docker-compose.yml that comes with the template. So the folder would only appear, if you develop with a local DB.
To make it work after a shutdown of the container, I had to also alter the docker-compose.yml to this configuration:
version: '3.7'
services:
  postgres:
    image: postgres:latest
    restart: always
    environment:
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: postgres
      POSTGRES_DB: postgres
      PGDATA: /var/lib/postgresql/data/pgdata
    ports:
      - '5432:5432'
    volumes:
      - ./postgresql.conf:/var/lib/postgresql/data/postgresql.conf
      - ./pg-data:/var/lib/postgresql/data/pgdata

volumes:
  pg-data:

Yeah got you @simulieren !
My issue with this is that, I wasn't using Docker to initialize my database.
So I never been aware of a postgres-data folder. :)
Not sure if I should update also the docker-compose.yml file, or document it into the Docs.
Usually Github Actions or deploying the template, never had an Issue with it, so yeah.
Thanks you for the PR #32 and for noticing me about this!
Have you tried to initialize the template again? As said before, remix.init folder should not be present anymore, and you should not get any error after template has been initialized.
(Still have to configure it manually for the Postgres version)
All right, thanks you for reaching on here and for noticing me about this!
Any other question / issue / whatever, feel free to ask!

authors: dev-xo simulieren

repo: dev-xo/stripe-stack


text:
Prefer npm cmake/ninja instances instead of system instances

Currently, this package is hardcoded to prefer system installs of cmake/ninja instead of those installed into node_modules.
Consider defaulting to the node_modules installation, and allow configurable path to a system installation. E.g., cmake-path="/path/to/cmake" or cmake-system-path="true" to search PATH first before looking at cmake-path then node_modules in that order.
Re: downloading:

On NPM install time, don't download anything nor print anything on NPM
On NPM build script, if CMake/Ninja doesn't exist on PATH or NPMRC, then download it to module.

The bug is fixed, but the behavior still needs improvement.

This may depend on a couple long-term goals which are to make CMake and Ninja run on WASM.
The current behavior (prefer system installs instead of NPM installs) is fine, albeit not ideal. The issue with supporting NPM-first priority is that CMake takes a while to download on NPM.

This may depend on a couple long-term goals which are to make CMake and Ninja run on WASM.
The current behavior (prefer system installs instead of NPM installs) is fine, albeit not ideal. The issue with supporting NPM-first priority is that CMake takes a while to download on NPM.

repo: devappd/emscripten-build-npm


text:
Add send and recv parameters to New-NSLBMonitor

Additional parameters, send and recv, needed when creating a new monitor.
Expected Behavior
Should be able to pass in optional send and recv parameters.
Current Behavior
New-NSLBMonitor function does not allow for these parameters.

Fixed in #50

authors: devblackops rokett

repo: devblackops/NetScaler