Official Meteor integration

Hello guys,
As you might know, the Meteor community is loving Materialize. We have many different wrapper packages all doing the same thing but not all of them kept updated, so I'm submitting a PR that integrates Meteor packaging directly into your repository: at the end of this merge process, in case you'll find yourself comfortable with it, we'll get automated new Meteor package releases with every new release of Materialize.
I've made this PR as lean as possible so as not to take up too much space within your repository: basically it adds only a package.js file among the ones already present for other package managers.
All you have to do after accepting this PR would be:

Create an account at https://meteor.com/ (click SIGN IN, then Create account). After you've done that, please let me know the name of the account, and we'll add you as a maintainer of the materialize organization (which has been already reserved to make things simpler for you).

Head to autopublish.meteor.com, sign in with your GitHub account, locate this repository and enable it for autopublish by toggling the checkbox you'll find on the right side of the repository item. You can get an idea about how Meteor Autopublish works by having a quick look at this page, but basically it creates a web hook to let us know when you push new tags. When you'll release new versions, autopublish.meteor.com will automatically package the the new version of the library also for Meteor!

In case you're not comfortable with autopublish.meteor.com maintaining access rights to your repos, please head to GitHub Application Settings and revoke permissions for Meteor Autopublish.

Please note that you will not be able to toggle your repository until you'll have the package.js file on your master branch.
Please also note that we've not yet published the current version of the package on Atmosphere (Meteor's package directory) under the new name materialize:materialize to wait for your approval. If you think another name would be a better fit, just let us know!
Thanks in advance for your availability and collaboration and congratulation for the awesome project!
Luca & the Meteor Packaging Team

This sounds like something we definitely want to do. We will incorporate this in soon, thanks!

Great!
...we'll wait for progress news then :)
Tnx a lot,
Luca

We have created an account. Username: materializecss

I've just added materializecss to the materialize organization, tnx!
is materialize:materialize fine as the package name? or would you prefer materializecss:materializecss or something else?

materialize:materialize is good. Now ill take a look at intergrating the PR

I think I have set everything up properly, but I did not see the packaged created on Atmosphere. Could you take a look and verify that everything was done correctly? Thanks!

Hei @Dogfalo,
you did it right, thank you very much!
You're not seing it on atmosphere because the first publish should be done by hands.
From now on next releases will be published automatically though :-)

Please see materialize:materialize

Version 0.95.3 successfully autopublished! :-)
See it on autopublish.meteor.com and on atmosphere
Thanks again!


Private keys of type string should be assumed to be little-endian.

Private keys of type string should be assumed to be little-endian. Because the private key in string form is for ordinary users, this form of private key is more readable. Perform special reverse processing into internal big-endian form during serialization and deserialization.

Add note in "try_from" functions, little-endian is expected


Error on signup page

Hi,
I'm getting error on signup page "There is no user pool configured in /js/config.js. You'll configure this in Module 2 of the workshop" even after making changes(Module 2) in /js/config.js .
Strange thing is the changes are reflected in bucket /js/config.js file but on signup page i see error.

Never Mind :)
I fixed it

how did you fix it?

I am having the same problem. how to fix it?


fix(react-query-devtools): do not hide sort options when filter is used

Sort options (asc/desc, and sort function) were hidden when filter was set.
Sort options are now shown along with the filter, even when a filter is set.
Closes #4989

@TkDodo the failed action doesn't seem to be the result of my changes, locally the tests are passing.

Codecov Report
Base: 91.88% // Head: 91.88% // Decreases project coverage by -0.01% :warning:

Coverage data is based on head (fd9feb5) compared to base (9434a16).
Patch coverage: 100.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5038      +/-   ##
==========================================
- Coverage   91.88%   91.88%   -0.01%
==========================================
  Files         111      111
  Lines        4178     4175       -3
  Branches     1085     1082       -3
==========================================
- Hits         3839     3836       -3
  Misses        318      318
  Partials       21       21

Impacted Files
Coverage Δ

packages/react-query-devtools/src/devtools.tsx
83.75% <100.00%> (-0.18%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Write Tests

Write tests for both backend and frontend code.

I’d like to take this one because I want to practice doing testing with JavaScript. I hope you can be my mentor in it’s needed.
where can I watch the serie, is it free? I didn’t hear about it before,

Hey Hey @JuanVqz
Awesome, I will assign you this issue 👍
Yes, I will help you if needed.
I don't have a recommendation but mocha is fine with me.
Are you planning on writing tests for both backend and frontend?
I will recommend writing tests for backend folder, there are many resources on the same to help you.
The series is available on Netflix, so unfortunately you can't watch it for free.
Let me know if you have any other questions.
Thanks for your help

When this is done, please ping me in issue #5  :) - then I will start the testing workflow action

Hey @JuanVqz
Is there any update on this?
Just checking in
Thanks

I'll start doing this today afternoon, I'll use jest I saw it is kind of the standard, is it okay?
I found the serie, I started to see it

Great 👍
I am fine with jest.
Let me know if you have any questions.

@JuanVqz
How is the work going on this?
Confirming: You are working on tests in backend directory i.e. express server right ?

Yes I’m working on test in backend

Hey @JuanVqz
What's the update on this?

@lelouchB I'm working on the file structure before this one I had a break in the weekend I'll continue this week, sorry.

@lelouchB I'm working on the file structure before this one I had a break in the weekend I'll continue this week, sorry.

No problem
Just wanted an update
Thanks

@JuanVqz
Is there any update on this?
Thanks

@JuanVqz
Is there any update on this?
Thanks

@JuanVqz

Not yet, sorry I lost my brother in law. I'll do it but I don't know when

I am so sorry @JuanVqz
I didn't know
Take all the time you need.


Better support for github pages

Changes
On the road to out-of-the-box github pages

Testing
not yet

Docs

This is an internal change that makes buildOptions.baseUrl work well for gh pages.

@FredKSchott

Draft while designing actual github pages deployment tests. @FredKSchott

This looks pretty good to me. I think the .nojekyll file should be documented in the docs and manually added by the users wanting to support GH pages.

Looking forward to this!

First cut at testing/demo demo-snowpack-gh-pages
I have some issues tracked there (some missing logos, etc.)
@FredKSchott @stramel

Stalled on #1590

Closing since we'll change default behavior here in v3.0, and don't want to thrash the default templates between now and then


Pinned dask[distributed] deployemnts are broken.

I have pinned version dask[distributed]==2.10.1 in my requirements file. Since recent release(2020.12.0) it installs distributed==2020.12.0 which isn't compatible with pinned dask version

Thanks for reporting @whalebot-helmsman -- the distributed extra as defined in setup.py only has a lower bound defined in its version constraints.  I'd suggest that you pin distributed independently.  Usually you don't want dask and distributed to stray too much from one another version-wise, so maybe pin to distributed==2.11.0?

@gforsyth would it make sense to pin distributed more tightly in dask? I could imaging pinning to YYYY.MM.* or something.

I think we should, and the calver switch should make it a lot easier to manage

@dask/maintenance does anyone not like that idea?

I don't think we formally promise to release together, though, so it's conceivable that a new release of distributed needs the version of dask from the previous month, or a bugfix-only release of dask is needed for the latest distributed, again crossing the month boundary.

hmm yeah and I guess pinning it in the setup.py would make it hard for people to upgrade their distributed independently in a case like that.

It would be hard in the case of pip install -U dask[distributed]. I don't know if that is considered common. You would still be able to upgrade the parts separately, though I hear that the new pip resolver is causing problems.

Yeah ok I feel convinced that we should not change the setup.py. @gforsyth I'm going to close this unless you disagree.


Fix custom shape size

Thank you for contributing to vis.js!!
Please make sure to check the following requirements before creating a pull request:
Simple attempt to fix https://github.com/visjs/vis-network/issues/1494
Additionally, custom shapes can now receive the options object in the renderer to further allow customization and external values.
Lastly, added a new option to allow nodes to be tapped / selected beyond their dimensions.  This is to support being able to select small nodes by adding a small padding to them (defaulting to).  Such a small change that another PR didn't make much sense.

Trying to slip a feature in a fix is a really bad practice, atop of that you're exposing internal, undocumented object to the users. If this is something that is really necessary, a proper stable API has to be established and documented first. Anyway, there should be two PRs for this.

Sorry I didn’t have time to set up and document a whole new API for the changes, they seemed pretty small. If you think this would still be useful, I can try to put a proper PR for it when I have time, but we needed the change right away for what we are doing.


Fails due to KUBECONIG location

/kind bug

What versions of software are you using?

Trying to use s2i on Openshift VSCode ext
Actual behavior
odo list --app foo --project josh -ojson
returns:
{
        "kind": "Error",
        "apiVersion": "odo.dev/v1alpha1",
        "metadata": {
                "creationTimestamp": null
        },
        "message": "Please specify the application name and project name\nOr use the command from inside a directory containing an odo component."
}

I found this is because I have my KUBECONFIG set in an env var and it is not in ~/.kube/config. When I changed to that location it worked.
Expected behavior
Return:
{
        "kind": "List",
        "apiVersion": "odo.dev/v1alpha1",
        "metadata": {},
        "s2iComponents": [],
        "devfileComponents": []
}

I expect to be able to configure the location of the kubeconfig according to all kubernetes acceptability places.

We are using KUBECONFIG a lot in our tests and on my local system I also have KUBECONFIG set to a different path than .kube/config.
Did you run odo command in your "normal" terminal or it was in VSCode integrated terminal?
If you run odo with verbose logging -v 10 you should where the kube config is loaded from.
▶ odo -v 10 list
I0316 10:03:11.849734    3404 preference.go:235] The path for preference file is /home/tomas/.odo/preference.yaml
I0316 10:03:11.850182    3404 util.go:422] path devfile.yaml doesn't exist, skipping it
I0316 10:03:11.850248    3404 list.go:87] New Context
I0316 10:03:11.850297    3404 util.go:727] HTTPGetRequest: https://raw.githubusercontent.com/openshift/odo/master/build/VERSION
I0316 10:03:11.850362    3404 util.go:748] Response will be cached in /tmp/odohttpcache for 1h0m0s
I0316 10:03:11.850533    3404 util.go:761] Cached response used.
I0316 10:03:11.850890    3404 loader.go:375] Config loaded from file:  /tmp/test/config

I ran it in both vscode and standard terminal.
If I have kubeconfig in both locations it works. But if it is missing from .kube/config I got that error.

