CB6 Test Case Option 1

Attach(%): 0.00 4.00 18.10 49.60 100
Pull(Ang): 0.00 1.00 2.00 3.00 4.00 5.00 6.00 7.00 8.00 9.00 10.00
force constant = 2.0 kcal/mol-A^2
Mask1 :CB6@O*
Mask2 :BUT@C*

I've added support for writing a restraints file in each directory for multiple restraints as of commit 3789959 .
See this notebook for a short example: https://gist.github.com/anonymous/e67b3edfb414e3d9e9ee860880c103f2
There are a couple quirks to iron out (like making the ranges inclusive of the last element) but I think most of the groundwork is there. We should check the restraint lines to make sure they are correct next week.

I think I am still missing some conversions. There seems to be some confusion between restraint.phase[phase]['forces'][window] and restraint.phase_forces[window] (for example) probably due to my sloppiness.

formatting comment: probably should add commas each field.
r1 = 0.0, r2 = 0.5, etc
Although haven't tested it.

Done in d2f2fed.


feat(Ads): Add support for AWS Elemental MediaTailor

Thanks @theodab !

Any documentation for this?

@cristian-atehortua I created https://github.com/shaka-project/shaka-player/pull/5803 to add a new tutorial for this.

Thanks!


Time is takes for a node to rejoin the cluster

Hey there, I am running through some tests with your test application.  Four nodes in the cluster. I terminate a single node and bring it back online and seems like the time it takes for the terminated node to rejoin the cluster and node be on the dead list is highly variable. Sometimes it will take 30 seconds, sometimes 5 minutes, sometimes never?
Maybe I am making an improper configuration?  If I query the recently terminated node it shows all nodes live, but the other 3 nodes have trouble knowing the previously terminated node is not live.
I have tried this on the main branch.  Any advice would be great. Very cool system.

Ok, so I think this has something to do with is_ready_predicate. I noticed if I add a key/value to the node that will not become active in the cluster, it will then be ready in the cluster again.

Hi @densone,
We removed the readiness logic from Chitchat on main, so unless I missed some code when performing that refactor, the is_ready_predicate should no longer exist.
Could you help me reproduce your issue? Are you running four nodes in the same process in unit tests, in 4 shells via the command line, or in your application?
Feel free to ping me on Discord.


THORN-2385: MP OpenTracing: nested spans aren't reported

Motivation
Say I have a simple JAX-RS resource like this:
@Path("/")
public class RestSimpleResource {
    @Inject
    private MyService myService;

    @GET
    public Response tracedOperation() {
        return Response.ok().entity(myService.hello()).build();
    }
}

It uses a simple service looking like this:
@ApplicationScoped
public class MyService {
    @Inject
    private Tracer tracer;

    @Traced
    public String hello() {
        tracer.activeSpan().log("Hello tracer");
        return "Hello from traced service";
    }
}

When MicroProfile OpenTracing is enabled, a single invocation
of the JAX-RS endpoint should produce a single trace with two spans:
one span for the JAX-RS endpoint itself (because JAX-RS endpoints
are traced automatically per MP OpenTracing), and a nested span
for the service invocation (because it's @Traced).
This used to work up to Thorntail 2.2.1.Final, but doesn't work
since 2.3.0.Final. The culprit seems to be this change to SmallRye
OpenTracing: https://github.com/smallrye/smallrye-opentracing/pull/25
After this change, the interceptor for handling the @Traced calls
no longer comes from SmallRye OpenTracing itself, but from OpenTracing
Java Interceptors project. The necessary integration work in Thorntail
wasn't done when updating to the new SmallRye OpenTracing version.
Modifications
Properly integrate the new SmallRye OpenTracing version. Specifically,
the OpenTracing Java Interceptors artifact needs to be added to the
SmallRye OpenTracing module.xml. Also the interceptor itself
needs to be registered in the CDI extension.
Result
The @Traced interceptor works correctly.

[x] Have you followed the guidelines in our Contributing document?
[x] [v2] Have you created a JIRA and used it in the commit message?
[ ] [v4] Have you created a GitHub Issue and used it in the commit message?
[x] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[ ] Have you built the project locally prior to submission with mvn clean install?

@pavolloffay could you please take a look? Thanks!

I think you are right the CDI interceptor is not being invoked - so the span for CDI is missing.
I think @jpkrohling moved the interceptor to the separate library. I am not sure what is required to register it in thorntail. In smallrye TCK the interceptor is automatically discovered https://github.com/smallrye/smallrye-opentracing/pull/25/files#diff-1f073f0e30a725752136b28b30d44a59L19

@jpkrohling I am wondering if it could be also broken in WF.

Yea, I've seen that. Just adding the opentracing-interceptors artifact didn't help, I had to register the interceptor manually.  I added a test here: https://github.com/rhoar-qe/thorntail-test-suite/commit/4fa31cbb4b0e49141848fe5f8f48d52ffc5cf902

I am wondering if it could be also broken in WF.

It might: WF seems to be using 1.1.1.

Wow, the MP OpenTracing TCK fails, this probably isn't the best fix.

Had to fix the TCK runner, as it added all of io.opentracing to the deployment, which 1. meant that the interceptor is registered twice, causing all the nice TCK failures; 2. isn't how it works in real applications. The TCK, however, doesn't need all of io.opentracing, just io.opentracing.tracerresolver and io.opentracing.mock, so the fix was pretty simple.

@pavolloffay @jpkrohling FYI this very likely will affect WFLY as they currently register the old interceptor here.


How to create map with Gmapping

move_base.xml error when I use Gmapping. How to fix this problem?
[ INFO] [1612257815.699039618, 1934.027000000]: Name is SBPLLatticePlanner terminate called after throwing an instance of 'SBPL_Exception'   what():  ERROR: failed to read in motion primitive file [move_base_node-1] process has died [pid 734, exit code -6, cmd /opt/ros/melodic/lib/move_base/move_base map:=/map odom:=/odom marker:=move_base_node/DWBLocalPlanner/markers __name:=move_base_node __log:=/home/its/.ros/log/7500f83e-6533-11eb-a8ca-f8ac65f551a4/move_base_node-1.log]. log file: /home/its/.ros/log/7500f83e-6533-11eb-a8ca-f8ac65f551a4/move_base_node-1*.log
thank you for reply

Probably the resolution of your map and the resolution of your *.mprim file doesn't match. See here: https://github.com/ros-planning/navigation_experimental/issues?q=is%3Aissue+failed+to+read+in+motion+primitive+file

I'm closing this because of lack of activity. Feel free to reopen if you have anything to add!


accept list of solvers in MIOPEN_DEBUG_FIND_ONLY_SOLVER

This PR allows MIOPEN_DEBUG_FIND_ONLY_SOLVER to comprise of multiple solvers separated by semicolon. For example, when debugging issues in frameworks, one needs multiple solvers (different directions). This PR enables such a functionality.

This PR allows MIOPEN_DEBUG_FIND_ONLY_SOLVER to comprise of multiple solvers separated by semicolon. For example, when debugging issues in frameworks, one needs multiple solvers (different directions). This PR enables such a functionality.

@JehandadKhan could you add the use case and option in
https://rocmsoftwareplatform.github.io/MIOpen/doc/html/DebugAndLogging.html
The documentation has not been updated for a while, this new feature could be very useful. Thanks!


Time on pd.cut in the salinity cleaning is taking 50% of the runtime

Find a different solution

Fixed


Optimize SVG files

First of all, thanks for these icons! I was wondering if it is possible to add optimized versions of the SVG icons - currently they contain a lot of things that can be removed, like Illustrator comments and doctype. Using a tool like svgo this can easily be achieved. Would be happy to make a PR too!

thanks for the suggestion , i was very excited to release this , looks like i forgot to look at the small details. i will look into svgo , does it remove the unnecessary stuff?


fix mobilenumber input type width

What is the context of this PR?
The mobilenumber type input field is only wide enough for 8 characters so will not fit a full mobile number especially if you suffix it with "+44". This will up the width to 15
How to review

Open test_multiple_answers schema
Enter "+44 0000 000000" into the mobile number field and see that the mobile number field is now wide enough for a full mobile number

Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

 Mobilenumber input type not wide enough for full mobile number

Was it like this in census 🤔

I don't think so, I did some work on the DS a while ago to make the width value match up with the number of characters you expect in the input which is why this is now wrong but I think that was after census


I cannot get the IP address

When i run: "docker inspect -f "{{ .NetworkSettings.Networks.nat.IPAddress }}" myapp"
i get "<no value>"
.
All previous steps are done without issue.
Do I need to modify that command, or is there another way to get the IP address?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e38de4f3-3343-74cd-103a-fe12846ce7c3
Version Independent ID: 6bf65efb-13eb-15d9-5aac-9d5cf9c1aa96
Content: Build a Sample App
Content Source: virtualization/windowscontainers/quick-start/building-sample-app.md
Service: windows-containers
Product: windows-containers
GitHub Login: @cwilhit

I can visit the website via "http://localhost:5000" under the condition that "docker run -d -p 5000:80 myapp" is issued beforehand.
By the way, sometimes your docker instance dosen't enroll himself into NAT network. On the contrary, it resides in "bridge" network. Thus you can read the ip address via command "docker inspect -f "{{ .NetworkSettings.Networks.bridge.IPAddress }}" myapp" although you still can't vist the website via the ip address.

They don't work, I can't find any addresses.
docker inspect -f "{{ .NetworkSettings }}" myapp

It seems to use nat, but both methods above are not valid and I can't get an address.

@he852100 if you're running the command that maps the ports correctly, you shouldn't have to find the IP address of the container--you can just go to http://localhost:5000 (or whichever port it is you chose to map).
Otherwise, you can use the following command to get the container's IP address:
docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' myapp

They are empty and inaccessible.
C:\Users\Administrator\Virtualizatidocker ps -ltion\windows-container-samples\asp-net-getting-started>
CONTAINER ID        IMAGE               COMMAND                    CREATED             STATUS                      PORTS               NAMES
dcff2bf5c7ab        my-asp-app          "c:\\windows\\system32…"   11 minutes ago      Exited (0) 11 minutes ago                       myapp
PS C:\Users\Administrator\Virtualization-Documentation\windows-container-samples\asp-net-getting-started> docker inspect -f '{{range .Network
Settings.Networks}}{{.IPAddress}}{{end}}' myapp

PS C:\Users\Administrator\Virtualization-Documentation\windows-container-samples\asp-net-getting-started>

Windows 10, docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' myapp returns a blank value and localhost:[port] can't be reached (ERR_CONNECTION_REFUSED). Docker desktop enabled in firewall. How to fix?

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


script/adjust: preserve all comments in requirements

Before submitting

[x] Was this discussed/agreed via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
Did you make sure to update the docs?
[x] Did all existing and newly added tests pass locally?

