Add config.ui.meta_image

This lets you set the meta_image that appears when sharing your Chainlit app, by default it is https://chainlit-cloud.s3.eu-west-3.amazonaws.com/logo/chainlit_banner.png but by adding to your config your own banner you can use your own.
e.g. within .chainlit/config.toml

[UI]
# Name of the app and chatbot.
name = "Your app name"

# the metadata image that appears when sharing links
meta_image = "https://chainlit-cloud.s3.eu-west-3.amazonaws.com/logo/chainlit_banner.png"

@tpatel I have updated the config as requested

Thanks for the update @MarkEdmondson1234, sorry I wasn't clear on all the things that needs to be updated. Here are some example from another PR:

You would need to create a python class for the meta object, and add it into the UISettings class, like in this PR: https://github.com/Chainlit/chainlit/pull/787/files#diff-e76edd7e411b9e044dbc1f307015efc5d8e83f7b254af919786191f86dfc7c74R192-R199
You would also need to update the frontend types to make sure they match the backend types, like in this PR: https://github.com/Chainlit/chainlit/pull/787/files#diff-e8a4293b0716fc7dcef3122181e5d41b58a52c46d779d352953bd0d41db43261R24-R29

Closing as the discussion has stopped, we can still reopen the PR in the future


Don't raise exception when sysctl is not ready

When /usr/sbin/sysctl is not available, it emits "[WARN] Command sysctl -a" does not exist.
That behavior is ok, but it should not raise exception by passing nil to readlines here.
Before:
/opt/fluent/lib/ruby/gems/3.2.0/gems/fluent-diagtool-1.0.4/lib/fluent/diagtool/validutils.rb:60:in
`readlines': no implicit conversion of nil into String (TypeError)
  File.readlines(sysctl_file).each{ |line|
                 ^^^^^^^^^^^
from /opt/fluent/lib/ruby/gems/3.2.0/gems/fluent-diagtool-1.0.4/lib/fluent/diagtool/validutils.rb:60:in `valid_sysctl'
from /opt/fluent/lib/ruby/gems/3.2.0/gems/fluent-diagtool-1.0.4/lib/fluent/diagtool/diagutils.rb:213:in `run_diagtool'
from /opt/fluent/lib/ruby/gems/3.2.0/gems/fluent-diagtool-1.0.4/exe/fluent-diagtool:41:in `<top (required)>'
from /opt/fluent/bin/fluent-diagtool:25:in `load'
from /opt/fluent/bin/fluent-diagtool:25:in `<main>'

[Collectutils] [WARN] Command sysctl -a does not exist -  skip collecting sysctl -a output
After:
[Diagtool] [INFO] [Collect] Collecting sysctl information...
[Collectutils] [WARN] Command sysctl2 -a does not exist -  skip collecting sysctl2 -a output
[Diagtool] [INFO] [Collect] sysctl information is stored in
[Diagtool] [INFO] [Valid] Validating sysctl information...
[Diagtool] [INFO] [Collect] Collecting ulimit information...
[Diagtool] [INFO] [Collect] ulimit information is stored in /tmp/20240318063926/output/sh_-c_'ulimit_-n'.txt
[Diagtool] [INFO] [Valid] Validating ulimit information...
[Validutils] [WARN]     ulimit => 1024 is incorrect, should be 65535
[Diagtool] [WARN] [Valid]    ulimit => 1024 is incorrect (recommendation is >65535)
[Diagtool] [INFO] [Collect] Generate tar file /tmp/diagout-20240318063926.tar.gz

you mean:
      sysctl = c.collect_cmd_output("sysctl -a")
      diaglogger_info("[Collect] sysctl information is stored in #{sysctl}")

      if sysctl
        diaglogger_info("[Valid] Validating sysctl information...")
        ...
      end

I mean
      diaglogger_info("[Collect] Collecting sysctl information...")
      sysctl = c.collect_cmd_output("sysctl -a")
      if sysctl
        diaglogger_info("[Collect] sysctl information is stored in #{sysctl}")

        diaglogger_info("[Valid] Validating sysctl information...")
        ret, sysctl = v.valid_sysctl(sysctl)
        list =  sysctl.keys
        list.each do |k|
          if sysctl[k]['result'] == 'correct'
            diaglogger_info("[Valid]    Sysctl: #{k} => #{sysctl[k]['value']} is correct (recommendation is #{sysctl[k]['recommend']})")
          elsif sysctl[k]['result'] == 'incorrect'
            diaglogger_warn("[Valid]    Sysctl: #{k} => #{sysctl[k]['value']} is incorrect (recommendation is #{sysctl[k]['recommend']})")
          end
        end
      end

or
      diaglogger_info("[Collect] Collecting sysctl information...")
      if sysctl = c.collect_cmd_output("sysctl -a")
        diaglogger_info("[Collect] sysctl information is stored in #{sysctl}")

        diaglogger_info("[Valid] Validating sysctl information...")
        ret, sysctl = v.valid_sysctl(sysctl)
        list =  sysctl.keys
        list.each do |k|
          if sysctl[k]['result'] == 'correct'
            diaglogger_info("[Valid]    Sysctl: #{k} => #{sysctl[k]['value']} is correct (recommendation is #{sysctl[k]['recommend']})")
          elsif sysctl[k]['result'] == 'incorrect'
            diaglogger_warn("[Valid]    Sysctl: #{k} => #{sysctl[k]['value']} is incorrect (recommendation is #{sysctl[k]['recommend']})")
          end
        end
      end

Thanks, I've fixed it.

It should be released as v1.0.5

Thanks!

Shouldn't we check it outside of valid_sysctl()?
We should skip the entire logic for sysctl if the result of collect_cmd_output("sysctl -a") is nill.

Sorry for not explaining the reason.
The reason is as follows.

valid_sysctl() should not care about whether the result of collect_cmd_output("sysctl -a") is nil or not because the methods are separated, and they should be independent of each other.
The entire logic for sysctl is completely meaningless when the result of collect_cmd_output("sysctl -a") is nil.


Execute termination actions on error lifecycle event

At our pipelines, we try to use the after and error lifecycle events in order to set Github statuses. The problem is that the after ones are correctly set, but the error ones no, Is like if this event handler doesn't wait until everything is finished (in very few cases the GitHub status job pod triggers and when this happens the github status pod finishes after the worker has finished). I guess that has something to do with this.
https://github.com/Azure/brigade/blob/a140145cd4200e9be358165978f0344c3a374a41/brigade-worker/src/app.ts#L106-L106
We are not "catching" errors when executing jobs or groups because this could make repetitive to handle in all different kind of event flows (push, pull_request, exec...).
Are we doing something wrong?

To make sure I understand, you have an error handler like this:
events.on("error", () => {
  console.log("do something");
});

But that error handler is never called?
It should be the case that the default error handler is called last. But maybe there is a bug and it's either being called first or not being called at all.

Yeah, it's called, but it doesn't wait to finish the handler.
Here is an example of a brigade.js file to reproduce the problem:
const { events, Job } = require("brigadier");

function exec(cmd) {
    let goBuild = new Job("brigade-test", "busybox");
    goBuild.tasks = [cmd]
    goBuild.run()
}

function sleepWithLog(ms, msg) {
    return new Promise(resolve => {
        console.log(msg)
        setTimeout(resolve, ms)
    });
}

function debug(e, project) {
    let times = 20
    let sleepMS = 500

    let sleepLoop = sleepWithLog(sleepMS, "------------------------start------------------------")
    Array.from({ length: times }, (x, i) => {
        sleepLoop = sleepLoop.then(() => sleepWithLog(sleepMS, i))
    });
    sleepLoop = sleepLoop.then(() => sleepWithLog(sleepMS, "------------------------end------------------------"))

    Promise.resolve(sleepLoop);
}

events.on("exec", () => {
    exec("echo 1")
});
events.on("exec-error", () => {
    exec("exit 1")
});

events.on("after", debug);
events.on("error", debug);

Doing brig run works ok, doing brig run -e exec-error doesn't.

Hmmm... this might be an esoteric issue with the way Node does the event handling. Once we sleep, Node will consider that part of the current tick to be done, and may then go on and execute the next event handler. That handler will exit the process. I'll have to see if there is a good way to work around that.


可以将此项目打包成可执行的exe文件吗

我试了几天 总是闪退

我也没成功，同求

You can try another open-source and free Puppet  https://github.com/atorber/puppet-bridge, which does not depend on Frida, is very easy to install, and has implemented nearly all the functionalities of puppet-xp, and even more.


Move all items from one list to another.

If the user wants to move all items to another list I would like to have a button so they don't have to drag each item individually.
I have it working just by moving the items in to the other array but then things get out of sync because I get this error when dragging items after the move: "Uncaught HierarchyRequestError: Failed to execute 'appendChild' on 'Node': The new child element contains the parent."
Seems like this would already be available, I just didn't see it mentioned in the docs.

right now this feature is not available.


Adjust payouts in comment incentives

We have recently implemented the "comment incentives" feature which adds payouts for issue comment contributions
We should:

make incentives for an original issue description greater than for a regular comment.
adjust payout amounts according to a currently set bot's param base-multiplier.

Original proposals:
Double the credit in the original post (e.g. the bounty specification should receive double credits like $0.2/word etc. to try and compensate for the time to think of the bounty in the first place.)

Read repository BASE_RATE from the ubiquibot-config.yml and multiply the output

What should be done:

Create a new bot's config param (smth like comment-incentive-origin-multiplier)
On comment incentive payout generation multiply pricing for original post (i.e. issue description) by the newly created config param from step 1
On comment incentive payout generation multiply total incentive reward by the base-multiplier bot's config param

How about issue-creator-multiplier?

How about issue-creator-multiplier?

seems fine, updated the description

Hi, @rndquu and @pavlovcik,
Could you please verify if my understanding is accurate? Let's assume that there are two multipliers: issue-creator-multiplier and issue-base-multiplier. When a comment is added to a specific issue, does the issue price increase by a factor of the issue-creator-multiplier, and do the comment incentives increase by a factor of the issue-base-multiplier?
Additionally, has the "comment incentives feature" been implemented?

/assign


Feature Request - Interface to see which blocks can / cannot be cached.

I'd like to see an interface where we can see which blocks are currently being cached. Here's a quick example I've got working by modifying the Caching panel. The downside, is it's not obvious which block on the page this is referring to, suggestions on how to do this better?
http://screencast.com/t/ukqiEpddst2

When I first read this I thought you meant a programming interface lol
On Mon, Jul 27, 2015, 3:54 PM TimDix<EMAIL_ADDRESS>wrote:

I'd like to see an interface where we can see which blocks are currently
being cached. Here's a quick example I've got working by modifying the
Caching panel. The downside, is it's not obvious which block on the page
this is referring to, suggestions on how to do this better?
http://screencast.com/t/ukqiEpddst2
—
Reply to this email directly or view it on GitHub
https://github.com/concrete5/concrete5/issues/2819.

Talking with @joe-meyer, we came up with this alternative interface to solve the same goal.
http://screencast.com/t/RxTuCMCj

@TimDix, is that just highlighting block areas that are not cached when the cache panel opens?

Yes, I had also had this one: http://screencast.com/t/JMOBmf1lkT - but it looked really busy.

@TimDix that panel-based interface (with the highlighted blocks on the right and the settings on the left) is really, really great. We'd want to make sure the options on the left match the style of the dark panel, but that's something we could add in afterwards. Cool idea, that would be very helpful.

this package does help with that, worked for 5.6 and now for 5.7 too
https://github.com/Remo/concrete5-cache-check
Your approach looks certainly nicer and is better integrated into concrete5, just for those who can't wait ;-)


I will beg every day of the year, my children's education is in your hands

@patricklodder Me and my family need your help, please help, I'm sure it will take a little of your time

