Add anachronisms task

Submission of anachronisms task

I authored all the commits in this pull request but had done so from two separate emails. All commits in this can be associated with the CLA signed by user pwchang with email<EMAIL_ADDRESS>

@googlebot I fixed it.

@googlebot  I fixed it.

Hi @pwchang - I've been assigned as a community reviewer for this task on these criteria.
The task looks good on the criteria ✅
I appreciate how the readme spells out the type of anachronistic and non-anachronistic sentences
Small typo: Westminister -> Westminster
Some examples I was questioning:

The emperor rode his Ferrari to the Coliseum [not anachronism]

I guess this could possible for an emperor in modern times (not the Roman emperor), but this seems to be testing specificity / assumption over the more natural association of the emperor and the Coliseum. By the same logic it could be some other obelisk in Westminster.

William the Conqueror enjoyed plenty of chile peppers to flavor his meals. [not anachronism]
Homo neanderthalensis consumed corn as a main staple of their diet. [anachronism]

I see this is true because chile peppers did exist in the Americas at the time of the 1st example, and corn had not been cultivated at the time of the 2nd example. It just was a little harder to evaluate these.

Hi @mapmeld ,
Thank you for the comments. We are currently reviewing it all as a team and will provide a detailed answer at the beginning of next week. The point about specificity and assumption of association of elements has many layers in its association with anachronisms and we'll try to address all of them.
For some immediate clarification, the obelisk in Westminster example was an anachronism based on the invention of the moto jacket being after the death of Dr. Elizabeth Garrett Anderson. However your comment still raises a good comparison to the emperor/Coliseum example that we will discuss and get back to you on.

Hi @mapmeld,
There is certainly a grey zone when dealing with the specificity and the assumption of association of the entity. Since we are dealing with natural language, there is a component of human interpretation that cannot be entirely removed from the judgement of anachronistic vs not anachronistic. What one person associates with a term is not necessarily the same as what another person might. The statements in this benchmark had to follow a standard that is consistent in spite of these potential differences.
As discussed in the README, we chose to follow a strict definition of anachronism dealing with whether the entities could possibly exist at the same time. We used proper nouns, historical events, or objects with a documented invention date to provide specificity whenever required. Whenever a more general term is used, e.g. "the emperor", it must be assumed to be as temporally broad as possible.
The primary reason for this is that using a standard of the "more natural association" starts to become dependent on cultural norms which we avoided to remove bias from the benchmark. While one person may assume that the statement is referring to the Roman emperor, a person with a different educational or cultural background may not. In fact, Japan still has an emperor (albeit ceremonial) so it is highly reasonable that many people's natural association of the term "the emperor" would be to the Japanese one even if the Coliseum is mentioned.
Likewise, in the case of the obelisk example, the obelisk could indeed refer to any "stone pillar, typically having a square cross section and a pyramidal top, set up as a monument or landmark". However, as mentioned previously, the moto jacket is a strictly modern term which has an invention date after the death of Dr. Elizabeth Garrett Anderson.
We believe that the standard of a term being as temporally broad as possible unless specified further is the most consistent for the purposes of this benchmark. Otherwise the task would be too subject to personal opinions.

In addition to fixing the typo of Westminster, we've edited a few other examples for grammatical or descriptive clarification. The README now also has more detail on descriptive versus relational clauses and uses some new terminology to describe types of anachronisms. Those commits to be coming today.

@chiafullo Accept

@pwchang We are now requesting that task authors please include an explicit section in the README.md file called "data source", listing exactly where you got your data from (or explicitly state that you made it up yourself). Many thanks!

@chiafullo done!

@TalSchuster are one of the assigned reviewers for this task.  Please provide feedback and be sure to notify me with a formal accept or does not meet criteria by Tuesday June 22 (if you have not already done so).

@mapmeld are one of the assigned reviewers for this task.  Please provide feedback and be sure to notify me with a formal accept or does not meet criteria by Tuesday June 22 (if you have not already done so).

Hi, this is a very creative and interesting idea! Sharing my thoughts following the reviewing guidelines:
Review Criteria for Submissions

Correctness: Seems overall good from a few examples I checked. There is some inherent ambiguity in the task, as mentioned in the README. It would be great if you had some inter-annotation agreement score to quantify this.
Formatting:  Works with the colab and looks good and easy to read. I'm only wondering for LM, if it would have been interesting to have this as a text completion task rather than classification. For example: This is an example of an anachronistic sentence: In 1943, the author was knighted by  and then to see if Queen Elizabeth II has higher probabilities than some contemporaneous options. Though, for LTR LMs some examples will have to be rephrased, and also not if comparing the probabilities of a few sampled output options is comprehensive enough as maybe the top predicted option is correct but is not is the predefined examples to examine. So I do appreciate the simplicity of the current classification task 👍
Specificity: I appreciate the explanations in the README. Maybe a few links to references could make it even stronger.
Thoroughness: It's hard to the whole space of non-contemporaneous but I think that this is a very nice collection of examples. Maybe it can be expanded automatically with entity switching but I very much appreciate the manual work here to create diverse examples. Perhaps having contrastive examples would help here for a more thorough evaluation. For example, the template “The author was knighted by __ in 1943” could have two examples one with Queen Elizabeth II and another that is contemporaneous. Or the same with “The author was knighted by Queen Elizabeth II in __”.
Difficulty: Is the result in the README file for GPT-small? I'm curious to know what is the curve for larger models.
Not solvable by memorizing the Internet:  I guess it is... but still you will need to do some basic reasoning and disambiguation.
Novelty:  I think this aspect of commonsense with some world knowledge is also already captured in some other QA tasks, like StrategyQA. Maybe it will help to clarify the difference in the README
Justification: The task is overall well justified and interesting. See previous comments on the README.
Size:  Relatively small but within the limits
Compute resources: ✅

Hi @TalSchuster,
Thanks for the feedback. Sharing our thoughts in response to those in order below:

We agree that having an inter-annotation score would be great but given the time frame we won't be able to set one up to an appropriate standard. We think an inter-annotation score would become more important as the anachronisms start to dive into the "cultural" or "parachronism" categories. However, with "prochronisms", there is less inherent ambiguity in the classification so we think our manual reviewing process should be sufficient for this task. I've added this to the "Limitations and Future Work" section of the README.

Relevant references linked in README.

We considered having contrasting examples for every case but it reduced our flexibility in developing creative statements. Many of our statements used more than 2 entities or relied on descriptive clauses to create the anachronisms so automatic entity switching would be slightly more complicated. We would be happy to go through and develop these for completion but it may be a stretch unless we are able to make edits after the June 21st deadline. It could probably be done but I wouldn't want
to sacrifice correctness in a rush to get it done.

The result in the README came from the evaluate_task script provided in the instructions. All the output says is that it was on GPT2, it doesn't specify which size of GPT2 it was evaluated on.

The StrategyQA reference (Geva, et al, 2021) is a comprehensive strategy to question and answer (QA) systems; of which temporal reasoning is only a part. The approach is more one of identifying what facts need to be decomposed from the question, then how to select a strategy to answer the question from the decomposed facts. Our benchmark would ultimately be used to test systems that have a temporal strategy to resolve the decomposed facts (see Table 6 in the reference). On top of question-answer systems, our task would also support development of temporal reasoning in tasks such as multi-document summarization (Otterbacher, et al, 2002; https://www.aclweb.org/anthology/W02-0404/) and information extraction and event attribution (Popescu and Strapparava, 2015 ;https://www.aclweb.org/anthology/S15-2147/). This distinction has been added to the Motivation section of the README.

Hi @pwchang, Thank you for your answer.
Regarding adding contrastive examples, I appreciate your enthusiasm to add contrastive examples. In my opinion it will make the evaluation more reliable as it can help identify "right classifications for the wrong reason". I don't know about the post-deadline modifications (I'm just an assigned reviewer providing feedback...) maybe @chiafullo can help with that

@chiafullo Accept