What does this PR do?
When we ran the adjusted version in our CI, it removed all comments (also # strict directive), which yielded wrongly preserving upper bounds...
PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues, there's a high chance it will not be merged.

Damm windows has a line ending that I am not bale to drop, so the final replacement has empty line after each normal line...


Test ruby install time with 2.4.1 on all repos

Basically sensu 0.29+ uses ruby 2.4 we need to start seeing what breaks horribly and prep for bumping sensu-plugin related to: #26,
I had started going through them ad-hoc for the last few weeks after merging requests but I think we need a bit more cadence on this so I pulled the list of remaining plugins and should circle back and update as we do this to bring some sanity to this madness.
remaining plugins:

[x] sensu-plugins-ansible
[x] sensu-plugins-apache
[x] sensu-plugins-aws
[ ] sensu-plugins-beanstalk
[ ] sensu-plugins-bigpanda
[ ] sensu-plugins-campfire
[ ] sensu-plugins-cassandra
[ ] sensu-plugins-cgroups
[ ] sensu-plugins-chatwork
[ ] sensu-plugins-clockworksms
[ ] sensu-plugins-conntrack
[x] sensu-plugins-consul
[ ] sensu-plugins-couchdb
[x] sensu-plugins-cpu-checks
[ ] sensu-plugins-cucumber
[ ] sensu-plugins-dns
[ ] sensu-plugins-docker
[x] sensu-plugins-elasticsearch
[ ] sensu-plugins-erlang
[ ] sensu-plugins-etcd
[ ] sensu-plugins-execute
[ ] sensu-plugins-filesystem-checks
[ ] sensu-plugins-flowdock
[ ] sensu-plugins-freeradius
[ ] sensu-plugins-gearman
[ ] sensu-plugins-github
[ ] sensu-plugins-gluster
[ ] sensu-plugins-google-spreadsheet
[ ] sensu-plugins-gpg
[ ] sensu-plugins-graylog
[x] sensu-plugins-haproxy
[ ] sensu-plugins-hbase
[ ] sensu-plugins-hipchat
[ ] sensu-plugins-http
[ ] sensu-plugins-hubot
[ ] sensu-plugins-imap
[ ] sensu-plugins-influxdb
[x] sensu-plugins-io-checks
[ ] sensu-plugins-ipmi
[ ] sensu-plugins-ipvs
[ ] sensu-plugins-jenkins
[ ] sensu-plugins-kannel
[ ] sensu-plugins-kubernetes
[x] sensu-plugins-load-checks
[x] sensu-plugins-logs
[ ] sensu-plugins-lvm
[ ] sensu-plugins-lxc
[ ] sensu-plugins-mailgun
[x] sensu-plugins-memory-checks
[ ] sensu-plugins-mesos
[ ] sensu-plugins-mongodb
[ ] sensu-plugins-monit
[ ] sensu-plugins-nbzget
[ ] sensu-plugins-network-checks
[ ] sensu-plugins-newrelic
[x] sensu-plugins-nginx
[x] sensu-plugins-ntp
[ ] sensu-plugins-nvidia
[ ] sensu-plugins-openldap
[ ] sensu-plugins-openstack
[ ] sensu-plugins-openvpn
[ ] sensu-plugins-opsgenie
[x] sensu-plugins-pagerduty
[ ] sensu-plugins-percona
[ ] sensu-plugins-php-fpm
[ ] sensu-plugins-ponymailer
[ ] sensu-plugins-postfix
[ ] sensu-plugins-postgres
[ ] sensu-plugins-process-checks
[ ] sensu-plugins-puppet
[ ] sensu-plugins-pushover
[x] sensu-plugins-rabbitmq
[ ] sensu-plugins-raid-checks
[ ] sensu-plugins-resque
[ ] sensu-plugins-rethinkdb
[ ] sensu-plugins-riak
[ ] sensu-plugins-rspec
[x] sensu-plugins-sensu
[x] sensu-plugins-serverspec
[x] sensu-plugins-sftp
[ ] sensu-plugins-skyline
[ ] sensu-plugins-sms
[x] sensu-plugins-snmp
[ ] sensu-plugins-ssl
[ ] sensu-plugins-strongswan
[ ] sensu-plugins-tripwire
[ ] sensu-plugins-twemproxy
[x] sensu-plugins-twilio
[ ] sensu-plugins-twitter
[x] sensu-plugins-ubiquiti
[x] sensu-plugins-uchiwa
[ ] sensu-plugins-unicorn
[ ] sensu-plugins-ups
[x] sensu-plugins-uptime-checks
[ ] sensu-plugins-varnish
[ ] sensu-plugins-victorops
[x] sensu-plugins-vmstats
[x] sensu-plugins-wordpress
[x] sensu-plugins-xen
[x] sensu-plugins-zendesk
[x] sensu-plugins-zookeeper

There's some overlap between this list and the plugins that need to have the hard coded sensu-plugin 1.2.0 dep removed. Can you mark them off on https://github.com/sensu-plugins/sensu-plugins-feature-requests/projects/1 if any of those are updated.

@eheydrick I have not seen them but we are gonna be bumping everything to 2.x shortly anyways so it seems like a moot point to update both and then update again. Just my 2 cents, if you feel there is value I am ok with doing it, it just slows down the process as its one more thing to check and update.

@portertech thanks for the help, please do them as PRs with your travis changes so that we can keep track of them all here and avoid committing to master directly.

Some test results.
GOOD: etcd, execute, filesystem-checks, flowdock
BAD:
etcd
root@86f6a33456b3:/# sensu-install -p etcd
[SENSU-INSTALL] installing Sensu plugins ...
[SENSU-INSTALL] determining if Sensu gem 'sensu-plugins-etcd' is already installed ...
false
[SENSU-INSTALL] Sensu plugin gems to be installed: ["sensu-plugins-etcd"]
[SENSU-INSTALL] installing Sensu gem 'sensu-plugins-etcd'
Building native extensions.  This could take a while...
Successfully installed unf_ext-<IP_ADDRESS>
Fetching: unf-0.1.4.gem (100%)
Successfully installed unf-0.1.4
Fetching: domain_name-0.5.20170404.gem (100%)
Successfully installed domain_name-0.5.20170404
Fetching: http-cookie-1.0.3.gem (100%)
Successfully installed http-cookie-1.0.3
Fetching: mime-types-2.99.3.gem (100%)
Successfully installed mime-types-2.99.3
Fetching: netrc-0.11.0.gem (100%)
Successfully installed netrc-0.11.0
Fetching: rest-client-1.8.0.gem (100%)
Successfully installed rest-client-1.8.0
Fetching: mixlib-log-1.7.1.gem (100%)
Successfully installed mixlib-log-1.7.1
Fetching: etcd-0.3.0.gem (100%)
Successfully installed etcd-0.3.0
Fetching: sensu-plugins-etcd-1.0.0.gem (100%)
You can use the embedded Ruby by setting EMBEDDED_RUBY=true in /etc/default/sensu
Successfully installed sensu-plugins-etcd-1.0.0
10 gems installed
[SENSU-INSTALL] successfully installed Sensu plugins: ["sensu-plugins-etcd"]

root@86f6a33456b3:/# /opt/sensu/embedded/bin/check-etcd.rb --help
Usage: /opt/sensu/embedded/bin/check-etcd.rb (options)
    -a, --all                        check health of all etcd members
        --ca CA                      SSL CA file
        --cert CERT                  client SSL cert
        --insecure                   change SSL verify mode to false
        --key KEY                    client SSL key
        --passphrase PASSPHRASE      passphrase of the SSL key
    -p, --port PORT                  Etcd port, defaults to 2379
    -h, --host HOST                  Etcd host, defaults to localhost
        --ssl                        use HTTPS (default false)
root@86f6a33456b3:/# /opt/sensu/embedded/bin/check-flannel-subnet-count.rb --help
Usage: /opt/sensu/embedded/bin/check-flannel-subnet-count.rb (options)
        --ca CA                      SSL CA file
        --cert CERT                  client SSL cert
        --insecure                   change SSL verify mode to false
        --key KEY                    client SSL key
        --passphrase PASSPHRASE      passphrase of the SSL key
    -p, --port PORT                  Etcd port, defaults to 2379
    -h, --host HOST                  Etcd host, defaults to localhost
        --ssl                        use HTTPS (default false)
    -w, --warn COUNT                 Warn when number of subnets exceeds the max minus this threshold
root@86f6a33456b3:/# /opt/sensu/embedded/bin/check-etcd-peer-count.rb --help
Usage: /opt/sensu/embedded/bin/check-etcd-peer-count.rb (options)
        --ca CA                      SSL CA file
        --cert CERT                  client SSL cert
        --insecure                   change SSL verify mode to false
        --key KEY                    client SSL key
        --passphrase PASSPHRASE      passphrase of the SSL key
    -c, --count NUMBER               Number of expected etcd peers (required)
    -p, --port PORT                  Etcd port, defaults to 2379
    -h, --host HOST                  Etcd host, defaults to localhost
        --ssl                        use HTTPS (default false)

execute
root@86f6a33456b3:/# sensu-install -p execute
[SENSU-INSTALL] installing Sensu plugins ...
[SENSU-INSTALL] determining if Sensu gem 'sensu-plugins-execute' is already installed ...
false
[SENSU-INSTALL] Sensu plugin gems to be installed: ["sensu-plugins-execute"]
[SENSU-INSTALL] installing Sensu gem 'sensu-plugins-execute'
Fetching: sensu-plugin-1.2.0.gem (100%)
Successfully installed sensu-plugin-1.2.0
Fetching: systemu-2.6.5.gem (100%)
Successfully installed systemu-2.6.5
Fetching: sensu-plugins-execute-0.0.2.gem (100%)
You can use the embedded Ruby by setting EMBEDDED_RUBY=true in /etc/default/sensu
Successfully installed sensu-plugins-execute-0.0.2
3 gems installed
[SENSU-INSTALL] successfully installed Sensu plugins: ["sensu-plugins-execute"]

root@86f6a33456b3:/# /opt/sensu/embedded/bin/execute.rb --help
Usage: /opt/sensu/embedded/bin/execute.rb (options)

filesystem-checks
root@86f6a33456b3:/# sensu-install -p filesystem-checks
[SENSU-INSTALL] installing Sensu plugins ...
[SENSU-INSTALL] determining if Sensu gem 'sensu-plugins-filesystem-checks' is already installed ...
false
[SENSU-INSTALL] Sensu plugin gems to be installed: ["sensu-plugins-filesystem-checks"]
[SENSU-INSTALL] installing Sensu gem 'sensu-plugins-filesystem-checks'
Fetching: sensu-plugins-filesystem-checks-1.0.0.gem (100%)
You can use the embedded Ruby by setting EMBEDDED_RUBY=true in /etc/default/sensu
Successfully installed sensu-plugins-filesystem-checks-1.0.0
1 gem installed
[SENSU-INSTALL] successfully installed Sensu plugins: ["sensu-plugins-filesystem-checks"]

root@86f6a33456b3:/# /opt/sensu/embedded/bin/check-checksums.rb --help
Usage: /opt/sensu/embedded/bin/check-checksums.rb (options)
    -f, --files FILES                Comma separated list of files to check. (required)
    -h, --hash SHA2HASH              The hash these files must hash as. If unspecified the files will be compared to the first file.
    -H, --hashfile SHA2HASHFILE      The file containing the hash these files must hash as.
    -w, --warn-only                  Warn instead of critical if they don't match
root@86f6a33456b3:/# /opt/sensu/embedded/bin/check-dir-count.rb --help
Usage: /opt/sensu/embedded/bin/check-dir-count.rb (options)
    -c, --critical NUM               Critical if count of files is greater than provided number (required)
    -d, --dir DIR                    Directory to count files in (required)
    -w, --warning NUM                Warn if count of files is greater than provided number (required)
root@86f6a33456b3:/# /opt/sensu/embedded/bin/check-dir-size.rb --help
Usage: /opt/sensu/embedded/bin/check-dir-size.rb (options)
    -c, --critical SIZE_IN_BYTES     The size (in bytes) of the directory where CRITICAL is raised
    -d /path/to/directory,           Directory to stat (full path not including trailing slash) (required)
        --directory
    -p, --du-path /path/to/du        The path to the `du` command
        --ignore-missing             Do not throw CRITICAL if the directory is missing
    -w, --warn SIZE_IN_BYTES         The size (in bytes) of the directory where WARNING is raised
root@86f6a33456b3:/# /opt/sensu/embedded/bin/check-fs-writable.rb --help
Usage: /opt/sensu/embedded/bin/check-fs-writable.rb (options)
    -a, --auto-discover              Auto discover mount points via fstab
        --debug                      Print debug statements
    -d, --directory DIRECTORY        Directory to check for writability
root@86f6a33456b3:/# /opt/sensu/embedded/bin/check-mtime.rb --help
Usage: /opt/sensu/embedded/bin/check-mtime.rb (options)
    -c, --critical SECONDS           Critical if mtime greater than provided age in seconds
    -f, --file FILE                  File to check last modified time
    -o, --ok-no-exist                OK if file does not exist
    -z, --ok-zero-size               OK if file has zero size
    -w, --warning SECONDS            Warn if mtime greater than provided age in seconds
root@86f6a33456b3:/# /opt/sensu/embedded/bin/check-tail.rb --help
Usage: /opt/sensu/embedded/bin/check-tail.rb (options)
    -a, --absent                     Fail if pattern is absent
    -f, --file FILE                  Path to file
    -l, --lines LINES                Number of lines to tail
    -P, --pattern PAT                Pattern to search for
    -w, --warn-only                  Warn instead of critical on match

flowdock (handler)
root@86f6a33456b3:/# sensu-install -p flowdock
[SENSU-INSTALL] installing Sensu plugins ...
[SENSU-INSTALL] determining if Sensu gem 'sensu-plugins-flowdock' is already installed ...
false
[SENSU-INSTALL] Sensu plugin gems to be installed: ["sensu-plugins-flowdock"]
[SENSU-INSTALL] installing Sensu gem 'sensu-plugins-flowdock'
Fetching: multi_xml-0.6.0.gem (100%)
Successfully installed multi_xml-0.6.0
Fetching: httparty-0.15.5.gem (100%)
When you HTTParty, you must party hard!
Successfully installed httparty-0.15.5
Fetching: multi_json-1.12.1.gem (100%)
Successfully installed multi_json-1.12.1
Fetching: flowdock-0.7.0.gem (100%)
Successfully installed flowdock-0.7.0
Fetching: sensu-plugins-flowdock-0.1.1.gem (100%)
You can use the embedded Ruby by setting EMBEDDED_RUBY=true in /etc/default/sensu
Successfully installed sensu-plugins-flowdock-0.1.1
5 gems installed
[SENSU-INSTALL] successfully installed Sensu plugins: ["sensu-plugins-flowdock"]

root@86f6a33456b3:/# /opt/sensu/embedded/bin/handler-flowdock.rb --help
Usage: /opt/sensu/embedded/bin/handler-flowdock.rb (options)
    -j, --json_config JsonConfig     Config Name

@majormoses I will create PRs with the travis.yml updates for the plugins above, associating them with this issue 👍

@majormoses @eheydrick I only had enough time today to smash on those 4, please let me know if the PRs are sufficient.

@portertech for sure I will review them shortly I will probably merge and release the ones that have breaking changes tonight as I don't believe in functional changes not being released as this incurs unneeded risk.

@majormoses sensu-plugins-skyline can be removed from the list as it is no longer maintained :)