Did any of you ever take a look at this?


Added meditation feature

Description
Added meditation feature
This feature allows user to meditate by selecting the required duration and required environment(forest, rain, summer night, beach) and sound effect. This project is created using HTML, CSS, JavaScript .
Fixes:  #561

Type of change

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] I have made this from my own
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

https://deploy-preview-615--amazing-js-projects.netlify.app/meditation feature/assets/meditation

@VidhiBhatt01 I am working on the responsiveness issue mam I will inform you if I will fail to do so

Cool. You can take 4/5 days max to fix this

@VidhiBhatt01 Made the site responsive please check


Added --version flag

Fixes #26 (using the flag -v or --version)

Is it possible to create a versioning similar to how we do this in Troubleshoot with "github.com/replicatedhq/troubleshoot/pkg/version"? Also, in Troubleshoot we use support-bundle version rather than --version, reserving -v for verbose.
FWIW we're planning to include this repo in the Troubleshoot repo (hence the need for consistency).

This uses the default from cobra. So making it a command would deviate from that. But can of course be done.

I'm also leaning towards version command instead of GNU's --version flag mainly cause of 2 reasons.

It seems to be the preferred way tools follow in k8s ecosystem e.g helm, kompose, kubectl crictl..... Some out there may defer of course like prometheus, but still :)
There is a thought of adopting klog logging library which gives us log levels that use -v=3 like flags to allow increasing/decreasing the amount of logging printed out. If we use --version/-v, we rule out any opportunity of adopting the lib

Closing, we won't merge this in preference of a version subcommand. https://github.com/replicatedhq/troubleshoot/issues/933 will handle that.


Map display improvements (length, pagination)

What problem does this feature solve?

Number of elements in the Map
Hide Map Default. I use Map to store large data. When I open DevTools everything hangs. Since DevTools renders all the Map items. I think the same behavior as the array will be just right

What does the proposed API look like?

I can pick this enhancement.


Including ops_partition("") call

This commit is including the ops_partition("") call into code generated by Devito using OPS backend.
The class Literal was created in the codebase.

LGTM

I can't understand why the travis is breaking.

yeah, that's really odd... I'll restart it, no idea what's going on. pipelines seems fine at least

Codecov Report

Merging #878 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #878      +/-   ##
==========================================
+ Coverage   89.27%   89.28%   +<.01%
==========================================
  Files         105      105
  Lines       11873    11878       +5
  Branches     2349     2349
==========================================
+ Hits        10600    10605       +5
  Misses        981      981
  Partials      292      292

Impacted Files
Coverage Δ

devito/ops/operator.py
96.15% <100%> (+0.32%)
:arrow_up:

devito/ir/iet/utils.py
89.85% <100%> (ø)
:arrow_up:

devito/ops/utils.py
100% <100%> (ø)
:arrow_up:

devito/symbolics/extended_sympy.py
86.12% <100%> (+0.13%)
:arrow_up:

Continue to review full report at Codecov.

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

Merged.


Election timeout reached, restarting election

2015/12/21 10:42:48 [WARN] raft: Election timeout reached, restarting election
    2015/12/21 10:42:48 [INFO] raft: Node at <IP_ADDRESS>:8300 [Candidate] entering Candidate state
    2015/12/21 10:42:48 [ERR] raft: Failed to make RequestVote RPC to <IP_ADDRESS>:8300: dial tcp <IP_ADDRESS>:8300: connection refused
    2015/12/21 10:42:48 [ERR] raft: Failed to make RequestVote RPC to <IP_ADDRESS>:8300: dial tcp <IP_ADDRESS>:8300: connection refused

@Dreampie What is the solution for this issue? I get the same error for sometime and then a leader is elected


Fix vector field particle attractor texture sampling

Fixes #63625
The offending shader code is this part in particles.glsl (comments mine):
case ATTRACTOR_TYPE_VECTOR_FIELD: {
	vec3 uvw_pos = (local_pos / FRAME.attractors[i].extents) * 2.0 - 1.0; // This part is wrong, the mapping should be the opposite
	if (any(lessThan(uvw_pos, vec3(0.0))) || any(greaterThan(uvw_pos, vec3(1.0)))) {
		continue;
	}
	vec3 s = texture(sampler3D(sdf_vec_textures[FRAME.attractors[i].texture_index], material_samplers[SAMPLER_LINEAR_CLAMP]), uvw_pos).xyz; // * 2.0 - 1.0 belongs in here instead
	dir = mat3(FRAME.attractors[i].transform) * safe_normalize(s);
	amount = length(s);

	} break;

The first line is supposed to map a location in 3D space to texture space, but it does the opposite. x * 2 - 1 is used to map from the [0 ... 1] range to the [-1 ... +1] range, but what we want is to map in the other direction. This caused the shader code to always read the wrong coordinate from the vector field texture.
The line where the texture is sampled was missing the mapping back to 3D space. Without it, the vectors would always point in positive X, Y, and Z directions, which caused the relatively uniform diagonal movement that was described in the issue.

Thanks!


[repo] sponsor link leads to 404 page

I was trying to see how I could help the project, but the sponsor link leads to https://gitcoin.co/grants/79/lodestar-eth20-client which is a dead link.
Anything I can do to help?

@GregTheGreek @aidanih

Duplicate of #3136


Windows install issue with leaderf

In the install guide about installing leaderF on windows, these is this sentence:

First, make sure py -2 and/or py -3 commands are available.

I am not clear what this means.  Why not simply detect which python the user is using and use python?
I am using Anaconda for Windows and I do not know how I am supposed to do to make py -3 command available.  Each time I update leaderF, I got the warning message:

'py' is not recognized as an internal or external command,
operable program or batch file.

If you install python from https://www.python.org/downloads/windows/ , py command should be available.

This  is what py is.

Anaconda is a standard python distribution which is very popular. How do we use python provided by Anaconda instead of the Python distribution from official Python website？

I think if you install another version of python from  https://www.python.org/downloads/windows/, py command should also be installed and py can also launch python installed by Anaconda.

Thanks for your suggestion. But I would rather keep just more python distribution instead of two to simply install a plugin. Maybe I should just use this plugin without the c extensions.


Installation error when installing with Node 4.2.1 and 5.0.0

Error output is here: http://pastebin.com/6XtgESUr
Information about the system and environment can be found here by expanding the "Build system information" section at the top of the output: https://travis-ci.org/GoogleCloudPlatform/cloud-trace-nodejs/jobs/88848714

I believe that the cause of your error is in the first error message on line 196 of that paste:
../node_modules/nan/nan.h:41:3: error: #error This version of node/NAN/v8 requires a C++11 compiler

Ah, thank you! Grabbing gcc 4.8 fixed things up. Sorry I missed that.


The OracleJDK Exorcism

"Unmaintained security disaster" -anonymous Nixpkgs maintainer

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@techknowlogick I see that you’ve made changes to the Atlassian packages recently – the NixOS module says that Atlassian only support the Oracle JDK, but reference a bug that appears to be related to some regex parsing issue of the java -version output? It seems like our OpenJDK packages should work fine with that, but also our Oracle JDK packages haven’t been updated since 2021(!!) and since they’re just builds of OpenJDK with a weird/bad licence, it seems like substituting our Nixpkgs‐built OpenJDKs should be fine. Just wanted to check that you think this should be fine, as I have no way of testing the modules.

@emilazy, thanks for the ping. I've since stopped using the Atlassian software suite, and I should probably rm my maintainership on those packages. TBH, I'd suggest making this switch as I'm not sure how much these are used with how few (see: none) reports came through for them being out of date, so if this PR breaks them, it might not have much impact.


Aggregate 1.4.13 fails to start with PostgreSQL 9.3

When installing Aggregate 1.4.13 with a PostgreSQL 9.3 backend, the application fails to initialise. With PostgreSQL 9.5 it works fine.
Configuration
WAR deployment on Tomcat 8.5.11 on Ubuntu 14.04 LTS with default JRE (OpenJDK 7u121) and default PostgreSQL (9.3). Freshly created database using create_db_and_user.sql.
Problem description
The application fails to start. SQL exceptions are logged in catalina.out. The innermost exception thrown is java.sql.SQLException: validationQuery didn't return a row.
Diagnosis
The validation query referenced in the root exception is set in the validationQuery property on the dataSource bean in WEB-INF/lib/ODKAggregate-settings.jar:odk-settings.xml to be select schema_name from information_schema.schemata limit 1.
When executing that query as the odk database user against its database on PostgreSQL 9.3, the query returns 0 records. On PostgreSQL 9.5 it returns 1 record.
The issue seems specific to PostgreSQL 9.3, not to the odk database user. Any regular database user executing that query gets an empty result on 9.3, and 1 record on 9.5.  The postgres superuser does get the expected 1 record on both.
AFAIK my 9.3 and 9.5 database instances are configured identically. Maybe there was a default permissions change between PostgreSQL versions?
Workaround
My (quick &  dirty) workaround was to replace the validationQuery by select 1:
jar xf ODKAggregate.war WEB-INF/lib/ODKAggregate-settings.jar
jar xf WEB-INF/lib/ODKAggregate-settings.jar odk-settings.xml
sed -i -e 's/schema_name from information_schema.schemata limit//' odk-settings.xml
jar uf WEB-INF/lib/ODKAggregate-settings.jar odk-settings.xml
jar uf ODKAggregate.war WEB-INF/lib/ODKAggregate-settings.jar

I've updated the Aggregate 1.4.13 upgrade steps to direct users to upgrade to PostgreSQL 9.4 or newer. This appears to be an issue with permissions required to access to the information_schema content. That appears to be resolved in 9.4 and higher.

Thanks @mitchellsundt but wouldn't it be better to change the validation query so as to make this work irrespective of PostgreSQL version? PostgreSQL 9.3 will be around for another year and a half, and in many places won't/can't be upgraded to 9.4.
In applications that don't create their own tables, the validation query usually checks that some core table is found in the database, so that the application can "fail fast" when connected wrongly. In our case, where there may or may not be ODK tables yet in the database, the purpose of the validation query is really only to check that there is a PostgreSQL at the other end of the connection. For this, a SELECT 1 would suffice.
Using SELECT schema_name FROM information_schema.schemata WHERE schema_name = 'my-expected-schema-name' would add some value to the validation. However SELECT schema_name FROM information_schema.schemata LIMIT 1 adds close to none relative to SELECT 1.

