Make docs page more presentable

[ ] Support going fullscreen
[ ] Research: make it fun to use

Some amazing docs sites:

https://docs.expo.dev
https://lens.xyz/docs
https://figure.ai/ - Love the header design on mobile

can i work on this??

@hari can i work on this??

@SEEDART007 yes but this is out of the scope of hacktoberfest as it is a big one.

@SEEDART007 yes but this is out of the scope of hacktoberfest as it is a big one.

I just want to contribute I'm tired of these events..

Assigned to you @SEEDART007
Please share what changes you'd like to make before writing the code. We can discuss it first.

@hari  besides building up the docs i want to say that i am using you website heavily on my recent projects......everything is pretty fine also the docs....but i find some difficulties , first one is that your website lacks input and textarea ui components as well as forms....can we together add those to your website?.....I am heavily dependent on your website for ui components but for these tiny little things i have to surf more ui website which is pretty bad.

@SEEDART007 We can come up with plan and create a new form section for this.

@SEEDART007 We can devise a plan and create a new form section for this.

sure


Logging function

Added a function that is called whenever an error occurs in a mutation or query. Whether it is a connection error or GraphQL error. It can be added like so:
@rootDataConnect({
  logging: ({data, errors}, dispatch) =>  console.log(`${errors}`)
})

data may not exist, it will be there if one of the queries returned some data but had GraphQL errors.
errors should always an array of objects which should always have a message key with a string.

Fix the unit tests and it's ready to go ;)

Changed so that the logging function isn't kept in redux state (for obvious performance reasons). It must now be passed in the logging key of the rootDataConnect config for queries and in the mutation's options ({ fragments: {...}, logging: console.log}) for mutations.

Coverage decreased (-0.1%) to 71.774% when pulling f49bc19e55a28be251cb6e3a0325873a9ac8ac6f on s-coimbra21:loggingAPI into ea045ff4c69b998769a7b1e9ac9b4b5c9b46c6dd on relax:master.

Hey! Could you fix the conflicts so we can merge this?


Stake Info and Purchase Tickets implementation

This adds stake info and purchase tickets pages to the web interface that fixes #158 . It also abstracts common javascript functions to allow for code readability.

Despite having 1000 DCR, I am getting error insufficient balance.

There is an error on the send page
Error: Missing target element "send.submitButton"
Can you check it please

@ademuanthony I'm not able to reproduce the error. Do you have the latest code?

@Sirmorrison done


Codespace devlynnx miniature umbrella jx7vj765wx4cp966

Description:
Describe your changes.
Related issue:
Add link to the related issue.
Check list:

[x] Mark if documentation changes are required.
[ ] Mark if tests were added or updated to cover the changes.

Updated


zulip_bots: Fix get_storage request arguments in StateHandler.

I tried running connect_four game and it failed with these errors:
Traceback (most recent call last):
  File "/home/klitzy/python-zulip-api/zulip-api-py3-venv/bin/zulip-run-bot", line 11, in <module>
    load_entry_point('zulip-bots', 'console_scripts', 'zulip-run-bot')()
  File "/home/klitzy/python-zulip-api/zulip_bots/zulip_bots/run.py", line 123, in main
    bot_name=bot_name
  File "/home/klitzy/python-zulip-api/zulip_bots/zulip_bots/lib.py", line 300, in run_message_handler_for_bot
    message_handler = prepare_message_handler(bot_name, restricted_client, lib_module)
  File "/home/klitzy/python-zulip-api/zulip_bots/zulip_bots/lib.py", line 263, in prepare_message_handler
    message_handler.initialize(bot_handler=bot_handler)
  File "/home/klitzy/python-zulip-api/zulip_bots/zulip_bots/game_handler.py", line 180, in initialize
    self.get_user_cache()
  File "/home/klitzy/python-zulip-api/zulip_bots/zulip_bots/game_handler.py", line 642, in get_user_cache
    user_cache_str = self.bot_handler.storage.get('users')
  File "/home/klitzy/python-zulip-api/zulip_bots/zulip_bots/lib.py", line 72, in get
    response = self._client.get_storage(keys=(key,))
TypeError: get_storage() got an unexpected keyword argument 'keys'

It seems like the first commit introduces keys when the message only says you're renaming a test.  Can you rebase to make that clean (and run tests locally after the first commit to make sure it's atomic).
I'm also curious what the history is here.  Were you testing this against dev/master or czo?

I was testing in dev env, actually, I was debugging the issue reported by Jessica in #issues so I was trying to reproduce it with other bots. I found bot server exited with the error (fixed in this PR) with pip package first, then reproduced it PZA master branch.

It seems like the first commit introduces keys when the message only says you're renaming a test. Can you rebase to make that clean (and run tests locally after the first commit to making sure it's atomic).

It's because of this line https://github.com/zulip/python-zulip-api/pull/446/commits/aad9ced0849e3aa53ac614e1ef8d70b6da08c20d#diff-5db543d6b799cdac9921eaa52303e294R73

Merged, thanks @shubhamdhama!


Add smart quote example, as discussed in #967

This small PR adds a sentence of documentation out of the resolution of #967 (Render smart quotes in math as regular quotes).

@edemaine I was thinking we'd have actually "gotchas" section, maybe called # Common Issues where we could list this as well as things like there not being enough space between rows in {aligned} when using fractions or the font being bigger than MathJax.  That way it would have better visibility.

@kevinbarabash Sounds good! Feel free to start a new PR to replace this one, or appropriate this PR.

@edemaine will do sometime this weekend.

Closing in favor of #1034.


[ZEPPELIN-4355] Fix broken tests in master branch

What is this PR for?
Recently, master branch tests are broken with multiple different reasons.
This PR address some of them including

https://issues.apache.org/jira/browse/ZEPPELIN-4355
r-base package installation fail on travis (maybe travis or r package repo changed somehow)
PersonalizeActionIT fails (not sure what made this test fail. but anyway made test verify correct behavior)

After this PR, all tests except for LivyInterpreterIT (last 2 test profile in travis) will pass. ZEPPELIN-4357 is NOT addressed in this PR.
What type of PR is it?
Bug Fix
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-4355
How should this be tested?

All CI test should pass except for last 2

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

@zjffdu Do you have any good idea about https://issues.apache.org/jira/browse/ZEPPELIN-4357 ?

Maybe it makes sense to split fixes by JIRA?

Created new PR https://github.com/apache/zeppelin/pull/3469. Closing this one.


Feat: Support OIDC discovery

Describe the Feature
Support  OIDC discovery so users must not know every provider specific config detail.
Platform(s) Support Requested

Android
iOS
Web

Test FB with https://developers.facebook.com/docs/facebook-login/limited-login


Move priviledged files out of repo

Related to #24. Move out API keys/files into a standard direction. Files should be stored in resources.

For now, keystore uses API to get, however when #34 allows for templating, then keys will be directly injected into the HTML

Merged #35 into master


Search with only one result shows Uncaught Exception 200

Has been discussed before.
I guess the easiest would be to have some kind of IRC if IM is necessary.

Hey, had same problem. Download the whole php stuff again https://github.com/BanManagement/BanManager-WebUI/tree/1.5.4 and try or it works.

I keep my version cloned so I don't think that a manual reinstall would help with this.

Yep getting the same issue.

Can you guys provide an link so I can take a look by myself?

Try http://bans.mineagepvp.com/

@Bestle what do you search for exactly? When I try "display all" I don't see any error message:
http://imgur.com/6MvlOqo
Sent from my iPhone

On 05 Nov 2015, at 17:51, Bestle<EMAIL_ADDRESS>wrote:
Try http://bans.mineagepvp.com/
—
Reply to this email directly or view it on GitHub.

@Bestle Never mind, found it:
http://bans.mineagepvp.com/index.php?player=LuckyCritz&server=0&action=searchplayer
Sent from my iPhone

On 05 Nov 2015, at 17:51, Bestle<EMAIL_ADDRESS>wrote:
Try http://bans.mineagepvp.com/
—
Reply to this email directly or view it on GitHub.

Im also getting this issue. I type in % as the search and this show up
http://p-x.ca/banlog/index.php?player=%25&server=0&action=searchplayer

Caused by a location redirect in the search response
$ curl -I "http://bans.mineagepvp.com/index.php?action=searchplayer&player=LuckyCritz&server=0&excluderecords=undefined&ajax=true&size=10&page=0&sortby=column\[5\]=1&filter=filter"

HTTP/1.1 302 Found
Date: Tue, 01 Dec 2015 16:53:58 GMT
Content-Type: text/html
Connection: keep-alive
Set-Cookie: __cfduid=d5c2fddc53d8ff62ca161d0e7563db3d71448988838; expires=Wed, 30-Nov-16 16:53:58 GMT; path=/; domain=.mineagepvp.com; HttpOnly
X-Powered-By: PHP/5.5.9-1ubuntu4.14
Set-Cookie: BanManagement=ahieraodnql1hlotme5komttv2; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: BanManagement=gdq2sd1ai1glk3571et9kso1i7; path=/
X-FRAME-OPTIONS: SAMEORIGIN
Location: index.php?action=viewplayer&player=LuckyCritz&server=0
Server: cloudflare-nginx
CF-RAY: 24e04fb112883446-LHR

So is this a web server configuration issue or something we need to wait for you to resolve?

@Bestle should be resolved in the master branch, however, unfortunately I don't have a database copy to test with to confirm

Fixed confirmed by @Kakifrucht


Update fleetdm_dl_url for Ansible playbook

Update fleetdm_dl_url in Ansible playbook. Fleet no longer releases ZIP files, only TARs.
Action items

Update fleetdm_dl_url to TAR download link
Update playbook to use TAR and NOT zips
Update playbook to latest version of Fleet

https://github.com/CptOfEvilMinions/FleetDM-Automation/pull/5


Fix/#6416 Input Validator (also for #6417, #6418, #6419)

This PR is related to #170.

@spetros-do @yonatan-dp I pushed up the minimal amount of changes to make this PR functionally similar to https://github.com/US-EPA-CAMD/easey-common/pull/178/files. There are some differences in implementation details that I left alone because they differ in flavor only.


[HHVM] Failed to initialize central HHBC repository after upgrade 3.2.2