@Evesy @thomasriley you guys are awesome! We are over 1/2 way done with install testing. There is no way I would have gotten around to all this on my own this quickly. Sounds like we are getting close to needing some decisions on runtime testing requirements so I can scope out that work before we get done here. I will start that discussion internally and update that issue.

@majormoses sensu-plugins-varnish can be checked off the list because it's already been done by yourself :) However as I already forked it I took the opportunity to remove some redundant code from the Rakefile.

@majormoses the plugins below have already been done so can be checked off:
sensu-plugins-chatwork
sensu-plugins-docker
sensu-plugins-flowdock
sensu-plugins-riak
sensu-plugins-twemproxy

rethinkdb has had changes but is blocked on release because of this: https://github.com/sensu-plugins/sensu-plugins-rethinkdb/issues/2

I think there might be some caching issues with the list items, I see ones unchecked I know I previously checked off...

Are we really down to just 1 more plugin out of this list?! It looks like sensu-plugins-percona is the last (accepting the blocked rethinkdb one)?!

yes, we are gonna move to runtime testing but we need to figure out what that means. I think we should move on and worry about percona separately since it's blocked by upstream issues.


Failure during Plot <<press any key to continue…>>

Hi Guys
I try to explain as best as possible
I started to plot with MadMax Plot.
Sometimes, radomically, it stopped without any reason ad appear at the bottom press any key to continue
If I press a Kay, the consolle desappear
I plot using Windows 10.
Someone know the reasons?
Thanks a lot

•I use 110Gb of RamDisk
•Ryzen 5800X
Can be a SSD trouble?
Now the pc it’s not overclocked
Only using the XMP profile

Short answer - unstable Ram.
My RAM passed memtest for days but I needed to change comand rate from 1T to 2T and increase voltage to stop Mad max from crashing.


SQL Server Profiler -- cannot set property 'actionBarContext' of undefined

Azure Data Studio Version:Version: 1.17.1 (user setup)
Commit: 814ce88c41e0daaca89afed8b184e795057a6f9d
Date: 2020-04-30T00:16:35.943Z
VS Code: 1.42.0
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

Steps to Reproduce:

Open Azure Data Studio
Connect to database
ALT+P

This extension worked fine for me yesterday. I have uninstalled/disabled the extension multiple times today trying to get it to work. Last resort I guess will be to uninstall Azure Data Studio and reinstall it.

@JStanl I think this is a duplicate of https://github.com/microsoft/azuredatastudio/issues/10282.  To workaround the issue you can open a folder or close the currently open folder, which will reset the HotExit document list.  The issue is fixed in the latest insider build and the fix will ship in May release next week.  Sorry for the inconvenience.  Please let me know if the workaround doesn't work.

@JStanl , please reactivate the issue if you are still seeing the issue after May release.

Reopening this since @ymkumar is apparently running into this issue with the 1.20.1 build.
@alanrenmsft did we ever figure out what the issue was here?
@ymkumar Please include your ADS version info here for confirmation

here is the ADS version

@ymkumar Please follow what Karl pointed out in the other issue: https://github.com/microsoft/azuredatastudio/issues/10492#issuecomment-672090036

IIRC, the issue was bad state cached by an earlier version, so the problem can repro in any future ADS build if that bad state is still cached.  Open\closing a folder should reset the "open document" cache.  Worst case, the entire application cache can be removed but that would lose all application state and revert to a "first launch" state.

worked with @ymkumar offline and the problem has been solved for him.
steps to resolve the issue for whoever run into this:

In the main menu, under "File", select 'Open Folder'

Pick a folder and press "Select Folder"

close all editors and restart Azure Data Studio


[SwipeableView] Using willChange sparingly

Hey, Thanks for this great project, all my respect!
I am using React-Swipeable-Views to build a Web App. I noticed that will-change is always on container react-swipeable-view-container, and I think maybe this could be optimized by adding will-change when touchstart triggered, and removing when touchend triggered.
Checkout this MDN documentation,

@oliviertassinari Thank you very much for the explanations, I got it.


Hover Event/Function menu items

Hi, it would be possible to add a function to execute when the commands are hovered, as is the case for select.
ex.
  /*
   * A function to execute when the command is hovered.
   */
  hover?: ((element: cytoscape.SingularData) => void) | undefined;

Thank you

That sounds like a great idea for a feature.  Would you put up a pull request with your proposal?

I already did, but I didn't associate it with the issue.
Il giorno mar 10 gen 2023 alle ore 17:49 Max Franz @.***>
ha scritto:

That sounds like a great idea for a feature. Would you put up a pull
request with your proposal?
—
Reply to this email directly, view it on GitHub
https://github.com/cytoscape/cytoscape.js-cxtmenu/issues/135#issuecomment-1377556937,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI45ECETBOV2ODF5HI3L5FTWRWHJBANCNFSM6AAAAAAR6GBPDQ
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Great, thanks.
Ref: #137

Released as 3.5.0.  Thanks for the PR


fitBounds round fix

I think this is the right fix for the fitBounds jumping bug.

The jump actually happens only inside the snap part (with zoomSnap: 0, there is no jumping).
It is because of the Math.floor function: zoom level 14.9999 becomes 14.
This fix rounds to the nearest snap level, if within 1% of it. So 14.9999 becomes 15 and then floor and ceil doesn't make a jump.

Yes, this is a much better approach! :+1:


Create stale.yaml

Creating a stalebot workflow that will check every day for stale PRs older than 180 days, then close any that were labeled 'stale' after another 15 days.
It exempts any PRs assigned to the dependency graph dev team.
This will also need a PAT created, and stored as a repo secret with the name STALE_BOT

This will also need a PAT created, and stored as a repo secret with the name STALE_BOT

updated the workflow definition to use the default github token, with explicit scopes to write PRs


JSON to LVObject fails to deserialize Enum

When deserializing a class that contains an Enum, the value of the Enum is never going to change.
The Generic Object Serializer assumes that the data type returned by JSONtext always matches the data type provided as input. However, when the data string does not match exactly with the original type info, then the resulting element is going to be wrong.

In the case of Enums, the value returned by JSONtext is the index of the element (I32). A standard Enum, however, is only 16 bits wide.

When the data string returned by JSONtext is combined with the type info from the Enum, the lower 16 bits are truncated, so the resulting value is zero.
This may affect other numeric types as well.
This can probably be solved by casting the value returned by JSONtext to the input type before reading the data string.
Nevermind. A simple type cast is not going to fix this because we are working with variants.
Here is a test case that illustrates the issue