The amount of tasks we received this round is tremendous.  With so many tasks to review we have decided to extend the review period to Tuesday, June 29.
Reviewers: if the submitter has made revisions please be sure to notify me with a formal ”accept” or ”does not meet criteria” by Tuesday, June 29  (if you haven't already done so).
this is an automated message

Hi @TalSchuster and @mapmeld,
We just pushed all the contrasting statements for each example. If a second approval is needed for this revision as noted by chiafullo above then feel free to review again as all substantial changes have been completed.

Your task has been accepted in the initial review stage.  The next stage of this process is for us to assign your task a meta-reviewer for final review and merge.  An assigned meta-reviewer will follow-up by commenting on the PR should it need further revisions.

Hello, I’m the meta-reviewer for this task. Here’s my feedback with respect to our review criteria:
Overall
I think this is a strong task that the authors have taken great care to explain and design. The README is quite thorough and explains the design considerations well and lays out the task justification and background thoroughly. The reviewers also did a great job and the authors were very responsive. As a result I have little to add and will merge this task right away.
Correctness
The task is correct and passes the tests.
Specificity
The task is very specific and focused.
Thoroughness
The task is thorough and has a good number of hand-crafted examples, and the authors have given a lot of thought to ensure each example is correct.
Difficulty
The task seems well-matched difficulty-wise to the benchmark and current large models.
Not Solvable by Memorizing the Internet
This task does not seem solvable via memorization of internet data.
Novelty
This task seems novel with little overlap with other BIG-bench tasks.
Justification
This task is well described and the authors lay out their justification very well in the README.
Compute Resources
This task has no compute issues.
Data Sources and Licensing
The authors created each of the examples, so no issues here.


HTTP Error 502.5 - Process Failure - 2.0.0 Deployment in Azure Web App with 2.0.3 Runtime

As @davidebbo stated in #406 I create a new Issue here for my Problem with 2.0.0 deployment on 2.0.3 Azure Web App.
My 2.0.0 deployment broke when the .net Core Runtime of my Azure Web App was updated to 2.0.3.
A HTTP Error 502.5 - Process Failure was displayed.
The app that was running suddenly broke with no deployments.
I then tried to redeploy my 2.0.0 App but the error stayed.
After I updated my locally installed .net Core SDK to 2.0.3 and redeployed, it was working again.
I still have a 2.0.0 Deployment on another instance (http://sto-update-test.azurewebsites.net/), there you can still see the error.
Message from Application Events:
Application 'MACHINE/WEBROOT/APPHOST/STO-UPDATE-TEST__A4C5' with physical root 'D:\home\site\wwwroot\' failed to start process with commandline 'dotnet .\MyApp.dll', ErrorCode = '0x80004005 : 8000808c.
Message from KUDU Debug Console:
D:\home\site\wwwroot>dotnet .\MyApp.dll
Error:
  An assembly specified in the application dependencies manifest (MyApp.deps.json) was not found:
    package: 'Microsoft.ApplicationInsights.AspNetCore', version: '2.1.0-beta6'
    path: 'lib/netstandard1.6/Microsoft.ApplicationInsights.AspNetCore.dll'

  This assembly was expected to be in the local runtime store as the application was published using the following target manifest files:
    aspnetcore-store-2.0.0-preview2-25794-linux-x64.xml;aspnetcore-store-2.0.0-preview2-25794-osx-x64.xml;aspnetcore-store-2.0.0-preview2-25794-win7-x64.xml;aspnetcore-store-2.0.0-preview2-25794-win7-x86.xml;aspnetcore-store-2.0.0-preview2-final-linux-x64.xml;aspnetcore-store-2.0.0-preview2-final-osx-x64.xml;aspnetcore-store-2.0.0-preview2-final-win7-x64.xml;aspnetcore-store-2.0.0-preview2-final-win7-x86.xml

PS: The real Application Name above was replaced with "MyApp"

Was this targeting 2.0.0 or 2.0.0-preview2 as implied by the manifest errors?
Can you share your deps.json?

It looks like it's targeting 2.0.0, but has references to pre-release assemblies which only existed in the pre-release runtime store. So it got broken when 2,0 prerelease was removed from App Service, and not because 2.0.3 was deployed.
So I think this is by design.

I think this explains it.
Thank you. Can be closed.


PLANNER-284: Ability to report multiple scores from a single rule

This is PR is not ready to merge (yet).
The tests and BendableBigDecimalScoreHolder should be ready.
The fix currently makes use of constraintMatchTotalMap therefore only works in an environment where constraint matching is enabled.

Currently, I see no way to get around this than to use the map always, or create another one that will be used to map which of the score levels are we using right now (and therefore if we should unmatch the AgendaItem).

Please check the tests behave like they should (especially the assertEquals(N, scoreHolder.getConstraintMatchTotals().size()) assertion)

I 've done some general benchmark comparisons and it seems there's be a performance degradation - I am going to take my time to do some experiments to see if there's a way around it, if it doesn't make CR2, so be it (I 'll adjust the jira accordingly).

@ge0ffrey ok, also, don't forget to adjust the release notes.

Merged manually, thanks! :)


riscv support

this adds riscV support to OpenFHE. This has been fully tested on a HiFive Unmatched from SiFive running Ubuntu 22.04.1 LTS, g++ 11.2.0.
@dsuponitskiy , I've coordinated this with @yspolyakov since it cannot be tested in our CI pipeline (for riscV operation).

Also please squash the commit history as you see fit. -- I am not used to this interface (been in Gitlab for years)


Added New Relic APM client to the Php-FPM container

Added the New Relic APM client install to the Php-FPM container with three new config variables in the .env file and examples of setting the site name in the nginx site file examples.
#1155
I completed the 3 steps below:

[x] I've read the Contribution Guide.
[x] I've updated the documentation. (refer to this for how to do so).

Two things to note, one i had to move the swoole install in the workspace to the bottom after the PHP version check else i was experiencing segmentation faults in other packages installs if it happened before them.
Second I removed the pdo install from the php-worker as this was causing a build error when building under PHP 7.0 and gets installed anyway with the pdo_mysql and pdo_pgsql, unless im wrong on that and some one give me a shout if that is the case.

Going to close this ticket and reopen a new one as I have noticed that i forgot to do this in a separate branch, my bad.


Video and iframe (others maybe) don't lazyload, need to create a new instance with a added class

Tested on chrome and firefox (latest versions).
i have img, video and iframe with data-src.
latest version of lazyloadjs.
after dom is loaded:
//lazyload
var myLazyLoad = new LazyLoad();
//videos and iframe
var myLazyLoad2 = new LazyLoad({
  elements_selector: ".lazy"
});

all images load fine but for videos and iframe i need to add the class .lazy and create a instance catching the .lazy class, otherwise then won't load.
images work if i add the lazy class. but would expect it would work without the class added.

That is the expected behavior since the default value for the elements_selector is img as you can read in the API section of the documentation (readme file).
You can have a single LazyLoad instance passing .lazy as value and using the lazy class on the images too.

i understood that later, i keep the impression that it would parse all the data-src, and change accordingly to the element wrapper.
But you are right, using the class is the better option. thanks for the feedback.


Make a end to end quick start using docker

The problem faced currently?
The current steps require the user to follow several steps in order to get a sample app running.
How can we solve it?
Maybe we can make a getting started guide using docker compose. We can do something like this: https://github.com/MichaelLeeHobbs/space-dock

If you want this feature to be implemented, give it a thumbs up reaction, so that we can determine which features are important to you.
👍

Resolved in v0.11.0 by introducing a quick start based on the explorer in mission-control


test for signout event timing bug

https://github.com/hoodiehq/camp/issues/9

This PR only prepares a test for https://github.com/hoodiehq/camp/issues/9, as Daniel is still new to JavaScript, this will help him focusing on finding and fixing the issue. We can get to creating tests later :)
I'll give this a LGTM myself, I guess that makes sense for a PR like this?
ping @hoodiehq/maintainers 👀 ❤

LGTM :+1: 🚀


Make visibility configurable

At the moment a flavor is public by default. It should be possible to also manage private flavors to be able to use the https://github.com/osism/openstack-project-manager/issues/188 feature. Add a new (optional) key visibility with private/public as possible values. The value should be public by default to not change the default behavior.

Should alraedy be possible with the public attribute
https://github.com/osism/openstack-flavor-manager/blob/8db41db649b51abcd0e123373c290b280066b61c/openstack_flavor_manager/main.py#L64-L66


google colab crashed after run tensofrflow code which is upgraded from 1.8 to 2.2

I subscribed in colab pro and I have enough RAM but the code crashes the colab after upgrade it from TF1.8 to TF 2.2, how to solve this problem

@RokiaAbdeen
Can you please share the colab link you are referring to reproduce the issue in our environment.It helps us in localizing the issue faster. Thanks!


checksum value is ignored when binary download url is not set

Cookbook version
5.0.0
Chef-client version
13.6.4
Platform Details
Centos 7.4
Scenario:
I noticed that if you don't set the default['nodejs']['binary']['url'] attribute value then the checksum value is ignored.
Steps to Reproduce:
use the following attributes and values -
node.override['nodejs']['install_method'] = 'binary'
node.override['nodejs']['version'] = '8.7.3'

Expected Result:
Notice that i did not set node['nodejs']['binary']['checksum']['linux_x64'] value, so technically kitchen converge should fail because it would use the default checksum value but not the checksum value for node-v8.11.1-sunos-x64.tar.gz.
Actual Result:
kitechen converge succeeds.

I've found a similar issue today in version 7.3.1 and Chef client 15.15.1 on an Ubuntu 18.04 box with the following:
attributes.rb
default['nodejs']['version'] = '14.15.5'
default['nodejs']['install_method'] = 'binary'
default['nodejs']['binary']['checksum'] = 'gatomon'
default['nodejs']['packages'] = %w(nodejs)

recipe.rb
apt_update 'all'
include_recipe 'nodejs'

The output being:
Recipe: example_projects::recipe
 * apt_update[all] action periodic
   - update new lists of packages
   * directory[/var/lib/apt/periodic] action create (up to date)
   * directory[/etc/apt/apt.conf.d] action create (up to date)
   * file[/etc/apt/apt.conf.d/15update-stamp] action create_if_missing
     - create new file /etc/apt/apt.conf.d/15update-stamp
     - update content in file /etc/apt/apt.conf.d/15update-stamp from none to 174cdb
     --- /etc/apt/apt.conf.d/15update-stamp	2021-02-19 13:59:15.182576333 +0000
     +++ /etc/apt/apt.conf.d/.chef-15update-stamp20210219-2030-1jz7b7i	2021-02-19 13:59:15.182576333 +0000
     @@ -1 +1,2 @@
     +APT::Update::Post-Invoke-Success {"touch /var/lib/apt/periodic/update-success-stamp 2>/dev/null || true";};
   * execute[apt-get -q update] action run
     - execute ["apt-get", "-q", "update"]

Recipe: nodejs::nodejs_from_binary
 * ark[nodejs-binary] action install
   * directory[/usr/local/nodejs-binary-14.15.5] action create
     - create new directory /usr/local/nodejs-binary-14.15.5
   * remote_file[/tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz] action create
     - create new file /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz
     - update content in file /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz from none to e30c1f
     (file sizes exceed 10000000 bytes, diff output suppressed)
   * execute[unpack /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz] action nothing (skipped due to action :nothing)
   * execute[set owner on /usr/local/nodejs-binary-14.15.5] action nothing (skipped due to action :nothing)
   * link[/usr/local/bin/node] action create
     - create symlink at /usr/local/bin/node to /usr/local/nodejs-binary-14.15.5/bin/node
   * link[/usr/local/bin/npm] action create
     - create symlink at /usr/local/bin/npm to /usr/local/nodejs-binary-14.15.5/bin/npm
   * link[/usr/local/bin/npx] action create
     - create symlink at /usr/local/bin/npx to /usr/local/nodejs-binary-14.15.5/bin/npx
   * link[/usr/local/nodejs-binary] action create
     - create symlink at /usr/local/nodejs-binary to /usr/local/nodejs-binary-14.15.5
   * template[/etc/profile.d/nodejs-binary.sh] action create
     - create new file /etc/profile.d/nodejs-binary.sh
     - update content in file /etc/profile.d/nodejs-binary.sh from none to c7b5d7
     --- /etc/profile.d/nodejs-binary.sh	2021-02-19 13:59:21.785876094 +0000
     +++ /etc/profile.d/.chef-nodejs-binary20210219-2030-1b695sr.sh	2021-02-19 13:59:21.785876094 +0000
     @@ -1 +1,2 @@
     +export PATH=/usr/local/nodejs-binary-14.15.5/bin:$PATH
     - change mode from '' to '0755'
     - change owner from '' to 'root'
     - change group from '' to 'root'
   * ruby_block[adding '/usr/local/nodejs-binary-14.15.5/bin' to chef-client ENV['PATH']] action run
     - execute the ruby block adding '/usr/local/nodejs-binary-14.15.5/bin' to chef-client ENV['PATH']
   * execute[unpack /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz] action run
     - execute /bin/tar xzf /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz --strip-components=1
   * execute[set owner on /usr/local/nodejs-binary-14.15.5] action run
     - execute chown -R root:0 /usr/local/nodejs-binary-14.15.5

Running handlers:
Running handlers complete

Ironically, if you destroy the kitchen suite, and then remove this line from the attributes:
default['nodejs']['binary']['checksum'] = 'gatomon'

and run converge again, the recipe crashes and shows a checksum mismatch error:
       Recipe: nodejs::nodejs_from_binary
         * ark[nodejs-binary] action install
           * directory[/usr/local/nodejs-binary-14.15.5] action create
             - create new directory /usr/local/nodejs-binary-14.15.5
           * remote_file[/tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz] action create

             ================================================================================
             Error executing action `create` on resource 'remote_file[/tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz]'
             ================================================================================

             Chef::Exceptions::ChecksumMismatch
             ----------------------------------
             Checksum on resource (2f0397) does not match checksum on content (e30c1f)

             Resource Declaration:
             ---------------------
             # In /tmp/kitchen/cache/cookbooks/ark/resources/default.rb

       62:   remote_file new_resource.release_file do
       63:     Chef::Log.debug('DEBUG: new_resource.release_file')
       64:     source new_resource.url
       65:     checksum new_resource.checksum if new_resource.checksum
       66:     action :create
       67:     notifies :run, "execute[unpack #{new_resource.release_file}]"
       68:     backup new_resource.backup
       69:   end
       70:

             Compiled Resource:
             ------------------
             # Declared in /tmp/kitchen/cache/cookbooks/ark/resources/default.rb:62:in `block in class_from_file'

             remote_file("/tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz") do
        action [:create]
        default_guard_interpreter :default
        source ["https://nodejs.org/dist/v14.15.5/node-v14.15.5-linux-x64.tar.gz"]
        declared_type :remote_file
        cookbook_name "nodejs"
        checksum "2f0397bb81c1d0c9901b9aff82a933257bf60f3992227b86107111a75b9030d9"
        backup 5
        remote_domain nil
        remote_user nil
        path "/tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz"
        owner nil
        group nil
        headers {}
        mode nil
        verifications []
             end

             System Info:
             ------------
             chef_version=15.15.1
             platform=ubuntu
             platform_version=18.04
             ruby=ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-linux]
             program_name=/opt/chef/bin/chef-client
             executable=/opt/chef/bin/chef-client

           * execute[unpack /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz] action run

             ================================================================================
             Error executing action `run` on resource 'execute[unpack /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz]'
             ================================================================================

             Mixlib::ShellOut::ShellCommandFailed
             ------------------------------------
             Expected process to exit with [0], but received '2'
             ---- Begin output of /bin/tar xzf /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz --strip-components=1 ----
             STDOUT:
             STDERR: tar (child): /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz: Cannot open: No such file or directory
             tar (child): Error is not recoverable: exiting now
             /bin/tar: Child returned status 2
             /bin/tar: Error is not recoverable: exiting now
             ---- End output of /bin/tar xzf /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz --strip-components=1 ----
             Ran /bin/tar xzf /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz --strip-components=1 returned 2

             Resource Declaration:
             ---------------------
             # In /tmp/kitchen/cache/cookbooks/ark/resources/default.rb

       72:   execute "unpack #{new_resource.release_file}" do
       73:     command unpack_command
       74:     cwd new_resource.path
       75:     environment new_resource.environment
       76:     notifies :run, "execute[set owner on #{new_resource.path}]"
       77:     action :nothing
       78:   end
       79:

             Compiled Resource:
             ------------------
             # Declared in /tmp/kitchen/cache/cookbooks/ark/resources/default.rb:72:in `block in class_from_file'

             execute("unpack /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz") do
        action [:nothing]
        default_guard_interpreter :execute
        command "/bin/tar xzf /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz --strip-components=1"
        backup 5
        declared_type :execute
        cookbook_name "nodejs"
        domain nil
        user nil
        cwd "/usr/local/nodejs-binary-14.15.5"
        environment {}
             end

             System Info:
             ------------
             chef_version=15.15.1
             platform=ubuntu
             platform_version=18.04
             ruby=ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-linux]
             program_name=/opt/chef/bin/chef-client
             executable=/opt/chef/bin/chef-client

           ================================================================================
           Error executing action `install` on resource 'ark[nodejs-binary]'
           ================================================================================

           Chef::Exceptions::MultipleFailures
           ----------------------------------
           Multiple failures occurred:
           * Chef::Exceptions::ChecksumMismatch occurred in Chef Infra Client run: remote_file[/tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz] (/tmp/kitchen/cache/cookbooks/ark/resources/default.rb line 62) had an error: Chef::Exceptions::ChecksumMismatch: Checksum on resource (2f0397) does not match checksum on content (e30c1f)
           * Mixlib::ShellOut::ShellCommandFailed occurred in delayed notification: execute[unpack /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz] (/tmp/kitchen/cache/cookbooks/ark/resources/default.rb line 72) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '2'
           ---- Begin output of /bin/tar xzf /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz --strip-components=1 ----
           STDOUT:
           STDERR: tar (child): /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz: Cannot open: No such file or directory
           tar (child): Error is not recoverable: exiting now
           /bin/tar: Child returned status 2
           /bin/tar: Error is not recoverable: exiting now
           ---- End output of /bin/tar xzf /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz --strip-components=1 ----
           Ran /bin/tar xzf /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz --strip-components=1 returned 2

           Resource Declaration:
           ---------------------
           # In /tmp/kitchen/cache/cookbooks/nodejs/recipes/nodejs_from_binary.rb

            60: ark archive_name do
            61:   url nodejs_bin_url
            62:   version node['nodejs']['version']
            63:   checksum checksum
            64:   has_binaries binaries
            65:   append_env_path node['nodejs']['binary']['append_env_path']
            66:   action :install
            67: end

           Compiled Resource:
           ------------------
           # Declared in /tmp/kitchen/cache/cookbooks/nodejs/recipes/nodejs_from_binary.rb:60:in `from_file'

           ark("nodejs-binary") do
             action [:install]
             updated true
             updated_by_last_action true
             default_guard_interpreter :default
             declared_type :ark
             cookbook_name "nodejs"
             recipe_name "nodejs_from_binary"
             url "https://nodejs.org/dist/v14.15.5/node-v14.15.5-linux-x64.tar.gz"
             version "14.15.5"
             checksum "2f0397bb81c1d0c9901b9aff82a933257bf60f3992227b86107111a75b9030d9"
             has_binaries ["bin/node", "bin/npm", "bin/npx"]
             append_env_path true
             extension "tar.gz"
             prefix_bin "/usr/local/bin"
             prefix_root "/usr/local"
             home_dir "/usr/local/nodejs-binary"
             owner "root"
             path "/usr/local/nodejs-binary-14.15.5"
             release_file "/tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz"
           end

           System Info:
           ------------
           chef_version=15.15.1
           platform=ubuntu
           platform_version=18.04
           ruby=ruby 2.6.6p146 (2020-03-31 revision 67876) [x86_64-linux]
           program_name=/opt/chef/bin/chef-client
           executable=/opt/chef/bin/chef-client

       Running handlers:
       [2021-02-19T14:02:50+00:00] ERROR: Running exception handlers
       Running handlers complete
       [2021-02-19T14:02:50+00:00] ERROR: Exception handlers complete
       Chef Infra Client failed. 4 resources updated in 18 seconds
       [2021-02-19T14:02:50+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
       [2021-02-19T14:02:50+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
       [2021-02-19T14:02:50+00:00] FATAL: Chef::Exceptions::MultipleFailures: Multiple failures occurred:
       * Chef::Exceptions::ChecksumMismatch occurred in Chef Infra Client run: remote_file[/tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz] (/tmp/kitchen/cache/cookbooks/ark/resources/default.rb line 62) had an error: Chef::Exceptions::ChecksumMismatch: Checksum on resource (2f0397) does not match checksum on content (e30c1f)
       * Mixlib::ShellOut::ShellCommandFailed occurred in delayed notification: execute[unpack /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz] (/tmp/kitchen/cache/cookbooks/ark/resources/default.rb line 72) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '2'
       ---- Begin output of /bin/tar xzf /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz --strip-components=1 ----
       STDOUT:
       STDERR: tar (child): /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz: Cannot open: No such file or directory
       tar (child): Error is not recoverable: exiting now
       /bin/tar: Child returned status 2
       /bin/tar: Error is not recoverable: exiting now
       ---- End output of /bin/tar xzf /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz --strip-components=1 ----
       Ran /bin/tar xzf /tmp/kitchen/cache/nodejs-binary-14.15.5.tar.gz --strip-components=1 returned 2


Empty commit to configure license/cla

There needs to be at least one PR for license/cla to be listed as one of the checks that can be marked as required.

All set!


Add vault.png new image

The previous image size was 250x250 - i changed it to 500x500
Let me know if this is ok to change , thanks!

This is just above 200 KB. It's best to try to keep it smaller than that. I would instead recommend focusing on removing the padding so the visuals take up the entire canvas.

Changed the padding

Please resolve conflicts


adds go mod support and upgrades dependencies to latest

This does not use sqlboiler v4 (the module-aware version) or the null v8 package (also module aware) :(

updated

Thank you


Update renovate

related: #285
this PR sets a schedule and limitations for renovate:

run only weekends
and create only 5 PRs at a time

these settings are up for discussion so feel free to recommend/suggest a better configuration

merging this so we can slow down all the renovate PRs but we should have discuss on what is a good set of configuration

It's fine with me now that there are so many outdated dependencies. But when everything is more or less up to date I think we could remove these restrictions.

It's fine with me now that there are so many outdated dependencies. But when everything is more or less up to date I think we could remove these restrictions.

yeah, we can definitely reset it once we've worked through all the current dependencies and get to a manageable status


Setup readthedocs api doc

https://github.com/10sr/webtools/issues/27

https://qiita.com/koreyou/items/00f5820591ec9196ef07


Because rust and cargo need to be installed in advance, there will be some extra work, it is recommended to install the rust and cargo in the loader when npm install, to reduce the cognitive cost

Because rust and cargo need to be installed in advance, there will be some extra work, it is recommended to install the rust and cargo in the loader when npm install, to reduce the cognitive cost

Hey!
The actual rust environment actually depends from machine to machine, so after a dozen of internal testing, I decided to not include an automatic rust install when loader is installed/downloaded.
I did an update of README though, it should be much clearer, what should be installed on.
If you guys have other opinions about this issue, feel free to re-open!


Music app with a analyser

Music-app with analyser #843
Close #<843>
close issue no- #843
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md

wrong commits

.


Release Definition 'Publish Build Artifacts' fails

Environment
TFS on-premises, provide the version: Version 16.131.28106.2

Agent Private:

If using private agent, provide the OS of the machine running the agent and the agent version:
Windows 10, Visual Studio Professional 15.8, Agent.Version | 2.122.1

Issue Description
Release Definition 'Publish Build Artifacts' keeps failing
When published to shared folder:
2018-10-26T15:07:44.1432264Z ##[error]Unable to process command '##vso[artifact.associate artifacttype=filepath;artifactname=TestRelease_Release-15;artifactlocation=\\cmpny\data;]\\cmpny\data' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)
2018-10-26T15:07:44.1432264Z ##[error]Value cannot be null.
Parameter name: buildId
2018-10-26T15:07:44.1901114Z ##[debug]System.ArgumentNullException: Value cannot be null.
Parameter name: buildId
   at Microsoft.VisualStudio.Services.Agent.Worker.Build.ArtifactCommandExtension.ProcessArtifactAssociateCommand(IExecutionContext context, Dictionary`2 eventProperties, String data)
   at Microsoft.VisualStudio.Services.Agent.Worker.WorkerCommandManager.TryProcessCommand(IExecutionContext context, String input)

When published to TFS:
2018-10-26T15:05:22.4400661Z ##[error]This task must run in a build to publish artifacts to Visual Studio Team Services/TFS.
Release Definition Provided
I have attached the exported json file from the release definition. Although I have removed/replace sensitive information. So you may need to patch it properly before importing. It is in txt format as github won't allow json upload.
I am new to TFS and hence might lack the understanding as to how the release definition works.
Is there a different mechanism to publish released items ideally to TFS (and not file share) ?
TestRelease.txt

The task 'Publish Artifact' can only run in a build process. You create Artifacts that are attached to the build. In your release the artifacts from the underlying are downloaded automatically. you can than use tasks like 'copy' etc to deploy the artifacts to where you want them to be

Does it mean we cannot have artifact (viz. released MSI) on the release task 'to be downloaded on click' on TFS?

You can, you just used the wrong task in the wrong context. A Release-Definition deploys the artifacts of a build-definition. You are  creating a file in release-definition and try to publish it as artifact. The last part is supposed to run in a build-process. replace this with a copy-task to copy the file or artifact

One last thing to clarify before we close this issue.
The copy-task, you mean copy it to somewhere on a folder/network and not be an artifact on the Release? Or copy where?
I understand that publish build artifact shouldn't be on a release definition. Thanks for your reply.

Copy it to somewhere on a folder/network.
If you want it to be an artifact you need to create it in a build, publish as artifact and then copy that artifact to a folder/network.
Pls checkout the concepts/guids here -> https://docs.microsoft.com/en-us/azure/devops/pipelines/release/artifacts?view=vsts#sources

Thanks a lot @JohannesDrexler


react-native-web implementation of AsyncStorage

Should the react-native-web implementation of AsyncStorage also reside in this community library?
When changing to @react-native-community/async-storage the web version of my React Native app fails on multiMerge
I believe it would be a simple copy paste of the localStorage code here: https://github.com/necolas/react-native-web/blob/master/packages/react-native-web/src/exports/AsyncStorage/index.js
And it appears the react-native-web maintainers agree with the functionality residing in this library - https://github.com/necolas/react-native-web/issues/1260
Thank you.

Thanks @cohawk for pointing this out!
I'm moving discussion over there, if you think it'd be nice to continue here, let me know.
thanks.

Please continue the discussion here and lift any code from RNW that is necessary.

@krizzu Please reopen this issue

This is the last commit in React Native for Web that will include AsyncStorage - https://github.com/necolas/react-native-web/tree/33dc3cb01869cde556387e1cbc4e43323015b5b7/packages/react-native-web/src/exports/AsyncStorage

Reopening the issue to continue to talk about making Web support first-class citizen in this repo. Currently working on implementing core of AS v2, and soon going to start on adding Storages.

I see the coding work on v2 has started but apparently became stale. So how should one proceed to add web support to this repo? Master branch? Legacy?

@brunolemos Once #186 is done, I think it'd be a good start to add web support.

@Krizzu if you would like help with adding web support, please let me know. I use RNW with AsyncStorage and am holding off on upgrading.

I know it took some time but - I'm open for help with Web storage. If you're interested, please respond to this issue.
I've prepared a basic scaffold that work can be best on. Checkout to master branch and see packages/storage-web package.
Some todo list:

Follow instructions to create a storage backend
Make it compatible with both localStorage and sessionStorage (add an option to select one to use, when creating an instance of this storage)
Add unit tests
Update Readme

I'm going to help whoever takes this one.
Thanks a lot in advance!

I am interested. I will try and get started on it sometime this week.

Hey @Krizzu ! I got localStorage and sessionStorage working. I wanted to let you take a look before I go any further. I didn't write any tests yet and I am not used to working with TypeScript, so I may not have done it correctly. Please let me know if I am on the right track when you get a chance! https://github.com/JesseRWeigel/async-storage/blob/web-storage/packages/storage-web/src/index.ts

@JesseRWeigel Great, please create PR so we can discuss it there

Hi, I am not able to upgrade to react-native-web 0.12.0 because of AsyncStorage support removed. I use it for native, on  the web I use the localStorage. How can I perform my upgrade without breaking native? Thanks!

For those upgrading to react-native-web 0.12.0 but blocked by this, here is my solution:

save the last version of AsyncStorage file to your project from<EMAIL_ADDRESS>alias AsyncStorage import to your local file. I'm using webpack:

resolve: {
  alias: {
    'react-native$': 'react-native-web',
    '@react-native-community/async-storage': path.resolve(__dirname, './AsyncStorage.web.js'),
  },
  ...
}

I am afraid this won't work with expo because expo is using metro not webpack (If I am correct).
I use AsyncStorage in native and localStorage on the web =/

That's not correct. Expo uses web pack for web builds. See the
@expo/webpack-config npm package
On Sat, Feb 8, 2020, 10:15 AM Dimitri KOPRIWA<EMAIL_ADDRESS>wrote:

I am afraid this won't work with expo because expo is using metro not
webpack (If I am correct).
I use AsyncStorage in native and localStorage on the web =/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/react-native-community/async-storage/issues/52?email_source=notifications&email_token=AACKD6I7QYTBBR4DXIVZNR3RB3LDRA5CNFSM4HCOCTHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELFVLAA#issuecomment-583751040,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKD6KLCJGOHK2BB6ZUXMDRB3LDRANCNFSM4HCOCTHA
.

@kopax AsyncStorage from react-native-web is using localStorage underhood

That's not correct. Expo uses web pack for web builds. See the @expo/webpack-config npm package

I am not concerned about the web but the natives ios and android application. Do they also use webpack in development? Isn't it metro supposed to build the react native application?

@kopax AsyncStorage from react-native-web is using localStorage underhood, it just wraps it with the same api as native AsyncStorage

Glad to know and thanks, but I am concerned about the IOS/Android application.

@wong2, I have test to fix my issue using:
config.resolve.alias['react-native-web/dist/exports/AsyncStorage'] = resolve(__dirname, './AsyncStorage.web.js');

I stil have this error:
Module not found: Can't resolve 'react-native-web/dist/exports/AsyncStorage' in '/home/dka/workspace/test-native/node_modules/expo/build/Notifications'

@kopax how do you import AsyncStorage in your code?

@wong2 it is not in my code, it is in expo source code:
https://github.com/expo/expo/blob/e65bceb325baf9a70ecea0cacfb117969134c89d/packages/expo/src/Notifications/Notifications.ts#L4

@kopax sorry I'm not sure how to do that with expo

Me neither, I guess I am stuck with react-native-web 0.11, too bad I was actively waiting for the useNativeDriver fix :(

What about not Expo projects? I have "NativeModule: AsyncStorage" error too.
"@react-native-community/async-storage": "^1.12.0",
"react-native-web": "^0.13.14"


Chrome Perf Issue / Long Running Tasks

device: Nexus 5
browser : Chrome Beta 50.0.2661.49
Description:
On an Android device running Chrome when you open any image lightbox you get met - randomly - with this in the console:
Deferred long-running timer task(s) to improve scrolling smoothness. See crbug.com/574343

here is the reference bug:  https://bugs.chromium.org/p/chromium/issues/detail?id=574343
Example URL:  https://feimosi.github.io/baguetteBox.js/
Example URL Data:
here is the timeline data from chrome -sorry for the dropbox link the file is rather large :(

https://dl.dropboxusercontent.com/u/19395935/TimelineRawData-baguetteBox-20160330T112520.json

Possible Fixes:
This can be fixed by replacing setTimeout in the script with requestAnimationFrame.
rough example:
requestAnimationFrame(function() {
  overlay.className = 'visible';
  if(options.afterShow)
    options.afterShow();
});

This though might cause other issues.

Browser Support is IE10 + and Android Browser 4.4+

then again 2.0 is looking to drop ie < 11 https://github.com/feimosi/baguetteBox.js/issues/57

If you do go the RAF route a polyfill could make the script larger than you wish.

Possible Fix Results:
here is the timeline data from replacing the following setTimeouts with requestAnimationFrame

https://github.com/feimosi/baguetteBox.js/blob/master/src/baguetteBox.js#L322
https://github.com/feimosi/baguetteBox.js/blob/master/src/baguetteBox.js#L358
https://github.com/feimosi/baguetteBox.js/blob/master/src/baguetteBox.js#L453
https://github.com/feimosi/baguetteBox.js/blob/master/src/baguetteBox.js#L474
https://github.com/feimosi/baguetteBox.js/blob/master/src/baguetteBox.js#L488

and the timeline data ... again sorry about the DropBox link its a big file haha.

https://dl.dropboxusercontent.com/u/19395935/TimelineRawData-baguetteRAF-20160330T114254.json

you can load the data in Chrome Devtools under Timeline > right click load Timeline data. Then you can filter the Event Data with "timer Fired" to get all the set timeout calls exceeding 50 milliseconds. Newer and/or more powerfull phones may not run into this and things may change in Chrome. This also may not be the appropriate "fix". I just wanted to make you aware!

Thanks for pointing that out! Actually, I had no idea about it.
requestAnimationFrame sounds like a good solution. For sure it's suitable for the milestone 2.0


0.14 RC1 support

Can you add support for React 0.14 RC 1?

+1

+1
Getting a warning because fixed-data-table uses React.findDOMNode instead of ReactDOM.findDOMNode :(

+1

+1

+1

+1

+1

I have done a quick release with @chentsulin's PR to allow<EMAIL_ADDRESS>as a dep (https://github.com/facebook/fixed-data-table/releases/tag/v0.4.7) and will try to do another release shortly to clean up the warnings.

+1
this is causing that npm breaks too
npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS><0.15.0 || ^0.14.0-beta3

Yup getting the same npm error as @eriknyk
+1 for v0.14 support

+1

Thank you! https://github.com/facebook/fixed-data-table/releases/tag/v0.5.0

I have 0.5 installed, but am still getting the warning about using React instead of ReactDOM.

I see this issue is still open.  My CI Build is failing on peer deps because we're using React 15.  Will there be an update for this?


The new constructor/method call syntax

Imagine that a method call doesn't consist of a method name and a list of its arguments. On the contrary, it looks more like a natural language sentence, is more agile and readable, but still well structured. Does it sound interesting?
In order to get closer to this idea, I like to use named arguments, i.e match(text='abcd', regex='\w+') instead of match('abcd', '\w+'). Particularly, it makes a lot of sense in case of deeply nested constructions, where an order of method arguments gets non-obvious and simply unshapely because of a cumbersome structure:
match(
  stripped_text(
    file(
      file_path(
        ['tmp', 'xxx.txt']
      ),
      'r'
    )
  ),
  '10$'
)

Here, one wouldn't so easily understand, what's going on. Really, what do these 'r' and '10$' mean? They are already out of context. Here, named arguments would come in very handy.
Let's get back to the first example: match(text='abcd', regex='\w+') vs match('abcd', '\w+'). The need to use named arguments here is much more controversial. They are still useful in case one mixes up an order of arguments, but make the code twice as verbose.
What would be the compromise?
I suggest to make argument naming required and eliminate the difference between a method name and argument names.
Simply put, I'd change match('w+', 'abcd') to match: '\w+' text: 'abcd'. Makes sense?
Take a look at our current code outline:
create fibonacci(1) as Number:
  Number n
  bytes asBytes():
    if:
      lessThan: @n, 2
      1,
      plus:
        @n
        fibonacci:
          minus: @n, 1

Indeed, as we got rid of the brackets, it isn't verbose at all. But the readability suffers just like in the example above. I believe, if the if had more code inside, it wouldn't be readable anymore.
What about something like this?
create fibonacci(1) as Number:
  Number n
  bytes asBytes():
    if:
      less: @n than: 2
    then:
      1
    else:
      plus:
        @n
      and:
        fibonacci:
            minus: @n and: 1

Here, the if isn't a constructor with 3 unnamed arguments anymore. It has two named arguments: good old then and else are back in the game, but now in an object oriented way!
What do you think?

I like the general idea and reasoning for your change (I find some of this stuff not as readable as I might like) but the fact that, in the new idea, if: is an object and then: is the name of an argument (even thought they look identical) is not at all obvious and so it seems confusing.

@gukoff yeah, I agree with @pa9ey It does look more similar to the good old Java, but it's not OOP any more. We have to make if an object with 3 arguments. In your example we have if, then and else -- three objects.
Also, keep in mind that long methods is a bad idea in the first place. They will have to be short in order to be readable. It's like in Lisp -- long structures are not readable and developers avoid them.

the fact that, in the new idea, if: is an object and then: is the name of an argument (even thought they look identical) is not at all obvious and so it seems confusing.

@pa9ey well, it's all about their order. The first one is a main thing being called, the others mean some additional information. Yes, it is pretty unusual and isn't obvious at first glance. But I got used to it very quickly, while writing this issue :)

We have to make if an object with 3 arguments

@yegor256 yup, and these arguments have to be objects.

In your example we have if, then and else -- three objects.

Hmm. What do you mean? if is some standard library object here, and then and else are just the names of its constructor parameters. The new constructor accepts three objects, and so it does in our current example as well.

Actually, I was talking primarily about constructors. A method call would look like this:
filesystem file: '/tmp/x.txt' mode: 'r'

Or, the more complex example:
filesystem
    file:
        stripped: '__new_name.txt__' by_symbol: '_'
    mode:
        if:
            filesystem writable
        then: 'rw'
        else: 'r'

I see three levels of syntax.
First, basic relations of objects - instantiating and invoking of methods. All that above will be translated to this level. It's technical level.
Second, user friendly expressions: control statements, operators, etc - all that forms logic of method.
Third, level of composition of objects. This we not only instantiate and invoke. This it has a sense, and will be comfortable to see names of arguments.
What we have - first level is  as third level, but without optional elements.
Second level - sugar for more readable composition of low-level, senseless objects.

Hello! May I bring some SmallTalk here? Take a look:
expr ifTrue: [statements to evaluate if expr] ifFalse: [statements to evaluate if not expr]

In the SmallTalk "if statement" is just a method (message) of some boolean expression, and ifTrue/ifFalse is just a named arguments of method if.
A smalltalk'ish version of fibonacci example can look like this:
create fibonacci(1) as Number:
  Number n
  bytes asBytes():
    lessThan: @n, 2
      ifTrue: 1
      ifFalse:
        plus:
          @n
          fibonacci:
            minus: @n, 1

And this example is even closer to FP: it looks just like a Church encoding of booleans:
true = (x, y) -> x
false = (x, y) -> y
if = (expr, then, else) -> expr(then, else)

if(lessThan(1, 2), "less", "greater") --> "less"

The main benefit of if as a method is type safety - if will be available only for "boolean" objects.

@gukoff take a look at our new syntax, I believe you will like it

@gukoff take a look at our new syntax, I believe you will like it


Fix contributor list

Bug noticed by @nsoranzo in https://github.com/galaxyproject/training-material/pull/1352

thanks @erasche !


Implement validation for SPDX 3.0

From the implementers call on 1 May 2024, a few suggestions:

Validate using the generated Python code from SHACL2Code
Validate using the SHACL file generated from the spdx-3-model repo
Wait for the updated java libraries

Resolved with #541


[WIP] Functions

Proposal for adding custom functions, based on the pg_tileserv and martin implementations.
Ref #8

done in #59


time out of joint

Here's a pretty bug:

Looks like time is skipping around. More likely, the data is not getting pulled in sequential order.

Hmm, just sorting the keys isn't going to help!


⚠ Bofrost.de has degraded performance

In f078352, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1444 ms

Resolved: Bofrost.de performance has improved in de64221 after 9 minutes.


[Feature] Add rancher2 snippets from doc

It would be grate to have rancher2 snippets from doc.

added rancher2 snippets in the most recent update.


[SD-App] please add MhageGH's M5Stack-Neural-Network

https://github.com/MhageGH/M5Stack-Neural-Network

The app has been scheduled for rebuild

Compilation of this package failed, it has been labeled as invalid until the source of the problem is identified and addressed

compilation errors:
M5Stack_NeuralNetwork:7:19: error: redefinition of 'const int N'
 const int s = 10, N = 10;
                   ^
In file included from /home/runner/work/M5Stack-Neural-Network/M5Stack_NeuralNetwork/M5Stack_NeuralNetwork.ino:4:0:
/tmp/arduino_build_715657/sketch/const.h:1:11: note: 'const int N' previously defined here
 const int N = 100, N0 = 784, N1 = 50, N2 = 100, N3 = 10;
           ^


Add Social Login

Describe the feature you'd like
Add facebook,google login
Screenshots

Would you like to work on the issue?

[x] Yes

Not working on server yet

@iamareebjamal facebook login is working

Can you give me the link to the website where it's working?

https://eventyay.com/

That's the legacy server. We're not using its API


How can plugins add new models, migrations and mutations

What I'm trying to achieve
Allow buyers to pick a "delivery slot" for when to deliver their orders
Describe a proposed solution
Wish to introduce a new table for storing the available delivery slots, with the following schema
slot_id | slot_date | slot_start | slot_end | max_deliveries | remaining_deliveries
1 | 2022-03-02 | 09:00:00 | 13:00:00 | 100 | 17
2 | 2022-03-03 | 09:00:00 | 13:00:00 | 100 | 85
3 | 2022-03-03 | 14:00:00 | 18:00:00 | 150 | 45

The customer will be able to pick a slot for their delivery
When the order is saved, the slot_id will be added to the checkout metadata
The plugin will use the order_updated method to deduct the remaining_deliveries
Need to be able to create the schema using migrations, and create a mutation to insert a new slot

Other solutions I've tried and won't work
Do this outside of Saleor using a separate set of APIs, and create an APP to use the webhooks to update the external API. Don't want to go this route, since it'll mean running and maintaining another service.
Screenshots or mockups
None

@coolbung Have you considered using serverless functions like AWS lambda, Vercel, Cloudflare workers?
This is our recommended way to extend Saleor and we are planning to phase out plugins eventually (long-term goal).

Have certainly considered that option as mentioned in my post. If that is the recommended way, thats fine.
So plugins cannot add mutations / schemas / models ?

So plugins cannot add mutations / schemas / models ?
Correct, plugins should not be able to do so


Fix failing tests in LegacyTests

I've brought over a bunch of legacy tests from the original email extractor and dropped them into this solution. A bunch of them are failing due to weird edge cases I never properly handled in the regex. If someone would like to give these a go (any regex tragics out there?!), it'd be cool to get these handled properly.

@troyhunt Can you share some samples of edge cases you are thinking about? curious.
Here is my attempt on email address validation: https://regex101.com/r/34ha1f/1

Fixed all the mentioned cases in the pull request: https://github.com/HaveIBeenPwned/EmailAddressExtractor/pull/9

Still seeing a few failing testes (i.e. "dot_first_is_invalid")

@troyhunt Can we close this issue? or anything pending here?

I'm still seeing some failing tests, for example domain_with_underscore_is_valid and unescaped_double_quote_is_invalid (among others). Want to have a go at those?


Potential for adding a 'system' role to usePollinationsText

I know it works well through usePollinationsChat, and usePollinationsText is designed to be simple, which I appreciate. However, what are your thoughts on adding support for sending a role="system" as well?"
const text = usePollinationsText('Write a short haiku about Pollinations.AI', 'You are a Hindu poet');

yes i was considering it. with usePollinationsChat it's already possible.
we can just call the endpoint with a post request and send the system prompt along as the first message with role system

@diogo-karma check the pull request: https://github.com/pollinations/pollinations/pull/667


Svelte group 1 docs review

Contributing to:

https://github.com/skeletonlabs/skeleton/issues/1049

Checklist

[x] Clipboard
[x] Filters
[x] Focus Trap
[x] Accordions
[x] App Bar
[x] App Rail
[x] App Shell
[x] Avatars
[x] Conic Gradients
[x] File Buttons
[x] File Dropzone
[x] Input Chips

You might want to decide on either space or no in Clipboard ;)

Focus Trap:

Apply use:focusTrap then the action value to either true or false to enable or disable focus.
then set the action value?

AppRail:

This component implements restProps. This passes all extra attributes to the component's AppRailTile element.
Should probably be AppRailTile elementS?
Apply abitrary classes (in props)
Probably the whole repo needs a Find & Replace for abitrary to arbitrary
Page State
Isn't that also handled with AppRailTile values & the selected store? I feel like we should mention that that's the default, recommended way

AppShell

Apply abitrary classes (in props)
Probably the whole repo needs a Find & Replace for abitrary to arbitrary

FileDropzone

Apply abitrary classes (in props)
Probably the whole repo needs a Find & Replace for abitrary to arbitrary

Under the clipboard input value section it states "To copy a form input value", shouldn't this apply to all input value's and therefor just be "To copy an input value"? No clue if I'm nitpicking here but something I noticed.

Under the clipboard input value section it states "To copy a form input value", shouldn't this apply to all input value's and therefor just be "To copy an input value"? No clue if I'm nitpicking here but something I noticed.

The intention is it copies the input that you target. So perhaps insert that term?
"To copy the target input value...."

@niktek if all changes are current you've got my go ahead to merge!

@niktek , seems to be a minor issue on https://skeleton-docs-oi8f3pcbb-skeleton-labs.vercel.app/components/app-shell -> slots -> header:

... apologies if I'm looking at a stale page.

I think this is the line?
https://github.com/niktek/skeleton/blob/f4a0fa09a55f9f69d93f2e56d85bb79c1288a8c0/src/lib/components/AppShell/AppShell.svelte#L3
Sorry. Wait out of my depth right now.

moved here:
https://github.com/skeletonlabs/skeleton/issues/1049#issuecomment-1452915286


Struggling to locate Submit button in Ember App

Hi,
First of all thank you for making this - it's a great resource we've been using for over a year
I am now moving to implement the solution against an existing product we are not yet scanning and am hitting a brick wall authenticating. I have managed to fill in the Username and Password fields on the login screen, but the XPath for our Login button is //*[@id="login-button"]/button and as a result i can't find a way to get this to be detected. Any ideas how i can achieve this, or is it possible to add this as an option into the Python script for buttons?
Many Thanks

@andydkelly-ig I just recently commited a change that allows this parameter:
auth.submitaction=submit
This will instruct the tool to perform a submit on the form in which the Username field is located. Can you try this?

Will give it a go

By the way, you can also provide xpath in the auth.submit_field config param. So you could do: auth.submit_field='//*[@id="login-button"]/button'

Sadly this didn't work with either of my apps (one is Ember and one is Angular) - it just cannot seem to find the button to submit. I can find and fill Username and Password but on both apps the login button doesn't appear as type button or submit.

On the Angular app the XPath for the login button is //*[@id="button-1022"] and on the Ember app it is //*[@id="login-button"]/button
I have tried adding these by ID and also by XPath as follows:
auth.submit_field='//*[@id="button-1022"]'
auth.submit_field='//*[@id="login-button"]/button'

I receive the error:
selenium.common.exceptions.NoSuchElementException: Message: Unable to locate element: //*[@type='submit' or @type='button']

@andydkelly-ig could you post a demo page or the HTML / DOM? So I can debug the issue.

https://d3sa-preview.infogixsaas.com/editor is one of them

Cool, I'll take a look!

@andydkelly-ig can you pull the latest image, it should work now without providing any field name. Alternatively you can provide auth.username_field="ember4" auth.password_field="ember5" auth.submit_field="//button"

Fantastic Dick, it's running now. Really appreciate the quick turnaround on this. Thank you very much 👍

Nice!


v0.3.0 API changes for OpenMMTools compatibility

Description
Significant changes to the overall BLUES API, where much of the refactoring is to follow similar structure to the openmmtools toolkit.
"Move" classes are now what carry out the actual simulation and modification of the openmm.Integrator/openmm.Context objects.

Running the NCMC+MD simulation now relies on using the LangevinDynamicsMove class which I've modified to ReportLangevinDynamicsMove to allow storing coordinates over the MD simulation phase.
NCMCMove provides the base class for perturbing atom coordinates. Every subsequent move we develop should inherit from this class and override the _propose_positions() function which simply takes a positions array and outputs the proposed positions (as opposed to modifying the context itself).
The RandomLigandRotationMove has been refactored to utilize this framework.
This redesign should allow us to draw from the openmmtools library of monte carlo moves which perturb atom coordinates and turn them into a move which uses the NCMC protocol. For example:

from openmmtools.mcmc import MCDisplacementMove
class NCMCDisplacementMove(MCDisplacementMove, NCMCMove):
    def _get_integrator(self, thermodynamic_state):
        return NCMCMove._get_integrator(self,thermodynamic_state)

BLUESSampler replaces what was the BLUESSimulation class, drawing inspiration from the openmmtools.mcmc.MCMCSampler class.

Instead of handling openmm.Simulation objects, we now make use of the openmmtools.ThermodynamicState/SamplerState objects.
The BLUESSampler class ties together the States and Moves in order to execute the NCMC+MD simulation.

Reporters have been changed to Storage to avoid confusion with reporters designed to work with openmm.Simulations. Our reporters have been modified to NetCDF4Storage and BLUESStateDateStorage. These now take openmm.States and openmm.Integrators as their input, instead of the openmm.Simualtion and openmm.Context.
Todos
Notable points that this PR has either accomplished or will accomplish.

[x] Re-implementation of random rotation
[x] Test toluene/T4-lysozyme system
[x] Module refactoring
[x] Code clean-up
[x] Unit testing
[x] Docstrings
[x] ReadTheDocs

Status

[x] Ready to go

A couple notes from discussing with Nathan:

He accidentally merged an earlier version of this, then forced a roll back. So it looks like a 0.2.5 version was merged, but it was reverted.
The branch is called 0.2.5 but we're renaming the PR because of the need to release an interim version number before sorting this out


Add prev/next/first/last IANA links to TimeMap representation

See https://gist.github.com/acoburn/7e1b5078379a4405c28c610a72c2a3f6

Actually, I'm going to close this; the IANA links aren't part of the link headers at the moment, and all of that information is discoverable anyway.


Fix regression in stats API endpoint

fixes #13421
Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

ping @tiborvass @cpuguy83 @thaJeztah

ping @vieux @crosbymichael interested in your thoughts; the discussion is if the /stats endpoint should no longer stream by default, but only if a ?stream[=1] param is passed

making it consisted with logs endpoint with follow param. Even if stats is made to stream by default..

ping @cpuguy83 @thaJeztah is this going to 1.7?

@runcom if we're talking purely about the regression (/stats no longer streaming by default), then I think yes, because that was an unintended change.
(Not taking into account the discussion to change the default)
But @vieux is the release captain, so he has the final word :)

LGTM. Moved to code review.

I'll rebase in a while, but still think this whole thing needs other opinions

We can (and should) just version the API here, < 1.19 == stream always true, else stream is defaulted to false. Will have to update the CLI as well.

Stats are streaming by default, the cli even has the flag --no-stream to disable this behavior. This is the correct behavior in the server to keep backwards compatibility:

No Parameter == Stream
Parameter true == Stream
Parameter false == NO Stream

@runcom this needs a rebase unfortunately. Do you think we can still fix it for 1.7? I can carry it in if you don't have time.

@calavera fixing right now based on your comment

@calavera rebased

LGTM

LGTM

cherrypicked \o/
On Fri, May 29, 2015 at 3:05 PM, David Calavera<EMAIL_ADDRESS>wrote:

Assigned #13425 https://github.com/docker/docker/pull/13425 to
@jfrazelle https://github.com/jfrazelle.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/pull/13425#event-317669844.


Rename type_support_commons -> type_support_common

thanks for indulging me
Standard CI:

Linux
Linux-aarch64
macOS
Windows

CI including connext dynamic:

Linux
Linux-aarch64  (no new info provided)
macOS
Windows

reran the first osx job to be sure it was flaky tests that failed:


Unit test cases for post checklist and error handling for post checklist json file

:nut_and_bolt: Description: What code changed, and why?

:chains: Related Resources
:+1: Definition of Done
:athletic_shoe: How to Build and Test the Change
:white_check_mark: Checklist
All PRs must tick these:

[ ] I have read the CONTRIBUTING document.
[ ] All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

[ ] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
[ ] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
[ ] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
[ ] Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
[ ] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

[ ] Tests added/updated? (all new code needs new tests)
[ ] Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.
:camera: Screenshots, if applicable

created another pr, as I was getting issues while rebasing with base branch https://github.com/chef/automate/pull/6796


Use more official Jedi APIs for gotos

https://github.com/davidhalter/jedi-vim/pull/808

Dupe of #9458 #10632


No option to exit with failure code if ES errors are returned on write

Occasionally we hit a mapper_parsing_exception from ES when copying data (to be expected - some documents had inconsistent types). However elasticdump does not abort if these errors occur - it continues, eventually exiting with a success exit code. When elasticdump is used as part of a CI/CD pipeline, where people are not watching over the console output, this can lead to missing documents.
We do not pass the --ignore-errors option.
Example:
./bin/elasticdump --input=http://redacted/ --input-index=2a19a7df-59df-54dc-b489-a16ee76ece53_1.0.642/product --output=http://redacted/ --output-index=2a19a7df-59df-54dc-b489-a16ee76ece53_1.0.643/product --type=data --limit=10
Sat, 02 Dec 2017 10:36:11 GMT | starting dump
Sat, 02 Dec 2017 10:36:11 GMT | got 10 objects from source elasticsearch (offset: 0)
Sat, 02 Dec 2017 10:36:11 GMT | sent 10 objects to destination elasticsearch, wrote 10
Sat, 02 Dec 2017 10:36:12 GMT | got 10 objects from source elasticsearch (offset: 10)
{ _index: '2a19a7df-59df-54dc-b489-a16ee76ece53_1.0.643',
  _type: 'product',
  _id: '48047f65-6010-47a1-93b1-23def0edacd6',
  status: 400,
  error:
   { type: 'mapper_parsing_exception',
     reason: 'failed to parse [content.approximate]',
     caused_by:
      { type: 'number_format_exception',
        reason: 'For input string: "6.2400"' } } }
{ _index: '2a19a7df-59df-54dc-b489-a16ee76ece53_1.0.643',
  _type: 'product',
  _id: '34ab6f73-fa93-4f39-b155-445a35daf667',
  status: 400,
  error:
   { type: 'mapper_parsing_exception',
     reason: 'failed to parse [content.approximate]',
     caused_by:
      { type: 'number_format_exception',
        reason: 'For input string: "6.2400"' } } }
Sat, 02 Dec 2017 10:36:12 GMT | sent 10 objects to destination elasticsearch, wrote 8
Sat, 02 Dec 2017 10:36:12 GMT | got 10 objects from source elasticsearch (offset: 20)
Sat, 02 Dec 2017 10:36:13 GMT | sent 10 objects to destination elasticsearch, wrote 10
Sat, 02 Dec 2017 10:36:13 GMT | got 10 objects from source elasticsearch (offset: 30)
Sat, 02 Dec 2017 10:36:13 GMT | sent 10 objects to destination elasticsearch, wrote 10
Sat, 02 Dec 2017 10:36:13 GMT | got 10 objects from source elasticsearch (offset: 40)
Sat, 02 Dec 2017 10:36:14 GMT | sent 10 objects to destination elasticsearch, wrote 10
...

The is due to elasticsearch.prototype.setData:
           r.items.forEach(function (item) {
             if (item['index'].status < 400) {
               writes++
             } else {
               console.error(item['index'])
             }
           })

We'd like an option to instead return callback(item['index']); in the case of a 400/500 response from ES.

ElasticDump version
3.3.1
Elasticsearch version
2.x, 5.x

Closing this issue.
Please re-open if you do not feel the question has been answered sufficiently.


UNMET PEER DEPENDENCY webpack@1 || ^2.1.0-beta

I installed redux today with the command npm install --save redux today - which installed "redux": "^3.5.2" - and I saw the following warning echoed to my console.

UNMET PEER DEPENDENCY webpack@1 || ^2.1.0-beta

I don't see why a library like Redux should have anything to do with a build utility like Webpack, and what's even more concerning for me is that it wants a beta version of Webpack.
I think that this peer dependency may have been added in error.  If it hasn't, can someone explain the consequences of not having this dependency installed?

My apologies.  On closer inspection of the console, I see that it is babel-loader that is issuing this complaint, not Redux.


trouble baking out BuildableDetailView pages

For a small personal project I think I've configured BuildableListViews properly (I can see the baked-out files) but I'm having issues with a BuildableDetailView that is supposed to bake out 10 profile pages. It works on my local server but this is the error I get when I try to run python manage.py build:
Traceback (most recent call last):
  File "manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
  File "/home/ryan/.virtualenvs/cutthecheck/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 354, in execute_from_command_line
    utility.execute()
  File "/home/ryan/.virtualenvs/cutthecheck/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 346, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/home/ryan/.virtualenvs/cutthecheck/local/lib/python2.7/site-packages/django/core/management/base.py", line 394, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/home/ryan/.virtualenvs/cutthecheck/local/lib/python2.7/site-packages/django/core/management/base.py", line 445, in execute
    output = self.handle(*args, **options)
  File "/home/ryan/.virtualenvs/cutthecheck/local/lib/python2.7/site-packages/bakery/management/commands/build.py", line 81, in handle
    self.build_views()
  File "/home/ryan/.virtualenvs/cutthecheck/local/lib/python2.7/site-packages/bakery/management/commands/build.py", line 188, in build_views
    view().build_method()
  File "/home/ryan/repos/cutthecheck/rosters/views.py", line 40, in build_queryset
    self.build_object(o)
  File "/home/ryan/.virtualenvs/cutthecheck/local/lib/python2.7/site-packages/bakery/views.py", line 196, in build_object
    self.request = RequestFactory().get(self.get_url(obj))
  File "/home/ryan/.virtualenvs/cutthecheck/local/lib/python2.7/site-packages/django/test/client.py", line 303, in get
    return self.generic('GET', path, secure=secure, **r)
  File "/home/ryan/.virtualenvs/cutthecheck/local/lib/python2.7/site-packages/django/test/client.py", line 357, in generic
    parsed = urlparse(path)
  File "/usr/lib/python2.7/urlparse.py", line 143, in urlparse
    tuple = urlsplit(url, scheme, allow_fragments)
  File "/usr/lib/python2.7/urlparse.py", line 182, in urlsplit
    i = url.find(':')
AttributeError: 'NoneType' object has no attribute 'find'

I can't figure out whether this is because of an improper setting or something in my view. Here is my view, url and settings.py. Thanks

Looks like it doesn't like the "url" or output path configured on your view. How is that set?

@palewire what do you mean by "output path" on my view?

This stuff

Aha! I added get_url and get_build_path functions and it now works. Thanks.

Good. If you have get_absolute_url set on your model it will probably
solve itself without any configuration, FWIW.
On Mon, Dec 7, 2015 at 3:55 PM Ryan Menezes<EMAIL_ADDRESS>wrote:

Closed #76 https://github.com/datadesk/django-bakery/issues/76.
—
Reply to this email directly or view it on GitHub
https://github.com/datadesk/django-bakery/issues/76#event-485061743.


fix/Freeze Weaviate client to v3

When running dest/weaviate.sh I saw:
Python client v3 `weaviate.Client(...)` connections and methods are deprecated and will
            be removed by 2024-11-30.

            Upgrade your code to use Python client v4 `weaviate.WeaviateClient` connections and methods.
                - For Python Client v4 usage, see: https://weaviate.io/developers/weaviate/client-libraries/python
                - For code migration, see: https://weaviate.io/developers/weaviate/client-libraries/python/v3_v4_migration

            If you have to use v3 code, install the v3 client and pin the v3 dependency in your requirements file: `weaviate-client>=3.26.7;<4.0.0`

To make sure in December it suddenly won't stop working, I limited it just like that.
Why not upgrade to v4? Because it won't be easy, and it's probably not prio right now:

The v4 Weaviate Python client API is a complete rewrite, aimed at an improved overall user experience. It is therefore also very different to the v3 API, and will require re-learning of changed patterns in the way you interact with Weaviate.

We've decided not to support this but instead prioritize updating the code to support v4.


The Github Extension

Is your feature request related to a problem? Please describe.
I would like to add a Github Extension
Describe the solution you'd like.
This Extension will showcase the status of feed, issues and recent activity of a Github User.

[x]  GSSoC  Contributor

Kindly assign it to me. @ridsuteri
Describe alternatives you've considered.
I'm a GSSoC contributor and would like to take up this issue.
Add any other context or screenshots about the feature request here.
I will use the Github REST API for this extension.

sounds fun @shreya024, go ahead I am assigning you the issue!


Rhino Compas IGS initiation error

Describe the bug
I first installed and worked with IGS late last year. It worked fine then. Now I am getting the following error message when trying to initiate the plugin

It is followed by following error message, when I keep rhino open and try to initiate IGS

These errors persist after trying to reinstall IGS. Other IGS commands will give similar error messages
To Reproduce
Steps to reproduce the behavior:

install rhino igs following the steps described in https://blockresearchgroup.gitbook.io/igs/quick-start/untitled
Initiate IGS in rhino
Instead of the expected initiation, the error messages as seen above will pop up

Expected behavior
Regular initiation and working behavior of the plugin
Computer

Windows 10
-rhino 7.1922165.13001,2022-06-14
-igsGS_v0.3.3rc0

Additional context
No python installed on machine

Update:
I also tried installing it through the compas-dashboard following the instructions from https://blockresearchgroup.gitbook.io/csd1-2021/tools/compas-tools
including installation of anaconda3. The previous plugin and script files were deleted and uninstalled previously. The compas console returns a "failed" message and following console messages:

echo Add conda-forge && conda config --add channels conda-forge && echo Create compas-apps env && conda create -n compas-apps -y && echo Activate Environment && conda activate compas-apps && echo Install planarity and cython && conda install python-planarity cython=0.29.23  -y && echo Install the package && pip install compas_igs==v0.3.3rc0 && echo Install to Rhino && python -m compas_igs.install --rhino_version 7.0
Add conda-forge
Warning: 'conda-forge' already in 'channels' list, moving to the top
Create compas-apps env
D:\Programs\anaconda3\lib\site-packages\requests_init_.py:109: RequestsDependencyWarning: urllib3 (1.26.9) or chardet (5.0.0)/charset_normalizer (2.0.12) doesn't match a supported version!
warnings.warn(
Collecting package metadata (current_repodata.json): ...working...
done
Solving environment: ...working...
done

Package Plan
environment location: D:\Programs\anaconda3\envs\compas-apps
Preparing transaction: ...working...
done
Verifying transaction: ...working...
done
Executing transaction: ...working... done

To activate this environment, use

$ conda activate compas-apps

To deactivate an active environment, use

$ conda deactivate
Activate Environment
Install planarity and cython
D:\Programs\anaconda3\lib\site-packages\requests_init_.py:109: RequestsDependencyWarning: urllib3 (1.26.9) or chardet (5.0.0)/charset_normalizer (2.0.12) doesn't match a supported version!
warnings.warn(
Collecting package metadata (current_repodata.json): ...working...
done
Solving environment: ...working...
failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): ...working...
done
Solving environment: ...working...
done
Package Plan
environment location: D:\Programs\anaconda3\envs\compas-apps
added / updated specs:
- cython=0.29.23
- python-planarity
The following NEW packages will be INSTALLED:
bzip2              conda-forge/win-64::bzip2-1.0.8-h8ffe710_4
ca-certificates    conda-forge/win-64::ca-certificates-2022.6.15-h5b45459_0
cython             conda-forge/win-64::cython-0.29.23-py39h415ef7b_1
libffi             conda-forge/win-64::libffi-3.4.2-h8ffe710_5
libzlib            conda-forge/win-64::libzlib-1.2.12-h8ffe710_1
openssl            conda-forge/win-64::openssl-3.0.4-h8ffe710_0
pip                conda-forge/noarch::pip-22.1.2-pyhd8ed1ab_0
planarity          conda-forge/win-64::planarity-<IP_ADDRESS>-hfa6e2cd_1002
python             conda-forge/win-64::python-3.9.13-hcf16a7b_0_cpython
python-planarity   conda-forge/win-64::python-planarity-0.4.1-py39hb82d6ee_7
python_abi         conda-forge/win-64::python_abi-3.9-2_cp39
setuptools         conda-forge/win-64::setuptools-62.6.0-py39hcbf5309_0
sqlite             conda-forge/win-64::sqlite-3.38.5-h8ffe710_0
tk                 conda-forge/win-64::tk-8.6.12-h8ffe710_0
tzdata             conda-forge/noarch::tzdata-2022a-h191b570_0
ucrt               conda-forge/win-64::ucrt-10.0.20348.0-h57928b3_0
vc                 conda-forge/win-64::vc-14.2-hb210afc_6
vs2015_runtime     conda-forge/win-64::vs2015_runtime-14.29.30037-h902a5da_6
wheel              conda-forge/noarch::wheel-0.37.1-pyhd8ed1ab_0
xz                 conda-forge/win-64::xz-5.2.5-h62dcd97_1
Preparing transaction: ...working...
done
Verifying transaction: ...working...
done
Executing transaction: ...working...
done
Install the package
Collecting compas_igs==v0.3.3rc0
Using cached compas_igs-0.3.3rc0-py2.py3-none-any.whl (1.9 MB)
Collecting compas-ags
Using cached compas_ags-1.1.1-py2.py3-none-any.whl (31 kB)
Collecting compas>=1.9.4
Using cached COMPAS-1.16.0-py2.py3-none-any.whl (5.2 MB)
Collecting pillow
Using cached Pillow-9.1.1-cp39-cp39-win_amd64.whl (3.3 MB)
Collecting pycollada
Using cached pycollada-0.7.2-py3-none-any.whl
Collecting schema
Using cached schema-0.7.5-py2.py3-none-any.whl (17 kB)
Collecting sympy
Using cached sympy-1.10.1-py3-none-any.whl (6.4 MB)
Requirement already satisfied: cython in d:\programs\anaconda3\envs\compas-apps\lib\site-packages (from compas>=1.9.4->compas_igs==v0.3.3rc0) (0.29.23)
Collecting scipy>=1.1
Using cached scipy-1.8.1-cp39-cp39-win_amd64.whl (36.9 MB)
Collecting matplotlib>=3.1
Using cached matplotlib-3.5.2-cp39-cp39-win_amd64.whl (7.2 MB)
Collecting numpy>=1.15.4
Using cached numpy-1.23.0-cp39-cp39-win_amd64.whl (14.7 MB)
Collecting typing-extensions
Using cached typing_extensions-4.2.0-py3-none-any.whl (24 kB)
Collecting watchdog
Using cached watchdog-2.1.9-py3-none-win_amd64.whl (78 kB)
Collecting networkx
Using cached networkx-2.8.4-py3-none-any.whl (2.0 MB)
Collecting jsonschema
Using cached jsonschema-4.6.0-py3-none-any.whl (80 kB)
Collecting imageio>=2.7
Using cached imageio-2.19.3-py3-none-any.whl (3.4 MB)
Collecting fonttools>=4.22.0
Using cached fonttools-4.33.3-py3-none-any.whl (930 kB)
Collecting cycler>=0.10
Using cached cycler-0.11.0-py3-none-any.whl (6.4 kB)
Collecting python-dateutil>=2.7
Using cached python_dateutil-2.8.2-py2.py3-none-any.whl (247 kB)
Collecting kiwisolver>=1.0.1
Using cached kiwisolver-1.4.3-cp39-cp39-win_amd64.whl (55 kB)
Collecting pyparsing>=2.2.1
Using cached pyparsing-3.0.9-py3-none-any.whl (98 kB)
Collecting packaging>=20.0
Using cached packaging-21.3-py3-none-any.whl (40 kB)
Collecting attrs>=17.4.0
Using cached attrs-21.4.0-py2.py3-none-any.whl (60 kB)
Collecting pyrsistent!=0.17.0,!=0.17.1,!=0.17.2,>=0.14.0
Using cached pyrsistent-0.18.1-cp39-cp39-win_amd64.whl (61 kB)
Collecting contextlib2>=0.5.5
Using cached contextlib2-21.6.0-py2.py3-none-any.whl (13 kB)
Collecting mpmath>=0.19
Using cached mpmath-1.2.1-py3-none-any.whl (532 kB)
Collecting six>=1.5
Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Installing collected packages: mpmath, watchdog, typing-extensions, sympy, six, pyrsistent, pyparsing, pillow, numpy, networkx, kiwisolver, fonttools, cycler, contextlib2, attrs, scipy, schema, python-dateutil, packaging, jsonschema, imageio, pycollada, matplotlib, compas, compas-ags, compas_igs
Successfully installed attrs-21.4.0 compas-1.16.0 compas-ags-1.1.1 compas_igs-0.3.3rc0 contextlib2-21.6.0 cycler-0.11.0 fonttools-4.33.3 imageio-2.19.3 jsonschema-4.6.0 kiwisolver-1.4.3 matplotlib-3.5.2 mpmath-1.2.1 networkx-2.8.4 numpy-1.23.0 packaging-21.3 pillow-9.1.1 pycollada-0.7.2 pyparsing-3.0.9 pyrsistent-0.18.1 python-dateutil-2.8.2 schema-0.7.5 scipy-1.8.1 six-1.16.0 sympy-1.10.1 typing-extensions-4.2.0 watchdog-2.1.9
Install to Rhino
Traceback (most recent call last):
File "D:\Programs\anaconda3\envs\compas-apps\lib\runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "D:\Programs\anaconda3\envs\compas-apps\lib\runpy.py", line 87, in _run_code
---------- Checking packages ----------
compas               OK
compas_rhino         OK
compas_ags           OK
compas_igs           OK
compas_igs is editable install:  False
---------- Installing compas_ags python plugin ----------
exec(code, run_globals)
File "D:\Programs\anaconda3\envs\compas-apps\lib\site-packages\compas_igs\install.py", line 72, in
python_plugins_path = compas_rhino.get_python_plugins_path(args.rhino_version)
AttributeError: module 'compas_rhino' has no attribute 'get_python_plugins_path'
Error: Command failed: D:\Programs\anaconda3/Scripts/activate.bat && echo Add conda-forge && conda config --add channels conda-forge && echo Create compas-apps env && conda create -n compas-apps -y && echo Activate Environment && conda activate compas-apps && echo Install planarity and cython && conda install python-planarity cython=0.29.23  -y && echo Install the package && pip install compas_igs==v0.3.3rc0 && echo Install to Rhino && python -m compas_igs.install --rhino_version 7.0
Warning: 'conda-forge' already in 'channels' list, moving to the top
D:\Programs\anaconda3\lib\site-packages\requests_init.py:109: RequestsDependencyWarning: urllib3 (1.26.9) or chardet (5.0.0)/charset_normalizer (2.0.12) doesn't match a supported version!
warnings.warn(
D:\Programs\anaconda3\lib\site-packages\requests_init.py:109: RequestsDependencyWarning: urllib3 (1.26.9) or chardet (5.0.0)/charset_normalizer (2.0.12) doesn't match a supported version!
warnings.warn(
Traceback (most recent call last):
File "D:\Programs\anaconda3\envs\compas-apps\lib\runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "D:\Programs\anaconda3\envs\compas-apps\lib\runpy.py", line 87, in _run_code
exec(code, run_globals)
File "D:\Programs\anaconda3\envs\compas-apps\lib\site-packages\compas_igs\install.py", line 72, in
python_plugins_path = compas_rhino._get_python_plugins_path(args.rhino_version)
AttributeError: module 'compas_rhino' has no attribute '_get_python_plugins_path'

Hi @rstarossek installation through dashboard could be impacted by some latest compas updates and not working properly at the moment. This might be a redundant question, but have you tried to re-install IGS directly through installer at https://github.com/BlockResearchGroup/compas-IGS/releases/tag/v0.3.3rc0 ? (This is a compiled version that suppose to always work). If the same error presents, could you in Rhino python editor run the script:
import compas
print compas.__version__

and let me know what compas version is it in your Rhino environment?

Hi @Licini thanks for your response. I tried reinstalling through the stand-alone installer before, but gave it another go, since I also reinstalled rhino in the last few days as well. Unfortunately, I am still getting the same error.
I ran the script you posted and the output/version seems to be 1.11.1

Let me know if I should try anything else or if you need any other information

Hi @rstarossek Thanks for the feedback. We have pin-pointed the issue now. These errors were originated from a Rhino version update earlier this year which affects how the Ironpython environment can be detected programmatically. COMPAS itself been patched to address the issue in February, however it also has introduced numerous other changes which COMPAS-IGS hasn't been caught up yet. To bring everything up to date we might need a bit longer especially the main author of IGS @ricardoavelino is currently on vacation. Meanwhile the easiest way to fix the issue would be downgrade to an earlier version of Rhino7 such as SR9: https://drive.google.com/file/d/1P0fBmx--9SlkANn3Q-cUiXYORtv6eNel/view?usp=sharing (you will need to first uninstall your current rhino before using the installer)

Hi @Licini , I reinstalled as per instructions and the plugin works again! Will keep in mind not to update my rhino for a while ;) Thank you very much for your help, and I am looking forward to further updates to the plugin!

Hi @Licini may I know if this problem has been fixed? cause I am currently having the same problem now and was wondering if there are any other fix other than downgrading to an earlier version?


[early review only] Log analytics oms

@krish7919  and @ttmc  This is for early review, small details still need to be addressed:

[x] Document how to get the workspace key via the az command line (if possible).
[x] Use more meaningful names for examples (workspace name mainly).
[x] Add a bit of explanations around the oms daemon set deployment docs.

Codecov Report

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

@@           Coverage Diff           @@
##           master    #1431   +/-   ##
=======================================
  Coverage   98.37%   98.37%
=======================================
  Files          56       56
  Lines        2588     2588
=======================================
  Hits         2546     2546
  Misses         42       42

My comments:

Put the oms-daemonset.yaml, log_analytics_oms.json and log_analytics_oms.parameters.json files in a folder perhaps? Something like k8s/log-analytics?

Document the change needed for the workspaceName param in log_analytics_oms.parameters.json. This can be changed to the name user wishes to keep for the OMS workspace.

You can use jsonlint.com to format and validate json. Currently, both log_analytics_oms.json and log_analytics_oms.parameters.json are not valid json schemas.

Missing backslash in the command: az resource show....

Please docuemnt how to obtain workspace key, even without az cli tool.

Put the oms-daemonset.yaml, log_analytics_oms.json and log_analytics_oms.parameters.json files in a folder perhaps? Something like k8s/log-analytics?

ok, done

You can use jsonlint.com to format and validate json. Currently, both log_analytics_oms.json and log_analytics_oms.parameters.json are not valid json schemas.

ok, done

Missing backslash in the command: az resource show....

Good catch! Done.

Document the change needed for the workspaceName param in log_analytics_oms.parameters.json. This can be changed to the name user wishes to keep for the OMS workspace.

Yes, this will be done as part of the second checkbox in the description:

Use more meaningful names for examples (workspace name mainly).

@ttmc @krish7919 I have addressed the remaining details, and also @krish7919 comments.

I will approve this PR and if I find issues in my future review/test, I'll create a new issue or pull request at that time.

note: created an issue to eventually pass JSON files through a linter in travis: #1438

created an issue to eventually pass JSON files through a linter in travis: #1438

I think that's overkill.
LGTM, I see some logs on the portal.

Note to those who may care about a clean git history:
sorry I merged the PR too fast here, as I was going to rebase it to clean its history.


As a CSE engineer, I want to re-use terraform templates for Azure resources across projects to avoid redevelopment of already existing assets.

Tagging @timfpark

@rickrain  @xtophs
This is the directory structure i would suggest if you plan to share/merge cobalt and bedrock
- ./components <<PIPELINE SHOULD NEVER RUN THESE INDIVIDUALLY>>
	- ./network
		- main.tf
			- vnet
	- ./keys
		- main.tf
			- key vault
	- ./ingress
		- ./multi-region
			- main.tf
				- traffic manager
		- ./single-region
			- main.tf
				- app gateway
	- ./monitoring
		- main.tf
			- azure monitor
	- ./compute
		- ./bedrock
		- ./cobalt

- ./solutions <<PIPELINE SHOULD RUN ONE OF THESE>>
	- ./single-region-bedrock
		- main.tf
			- .../../components/network (reuses network module)
			- .../../components/keys
			- .../../components/ingress/single-region
			- aks
	- ./multi-region-bedrock
		- main.tf
			- .../../components/network
			- .../../components/keys
			- .../../components/ingress/multi-region
			- aks
	- ./single-region-cobalt
		- main.tf
			- .../../components/network (reuses network module)
			- .../../components/keys
			- .../../components/ingress/single-region
			- aks
	- ./multi-region-cobalt
		- main.tf
			- .../../components/network
			- .../../components/keys
			- .../../components/ingress/multi-region
			- aks

This should really be an epic.


Refactor out quorum / join + leave logic out of Container class

This will allow custom logic to be plugged in, for hosts like Word be able to control system messages on their own (i.e. not necessarily sequence join & leave ops, but rather have alternative ways of communicating this information).
See Epic #7993 for more details.

It should likely be closed in favor of the item I've just opened in ADO.

Duplicate of 261


Fixed question mark in latex issue. closes #39

Breaks on channels starting on the second newline ?meta\n?lobby, and inside parenthesis (?lobby), as can be seen on the homepage. It's close though.

Logical.

Okie dokie. Try that out @AndrewBelt

Hm. Still broke. Nevermind. Will try again.

Okay.... I've got everything expect the one link of the front page working. My brain has decided to stop logically working for the moment.


Updated Login Form and Signup page, with NavBar and Footer from Yifan

Working LoginForm and partial Signup page, email verification still in progress

Personally I don't think the verify should be an extra routing. I prefer it to be a popup window.


A way to deny connections on the server

I don’t know if this is already a feature, but I was wondering if there was a way for the server to deny incoming connections. For example everyone joins the server in the “lobby” and then when the game starts nobody can join at this point until the game finishes like in among us lol. So the server will keep the clients that connected before the game starts but will deny any new incoming connections.

Currently all you can do is immediately disconnect the person trying to join late (using the server's DisconnectClient method), but I may add a way to refuse connections so the ClientConnected event never fires.

Reopening this as it's something I do want to implement.


Add v2 to WebSocket.md

Apparently we've forgotten to add some v2s to the URLs.
NOTE: I think there will be more changes needed.
Motivation
Docs are missing critical v2 URL component for APIs!

Result
The docs will be more accurate :anger:

PR made to the wrong master 🤦♂