Yes, the validation query could be changed BUT, within ODK Aggregate, we MUSTbe able to run select statements against the information_schema. If that fails, then ODK Aggregate will never function correctly.  So in this case, having a validation query that confirms you can access the information_schema is actually beneficial, as it catches this failure very early.
e.g.,
https://github.com/opendatakit/aggregate/blob/master/src/main/java/org/opendatakit/common/persistence/engine/pgres/DatastoreImpl.java#L180
The remedy is to add a grant to that schema when running against older versions.
e.g., something like the following as part of the create_db_and_user.sql content:
grant all privileges on schema "information_schema" to "your_odk__user";
Or perhaps just "usage" ?  I am unclear whether usage would be sufficient for running select queries against the tables within the schema.

This is a puzzling failure that seems to be an issue with how 9.3 does grants, as everything was working on 9.1.x, and then everything is working on 9.4 (the version I used when updating everything to use JDBC 4 and Tomcat 8).

GRANT either USAGE or ALL on information_schema did not help so I looked a bit deeper. I've spotted the issue, and think I've got the clean solution.
Strangely, SELECT * FROM information_schema.columns works fine, which probably explains why my ODK instance is actually working on 9.3 ... until it breaks on another possible information_schema.* table permissions issue :-/
So what is the issue with information_schema.schemata? Looking at its definition (using \d+  information_schema.schemata in psql) gave a clue. It is defined as a view, with one significant difference between 9.3 and 9.5:
SELECT ... FROM pg_namespace n, pg_authid u ...
-- 9.3
WHERE n.nspowner = u.oid AND pg_has_role(n.nspowner, 'USAGE'::text);
-- 9.5
WHERE n.nspowner = u.oid AND (pg_has_role(n.nspowner, 'USAGE'::text)
                              OR has_schema_privilege(n.oid, 'CREATE, USAGE'::text));