This issue is fixed in JSONtext 1.6.6 and higher.
For more information see https://bitbucket.org/drjdpowell/jsontext/issues/92/all-integer-types-needed-for-set-map


color with small values crash browser in pie chart

this works
var data = [
{"value": 0.1, "name": "beta"},
]
when add the color dont work
var data = [
{"value": 0.1, "name": "beta", "color": "#80D066"},
]
here is an example
https://jsfiddle.net/ImMonTty/5z38hh7v/

seems to be related to #558 and will be fixed as part of the next release


Minor UI changes

Change look and feel in Report number screen. Also change view holder look and feel in the phone number list.

Thanks!  @logo17  With this commit you are granted commit access to the Repo! 🎊 🎉


Texas clinics

[ ] Add neighboring state abortion clinics.

to give a more complete picture of clinics available to people in Texas.

Here is the full list of clinics for neighboring states as reported by Fund Texas Choice: https://drive.google.com/file/d/1WYgAGFiwu3AaQh4Lidz-lNupD7jB0msG/view?usp=sharing
There are 30 sites in total across TX, NM, CO, KS, LA.
The Service Area should still be defined as Texas only.


[vote] vote for release 1.6.0

Signed-off-by: slievrly<EMAIL_ADDRESS>

[x] I have registered the PR changes.

Ⅰ. Describe what this PR did
vote for release 1.6.0(https://github.com/seata/seata/milestone/23)
at least 3 votes with binding to pass
Please vote accordingly:

[x] +1 approve
[x] +0 no opinion
[x] -1 disapprove with the reason

vote result:
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

+1 Approve
XA phase two testing in 8.0.30 and 5.7 version passed

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

+1 binding


Typed Builder implementation Part 3.5: Polymorphism support

[x] Tests added for any new code
[x] Ran make fmt-fix (or had formatting run automatically on all files edited)
[ ] Documentation added for any new functionality
[ ] Entry added to UNRELEASED.md for any new functionality

In order to support Builder construction of expressions with type variables we needed to redesign the old approach to signatures. Now, instead of constructing a signature as OperT1(from, to), where from contains freshly generated typevars, which have to be unified (and would have to have been substituted if we wanted to build on this approach further), we construct signatures as (partial) functions from => to.
This also simplifies the code, as there is no longer a need for a) varPools and b) arity-hints.

Codecov Report

Merging #1743 (4cb6f25) into unstable (0e5c321) will decrease coverage by 0.11%.
The diff coverage is 95.08%.

:exclamation: Current head 4cb6f25 differs from pull request most recent head 58b1d48. Consider uploading reports for the commit 58b1d48 to get more accurate results

@@             Coverage Diff              @@
##           unstable    #1743      +/-   ##
============================================
- Coverage     76.76%   76.65%   -0.12%
============================================
  Files           376      376
  Lines         11803    11751      -52
  Branches        563      571       +8
============================================
- Hits           9061     9008      -53
- Misses         2742     2743       +1

Impacted Files
Coverage Δ

...ala/at/forsyte/apalache/tla/typecomp/package.scala
100.00% <ø> (ø)

...at/forsyte/apalache/tla/typecomp/BuilderUtil.scala
90.47% <71.42%> (-9.53%)
:arrow_down:

...apalache/tla/typecomp/TypeComputationFactory.scala
90.00% <88.88%> (-0.48%)
:arrow_down:

.../tla/typecomp/signatures/ArithOperSignatures.scala
100.00% <100.00%> (ø)

...e/tla/typecomp/signatures/BaseOperSignatures.scala
100.00% <100.00%> (ø)

...e/tla/typecomp/signatures/BoolOperSignatures.scala
100.00% <100.00%> (ø)

...he/tla/typecomp/signatures/SeqOperSignatures.scala
100.00% <100.00%> (ø)

...he/tla/typecomp/signatures/SetOperSignatures.scala
100.00% <100.00%> (ø)

...te/apalache/tla/typecomp/unsafe/ProtoBuilder.scala
100.00% <100.00%> (ø)

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 0e5c321...58b1d48. Read the comment docs.


Fix/session display

This PR fixes problems around displaying the finished sessions for an experiment in a collection.

This PR fixes problems around displaying the finished sessions for an experiment in a collection.

What was the problem exactly?


Specify yaml.FullLoader in yaml.load_all statement

Currently, running kube-shell shows a PyYAML Loader deprecation warning because the yaml Loader type isn't specified in two "yaml.load_all" calls.
As per PyYAML documentation, after showing the warning, PyYAML defaults to using the FullLoader.
This change explicitly sets the FullLoader, which will suppress the error in a non-future-breaking way - that is, if a future PyYAML version exits instead of warning & defaulting when a Loader type is not specified.
Fixes #71
Fixes #73
Signed off by: Matthew Field<EMAIL_ADDRESS>

Is this project still maintained?

Abandoning this PR. Project doesn't seem active.


monitor.isOver() wonky with developer tools opened

With dev tools open:

With dev tools closed:

Is this React DnD problem or a Chrome bug?

AFAIK it is a chrome bug when you set a viewport scale


Compatibility With Cinders

Hi,
This isn't an issue, but I didn't know where to ask this. Since the outage of servers, I took this as a chance to try out the Cinders mod, and I wanted to learn if your Multiplayer Mod is compatible with Cinders if I wanted to play online co-op with a friend.
Thanks in advance,
Props for the hard work!

DS3OS is mod agnostic. Its original intent was actually to help allow mods to run online without using the ban server :).

I understand, thanks for the very fast reply btw, and I'll test it out as soon as possible then!


Delete files from tmp

This makes sure that temp files are deleted after uploading to amazon.
To test:

Empty the ./tmp folder in the project directory
Run a scrape (using a test?)
Ensure the folder is empty still.

Closes #242


Adding a new rebus

Associated Issue: #
Summary of Changes

added a new rebus, 'daybreak' with symbols 📅 and 💔

Pull Request Test Coverage Report for Build 522

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.143%

Totals

Change from base Build 514:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls


Project name

Hello,
I've built another React bindings for the excellent derivable library. It's called... React Reactive: https://github.com/andreypopp/react-reactive.
Why I'm creating this issue is I'm thinking of renaming mine to react-derivable and then publish to npm but as your library already exists (though not on npm) and derivable author already starred you repo and linked from some of the derivable issues I figured out I'd better ask you first if you are ok with that.

cc @jevakallio as you are not subscribed to the repo

I'm fine with it, will discuss with @ds300 so he can update relevant docs links and rename, likely tomorrow.

We discussed this last night and I'm also fine with it. I'll update the readme.

Awesome, thank you.
On Wed, 13 Jul 2016 at 11:55, David Sheldrick<EMAIL_ADDRESS>wrote:

We discussed this last night and I'm also fine with it. I'll update the
readme.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jevakallio/react-derivable/issues/1#issuecomment-232297197,
or mute the thread
https://github.com/notifications/unsubscribe/AAB3gv2A4LOYXRJYs-1YwB1IR5FHSJqCks5qVKgXgaJpZM4JJu9o
.

Ok, it's up on npm. Thank you all.

Great! I've renamed this repository and added a link to your in the readme.


Radio Noise, No audio transmission

I disabled all my other voice chat plugins other than mumble and rp-radio. Mumble seems to work great, but RP-radio doesnt. All I hear is the click in and out of other players talking. The voice isnt transmitting, but the radio registers that someone is broadcasting
Thanks!.

Also, there isn't a server script associated with this?? Is it necessary to keep that in the fxmanifest?

do you had fixet it @aidenszolosi

do you had fixet it @aidenszolosi

Nope.

move to #17


Deleted .vscode directory

fix issue #75

@Neel-07 It would be great if you could raise a new PR updating data.js and contributors.md


Semantic Difference Between Python 2 and Python 3

While looking for performance differences between CPython 2.7 and CPython 3.6, I noticed the same benchmark would exercise different parts of the interpreter.
pybench/Calls.py (PythonMethodCalls), pybench/Lookups.py (SpecialClassAttribute, NormalClassAttribute, SpecialInstanceAttribute, and NormalInstanceAttribute):
These benchmarks are using the syntax class c: to create classes. This syntax creates old-styles classes in Python 2 and new-style classes in Python 3. Should we create separate tests for old-style classes (disabled in Python 3) and new-style classes?
pybench/Strings.py:
Due to the str changes in Python 3, it is hard to use these benchmarks to compare between Python 2 and Python 3. While we could use bytes in Python 3 (similar to how unicode is being used Unicode.py), not use if that is the correct approach. Because, at that point, it would more of an ascii string benchmark rather than a str.
Thanks!

I modified pybench to be able to run it on Python 2 and Python 3, but I agree that the code doesn't do exactly the same thing between the two versions.
I'm not a big fan of pybench. First, results look very unstable, so I decided to exclude it from the default group of performance. They are really tiny microbenchmarks, so heavily impacted by all tiny things like CPU caches and code location.
I prefer to use more "macro" benchmarks.
But ok, well, about pybench: what do you suggest?

I removed the pybench from performance. I moved it to my other https://github.com/haypo/pymicrobench project. So I close this PR now.


Support blocked KV cache for flash decoding

Restriction: block_size must match kBlockN in the kernel.

Hi @beginlner I have a commit implementing paged KV cache based on some on the ideas in this PR, can I add you as co-author of the commit?

Hi @beginlner I have a commit implementing paged KV cache based on some on the ideas in this PR, can I add you as co-author of the commit?

Hi @tridao Sure, I'd be happy to be added as a co-author on your commit.

@tridao Is there a possibility to support smaller block sizes than 256?

@tridao Is there a possibility to support smaller block sizes than 256?

Sure, we just need someone interested in working on that.

@tridao I work with the vLLM project a bit and we are super interested in this feature getting implemented, so I took a stab at it here: https://github.com/Dao-AILab/flash-attention/pull/824 . Would greatly appreciate a review.


[Help] How to use headerbar? How Gtk classes are translated into swift?

Dear Tomas,
Thank you for this bindings! This is super useful.
I have a little experience in Vala, but on trying to use some elements from gtk I get errors. Specifically I am trying to use headerbars. How do this class translates into Swift? What am I doing wrong in the code below?
import SwiftGtk

let app = Application(applicationId: "com.example.application")

app.run { window in
    window.defaultSize = Size(width: 400, height: 400)
    window.resizable = true
    let headerbar = Headerbar()
    headerbar.set_title("My test")

    let button = Button(label: "Press Me")
    button.clicked = { _ in
        let newWindow = Window(windowType: .topLevel)
        newWindow.title = "Just a window"
        newWindow.defaultSize = Size(width: 200, height: 200)
        let labelPressed = Label(text: "Oh, you pressed the button.")
        newWindow.add(labelPressed)

        newWindow.showAll()
    }
    window.set_titlebar(headerbar)
    window.add(button)
}

A better inspection of the source code and I found that these classes are implemented in the Sources directory. How would you recommend to approach creating a new one? Where you get the API or the methods that one should implement in the class source? I suppose those are the C Gtk methods, right?

I am away from a computer for a few days. Once I am back I will give you some information.

