text:
Error: you need to provide a host and port to test.

Additional info
Apologies in advance for being so verbose in my explanation. I appreciate your time to review this issue knowing that you must be very busy working on more critical issues.
Describe the bug
Unfortunately, I was unable to get the fullstack swarm to start as expected. (pingidentity-devops-getting-started/12-docker-swarm/fullstack.yaml).
Below is what I observed, and the steps I took to get the fullstack swarm to start as expected. I'm still not sure exactly why my solution worked, but it did, and I am stoked. :)
I discovered the following error in the service logs for the pingaccess, pingfederate-admin, and pingfederate swarm services (docker service logs -f ${service-name})
Example error from fullstack_pingfederate service logs:
fullstack_pingfederate.1.zfaznu425nhx@node1    | ----- Starting hook: ./bootstrap.sh
fullstack_pingfederate.1.zfaznu425nhx@node1    | ### Bootstrap
fullstack_pingfederate.1.zfaznu425nhx@node1    | ----- Starting hook: /opt/entrypoint.sh
fullstack_pingfederate.1.zfaznu425nhx@node1    | Command: sh -c wait-for pingfederate-admin:9999 -t 600 -- entrypoint.sh start-server
fullstack_pingfederate.1.zfaznu425nhx@node1    | ##################################################################################
fullstack_pingfederate.1.zfaznu425nhx@node1    | #    Ping Identity DevOps Docker Image
fullstack_pingfederate.1.zfaznu425nhx@node1    | #     IMAGE_VERSION: pingfederate-alpine-10.0.0-200126-9f12
fullstack_pingfederate.1.zfaznu425nhx@node1    | #     IMAGE_GIT_REV: 9f120fd51f74475c6bf5d6f741a92981be78fc55
fullstack_pingfederate.1.zfaznu425nhx@node1    | #           STARTED: Fri Jan 31 10:30:52 UTC 2020
fullstack_pingfederate.1.zfaznu425nhx@node1    | #          HOSTNAME: e114761ebc8f
fullstack_pingfederate.1.zfaznu425nhx@node1    | #        DOMAINNAME:
fullstack_pingfederate.1.zfaznu425nhx@node1    | ##################################################################################
fullstack_pingfederate.1.zfaznu425nhx@node1    | Running command: sh -c wait-for pingfederate-admin:9999 -t 600 -- entrypoint.sh start-server
fullstack_pingfederate.1.zfaznu425nhx@node1    | Error: you need to provide a host and port to test.
fullstack_pingfederate.1.zfaznu425nhx@node1    | Usage:
fullstack_pingfederate.1.zfaznu425nhx@node1    |    host:port [-t timeout] [-- command args]
fullstack_pingfederate.1.zfaznu425nhx@node1    |   -q | --quiet                        Do not output any status messages
fullstack_pingfederate.1.zfaznu425nhx@node1    |   -t TIMEOUT | --timeout=timeout      Timeout in seconds, zero for no timeout
fullstack_pingfederate.1.zfaznu425nhx@node1    |   -- COMMAND ARGS                     Execute command with args after the test finishes

Troubleshooting
I ended-up commenting line 29 of 'fullstack.yaml' so that I could get the pingfederate-admin continer to simply start. I also added a published port of 22 so that I could "SSH" into the container and test the /opt/wait-for script, which worked as expected from the container interactive shell.
Next, I double-checked the Docker Compose documentation and tested using a different syntax for the service command override, which didn't fix the issue.
https://docs.docker.com/compose/compose-file/#command
command

Override the default command.

command: bundle exec thin -p 3000

The command can also be a list, in a manner similar to dockerfile:

command: ["bundle", "exec", "thin", "-p", "3000"]

Fix
Keeping the alternate command syntax, I next tried modifying the command to use the absolute path to the script, instead of invoking the script with 'sh -c'. With the below modifications to fullstack.yaml, I was able to successfully start the swarm. :)
line 7 original (generates similar error as above):
command: ["sh", "-c", "wait-for pingfederate:9031 -t 700 -- entrypoint.sh start-server"]

line 7 changed (works as expected):
command: /opt/wait-for pingfederate:9031 -t 700 -- entrypoint.sh start-server

line 29 original (generates similar error as above):
command: ["sh", "-c", "wait-for pingdirectory:389 -t 300 -- entrypoint.sh start-server"]

line 29 changed (works as expected):
command: /opt/wait-for pingdirectory:389 -t 300 -- entrypoint.sh start-server

line 48 original (generates similar error as above):
command: ["sh", "-c", "wait-for pingfederate-admin:9999 -t 600 -- entrypoint.sh start-server"]

line 48 changed (works as expected):
command: /opt/wait-for pingfederate-admin:9999 -t 600 -- entrypoint.sh start-server

Example success from fullstack_pingaccess service logs:
~/projects/pingidentity-devops-getting-started/12-docker-swarm$ docker service logs -f fullstack_pingaccess
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | ----- Starting hook: ./bootstrap.sh
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | ### Bootstrap
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | ----- Starting hook: /opt/entrypoint.sh
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | Command: /opt/wait-for pingfederate:9031 -t 700 -- entrypoint.sh start-server
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | ##################################################################################
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | #    Ping Identity DevOps Docker Image
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | #     IMAGE_VERSION: pingaccess-alpine-6.0.0-200126-9f12
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | #     IMAGE_GIT_REV: 9f120fd51f74475c6bf5d6f741a92981be78fc55
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | #           STARTED: Fri Jan 31 12:06:22 UTC 2020
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | #          HOSTNAME: 66a8c9659a89
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | #        DOMAINNAME:
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | ##################################################################################
fullstack_pingaccess.1.l8vcjwx57xb9@node1    | Running command: /opt/wait-for pingfederate:9031 -t 700 -- entrypoint.sh start-server
...
...
fullstack_pingaccess.1.pl2n1k4jphfw@node2    | 2020-01-31T12:15:05,953  INFO [] com.pingidentity.pa.cli.RouterCLI - PingAccess started in 30s:214ms

/projects/pingidentity-devops-getting-started/12-docker-swarm$ docker service ls
ID                  NAME                           MODE                REPLICAS            IMAGE                               PORTS
h4rb1wl1phrh        fullstack_pingaccess           replicated          1/1                 pingidentity/pingaccess:edge        *:443->443/tcp, *:9000->9000/tcp
7f7s7g4yt64v        fullstack_pingdataconsole      replicated          1/1                 pingidentity/pingdataconsole:edge   *:8443->8443/tcp
pskuz8cndc4z        fullstack_pingdirectory        replicated          1/1                 pingidentity/pingdirectory:edge     *:1443->443/tcp, *:1636->636/tcp
tdl528pb94i7        fullstack_pingfederate         replicated          1/1                 pingidentity/pingfederate:edge      *:9031->9031/tcp
p41ew8jtwl2m        fullstack_pingfederate-admin   replicated          1/1                 pingidentity/pingfederate:edge      *:9999->9999/tcp

Environment:

Github Repo: pingidentity-devops-getting-started/12-docker-swarm/fullstack.yaml
Docker Container: n/a
Cloud Environment: 3x CentOs 7.7.1908 Docker Swarm worker node VMs that I manage from my Linux Mint dev VM, which is the Docker Swarm manager.

Additional info
After discovering Ping Identity DevOps, I realized that I wanted/needed to learn Docker. I started learning Docker in December, 2019 by watching a really good Udemy course by Bret Fisher, a Docker Captain (https://www.bretfisher.com/). I am about 50% through the course, which last covered Docker Swarm Mode, and next up is Kubernetes (excited :) ).
I say all that so you will hopefully understand that I may not be using the most correct terms when I describe the issue I experienced, and also to say thank you for creating such awesome documentation! I simply cannot wait until we can hopefully start managing our PingFederate and PingAccess services using DevOps practices, instead of the very manual, error-prone method we use today to manage our considerably-sized clusters.
I've finally learned enough about Docker to start testing with Ping Identity products on my home lab where I have 3x CentOs 7.7.1908 Docker Swarm worker node VMs that I manage from my Linux Mint dev VM, which is the Docker Swarm manager.
Right now I am primarily focused on learning Swarm because, as it was interpreted by me from Bret Fisher's course, a small team that is new to DevOps using Docker will most likely be successful moving to Swarm first, since Swarm will cover most use-cases (80-20 rule), and then, things like Kubernetes, Docker Enterprise UCP, etc. can be added later, as the DevOps practices of the team matures.

Hello @arnaudlacour,
I appreciate your comments about the issue I created, and your prompt response. :)
Thank you for commit d1d42b9deb73ed8732b9763a0eef7db9a4c0dc9f which looks like it addresses the issue. :)
Have a great weekend, sir!