After running ee update I notice HHVM stopped. I ran sudo service hhvm start, HHVM starts but then running sudo service hhvm status, "HHVM is not running"
I checked /var/log/hhvm/error.log and got this
[Fri Jun 19 18:14:22 2015] [hphp] [28764:7f731e7ff700:1:000003] [7f7330244d40:7f7330244cc9:7f73302480d8:220f09d:11d0c03:11d137e:11d160c:11d16f9:e8e568:2c8a2d5:2c89881:2cafe6a:fc00b2:dcb142:11091fa:110b2f2:111f05a:111f5ce:111bff6:21f4b67:f8c287:7f7330dfb182:7f733030847d] Stack trace in /tmp/stacktrace.28764.log
[Fri Jun 19 18:16:03 2015] [hphp] [28802:7ff46486b7c0:0:000001] [] Failed to initialize central HHBC repository:\n  Failed to initialize schema in /var/run/hhvm/hhvm.hhbc: \n  Failed to open /var/www/.hhvm.hhbc: 14 - unable to open database file\n
[Fri Jun 19 18:17:57 2015] [hphp] [28846:7f23dcbff700:1:000001] [] Failed to initialize central HHBC repository:\n  Failed to initialize schema in /var/run/hhvm/hhvm.hhbc: \n  Failed to open /var/www/.hhvm.hhbc: 14 - unable to open database file\n
[Fri Jun 19 18:17:57 2015] [hphp] [28846:7f23dcbff700:1:000002] [7f23ee34fd40:7f23ee34fcc9:7f23ee3530d8:220f09d:11d0c03:11d137e:11d160c:11d16f9:e8e568:2c8a2d5:2c89881:2cafe6a:fc00b2:dcb142:11091fa:110b2f2:111f05a:111f5ce:111bff6:21f4b67:f8c287:7f23eef06182:7f23ee41347d] Core dumped: Aborted
[Fri Jun 19 18:17:57 2015] [hphp] [28846:7f23dcbff700:1:000003] [7f23ee34fd40:7f23ee34fcc9:7f23ee3530d8:220f09d:11d0c03:11d137e:11d160c:11d16f9:e8e568:2c8a2d5:2c89881:2cafe6a:fc00b2:dcb142:11091fa:110b2f2:111f05a:111f5ce:111bff6:21f4b67:f8c287:7f23eef06182:7f23ee41347d] Stack trace in /tmp/stacktrace.28846.log
[Fri Jun 19 18:20:32 2015] [hphp] [28908:7f7170fff700:1:000001] [] Failed to initialize central HHBC repository:\n  Failed to initialize schema in /var/run/hhvm/hhvm.hhbc: \n  Failed to open /var/www/.hhvm.hhbc: 14 - unable to open database file\n
[Fri Jun 19 18:20:32 2015] [hphp] [28908:7f7170fff700:1:000002] [7f7182aaed40:7f7182aaecc9:7f7182ab20d8:220f09d:11d0c03:11d137e:11d160c:11d16f9:e8e568:2c8a2d5:2c89881:2cafe6a:fc00b2:dcb142:11091fa:110b2f2:111f05a:111f5ce:111bff6:21f4b67:f8c287:7f7183665182:7f7182b7247d] Core dumped: Aborted
[Fri Jun 19 18:20:32 2015] [hphp] [28908:7f7170fff700:1:000003] [7f7182aaed40:7f7182aaecc9:7f7182ab20d8:220f09d:11d0c03:11d137e:11d160c:11d16f9:e8e568:2c8a2d5:2c89881:2cafe6a:fc00b2:dcb142:11091fa:110b2f2:111f05a:111f5ce:111bff6:21f4b67:f8c287:7f7183665182:7f7182b7247d] Stack trace in /tmp/stacktrace.28908.log
[Fri Jun 19 18:24:24 2015] [hphp] [29113:7fa5d066d7c0:0:000001] [] Failed to initialize central HHBC repository:\n  Failed to initialize schema in /var/run/hhvm/hhvm.hhbc: \n  Failed to open /var/www/.hhvm.hhbc: 14 - unable to open database file\n
[Fri Jun 19 18:24:47 2015] [hphp] [29143:7ff23c9807c0:0:000001] [] Failed to initialize central HHBC repository:\n  Failed to initialize schema in /var/run/hhvm/hhvm.hhbc: \n  Failed to open /var/www/.hhvm.hhbc: 14 - unable to open database file\n

Hello @w33zy,
In EasyEngine 3.2.2 we are only adding hhvm.server.ip in HHVM config, no other changes are made in HHVM config.
Can You give me your output of following commands?
lsb_release -a
cat /etc/hhvm/server.ini
cat /etc/hhvm/php.ini

@w33zy Seems like you are hitting maximum number of open file descriptors.
cc: @harshadyeola @gau1991
Refer: https://github.com/facebook/hhvm/issues/4319#issuecomment-64285943

@gau1991
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.2 LTS
Release:        14.04
Codename:       trusty

; php options

pid = /var/run/hhvm/pid

; hhvm specific

hhvm.server.port = 8000
hhvm.server.type = fastcgi
hhvm.server.default_document = index.php
hhvm.log.use_log_file = true
hhvm.log.file = /var/log/hhvm/error.log
hhvm.repo.central.path = /var/run/hhvm/hhvm.hhbc
hhvm.server.ip = <IP_ADDRESS>

; php options
session.save_handler = files
session.save_path = /var/lib/php5
session.gc_maxlifetime = 1440

; hhvm specific
hhvm.log.level = Warning
hhvm.log.always_log_unhandled_exceptions = true
hhvm.log.runtime_error_reporting_level = 8191
hhvm.mysql.typed_results = false
hhvm.log.header = true
hhvm.log.natives_stack_trace = true

@MiteshShah
root@rose:~# cat /proc/sys/fs/file-max
2097152

I'll close this issue. The headache that is HHVM is not worth it. The PHP-FPM failover works and their is no perceived difference on the site.


Channel Group Subscription Support

param to allow adding groups and stuff

Opened an issue in each sub repo:
https://github.com/pubnub/eon-chart/issues/5
https://github.com/pubnub/eon-map/issues/6

:+1:


Parser doesn't seem to support left recursion

I was trying to run some basic grammar that had some left recursion and realized that the parser doesn't seem to support that. Is there a reason for that/would it be possible for the parser to support that?

Hello @clache547 , you are right. Our parser is a recursive descent parser which doesn't support left-recursion by construction. There are two solutions:

transform the grammar to avoid left-recursion, this is always possible. See this related issue
update the parser to a version that supports left-recursion such as Earley Parser. But we don't foresee such a major update in the short future.


'_' makes matplotlib to render the following character as subscript

Environment

Qiskit Terra version:  0.19.1
Python version:  3.9.9
Operating system: Linux(Fedora 34)

What is happening?
The '_' in the name of QuantumRegister forces the following character to be rendered as subscript
In this example see the 'r' is rendered as a subscript.

The problem vanishes when the number of qubits is increased to 2 or more.

How can we reproduce the issue?
from qiskit import QuantumRegister, QuantumCircuit
num_of_qubits=1
q_reg=QuantumRegister(num_of_qubits, 'q_reg')
qc=QuantumCircuit(q_reg)
qc.draw(output='mpl')
What should happen?
This should be the output:

Any suggestions?
No response

Thanks for spotting this. Actually the second case is incorrect as well. It should be q_reg0.
@javabster Can you assign this to me? Thanks.

Thanks for spotting this. Actually the second case is incorrect as well. It should be q_reg0.
@javabster Can you assign this to me? Thanks.

@enavarro51 , actually I was working on this, now, since you have asked for the permission. You go ahead with this and I tell you my recent progress in this:
Go to qiskit/visualization/matplotlib.py#L456
I changed this:
words = [word.replace("", r"_") if word.count("") > 1 else word for word in words]
to this:
words = [word.replace("", r"_") if word.count("") >= 1 else word for word in words]
and got the image I mentioned in the what should happen section above.
and you put "^" in place of "_" and see new hosts of problems
Now, you take it from here :)

@enavarro51 , actually I was working on this, now, since you have asked for the permission. You go ahead with this and I tell you my recent progress in this:
Go to qiskit/visualization/matplotlib.py#L456
I changed this:
words = [word.replace("", r"_") if word.count("") > 1 else word for word in words]
to this:
words = [word.replace("", r"_") if word.count("") >= 1 else word for word in words]
and got the image I mentioned in the what should happen section above.
and you put "^" in place of "_" and see new hosts of problems
Now, you take it from here :)

Thanks, @MozammilQ. I believe this is a bit of a deeper problem with register naming. We'll probably need to get some input from the IBM side for this. OpenQASM 3.0 says this about names.
"Names of gates, variables, and constants — In OpenQASM 2, the names of registers
and gates must begin with a lower-case alphabetic ASCII character. This constraint is
relaxed in OpenQASM 3: identifiers may now begin with other characters, such as capital
letters, underscores, and a range of unicode characters. For example, angular values used
as gate arguments may now be represented by greek letters. (The identifier π is reserved in
OpenQASM 3 to represent the same constant as pi.) Note that OpenQASM 3 has a slightly
different set of keywords from OpenQASM 2. This may cause errors in OpenQASM circuits
which happen to use a keyword from version 3 as an identifier name: such identifiers would
have to be renamed in order for the source to be valid OpenQASM 3."
In OpenQASM 2.0, names were restricted to alphanumeric and underscores. This means '^' should not have been allowed in register names. In #3827 an attempt was made to fix more than one underscore in a name displaying with matplotlib. But that solution was not complete and no tests were added, so part of that problem is showing up now.
The final problem is that the text_width calculation in matplotlib strips out the underscores, which for multiple underscores in a name, results in an incorrect text_width which can lead to letters being cut off to the left.
So a solution could be to put a validity check for what are proper 2.0 and 3.0 names., do the replacement of '_' with '\_', and finally fix the text_width calcs to properly handle '_'.