So...
First, you need to find documentation for API that you want to use. In your case it is https://developer.gnome.org/gtk3/stable/GtkHeaderBar.html Here you see all properties and methods that are available. To use them you need to create a new class and properties and methods for everything that you find the documentation.
I went ahead and created the binding for you so you can see how you would do it,
https://github.com/TomasLinhart/SwiftGtk/commit/1801c74495f155c9def4f8a7ee204180a1c6febb.
And you can use it in the following way.
let headerBar = HeaderBar()
headerBar.title = "Hello World"
headerBar.subtitle = "oh yea"
headerBar.showCloseButton = true
headerBar.spacing = 50

let label = Label(text: "1")

headerBar.packStart(child: label)
headerBar.packStart(child: Label(text: "2"))

headerBar.remove(label)

window.titlebar = headerBar
window.hideTitlebarWhenMaximized = true

I hope, it helps. 😄

Thank you very much! I will contribute as soon as possible. Why don't you add this instruction into the README so others can get right at it?

I am, however, getting an error with the latest addition (now I am running it in Ubuntu):
/Coding/Swift/SwiftGtk/.build/checkouts/SwiftGtk-6200083138746211161/Sources/HeaderBar.swift:15:63: error: value of type 'UnsafePointer<gchar>' (aka 'UnsafePointer<Int8>') has no member 'toString'
        get { return gtk_header_bar_get_title(castedPointer())?.toString() }

I have found a problem in the new code, the error is (I switched to Ubuntu):
/home/luis/Dropbox/Documentos/Coding/Swift/SwiftGtk/.build/checkouts/SwiftGtk--2571330441700638662/Sources/HeaderBar.swift:15:63: error: value of type 'UnsafePointer<gchar>' (aka 'UnsafePointer<Int8>') has no member 'toString'
        get { return gtk_header_bar_get_title(castedPointer())?.toString() }
                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^ ~~~~~~~~
/home/luis/Dropbox/Documentos/Coding/Swift/SwiftGtk/.build/checkouts/SwiftGtk--2571330441700638662/Sources/HeaderBar.swift:20:66: error: value of type 'UnsafePointer<gchar>' (aka 'UnsafePointer<Int8>') has no member 'toString'
        get { return gtk_header_bar_get_subtitle(castedPointer())?.toString() }
                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^ ~~~~~~~~
/home/luis/Dropbox/Documentos/Coding/Swift/SwiftGtk/.build/checkouts/SwiftGtk--2571330441700638662/Sources/HeaderBar.swift:41:75: error: value of type 'UnsafePointer<gchar>' (aka 'UnsafePointer<Int8>') has no member 'toString'
        get { return gtk_header_bar_get_decoration_layout(castedPointer())?.toString() }

The code I used was:
import SwiftGtk

let app = Application(applicationId: "com.example.application")

app.run { window in
    window.defaultSize = Size(width: 400, height: 400)
    window.resizable = true
    let headerBar = HeaderBar()
    headerBar.title = "Hello World"
    headerBar.subtitle = "oh yea"
    headerBar.showCloseButton = true
    headerBar.spacing = 50

    let label = Label(text: "1")

    headerBar.packStart(child: label)
    headerBar.packStart(child: Label(text: "2"))

    headerBar.remove(label)

    window.titlebar = headerBar
    window.hideTitlebarWhenMaximized = true

    let button = Button(label: "Press Me")
    button.clicked = { _ in
        let newWindow = Window(windowType: .topLevel)
        newWindow.title = "Just a window"
        newWindow.defaultSize = Size(width: 200, height: 200)
        let labelPressed = Label(text: "Oh, you pressed the button.")
        newWindow.add(labelPressed)

        newWindow.showAll()
    }

    window.add(button)
}

I see I will look into it.

@TomasLinhart , nevermind, for some reason swift builder is not pulling the new files. I added UnsafePointerGChar and Window.swift; the issue was resolved. Sorry for the bother.

Not related to your package, but I am doing something wrong.
Any changes to main.swift requires .build folder to be deleted and the addition to the new files Window, UnsafePointerGChar, and HeaderBar. How can I instruct Swift build to detect the changes into main.swift without having to start over every run? It is probably something easy, but I cant find it!
Thank you.

Found the solution for that too, the contents of Packages.swift:
import PackageDescription

let package = Package(
    name: "SwiftGtkApplication",
    dependencies: [
        .Package(url: "https://github.com/TomasLinhart/SwiftGtk", majorVersion: 1)
    ]
)


Automatic backups not captured anymore?

When I went to postgres.heroku.com to capture a backup for #3415, I didn't find any in the list.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/15179602-automatic-backups-not-captured-anymore?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F85909&utm_medium=issues&utm_source=github).

$ heroku pg:backups -a gratipay

=== Backups
ID    Backup Time                Status                              Size    Database
----  -------------------------  ----------------------------------  ------  --------
b001  2015-05-15 19:28:59 +0000  Finished 2015-05-15 19:29:11 +0000  43.1MB  MAROON

=== Restores
No restores found. Use `heroku pg:backups restore` to restore a backup

=== Copies
No copies found. Use `heroku pg:copy` to copy a database to another

$ heroku pg:backups schedules -a gratipay

No backup schedules found. Use `heroku pg:backups schedule` to set one up.

$ heroku pg:backups schedule DATABASE_URL -a gratipay

Scheduled automatic daily backups at 04:00 UTC for HEROKU_POSTGRESQL_MAROON

@rohitpaulk Did you mean to close both Issues?

Yes. They're both solved, aren't they?


Gym landing page

You can also checkout our Idea-Arca, the project idea bank for any languages, for open-source contributions.
Happy Contributing season!
Keep up the good work!


Inconsistent FOV & Aspect Ratio handling in ogre2

Environment

OS Version:  Xubuntu 20.04
Source or binary build?
Garden, probably others too.
If this is a GUI or sensor rendering bug, describe your GPU and rendering system. Otherwise delete this section.

Rendering plugin: [ogre2]

Description
While creating Heightmap integration tests, I noticed Camera and DepthCamera produced quite different results; despite having the same parameters.
Tracking down the root of the problem, I nailed down on how gz-rendering handles Aspect Ratio inconsistently and very awkwardly.
Here are the problems:
Most Gazebo cameras call Ogre::Camera::setAutoAspectRatio( true )
This looks undesirable because Gazebo has no toggle for auto aspect ratio; but instead asks for an explicit AspectRatio
When this is set; Ogre will overwrite calls to Camera::setAspectRatio during rendering; which means gz::Ogre2Camera::AspectRatio won't be honored (assuming the AR is different from the requested resolution)
Some form of gz::Ogre2Camera::AspectRatio is still "honored" in some form because Gazebo asks for HFOV while Ogre asks for VFOV. And for the conversion the AR is still needed. This means Gazebo does:
vfov = 2.0 * atan(tan(this->HFOV().Radian() / 2.0) / this->AspectRatio());
this->ogreCamera->setFOVy(Ogre::Radian(this->LimitFOV(vfov)));

Hence calls to gz::Camera::SetAspectRatio will appear to make an impact, but it may be producing the wrong output.
Ogre2Camera::AspectRatio fallbacks to Ogre::Camera::getAspectRatio
Because of the setAutoAspectRatio() call, the following will fail:
gzCamera->SetImageWidth( 1600 );
gzCamera->SetImageHeight( 900 );
gzCamera->SetHFOV( 1 );

gzCamera->Render();

assert( gzCamera->HFOV() == 1 ); // FAIL: Ogre modified the FOV due to setAutoAspectRatio.

An integration test can be made for this due to its simplicity.
SetHFOV depends on AspectRatio
This means with the current API order matters and the following code is wrong:
camera->SetHFOV( value );       // Error AspectRatio is uninitialized
camera->SetAspectRatio( ar );

And the following code is correct:
camera->SetHFOV( value );
camera->SetAspectRatio( ar );

The most user-friendly solution would be to set the HFOV to Ogre every time in PreRender; this way initialization order won't matter.
Ogre2DepthCamera::HFOV does not rely on Ogre::Camera
This is correct IMO, but inconsistent with Ogre2Camera.
Ogre2DepthCamera only ever sets HFOV in CreateDepthTexture
Again calling order matters.
This fails:
depthCamera->CreateDepthTexture();
depthCamera->SetHFOV( value );       // Value will be ignored

This succeeds:
depthCamera->SetHFOV( value );
depthCamera->CreateDepthTexture();

Expected behavior:

All cameras should be consistent and produce the same results.
Calling order should not matter. If it does, then Gazebo should produce an error and complain very loudly.
Ogre should not override Aspect Ratio. The value set by the user should be honored.

Actual behavior:

Ogre2Camera and Ogre2DepthCamera may produce different output
Calling order matters. Using the wrong order will cause some parameters to be ignored, overriden, or result in wrong internal calculations.
Arbitrary AR set by user is being ignored

Steps to reproduce
Output
Output by normal Camera:

Output by normal DepthCamera:

Fix
I will be fixing this issue and submit a PR for it. So just assign this ticket to me.

OK I'm hitting a few problems when trying to fix this issue in an ABI stable way because:

Fixing this issue means disabling AutoAspectRatio to respect the one set by caller
However if caller always left the default value (1.3333) then rendering output gets visibly messed up
test/common_test/Camera_TEST.cc fails for this very own reason. It sets width, height and HFOV, but not Aspect Ratio.

Technically I could fix Camera_TEST and push a PR that is ABI stable.
But while it would pass all the checks, it feels like morally I'm breaking the ABI due to Hyrum's Law:

With a sufficient number of users of an API,
it does not matter what you promise in the contract:
all observable behaviors of your system
will be depended on by somebody.

So I began to question what is Aspect Ratio and why we need it?
Aspect Ratio at low level makes sense
At OgreNext level (or anything lower level), AR makes sense. Cameras can be reused for multiple RenderTargets of varying resolutions. They may even be used to draw to only a portion of that target.
In OgreNext we added setAutoAspectRatio because most users don't care and want the AR to match that of the Viewport.
Aspect Ratio at Gazebo level doesn't make much sense
Gazebo seems to map 1 Camera == 1 physical camera in the real world. It's got its own feeds, its own render target resolution.
Hence the AR should be tied to its RenderTarget resolution.
But we have to admit, there's always "that one user", that needs a custom AR.
Solution?
As far as I can see, one approach I can try is to pretend to use Auto Aspect Ratio unless SetAspectRatio is explicitly called.
This should fix it in the most sensible way without breaking everything for everyone.

As far as I can see, one approach I can try is to pretend to use Auto Aspect Ratio unless SetAspectRatio is explicitly called.

agreed

agreed

The final solution I arrived turned out to be more elegant and simple than I could imagine: When you try to set an invalid value (i.e. AR <= 0.0) we start autocalculating and Camera::AspectRatio will return the autocalculated ratio instead of 0.0 or the invalid negative value it was set.
Thus if a user explicitly calls SetAspectRatio( 2.0 ) that value will be respected.
And if the user never calls the function, the (new) default value of 0.0 will cause Gazebo to return the auto calculated value.
The only case where my PR will break user code is if the user explicitly relied on calling SetAspectRatio with an invalid value (e.g. 0.0 or negative) which would have been a very, very bad practice.


