Identify some quick design and code improvements to the site

The cluster.ipfs.io landing page was recently updatedd, but a quick design/content/tech review might highlight some spots for additional improvement. (Hopefully the vibe for this initiative can be more "hackathon" than "epic")
A few avenues to explore/tasks …
Content

[ ] Rework it into a hierarchical format (as opposed to a bulleted list), and modify to engage any key user groups we've identified. Note: this will have to be a first-pass level of effort, since we have no content strategist/writer atm *

*Have user groups been defined @hsanjuan? 😆
Tech

[ ] Audit to see where the code be simplified, and dependencies reduced (eg re css libraries, fonts, themes, js code) (@cwaring? :bowtie: ) site wide

UX/Visual design

[ ] Improve type scaling (consider Tachyons?) site wide

[ ] Solidify the grid structure/fix margins site wide

[ ] Break up the content (into panels?), in order to improve flow and make the page more engaging

[ ] Add more color below the fold

[ ] Add a high-profile call to action to the hero (above-the-fold) area

[ ] Add a clear call to action at the bottom of the content area ("Get started" eg)

[ ] Create implementation issues as needed, and

[ ] Bang em out

Plus anything else i'm missing.
Current landing page

One of the things that I find worrying is that we load a bunch of things and I don't know what for. This is a very static site. I want to minimize the amount of styling to something that be easily controlled:
  <script src="./js/jquery-2.x.min.js"></script>                              <- Why? I really don't want FadeIns or anything.

    <link rel="stylesheet" href="./css/nucleus.css">                       <- Why?
    <link rel="stylesheet" href="./css/fontawesome-all.min.css"> <- Only use like 5, can we import less?
    <link rel="stylesheet" href="./css/hybrid.css">                         <- Why?
    <link rel="stylesheet" href="./css/featherlight.min.css">         <- Why?
    <link rel="stylesheet" href="./css/perfect-scrollbar.min.css"> <- Why???
    <link rel="stylesheet" href="./css/auto-complete.css">          <- Why? Can we extract the necessary? Auto-complete is only in a search box. It can't be so hard to style a single input field.
    <link rel="stylesheet" href="./css/hybrid.css">                       <- Again?
    <link rel="stylesheet" href="./css/fontawesome-all.min.css"> <- Again?
    <link rel="stylesheet" href="./css/tachyons.min.css"/>           <- Already had discussion about this. I find the css classes they add barely documented, hard to understand. But ok.
    <link rel="stylesheet" href="./fonts/fonts.css"/>                     <- Why?
    <script async defer src="./buttons.js"></script>
    <link href="https://fonts.googleapis.com/css?family=IBM+Plex+Mono|IBM+Plex+Sans" rel="stylesheet">     <- Can we not load 3rd party fonts? Can we use default fonts or is that crazy? Can we distribute the fonts with the site at least?
    <link rel="stylesheet" href="./css/theme.css">                    <- Comes from `hugo-theme-learn`: How much of this is used? Can the couple of things be blended with `main.css`?
    <link rel="stylesheet" href="./css/hugo-theme.css">           <- Comes from `hugo-theme-learn`: How much of this is used? Can the couple of things be blended with `main.css`?
    <link rel="stylesheet" href="./css/main.css"/> <- This is the actual original CSS file that is generated from less and that is easy to understand and goes to the point.

    <style type="text/css">
      :root #header + #content > #left > #rlblock_left{
          display:none !important;
      }

        :not(pre) > code + span.copy-to-clipboard {
            display: none;
        }

The documentation menu does not support adding external links to it
H1 are huge, H2 small, H3 almost invisible:

This should look better: https://cluster.ipfs.io/documentation/deployment/setup/

Could hugo autogenerate page-index at the top of each documentation page with links to each section in the page?
<code> tags look ok in some places, but inside tables etc maybe not so good https://cluster.ipfs.io/documentation/reference/configuration/

* Rework it into a hierarchical format (as opposed to a bulleted list), and modify to engage any key user groups we've identified. _Note: this will have to be a first-pass level of effort, since we have no content strategist/writer atm_ *

*Have user groups been defined @hsanjuan? laughing

Not sure what content needs hierarchical format vs bulleted list ?
User groups are: IPFS user for the frontpage. System administrators for the docs mostly, we need to add a section focused on users that just join existing clusters but that's not written yet.


chore(deps): loopback version update

loopback version update
GH-55
Description
loopback version update
Fixes #55
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Intermediate change (work in progress)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] Performed a self-review of my own code
[x] npm test passes on your machine
[ ] New tests added or existing tests modified to cover all changes
[ ] Code conforms with the style guide
[ ] API Documentation in code was updated
[ ] Any dependent changes have been merged and published in downstream modules

:tada: This PR is included in version 5.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixes issue with bad join in Phase load