Thanks, @MozammilQ. I believe this is a bit of a deeper problem with register naming. We'll probably need to get some input from the IBM side for this. OpenQASM 3.0 says this about names.
"Names of gates, variables, and constants — In OpenQASM 2, the names of registers
and gates must begin with a lower-case alphabetic ASCII character. This constraint is
relaxed in OpenQASM 3: identifiers may now begin with other characters, such as capital
letters, underscores, and a range of unicode characters. For example, angular values used
as gate arguments may now be represented by greek letters. (The identifier π is reserved in
OpenQASM 3 to represent the same constant as pi.) Note that OpenQASM 3 has a slightly
different set of keywords from OpenQASM 2. This may cause errors in OpenQASM circuits
which happen to use a keyword from version 3 as an identifier name: such identifiers would
have to be renamed in order for the source to be valid OpenQASM 3."
In OpenQASM 2.0, names were restricted to alphanumeric and underscores. This means '^' should not have been allowed in register names. In #3827 an attempt was made to fix more than one underscore in a name displaying with matplotlib. But that solution was not complete and no tests were added, so part of that problem is showing up now.
The final problem is that the text_width calculation in matplotlib strips out the underscores, which for multiple underscores in a name, results in an incorrect text_width which can lead to letters being cut off to the left.
So a solution could be to put a validity check for what are proper 2.0 and 3.0 names., do the replacement of '_' with '\_', and finally fix the text_width calcs to properly handle '_'.

Oh Nice! I didn't know that the problem could be this deep, @enavarro51 thanks for sharing the information, you do have a deeper understanding of the problem :)

Oh Nice! I didn't know that the problem could be this deep, @enavarro51 thanks for sharing the information, you do have a deeper understanding of the problem :)


chore(script): add bash script for macos

What this PR does 📖
Adds a script with all the stuff that we need on macOS

Also updated the read me with the above script.

chances are you will probably have to chmod +x the script to run it. While this is a nice thought to include this, i think it is fine as-is.

chances are you will probably have to chmod +x the script to run it. While this is a nice thought to include this, i think it is fine as-is.

gonna check

chances are you will probably have to chmod +x the script to run it. While this is a nice thought to include this, i think it is fine as-is.

so we tested i asked phil to run the command and worked fine he didnt had to make the chmod + x


Specify correct imports for certificate creation example

Greetings,
Which are the correct imports to make the example on how to build a certificate from a pem file given here work?
I tried with
use std::fs::File;
use std::io::Read;

And with
use tokio::fs::File;

but in both cases, Clippy complains about using the ? operator on a function not implementing the needed trait.

The first one should work. It's what the example uses, and docs test it.

Somehow that doesn't work for me. Instead, the following seems to work:
use std::fs::read;

let buf= read(root_ca_certificate_path).expect("Error reading root CA certificate");
let cert = reqwest::Certificate::from_pem(&buf).expect("Error parsing root CA certificate");