Unable to instantiate Client Struct

Issue
When running the below code block (from the readme) to instantiate Client struct
let client = Client::default().await.unwrap();

I get the following error:
GAX(Auth(HttpError(reqwest::Error { kind: Decode, source: Error("EOF while parsing a value", line: 1, column: 0) })))
I am using the google_auth crate from this repository utilising the below code block to set the credentials (from the readme)
    let credentials_path = PathBuf::from("./src/keys/dev-key.json");
    let service_account = CustomServiceAccount::from_file(credentials_path).expect("Service account threw an error");
    let authentication_manager = AuthenticationManager::from(service_account);
    let scopes = &["https://www.googleapis.com/auth/cloud-platform"];

Setting the credentials seems to be working fine; when I run the code in debug, I can see the below all populating with the correct values

My environment
rustc --version
rustc 1.62.1 (e092d0b6b 2022-07-16)

cargo --version
cargo 1.62.1 (a748cf5a3 2022-06-08)

My Cargo.toml file looks like this:
actix-web = "4.1.0"
awc = "3.0.0"
colored = "2.0.0"
dotenv = "0.15.0"
env_logger = "0.9.0"
futures = "0.3.21"
gcp_auth = "0.7.3"
google-cloud-gax = "0.7.0"
google-cloud-googleapis = {version = "0.4.0", features = ["pubsub"]}
google-cloud-pubsub = {version = "0.4.0", features = ["trace"]}
google_auth = "0.2.1"
prost-build = "0.10.4"
protobuf = "3.1.0"
serde = { version = "1.0.140", features = ["derive"] }
serde_json = "1.0.82"
tokio = "1.20.1"
validator = "0.16.0"
validator_derive = "0.16.0"

google-cloud-spanner uses google-cloud-auth and google-cloud-auth reads the credential file from GOOGLE_APPLICATION_CREDENTIALS outside of GCP.
When you set GOOGLE_APPLICATION_CREDENTIALS then it works fine.
export GOOGLE_APPLICATION_CREDENTIALS=/src/keys/dev-key.json

It seems the response from GCP is unexpected for google-cloud-auth.
Would you send me "./src/keys/dev-key.json" to investigate this issue.

dev-key.json is the service account to access my GCP environment I can't send it to you. But to re-create the issue just replace that text with the path to your own local service account.

It works fine with my own service account file. The type of it is service_account and the structure is same as your ./src/keys/dev-key.json.
Are you setting your file path into GOOGLE_APPLICATION_CREDENTIALS environment variable?
The google-cloud-pubsub uses google-cloud-auth and google-cloud-auth read the credentials from GOOGLE_APPLICATION_CREDENTIALS when it runs outside the GCP.

all sorted now. Wasn't setting the credentials propley. For anyone else that runs into this issue, below is the code I used to set the GOOGLE_APPLICATION_CREDENTIALS environment variable when running the app locally.
let local = dotenv::var("local").unwrap_or("none".to_string());
    if local == String::from("true") {
        println!("==Running Locally==");
        // Get current working directory as owned string
        let current_dir = env::current_dir()
            .expect("Could not get current working directory")
            .to_str()
            .expect("Could not convert to str")
            .to_owned();
        println!("{:?}/src/keys/dev-key.json", current_dir.to_owned());
        // Concatenate string to form full path to key
        let _path_to_key = current_dir + "/src/keys/dev-key.json";
        // Take ownership of String and convert it to a &str
        let path_to_key = _path_to_key.as_str();
        println!("Path to key: {:?}", path_to_key);
        // Set GOOGLE_APPLICATION_CREDENTIALS env variable if working in a local env
        env::set_var("GOOGLE_APPLICATION_CREDENTIALS", path_to_key);
        println!(
            "GOOGLE_APPLICATION_CREDENTIALS: {}",
            dotenv::var("GOOGLE_APPLICATION_CREDENTIALS").unwrap_or("none".to_string())
        );
        // `credentials_path` variable is the path for the credentials `.json` file.
        let credentials_path = PathBuf::from(path_to_key);
        let service_account = CustomServiceAccount::from_file(credentials_path)
            .expect("Could not find Service account");
        let authentication_manager = AuthenticationManager::from(service_account);
        let scopes = &["https://www.googleapis.com/auth/cloud-platform"];
        let _token = authentication_manager
            .get_token(scopes)
            .await
            .expect("Token stuffed");
    }

Happy to close this now


chore(master): release 0.13.0

:robot: I have created a release beep boop
0.13.0 (2024-06-03)
Features

updating from newer svd2rust (#101) (a4eea05)

Bug Fixes

deps: reverting cortex-m-rt to 0.7.3 due to yanking (b52fb5b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/xmc-rs/xmc4500/releases/tag/v0.13.0 :sunflower:


Some Emoji not displaying on iOS

flutter doctor
[✓] Flutter (Channel stable, v1.12.13+hotfix.9, on Mac OS X 10.15.4 19E266, locale zh-Hans-CN)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 11.4)
[✓] Android Studio (version 3.6)
[✓] IntelliJ IDEA Ultimate Edition (version 2019.3.4)
[✓] VS Code (version 1.42.1)
[✓] Connected device (3 available)

program
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Welcome to Flutter',
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        appBar: AppBar(
          title: Text('Welcome to Flutter'),
        ),
        body: Center(
          child: Text(
            '⭐✯✡✩✪✫✬✭✮✶✷✵✸✹✺❊✻✽✼❉✱✲✾❃❋✳✴❇❈※❅❆❄⚙✿❀❁❂✓',
            style: TextStyle(
              fontSize: 48.0,
              color: Colors.blue,
            ),
          ),
        ),
      ),
    );
  }
}

I'm experiencing the same issue (looks like the same as https://github.com/flutter/flutter/issues/49627). This happens for number emoji's like 3⃣ or 7⃣ as well.
I would love to enable emoji's in my app which includes user generated content, but this is a blocker.

Hi @mentalmap
are you still experiencing the issue with the latest stable or above?
Thank you

on 1.17.5:

Hi @mentalmap
I do experience this behaviour with the latest master

screenshot

logs
[✓] Flutter (Channel master, 1.20.0-3.0.pre.126, on Mac OS X 10.15.5 19F101, locale en-GB)
    • Flutter version 1.20.0-3.0.pre.126 at /Users/nevercode/development/flutter_master
    • Framework revision 462b0ea76e (12 hours ago), 2020-07-02 16:13:02 -0400
    • Engine revision 51ca1432b3
    • Dart version 2.9.0 (build 2.9.0-20.0.dev 8afe9875a6)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/nevercode/Library/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.9.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.1

[✓] Connected device (4 available)
    • iPhone 11 Pro Max (mobile) • D6967F45-CB0F-4D4E-AFD5-278816A21CAE • ios            • com.apple.CoreSimulator.SimRuntime.iOS-13-5 (simulator)
    • macOS (desktop)            • macos                                • darwin-x64     • Mac OS X 10.15.5 19F101
    • Web Server (web)           • web-server                           • web-javascript • Flutter Tools
    • Chrome (web)               • chrome                               • web-javascript • Google Chrome 83.0.4103.116

• No issues found!

Thank you

Don't we use Unicode for Emoji??

✌☝✍
Flutter version: 1.20.2

I'm experiencing this issue as well on flutter 2.5.3

I am also experiencing the issue on Flutter 3.0.2.

I am also experiencing the issue for number emojis on Flutter 3.0.2.

same

I am also experiencing same issue on flutter 3.3.10. When we begin text with 10 digit icon, everything works smoothly. If we begin with 0 to 9 digit icon, then there is rendering issue.

I verified the issue on the latest master channel 3.7 on iphone 12 pro simulator and it seems to render the icons fine.

code sample
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Welcome to Flutter',
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        appBar: AppBar(
          title: const Text('Welcome to Flutter'),
        ),
        body: const Center(
          child: Text(
            '⭐✯✡✩✪✫✬✭✮✶✷✵✸✹✺❊✻✽✼❉✱✲✾❃❋✳✴❇❈※❅❆❄⚙✿❀❁❂✓\n0⃣1⃣2⃣3⃣4⃣5⃣6⃣7⃣8⃣9⃣',
            style: TextStyle(
              fontSize: 48.0,
              color: Colors.blue,
            ),
          ),
        ),
      ),
    );
  }
}

flutter doctor -v (mac)
[✓] Flutter (Channel master, 3.7.0-13.0.pre.131, on macOS 13.1 22C65 darwin-arm64, locale en-IN)
    • Flutter version 3.7.0-13.0.pre.131 on channel master at /Users/mahesh/Development/flutter_master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 0196e6050b (2 days ago), 2022-12-31 11:10:23 -0500
    • Engine revision 932591ec04
    • Dart version 3.0.0 (build 3.0.0-76.0.dev)
    • DevTools version 2.20.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks
      and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.74.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.56.0

[✓] Connected device (3 available)
    • iPhone 12 Pro (mobile) • 026D5789-9E78-4AD5-B1B2-3F8D4E7F65E4 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 13.1 22C65 darwin-arm64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 108.0.5359.124

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

[✓] Flutter (Channel stable, 3.3.9, on macOS 12.6 21G115 darwin-arm, locale en-IN)
    • Flutter version 3.3.9 on channel stable at /Users/mahesh/Development/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision b8f7f1f986 (24 hours ago), 2022-11-23 06:43:51 +0900
    • Engine revision 8f2221fbef
    • Dart version 2.18.5
    • DevTools version 2.15.0

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

[✓] VS Code (version 1.70.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.53.20221101

[✓] Connected device (3 available)
    • iPhone 12 Pro (mobile) • 026D5789-9E78-4AD5-B1B2-3F8D4E7F65E4 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 12.6 21G115 darwin-arm
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 107.0.5304.110

[✓] HTTP Host Availability
    • All required HTTP hosts are available

• No issues found!

Closing this issue as fixed. Incase you still encounter the issue, then please feel free to write in the comments and we will reopen it.
Thank you.

I verified the issue on the latest master channel 3.7 on iphone 12 pro simulator and it seems to render the icons fine.

code sample
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Welcome to Flutter',
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        appBar: AppBar(
          title: const Text('Welcome to Flutter'),
        ),
        body: const Center(
          child: Text(
            '⭐✯✡✩✪✫✬✭✮✶✷✵✸✹✺❊✻✽✼❉✱✲✾❃❋✳✴❇❈※❅❆❄⚙✿❀❁❂✓\n0⃣1⃣2⃣3⃣4⃣5⃣6⃣7⃣8⃣9⃣',
            style: TextStyle(
              fontSize: 48.0,
              color: Colors.blue,
            ),
          ),
        ),
      ),
    );
  }
}