text:
[+Here's how To WatcH! BOXING] Jake Paul vs Mike Tyson Live Streams [PPV] and TV Channel

Mike Tyson vs. Jake Paul fight start time: Where to watch, live stream online, fight card, Netflix price
Everything you need to know to watch Friday's unprecedented fight
🅻🅸🆅🅴🔴▶ CLICK HERE TO WATCH LIVE ONLINE
🆆🅰🆃🅲🅷🔴▶ CLICK HERE TO LIVE STREAM
The biggest combat sports spectacle of 2024 is inbound. "Iron" Mike Tyson boxes professionally for the first time in nearly two decades against Jake Paul, a controversial boxer with a massive youth edge.
Paul vs. Tyson should draw more eyes than any combat sports event this year. This is a credit to the headliners' wide reach, but most importantly, the fight will stream to Netflix's reported 282 million subscribers at no extra cost. It's a puzzling fight that raises the question: how competitive will Tyson, 58, be against an athletic opponent 31 years his junior?
"Yeah, it's cute. I fear no man. So I want him to be that old savage Mike," Paul said. "He says he's going to kill me. I'm ready. I want that killer. I want the hardest match possible Friday night, and I want there to be no excuses from everyone at home when I knock him out."
Things got heated at the ceremonial weigh ins on Thursday when after stepping off the scale and preparing for the final faceoff, Tyson slapped Paul square across the face before the two were separated. An enraged Tyson stormed off the stage as Paul continued to troll the living legend.
The action gets underway on Netflix at 8 p.m. ET. The full fight card with odds and complete viewing information is listed below.
Where to watch Mike Tyson vs. Jake Paul
Date: Nov. 15
Location: AT&T Stadium -- Arlington, Texas
Start time: 8 p.m. ET (Main card)
Where to watch: Netflix (subscription required, plans begin at $6.99)
Tyson vs. Paul fight card, odds
Favorite Underdog Weight class
Jake Paul -200 Mike Tyson +160 Heavyweights
Katie Taylor (c) -115 Amanda Serrano -115 Undisputed junior welterweight title
Mario Barrios (c) -1400 Abel Ramos +800 WBC welterweight title
Neeraj Goyat -475 Whindersson Nunes +330 Middleweights
Who wins Mike Tyson vs. Jake Paul on November 15, and which Paul vs. Tyson props should you be all over? Visit SportsLine now to see Brandon Wise's best bets for the Nov. 15 bout, all from the CBS combat sports specialist who just called Paul's first-round win in March, and find out.
Mike Tyson vs. Jake Paul fight start time: Where to watch, live stream online, fight card, Netflix price
Everything you need to know to watch Friday's unprecedented fight
The biggest combat sports spectacle of 2024 is inbound. "Iron" Mike Tyson boxes professionally for the first time in nearly two decades against Jake Paul, a controversial boxer with a massive youth edge.
Paul vs. Tyson should draw more eyes than any combat sports event this year. This is a credit to the headliners' wide reach, but most importantly, the fight will stream to Netflix's reported 282 million subscribers at no extra cost. It's a puzzling fight that raises the question: how competitive will Tyson, 58, be against an athletic opponent 31 years his junior?
"Yeah, it's cute. I fear no man. So I want him to be that old savage Mike," Paul said. "He says he's going to kill me. I'm ready. I want that killer. I want the hardest match possible Friday night, and I want there to be no excuses from everyone at home when I knock him out."
Things got heated at the ceremonial weigh ins on Thursday when after stepping off the scale and preparing for the final faceoff, Tyson slapped Paul square across the face before the two were separated. An enraged Tyson stormed off the stage as Paul continued to troll the living legend.
The action gets underway on Netflix at 8 p.m. ET. The full fight card with odds and complete viewing information is listed below.
Where to watch Mike Tyson vs. Jake Paul
Date: Nov. 15
Location: AT&T Stadium -- Arlington, Texas
Start time: 8 p.m. ET (Main card)
Where to watch: Netflix (subscription required, plans begin at $6.99)
Tyson vs. Paul fight card, odds
Favorite Underdog Weight class
Jake Paul -200 Mike Tyson +160 Heavyweights
Katie Taylor (c) -115 Amanda Serrano -115 Undisputed junior welterweight title
Mario Barrios (c) -1400 Abel Ramos +800 WBC welterweight title
Neeraj Goyat -475 Whindersson Nunes +330 Middleweights
Zzzxzx..3233..33333.........

vcvcv

gf fgf

source: gharchive/issue

repo: pinokiocomputer/pinokio

license: MIT

license_type: permissive

license_source: github-api


text:
fun-keyword-spacing is redundant with keyword-spacing

Maybe fun-keyword-spacing should be removed, and parameters could be added to keyword-spacing to include or exclude specific keywords?

Those rules can be merged. Except that it is one rule less, there does not seem to be much other benefits. Also, there are more spacing rules than this.
So what would be the benefit from your perspective?

In my opinion, its just about the benefits of removing redundancy. I haven't yet taken a close look at most of the rules, but in general I think removing redundancy between rules is good?

Yes, and no. Given two rules that have no overlap. Combining those rules into one rule means less flexibility for users who want to disable only one of the rules, as they then can only disable the combined rules. Given two rules where one of the rules is a subset of the other rule it would also result in loss of flexibility as the user can no longer keep the first rule enabled while disabling the rule with which it overlaps.

Removing redundancy might lead to performance improvements

Of course it is more performant to have less rules. But one should never optimize before measuring that this is a performance bottleneck.

but more importantly I think it just makes the library easier and more organized for maintainers and users.

Yes and no. Less rules is of course more easy. But if the rules get more complex then the benefit is quickly lost.
In this particular example I see no gains (reuse of code) by combining fun-keyword-spacing and keyword-spacing. It would also not be a big deal to combine them as the complexity of the combined rule is still manageable. Combining them could cause some problems for the very unlikely case that some user has disabled the fun-keyword-spacing.

This is a way how it could be solved, but it is not the way we should do it.
Adding configuration options is a kind of last resort in Ktlint. The more options ktlint has, the more it leads to bikeshedding. Also, it has been proven to be hard to maintain (e.g. more difficult to test), it is hard for users to understand what possible options are, and it is more difficult to document. User often request additional configuration options for their use case, and for this reason I have add this FAQ.
For this particular case, I can not think of any good reasons why a configuration option would be of value. Why should it be supported that user can choose for which keyword the standard spacing is used or not.

But according to this logic, the existence of fun-keyword-spacing seems unjustified. Am I missing something? What reason would anyone have to want different spacings around fun but not similar keywords like val or var?
You mentioned above that removing flexibility for users is undesirable, but now you are saying that bikeshedding and overly complicated configuration is undersirable. It seems that these two design principles are conflicting. But if the conclusion is to just leave it as is, with a special spacing rule for fun but not for other keywords, that doesn't seem right either as it is arbitrarily giving special flexibility for one keyword.

The fun-keyword-spacing was created while developing the function-signature rule. When that rule got more and more complicated, I extracted some logic into separate rules. When I created the fun-keyword-spacing rule, I did not notice that there was already a rule keyword-spacing. If I would have notice that, I probably would have extended that rule. But now the rule has been published, it has given users the flexibility to disable only one of the rules.
A a general design principle, more smaller rules give users more flexibility. But you're right that using that flexibility leads to bikeshedding. Enabling/disabling rules however is generic for all rules. Users do not need to lookup documentation once they know the principle. When introducing configuration parameters, users do need to read the documentation to become aware of them, and how to use them.

I also am surprised that you don't see the potential to merge rules in a way that reuses code.

I have investigated the merge of the fun-keyword-spacing and keyword-spacing based on your earlier remarks, and did not see how merging would lead to reuse of code.

repo: pinterest/ktlint


text:
Problems with Line-Endings

Expected Behavior
We are a small Team of Devs with different OS (Linux, Mac, Windows) so we all have systems with different line endings.
Since we switched from 0.47.1 to ktlint-cli 1.3.0 the tool touches the line endings. I have searched for an option that just says: keep the line-endings as they are. But only the following are supported in the .editorconfig:
end_of_line = lf
end_of_line = crlf
end_of_line = cr
So what we have done is to create an .editorconfig_win/.editorconfig (as default for linux) /.editorconfig_mac with identical rulesets but differet eol.
The next problem occured: It seems if i run ktlint and if it finds any ".editorconfig" the settings of this file overwrites any passed editorconfig argument.
=>

If i run
ktlint --editorconfig=.editorconfig_win -F
on my windows machine, all the files get LF ending instead of CRLF.
As a workaround every Dev just sets temporaly the correct line ending in the .editorconfig for formatting. This is a risk, they have to take care not to check in their eol-setting...

We need a "end_of_line = keep it " option
If a default .editorconfig file is found in the CWD it should not overwrite settings of a argument-passed editorconfig

Your Environment

Version of ktlint used: 1.3.0
Relevant parts of the .editorconfig settings: end_of_line = cr/crlf/lf
Operating System and version: Multiple Windows 11/10, Ubuntu 22.4 and some macos quatsch (i dont like macos :))

Duplicate of #2747


text:
[pinterest-only] only update deploy priority once in post deploy

this is for pinterest internal ngapp2 deploy only, we use finish_message_flag to check if we have already updated deploy priority or not.
@sbaogang @yujunglo

looks good to me. thanks

source: gharchive/pull-request

authors: jinruh yujunglo

repo: pinterest/teletraan

license_source: bigquery


text:
Initial Implementation of Basic API

Issue to track development of a basic API.

Hi @2devnull,
You may be interested in this alternative approach I took: https://github.com/pioto/thermostat
The key classes to look at:

Tstat - this represents the /tstat endpoint. Using Lombok and Jackson annotations makes this really succinct. Most of the numeric enum-like things are mapped to Java enums, and the booleans are mapped to Boolean types. (e.g. Tmode)
ThermostatServiceImpl - this class uses Spring's RestTemplate to make the API calls nice and clean, with all the serializiation/deserialization of the JSON request/response objects being transparent. There's even some caching added so that we don't hit the poor little thermostat's controller too hard if you start mashing refresh or something in your browser

repo: pioto/radio-thermostat


text:
csv output

this works really well.
god knows how you ported the ruby data across. hopefully it was copy only :)
anyway i was thinking that it would be useful to have a dumper that can output all data in CSV format.
then can import into a DB.
I would extend the generator to output csv. Seems like the smart place to do it.
use case is that some people like me :) need the lookup data to be in a DB.
SO we then have countries output as golang code and csv data. take your pick..
what do you think ?

I think this is not the purpose, the competence of this package. Maybe another package can do this. It can use this package API and generate a CSV file.
ps: to import data we need only to copy some files from the Ruby gem and run a go generator.

repo: pioz/countries


text:
Use a newer docker image

To apply Improve Terraform plan result handling #5177, change the docker image to a newer one.

I checked the commit hash on the link.
https://github.com/pipe-cd/pipecd/pkgs/container/actions-plan-preview/268616488?tag=v0.48.0-118-g25e9a71

authors: Warashi ffjlabo

repo: pipe-cd/actions-plan-preview


text:
Add missing close redis connection in ops

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/lgtm

Nice catch!
/approve

authors: khanhtc1202 nakabonne nghialv

repo: pipe-cd/pipe


text:
Refactor constants in ts by moving them to separate files

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/approve

authors: cakecatz nghialv


text:
Warning  FailedScheduling   (x7 over 26s)  default-scheduler  0/5 nodes are available: 5 Insufficient cpu

Hello,
I have setup a k8s cluster with the following:
$ kops validate cluster
Using cluster from kubectl context: es.k8s.local

Validating cluster es.k8s.local

INSTANCE GROUPS
NAME                    ROLE    MACHINETYPE     MIN     MAX     SUBNETS
bastions                Bastion t2.micro        1       1       utility-eu-west-1a
data                    Node    t2.medium       2       2       eu-west-1a
master-eu-west-1a       Master  m3.medium       1       1       eu-west-1a
nodes                   Node    t2.medium       2       2       eu-west-1a

NODE STATUS
NAME                                            ROLE    READY
ip-172-20-39-51.eu-west-1.compute.internal      node    True
ip-172-20-40-39.eu-west-1.compute.internal      node    True
ip-172-20-43-105.eu-west-1.compute.internal     node    True
ip-172-20-44-5.eu-west-1.compute.internal       node    True
ip-172-20-62-224.eu-west-1.compute.internal     master  True

Your cluster es.k8s.local is ready

so I have one master, 2 nodes and 2 data nodes
when I try to add the es-client, this fails, with the following error:
$ kubectl describe po es-client-7b59bd6d64-vmvv5
Name:           es-client-7b59bd6d64-vmvv5
Namespace:      default
Node:           <none>
Labels:         component=elasticsearch
                pod-template-hash=3615682820
                role=client
Annotations:    kubernetes.io/limit-ranger=LimitRanger plugin set: cpu request for init container init-sysctl
Status:         Pending
IP:
Controlled By:  ReplicaSet/es-client-7b59bd6d64
Init Containers:
  init-sysctl:
    Image:  busybox:1.27.2
    Port:   <none>
    Command:
      sysctl
      -w
      vm.max_map_count=262144
    Requests:
      cpu:        100m
    Environment:  <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-nb2zw (ro)