Glad you got it working. (Were you writing that inside a function that doesn't have a Result return type? The ? operator requires that.)


No content in "Widgets" Tab on Firefox and mobile scrolling in Internet Explorer

Problem

Opening the Widgets Tab on Pages with Firefox only shows me an empty screen... With other browsers it works perfectly.
Trying to mark some text in any form inputs on admin interface with Internet Explorer scrolls through the Tabs (for example on Widgets or Sites, pulling to the left or right with dragged mouse button on any form inputs). For me it looks like some mobile functions are activated for desktop browser.

Technical Details

Pagekit version: 0.11.2
Webserver: Apache/2.4.7 (Ubuntu)
Database: MySQL
PHP Version: 5.5.9-1ubuntu4.14

Troubleshooting

[x] I have enabled debug mode: https://pagekit.com/docs/troubleshooting/debug-mode
[x] I have verified the server requirements: https://pagekit.com/docs/getting-started/requirements
[x] I have tried disabling all installed extensions
[x] I have checked the browser developer console for JavaScript errors

I can confirm that I'm am also not seeing the widgets page in Firefox.  It works okay in Safari, however.

I got the same problem. Firefox console reports an error in widget's index.js:
TypeError: t is undefined index.js:1:3643

It seems like this has to do with the latest Vue.js version 1.0.20. For some reason a function argument is missing only in Firefox.
To downgrade Vue open bower.json, change "vue": "~1.0.14", to "vue": "1.0.14",, and run bower install.

This issue is fixed in the vue dev branch (https://github.com/vuejs/vue/issues/2592#issuecomment-204819916).


修复开启 WM_Pointer 后，非主屏获取的 GetTouchPoint/GetStylusPoint 坐标错误

Fixes Issue
Main PR
Description

Customer Impact

Regression

Testing

Risk

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

此更改带入到 https://www.nuget.org/packages/dotnetCampus.WPF.Resource/6.0.4-alpha07-test02 里面


Feature Importance not supported for certain Scikit-Learn model types

Weights and Biases version: 0.8.32
Python version: 3.7.2
Operating System:  MacOS

Description
I tried to use plot_feature_importances() as described in https://docs.wandb.com/library/frameworks/scikit#feature-importances and found that it wouldn't work, the console logs show this message:
feature_importances_ attribute not in classifier. Cannot plot feature importances.

It's possible you are specifically looking for the attribute feature_importances_ on the model but models like ElasticNet and ElasticNetCV have an attribute called _coeff, see docs https://scikit-learn.org/stable/modules/generated/sklearn.linear_model.ElasticNet.html?highlight=elasticnetcv#sklearn.linear_model.ElasticNet and https://scikit-learn.org/stable/modules/generated/sklearn.linear_model.ElasticNetCV.html?highlight=elasticnetcv#sklearn.linear_model.ElasticNetCV which essentially have the same information per variable/feature.
Would it be possible to enable the functionality for these class of models?
What I Did
Checked the scikit-learn docs and W&B docs about this feature

We have this feature now, closing issue, thanks @vanpelt


[breaking change] Allow private field promotion for abstract getters if there are no conflicting declarations.

Change intent
Change the rules for which property gets are eligible for type promotion so that a reference to an abstract getter is considered promotable, provided that there are no other declarations with the same name in the library that would prevent promotability.
For example, this code currently doesn't type promote; with the change it would:
class A {
  int? get _field;
}
class B extends A {
  final int? _field;
  B(this._field);
}
test(A a) {
  if (a._field != null) {
    print(a._field * 2); // Currently an error; will be allowed
  }
}

Justification
The current rules for private field promotion require the implementation to figure out which declaration each property access refers to. If a property access refers to a private final field declaration, and there are no declarations with the same name in the library that aren't safe to promote, then the property access is considered promotable. But if it refers to an abstract getter declaration (as in the above example), then it's considered not promotable. There are two problems with this.
First, and probably most interesting to end users, it unnecessarily restricts type promotion. In the example above, there's no reason a._field wouldn't be safe to promote; we simply decided not to. That seems unfortunate.
Second, and probably more of interest to those of us who maintain the language, the language specification doesn't consider property accesses to refer to declarations directly; they refer to members of interfaces. Those members sometimes arise from getter declarations; sometimes they arise from field declarations; and sometimes they arise through a different process entirely. So the notion of "which declaration a property get refers to" isn't always well defined. For example, consider this code:
abstract class A {
  abstract final int? _field;
}
abstract class B {
  int? get _field;
}
abstract class C implements A, B {}
class D implements C {
  final int? _field;
  D(this._field);
}
test(C c) {
  if (c._field != null) {
    int i = c._field; // OK? ERROR?
  }
}

The reason it's unclear whether c._field should be eligible for type promotion is because it refers to a getter in class C called ._field. But class C doesn't contain a declaration called _field. Instead, this getter arose from merging the interfaces of classes A and B, one of which contains a promotable member called _field, and one of which contains a non-promotable member called _field.
In practice, the implementation makes a choice of whether to allow type promotion, but it does so in an arbitrary and unreliable way. For this example, the code is accepted as written (c._field promotes), but swapping the order of A and B in class C's implements clause (changing it to abstract C implements B, A) leads to a compile error.
With the change, the behavior will be well-defined, and c._field will promote regardless of the order in which C lists its interfaces.
For further discussion see https://github.com/dart-lang/language/issues/3328#issuecomment-1792511446.
Expected impact
The primary effect of this change is to make certain property accesses promotable that previously weren't, so for most purposes it should be non-breaking. However, it is technically a breaking change, because changes to type promotion can lead to different types being inferred in situations where the type is implicit, and those different types can have different behaviors. For example the following code would break:
test(C c) {
  if (c._i != null) {
    var x = [c._i]; // Currently inferred as `<int?>[c._i]`; will change to `<int>[c._i]`.
    x.add(null); // Currently ok; will become an error
  }
}

It's also possible that the improved type promotion could lead to some lints such as unnecessary_non_null_assertion, invalid_null_aware_operator, or unnecessary_cast. If the user has a continuous integration setup which treats these lints as errors, then that could lead to a build failure when upgrading to a version of Dart containing the breaking change.
Mitigation
If any code is broken due to different types being inferred, it should be easy to fix by adding explicit types. For example, in the code above, [c._i] could be changed to <int?>[c._i].
If a continuous integration setup is broken due to lints being treated as errors, then there are two possibilities. Either:

Fix the lint when upgrading the version of Dart
Add // ignore: comments everywhere that's affected, then upgrade the version of Dart, then fix the lints and remove the // ignore: comments.

@vsmenon @grouma @Hixie for a breaking change request.

Can noSuchMethod no longer override privates like this? That was the reason we had previously not implemented this.

Can noSuchMethod no longer override privates like this? That was the reason we had previously not implemented this.

Correct. That was a breaking change we made last year (https://github.com/dart-lang/sdk/issues/49687) and in point of fact it was necessary in order for field promotion to be sound at all.

@leonsenft or @mattrberry - does this change impact the ACX injection system at all?

@leonsenft or @mattrberry - does this change impact the ACX injection system at all?

I don't think it has any impact.

@stereotype441 - is the pattern (at the top of your first comment) common?  Just curious.

LGTM


Incorporate all minerals from the GSO source

We need to finish building out the minerals reference in the GeoKB. This was started with a combination of MRData and Mindat reference materials, where I attempted to develop a new type of conceptual mapping to named entities that can be classed as minerals, commodities, or even chemical elements. While we may need to revisit the notion of single element minerals, the mineral commodity approach seems like it should work.
This work will include bringing in a full representation of the GSO minerals module processed through software code, factoring in where I have already instantiated some items from other sources.

I've started working through the contents of the GSO minerals module and have come up with a few questions we need to answer before I proceed with pulling this into the GeoKB representation. I've attached a simplified Excel table with the major elements from the GSO minerals schema that we might be able to make use of. My questions are based on this.
gso_minerals.xlsx

Do we want to incorporate all minerals from this list or take more of the approach that Peter Schweitzer used for certain things in the USGS Thesaurus where we only bring in selective parts of larger "vocabularies" that are directly related to USGS work? If we do slim it down, how do we decide which minerals to include? Note that the subclass_of field here does contain classification that places certain mineral items as subclassed under other mineral items (e.g., kaolinite is both a mineral material and part of the kaolinite subgroup, which is its own entity).
The primary source for the GSO minerals was RRUFF. They included values in the rruffnameplain column that I'm thinking of using as our primary label when those are different from the value in label because certain queries will work better with values that do not include linguistic special characters or HTML (e.g., Zincohogbomite-2N2S vs. Zincohögbomite-2N2S). We would include the values from label where those are different as aliases, although the example there isn't going to work anyway as we cannot include HTML tags in aliases within Wikibase. Let me know if this is a bad design choice for some reason.
The crystalsystem property in the GSO is a little bit suspect, and I'm not sure we can trust those values. A spot check shows that they do not always align with either RRUFF or Mindat where I'm only seeing single values. The provenance of this property is not discussed in the OFR that published the GSO. If crystal system is useful, I can pull it from Mindat in another step since we have those identifiers. We would model this into the GeoKB such that we have items for the crystal structure types turning them into more functional queryables. But I'd like to know if this is a valuable classifier or not.
The structuralgroup property contains logical linkages to groups that are also classified in the GSO minerals module as "mineral_material," and I'm not entirely sure why they opted to encode it the way they did with simple string values. RRUFF refers to these as "mineral group" and Mindat shows them as a "member of" labeled property. This seems like something we would want to capture in the GeoKB representation. We could include these in the GeoKB using the "part of" general property we already have, simply indicating that one thing is a part of another. We could also provide a reciprocal relationship using "has part" to aid in queries and visual organization of the information. Or we could create a new property for "structural group" or "mineral group" or the like if someone can provide a reasonable way that we would define that property. I also don't understand what fleischersgroup is. In most cases, this is the same value as structuralgroup, but there are exceptions (e.g., Zincrosasite indicates Malachite for "structuralgroup" vs. "rosasite" for fleischersgroup). If someone can explain the significance of these concepts and indicate whether they are useful, that would be helpful.
The Strunz classification in the GSO seems to be simplified from what is in Mindat. Folks had indicated that this would be useful to have in the GeoKB for query purposes, which means we need to first represent the Strunz classification itself in some way so that there are actual items to link with and then incorporate these into the schema for mineral items. It would be useful to know if the strunzcodeV10 and strunzlabel values as used in the GSO mineral module are reasonable and a useful set of codes and labels.
Folks had indicated previously that indicating whether a mineral is on the IMA list or not is useful. In the GSO ontology, we have both a multi-valued imastatus property and a imanumber. Should we incorporate one or both of these as new properties for claims in the GeoKB? The imanumber would be an ExternalID type of property, simply recording the string. The imastatus would be an Item type property pointing to part of the classification scheme defining what the terms (e.g., "grandfathered" mean in the IMA mineral list context).

I do not think we need all of the minerals for our purposes. I think a good starting point would be pulling out all of the unique mineral names from MRDS. Most of the relevant "economic geology" minerals will be in there, and we can relate things from there.
I am okay with using the 'rruffnameplain' labels.
'crystalsystem' is not all that important for what we do.  Feel free to skip it, or if you import it, flag it as unvalidated or something.
The key point here is providing a reciprical relationship between 'structuralgroup' and the primary label. For example, very few geologists would probably realize what you are talking about if you mention zinrosasite (it was a new one to me), but all of us economic geologist know malachite.  Economic geology reports and whatnot often describe things at an observational level, which is sometimes close to the 'structuralgroup' value captured here. Another example might be the Columbite structural group. If an economic geologist is working in an area known to contain columbite, they will probably be able to identify it with a microscope or whatnot. However, they will not be able to immediately tell if it is Columbite-(Fe) or Columbite-(Mn) (these are rruffplain labels for Columbite group minerals) without some sort of chemical measurement. So, I imagine we will be working off of structural group-level data quite often as we compile information from mineral reports.
I skimmed around and I am not sure how it is simplified?  It appears to follow the NN.XY.### format, although not all of the minerals have 3 numbers in the ### spot (this represents the mineral or group). When I have used Strunz codes in the past to aggregate mineral occurrence data, we aggregated to the X and NN levels, which are the two highest orders of the hierarchy. That hierarchical detail seems to be present here, so I say we just use it.  Unless I am missing some detail?
I still do not see much use for IMA status in our work, specifically. If it is easy to roll over with what you are doing, then sure, but if it turns into any sort of challenge, I would say to drop it.

@jrosera - Thanks for the comments. That's perfect!
I'll work in a process to essentially consult MRDS to subset the full list of "mineral materials" from the GSO. I think that seems reasonable, and we can always come back and pull in more entities as use cases expand beyond economic geology.
Thanks for providing feedback on things to ignore. There is no need to pull in additional information beyond what we will actually use as we're not trying to set up the comprehensive resource here.
For the structural group part of this, I think I'll start with the existing part of/has part properties we already have. These are designed to produce the reciprocal relationship you're talking about. There are different schools of thought in the semantics world on using a bunch of different specific properties vs. more general relationships. I go back and forth, and we can always rework the relationships at a later time if needed.
I had worked out the basics of a method to pull in the full Strunz classification system from source material. I'll look at that again but may end up simplifying that for our immediate purposes and use only the part of the classification referenced in the GSO.

@skybristol
I cannot speak too much to ongoing semantics debates, but I would just recommend that you keep in mind that very specific mineral names often require lab methods that are not necessarily part of routine economic geology surveys - especially the older reports that more or less list out mineral phases that were observed in mapping / drilling / thin section etc. While there is great information baked into specific, end-member mineral names based on full geochemical characterization, much of what we work with is at the slightly more general level (e.g., structural group).
My guess is that if you pull all of the unique MRDS materials flagged as ore or gangue you will have a mix of names from specific to structural group.

@jrosera - That's the approach I'm taking this morning. Looking at that list of 743 unique names found in ore or gangue, we do not have complete alignment with either the Geoscience Ontology or Mindat.
The bottom line is that mineralogy is complex just like biological taxonomy that's closer to my own domain. Every scientist that approaches this problem of classification and identification is going to come at it a little bit differently, and the whole system is in flux at any given point with no perfect way of capturing the complexity of the state of scientific knowledge in the simplicity of linked open data and explicit semantics. As you say, at some point in time, some things that show up in an attempt to classify everything are going to be in the process of being studied and better characterized.
Our overall goal with the GeoKB is to have named and identified entities from all the subject matter we study and encounter in our specific scientific portfolio. This is conceptually similar to what Peter Schweitzer has done with much of the USGS Thesaurus work, but we are taking that further into other domains and focusing significant attention on linking "our concepts" with linkable entities from other knowledge representations in order to do the following:

help other people (and ourselves) understand what we're talking about
provide an avenue to go after further details from reference sources when we need them
help distinguish our unique scientific contributions so that other people/systems can leverage those

Decision Points

Make sure the 743 named entities from MRDS have entities in the GeoKB. Names will either be primary label or alias, depending on if we identify a preferred name in a trusted source.
Items will be classified as mineral material and potentially another class if indicated by a trusted source.
Include same as claims to either the Geoscience Ontology, Mindat, or both. This is our assertion that we are functionally talking about the same entity and expect to be able to follow those links to further information as needed.
For the structural group concept, I'm thinking to introduce two new properties, member of and has member, to accomplish reciprocal relationships. These would be semantically distinct from part of and has part, and we'll work at further clarifying the significance of these properties through time and practice.
Once I establish connections to GSO/Mindat, I'll look for any differences in Strunz classification between the sources. We'll have to decide on a trusted source for that information if it comes to it. I'll introduce at least those aspects of the Strunz classification we need to link to but keep that as simple as possible so we can just use these as grouping attributes.
If there is additional information that could prove useful as reference (e.g., comments from GSO items, links to other resources), I'll drop these into item discussion pages so we have it ready at hand.

Questions

The GSO includes a property with a list of chemical elements. I don't know the exact provenance on this, but it appears to align with the two references to chemistry (IMA and RRUFF). Since we have chemical elements as identified items in the GeoKB, is it useful to establish linkages on chemical composition? This would allow us to efficiently answer questions like, "what minerals have calcium and magnesium?" (I actually don't know why the GSO did not encode linkages to chemical elements more explicitly like this since they incorporated a module for elements and could have handled this better than a string list.)


Add option to lock numbering of structural/analytical id

Hi! We have had some struggles lately with objects being re-numbered.
For example, if the walls in a model are called W1, W2, W3.... they will sometimes be called the same thing when the struxml file is opened in FEM-Design again, but sometimes they will be renumbered.
To stop this from happening, we can put "@" before the slabpart name in the struxml. Then the numbering will be "locked".
It is also possible to lock the numbering in the FEM-Design UI, but this setting disappears when exporting to struxml.

We think it should be possible for the user to choose if they want renumbering or not.
When renumbering is good: For example if you want to merge two models, or create a lot of objects and not want to handle potential conflicts between elements with the same name.
When renumbering is bad: When you want to keep track of certain objects.
I'm not sure how this best could be implemented. Some ideas:

Have a component that locks/unlocks the identifier for any element (bar, slab etc)
Have a component for "global settings" where this can be changed
Add input to "save struxml" and "open model" and those components with a toggle for locked/unlocked

This has also been mentioned in case #81

@andosca @Marco-Pellegrino what do you think?

Having a fixed identifier was discussed in #81 and is planned for implementation. So having the possibility to lock the identifier on the component level will be done.
Problem with export from FEM-Design should be raised to BP dev. team.

Duplicate of #81

It will be implemented on any component that creates or modifies an element (bar, slab, support etc.)

It will be implemented on any component that creates or modifies an element (bar, slab, support etc.)

Why not have this operation (of adding a single "@"/locking the identifier) as a separate component? Like this:

Having a fixed identifier was discussed in #81 and is planned for implementation. So having the possibility to lock the identifier on the component level will be done.
Problem with export from FEM-Design should be raised to BP dev. team.

👍 Great! I saw it was discussed in #81 but I thought it is better to have a dedicated case for each topic 😉 On what components will this be implemented? Or is there going to be a new component for this?

Maybe you are correct. I figured that they were so tightly related.

@xRadne That is also an option. Would possibly make for more components. As we intend to have a constructor/modifier for each type of element why not have it on that one as well?

I suggest we do not add any extra input to the components (they have plenty of inputs already),
But instead the identifiers can be locked using a @ in the beginning (which will be equivalent to the .struxml).
We should also add a grasshopper component that locks/unlocks the identifier of any element. This will be more intuitive to most users that don't know how the .struxml works.

using @ at the beginning of the Identifier is a good option.
I am not a big fan of "large components" with several input and a custom component might be better from my point of view

using @ at the beginning of the Identifier is a good option.
I am not a big fan of "large components" with several input and a custom component might be better from my point of view

Just to be clear, Adding @ in the beginning is already working. But, I think it is unintuitive for beginners, and if you want to modify (lock/unlock) then it is needed to 1 deconstruct,  2 add @, 3 modify bar/slab/panel/edgeconnection etc with new identifier


Add an SOP regarding the usage of the release notes generator

Add an SOP about how to use the release notes generator for our web apps.
This could be useful for any existing or new starter developer in our team.
How to create an SOP: https://www.ebi.ac.uk/seqdb/confluence/display/GXA/GEGGENSOP000%3A	SOP+writing%2C+versioning+and+sign-off
SOP template:
https://www.ebi.ac.uk/seqdb/confluence/display/GXA/GEGGENSOPXXX%3A+SOP+template

Done: GEGDEVSOP014 - Generating release notes for our web application into GitHub.
Need to be reviewed by at least 1 dev.

Sandeep has reviewed & approved it.


Added SWC usage to ts-node

As stated in #17 SWC compile code much more faster for dev enviroment no reason to ignore it if can speed up bot start to test things.
I read some topics about SWC in general for ts-node & stuff, we probably not should use it when building prod because of problems with type checking and other
Also added "npx" command to scripts so they will launch 100% from local node_modules.

 SWC Support


Fix regression with Babel 6

Since in Babel 6 it is not supported to replace the argument of a default export declaration with an expression, use a custom "replaceWith" function which handles also that case.
Fixes #155, fixes #156.

Hm ok


overwrite for seo image

using the tobimori.seo.default one can overwrite the metaTitle or ogDescription but not which field gets resolved for the opengraph image. that would be handy to have to reuse an existing field.

You should be able to overwrite every field using its key. (ogImage, set it to a closure that returns a field ideally)
Although make sure the Site field is not set.
You can also use Page models to overwrite the image at a higher point in the cascade.


rye mangles/strips escape sequences when run in cmd.exe with stdout redirected

I've been hacking together an improvement to rye-up.com/get that would enable Windows users to install rye in the same way Linux and macOS users can (piping curl output to shell), though I've hit a wall - no matter what I do, the executable is unable to produce correct output with stdout redirected.
Steps to Reproduce
git clone -b feat/windows/install --single-branch https://github.com/mataha/rye
cd rye
::: Notice I'm redirecting stdout to `nul` here - this is necessary as `cmd.exe`
::: prints every command executed when evaluating piped input, prompts included
curl -fsSL "file:///%CD%/scripts/install.cmd" | cmd /d/x/k >nul

Expected Result

Actual Result
As expected - text is on stdout, which is redirected to nul (though the prompt remains visible):

Redirecting the binary's output to stderr makes the entire text get mangled:

::: This makes invoking the binary roughly equivalent to `rye self install >&2`
set "RYE_INSTALL_OPTIONS=>&2"

With the following change all ANSI escape sequences are stripped except those in prompts (last line):

diff --git a/rye/src/cli/rye.rs b/rye/src/cli/rye.rs
index 72d7ca357ff3..733710bad41e 100644
--- a/rye/src/cli/rye.rs
+++ b/rye/src/cli/rye.rs
@@ -525,6 +525,7 @@ fn perform_install(
         },
     };

+    let _guard = crate::tui::redirect_to_stderr(true);
     echo!("{}", style("Welcome to Rye!").bold());

     if matches!(mode, InstallMode::AutoInstall) {

I have no idea what's going on; why is dialoguer able to work correctly in every instance?
Admittedly I don't believe this is a bug in rye itself, but I have to start somewhere.
Version Info
rye 0.34.0
commit: 0.33.0+14 (761e4b583 2024-05-18)
platform: windows (x86_64)
self-python<EMAIL_ADDRESS>symlink support: true
uv enabled: true

Not applicable anymore - figured how to run rye without butchering stdout.


Erin thacker add silver members

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you included a URL for your SVG or added it to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

:heavy_check_mark: Deploy Preview for landscape ready!
:hammer: Explore the source changes: 581c65db5bccb2a2281c56ea564ba0302274989c
:mag: Inspect the deploy log: https://app.netlify.com/sites/landscape/deploys/60b6891b6e2f4d0007c08f35
:sunglasses: Browse the preview: https://deploy-preview-2121--landscape.netlify.app


Hold np.ndarray not list in Experience

To hold ndarray, the array should be padded with its max episode length.
For now, it makes sense to have the data with list.


[question] italics in markdown

hello! first of all, absolutely lovely theme, an even better version of solarized, it perfectly scratched the itch I had over a high-contrast blue dark theme.
quick question, why disable markdown italics?
in the default theme, an italic looks like this:

which i do concede, orchid is a very nice color choice and as you described here you don't quite like bold fonts (and i wholeheartedly agree, don't like bold text) and hl link is faster than the default hl
wouldn't setting g:nightflyItalics to true enabling it be a better experience?
imho looks quite nice when you patch it

how do you feel about letting this be a config?
thanks in advance!

I am against bolds, yes.
However, I do use and support italics.
In my Neovim theme for Markdown Tree-siiter I already support italics, so I assume you are talking about Vim and the Tim Pope Markdown syntax?

I assume you are talking about Vim and the Tim Pope Markdown syntax?

yup, sorry for the omission, I have some custom markdown syntax on a personal plugin (just some specific tokens, no major changes) and as such I disable treesitter on markdown files
yes, this uses the default tpope plugin that comes by default, both screenshots are done with all other plugins disabled (incl. my custom ones and TS), and just nightfly enabled with this simple patch:

I can use TS just fine and convert my syntax to .scm but my setup is quite convenient, but this is quite a small change, I could put a PR up in a sec if you want

Implemented.
Good suggestion, thanks.


implement callback function in imputation

Cleaning and adding callback function similarly to last time

Again, not sure if this is the best way to implement it as it requires the usage of the Decomposition object.


search on protein family

can we add protein family to the global search drop down?

Would this be the correct search results? Showing the protein families tab?

search on protein family may mean,

search on protein family definition. your result will be a list of protein family id and family names, and you can link to all features within that protein family.

search on features that match to one or list of protein family id(s).

search on genomes matches your keyword criteria and show protein family tab.

or something else. @jimdavis1 i saw same request multiple time. Would you clarify your need?

Maulik and I discussed, and we're going to address this issue on PDP5, nov 2018 release. closing.


The toggle method on mat-checkbox does not emit to valueChanges

Bug, feature request, or proposal:
Bug
What is the expected behavior?
valueChanges should emit whenever the checkbox's value changes
What is the current behavior?
If the checkbox changes value via the toggle() method, valueChanges does not emit
What are the steps to reproduce?
https://stackblitz.com/edit/angular-35rjy5
What is the use-case or motivation for changing an existing behavior?
Sometimes there are other places in the app that toggle a checkbox
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
material 6.4.1
Is there anything else we should know?

Will be fixed by https://github.com/angular/material2/pull/11902.

Like when?! It's been there since August what the heck are you guys waiting for??


Add additional check to only extract titles from questions

Add private method to handle what gets extracted from the domains in parse_domain method.
Now only posts that are questions will extract both body and title whereas posts that are answers will only extract the body.
Link to the corresponding GitHub Issue here: We shouldn't extract domains from title of answers
Please let me know if you have any feedback!

This looks good to me - I'm happy to merge it, unless you closed it because you want to try something different?

Hi @ArtOfCode- closed it so I could take a look at those failing SpamDomainController tests, unless you think they are not related? If all is good, Ill reopen!

I'll have a check, but tests failing on metasmoke is not uncommon... which we should probably fix :)

:-) let me know, reopening just in case.