flutter doctor -v (mac)
Closing this issue as fixed. Incase you still encounter the issue, then please feel free to write in the comments and we will reopen it.

Thank you.

@maheshmnj
if I put some emoji in front of 1⃣, it will display. But I only type 1⃣ in textfield, it will show two box with question mark and the Text widget also displays like that.
It happen when I run debug in iPhone 14 simulator with iOS version 16.1
[✓] Flutter (Channel stable, 3.0.5, on macOS 13.0.1 22A400 darwin-arm, locale en-VN)
[!] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more
      details.
[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.73.1)
[✓] Connected device (3 available)
[✓] HTTP Host Availability

cc: @danagbemava-nc

Hi @wadeowenwatt, you are on an older version of flutter can you upgrade to the latest version of flutter stable(3.7.6) to see if you can still reproduce the issue?  Can you also check on the latest master channel to see if it reproduces as well?
There's a similar report in https://github.com/flutter/flutter/issues/36062

Hi @wadeowenwatt, you are on an older version of flutter can you upgrade to the latest version of flutter stable(3.7.6) to see if you can still reproduce the issue? Can you also check on the latest master channel to see if it reproduces as well?
There's a similar report in #36062

Thanks for your support @danagbemava-nc, I tried updating the latest flutter version, but I can still reproduce this issue. I think this issue is not the same as the one you mentioned because it occurs in both TextField.

Hi @wadeowenwatt, since this issue was about a specific scenario that has since been fixed, kindly file a new issue for the scenario you're facing so that it can be looked at independently.
Thank you


yaml file extension raise un user friendly message.

If I use file extension except yml or yml.liquid,
the following exception raised.
But It's not user friendly, Should output following message which
is raise on runner.rb: line.120.
Unsupported file extension. Supported file extensions are .yml and .yml.liquid: yaml

Test procedure.
embulk example test1
cp test1/example.yml test1/example.yaml
embulk guess test1/example.yaml -o config.yml