Note that n aliases pg_namespace which is the 'real' table of schemata, and u aliases pg_authid, the table of user accounts (needed only to display the schema owner names).
The WHERE clause filters the rows the user gets to see. The check pg_has_role checks that the current user has the USAGE permission for the role n.nspowner. In other words, can the ODK user assume the role of the schema owner? Since the schema owner of the ODK schema is postgres this is false.
On 9.5, things work out because of the disjunct: the ODK user does have USAGE (and CREATE) privilege for the ODK schema (even if postgres is the schema owner), as the schema sits in its own ODK database, for which it is granted ALL.
The obvious solution then is to make the ODK user the owner of its own schema.
In create_db_and_user.sql, add the statement alter schema "odk_schema" owner to "odk_user"(in fact, this could probably replace the current `grant all privileges on schema "odk_schema" to "odk_user").

Can you confirm that the additional grant on information_schema is not required?
I will add the alter-owner to the script. Update will be in the next ODK Aggregate release (no ETA).

I have just tested it on 9.3 with a freshly created user and database, and no grants (either on information_schema or the odk_schema) are needed:
create database testdb;
create user testuser with unencrypted password 'secret';
alter database testdb owner to testuser;
\c testdb
You are now connected to database "testdb" as user "postgres".
create schema testschema;
alter schema testschema owner to testuser;
\c testdb testuser
You are now connected to database "testdb" as user "testuser".
select count(*) from information_schema.schemata
1
(1 row)

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain beorse.net has exceeded the max emails per hour (307/250 (122%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from o8.sgmail.github.com ([<IP_ADDRESS>]:40413)
by hp159.hostpapa.com with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.89)
(envelope-from<EMAIL_ADDRESS>id 1dgMDo-000f71-RT
for<EMAIL_ADDRESS>Fri, 11 Aug 2017 22:32:16 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=q0VgpF/y8CuZz9Uu8XxTsaOOSMc=; b=ooDdWDg8sHY+cIUu
jo2qZYqBiWr+veHMsWDBGFqb1AE69sbDeQD9qDWTso1zmh5BvRxmYsYjBTY+9oxv
DVqYYIhbek5caKv2TMaJynENzOA6j6XXSULPWTh4boBP9TJ7CrTn3nFafj2L4VFv
GsgINrAx7U5LcyY0imlctCasV10=
Received: by filter0941p1mdw1.sendgrid.net with SMTP id filter0941p1mdw1-27688-598E6889-19
2017-08-12 02:31:37.233469507 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id SoLjUkVLTT6UuoniaatZfQ
for<EMAIL_ADDRESS>Sat, 12 Aug 2017 02:31:37.182 +0000 (UTC)
Date: Sat, 12 Aug 2017 02:31:37 +0000 (UTC)
From: Open Data Kit<EMAIL_ADDRESS>Reply-To: opendatakit/opendatakit<EMAIL_ADDRESS>To: opendatakit/opendatakit<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [opendatakit/opendatakit] Aggregate 1.4.13 fails to start with
PostgreSQL 9.3 (#1270)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_598e6889f7e8_381f3ff40beedc2c10118b";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: opendatakit-bot
X-GitHub-Recipient: jbeorse
X-GitHub-Reason: subscribed
List-ID: opendatakit/opendatakit <opendatakit.opendatakit.github.com>
List-Archive: https://github.com/opendatakit/opendatakit
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AAUZr8PFZvQz6KBUlsAmuDYH5pE2D3Kmks5sXQ6JgaJpZM4L6rt4
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: JVRD81wLmvjBgNlAmNtibjEbEEhcPGKEESixoxP2c45oX6un8Aa4uwMXI6dRUdoDSRq1myArXLY9LF
DKtOjuk/q36VmYlubODRF2Da/aXYg64LG0sKCam4T+ud3sqeUXjwvyIWLng0OxkBURhlu1g8+RWiIL
yCP9qPcAmgYYVFd3FaclW5kBjzQ7G6brY2ajvDA9X2KQCw8R00siMqS0rM/qeE8ZQkAan2SDiiff3K
I=
----==_mimepart_598e6889f7e8_381f3ff40beedc2c10118b
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #1270.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/opendatakit/opendatakit/issues/1270#event-1203484615
----==_mimepart_598e6889f7e8_381f3ff40beedc2c10118b
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #1270.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_598e6889f7e8_381f3ff40beedc2c10118b--


The difference between Fpz-T8-Oz-T7 and Nz-T10-Iz-T9

Hi，this repo works for me. May I know the difference between the two modes (Fpz-T8-Oz-T7 and Nz-T10-Iz-T9)?

Hi @zhaoyanxi, you can read more about that here: https://stefanappelhoff.com/eeg_positions/generated/eeg_positions.get_elec_coords.html#eeg_positions.get_elec_coords under the equator_contour parameter:

Control which contour line of electrodes should be at the equator of the sphere. Both permissible options ("Nz-T10-Iz-T9" or "Fpz-T8-Oz-T7") are reasonable assumptions. Selecting "Nz-T10-Iz-T9" is recommended, because the electrodes Nz, T9, and T10 correspond to the anatomical landmarks NAS, LPA, and RPA in our spherical head model (see Notes section). Thus, the anatomical landmarks lie on the equator, and all electrodes are drawn inside a circule head shape when projecting to 2D. The option to select "Fpz-T8-Oz-T7" is provided (but not recommended), because this contour line corresponds to where the head circumference would be measured for real humans. However, when selecting "Fpz-T8-Oz-T7" as the equator, several electrodes may be drawn outside a circular head shape when projecting to 2D. Defaults to "Nz-T10-Iz-T9".

Basically: We compute the electrode positions on a sphere according to the 10-20 (or by logical extension 10-10, or 10-05) system. For that we have to make some assumptions: such as which electrodes lie on the equator of our sphere. Practically it makes only little difference, and I recommend the default ("Nz-T10-Iz-T9").


Cannot instantiate interface Bernard\Serializer

I'm using bernard, 0.13.0.
Whenever I execute my function to get the queue factory, the following error is raised:
php background-logic/consumer.php consume
PHP Fatal error:  Uncaught Error: Cannot instantiate interface Bernard\Serializer in /Users/robskrob/code/scrap/bernard-toy/background-logic/message-queue.php:20
Stack trace:
#0 /Users/robskrob/code/scrap/bernard-toy/background-logic/consumer.php(23): MessageQueue->getQueueFactory()
#1 /Users/robskrob/code/scrap/bernard-toy/background-logic/consumer.php(58): consume()
#2 /Users/robskrob/code/scrap/bernard-toy/background-logic/consumer.php(62): main()
#3 {main}
  thrown in /Users/robskrob/code/scrap/bernard-toy/background-logic/message-queue.php on line 20

Why can I not instantiate Bernard\Serializer here?

You are using the example from master and not the example from 0.13 (or we haven't updated the example).
In 0.13 you can use one of the implementations https://github.com/bernardphp/bernard/blob/0.13.0/src/Bernard/Serializer/SimpleSerializer.php

@henrikbjorn thank you for sharing SimpleSerializer. Also, per version I will check this example.


ci: add url check

As the URL check simply uses git diff, and url_check.sh contains a line with URL, this PR is intended to fail on check_url.

👍👍

😥


[feature] want to add MComment  components

Want to add a comment panel for a comment.

Rejected, not a common component.


stopwatch wait for jenkins

when waiting for jenkins we should see a message
[date time sec] - Waiting until Jenkins is up...
new message should show up every 10 seconds.

Fixed.


Modify mainnet params for 2/4/8, block version=5

Makes 2 changes to the BIP101 implementation:

Initial post-fork block size limit is 2MB
The limit doubles twice, at 2-year intervals

Earliest activation is not changed.  Grace period is not changed.
Block version is set to 5.
There is no BIP that corresponds exactly to this PR.  It is BIP101 with the above changes.
No testnet parameters are changed (testnet still supports 8MB and 10 doublings).

Hi guys, just want you to know I am on board here.  I have been working for this option both at the google groups, and reddit.  jtoomim has really done some great work in in development and testing.  Thanks to him we have all the data necessary to argue our point.  In particular we know we best represent the option that the miners and business community can most likely support.  2-4-8 is the most sensible and practical option.  This option takes out the unnecessary forward predictions that we won't be using anyway because we are going to develop dynamic models instead.  The block limit should only be a last resort and way above what is happening in the code which is what should be used to determine the block size.

Hi guys, just want you to know I am on board here.  I have been working for this option both at the google groups, and reddit.  jtoomim has really done some great work in in development and testing.  Thanks to him we have all the data necessary to argue our point.  In particular we know we best represent the option that the miners and business community can most likely support.  2-4-8 is the most sensible and practical option.  This option takes out the unnecessary forward predictions that we won't be using anyway because we are going to develop dynamic models instead.  The block limit should only be a last resort and way above what is happening in the code which is what should be used to determine the block size.

Sorry if others already know this, but does this implementation have a "smooth" increase in block size over time, or does it literally double at fixed intervals every two years?
I believe I heard Gavin mention that the existing BIP101 code had smooth increases over time, which I believe is a good thing (BIP202 has similar properties).

Sorry if others already know this, but does this implementation have a "smooth" increase in block size over time, or does it literally double at fixed intervals every two years?
I believe I heard Gavin mention that the existing BIP101 code had smooth increases over time, which I believe is a good thing (BIP202 has similar properties).

@amacneil It increases linearly between the doubling points.

@amacneil It increases linearly between the doubling points.

I agree with jtoomim about changing the activation condition but think 80% is sufficient.  I don't know enough about the details of the code to suggest core over xt, but would say: If it was core we have to take out RBF and any connections they have been rigging to support their LN.

I suggest leaving this at nMaxSizeDoublings = 10;

The whole point is we are getting away from forward predictions that are too far out.  The odds of these guesses being successful tends to zero quicker than we think.  They will be unnecessary as we will have dynamic code, even Gavin Andresen has referred to it.  And finally for all that zero gain we put off most of the hashing power.  Yes, by some super small chance the guess could turn out to be correct and used, but making the guess itself decreases the odds by much more that the code would ever be considered for use.

I 100% agree with you we can't make forward predictions that far out.  Heck, we can't even make accurate forward predictions a few weeks out let alone a few years.  I don't expect to be able to guess this correctly at all. But no matter what you do about the block size, you're making a guess today.  Making the limit stop growing at 8MB is making a guess today that 8MB will be enough.
Which is exactly why I'm arguing it should keep doubling, we can't possible know today when to stop the block size from growing.  We can't possible know if 8MB is the best limit or 16MB or any other number.  The block size limit should stop growing when we have a reason and make the choice to stop it from growing.
I'm advocating that we adopt a strategy of "future inaction won't change the economic conditions".  I'm just fine with changing the economic conditions someday, I just want to see that happen due to deliberate action of the community.
All that said, if Jon is correct, and leaving it a 2 doublings is required to get the miners on board.  So be it.

All that said, if Jon is correct, and leaving it a 2 doublings is required to get the miners on board. So be it.

Quick recap:

The chance we guess correctly tends to zero quickly.
As we go out to 2020 we almost surely will have dynamic code instead.
By guessing we open ourselves up to criticism and put off miners thereby reducing not increasing the chance that the code runs to begin with which is more important than the many year out guess.
The whole point of 2-4-8 is it just goes to 8 otherwise it's really back to being xt.  (I know xt is starting at 8mb)
There will be likely other reasons for hard forks before 2020 including a properly done SegWit.  Assuming we want that at all.
Additionally:
I would add hard forks have been made out to be something negative when in fact it's just a way of continuing to get community consensus.  We are not Core trying to get our way with passive aggressive soft forks that lack consensus.  Nor are we trying to get our way by advance for so many years out.  We want continued consensus and are not afraid of it.

We need the following before we can get listed at Coin Dance or xtnodes.com:
Homepage Link  Not same as Github / Download Page Link / FAQ/Help Page Link  // Downloadable files
I have a hosting package and could make the homepage link and format for that page, but would prefer if someone else was helping write it.  Are we all okay with a fork of xt or do we want to fork Core?

I do not mind having a version of this built off of the XT code. However, I do object to not having a version of this built off of the Core code. The miners have been very explicit that they want this in Core, and I intend to follow their wishes.
Besides, Core has a lot of good code that's been added recently. I've wanted to use that code a lot while hacking on XT stuff. I disagree with some of the changes that they've made, but most of the changes have been pure technical improvements, and not politically charged crap.
If you guys are focusing on an XT-based branch, I will not be investing much effort in it, and will instead be working on a branch that I'll make off of Core. I may try to cherry-pick code into that new Core fork.

@barmstrong (just blogged a cool<EMAIL_ADDRESS>for how to count votes:

I’d like to propose a new way to think about measuring votes where only explicit votes are counted. Right now, default blocks are being counted as a vote for bitcoin core, but it could be that miners haven’t had a chance to upgrade or they don’t want to vote at all (as they’ve stated).

We should give miners the option of making an explicit vote for bitcoin core if they want it, or a way to abstain and not vote at all.

It would be very helpful to see if miners are actually voting against this proposal, or just are too lazy to consider it. Is there a way to let them vote and say that they actively reject it, vs. just not bothering to vote?

Some miners know they have no say in hardforks, and will refuse to vote on such things period on principle.

@toomim I can add that pretty easily to my spreadsheet... Done.
https://docs.google.com/spreadsheets/d/1Cg9Qo9Vl5PdJYD4EiHnIGMV3G48pWmcWI3NFoKKfIzU/edit#gid=1056384823

@jtoomim Most of the new code in Core is crap and would have to be removed anyway (e.g. the RBF stuff, the SegWit soft fork, the connection count limiting etc).
So I'm not in favour of changing XT to do something that isn't specified as a BIP anywhere, has bizarre changes with no justification (e.g. block height instead of timestamp, why?), and which miners are already saying they won't run (again, without justification).
I know I said a few days ago in email I'd be OK with this, but I changed my mind. I'm going to close this. As 2/4/8 is a bad technical choice anyway (2mb is nowhere near enough excess capacity for a robust network even with current conditions) and the only justification for it is "miners say they might consider that", but miners are also not yet ready to accept that Core is a writeoff, I see no reason to use XT for this.


tado: Cannot set "Off" state

Home Assistant release (hass --version):
0.41 (docker)
Component/platform:
tado
Description of problem:
I cannot set tado climate to "Off" using the UI or automation scripts.
Expected:
Mode changes to "Off"
Traceback (if applicable):
17-03-29 16:23:45 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "uvloop/future.pyx", line 374, in uvloop.loop.BaseTask._fast_step (uvloop/loop.c:112704)
  File "/usr/src/app/homeassistant/core.py", line 1010, in _event_to_service_call
    yield from service_handler.func(service_call)
  File "/usr/src/app/homeassistant/components/climate/__init__.py", line 362, in async_operation_set_service
    yield from climate.async_set_operation_mode(operation_mode)
  File "uvloop/future.pyx", line 230, in __iter__ (uvloop/loop.c:110600)
  File "uvloop/future.pyx", line 432, in uvloop.loop.BaseTask._fast_wakeup (uvloop/loop.c:113980)
  File "uvloop/future.pyx", line 101, in uvloop.loop.BaseFuture._result_impl (uvloop/loop.c:108900)
  File "/usr/local/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/src/app/homeassistant/components/climate/tado.py", line 178, in set_operation_mode
    self._control_heating()
  File "/usr/src/app/homeassistant/components/climate/tado.py", line 286, in _control_heating
    self._store.set_zone_overlay(self.zone_id, CONST_OVERLAY_MANUAL)
TypeError: set_zone_overlay() missing 1 required positional argument: 'temperature'

Additional info:
https://github.com/wmalgadey/tado_component/tree/f6e266856f864ad65c240af4fd7bd845fd3f14a0 works for me. I was using this before, just changed SMART_SCHEDULE to Smart Schedule and OFF to Off in my scripts.

@wmalgadey
I'd also like to get confirmation whether this is OK or if I should use the old all-caps modes:

I was using this before, just changed SMART_SCHEDULE to Smart Schedule and OFF to Off in my scripts.

I have to check this! I suppose you have to use the new readable values. They are translated to the correct ones known to tado.

I think I found the reason for the error. A commit is on the way, think it has to be merged!
And to give a complete answer to your second question: Yes I think you have to use the readable values, any method accessible external are using the readable values.

Many thanks! Looking forward to the updated version!

so! letzt hope https://github.com/home-assistant/home-assistant/pull/6848/ gets merged fast ;)

Closed with #6848


Adding document references to choice fields in "campaign" models

Your mission
Add a documentcloud_pages attribute to a model for one of the choice fields on the campaign tables.
This will connect our code with the official government documentation so we can incorporate it as part of our expanded version.
To-do list
According to our documentation unit tests, the following choice fields in campaign.py lack any reference to official CAL-ACCESS documentation.

[ ] Cvr2SoCd.form_type
[ ] CvrCampaignDisclosureCd.form_type
[ ] Cvr2CampaignDisclosureCd.form_type
[ ] RcptCd.form_type
[ ] Cvr3VerificationInfoCd.form_type
[ ] LoanCd.form_type
[ ] S401Cd.form_type
[ ] ExpnCd.form_type
[ ] F495P2Cd.form_type
[ ] DebtCd.form_type
[ ] S496Cd.form_type
[ ] S497Cd.form_type
[ ] F501502Cd.form_type
[ ] S498Cd.form_type
[ ] CvrF470Cd.form_type
[ ] Cvr2SoCd.off_s_h_c
[ ] CvrCampaignDisclosureCd.off_s_h_c
[ ] Cvr2CampaignDisclosureCd.off_s_h_c
[ ] RcptCd.off_s_h_c
[ ] S401Cd.off_s_h_c
[ ] ExpnCd.off_s_h_c
[ ] S497Cd.off_s_h_c
[ ] S498Cd.off_s_h_c
[ ] CvrF470Cd.off_s_h_c
[ ] CvrSoCd.rec_type
[ ] Cvr2SoCd.rec_type
[ ] CvrCampaignDisclosureCd.rec_type
[ ] Cvr2CampaignDisclosureCd.rec_type
[ ] RcptCd.rec_type
[ ] Cvr3VerificationInfoCd.rec_type
[ ] LoanCd.rec_type
[ ] S401Cd.rec_type
[ ] ExpnCd.rec_type
[ ] F495P2Cd.rec_type
[ ] DebtCd.rec_type
[ ] S496Cd.rec_type
[ ] S497Cd.rec_type
[ ] F501502Cd.rec_type
[ ] S498Cd.rec_type
[ ] CvrF470Cd.rec_type
[ ] F501502Cd.party_cd
[ ] Cvr2SoCd.sup_opp_c
[ ] CvrCampaignDisclosureCd.sup_opp_c
[ ] Cvr2CampaignDisclosureCd.sup_opp_c
[ ] RcptCd.sup_opp_c
[ ] S401Cd.sup_opp_c
[ ] ExpnCd.sup_opp_c
[ ] S497Cd.sup_opp_c
[ ] S498Cd.sup_opp_c
[ ] F501502Cd.elec_type
[ ] CvrCampaignDisclosureCd.reportnam
[ ] ExpnCd.expn_code
[ ] DebtCd.expn_code

Here's how
Step 1: Claim a field from the to-do list above by leaving a comment below. Tell everyone you're ON IT!
Step 2: Open up the file that contains this model. It should be in calaccess_raw.models.campaign.py.
Step 3: Hit the little pencil button in the upper-right corner of the code box to begin editing the file.

Step 4: Find the your field in the file. It will be under the specific model (aka, data table) specified above (Clicking into the box and searching with CTRL-F can help you here.) Once you find it, we expect the field to lack the documentcloud_pages attribute we want to ensure every model has attached. If it's already there it would look something like this:
@python_2_unicode_compatible
class MyFakeModel(CalAccessBaseModel):
    """
    Blah blah blah.
    """
    UNIQUE_KEY = (
        "WHATEVER",
    )
    # other attributes, including other fields on the model / data table
    your_field = fields.CharField(
        max_length=4,
        db_column="YOUR_FIELD",
        choices=YOUR_FIELDS_CHOICES,
        help_text='Blah blah blah',
        documentcloud_pages=[
            DocumentCloud(id='2756977-Lookup-Codes-Cd', start_page=21, end_page=22),
        ]
    )

A properly configured documentcloud_pages attribute will contain one or more DocumentCloud items that specify where this table is explained in the state's official documentation. The links draw their name from the documentcloud.org hosting service where we are republishing the state's source documents, which were provided in PDF format.
If it's already there, the work is already done and you need to pick another field. If it's not, it's going to be your job to add it.
Step 5: In a separate tab, open up the official state documentation.
Step 6: Find the pages with useful info about the look-up values.
Step 7: Note the document's start and end pages as well as the id in the DocumentCloud URL (Hint: It's probably '2756977-Lookup-Codes-Cd').
Step 7: Return to the GitHub tab.
Step 8: Add a documentcloud_pages list that includes points to the pages you just found. If your model is found on pages 200 and 201 of the state documentation linked above, you'd fill add these three lines:
    documentcloud_pages = [
        DocumentCloud(id='2756977-Lookup-Codes-Cd', start_page=200, end_page=201),
    ]

But indented below the field's model and name (as seen in the above example).
Step 9: Scroll down below the code box and describe the change you've made in the commit message. Press the button below.

Step 10:  Review your changes and create a pull request submitting them to the core team for inclusion.

That's it! Mission accomplished!

I'm gonna grab this one Cvr2SoCd.form_type

I picked off the last three.

This quick SQL query I hacked together will return all of the form_type values in the campaign models. Before we define a global set of form_type option we should probably integrate the other models files as well.
SELECT *
FROM (
	SELECT 'CVR_F470_CD', "FORM_TYPE", COUNT(*)
	FROM "CVR_F470_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'S498_CD', "FORM_TYPE", COUNT(*)
	FROM "S498_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'F501_502_CD', "FORM_TYPE", COUNT(*)
	FROM "F501_502_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'S497_CD', "FORM_TYPE", COUNT(*)
	FROM "S497_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'S496_CD', "FORM_TYPE", COUNT(*)
	FROM "S496_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'DEBT_CD', "FORM_TYPE", COUNT(*)
	FROM "DEBT_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'F495P2_CD', "FORM_TYPE", COUNT(*)
	FROM "F495P2_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'EXPN_CD', "FORM_TYPE", COUNT(*)
	FROM "EXPN_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'S401_CD', "FORM_TYPE", COUNT(*)
	FROM "S401_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'LOAN_CD', "FORM_TYPE", COUNT(*)
	FROM "LOAN_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'CVR3_VERIFICATION_INFO_CD', "FORM_TYPE", COUNT(*)
	FROM "CVR3_VERIFICATION_INFO_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'RCPT_CD', "FORM_TYPE", COUNT(*)
	FROM "RCPT_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'CVR2_CAMPAIGN_DISCLOSURE_CD', "FORM_TYPE", COUNT(*)
	FROM "CVR2_CAMPAIGN_DISCLOSURE_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'CVR2_SO_CD', "FORM_TYPE", COUNT(*)
	FROM "CVR2_SO_CD"
	GROUP BY 1, 2

	UNION

	SELECT 'CVR_CAMPAIGN_DISCLOSURE_CD', "FORM_TYPE", COUNT(*)
	FROM "CVR_CAMPAIGN_DISCLOSURE_CD"
	GROUP BY 1, 2
) as form_type_table
ORDER BY 1, 2, 3 DESC

I just expanded the above query to pull form_type values from all models where I could find the field. I will run a fresh database installation and then post the values I get back. We can then use that to create a centralied FORM_TYPE_CHOICES lookup that can be shared among the fields.


Bot unable to listen to its own messages

Haven't found anything in the docs or other issues for this-- is it possible for the hubot rc adapter to relay back messages emitted by itself?

There is code explicitly put in place to prevent this. What's the use case here?

I stumbled onto this issue too after writing a few scripts for Hubot. I schedule the bot to post a poll with the command !poll "Question" "Answer 1" "Answer 2". I also have it scan for these commands and count the number of answers, store that and when the poll is posted it adds the reactions from 1-9 so that the users won't have to search for them and also makes them appear in order.
This works fine as long as it's a user who posts the poll command. But when Hubot posts the sceduled command it won't work as it cannot trigger on its own messages and count the number of answers.
Also I'm having trouble getting the message id for messages sent by the bot. Listening for keywords could be a solution to get the message id and doing whatever you want with it. Not perfect but one way of doing it.


Fetch all links in the line

2015-12-20 13:55:57+0200 <@Mikaela> maybe I should have linked http://blogs.msdn.com/b/powershell/archive/2015/06/03/looking-forward-microsoft-support-for-secure-shell-ssh.aspx & http://blogs.msdn.com/b/powershell/archive/2015/10/19/openssh-for-windows-update.aspx instead?
2015-12-20 13:55:59+0200 < FatalException> [http://is.gd/UdWNaG] OpenSSH for Windows Update - Windows PowerShell Blog - Site Home - MSDN Blogs | [second short url] and title are missing here

[12:57] <Mikaela> your bot ignored the second link, it should separate the short URLs and titles with | in the middle and Limnoria has the same issue
[12:58] <NanoSector> i deliberately made it like that
[12:58] <Mikaela> why? :(
[12:58] <Mikaela> where is the issue tracker?
[12:58] <NanoSector> http://github.com/WildPHP/module-linksniffer
[12:58] <FatalException> [http://is.gd/ru9XWy] WildPHP/module-linksniffer · GitHub
[12:59] <NanoSector> because imo there's no clean way to implement multiple links
[12:59] <NanoSector> you'd either have to send multiple replies to the channel or separate them and risk getting the message split in multiple lines

tl;dr: Not sure if there's a clean way to properly implement this.

With the backends system this should be pretty easy to implement using the multiple-message method that more bots implement. With the async method used right now this should pose no (significant) issues.


phy-spikesort unexpectedly dies

Issue faced by Jonathan Herz.

This happened twice to me at exactly the same spot (So I don't think I pressed anything accidentally):

Extracting spikes: 75.61%. 11801 spikes extracted in chunk 93/122.
Killed

Running on 16 GB RAM

Any idea what might be causing this error message and termination?

Thanks
JH

can you check CPU and RAM usage over time, and at the time of termination?

@jonathanherz when you run this, could you
a) look at memory usage (run "top" in another terminal) and see if that's getting near the limit?
b) send us the contents (or last few lines) of /var/log/syslog (assuming you're on Ubuntu) to see if you're hitting the OOM killer or some other kernel issue?
c) after the script dies, run echo $? to see what return code it gave
My best bet is that it's running out of memory. Why, I'm not sure...

oh and also check disk usage: spike detection should not use much RAM, but will be quite heavy on HDD/SDD

It does look like I ran out of memory (some selected lines from /var/log/syslog):
Jul 15 01:53:24 theodore kernel: [17324.184617] Free swap  = 0kB
Jul 15 01:53:24 theodore kernel: [17324.184618] Total swap = 4104188kB
Jul 15 01:53:24 theodore kernel: [17324.184624] [ pid ]   uid  tgid total_vm      rss nr_ptes swm_sapents oocore_adj name
Jul 15 01:53:24 theodore kernel: [17324.184918] [ 3133]  1000  3133  4987138  3823327    9697   868785             0 phy
Jul 15 01:53:24 theodore kernel: [17324.184925] Out of memory: Kill process 3133 (phy) score 919 or sacrifice child
Jul 15 01:53:24 theodore kernel: [17324.184929] Killed process 3133 (phy) total-vm:19948552kB, anon-rss:15293308kB, file-rss:0kB
and echo:
jonathan@theodore:~/Documents/imec_iia_remap$ echo $?
137
I don't have a solid state drive.  Have 16GB RAM on this machine.  Are there any parameters I can change to make it less memory intensive?  The recording I'm trying to spike sort is only 2 minutes long, and I can't put any more RAM on this chipset
Thanks for looking into this, guys!

that's weird. It looks like a memory leak, right? Does the RAM slowly increase while spike detection is running? It seems not to be the case on my computer. What is your OS exactly?
At every chunk (1 second of data) the program should release any previously allocated memory. So RAM usage should be quite low (and it is on my computer, even on large datasets), except when finding the thresholds initially, and potentially when computing PCA at the end of spike detection. But here it appears to happen during spike detection...

Have you got a copy of the dataset and PRB/PRM files? We could try it
here...
On Wed, Jul 15, 2015 at 2:25 PM, Cyrille Rossant<EMAIL_ADDRESS>wrote:

that's weird. It looks like a memory leak, right? Does the RAM slowly
increase while spike detection is running? It seems not to be the case on
my computer. What is your OS exactly?
At every chunk (1 second of data) the program should release any
previously allocated memory. So RAM usage should be quite low (and it is on
my computer, even on large datasets), except when finding the
thresholds initially, and potentially when computing PCA at the end of
spike detection. But here it appears to happen during spike detection...
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/540#issuecomment-121616188.

you use the latest version?

The version is 0.2.0.dev0.
What is the best way to share the files with you?  Probably too big to e-mail.
I need to go to my day job and will be back in about 6-7 hours, and can try to run it again and closely watch the memory as Cyrille suggested.

@JonathanHerz OK, you could try again with the latest version (master), which is 0.3.0.dev0. I did a memory fix last week that may solve your problem.

@JonathanHerz - the release version (0.2.0) should have this fix, so you can follow the instructions on http://phy.cortexlab.net/ to install it (you should be able to do pip install phy).

still getting same behavior with both versions 0.2.1 (from pip install phy) and 0.2.2dev0 (which is what I was able to get from github).  Did not see 0.3.0.dev0.  It does look like a memory leak because I watched the System monitor each time - more and more memory was slowly gobbled up until the computer ran out of swap, then killed the process.

using version 0.2.2.dev0 I also tried increasing my swap file size so now have 16GB RAM + 16GB swap.  After increasing swap there was enough memory for "Extracting spikes to finish".  After "Spike extraction complete" message memory was not released.  "Computing the features" also finished but once I got the "All features computed and saved" message, memory usage started going back up and OS killed phy once memory+swap was exhausted.

Can you send us your dataset? What is your OS?
Le jeudi 16 juillet 2015, Jonathan Herz<EMAIL_ADDRESS>a écrit :

using version 0.2.2.dev0 I also tried increasing my swap file size so now
have 16GB RAM + 16GB swap. After increasing swap there was enough memory
for "Extracting spikes to finish". After "Spike extraction complete"
message memory was not released. "Computing the features" also finished but
once I got the "All features computed and saved" message, memory usage
started going back up and OS killed phy once memory+swap was exhausted.
—
Reply to this email directly or view it on GitHub
https://github.com/kwikteam/phy/issues/540#issuecomment-121829774.

OS is Ubuntu 14.04.  Data set is 640 MB.  What is the best way to send it over?

Dropbox? I'd need the PRM file as well.
Do you see the same RAM issue with the sample dataset (see quick start guide)?

Shared in dropbox - prm, dat, and prb.
Using the quick start guide it runs too fast to tell what is happening with the RAM in those steps since the data set is much smaller - I'm getting to klustakwik step in about 5 seconds.

Ok, that's an exaggeration.  10 seconds max.

OK thanks! Running it now on my Ubuntu 14.04 laptop. A few questions:

on this dataset and your laptop, how long does it take for the RAM to be full?
do you have a 64-bit system and 64-bit Python?
do you know your versions of NumPy and Python?

@nippoo is that possible that RAM doesn't increase on my laptop because I have a large SSD (there are a lot of memmaps under the hood)?

Takes maybe 20-30 minutes for RAM to fill up... It is a slow and gradual process where RAM usage increases constantly.  Does not suddenly die all at once.
64 bit OS, when I fire up Python console it is 64 bit:

sys.maxsize
9223372036854775807

Python version 3.4.3, Numpy version 1.9.2.  I'm using the Python that Max suggested - Anaconda or something like that?  Only using this computer for Spike Sorting, nothing else on it really.

OK thanks. RAM usage is steady on my laptop during spike detection, and also slowly increases during spike extraction. I'm working on a fix now.

OK thanks!  Glad you were able to reproduce the issue.

@JonathanHerz this should be fixed by https://github.com/kwikteam/phy/pull/552 -- can you try it?

This has been merged, right?  So if I
git clone https://github.com/kwikteam/phy/ && cd phy && python setup.py install
that should pick up the changes, correct?  Just did that and phy -v says "0.2.2.dev0", just want to confirm I'm on the right one
Thanks

Should be ok. @nippoo do you know why it doesnt show the full git version?

looks like all the spike detection and extraction was done quickly and without incident.  It's now running Klustakwik

@JonathanHerz @rossant you have to do python setup.py develop to see the git version, if you do install then it copies the files to a new non-git-tracked location - though you're running the same code either way.


Chef Client Service not starting after reboot on Windows

On a windows system whenever it reboots, the chef client service isn't started.
Specs:

Windows 2012 (no release packs)
Chef 12.0.3

The Eventlog says:
A timeout was reached (30000 milliseconds) while waiting for the Chef Client Service service to connect.

There is nothing in the chef-stacktrace.out file.
I tried changing it to "Automatic (Delayed)" but it didn't fix whatever is going wrong.
I'm happy to help troubleshoot this, if you can give me steps to check or try.

If it helps, I think this problem existed in chef 11 too.  But I've only been able to figure it out now that Chef 12 reports start and stop to the EventLog.

This applies to Windows 2008R2 and Windows 2012R1 as well.

@docwhat I ran into this issue today, but switching to delayed start is working as a workaround on 2008 and 2012.
Can you verify you're seeing the same behavior when using delayed start?

I manually changed it, rebooted, and I got the same message on win 2012

This issue bit me. I can confirm that changing the startup type to Automatic (Delayed Start) seems to resolve the problem on Windows 2012 R2.

I've also bumped into this in AWS(2012R2) w/ chef-client 12.0.0 - 12.0.3
EventLog shows:
The Chef Client Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

The workaround of changing from 'Automatic' to 'Automatic (Delayed start)' worked for me also on 2012R2.
This is the Chef resource to use in order to change the startup type until this issue is resolved:
registry_key 'HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\chef-client' do
  values [{
    :name => "DelayedAutostart",
    :type => :dword,
    :data => 1
  }]
  action :create
end

I've hit this too. Using the latest Chef-Client, built from Master some time last week. Unfortunately, the resource code my good man Mr Pop has put above, does create the registry key, but doesn't actually start my client service upon reboot. Manually starting the service, completes my chef-client run appropriately.

Not absolutely positive here, but changing
DelayedAutostart to DelayedAutoStart - (Notice the capital S)
Appears to have fixed this, at least for me. I thought Windows and the registry were case insensitive.

Hi, this workaround doesnt work for me, any idea to find root cause?
server win2012r2 (Platform:    windows 6.3.9600)
chef-client - 12.2.1
service starting well if i run it in manual mode but falling to start after server restart

I continually had this working in my last project, with the work-around, but it was with Win2012 R1, not R2, I'm unsure if R2 somehow breaks the work-around. My current project is using Win2008, so I may not get the chance to test this either.

well, my investigations continuing, we are using hyper-v, and vlans
so far we tested that chef-client as service successfully starts on virtualbox and hyper-v without vlan configuration. But when we turn it on and reboot server chef-client isn't starts.

This appears fixed for me in the latest Chef-Client. At least on Win 2008 R2, which is one of the systems people have complained about this bug with, the latest Chef-12.2.1-1 client appears to be setting itself to Automatic(Delayed Start) without my intervention.

I am a coworker of vvchik and I can reproduced this.
The chef client starts automatically when there is no network connectivity on Windows 2012r2
As soon as we connect the network, then the chef client fails to start by itself.
The variable that makes the difference is network connectivity.
Chef <IP_ADDRESS>

There is a stacktrace.out file that is generated
Generated at 2015-04-17 18:19:10 -0400
SocketError: Error connecting to https://foobar.example.com/organizations/dev/nodes/host01 - getaddrinfo: No such host is known.
C:/opscode/chef/embedded/lib/ruby/2.0.0/net/http.rb:878:in `initialize'
C:/opscode/chef/embedded/lib/ruby/2.0.0/net/http.rb:878:in `open'
C:/opscode/chef/embedded/lib/ruby/2.0.0/net/http.rb:878:in `block in connect'
C:/opscode/chef/embedded/lib/ruby/2.0.0/timeout.rb:66:in `timeout'
C:/opscode/chef/embedded/lib/ruby/2.0.0/net/http.rb:877:in `connect'
C:/opscode/chef/embedded/lib/ruby/2.0.0/net/http.rb:862:in `do_start'
C:/opscode/chef/embedded/lib/ruby/2.0.0/net/http.rb:851:in `start'
C:/opscode/chef/embedded/lib/ruby/2.0.0/net/http.rb:1367:in `request'
C:/opscode/chef/embedded/apps/chef/lib/chef/http/basic_client.rb:65:in `request'
C:/opscode/chef/embedded/apps/chef/lib/chef/http.rb:261:in `block in send_http_request'
C:/opscode/chef/embedded/apps/chef/lib/chef/http.rb:293:in `block in retrying_http_errors'
C:/opscode/chef/embedded/apps/chef/lib/chef/http.rb:291:in `loop'
C:/opscode/chef/embedded/apps/chef/lib/chef/http.rb:291:in `retrying_http_errors'
C:/opscode/chef/embedded/apps/chef/lib/chef/http.rb:255:in `send_http_request'
C:/opscode/chef/embedded/apps/chef/lib/chef/http.rb:142:in `request'
C:/opscode/chef/embedded/apps/chef/lib/chef/rest.rb:115:in `get'
C:/opscode/chef/embedded/apps/chef/lib/chef/node.rb:499:in `load'
C:/opscode/chef/embedded/apps/chef/lib/chef/node.rb:483:in `find_or_create'
C:/opscode/chef/embedded/apps/chef/lib/chef/policy_builder/expand_node_object.rb:92:in `load_node'
C:/opscode/chef/embedded/apps/chef/lib/chef/client.rb:233:in `load_node'
C:/opscode/chef/embedded/apps/chef/lib/chef/client.rb:435:in `run'
C:/opscode/chef/embedded/apps/chef/lib/chef/application.rb:253:in `run_with_graceful_exit_option'
C:/opscode/chef/embedded/apps/chef/lib/chef/application.rb:230:in `block in run_chef_client'
C:/opscode/chef/embedded/apps/chef/lib/chef/local_mode.rb:38:in `with_server_connectivity'
C:/opscode/chef/embedded/apps/chef/lib/chef/application.rb:213:in `run_chef_client'
C:/opscode/chef/embedded/apps/chef/lib/chef/application/client.rb:365:in `run_application'
C:/opscode/chef/embedded/apps/chef/lib/chef/application.rb:60:in `run'
C:/opscode/chef/embedded/apps/chef/bin/chef-client:26:in `<top (required)>'
C:/opscode/chef/bin/chef-client:63:in `load'
C:/opscode/chef/bin/chef-client:63:in `<main>'

The chef service will start and stay running if you open services.msc and click the start button. Even when there is internet connectivity.
Service Order
I've verified that the windows machine can resolve 'foobar.example.com'.
jaym in the IRC Chanel theorizes that the chef client is starting before the DNS service. I've added the following dependencies to the chef-client. (The space is required after depend=)
sc config chef-client depend= LanmanServer/Dnscache

This had no luck. After 2 minutes, the chef-client service tried to start, but failed. No stacktrace was generated. I was able to start the process manually by clicking 'start' in services.msc
Event Viewer
The only thing that the event viewer shows is " A timeout was reached (30000 milliseconds ) while waiting for the chef client to start".
Interestingly, if I reboot the VM and quicky attempt to start the chef process manually, I get this error.

Surprisingly, if I wait 2 minutes, the chef process will start by itself. Attempting to start the process manually (even though it fails) appears to "dislodge" whatever was stopping the service from starting itself.
I've also tried setting the service to recover itself 2 more times after 1 minute, Strangely, windows did not honor this setting and gave up after one attempt.

The bug is likely in this code, however I am at a loss of how to further troubleshoot this problem.
https://github.com/chef/chef/blob/master/lib/chef/application/windows_service.rb

After updating my bootstrapping scripts (cloudformation) to install chef-client 12.3.0-1 instead of 11.16.4-1, I'm seeing the same error as the dialog above (Error 1053: ...). In troubleshooting the issue, I noticed that the Path to executable in the service config is:
"C:\opscode\chef\embedded\bin\ruby" "C:\opscode\chef\embedded\lib\ruby\gems\bin\chef-windows-service"  -c C:\chef\client.rb -L C:\chef\log\client.log
When I look for these things on the filesystem, I see that chef-windows-service is located in:
C:\opscode\chef\embedded\lib\ruby\gems_2.0.0_\bin
Comparing this to an older instance running chef-client 11.16.4-1 I see:
"C:\opscode\chef\embedded\bin\ruby" "C:\opscode\chef\embedded\lib\ruby\gems_1.9.1_\gems\chef-11.16.4-x86-mingw32\lib\chef\application\windows_service.rb"  -c C:\chef\client.rb -L C:\chef\log\client.log
It looks as if some PR has borked out the version. I'm not sure how to reconcile this with the workarounds and spontaneous fixes mentioned above as I can't see how the path would be corrected.

We worked around it by specifying an older version of chef while bootstrapping.
knife bootstrap --bootstrap-version 11.xx

Falling back to the 12.2.1-1 msi fixes the issue for me.

ping @chef/client-windows

@thom we'll pull it into our committed lane next week.

For those still having issues, please try this workaround: sc.exe config chef-client depend= dnscache and report back.

I tried this first with the default install of the chef-client service and then with the dependency set.  Both failed on startup.  The only way this works for me is if the Delayed Start option is selected.  I am running Windows Server 2008 R2 for reference.  In addition there are no logs anywhere to show what the error is

@bigbam505 what version of Chef are you using? Delayed Start became the default in https://github.com/chef/omnibus-chef/pull/346, which based on the date it was merged would have been in Chef 12.1.0. /cc @jdmundrawala.
I'm trying to get my Server 2012 VM to not boot so fast. It's annoyingly difficult.

@btm I am running chef client 12.2.1

@bigbam505 I downgraded to 12.2.1 and confirmed the service was created as Delayed Start. If that works for you as a workaround, that's great.
The complete solution is likely to identify a service we can depend on, as I mentioned Delayed Start is a timer which is arbitrary and won't work in some cases. I'll keep looking.

Interesting.  We install the service with chef itself using the chef-client cookbook.  This just calls the chef-service-manager Here.  Looking at the chef-service-manager it looks like it does not use the delayed start of the service unless I am missing something.  Here is the code for the chef-service-manager here

Actually this is why.  The chef-service-manager does not use delayed, however the installer does https://github.com/chef/omnibus-chef/blob/master/resources/chef/msi/source.wxs.erb#L49-L60

@spuder @vvchik The issue due to VLAN might be related or might be independent - it seems that DNS resolution very early on is failing for some reason but that might not be related to the timeouts others are seeing.  For others who still see "A timeout was reached", could you follow steps in https://support.microsoft.com/en-us/kb/824344 to set ServicesPipeTimeout under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control to some long time (say 2 hours or something along those line)?  If it starts working, that would imply that our service startup is being slow for some reason.  The reason for the poor logging involved is because the service is getting killed for before logging has been set up.

Okay, so I have performed a significant amount of investigation into this issue, and I believe we are potentially seeing multiple issues here.  Firstly, a performance issue.  I have found in our test environment (which isn't the fastest environment in the world) that the first time I execute chef-client after a reboot and from the command line, it can literally take over 30 seconds to even return any kind of response (IE "Starting Chef Client, version 12.4.1").  If this is significantly less than 30 seconds, you may never see this issue.  If it is around 30 seconds, you may see the service intermittently starting with the above error randomly.  If it is well over 30 seconds (in my case 45-55 seconds) you will likely always see this error.  I am not sure why chef-client takes so long to initialise the first run, but subsequent runs are usually much quicker in the environment I am using to test.  Thus far in my case, I have needed to extend the ServicesPipeTimeout to 60 seconds to give the service long enough to start.
However, even this may not be enough.  The chef-client environment is dependent on the service "Windows Management Instrumentation" or "Winmgmt".  You can confirm this by stopping the chef-client service (and any other running instances of chef-client), setting the Winmgmt service to disabled, and then attempting to run chef-client from the command line: it will fail.  In my case, this was the primary issue I was seeing here - and the chef-client didn't seem to fail gracefully - it would just hang.  The longer you set the timeout for ServicesPipeTimeout - the longer it would be hung before Windows killed it, and it seemed to delay other services from starting also (I assume Windows only starts one service at a time).
So it seems to me that the service is being installed incorrectly by the chef-client recipe so far as it is not supplying the service the correct dependencies (Winmgmt) when installing the service.  There are multiple ways to modify this as a work around:  either using the "sc.exe" command ("sc.exe config chef-client depend= Winmgmt")(definitely note there is a space after the depend=).  Alternatively, you could create a recipe that adds a REG_MULTI_SZ (Multi String Value) to the registry (at your own risk) under HKLM\SYSTEM\CurrentControlSet\Services\chef-client which you would name "DependOnService" and for the value you would add a single row of text "Winmgmt" without the quotes.  The dependency should take effect from the next reboot of the server.  This will force the Windows to wait until it's dependent service is running before it attempts to start the chef-client service, and should allow you to more accurately identify the amount of time required for the chef-client service to start correctly.  One way to do this may be by temporarily extending the ServicesPipeTimeout value as described above, stopping the chef-client service, setting it to manual start, restarting Windows, and then manually timing how long the service takes to start.  This (with some extra time for fluctuations) would be your new value for ServicesPipeTimeout.
In my opinion, the service start time for chef-client needs a significant reduction to be feasible in an enterprise environment.  I think it also needs to fail more gracefully, and do so in an automated fashion within 25 seconds, and hopefully with some logging.  I am not sure how much luck we will have with that.
@spuder did some nice work there, and seemed to get pretty close.  I think the recovery does not work because the service never successfully started to begin with.  I am of the opinion that if the service started returned success but the failed later, Windows would attempt to restart.  I am not sure what your specific issue is/was, but if I had to guess, maybe something is shutting down your Winmgmt service once network connectivity is available?
I hope someone finds this useful.  Would appreciate any feedback!

@GregAndo - Amazing debugging there!
Do we know how Windows is detecting if the program is working?  Is it looking for output? Or is it something else (e.g. an internal state in the Kernel process table)?
Would it help with the long start up by calling a .cmd or .ps1 script instead and have that run ruby?  That way the script is marked as running quickly and then Ruby can take longer to start?
I'm thinking Ruby isn't loading quickly because it gathers lots of files (both .rb and .dll) to run chef-client.  Windows is slow at opening lots of little files and with a busy disk (due to startup) and a very cold cache it is expected a complicated Ruby program would take a while to start.

@GregAndo Hey, thanks for that!  I am adding Winmgmt to the list of dependencies for chef-windows-service.  That service is supposed to be automatically launched when WMI is invoked (and we invoke WMI to figure out which version of windows we're on - there's not much else we can do before that).  Also, the startup time for the actual chef-client run is different from the startup time for the service itself.  There may very well be some reason our ruby startup is taking a while but I'm having a hard time reproducing it.
As for chef-client itself taking a long time to start up - I agree that that's too long but that might be a separate issue (ohai takes a while to startup, plugins need to be loaded...  etc.).

@docwhat For a service, it has strict rules.  A service needs to broadcast that it's in the running state within 30 seconds of startup (that time is overriden by ServicesPipeTimeout).  We run https://github.com/chef/chef/blob/master/lib/chef/application/windows_service.rb#L63 (and initialization) - so not a lot except for initializing logging.  My primary suspicion here is that ruby is taking a while to launch and collect the gems involved but I can't seem to reproduce it with on 12.4.1 using a fresh chef-client installation.  That is unless your client.rbs all contain extremely weird and end-case triggering options - like putting your config file online (we open up a web client to download the config), or your config file is on a network drive or a hyper-v shared drive (we block to open the file) or something else like that.

Can you send the "I'm up" message before doing a full require "chef"?  On my blazing fast SSD MacBook that require takes about 3 seconds (not measured).
Though that doesn't really explain 30 seconds and would probably hide the problem.
Is there a way we can profile it? I'd be happy to create a VM here to run a profiling version of Chef or Ruby.
I'm not a windows person so I'm not familiar with the toolset.

Can someone validate if chef/omnibus-chef#440 fixes this or not?

Just run in a scheduled task.

I can @lamont-granquist. Is chef-client 12.4.3 a good build for that?

@alexpop You need a 12.5 nightly I believe.

@ksubrama @alexpop fwiw, I see the referenced commited tagged in 12.4.3

The fix is "sc.exe config chef-client depend= Winmgmt"
If you want to fix them all,
$list = @"
server1
server2
server3
"@ -split "`n" | % { $_.trim() }
$serviceAccount = Get-Credential
$serverlist = foreach ($server in $list){ Invoke-Command -ComputerName $server -credential $serviceAccount -ScriptBlock { sc.exe config chef-client depend= Winmgmt; start-service chef-client} }
$serverlist

I have a Windows 2012R2 VirtualBox VM where I'm seeing the Chef Client Service(version 12.4.1) not starting after reboot using "Automatic" Startup Type. Changing that to "Automatic (Delayed Start)" makes the service start a few minutes after boot.
I've now installed a chef-client 12.5 nightly build which uses "Automatic (Delayed Start)" by default. I switched that to "Automatic" and the Chef Client Service is starting fine after reboot.
Is it safe to default back to "Automatic" in order to avoid the delayed start?

It looks like the fix appears in the commit tagged [12.4.2] (https://github.com/chef/omnibus-chef/blob/chef-12.4.2/resources/chef/msi/source.wxs.erb#L69) but the released chef-client versions 12.4.2 and 12.4.3 don't seem set the dependency.  I'm sure I'm missing something obvious, but how can I tell what version it is (will be?) fixed in?

I'm still seeing the error on Windows 2012 R1 VMs built on Azure.
Running chef-client version 12.5.1.
It appears as though startup type is already set to "Automatic (Delayed Start)", and Winmgmt is a dependency.
PS C:\Users\***> get-item -path "HKLM:\SYSTEM\CurrentControlSet\Services\chef-client"

    Hive: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

Name                           Property
----                           --------
chef-client                    Type             : 16
                               Start            : 2
                               ErrorControl     : 0
                               ImagePath        : c:\opscode\chef\embedded\bin\ruby.exe C:\opscode\chef\bin\chef-windows-service
                               DisplayName      : Chef Client Service
                               DependOnService  : {Winmgmt}
                               ObjectName       : LocalSystem
                               Description      : Runs Chef Client on regular, configurable intervals.
                               DelayedAutostart : 1

Setting ServicesPipeTimeout to a large value helped.

also seeing this in AWS for Win2012 R1 and R2 images.

I can repro this on Windows Server 2012 with Chef Client version 12.5.1, but it seems to work fine on Windows Server 2012 Data Center.

I'm going to close this out at this point since we recommend users not setup chef as a service. The preferred route is a task since that avoids the long running ruby task and ruby on windows memory leaks.


Player Reset Option

I don't see an option to reset the player at all. Looping doesn't seem like a great option when using in a chat app.

Hey @rlee1990, you can use FinishMode.pause and FinishMode.stop. If this option doesn't satisfy your use case, can you please share your use case or any suggestions?

@ujas-m-simformsolutions What I am trying to do is when the audio is done playing have the player reset the audio back to the start and have it ready to be played again. Putting it on stop doesn't allow us to play it again. Looping will still keep playing.

@rlee1990 You can use FinishMode.pause for this use case

@ujas-m-simformsolutions No I can not that will just pause the file at the end and the person won't be able to hear it again from the start without closing the chat

@rlee1990 With FinishMode.pause player will be paused at the end of the file but if you call startPlayer again it will start playing again from the start of the file. And if you are still facing this issue then please share your implementation so that we can check where is the issue.

Closing this since no more feature info was provided and the current implementation works for the use case.


[BUGFIX] Remove compilation warning

Description
It gets rid of compiltation warning:
'float' changes value from<PHONE_NUMBER> to<PHONE_NUMBER>
for -Wimplicit-const-int-float-conversion flag
It fixes https://github.com/apache/incubator-mxnet/issues/20833
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented

@mxnet-bot run ci [unix-gpu]


polybar: 3.3.1 -> 3.4.0

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build polybar

LGTM!
Built and tested locally on NixOS.
Hi @marsam, could you merge this PR? Thank you very much!

Can we add a homepage attribute to meta while we're at it?

https://polybar.github.io/


Add data in ML Model Builder from .csv file (exported from SQL Server)

Model Builder Version:

Visual Studio Version
Microsoft Visual Studio Professional 2019
Version 16.4.5
VisualStudio.16.Release/16.4.5+29806.167
Microsoft .NET Framework
Version 4.8.03761
Installed Version: Professional

Describe the bug
Add data in ML Model Builder from .csv file (exported from SQL Server)
Data from SQL Server I've exported using  this script in PowerShell
$dbname = "YOUR_DB_NAME_WITHOUT_STARS"
$AttachmentPath = "c:\export.csv"
$QueryFmt= @"
YOUR_QUERY_WITHOUT_STARS
"@
Invoke-Sqlcmd -ServerInstance MySQLserver123 -Query $QueryFmt -querytimeout 600 | Export-CSV $AttachmentPath
Data:

Additional context

Sorry, Issue closed.


Frontend web development react angular vue : difference in angular forms

Description 📜
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes #6847

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Doc#umentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[ ] DS#A
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[x] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] JavaScript_#Domain
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

Well done @HastiSutaria realy loved the explanation ..and the my point section really awesome ..Good work!!

Well done @HastiSutaria realy loved the explanation ..and the my point section really awesome ..Good work!!

Thank you @mukeshmjn !


Cmake refactor

Add toolchain files and update the cmake files, add some cmake utils.

Merged with small fixes


Upgrade Postgres requirement to 14.7 or newer

The DPIA backend DBMS specified in the Docker config is currently Postgres version 10.21 but it should be something modern like 15.2 or 14.7 instead.
(Likewise for every other bcgov project still specifying a Postgres version older than 14.7 or so.)
One key reason for this is that Postgres 10 is no longer supported by its creators and so depending on it presents a security risk.
Another key reason is that Postgres 10 is 5 major versions behind the latest production version and so we are missing out on using 5 years' worth of very useful new features and improvements.
(It is also notable that Postgres 10 was already 4 major versions out of date, and half a year from end of support, when the earliest surviving commit of 2022 Jun 17 was made to the DPIA repository.)
The DPIA Docker config specifies that the dpia-db image is postgres:10.21-alpine3.16.
See the Docker site for the newer options:
https://hub.docker.com/_/postgres
The most minimal update that is still supported by upstream is 11.19-alpine3.17.
The newest update is 15.2-alpine3.17 to get a major version that is a few months old.
If you want to be a bit more conservative, the second to newest major version is 14.7-alpine3.17 and that is the oldest I would recommend.
Postgres is very good at keeping high quality and reliability, so one shouldn't really see any need to be more than a year or so out of date to feel that they are using something stable and bug free.
Since Postgres is very good with backwards-compatibility for minor versions of the same major, specifying an alternate alias like 15-alpine or 14-alpine means that any given time you get the latest minor version for the major without having to specify it explicitly, meaning less maintenance.
Note that Postgres major version updates mean a different on disk format for data directories, so this change is only a drop-in replacement in scenarios where upgrading users would create a database from scratch, like new users, or a dump/restore or replication migration will be needed.

Hey Darren,
I appreciate the feedback. Currently this project is going to be transitioning to a CrunchyDB instance in Openshift in the next month, as I'm currently working on some higher prioritized issues in our DevOps backlog.

Thank you Adam.  Given that you have an imminent alternate solution, I will close this issue.


marpa_r_furthest_earleme() error checks

marpa_r_latest_earleme() fails if the recognizer is not trace-safe, including that the recognizer has been started.  marpa_r_furthest_earleme() never fails.  Shouldn't marpa_r_furthest_earleme() fail consistently with marpa_r_latest_earleme()?

There is a similar issue with marpa_r_current_earleme()

Fixed in the course of working on issue #79.  Absent feedback to the contrary I will close this issue in a couple of days.

Closed per https://github.com/jeffreykegler/libmarpa/issues/107#issuecomment-1134010572.


y-axis range in the across-bands plot is not correct

values appear to be mapped to the 0-1 range in the plot as if they were reflectance, even for the captured image in radiance (which goes eg 200-1000)

Interesting. What data are you using? We are building this for sediment cores, where we measure reflectance/absrobace. Then we normalize the data in the first step by scaling the reflectance data between 0-1, where 0 is black, and 1 is white. For this, we scan white reference certified material (BaSO4 plate) and black is just a photo take with closed camera shutter.
So for our white corrected data the y-scale is correct. But if you explain more what are your data and what do you want to achieve, we can see if we can modify this to make it suitable for wider range of hyperspectral data.
You can also contact me directly via email (petra.zahajska@unibe.ch).
Thanks,
Petra


add Node Version Manager support

.nvmrc file is for Node Version Manager
there is a Feature Request to use engines.node from package.json but for now only a separate file is supported

To be honest, I am not a big fan of using non-standard dev files.
You can use .nvmrc by adding it to .git/info/exclude.
What are your reasons to give this file to everyone?

Many people uses NVM to run required Node version for projects. Some requires 10, some requires 13.

Hm. It will have more sense if we will use the same nvm in GitHub Actions (I do not like to add more configs, but I like to reduce code duplication).
You can replace `@actions/setup-node with https://github.com/dcodeIO/setup-node-nvm in GitHub Action configs.

Closing because of lack of answer


Added styles to the about us page #1168

Fixes Issue
Closes  #1168

Changes proposed

corrected footer of the about Page
Turned off text selection
added copyrights selection
added payments image
added colour to button
added hovering effect to button
Changed the content for header
Added style for the header topic
Changed the description content
Added style to description
Changed the about image

Screenshots

Note to reviewers

@codervivek5 I am contributing under GSSoC24 .. Please assign me this PR under GSSoC and label this PR

@codervivek5 As you said, I have updated the image

is this page responsive ?

can you plz customize this page like this

@codervivek5
Yes the page is responsive

Styling the page like that image you have given would make that page alone look different from other pages

@codervivek5  Please merge this PR and label it under GSSoC

@codervivek5 Please add level label to this PR as it would be considered by GSSoC


chore(prow/config): split the cron job to serval containers

for debug which repo's configuration make the job failed.
Signed-off-by: wuhuizuo<EMAIL_ADDRESS>
What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
What's Changed:
How it Works:

/approve

/approve


Performance improvements

Currently the exporter has two usability issues that should be addressed:

The exporter performs scrapes one-by-one, resulting in an accumulation of scrape durations. Results are not returned until all scrapes are finished, which may cause timeouts on behalf of the prometheus collector. This can be addressed by making each scrape asynchronous. For examples, see the Raritan PDU Exporter
The URLs in the configuration must point precisely at http://printer.url/web/guest/en/websys/webArch/getStatus.cgi. It is better to require users to setup with only http://printer.url and then append the remaining part in the code. If this ever changes, all of the scraping will start failing anyway.

Both of these issues have been resolved in v1.4.0.


Add SMISMEMBER command

Applying this PR will add the SMISMEMBER command, which was introduced in Redis 6.2. I didn't add the tests yet, because I think that requires some work on the CI build first.

Thanks for the PR. Unfortunately at the moment it looks like there's no active maintainer of this repo. Are you interested in this role @Philippus ?

Yes, I'm interested.

Great! I've added you as maintainer for now.

@Philippus could you please add a simple test for new command?

I added a test.

Can you have another look @kardapoltsev ?