Containers:
  es-client:
    Image:  quay.io/pires/docker-elasticsearch-kubernetes:6.2.2_1
    Ports:  9200/TCP, 9300/TCP
    Limits:
      cpu:  2
    Requests:
      cpu:      2
    Liveness:   tcp-socket :transport delay=0s timeout=1s period=10s #success=1 #failure=3
    Readiness:  http-get http://:http/_cluster/health delay=20s timeout=5s period=10s #success=1 #failure=3
    Environment:
      NAMESPACE:     default (v1:metadata.namespace)
      NODE_NAME:     es-client-7b59bd6d64-vmvv5 (v1:metadata.name)
      CLUSTER_NAME:  es
      NODE_MASTER:   false
      NODE_DATA:     false
      HTTP_ENABLE:   true
      ES_JAVA_OPTS:  -Xms256m -Xmx256m
      NETWORK_HOST:  _site_,_lo_
      PROCESSORS:    2 (limits.cpu)
    Mounts:
      /data from storage (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-nb2zw (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  storage:
    Type:    EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
  default-token-nb2zw:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-nb2zw
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s

Events:
  Type     Reason            Age                      From               Message
  ----     ------            ----                     ----               -------
  Warning  FailedScheduling  <invalid> (x13 over 2m)  default-scheduler  0/5 nodes are available: 5 Insufficient cpu.

what am i missing?

0/5 nodes are available: 5 Insufficient cpu. you don't have enough CPU available in your Kubernetes nodes.

@pires what ec2 node size would you recommend for a test setup?

Honestly, I don't have an answer for that :(

Hi @nkhine, I think you should start with the t2.large for the nodes and scale it out depending of your consumption.

You can exec cat /proc/cpuinfo to check cpu.
May be your machine's Insufficient cpu, Because :

authors: ameukam nkhine pires yangwenmai

repo: pires/kubernetes-elasticsearch-cluster


text:
How to prevent types from overflowing?

🤔 Question
ts-toolbelt has been a revelation for me. I always felt typescript had great potential but fell short on tooling for its type system and ts-toolbelt delivers on that. As a result I've been more adventurous with my type programming, so thank you!
As a result of my newfound adventurousness, I find myself coming up against performance problems in type computation, resulting in poor intellisense and compiler errors such as: Type instantiation is excessively deep and possibly infinite...
Describe your question
You must have had to battle with these issues developing ts-toolbelt. Can you share with us some of your experience on how you diagnosed and solved type computation performance issues?
Specifically, I'm interested in any tools, techniques or rules of thumb you might be able to share.
Search tags, topics
typescript, type resolution, type computation, performance, type debugging

Usually  you don't hit these kind of errors with simple types. But this is likely to happen with recursive types, which are not officially supported type TypeScript but by ts-toolbelt instead.
TypeScript is smart and it forces you to keep a type count before it tells you Type instantiation is excessively deep and possibly infinite. This should force you to:

Keep your types short and neat
Keep your type count under 50
Prevent infinite loop for recursive types

Since recursive types are not directly supported by ts, it is your responsibility to make sure that your type won't overflow. In other words, it MUST have a proper terminating condition. This should be tested by you. The toolbelt enables you to do tests, check this out on the README.
If your (recursive) type overflows, it can be because:

Of no terminating condition
Type is too complex for TypeScript

It is important to note that the type system was not designed to do scripting.
However, like you pointed out, there is a need for a more modular type system.
It's is good to (always) ask yourself if the computation is worth it, or could it be narrowed down to something simpler? If not, then use ts-toolbelt.
So, a good rule of the thumb is: "are there more than 50 instructions within my type?"
There is one trick that I use for the recursive types described here https://github.com/pirix-gh/ts-toolbelt/issues/5. This one will prevent TS from evaluating heavy recursive types immediately, especially when they are combined together and prevent that instantiation error. You can check this out in the codebase, look for extends infer X.

Wow! Thanks for the write up!
I understand the 50 instruction limit okay, it makes sense... in my case my types are complex, involving higher-kinded types but at least in theory they shouldn't be recursive.
The difficulty for me is tracing typescript's computation logic... it COULD be that I've introduced a recursion somewhere unexpectedly... but how can I discover this?
Also, what counts as a single 'instruction'...? e.g. is it a single type declaration, or a branch of logic in a type alias?
And is there a way I can evaluate the 'instruction count' for a particular type's instantiation?
Also, that defer syntax looks extremely useful. It would be useful to have a 'recipe book' of these kind of manipulation that force the typescript compiler to do something 'out of the ordinary'... Computer, Clean and Cast are good example also.

I also noticed that in 3.9.0, my excessively deep type error goes away... I'm speculating that this is to do with the optimisations they introduced (https://devblogs.microsoft.com/typescript/announcing-typescript-3-9-beta/#speed-improvements)
Any insight into whether the new version changes the game?

I agree, it is difficult to trace those errors. You can either start compiling your own version of TypeScript so that you can display useful info... Or, you can use the --extendedDiagnostics flag which will give you a somewhat clearer understanding of how your type is behaving. You'll be able to see your type count there.
What I call a single instruction is basically either a (naked) extends clause, mapped type, or simply a return. So if you'd nest such utilities in a parent type, it counts the branches of logic within it too... And if it hits that count before finishing, then it throws you that message. You see, it's your whole type that has to stay lightweight, all your logic branches within it.
And it's not always easy. Sometimes, you'd be better off rewriting the whole thing from scratch rather than using ts-toolbelt, just to save yourself from that count. A simple approach is to disable some of your logic with dummy data, then see which parts are under-performing. But maybe you're doing something wrong, and you can as well post your type in another question.
With the type system running on top of JavaScript, we clearly lose performance. IMHO, we would have been better off if the TS server had native performance so that we could have a more scripted (and faster) type system... But maybe, as TypeScript grows, this will become more obvious in the future.

Thanks for the info, I'm gland they've put effort into it :)

authors: Martaver pirix-gh

repo: pirix-gh/ts-toolbelt


text:
NPM/Yarn: dependencies not found

I'm trying to get license_finder to list licenses for license validation in jenkins.
$ ruby -v
ruby 2.4.3p205 (2017-12-14 revision 61247) [x86_64-linux-gnu]
$ license_finder version
5.0.3
$ ls
dist	      test		   webpack.production.config.js
fonts   package.json  src	webpack.config.js    yarn.lock
$ lsb_release -di
Distributor ID:	Ubuntu
Description:	Ubuntu 14.04.5 LTS

It works fine on my laptop but when running as jenkins on the server it just shows an error
$ license_finder
LicenseFinder::NPM: is active
LicenseFinder::Yarn: is active

No dependencies recognized!

I don't see any log or reason why the packages aren't read like they are on my own machine. Help debugging this would be appreciated.

Hi @dutt,
Behind the scenes, when the Yarn package manager is active, it runs the following command:
yarn licenses list --no-progress --json --cwd <path_to_project>
A couple of things to try to see if you can get more information would be:

Pass license_finder the -p or --prepare flag which will run yarn install. I forget offhand if yarn fails to report packages that it hasn't installed, but it should be a quick thing to try. If there's a failure when running the prepare command, it should also leave a log file under the project directory that may yield some additional insights.
Try having Travis run the yarn command above that license_finder runs and see if there's any output.

Hi,
Thanks for taking the time to help me look into this.
yarn list:
frontend$ ls
dist	         package.json  src	 webpack.config.js	        yarn.lock
  fonts   node_modules  webpack.production.config.js  webpack.reportapp.config.js
/frontend$ yarn licenses list --no-progress --json --cwd .
{"type":"error","data":"Invalid subcommand. Try \"ls, generate-disclaimer\""}
{"type":"info","data":"Visit \u001b[1mhttps://yarnpkg.com/en/docs/cli/licenses\u001b[22m for documentation about this command."}

license_finder -p
frontend$ yarn install
yarn install v0.24.6
[1/4] Resolving packages...
success Already up-to-date.
Done in 1.03s.
frontend$ license_finder -p
LicenseFinder::NPM: is active
LicenseFinder::Yarn: is active

No dependencies recognized!

@dutt looks like your server has an old version of yarn, which still spells the command yarn licenses ls, instead of yarn licenses list. The yarn project changed this behavior in https://github.com/yarnpkg/yarn/pull/3898.
You could upgrade yarn on your server (check yarn versions on both your laptop and jenkins—they should be the same), or look into teaching yarn the ls alias.

Thanks! I upgraded yarn and it works splendidly now. I'm a little embarrased, should've thought of this earlier...oh well, we live and learn.

Thanks @mainej
... and sorry, I meant "Jenkins" not "Travis" in my earlier comment.

authors: dutt kdykeman mainej

repo: pivotal/LicenseFinder

license: mit


text:
Compatibility with redmine 2.3

Clicking on activity with a Reporter user it shows the activities with the default theme. With Administrator everything's work fine

Sorry, it was a caching issue...

repo: pixel-cookers/redmine-theme


text:
Add a timer

As a user I want to have a timer, so that I can track the time I spend in a room

closed via #4

repo: pixelass/we-and-me


text:
page organisation : list of jobs

ce panel ne semble pas fonctionnel

SyntaxError: missing } after property list
...ris', '55d62ba1f6ca47ca3f56b7ca' : 'l'atelier symbiotique', 	}, function(k, v)

authors: MathieuCoste oceatoon

repo: pixelhumain/communecter


text:
Target current tab from any iframe

We have tabId: "this" for this purpose:

https://github.com/pixiebrix/webext-messenger/pull/53

however it only works between extension pages because:

only extension pages can use chrome.tab without intermediary steps

the current logic only handles "this" by comparing the sender to the current context, but this could be trivially changed:
on send:
	if isContentScript && tabId === "this"
		send to background

on background receive:
	if tabId === "this"
		forward to this.trace[0].tab.id

https://github.com/pixiebrix/webext-messenger/blob/ed302a0f45c26714f3d0bdd034d23d4572cb1047/source/thisTarget.ts#L68-L71

This is no longer used after the migration to sidePanel, but it can be added in these two places if it ever becomes useful again.
https://github.com/pixiebrix/webext-messenger/blob/3ac32d7e55c27ebf13558fc168cc1dbf5d6abc4b/source/receiver.ts#L61-L63
https://github.com/pixiebrix/webext-messenger/blob/3ac32d7e55c27ebf13558fc168cc1dbf5d6abc4b/source/sender.ts#L299-L300

repo: pixiebrix/webext-messenger


text:
[Suggestion] Don't use dynamic parameters of ES6

the function with  dynamic parameters  like  this (ES 6) :
   // in  class Container
    addChild(...childs)
    {
        // ......
    }

will be transformed to  (ES 5):
    Container.prototype.addChild = function addChild() {
        for (var _len = arguments.length, childs = Array(_len), _key = 0; _key < _len; _key++) {
            childs[_key] = arguments[_key];
        }
        // ......
    }

The performance of the porting code is bad.

ouch, that is slow :/

var childs = Array.prototype.slice.call(arguments, 0);

is enough.
And why use childs  , children is a good name, I think.

thats still creating a new array. The fastest way is how we had it before:
var argumentsLength = arguments.length;

    // if there is only one argument we can bypass looping through the them
    if(argumentsLength > 1)
    {
        // loop through the arguments property and add all children
        // use it the right way (.length and [i]) so that this function can still be optimised by JS runtimes
        for (var i = 0; i < argumentsLength; i++)
        {
            this.addChild( arguments[i] );
        }
    }
    else
    {
          //add child code
    }

I think best way is separate it to 2 functions:
addChild
addChildren

var childs = Array.prototype.slice.call(arguments, 0);

You should not use that, it causes an argument leak deoptimization. The compiled ES5 from babel is the correct way to convert arguments to an array (and is faster that slice anyway).
In this case, not creating the array at all is the obvious solution. However, if the function would be creating an array from arguments anyway then rest-params and the associated transpiled code is perfectly fine.

authors: GoodBoyDigital englercj finscn


text:
Compatible binary files

For compatible with binary files, add “ ||xhr.responseType==='arraybuffer'  " when status = STATUS_OK.

Is this a comment? I’m going to close, reopen if you would like to clarify.

authors: bigtimebuddy lipigirl


text:
Auto generation for typescript definitions

Work in progress.
npm install
npm run types

The result is inside dist/types folder.
Current problems:

resource-loader dependency
we have to separate canvas definitions from the rest
private:true for jsdocs
strange messages about module.exports
module for static members of classes