@ArtOfCode- JS can't be jpotts244's fault because JS wasn't changed, rubocop is pointing at unchanged files as well (although we should fix that on master), and rails tests are pointing at some unexpected redirected in SpamDomainsController, which seems unrelated to me.
IMO this is good to merge.

Aye, those test failures existed before this PR: build 2384@master/50c69de. Merging, thanks for working on this @jpotts244!

Thanks all - cheers!


Chore bump dev deps

Pull Request Checklist
🚨 Please review the guidelines for contributing to this repository.

[ ] Appropriate label or labels have been added
[ ] ✅ Tests for the changes have been added (for type:fix / type:feat)
[ ] 📝 Docs have been reviewed, added or updated if needed (for type:fix / type:feat)
[ ] 🏁 Issue number has been linked if this PR closes one

Description
Please describe your pull request.
Breaking Change?

[ ] 💥 Yes
[ ] No

❤ Thank you for contributing!

Codecov Report
Patch and project coverage have no change.

Comparison is base (04cb86d) 97.46% compared to head (abd24b8) 97.46%.
Report is 1 commits behind head on master.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #370   +/-   ##
=======================================
  Coverage   97.46%   97.46%
=======================================
  Files          31       31
  Lines         394      394
  Branches       67       67
=======================================
  Hits          384      384
  Misses          8        8
  Partials        2        2

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


forgot-password fails if loginOnPasswordReset: true

ISSUE
Superlogin fails with 'Unhandled rejection TypeError: user.createSession is not a function'
on
POST /password-reset
if
// If set to true, the user will be logged in automatically after resetting the password
loginOnPasswordReset: true
WORKAROUND
Set loginOnPasswordReset: false
SUPERLOGIN VERSION PER PACKAGE.JSON
"superlogin": "^0.6.1"

@tonydiep - The NPM has not been updated in quite a while, this issue and others have been fixed in the github repo, to get the fixes you will need to pull the version directly from the repo :yum:
You can edit the superlogin package.json directly with "superlogin": "colinskow/superlogin#commit_hash" which as of October 22, 2017 would look like:
    "superlogin": "colinskow/superlogin#8e7c7c1a77c1f5303b74f941208349e3a6e0c9ad",