embulk guess test1/example.yaml -o config.yml
2015-09-30 10:00:34.089 +0900: Embulk v0.7.4
exception class/object expected
    /path/to/home/.embulk/bin/embulk!/embulk/runner.rb:120:in `read_config'
    /path/to/home/.embulk/bin/embulk!/embulk/runner.rb:12:in `guess'
    /path/to/home/.embulk/bin/embulk!/embulk/command/embulk_run.rb:274:in `run'
    /path/to/home/.embulk/bin/embulk!/embulk/command/embulk_main.rb:2:in `<top>'
    org/jruby/RubyKernel.java:940:in `require'
    uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:1:in `(root)'
    file:/path/to/home/.embulk/bin/embulk!/embulk/command/embulk_bundle.rb:55:in `<top>'

Error: exception class/object expected

Good point.

Fixed at 69d7ac2a5cdd38baa7f6fbd01e9163ef9a9b0c4e. Thank you for reporting!

Thanks!


The typing on SSML triggers page to refresh

The SSML audio repeats on typing on input text form
   handleChange = e => {     //e.preventDefault();     this.props.updateState({       type: 'CAPTURE_RESPONSE',       payload: e.target.value     })   }

Sorry, I'm not sure what you're referring too. This project is a command-line tool (for the console), so there's no input field. I don't know the code you mentioned.


White square appears where image is expected...

Describe the bug
White square appears where image is expected with no error message....
Device hardware

ESP32
Display with link: ILI9341 Generic 3.2"
GUIslice config selected: ??? esp-tftespi-default-notouch.h

Checklist to try first
Most display/touch issues can be identified by working through the steps in the Configuring GUIslice guide.
Please confirm whether:

Display works correctly with standalone display driver library examples (eg. TFT_eSPI graphicstest, Adafruit graphicstest, etc.) without GUIslice:  YES
Touch works correctly with standalone touch library examples without GUIslice: YYES

Expected behavior
I expected to see the image where I placed it in the Builder window...
Initialization messages
Please copy any startup messages / errors reported to the serial monitor window here. You can enable all error messages by setting DEBUG_ERR 2 in the GUIslice config file. NO ERRORS
Additional info
So i've attempted to do the following steps but end up with a GREY square on the display where the iimage is supposed to be....
In the builder I add an image.....
I've added 12 images to the SPIFF area of my ESP32.
I can print out the file list...
20:51:46.945 -> File: /partnight_sm.jpg 20:51:46.945 -> File: /downpour_sm.jpg 20:51:46.945 -> File: /thunderstorm_sm.jpg 20:51:46.945 -> File: /clearnight_sm.jpg 20:51:46.945 -> File: /snow_sm.jpg 20:51:46.945 -> File: /snowshowers_sm.jpg 20:51:46.945 -> File: /Clouds_sm.jpg 20:51:46.945 -> File: /partsun_sm.jpg 20:51:46.945 -> File: /dangcold_sm.jpg 20:51:46.945 -> File: /verycloud_sm.jpg 20:51:46.945 -> File: /thunder_sm.jpg 20:51:46.981 -> File: /windy_sm.jpg 20:51:46.981 -> File: /Sunny_sm.jpg 20:51:46.981 -> File: /danghot_sm.jpg
I set the image to one in the file list..... uaing the builder....
#define IMG_CLEARNIGHT_SM         "/clearnight_sm.jpg"
pElemRef = gslc_ElemCreateImg(&m_gui,E_ELEM_IMAGE1,E_PG_MAIN,(gslc_tsRect){215,17,70,70},     gslc_GetImageFromFile(IMG_CLEARNIGHT_SM,GSLC_IMGREF_FMT_JPG));
the above appears in the _GSLC.h file.
I also made sure that in the GUIslice config file I changed
 #define GSLC_SPIFFS_EN               1
in the
esp-tftespi-default-notouch.h
Still end up with the grey square thoug.....am I missing  some stepss...

@bostonmacosx You don't seem to have missed any steps.
Please  post a zip file of complete sample project including *.prj, *.ino, *.h and the data sub folder with its image otherwise we have no idea what's going on.   Try and redo the sample with just one image for us to debug.
Paul--

@bostonmacosx I just created a new project and stored image button and image in SPIFFs and it worked fine.
When you pack up your zip file for debugging include you're TFT_eSPI/User_Setup.h and esp-tftespi-default-notouch.h
Paul--

Thanks Paul. Here are the requested files....
GUISLICE_GIT.zip
Otherconfigs.zip
@Pconti31

@bostonmacosx Turns out you are actrually getting an error from TFT_eFEX that isn't being reported by GUIslice.
Jpeg file format not supported!
According to my Adobe tools you have ICC Profile: GIMP Builtin sRGB color
with format option:  progressive with 3 scan lines.
I changed format option to Baseline: Standard for clearnight_sm.jpg and it loaded fine.
Attached is the new file.
clearnight_sm.zip
If you need me to convert the others It will have to wait until tomorrow.  You might want to report this as an issue for the JPeg converter.
Paul--

SUPER! Should I rerport it as (should be reported in GUISlice as well)

@Pconti31 bodmer replied will never be support for progressive images.

@bostonmacosx Well, at least he answered you...
Close the issue if it works otherwise post a zip images that fails.  As to reporting to GUIslice, Ah.. isn't that where we are?   The whole idea of this issue list is so @ImpulseAdventure Calvin will notice and fix problems.
Note that the error reporting is a little unfair in that TFT_eFEX's routines are void with no error return so GUIslice thinks everything is working.   Still a blank block is a pretty good hint that something is wrong.
Paul--

I have now forwarded the error return value from TFT_eFEX drawBmp() / drawJpgFile() / drawJpeg(), which should then be trapped in ElemDrawByRef(). If DEBUG_ERR=2 is set in the config (full debug messaging), it might now report an error within GUIslice.
@Pconti31 -- Note that I haven't tested this specific code yet, but I was thinking the progressive image decode error would be exposed by a false return from drawJpgFile()?
I had the fun of writing a JPEG decoder from scratch a while back ( JPEGsnoop ) and similarly figured that progressive images weren't worth the effort, especially with broadband access being pretty common now.

 :)
Anyway, you now have a problem compiling:
C:\Users\Paul\Documents\Arduino\libraries\GUIslice-0.16.8\src\GUIslice_drv_tft_espi.cpp:1052:45: error: void value not ignored as it ought to be

   return fex.drawBmp(pStrFname, nDstX, nDstY);

With this fixed I tested spiffs with JPG's and it correctly loads non progressive jpegs.
However, no error is reported with progressive jpegs.
I would suggest something like:
bool gslc_DrvDrawJpegFromFile(gslc_tsGui* pGui,int16_t nDstX,int16_t nDstY,gslc_tsImgRef sImgRef)
{
  const char* pStrFname = sImgRef.pFname;

  // Load JPEG image from file system
#if defined(ESP32)
  // use optimized ESP32 native decoder  if(!fex.drawJpgFile(SPIFFS, pStrFname, nDstX, nDstY)) {
   // Unsupported source
    GSLC_DEBUG_PRINT("DBG: DrvDrawJpegFromFile() %s unsupported jpeg format\n", pStrFname);
  }
#else
  // use library decoder
  if(!fex.drawJpeg(pStrFname, nDstX, nDstY)) {
    // Unsupported source
    GSLC_DEBUG_PRINT("DBG: DrvDrawJpegFromFile() %s unsupported jpeg format\n", pStrFname);
  }
#endif
return true;
}

and this successfully reported:
INFO:   Add elem to collection: ElemRef=6/6, ElemRAM=6/6, ElemId=4 (RAM)
DBG: DrvDrawJpegFromFile() /danghot_sm.jpg unsupported jpeg format

Paul--

Oops, yes, maybe a bit impulsive :) I did run my changes through the regression environment and didn't encounter any errors. But I see now that the GSLC_SPIFFS_EN code wasn't being tested -- so I'll have to add that to my checks as well.
Looks like I was thrown off by the fact that that both drawJpg() and drawJpgFile() had return values, but not drawBmp() or drawJpeg(), despite all being able to detect an error. For the same reason, I'm guessing that your last proposed line with drawJpeg() might not actually operate as intended.
Thankfully, for the specific problem at hand, we can still detect the error on ESP32 platforms.
I have pushed a change for the above... hopefully this one reports the error as intended! (Though I don't have the test setup ready on hand at the moment, so have only confirmed compilation, not on physical hardware)

Closing for now as I believe it has been addressed.
If there are any outstanding issues with the latest changes, please reply and I'll re-open.
thx

Closing for now as I believe it has been addressed.
If there are any outstanding issues with the latest changes, please reply and I'll re-open.
thx


:bug:Fix challenge level routing

Coverage remained the same at 61.917% when pulling 574a65c7e82f808784d21cd4732751ba84b145be on fix-challenge-routing into eabb84bd8e8c66b22d00648206d9a99c4b0346a2 on master.


implement hoppers

TODO:

implement the hopper model

ready for review, tested and everything works.
feel free to test yourself (gotta remove raptor's last commit which creates a deadlock)

should be good for review, fully working now

this was completed in #911
this pr can be closed


Plugin prettier not found

Hello, I have problem with prettier plugin not loaded correctly or not found. We upgraded whole project to newer packages, everything works fine, but we found out, that prettier/eslint is not working at all (at least in VS Code, in terminal it works).
We upgraded from
"devDependencies": {
    "babel-eslint": "^10.0.1",
    "eslint": "^5.15.1",
    "eslint-config-biq": "0.3.0",
    "eslint-config-prettier": "^4.1.0",
    "eslint-config-standard": "^12.0.0",
    "eslint-plugin-import": "^2.16.0",
    "eslint-plugin-jsdoc": "^4.4.3",
    "eslint-plugin-jsx-a11y": "^6.2.1",
    "eslint-plugin-node": "^8.0.1",
    "eslint-plugin-prettier": "^3.0.1",
    "eslint-plugin-promise": "^4.0.1",
    "eslint-plugin-react": "^7.12.4",
    "eslint-plugin-react-hooks": "^1.5.0",
    "eslint-plugin-redux-saga": "^1.0.0",
    "eslint-plugin-standard": "^4.0.0",
    "prettier": "^1.16.4"
}

to newer one:
"devDependencies": {
    "babel-eslint": "^10.0.1",
    "eslint": "^6.6.0",
    "eslint-config-biq": "0.4.0",
    "eslint-config-prettier": "^6.5.0",
    "eslint-config-standard": "^14.1.0",
    "eslint-plugin-import": "^2.16.0",
    "eslint-plugin-jsdoc": "^17.1.0",
    "eslint-plugin-jsx-a11y": "^6.2.1",
    "eslint-plugin-node": "^10.0.0",
    "eslint-plugin-prettier": "^3.0.1",
    "eslint-plugin-promise": "^4.0.1",
    "eslint-plugin-react": "^7.12.4",
    "eslint-plugin-react-hooks": "^2.2.0",
    "eslint-plugin-redux-saga": "^1.0.0",
    "eslint-plugin-standard": "^4.0.0",
    "prettier": "^1.16.4",
  }

and eslint/prettier stop working in VS Code, here is info from vs code terminal
[Info  - 3:11:15 PM] ESLint server stopped.
[Info  - 3:11:15 PM] ESLint server running in node v10.11.0
[Info  - 3:11:15 PM] ESLint server is running.
[Info  - 3:11:16 PM] ESLint library loaded from: /Volumes/SSD/Job/Bootiq/starter/frontend/node_modules/eslint/lib/api.js
[Error - 3:11:16 PM]
Failed to load plugin 'prettier' declared in 'frontend/.eslintrc » eslint-config-biq': Cannot find module 'eslint-plugin-prettier'
Require stack:
- /Volumes/SSD/Job/Bootiq/starter/__placeholder__.js
Referenced from: /Volumes/SSD/Job/Bootiq/starter/frontend/node_modules/eslint-config-biq/index.js
Happened while validating /Volumes/SSD/Job/Bootiq/starter/frontend/src/components/Company/AddCompany.js
This can happen for a couple of reasons:
1. The plugin name is spelled incorrectly in an ESLint configuration file (e.g. .eslintrc).
2. If ESLint is installed globally, then make sure 'eslint-plugin-prettier' is installed globally as well.
3. If ESLint is installed locally, then 'eslint-plugin-prettier' isn't installed correctly.

Consider running eslint --debug /Volumes/SSD/Job/Bootiq/starter/frontend/src/components/Company/AddCompany.js from a terminal to obtain a trace about the configuration files used.

We have also BE, where is same devDep configuration as old one and thats working correctly. Also I check all eslint configuration and everything looks good
Now I dont know if problem is with eslint plugin for VS Code or with eslint/prettier

@LadIQe does the validation happen correctly when you use eslint in the terminal. If this is the case can you please provide me with a GitHub repository I can clone that demos what you are experiencing.

@dbaeumer  hello, thank you for reply. Yes validation is working in terminal, but inside VS Code it doesnt work.
I can give you repo for eslint-biq, which we are using:
https://www.npmjs.com/package/eslint-config-biq
than we have .eslintrc
{
  "plugins": [
    "jsdoc"
  ],
  "rules": {
    "jsdoc/require-jsdoc": 0
  },
  "extends": ["biq", "biq/react"]
}

Unfortunately, I cant give you repo for project, because its our internal private project.

A GitHub repository I can clone that demos what you are seeing is highly appreciated. Without it it will be hard to understand what causes this for you.

yes I understand you, but as I said, its project for our customer and we cant share any code. But if it can help you, its based on create-react-app where we are using eslint-config-biq, thats all
almost forget, we are using docker, but as I said, I cant give you repo for project, and also we are using gitlab, not github

I wonder if this is related to this issue (which is still impacting me)...
#759
Seems like ESLint / VSCode cannot find plugins when running as part of a multi project workspace, but if I open the project in its own VSCode window (or run lint via terminal), it works fine

@LadIQe it must not be your private repository. I could also be a repository that only contains an example that demos what you are seeing.

@dbaeumer here is sample project
https://github.com/LadIQe/eslint-test

@LadIQe in the example you provide which folder do you open in VS Code ?

@dbaeumer whole project, because we are constantly changing FE and BE code, so always switching is not a good idea
before it works great but now after upgrading packages it doesnt work

Then you need to set the workingDirectory settings to tell VS Code eslint to treat them as working dirs. See https://github.com/microsoft/vscode-eslint. Best with changeProcessCWD set to true.

So do we need to set every single directory in this setting? e.g. if I have one large workspace with 10+ projects, and cloning other repos regularly, I need to update this setting each time? Is there not a way to have this auto detect to current directory you are working in? Thanks!

@dbaeumer thank you for your quick fix, now its working like before (at least in directory, which is set under eslint.workingDirectories). But, as @markmckim mentioned, is there auto detect function, which can detect it by itself? thank you

For auto detection see: https://github.com/microsoft/vscode-eslint/issues/745
The problem is that the auto detection is not trivial without reimplementing internals of the ESLint npm module.
Interestingly devs have no problem doing a cwd in a terminal to make this work since eslint in the terminal will fail in the root directories of these setups as well. Or does this work in the roots for you and not in VS Code.

I spoke with other devs in my team and we are going to use eslint.workingDirectories. Its not that great, but at least its working.
But interestingly, before it worked well


CClaimTrieCache::removeClaim does not need the height parameter

Removed the height parameter from the removeClaim function.
Closes https://github.com/lbryio/lbrycrd/issues/226

Please review this.

I'm sorry that I wasn't checking my email yesterday. However, there was already a pull request to take care of this ( #228 ), and that was clearly noted in #226. In addition, you would have needed to use claim->nHeight in place of the parameter.


nixos/users+nixos/lightdm: fixed users starting at 1000, and system users below 1000

Motivation for this change
The documentation for users-groups.nix was wrong for isSystemUser, and the check for system users was not correct (as it only checked for below 500).
Also changed lightdm to only include users IDs at 1000 or above.
The reason for this change is here https://github.com/NixOS/nixpkgs/commit/23d920c8f0d8d790fc69e155acbe9342853cc46a
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

For lightdm, this does not seem to work:

jupyter has uid 997 and nix-ssh has uid 995, yet here they are. They also do not belong to group 100.
Lightdm mentions that user lists can also come from AccountsService if it's enabled. Could that be why?

I think that might be why. I am currently hiding my user via. The hidden users option. One could add all system users to that option?
However, these changes should still be merged either way. Maybe with some additions

My user still shows up, when I add it to the hidden users. I am unsure why however, as I run tmpfs, and I don't really save any state about "users" as such.


[Proposal] add functionality for windowing of sequence to be process by Fourier transform

Background
If S(f) is Fourier transform (FT) of S(t), then any linear time-invariant operation on function s(t) produces a new spectrum of the form H(f)•S(f), which changes the relative magnitudes and/or phase of the non-zero values of S(f). Any other type of operation creates new frequency components that may be referred to as spectral leakage in the broadest sense.
One of such operations is a windowing. To perform FT on a finite-time part of infinite-time signal, this signal is multiplied by a window function, which value is 0 outside of finite time interval to process.
This operation produces a new frequency components that may break the process of frequency recognition for signals with close frequencies or if signal with low amplitude lies near the  frequency of spectral leakage of signal with high amplitude.
Currently, package "fourier"  perform FT on  the input sequence, which is a case of rectangle window function applied to the infinite-time signal. Bat there are many other window functions , with different parameters of spectral leakage (rectangular is, may be, the worst of them).
Proposal
I want to add a set of functions to perform the transformation of sequence by different window functions:
Rectangle( []float64 ) []float64,
RectangleCmplx( []complex128 ) []complex128,
Sin( []float64 ) []float64,
SinCmplx( []complex128 ) []complex128,
...
and so on.
This functions will be a member of somePackage
it'll allow to do some thing like this:
coeff := fft.Coefficients( nil,  somePackage.Sin( data ) )
Potential impact of proposal
The current approach , which have been discussed on "https://groups.google.com/forum/#!topic/gonum-dev/DkSuS2NiYo0"
is to organize a package tree for algorithms of digital signal processing: dsp. After that, in this tree, to create a package windowing with discussed set of functions.
Looks logical to move fourier package and, may be, some other packages to dsp later.
Another approach is just to do discussed set of functions a part of fourier package, because i don't see other applications for this functions at first glance.

To use it as fft.Coefficients(funcName(nill,src)) the function would need to return two, a dst and a src.

Sorry - my fault. I mean:
fft.Coefficients(dst,funcName(nill,src))
or
fft.Coefficients(nill,funcName(nill,src))
to allocate buffer in funcName
or
fft.Coefficients(dst,funcName(src,src))
to modify data by funcName in place
or
fft.Coefficients(dst2,funcName(dst1,src))
to use external buffers.
I just don't like to do some actions with unobvious result silently. It may cause some data change, when user don't expect it, without any report.
Explicitly is better then implicitly.
Another option is a flag:
func function (src []DataType, inPlace bool) dst []DataType {}.

I would greatly prefer to mutate in place and tell the user explicitly that that is what the function does.

OK

Taking a look at the importers of the fourier package, there are 6 non-Gonum authors importing it into 9 non-Gonum packages. If we want to move fourier to dsp/fourier (which I am inclined to think is a good idea) I think we should get broader feedback.
If the packages importing fourier are using modules, this will not immediately break them, but will require a import path rewrite when they bump versions.
Also note that we are in v0, so while this is not without cost, we are allowed.
cc @aouyang1 @but80 @davidkleiven @lsst-lpc (@sbinet) @matrix-profile-foundation (@aouyang1) @sfluor

Fine by me.
(I'll update the packages for lsst-lpc)

Fine by me. I'll update the package.

I can just move it to fourier/window, if there are no other dsp algorithm in mind except fourier.

I think dsp is good. Maybe at some point one would like to implement wavelet transforms (e.g. Daubechies-family).

I’m happy to make the updates to the packages as well.

Fine by me too :+1: , I will update the package (for musig)