@patricklodder dear Patrick, please help me and my family very much, you are our hope and future

@patricklodder, please help me, you are the only one who can help me now!

@patricklodder , please help me

@patricklodder, you are the only person who can change my life

dear Patrick, please do not pass by, I really hope for your help

Actually, I have a problem too.  Just logged into dogechain.info to check funds on my 3 wallets but they all show 0 balance!  I tried to sweep one of private keys but they no longer have any funds.  Does anybody know what could have happened?

@patricklodder I have a history of deposits on the exchange.
The account on the exchange was verified by the documents


Add maillist to README.

@tisonkun It makes sense to me. The slack channel link is also not the correct one. I don't have the invitation link now. Will involve JB to update later.

Closed as conflict and no activities. @Hexiaoqiao you may open another PR to finish the task based on the nightly default branch.


Output layers as CSS Cascade Layers [re-request]

Clear and concise description of the problem
Re-request of #3384: Output the UnoCSS layers as CSS Cascade Layers (@layer).
The PostCSS solution suggested there has limitations that aren't ideal.
Suggested solution
Add an option to the unocss config to do this.
Alternative
This could also be achieved with a transformer (I think... maybe).
Or maybe with a new mode for the Vite plugin.
Additional context
Using the PostCSS solution isn't ideal as the PostCSS integration has limitations that things like the Vite integration don't (e.g. #3192).
Validations

[X] Read the Contributing Guidelines.
[X] Read the README.md of using the package.
[X] Already used the Interactive Docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I would love even some limited support to pick a CSS layer for the pre-flight styles (as a workaround I could paste them manually) and the default constants (this is a blocker!).
The problem with constants is this: unocss emits some default constants, like
*, :before, :after {
  --uno-shadow-color: #0008;
}

Now if I'm defining some base components styles for my app using transformers, I might do this:
@layer components {
  button {
    @apply shadow-md shadow-blue;
  }
}

And this will not work as expected, did you spot why?
The shadow-blue rule will be inlined in my base components layer:
@layer components {
  button {
    box-shadow: 8px 8px var(--uno-shadow-color), ...;
    --uno-shadow-color: blue;
  }
}

But this has no effect because the default constant rule above says that for all * elements --uno-shadow-color: #0008, and since this default is not in a layer, it takes precedence over my @layer components button.


Traefik Ingress

Add docker-compose override to allow config via Traefik

Set SERVER_NAME in .env to match DNS Hostname (eg eproms.ubu.ivanc.dev.cirg.uw.edu)

Add docker-compose override for exposing port (current apache deploy method)

ports: section will be removed from docker-compose.yaml at a later date

@jhowe-uw
Can you take a look at this when you get a chance? I've got it deployed on eproms.ubu.ivanc.dev.cirg.uw.edu if you want to take a look at how it's set up.
Thanks!


Action row not show all elements

What version of Unfold are you using?
0.41.0 or main
What version of Django are you using?
5.1.1
What browser are you using?
Chrome 130.0.6723.119
Did you checked changelog/commit history, if the bug is not already fixed?
Yes
Did you searched other issues, if the bug is not already fixed?
Yes
Did you checked documentation?
Yes
Are you able to replicate the bug in the demo site?
No
Repository with reproduced bug
Create minimal repository where it is possible to reproduce an error.
Describe your issue
on action rows section all actions is shown but not all shown, its like sliced like this

its not fully shown elements, thank you

How did you rotated that dropdown and added these icons? Both things are not supported by default. Did you override the template?

i copied from changelist html dropdown, and using how_to_reg for icon to make dashboard that has dropdown for additional actions. From dashboard_callback wrap it using mark_safe. like this code
for acara in hariini:         result_hariini.append([             f"{hari[acara.tanggal.weekday()]}, " + acara.tanggal.strftime("%d %B %Y"),              f"{acara.golongan.nama}",              acara.babak.nama,              f"{acara.waktu_mulai.strftime('%H.%M')} - {acara.waktu_akhir.strftime('%H.%M')}",              mark_safe("""
more_horizco_present

"""),         ])
this the page

I believe this issue was fixed in the most recent update. But you have update your overridden template.


Creating a Laravel project fails, probably because FrankenPHP doesn't support -r flag

What happened?
When I try to create a new Laravel project with
 ./composer create-project laravel/laravel laraveltest

it fails with
> @php -r "file_exists('.env') || copy('.env.example', '.env');"

Warning: Unknown: Failed to open stream: No such file or directory in Unknown on line 0

Fatal error: Failed opening required '-r' (include_path='.:') in Unknown on line 0
Script @php -r "file_exists('.env') || copy('.env.example', '.env');" handling the post-root-package-install event returned with error code 255

The helper script composer is in the same directory and looks like this
#!/bin/bash
exec ./frankenphp-linux-x86_64 php-cli ./composer.phar $@

It looks like (at least) one step in creating the project tries to use php -r to execute PHP code without a file. As far as I can tell, FrankenPHP doesn't support the -r  flag yet. Some experiments underpin that
php -r "echo 'Hello';" # on a "regular" PHP installation, correctly prints 'Hello'

# compared with

./frankenphp-linux-x86_64 php-cli -r "echo 'Hello';"

Warning: Unknown: Failed to open stream: No such file or directory in Unknown on line 0

Fatal error: Failed opening required '-r' (include_path='.:') in Unknown on line 0

Build Type
Standalone binary
Worker Mode
Yes
Operating System
GNU/Linux
CPU Architecture
x86_64
PHP configuration
Not applicable, we don't get that far ;)

Relevant log output
No response

Indeed, -r isn't supported yet.


generateDebugSolution creates invalid /sources command line parameters in the csproj.user file

When running Sharpmake with /generateDebugSolution and passing multiple /source arguments to the original command line, the resulting csproj.user file has invalid syntax in the /source arguments. Eg.
original Sharpmake command line:
/generateDebugSolution /sources(@"d:\folder\file1.sharpmake.cs",@"d:\anotherfolder\anotherfile.sharpmake.cs")

the  tag in the generated csproj.user file however looks like this:
/sources(@'d:\folder\file1.sharpmake.cs;d:\anotherfolder\anotherfile.sharpmake.cs')

which is invalid and results in the following exception:
	The given path's format is not supported.

	Stack trace:
	Root stack trace:
   at System.Security.Permissions.FileIOPermission.EmulateFileIOPermissionChecks(String fullPath)
   at System.Security.Permissions.FileIOPermission.QuickDemand(FileIOPermissionAccess access, String fullPath, Boolean checkForDuplicates, Boolean needFullPath)
   at System.IO.Path.GetFullPath(String path)
   at Sharpmake.Application.Program.Argument.ValidateFiles(String[] files) in d:\github\sharpmake\Sharpmake.Application\CommandLineArguments.cs:line 395
   at Sharpmake.Application.Program.Argument.SetSources(String[] files) in d:\github\sharpmake\Sharpmake.Application\CommandLineArguments.cs:line 77
   at Sharpmake.Application.AssemblerBuildFunction_Class.AssemblerBuildFunction_Method(Object obj) in C:\Users\zsolt.molnar\AppData\Local\Temp\4f1cbb113bc64329af399dcbc4babefa.tmp:line 13
   at Sharpmake.CommandLine.Execute(Type type, Object instance, String commandLine, String[] namespaces) in d:\github\sharpmake\Sharpmake\CommandLine.cs:line 230
   at Sharpmake.CommandLine.ExecuteOnObject(Object obj, String commandLine, String[] namespaces) in d:\github\sharpmake\Sharpmake\CommandLine.cs:line 58
   at Sharpmake.CommandLine.ExecuteOnObject(Object obj, String commandLine) in d:\github\sharpmake\Sharpmake\CommandLine.cs:line 53
   at Sharpmake.CommandLine.ExecuteOnObject(Object obj) in d:\github\sharpmake\Sharpmake\CommandLine.cs:line 48
   at Sharpmake.Application.Program.Main() in d:\github\sharpmake\Sharpmake.Application\Program.cs:line 224

This patch fixes it, in DebugProjectGenerator.cs
        public static void SetupProjectOptions(this Project.Configuration conf, string startArguments)
        {
            conf.CsprojUserFile = new Project.Configuration.CsprojUserFileSettings();
            conf.CsprojUserFile.StartAction = Project.Configuration.CsprojUserFileSettings.StartActionSetting.Program;

            string quote = "\'"; // Use single quote that is cross platform safe

-            conf.CsprojUserFile.StartArguments = $@"/sources(@{quote}{string.Join(";", MainSources)}{quote}) {startArguments}";
+            conf.CsprojUserFile.StartArguments = $@"/sources(@{quote}{string.Join($"{quote},@{quote}", MainSources)}{quote}) {startArguments}";
            conf.CsprojUserFile.StartProgram = DebugProjectExtension.GetSharpmakeExecutableFullPath();
        }

I tested this with Sharpmake 0.16.0 on Windows 10.

Thanks for the detailed report and the fix! Could you send it as a pull request so it gets properly attributed to you?


Incorrect Environment variable GOROOT path

I am using windows 7 64 bit and downloaded the .msi for go.
The MSI sets the GOROOT at c:\go but the GOPATH is not set (contradicts the install docs)

Which docs state that GOROOT should point to the bin directory? c:\go is
the correct value for GOROOT.

@hc000 GOROOT should point to "c:/go" for specifying the version of go which you use(if you have few versions). The MSI sets automatically this. And GOPATH should point path you favorited for specifying the path that you will install third-party libraries or codes.
See http://golang.org/doc/code.html#GOPATH

Unless our docs are saying GOROOT should point to the bin directory,
this issue is working as intended.


RPKM, FPKM, and TPM-like normalization

Add a function for RPKM, FPKM, and TPKM-like normalization, given total counts. For example, to normalize read counts/depth from chromatin accessibility assays.

See normalization options offered by deepTools' bamCoverage.


Scientific Calculator

Scientific Calculator with UI changes 📜
A Scientific Calculator with  changes in UI and functions to make it look more attractive and varied a color to it. # <65>
Functionalities :-
• Addition
•Subtraction
•Division
•Multiplication
•log
•tangent
•sine
•cosine
•pi
•factorial
•percentage
•root
•x^n
##Built With :-
• Html, Css, Javascript

Checklist ✅

[✅] I follow Contributing Guidelines & Code of conduct of this project.
[✅] I have performed a self-review of my own code or work.
[✅] I have commented my code, particularly in hard-to-understand areas.
[✅] My changes generates no new warnings.
[✅] I'm GSSOC'22 contributor
[ ] Have you added a working video of your calculator ?

Screenshots / Gif (Optional) 📸

@Chayan-11 What can I add more features to it

It was not about adding features to this but it was already out there in our repository, you can look out for some unique calculators and then make a PR. Hope you get it!


Libvirt: add libvirt support and documentation

Still need to fix ip address assigning.

Still working on getting the expected IP address


Auto paragraph formatting not working on partial line deletion

Describe the bug
Auto paragraph formatting is no longer performed when a line is partially deleted
To Reproduce
Run vim -u NONE
Enter :set formatoptions=tcqbawn
Enter the following
a b
c

Navigate to the b in normal mode and type x or D. The line is not reformatted.
Expected behavior
Due to the trailing space after a, the c should be brought to the same line. Instead, no line adjustments are performed until either line is further modified.
Earlier versions do not seem to have this issue (how early I'm not sure, but confirmed does not exhibit this problem in version 8.0).
Screenshots
https://user-images.githubusercontent.com/4514942/102700134-0d956c00-4208-11eb-87b5-fda3cb741acf.mov
Environment (please complete the following information):
VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Dec 18 2020 12:03:54)
macOS version
Included patches: 1-2150
Compiled by Homebrew
Huge version without GUI.  Features included (+) or not (-):
+acl               -farsi             +mouse_sgr         +tag_binary
+arabic            +file_in_path      -mouse_sysmouse    -tag_old_static
+autocmd           +find_in_path      +mouse_urxvt       -tag_any_white
+autochdir         +float             +mouse_xterm       -tcl
-autoservername    +folding           +multi_byte        +termguicolors
-balloon_eval      -footer            +multi_lang        +terminal
+balloon_eval_term +fork()            -mzscheme          +terminfo
-browse            +gettext           +netbeans_intg     +termresponse
++builtin_terms    -hangul_input      +num64             +textobjects
+byte_offset       +iconv             +packages          +textprop
+channel           +insert_expand     +path_extra        +timers
+cindent           +ipv6              +perl              +title
-clientserver      +job               +persistent_undo   -toolbar
+clipboard         +jumplist          +popupwin          +user_commands
+cmdline_compl     +keymap            +postscript        +vartabs
+cmdline_hist      +lambda            +printer           +vertsplit
+cmdline_info      +langmap           +profile           +virtualedit
+comments          +libcall           -python            +visual
+conceal           +linebreak         +python3           +visualextra
+cryptv            +lispindent        +quickfix          +viminfo
+cscope            +listcmds          +reltime           +vreplace
+cursorbind        +localmap          +rightleft         +wildignore
+cursorshape       +lua               +ruby              +wildmenu
+dialog_con        +menu              +scrollbind        +windows
+diff              +mksession         +signs             +writebackup
+digraphs          +modify_fname      +smartindent       -X11
-dnd               +mouse             -sound             -xfontset
-ebcdic            -mouseshape        +spell             -xim
+emacs_tags        +mouse_dec         +startuptime       -xpm
+eval              -mouse_gpm         +statusline        -xsmp
+ex_extra          -mouse_jsbterm     -sun_workshop      -xterm_clipboard
+extra_search      +mouse_netterm     +syntax            -xterm_save
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
 2nd user vimrc file: "~/.vim/vimrc"
      user exrc file: "$HOME/.exrc"
       defaults file: "$VIMRUNTIME/defaults.vim"
  fall-back for $VIM: "/usr/local/share/vim"
Compilation: clang -c -I. -Iproto -DHAVE_CONFIG_H   -DMACOS_X -DMACOS_X_DARWIN  -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
Linking: clang   -L. -fstack-protector-strong -L/usr/local/lib -L/usr/local/opt/libyaml/lib<EMAIL_ADDRESS>-L/usr/local/opt/readline/lib  -L/usr/local/lib -o vim        -lm  -lncurses -liconv -lintl -framework AppKit  -L/usr/local/opt/lua/lib -llua5.4 -mmacosx-version-min=11.0 -fstack-protector-strong -L/usr/local/lib  -L/usr/local/Cellar/perl/5.32.0/lib/perl5/5.32.0/darwin-thread-multi-2level/CORE -lperl<EMAIL_ADDRESS>-lpython3.9 -framework CoreFoundation  -lruby.2.7  -L/usr/local/Cellar/ruby/2.7.2/lib

The same happens if you have:
a b
c

...(note there is now already a space after b), then navigate to a in normal mode and do dtb.
Behavior is different in Vim 8.0 (auto-formats line, bringing c on the same line as b) vs Vim 8.2 (does not auto-format line).


"No route to host" after initial installation

I tried to install k3s on ubuntu 16.04 and 18.04 and same error happens.
$ curl -sfL https://get.k3s.io | sh -

I used this command to install k3s.
Version:
$ k3s -v
k3s version v0.10.0 (f9888ca3)

Describe the bug
$ kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS             RESTARTS   AGE
kube-system   coredns-57d8bbb86-bvxhz                   1/1     Running            0          46s
kube-system   helm-install-traefik-p5hvk                0/1     Error              1          46s
kube-system   local-path-provisioner-58fb86bdfd-4hqbt   0/1     CrashLoopBackOff   2          46s

These two pods crash with "No route to host" errors.
$ kubectl logs -n kube-system helm-install-traefik-p5hvk
...
+ helm repo update --strict
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
Error: Update Failed. Check log for details
...Unable to get an update from the "stable" chart repository (https://kubernetes-charts.storage.googleapis.com):
        Get https://kubernetes-charts.storage.googleapis.com/index.yaml: dial tcp: lookup kubernetes-charts.storage.googleapis.com on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:38460-><IP_ADDRESS>:53: read: no route to host
...

To Reproduce
Just install k3s with this command: curl -sfL https://get.k3s.io | sh -
Expected behavior
k3s works fine.
Actual behavior
Two pods don't work.
I'm a beginner about kubernetes, so there may be something overlooked...

There shouldn't be any issues with k3s here; or at least I'm not aware of any issues presently. Is this issue still happening for you? It looks like a possible networking issue or something else funky is going on. Can the host reach kubernetes-charts.storage.googleapis.com ?
Have you taken a look at the network and ensured everything looks good?

Since I did nothing special other than installing k3s, I think the network is working fine.
$ ping kubernetes-charts.storage.googleapis.com
PING kubernetes-charts.storage.googleapis.com (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from nrt12s17-in-f16.1e100.net (<IP_ADDRESS>): icmp_seq=1 ttl=58 time=2.15 ms
64 bytes from nrt12s17-in-f16.1e100.net (<IP_ADDRESS>): icmp_seq=2 ttl=58 time=2.11 ms
64 bytes from nrt12s17-in-f16.1e100.net (<IP_ADDRESS>): icmp_seq=3 ttl=58 time=2.13 ms
64 bytes from nrt12s17-in-f16.1e100.net (<IP_ADDRESS>): icmp_seq=4 ttl=58 time=2.11 ms
64 bytes from nrt12s17-in-f16.1e100.net (<IP_ADDRESS>): icmp_seq=5 ttl=58 time=2.17 ms
64 bytes from nrt12s17-in-f16.1e100.net (<IP_ADDRESS>): icmp_seq=6 ttl=58 time=2.11 ms
64 bytes from nrt12s17-in-f16.1e100.net (<IP_ADDRESS>): icmp_seq=7 ttl=58 time=2.14 ms
64 bytes from nrt12s17-in-f16.1e100.net (<IP_ADDRESS>): icmp_seq=8 ttl=58 time=2.12 ms
64 bytes from nrt12s17-in-f16.1e100.net (<IP_ADDRESS>): icmp_seq=9 ttl=58 time=2.14 ms
64 bytes from nrt12s17-in-f16.1e100.net (<IP_ADDRESS>): icmp_seq=10 ttl=58 time=2.12 ms
64 bytes from nrt12s17-in-f16.1e100.net (<IP_ADDRESS>): icmp_seq=11 ttl=58 time=2.16 ms
^C
--- kubernetes-charts.storage.googleapis.com ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 10012ms
rtt min/avg/max/mdev = 2.114/2.137/2.178/0.065 ms

The host can reach kubernetes-charts.storage.googleapis.com.
And I realized that there's no helm-install pods now. I don't know why it was disappeared.
Now there is two pods and one of them failed to start with same error.
$ kubectl get pods -A
NAMESPACE     NAME                                      READY   STATUS             RESTARTS   AGE
kube-system   coredns-57d8bbb86-bvxhz                   1/1     Running            0          4d9h
kube-system   local-path-provisioner-58fb86bdfd-4hqbt   0/1     CrashLoopBackOff   1241       4d9h

$ kubectl logs local-path-provisioner-58fb86bdfd-4hqbt -n kube-system
time="2019-11-01T22:24:49Z" level=fatal msg="Error starting daemon: Cannot start Provisioner: failed to get Kubernetes server version: Get https://<IP_ADDRESS>:443/version?timeout=32s: dial tcp <IP_ADDRESS>:443: connect: no route to host"

What is the output of ip a and ip route?

Here.
$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 02:00:17:00:7a:99 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global ens3
       valid_lft forever preferred_lft forever
    inet6 fe80::17ff:fe00:7a99/64 scope link
       valid_lft forever preferred_lft forever
3: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8950 qdisc noqueue state UNKNOWN group default
    link/ether 72:c9:9b:5e:04:90 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/32 brd <IP_ADDRESS> scope global flannel.1
       valid_lft forever preferred_lft forever
    inet6 fe80::70c9:9bff:fe5e:490/64 scope link
       valid_lft forever preferred_lft forever
4: cni0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8950 qdisc noqueue state UP group default qlen 1000
    link/ether 8a:7d:d4:85:9f:30 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 scope global cni0
       valid_lft forever preferred_lft forever
    inet6 fe80::887d:d4ff:fe85:9f30/64 scope link
       valid_lft forever preferred_lft forever
5: veth3077c663@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8950 qdisc noqueue master cni0 state UP group default
    link/ether fa:93:80:e2:ca:d6 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    inet6 fe80::f893:80ff:fee2:cad6/64 scope link
       valid_lft forever preferred_lft forever
6: vethb6909f4b@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 8950 qdisc noqueue master cni0 state UP group default
    link/ether e6:14:78:1f:03:5a brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::e414:78ff:fe1f:35a/64 scope link
       valid_lft forever preferred_lft forever

$ ip route
default via <IP_ADDRESS> dev ens3
<IP_ADDRESS>/24 dev ens3  proto kernel  scope link  src <IP_ADDRESS>
<IP_ADDRESS>/24 dev cni0  proto kernel  scope link  src <IP_ADDRESS>

Thanks! Also, iptables --version and iptables-save?

OK
$ iptables --version
iptables v1.6.0

$ iptables-save
<no output>

Interesting that iptables-save has no output, the errors make sense if you have no iptables entries. Would you mind attaching the contents of /var/log/syslog to this issue? Are you able to give any more info about the environment you are using? (eg cloud or vm)

I'm using vm on Oracle Cloud.
And this is syslog.
syslog.txt

I installed on new machine.
How about this?
syslog.txt

Thanks, nothing pops out to me from the logs, looks like it should be creating iptables entries.
It looks like the network devices and route are created, but iptables-save is showing no entries (are you running the command as root?). Is Oracle doing anything special with iptables or firewalls here?

Sorry... I didn't use sudo when check iptables-save...
This is the output of sudo iptables-save.
$ sudo iptables-save
# Generated by iptables-save v1.6.0 on Wed Nov  6 21:31:52 2019
*nat
:PREROUTING ACCEPT [6:270]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [17:1130]
:POSTROUTING ACCEPT [17:1130]
:KUBE-MARK-DROP - [0:0]
:KUBE-MARK-MASQ - [0:0]
:KUBE-NODEPORTS - [0:0]
:KUBE-POSTROUTING - [0:0]
:KUBE-SEP-6KJXLLADRY4FRUOJ - [0:0]
:KUBE-SEP-HSRFD4S3AHFNRYNO - [0:0]
:KUBE-SEP-VOJ5KSDSMKF2NGVM - [0:0]
:KUBE-SEP-YP32F2HEJI64ZYJN - [0:0]
:KUBE-SERVICES - [0:0]
:KUBE-SVC-ERIFXISQEP7F7OF4 - [0:0]
:KUBE-SVC-JD5MR3NA4I4DYORP - [0:0]
:KUBE-SVC-NPX46M4PTMTKRN6Y - [0:0]
:KUBE-SVC-TCOU7JCQXEZGVUNU - [0:0]
-A PREROUTING -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A OUTPUT -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A POSTROUTING -m comment --comment "kubernetes postrouting rules" -j KUBE-POSTROUTING
-A POSTROUTING -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/16 -j RETURN
-A POSTROUTING -s <IP_ADDRESS>/16 ! -d <IP_ADDRESS>/4 -j MASQUERADE
-A POSTROUTING ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/24 -j RETURN
-A POSTROUTING ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/16 -j MASQUERADE
-A KUBE-MARK-DROP -j MARK --set-xmark 0x8000/0x8000
-A KUBE-MARK-MASQ -j MARK --set-xmark 0x4000/0x4000
-A KUBE-POSTROUTING -m comment --comment "kubernetes service traffic requiring SNAT" -m mark --mark 0x4000/0x4000 -j MASQUERADE
-A KUBE-SEP-6KJXLLADRY4FRUOJ -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-6KJXLLADRY4FRUOJ -p tcp -m tcp -j DNAT --to-destination <IP_ADDRESS>:9153
-A KUBE-SEP-HSRFD4S3AHFNRYNO -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-HSRFD4S3AHFNRYNO -p tcp -m tcp -j DNAT --to-destination <IP_ADDRESS>:6443
-A KUBE-SEP-VOJ5KSDSMKF2NGVM -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-VOJ5KSDSMKF2NGVM -p udp -m udp -j DNAT --to-destination <IP_ADDRESS>:53
-A KUBE-SEP-YP32F2HEJI64ZYJN -s <IP_ADDRESS>/32 -j KUBE-MARK-MASQ
-A KUBE-SEP-YP32F2HEJI64ZYJN -p tcp -m tcp -j DNAT --to-destination <IP_ADDRESS>:53
-A KUBE-SERVICES ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/32 -p udp -m comment --comment "kube-system/kube-dns:dns cluster IP" -m udp --dport 53 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d <IP_ADDRESS>/32 -p udp -m comment --comment "kube-system/kube-dns:dns cluster IP" -m udp --dport 53 -j KUBE-SVC-TCOU7JCQXEZGVUNU
-A KUBE-SERVICES ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/kube-dns:dns-tcp cluster IP" -m tcp --dport 53 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/kube-dns:dns-tcp cluster IP" -m tcp --dport 53 -j KUBE-SVC-ERIFXISQEP7F7OF4
-A KUBE-SERVICES ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/kube-dns:metrics cluster IP" -m tcp --dport 9153 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d <IP_ADDRESS>/32 -p tcp -m comment --comment "kube-system/kube-dns:metrics cluster IP" -m tcp --dport 9153 -j KUBE-SVC-JD5MR3NA4I4DYORP
-A KUBE-SERVICES ! -s <IP_ADDRESS>/16 -d <IP_ADDRESS>/32 -p tcp -m comment --comment "default/kubernetes:https cluster IP" -m tcp --dport 443 -j KUBE-MARK-MASQ
-A KUBE-SERVICES -d <IP_ADDRESS>/32 -p tcp -m comment --comment "default/kubernetes:https cluster IP" -m tcp --dport 443 -j KUBE-SVC-NPX46M4PTMTKRN6Y
-A KUBE-SERVICES -m comment --comment "kubernetes service nodeports; NOTE: this must be the last rule in this chain" -m addrtype --dst-type LOCAL -j KUBE-NODEPORTS
-A KUBE-SVC-ERIFXISQEP7F7OF4 -j KUBE-SEP-YP32F2HEJI64ZYJN
-A KUBE-SVC-JD5MR3NA4I4DYORP -j KUBE-SEP-6KJXLLADRY4FRUOJ
-A KUBE-SVC-NPX46M4PTMTKRN6Y -j KUBE-SEP-HSRFD4S3AHFNRYNO
-A KUBE-SVC-TCOU7JCQXEZGVUNU -j KUBE-SEP-VOJ5KSDSMKF2NGVM
COMMIT
# Completed on Wed Nov  6 21:31:52 2019
# Generated by iptables-save v1.6.0 on Wed Nov  6 21:31:52 2019
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [152:35760]
:InstanceServices - [0:0]
:KUBE-EXTERNAL-SERVICES - [0:0]
:KUBE-FIREWALL - [0:0]
:KUBE-FORWARD - [0:0]
:KUBE-SERVICES - [0:0]
-A INPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A INPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes externally-visible service portals" -j KUBE-EXTERNAL-SERVICES
-A INPUT -j KUBE-FIREWALL
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p udp -m udp --sport 123 -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -m comment --comment "kubernetes forwarding rules" -j KUBE-FORWARD
-A FORWARD -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -s <IP_ADDRESS>/16 -j ACCEPT
-A FORWARD -d <IP_ADDRESS>/16 -j ACCEPT
-A OUTPUT -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A OUTPUT -j KUBE-FIREWALL
-A OUTPUT -d <IP_ADDRESS>/16 -j InstanceServices
-A InstanceServices -d <IP_ADDRESS>/32 -p tcp -m owner --uid-owner 0 -m tcp --dport 3260 -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j ACCEPT
-A InstanceServices -d <IP_ADDRESS>/24 -p tcp -m owner --uid-owner 0 -m tcp --dport 3260 -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j ACCEPT
-A InstanceServices -d <IP_ADDRESS>/32 -p tcp -m tcp --dport 80 -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j ACCEPT
-A InstanceServices -d <IP_ADDRESS>/32 -p udp -m udp --dport 53 -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j ACCEPT
-A InstanceServices -d <IP_ADDRESS>/32 -p tcp -m tcp --dport 53 -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j ACCEPT
-A InstanceServices -d <IP_ADDRESS>/32 -p tcp -m owner --uid-owner 0 -m tcp --dport 80 -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j ACCEPT
-A InstanceServices -d <IP_ADDRESS>/32 -p tcp -m tcp --dport 80 -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j ACCEPT
-A InstanceServices -d <IP_ADDRESS>/32 -p tcp -m tcp --dport 80 -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j ACCEPT
-A InstanceServices -d <IP_ADDRESS>/32 -p udp -m udp --dport 67 -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j ACCEPT
-A InstanceServices -d <IP_ADDRESS>/32 -p udp -m udp --dport 69 -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j ACCEPT
-A InstanceServices -d <IP_ADDRESS>/32 -p udp -m udp --dport 123 -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j ACCEPT
-A InstanceServices -d <IP_ADDRESS>/16 -p tcp -m tcp -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j REJECT --reject-with tcp-reset
-A InstanceServices -d <IP_ADDRESS>/16 -p udp -m udp -m comment --comment "See the Oracle-Provided Images section in the Oracle Cloud Infrastructure documentation for security impact of modifying or removing this rule" -j REJECT --reject-with icmp-port-unreachable
-A KUBE-FIREWALL -m comment --comment "kubernetes firewall for dropping marked packets" -m mark --mark 0x8000/0x8000 -j DROP
-A KUBE-FORWARD -m conntrack --ctstate INVALID -j DROP
-A KUBE-FORWARD -m comment --comment "kubernetes forwarding rules" -m mark --mark 0x4000/0x4000 -j ACCEPT
-A KUBE-FORWARD -s <IP_ADDRESS>/16 -m comment --comment "kubernetes forwarding conntrack pod source rule" -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A KUBE-FORWARD -d <IP_ADDRESS>/16 -m comment --comment "kubernetes forwarding conntrack pod destination rule" -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
COMMIT
# Completed on Wed Nov  6 21:31:52 2019

Looks like Oracle's firewall is breaking things.

What should I do?

same problem, using oracle cloud ubuntu

@erikwilson After also running into this issue I dug deeper and found the culprit. I am on CentOS7 with the following iptables default configuration:
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT

By default this setup only allows SSH and rejects all other input and forward requests. Now when k3s starts itself the rules look like this (forward only):
-A FORWARD -m comment --comment "kubernetes forwarding rules" -j KUBE-FORWARD
-A FORWARD -m conntrack --ctstate NEW -m comment --comment "kubernetes service portals" -j KUBE-SERVICES
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -s <IP_ADDRESS>/16 -j ACCEPT
-A FORWARD -d <IP_ADDRESS>/16 -j ACCEPT

As you can see while the kubernetes forwarding rules and service portal are created properly, the flannel rules are just appened last and as such will just fail. You can find the relevant code in:
https://github.com/rancher/k3s/blob/405f85aa025fe4ce2f74f19916eeadb5dcac8e08/pkg/agent/flannel/flannel.go#L70-L71
Interestingly enough there is a similar rule in the KUBE-FORWARD chain:
-A KUBE-FORWARD -s <IP_ADDRESS>/16 -m comment --comment "kubernetes forwarding conntrack pod source rule" -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
-A KUBE-FORWARD -d <IP_ADDRESS>/16 -m comment --comment "kubernetes forwarding conntrack pod destination rule" -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT

But this one only accepts already established connections, so it won't help here. All in all I do not think that the existing firewalls are to blame here, but k3s creating it's rules in the wrong place.

Note: Just moving the rules before the REJECT doesn't seem to be enough, I have to check where else it triggers failures :( [Removing the default REJECT does fix it]

Okay, I have got it. The default INPUT rules also drop everything, so one needs to (for instance) add:
iptables -I INPUT 3 -s <IP_ADDRESS>/16 -j ACCEPT
iptables -I INPUT 3 -d <IP_ADDRESS>/16 -j ACCEPT

The better option is probably to add rules to allow traffic through the cni0 interface. Either way, to summarize I can say:
If there are rules in the foward or input chains that reject any traffic, k3s will not work

A working iptables configuration with comments where I added rules and what they look like:
# Generated by iptables-save v1.4.21 on Mon Nov 11 16:51:13 2019
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [51:25393]
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
# Added my rules
-A INPUT -s <IP_ADDRESS>/16 -j ACCEPT
-A INPUT -d <IP_ADDRESS>/16 -j ACCEPT
-A INPUT -j LOG --log-prefix "IPTables-Reject-Input: " --log-level 4
# End added my rules
-A INPUT -j REJECT --reject-with icmp-host-prohibited
# Added my rules
-A FORWARD -s <IP_ADDRESS>/16 -j ACCEPT
-A FORWARD -d <IP_ADDRESS>/16 -j ACCEPT
-A FORWARD -j LOG --log-prefix "IPTables-Reject-Forward: " --log-level 4
# End added my rules
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Completed on Mon Nov 11 16:51:13 2019
# Generated by iptables-save v1.4.21 on Mon Nov 11 16:51:13 2019
*nat
:PREROUTING ACCEPT [17:964]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT
# Completed on Mon Nov 11 16:51:13 2019

In general I think it would be good to allow INPUTs on cni0 instead of the source addr, but it illustrates the issue nicely. If you drop the added accepts the kernel will show you the rejections:
Nov 11 17:10:49 infra01 kernel: IPTables-Reject-Input: IN=cni0 OUT= PHYSIN=veth3a22aa74 MAC=3e:3a:0a:8c:95:78:72:c4:80:d8:db:e9:08:00 SRC=<IP_ADDRESS> DST=<IP_ADDRESS> LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=20683 DF PROTO=TCP SPT=36444 DPT=6443 WINDOW=28200 RES=0x00 SYN URGP=0

Here the pod tries to talk to the kube master on the same host but the INPUT rule forbids it.

I guess my issue is also connected with this: https://github.com/rancher/k3s/issues/1247

A working iptables configuration with comments where I added rules and what they look like:
# Generated by iptables-save v1.4.21 on Mon Nov 11 16:51:13 2019
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [51:25393]
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
# Added my rules
-A INPUT -s <IP_ADDRESS>/16 -j ACCEPT
-A INPUT -d <IP_ADDRESS>/16 -j ACCEPT
-A INPUT -j LOG --log-prefix "IPTables-Reject-Input: " --log-level 4
# End added my rules
-A INPUT -j REJECT --reject-with icmp-host-prohibited
# Added my rules
-A FORWARD -s <IP_ADDRESS>/16 -j ACCEPT
-A FORWARD -d <IP_ADDRESS>/16 -j ACCEPT
-A FORWARD -j LOG --log-prefix "IPTables-Reject-Forward: " --log-level 4
# End added my rules
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Completed on Mon Nov 11 16:51:13 2019
# Generated by iptables-save v1.4.21 on Mon Nov 11 16:51:13 2019
*nat
:PREROUTING ACCEPT [17:964]
:INPUT ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:POSTROUTING ACCEPT [0:0]
COMMIT
# Completed on Mon Nov 11 16:51:13 2019

In general I think it would be good to allow INPUTs on cni0 instead of the source addr, but it illustrates the issue nicely. If you drop the added accepts the kernel will show you the rejections:
Nov 11 17:10:49 infra01 kernel: IPTables-Reject-Input: IN=cni0 OUT= PHYSIN=veth3a22aa74 MAC=3e:3a:0a:8c:95:78:72:c4:80:d8:db:e9:08:00 SRC=<IP_ADDRESS> DST=<IP_ADDRESS> LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=20683 DF PROTO=TCP SPT=36444 DPT=6443 WINDOW=28200 RES=0x00 SYN URGP=0

Here the pod tries to talk to the kube master on the same host but the INPUT rule forbids it.

you're the man! this fixes it for me on centos8.
now we just need to get it working with firewalld.
for plain podman i had to add the firewalld plugin to the cni config, maybe this needs to be done here as well ?

what's the proper fix for this?

Just in case if somebody faced the same on Oracle Cloud 9:
sudo firewall-cmd --add-port=6443/tcp

No other changes to iptables needed.
Also add Ingress Rule limiting to the internal network:

To join a master node use internal node's hostname or IP (i.e. 10.0.0.X):
sudo k3s agent --server https://k3s-master.subnetXXX.vcnYYYY.oraclevcn.com:6443 --token "${TOKEN}"


retain bit is not maintained over mosquitto bridge

Comment
I emailed this to<EMAIL_ADDRESS>but after initial receipt response no further communication was received, so I thought I'd just record this issue here.
Environment

OS: Debian 9
Erlang/OTP: R20/9.0
EMQ: emqttd-2.3-beta.4

Description
It looks like the retain bit is not maintained while bridging to mosquitto.
I have emqttd setup so that the internal listener listens on <IP_ADDRESS>:1883.
I then have a bridge in mosquitto setup like this:
connection emq
address <IP_ADDRESS>:1883
topic building/pisec/# in 1
try_private true
bridge_protocol_version mqttv311

I publish first a retained value to mosquitto:
mosquitto_pub -t "building/pisec/FX00.07" -m "open" -p 21883 -r
Then I listen to mosquitto:
mosquitto_sub -t "building/pisec/FX00.07" -p 21883 -v
And I publish to emqttd like this:
mosquitto_pub -t "building/pisec/FX00.07" -m "closed" -r
And out of the listener I see what I expect:
building/pisec/FX00.07 closed
But when I run the listener again to see the retained message
mosquitto_sub -t "building/pisec/FX00.07" -p 21883 -v -C 1
Then I get the previous retained value (that I sent directly to mosquitto before)
building/pisec/FX00.07 open
So, in other words: The bridge between mosquitto and emqttd is working, but the retained bit is lost in the process. I believe this is what mosquitto uses the "try_private" flag for. I have been able to bridge mosquitto to mosquitto and then the retain bit is carried to the other broker.
So my thought is that emqttd does not forward the retain bit. Is that true?

I see that 2.3-rc.2 has been released. Has this been fixed?

@victorclaessen, The MQTT v3.1.1 specification on this issue:
It MUST set the RETAIN flag to 0 when a PUBLISH Packet is sent to a Client because it matches an established subscription regardless of how the flag was set in the message it received [MQTT-3.3.1-9].

Well, then I suppose we'd better call this a feature request.
From the mqtt.org wiki at https://github.com/mqtt/mqtt.github.io/wiki/bridge_protocol :

RSMB added (and Mosquitto followed) a non-spec feature that allows an RSMB
to recognise an inbound connection as another RSMB bridge. From a thread on the google group:

You are right, RSMB recognizes when another RSMB connects to it via a bridge
by using a different protocol version number (when try_private is true, which is the default).
If that connect fails, then the bridge will fall back to MQTT 3.1. This internal protocol is
the same as MQTT 3.1 except that:

        the retained flags are propagated on publish packets,
        and the subscriptions are nolocal (in the JMS sense),
        to reduce the chances of infinite message loops.

This behaviour is easy to apply when the broker is the one making the bridge (outgoing topics)
because it knows that the client is a bridge. For incoming topics the different protocol
number is used. The protocol number is the actual protocol number (3) OR'd with 128 (bit 8).

Both RSMB and Mosquitto implement this behaviour - but it is not a formal part
of the protocol specification.```

@victorclaessen Plan to implement the feature in version 2.3.1, which will be released next weekend;)

That is awesome!

@victorclaessen The issue has been fixed in develop branch:
https://github.com/emqtt/emqttd/commit/26fb809dbed287854cee2d97fb717cb72751649c
Build EMQ from source of develop branch:
git clone -b develop https://github.com/emqtt/emq-relx.git
cd emq-rel && make run

That is great. Can't wait for the next release!
So I took a fresh Debian 9 VM, and did:
apt-get install erlang
git clone -b develop https://github.com/emqtt/emq-relx.git
cd emq-relx && make run

The (last part of) the output is:
===> Starting relx build process ...
===> Resolving OTP Applications from directories:
          /opt/emq-relx/deps
          /usr/lib/erlang/lib
          /opt/emq-relx/apps
===> Resolved emqttd-2.3.1
===> Including Erts from /usr/lib/erlang
===> release successfully created!
Exec: /opt/emq-relx/_rel/emqttd/erts-8.2.1/bin/erlexec -boot /opt/emq-relx/_rel/emqttd/releases/2.3.1/emqttd -mode embedded -boot_var ERTS_LIB_DIR /opt/emq-relx/_rel/emqttd/erts-8.2.1/../lib -mnesia dir<EMAIL_ADDRESS>-config /opt/emq-relx/_rel/emqttd/data/configs/app.2<IP_ADDRESS>.17.49.config -args_file /opt/emq-relx/_rel/emqttd/data/configs/vm.2<IP_ADDRESS>.17.49.args -vm_args /opt/emq-relx/_rel/emqttd/data/configs/vm.2<IP_ADDRESS>.17.49.args -- console
Root: /opt/emq-relx/_rel/emqttd
/opt/emq-relx/_rel/emqttd
Protocol 'inet_tcp': the name<EMAIL_ADDRESS>seems to be in use by another Erlang node
erlang.mk:2499: recipe for target 'run' failed
make: *** [run] Error 1

And if I try:
cd bin
./emqttd console

I get:
./emqttd: 20: ./emqttd: runner_log_dir: not found

@ victorclaessen First ps -ef | grep beam to check if there is already a running EMQ. Kill it and then make run or make && cd _rel/emqttd && ./bin/emqttd console:)

My apologies, it appears this VM was not as clean I thought. I cleared the existing beam process, and then started with make run.
I now run into the following problem. When I publish something (directly) to emqtt broker, the message is only accepted if the retain flag is set.
root@n014085:~# mosquitto_sub -t "building/#" -v &
root@n014085:~# mosquitto_pub -t "building/pisec/FX00.00" -m "closed"
root@n014085:~# mosquitto_pub -t "building/pisec/FX00.00" -m "closed" -r
building/pisec/FX00.00 closed

The output of emqttd in the console is this:
=INFO REPORT==== 29-Nov-2017::15:04:44 ===
    alarm_handler: {set,{system_memory_high_watermark,[]}}
starting emqttd on node<EMAIL_ADDRESS>emqttd ctl is starting...[ok]
emqttd hook is starting...[ok]
emqttd router is starting...[ok]
emqttd pubsub is starting...[ok]
emqttd stats is starting...[ok]
emqttd metrics is starting...[ok]
emqttd pooler is starting...[ok]
emqttd trace is starting...[ok]
emqttd client manager is starting...[ok]
emqttd session manager is starting...[ok]
emqttd session supervisor is starting...[ok]
emqttd wsclient supervisor is starting...[ok]
emqttd broker is starting...[ok]
emqttd alarm is starting...[ok]
emqttd mod supervisor is starting...[ok]
emqttd bridge supervisor is starting...[ok]
emqttd access control is starting...[ok]
emqttd system monitor is starting...[ok]
emqttd 2.3.0 is running now
Eshell V8.2.1  (abort with ^G)
(emq@<IP_ADDRESS>)1> Load emq_mod_presence module successfully.
dashboard:http listen on <IP_ADDRESS>:18083 with 2 acceptors.
mqtt:tcp listen on <IP_ADDRESS>:11883 with 16 acceptors.
mqtt:tcp listen on <IP_ADDRESS>:1883 with 16 acceptors.
mqtt:ws listen on <IP_ADDRESS>:8083 with 4 acceptors.
mqtt:ssl listen on <IP_ADDRESS>:8883 with 16 acceptors.
mqtt:wss listen on <IP_ADDRESS>:8084 with 4 acceptors.
mqtt:api listen on <IP_ADDRESS>:8080 with 4 acceptors.
15:05:18.498 [error] gen_server <0.1458.0> terminated with reason: no function clause matching emqttd_protocol:clean_retain(false, {mqtt_message,<<0,5,95,31,160,29,251,167,110,124,0,0,5,185,0,1>>,undefined,{<<"mosqpub/5098-n0140...">>,...},...}) line 553
15:05:18.499 [error] CRASH REPORT Process <0.1458.0> with 0 neighbours exited with reason: no function clause matching emqttd_protocol:clean_retain(false, {mqtt_message,<<0,5,95,31,160,29,251,167,110,124,0,0,5,185,0,1>>,undefined,{<<"mosqpub/5098-n0140...">>,...},...}) line 553 in gen_server2:terminate/3 line 1157
15:05:18.499 [error] gen_server <0.1457.0> terminated with reason: no function clause matching emqttd_protocol:clean_retain(false, {mqtt_message,<<0,5,95,31,160,29,251,167,110,124,0,0,5,185,0,1>>,undefined,{<<"mosqpub/5098-n0140...">>,...},...}) line 553
15:05:18.499 [error] CRASH REPORT Process <0.1457.0> with 0 neighbours exited with reason: no function clause matching emqttd_protocol:clean_retain(false, {mqtt_message,<<0,5,95,31,160,29,251,167,110,124,0,0,5,185,0,1>>,undefined,{<<"mosqpub/5098-n0140...">>,...},...}) line 553 in gen_server2:terminate/3 line 1157
15:05:18.500 [error] gen_server <0.1459.0> terminated with reason: no function clause matching emqttd_protocol:clean_retain(false, {mqtt_message,<<0,5,95,31,160,29,251,167,110,124,0,0,5,185,0,1>>,undefined,{<<"mosqpub/5098-n0140...">>,...},...}) line 553
15:05:18.500 [error] Supervisor 'esockd_connection_sup - <0.1394.0>' had child connection started with emqttd_client:start_link([{max_publish_rate,0},{client_idle_timeout,30000},{client_enable_stats,false},{max_clientid_len,...},...]) at <0.1458.0> exit with reason no function clause matching emqttd_protocol:clean_retain(false, {mqtt_message,<<0,5,95,31,160,29,251,167,110,124,0,0,5,185,0,1>>,undefined,{<<"mosqpub/5098-n0140...">>,...},...}) line 553 in context connection_crashed
15:05:18.501 [error] Supervisor 'esockd_connection_sup - <0.1394.0>' had child connection started with emqttd_client:start_link([{max_publish_rate,0},{client_idle_timeout,30000},{client_enable_stats,false},{max_clientid_len,...},...]) at <0.1457.0> exit with reason no function clause matching emqttd_protocol:clean_retain(false, {mqtt_message,<<0,5,95,31,160,29,251,167,110,124,0,0,5,185,0,1>>,undefined,{<<"mosqpub/5098-n0140...">>,...},...}) line 553 in context connection_crashed
15:05:18.501 [error] CRASH REPORT Process <0.1459.0> with 0 neighbours exited with reason: no function clause matching emqttd_protocol:clean_retain(false, {mqtt_message,<<0,5,95,31,160,29,251,167,110,124,0,0,5,185,0,1>>,undefined,{<<"mosqpub/5098-n0140...">>,...},...}) line 553 in gen_server2:terminate/3 line 1157
15:05:18.501 [error] Supervisor 'esockd_connection_sup - <0.1394.0>' had child connection started with emqttd_client:start_link([{max_publish_rate,0},{client_idle_timeout,30000},{client_enable_stats,false},{max_clientid_len,...},...]) at <0.1459.0> exit with reason no function clause matching emqttd_protocol:clean_retain(false, {mqtt_message,<<0,5,95,31,160,29,251,167,110,124,0,0,5,185,0,1>>,undefined,{<<"mosqpub/5098-n0140...">>,...},...}) line 553 in context connection_crashed

That 15:05:18.498 crash report was when I published without the retain flag (and before I published the same message with the retain flag).

@victorclaessen cd deps/emqttd && git pull and then make run again.
@huangdan Please add unit test cases for the clean_retain/2 function.

Ok, now the crash does not occur anymore, and the message is propagated.
Also, I can confirm that the retain flag is carried across the bridge if (and only if) try_private is set to true in the mosquitto configuration.
Thanks a lot, this makes bridging much more flexible and useful!


add support for shorthand npx command

I'm interested to try using this package in my CI setup,
currently my setup uses s3-directory-sync-cli and s3-invalidate-cloudfront-id in this sort of way, where env vars are defined and then the npm package is called,
S3_DIRECTORY_SYNC_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID \
S3_DIRECTORY_SYNC_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY \
S3_DIRECTORY_SYNC_BUCKET=$AWS_BUCKET_NAME \
S3_DIRECTORY_SYNC_LOCAL_DIRECTORY=build \
S3_DIRECTORY_SYNC_DRIVE_CONTENT_TYPE="true" \
npx @foo-software/s3-directory-sync-cli
S3_INVALIDATE_CLOUDFRONT_REGION=eu-central-1 \
S3_INVALIDATE_CLOUDFRONT_ACCESS_KEY_ID=$AWS_ACCESS_KEY_ID \
S3_INVALIDATE_CLOUDFRONT_SECRET_ACCESS_KEY=$AWS_SECRET_ACCESS_KEY \
S3_INVALIDATE_CLOUDFRONT_IDS=E29BKF76GZ5 \
npx s3-invalidate-cloudfront-id

Using npx this way allows me to use these packages in CI pipelines without updating my package.json or adding config files. npx uses the 'bin' namespace to define an entry point.
Would s3-sync-client add support for npx usage?

Does s3-sync-client support compression in any way? A similar package added support for GZIP compression here.
Thanks!

Hello there,
First, about a CLI wrapper (e.g. npx usage)
I understand the use case but I'm not a fan of supporting it natively for two reasons:

Using this module as a CLI would be an edge case since https://awscli.amazonaws.com/v2/documentation/api/latest/reference/s3/sync.html already exists. I understand you can't use the official CLI in CI but that would remain an edge case for this module.
It's too much work to do for an edge case. Wrapping advanced options such as https://github.com/jeanbmar/s3-sync-client#use-aws-sdk-command-input-options would require additional dependencies and logic that exceed the purpose of syncing objects.

Then, about the compression requirements
My understanding is that you want to store gzipped files in S3 so they can be served compressed without further processing by your website.
This module can't do file compression. It would imply to:

Compress files before everything for progress tracking
Compute ContentLength and ContentEncoding
Doing object diff on local uncompressed files and remote compressed files before doing syncing.
I believe it drifts too much from the purpose of syncing.

In this situation I would manage compression before using the sync module.
Overall, I'm not sure you need a sync tool. It looks like you need instead an upload / deploy tool.
Have you considered using the official https://github.com/aws/aws-sdk-js-v3/tree/main/lib/lib-storage?
There's no CLI either but it would be easier to manage file compression since data go in only one direction.

thanks for you reply @jeanbmar I will consider those points


⚠ Visual-Crew_Builder has degraded performance

In 406b7f6, Visual-Crew_Builder (https://visual-crew-builder.ai) experienced degraded performance:

HTTP code: 200
Response time: 2046 ms

Resolved: Visual-Crew_Builder performance has improved in 554e397 after 9 minutes.


fix exception when airflow home is null

Not sure if there's an issue, this fixes the following though and adds a test
REPRO:
(1) export AIRFLOW_HOME=
(2) airflow list_dags
EXPECTED: uses default airflow home or at least fails in a reasonable way
ACTUAL: fails with a stack trace
Traceback (most recent call last):
  File "/usr/local/bin/airflow", line 17, in <module>
    from airflow import configuration
  File "/usr/local/lib/python2.7/site-packages/airflow/__init__.py", line 29, in <module>
    from airflow import configuration as conf
  File "/usr/local/lib/python2.7/site-packages/airflow/configuration.py", line 723, in <module>
    mkdir_p(AIRFLOW_HOME)
  File "/usr/local/lib/python2.7/site-packages/airflow/configuration.py", line 712, in mkdir_p
    raise AirflowConfigException('Had trouble creating a directory')
airflow.exceptions.AirflowConfigException: Had trouble creating a directory

This addresses JIRA issue https://issues.apache.org/jira/browse/AIRFLOW-2262


docs: add description for input type range

Fixes Issue
**My PR closes #371 **
👨💻 Changes proposed(What did you do ?)

added description for input type range in readme

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title and description of the PR is clear and explains the approach.

:tada: This PR is included in version 2.46.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


USER STORY: Responsive UI

As an developer, I want to be able to view the nav bar hamburger menu when the screen is between 600px and 900px widths. At the moment, the page crops out the hamburger menu and parts of the screen when the window is shrunk. I want to adjust the styling of the page so page elements on all pages are not broken or cropped or off-screen for mobile screens.
Issue:

[x] #414

Closing since we no longer use user story issues.


[Auto-Complete] Investigate the validation of URL using ABNF syntax

Currently, our only validate white spaces in URLs ( to be confirmed with developers).
The aim is to have a full on validation using the ABNF syntax

Yes. We currently only raise invalid whitespace error.
What kind of extra validation are we looking at @RabebOthmani? ABNF is very general

@Onokaev  ABNF itself is generic,  but this ABNF description https://github.com/oasis-tcs/odata-abnf/blob/main/abnf/odata-abnf-construction-rules.txt is specific to validating OData.  It contains specific syntax rules for OData URLs including validating query parameter values.

@Onokaev Do you feel like you have clarity on the task with the link provided by Darrel? Let me know if you need further details

Hey @RabebOthmani, @thewahome picked this up since he is already working on autocomplete.

I am closing this since the investigation was successful and documented in a technical document.
A PR exists that attempts to implement the findings for this under #2044


Official support for mingw-64

The official documentation lists mingw-w64 as unsupported toolchain, but it seems that the latest mingw-64 distribution works like charm out of the box with simple declaration like:
        mingw_x86_64(Gcc) {
            path minGW64Path
            target("windows_x86_64")
        }

Is there any reason why it is not marked as supported or at least partially supported?

PR: https://github.com/gradle/gradle/pull/8123
@lacasseio Can you take a look at ☝ ?


add persistent kad store

Very much WIP...

It will be a while until something like this becomes really useful, given the constraints of the current rust libp2p kad RecordStore trait. So closing this for the time being.


pageserver: getpage requests sometimes skip reading recently written image layers

Via investigation of https://github.com/neondatabase/neon/issues/9058 -- in that issue, it was observed that layers before recently written image layers were being visited by getpage requests.
It seems like under some circumstances, a getpage request to the exact same LSN where an image layer exists can fail to hit that image layer.  Not clear if being at the exact same LSN is important or not: it might just be that we don't hit image layers for reads until the current in memory layer is closed?
Lots of uncertainty here, not claiming to have conclusively diagnosed this
Branch with experimental test:
https://github.com/neondatabase/neon/tree/jcsp/layer-map-search-at-image-lsn-2
In that branch, there are some log lines hacked in to record which layers are visited at INFO level.  In the test, there is a checkpoint line commented out:
    # Uncomment this checkpoint, and the logs will show getpage requests hitting the image layers we
    # just created.  However, without the checkpoint, getpage requests will hit one InMemoryLayer and
    # one persistent delta layer.
    # env.pageserver.http_client().timeline_checkpoint(tenant_id, timeline_id, wait_until_uploaded=True)

The presence or absence of inmemory layers shouldn't make any difference to whether reads hit an image layer, but apparently it does.

A cleaner reproducer that uses layer eviction + on-demand downloads to prove which layers are touched by a getpage request: https://github.com/neondatabase/neon/tree/jcsp/layer-map-search-at-image-lsn-3

Perhaps this piece of logic is at fault in get_vectored_reconstruct_data_timeline:
                match in_memory_layer {
                    Some(l) => {
                        let lsn_range = l.get_lsn_range().start..cont_lsn;
                        fringe.update(
                            ReadableLayer::InMemoryLayer(l),
                            unmapped_keyspace.clone(),
                            lsn_range,
                        );
                    }

...because lsn_range is being constructed from the absolute start of the layer.  Our cont_lsn jumps back to the start of the oldest inmemory layer before we start looking at historic layers at all.


Add FragmentInfo.

This PR implements TileDB's fragment info API, and adds tests to it, ported from Java.
SC-22321

CI is displaying these errors.


Tag Handling and special @skip tag

The filtering of scenarios and features by tags is a good way.
At this point i have questions / suggestions.
Feature tags and scenario tags
In the examples there is file 4_tags.feature.
This is a little bit different to the README due to the @all feature tag.
If i run with tag @all then no @apple or @bananas test is executed. This is not what i expected, but ok. (expected to run all scenarios of the feature and use tagged features to filter features if run with many files)
I wanted then to run the banana test only so i run @all and @bananas. But this does nothing, i have to execute @all or @bananas".
And if i run @bananas nothings gets run.
Is this intended in this way? For me it would be more intuitive to run @all to use the feature and then the "and" operator to run tagged scenarios in this feature? @all to enable the feature file itself and then "and" to enable the tagged scenarios.
if "or" was intended and ok then i do not understand why the only @bananas does not work.
Suggestion for special @skip
Some of the frameworks i use have a possiblity to skip scenarios by code.
So it might be helpful to have
BEFORE_T(_(), "@skip")
{
  cuke::skip("msg")
}

This could apply to features and/or scenarios
Tagged Examples
Tagging a "Scenario Outline" is reasonable, but what should be achieved by tagging "Examples" like the README says?
Could i then provide more than one example section to the Scenario Outline? Maybe a test / example / README example may be helpful.

Feature Tags: you're right I messed up the tag inheritance, I'll fix it.
Default Tags: Let me sleep on that, maybe we can provide default tags at compile time then its up to the developer to introduce them or not.
Tagged examples: As I found out (JS and python version where my references at point of implementation) it is possible to have multiple Examples per Scenario Outline and you can tag each. Why it is so? I have no idea. I tried to mimic their implementations. And yes you're right I didn't put this in the docs nor in the readme.
I'll update this issue at a time when i make some progress

Feature Tags: you're right I messed up the tag inheritance, I'll fix it.

:+1:

Default Tags: Let me sleep on that, maybe we can provide default tags at compile time then its up to the developer to introduce them or not.

Maybe you understand me wrong: to support the @skip tag is just need a cuke::skip function. I think its up to myself to implement the hook to have @skip working without providing tags. An alternative would be to run with -t "not @skip"

Tagged examples: As I found out (JS and python version where my references at point of implementation) it is possible to have multiple Examples per Scenario Outline and you can tag each. Why it is so? I have no idea. I tried to mimic their implementations. And yes you're right I didn't put this in the docs nor in the readme.

Ok, that was absolutely new to me. Cool feature

Maybe you understand me wrong: to support the @skip tag is just need a cuke::skip function. I think its up to myself to implement the hook to have @skip working without providing tags. An alternative would be to run with -t "not @skip"

I see, lets start with @skip (and maybe @ignore) i found some references online.
I'll do each on a separate branch.

Ok. Thanks for your support this week, this helped me a lot during evaluation of your project as an replacement for our current cucumber toolchain! Very good and clean project/code!

Thanks a lot, I appreciate this feedback.

Tag inheritance fixed& merged https://github.com/ThoSe1990/cwt-cucumber/pull/35
I'll do the skip function tomorrow or so and when its solved I'll close this Issue.

currently the after hooks of the specific skipped scenario do not need to be executed, i currently have no use case for it. But the AFTER_ALL hooks etc should be executed (no scenario specific hooks).

Yes, AFTER_ALL is still called


Consider updating default version to latest release

Is your feature request related to a problem? Please describe.
The default version of MCNP for MontePy is 6.2.0. At each new release supported by MontePy, consider updating the default version.
Describe the solution you'd like
As of issue submission, MCNP version 6.3.0 is the latest. In the documentation, prefer links to the 6.3.0 user manual. Update the global constant montepy.DEFAULT_VERSION to the tuple (6,3,0).
Describe alternatives you've considered

Leave as 6.2.0 forever
Point to the earliest supported version instead

Good idea. I was holding off on this for #NaN, but I think we have had enough time to see this isn't a significant issue with 6.3.0. Though 6.3.1 I believe maybe.


Title: Improve the footer and make it more responsive

Which pre-existing JavaScript project will you be working on?
Footer part
Describe your enhancement/improvement
Using HTML CSS
Anything you need to say to the Reviewers
No response
Add any other context or relevant screenshots about the enhancement here.
No response

@Sapta-Dev27 Thank you for providing your insight but it is not required as of now.


Filter project issues by assignee

Supports displaying project issues and pull requests assigned to a particular user

Looks good! You will have to accept the CLA. The link is among the status checks for this PR.

Thanks! I just accepted the CLA

After a few minor nitpicks this will be ready to merge! Thank you for the exceptionally high quality pull request.
One more open question: should there be a way to list all issues assigned to yourself, without having to type your own login name? It would be nice if we could do -a me or something, but unfortunately a user with login name "me" exists.
I plan to overhaul the hub issue command soon just as I did with release #1095, but this will make a great feature to keep.

Thanks for the feedback! I'm totally on board with the idea of short hand to find issues assigned to 'me' I just couldn't think of an intuitive way to include it off the top of my head. That's actually the way I'd most commonly use this feature.
I'll give it some more thought and fix up the suggestions from your other comments in the mean time.

I think I've addressed your concerns with the code.
As for the suggestion about referencing yourself automatically, it might be useful to try and interpret -a with no assignee login given as the current user. I'm not sure if that's the most intuitive implementation or if its even possible for the pflag library to treat a flag like both a string value and a simple boolean at the same time.
Regardless, if someone wanted that functionality, they could also create an alias like the following:
git config --global alias.myissues 'issue -a cornwe19'

Thanks for your patience!

it might be useful to try and interpret -a with no assignee login given as the current user

No that's not possible. A flag should either accept a value or not accept a value, but it can't be both. The only exception are boolean flags which usually don't take a value (e.g. -p) but can optionally take a value using equal signs e.g. -p=false.

Makes sense. I got the impression that wouldn't work out. Thanks for confirming and for merging the change through.


How to use the annotations @Issue, @TestCaseID, etc with Cucumber-JVM framework ?

I tried adding the way it is mentioned in the documentations but i was not able to see the Test Case ID and Issue ID.
Sample Code :
@Issue("CON-1062")
@When("^User logs in using Username as "(.)" and Password "(.)"$")
public void login(String username, String password) {
-- implementation code
}
@TestCaseId("CON-1055")
@Then("^User should be logged in$")
public void User_should_be_logged_in() throws Throwable {
-- implementation code
}
How can we integrate these things with Cucumber JVM Framework ?
Using the documentation and other framework (Like TestNG), I was able to see those linkable IDs in the report. Is there a way to use these annotations with Cucumber JVM Framework ?

Please move to https://github.com/allure-framework/allure-cucumber-jvm-adaptor/issues/.


mvnw permission issue in tutorial: Build and deploy your app to Azure Container Apps

Please provide us with the following information:

This issue is a: (mark with an x)

[ x ] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
Running the tutorial: Build and deploy your app to Azure Container Apps for Java with cloud build, the "Build the container with ACR" step returns an error message:
/bin/sh: line 1: ./mvnw: Permission denied
Steps to reproduce

Run the preceding steps of the tutorial.
For the "Build the container with ACR" step, run the following command: az acr build --resource-group $RESOURCE_GROUP --registry $ACR_NAME --image $API_NAME .

Expected behavior [What you expected to happen.]
As per the tutorial, it should create a container image in the ACR.
Actual behavior [What actually happened.]
Error message:
thes@SAG-6YQ9SG3:/mnt/c/Git/code-to-cloud$ az acr build --resource-group $RESOURCE_GROUP --registry $ACR_NAME --image $API_NAME .
Packing source code into tar to upload...
Excluding '.git' based on default ignore rules
Excluding '.gitignore' based on default ignore rules
Uploading archived source code from 'C:\Users\THES\AppData\Local\Temp\build_archive_6fb14102ac08470cbfaeaf6899ef2dfa.tar.gz'...
D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\cryptography/hazmat/backends/openssl/backend.py:27: UserWarning: You are using cryptography on a 32-bit Python on a 64-bit Windows Operating System. Cryptography will be significantly faster if you switch to using a 64-bit Python.
Sending context (69.652 KiB) to registry: acaalbumsthesse1...
Queued a build with ID: cb2
Waiting for an agent...
2024/03/18 08:41:02 Downloading source code...
2024/03/18 08:41:03 Finished downloading source code
2024/03/18 08:41:03 Using acb_vol_ba1e076d-783e-4d1c-8a0b-adaed4506df5 as the home volume
2024/03/18 08:41:03 Setting up Docker configuration...
2024/03/18 08:41:04 Successfully set up Docker configuration
2024/03/18 08:41:04 Logging in to registry: acaalbumsthesse1.azurecr.io
2024/03/18 08:41:04 Successfully logged into acaalbumsthesse1.azurecr.io
2024/03/18 08:41:04 Executing step ID: build. Timeout(sec): 28800, Working directory: '', Network: ''
2024/03/18 08:41:04 Scanning for dependencies...
2024/03/18 08:41:05 Successfully scanned dependencies
2024/03/18 08:41:05 Launching container with name: build
Sending build context to Docker daemon  133.6kB
Step 1/13 : FROM mcr.microsoft.com/openjdk/jdk:21-mariner AS build
21-mariner: Pulling from openjdk/jdk
0455e3c62813: Pulling fs layer
dec38aea8163: Pulling fs layer
96e42a458ed4: Pulling fs layer
dec38aea8163: Verifying Checksum
dec38aea8163: Download complete
0455e3c62813: Verifying Checksum
0455e3c62813: Download complete
96e42a458ed4: Verifying Checksum
96e42a458ed4: Download complete
0455e3c62813: Pull complete
dec38aea8163: Pull complete
96e42a458ed4: Pull complete
Digest: sha256:1c7fff8147b1229d6aaec82fbb83bb0da458ee7c5c55bafca4d0caf62b6583ce
Status: Downloaded newer image for mcr.microsoft.com/openjdk/jdk:21-mariner
 ---> dc036ee5555b
Step 2/13 : ENV JAR_FILE=containerapps-albumapi-java-0.0.1-SNAPSHOT.jar
 ---> Running in 8d9c483ce310
Removing intermediate container 8d9c483ce310
 ---> a1727f7382e4
Step 3/13 : WORKDIR /app
 ---> Running in a173cdbe30bb
Removing intermediate container a173cdbe30bb
 ---> f1aa7f68bac6
Step 4/13 : COPY mvnw* /app/
 ---> 134ece7b236d
Step 5/13 : COPY .mvn /app/.mvn
 ---> 9d26351ccb44
Step 6/13 : COPY pom.xml /app
 ---> 7377fbfc6dc1
Step 7/13 : COPY ./src /app/src
 ---> b3cf2e2a5b29
Step 8/13 : RUN ls -la /app
 ---> Running in c63b3f854723
total 40
drwxr-xr-x 1 root root  4096 Mar 18 08:41 .
drwxr-xr-x 1 root root  4096 Mar 18 08:41 ..
drwxr-xr-x 3 root root  4096 Mar 18 08:41 .mvn
-rw-rw-rw- 1 root root 11598 Mar 18 08:02 mvnw
-rwxrwxrwx 1 root root  7797 Mar 18 08:02 mvnw.cmd
-rw-rw-rw- 1 root root  1316 Mar 18 08:02 pom.xml
drwxr-xr-x 4 root root  4096 Mar 18 08:41 src
Removing intermediate container c63b3f854723
 ---> f85e64f53d0d
Step 9/13 : RUN ./mvnw dependency:go-offline -B -Dproduction package
 ---> Running in 0c68d049565a
/bin/sh: line 1: ./mvnw: Permission denied
The command '/bin/sh -c ./mvnw dependency:go-offline -B -Dproduction package' returned a non-zero code: 126
2024/03/18 08:41:20 Container failed during run: build. No retries remaining.
failed to run step ID: build: exit status 126

Run ID: cb2 failed after 19s. Error: failed during run, err: exit status 1
Run failed

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Ex. Did this issue occur in the CLI or the Portal? CLI

Also reported as https://github.com/microsoft/containerregistry/issues/160, as it seems to be an ACR issue.


Finding inscriptions with sats-connect

Hello,
I see in the X-verse wallet it can render all NFTs. I want to do the same in my app, I need to find all the inscriptions in the wallet with their collection names to do further processing. Can I do this using sats-connect?
Thanks!

This is not functionality that sats connect provides currently. I would suggest finding an API where you can get inscription per address data from.

Thanks, so X-Verse is keeping this functionality and not opening it for developer's usage, at least for now.
I thought if I could avoid multiple lookups, anyhow. Anyone interested in knowing the inscriptions in your X-verse wallet can use ordinals API by running your node or use the rest endpoint from https://docs.hiro.so/ordinals/specific-inscription.

The functionality is out of scope for Sats Connect. It's much better to directly hit the APIs for inscriptions instead of through Sats Connect.


Add "get started" basic tutorial notebook(s) to teach users how to create a StellarGraph and do basic ML workflow.

Description
Split from #910 - Our current set of demo notebooks are good to show particular algorithms, but don't teach the basics of how to create a StellarGraph from a dataset on disk, then use it for a basic ML workflow.
We can create two (or possibly one?) tutorial notebooks that show:

how to load/preprocess data to build a StellarGraph

can be based on existing notebooks, but with a focus on documenting the c ore workflow, rather than specific algorithm or results.
need to cover homogeneous and heterogeneous data sets. (possibly CORA for homog; could include our own CSV for hetero. )

2. the very basics of the machine learning workflow (something very simple like GCN node classification)
* important now that are examples are using the datasets module to return a StelalrGraph object rather than explicit code in the notebook.
User Story
As a new user to StellarGraph, I want a basic tutorial showing me how to load data and construct a StellarGraph, then construct the basic machine learning workflow so that I can understand the library and use it on my own datasets
Done Checklist

[ ] Produced code for required functionality
[ ] Tests written and coverage checked
[ ] Code review performed
[ ] Documentation on Google Docs  (if applicable)
[ ] Documentation in repo
[ ] Version number reflects new status
[ ] CHANGELOG.md updated
[ ] Team demo

I've split https://github.com/stellargraph/stellargraph/issues/1087 off to cover how we surface these (and other) notebooks, leaving this one to just create the notebooks.


[Enhancement] Spacing between chat cards

Is there any way you could add an option to put  small extra space (maybe 5px) between chat cards? They're so jammed up together, it's sometimes hard to tell what's what.
From this:

to this:

You can use custom CSS to change this exactly as you prefer, example:
.chat-message:not(:first-child) {
    margin-top: 10px;
}


add formatted output and ability to filter on pool/cluster

leverage datacenter function from base
add option for filtering datastores by cluster/pool
add formatted output

Thanks Will. Hoping to catch up on my work with this project this week.
Can you add the pool option to the readme? Thanks.

@swalberg not a problem, updated!

Thanks for the contribution!


HMR with webpack-dev-middleware, webpack-hot-middleware and Connect not working

I have working HMR for typescript files, but i can`t make it working for scss files.
My server has following setup (snippet):
var connect = require('connect');

var app = connect();

var webpack = require('webpack'),
      webpackConfig = require('./webpack.config.index.js'),
      webpackDev = require('webpack-dev-middleware'),
      hmr = require("webpack-hot-middleware");

var compiler = webpack(webpackConfig);

//enables webpack dev middleware
app.use(webpackDev(compiler,
{
    noInfo: true,
    publicPath: webpackConfig.output.publicPath
}));

app.use(hmr(compiler));

My webpack configuration (snippet) is:
entry:
{
   "style": [path.join(__dirname, "content/site.scss"), 'webpack-hot-middleware/client'],
   "app": [path.join(__dirname, "app/app.ts"), 'webpack-hot-middleware/client']
},
output:
{
    path: path.join(__dirname, 'wwwroot/dist'),
    filename: '[name].js',
    publicPath: '/dist/',
    chunkFilename: '[name].chunk.[chunkhash].js'
},
module:
{
    loaders:
    [
        {
            test: /\.ts$/,
            loaders: ['awesome-typescript-loader', 'angular2-template-loader']
        },
        {
            test: /\.html$/,
            loader: 'raw-loader'
        },
        {
            test: /\.scss$/,
            loaders: ['style-loader', 'css-loader', 'sass-loader']
        },
        {
            test: /\.(ttf|eot|svg)$/,
            loader: "file-loader"
        }
    ]
},
plugins:
[
    new webpack.HotModuleReplacementPlugin()
]

When i change something in scss file i can see following in browser console.
[HMR] bundle rebuilding
[HMR] bundle rebuilt in 5253ms
[HMR] Checking for updates on the server...
[HMR] Nothing hot updated.
[HMR] App is up to date.

When i refresh page i can see new styles applied. But HMR does not apply new styles. When i do some change in typescript file it is automaticaly refreshed.
I even tried to put import scss file into typescript file and use module.hot.accept() but it does not helped.
Is this bug, or do i have something wrong?
Thank you

Have you tried using a full URL in output.publicPath? I would also suggest asking this question on StackOverflow, you'll get better help there.

I found solution and problem.
Problem was that i included generated style.js in html head, but it should be in body. Also 'webpack-hot-middleware/client' should be at the beginning of entry.
Closing this one.


Grouping styles

Hi,
I wish the .sunlight* styles were all called pre.sunlight*
In my authoring tool I have a list of styles that appear where they are allowed. This means that all styles in the imported sunlight.default.css file appear at the top of the list.
I tried renaming the styles to pre.sunlight* - that would be really nice, because then all the styles were grouped below pre, and I could even hide them.
But if I rename the styles, the javascript does not work correctly - the color coding is gone.
I know this is just a convenience issue... but it is quite annoying having to scroll through the full list (almost full, as I've removed the styles that do not apply to my programming language) every time you need some style.
Apart from this - thanks for a great tool!
-Niels

I'm not sure I really follow what you're asking. Do you want the class names to be named something different, i.e. with a different prefix? There is an option for that (make sure to change your CSS, though): http://sunlightjs.com/docs.html#class-prefix
If you're referring to something else, can you be more specific or provide some sample CSS/HTML of what you're after?

Hi,
Sorry for the LATE reply. You got me in the right direction, thanks!


Sending messages cannot be updated

In the send example, if each time the message to be sent is updated in a loop, it is found that the update cannot be completed, and the CAN bus is always the first third message

I'm having the same issue, I'm thinking that the the MCP_CANINTF register is not being reset resulting in all the message buffers not being able to be re-assigned.

This is the output log I get when trying to send a message:
Send msg - OK <- I can see on the oscilloscope it being sent
Send msg - OK <- I can see on the oscilloscope the data has been updated
Send msg - OK
Send msg - All TX Busy <- No change in data on the oscilloscope
Send msg - All TX Busy
...

Ended up modifying the sendMessage() method to reset the TX CTRL registers if all the buffers are full. Don't know what the implications are so if someone who knows more about this could help that would be greatly appreciated.
This is my sendMessage() method now, be aware its recursive.
MCP2515::ERROR MCP2515::sendMessage(const struct can_frame *frame)
{

    if (frame->can_dlc > CAN_MAX_DLEN) {
        return ERROR_FAILTX;
    }

    TXBn txBuffers[N_TXBUFFERS] = {TXB0, TXB1, TXB2};

    for (auto & txBuffer : txBuffers) {
        const struct TXBn_REGS *txbuf = &TXB[txBuffer];
        uint8_t ctrlval = readRegister(txbuf->CTRL);
        if ( (ctrlval & TXB_TXREQ) == 0 ) {
            return sendMessage(txBuffer, frame);
        }
    }

    uint8_t zeros[14]{};
    setRegisters(MCP_TXB0CTRL, zeros, 14);
    setRegisters(MCP_TXB1CTRL, zeros, 14);
    setRegisters(MCP_TXB2CTRL, zeros, 14);

    return sendMessage(frame);
}


Update to handle optional return from SecPolicyCreateSSL in Xcode 8.0 beta 4

This gets the swift 2.3 branch compiling on latest XCode

The swift2.3 branch is up to date with beta 5.


add Memory field to DomainPresetSpec struct

related to https://github.com/kubevirt/kubevirt/pull/1115 ... left out one important field from that PR.

Thanks @tchughesiv! Does this fix https://github.com/kubevirt/kubevirt/issues/1118?

@stu-gott hmm... I'd have to investigate that one but i doubt it. I can look into that issue though since this preset / validation code is fresh in my mind right now.

Awesome!
We really need functional tests for presets and the examples.


Konga support Let’s Encrypt SSL?

Dear team,
I need support Let’s Encrypt SSL
Thanks

Have you tried proxying through Nginx? (or some other web server)
That's how I generally configure my SSL for these types of applications.


gmm: 5.1 -> 5.3

Motivation for this change
Refresh package source since Gna.org forge is closed
Things done

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

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

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

Success on aarch64-linux (full log)
Attempted: gmm
Partial log (click to expand)
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/build/gmm-5.3'
make[1]: Leaving directory '/build/gmm-5.3'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/6j6sdjd5dp7ij27g35qrck8qf31qjq4s-gmm-5.3
strip is /nix/store/428gs2z4b8f9byvghzlpbjwjb3a7jwxx-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/6j6sdjd5dp7ij27g35qrck8qf31qjq4s-gmm-5.3
checking for references to /build in /nix/store/6j6sdjd5dp7ij27g35qrck8qf31qjq4s-gmm-5.3...
/nix/store/6j6sdjd5dp7ij27g35qrck8qf31qjq4s-gmm-5.3

Success on x86_64-linux (full log)
Attempted: gmm
Partial log (click to expand)
make[2]: Nothing to be done for 'install-exec-am'.
make[2]: Nothing to be done for 'install-data-am'.
make[2]: Leaving directory '/build/gmm-5.3'
make[1]: Leaving directory '/build/gmm-5.3'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/aljw1bjxqzs315063j4dxwqz6zp61ci9-gmm-5.3
strip is /nix/store/dxf1m7dhc4qb655bdljc1fsd74v1nag3-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/aljw1bjxqzs315063j4dxwqz6zp61ci9-gmm-5.3
checking for references to /build in /nix/store/aljw1bjxqzs315063j4dxwqz6zp61ci9-gmm-5.3...
/nix/store/aljw1bjxqzs315063j4dxwqz6zp61ci9-gmm-5.3

And nox-review ended successfully with the build of gmm-5.3 and gmsh-4.0.1


: Failed to resolve async component: function () {   return webpack_require.e(/*! import() | mining-component / "mining-component").then(webpack_require.bind(webpack_require, /!

Laravel Mix Version:  6.0.6
Node Version (node -v): 14.15.5
NPM Version (npm -v): 6.14.11
OS: Linux

Description:
I don't see my components. Console showing following message =>

But I got files

Code:
Vue.component(
    'mining-component',
    () => import(/* webpackChunkName: "mining-component" */ './components/organisms/Mining.vue')
);

I got this error, than I build on Production mode

I cleaned the public folder 2 times and reassembled the solutions a couple of times and it helped


Creating Make File, updated file system, and updated yml file

@voremargot the changes look good to me.


Cut a release of notification services

An official release of notification services should be cut before moving to the demo environment.

@emetsger we will most likely deploy ns to demo tomorrow 11/14/2018. we should cut NS release today then?

@htpvu sounds good!  Should be doable!

closed by https://github.com/OA-PASS/pass-docker/pull/167


update wechat id

update wechat id

Codecov Report

Merging #2046 into dev will decrease coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev    #2046      +/-   ##
============================================
- Coverage     33.17%   33.14%   -0.04%
+ Complexity     1553     1552       -1
============================================
  Files           313      313
  Lines         15528    15528
  Branches       1886     1886
============================================
- Hits           5152     5146       -6
- Misses         9848     9856       +8
+ Partials        528      526       -2

Impacted Files
Coverage Δ
Complexity Δ

...scheduler/alert/template/AlertTemplateFactory.java
42.85% <0%> (-14.29%)
2% <0%> (ø)

...he/dolphinscheduler/common/thread/ThreadUtils.java
71.18% <0%> (-6.78%)
12% <0%> (-1%)

...pache/dolphinscheduler/common/utils/FileUtils.java
17.58% <0%> (-1.1%)
7% <0%> (ø)

...cheduler/api/service/ProcessDefinitionService.java
74.6% <0%> (-0.35%)
83% <0%> (-1%)

...inscheduler/common/task/sqoop/SqoopParameters.java
80% <0%> (ø)
15% <0%> (ø)
:arrow_down:

...he/dolphinscheduler/api/service/LoggerService.java
100% <0%> (+8.69%)
8% <0%> (+1%)
: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 0df7c67...36893e5. Read the comment docs.


Update dependencies and make ranges more inclusive

@andreasrs I think we can test out using ^ in this extension, trusting the ecosystem and it will remove some maintenance where we would need to update the dependencies more frequently.
@voldern I have updated @rocjs/roc-internal-dev to be compatible with npm 5, could you rebase your branch removing the last commit and we are ready to merge.

Seems like there is something weird going on with npm@5, I will just go ahead and merge this and we can look into it more later.

Seems like there is still issues with NPM5 and some dependencies not being installed when running rid link, which is very strange. I've agreed with @dlmr that we'll just release this one with only NPM4 support for now, to get it out the door, since its a CI problem. And then fix the link issue later.