Then you need to do npm install, you can also do everything from the command line with a --save to update the package.json with npm install --save colinskow/superlogin#commit_hash, which would look like below using the current master as of October 22, 2017:
`npm install --save colinskow/superlogin#8e7c7c1a77c1f5303b74f941208349e3a6e0c9ad
Just remember you then own the version of superlogin and if the npm package is ever updated you will want to make changes or update to get the latest directly from the npm configuration.  Good luck and post back here to confirm the fix and close the issue.

Thanks for the quick reply and the instructions for using the github repo. I'm going to stick with the npm version as I don't have the skills to maintain my own version of superlogin. Can I ask if there are plans to update the npm version?

@tonydiep - There is not much more to maintain by pointing to the repo directly, just that one line in the package.json.

Can I ask if there are plans to update the npm version?

Updates are controlled by the owner of this repo @colinskow , so he would be the only one to answer for sure.  I wouldn't expect anything until there is official word from Colin, who most recently commented that he was busy on other projects.


Validation issues should mention names of affected files

not as in #24 – there you don't know what files are affected

Duplicate of #10, closing


#161075190 Added category page

What does this PR Do?
Creates a category page where the user can see all items and there categories
How should this be manually tested
steps for testing :
-Create a working folder on your desktop or preferred location.
-Navigate to your working folder and open a new terminal
-Type the following git clone https://github.com/jonathanmusila/store-manager.git
-Navigate to the UI and open category.html in a preferred browser.
What are the relevant pivotal tracker stories?
Story-ID #161075190
Screenshot

the search field is hardly visible you can change the background color

You can put some space between the table and the search field.

Nice table layout 🔥


SDTM to FHIR transformation (conceptual)

Outcome: Table with SDTM resource and column names mapped to FHIR resources and attributes
In Nov 2023, the team decided to use FHIR as the data layer for ISARIC 3.0. Reasons why we chose it over SDTM/OMOP:

SDTM: This is the existing schema and is difficult to extend as SDTM terminology is controlled by CDISC
OMOP: Issues with dates (have to specify full date, which we do not have), uses their own terminology (mapped to SNOMED/ICD/...), but can be extended.

Full reasoning is in this document: TODO
As part of this process, we are mapping existing SDTM resources to FHIR terminology.

Rationale for selection of FHIR as the central data model;
ISARIC_ARCH_FHIR.docx


Add friends

I need that after a long time.
It would help, not very effective in general use.

Could you provide more details?

I want to add an account as a friends via Atarashii.
I can do that in the website and i thought i could be great.

Not currently supported in our back-end API. In fact, there isn't a lot of user-based stuff there yet. Until we get around to adding that in the API, it won't be possible to do in the application, for MyAnimeList at least.


analysis & execution strategy integration

UI should support different analysis types & values

some analysis types:
factorial analysis, bayesian optimization, t-tests (as in paper)

depending on the result of analysis, it should be able to do trigger next phases (e.g. offer 10 more experiments, stop experiment etc.)

implemented here


Task: review & improve if needed UI and UX of admin2 commands

What is the task about?
What is the task about?
Compare UI and UX between admin2 commands and current corresponding commands.
This will be an umbrella issue for UI and UX improvements for each of the commands.
Parent feature
https://github.com/repository-service-tuf/repository-service-tuf-cli/issues/532
TODO

[ ] Sign command
[ ] Ceremony command
[ ] Metadata Update command
[ ] Change v1 to not use online key that is also used by root offline keys

Sign  UI & UX improvements
Ceremony UI & UX improvements
Metadata Update improvements
Code of Conduct

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

Adding here as a note for error handling in the user UI/UX
Please enter path to encrypted private key: tests/files/key_storage/online1.key
Please enter password:
Traceback (most recent call last):
  File "/Users/kairo/.local/share/virtualenvs/repository-service-tuf-cli-EVsxK5JG/bin/rstuf", line 8, in <module>
    sys.exit(rstuf())
  File "/Users/kairo/.local/share/virtualenvs/repository-service-tuf-cli-EVsxK5JG/lib/python3.9/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/Users/kairo/.local/share/virtualenvs/repository-service-tuf-cli-EVsxK5JG/lib/python3.9/site-packages/rich_click/rich_command.py", line 126, in main
    rv = self.invoke(ctx)
  File "/Users/kairo/.local/share/virtualenvs/repository-service-tuf-cli-EVsxK5JG/lib/python3.9/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/kairo/.local/share/virtualenvs/repository-service-tuf-cli-EVsxK5JG/lib/python3.9/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/kairo/.local/share/virtualenvs/repository-service-tuf-cli-EVsxK5JG/lib/python3.9/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/kairo/.local/share/virtualenvs/repository-service-tuf-cli-EVsxK5JG/lib/python3.9/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/Users/kairo/dev/RSTUF/repository-service-tuf-cli/repository_service_tuf/cli/admin2/ceremony.py", line 91, in ceremony
    _add_root_signatures_prompt(root_md, None)
  File "/Users/kairo/dev/RSTUF/repository-service-tuf-cli/repository_service_tuf/cli/admin2/helpers.py", line 415, in _add_root_signatures_prompt
    _add_signature_prompt(root_md, key)
  File "/Users/kairo/dev/RSTUF/repository-service-tuf-cli/repository_service_tuf/cli/admin2/helpers.py", line 377, in _add_signature_prompt
    signer = _load_signer_from_file_prompt(key)
  File "/Users/kairo/dev/RSTUF/repository-service-tuf-cli/repository_service_tuf/cli/admin2/helpers.py", line 142, in _load_signer_from_file_prompt
    private_key = load_pem_private_key(private_pem, password.encode())
TypeError: Password was given but private key is not encrypted.

... and cryptography.exceptions.UnsupportedAlgorithm, which may also be raised by load_pem_private__key.

UnsupportedAlgorithm may be also raised in load_pem_public_key, so we should also except it here:
https://github.com/repository-service-tuf/repository-service-tuf-cli/blob/6bbf1e809695bc388a9084e51bd20ab455573a47/repository_service_tuf/cli/admin2/helpers.py#L164


SR-6084: libdispatch.so missing from snapshot builds

Adjust install path for libdispatch in CMakelists.txt

Seems to fix https://bugs.swift.org/browse/SR-6084 for me (but I am not a buildbot ;) )
@jrose-apple @compnerd

@shahmishal, how would you suggest testing that this fixes installable toolchains on Linux?

https://github.com/apple/swift/pull/12383
@swift-ci test

Well, that still didn't test the installable package part, but it didn't make any of the existing parts worse. Do you think we should run that preset explicitly, or just merge this?

I'd suggest just to merge it and check the next nightly snapshot tar ball to be sure it is fixed.
I manually ran something closely derived from the linux-buildbot config and verified that libdispatch.so was in the expected plan in the produced tarball.  So I really do expect this to fix the problem, but since I can't exactly reproduce the build machine environment, I could have missed something.

All right, makes sense.

Mishal, does it make sense to kick off a middle-of-the-day package build so we can see if it worked? Or should we just wait until tomorrow/Monday?

@dgrove-oss @compnerd  We are still seeing test failure:
https://bugs.swift.org/browse/SR-6123
******************** TEST 'swift-package-tests :: swift-package-init-lib.md' FAILED ********************
Script:
--
rm -rf /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.dir
mkdir -p /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.dir/Project
/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/bin/swift package --package-path /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.dir/Project init --type library
/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/bin/swift build --package-path /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.dir/Project 2>&1 | tee /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.build-log
/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/bin/swift test --package-path /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.dir/Project 2>&1 | tee /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.test-log
/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/llvm-linux-x86_64/bin/FileCheck --check-prefix CHECK-BUILD-LOG --input-file /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.build-log /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/swift-integration-tests/swift-package-init-lib.md
/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/llvm-linux-x86_64/bin/FileCheck --check-prefix CHECK-TEST-LOG --input-file /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.test-log /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/swift-integration-tests/swift-package-init-lib.md
/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/llvm-linux-x86_64/bin/FileCheck --check-prefix CHECK-NO-WARNINGS-OR-ERRORS --input-file /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.build-log /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/swift-integration-tests/swift-package-init-lib.md
/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/llvm-linux-x86_64/bin/FileCheck --check-prefix CHECK-NO-WARNINGS-OR-ERRORS --input-file /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.test-log /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/swift-integration-tests/swift-package-init-lib.md
--
Exit Code: 1

Command Output (stdout):
--
$ "rm" "-rf" "/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.dir"
$ "mkdir" "-p" "/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.dir/Project"
$ "/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/bin/swift" "package" "--package-path" "/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.dir/Project" "init" "--type" "library"
# command output:
Creating library package: Project
Creating Package.swift
Creating README.md
Creating .gitignore
Creating Sources/
Creating Sources/Project/Project.swift
Creating Tests/
Creating Tests/LinuxMain.swift
Creating Tests/ProjectTests/
Creating Tests/ProjectTests/ProjectTests.swift

$ "/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/bin/swift" "build" "--package-path" "/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.dir/Project"
$ "tee" "/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.build-log"
# command output:
Compile Swift Module 'Project' (1 sources)

$ "/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/bin/swift" "test" "--package-path" "/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.dir/Project"
note: command had no output on stdout or stderr
error: command failed with exit status: 1
$ "tee" "/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.test-log"
# command output:
Compile Swift Module 'ProjectTests' (1 sources)
<module-includes>:1:10: note: in file included from <module-includes>:1:
#include "CoreFoundation.h"
         ^
/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/lib/swift/CoreFoundation/CoreFoundation.h:77:10: note: in file included from /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/lib/swift/CoreFoundation/CoreFoundation.h:77:
#include <CoreFoundation/CFPropertyList.h>
         ^
/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/lib/swift/CoreFoundation/CFPropertyList.h:17:10: note: in file included from /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/lib/swift/CoreFoundation/CFPropertyList.h:17:
#include <CoreFoundation/CFStream.h>
         ^
/home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/lib/swift/CoreFoundation/CFStream.h:20:10: error: 'dispatch/dispatch.h' file not found
#include <dispatch/dispatch.h>
         ^
<unknown>:0: error: could not build C module 'CoreFoundation'
error: terminated(1): /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/usr/bin/swift-build-tool -f /home/buildnode/jenkins/workspace/swift-PR-Linux/branch-master/buildbot_linux/none-swift_package_sandbox_linux-x86_64/tests/Output/swift-package-init-lib.md.tmp.dir/Project/.build/debug.yaml test

--

********************

@shahmishal I think that is a different issue.  Looks like the Foundation module is failing to be built due to the headers missing.  Can we get a verbose trace of that build?  I suspect that the path being used for building the module is incorrect or that headers are being copied in a weird way.  This would be easier to understand if the Foundation build system was also done similar to the rest of swift/libdispatch so that everything could be tied together with dependency tracking.

@compnerd Thanks I will keep bug open https://bugs.swift.org/browse/SR-6123.
What about his error?
https://ci.swift.org/job/swift-protobuf-linux-ubuntu-16_10/14/console
+ swift build -c release
latest_toolchain/swift-DEVELOPMENT-SNAPSHOT-2017-10-15-a-ubuntu16.10/usr/bin/swift-build: error while loading shared libraries: libdispatch.so: cannot open shared object file: No such file or directory

@shahmishal , that error is pretty interesting.  It implies that the DT_RUNPATH (or possibly DT_RPATH) is incorrect, or the embedded values are not correct.  Would it be possible to get the output of readelf -Wa of the swift-build binary?

Why would it mean that, rather than simply that libdispatch.so isn't being installed?

@jrose-apple oh it could absolutely be that too.  However, cmake will build binaries with a rpath for testing purposes and then adjust them at install time.  So, that was the first thing which came to mind.  The readelf output would show where it was looking for the libraries.


Bold each line individually

This should make the message in Travis logs look better.

Will check in when the tree is green.

Sadly this didn't fully fix the formatting on Travis. Looks like Travis uses a non-monospace font or a font that doesn't have the line drawing characters or something.


[blas] Add missing return

Add bug fix for blas raw implementation for missing return.
Signed-off-by: Parichay Kapoor<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #916. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #916. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.


imho bad things about strax / stratis

written in C#

you see this maybe as advantage, but as pure linux server user, I just hate it.
you can run it with docker, but it is not really stable, has memory problems (better since the switch to strax, but when blockchain grows this will be again a problem) and staking is somehow ending for no reasons, happening every few weeks.
hundreds of warnings during compile - honestly is this the way of building trustworthy software ?
I bet nerds do not trust or like this language, so I would consider to switch to golang, rust or whatever is working natively on linux.

not having a fixed main address

this is by far the most annoying thing if you reinstall your wallet, it just uses new addresses (without possibility to use the old one) and your coins are soon spread around. The only and best way I found was moving all coins to a new address with could bring you in a lot of problems explaining this to tax office.
backup of the wallet file is by far the better method and works at least.

Sincerly hope you are trolling.

$0.44 during a bull run is trolling...
or maybe the great plan of inflation
like from https://chainz.cryptoid.info/strax/address.dws?XCb7PegDAmE1kXeFeQVXbt411cTjHLaExV.htm
or the extremly stable wallets irony which can be run unattended for maybe 4 weeks

Hi @weetie , you are more than welcome to raise these issues with me in Discord (fassadlr). Message me there then we can discuss further.

Link:
https://discord.com/channels/404643249798512652/404646522425442307


Build failure with polybar-3.4.1, xpp-1.4.0, i3ipcpp-0.7.1

Build Process
Describe how you build polybar, list the exact commands you are using:
$ git clone https://github.com/polybar/polybar --recursive
# Grab latest release versions of xpp, i3ipcpp, polybar
$ cd polybar/lib/xpp && git checkout 1.4.0
$ cd ../i3ipcpp && git checkout v0.7.1
$ cd ../.. && git checkout 3.4.1
$ mkdir build && cd build && cmake ..
$ make

If you build polybar directly from this repository:

Output of git describe --tags:

3.4.1
List exactly where you are building from and which version you are building.
polybar-3.4.1, with xpp at 1.4.0 and i3ipcpp at v0.7.1. All latest release versions.
Build Log
Post everything that is output to the terminal while building polybar below. This HAS to include the output of the cmake and make commands, if you used them.
$ cmake .. # From `build` directory
-- Trying to enable ccache
-- Using compiler cache /usr/bin/ccache
-- The CXX compiler identification is GNU 9.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- No build type specified; using Release
-- Using supported compiler GNU-9.2.0
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2")
-- Looking for C++ include pthread.h
-- Looking for C++ include pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- Checking for module 'cairo-fc'
--   Found cairo-fc, version 1.16.0
-- Checking for module 'alsa'
--   Found alsa, version <IP_ADDRESS>
-- Checking for module 'libcurl'
--   Found libcurl, version 7.67.0
-- Checking for module 'libmpdclient'
--   Found libmpdclient, version 2.16
-- Checking for module 'libnl-genl-3.0'
--   Found libnl-genl-3.0, version 3.5.0
-- Checking for module 'libpulse'
--   Found libpulse, version 13.0
-- Checking for module 'xcb-composite'
--   Found xcb-composite, version 1.13.1
-- Checking for module 'xcb-xkb'
--   Found xcb-xkb, version 1.13.1
-- Checking for module 'xcb-randr'
--   Found xcb-randr, version 1.13.1
-- Checking for module 'xcb-randr>=1.12'
--   Found xcb-randr, version 1.13.1
-- Checking for module 'xcb-xrm'
--   Found xcb-xrm, version 1.3
-- Checking for module 'xcb-cursor'
--   Found xcb-cursor, version 0.1.3
--  Build:
--    Version: 3.4.1-dev
--    Type: Release
--    CXX: /usr/bin/c++  -Wall -Wextra -Wpedantic -O3 -DNDEBUG
--    LD: /usr/bin/ld
--  Install Paths:
--    PREFIX:  /usr/local
--    BINDIR:  /usr/local/bin
--    DATADIR: /usr/local/share
--    DOCDIR:  /usr/local/share/doc/polybar
--    MANDIR:  /usr/local/share/man
--  Targets:
-- [X]   polybar-msg
-- [ ]   testsuite
-- [X]   documentation
--  Module support:
-- [X]   alsa (<IP_ADDRESS>)
-- [X]   curl (7.67.0)
-- [X]   i3
-- [X]   mpd (2.16)
-- [X]   network (libnl) (3.5.0)
-- [X]   pulseaudio (13.0)
-- [X]   xkeyboard (1.13.1)
--  X extensions:
-- [X]   xcb-randr (1.13.1)
-- [X]   xcb-randr (monitor support) (1.13.1)
-- [X]   xcb-composite (1.13.1)
-- [X]   xcb-xkb (1.13.1)
-- [X]   xcb-xrm (1.3)
-- [X]   xcb-cursor (0.1.3)
--  Log options:
-- [X]   Trace logging
-- The C compiler identification is GNU 9.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Checking for module 'xcb-proto'
--   Found xcb-proto, version 1.13
-- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.17", minimum required is "2.7")
-- XCB[XCB]: Found component XCB
-- Found XCB_XCB: /usr/lib64/libxcb.so
-- XCB[ICCCM]: Found component ICCCM
-- Found XCB_ICCCM: /usr/lib64/libxcb-icccm.so
-- XCB[EWMH]: Found component EWMH
-- Found XCB_EWMH: /usr/lib64/libxcb-ewmh.so
-- XCB[UTIL]: Found component UTIL
-- Found XCB_UTIL: /usr/lib64/libxcb-util.so
-- XCB[IMAGE]: Found component IMAGE
-- Found XCB_IMAGE: /usr/lib64/libxcb-image.so
-- Found XCB: /usr/lib64/libxcb.so;/usr/lib64/libxcb-icccm.so;/usr/lib64/libxcb-ewmh.so;/usr/lib64/libxcb-util.so;/usr/lib64/libxcb-image.so
-- Searching for xcbgen with python2
-- Found xcbgen in /usr/lib64/python2.7/site-packages
-- XCB[RANDR]: Found component RANDR
-- Found XCB_RANDR: /usr/lib64/libxcb-randr.so
-- Found XCB: /usr/lib64/libxcb.so;/usr/lib64/libxcb-icccm.so;/usr/lib64/libxcb-ewmh.so;/usr/lib64/libxcb-util.so;/usr/lib64/libxcb-image.so;/usr/lib64/libxcb-randr.so
-- XCB[COMPOSITE]: Found component COMPOSITE
-- Found XCB_COMPOSITE: /usr/lib64/libxcb-composite.so
-- Found XCB: /usr/lib64/libxcb.so;/usr/lib64/libxcb-icccm.so;/usr/lib64/libxcb-ewmh.so;/usr/lib64/libxcb-util.so;/usr/lib64/libxcb-image.so;/usr/lib64/libxcb-randr.so;/usr/lib64/libxcb-composite.so
-- XCB[XKB]: Found component XKB
-- Found XCB_XKB: /usr/lib64/libxcb-xkb.so
-- Found XCB: /usr/lib64/libxcb.so;/usr/lib64/libxcb-icccm.so;/usr/lib64/libxcb-ewmh.so;/usr/lib64/libxcb-util.so;/usr/lib64/libxcb-image.so;/usr/lib64/libxcb-randr.so;/usr/lib64/libxcb-composite.so;/usr/lib64/libxcb-xkb.so
-- xpp: including xcb proto composite.xml
-- xpp: including xcb proto randr.xml
-- xpp: including xcb proto xkb.xml
-- xpp: including xcb proto xproto.xml
-- Checking for module 'jsoncpp>=1.7.7'
--   Found jsoncpp, version 1.9.2
-- Found font: fixed:pixelsize=10
-- Font not found: unifont:fontformat=truetype
-- Found font: wuncon siji:pixelsize=10
-- Configuring done
-- Generating done
-- Build files have been written to: /home/jake/Programs/polybar/build

$ make
Scanning dependencies of target doc_html
[  1%] sphinx-build html: see doc/builder-html.log
WARNING: html_static_path entry '/home/jake/Programs/polybar/doc/_static' does not exist
[  1%] Built target doc_html
Scanning dependencies of target doc_man
[  2%] sphinx-build man: see doc/builder-man.log
[  2%] Built target doc_man
Scanning dependencies of target doc
[  2%] Built target doc
Scanning dependencies of target xpp
[  3%] Linking CXX static library libxpp.a
Traceback (most recent call last):
  File "/home/jake/Programs/polybar/lib/xpp/generators/cpp_client.py", line 3163, in <module>
    from xcbgen.state import Module
  File "/usr/lib64/python2.7/site-packages/xcbgen/state.py", line 7, in <module>
    from xcbgen import matcher
  File "/usr/lib64/python2.7/site-packages/xcbgen/matcher.py", line 12, in <module>
    from xcbgen.xtypes import *
  File "/usr/lib64/python2.7/site-packages/xcbgen/xtypes.py", line 1221, in <module>
    class EventStruct(Union):
  File "/usr/lib64/python2.7/site-packages/xcbgen/xtypes.py", line 1239, in EventStruct
    out = __main__.output['eventstruct']
KeyError: 'eventstruct'
make[2]: *** [lib/xpp/CMakeFiles/xpp.dir/build.make:70: lib/xpp/libxpp.a] Error 1
make[1]: *** [CMakeFiles/Makefile2:477: lib/xpp/CMakeFiles/xpp.dir/all] Error 2
make: *** [Makefile:130: all] Error 2

Environment:

Distro (with Version):
Gentoo

Additional context
Add any other context that you think is necessary about the problem here.
The build works fine if polybar, xpp, and i3ipcpp are a ttheir newest commits. It seems that something changed with xpp since its release 1.4.0 and that fixes this breakage. An easy remedy would seem to be a version bump of xpp.

That's not how you build polybar. Please follow the instructions on the wiki. For tagged releases there are release tar balls here.
A certain polybar commit or version is only guaranteed to work the the specific i3ipcpp and xpp commit which it is associated with (via git submodules). So manually checking out different commits in those submodules is not advised. If you want to make sure that the submodules are at the right commit, run git submodule update --init --recursive after checking out a new polybar branch or commit.


[BSI][0.5.4-alpha] Unencrypted Sensitive Data in External Storage

Rating: High
Description:
The App saves the diagnosis keys it receives on the device's external storage. Android's external storage is not protected by sandboxing, therefore any other app can access this data. There is no sign of encryption done by the app before persisting the keys on its external storage.
It is recommended to save sentivie data in an encrypted form, preferrably in the app's local storage directory.
Proof of Concept:
in Class de.rki.coronawarnapp.receiver.DiagnosisKeyDownloadReceiver:
setupReceiver(openDownloadIDs: AtomicReference<MutableList<Long>>, cancellableContinuation: CancellableContinuation<List<File>>):
	val receiver = DiagnosisKeyDownloadReceiver(CoronaWarnApplication.getAppContext().getExternalFilesDir(null), openDownloadIDs, cancellableContinuation)
	......
	receiver.register()

Additionally in TestForApiFragment.enterOtherKeys():
	val dir = File(File(requireContext().getExternalFilesDir(null), "key-export"), token ?: "")
	......
	googleFileList = KeyFileHelper.asyncCreateExportFiles(appleFiles, dir)

related: corona-warn-app/cwa-documentation#165

@BSI-TF-CWA The diagnosis keys that the app receives from cwa-server do not seem to be sensitive data, right? Why should the app spend effort encrypting them, when everybody could just download them from cwa-server themselves?

Files will be stored as a ZIP together with the Signature. The Storage Directory has changed to internal in the referenced PR and the Download Manager is not used anymore.

This issue is solved as we now store the data internally.


some clean up and enhancements

better naming
containers health checker

@Ali-Razmjoo : maybe we should put pytest in script of travis.yml because it's currently not running and it's a bug now

@Ali-Razmjoo but we don't have any defined tests...

@dhirensr but we don't have any defined tests...


JSDoc Template and Type Definitions

We either need a template in which we can control the nesting of object params or look into creating type definition for known objects such as Mapp-Layer, Mapp-Location, httpRequest, httpResponse, etc.

It would be great in the future for global typedefs to possibly show a list of place where it is referenced


Zarr version 2 or 3

Thanks for making this library available. I think it is nice to have an alternative in C/C++ besides tensorstore.
Looking through the code, I am a bit confused whether this library supports Zarr versions 2 or 3 or both?
Here, I can see that the "zarr_format": 2 is used: https://github.com/abcucberkeley/cpp-zarr/blob/main/src/zarr.cpp#L29
And here, I the sharding codec is checked, which is only available in version 3: https://github.com/abcucberkeley/cpp-zarr/blob/main/src/zarr.cpp#L43-L46
However, for version 3 other metadata keys have changed (e.g. dimension_separator -> chunk_key_encoding) and the json files are now all called zarr.json instead of .zarray.

Thank you for your interest in cpp-zarr. We currently only support v2 of the Zarr spec but we were experimenting with adding v3 features. We added sharding first because we had use cases where we thought sharding could provide major speed increases for us.

Thanks for the reply! We might have some capacity to contribute to your library in the coming months. Would you be interested in PRs that improve support for Zarr v3?

Yes, we would be interested in that. I think having some real support for Zarr v3 would be great for the library.


Exception hyperlinks not working with modules located in subfolders of global working directory

From<EMAIL_ADDRESS>on 2014-11-06T21:09:15Z
Spyder Version:  2.2.4
Python Version:  2.7.5
Qt Version    :  4.8.4, PySide 1.2.1 on Windows
pyflakes >=0.5.0:  0.7.3 (OK)
pep8 >=0.6      :  1.4.6 (OK)
IPython >=0.13  :  1.0.0 (OK)
rope >=0.9.2    :  0.9.4 (OK)
sphinx >=0.6.6  :  1.1.3 (OK)
matplotlib >=1.0:  1.3.0 (OK)
sympy >=0.7.0   :  0.7.3 (OK)
pylint >=0.25   :  None (NOK)
What steps will reproduce the problem?

unzip 'somesubfolder.zip' and put the 'somesubfolder' folder in your Spyder Global Working Directory
In Spyder, open (I used File->Open...) the 'main.py' file inside 'somesubfolder'
Run (F5) and click on the last hyperlink ('File "somemodule.py", line 2, in raise_an_error') in the resulting error

What is the expected output? What do you see instead?
I expect to be taken to line 2 of 'somemodule.py', but instead I'm just taken back to the editor where I last was ('main.py' as that's where I was when I ran with F5).
I'm guessing also that I should see this hyperlink refer to the full file location, "C:\Users\Andy\Google Drive\Development\Spyder-workspace\somesubfolder\somemodule.py" instead of just "somemodule.py".
Please provide any additional information below
. -Doesn't matter if I'm running this in an iPython console or Python interpreter.
-I'm on Windows 8.1 and my global working directory is "C:\Users\Andy\Google Drive\Development\Spyder-workspace"
-In case you have trouble reproducing this bug, there's a bit more info about my experience with this issue on a stackoverflow post I made about it: https://stackoverflow.com/questions/26666159/spyder-exception-hyperlinks-not-working-with-modules-located-in-subfolders-of-gl/26766578#26766578
Attachment: somesubfolder.zip
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=2043

From ccordoba12 on 2015-01-08T15:10:53Z
Labels: -MS-v2.3.3 MS-v2.3.4

From ccordoba12 on 2014-11-07T09:02:57Z
Labels: Cat-Console MS-v2.3.3


several non-multienv packages are downloaded, despite being specified as multienv

Describe the bug
Installing @aws-amplify/cli@multienv with yarn results in several non-multienv packages being downloaded, resulting in faulty behavior.
To Reproduce

Run yarn global add @aws-amplify/cli@multienv
Go to global yarn directory (yarn global bin)
Observe non-multienv version number in node_modules/graphql-elasticsearch-transformer/package.json
Observe non-multienv version in global yarn.lock entry for graphql-elasticsearch-transformer

Expected behavior
Multienv versions of graphl-*-transformer packages should resolve to correct multienv versions.
Desktop (please complete the following information):

OS: macos

Additional context
I have also tested with npm -g install @aws-amplify/cli@multienv and am observing similar results.

This issue may be related to #631.
What clued me into this behavior in the first place was the lack of env in the DDBTableName variable, even though I was using @aws-amplify/cli@multienv

This is possibly a semver interpretation issue? See here.

I've also tested with npm -g install

I've found a temporary workaround by installing the problematic packages with more explicit versions (e.g. yarn global add graphql-elasticsearch-transformer@multienv)

@thisjeremiah There was an issue with publishing the multienv tag graphql-* packages. Looking into it.


GpuParticles2D jitter when scene tree is paused for various different ProcessMaterial properties

Godot version
4.2
System information
Linux Mint 21.1 Vera
Issue description
Issue is similar to #85213, #65390, #50824
Pausing the scene tree while particles are emitting displays jittering behavior. The jittering occurs using various different ParticleMaterial properties. The minimal test project uses tangential accel as an example but turbulence and gravity show jitter as well.

Steps to reproduce
Open the project and click play and watch the particles jitter when the game pauses after 5.0 seconds.
Minimal reproduction project
ParticleTest.zip

I asked about this in the forums before figuring out to come here:
https://forum.godotengine.org/t/gpuparticles2d-does-not-seem-to-fully-pause/36174

Thanks for the report! Consolidating in https://github.com/godotengine/godot/issues/65390.


feat(tsi): optimize series iteration

When using queries like 'select count(_seriesKey) from bigmeasurement`, we
should iterate over the tsi structures to serve the query instead of loading
all the series into memory up front.
Closes #20543
Describe your proposed changes here.

[ ] CHANGELOG.md updated with a link to the PR (not the Issue)
[x] Well-formatted commit messages
[x] Rebased/mergeable
[x] Tests pass
[x] Documentation updated or issue created (provide link to issue/pr)
[x] Signed CLA (if not already signed)

Note we also have the _series System Iterator for show series queries - this also requires everything to be slurped into memory per-measurement.

Note we also have the _series System Iterator for show series queries - this also requires everything to be slurped into memory per-measurement.

Now with gofmt run

Now with gofmt run

We're going to do this in flux instead of influxql, so this can be closed.

We're going to do this in flux instead of influxql, so this can be closed.

@benbjohnson We're back to planning on doing this in influxql, so this PR is back on the menu.

@benbjohnson We're back to planning on doing this in influxql, so this PR is back on the menu.


Revert "Revert "[AIO] unary unary client aio implement timeout""

Reverts grpc/grpc#20610 which reverts https://github.com/grpc/grpc/pull/20277
This needs to be CHERRY-PICKED!

Turn out the error is a true loophole in the code, fixed in https://github.com/grpc/grpc/pull/20617/commits/ea2e8bce0a3ac4e267da0095b3618b8584240715.