feat: Add window.alby methods

Describe the changes you have made in this PR
This adds a window.alby API and adds an initial method to it: window.alby.addAccount allows websites to register an account in Alby.
Link this PR to an issue [optional]
Fixes #ISSUE-NUMBER
Type of change

feat: New feature (non-breaking change which adds functionality)

Screenshots of the changes [optional]

How has this been tested?
Manually calling the function from the browser dev tools. I'll create a demo app later.
Checklist

[x] My code follows the style guidelines of this project and performed a self-review of my own code
[x] New and existing tests pass locally with my changes
[ ] I checked if I need to make corresponding changes to the documentation (and made those changes if needed)

Things that are still missing

Accounts should be better validated before adding them
Better type definitions for window.alby (Maybe with a custom library similar to the existing webln lib on npm?)
Documentation

I opened this PR to gather feedback on this API. I already suggested it in the Alby telegram channel.

thanks for this PR and tackling this! looks pretty good, I will review this asap

@AaronDewes do you still have time for this? otherwise maybe @im-adithya could you also help here?

After chatting with @reneaaron we think it's best to move the content script for this in its own file - to have this separate. Then every provider has it's own corresponding content script and we are fully flexible there and those are independent of each other.
but we don't do an enable call there as we always prompt the user anyway.
wdyt? If ok, then we get this in the next release. :shipit:

Without an enable call the user will not be able to reject further requests. Is this ok?

I agree it would be good to split this into a separate file. With 3 files and much duplication I think it would be best to refactor this, but I guess could be done in a follow up MR. Maybe we can also migrate these files to Typescript.
Why are these files called "onend"?

I agree it would be good to split this into a separate file. With 3 files and much duplication I think it would be best to refactor this, but I guess could be done in a follow up MR. Maybe we can also migrate these files to Typescript.

👍

Why are these files called "onend"?

They are added via at document_end in the manifest.json:

To add an account, do
await alby.enable() and then
await alby.addAccount("name", "lndhub", {lnAddress<EMAIL_ADDRESS>login: "xxxxx", password: "xxxx", url: "https://ln.getalby.com"})

@im-adithya Can you please address the review feedback in this PR. Let's get this merged! :rocket:

@reneaaron Done!


nuget missing new package

Hi, I can't get new version working because it's missing new package on nuget (Naxam.Mapbox.iOS.4.1.1). I understand you don't want to release a new version yet before testing on official nuget, but do you have other packages sources like myget.org for them?

Plz check again.


USHIFT-2345: Revert "Work around broken osbuild dependency on RHEL 9.3"

This reverts commit 47fba3b496d2546a5102f668206575ddf5bc46f3.

/lgtm


Cleanup workflows

remove unnecessary action argument in release workflow
remove selftest that is now essentially a duplicate of previous test

possibly for #143


Generated Extension Methods contribute to build warnings

We've got a project with:
   <PropertyGroup>
      <GenerateDocumentationFile>true</GenerateDocumentationFile>
   </PropertyGroup>

We rely on warnings to help us find undocumented public methods. When using AutoRegisterInject, we get these build issues
...\AccountSvc\srcs\webs\WebApi\AutoRegisterInject\AutoRegisterInject.Generator\AutoRegisterInject.ServiceCollectionExtension.g.cs(7,21,7,65): warning CS1591: Missing XML comment for publicly visible type or member 'AutoRegisterInjectServiceCollectionExtension'
...\WebApi\AutoRegisterInject\AutoRegisterInject.Generator\AutoRegisterInject.ServiceCollectionExtension.g.cs(9,79,9,117): warning CS1591: Missing XML comment for publicly visible type or member 'AutoRegisterInjectServiceCollectionExtension.AutoRegisterFromAccountWebApi(IServiceCollection)'

I considered attempting to suppress the warnings by first seeing if I couldn't extended the generated code with partial implementations, but the generated code isn't partial.
// <auto-generated>
//     Automatically generated by AutoRegisterInject.
//     Changes made to this file may be lost and may cause undesirable behaviour.
// </auto-generated>
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.DependencyInjection.Extensions;
public static class AutoRegisterInjectServiceCollectionExtension
{
    public static Microsoft.Extensions.DependencyInjection.IServiceCollection AutoRegisterFromTaylorUFPAccountWebApi(this Microsoft.Extensions.DependencyInjection.IServiceCollection serviceCollection)
    {
        return AutoRegister(serviceCollection);
    }

    internal static Microsoft.Extensions.DependencyInjection.IServiceCollection AutoRegister(this Microsoft.Extensions.DependencyInjection.IServiceCollection serviceCollection)
    {

        return serviceCollection;
    }
}

The generated code could supply xml comments or suppress warnings related to them. I'm unsure which would be the better solution.

This will be fixed in a new version by the end of the month.


Oh returns error on Windows 10 (x64)

When I tried to get latest version on Oh on my Windows 10 machine with x64 arch. First it asked me to enable 'object type list' flag needed by the OH utility and execute 'oh -otl' command to enable it. That will take effect next time you boot.
So after rebooting, I tried to access 'oh' via command-line but it returned
> oh
RtlAdjustPrivilege(SE_DEBUG) failed with status = C0000061. -u may not work.//
// TIME: 2018-06-19 16:51
// MACHINE: LP-5CD7436N0Z
// BUILD: 9200
// OH version:  built by: dnsrv_dev(v-smgum)
//
//

followed by some kind of dump.
Then I tried to open the command-line using 'Run as administrator' but again got
> oh
//
// TIME: 2018-06-19 16:55
// MACHINE: LP-5CD7436N0Z
// BUILD: 9200
// OH version:  built by: dnsrv_dev(v-smgum)
//
//

followed by some kind of dump.
Although 'oh  -help' command works and displays all the switches/options available and returns
> oh -help
oh - Object handles dump -- built by: dnsrv_dev(v-smgum)
Copyright (c) Microsoft Corporation. All rights reserved.

OH [DUMP_OPTIONS ...]
OH [FLAGS_OPTIONS ...]
OH -c [COMPARE_OPTIONS ...] BEFORE_LOG AFTER_LOG

DUMP_OPTIONS are:

    -p N - displays only open handles for process with ID of n. If not
           specified perform a system wide dump.
    -t TYPENAME - displays only open object names of specified type.
    -o FILENAME - specifies the name of the file to write the output to.
    -a includes objects with no name.
    -s display summary information
    -h display stack traces for handles (a process ID must be specified)
    -u display only handles with no references in process memory
    -v verbose mode (used for debugging oh)
    NAME - displays only handles that contain the specified name.

FLAGS_OPTIONS are:

    [+kst|-kst] - enable or disable kst flag (kernel mode stack traces).
    [+otl|-otl] - enable or disable otl flag (object lists).

The `OH [+otl] [+kst]' command can be used to set the global flags
needed by OH. `+otl' is needed for all OH options and `+kst' is needed
by the `-h' option. The changes will take effect only after reboot.
The flags can be disabled by using `-otl' or `-kst' respectively.

COMPARE_OPTIONS are:

    -l     Print most interesting increases in a separate initial section.
    -t     Do not add TRACE id to the names if files contain traces.
    -all   Report decreases as well as increases.

If the OH files have been created with -h option (they contain traces)
then handle names will be printed using this syntax: (TRACEID) NAME.
In case of a potential leak just search for the TRACEID in the original
OH file to find the stack trace.

Looks like you are running a program called 'object handles dump' not the shell oh.
If you have installed github.com/michaelmacinnis/oh and are trying to run it, it looks like there is a problem finding the executable.
If you looking for help with 'object handles dump' you will need to find the maintainer of that program.

Yes, thanks for pointing it out!
It seems that there is another program with the same name from which it's name is conflicting.
Now I have renamed that program to resolve the conflict.
So oh is actually stated running but it shows this error
C:\>oh
boot.oh: 485: error/runtime: 'HOME' undefined
C:\$

Thank you for your interest in oh. As mentioned in the README, oh compiles and runs but should be considered experimental on Windows. If you are interested in solving issues you discover, pull requests are welcome.


Uncaught (in promise) SyntaxError: Unexpected token 's', "storage op"... is not valid JSON

Description

https://gitea.com/gitea/changelog/actions/runs/43/jobs/0
Gitea Version
latest
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
gitea.com
Database
None

response body:
storage open "gitea/changelog/f1/17905.log": open /data/gitea/gitea/actions_log/gitea/changelog/f1/17905.log: no such file or directory

We also need to stop loading and show a error toast here.

We also need to stop loading and show a error toast here.

https://github.com/go-gitea/gitea/pull/31124 takes care of those parts.


CLI glob problem for recursively targeting files

Given a structure:
./source/images/
./source/images/test/
./source/images/foo/