rewrote Plans.load_for_phase query
We discovered that the join from the old query was not considering the plan when retrieving answers. This resulted in a query that returned - (question * ([all answers from any plan]). The page logic was only displaying the correct records but the query itself was causing significant page load times.  Note that any note within the entire db was also retrieved...


Doc contains broken links

The doc contains broken links, e.g. the second link on that page for AsChangeset (the first one works).
Maybe others are affected too (depending on the cause).

I also noticed that the link to update in IncompleteUpdateStatement is broken as well (I'm guessing it should be update_statement? I think this one is because something was renamed.

I just tested the docs at http://docs.diesel.rs/diesel/index.html with a linkchecker.
It reports no broken links, so I think this can be closed.

Nice. Thanks, @theduke!
We currently cheated this issue by using absolute URLs (well, absolute paths) in a few places. This is good for now, but we should revisit this when a better solution (e.g. https://github.com/rust-lang/rfcs/pull/1946) is available.


ModuleInterface: Don't alias Foundation module in swiftinterfaces

Skip aliasing Foundation when -alias-module-names-in-module-interface is specified since it appears to confuse the typechecker. The module name "Foundation" is hardcoded and checked in several places, so aliasing Foundation may be changing some subtle behaviors.
Resolves rdar://128897610.

@swift-ci please smoke test

https://github.com/swiftlang/swift-testing/pull/663
@swift-ci please smoke test Windows


Performance issue with stream download

I am downloading 400 MB file on local machine with 7 MB/Second (.net core 2.0) same code run with .net framework 4.6 download speed 100 MB/Second.
public IActionResult DownloadDocument(Guid documentUniqueId)
{
var bytes = System.IO.File.OpenRead(@"D:\home\site\wwwroot\file\Organizer01_2017-09-03 (14) (3).zip");
return File(bytes, "application/octet-stream");
}
File size 400 MB .  API on local system. FIle on local system

@JeremyKuhne can we get this tracked in dotnet/corefx?

This issue was also opened as: https://github.com/aspnet/Performance/issues/246
@chintan3100 We need to know exactly how the FileStream is being written. What is the File class you're using? If you're writing via ASP.NET apis it would probably be better to start on that end.

I am using .net core. Please refer below code
public IActionResult DownloadDocument(Guid documentUniqueId)
{
var bytes = System.IO.File.OpenRead(@"D:\home\site\wwwroot\file\Organizer01_2017-09-03 (14) (3).zip");
return File(bytes, "application/octet-stream");
}

Presumably you're talking about System.Web.Mvc.Controller.File. You should probably start with https://github.com/aspnet/Mvc/issues. The ASP.NET team is the right starting point.

Moved this issue here: https://github.com/aspnet/Home/issues/2233


[In-progress] Docs 4.4.0

Getting our new documentation up and running is close, but currently still in-progress.
This stuff is our docs tooling, not the hosted docs themselves. Running doxygen in the docs folder outputs the docs themselves into a folder called html, which then has to be moved to the gh-pages branch to be hosted. (This is all explained in docs/README.md.)
Remaining tasks:

[x] @Amarcolina Port Graphic Renderer wiki guide into /docs/content/300-Graphic-Renderer.md - the Getting Started and Core documents are good references, they are complete or nearly complete.
[x] Finish porting the Interaction Engine wiki guide into /docs/content/200-Interaction-Engine.md

[x] Migrate GIFs for IE examples from wordpress hosting -> directly into the repo

[x] Port the Hands Module wiki guide into /docs/content/400-Hands-Module.md
[x] Port any remaining content from the wiki to /docs/content

So... I'm pretty sure this needed to be done before the 5am release.

Just to follow-up here, the tasks listed were already done, the finished site was linked on the frontend channel. The rest is all tooling, not the documentstion itself:

This stuff is our docs tooling, not the hosted docs themselves.

(I've marked the checkboxes now so there isn't any confusion)


conformance: Gloo Gateway report for v1.0.0

What type of PR is this?

/kind documentation
/area conformance
What this PR does / why we need it:
This PR adds a conformance report for gloo gateway against gateway API v1.0.0
Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

NONE

Thanks @EItanya! I'd recommend updating implementations.md at the same time and adding a conformance badge to link to this report.
/ok-to-test
/approve

Thanks @EItanya! I'd recommend updating implementations.md at the same time and adding a conformance badge to link to this report.
/ok-to-test /approve

Sounds good, will do!

looks good, but holding off approving until we get confirmation if @EItanya wants to add a badge or not

Oh now I see what you mean, I can add that!

Thanks!
/lgtm


Business table - sometimes the rows disappear

I populated table with 8 queries , and sometimes a row disappears and reappears.
I can't undertstan because query are identical ( only the address chenges).
Individually query are working but not propely displayed in table.

Here the table configuration , as you can see query are 8 and rows in table are 7

Here query inspect
As you can see row sometimes are not equal to query
How can i fix it ?
Thank you

@davecarcu This issue is not related to the Business Table panel. It's a data issue.
If your data source (Infinity) does not return all rows, it's probably an API rate limiting issue.
If it's internal API, check with the API team. If 3rd party check the limit for number of concurrent requests.


Cannot use object of type Mockery_0 as array

I made a very simple example:
<?php

namespace AppBundle\Manager;

use Mockery as m;
use PHPUnit\Framework\TestCase;

class ProductManagerTest extends TestCase
{
    public function testProductManager()
    {
        $config = m::mock(array('reference'=>'abc', 'type'=>'def'));
        $pm = new ProductManager($config);
    }
}

Related class:
<?php

namespace AppBundle\Manager;

class ProductManager
{
    public function __construct($config)
    {
        if (isset($config['reference'])) {
            $this->reference = $config['reference'];
        }
    }
}

When I execute testProductManager(), I get:
Fatal error: Cannot use object of type Mockery_0 as array
Am I using a wrong way to mock an array or something else is wrong?

You don't really want or need to mock an array, I would recommend just passing an array.
    public function testProductManager()
    {
        $config = array('reference'=>'abc', 'type'=>'def');
        $pm = new ProductManager($config);
    }

Ok, in which case should we use the following paragraph in the quick reference ?

$mock = \Mockery::mock(array('foo'=>1,'bar'=>2));
Creates a mock object named unknown since we passed no name. However we did pass an expectation array, a quick method of setting up methods to expect with their return values.

@Kwadz That would set up an test double, stubbing calls to the foo and bar methods.
$mock = \Mockery::mock(array('foo'=>1,'bar'=>2));

$mock->foo(); // int(1)
$mock->bar(); // int(2)


Skill Name
SVN (Apache Subversion)
Why?
Still used in different companies around the world.
Reference Image
https://upload.wikimedia.org/wikipedia/commons/2/22/Apache_Subversion_logo.svg
Code of Conduct Acknowledgment

[X] I have read and agree to the Code of Conduct.

I'm going to search a way to make an integration for this icon

Thank you.


Request to add publisher at function ReverseAmounts on table "Invoice Posting Buffer"

Describe the request
Dear team,
On table "Invoice Posting Buffer", please help to add publisher after function ReverseAmounts to have more customization on this

Thank you.
Additional context
I'd like to have more customization on this function
Internal work item: AB#548947

Hi there, Can you reply me?

Availability update: We will publish a fix for this issue in the next update for release 25.
Build ID to track: 26614.


What would CI do.md

verifying https://github.com/openshift/oadp-operator/issues/315

@openshift-ci
ci/prow/ci-index Pending — Job triggered.


Simplify flaky db-router test by reducing number of mysql units

Issue

We are deploying a HA mysql cluster for the db-router tests
We are testing no loss of data with the mysql cluster scale down in the db-router tests (where we have separate tests that test this)
The following error is likely to occur due to a race condition (deploying mysql and mysqlrouter simultaneously, router could be deployed and related to mysql before mysql is deployed)
The test on CI consistently times out after deploying keystone and waiting for the app to stabilize. We are deploying 2 units for each of the 2 keystone apps

Solution

Deploy a cluster with 1 mysql unit
Do not test the "no loss of data with the cluster scale down"
Refactor to avoid the race condition
Decrease the number of units to 1 for each of the 2 keystone apps

Release Notes
Simplify flaky db-router test by reducing number of mysql units

Have you saw any improvement here?


[DO NOT MERGE] Snappnet Build

A PR that triggers a build for the daemon with Snapps enabled.

Placeholder PR, closing.


cmake: fixed issue with invalid usage of APPLICATION_SOURCE_DIR

Fixes: #24158
The shell/fs sample was using APPLICATION_SOURCE_DIR before it has been
defined.
This has now been fixed to use the proper way of overlaying board
specific settings using boards folder.
Signed-off-by: Torsten Rasmussen<EMAIL_ADDRESS>

At what point is it safe to use that variable in an application

After the call find_package(Zephyr).

samples/sensor/sensor_shell may require a similar fix, or at least it looks weird.

what happens there is only a macro definition, and as such the APPLICATION_SOURCE_DIR is not used here.
The macro will expand at the location where it is used, and in this case that will happen after APPLICATION_SOURCE_DIR has been defined.
But this is a deprecated way, so will send a PR to update.
Thanks for spotting.


Global Scopes remain on models within testing

Laravel Version: 5.4.27
PHP Version: 7.1.0
Database Driver & Version: mysql 5.7.16

Description:
When making HTTP requests for testing as described here if your application makes use of global scopes, then the scopes will remain active outside of the application, within testing.
For example, within my application, I may want to add a global scope which restricts retrieving user modals based on a field.
I only want this scope to be added inside my application, and not outside the application (IE in the test environment).
I would expect, that after the request has finished, that global scopes that were added within the request, are removed.
Additional reasoning is that the $this->call() method in testing is emulating a Guzzle type request. If we were to actually use guzzle, the scope would never be applied in the test environment, and would only live for as long as the request took.
I'm happy to close this, is this is the intended behaviour.
Steps To Reproduce:

Within a controller, add a global scope to a modal, and add the route etc /users/{user}

public function __construct()
{
    User::addGlobalScope('username', function ($builder) {
        $builder->where('username', '=', 'phil');
    });
}

public function show($user)
{
    // The global scope should be applied because it is within the application
    var_dump((new User)->getGlobalScopes());
}

In your test, run:

function test_scopes()
{
    $response = $this->get('/users/1');

    // This shouldn't have the global scope still attached, because it is outside of
    // the application (In the test environment), but it does still have the scope attached
    var_dump((new User)->getGlobalScopes());

    // This won't work:
    User::where('username', '=', 'Brody')->first(); // Doesn't work because username=phil scope is still applied

    // Instead, you need to run:
    Model::clearBootedModels();
    User::where('username', '=', 'Brody')->first(); // Works because scope is now removed

    // or
    User::withoutGlobalScopes()->where('username', '=', 'Brody')->first();
}

My thoughts are you shouldn't need to clear global scopes within the test because they should only live within the application.

 I use global scopes on many applications and absolutely expect them to be applied while testing. If I need a case without them, they're easily removed.


Enumerated lists don't need to start with 1, however...

In the Markdown Guide, I noticed this statement:

The numbers don’t have to be in numerical order, but the list should start with the number one.

However Gruber's original syntax guide at Daring Fireball specifically says:

The point is, if you want to, you can use ordinal numbers in your ordered Markdown lists, so that
the numbers in your source match the numbers in your published HTML. But if you want to be lazy, you don't have to.

The emphasis here in both cases is mine and is key to the part that I struggle with. A numbered list in Markdown does not have to start with the number one, it just makes sense to do it that way because of how processors mangle markup languages. So somehow, the statement needs a little clarification.
This is the crux of it:

There's this whole topic of lightweight markup language processing that isn't really the point of this guide. Processors take your markup and make everything suitable for display on a web page by translating it into a real document markup language like HTML. That's why your markup is only considered "lightweight." Once server software converts your text and its markup so that it can be displayed, your stuff will break in weird ways if you don't start your enumerated lists with 1.

I'm struggling with how to add all add that to this guide and still maintain the simplicity.

Thanks for raising this as an issue! My (admittedly limited) understanding is that this is kind of a gray area. Gruber himself noted in his original design document that it's a good idea to start with the number one:

If you do use lazy list numbering, however, you should still start the list with the number 1. At some point in the future, Markdown may support starting ordered lists at an arbitrary number.

Sure enough, the Bablefish 2 tool reveals that a number of Markdown implementations start the list with the first number used. Take the following list for example:
4. hi
9. hello
1. hey

You can see the results here. CommonMark and several other implementations start the list with the <ol start="4"> tag, which means the list will start with the number four. I tested this in Dillinger (which uses a CommonMark implementation), and the list does start with the number four. The other implementations still start the list at number one.
Very confusing!
I'm not quite sure how to communicate stuff like this. I'm working on a troubleshooting section, but there are so many gray areas like this that it's probably impossible to note them all.
In this particular case, my personal opinion is that if you want the list to start with the number one, you should start the list with the number one. It's not required for all implementations, but it's a best practice that can prevent unexpected issues down the road if you move your Markdown files into another application.

Open to suggestions on this one.
FWIW, I do think the "How Does it Work?" section needs some revision. I'm also planning on adding an entire "Extended Syntax" section with information about the various lightweight markdown languages. But I don't know... maybe the markdown languages need a shoutout earlier in the guide.

Actually I think it would be immensely useful to have a gray area information even if it's only to show the most troublesome things people run into. If the list started to get obscenely long, I suppose it could always get moved to another page or something. But even if it only focused on the chief offenders for the time being, I think it would be of use.
What about keeping the comment as is right now, and then when the troubleshooting or "gray area" is created, place it at the bottom of the guide and link inline to it? Something like this...

The numbers don’t have to be in numerical order, but the list should start with the number one
(though read more about gray areas when formatting numbered lists).


chore(deps): update ci dependencies

This PR contains the following updates:

Package
Type
Update
Change

common-dev-assets

digest
5b96dd7 -> bab77a8

go (source)
toolchain
patch
1.23.0 -> 1.23.1

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

:tada: This PR is included in version 2.2.19 :tada:
The release is available on:

GitHub release
v2.2.19

Your semantic-release bot :package::rocket:


bug

Error: init chain: get chain id: Post "http://222.1********": read tcp 43.248.76.*****->222.186*******: wsarecv: An existing connection was forcibly closed by the remote host.

This is an issue associated with the swap endpoint and not related to bee. For support, please contact the relevant support channel on the Swarm discord server.


Single selection Web Views

Single Selection Support

Coverage increased (+2.8%) to 50.538% when pulling af56147afebbc033a2ae4ad43f8a9dfe3972d0c3 on single_selection into fcfd2c54582b0c623b2a1b5d1d23be1542a9a9d2 on master.

Coverage increased (+3.7%) to 51.502% when pulling 94169048ac2de5226c3cfa94ab83148e45d0a31a on single_selection into fcfd2c54582b0c623b2a1b5d1d23be1542a9a9d2 on master.

I didn't put the deprecations in place. @mtabacman we must review this changes and decide how to deprecated the old code.

Coverage increased (+6.007%) to 53.79% when pulling 1353f5ccd250803439d78336d8d6a6aef4ba91d9 on single_selection into fcfd2c54582b0c623b2a1b5d1d23be1542a9a9d2 on master.

Coverage increased (+6.03%) to 53.807% when pulling 471e963bdb82de33691fa99702303603dc5aaec2 on single_selection into fcfd2c54582b0c623b2a1b5d1d23be1542a9a9d2 on master.

Coverage increased (+6.4%) to 54.197% when pulling e47d6964a2d23628937393f8dd1e358f6029dfb1 on single_selection into fcfd2c54582b0c623b2a1b5d1d23be1542a9a9d2 on master.

Coverage increased (+7.4%) to 55.193% when pulling 340c339cb8b1dacd9ccee3d5221ce9fe8127ef38 on single_selection into fcfd2c54582b0c623b2a1b5d1d23be1542a9a9d2 on master.

Coverage increased (+7.4%) to 55.193% when pulling 4e7b54b1421388737f58bceaecd97bc8ed5b0421 on single_selection into fcfd2c54582b0c623b2a1b5d1d23be1542a9a9d2 on master.

Coverage increased (+6.5%) to 58.593% when pulling bb719a1af2f10d61af4d40c41a8589c67f414f50 on single_selection into 965637af02f8fb1ab4d12a011d628677783577fc on master.

Coverage increased (+8.7%) to 60.74% when pulling 630166c78df60a5618f5ec3a66cbcee086b85351 on single_selection into 965637af02f8fb1ab4d12a011d628677783577fc on master.


An error occurred while Rails/UniqueValidationWithoutIndex cop

Information
0.80.1 (using Parser <IP_ADDRESS>, running on ruby 2.6.3 x86_64-linux)
(Running under BitBucket-Pipeline in Ruby 2.6.3 docker image)
Error
An error occurred while Rails/UniqueValidationWithoutIndex cop was inspecting /opt/atlassian/pipelines/agent/build/app/models/user.rb:11:2.
To see the complete backtrace run rubocop -d.
1 error occurred:
An error occurred while Rails/UniqueValidationWithoutIndex cop was inspecting /opt/atlassian/pipelines/agent/build/app/models/user.rb:11:2.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
https://github.com/rubocop-hq/rubocop/issues
Mention the following information in the issue report:
0.80.1 (using Parser <IP_ADDRESS>, running on ruby 2.6.3 x86_64-linux)
Inspecting 56 files
........................................................
56 files inspected, no offenses detected

The file in error
# User of the app
class User < ApplicationRecord
  attr_writer :login # Used for devise authentication by username

  devise :invitable, :database_authenticatable,
         :recoverable, :rememberable, :trackable, :validatable,
         :confirmable, :lockable, :timeoutable, timeout_in: 2.days

  belongs_to :legacy_user, foreign_key: :id, inverse_of: :user

  validates :username, presence: true, uniqueness: { case_sensitive: false }
  validates :username, format: { with: /^[a-zA-Z0-9_\.]*$/, multiline: true }

  def login
    @login || username
  end

  def self.find_first_by_auth_conditions(warden_conditions)
    conditions = warden_conditions.dup
    login = conditions.delete(:login)
    if login.present?
      where(conditions).find_by(["lower(username) = :value ", { value: login.downcase }])
    elsif conditions[:username].nil?
      find_by(conditions)
    else
      find_by(username: conditions[:username])
    end
  end
end

Extra information
I am not able to replicate the issue on my PC (Mac OS Catalina).
Thank you

@jamesst20 Thank you for the feedback. Can you show me the backtrace of running rubocop -d?

@koic
BitBucket Pipeline didn't make it easy to copy paste hehe
https://pastebin.com/LQhyhHY3

@denny
Have same issue
0.74.0 (using Parser <IP_ADDRESS>, running on ruby 2.6.5 x86_64-linux)
Running with debug flag gives this error:
An error occurred while Rails/UniqueValidationWithoutIndex cop was inspecting /home/oleh/dev/bookstore/app/models/category.rb:4:2.
undefined method `method?' for #<RuboCop::AST::BlockNode:0x0000558992abdbe8>
Did you mean?  method
               methods

@olehvolynets Can you open a new issue with the error reproduction steps?
https://github.com/rubocop-hq/rubocop-rails/issues/new?template=bug_report.md

@koic Sorry, couldn't reproduce the error, but noticed that rubocop was outdated, so updating to 0.81.0 and rubocop-rails to 2.5 solved that error for me.
Previously had rubocop 0.74.0 and rubocop-rails 2.3.
But now have bug described in #225

I updated rubocop and still having the same error
Mention the following information in the issue report:
0.81.0 (using Parser <IP_ADDRESS>, running on ruby 2.6.3 x86_64-linux)

@jamesst20 is rubocop-rails version 2.5 ?

@olehvolynets Yes it is

RuboCop Rails 2.5.1 has been released. If the error is the same cause as #214, the issue will be resolved.
https://github.com/rubocop-hq/rubocop-rails/releases/tag/v2.5.1
If you upgrade to RuboCop Rails 2.5.1 and still get unexpected errors, please open a new issue with reproduction steps . Thank you for your feedback!

@koic
It did not fix the issue, please reopen the issue.
I already did provide the replication step: Running rubocop in a bitbucket pipeline with Ruby 2.6.3 image.
Thank you

https://github.com/rubocop-hq/rubocop-rails/issues/226


[build-script] Respect dry-run when building/testing ICU

Some shell commands when building ICU weren't using call which handles
the dry-run parameter, and were trying to execute.
NOTE: there's some invocations to xcrun inside $() which are not using
dry-run, but since those are mostly query commands, I left them alone
(they don't work on Linux, but nobody should use those code paths in
Linux).

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - aba38fbc1abaa2196c219942c342c8252cd4ff10

My fault. I don’t think I compiled with static libraries, and that variable assign didn't need the call in front. Sorry about that.

@swift-ci test

Build failed
Swift Test Linux Platform
Git Sha - aba38fbc1abaa2196c219942c342c8252cd4ff10

Build failed
Swift Test OS X Platform
Git Sha - aba38fbc1abaa2196c219942c342c8252cd4ff10

@spevans: it seems to me that the failure in Linux (an async test from XCTest) should be unrelated. It seems that my CI powers aren’t enabled yet. Could you restart it for Linux? Thanks.

@swift-ci test


Hide remote actor functionality behind "remote" feature

Closes #58
Not sure if I made all unnecessary dependencies optional, maybe you'll have some suggestions on which other dependencies can be disabled.

Actually feature = "doc" would be used by docsrs since I used all-features = true in the manifest, but I do agree doc_auto_cfg is more convenient.


Can't parse dates on .rs domains

sample code:
import whois
domain = whois.whois("domain.rs")
print(domain.creation_date)

The above code will print 'None', even though the dates are visible in the whois.
Sample of whois response:
Registration date: 01.08.2020 13:11:08
Modification date: 13.09.2021 10:05:55
Expiration date: 01.08.2022 17:19:38

I did fix it locally by addinbg a class WhoisRS to use the proper regex, but would be nice to implement in future update

can share your code about WhoisRS ?


PeppolValidationAUNZ 101 still use IReadableResource for 100

Executor set for VESID 101 still use IReadableResource for 100. Shouldnt it use 101 version?:
https://github.com/phax/ph-bdve/blob/e3b051f9ef3af8a4fc56dc455ac169c58f81bc8a/ph-bdve-peppol/src/main/java/com/helger/bdve/peppol/PeppolValidationAUNZ.java#L180-L244

You are totally right. Thanks for pointing that out

Fixed in 5.2.9 release

Thank you @phax for your quick response and release


Add commands for evaluating HelmReleases

Add commands for evaluating HelmReleases. The command can run kustomize build to locate HelmRelease and HelmRepository objects, then evaluate them with helm template. The resulting objects can also be filtered using kustomize cfg grep.

Codecov Report

Merging #12 (7209266) into main (f3b8663) will increase coverage by 8.84%.
The diff coverage is 88.65%.

@@            Coverage Diff             @@
##             main      #12      +/-   ##
==========================================
+ Coverage   69.33%   78.18%   +8.84%
==========================================
  Files           6        6
  Lines         150      220      +70
==========================================
+ Hits          104      172      +68
- Misses         46       48       +2

Impacted Files
Coverage Δ

flux_local/manifest.py
78.76% <84.84%> (+2.16%)
:arrow_up:

flux_local/helm.py
90.00% <90.00%> (+90.00%)
:arrow_up:

flux_local/kustomize.py
92.30% <91.66%> (+10.48%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


watchEffect tracks additional dependencies causing a render loop

Version
3.2.29
Reproduction link
stackblitz.com
Steps to reproduce

open the link to minimal reproduction.
open dev tools
wait for the server to start.
notice how multiple refs are tracked on top of props.msg.

What is expected?
Only props.msg should be tracked.
What is actually happening?
Refs inside vuex's mutation are getting tracked by watchEffect, which will cause the effect to trigger if any data in the store changes even though it isn't used by the watch itself. This will cause all sensible uses of vuex mutations (ones that change the state) in a watchEffect to trigger in loops.

Notes
I'm not too sure of what to expect here. To me, it's obvious that you should be able to dispatch/commit inside a watcher, but I also understand that you might want to call a local function with tracked refs as well. I think the solution should take both situations into account.
Workaround
It is possible to get a correct behavior by using watch with the { immediate: true } option, but this solution forces you to specify all of the watched refs twice which might lead to subtle bugs if they are not properly updated.

watchEffect tracks all reactive property access that happens during synchronous execution. So this is expected and can't be prevented automatically for the reasons you laid out yourself.
You can regulate what gets tracked by pushing something on a next Tick, for example:
watchEffect(async ()=> {
const msg = props.msg // sync access, tracked
await nextTick() // now we go async
store.commit('updateBiz', msg) // untracked
})

Also, it might be worth exploring wether Vuex should simply be pausing tracking altogether during mutations. That would have to be discussed in the vuex repo, though.
Also, I'm not getting your point about watch() here:

but this solution forces you to specify all of the watched refs twice which might lead to subtle bugs if they are not properly updated.

Thanks for the nextTick() trick. I'll remember that.

it might be worth exploring wether Vuex should simply be pausing tracking altogether during mutations.

Do you want me to open an issue over in the vuex repo to discuss this? I think it makes a lot of sense, and is also what I expected initially.

How do refs have to be specified twice?

Assuming that you want the same behavior to watchEffect which would track every refs automatically, it means that every ref you are using in your callback also have to be specified in the source. The equivalent call for you example would be this:
watch(
  () => props.msg,
  () => store.commit('updateBiz', props.msg),
  { immediate: true },
)

I think you can see how a larger callback, with multiple refs, would lead to more risk of mismatch with the source parameter. For smaller callbacks with a single ref, it's just more verbose so it's not too much of an issue. It is also totally fine if you're looking for a different behavior.

Do you want me to open an issue over in the vuex repo to discuss this? I think it makes a lot of sense, and is also what I expected initially.

Yes. Could be an actual bug in Vuex.

I'll close this here as the behavior is fine as far as Vue core is concerned.


update: refactor blas/ext/base/dnannsumkbn to follow current project conventions

Resolves #1479  .
Description

What is the purpose of this pull request?

refactor blas/ext/base/dnannsumkbn to follow current project conventions
Related Issues

Does this pull request have any related issues?

#1479

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

@Planeshifter @kgryte @Pranavchiku can you please review my Pr.


add advanced dependency checking (fixes #81)

completely replaced peerDependencies with check & error for missing modules.

Is it possible to add tests for these?

Hmm, since all the deps are in devDependencies I can think of no way testing this.
I would have to mock require.resolve, I think that is not possible.

Done. Used rewire instead. Only tests for a single missing dependency.


Before we get started...

I am a little concerned about the legitimacy of this project.
What happens if the website gets updated and the DOM is changed? Do we forcefully change the content of the live webpage visible to the user? This could be misleading.
I think we should serve up a static page that is only a cached copy, but clicked links would still reference the real website. This way, the data can be saved/reloaded safely and we don't risk user confusion.
Also, how do we want to save the data? Storing it on a database that is network-accessible seems intriguing, but insecure. The same problem will occur if we use HTML5/Chrome local storage. I was thinking of encrypting the data using an encryption server (per se) and store then store the encrypted data in Local Storage. This obfuscates the data so people with a data analyzer cannot see it and it keeps it local (only the public key is stored on the server).
Does this threaten the concept of the project?

I think we should save a static page, but on reloading it, it reloads from the server, becoming dynamic.
For storage, I don't see the need for a separate encryption server, especially if people want to access stored tabs offline. Also, nedb is a great database that provides a mongo like api, but is purely javascript, and can run in memory in a browser.


Multiple Displays

This is my second draft at this. The first one was way too cumbersome and didn't fit with the focus of this project. This one takes more of a library approach and involves minimal changes to the codebase here.
Goal
Provide a way to allow multiple display types to be used with slowmovie.py with the most minimal impact to the developing codebase here. The solution should be user friendly and not require end users to muck about changing python files.
Solution
I've spun off a separate repo specifically for abstracting EPD drivers for "vsmp" (very slow movie player) projects. Right now it will handle a mock display (for testing without hardware) and any Waveshare devices in the Waveshare e-Ink repo. Within the next few days I hope to add Inky displays as well, just waiting for my Inky hardware to arrive.
vsmp-epd is published to PyPi and is available as a dependency. This makes it easy to integrate with this project. You can see from the changes to slowmovie.py that it's almost a 1:1 replacement in terms of interacting with the library. The main 7.5in display from the instructions is the default but using the -e argument you can specify any compatible display.
Pros/Cons
The big pro here is this keeps all the E-ink abstraction code separate from this project. The goal here is to provide the media player, not drag along the interaction code for the displays. It also allows for specifying different display types pretty easily for the end user.
The major con is mainly Waveshare itself. Because it's not available as a pip install it will still be a manual build per the install instructions. I can include the Inky libraries as dependencies with vsmp-epd but Waveshare will need to have it's own build instructions (unless you're not using that type of display).
Fun Note: I've been running this abstraction code for 2 days now with no issues on my home display.

Just wanted to ping this PR and see if there are any thoughts on it. Is this a direction anyone is interested in this or are we pretty much just supporting the existing device (hardcoded) and directing people to roll their own via a fork if they need to do something different?
I've made some pretty good progress on the abstraction library and have basic Inky support hammered out. My plan is to reach out to a few of the known forks where people have done other devices and ask them for a little help in testing to make sure something obvious isn't being missed. Should make this a pretty robust solution.

Looks like a good way to expand display support without messing with much of the code here.
I do have one (very minor) thought. Why name the module vsmp-epd? Surely this is suitable for any e-ink project.

Seems like this would close #62

Modified per the suggestions above.
I have been thinking about the library name a bit. @missionfloyd is right - this is generally suited for any e-ink display project where you want to support multiple displays. If a rebrand is a good thought it should be done prior to merging anything into this project since it will affect naming.
Any thoughts? Something like universal-epd or abstract-epd? Naming things isn't my strong suit but I think it should be descriptive and not something random like a character name.

Maybe something like multi-epd. The multi-epd library. I think that gets across the essence of the library: supporting multiple e-paper displays in the same library.

omni-epd?

Both of those are pretty good omni sounds pretty cool so I'll run with that. I'll make the necessary changes to the library and then update this PR. So far there is support for:

The displays listed in the table
All Python libraries for the supported EPDs required as part of setup.cfg - still need to setup any OS stuff like enabling SPI manually or via scripts from implementing projects (like we have in our install.sh script)
A CLI tool vsmp-epd-test - it can write a random image or just a series of squares to your EPD to test driver functionality

I'd like to get more confirmed hardware tests but a problem occurred to me. I can find lots of forks where people have modified code to work with other displays (Inky and Waveshare). The issue is you can't send messages on Github so there isn't any way to reach out and ask them for help testing anything. If anyone has ideas on that front that would be great.

The issue is you can't send messages on Github so there isn't any way to reach out and ask them for help testing anything.

Can you add an issue on their fork explaining the situation and asking for testing?

I could be missing something, but doesn't look like you've accounted for the fact that waveshare 3-color displays take two images. and they haven't set default values (their drivers could really use some work.)
Seems like this will fail on them.

I could be missing something, but it doesn't look like you've accounted for the fact that waveshare 3-color displays take two images (their drivers could really use some work.)

@missionfloyd - Well that's not good. My oversight there. I looked at a good handful of those classes and they all appeared to be the same format. It troubled me a bit they didn't inherit methods from a parent class but thought it was just laziness on their part. Guess there was a reason for that.
Two options really that I can see:

just remove those devices from the approved list for now
create some special handling for those in the abstract class

I think it could be handled fairly well by taking the Image passed in and performing some transforms on it. It could be stripped to 3 colors (black/white/red) and then separated again so color 1 went to the black image and color 2 to the red image. The inky library does something similar for their Impression displays to convert an image to 7 colors only.  Without a device to test it on though I'd be a little apprehensive about just writing that code and calling it ready.
I created an issue for this if you want to continue this discussion there on possible solutions.

Would it still help for me to test this even thought I only have the one display?

Now that epd is in the config file, this is where the display menu I suggested for install.sh would come in.
Here's a working implementation using the names from the omni-epd readme.

This even could be taken a step further by running omni-epd-test with the selected display, and asking the user if it worked. But that might be overkill.

I moved the default waveshare device to the conf file and removed the default for -e in the main program. This should allow the user to use basically any combination of the conf file, CLI, or omni-epd.ini file to set their default. Also updated the README to add the other INI file values that could be used. I left the contrast option for now, we can always remove in another PR just to keep this from modifying too many pieces.

Looking through this I think we're ok. All major issues should be addressed.

Yup, looks good!


Tech split common package

:tada: This PR is included in version 6.68.0 :tada:
The release is available on:

v6.68.0
GitHub release

Your semantic-release bot :package::rocket:


Verbose output

Is there a way to enable more verbose output in the VSTS logs for deployments? It seems pretty sparse as of now and it would be great to see the commands that are actually executed (e.g. msdeploy.exe commands).
This is a question and/or an enhancement.

More then setting system.debug=true in the variables screen?

@jabbera, Yep, that didi it! Can I suggest adding that to the docs?
Thank you for helping and the quick reply!


Rename and publish in npm

Please, do the follow:

rename repo to karma-yatra
add version to package.json (I suppose 1.0.0 will be great)
publish in npm (npm publish in repo folder)

Thanks!

I think will be better move this repo to basis/karma-yatra? What do you mean about it?
But before publish 1.0.0 , i should fix karma with singleRun:false. Now karma-yatra doesn't work with this flag. And add unit test.

It's would be great. But you should rename it first. Than transfer the ownership to basisjs.
I don't know about problem with singleRun:false. In this mode your should press debug button in opened browser just the case. Or what do you mean?

All works good. Just i run test with flag 'autoWatch: false'. 'Press to debug' isn't necessary. If you run karma with autoWatch is enabled, Then on change test file or your code, which describe in files section of karma config, karma automatically re run all tests and print result in console.


Add files via upload

Uploaded assignment submission
PR Description

Some notes

[ ] Please make sure that you placed the files in an appropriate folder

[ ] And that the files have indicative names.

[ ] Please note that Classiq runs automatic code linting, which may minorly alter some files.

[ ] If you're familiar with pre-commit, you may run pre-commit install, and then at each commit, your files will be altered in a similar way

Your boundary conditions don't meet instructions.
Will be merged in the next version :)
Score: 7/10


Addition of footer section

Issue #586 Solved
Description
I implemented the footer section by creating JavaScript to handle the dynamic behavior and a CSS file to style the footer. The JavaScript code enables dynamic features such as displaying the current year, updating the copyright information, and providing smooth scrolling to the top of the page.
The CSS file contains the styling rules for the footer, including the layout, color scheme, font choices, and responsive design considerations. I made sure to maintain consistency with the rest of the website's visual identity.
By adding this footer section, I enhanced the overall user experience, improve the website's accessibility, and provide valuable information to the visitors.
Work
By including social media links in the footer section, I provide users with convenient and direct access to the project's social media presence. This commit contributes to enhancing the project's online visibility, fostering user engagement, and promoting effective communication with the audience.
Screenshot

Thank You!

@panwar8279  please check this commit, I have completed this work very early.

Merge conflicts are there please resolve and then make pr

Please Create new PRs for this because it contains conflict issue.


[NCL-4810] Add support for custom parameters for Gradle builds - 1.7

This reuses the CUSTOM_PME_PARAMETERS variable and is subject
for refactoring after 1.7 release.

@goldmann looks good to me, maybe @thescouser89 wants to take a look as well? Thanks!


abrupt stop

The flow app stops mostly after some time (sometimes earlier, sometimes later).
@zehortigoza Have you had the same issue?

I had some times but every-time that it happens I don't have GDB connected to debug, 99% sure that is because badly ported ISP driver.
I will try some workarounds to restart the video streaming after 2 times of the period between 2 frames.

Workaround implemented the problem is the atomisp driver, as we already have a issue on https://github.com/intel-aero/meta-intel-aero to update the atomisp driver I'm closing this issue.

Is this still being tracked? I can't find the issue in https://github.com/intel-aero/meta-intel-aero/issues

Is this still being tracked? I can't find the issue in https://github.com/intel-aero/meta-intel-aero/issues

It this one: https://github.com/intel-aero/meta-intel-aero/issues/64


Kubernetes grpc probe on kubearmor and kubearmor-relay-server

Purpose of PR?:
Fixes https://github.com/kubearmor/kubearmor-relay-server/issues/18
Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered::
I deployed the new manifest files and ensured the pods were running fine

What a wow. Commitsw are messed. I will just close this and make the change in another branch and open another PR


Add rest of sql-bindings/azure funcs logic to sql bindings ext

This PR adds remaining logic that was dependent on STS in vscode-mssql to SQL bindings extension. Now that there is a sendRequest API in mssql we can then bring over the logic for both addSQLBinding and getAzureFunctions. I also added these to our own API to be utilized as well.
For the moment I had to delete the vscode-mssql typings in order to make sure the build passes. I will be updating the vscode-mssql typings as well with the corresponding updates.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 15 (0.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.01%) to 48.02%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/sql-bindings/src/contracts/azureFunctions/azureFunctionsContracts.ts
0
5
0.0%

extensions/sql-bindings/src/services/azureFunctionsService.ts
0
10
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-bindings/src/services/azureFunctionsService.ts
1
0%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
15009

Relevant Lines:
29640

💛  - Coveralls


AKS authorized ip ranges does not mention devops environments

Unless I am mistaken, restricting the ip ranges will prevent azure devops environments to connect to the cluster:

This scenario does not seem to be talked about in the documentation.
Are there any ways to make environments still work in such a setup? Perhaps by using some kind of agent pushing the data instead or re-using an hosted vsts agent?

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

ID: 660320d4-fad5-3307-e29f-5f4cfad4b7f7
Version Independent ID: 85ac2e8b-633f-6e1a-e642-0645ca92e129
Content: API server authorized IP ranges in Azure Kubernetes Service (AKS) - Azure Kubernetes Service
Content Source: articles/aks/api-server-authorized-ip-ranges.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

@jemag Thank you for your feedback! We will review and provide an update as appropriate.

@MicrosoftDocs/aks-pm Please add your comments.

@jemag Once we enable the authorized ip ranges, Then it will allow only the ips added to that.
So it restricts other environments to connect.  For example , for the azure pipelines to connect, We need to add the ips of pipelines for that regions to the authorized ip ranges.
problem is that those ips may change on weekly basis.
Lets wait for the comments from the aks-pm team.

@jemag Only way is to add the ips used by the azure pipelines of that region to the authorized ips list.
Also we need to update the ips when it changes for that region.
Please provide a feedback here for improvement.
Community can vote on this feedback and product teams will look into this items to build their backlog

@jakaruna-MSFT that seems quite unfortunate if this is the only option. With authorized IP ranges and now Private API Server in preview, it seems like there should be a better way to handle this.
Having a Private API Server would be inconvenient with the current Environments requirements. Anyway, thanks for the clarification I will try to create a feedback post a suggested.

@jakaruna-MSFT just to be sure, the link you provided is for AKS feedback, wouldn't it be more appropriate to leave the feedback for azure devops instead? Since environments is purely a devops concept.

You can submit feedback in azure devops as well.
It would be easier to add "allow Azure devops" as one of the rule in Authorized ip ranges.

I have added this thread for review with Product team

Adding the devops feedback url, for those who come by this issue: https://developercommunity.visualstudio.com/idea/947371/allow-devops-environments-communication-with-prote.html

@jemag
I will close this out for now. If you need additional help please open a new issue.

i faced similar issue today with AKS+Azure DevOps pipeline that AzureDevOps cannot connect to AKS with Authorized Ips even with correct IP regions ,, and we were able to solve by adding following Azure CLI task
i added the outbound IPs also the regions Ips for india central and south india incase
but most important is the agent Ip
in the Azure Dev Ops :
Task 1: add the MS hosted Ips
IP=($(curl -s http://ipinfo.io/json | jq '.ip' | sed -e 's/^"//' -e 's/"$//'))
echo "This Microsoft hosted agent public IP is: $IP"
echo "##vso[task.setvariable variable=AGENT_IP;]$IP "
az aks update --resource-group myResourceGroup --name myAKSCluster  --api-server-authorized-ip-ranges "<IP_ADDRESS>/24,<IP_ADDRESS>/24,<IP_ADDRESS>/24,<IP_ADDRESS>/24, <IP_ADDRESS>/24, $IP"
Task 2: remove only the Agent Ip
az aks update
--resource-group myResourceGroup
--name myAKSCluster
--api-server-authorized-ip-ranges  "<IP_ADDRESS>/24,<IP_ADDRESS>/24,<IP_ADDRESS>/24,<IP_ADDRESS>/24,<IP_ADDRESS>/24"
hope this helps


Read only mode when select is disabled

Is there read only mode when <select> element is disabled?

I would also like a read-only mode. But the lack of response to your question left me hopeless.


Py38 compatible

Tested os cached and device login methods on py 3.8 and 3.10 and they work. Had to get rid of some things that do not exists in old things. test.py probably can be improved significantly.

Took care of this out of band


Giving skulls

Here's a little testing script giving a decorated player skull. Doing this works just fine
SkullCommand:
  type: world
  speed: 0
  debug: false
  events:
    on newskull command:
    - execute as_player 'give @p skull 1 3 {display:{Name:"Hamburger"},SkullOwner:{Id:"f597e06f-e01a-492d-b63f-c23b9809ce01",Properties:{textures:[{Value:"eyJ0ZXh0dXJlcyI6eyJTS0lOIjp7InVybCI6Imh0dHA6Ly90ZXh0dXJlcy5taW5lY3JhZnQubmV0L3RleHR1cmUvYzVlMjc5ODhhNjUzODAxMGVmYzBlMjQ3NTZiYzNlM2VlYTI0ZDc1MzZiMjA5MzJjMTdlMDQwNGU1Y2M1NWYifX19"}]}}}'

Now, holding that item you can check the details and it appears to report correctly
/ex narrate <player.item_in_hand>
But using the give command throws an error
/ex give <player.item_in_hand>

@Morphan1 :(

It looks like it's just failing the skin lookup....does this error happen every time?

yerp. I'm also on a bungee server, so idk if the fact that the server is in offline mode makes things go bonkers.

That shouldn't matter. I remember using dScript pokeballs on the dServer
I'll look into it... Maybe something internal changed

Oh yeah, you did do that.

Actually, why don't item script containers have the options to set skull skins natively?

Eh... here's yet another example.
Can't even adjust the damn thing :/

Seems to be working now with developmental builds, though some errors still persists... namely an error occurring from too many lookups.

576c32e


Mac Keybase Update: Version 5.2.1-... Stuck in install loop

On my Mac (10.15.3), I see the following behavior:

Keybase notifies me of an update via a dialog. If I accept by clicking Update, the dialog disappears giving no visual indication of success or failure.
Roughly a day later I am prompted again to install the same update, ad infinitum.

Version is: Keybase Update: Version 5.2.1-20200225174716+9845113a89

Hey @reub can you run keybase log send and post the ID here?

Thanks! Here you are: 05540f3ddc3d9a4a6cd99f1c

@reub To get you of this loop can you try running keybase install --components=app

Thanks. Unfortunately I receive the following error trying to do this:
 $ keybase install --components=app ▶ INFO Install app bundle ▶ ERROR Error installing app bundle: exit status 8
I've uploaded a fresh log with id: 6c096472798e48bb06272a1c

Great thanks for this. Interestingly enough I'm writing from a machine on the same client version as you experiencing the same issue. Should be able to resolve it shortly and get back to you.
Thanks for the fast replies. I'll keep you posted.


✨ Filter-search for services by name

There can be many services, and each service takes up a lot of space. This can make it difficult to find the right service. At the same time, there is a free space next to the "Services" heading. We can place a text input there and show only those services whose name contains the substring entered in this input.

Is this free space available in the mobile version? maybe it's better to wait for the layout figma?

@VladislavBobyrev, now our layout is a draft. The main thing is to add the necessary functionality. As a user of Passcryptum, I consider service filtering to be necessary.


Allow to open all files at once from quick open

Issue Type: Feature Request
When searching for a file (Ctrl+P), it would be nice if there was a way to open all files in one step.
Especially in a workspace, I often find myself looking for an approach to this.

VS Code version: Code 1.21.1 (79b44aa704ce542d8ca4a3cc44cfca566e7720f1, 2018-03-14T14:46:47.128Z)
OS version: Windows_NT x64 10.0.16299

You can probably achieve this with extension:
https://marketplace.visualstudio.com/items?itemName=fabiospampinato.vscode-open-multiple-files

A quick repetition of hitting the Right Arrow and Down Arrow keys also works quite well.


Change of focus state in inputs

We changed the focus state in form component to 2px blue border, check the specs in Zeplin.
https://zpl.io/aRYpZnz
Also for those components:

Input
Textarea
Select
Checkbox / Radio
File input

Preview

Should we update all form components in one iteration? Textarea and InputField are not still implemented. cc @darkwindcz

Is it still required ? I think #303 solved this cc @wEprous @williamkolmacka

Yes, solved in #303


Improve testing to cover api fn calls

In order to resolve some open issues with confidence in not breaking the library, we need to instrument the api call parts of the library with tests.
See issues: https://github.com/fti-technology/node-skytap/issues/9, https://github.com/fti-technology/node-skytap/issues/5, https://github.com/fti-technology/node-skytap/issues/12
I suggest we use nock, as we can test our api calls without modifying library code by hooking into node's http lib directly.
See a sample change here: https://github.com/ftikbogle/node-skytap/blob/MockTests/test/skytap.js

Added some more examples of nock tests:
https://github.com/fti-technology/node-skytap/compare/master...ftikbogle:0ffeb7e106903449d7aac0903f75e0dbfd797596
After using this a bit, I feel like this may be able to be simplified a lot. We don't really care about the content of the response, as we're just passing it directly onto the consumer. I think I'll work on another revision that simplifies these calls quite a bit.
I think we only care about:

The requests are actually called (automatically verify with nock.done())
The request had it's body set correctly (we can just feed these through to the api call)
The request had it's parameters (if any) sent correctly
There is some sort of response (but we don't care about the content)

Yeah that sounds perfect.

Already found a bug while implementing nock tests: https://github.com/fti-technology/node-skytap/pull/13

Work on this is ongoing in the testing branch: https://github.com/fti-technology/node-skytap/compare/master...ftikbogle:MockTests


Create folder for the folder structure for each trial

In the documentation folder, add the sample folder structure for each trial, so the user could know the upload folder structure.

Done


Doc typo: NormalizeSeparators page - Ignored sections example typo

Doc uses 'sections' but example incorrectly uses 'section':
Ignored sections
You can decide which sections should be transformed by configuring
sections = comments,settings,variables,keywords,testcases param:
robotidy --configure NormalizeSeparators:section=variables src
.....................................................................^^^^

Thanks! Since this kind of typo is not the first time I need to think of a way to avoid such problems. For example we can test the examples provided in the documentation - gather all configuration/run examples and run them in an isolated environment and check return status. Probably it'll take a bit more time than it's worth but it sounds interesting, I will think about it and open a new issue for it if needed.


Python - Get Started phase 1 links update

Description
The links within Phase 1 of the Python Get Started article currently get a 404 - page not found. This PR updates the links to the correct file path.
Type of change
The current links have /azure/developer/ in the path.  This PR corrects the path by removing /azure/developer/ and replacing it with /articles/
Testing
Verified that each link works via manually clicking each link

@kingralph33,
Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request.
Thanks!

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@kingralph33 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree

@bobtabor-msft
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.

@kingralph33 Thank you for your submission. I just tested this on several browsers and the URLs work fine. Can you send me the full URL you are trying to access (after our servers redirect you based on your language-country)?

@kingralph33 Thank you for your submission. I just tested this on several browsers and the URLs work fine. Can you send me the full URL you are trying to access (after our servers redirect you based on your language-country)?

@bobtabor-msft Here are the links I get when I click on Phase 1 parts on Azure Dev Docs for Python :
Part 1 - https://github.com/MicrosoftDocs/azure-dev-docs/blob/main/azure/developer/intro/azure-developer-overview
Part 2 - https://github.com/MicrosoftDocs/azure-dev-docs/blob/main/azure/developer/intro/azure-developer-key-services
Part 3 - https://github.com/MicrosoftDocs/azure-dev-docs/blob/main/azure/developer/intro/hosting-apps-on-azure
Part 4 - https://github.com/MicrosoftDocs/azure-dev-docs/blob/main/azure/developer/intro/connect-to-azure-services
Part 5 - https://github.com/MicrosoftDocs/azure-dev-docs/blob/main/azure/developer/intro/azure-developer-create-resources
Part 6 - https://github.com/MicrosoftDocs/azure-dev-docs/blob/main/azure/developer/intro/azure-developer-key-concepts
Part 7 - https://github.com/MicrosoftDocs/azure-dev-docs/blob/main/azure/developer/intro/azure-developer-billing
Part 8 - https://github.com/MicrosoftDocs/azure-dev-docs/blob/main/azure/developer/intro/azure-service-sdk-tool-versioning

@kingralph33 Thank you, I see where the disconnect is. These pages are not intended to be consumed on GitHub. Rather, they get transformed and built into learn.microsoft.com articles. So, for example, this is the ACTUAL RENDERED page you have requested to change:
https://learn.microsoft.com/en-us/azure/developer/python/get-started
If you click through the links, they all work because the file location on the hard drive (or in GitHub) do not determine the URL.
So, I appreciate your submission, but this works as intended currently. Thank you!


fix dim change when no layers

Description
This PR fixes a bug that prevented the dims model from reseting to its default values when no layers are present. It lead to weird / confusing behaviour where you could add a 4D image, get 2 dims sliders present, deleted the 4D image, still have the two sliders present, add a new 2D image and still have the two sliders present, which I think was quite strange.
Now when there are no layers present, the ndim will return to 2 and no sliders will be present.
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

How has this been tested?

[x] I've added a test for this inside the viewer model tests

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works

Good catch @sofroniewn !

@jni I have consolidate this function - it didn't end up saving too much code as I had to deal with the special case of inserting a new axis and reseting an existing one separately. Let me know if you think the implementation can improve, otherwise feel free to merge once the tests pass

Once again: nice pre-emptive debugging! I just ran into this bug:
import napari
import numpy as np

with napari.gui_qt():
    viewer = napari.view_image(np.random.random((51, 5, 2, 196, 171)),
                               name='mitosis')
    viewer.layers.remove('mitosis')
    viewer.add_image(np.random.random((10, 256, 256, 256)), name='blobs')

results in:
 $ python test-remove.py
Traceback (most recent call last):
  File "test-remove.py", line 9, in <module>
    viewer.add_image(np.random.random((10, 256, 256, 256)), name='blobs')
  File "/Users/jni/projects/napari/napari/components/viewer_model.py", line 479, in add_image
    self.add_layer(layer)
  File "/Users/jni/projects/napari/napari/components/viewer_model.py", line 384, in add_layer
    self.layers.append(layer)
  File "/Users/jni/projects/napari/napari/util/list/_model.py", line 56, in append
    self.events.added(item=object, index=len(self) - 1)
  File "/Users/jni/projects/napari/napari/util/event.py", line 508, in __call__
    self._invoke_callback(cb, event)
  File "/Users/jni/projects/napari/napari/util/event.py", line 529, in _invoke_callback
    cb_event=(cb, event),
  File "/Users/jni/projects/napari/napari/util/event.py", line 523, in _invoke_callback
    cb(event)
  File "/Users/jni/projects/napari/napari/components/viewer_model.py", line 94, in <lambda>
    self.layers.events.added.connect(lambda e: self._update_grid())
  File "/Users/jni/projects/napari/napari/components/viewer_model.py", line 1193, in _update_grid
    stride=self.grid_stride,
  File "/Users/jni/projects/napari/napari/components/viewer_model.py", line 1180, in grid_view
    self._subplot(layer, (i_row, i_column))
  File "/Users/jni/projects/napari/napari/components/viewer_model.py", line 1208, in _subplot
    scene_size, corner = self._scene_shape()
  File "/Users/jni/projects/napari/napari/components/viewer_model.py", line 263, in _scene_shape
    size = [size[i] for i in self.dims.displayed]
  File "/Users/jni/projects/napari/napari/components/viewer_model.py", line 263, in <listcomp>
    size = [size[i] for i in self.dims.displayed]
IndexError: index 4 is out of bounds for axis 0 with size 4

This PR fixes it. I think there's probably improvements to be had in this code, but since I'm a little swamped and it fixes a significant bug (currently, a viewer cannot be safely "reused"), I'm just going to merge, and leave improvements for later PRs.

Also: man, writing documentation is the best way to fix bugs. I've been writing this blog post for the best part of a month and keep running into stuff I want to fix before publishing it. :joy: Almost there! 🤞


After effect features are not animated properly

Tell us about your environment mac os x 10.11.6 (15G1510)

Browser and Browser Version: N/A - problem is not browser related
After Effects Version: 2017 CC

What did you do? Please explain the steps you took before you encountered the problem. tried to export an after effects project by bodymovin
What did you expect to happen? export the after effect project by bodmovin
What actually happened? Please include as much relevant detail as possible. some of the letters what were intended to animate (moving along a path) were just appear while others were animated properly, the timing of the effects in the exported result at preview was wrong (delayed vs. original timing)
Please provide a download link to the After Effects file that demonstrates the problem. https://drive.google.com/open?id=0B-6XiRhUIggYNTZPR01JLVU3b3M
Csongvai Roland Logo Sliced final.aep.zip

Apparently using an expression that point to a different composition uses the property's expression time instead of the comp's time.
I need to work on this since it's not a simple fix.
Can you use valueAtTime?

Thank You for Your response. What do You mean under valueAtTime?

for example in your composition "o 2", on layer "o 1", instead of using
FM_controllerLayer.effect("Gilbert Controller")("Color 3")
use
FM_controllerLayer.effect("Gilbert Controller")("Color 3").valueAtTime(time)
but I see there's too many of them.


Extensions shows a blank white window

I have recently noticed, that (disabling extensions until I found it is this one), that as soon as I enable it, I get and extra blank white window showing

Not sure what may be causing this (I have uninstalled, reinstalled but it is still there)
Using a window finder utility, Winspector, it seems to be around all of vscode (over my 2 screens)...

I think it's related to a recent update of the "Test Adapter Converter" extension, which Karma Test Explorer depends on. That's where I ended up after an extension bisect and that extension just had a new release while Karma Test Explorer hasn't.

Thanks for that, I have logged the same thing at the extension you mention above (we also get it on another developers machine)

I have the same issue. I didn't notice your issue report at first.

To anyone fixing this; there's some more information from me in https://github.com/lucono/karma-test-explorer/issues/95.

I'm having the same issue...

I tried downgrade test ui explorer, karma test explorer and the test adapter to the oldest version of it that still works with my tests
And it still shows the blank page as soon as it loads the tests.
So i think it probably was caused by a vs code update and not an extension update.


vulkan-validation-layers: fix cross compilation, set strictDeps

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

@ofborg build pkgsCross.aarch64-multiplatform.vulkan-validation-layers

Result of nixpkgs-review pr 345304 run on x86_64-linux 1

5 packages built:

cosmic-store
google-amber
hyperspeedcube
vulkan-validation-layers
vulkan-validation-layers.debug


doc_id missing from source_nodes in GPTQdrantIndex queries

If I query against GPTSimpleVectorIndex, the response has source nodes that can be looked at to determine the original document id. Very useful behavior.
If I query against GPTQdrantIndex, source nodes don't have this information.
Looking at the GPTQdrant index creation code, doc_id seems to enter the index as payload though.
Problem is Probably here
@dataclass
class SourceNode(DataClassJsonMixin):
    """Source node.

    User-facing class containing the source text and the corresponding document id.

    """

    source_text: str
    doc_id: Optional[str]
    extra_info: Optional[Dict[str, Any]] = None
    node_info: Optional[Dict[str, Any]] = None

    # distance score between node and query, if applicable
    similarity: Optional[float] = None

    @classmethod
    def from_node(cls, node: Node, similarity: Optional[float] = None) -> "SourceNode":
        """Create a SourceNode from a Node."""
        from IPython import embed; embed()
        return cls(
            source_text=node.get_text(),
            doc_id=node.ref_doc_id,
            extra_info=node.extra_info,
            node_info=node.node_info,
            similarity=similarity,
        )

doc_id  looks for ref_doc_id
Why does the behavior differ between indexes?

@kacperlukawski are you able to help with this by any chance? Actually I took a look at GPTQdrantIndexQuery and I think it's a matter of swapping
node = Node(
    doc_id=payload.get("doc_id"),
    text=payload.get("text"),
)

for
node = Node(
      ref_doc_id=payload.get("doc_id"),
      text=payload.get("text"),
 )

That seems to be it! I made a small PR :)

thanks @Mikkolehtimaki !!

@jerryjliu seems that this bug is back in the latest version of gpt/llama-index.


CiliumNetworkPolicy FQDN egress not working

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I was trying to implement the FQDN feature of CiliumNetworkPolicy but it's not working for some reason. I tried many things but for the sake of reproduction, let's use the blog from cilium team directly.
Reproduction steps

Create a kind clustercurl -LO https://raw.githubusercontent.com/cilium/cilium/1.12.5/Documentation/gettingstarted/kind-config.yaml
kind create cluster --config=kind-config.yaml

Create deployments & serviceskubectl create ns empire
kubectl apply -n empire -f https://raw.githubusercontent.com/cilium/cilium/v1.2.2/examples/minikube/http-sw-app.yaml

Apply cilium network policy allowing dns resolutioncat <<EOF | kubectl apply -n empire -f -
apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
  name: "allow-within-namespace"
specs:
  - endpointSelector:
      matchLabels: {}
    egress:
    - toEndpoints:
      - matchLabels:
          "k8s:io.kubernetes.pod.namespace": empire
    ingress:
    - fromEndpoints:
      - matchLabels:
          "k8s:io.kubernetes.pod.namespace": empire
  - endpointSelector:
      matchLabels: {}
    egress:
    - toEndpoints:
      - matchLabels:
          "k8s:io.kubernetes.pod.namespace": kube-system
          "k8s:k8s-app": kube-dns
EOF

Test for dns connectivity & it's successfulkubectl exec -it tiefighter -- curl deathstar.empire.svc.cluster.local/v1

Add an additional rule for outbound traffic to cilium.iocat <<EOF | kubectl apply -n empire -f -
apiVersion: "cilium.io/v2"
kind: CiliumNetworkPolicy
metadata:
  name: "allow-within-namespace"
specs:
  - endpointSelector:
      matchLabels: {}
    egress:
    - toEndpoints:
      - matchLabels:
          "k8s:io.kubernetes.pod.namespace": empire
    ingress:
    - fromEndpoints:
      - matchLabels:
          "k8s:io.kubernetes.pod.namespace": empire
  - endpointSelector:
      matchLabels: {}
    egress:
    - toEndpoints:
      - matchLabels:
          "k8s:io.kubernetes.pod.namespace": kube-system
          "k8s:k8s-app": kube-dns
  - endpointSelector:
      matchLabels: {}
    egress:
    - toFQDNs:
        - matchName: "cilium.io"
EOF

Test for connectivity
6.1 Test for internal DNS resolution - works
     kubectl exec -it tiefighter -- curl deathstar.empire.svc.cluster.local/v1
6.2 Test for external DNS resolution - works
     kubectl exec -it tiefighter -- nslookup cilium.io <IP_ADDRESS>
6.3 Test to curl the endpoint - doesn't work
     kubectl exec -it tiefighter -- curl cilium.io
For some reason, cilium fqdn list is empty. Not sure if that's something related to this issue but nevertheless, I tried it.POD_NAME=$(kubectl get po -n kube-system -l k8s-app=cilium<EMAIL_ADDRESS>kubectl exec -n kube-system -it $POD_NAME -- cilium fqdn names

Tried debugging a with cilium observe, cilium endpoint list, etc but no information.
Cilium Version
1.12.2
Kernel Version
Darwin laptop 21.6.0 Darwin Kernel Version 21.6.0: root:xnu-8020.240.7~1/RELEASE_ARM64_T6000 arm64
Kubernetes Version
1.25
Sysdump
cilium-sysdump-20221229-094847.zip
Relevant log output
No response
Anything else?
No response
Code of Conduct

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

I have the same issue.

@squeed @gandro @tommyp1ckles

@rewanthtammana Please don't ping arbitrary people to get attention. You've opened this issue in between Christmas and New Year so a bit of delay is only expected.

I tried many things but for the sake of reproduction, let's use the blog from cilium team directly.

Whoah, that blog post is 4+ years old. Cilium was a baby back then :smile_cat:
Have you tried following the official guide for FQDN policies? In particular, the policy you cited is missing the dns rule (which I'm guessing wasn't required back then) so that won't work.

I also tried the official guide for FQDN policies but still it doesn't work! Attaching screenshot for reference

Could you share a sysdump with that last policy loaded? 🙏

PFA sysdump
cilium-sysdump-20230106-121312.zip

Nothing I can think of

Are you able to establish a connection over 8472/udp between two nodes in the cluster with e.g. netcat?

Yes, it's working.

How did you install Cilium?
Is connectivity working for any pod-to-pod across nodes? Maybe it's just the health checks that are failing :thinking:

It's been a while, so I don't remember exactly but I'm presuming I installed cilium with helm charts.
I created a new pod with labels different from the ciliumnetworkpolicy selectors & the connection seem to be working.

Are the two pods on different nodes? If you try to resolve domain names from that client pod multiple times, does it always work?

Yes, they are on different nodes. The nginx pod I created is on kubernetes1.25-worker. The debug container I created for testing is on kubernetes1.25-worker3. The mediabot with ciliumnetworkpolicy is on kubernetes1.25-worker2.

cilium-health status in the Cilium agent pods

I exec into one of the cilium pods in kube-system namespace & I see some endpoint connectivity errors here for control plane & two worker nodes. For third worker node, it's okay.

Sorry, missed your answer here. Looking at the health checks here, it looks like all pod-to-pod connectivity across nodes is affected. So this is likely not specific to the FQDN policies. I would check that there are no firewall rules blocking VXLAN. The required ports are documented at https://docs.cilium.io/en/stable/operations/system_requirements/.


Beta d3 SelectAll

Data Visualization with D3: Select a Group of Elements with D3

http://beta.freecodecamp.com/en/challenges/data-visualization-with-d3/select-a-group-of-elements-with-d3
Issue Description

Code to solution doesn't show on screen until user clicks submit. This functionality is different from previous exercises where the output from your code appears before submit.
Browser Information

Browser Name, Version: Chrome.
Operating System: Mac
Mobile, Desktop, or Tablet: Desktop

Your Code

Screenshot

Untitled
Ellieedds was born with me know thanks to work at five people that want
your phone number
On Jan 31, 2017 12:12 PM, "Benjamin Schachter"<EMAIL_ADDRESS>wrote:

Data Visualization with D3: Select a Group of Elements with D3
http://beta.freecodecamp.com/en/challenges/data-
visualization-with-d3/select-a-group-of-elements-with-d3
Issue Description
Code to solution doesn't show on screen until user clicks submit. This
functionality is different from previous exercises where the output from
your code appears before submit.
Browser Information

Browser Name, Version: Chrome.
Operating System: Mac
Mobile, Desktop, or Tablet: Desktop

Your Code
Screenshot
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/13006, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AQcrZAzEH1glSJA6qq1FWNS--1T0zifMks5rX2ttgaJpZM4Ly6Ey
.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain funtasticlabs.com has exceeded the max emails per hour (110/100 (110%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from mailin-01.elitehosts.com ([<IP_ADDRESS>]:60214 helo=offsite.elitehosts.com)
by neo.internetwebserver.net with esmtp (Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1dnx3G-0003TA-1G
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:16:46 -0400
Received: from o1.sgmail.github.com ([<IP_ADDRESS>]:28686)
by offsite.elitehosts.com with esmtp (Exim 4.69)
(envelope-from<EMAIL_ADDRESS>id 1dnx38-0001sz-QQ
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:16:39 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=T5E4KIs1VEu5J03IVWrxyY9eJbc=; b=qJRGWgccp3ZITf2h
iiIUbFV8t/iByZajafCjved7XK0y7U0tqpasEBBL7P2hwfWkF/x5LjCOxw2lFCsi
XfMA00+7RO3KNgT5Ujddu1FBX+rZ4n18U4lM8Zlc/qcUr+RfmRYnB3DO7r8m/p6b
YKZ8viKd0HFsIgfcwBA9koJpoEo=
Received: by filter0102p1las1.sendgrid.net with SMTP id filter0102p1las1-20807-59AA0675-2F
2017-09-02 01:16:37.832084994 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id fHvWEvYyQBqxlpIXOHcnxA
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 01:16:37.725 +0000 (UTC)
Date: Sat, 02 Sep 2017 01:16:37 +0000 (UTC)
From: Quincy Larson<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Beta d3 SelectAll (#13006)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59aa06707185_34ef3f9a441c3c3416073e";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: QuincyLarson
X-GitHub-Recipient: manzilo
X-GitHub-Reason: subscribed
List-ID: freeCodeCamp/freeCodeCamp <freeCodeCamp.freeCodeCamp.github.com>
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AL1KCn3Z1XGcyzWwLllVltah1CmkDhgHks5seKxwgaJpZM4Ly6Ey
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: 83UmH9Yz2HjU1qKK7JE10vR6ZA73mzRCr3l9ny8S/eH9GLHJlsS+silTns8Vg6NJyxPywPXVc6qQEp
P/I5yDatVDmeRctdgGt745ZStq+MPz0KNmgYzQinLofDDg9AjfJ8FLUv0ukY+TGldggTpSBmZe9XzZ
VNShYVd96npHb7W0SfXPNWgbzD0C5Iuh2nOMFe7xQHm8AFHhTsLuOQxGSSvabNIZ/rRU1M+peAs3Mn
Q=
X-MAILIN-01-MailScanner-Information: Please contact the ISP for more information
X-MAILIN-01-MailScanner-ID: 1dnx38-0001sz-QQ
X-MAILIN-01-MailScanner: Found to be clean
X-MAILIN-01-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=1.584, required 10, AWL -3.12, BAYES_00 -1.90,
HTML_IMAGE_ONLY_24 1.62, HTML_MESSAGE 0.00, KHOP_THREADED -1.50,
PYZOR_CHECK 6.50, SPF_PASS -0.00, T_RP_MATCHES_RCVD -0.01,
URIBL_BLOCKED 0.00)
X-Spam-Level: *
X-MailScanner-From<EMAIL_ADDRESS>X-Spam-Status: No
----==_mimepart_59aa06707185_34ef3f9a441c3c3416073e
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #13006.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/freeCodeCamp/freeCodeCamp/issues/13006#event-1232190150
----==_mimepart_59aa06707185_34ef3f9a441c3c3416073e
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #13006.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/freeCodeCamp/freeCodeCamp","title":"freeCodeCamp/freeCodeCamp","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/freeCodeCamp/freeCodeCamp"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Closed #13006."}],"action":{"name":"View Issue","url":"https://github.com/freeCodeCamp/freeCodeCamp/issues/13006#event-1232190150"}}}
----==_mimepart_59aa06707185_34ef3f9a441c3c3416073e--

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain oss-india.net has exceeded the max emails per hour (110/100 (110%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from mail-oi0-f52.google.com ([<IP_ADDRESS>]:32890)
by server14.hostingraja.in with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.89)
(envelope-from<EMAIL_ADDRESS>id 1dnx41-003myF-Id
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 06:48:04 +0530
Received: by mail-oi0-f52.google.com with SMTP id r203so13972357oih.0
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 18:17:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:delivered-to:dkim-signature:dkim-signature:date
:from:reply-to:to:cc:message-id:in-reply-to:references:subject
:mime-version:content-transfer-encoding:precedence:list-id
:list-archive:list-post:list-unsubscribe;
bh=reNpybDYNJNYav8f2pMA+AlXy7j93ZFq5u8BAWcKLyc=;
b=j7spEKpQV1v/bBbIwWvVOvCA+OeAKialEGZMdAS3IIKxwFY0COJueVA81M70xsUtmS
fYVixxNzBsUm82HuV8vHN2+7WvCjRiUnNlTuhViVcQj3n2fpbJOaFs7ia3i99iuJaYm2
AkvqMXOHbogO043mDURwStVHXOc3/lNwB5uN0P4edavSxfePoyDBAEVrwS74ZZ7C99yc
BHDg7Jmlv9Omi4PcrJ/f76PyhzrQeyVb9zkp0Db2TjNErVizx6OxEs/7xtJ6dOmlCH5f
ZeO5VxmL2zUdjuddBiX9cWJtjHPv0AhKlLQaTMAGIFdpqeoaOWcvGUixWS5Qso1g/x7a
qRgg==
X-Gm-Message-State: AHPjjUjfRLWh6mFQUBEWiMlIeUyPoLL04YKXyp/CXr8tCSANGK+KIVNT
ADDxHqDR5cq8CrIH/9qfCkxQtXf/rOjlD1r9erxVuQ==
X-Received: by <IP_ADDRESS> with SMTP id h12mr4144347oib.35.1504315011293;
Fri, 01 Sep 2017 18:16:51 -0700 (PDT)
X-Forwarded-To<EMAIL_ADDRESS>X-Forwarded-For<EMAIL_ADDRESS><EMAIL_ADDRESS>Delivered-To<EMAIL_ADDRESS>Received: by <IP_ADDRESS> with SMTP id q13csp1352945ofe;
Fri, 1 Sep 2017 18:16:50 -0700 (PDT)
X-Google-Smtp-Source: ADKCNb5sQap9h1Ir0e9tESsJOpFoxq2JXOGkvgcqdPZE5Ynz8X1H9aYA5Sv0GzPZep3Y9IUaiQIA
X-Received: by <IP_ADDRESS> with SMTP id 90mr2806391pld.195.1504315010559;
Fri, 01 Sep 2017 18:16:50 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1504315010; cv=none;
d=google.com; s=arc-20160816;
b=E12L25MYOqH+nr0jcTuGVyDaFkmLKV5vn5dpe/47QfiMmXz/NdPrPwEJMYSv6s0Z+H
hX5nnlVWButQGJ6I3K8SvIvElImkruwU9vvznVUW0MwNgbx2Sr3S+E7P/y/IqSsmGYHr
bMJl4yrSCEkFfFS/C/l3mX0hFf6/+puM+hHE7DxsMvRc7oEWvCDNTKiW23bzgnPVY04M
YbtorfYYeIZa91dJWRelxniVwrL7z0M/J4LoZZ8ZQUiRz6TZYmKvLJ7+VDwz87qeYCja
Jf4wYbqMUKlpKWI8B0BD3Z30giFKeMfbq2EvDqMH4xKfClEcLUQ+vGNi+v6XZyn4na1H
l5iA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=list-unsubscribe:list-post:list-archive:list-id:precedence
:content-transfer-encoding:mime-version:subject:references
:in-reply-to:message-id:cc:to:reply-to:from:date:dkim-signature
:dkim-signature:arc-authentication-results;
bh=reNpybDYNJNYav8f2pMA+AlXy7j93ZFq5u8BAWcKLyc=;
b=Y9WW2Z6pKjNFtKxvIm645qogrwCJvJ3BpiXWCyV020fmYkqmwFi6zk/KhACC3cnFAd
NwT5YjvysAZ8rdwAwjuCumNbbbsgR6MQT8GK0nguc+wjMEpURTRU3gKTyqY1NpxLMl5q
qEsfuh3G+L3LDbt4iHmYuOi5b1h9lgGGDU9enW1dUV3Cy1QjaQowSztdkDGnscmRqzm1
2hTmCG2yNeaqaOgQFaZRleApdfznOPX+yOCsXWCaKOssAjLmCda2rmcVGz3xlFjzm7+l
IaaKlm9oGG6ZypMMOtKt7SKwCC05STutk5AYLn/rhYiJfaVPc/QlzZSWxQ54cNK6Kkcj
oiQA==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass<EMAIL_ADDRESS>header.s=s20150108 header.b=ktCzhN9O;
dkim=pass<EMAIL_ADDRESS>header.s=smtpapi header.b=xgjljjz7;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
Received: from o6.sgmail.github.com (o6.sgmail.github.com. [<IP_ADDRESS>])
by mx.google.com with ESMTPS id 4si1053461pgc.347.2<IP_ADDRESS>.16.50
for<EMAIL_ADDRESS>(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 01 Sep 2017 18:16:50 -0700 (PDT)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
dkim=pass<EMAIL_ADDRESS>header.s=s20150108 header.b=ktCzhN9O;
dkim=pass<EMAIL_ADDRESS>header.s=smtpapi header.b=xgjljjz7;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=BzD77mt7sqMcZdgGEsUFwTbF23Y=; b=ktCzhN9O3JEnENF7
+Rxi1XmwrCtfYmZZZ4gMWrDRvA5o8w0nWhdcN4fRJkkv3jsfigTI9ol9FQrEDacd
pxf257oRSJTqa9sW4dircwNpJ0UVFKGI2Zt4DR5Ps/6b+bTSuz2eydL2OiY05WsL
06711p33abTudj294c9VSZRBMcE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=sendgrid.info;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe:x-feedback-id;
s=smtpapi; bh=BzD77mt7sqMcZdgGEsUFwTbF23Y=; b=xgjljjz7u3amhMqHer
FCZNoUh/ks+2GtpnKxA2WSIaRK0J6g2KdtbFcQ5pJU01x/oQBiLpqrWF2cr1PRcj
hKX8IkAIt5+flpApy53ZqwJ2EqQVwKGGRp97gE+salzeLBaAeCJGkdD+FaGLIaff
s31/ADaOvchpMK5ggSnEdAaxM=
Received: by filter0493p1las1.sendgrid.net with SMTP id filter0493p1las1-9260-59AA0681-6F
2017-09-02 01:16:49.999844787 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0006p1iad1.sendgrid.net (SG) with ESMTP id b8zyS6bTQ06L_eXs0WzyQg
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 01:16:49.958 +0000 (UTC)
Date: Sat, 02 Sep 2017 01:16:50 +0000 (UTC)
From: Quincy Larson<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Beta d3 SelectAll (#13006)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59aa067d28969_34ef3f9a441c3c34182919";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: QuincyLarson
X-GitHub-Recipient: pawan-mehta
X-GitHub-Reason: subscribed
List-ID: freeCodeCamp/freeCodeCamp <freeCodeCamp.freeCodeCamp.github.com>
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AM9SCGnSeSNFWvPXOME8vooxPU6UCd3Nks5seKx9gaJpZM4Ly6Ey
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: OpfRgdkK9YQWPKIAgM5UQUoN56mCdWNmGtfFv0Mnvk33WjaIv0PlqQsDMUgGTpGp2+wgnLBtTMkiCD
wa6e15wHJGg1vDpvnS+gsiPST8uuVqj4uInvkqA1cDvC3ai5EB9YjEDAhVjYth1Rru37TaxM861I0/
2EgccTiQbEqJt4Rd1x5MPQWkraLuI7A1FDn+TTLsPPKgeXM6y0P4ScDRLp8uIU7QheqBE2fX+ldXZd
w=
X-Feedback-ID: 848413:6xvVEJqleZlAW7/vhv7PzD/cv5tamo2SWZDKyvugGvg=:6xvVEJqleZlAW7/vhv7PzD/cv5tamo2SWZDKyvugGvg=:SG
X-Spam-Status: No, score=1.7
X-Spam-Score: 17
X-Spam-Bar: +
X-Ham-Report: Spam detection software, running on the system "server14.hostingraja.in",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
root@localhost for details.
Content preview:  Closed #13006. -- You are receiving this because you are subscribed
to this thread. Reply to this email directly or view it on GitHub: https://github.com/freeCodeCamp/freeCodeCamp/issues/13006#event-1232190150
[...]
Content analysis details:   (1.7 points, 5.0 required)
pts rule name              description

0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: sendgrid.info]
0.5 RCVD_IN_SORBS_SPAM     RBL: SORBS: sender is a spam source
[<IP_ADDRESS> listed in dnsbl.sorbs.net]
-0.0 RCVD_IN_MSPIKE_H3      RBL: Good reputation (+3)
[<IP_ADDRESS> listed in wl.mailspike.net]
0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
domains are different
0.0 T_SPF_HELO_TEMPERROR   SPF: test of HELO record failed (temperror)
-0.0 SPF_PASS               SPF: sender matches SPF record
0.0 HTML_MESSAGE           BODY: HTML included in message
1.3 HTML_IMAGE_ONLY_24     BODY: HTML: images with 2000-2400 bytes of words
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
-0.0 RCVD_IN_MSPIKE_WL      Mailspike good senders
X-Spam-Flag: NO
----==_mimepart_59aa067d28969_34ef3f9a441c3c34182919
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #13006.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/freeCodeCamp/freeCodeCamp/issues/13006#event-1232190150
----==_mimepart_59aa067d28969_34ef3f9a441c3c34182919
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #13006.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_59aa067d28969_34ef3f9a441c3c34182919--


update version to 1.2.9

fix: api key retrieval

One thing of note here. The Newly Added Series slider on the homepage doesn't seem to load.

But clicking on the header seems to load (although with books)

Thanks for your nice workaround
I've been updated version to 1.2.9 with revamps of api retrieval
For 'Newly Added Series', This section looks the same as 'Newly Added Series' on the kavita server, and if there are no newly added books, it will be blank.
This is because paperback does not support the removal of empty sections. Although empty sections can be made invisible through other implementation methods, in this case, loading of the home page will be delayed.
Instead, you can manually disable this section in the settings.


Suggestions for extensibility

When using smart-doc for secondary encapsulation, there are several problems about extensibility, which have to cover the source code to be solved, and if these problems are solved, it will be a very perfect result

Regarding the use of FrameworkEnum Template enumeration class, can you consider to change to the SPI-based way, convenient for users to define their own Template logic, the existing implementation of the target class fully qualified class name wrapped up, can not select the specified template.
Regarding the isCollection method for determining collections in the JavaClassValidateUtil utility class, can we consider including the iterator java.lang.Iterable, which is also a member of the collection scene.
About the configFile field in the abstract base class BaseDocsGeneratorMojo, can you adjust its scope to protected? When you need to add additional configuration, you can obtain the required configuration information through the configFile.

@duanmourena The upcoming release 3.0.6 has provided support, and you can refer to the official documentation at https://smart-doc-group.github.io/guide/advanced/expand#other-framework-documentation-parsing-development-based-on-java-spi-since-3-0-6


Docs: Link to "Release archive" on "Release Notes" page appears to be incorrect?

For the v3.14 release, it appears that clicking on the "Release archive" link simply downloads the tgz for v3.14. I would expect that this takes me to the release notes for other releases. i.e. v3.13, v3.12, v3.11...
https://docs.projectcalico.org/release-notes/

Nevermind...I guess this is the archive of the entire release. You'd think I would know better :)
Nothin to see here...! :)