OK, now we have only one problem before it generates correct typescript definition - static overrides, from and fromImage.
I'll add it to manual steps list.
Please review and merge this.

Please don’t merge this yet, I’m testing it today.

Manual changes list:

add typings for resource-loader
event-emitter
change from and fromImage, add extra declarations in TilingSprite and CubeTexture.

I'm gonna commit typings based on that thing and manual changes in separate PR soon

Currently, Travis is blocked on getting the latest tsd-jsdoc published. There's critical fix in master not yet on NPM. Also @ivanpopelyshev created 2 PRs that would be helpful here (we could remove some hacks).
We have been testing typings in this branch of pixi-typescript. Seems to work well and support typings for legacy and default bundles.

authors: bigtimebuddy ivanpopelyshev


text:
"failed to download or apply critical settings."

Whenever i try to open bloxstrap, this error pops up, what do i do to resolve it? or do i just delete the old launcher.

That doesn't seem like a Bloxstrap-related issue. Try uninstalling Bloxstrap to revert back to the stock launcher, and see if the issue still persists.

sorry for the delay, it works fine without bloxstrap, maybe i need to reinstall bloxstrap?

Sure, go ahead and try.

it works now, thanks for the help

but i am having trumble to play

authors: Instearstell coolkide2 pizzaboxer

repo: pizzaboxer/bloxstrap


text:
fix: remove code cov and git hacks

Using proper mocks now for testing env var code paths and non existing git
infos.
closes #4

Codecov Report

Merging #5 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master     #5   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          12     13    +1
=====================================
+ Hits           12     13    +1

Impacted Files
Coverage Δ

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

Continue to review full report at Codecov.

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

authors: codecov-io pke

repo: pke/parse-app-info


text:
Remove In from the end of this line

https://github.com/pkic/pkimm/blob/830223b9afa3bbcd464fc0cb8f46b6af4d85e04a/model/_index.md?plain=1#L71C1-L71C33
Howdy,
I wanted to let you know of a typo that I found. Awesome work by the way!

Thanks @jwgarrett , fixed by https://github.com/pkic/pkimm/commit/0aa269078dcfe3df1a955ec49a0ceea798b8501d.

repo: pkic/pkimm


text:
BUG: A user can copy a link to a profile / author page from the main feed

Steps to Reproduce:

Visit planetary.link
Click on the elipses menu
Select copy link to author
Post it into a url bar
Issue: Header flashes and then page is black
Expected: Profile page should render.

Fixed in #104

authors: nichoth setch-l

repo: planetary-social/viewer-frontend


text:
🛑 API (my.plantnet.org) is down