where each directory contains images, I am unable to run any successful imagemin task where I glob this path and wish to have the output respect the input structure.
If I issue the following command: imagemin ./source/images/**/* ./build/images, ./build/images will only contain images from the subdirectories, ignoring those in ./source/images directly. If I choose my glob with file extensions (./source/images/**/*.{png,jpg,svg}, etc.), all images are thrown into  ./build/images, however without the subdirectories as desired (naturally due to the extension specifier). I have tried a few variations here, such as targeting the entire source image directory (./sources/images) to no avail. The closest fails to recurse: imagemin ./source/images/** ./build/, which at least does the images in the root images directory and recreates the subdirs, but does not enter them to process their images.
UPDATE: To further highlight this point, I have tried every possible combination of doing this to no avail, including your own documented example of basic direct targets: imagemin <directory> <output>. So, in my case, I run imagemin source/images build, which yields an empty build/images directory.

Agree, it would be great to have imagemin -r dir/** build to recursively copy the exact structure as the original directory but with images compressed.

I though that worked already. Will have a look at this later today.

Perhaps this can be merged into #78 since apparently that still an issue with the current version?

Hey @kevva! I (re-?)added recursive support in imagemin-cli. Would be happy if you have comments on it :-)
As I've mentioned, using globbing pattern would indeed select all files, but won't keep the folder structure which I believe most of us want.

May I ask why isn't this solved yet?

Yet another bump on this. Looks like there are 2 submitted PRs (#196, #225) that are attempting to solve this; both are 6+ months old. Is there anything else the community can do to get this feature pushed though? Thanks!

Has this been fixed?

Yeah same problem here.. Not sure how is supposed to work if is not doing this critical feature..

@sktt 's PR#11 works fine.  Not merged yet?

This definitely needs fixing soon. It sounds like there's been a possible fix around for a year!

I too think this would be useful, looks like there are two PRs - but they're failing. Any plans to address these?


criteria_for_inclusion_of_external_sources (Search Engines)

A guide on selection of external sources
Fixes

Fixes #112  by @Marshalng
Description
As contributors seek to integrate more search engines as External Sources on  Creative Commons Search to enhance its effectiveness, this guide will help them identify important factors to bear in mind when considering these search engines in line with the goals of Creative Commons Search.
Technical details

Tests

Screenshots

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main or master).
[x] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Hi @Marshalng thank you for contributing!
The guide name does not follow the standards outlined here: https://github.com/creativecommons/search/tree/main/guides

the file name should be in snake_case. You instead appended  (Search Engines) at the end, this is not a valid snake_case name
the file should be in markdown format, and as such should have the .md extension, currently it has no extension
I might also suggest a change in name to something like: search_engines_inclusion_criteria.md since that is a little more clear when scanning the names as the list of guides grows. I'm open to iterations/versions of this, but I think the current criteria_for_inclusion_of_external_sources is not quite clear enough.

Thank you for your guidance @possumbilities  , I will effect the changes immediately.

Changes effected @possumbilities , please check. Thanks


Add the CLI scripts back to the build command.

Looks like the building of the CLI script was removed at some point, which meant the CLI scripts weren't working if the user didn't explicitly call yarn run build:cli.
Should we do a bit of a shuffle with the package.json to rename some of the scripts so we can use run-p more?

Thanks for catching this, @CrossR ! Looks good to me 😄

Should we do a bit of a shuffle with the package.json to rename some of the scripts so we can use run-p more?

Sure, that would make sense.


Feature Request: Support for newline replacement token in log streamer

Before I start on the issue let me know that I'm willing to submit a PR for this if approved.
The problem of correct handling of multi-line log messages into loggregator is a long discussed one.  This is yet another attempt to provide some relief for those of us suffering from this affliction.  For brevity I'm going to assume that the reader has some familiarity with the issue.  Though I can go into that if necessary.
Let me start by stating that I believe loggregator supports multi line log messages just fine.  If I submit a single event with mutliple lines in it loggregator will handle that perfectly as a single event.
I believe the true problem here is that stdout/stderr doesn't provide rich enough of an interface to differentiate between a new line and a new event.  Loggregator doesn't care about stdout/stderr, it only knows that it got an event it needs to pass on.  Loggregator's interface is rich enough to differentiate between a new line and a new event.
Because stdout/stderr is such an anemic interface the only way for the producer to provide more richness is to insert tokens into the stream that can be interpreted by something downstream of the true intent of the data.
Loggregator currently doesn't really know where the interface used to create the original event so I think it is the completely wrong component to interpret tokens inserted because of the original interface.  If I am using the richer loggregator api to add data into loggregator I don't want it to interpret data I'm giving it assuming it came from stdout/stderr.
This leaves, IMHO, only 3 viable options for interpreting the stream.  I've ordered them by what I feel is worst to best. :)
1 Add another event type to loggregator so that loggregator can know the event came from stdout/stderr.  This will allow it to intelligently interpret tokens in the event inserted to makeup for anemic interfaces.
2 Ask all possible consumers of loggregator events to interpret the tokens injected in the event.  This is only viable because it can be handled on an application by application basis.  An application can say "I know this application inserted this token upstream because I know this message was sent via stdout/stderr.  A similar judgement cannot be made globally for all applications and all loggregator message events.
However, this is a significant burden to place on the user.  All consumers of these events (cli, webui log streamers, log aggregators, etc) need to be enhanced to support interpreting these token on a per application basis.
3 Allow the stdout/stderr to loggregator adapter to interpret the token.  This makes sense since it is the adapter's job to properly adapt the anemic stdout/stderr interface into a loggregator event.  Is there a reason why this is a bad option?  Perhaps more processing by the adapter?
My proposal is that we add a small enhancement to the current executor event demarcation logic that looks for a configurable token.  When found the executor adapter simply replaces that token with a new line to make up for the lack of richness in the stdout/stderr interface being used.
Thoughts?

Closing in favor of https://www.pivotaltracker.com/story/show/117583365


[README.md] Add hall-of-fame section to README.md

This patch adds hall-of-fame section to README.md
It looks like below

Signed-off-by: Dongju Chae<EMAIL_ADDRESS>

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

INFO: You can read if there are misspelled characters at our misspelling check report. Please read http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/680-202010291139020.57240200042725-e3b62b07818aee23654654f1c241561d656d9afd/report/misspelling_result.txt.


Very slow and memory inefficient algorithm used to sieve primes...

This repo's implementation of sieveUpTo called by primesUpTo* has got to be one of the slowest and most wasteful of memory implementation of the Sieve of Eratosthenes of any I have seen...
The problems are as follows:

In using IntSet as it's base storage, it uses multiple bytes per stored composite entry, which memory use is so high that it can't sieve even up to a billion as it consumes Gigabytes of memory over that range as it uses many bytes per entry for every composite number over the range.
It doesn't even implement the very simple optimization of sieving "odds-only" so there are about two and a half times more culling operations than necessary (and twice as much memory is required for all the unused evens).
Composite culling operation execution overheads are atrocious (although constant time on the average) as it must perform a hashing operation each time.
Cache associativity is also atrocious as it is skipping over this huge linked memory storage.

It has the single advantage of being short.  However, it can't sieve to a billion using a reasonably amount of RAM memory and even if it could it would take about a minute or so.
A much better short implementation which greatly reduces the memory consumption such that very large ranges can be sieved (although still somewhat slowly due to the hashing) is as follows:
# compile with "-d:release -d:danger"

import tables

type PrimeType = uint64
proc primesHashTable(): iterator(): PrimeType {.closure.} =
  iterator output(): PrimeType {.closure.} =
    # some initial values to avoid race and reduce initializations...
    yield 2.PrimeType; yield 3.PrimeType; yield 5.PrimeType; yield 7.PrimeType
    var h = initTable[PrimeType,PrimeType]()
    var n = 9.PrimeType
    let bps = primesHashTable()
    var bp = bps() # advance past 2
    bp = bps(); var q = bp * bp # to initialize with 3
    while true:
      if n >= q:
        let inc = bp + bp
        h.add(n + inc, inc)
        bp = bps(); q = bp * bp
      elif h.hasKey(n):
        var inc: PrimeType
        discard h.take(n, inc)
        var nxt = n + inc
        while h.hasKey(nxt): nxt += inc # ensure no duplicates
        h.add(nxt, inc)
      else: yield n
      n += 2.PrimeType
  output

# tested as...
from times import epochTime

let limit = 100_000_000.PrimeType
let start = epochTime()
let iter = primesHashTable()
var count = 0
for p in iter():
  if p > limit: break else: count.inc
let elpsd = (epochTime() - start) * 1000.0
echo "Found ", count, " primes up to ", limit, " in ", elpsd, " milliseconds."

This is an "incremental" Odds-Only Sieve of Eratosthenes and only stores a hash entry for each of the base primes up to the square root of the current iteration value (determined automatically by the recursive secondary base primes feed).  It still takes about a minute to count the number of primes to a billion, but at least it doesn't take an excessive amount of memory to do so.  Its output also doesn't consume memory as it is just an iterator over the "incrementally" found primes.
If being so short isn't a consideration, the Page Segmented Bit-Packed Odds-Only Unbounded Sieve of Eratosthenes from RosettaCode is fast as in only taking about a second to sieve to a billion, consumes even less memory, and can even relatively easily have multi-threading added, but is over a hundred lines of code.

Hi @GordonBGood I agree that the implementation is not really good (this is why the test for primality for bigger ints uses deterministic Miller-Rabin, and probabilistic Miller-Rabin for even bigger numbers).
But I am confused about your point 1 (and consequently 3 and 4 as well). The documentation for intsets says literally

An efficient set of int implemented as a sparse bit set.

Now, I admit I never looked at the implementation, but if I understand correctly this means that a set of integers is represented by some pattern of bits like<PHONE_NUMBER>1001...001001 where a bit in position k means that k is in the set. For a billion that would be 10^9 bits =~ 125MB, not multiple Gigabytes. It certainly doesn't use multiple bytes per entry. I agree this is quite a lot - primes are sparse so most of that will be 0. Since the ratio of populated entries is about log n / n, for bigger n there are certainly more efficient daa structures, but for smaller n 1 bit per entry is reasonable. Also, I don't understand why in 3 you speak about hashes: if I understand correctly there should be no hashing going on in this implementation.
Unless, of course, I have totally mistunderstood what intsets are. Can you explain a little better why you speak of multiple bytes per entry?
BTW, I completely agree that one can skip even numbers, or for what is worth various classes modulo k for as big k as you care to implement.

@andreaferretti:

not really good (this is why the test for primality for bigger ints uses...

Yes, I appreciate that, but being so slow, you have to switch to the more complex math sooner than you should have to.

An efficient set of int implemented as a sparse bit set.

I did have a quick look at the implementation and while it's true that it uses a one bit representation per number in a packed (32-bit) representation, it is still within a nested (so that it can be sparse) hashed tree structure to quickly find the actual populated bits, and that is as far as I looked as I could see why it was taking an average of much more than one bit per represented composite number, and also why it is slow in having to do hashing.  As promoted, it is faster per operation than using a full hash table (which is why my table implementation for odds-only with less operations is no faster than your implementation), but probably an inappropriate use of IntSet's when a simple bit-packed array would have done the job, and much faster other than still having the cache associativity problem for large arrays - but at that, the cache delays are still smaller than the hashing time costs plus the associativity cost.
So no, it isn't a simple bit-packed array using the amount of memory as you calculated, although it does use some bit-packed words within the hash tables to save some space.  To save much more space and time, it is quite trivial to implement a "monolithic" bit-packed array version which would then only use 62.5 Megabytes for a range of a billion for "odds-only" and would reduce the time to cull by about a third, not more because of the remaining cache associativity problem.  This type of "naive" SoE (other than moving up one step to use bit-packing and odds-only) can be found anywhere, including RosettaCode.
I highly recommend the page segmented version as it avoids the cache associativity problem at the cost of 150 LOC or so.

or for what is worth various classes modulo k for as big k as you care to implement.

I've done quite a lot of work with maximal wheel factorization as you describe, and while one can implement it efficiently up to wheels eliminating all the primes up to 7 or even 11, anything above that doesn't offer anything much in gains for the cost.  The efficient ways of doing this cost another few hundred LOC.  One of these days, I'll be posting a way of doing this on the forum that uses Nim to be faster than Kim Walisch's "primesieve", with the main hold-up ATM being the instability of how Nim does threading.

Thank you, I did not know the internals of intsets. I can easily replace that with custom intsets, and make it odd only. Or switch to your version, I am still not sure. But in any case, I expect that testing a single prime will be much faster with deterministic Miller Rabin

@ andreaferretti:

I can easily replace that with custom intsets, and make it odd only. Or switch to your version, I am still not sure.

I think you'll find that (my RosettaCode) page segmented version is immensely faster than anything you can do with intsets, and even that is limited by the time it takes to iterate over the found primes, if you don't mind the number of LOC.  Further refinements can likely reduce the time by another factor of three or so using multi-threading in spite of the time it takes to iterate to down to a fraction of a second to iterate over the primes to a billion using a reasonable CPU.
If you don't need to iterate over the primes, then it can be made even faster down to "primesieve" type speeds, but I assume that you do.
If you want to stay simple, an odds-only bit-packed "monolithic" array will do it, take only one bit per odd number to the sieving range, and be about six times faster than your intset version in spite of the huge array to a billion:
iterator primesUpTo(top: uint): uint =
  let topndx = int((top - 3) div 2)
  let sqrtndx = (int(sqrt float64(top)) - 3) div 2
  var cmpsts = newSeq[uint32](topndx div 32 + 1)
  for i in 0 .. sqrtndx: # cull composites for primes
    if (cmpsts[i shr 5] and (1u32 shl (i and 31))) == 0:
      let p = i + i + 3
      for j in countup((p * p - 3) div 2, topndx, p):
        cmpsts[j shr 5] = cmpsts[j shr 5] or (1u32 shl (j and 31))
  yield 2 # separate culling above and iteration here
  for i in 0 .. topndx:
    if (cmpsts[i shr 5] and (1u32 shl (i and 31))) == 0:
      yield uint(i + i + 3)


Swagger issue when working with identities

Attempting to get the details of an identity through a GET call, or update an identity through a PATCH call via the embedded Swagger UI results in an error. It appears something in the swagger isn't generated quite right. Specifically, the path argument that corresponds to the identity id is not passed and instead a constant string is included.

Note that the API itself works correctly e.g. calling the APIs from an external client like Postman. The issue is just with the embedded Swagger UI.


remove release of realsense2_camera due to missing release branches

Re: https://github.com/ros/rosdistro/pull/23460#issuecomment-572838057
@doronhi FYI I'm rolling back the release @Levi-Armstrong I"m leaving the source entry.

This is superseded by #23493, so I'll close this out.


Add optional -l/--lang flag to specify the language attribute of the html tag

Example Usage:
./rost_gen -i myFile.txt --lang en-CA

This will result in the following html document:
<html lang="en-CA">
...Rest of the document

Ideally, #23 should be resolved first. It would make this much easier to implement
If no lang option is provided, it should default to en-CA

Closed by https://github.com/Eakam1007/rost_gen/commit/107aae547ede87605714870b51a6045e3e377d12, https://github.com/Eakam1007/rost_gen/commit/eb28ba577991c03e4f8ca053979ffc35f400af67


Use stripped variants by default in Python install

Summary
Will file a separate ticket to support --debug.
Closes https://github.com/astral-sh/uv/issues/5447.

They're no smaller on macOS, but like 40% smaller on Windows and 10-20% smaller on Linux IIRC.

They're no smaller on macOS, but like 40% smaller on Windows and 10-20% smaller on Linux IIRC.

@charliermarsh , just to correct your understanding - For the latest (3.12.4) python for the most popular linux distribution (x86_64-unknown-linux-gnu), install_only download is 238M, and install_only_stripped is 82M, i.e. 66% smaller!

@bulletmark -- That's awesome. Is that the variant that's confusingly large? Wonder how much smaller we can make it.

@charliermarsh yes, this was discussed here. Python 3.12 jumped massively in size compared to 3.11.


Behind firewall UDP is not working

Hi Team,
I am behind a corporate network and using this example, My firewall allows only TCP protocols and UDP is blocked. In the example only one ice candidate is being generated which is a UDP. I believe my problem could be solved if we have an ice candidate with TCP too. Can you suggest me if we can have a TCP candidate?

I think you can use a turnserver for your case.


Fixes a few compiler warnings.

printf->puts for non-format strings.
declares the example_test_printf mock predeclaration.

cmockery is dead since several years, you probably want to take a look at https://cmocka.org which is the successor of cmockery.

Actually we're still here :)


Add metrics to monitor the memory, that usercontainers are consuming …

…in the system.
This Pull request will add a new metric, to monitor the memory utilisation of user-containers in the whole system.
This PR is a prereq for the PR https://github.com/apache/incubator-openwhisk/pull/3747, as it is possible to decide if the system that is deployed is big enough after changing the loadbalancing algorithm.
Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[x] Controller
[ ] Message Bus (e.g., Kafka)
[x] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[x] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

PG5#471 running.

Codecov Report

Merging #3831 into master will increase coverage by 0.79%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #3831      +/-   ##
==========================================
+ Coverage   73.87%   74.67%   +0.79%
==========================================
  Files         138      138
  Lines        6446     6452       +6
  Branches      401      407       +6
==========================================
+ Hits         4762     4818      +56
+ Misses       1684     1634      -50

Impacted Files
Coverage Δ

...on/scala/src/main/scala/whisk/common/Logging.scala
86.81% <0%> (-0.97%)
:arrow_down:

...e/loadBalancer/ShardingContainerPoolBalancer.scala
31.6% <0%> (-0.94%)
:arrow_down:

...cala/src/main/scala/whisk/http/ErrorResponse.scala
89.77% <0%> (+1.13%)
:arrow_up:

...ain/scala/whisk/core/entity/ActivationResult.scala
92.3% <0%> (+1.53%)
:arrow_up:

...in/scala/whisk/utils/ExecutionContextFactory.scala
100% <0%> (+7.69%)
:arrow_up:

...rc/main/scala/whisk/core/entity/ExecManifest.scala
96.29% <0%> (+14.81%)
:arrow_up:

...whisk/connector/kafka/KafkaConsumerConnector.scala
62.96% <0%> (+29.62%)
:arrow_up:

...whisk/connector/kafka/KafkaProducerConnector.scala
58.33% <0%> (+36.11%)
:arrow_up:

...whisk/connector/kafka/KafkaMessagingProvider.scala
69.23% <0%> (+46.15%)
:arrow_up:

Continue to review full report at Codecov.

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


Multistate property definitions

Define data structures and keyword for storing electronic properties on multiple electronic states

These are now available as part of 0.7.3 release - bdaef4d876c54cf98901187801dc2fa81871b91e


checkers in decoder

in future we have to pass down the checker we want to use here.
fn perform_decoding(text: &str) -> Vec<CrackResult> {
    let decoders = filter_and_get_decoders();
    let athena_checker = Checker::<Athena>::new();
    let checker = CheckerTypes::CheckAthena(athena_checker);
    decoders.run(text, checker)
}

Lots of merge conflicts here D:


Add support for network proxy in future

Is your feature request related to a problem? Please describe.
Slow download in China, both GitHub or TuxFamily.org. (I know download mirror is not implemented yet, TuxFamily.org is slow via browser download. It shouldn't be any faster in godot-manager either.)
Describe the solution you'd like
Add support for http proxy or even SOCKS5, after https://github.com/godotengine/godot/pull/55988 gets merged.
Or if you end up porting godot-manager to 4.0, as 4.0 already has proxy support https://github.com/godotengine/godot/pull/55747
Describe alternatives you've considered
Add another mirror, maybe SourceForge (https://sourceforge.net/projects/godot-engine.mirror/files/), which is extremely fast in China. But it's not a matter of course to do so, as SourceForge had injected ads into the download file back in 2013, caused GIMP to stop using it. Now it seems good though, after it got acquired by another company https://www.reddit.com/r/sysadmin/comments/4n3e1s/the_state_of_sourceforge_since_its_acquisition_in/.
Actually it seems to be the only mirror, besides itch.io, which only has the latest version.
Or just don't implement it. Browser/steam download is fine.
Additional context
Maybe "Tuxfamily not available" tooltip needs be more obvious. For example, making the Tuxmaily.org button Tuxmaily.org (unavailable), because I was all set to raise an issue that mirror switching is broken, until I cloned the repo and looked at the source code to find it's unavailable.

Hey Rambda,
Yeah, I was hoping to have Tuxfamily available for v0.1.0, but had to push it off, due to needing to setup a way to reliably scrape Tuxfamily's downloads, as well as create a possible system for allowing other developers that modify the Godot Engine, the ability to provide mirrors for their versions of Godot for users to be able to download custom versions of the Engine/Editor with Godot Manager.  Hence why I pushed it off to v0.2.0.
As for SOCKS5, I have no problems with implementing Proxy / SOCKS5 communication for Godot to do Downloads through, for all download aspects that Godot Manager will do.  It may not make it into the v0.1 branch, but I definitely added it as a Milestone for v0.2.0 to have that fully implemented for use, as I have had to do the Proxy setup in the past.
My plan is to eventually migrate to Godot 4.0, but their Mono/C# support is not quite there yet, and as you can tell from the code, I am using C# as the basis for code in the Godot Manager itself.  So until they support it, I will continue to work with the 3.x branch of Godot, while still supporting Godot 4 for launching, and project file handling.
Currently, I'm working on bug #9 that introduced an incompatibility in the Project File format, with the use of PackedStringArray() in Godot 4, which is not available in Godot 3.  So, I'm hopeful to get a few more things tied up in the 0.1 release in regards to bugs, and will then focus my attention to features for 0.2.

After reviewing godotengine/godot#55988, it looks like they have added support for HTTP Proxy, but will not be available in 3.4.x release, instead is available in 3.5.  Once 3.5 reaches stable, I will add Proxy support to all aspects of Godot's Network communication, at which point you should have no issues with setting up Proxy support for Godot Manager.  Still with the progress of 3.5 betas, it will more then likely become stable in time for 0.2.0, so the plan to add proxy support will still be targeting said release.


Hello, how to finetune own datasets

What should I do if I want to fine tune the current pre training model to my own dataset instead of Imagenet's Val dataset? Can you answer it? Thank you very much

@wudizuixiaosa You just need to write your own Dataset Class in datasets.py. Also, don't forget change the data_path and nb_classes in args of main_finetune.py.

Thank you for your reply. I know that we can change the data_path and class in finetune..py. I've also seen dataset.py project, but I see that the settings in it are based on Imagenet. As I am a beginner, my foundation is not good, and I am very interested in your project. So can you give me an example? Let's assume that there are two kinds of dogs and cats in my dataset. How can I define them? Mainly, I don't see relevant parameter settings in the project.

By the way, which format of dataset should i choose,coco,voc or Unlabeled pictures in folders of corresponding categories？

Please follow the dataset format of Imagenet. Basically, you can need to build two folders named dog and cat then put images into the corresponding folder.

Oh, thank you for replying so quickly，i am coming to try it now


Rationalise Survey type and method with observation type and instrument

We need to fix the vocabs associated with geophysical surveys following the resolution of multi-type surveys into a single survey (with the raw aquired data attached) to cover the acquisition and then multiple observations of different type (with the processed datasets attached). The processsed datasets can also be related to the original survey as additional datasets where their survey 'type' is recorded by their earth science data category.
E.g. AG surveys are therefore of type:geophysics and method:airborne. There would also be mag, rads, and DEM observations with the grids/images attached. The Mag/RAD/DEM observation metadata could be omitted if it is not of interest and all datasets could be attached to the original AG survey.
The changes required involves substantial expansion of observation instrument to include AG tech specs and seismic source along with the additional concepts from the survey type review. Additional work will be required to transfer detail from survey type to observation type, remove narrower concepts from survey method, understand how/if obs.sample_preparation will be used in Geophysical surveys, workshop how the new understanding of AG surveys is reflected in Seismic, geochem, general field sampling, etc., possibly writing some documentation along the way.
@CantRoger might be the right person to lead this. I'll raise this as an activity in the standup to prioritise this work.

@geoderekh I dont think we want to separate the data attached to observations or survey based on a raw/processed classification.  I think all data is an observation that relates to the survey.  That observation may be multi-type or that survey may have many types of observations.
For metadata there should be a consistent approach to where it is stored in relation to the datasets in CKAN so i can be used to display the results


In case of GRE encapsulation, Fragmentation required due to exceeding 1514 Bytes

Hi Smirnov,
I noticed that the MAX_ETHER_FRAME is hardcoded with size of 1514. In other words, the array m_IBuffer of struct INTERMEDIATE_BUFFER  is limited to 1514 bytes.
In my case, I added 24-bytes header for GRE encapsulation. Therefore, the total size is increased to 1538 bytes (1514+24). In this case, fragmentation must be done.
My question is, does winpkfilter driver already support fragmentation? In other words, just by replacing the constant MAX_ETHER_FRAME  to 1538 will solve my problem?
Best Regards,
Dat

Hi Dat,
No, the driver won't do packet fragmentation for you. If, after attaching extra headers, your packet size exceeds MTU (typically Internet MTU never exceeds 1514 bytes, in LAN jumbo frames can reach 9014 bytes size), then you have to fragment it into two INTERMEDIATE_BUFFER structures and inject two packets instead of one. However, I would recommend avoiding fragmentation (fragmented packets are often silently dropped by firewalls/routers) at all. For example, for TCP protocol, you could manipulate the TCP MSS option to limit the maximum packet size and thus reserve space for your extra headers.
Hope it helps.
Vadim


⚠ Mobitopup has degraded performance

In 1a0bad2, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 5096 ms

Resolved: Mobitopup performance has improved in 781867a after 417 days, 11 hours, 47 minutes.


async clean undo log

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
Ⅱ. Does this pull request fix one issue?

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

原pr不需要关了重新提的

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: renliangyu857:x: wangliang181230You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #4401 (303c754) into develop (d919789) will decrease coverage by 0.10%.
The diff coverage is 17.47%.

@@              Coverage Diff              @@
##             develop    #4401      +/-   ##
=============================================
- Coverage      49.01%   48.90%   -0.11%
+ Complexity      3953     3945       -8
=============================================
  Files            733      732       -1
  Lines          24978    24985       +7
  Branches        3092     3093       +1
=============================================
- Hits           12242    12218      -24
- Misses         11439    11469      +30
- Partials        1297     1298       +1

Impacted Files
Coverage Δ

...c/main/java/io/seata/common/ConfigurationKeys.java
0.00% <ø> (ø)

...n/src/main/java/io/seata/common/DefaultValues.java
0.00% <ø> (ø)

...java/io/seata/rm/datasource/DataSourceManager.java
20.45% <0.00%> (-3.94%)
:arrow_down:

...ata/rm/datasource/undo/AbstractUndoLogManager.java
39.70% <17.20%> (-10.58%)
:arrow_down:

.../autoconfigure/properties/client/RmProperties.java
42.22% <66.66%> (ø)

...in/java/io/seata/server/session/GlobalSession.java
78.65% <0.00%> (-0.40%)
:arrow_down:

...o/seata/server/coordinator/DefaultCoordinator.java
52.18% <0.00%> (-0.37%)
:arrow_down:

Due to code conflicts and age, if you are still interested in participating in the community, please resubmit this pr to the 2.x branch after resolving the conflict.
由于代码冲突以及年代久远，如果你还有兴趣参与到社区，请解决完冲突后重新请提交这份pr至2.x分支中


Parse complex filters in URL (#465)

This update added to the common URL parsing to handle complex filter parameters.

I made changes to recordEdit and viewer apps, so including @howdyjessie @jrchudy here.

Changes look good to me. I used a lot of this code in the parse function I wrote in ermrestJS and I'm sure there's some refactoring that can be done that we can look at. @howdyjessie do the changes for viewer look okay to you? I'm not sure if we need to be so precise, but they work.

Looks good to me too :) Merge at will.


choose different kubernetes-in-docker solution

as bsycorp/kind is not working properly, there is the suggestion to choose a different kubernetes-in-docker solution.
see this issue for details
https://github.com/w3f/polkadot-deployer/issues/5

I have tried it:
https://github.com/drandreaskrueger/chainhammer/blob/polkadot/docs/polkadot.md#polkadot-deployer-swap-out-kubernetes
what else to try to make sure it really works?

For this:
kind build node-image

I get a
Error: error creating build context: error finding kuberoot: could not find kubernetes source

the README.md says
ensure that Kubernetes is cloned in $(go env GOPATH)/src/k8s.io/kubernetes

but I do not know to clone from where. Please advise. Thanks.

No need to build images, just kind create cluster should be enough. After the cluster is up you should follow the instructions:
export KUBECONFIG="$(kind get kubeconfig-path --name="kind")"
kubectl cluster-info

and check the output.
To be completely sure it would be good to run initialize helm (this is where the other kind project was getting stuck), install helm following https://helm.sh/docs/using_helm/#installing-the-helm-client and run helm init.Then kubectl get pods --all-namespaces -w, you should see the tiller pod in ready state after a while if all is ok.

kind create cluster
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.14.2) 🖼
 ✓ Preparing nodes 📦
 ✓ Creating kubeadm config 📜
 ✓ Starting control-plane 🕹
 ✓ Installing CNI 🔌
 ✓ Installing StorageClass 💾
Cluster creation complete. You can now use the cluster with:
export KUBECONFIG="$(kind get kubeconfig-path --name="kind")"
kubectl cluster-info

export KUBECONFIG="$(kind get kubeconfig-path --name="kind")"
echo $KUBECONFIG
~/.kube/kind-config-kind

kubectl cluster-info
Kubernetes master is running at https://localhost:34755
KubeDNS is running at https://localhost:34755/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

trying helm now

done.
looks good, right?
https://github.com/drandreaskrueger/chainhammer/blob/polkadot/docs/polkadot.md#polkadot-deployer-swap-out-kubernetes

Indeed, kube-system   tiller-deploy-765dcb8745-9l97m               1/1     Running   0          27s, ok! i'll prepare the changes for using it instead of bsycorp/kind, will keep you posted.

Fantastic, thanks a million

@drandreaskrueger this is already done in polkadot-deployer v0.10.1, please reinstall and give it a try.

looks good - but not perfect yet.

polkadot-deployer --version
0.10.1

polkadot-deployer list

Downloading component kubectl...
Done
Downloading component helm...
Done
Downloading component terraform...
Done
Downloading component kind...
Done
No deployments found, try `polkadot-deployer create`

cat testnet1.json
{
  "name": "testnet1",
  "type": "local",
  "nodes": 4
}

polkadot-deployer create --verbose --config testnet1.json

Creating cluster 'testnet1'...
Creating cluster "testnet1" ...

 • Ensuring node image (kindest/node:v1.14.2) 🖼  ...

kubectl --kubeconfig=./config describe node minikube ✓ Ensuring node image (kindest/node:v1.14.2) 🖼
 • Preparing nodes 📦  ...

 ✓ Preparing nodes 📦

 • Creating kubeadm config 📜  ...

 ✓ Creating kubeadm config 📜
 • Starting control-plane 🕹  ...

 ✓ Starting control-plane 🕹
 • Installing CNI 🔌  ...

 ✓ Installing CNI 🔌
 • Installing StorageClass 💾  ...

 ✓ Installing StorageClass 💾
Cluster creation complete. You can now use the cluster with:

export KUBECONFIG="$(kind get kubeconfig-path --name="testnet1")"
kubectl cluster-info

~/.kube/kind-config-testnet1

Done
Installling dependencies...
NAME                                 SECRETS   AGE
attachdetach-controller              1         4s
certificate-controller               1         4s
clusterrole-aggregation-controller   1         4s
coredns                              1         3s
daemon-set-controller                1         4s
expand-controller                    1         4s
generic-garbage-collector            1         3s
ip-masq-agent                        1         1s
kindnet                              1         1s
kube-proxy                           1         3s
namespace-controller                 1         3s
node-controller                      1         4s
persistent-volume-binder             1         4s
pod-garbage-collector                1         3s
statefulset-controller               1         4s
token-cleaner                        1         4s
ttl-controller                       1         2s

serviceaccount/tiller created

NAME                                                   AGE
cluster-admin                                          7s
ip-masq-agent                                          1s
kindnet                                                1s
kubeadm:kubelet-bootstrap                              3s
kubeadm:node-autoapprove-bootstrap                     3s
kubeadm:node-autoapprove-certificate-rotation          3s
kubeadm:node-proxier                                   3s
system:aws-cloud-provider                              6s
system:basic-user                                      7s
system:controller:attachdetach-controller              6s
system:controller:certificate-controller               5s
system:controller:clusterrole-aggregation-controller   6s
system:controller:cronjob-controller                   6s
system:controller:daemon-set-controller                6s
system:controller:deployment-controller                6s
system:controller:disruption-controller                6s
system:controller:endpoint-controller                  6s
system:controller:expand-controller                    6s
system:controller:generic-garbage-collector            6s
system:controller:horizontal-pod-autoscaler            6s
system:controller:job-controller                       6s
system:controller:namespace-controller                 6s
system:controller:node-controller                      6s
system:controller:persistent-volume-binder             6s
system:controller:pod-garbage-collector                6s
system:controller:pv-protection-controller             5s
system:controller:pvc-protection-controller            5s
system:controller:replicaset-controller                6s
system:controller:replication-controller               6s
system:controller:resourcequota-controller             6s
system:controller:route-controller                     6s
system:controller:service-account-controller           6s
system:controller:service-controller                   5s
system:controller:statefulset-controller               5s
system:controller:ttl-controller                       5s
system:coredns                                         3s
system:discovery                                       7s
system:kube-controller-manager                         7s
system:kube-dns                                        6s
system:kube-scheduler                                  6s
system:node                                            6s
system:node-proxier                                    7s
system:public-info-viewer                              7s
system:volume-scheduler                                6s

clusterrolebinding.rbac.authorization.k8s.io/tiller created

Creating ~/.config/polkadot-deployer/components/repository

Creating ~/.config/polkadot-deployer/components/repository/cache
Creating ~/.config/polkadot-deployer/components/repository/local
Creating ~/.config/polkadot-deployer/components/plugins
Creating ~/.config/polkadot-deployer/components/starters
Creating ~/.config/polkadot-deployer/components/cache/archive
Creating ~/.config/polkadot-deployer/components/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com

Adding local repo with URL: http://<IP_ADDRESS>:8879/charts

$HELM_HOME has been configured at ~/.config/polkadot-deployer/components.

Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.

Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
To prevent this, run `helm init` with the --tiller-tls-verify flag.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
Happy Helming!

NAME                             READY   STATUS    RESTARTS   AGE
tiller-deploy-796c9d7db6-pz668   0/1     Pending   0          0s
tiller-deploy-796c9d7db6-pz668   0/1     Pending   0          0s
tiller-deploy-796c9d7db6-pz668   0/1     Pending   0          11s
tiller-deploy-796c9d7db6-pz668   0/1     ContainerCreating   0          11s
tiller-deploy-796c9d7db6-pz668   0/1     Running             0          25s

"w3f" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "w3f" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈

Could not install dependencies: unacceptable kind of an object to dump [object Undefined]
Deleting cluster "testnet1" ...

ok, i've been able to reproduce, a fix has been published in v0.10.2, can pls you upgrade and retry? hopefully all should be fine now :)

yeehah, you did it!

polkadot-deployer create --verbose --config testnet1.json

Downloading component kubectl...
Done
Downloading component helm...
Done
Downloading component terraform...
Done
Downloading component kind...
Done
Creating cluster 'testnet1'...
Creating cluster "testnet1" ...

 • Ensuring node image (kindest/node:v1.14.2) 🖼  ...
 ✓ Ensuring node image (kindest/node:v1.14.2) 🖼
 • Preparing nodes 📦  ...
 ✓ Preparing nodes 📦
 • Creating kubeadm config 📜  ...
 ✓ Creating kubeadm config 📜
 • Starting control-plane 🕹  ...
 ✓ Starting control-plane 🕹
 • Installing CNI 🔌  ...
 ✓ Installing CNI 🔌
 • Installing StorageClass 💾  ...
 ✓ Installing StorageClass 💾
Cluster creation complete. You can now use the cluster with:
export KUBECONFIG="$(kind get kubeconfig-path --name="testnet1")"
kubectl cluster-info
~/.kube/kind-config-testnet1
Done
Installling dependencies...
NAME              SECRETS   AGE
coredns           1         5s
ip-masq-agent     1         1s
kindnet           1         1s
kube-proxy        1         4s
node-controller   1         5s
serviceaccount/tiller created
NAME                                                   AGE
cluster-admin                                          8s
ip-masq-agent                                          1s
kindnet                                                1s
kubeadm:kubelet-bootstrap                              5s
kubeadm:node-autoapprove-bootstrap                     5s
kubeadm:node-autoapprove-certificate-rotation          5s
kubeadm:node-proxier                                   4s
system:aws-cloud-provider                              8s
system:basic-user                                      8s
system:controller:attachdetach-controller              7s
system:controller:certificate-controller               7s
system:controller:clusterrole-aggregation-controller   7s
system:controller:cronjob-controller                   7s
system:controller:daemon-set-controller                7s
system:controller:deployment-controller                7s
system:controller:disruption-controller                7s
system:controller:endpoint-controller                  7s
system:controller:expand-controller                    7s
system:controller:generic-garbage-collector            7s
system:controller:horizontal-pod-autoscaler            7s
system:controller:job-controller                       7s
system:controller:namespace-controller                 7s
system:controller:node-controller                      7s
system:controller:persistent-volume-binder             7s
system:controller:pod-garbage-collector                7s
system:controller:pv-protection-controller             6s
system:controller:pvc-protection-controller            7s
system:controller:replicaset-controller                7s
system:controller:replication-controller               7s
system:controller:resourcequota-controller             7s
system:controller:route-controller                     7s
system:controller:service-account-controller           7s
system:controller:service-controller                   7s
system:controller:statefulset-controller               7s
system:controller:ttl-controller                       7s
system:coredns                                         5s
system:discovery                                       8s
system:kube-controller-manager                         8s
system:kube-dns                                        8s
system:kube-scheduler                                  8s
system:node                                            8s
system:node-proxier                                    8s
system:public-info-viewer                              8s
system:volume-scheduler                                8s
clusterrolebinding.rbac.authorization.k8s.io/tiller created
Creating ~/.config/polkadot-deployer/components/repository
Creating ~/.config/polkadot-deployer/components/repository/cache
Creating ~/.config/polkadot-deployer/components/repository/local
Creating ~/.config/polkadot-deployer/components/plugins
Creating ~/.config/polkadot-deployer/components/starters
Creating ~/.config/polkadot-deployer/components/cache/archive
Creating ~/.config/polkadot-deployer/components/repository/repositories.yaml
Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
Adding local repo with URL: http://<IP_ADDRESS>:8879/charts
$HELM_HOME has been configured at ~/.config/polkadot-deployer/components.
Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
To prevent this, run `helm init` with the --tiller-tls-verify flag.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
Happy Helming!
NAME  READY   STATUS     RESTARTS   AGE
tiller-deploy-796c9d7db6-r2zz9   0/1     Pending   0          0s
tiller-deploy-796c9d7db6-r2zz9   0/1     Pending   0          1s
tiller-deploy-796c9d7db6-r2zz9   0/1     Pending   0          9s
tiller-deploy-796c9d7db6-r2zz9   0/1     ContainerCreating   0          9s
tiller-deploy-796c9d7db6-r2zz9   0/1     Running             0          23s
"w3f" has been added to your repositories
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "w3f" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete. ⎈ Happy Helming!⎈
NAME:   polkadot-base-services
LAST DEPLOYED: Fri Jun 14 20:34:01 2019
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/ClusterRole
NAME      AGE
polkadot  1s
==> v1/ClusterRoleBinding
NAME      AGE
polkadot  1s
==> v1/NetworkPolicy
NAME                    AGE
polkadot-base-services  1s
==> v1/ServiceAccount
NAME      SECRETS  AGE
polkadot  1        1s
==> v1beta1/PodSecurityPolicy
NAME      PRIV   CAPS      SELINUX           RUNASUSER  FSGROUP    SUPGROUP  READONLYROOTFS  VOLUMES
polkadot  false  RunAsAny  MustRunAsNonRoot  MustRunAs  MustRunAs  false     configMap,secret,persistentVolumeClaim,emptyDir
Done
Initializing nodes...
NAME:   polkadot-node-0
LAST DEPLOYED: Fri Jun 14 20:34:02 2019
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/ConfigMap
NAME                       DATA  AGE
polkadot-custom-chainspec  1     0s
==> v1/Pod(related)
NAME               READY  STATUS    RESTARTS  AGE
polkadot-node-0-0  0/1    Init:0/1  0         0s
==> v1/Secret
NAME                         TYPE    DATA  AGE
polkadot-node-0-node-key     Opaque  1     0s
polkadot-node-0-session-key  Opaque  1     0s
==> v1/Service
NAME                      TYPE       CLUSTER-IP     EXTERNAL-IP  PORT(S)          AGE
polkadot-node-0-bootnode  ClusterIP  <IP_ADDRESS>  <none>       30100/TCP        0s
polkadot-node-0-p2p       NodePort   <IP_ADDRESS>    <none>       30100:30100/TCP  0s
==> v1/StatefulSet
NAME             READY  AGE
polkadot-node-0  0/1    0s
NAME:   polkadot-node-1
LAST DEPLOYED: Fri Jun 14 20:34:03 2019
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/Pod(related)
NAME               READY  STATUS    RESTARTS  AGE
polkadot-node-1-0  0/1    Init:0/1  0         0s
==> v1/Secret
NAME                         TYPE    DATA  AGE
polkadot-node-1-node-key     Opaque  1     0s
polkadot-node-1-session-key  Opaque  1     0s
==> v1/Service
NAME                 TYPE      CLUSTER-IP     EXTERNAL-IP  PORT(S)          AGE
polkadot-node-1-p2p  NodePort  <IP_ADDRESS>  <none>       30101:30101/TCP  0s
==> v1/StatefulSet
NAME             READY  AGE
polkadot-node-1  0/1    0s
NAME:   polkadot-node-2
LAST DEPLOYED: Fri Jun 14 20:34:03 2019
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/Pod(related)
NAME               READY  STATUS    RESTARTS  AGE
polkadot-node-2-0  0/1    Init:0/1  0         0s
==> v1/Secret
NAME                         TYPE    DATA  AGE
polkadot-node-2-node-key     Opaque  1     0s
polkadot-node-2-session-key  Opaque  1     0s
==> v1/Service
NAME                 TYPE      CLUSTER-IP     EXTERNAL-IP  PORT(S)          AGE
polkadot-node-2-p2p  NodePort  <IP_ADDRESS>  <none>       30102:30102/TCP  0s
==> v1/StatefulSet
NAME             READY  AGE
polkadot-node-2  0/1    0s
NAME:   polkadot-node-3
LAST DEPLOYED: Fri Jun 14 20:34:05 2019
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1/Pod(related)
NAME               READY  STATUS    RESTARTS  AGE
polkadot-node-3-0  0/1    Init:0/1  0         0s
==> v1/Secret
NAME                         TYPE    DATA  AGE
polkadot-node-3-node-key     Opaque  1     0s
polkadot-node-3-session-key  Opaque  1     0s
==> v1/Service
NAME                 TYPE      CLUSTER-IP    EXTERNAL-IP  PORT(S)          AGE
polkadot-node-3-p2p  NodePort  <IP_ADDRESS>  <none>       30103:30103/TCP  0s
==> v1/StatefulSet
NAME             READY  AGE
polkadot-node-3  0/1    0s
Done
Waiting for nodes ready...
NAME                READY   STATUS     RESTARTS   AGE
polkadot-node-1-0   0/1     Init:0/1   0          3s
NAME                READY   STATUS     RESTARTS   AGE
polkadot-node-3-0   0/1     Init:0/1   0          1s
NAME                READY   STATUS     RESTARTS   AGE
polkadot-node-0-0   0/1     Init:0/1   0          4s
NAME  READY   STATUS     RESTARTS   AGE
polkadot-node-2-0   0/1     Init:0/1   0          2s
polkadot-node-0-0   0/1     Init:0/1   0          32s
polkadot-node-1-0   0/1     Init:0/1   0          32s
polkadot-node-0-0   0/1     PodInitializing   0          33s
polkadot-node-2-0   0/1     PodInitializing   0          32s
polkadot-node-1-0   0/1     PodInitializing   0          33s
polkadot-node-3-0   0/1     PodInitializing   0          32s
polkadot-node-0-0   0/1     Running           0          56s
polkadot-node-2-0   0/1     Running           0          55s
polkadot-node-1-0   0/1     Running           0          57s
polkadot-node-3-0   0/1     Running           0          56s

*************************************************************
 Websockets endpoint available at ws://<IP_ADDRESS>:11000
*************************************************************
Done

*******************************************************************************
*******************************************************************************
 IMPORTANT: the raw seeds for the created accounts will be shown next.
 These seeds allow to gain control over the accounts represented by
 the keys. If you plan to use the new cluster for other than testing
 or trying the technology, please keep them safe. If you lose these
 seeds you won't be able to access the accounts. If anyone founds them,
 they can gain control over the accounts and any funds (test or real DOTs)
 stored in them.

Node 0:
  - stash:
    address: 5D51CnVArtUAQzSqkaVMgyhXMHy1xELbf2WmVsFHKsVEEoUe
    seed: 0xa1fbdf59f2beb3f0493dece20717f5569561a37cc3c810ac8bd47ed015a5c32d
  - controller:
    address: 5CiefGSQXvhpPrFCELn5jtBgLU5kRF5tVjEcC6zb3K8dWBfp
    seed: 0xf7be0282893ea5d4d8ee9e481ee907cfca96fbc184045f4cc9ba30fd5ddc5313
  - session:
    address: 5G1U1qKPGkLo1LFnvWQLt5ETKPGREHvVrEu2TA2LwikcvjHx
    seed: 0x4cc2744b1b9bb1b9fc695372de2eda51b151d6d02f30cb1309ef1bac51f21d13
Node 1:
  - stash:
    address: 5FbLJUrxuH5pNptrGfjQsGvrurdXDELscaWkbquUYr7SX4qY
    seed: 0x3ff11b66b00b9c889df8ef8b4bc2002ad21958406b5181b177836bff0d053c12
  - controller:
    address: 5DCJog9d2AMwdFewhxwNiVUroXy69Z1L6tN42f8zfTRrz7Dj
    seed: 0xe3eaeca0f8f52087feb7655ea7ff15d82792640ac60f977b225555a8b1f99e52
  - session:
    address: 5GhahwPiMif7X3BPJfxyFWVLSy34sTMxTDMtXYb4666BBTNe
    seed: 0xf43013c70f99db5dbd3e60871f9dba0e9c63bc38a09b1f1e9d86e510a19c9fb9
Node 2:
  - stash:
    address: 5GCcrzFRgVjcs3UgCy9BzXSuCcwaRDEM4pDctwNUwtWam9wV
    seed: 0xd87e7ac71efe178275844ca9f61e3579399b945906c7031e65d55cee5c649e06
  - controller:
    address: 5HGaQfHPKd6a9J6eZfWt3uHN63WWsvKzH3aaKC9C5fgUT7ac
    seed: 0x72e264cdf97aa5020e9a3db3e87f6b6c66f517579c0ca8db5db038047376e147
  - session:
    address: 5FNMozGBujjoewHQuV8Jz8UYEQbFTggpZQYZVZWB8rKj9ht6
    seed: 0xcfddada851ee00019bd41701e5c8a0b3a3fe8fd5989e48c3058172615b8829bd
Node 3:
  - stash:
    address: 5ELv8i7HQhLuZ78ALBXdUHfAPXXmB8rfeQGZ9owVrBLsYapt
    seed: 0x44109425a2727a53184e3c592f0cbea125c3385a33cc125b8c8ceb2a75f5def8
  - controller:
    address: 5Eynz9j8ommDPtMrHnUgmAJcJWwgrzBmQLifj9J4tEG3SXYF
    seed: 0x200f30ea8a924ad8fe4b7e34484700abaf8e1920faab22fc4e4482af9d34ac67
  - session:
    address: 5DEwpeDBJS83X7hkZHXL9b2BFCRBtqpmcqKudAubw5oPVKhM
    seed: 0x956b67e735fb25054fd949e2a341513b35919c0a8d003b8d95a52d6f6856cf31

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

polkadot-deployer list
┌──────────────┬─────────────────┬──────────────────────┬──────────┬─────────┬────────────────┐
│ Network name │ Deployment type │ WebSockets endpoint  │ Provider │ Workers │ Polkadot nodes │
├──────────────┼─────────────────┼──────────────────────┼──────────┼─────────┼────────────────┤
│ testnet1     │ local           │ ws://<IP_ADDRESS>:11000 │ kind     │ 1       │ 4              │
└──────────────┴─────────────────┴──────────────────────┴──────────┴─────────┴────────────────┘

polkadot-deployer destroy
? Select a deployment: testnet1
Deleting testnet1 cluster...
Done
Deleting deployment directory...
Done
Removing database entry...
Done

or without --verbose
polkadot-deployer create --config testnet1.json
Creating cluster 'testnet1'...
Done
Installling dependencies...
Done
Initializing nodes...
Done
Waiting for nodes ready...

*************************************************************
 Websockets endpoint available at ws://<IP_ADDRESS>:11000
*************************************************************
Done

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

 IMPORTANT: the raw seeds for the created accounts will be shown next.

 These seeds allow to gain control over the accounts represented by
 the keys. If you plan to use the new cluster for other than testing
 or trying the technology, please keep them safe. If you lose these
 seeds you won't be able to access the accounts. If anyone founds them,
 they can gain control over the accounts and any funds (test or real DOTs)
 stored in them.

Node 0:
  - stash:
    address: 5CknUBo6AuTBTrgAfT8S6fWKXP4qdj77iXwBQDnNUsUUHXdq
    seed: 0x11767d4fa809b398b891cbf6a364e96da45f95d7a628f46f74b6140e2faa735d

  - controller:
    address: 5HExHAh6XdKqhvxwpUdDNRUejVNzLiWJAPeBCfLkMxxs93Xf
    seed: 0xb0417aba02e50b681f6f41c4b2d92a0cb97ad9bf247182523746ef634a55a3a8

  - session:
    address: 5DhNSohasYrycdGAZ66Cv6q57FRtWc1eXRdatw6Uhi9jxuR2
    seed: 0x50e5b042b46607aa8708a03ffbc083372064fddbf39c4cf17e926da84596382e

Node 1:
  - stash:
    address: 5Ek25swumeW4DDFa9QDL2Atuj87JnZpnwLBjBXYL5DVXvJED
    seed: 0xbecc5daa09887bf3a680332da0de8a85f2fa13f7a0fdcbdb51827143b2d7f8d7

  - controller:
    address: 5DFqxQPa1qzyzfgqEgtG8ztFPLg5a6zeLBc3c7mm7NcDpPhK
    seed: 0x04bb3288ce7c806b5c05bc0a84ddb8bd372f72bf4bf0661b5ba67e6f7a7c5c84

  - session:
    address: 5CPtYySFKdBfsFaQh2oTeWuSLEu2ZMBSn8CogsYHzhMUtrSK
    seed: 0x949942ba23d1709d9666f430be0a17ea2eeaf90c974a01912a6ca05008d0ddea

Node 2:
  - stash:
    address: 5ECKrjt9KZG6kxDjQ7kZScYVsh75E4yfktF4xLTGxe8d7e7u
    seed: 0x6da72c69922fff65db92ae7e6c3cd50437aa4be1963ff86c04fdcc74f2921402

  - controller:
    address: 5EjnX7Pu2ZjXK64PYpGY41ViMJ1pJYQVA7uJTCQP2wKMoJun
    seed: 0xa2d9530f779ccdf03d072847b8d9a239f17d1ba7e1c0725fc70efd79de19154b

  - session:
    address: 5CYJPVTHEex4cWXV6KK5j1JhwsaV5Rh3ybh4LtVdKJS4xRNr
    seed: 0x37979895f12be42b89647da640955ff26ab57802ce792fa2e951d824bfedf325

Node 3:
  - stash:
    address: 5Cm18vMuW2y2bcj2fbFNxVxrUAGaBDtWBSdAUMenSVwAupbj
    seed: 0xb818d9c9df6578095a331789b85b484e4dc62ee5eae0228a83070fe8b4158598

  - controller:
    address: 5FC3nTqJBQFCv9YfXRNFUbKTAa1pVhD8WJMKnzWDu9YQoy1C
    seed: 0x5f8dcfa99a053f9fecde2017020435d73b1fcd26627600a16ddec5c99ff3d123

  - session:
    address: 5Ce1ZPfVwFgUkNfMtYyYspDytxz93RzyXTmBhoVx45pd8Hd4
    seed: 0xf2c09da7e688d65dc09c4f07ed24b4488a298dd3825e89d4adf2249407b902f6

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

well done!

This looks good, right?
Thank you so much for your time and efforts, @fgimenez !
Much appreciated.  Hope we meet in person one day.
Andreas

CanClose

This looks good, right?

Indeed, looks great! :tada:
Now you can see how things go and interact with the network using https://polkadot.js.org/apps, in Settings you can configure the endpoint to connect to, it is explained at the end of https://github.com/w3f/polkadot-deployer#create-options

Thank you so much for your time and efforts

Thanks also for your feedback! without it, this would not be possible all was working fine for me :P

Hope we meet in person one day.

Indeed that would be great :)


cmd/link: Setting rounding quantum to a value higher than 2M or smaller than 4K breaks.

What version of Go are you using (go version)?

$ go version
go version devel go1.22-856cf23a8a Thu Sep 14 05:14:44 2023 +0000 linux/arm64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

GO111MODULE='auto'
GOARCH='arm64'
GOBIN=''
GOCACHE='/home/fanzha02/.cache/go-build'
GOENV='/home/fanzha02/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/fanzha02/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/fanzha02/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/fanzha02/work/go_project/govscode/gomain'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/fanzha02/work/go_project/govscode/gomain/pkg/tool/linux_arm64'
GOVCS=''
GOVERSION='devel go1.22-856cf23a8a Thu Sep 14 05:14:44 2023 +0000'
GCCGO='gccgo'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/home/fanzha02/work/go_project/govscode/gomain/src/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3689557035=/tmp/go-build -gno-record-gcc-switches'
What did you do?

Build a hello.go with:
$ go build -ldflags "-R 0x300000" -o hello_3M hello.go
Run with:
$ ./hello_3M
What did you expect to see?
Hello world!
What did you see instead?
Segment fault

@cherrymui With fix patch #527822, trying different values of the -R flag, I noticed that the segment fault issue still occurs when passing value is larger than 2M or smaller than 4K on arm64 and amd64.
Output of compiling the program with -R 0x300000 on arm64 machine:
`$ readelf -l ./hello_3M
Elf file type is EXEC (Executable file)
Entry point 0x35e7e0
There are 6 program headers, starting at offset 64
Program Headers:
Type             Offset             VirtAddr           PhysAddr
FileSiz            MemSiz              Flags  Align
PHDR           0x0000000000000040 0x0000000000300040 0x0000000000300040
0x0000000000000150 0x0000000000000150  R      0x300000
readelf: Error: the PHDR segment is not covered by a LOAD segment
NOTE           0x0000000000000f9c 0x0000000000300f9c 0x0000000000300f9c
0x0000000000000064 0x0000000000000064  R      0x4
LOAD           0xffffffffffe00000 0x0000000000100000 0x0000000000100000
0x000000000027ae64 0x000000000027ae64  R E    0x300000
LOAD           0x0000000000100000 0x0000000000400000 0x0000000000400000
0x0000000000298740 0x0000000000298740  R      0x300000
LOAD           0x0000000000600000 0x0000000000900000 0x0000000000900000
0x00000000000095c0 0x0000000000041730  RW     0x300000
GNU_STACK     0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000  RW     0x8
Section to Segment mapping:
Segment Sections...
00
01     .note.go.buildid
02
03     .rodata .typelink .itablink .gosymtab .gopclntab
04     .go.buildinfo .noptrdata .data .bss .noptrbss
05
From the log, we can notice that the first program header offset is less than 0, which should be the cause of the segment fault.  I wonder if we need to add some checks that when setting-Ror-T` results in incorrect values, an error is reported instead of a clueless segment fault.

I came up with another solution that may solve this problem, that is, if the frag is greater than e.Off , the alignment will not be performed.
func fixElfPhdr(e *ElfPhdr) {
	frag := int(e.Vaddr & (e.Align - 1))

	e.Off -= uint64(frag)
	e.Vaddr -= uint64(frag)
	e.Paddr -= uint64(frag)
	e.Filesz += uint64(frag)
	e.Memsz += uint64(frag)
}

I don't think we really care about alignment less than 4K, which is the the minimal possible physical page size on many systems. If one sets -R less than 4K, it is asking for problems.
I'll look into the issue with alignment larger than 2M.
In the end we don't know or want to list exactly what memory layouts are supported on each system. We ensure the default works well. We do best effort support for some reasonable non-default values. Other than that, one is on their own.

0x300000 doesn't work not because it is larger than 2M, but because it is not a power of 2. 0x400000 does work. I think it is fine to reject -R value that is not a power of 2 or less than 4K. I don't think we need to go farther than that. I'll send a CL.

cc @golang/compiler


Issues creating a Rackconnected server

I am receiving the following error when trying to create a server in a Rackconnected region.
==> default: Launching a server with the following settings...
==> default:  -- Flavor: 4 GB General Purpose v1
==> default:  -- Image: Windows Server 2012 R2
==> default:  -- Networks: ["00000000-0000-0000-0000-000000000000", "11111111-1111-1111-1111-111111111111", "defined_network"]
==> default:  -- Name: vagrant_win_test
[fog][WARNING] Received exception '814: unexpected token at 'Forbidden
Access was denied to this resource.
Networks (00000000-0000-0000-0000-000000000000) not allowed  '' while decoding>> 403 Forbidden
I am able to create one successfully if I modify some code in the config.rb file to not pass in the public net id into the networks array.  Is there another way to modify how this can be set or disabled?
Thanks
Michael

@machodeveloper what code are you changing? I'm running into the same issue and when I modify the default networks in config.rb to not include the PUBLIC_NET_ID I still get the error.

Is there any additional info about how to solve this?


Make Contribution Document

This is something I always like to have in all documentations. Also because I am limited on time to contribute to this project I would like it if there were other contributors. I feel setting some basic good practice guidelines for contributing would help.

I already committed this, just forgot to include it in the commit message. Commit sha 026d4e500444ddd7ed307d8197b2ad07b949bb8c

Contribution doc is already made. it may need some updates but closing for now


Superset dashboard  or no data loading after login

Even after successful docker-compose up with latest updates from master branch after login welcome page keeps loading no dashboards  or no data can be seen.
Checked the logs for PostgreSQL in image no error or exception in logs.
Even executed docker-init.sh successfully.
Expected results
Superset should load default roles and dashboard after login.
Actual results
welcome page keeps loading after login, no dashboards  or no data can be seen.
Screenshots

How to reproduce the bug

Go to '...'
Click on '....'
Scroll down to '....'
See error

Environment
(please complete the following information):

superset version: superset version
python version: python --version
node.js version: node -v
npm version: npm -v

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[x] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[x] I have reproduced the issue with at least the latest released version of superset.
[x] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.93. Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

Please post docker-init logs from the superset-init container

I run the docker-init command twice (considering resources not downloaded on first attempt) so in logs it says admin user already exists.
Please find attached logs.
superset-init.log

ok, that seems more or less ok. Looking at the uploaded picture you provided it seems that the docker build step may have failed. Try issuing a docker-compose build first (after docker-compose down)

@swapnil-chenoa Are you sure you've waited for superset-node container to finish before loading page? Looks like you're missing JS files generated from webpack.

ok, that seems more or less ok. Looking at the uploaded picture you provided it seems that the docker build step may have failed. Try issuing a docker-compose build first (after docker-compose down)

Thanks for your response.
The docker build was successful with all 32 steps executed few container initialization failed so used docker-compose build command which was successful.
It took hours for 11th step to complete.
Step 11/32 : RUN cd /app/superset/assets         && npm run build         && rm -rf node_modules
---> Running in ec3cd24edd7d

<EMAIL_ADDRESS>build /app/superset/assets
cross-env NODE_OPTIONS=--max_old_space_size=8192 NODE_ENV=production webpack --mode=production --colors --progress
clean-webpack-plugin: /app/superset/assets/dist has been removed.
Starting type checking service...
Using 1 worker with 2048MB memory limit
92% chunk asset optimization OptimizeCssAssetsWebpackPluginBrowserslist: caniuse-lite is outdated. Please r 92% chunk asset optimization TerserPlugin

I  met the same problem as yours, how do you resolve it

@swapnil-chenoa Are you sure you've waited for superset-node container to finish before loading page? Looks like you're missing JS files generated from webpack.

Thanks for your response.
Yes we waited for same even for log-in page resources didn't load.
If we missed something how to recover JS files from webpack.

I met the same problem as yours, how do you resolve it

No that issue not yet resolved.
We are looking for solution.

my superset-work is unhealthy, do you have the same situation ？

my superset-work is unhealthy, do you have the same situation ？

No. all were in healthy state.

the default username & password is admin & admin ?

the default username & password is admin & admin ?

Yes its written in docker-init.sh.

I used  cd superset/assets \ && npm install \ && npm run build \ && rm -rf node_modules to resolve it, but i met another problem：

@flutterWang you have to wait for the superset-init to finish, it takes a while since it's upgrading the db, and downloading all the data for the examples dashboards

@dpgaspar

but my superset-init has been exited, did this mean it was finish?

seems like superset-init failed, can you post the full log?

This is happening to me as well on macosx

@dpgaspar

but my superset-init has been exited, did this mean it was finish?

@flutterWang - looks like you were running this while github was having some issues, as you can see from the SSL error. Were you able to retry this at all?

This is happening to me as well on macosx

@nabinkhadka - how much RAM are you allocating to your Docker VM? I'd recommend at least 4GB, as the default of 2 isn't enough to get Terser off the ground.

This is what I have.

Ok, I'll take a deeper look at this. I'm wondering if there's a way to disable Terser for local development 🤔 ...

@nabinkhadka I looked into the issue you merged #8883 , as I had the same error message.. turns out I was missing webpack.  npm update then retrying docker-compose up fixed the issue for me.

@nabinkhadka I looked into the issue you merged #8883 , as I had the same error message.. turns out I was missing webpack. npm update then retrying docker-compose up fixed the issue for me.

That worked for me!
Outside docker, on your local repo, you should enter superset/assets/ folder and run npm update.

@nabinkhadka I looked into the issue you merged #8883 , as I had the same error message.. turns out I was missing webpack. npm update then retrying docker-compose up fixed the issue for me.

That worked for me!
Outside docker, on your local repo, you should enter superset/assets/ folder and run npm update.
And the, as @nabinkhadka said run docker-compose up

superset/assets/ doesnt exist anymore. has it been renamed to something else?

@chongzixin yes, superset/assets/ has been moved to superset-frontend/

Hi all,
New to superset and your comments above have been really helpful.
I just downloaded superset yesterday and I am able to login without any errors but I am unable to view any charts or dashboards. I have run the npm update on superset/superset-frontend/
but still getting chart plugin errors when inspecting the code (screenshot attached).
Any help would be really useful.

Just follow along with the Dockerfile configuration and your compose file and things will be OK.
you might get into some errors which I never bumped into and based on your resources(RAM+CPU) and your internet speed you will face delays, it will usually take about 1 hour to install cause lets face it, you are basically running 4 or 5 services and each will interfere with each other, if you wait for all stages to finish and if you found any "unhealthy" status, just do the docker container restart [container-id]  and what @jpatdalton said about running the image as a build not docker up.
but also, do the npm update, do the restarting and give your server some fermentation time  :smile:
superset is a heavy software, it demands to check, restart and reboot a couple of times.
Good luck and thanks to the community.

I used cd superset/assets \ && npm install \ && npm run build \ && rm -rf node_modules to resolve it, but i met another problem：

I have the same problem.  Have you resolved?

If you get HTTP 401 errors from browser console, try remote admin accounts from superset's internal postgres database. (You'd need to know some postgres knowledges)
I resolved that by removing up admin account and rerun docker-compose up

my superset-work is unhealthy, do you have the same situation ？

I met the same problem as yours, how do you resolve it

my superset-work is unhealthy, do you have the same situation ？

@flutterWang I met the same problem as yours, how do you resolve it

This issue has not been resolved yet. I have more than 4GB of RAM allocated to Docker, I ran npm update in superset-frontend, I have waited over two hours after running docker-compose up and allowed all the images to finish installing packages and setting things up but still not getting anything to load after the login page. What is the magic trick do get a hello-world example running on MacOS? For reference, tried on MacOS 10.15.7. Getting this as output:
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/Nov/2020 22:49:43] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/Nov/2020 22:49:43] "GET /static/assets/theme.d16f7015.entry.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/Nov/2020 22:49:43] "GET /static/assets/theme.d16f7015.entry.js HTTP/1.1" 404 -
superset_app             | <IP_ADDRESS> - - [21/Nov/2020 22:49:43] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/Nov/2020 22:49:43] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | <IP_ADDRESS> - - [21/Nov/2020 22:49:43] "GET /static/assets/thumbnail.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/Nov/2020 22:49:43] "GET /static/assets/thumbnail.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | <IP_ADDRESS> - - [21/Nov/2020 22:49:43] "GET /static/assets/mathjs.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/Nov/2020 22:49:43] "GET /static/assets/mathjs.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | <IP_ADDRESS> - - [21/Nov/2020 22:49:43] "GET /static/assets/vendors.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/Nov/2020 22:49:43] "GET /static/assets/vendors.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | <IP_ADDRESS> - - [21/Nov/2020 22:49:44] "GET /static/assets/mathjs.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/Nov/2020 22:49:44] "GET /static/assets/mathjs.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | <IP_ADDRESS> - - [21/Nov/2020 22:49:44] "GET /static/assets/thumbnail.d16f7015.chunk.js HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/Nov/2020 22:49:44] "GET /static/assets/thumbnail.d16f7015.chunk.js HTTP/1.1" 404 -

Upon further inspection, I noticed that the superset_node container died. Here is the tail of the logs for it:
<s> [webpack.Progress] 94% after asset optimization
<s> [webpack.Progress] 94% after seal
<s> [webpack.Progress] 95% emitting
<s> [webpack.Progress] 95% emitting fork-ts-checker-webpack-plugin
<s> [webpack.Progress] 95% emitting clean-webpack-plugin
<s> [webpack.Progress] 95% emitting ManifestPlugin
Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR<EMAIL_ADDRESS>dev: `webpack --mode=development --colors --debug --watch`
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-11-21T22_04_07_103Z-debug.log
npm WARN using --force I sure hope you know what you are doing.
/usr/local/bin/webpack -> /usr/local/lib/node_modules/webpack/bin/webpack.js
/usr/local/bin/webpack-cli -> /usr/local/lib/node_modules/webpack-cli/bin/cli.js
+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>updated 2 packages in 7.314s
npm WARN using --force I sure hope you know what you are doing.

Upon further inspection, I noticed that the superset_node container died. Here is the tail of the logs for it:
<s> [webpack.Progress] 94% after asset optimization
<s> [webpack.Progress] 94% after seal
<s> [webpack.Progress] 95% emitting
<s> [webpack.Progress] 95% emitting fork-ts-checker-webpack-plugin
<s> [webpack.Progress] 95% emitting clean-webpack-plugin
<s> [webpack.Progress] 95% emitting ManifestPlugin
Killed
npm ERR! code ELIFECYCLE
npm ERR! errno 137
npm ERR<EMAIL_ADDRESS>dev: `webpack --mode=development --colors --debug --watch`
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-11-21T22_04_07_103Z-debug.log
npm WARN using --force I sure hope you know what you are doing.
/usr/local/bin/webpack -> /usr/local/lib/node_modules/webpack/bin/webpack.js
/usr/local/bin/webpack-cli -> /usr/local/lib/node_modules/webpack-cli/bin/cli.js
+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>updated 2 packages in 7.314s
npm WARN using --force I sure hope you know what you are doing.

Status 137 is out of memory.  Maybe 4 GB of RAM is not enough.  My docker has 5 GB of memory and 3 GB of swap on windows 10.  It works fine for me.

I had the same issue, in fact the container superset_node takes very long time for first npm-install (more than 20 minutes on my configuration)...
A tips in order to check if still working is to go into this container, then in /app/superset-frontend/node_modules or /app/superset-frontend/node_modules/.staging and do some ls -lah | wc -l. Normally, the number of folder will vary ;).

For docker users on mac who are familiar with kubernetes, docker provides the option to start a kubernetes engine locally.
Just do helm upgrade --install superset ./helm/superset will get you going without all the troubles.
Remember to do kubectl port-forward service/superset 8088:8088 after the installation is done.

docker-compose up - did not work . Showed same blank screen as mentioned in the question above
docker-compose -f docker-compose-non-dev.yml up - works

could someone help me resolving the same error disccussed above. i will appreciate your collaboration 💯


Test improvement: removed Magic Number test smell

This is a test refactoring
Problem:
The Magic Number Test occurs when assert() statements in a test method contain numeric literals (i.e., magic numbers) as parameters.
Solution:
As magic numbers do not indicate the meaning/purpose of the number, they should be replaced with constants or variables, thereby providing a descriptive name for the input.
Before:
assertEquals(200, i.getStatus());
After:
private final int HTTP_STATUS_OK = 200;
assertEquals(HTTP_STATUS_OK, i.getStatus());

Hi @ryber.
Thanks for the reply.
As you recommended, I have implemented a constant class that lists all status code.


Feature: Class to container Complex number

Hey, looks good, nice work. Some of the unit tests fail however. Also some methods have the Type template re-declared at function scope, perhaps that should be removed, or renamed to something else if they are meant to represent a different type?


Improvement: add gravity

It will be awesome to add gravity to each particle.
Changing angle is a quick idea but by adding an independant gravity using device sensor on each particle we will respond perfectly and the animation will also be perfect.

I was working on it but during the last period I was busy with some university exams.
I'll continue this feature as soon as possibile.
Thank for the advice

w00t, good luck, if you need some let me know.

Hi, I've added this feature but it is only in the beta version. I have to fix some little graphic bugs.
Link to Beta section in ReadMe:
Beta

just tested it, it seems to works great, you've added a limit to the rotation which seems a bit low, will be cool to have almost 90° rotation. Also, the gravity is fixed for each particle, it should change in live according the the orientationSensor

I've added this feature in the 1.2.0 versione, please check the new release.


Merge pull request #105 from ivanprado/master

Avoid including itemprop from child itemscopes when using itemref

Sync with base repo


Flaky SparkR test: test_sparkSQL.R: sample on a DataFrame

Make sample test less flaky by setting the seed
Tested with
repeat {  if (count(sample(df, FALSE, 0.1)) == 3) { break } }

@shivaram @adrian555

Merged build triggered.

Merged build started.

Test build #45320 has started for PR 9549 at commit 6869ba1.

Test build #45320 has finished for PR 9549 at commit 6869ba1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

LGTM. Thanks @felixcheung -- Merging this


Add links to the git repository into project_urls

Obsolete / done with the move to pyproject.toml.