In 4cadcc2, API (my.plantnet.org) (https://my-api.plantnet.org/v2/languages?api-key=$MY_PLANTNET_API_KEY) was down:

HTTP code: 0
Response time: 0 ms

Resolved: API (my.plantnet.org) is back up in 25e1992.

repo: plantnet/status


text:
Mount read only shared data volume

Fixes #35.
Mount the /srv/data volume in the user containers.

[x] Update the documentation to mention this volume
[x] Update the overview diagram

Could it be the /data directory instead of /src/data?

Why not /srv/data as recommended in http://tljh.jupyter.org/en/latest/howto/content/share-data.html#option-2-create-a-read-only-shared-folder-for-data?

OK. Let's go with /srv/data

Good!

authors: jtpio pierrepo

repo: plasmabio/plasmabio


text:
Fix method reflection for ruby 2.1

Fixes warning:
    /home/badosu/.gem/ruby/2.2.1/gems/simple_form-2.1.2/lib/simple\
    _form/inputs/boolean_input.rb:37:
    warning: circular argument reference - unchecked_value

This build is failing on Ruby < 1.9.3, but that's because it's not supported on the gem i18n. So that should not be a problem caused by this PR.

Thanks.

Thanks!

Just a question, do you still release 2.1.x? What's the plan?

Depending on the change yes, we may release a new 2.1 version. 2.2 was just an experiment but I don't plan to release a version from it.

Thanks for the info.


text:
Handle dynamically generated property names in models

I've got an API that returns data in a format similar to this:
{
  "someProperty": {
    "_1_1": {
      some child object here
    },
    "_2_1": {
      some other child object here
    }
  }
}

As you can see, this is a map of objects where the keys are IDs, which means they are dynamically generated. The child objects are represented by a restmod model, but I don't see how to setup the relationship between the 2 models since the property names are dynamic.
Right now, I use the after-feed hook to manually convert the raw data to the proper model, by looping over the results. Is there a simpler way to do that with restmod?

This is somehow out of scope right now, we are not planning on extending the current relations behaviour.
Take a look at src/module/extended/builder-relations to see if you can modify the code for your convenience.

authors: agustinf blaiz

repo: platanus/angular-restmod


text:
FR: Break down the yaml-title rule into two rules

Currently the yaml-title rule gets the title from the first H1 or filename. This is incompatible with the use case that uses H1 headers as section names rather than the file name. See here for a discussion about different styles of H1 usage. For example:
# section 1

will be converted to
---
title: section 1
---

# section 1

Breaking the rule into 2 rules would solve this problem: yaml-title-from-filename and yaml-title-from-h1.

I believe it makes the most sense to make the yaml-title header work with a dropdown as to how it should work. It would have 3 options:

title from first H1 or file name
title from file name
title from first H1

We can add options down the road if we so choose this way. It also makes breaking this logic up better.

I believe that I have the change as described in my previous comment ready. I need to add the text for each of the current languages and then go ahead and update the current YAML Title description to match the new functionality of the rule. It should work the same out of the box.

The change to YAML Title adding 3 modes (one for how it currently works, one for just the filename, and one for just the first H1) should go out with the next release. Please let us know if this does not work on master or in the next release.

authors: pjkaufman yimingli

repo: platers/obsidian-linter


text:
Solución Reto 3

DESCRIPTION
Nombre: Juan Camilo Rico Orjuela
Usuario Platzi: juancarico92
Ciudad

[ ] Ciudad de México
[x] Bogotá

Retos:

[x] Primer problema
[x] Segundo problema
[x] Tercer problema

Pull Request entregado fuera de hora de revisión. :(


text:
Could not able to load 3DGS model

Hello developers, I am trying to visualize trained 3DGS model. But I am facing this error. Thanks in advance.
OS: ubuntu 22.04
Browser: Google Chrome
GPU: yes
Loading method: tried both drag & drop and using open button

@slimbuck Done.

Thanks @hardikdava.
Is this a recent change? Have you done this before on this system?

@slimbuck Yes, this is very recent change. I tried firefox and seems working but not with chrome.

CSP should be fine on the scripts. Not sure what to suggest. Perhaps cloudfront had a blip? Could you try loading again after clearing cache?

@slimbuck Tried but not resolved.

Unless we can reproduce there is not much we can do here unfortunately.
Please re-open this issue if you know how we can repro.

authors: hardikdava slimbuck

repo: playcanvas/supersplat


text:
Issue with Wait methods

if _, err := page.Locator(//input[@id='lastName-input']).WaitForLoadState({ 		state: "visible", });
whats wrong in this piece of code,I want to wait till state becomes visible?
can someone please help?

should be
err := page.Locator("//input[@id='lastName-input']").WaitFor(playwright.PageWaitForSelectorOptions{
	State: playwright.WaitForSelectorStateVisible,
})

state default to visible, so
err := page.Locator("//input[@id='lastName-input']").WaitFor()

WaitForLoadState is for page or frame, not element.

thankyou @canstand

authors: Ash-KODES canstand

repo: playwright-community/playwright-go


text:
🛑 Lindas Kingdoms is down

In a05f16b, Lindas Kingdoms (https://lindas.admin.ch/query?query=PREFIX rdf%3A <http%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23>
SELECT DISTINCT %3Fk (SAMPLE(%3Fs1) as %3Fs)%0AWHERE%20%7B%0A%20%20%3Fs1%20a%20%3Chttp%3A%2F%2Ffilteredpush.org%2Fontologies%2Foa%2FdwcFP%23TaxonName%3E%3B%0A%20%20%3Chttp%3A%2F%2Frs.tdwg.org%2Fdwc%2Fterms%2Fkingdom%3E%20%3Fk.%0A%7D%0AGROUP%20BY%20%3Fk) was down:

HTTP code: 503
Response time: 801 ms

Resolved: Lindas Kingdoms is back up in 66fd628 after 12 minutes.

repo: plazi/monitoring


text:
not removing a registered pattern

Hello, Here is the code I am working with:
package main

import (
	"bytes"
	"log"
	"time"

	coap "github.com/plgd-dev/go-coap/v2"
	"github.com/plgd-dev/go-coap/v2/message"
	"github.com/plgd-dev/go-coap/v2/message/codes"
	"github.com/plgd-dev/go-coap/v2/mux"
)

func loggingMiddleware(next mux.Handler) mux.Handler {
	return mux.HandlerFunc(func(w mux.ResponseWriter, r *mux.Message) {
		log.Printf("ClientAddress %v, %v, %v\n", w.Client().RemoteAddr(), r.String(), r.Message.Code)
		next.ServeCOAP(w, r)
	})
}

func handleA(w mux.ResponseWriter, r *mux.Message) {
	err := w.SetResponse(codes.Content, message.TextPlain, bytes.NewReader([]byte("hello world"+time.Now().String())))
	if err != nil {
		log.Printf("cannot set response: %v", err)
	}
}

func main() {
	r := mux.NewRouter()
	r.Use(loggingMiddleware)
	log.Println("Register: ", r.Handle("/a", mux.HandlerFunc(handleA)))
	log.Println("Response", r.HandleRemove("/a"))
	coap.ListenAndServe("udp", ":5683", r)
}

Here is what is printed on the console when I run it. It says pattern not registerd but it responds to client request with that pattern.
bruk@ubuntu_machine:$go run main.go
2020/09/12 11:05:53 Register:  <nil>
2020/09/12 11:05:53 Response pattern is not registered in
2020/09/12 11:05:54 ClientAddress 127.0.0.1:46927, Code: GET, Token: , Path: a, GET
keepalive: context deadline exceeded

Can anybody help?

solved: by removing the / from the handle remove parameter
log.Println("Response", r.HandleRemove("a"))

repo: plgd-dev/go-coap


text:
Volume issues

Hi,
Testing with Spotify IOS app on iPhone 5 and librespot on Pi.
sudo ./librespot --name RP3spot --cache /tmp --bitrate 320 --backend alsa --device hw:0
What I experienced is as follows:

Spotify IOS client set volume to 100% on first connect/play! iPhone local volume was only 30%. See attached image.
Volume stepping used by Spotify IOS client is very corse, only 10 steps to full volume using the physical iPhone buttons.
The slider volume control within the Spotify app behaves similarly in that it raises volume too much within the first half of the slider.
No support for hardware volume yet in librespot (already covered in existing issue)

The very nice debug logging shows volume cmds being received but how to decode them to see what level the client is requesting?
DEBUG:librespot::spirc: kMessageTypeVolume "Tim's iPhone" 3496dcfbf06e2b19c74d6d5216389761aa9a4e94 4 0
DEBUG:librespot::spirc: kMessageTypeNotify "RP3spot" 8ced8e4318e14e95632409ed1898989ff295f075 10 1485738325625
DEBUG:librespot::spirc: kMessageTypeVolume "Tim's iPhone" 3496dcfbf06e2b19c74d6d5216389761aa9a4e94 5 0
DEBUG:librespot::spirc: kMessageTypeNotify "RP3spot" 8ced8e4318e14e95632409ed1898989ff295f075 11 1485738326177
DEBUG:librespot::spirc: kMessageTypeVolume "Tim's iPhone" 3496dcfbf06e2b19c74d6d5216389761aa9a4e94 6 0
DEBUG:librespot::spirc: kMessageTypeNotify "RP3spot" 8ced8e4318e14e95632409ed1898989ff295f075 12 1485738326424

Regards,
Tim

Thanks for bringing this up.

Spotify IOS client set volume to 100% on first connect/play! iPhone local volume was only 30%

This is intentional, see https://github.com/plietar/librespot/pull/43 for the reasons. The local volume on the phone does not have an impact.

Volume stepping used by Spotify IOS client is very corse, only 10 steps to full volume using the physical iPhone buttons.

I'm not sure why it was set to 10, but I've just bumped it to 64 steps in 7be9626. This is the same behaviour as the desktop client.

The slider volume control within the Spotify app behaves similarly in that it raises volume too much within the first half of the slider.

Not sure what you mean there

Hi Paul,
Since its not possible for the software to know much about users audio system, assume that if client defaults to sending 100% volume that full volume will be output at speakers or headphones when play button is pressed.
-TIm

@plietar The reason it was set to 10 is because otherwise volume control using the OSX volume slider does not work properly. Try compiling the latest version with the 64 steps, and you'll see that no volume change occurs except between muted and unmuted. It was discussed on Gitter a number of months ago. Might I suggest we revert 7be9626 for now until we can find a solution that doesn't break existing use cases?

I'd be very interested in being able to specify an initial volume via an argument or config, or even better, have the ability to retain the previous spotify connect volume.
I'm using this with snapcast (https://github.com/badaix/snapcast/) and most of my other sources are never at 100% (e.g. airplay), so when I use spotify connect and switch sources, the volume is always too high since it's at 100%!
Thanks

I agree with pbros, it would be great if we could fix this for the snapcast users (including me :)). I would be happy with an initial volume of 0 if that would make things easier.

@moodeaudio

Consider setting initial volume to one of the following:

level that user previously set in the Spotify client app
level of client device local volume that user previously set

AFAIK this isn't possible, clients don't send their current level

0% (default)

This is inconvenient since it requires all users to increase the volume every time, and would lead to confusion

level specified in librespot cmd string. For example --initial-volume 10%. This would allow users that want client to always output 100% to their audio system to simply specify --initial-volume 100%.

This would work.
Note that audio volume was recently refactored (#148) to support multiple mixer backends

When using software volume, we can add a --initial-volume flag, as well as save volume to the cache and use that when the flag isn't passed.
When using alsa mixing (#158), we can just use the system's volume, which is what that PR does.

I'm a bit concerned about the increasing number of command line flags, and would like to move to a more flexible config file based solution, where each audio and mixer backend can have different configuration options.

For applications uses a pipe or stdout (like snapcast), alsa isn't an option. In this case, the best options would be a flag or a config file since we could always use a default initial volume when instantiating librespot. If ever the calling application can save the previous volume, then we could handle the case where we want to go back to the previous level!

I am interested in this feature to put an initial volume. Is it possible ?

authors: ashwinvandijk goguetchapuisb moodeaudio pbros plietar sashahilton00

repo: plietar/librespot


text:
BibTeX subsystem: warning: comma(s) at end of name (removing)

Hi,
I get "BibTeX subsystem: warning: comma(s) at end of name (removing)".
but there is no information about the line, so I can't correct my database easily.

I am afraid there isn't much we can do about this as it's a limitation of the btparse library that doesn't report line numbers . A quick  fgrep ',}; on your .bib shows a few fields with trailing commas.

oki, you are right. I made a mistake between "comma" and "dot" and I thought the message was becase I put some first name with a comma after. So we can close.

authors: maieul plk

repo: plk/biber


text:
Try "${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}" for default of current repository

REPO_URL="${GITHUB_SERVER_URL}/${GITHUB_REPOSITORY}"
That or make it a secret. Hard to develop on a fork otherwise.

Closed by some recent merge...

repo: plocket/docassemble-cucumber


text:
Create Event: Shows "Create Event Not Successful" message even when all fields are completely inputted

Create Event inputs:

Create Event Not Successful message:

UPDATE:
This is actually a date collision. Create Event is not successful because another event is already created on the same date. I think the user should be informed why the Create Event is not successful (in this case, date collision).

repo: ploidddddd/purplekeep


text:
UX: Confusing the X is used both delete (in a grid) and cancel (on a page)

Describe the bug
I'd say it makes it pretty unclear that x on a container block means delete
To Reproduce
make a grid. see the x
Expected behavior
Use a trash icon. It's consistent.
Screenshots
Here you can see the same x icon being used for two different purposes on the same page

Is this about https://github.com/kitconcept/volto-blocks-grid? The grid block hasn't been added to volto core yet.

There's also a trash can icon to the right of the block, making the X next to the gear icon redundant. X means "cancel" in my brain.

There's also a trash can icon to the right of the block, making the X next to the gear icon redundant. X means "cancel" in my brain.

exactly. X means cancel.
The delete next to the gear deletes the contents rather than the whole block. Which is itself another different UX problem with that particular container block.

Is this about https://github.com/kitconcept/volto-blocks-grid? The grid block hasn't been added to volto core yet.
fair enough. It also applies to other container blocks like accordion which also aren't in core. so hopefully the appropriate place to fix it is #3180 and the proper block in block UI once it's in core I guess.

since this is related to grids and rows and they aren't released yet this is not a current bug

authors: davisagli djay stevepiercy

repo: plone/volto


text:
add binwidth to histogram

should work just like R's ggplot: https://ggplot2.tidyverse.org/reference/geom_histogram.html

assigning it now so I don't forget but feel free to finish the existing tasks first

Acceptance Criteria

Add binwidth argument to geom_histogram(). It should mimic binwidth in R ggplot.
Add test images
Add documentation

sounds good!

repo: ploomber/jupysql


text:
dds only mode fix

Addresses DDS-Only mode aspect of https://github.com/plotly/streambed/issues/13208.
@josegonzalez please review
Tested:

[x] on-prem (admin-based deploys fail without this code when in DDS-only mode. admin-based deploys still succeed in non-DDS-only mode).

@josegonzalez updates made. Please review.

Thanks for the suggestions @josegonzalez! Updates made.

Thanks @josegonzalez! Update made : )

repo: plotly/dokku-acl


text:
🛑 KCG is down

In 5b9ac8e, KCG (https://kunstrijclubgroningen.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KCG is back up in ccf50b0 after 25 minutes.


text:
🛑 Dick Pluim.com is down

In 8bfc71e, Dick Pluim.com (https://dickpluim.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dick Pluim.com is back up in 899e7f1 after 16 minutes.


text:
🛑 Pierced Arrows is down

In 1222a14, Pierced Arrows (https://www.piercedarrows.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pierced Arrows is back up in 70e7b43 after 16 minutes.


text:
I'd like to join this project's community

Your public repo
https://github.com/michelezanini/gov4git-identity-public.git
Your public branch
main

Approved.

 Follow up
On Sunday, 10-Mar-24 22:21:42 UTC by Gov4Git dev
@michelezanini was added to the community.

repo: pluralitybook/plurality


text:
User Defined Timezone Settings

It would nice if there was an easy way to configure the timezone settings in a configuration without forcing the user to manually edit the VMconfigurationdata.psd1 file.

Beginning with v4.5.0 Unattend-Lab and Setup-Lab will have a -UseLocalTimeZone parameter which will overwrite any configuration defined time zones.

repo: pluralsight/PS-AutoLab-Env


text:
feat: public params artifact

WIP.

[x] Works locally!
[x] This won't work until we make web-prover public or get a key to be able to pull that in as a crate.
[ ] Test generated AuxParams in web-prover

Added a bit more here: serialize the ProverKey and VerifierKey
But won't work until changes are made in client-side-prover.

Github CI working (as seen here), but failing for other reasons here. Should just work in main.

Not sure why I had to deal with that conflict when I pushed up a change right before it. Sometimes I'm so dumb with git I swear

Want to merge in https://github.com/pluto/web-prover/pull/331 prior to merging this and then pin to the correct commit for proofs crate.

You can pull them up yourself if you go to the action

authors: Autoparallel mattes

repo: pluto/web-prover-circuits


text:
Add UTM Remote Virtual Machines

https://testflight.apple.com/join/mFlnyMv3

done

repo: pluwen/awesome-testflight-link


text:
Not creating the project if not existing

Hello, i tested your tool like that :
mvn io.github.pmckeown:dependency-track-maven-plugin:${MAVEN_PLUGIN_UPLOAD_BOM_VERSION}:upload-bom -Ddependency-track.projectName=${application} -Ddependency-track.projectVersion=${CI_COMMIT_REF_NAME} -Ddependency-track.dependencyTrackBaseUrl="${BASE_URL_DEPENDENCYTRACK_UPLOAD_BOM}/bom" -Ddependency-track.apiKey=${DEPENDENCYTRACK_API_KEY} -Ddependency-track.waitUntilBomProcessingComplete=false

It has permissions to do what it needs, but if the project is new it won't be created by your tool
Logs
[INFO] --- dependency-track-maven-plugin:0.8.8:upload-bom (default-cli) @ demo-svc-service ---
[INFO] Project Name: app-demo-svc-service
[INFO] Project Version: latest
[INFO] Plugin is configured to wait for BOM processing to complete
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  4.634 s
[INFO] Finished at: 2020-12-09T17:49:57Z
[INFO] ------------------------------------------------------------------------

In the app, the project is not created.
Before your tool we were using curl with something like that  :
The autocreate to true in order to create the project if needed
echo "{\"autoCreate\": true, \"projectName\": \"$application\", \"projectVersion\": \"$CI_COMMIT_REF_NAME\", \"bom\": \"$(base64 -w 0 target/bom.xml

Thanks for any update for that ;)

Hi, this line in the plugin that creates the request to upload the BOM has the autoCreate flag hardcoded to true.  I couldn't think of a reason to make that configurable.
            Response<UploadBomResponse> response = bomClient.uploadBom(new UploadBomRequest(
                   commonConfig.getProjectName(), commonConfig.getProjectVersion(), true, encodedBom));

See
https://github.com/pmckeown/dependency-track-maven-plugin/blob/2bff4cea563eee75de4a3b7240d5aac343c4df4a/src/main/java/io/github/pmckeown/dependencytrack/upload/UploadBomAction.java#L80
I suspect its because you have /bom appended to the end of the base URL property.  From your example: ${BASE_URL_DEPENDENCYTRACK_UPLOAD_BOM}/bom
Try changing that to ${BASE_URL_DEPENDENCYTRACK_UPLOAD_BOM} where BASE_URL_DEPENDENCYTRACK_UPLOAD_BOM is something like: http://localhost:8080
There is a property you can use to configure the plugin behaviour which I recommend you set to true while setting up your integration.  Set -Ddependency-track.failOnError=true to ensure that the plugin reports errors when failing to integrate.  I default this to false to ensure builds are unaffected when dependency track is unavailable but its up to you if you want to change that..
Please close this issue if this fixes it for you.

Yes you are right, i have append "api/v1/bom" :)
Working properly with the good URL.
I have this option : -Ddependency-track.waitUntilBomProcessingComplete=false
So i don't want to have the result at the end of the upload, can you say me why i'm having this ?
[INFO] Plugin is configured to wait for BOM processing to complete
[INFO] BOM uploaded to Dependency Track server
[INFO] Checking for BOM analysis completion
[INFO] Still processing: true
[INFO] Still processing: true
[INFO] Still processing: true
....
....
[ERROR] Polling for processing completion was interrupted so continuing: Call 'io.github.pmckeown.dependencytrack.upload.UploadBomAction$$Lambda$107/0x0000000800365c40@4b515eab' failed after 20 tries!
[INFO] Requesting Metrics analysis for project: projectname
[INFO] Refreshing Metrics for project: projectname

Thanks

Hi, my bad but the README is out of date.  That property got removed when I refactored the polling to be a bit smarter.  the pollingConfig ended up as a complex object which means that you can't disable it on the command line with properties.
I suggest that you define the plugin as a dependency in your POM.  That way you can set the configuration needed to run it once and you can then use a much simpler command in your terminal.
Add the following to your POM:
        <pluginManagement>
            <plugins>
                <plugin>
                    <groupId>io.github.pmckeown</groupId>
                    <artifactId>dependency-track-maven-plugin</artifactId>
                    <version>0.8.8</version>
                    <configuration>
                        <!--suppress UnresolvedMavenProperty -->
                        <dependencyTrackBaseUrl>${env.DEPENDENCY_TRACK_BASE_URL}</dependencyTrackBaseUrl>
                        <!--suppress UnresolvedMavenProperty -->
                        <apiKey>${env.DEPENDENCY_TRACK_API_KEY}</apiKey>
                        <failOnError>true</failOnError>
                        <pollingConfig>
                            <enabled>false</enabled>
                        </pollingConfig>
                    </configuration>
                </plugin>
            </plugins>
        </pluginManagement>

Then you can just run
mvn dependency-track:upload-bom  -Ddependency-track.projectName=${application} -Ddependency-track.projectVersion=${CI_COMMIT_REF_NAME}

I will raise an issue to update the documentation to address this.

Thanks for the response, in my case, i need to use only argument, without modifying the pom.xml. I went on another plugin that have an option for my goal. Thanks for your work !

repo: pmckeown/dependency-track-maven-plugin


text:
Feature/435 thread safe module config

Closes #435

This has been incorporated and released in v1.9.1 - thanks for the contribution @kpe09 👍


text:
The found PyTorch version is too old

Hi, @pmeier. Thanks for this package, it looks very useful. I've always wanted something like this.
I am on Linux, NVIDIA driver 430.50. According to Table 1 here, the latest CUDA version I can install is 10.1. When I ran ltt install torch, I expected it to run
pip install torch==1.8.0+cu101 -f https://download.pytorch.org/whl/torch_stable.html

i.e., the latest PyTorch version that supports 10.1 (as far as I know), but it does
Collecting torch==1.4.0+cu100
  Downloading https://download.pytorch.org/whl/cu100/torch-1.4.0%2Bcu100-cp36-cp36m-linux_x86_64.whl (723.9 MB)
     |██▏                             | 50.2 MB 43.4 MB/s eta 0:00:16^C

which I killed. It looks like instead of installing 1.8.0 with CUDA 10.1, it installs 1.4.0 with CUDA 10.0. Is this expected?

Hey @fepegar

It looks like instead of installing 1.8.0 with CUDA 10.1, it installs 1.4.0 with CUDA 10.0. Is this expected?

Partially yes. It has detected that you are using CUDA 10.0 and torch==1.4.0 is the latest version built for that. So this behavior is correct.
Now we need to know why it detected CUDA 10.0, but you think you have CUDA 10.1. Internally light-the-torch uses $nvcc --version as source for the information. Could you run that manually and post the output here?

Thanks for your reply. I'm not in front of my computer at the moment, but I do have 10.0 installed, you're right. The internet says that the version shown by nvidia-smi is the latest that the installed drivers (nvidia-smi --query-gpu=driver_version --format=csv, second line) support.
It might be better to retrieve the version shown by nvidia-smi instead of the installed one shown by nvcc. What do you think? I'm happy to contribute, if necessary.

the version shown by nvidia-smi is the latest that the installed drivers support.

[And that's why I can install torch==1.8.0+cu101.]

However, it looks like the highest supported version is shown is printed with drivers >= 410.72. Therefore it might be safer to retrieve the driver version and calculate the supported CUDA manually using the lookup table I shared above (https://github.com/pmeier/light-the-torch/issues/30#issue-927470215).

Well, it won't help you much if your driver supports up to 10.1, but you only have 10.0 installed, or am I wrong here? For example in my current setup this looks like this
$nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2020 NVIDIA Corporation
Built on Mon_Oct_12_20:09:46_PDT_2020
Cuda compilation tools, release 11.1, V11.1.105
Build cuda_11.1.TC455_06.29190527_0
$nvidia-smi
Wed Jun 23 09:48:45 2021
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 465.31       Driver Version: 465.31       CUDA Version: 11.3     |
|-------------------------------+----------------------+----------------------+

So although my driver supports CUDA 11.3, I only have 11.1 installed. IMO in turn that means I will not be able to run a PyTorch compiled for CUDA 11.3.

I don't know much about CUDA, but I'm pretty sure a PyTorch compiled for CUDA 11.3 (if there is one) would indeed work for you. I think the CUDA toolkit installed with PyTorch is minimal and independent of whatever you have installed and is shown by NVCC. As I said, that works for me: I have 10.0 installed, but PyTorch compiled for 10.1 works fine.

Let me check that with the PyTorch folks and get back to you.

It appears you are right. Thanks a lot for the heads-up! Here is my plan fixing this:

Expand
https://github.com/pmeier/light-the-torch/blob/49264ab486f16f556987deea2c9688876169025e/light_the_torch/compatibility.py#L6
to handle version comparison besides equality check. Maybe it is easier to simply rely on packaging or the vendored version that ships with pip.
Hardcode the table you mentioned above.
Adapt
https://github.com/pmeier/light-the-torch/blob/49264ab486f16f556987deea2c9688876169025e/light_the_torch/computation_backend.py#L81
to use nvidia-smi --query-gpu=driver_version --format=csv together with mapping from 2. to determine the computation backend.

One problem that I see is that currently the implementation relies on the fact that there is only a single CUDA version. So this would also needs to be fixed to work with multiple versions.

I'm happy to contribute, if necessary.

Happy to take you up on the offer. I will probably not be able to get onto this for a couple of days.

No worries! I'd probably feel more comfortable with points 2. and 3. I won't be able to help until next week, in the context of the NA-MIC Project Week: https://github.com/NA-MIC/ProjectWeek/tree/master/PW35_2021_Virtual/Projects/PyTorchIntegration#light-the-torch

One problem that I see is that currently the implementation relies on the fact that there is only a single CUDA version. So this would also needs to be fixed to work with multiple versions.

I'm not sure what you mean by "there is only a single CUDA version". Couldn't we just ignore the installed CUDA versions and choose the installer based on the drivers?

in the context of the NA-MIC Project Week

That being said, I might not be able to use ltt within the Slicer Python console...
>>> import light_the_torch as ltt
Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "/home/fernando/opt/Slicer/Nightly/lib/Python/lib/python3.6/site-packages/light_the_torch/__init__.py", line 3, in <module>
    from ._pip import *
  File "/home/fernando/opt/Slicer/Nightly/lib/Python/lib/python3.6/site-packages/light_the_torch/_pip/__init__.py", line 1, in <module>
    from .extract import *
  File "/home/fernando/opt/Slicer/Nightly/lib/Python/lib/python3.6/site-packages/light_the_torch/_pip/extract.py", line 5, in <module>
    from pip._internal.req.req_install import InstallRequirement
  File "/home/fernando/opt/Slicer/Nightly/lib/Python/lib/python3.6/site-packages/pip/_internal/req/__init__.py", line 10, in <module>
    from .req_install import InstallRequirement
  File "/home/fernando/opt/Slicer/Nightly/lib/Python/lib/python3.6/site-packages/pip/_internal/req/req_install.py", line 35, in <module>
    from pip._internal.utils.direct_url_helpers import direct_url_from_link
  File "/home/fernando/opt/Slicer/Nightly/lib/Python/lib/python3.6/site-packages/pip/_internal/utils/direct_url_helpers.py", line 12, in <module>
    from pip._internal.vcs import vcs
  File "/home/fernando/opt/Slicer/Nightly/lib/Python/lib/python3.6/site-packages/pip/_internal/vcs/__init__.py", line 9, in <module>
    import pip._internal.vcs.subversion  # noqa: F401
  File "/home/fernando/opt/Slicer/Nightly/lib/Python/lib/python3.6/site-packages/pip/_internal/vcs/subversion.py", line 336, in <module>
    vcs.register(Subversion)
  File "/home/fernando/opt/Slicer/Nightly/lib/Python/lib/python3.6/site-packages/pip/_internal/vcs/versioncontrol.py", line 317, in register
    self._registry[cls.name] = cls()
  File "/home/fernando/opt/Slicer/Nightly/lib/Python/lib/python3.6/site-packages/pip/_internal/vcs/subversion.py", line 191, in __init__
    use_interactive = is_console_interactive()
  File "/home/fernando/opt/Slicer/Nightly/lib/Python/lib/python3.6/site-packages/pip/_internal/utils/misc.py", line 906, in is_console_interactive
    return sys.stdin is not None and sys.stdin.isatty()
AttributeError: 'PythonQtStdInRedirect' object has no attribute 'isatty'

So the problem is in from pip._internal.req.req_install import InstallRequirement. But this is probably not your problem, so I will discuss it with the Slicer devs if necessary.

I'm not sure what you mean by "there is only a single CUDA version". Couldn't we just ignore the installed CUDA versions and choose the installer based on the drivers?

The current implementation is built on the assumption that there is only one computation backend. With the addition we are about to make this is no longer true, since a specific driver version supports multiple CUDA versions. Currently, the implementation restricts the field of possible installation candidates to one exact CUDA version. So this needs to be relaxed.

So the problem is in from pip._internal.req.req_install import InstallRequirement. But this is probably not your problem, so I will discuss it with the Slicer devs if necessary.

Yeah, sorry, I can't offer support there. I'll fix that this works with pip but to get this working within other projects is out of scope (at least for now).

The current implementation is built on the assumption that there is only one computation backend. With the addition we are about to make this is no longer true, since a specific driver version supports multiple CUDA versions. Currently, the implementation restricts the field of possible installation candidates to one exact CUDA version. So this needs to be relaxed.

Ok, I think I understand. Thanks!

Yeah, sorry, I can't offer support there. I'll fix that this works with pip but to get this working within other projects is out of scope (at least for now).

Sure! I just thought I'd let you know in case it was helpful.

I have opened a PR all the way up to PythonQt (https://github.com/MeVisLab/pythonqt/pull/49) to fix the problem with pip I mentioned above. Locally, I was able to avoid it by removing all references to InstallRequirement in _pip/extract.py. I don't know how necessary that import is, but it would help me solve this quickly!
Let me know if you would like me to open a new issue about this.

InstallRequirement is only used for linting, so I can make optional only for this use case.

Let me know if you would like me to open a new issue about this.

Yes, please. Keeps the project organized :wink:

Reopening since #31 only partially fixed this.

authors: fepegar pmeier

repo: pmeier/light-the-torch


text:
"Edit this page on GitHub" links broken

For example, on the page: "https://dext.vercel.app/drei/controls/introduction" the link is broken

I'm late to this, but seems outdated, at least the link does not work anymore

authors: abernier theRealProHacker

repo: pmndrs/docs


text:
Installation stuck

Hellooo,
I tried to use this tool, but it get's stuck on the installation.
npx gltfjsx 4kpoly_1ktexture.gltf
results in
Need to install the following packages:
  gltfjsx
Ok to proceed? (y) y
⸨   ░░░░░░░░░░░░░░░⸩ ⠋ idealTree:restore-cursor: sill placeDep ROOT restore-cursor@3.1.0 OK for: cli-cursor@3.1.0 want: ^3.1.0

nothing i can do there, this is npm. could be an outage.

If you are stuck for this, maybe try the online version at https://gltf.pmnd.rs/

Please reopen if you find that the issue doesn't depend on a temporary npm problem or your network

I am also stuck with the installation. I have also tried the link above. It doesn't work either. Any solution?

Same here. I run these commands:
npx gltfjsx empire.gltf
Need to install the following packages:
  gltfjsx
Ok to proceed? (y) y
[     .............] - idealTree:restore-cursor: sill placeDep ROOT restore-cursor@3.1.0 OK for: cli-cursor@3.1.0 want:

Same here, I tried to run the command several times and it was always getting stuck in the same line that the other posted above.

authors: BevyJiang drcmda eriksachse focux gsimone jrafaaael

repo: pmndrs/gltfjsx


text:
Reproduce results of SMILES-based CNN

We should probably do a controlled test verifying this method works by reproducing the results of this paper before trying something more complex, like what we're proposing.

To do this week @pmont056


text:
Error compiling rails app

-> Running [{"CI"=>"true", "PATH"=>"C:/Users/callm/AppData/Local/Temp/rubyc/ruby-2.4.1-0.4.0/build/bin:C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files (x86)\MSBuild\14.0\bin;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools;C:\Windows\Microsoft.NET\Framework\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\VCPackages;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Performance Tools;C:\Program Files (x86)\Windows Kits\8.1\bin\x86;C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6 Tools\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Calibre2\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files (x86)\GnuWin32\bin;C:\Ruby26-x64\bin;C:\Users\callm\AppData\Local\Microsoft\WindowsApps;C:\Program Files\heroku\bin", "GEM_HOME"=>nil, "GEM_PATH"=>nil, "ENCLOSE_IO_USE_ORIGINAL_RUBY"=>"1", "ENCLOSE_IO_RUBYC_1ST_PASS"=>"1", "ENCLOSE_IO_RUBYC_2ND_PASS"=>nil}, "gem", "install", "C:/Users/callm/AppData/Local/Temp/rubyc/ruby-2.4.1-0.4.0/vendor/bundler-1.15.3.gem", "--verbose", "--no-rdoc", "--no-ri"]
ERROR:  While executing gem ... (OptionParser::InvalidOption)
invalid option: --no-rdoc
Failed running [{"CI"=>"true", "PATH"=>"C:/Users/callm/AppData/Local/Temp/rubyc/ruby-2.4.1-0.4.0/build/bin:C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files (x86)\MSBuild\14.0\bin;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools;C:\Windows\Microsoft.NET\Framework\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\VCPackages;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Performance Tools;C:\Program Files (x86)\Windows Kits\8.1\bin\x86;C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6 Tools\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS\;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\Calibre2\;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files (x86)\GnuWin32\bin;C:\Ruby26-x64\bin;C:\Users\callm\AppData\Local\Microsoft\WindowsApps;C:\Program Files\heroku\bin", "GEM_HOME"=>nil, "GEM_PATH"=>nil, "ENCLOSE_IO_USE_ORIGINAL_RUBY"=>"1", "ENCLOSE_IO_RUBYC_1ST_PASS"=>"1", "ENCLOSE_IO_RUBYC_2ND_PASS"=>nil}, "gem", "install", "C:/Users/callm/AppData/Local/Temp/rubyc/ruby-2.4.1-0.4.0/vendor/bundler-1.15.3.gem", "--verbose", "--no-rdoc", "--no-ri"]

Fixed that issues by rolling back rubygems to 2.5.
God that issue seems so long ago. Now I have a new issue that I've been dealing with for days.
"fatal error c1060: compiler is out of heap space" while compiling memfs.

in my case when i compile preparing tools (it seems prelude.c) it uses 10GB memory

in my case when i compile preparing tools (it seems prelude.c) it uses 10GB memory
#74

I finally got past that error. I did it by increasing the paging file space to max 90000. The compiler finally(and I can't stress the word finally enough) ran through completion.
But...now I'm getting another error when I try to run the output exe.
$ ./a.exe server
c:/enclose_io_memfs/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in require': cannot load such file -- bundler/setup (LoadError)         from c:/__enclose_io_memfs__/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in require'
from c:/enclose_io_memfs/local/config/boot.rb:3:in <top (required)>'         from /__enclose_io_memfs__/local/bin/rails:3:in require_relative'
from /enclose_io_memfs/local/bin/rails:3:in `'

authors: iamsimakov treyvfromlbc


text:
plugin stopped working in iOS

Plugin stopped working in iOS. Im getting "Syntax error: Unexpected identifier 'exec'" at line 2 in BackgorundLocationServices.js
Derive from that error (I guess) I get " Error org.flybuy.cordova.background-location-services.BackgroundLocationServices does not exist"
I'm about to use the plugin in a production app, I would appreciate it a lot if you could look in to the problem.

@icedice how did you add the plugin to your project?
Make sure your not on this https://github.com/pmwisdom/cordova-background-geolocation-services/commit/bcb6115dd90fc36c20f9aa4c1f6d96378ba15852 commit.

Going to close this for now, Please re-open if its still a problem.

authors: icedice pmwisdom


text:
Get average daily balance

Code snippet migration. Average daily balance.

I might be mistaken (please correct me if I am), but I think it would be better to forward-fill before doing the daterange selection in step 3.
with the current implementation, we would leave the left-hand-side of the time-range unfilled.
in other words, what happens if we have a daterange 05/1 to 05/30. we subset all balances on that daterange. for a give institution and account_number, the earliest balance timestamp is 05/05. then we'd only forward-fill from 05/05-05/30, and we would not be including in our mean avg the balance over 05/01 - 05/05.
if, for the same account number and institution, we had a balance record on 04/25, then we'd want to forward-fill from 04/25-05/05, and have that daily forward-fill inplace before we truncated our dataframe for 05/01-05/30.

This is very valuable feedback and comment. I have modified the codes to address this issue.

authors: kevin-pngme kevindingpngme

repo: pngme/pngme-feature-library


text:
Docusaurs: Update sidebar.js to manually order cmd folder content

In the sidebar.js file we automatically sort the content of the cmd folder, but this may confuse our users as it doesn't match our current sorting.
To avoid confusion, let's change it so that we can manually order each item in the cmd folder. This will be similar to how we order the mkdocs.yml file. We can convert the commands section from the mkdocs.yml file to json and replace the auto-generate section in sidebar.js with the new commands section.
For more information on how to implement sidebar items, you can check out https://docusaurus.io/docs/sidebar/items.
Note!
When making a PR for this issue, make sure you target the branch docs-migration.

Related to #4396

@pnp/cli-for-microsoft-365-maintainers should we do this only for command pages, or also for all other sections (about, sample scripts, concepts, user guide, ...)?

authors: Jwaegebaert milanholemans


text:
new command: tenant report servicesusercount

Implements #1299

Coverage remained the same at 100.0% when pulling 1d64b76d08b035a150e0b68934b727646d6c17f2 on plamber:tenant-report-serviceusercount into dd73c4e5a4f1a779f3074f39052d2c664d7457d0 on pnp:dev.

Thanks @plamber! We'll go through it shortly 👍

@VelinGeorgiev: are you going to change the quotes for the outputfile as suggested in #1393?

I will. Thanks for the heads up!

Merged manually. Thank you! 👏

authors: VelinGeorgiev coveralls plamber waldekmastykarz


text:
Update Convert-WikiAndWebPartPages.ps1

Typo in -ForegroundColor Parameter on line 59

Thanks @lryanuk

authors: jansenbe lryanuk

repo: pnp/sp-dev-modernization


text:
React recently visited sites 1.16.1

Category

[ ] Bug Fix
[x] New Feature
Related issues: fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Upgraded solution to SPFx 1.16.1

merged to v3, thank you for the contribution

authors: chandaniprajapati eoverfield

repo: pnp/sp-starter-kit


text:
Dynamic Form: O evento validate não é disparado se o campo não for tocado

Reprodução

Utilize StackBlitz (https://po-ui-7rzruu.stackblitz.io) para reproduzir o bug relatado na issue.

Passos para reproduzir:

Reproduza o stackblitz enviado para simulação;
Habilite a console para acompanhar o log;
Clique diretamente no icone clean de todos os campos inputs sem tocar no conteúdo do campo;
Observe que não foi gerado nenhuma linha no console;
Recarregue a aplicação para um novo teste;
Clique primeiro no interior do campo antes de clicar no icone clean no primeiro campo;
Observe que gerou uma linha de log;
No segundo campo, apague o conteúdo usando o backspace do teclado;
Observe que gerou mais uma linha de log;

Qual o comportamento atual?
O evendo validate só é disparado de o campo for tocado antes de clicar no icone clean.
Que comportamento você esperava ver?
Que o evendo validate seja disparado quando clicar no icone clean, independente se o campo foi tocado ou não.
Ambiente

PO UI: 15.1.0
Angular: 15.0.5
Browser(s):

[x] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari
[ ] IE 11
[ ] Outros

Operating System:

[x] Windows
[ ] macOS
[ ] Ubuntu
[ ] Outros

Observações
Tempo de Resposta PO UI --> Em até 7 dias úteis.
Tempo de Retorno Solicitante --> 35 dias corridos
Issues sem retorno do solicitante por mais de 35 dias corridos serão encerradas.

Bom Dia @wsteixeira, tudo bem?
Obrigado por reportar, em breve iremos analisar e retornar uma resposta.
Attr.

Olá @alinelariguet @anliben,
Já atualizei o stackblitz para versão 17.2.3 do Angular e versão 17.6.0 do PO-UI.

@wsteixeira obrigado novamente pela contribuição!
Esta na fila de Code review.

authors: anliben jnrpalma wsteixeira

repo: po-ui/po-angular


text:
セルフホストできない

パッケージリポジトリに poac の依存パッケージが存在しないため， poac に対して poac install を行うとコケる．
不足パッケージ

[ ] boost/property_tree
[ ] boost/filesystem
[ ] boost/range
[ ] boost/algorithm
[ ] boost/foreach
[ ] boost/dynamic_bitset
[ ] boost/beast
[x] ~cpp-shell-cmd~

パッケージ頑張ります (成果報告会が終わったら...)
cpp-shell-cmdは依存関係から削除しました．-> d621f5df5afe2a41d70a740c04409b656fa1f619

こう，#93 でCygwinユーザー向けのビルドができることは確認したけど，たぶん現状だとpoacでセルフホストしようとしたときにコケる(はずな)ので，パッケージが揃えば確認と修正ができるなぁという…
当座CMake使ってビルドできればそれで良い，ということであればREADMEにCygwinユーザー向けの注釈を加えるPRを飛ばします．(これは本質的な解決ではないですし，Cygwinを積極的にサポートするのかは存じませんが…)

とりあえずは，最終的にはバイナリ配布を行う予定なのでCMakeでビルドできればそれで良いと思っています．
ですので，PR頂けるのは非常にありがたいです！

#100 で追記のPR飛ばしました．

repo: poacpm/poac


text:
Pock crashes when mac closed

Describe the bug
Whenever I close my macbook pro (thus putting it to sleep), Pock will crash 9/10 times.
When I open back my macbook, pock will be gone and the touchbar empty, having to start it again
Expected behavior
Pock to restore when opening the macbook again
Crashlog
Process:               Pock [11462]
Path:                  /Applications/Pock.app/Contents/MacOS/Pock
Identifier:            com.pigigaldi.pock
Responsible:           Pock [11462]
3   com.pigigaldi.pock            	0x000000010a751d51 0x10a692000 + 785745
4   com.pigigaldi.pock            	0x000000010a7397aa 0x10a692000 + 685994
5   com.pigigaldi.pock            	0x000000010a71db48 0x10a692000 + 572232
6   com.pigigaldi.pock            	0x000000010a7286ef 0x10a692000 + 616175
9   com.pigigaldi.pock            	0x000000010a699519 0x10a692000 + 29977
2   com.pigigaldi.pock            	0x000000010a7411fa 0x10a692000 + 717306
       0x10a692000 -        0x10a781ff7 +com.pigigaldi.pock (0.8.1 - 5) <3C9178B3-70D5-37B0-B16A-8CA1AC536AD9> /Applications/Pock.app/Contents/MacOS/Pock
       0x10a7e8000 -        0x10a7fffff +org.cocoapods.Defaults (4.1.0 - 1) <282A7E9D-3868-39EA-A6AB-0B9A351F3F25> /Applications/Pock.app/Contents/Frameworks/Defaults.framework/Versions/A/Defaults
       0x10a83f000 -        0x10a846ff7 +org.cocoapods.LoginServiceKit (2.2.0 - 1) <15D03403-4EE2-3DBE-82BE-62DDB0909EAD> /Applications/Pock.app/Contents/Frameworks/LoginServiceKit.framework/Versions/A/LoginServiceKit
       0x10a860000 -        0x10a86ffff +org.cocoapods.Magnet (3.2.0 - 1) <91ACEF97-B269-357E-B13F-1A242B05C3D3> /Applications/Pock.app/Contents/Frameworks/Magnet.framework/Versions/A/Magnet
       0x10a8a1000 -        0x10a8b8fff +org.cocoapods.PockKit (0.2.0 - 1) <D8EFB4F9-1A0E-383D-9FA2-888DC0A1E555> /Applications/Pock.app/Contents/Frameworks/PockKit.framework/Versions/A/PockKit
       0x10a90b000 -        0x10a926ff7 +org.cocoapods.Preferences (2.2.0 - 1) <E4949E2C-D7B7-3356-9F30-233901759203> /Applications/Pock.app/Contents/Frameworks/Preferences.framework/Versions/A/Preferences
       0x10a98e000 -        0x10a9a1fff +org.cocoapods.Sauce (2.1.0 - 1) <B2FC4A4E-783A-38BB-97DB-5AEFF03E203D> /Applications/Pock.app/Contents/Frameworks/Sauce.framework/Versions/A/Sauce
       0x10a9c7000 -        0x10a9dafff +org.cocoapods.SnapKit (5.0.1 - 1) <27EBC8F6-7B91-381B-BD87-443B4253DBC7> /Applications/Pock.app/Contents/Frameworks/SnapKit.framework/Versions/A/SnapKit
       0x10aa27000 -        0x10aa3eff7 +org.cocoapods.Zip (2.1.1 - 1) <11C983F1-4BC3-396D-BB3F-69ABD26F4C2D> /Applications/Pock.app/Contents/Frameworks/Zip.framework/Versions/A/Zip
       0x10e3f9000 -        0x10e40cff7 +com.pigigaldi.pock.Status (1.0 - 1) <AEA6B1C5-ABEC-34E4-A7D4-DD670108F2A3> /Users/USER/Library/Application Support/Pock/*/Status
       0x10e420000 -        0x10e42ffff +com.pigigaldi.pock.ControlCenter (1.0 - 1) <BEDD1EE4-2CFE-304B-BACA-ABFE5F21EAEA> /Users/USER/Library/Application Support/Pock/*/ControlCenter
       0x10e454000 -        0x10e45bff7 +com.pigigaldi.pock.Weather (1.0 - 1) <AF759D71-D7C4-3E33-9557-7BD71FC4D51B> /Users/USER/Library/Application Support/Pock/*/Weather
       0x10e4ce000 -        0x10e4ddfff +com.pigigaldi.pock.NowPlaying (1.0 - 1) <E44FA794-C903-3446-A151-0F7D6EC2773F> /Users/USER/Library/Application Support/Pock/*/NowPlaying
       0x10e4f3000 -        0x10e4fafff +com.pigigaldi.pock.Esc (1.0 - 1) <53129EC7-560A-3AA1-B693-C62EFBE7BA00> /Users/USER/Library/Application Support/Pock/*/Esc
       0x10e509000 -        0x10e54cff7 +com.pigigaldi.pock.Dock (1.1 - 8) <A754F8CC-6476-3BCD-BD34-D528F5063706> /Users/USER/Library/Application Support/Pock/*/Dock

All these crashlogs are the same

Versions:

macOS version: 10.14.6
Pock version:  0.8.1-5

Also while I'm at it, pock is amazing and thank you for all the work !! <3

I'm having a similar issue as well. However I'm on macOS 11.2.3 and I'm on the most recent update for pock. Are there any tips to keep pock running and have it open automatically when I open my mac?

I'm having a similar issue as well. macOS version: 10.16.7 and Pock version: 0.8.1-5

I'm having a similar issue as well. However I'm on macOS 11.2.3 and I'm on the most recent update for pock. Are there any tips to keep pock running and have it open automatically when I open my mac?

there sorta is a fellow user made this: https://github.com/pock/pock/issues/454#issuecomment-821913911

I'm having a similar issue as well. However I'm on macOS 11.2.3 and I'm on the most recent update for pock. Are there any tips to keep pock running and have it open automatically when I open my mac?

there sorta is a fellow user made this: #454 (comment)

Thank you !

Similar issue here on 11.4.
If it doesn't crash it will just start using up CPU till I quit pock.

repo: pock/pock


text:
Highlight foo

done

repo: pocke/iro


text:
deploy in a sub-path

Hi, I would like to deploy pocketbase to a sub-path of the domain http://<url>/admin, The nginx configuration is the following:
    location /admin {
        proxy_set_header Connection '';
        proxy_http_version 1.1;
        proxy_read_timeout 180s;

        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        rewrite /admin/(.*) /$1  break;
        proxy_redirect     off;
        proxy_pass http://localhost:8090;
    }

This only partially works, because pocketbase still makes calls against http://<url>/_/<resource>. How can I tell pocketbase it's deployed on a subpath? Setting the application url in the settings page doesn't work.
To make it work I had to add a new location to nginx, redirecting all calls to /_/ but I'd like to avoid it:
    location /_/ {
        proxy_set_header Connection '';
        proxy_http_version 1.1;
        proxy_read_timeout 180s;

        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        proxy_redirect     off;
        proxy_pass http://localhost:8090;
    }

Hi, thanks for reporting it. Indeed at the moment the prebuilt Admin UI uses an absolute path (/) as  API url address and this cannot be changed without building the ui manually.
I'll try to fix it in the next v0.4.0 release, but for now you'll have to use an additional rewrite/redirect rule as a workaround (eg. /api/... to /admin/api/...).

hey thanks for the quick reply. I'll then leave this nginx configuration or build the app in the docker-compose configuration I'm using 🖖🏼

A fix was relased in v0.3.3 -  the absolute prebuilt backend url (/) in the Admin UI was replaced with a relative one (../) so now it should send requests correctly to the sub-path deployed backend.
I've tested the fix locally, but if someone is still experiencing the same issue, please let me know and I'll investigate it further.

@tommyblue Actually the fix from v0.3.3 works only on the dev environment because I forgot that in the vite configuration we were also using a conditional base path depending whether we are building for prod or dev environment (which is why locally worked). Another fix that removes the discrepancies between the 2 environments was added in master (https://github.com/pocketbase/pocketbase/commit/6292e6cc2e0b62a62d06b98155170664d1393f64) and will be available with the next minor bugfix/feature release.

I followed @tommyblue nginx configuration and still can't make sub-path works, Do I need to anything else? Tried either nginx/apache but no luck.

@rdpascua Please open a new Q&A discussion with information about your nginx/apache configuration.

@tommyblue Actually the fix from v0.3.3 works only on the dev environment because I forgot that in the vite configuration we were also using a conditional base path depending whether we are building for prod or dev environment (which is why locally worked). Another fix that removes the discrepancies between the 2 environments was added in master (6292e6c) and will be available with the next minor bugfix/feature release.

@ganigeorgiev was that minor release released?

@tommyblue yes, but there are other quirks related to the subpath handling. I've just commented in https://github.com/pocketbase/pocketbase/discussions/1802#discussioncomment-4892902

@tommyblue Just to let you know that in v0.13.0 the subpath handling was updated and now it should work without the extra location redirects.
The only requirement for the subpath location block is to have a subpath rewrite rule.
If you are still facing issues with the subpath setup, please share your nginx config and I'll test it further.

authors: ganigeorgiev rdpascua tommyblue

repo: pocketbase/pocketbase


text:
博客 - 苹果核

姓名：gaosboy|苹果核团队
关注领域：iOS/android/无线后台建设
博客：http://pingguohe.net

高兄，名字太长啦，我觉得要么用gaosboy，要么用苹果核团队。

姓名：ICETIME17
关注领域：iOS/Swift/Python后端
博客：http://blog.csdn.net/icetime17
公众号：

authors: gaosboy icetime17 pockry

repo: pockry/mobile-frontier


text:
coordinators-improvements

Improvements:

translations added
added 'mailto' for the emails in the grid
ability to sort and search in the grid
added data to the view window
removed 'CoordinatorsGridHelper' because it is redundant

@yg1y great fix!
Could you please check the conflicts?

repo: podkrepi-bg/frontend


text:
Publishing changes from within view updates is not allowed, this will cause undefined behavior.

Description
Hi there,
I found really interesting your work and that there's definitely worth it give it a shot .
However i believe I found an issue, ViewStore.swift initialiser, objectWillChange.send() causes an undefined behaviour.
When Modifying any of the Object States changes are not published.
Sorry if in any case this is the expected behaviour on the demo project, the insides of the architecture are quite complex to my knowledge and I'm trying to get hang of it.
Keep up the great work !!

Checklist

[ ] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue.

Expected behavior
Publish state changes
Actual behavior
Does not publish state changes
Steps to reproduce

Clone repo https://github.com/pointfreeco/swift-composable-architecture.git
Build SwiftUI CaseStudies
Modify an object in any of the cases, navigate back to list

The Composable Architecture version information
built in swift-composable-architecture-main/Examples/CaseStudies
Destination operating system
iOS 16.0
Xcode version information
Xcode 14.0.1
Swift Compiler version information
No response

Hi @imediayala, this is actually a bug in SwiftUI and is easily reproducible in vanilla SwiftUI. See #1319 for more information. Luckily it seems to be fixed in Xcode 14.1 beta.
I'm going to close this issue since it's already being discussed in #1319.

Hey Brandon, thanks for letting me know.

authors: imediayala mbrandonw


text:
🛑 Pokko - au-syd1 is down

In 0cdae39, Pokko - au-syd1 (https://au-syd1.pokko.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pokko - au-syd1 is back up in e600d0a after 5 minutes.

repo: pokkocms/pokko-status