[Request] Multi block Hydro electric plant

Running on survival it takes alot of thinking on how to use resources and while fusion is great its not to easy to get the laser power to have it dump out power. Though i enjoy the fusion plant considering real life fusion is no capable of powering crap but i was hoping to get more generator if not this very massive hoover dam style hydro electric plant. Or fission power. Gas burners were my goto but the power they generate was dropped to 200 j/t and that just barely powers the seperator it hooks to.

Hydrogen was turned into an energy carrier in Mekanism 8. The preferred fuel source for the Gas-Burning generators is now Ethylene follow the link for the wiki page explaining how to make it and about its energy density.

No not hydrogen. Hydro electric. Like the hoover dam, pushes huge amounts of water through its turbines and that creates huge loads of power.

@Saizetsu, I'm interested in it to, but you need to give more details on how it would work so that the developer can get a better figure of your idea. Example: how to build, what is made of, size, shape etc.

Its really simple though, its falling water that would spin a turbine and output power based on how much water pressure there was to spin the turbine. An electric pump or several say seven would ram enough water into it to outdo a fusion generator. Real world hydro outputs more than civilian fission plants. But civvys only use 2% of the fission proc they cant do more without military secrets.
The multi block would just be a turbine size can be increased with something like the dynamic tank block it would need a helluva lot of water but the more the better

Hm rife with grammatical and spelling errors, the hydro electric plant would require multiple turbines, a water pump and a pressure pump. Higher amounts of pressure and water pushing through a turbine, this would cause the turbine to spin and the rotations would cause electrical discharges which would require something to take that and convert it into proper electricity, the more pressure, and water pushed through would generate more power but it would require a larger size. More turbines and so forth. A very large multiblock structure or just several machines.

This is worth giving a bump.  Hydroelectric is IRL a great source of power but as noted each unit would be fairly small output - the water equivalent of the existing heat generator.  RL hydro plants use a reservoir behind the dam, so what they're really doing is using water and turbines to convert gravity's pull to energy.  As long as the river upstream doesn't dry up you've got mind-boggling amounts of energy sitting in the reservoir.
Possibly implement like the existing wind generator, but single-block-sized and requiring both a water block above and empty (or flowing water) block below to function?  You could stack these like a vertical checkerboard for a large-scale plant or have a few hiding in a creek for a non-eyesore energy source.
Set up a few dozen of these and you should be able to power a typical base.    A few RL hydroelectric dams power most of Washington state and they export power to other states too.

Problem is, you can't have dried up rivers in minecraft.. since water doesn't flow like that.
Maybe something like RotaryCraft's hydro turbine thingy.

I have seen an electric pump drain a lake before. But a storage device could be used in place of having to use water, just set it up like the solar evap plant. Surround a tower multi block that works like a generator with dynamic glass pump an ocean with pumps into the tank and it spins up and makes electricity.

Using electric pump to pump water into a hydro generator? Thats not really a good idea =/
//IRL
For starters, it would violate the law of conservation of energy. Energy is being converted to kinetic energy then converted to potential energy, which is then converted back to kinetic energy then to electrical energy, which would cause quite a bit of energy loss I imagine.

Well if we want real life then the fusion generator shouldnt produce enough power beyond being able to sustain itself. And most humans can not punch a tree down either.
But i digress, a pump was part of an example. I use acqueous accumulator for most if not all water using machines. I assume most people would have a power network before using a hydro plant.

Well IRL its possible for nuclear fusion to generate enough power to sustain itself, we just haven't managed it yet. The sun does use fusion reactions after all.

We have managed it. We have a single fusion plant in the states. It powers itself and nothing else, actually i wonder if mekanism would add in cold fusion. Its only workable in theory but hey. Mc has people punch trees down.
The more pressure behind the water the faster the turbine will spin, generates more power so a cyclical system would work to start add in more water or more pressure or both and it would give more power, or set up several turbines. Hence a multi block, it would require thousands of gallons of water.

For Minecraft/Mekanism purposes we could have the hydroelectric turbine block require that water is above it (mostly for aesthetics) but not actually consume the water.
If it were to require a continuous supply passing through it, the user would simply put a pump below and a plenisher above anyway, making it all moot.

Actually, it could be setup to use more water than a standard plenish/pump can give. It needs massive amounts of water to give out power after all. Although having water fall down to it from a high height could help too. Like 255 near build cap. Water fall height would make such an aesthetic useful as well.

Well I hope this is taken into consideration.

Just to show off, a guy built a hydroelectric dam: https://redd.it/3kic2t

Although I don't think Mekanism needs to be like that.

I'd rather leave this kind of mechanical power generation to mods like Immersive Engineering for now.  This doesn't mean I'm taking it off the table, but for my current release schedule I'd rather streamline the amount of content I'm adding.


Improve scrolling experience on mobile

https://github.com/jwplayer/ott-web-app/assets/42120041/a29b623b-e7f8-4f2b-b00b-0b9ff8b1b1fc

With #437 merged, the slider should animate while sliding. However, it doesn't scroll when dragging the slider. I did make a POC a while ago, but never got to finish it.
https://github.com/Videodock/tile-slider/pull/15


Move items in inventories

A way to move items between different inventory slots. Both in the server sent inventory and the players belt.
If:

Server sent inventory is open

Then:

Release mouse
Track mouse clicks

If:

Mouse clicked on a slot

Then:

Select slot, if second selection send move package.

R,1,4,1,6 (R, from inventory, index, to inventory, index)
inventory 1 = chest/bag ....
inventory 0 = belt

Implemented in 8fa1523 for the external inventory.


Cannot capture not invokable method error

var o = {};
assert(o.m());

TypeError: assert._capt(...).m is not a function

var o = {};
assert(assert._expr(assert._capt(assert._capt(o, 'arguments/0/callee/object').m(), 'arguments/0'), {
    content: 'assert(o.m())',
    ...
}));

Thank you for reporting!
It's hard to fix...
I tried enclosing capture logic in function calls.
It seem to be a solution for me, but it does not work since it changes contextual semantics and dynamics around asynchronous nature, such as async/await.
I learned that I should not enclose original calls in extra function.
So, it's a wontfix issue for now and I should note this in FAQ section. Thanks!

Alright, please close this issue when you noted this in FAQ. If possible, please hide internal codes. I didn't understand what that meant. Thanks.

Alright, please close this issue when you noted this in FAQ

Yes I'm going to. Thank you!

If possible, please hide internal codes. I didn't understand what that meant.

I absolutely agree with you..


Academic Use allowed?

Hi Team, Can you confirm if it is legal to use this Goodreads dataset for academic research. I wanted to use it for my research?

Sorry for the late reply. Yes we collected the data for academic research only.


Compatibility with pytest-django 3.7.x

Currently, pytest-tipsi-django requires pytest-django==3.6.*, but we are using 3.7.0. Do you have the time to update this package to support pytest-django 3.7.0 soon?
I was going to try to do that myself, but I have not yet been able to get the test environment set up quite right.

@stevecj oh, will update it to less strict requirement

Uploaded as 2.4.0


feat(compaction): support compact partial files of overlapping level

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
If the data during one barrier is too large, we may flush a big sub-level. And when we try to compact this big sub-level, we found that compactor-node OOM.
We need to limit the size of compact task even if it is a task for overlapping level, so we can not select the whole sub level
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR contains user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

We will compact a large overlapping-level multiple outside sort.


added keyhud plugin

added new plugin: keyhud

Looks awesome!
Only suggestion is that for configurable things, you should use config.plugins.keyhud with common.merge like how most plugins do it.


Async/await support

Do you think it would be useful to support async functions and await in System implementations?

Hello @sunjay, as mentioned by @omni-viral, Specs is quite synchronous and async functionality is not a very good fit here. What would you want to use it for?

The reason I brought it up is because, as I was working with specs, I started to wonder what would happen if I needed to load something asynchronously as part of the results of a system. The more I thought about it though, the more I realized that it doesn't really make sense to do that in the context of an ECS. Any async code should run separately as @omni-viral said.
I just wanted to bring this up to see what your thoughts were. I think it's worth talking about given that the language will have first class async support pretty soon.
Thanks! This issue can probably be closed unless someone else has anything more to say. :smile:


[Feature Request] Log Compaction in Delta

Feature request
Which Delta project/connector is this regarding?

[ ] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[x] Other: Delta Protocol

Overview
This issues talks about problems related to checkpoint and how could they be handled using Log Compactions.
Motivation
Frequent Checkpointing is a major issue especially for large size tables. Today we checkpoint every 10th commit. Frequent checkpointing causes following issues:

Latency - Checkpoints involve full state reconstruction which is a slow operation. It could take more than 3-4 minutes for large delta tables even on large spark clusters.
Write Amplification - As we duplicate the majority of actions again. Amplification is O(N) where N is the number of files in the table – so total size of all checkpoints is O(N**2). Checkpoints generally have a lifespan of 30 days by default.

Why are frequent Checkpoints needed:
We try to reduce the total number of delta files below a certain threshold to make sure performance doesn’t go down.
More deltas => more files to read for State reconstruction => more tail latencies
Requirements

Increase the Checkpoint Interval to 20 without affecting the performance of Read/Write operations
Avoid any Protocol/TableFeature upgrades

Further details
Proposal sketch
Today DeltaLog has following files:
Commit File
00000000000000000005.json -> Represents a Delta file for a given version.
Checkpoint File
00000000000000000010.checkpoint.parquet -> Represents a Checkpoint file which captures everything from commit 0.
We could introduce a new "Log Compaction" file.
Log Compaction
A Log Compaction represents compaction of deltas between version ‘X’ and version ‘Y’ (both bounds inclusive). It can have following structure:
x.y.compact.json -> Represents all the changes from commit ‘X’ through commit ‘Y’. e.g.<PHONE_NUMBER>0000000100.00000000000000000200.compact.json
Instead of doing a full checkpoint every 10 commits, We could do a mix of minor compactions or full checkpointing. We could use different heuristics/policies to decide when to do minor compaction as against full checkpoint.
We could use a post-commit hook to trigger creating the minor compactions.
When to trigger MinorCompaction, Checkpointing
Old Rule

Trigger a checkpoint every ‘x’ commits

New Rule

Trigger a checkpoint every ‘y’ commits
Trigger a minor-compaction every ‘x’ commits if all individual ‘x’ commits are small
Trigger a checkpoint if a large commit lands

Metadata Cleanup
We could apply LOG_RETENTION (defaults to 30 days) even to compacted delta files. i.e. when we delete all old checkpoints before a given version ‘X’, we also delete all compacted deltas that have startVersion <= X.
Compatibility with older Delta versions
Older Delta versions won’t have capability to read/write compacted delta files. They will ignore such files and create a Snapshot backed by the last available checkpoint and delta files.
Willingness to contribute
The Delta Lake Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature?

[x] Yes. I can contribute this feature independently.
[ ] Yes. I would be willing to contribute this feature with guidance from the Delta Lake community.
[ ] No. I cannot contribute this feature at this time.

 Or only after 'x'?

Creating a checkpoint whenever a large commit lands is useful in many ways:

If the implementation can do predicate pushdown and reduce the anount of deltalog to read in a READ query
Reading a parquet file might be more efficient than reading a big commit json file due to 8-10X compression in parquet.

@prakharjain09 currently Delta only supports reading Log Compaction? Any plans for writing?


会错误的显示elementui的 el-link组件

Describe the bug
会错误的显示elementui的 el-link组件
Reproduction
none
System Info
win10

版本: 1.75.1 (system setup)
提交: 441438abd1ac652551dbe4d408dfcec8a499b8bf
日期: 2023-02-08T21:32:34.589Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
沙盒化: No

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

刚发现就看到这条反馈

You can set "iconify.includes": ["el"] in your config.


Starting CLI chroot issues

I am using a trusty chroot in the browser extension and things are working as expected (thanks for the great work !) on a Toshiba Chromebook2 (Firmware Google_Swanky.5216.238.5).
However for most tasks a simple CLI instance would be more efficient and I just added another chroot with cli-extra (tried both trusty and precise). But I seem to be unable to start them.
Entering /mnt/stateful_partition/crouton/chroots/precise...
Couldn't get a file descriptor referring to the console
Unmounting /mnt/stateful_partition/crouton/chroots/precise...
Not sure if this is an interaction with the crouton chrome browser extension. Any pointers appreciated.

This is likely due to freon; startcli won't work.  But you can enter the chroot without a graphical session by just running sudo enter-chroot.


Errors on Upgrade

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

Do you want to request a feature or report a bug?
Report a bug

What is the current behavior?
When upgrading vuestic-ui things are broken with errors like the following:

TypeError: Cannot read property 'gradient' of undefined
TypeError: Cannot read property 'shadow' of undefined

If the current behavior is a bug, please provide the steps to reproduce, ideally also a screenshot or gif if it's a style issue
Upgrade vuestic-ui from 0.1.8 to 0.2.2

What is the expected behavior?
We can upgrade without issues

What is the motivation / use case for changing the behavior?
Getting the latests changes on the template

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)
I would like to know if there is any better way to upgrade, as I might be missing the changes on the admin template itself, since the suggestion installation method is doing a git clone and working on the repository I am not sure how it should be updated so I tried to update vuestic-ui instead.

Hi. Sorry for late answer.
Updating is a weak point of vuestic and something we're to improve in later versions (it was designed as full app, not modular at all).
So some areas of code might be too tightly bound together, which also makes update guidline complicated to do.
But I can guesstimate what went wrong if you can provide a more detailed stack trace and more error examples hopefully.
Alternative would be to check current master of vuestic-admin with your version and tweak inconsistencies. vuestic-admin latest version is guaranteed to work with vuestic-ui 0.2.2.


Is cpputest orphaned?

Not much seems to have happened in the last 12 months is this project now unsupported?

no


c3c: init at unstable-2021-07-30

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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 nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 131708 at f5ea63d0 run on aarch64-linux 1

1 package failed to build:

c3c

1 package built successfully:

c2c

Note that build failures may predate this PR, and could be nondeterministic or hardware dependent.
Please exercise your independent judgement. Does something look off? Please file an issue or reach out on IRC.

oops, I thought I could rename the branch…

I have some issues with c2c and c2libs, so I will open a separate pr for it.
Now this should be ready for merge.


feat: @unocss/cli

Draft of the CLI. ☀
Notes/questions:

I'm having trouble executing the CLI inside the monorepo setup. No tsup build error thrown, but executing won't work... Works fine standalone over at unocss-cli. Am I importing the UnoCSS deps correctly?
Consequently, tests are failing at the moment.
Is the cli name unocss ok with you? Would you prefer unocss-cli or rather something else?

Some help to migrate is much appreciated. Thanks in advance! 🙂

Thank you very much! Should have found those minor issues myself. 🙈

Tests are actually working locally. As the CLI depends on @unocss/core/dist/index, deps have to be built first. Afterwards, the CLI works and tests pass.

it seems you also need to build config package...

just configure pnpm run build && pnpm -C cli run build, it will build all packages and then the cli

just configure pnpm run build && pnpm -C cli run build, it will build all packages and then the cli

OK. That didn't work locally. I may have to pass the complete package name.

it is working, just run test:update script

maybe you will need to merge main

@userquin Yes, that was the case. Also, thanks for the hint to use pnpm -C cli run build – I just had to replace cli with packages/cli and it worked.
I will update the build command right away.

finally 🥳

Sorry it took that many attempts. 🙈

Sorry it took that many attempts. 🙈

you should remove package/cli from the build script: -C will do it

@userquin Locally the following error is thrown if just using cli, rather than packages/cli:
 ERR_PNPM_NO_IMPORTER_MANIFEST_FOUND  No package.json (or package.yaml, or package.json5) was found in "/Users/johann/Git/unocss/cli".
 ELIFECYCLE  Command failed with exit code 1.

@userquin Locally the following error is thrown if just using cli, rather than packages/cli:
 ERR_PNPM_NO_IMPORTER_MANIFEST_FOUND  No package.json (or package.yaml, or package.json5) was found in "/Users/johann/Git/unocss/cli".
 ELIFECYCLE  Command failed with exit code 1.

But the package.json is there: see your path /Users/johann/Git/unocss/cli  should be /Users/johann/Git/unocss/packages/cli you have something wrong in your codebase.

Maybe you need to add the cli to root tsconfig.json file: can you test it?

I'm running from root. The docs state for using -C:

Run as if pnpm was started in <path> instead of the current working directory.

Thus, package/cli has to be the path. Am I right? 🤔
Adding the path to the tsconfig.json is only plausible if the package is imported somewhere else. Just like nuxt for example it doesn't need to be added imho.

I'm running from root. The docs state for using -C:

Run as if pnpm was started in <path> instead of the current working directory.

Thus, package/cli has to be the path. Am I right? 🤔
Adding the path to the tsconfig.json is only plausible if the package is imported somewhere else. Just like nuxt for example it doesn't need to be added imho.

ok, it should be npm -C..., but running it with pnpm it is ok (sorry man)

@antfu I messed up the PR while rebasing on main. Sorry about that. 😑


Node template fails to install dependencies in private npm registries

I saw a solution for this proposed in openfaas/faas-cli, I would suggest looking over there.


[ISSUE #3048]Dev simple code for schedule msg and send-one-way producer

Make sure set the target branch to develop
What is the purpose of the change
XXXXX
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage increased (+0.05%) to 54.131% when pulling 349f838c85053b7fd35d4ad64c553ca0045c1743 on zplovekq:dev_simple_code into 160c5772fbdf02e55cdc67bc3b74bb9f9c4c644b on apache:develop.

@zplovekq waiting for your fix to make the CI. passed

@zplovekq waiting for your fix to make the CI. passed

thanks! i am fixing it !

@zplovekq waiting for your fix to make the CI. passed

I find the CI is not passed because of the maven_code_style_plugin. I have fixed these problems by idea checkstyle plugin with style/rmq_checkstyle.xml. Thanks!

Codecov Report

Merging #3053 (c4cde2e) into develop (df1d93f) will decrease coverage by 0.10%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #3053      +/-   ##
=============================================
- Coverage      47.97%   47.87%   -0.11%
+ Complexity      4570     4551      -19
=============================================
  Files            552      552
  Lines          36628    36521     -107
  Branches        4844     4818      -26
=============================================
- Hits           17573    17485      -88
+ Misses         16832    16818      -14
+ Partials        2223     2218       -5

Impacted Files
Coverage Δ

.../broker/subscription/SubscriptionGroupManager.java
54.11% <0.00%> (-16.48%)
:arrow_down:

...rg/apache/rocketmq/common/stats/StatsSnapshot.java
84.61% <0.00%> (-15.39%)
:arrow_down:

...ache/rocketmq/common/stats/MomentStatsItemSet.java
39.13% <0.00%> (-13.05%)
:arrow_down:

...org/apache/rocketmq/store/ha/WaitNotifyObject.java
66.07% <0.00%> (-12.78%)
:arrow_down:

...rocketmq/broker/pagecache/ManyMessageTransfer.java
36.36% <0.00%> (-9.80%)
:arrow_down:

.../apache/rocketmq/common/stats/MomentStatsItem.java
38.09% <0.00%> (-9.53%)
:arrow_down:

.../rocketmq/broker/pagecache/OneMessageTransfer.java
24.00% <0.00%> (-9.34%)
:arrow_down:

...a/org/apache/rocketmq/logging/inner/SysLogger.java
28.57% <0.00%> (-5.72%)
:arrow_down:

...va/org/apache/rocketmq/common/stats/StatsItem.java
50.00% <0.00%> (-5.00%)
:arrow_down:

...org/apache/rocketmq/common/stats/StatsItemSet.java
41.79% <0.00%> (-4.48%)
:arrow_down:

... and 47 more

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 df1d93f...c4cde2e. Read the comment docs.


Use of library on jetson nano

Hello, I successfully established communication between two RP-s as described in the readme. Can library also be used for jetson nano, because the command sudo apt-get install python-pigpio python3-pigpio throws me and error: E: Unable to locate package python3-pigpio? Download using pip installs pigpio library, but the deamon still won't start.

Hi
The raspberry pi uses an ARM processor like The jetson nano, so I would guess that it is possible.
However, since the raspberry and jetson CPUs are different models, a jetson specific build may be needed.
A pigpio distribution is obviously not in the package manager for the jetson as you have already observed.
This means that you will have to build the jetson version from source.
Source of pigpiod
https://github.com/joan2937/pigpio
The pynrf24 does not need any platform specific build as it is just python.
Good luck with building on the jetson.
//bjarne

Thank you for your quick answer! I will try what you have suggested and will see if it works 👨

@bjarne-hansen I tried to build pigpio from source, but unfortunately without any luck. Is it possible to quickly modify this library in a way that it wouldn't be dependent on pigpio deamon?

Easy is a relative term ;-) but I believe the GPIO are available through RPi.GPIO.
import RPi.GPIO
That said, I believe this is quite low-level access to the pins, so a better approach would be to use spidev.
import spidev
See https://learn.sparkfun.com/tutorials/python-programming-tutorial-getting-started-with-the-raspberry-pi/experiment-3-spi-and-analog-input
Using spidev for SPI communication can establish an alternative to the pigpiod daemon.
Feel free to clone the project and give it a go.
Please let me know if you are successful (or if you have additional questions).
//bjarne

Also, please see https://www.sparkfun.com/datasheets/Components/SMD/nRF24L01Pluss_Preliminary_Product_Specification_v1_0.pdf
In chapter 8 is the command reference, and it should be relatively easy to identify where and how the commands are used in the existing code.

Thank you for all the references. I will look into it.


When using containerd as a container runtime, the systemd cgroup is enabled in the containerd configuration in the cluster image rootfs (SystemdCgroup = true), the cgroupDriver line in the kubelet configuration file will have an additional error configuration (SystemdCgroup = true)

What happen?
When using containerd as a container runtime, the systemd cgroup (SystemdCgroup = true) is enabled in the containerd configuration in the rootfs of the cluster image, and the cgroupDriver line in the kubelet configuration file will be misconfigured (SystemdCgroup = true), resulting in cluster initialization failure。
Relevant log output?
No response
What you expected to happen?
There should not be extra configuration for this (SystemdCgroup = true) error
How to reproduce it (as minimally and precisely as possible)?
No response
Anything else we need to know?

Debian 10
What is the Kernel version?
4.19.0-21-amd64
Other environment you want to tell us?

Cloud provider or hardware configuration:
Install tools:
Others:

@czhfe, could u pls show your contianerd config toml file under /etc/containerd? grep "SystemdCgroup = true" /etc/containerd/config.toml

@czhfe ,  which cloud image you used?

@czhfe , which cloud image you used?

Using my own cloud image that I built

@kakaZhou719 You can enable systemd as a group in containerd (SystemdCgroup = true) to reproduce the problem

@czhfe, I ran successfully using(SystemdCgroup = true) . Please show us your  full config.toml and your /var/lib/sealer/data/overlay2/{$layerid}/etc/kubeadm.yml under the cloudimage rootfs, {$layerid} could be got from sealer inspect .
below is my config.toml: [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]             SystemdCgroup = true

@czhfe, I ran successfully using(SystemdCgroup = true) . Please show us your full config.toml and your /var/lib/sealer/data/overlay2/{$layerid}/etc/kubeadm.yml under the cloudimage rootfs, {$layerid} could be got from sealer inspect .
below is my config.toml: [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options] SystemdCgroup = true

/etc/containerd/dump-containerd.toml

version = 2
[plugins]
  [plugins."io.containerd.grpc.v1.cri"]
    sandbox_image = "sea.hub:5000/huis/pause:3.2"
    [plugins."io.containerd.grpc.v1.cri".containerd]
      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]
        [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
          [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
            SystemdCgroup = true
    [plugins."io.containerd.grpc.v1.cri".registry]
      config_path = "/etc/docker/certs.d/"

Final Configuration

containerd --config /etc/containerd/dump-containerd.toml config dump > /etc/containerd/config.toml

@czhfe ,  and pls show your kubeadm.yml  file under : /var/lib/sealer/data/overlay2/{$layerid}/etc/kubeadm.yml

@czhfe , and pls show your kubeadm.yml file under : /var/lib/sealer/data/overlay2/{$layerid}/etc/kubeadm.yml

apiVersion: kubeadm.k8s.io/v1beta2
kind: InitConfiguration
localAPIEndpoint:
  bindPort: 6443
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
  taints: null
---
apiVersion: kubeadm.k8s.io/v1beta2
kind: ClusterConfiguration
kubernetesVersion: v1.19.16
imageRepository: sea.hub:5000/huis
apiServer:
  extraArgs:
    audit-log-format: json
    audit-log-maxage: "7"
    audit-log-maxbackup: "10"
    audit-log-maxsize: "100"
    audit-log-path: /var/log/kubernetes/audit.log
    audit-policy-file: /etc/kubernetes/audit-policy.yml
    enable-aggregator-routing: "true"
    feature-gates: TTLAfterFinished=true,EphemeralContainers=true
  extraVolumes:
    - hostPath: /etc/kubernetes
      mountPath: /etc/kubernetes
      name: audit
      pathType: DirectoryOrCreate
    - hostPath: /var/log/kubernetes
      mountPath: /var/log/kubernetes
      name: audit-log
      pathType: DirectoryOrCreate
    - hostPath: /etc/localtime
      mountPath: /etc/localtime
      name: localtime
      pathType: File
      readOnly: true
controllerManager:
  extraArgs:
    experimental-cluster-signing-duration: 876000h
    feature-gates: TTLAfterFinished=true,EphemeralContainers=true
  extraVolumes:
    - hostPath: /etc/localtime
      mountPath: /etc/localtime
      name: localtime
      pathType: File
      readOnly: true
dns:
  type: ""
  #imageRepository: sea.hub:5000/coredns
etcd:
  local:
    dataDir: ""
    extraArgs:
      listen-metrics-urls: http://<IP_ADDRESS>:2381
networking:
  podSubnet: <IP_ADDRESS>/12
  serviceSubnet: <IP_ADDRESS>/16
scheduler:
  extraArgs:
    feature-gates: TTLAfterFinished=true,EphemeralContainers=true
  extraVolumes:
    - hostPath: /etc/localtime
      mountPath: /etc/localtime
      name: localtime
      pathType: File
      readOnly: true
---
apiVersion: kubeadm.k8s.io/v1beta2
kind: JoinConfiguration
caCertPath: /etc/kubernetes/pki/ca.crt
discovery:
  timeout: 5m0s
nodeRegistration:
  criSocket: /run/containerd/containerd.sock
controlPlane:
  localAPIEndpoint:
    bindPort: 6443
---
apiVersion: kubelet.config.k8s.io/v1beta1
kind: KubeletConfiguration
authentication:
  anonymous:
    enabled: false
  webhook:
    cacheTTL: 2m0s
    enabled: true
  x509:
    clientCAFile: /etc/kubernetes/pki/ca.crt
authorization:
  mode: Webhook
  webhook:
    cacheAuthorizedTTL: 5m0s
    cacheUnauthorizedTTL: 30s
cgroupDriver: systemd
cgroupsPerQOS: true
clusterDomain: cluster.local
configMapAndSecretChangeDetectionStrategy: Watch
containerLogMaxFiles: 5
containerLogMaxSize: 10Mi
contentType: application/vnd.kubernetes.protobuf
cpuCFSQuota: true
cpuCFSQuotaPeriod: 100ms
cpuManagerPolicy: none
cpuManagerReconcilePeriod: 10s
enableControllerAttachDetach: true
enableDebuggingHandlers: true
enforceNodeAllocatable:
  - pods
eventBurst: 10
eventRecordQPS: 5
evictionHard:
  imagefs.available: 15%
  memory.available: 100Mi
  nodefs.available: 10%
  nodefs.inodesFree: 5%
evictionPressureTransitionPeriod: 5m0s
failSwapOn: true
fileCheckFrequency: 20s
hairpinMode: promiscuous-bridge
healthzBindAddress: <IP_ADDRESS>
healthzPort: 10248
httpCheckFrequency: 20s
imageGCHighThresholdPercent: 85
imageGCLowThresholdPercent: 80
imageMinimumGCAge: 2m0s
iptablesDropBit: 15
iptablesMasqueradeBit: 14
kubeAPIBurst: 10
kubeAPIQPS: 5
logging: {}
makeIPTablesUtilChains: true
maxOpenFiles: 1000000
maxPods: 110
nodeLeaseDurationSeconds: 40
nodeStatusReportFrequency: 10s
nodeStatusUpdateFrequency: 10s
oomScoreAdj: -999
podPidsLimit: -1
port: 10250
registryBurst: 10
registryPullQPS: 5
rotateCertificates: true
runtimeRequestTimeout: 2m0s
serializeImagePulls: true
shutdownGracePeriod: 0s
shutdownGracePeriodCriticalPods: 0s
staticPodPath: /etc/kubernetes/manifests
streamingConnectionIdleTimeout: 4h0m0s
syncFrequency: 1m0s
volumeStatsAggPeriod: 1m0s
---
apiVersion: kubeproxy.config.k8s.io/v1alpha1
bindAddress: ""
bindAddressHardFail: false
clientConnection:
  acceptContentTypes: ""
  burst: 0
  contentType: ""
  kubeconfig: ""
  qps: 0
clusterCIDR: ""
configSyncPeriod: 0s
conntrack:
  maxPerCore: null
  min: null
  tcpCloseWaitTimeout: null
  tcpEstablishedTimeout: null
detectLocalMode: ""
enableProfiling: false
healthzBindAddress: ""
hostnameOverride: ""
iptables:
  masqueradeAll: false
  masqueradeBit: null
  minSyncPeriod: 0s
  syncPeriod: 0s
ipvs:
  excludeCIDRs:
    - <IP_ADDRESS>/32
  minSyncPeriod: 0s
  scheduler: ""
  strictARP: false
  syncPeriod: 0s
  tcpFinTimeout: 0s
  tcpTimeout: 0s
  udpTimeout: 0s
kind: KubeProxyConfiguration
metricsBindAddress: ""
mode: ipvs
nodePortAddresses: null
oomScoreAdj: null
portRange: ""
showHiddenMetricsForVersion: ""
udpIdleTimeout: 0s
winkernel:
  enableDSR: false
  networkName: ""
  sourceVip: ""


sst shell not picking up .env values from within a package in a monorepo

I have a setup similar to the aws-monorepo example, with a scripts package with some scripts meant to be run via sst shell and .env* files placed in the monorepo root to be picked up by sst.config.ts.
Not sure when this behavior changed, but on 0.1.56 sst shell won't pick up values from .env[.stage] when run from within the package folder. In my case, it fails at start because it doesn't get a valid AWS_PROFILE value, which is set on .env.{stage}. It now only works when run from the monorepo root.
This also breaks drizzle usage, since sst shell drizzle-kit isn't working anymore from the packages that need it.

Went back a few versions and realized that this behavior/bug exists for quite some time already, but It only affected my project recently since I've started using .env.{stage} instead of .env files (because the latter takes precedence and make it hard to work with multiple stages; also, this).

This has been fixed in https://github.com/sst/ion/commit/ca6aad1ef0c1094a1be68b512a11db05fa332e69 (released in v0.1.72) :tada:


OSPRay 2.x ospSetParam(), ospSetXxx() don't emit error mesg or callback for mismatched parameter type

This is similar to issue #427 except that as far as I have been able to determine, the documentation doesn't actually specify what should occur if one calls ospSetParam() or ospSetXxx() with the correct object parameter ID string, but with an incorrect data type.  No error messages or error callbacks seem to get triggered in this case either, at least in my testing.

	device = ospGetCurrentDevice();

	ospDeviceSetStatusFunc(device, HandleOSPRayStatusMsg);
	ospDeviceSetErrorFunc(device, HandleOSPRayError);

	ospDeviceCommit(device);

....
// CALLBACKS
void HandleOSPRayStatusMsg(const char *messageText)
{
cout << "HDOSPRAY STMSG : " << messageText << endl;
};
void HandleOSPRayError(OSPError e, const char *errorDetails)
{
cout << "HDOSPRAY ERROR : " << e << " :: " << errorDetails << endl;
TF_CODING_ERROR("HDOSPRAY ERROR : %s", errorDetails);

};
works for me as expected, sometime even more annoying, than it should be
Win10x64/2.2.1

I think you misunderstood my issue.  I have no difficulty with setting the error callback, or getting error output from other scenarios, but the specific cases I have listed (mismatched parameter type) doesn't appear to cause an error message to be generated.  There's nothing wrong with the error callback mechanism itself...

You can try testing with different values for --osp:log-level (or the equivalent API parameter). Setting it to warning (or lower) should show the warnings (but not errors).

I get error when set OSP_VEC4I instead of OSP_VEC4UI,
error rises after commiting wrong setup object, not right after setting wrong typed parameter

I've gotten the mismatched parameter type in some specific cases but not others, so perhaps the issue is that not all of the parameter types are being checked equally well by the different types of objects?  I tested various bogus cases on the OSPRenderer object without generating errors at commit time.  I will turn on the status message callbacks to make sure I'm not missing these, but I still would have expected errors to show up on the error callback for the cases I encountered.

So, more interesting stuff.  If I set OSPRAY_LOG_LEVEL to "debug" before launching the app, I can get output on the status callback.  However, if I use the following code to set the log level after registering the error and status callbacks, I get no status output?  Anything obviously wrong with setting the logLevel value below per the docs?:
if (verbose == RT_VERB_DEBUG) printf("OSPRay2Renderer) setting error / status callbacks...\n");
OSPDevice dev = ospGetCurrentDevice();
ospDeviceSetErrorFunc(dev, vmd_ospray2_error_callback);
ospDeviceSetStatusFunc(dev, vmd_ospray2_status_callback);
ospDeviceSetParam(dev, "logLevel", OSP_STRING, "debug");
ospDeviceCommit(dev);
I still feel that bogus or mismatched parameters and types should be treated as errors and therefore trigger the error output callback, and not as "status" information, but I see that's a choice that the OSPRay devs have made.  If it is going to remain this way, I would strongly recommend documenting this such that it can't be missed, by pointing out this behavior as part of the discussion of ospSetParam(), etc.

So, more interesting stuff. If I set OSPRAY_LOG_LEVEL to "debug" before launching the app, I can get output on the status callback. However, if I use the following code to set the log level after registering the error and status callbacks, I get no status output? Anything obviously wrong with setting the logLevel value below per the docs?:
if (verbose == RT_VERB_DEBUG) printf("OSPRay2Renderer) setting error / status callbacks...\n");
OSPDevice dev = ospGetCurrentDevice();
ospDeviceSetErrorFunc(dev, vmd_ospray2_error_callback);
ospDeviceSetStatusFunc(dev, vmd_ospray2_status_callback);
ospDeviceSetParam(dev, "logLevel", OSP_STRING, "debug");
ospDeviceCommit(dev);

Hmm, I'm seeing the same thing (no output) when setting the value through the API. But using --osp:log-level=debug works though.

I still feel that bogus or mismatched parameters and types should be treated as errors and therefore trigger the error output callback, and not as "status" information, but I see that's a choice that the OSPRay devs have made. If it is going to remain this way, I would strongly recommend documenting this such that it can't be missed, by pointing out this behavior as part of the discussion of ospSetParam(), etc.

Well, there is warnAsError which you could set, although that doesn't address your point.

Thanks for validating that you don't get correct logging behavior via the API either.  It occurs to me that there may be a catch-22 here:  If one uses the wrong string for "logLevel" it'll just silently fail to set it, so then you don't get any of those warnings.  Kind of funny.  Maybe the docs have a typo there?  I'm going to call it a night for now.

Ah, seems the docs don't match the code. Docs say that logLevel is of type string, but the code actually assumes an int:
https://github.com/ospray/ospray/blob/2a97f95e1726fdbf65e75ef4cc7e50d29b2b5425/ospray/api/Device.cpp#L85

Yup, OSP_LOG_DEBUG is 1, using that value triggers the handlers

Echoing @tachyon-john above, I feel more things that are currently flagged as warnings should be reported as errors. For example, my typo ospray::cpp::Geometry geom("curves") will not work due to the incorrect geometry type but it is only reported as a warning ("WARNING: unrecognized geometry type 'curves'") .But any subsequent calls on the geom object will result in errors due to the underlying handle being null. Failing object construction should really be a severe type of error.
Plus I can imagine applications building on ospray setting a default log level of error to make those always visible.


Scope KMS policy to the exact KMS key

The policy here can be updated to scope it to the exact KMS key. For an example of the syntax, see https://github.com/terraform-ibm-modules/terraform-ibm-cos/pull/764

CC: @SarikaSinha


implement EQUIP_WEAPON action

EQUIP_WEAPON takes hero id and card id.
It should add a weapon id to weapon in heroesById and it should add a new object to weaponsById with properties from wiki.  The values of the properties can be looked up in cards.json

@ericebersohl I'll start working on this one.


Configure build-scan plugin

This small PR configures the build-scan Gradle plugin (https://guides.gradle.org/creating-build-scans/) which yields further insight into the build, allowing the team to make informed decisions on where and when the build may be tweaked to get faster, more performant builds.

Thanks! The change has been merged.

Thanks! 😄


[TFB-1449] Add basic git-review setup/usage to Contributors

Here are notes I took while setting up git-review and sending my first patch (for https://jira.tungsten.io/browse/TFB-1412 ) They need to be cleaned up, converted to .rst, and added to the Contributors directory.

Confirm you have a Jira ticket for the work (required for commit)
Confirm you have a signed CLA?

Gerrit > Settings > Agreements > New Contributor Agreement OR
https://contributor.lfcla.com/#/login
Should be directed to this first time you try to do a git-review?

Clone the repo (if you don’t have it yet)

Log into gerrit.tungsten.io
Click Browse > Repositories
Select the repo you want
git clone "ssh://vmbrasseur@gerrit.tungsten.io:29418/docs"

Set up SSH access for Gerrit (required for the scp in the next step)

Log into gerrit.tungsten.io (if you’re not already)
Click the ‘Settings’ gear in the upper right next to your name
Click ‘SSH Keys’
Add your public SSH key (.pub)
Test: ssh -p 29418<EMAIL_ADDRESS>gerrit version
Should be gerrit version 2.16.8 or higher

Set up git-review

References

section 4.2: https://github.com/tungstenfabric/docs/blob/master/Contributor/GettingStarted/getting-started-with-tungstenfabric-development.md
https://docs.openstack.org/infra/git-review/
https://www.mediawiki.org/wiki/Gerrit/git-review

pip install —user git-review
Update path to include git-review ($HOME/Library/Python/2.7/bin on macOS; ~/.local/bin on Ubuntu thanks to that --user in the pip command)
export PATH=$HOME/Library/Python/2.7/bin:$PATH <— .bash_profile
cd $repo

Set git config for the repo

git config user.email<EMAIL_ADDRESS>gitdir=$(git rev-parse --git-dir);
scp -p -P 29418 vmbrasseur@gerrit.tungsten.io:hooks/commit-msg ${gitdir}/hooks (necessary? cloned w/hooks above)
git remote add gerrit ssh://vmbrasseur@gerrit.tungsten.io:29418/docs
git review -s (tests the setup; success == no messages)

Make necessary changes
Commit your  changes

Use commit -s so you’ll get the signed-off-by, which is required by git review
If you forget to sign a commit, run git commit --amend -s -c <SHA> on it

Run git review to get the patch into Gerrit

git review

Success looks something like this:
`Θυια:docs vmb$ git review
remote:
remote: Processing changes: }}{{new: 1 ()
remote: Processing changes: new: 1 (|)
remote: Processing changes: new: 1
remote: Processing changes: new: 1
remote: Processing changes: new: 1 ()
remote: Processing changes: refs: 1, new: 1 ()
remote: Processing changes: refs: 1, new: 1, done
remote:
remote: SUCCESS
remote:
remote: New Changes:
remote:   https://gerrit.tungsten.io/r/c/docs/+/24 Reorg docs directories
To ssh://gerrit.tungsten.io:29418/docs

[new branch]      HEAD -> refs/for/master
`

Notes from Will:
After much trial and error, I was able to get a patch submitted.
My commit message looks like this:
$ git log
commit a474020b9c42f2d0526793a9534f8f9e38107b77 (HEAD -> swill)
Author: swill<EMAIL_ADDRESS>Date:   Fri Sep 13 15:02:36 2019 -0400
Updated the docs to be Read The Docs compatible

Jira Ticket: https://jira.tungsten.io/browse/TFB-1481
Closes: TFB-1481
Issue-ID: TFB-1481

Change-Id: I7c211b4799989f7563fe2f752528698c897e7d03
Signed-off-by: swill<EMAIL_ADDRESS>
It turns out that Issue-ID: is CASE SENSITIVE, so it has to be written EXACTLY as specified with case, etc...
It was pushed with the following command:
$ git push gerrit HEAD:refs/for/master%topic=swill-read-the-docs
I followed Vicky's instructions for the most part: https://jira.tungsten.io/browse/TFB-1449
I didn't do these steps because I didn't understand what it was trying to make me do, so I skipped these steps:
$ gitdir=$(git rev-parse --git-dir);
$ scp -p -P 29418 vmbrasseur@gerrit.tungsten.io:hooks/commit-msg ${gitdir}/hooks (necessary? cloned w/hooks above)
I used this extensively trying to get a format which was accepted:
$ git commit --amend -s -c 7359a37704ac5fd507ee4055c977413afc1c6281
Hopefully this helps.  Let me know if you still have issues and I will see if I can help.

Note: When writing this up, be aware of the Python version in the path. Come up with a way to generalise that.


Node.js RTE: “ERR_UNKNOWN_BUILTIN_MODULE” about “node:readline/promises”

I always get this when I try to use μtap in different projects.
Using Mocha, CSJ modules:
$ npx mocha | npx utap

node:internal/errors:478
    ErrorCaptureStackTrace(err);
    ^
Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:readline/promises
    at new NodeError (node:internal/errors:387:5)
    at ESMLoader.builtinStrategy (node:internal/modules/esm/translators:259:11)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:468:14) {
  code: 'ERR_UNKNOWN_BUILTIN_MODULE'
}
<MY_PROJECT>/node_modules/mocha/lib/runner.js:965
    throw err;
    ^
Error: write EPIPE

Using only native node:test, ES6 modules, enabling Node.js debug info:
$ node --trace-warnings test/index.mjs  | npx utap

(node:938777) ExperimentalWarning: The test runner is an experimental feature. []
    at emitExperimentalWarning (node:internal/util:227:11)
    at node:test:5:1
    at NativeModule.compileForInternalLoader (node:internal/bootstrap/loaders:329:7)
    at NativeModule.compileForPublicLoader (node:internal/bootstrap/loaders:269:10)
    at loadNativeModule (node:internal/modules/cjs/helpers:50:9)
    at ESMLoader.builtinStrategy (node:internal/modules/esm/translators:257:18)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:468:14)
node:internal/errors:478
    ErrorCaptureStackTrace(err);
    ^
Error [ERR_UNKNOWN_BUILTIN_MODULE]: No such built-in module: node:readline/promises
    at new NodeError (node:internal/errors:387:5)
    at ESMLoader.builtinStrategy (node:internal/modules/esm/translators:259:11)
    at ESMLoader.moduleProvider (node:internal/modules/esm/loader:468:14) {
  code: 'ERR_UNKNOWN_BUILTIN_MODULE'
}

I have tried installing μtap globally, too.
I'm using Node.js 16, npm 8.

utap is designed for and only works with Node >=18. I added "engines" section in package.json in v0.1.3. Thank you.

Good question,
I guess the main motivation for me writing μtap was having a decent and
non-bloated TAP formatter for the new Node's built-in tests which have only
been released from behind the experimental flag in Node 18.
Everything else could probably still be made to work in Node 16 as well,
but I just didn't feel like ironing out subtle API differences :)
On Tue, 15 Nov 2022 at 04:15, tripu @.***> wrote:

utap is designed for and only works with Node >=18. I added "engines"
section in package.json in v0.1.3. Thank you.
Ah, I see! Thanks.
I switched to Node.js 18 and μtap worked well in both cases 👍
(Out of curiosity: what's the limitation with Node.js < 18?)
—
Reply to this email directly, view it on GitHub
https://github.com/dmaevsky/utap/issues/2#issuecomment-1314252691, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AADY2MB3V7F7GGEMXBYYY63WIKFTZANCNFSM6AAAAAAR7YNGRI
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Node did't add in cluster: " Waiting to register with Kubernetes"

What kind of request is this (question/bug/enhancement/feature request):
Just install rancher 2.4.3 on clean OS (Alpine 3.11).
And when I try to add node in new cluster with command (Node with same OS):
docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent:v2.4.3 --server https://r.ioi.pp.ua --token 5rs****d --ca-checksum 0***3 --node-name node1 --etcd --controlplane --worker

Result:
So I got an error in Rancher:
[controlPlane] Failed to upgrade Control Plane: [[[controlplane] Error getting node node1: "node1" not found]]

In Nodes page got status: Waiting to register with Kubernetes
If open node monitor page "Kubelet" is red.
more info:
kuber:~# docker ps
CONTAINER ID        IMAGE                                 COMMAND                  CREATED             STATUS              PORTS               NAMES
79d630a7f55e        rancher/hyperkube:v1.17.5-rancher1    "/opt/rke-tools/entr…"   2 minutes ago       Up 2 minutes                            kube-scheduler
2c1f24b4ed9a        rancher/hyperkube:v1.17.5-rancher1    "/opt/rke-tools/entr…"   2 minutes ago       Up 2 minutes                            kube-controller-manager
1e415625b4c3        rancher/hyperkube:v1.17.5-rancher1    "/opt/rke-tools/entr…"   2 minutes ago       Up 2 minutes                            kube-apiserver
0681263dcc75        rancher/coreos-etcd:v3.4.3-rancher1   "/usr/local/bin/etcd…"   3 minutes ago       Up 3 minutes                            etcd
f0a43eb3826e        rancher/rancher-agent:v2.4.3          "run.sh --server htt…"   3 minutes ago       Up 3 minutes                            inspiring_liskov

In Alpine setup only docker. Maybe need some another package?

I saw this too using Kubernetes version v1.15.4-rancher1-2.
It disappeared with version v1.15.11-rancher1-2.
Docker version 18.09.4, build d14af54266 in both cases.
Rancher 2.4.3

I am facing same problem. Here is what i did.

Created 4 new VMs(One for server and 3 worker nodes)
Followed below steps to setup rancher server on one of the VM.
https://rancher.com/docs/rancher/v2.x/en/quick-start-guide/deployment/quickstart-manual-setup/
Created cluster using same setup instructions. Ran command on all of the three nodes as per instructions
After some time cluster provisioning is stuck and i see mutliple errors in the rancher UI and one of them is below
Failed to upgrade Control Plane: [[[controlplane] Error getting node rancher-n2: "rancher-n2" not found]]

Can somebody guide how to fix this? I am struggling since three day on this.

I have the same issue. @BalajiTechs how did you fix that?
Or is there any update on this?

unfortunately no, didn't fix it
So, I was uninstall Rancher and delete Alpine
As I see... Rancher was work fine on ubuntu only
Now I am using Docker Swarm and Portainer.

I encountered this error today while spinning up an Azure cluster (raw VMs) with the Azure cloud provider enabled.
In my case, I had mismatched my resource group names in my node templates and my cluster's cloud-provider config.
Fixing the resource group names to match resolved the issue.

I have this issue too.
How can I solve the problem ???

I have this issue too.
How can I solve the problem ???

Is there a fix for this yet?
I am having the same issue.


Refactor tools/istio-iptables/main.go

Please provide a description for what this PR is for.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Hi @abhide. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@abhide: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-lint-master
5a24acd78fc3eae1dc06cd2f4b5748ecff614d79
link
/test istio-lint-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-lint-master
5a24acd78fc3eae1dc06cd2f4b5748ecff614d79
link
/test istio-lint-master

istio-unit-tests-master
5a24acd78fc3eae1dc06cd2f4b5748ecff614d79
link
/test istio-unit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-unit-tests-master
5a24acd78fc3eae1dc06cd2f4b5748ecff614d79
link
/test istio-unit-tests-master

istio-lint-master
f497f91a59274d81ac38dfdbb61adc085dc36216
link
/test istio-lint-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-unit-tests-master
cb8c2b4345d2052a933968c4b71950263d421cb8
link
/test istio-unit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

hmm.. Latest failure seems unrelated to my change: /test istio-unit-tests-master

Yeah, I've seen this error before. This is a bit flaky.
*** Test killed with quit: ran too long (10m0s).
FAIL	istio.io/istio/galley/pkg/config/meshcfg	600.010s

/test istio-unit-tests-master

@abhide: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-unit-tests-master
cb8c2b4345d2052a933968c4b71950263d421cb8
link
/test istio-unit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests-master

@abhide: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-unit-tests-master
cb8c2b4345d2052a933968c4b71950263d421cb8
link
/test istio-unit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests-master

@abhide: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-unit-tests-master
cb8c2b4345d2052a933968c4b71950263d421cb8
link
/test istio-unit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests-master

@abhide: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

istio-unit-tests-master
cb8c2b4345d2052a933968c4b71950263d421cb8
link
/test istio-unit-tests-master

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-unit-tests-master

@abhide: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

racetest_istio
cb8c2b4345d2052a933968c4b71950263d421cb8
link
/test racetest_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test racetest_istio

@abhide: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lintmodern_istio
03d35cddb92649af208646b552149161ce16ced8
link
/test lintmodern

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lintmodern_istio
03d35cddb92649af208646b552149161ce16ced8
link
/test lintmodern

unit-tests_istio
03d35cddb92649af208646b552149161ce16ced8
link
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lintmodern_istio
03d35cddb92649af208646b552149161ce16ced8
link
/test lintmodern

unit-tests_istio
af900c0b832727e43cd2573c3b5eb56c44180af7
link
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lintmodern_istio
03d35cddb92649af208646b552149161ce16ced8
link
/test lintmodern

unit-tests_istio
af900c0b832727e43cd2573c3b5eb56c44180af7
link
/test unit-tests

lint_istio
af900c0b832727e43cd2573c3b5eb56c44180af7
link
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
af900c0b832727e43cd2573c3b5eb56c44180af7
link
/test unit-tests

lint_istio
af900c0b832727e43cd2573c3b5eb56c44180af7
link
/test lint

lintmodern_istio
af900c0b832727e43cd2573c3b5eb56c44180af7
link
/test lintmodern

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
af900c0b832727e43cd2573c3b5eb56c44180af7
link
/test lint

lintmodern_istio
af900c0b832727e43cd2573c3b5eb56c44180af7
link
/test lintmodern

unit-tests_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lintmodern_istio
af900c0b832727e43cd2573c3b5eb56c44180af7
link
/test lintmodern

unit-tests_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test unit-tests

lint_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test unit-tests

lint_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test lint

lintmodern_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test lintmodern

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test unit-tests

lint_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test lint

lintmodern_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test lintmodern

integ-mixer-k8s-tests_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test integ-mixer-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

lint_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test lint

lintmodern_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test lintmodern

integ-mixer-k8s-tests_istio
37e585df718f3097000046a44f476904f29c3ee9
link
/test integ-mixer-k8s-tests

unit-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test unit-tests

integ-mixer-k8s-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test integ-mixer-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test unit-tests

integ-mixer-k8s-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test integ-mixer-k8s-tests

e2e-simpleTestsMinProfile_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test e2e-simpleTestsMinProfile

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test integ-mixer-k8s-tests

e2e-simpleTestsMinProfile_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test e2e-simpleTestsMinProfile

unit-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test unit-tests

integ-mixer-k8s-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test integ-mixer-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test integ-mixer-k8s-tests

unit-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

unit-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test unit-tests

integ-mixer-k8s-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test integ-mixer-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I don't understand why the unit tests are failing. There are no indication that anything failed.

/test unit-tests

Not sure why the error is hidden, but:
$ ./tests/scripts/istio-iptables-test.sh
ok      istio.io/./tests/scripts/istio-iptables-test.sh/mode_redirect (script)  0.000s
ok      istio.io/./tests/scripts/istio-iptables-test.sh/mode_tproxy (script)    0.000s
ok      istio.io/./tests/scripts/istio-iptables-test.sh/mode_tproxy_and_ipv6 (script)   0.000s
ok      istio.io/./tests/scripts/istio-iptables-test.sh/mode_tproxy_and_wildcard_port (script)  0.000s
ok      istio.io/./tests/scripts/istio-iptables-test.sh/empty_parameter (script)        0.000s
ok      istio.io/./tests/scripts/istio-iptables-test.sh/outbound_port_exclude (script)  0.000s
ok      istio.io/./tests/scripts/istio-iptables-test.sh/wildcard_include_ip_range (script)      0.000s
ok      istio.io/./tests/scripts/istio-iptables-test.sh/clean (script)  0.000s
./tests/scripts/istio-iptables-test.sh: line 63: ISTIO_OUT: unbound variable

# Execute bash shell unit tests scripts
./tests/scripts/scripts_test.sh
Running IPv6 and IPv4 addresses validation functions...
Unit testing is specified...
Validation functions are loaded
Test has been completed successfully...
./tests/scripts/istio-iptables-test.sh
ok	istio.io/./tests/scripts/istio-iptables-test.sh/mode_redirect (script)	0.000s
ok	istio.io/./tests/scripts/istio-iptables-test.sh/mode_tproxy (script)	0.000s
ok	istio.io/./tests/scripts/istio-iptables-test.sh/mode_tproxy_and_ipv6 (script)	0.000s
ok	istio.io/./tests/scripts/istio-iptables-test.sh/mode_tproxy_and_wildcard_port (script)	0.000s
ok	istio.io/./tests/scripts/istio-iptables-test.sh/empty_parameter (script)	0.000s
ok	istio.io/./tests/scripts/istio-iptables-test.sh/outbound_port_exclude (script)	0.000s
ok	istio.io/./tests/scripts/istio-iptables-test.sh/wildcard_include_ip_range (script)	0.000s
ok	istio.io/./tests/scripts/istio-iptables-test.sh/clean (script)	0.000s
Makefile.core.mk:522: recipe for target 'common-test' failed
make[3]: *** [common-test] Error 1
Makefile:88: recipe for target 'common-test' failed
make[2]: *** [common-test] Error 2

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test integ-mixer-k8s-tests

unit-tests_istio
9899fa57956953a74769d09373659b5c84bad37b
link
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rlenglet @howardjohn thanks for bringing up the failure.
For now, I have revert to using fmt.Println instead of log.Info and updated the test script.
I will send a separate smaller PR for log later.

@abhide: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-k8s-tests_istio
c1977449464f5feb85157d346eec07d3fe5cd52e
link
/test integ-pilot-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-pilot-k8s-tests

@abhide: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-bookInfoTests-envoyv2-v1alpha3_istio
c1977449464f5feb85157d346eec07d3fe5cd52e
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-bookInfoTests-envoyv2-v1alpha3

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

e2e-bookInfoTests-envoyv2-v1alpha3_istio
c1977449464f5feb85157d346eec07d3fe5cd52e
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

integ-new-install-k8s-tests_istio
c1977449464f5feb85157d346eec07d3fe5cd52e
link
/test integ-new-install-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@abhide: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-new-install-k8s-tests_istio
c1977449464f5feb85157d346eec07d3fe5cd52e
link
/test integ-new-install-k8s-tests

e2e-bookInfoTests-envoyv2-v1alpha3_istio
c1977449464f5feb85157d346eec07d3fe5cd52e
link
/test e2e-bookInfoTests-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-new-install-k8s-tests_istio

/retest

@howardjohn All tests are passing now. Can you take a look?

thanks @howardjohn


Recent changes broke a use trick

See issue #1202 for background. This issue documents a related panic unrelated to the use of the experimental -source command introduced by changes starting with commit 6419f4524a1a5217e5d29fdc9ff0b6d4ca13b1a7. This failure occurs when using a module import trick popularized by @hanche on Gitter. Create a ~/.elvish/rc.elv with these lines:
use platform

# This is a clever way to conditionally import the `unix` module into the
# interactive namespace so that we don't get a startup exception when running
# on MS Windows.
nop (and $platform:is-unix (use unix))

-exports- = [&]
if $platform:is-unix {
  # -exports-[unix:] = $unix:  # not needed due to `use` trick above
  -exports-[umask] = $unix:umask
}

You should see a panic similar to this:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0x136f026]

goroutine 13793 [running]:
github.com/elves/elvish/pkg/eval.(*Ns).lookup(0x0, 0xc00042d385, 0x5, 0x1453420)
        /Users/krader/projects/3rd-party/elvish/pkg/eval/ns.go:68 +0x26
github.com/elves/elvish/pkg/eval.(*Ns).indexInner(...)
        /Users/krader/projects/3rd-party/elvish/pkg/eval/ns.go:60
github.com/elves/elvish/pkg/eval.deref(0xc0008565b0, 0xc0004c44b0, 0x10755cf, 0x142cae0)
        /Users/krader/projects/3rd-party/elvish/pkg/eval/var_ref.go:137 +0xf5
github.com/elves/elvish/pkg/eval.variableOp.exec(0x137f, 0x138a, 0x0, 0xc00042d380, 0xa, 0
xc0004c44b0, 0xc0008565b0, 0x203000, 0x203000, 0x203000, ...)
        /Users/krader/projects/3rd-party/elvish/pkg/eval/compile_value.go:320 +0x4d
github.com/elves/elvish/pkg/eval.compoundOp.exec(0x137f, 0x138a, 0x0, 0xc0004c6190, 0x1, 0
x1, 0xc0008565b0, 0x1473b40, 0x145ef01, 0xc00082cb40, ...)
        /Users/krader/projects/3rd-party/elvish/pkg/eval/compile_value.go:75 +0x69
github.com/elves/elvish/pkg/eval.seqValuesOp.exec(0x137f, 0x138a, 0xc0004c6180, 0x1, 0x1,
0xc0008565b0, 0xc000843180, 0xc00005caf0, 0x109bd32, 0xc00032de60, ...)
        /Users/krader/projects/3rd-party/elvish/pkg/eval/compile_value.go:620 +0xb3
github.com/elves/elvish/pkg/eval.(*assignOp).exec(0xc0004b1840, 0xc0008565b0, 0xc00005ce38
, 0x0)
        /Users/krader/projects/3rd-party/elvish/pkg/eval/compile_lvalue.go:110 +0x232
github.com/elves/elvish/pkg/eval.(*formOp).exec(0xc0004bb080, 0xc0008565b0, 0x0, 0x0)
        /Users/krader/projects/3rd-party/elvish/pkg/eval/compile_effect.go:388 +0x862
github.com/elves/elvish/pkg/eval.(*pipelineOp).exec.func1(0x152b780, 0xc0004bb080, 0xc0008
565b0, 0xc000010738, 0xc0007808e0, 0xc0003f8e00)
        /Users/krader/projects/3rd-party/elvish/pkg/eval/compile_effect.go:150 +0x3f
created by github.com/elves/elvish/pkg/eval.(*pipelineOp).exec
        /Users/krader/projects/3rd-party/elvish/pkg/eval/compile_effect.go:149 +0x225

A debug print in pkg/eval/var_ref.go@deref shows that its variable.Get().(*Ns) call is returning nil for the ns pointer and true for ok when subName is "umask". Resulting in the nil pointer being dereferenced by the ns.indexInner(subName) call.

The recent changes also breaks the more straightforward approach:
use platform
if ($platform:is-unix) {
    use unix
}
# ... more initialization
if $platform:is-unix {
    -exports-[umask] = $unix:umask
}

That doesn't result in a panic but does report compilation error: variable $unix:umask not found. So this change seems to make it impossible to conditionally import and use a module. At least when it is a builtin, pre-defined, module.

See also issue #1116 where I ask how to conditionally use a module interactively (such as the unix module). That issue resulted in me using the import trick suggested by @hanche. That trick was broken by the recent changes to how namespaces are managed.

I don't have any opportunity to test the new version now myself right now, but out of curiosity: Does the following work with the new version?
nop (foo = bar)
echo $foo

assuming $foo was not defined before, of course.

I suddenly had a spare moment to try what I asked above. It works just fine without crashing.

Hmm, this is a very subtle bug where the arguments of special commands (in this case and) are compiled twice, and only the result of the first compilation is evaluated.
In nop (and $platform:is-unix (use unix)), the use unix form is compiled twice since it's part of an argument of and. This causes there to be two $unix: variables, the second one shadowing the first. However, since only the first instance of use unix is executed, the unix: module is only stored in the first shadowed $unix: variable, leaving the second $unix: variable nil.

Hmm, this is a very subtle bug where the arguments of special commands (in this case and) are compiled twice, and only the result of the first compilation is evaluated.
In nop (and $platform:is-unix (use unix)), the use unix form is compiled twice since it's part of an argument of and. This causes there to be two $unix: variables, the second one shadowing the first. However, since only the first instance of use unix is executed, the unix: module is only stored in the first shadowed $unix: variable, leaving the second $unix: variable nil.


Query does not find DynamoDbTableName on valueConstructor

I have defined an object as follow:

@table(tableName)
export class NotificationTrigger {
  @hashKey()
  id: string;

  @rangeKey()
  sortKey: string;

  @attribute({
    indexKeyConfigurations: {
      gsi1: "HASH"
    }
  })
  gsi1PK: string;

  @attribute({
    indexKeyConfigurations: {
      gsi1: "RANGE"
    }
  })
  gsi1SK: string;
}

Where tableName is a string constant equal to my dynamo table Name (unprefixed).
I'm trying to query this object using my partition key with a query:
dataMapper.query(NotificationTrigger, { id: partitionKey });
but I'm getting this error:

Error: The provided item did not adhere to the DynamoDbTable protocol. No string property was found at the DynamoDbTable symbol

I don't understand why the table decorator is not working, is there something I'm missing ?
I'm on version 0.7.3
Also, here are my compiler options for typescript:
"compilerOptions": {
    "target": "es2016",
    "module": "commonjs",
    "moduleResolution": "node",
    "noImplicitAny": false,
    "lib": ["es2017", "dom"],
    "removeComments": true,
    "preserveConstEnums": true,
    "sourceMap": true,
    "forceConsistentCasingInFileNames": true,
    "outDir": "dist",
    "declaration": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true
  },

So I managed to find the non-root cause of the issue. I'm actually using a subclass of DataMapper, and the simple fact of importing my NotificationTrigger class inside my DataMapper subclass was causing all this.
It's not just query that was malfunctioning, all calls made to get or write items of type NotificationTrigger were failing because my prototype seems to be modified.
I don't know what's actually happening under the hood, if you want to investigate I can give you a reproducible example.


Problem with 'Avoided fields'

Hi there. According to the description,  I can disable the shortkey by 3 ways. However, when I try to disable it at one specific component in my project which is not an input field, all methods failed. I tried to put 'v-shortkey.avoid' at the root element in that component, and put it's root element class name in the 'prevent' array. The shortkey still works. Could any one help me out? Thank you

Hi, I found where the problem is. To make sure the field is avoided, that particular element should be focused. Sorry for that


Warning: ReactDOMComponent: Do not access .getDOMNode() of a DOM node

The component still has react dependency at >- 0.12.. There is no plan to upgrade to 0.14. unless those methods are actually removed in a react version.

fixed in 2.0.1 release

Thank you!


Some verses are not displayed in songs

Some verses in the song Ten Thousand reasons are not displayed by the app.

@sskjames  can mention the songs? It will helpful to identify the problem.

 The sun comes up,
It's a new day dawning
It's time to sing Your song again]]>
</verse>
<verse type="v" label="1">
             <![CDATA[Whatever may pass,
and whatever lies before me
Let me be singing till the evening comes]]>
</verse>
<verse type="v" label="2">
             <![CDATA[2.  And on that day,
When my strength is failing
The end draws near,
And my time has come]]>
</verse>
<verse type="v" label="3">
     <![CDATA[Still my soul will sing
      Your praise unending
      Ten thousand years
       and then forevermore]]>
</verse>
</lyrics>
</song> ```

 And verse order is c1 v1 c1 v2 c1 v3 c1.

The verse order c1 have two different contents. One is start with "Bless the lord". Other is *Sing like never before*. We  need to update this song with respective verse order.

This issue is not related to the app. Will fix it in db.


Feature: use the BigQuery dataset to supplement null source repo URLs for dependency checks

Is your feature request related to a problem? Please describe.
In v0 of the DepedencyDiff API (issue #2008), we skip those dependencies without a srcRepo URL for the scorecard checks, but those dependencies might be important.
Describe the solution you'd like
Use the BigQuery dataset to retrieve the srcRepo given the dependency's {pkg_ecosystem, pkg_name, pkg_version}, to supplement those null srcRepo URLs and get them checked by scorecard.
Additional context
This is a TODO introduced in PR #2046.

https://github.com/ossf/scorecard/issues/2008#issuecomment-2140865208


Misleading information about App Workspace visibility

In the section above about creating app workspaces (https://docs.microsoft.com/en-us/power-bi/developer/embedding-content#appws), it says that setting a workspace as Public will allow users to see all content.  From my own testing, this refers only to the relationship the workspace has with Office 365 groups and related content.  Only members of the workspace are actually able to see Power BI content.

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

ID: 0fdac5f7-cd43-34c5-5905-dceeb9813952
Version Independent ID: 6fd53f84-dbb2-2a9c-2745-ea1999779113
Content: How to embed your Power BI dashboards, reports and tiles - Power BI
Content Source: powerbi-docs/developer/embedding-content.md
Service: powerbi
GitHub Login: @markingmyname
Microsoft Alias: maghan

Thank you for your feedback.  We will look into this, so it's addressed.

@mparowski Please reference articles - https://docs.microsoft.com/en-us/power-bi/developer/embed-sample-for-customers or https://docs.microsoft.com/en-us/power-bi/developer/embed-sample-for-your-organization for specific information on embedding applications depending on your audience.  Thank you.


Extension - Update Network details screen for TON

Describe the bug
Update Network details screen for TON

Add "Network type" = TON
Remove "Address prefix"
Remove "ParaId"
Remove "Crowdloan URL"

Version test : http://<IP_ADDRESS>:8900/s/Sn6srqRKTQKkDQx
Validation passed in case :

Install/Update version

Check network detail for TON mainnet/TON testnet

Re-check network detail for some networks

Re-check transfer token TON


Describe what you expected:
Releases should also have linux/amd64 images.
Steps to reproduce the issue:
https://registry.hub.docker.com/r/datadog/serverless-init/tags
Additional environment details (Operating System, Cloud provider, etc):
Cloud Run only supports linux/amd64 images, so this is a blocker for using the latest version there.

I will say, we've been using the init script in Cloud Run with a SHA version lock and it still works on Cloud Run for some reason.

Still missing. As of the new push yesterday, I start seeing this from my build scripts:
invalid from flag value datadog/serverless-init:latest: no matching manifest for linux/amd64 in the manifest list entries

relates to https://github.com/DataDog/datadog-agent/issues/18160 ?

The metadata in the current image is wrong. The entire image consists of an AMD64 executable, so as long as you use it to copy the agent to your own (AMD64) image, is just works.

The metadata in the current image is wrong. The entire image consists of an AMD64 executable, so as long as you use it to copy the agent to your own (AMD64) image, is just works.

This is mostly true. My builds were blocked three days ago because the image was arm64. The image was updated after opening a support ticket.

Ah, so it's even more confusing than I thought 😆 . Out of curiosity, which tag did you use when that occurred? I've been using beta9 and didn't see that, but maybe I was either too early or too late.

We use latest.


Make the script use less RAM

when using slashy in replit, it will reach 512 MB RAM limit. And the program will just stop doing anything. When running it for 5-10 seconds, it went fine. but it suddenly hit 512MB RAM and then no response (there are no errors)

i am using the program with 3 alts (if this helps)

Ran it on 4 accounts using replit for 2 months, had no ram issues myself..

idk then. but it seems that my ram is all used up

The script uses less ram. I was able to use it on replit for 2 months with 18 accounts


Update and rename topics/library/index.md to  المواضيع/ المكتبة/index.md

https://library.islamweb.net/maktaba/index.php?flag=1&page=bookpages&bookid=210&id=4&bookparts=[22:1]&LoadTab=LoadBookDetail
Thank you for contributing! Please confirm this pull request meets the following requirements:

[ ] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[ ] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288)
[ ] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

[ ] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[ ] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of why you think this topic or collection should be curated.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Lisa Budzinski
On Thu, Jul 4, 2019, 8:51 AM Justin Kenyon<EMAIL_ADDRESS>wrote:

Closed #842 https://github.com/github/explore/pull/842.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/explore/pull/842?email_source=notifications&email_token=AHLLGCWOWNC6BN3ET3EH323P5XW5PA5CNFSM4H4M2QU2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSKUGOIQ#event-2460509986,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHLLGCSZCK4IIOWGD4ESPRDP5XW5PANCNFSM4H4M2QUQ
.

Lisa Budzinski
On Wed, Jul 10, 2019, 9:32 PM Lisa Budzinski<EMAIL_ADDRESS>wrote:

Lisa Budzinski
On Thu, Jul 4, 2019, 8:51 AM Justin Kenyon<EMAIL_ADDRESS>wrote:

Closed #842 https://github.com/github/explore/pull/842.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<
https://github.com/github/explore/pull/842?email_source=notifications&email_token=AHLLGCWOWNC6BN3ET3EH323P5XW5PA5CNFSM4H4M2QU2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSKUGOIQ#event-2460509986
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AHLLGCSZCK4IIOWGD4ESPRDP5XW5PANCNFSM4H4M2QUQ
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/explore/pull/842?email_source=notifications&email_token=AHLLGCTIBNVPKUZ6C7OZUHLP62ETLA5CNFSM4H4M2QU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZVGWPY#issuecomment-510290751,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHLLGCSNNEXFVRRFCLXYIO3P62ETLANCNFSM4H4M2QUQ
.


Update schema generation script to include mistral models

Update schema generation script to include mistral models to temporary support backward compatibility in st2flow.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #103   +/-   ##
=======================================
  Coverage   94.24%   94.24%
=======================================
  Files          38       38
  Lines        2379     2379
  Branches      470      470
=======================================
  Hits         2242     2242
  Misses         79       79
  Partials       58       58

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 475667b...f92d57e. Read the comment docs.


<IP_ADDRESS> is not accessed from other devices

When using version 2.1698-vsc1.41.1 of the code-sever in Termux on Android everything worked normally and access was made from any device on the network.

When updating the code-server to the current version (3.1.1) I can no longer access vscode, I only have access to ssh. To try to open port 8080 I tried to use ufw but termux without root does not let you modify the interfaces and network settings.
(code server)
(can't access vscode in pc)

(ssh working fine)
So, I realized that the problem occurs because the server address was changed from "localhost" to "<IP_ADDRESS>" and this is probably the cause of the reported problem

Try setting the --host flag. I think that may solve the issue.

Try setting the --host flag. I think that may solve the issue.

when i try " code-server -- host localhost" nothing changes. When i try "code-server -- host localhost:8080" i get a error "ENOTFOUND"

Try setting the --host flag. I think that may solve the issue.

Thank you very much, worked fine :)


feat: Implement turbofish operator

Description
Problem*
Resolves #3413
Summary*
Adds the turbofish operator ::<> to variables and method calls in Noir.
Additional Context
I'm publishing this as a draft because I'm shelving this work for now after implementing the majority of it.
The work that remains to be done is handling the special case of method calls on generic impls. A generic impl will implicitly add the impl generics to each method - which means the generic count on a method itself as seen by the turbofish operator will not match the actual generics on the function internally. We'll likely need to separate out these implicit generics internally. Such that expected_generic_count = function_generics - impl_generics. I've added this as a test case to the generics test to ensure it works when this is merged.
Documentation*
Check one:

[ ] No documentation needed.
[ ] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.
[x] No documentation is in this PR yet since it is still a draft.

PR Checklist*

[x] I have tested the changes locally.
[ ] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Would be nice to revive it

This should be ready again for the original simple test cases. I will have follow-ups to enable https://github.com/noir-lang/noir/issues/4710
To handle implicit generics on an impl I save the number of generics on the object type when converting a method call to a regular call. We then prepend these implicit generics to the supplied turbofish generics on the function for constructing the new function call HirIdent. We need to do this as the Type::Forall we will instantiate against will include these implicit generics along with the function generics. I kept the function generic count and implicit generics count as distinct variables as I found it to be simpler.

Odd, they were working locally.

Ah, it's due to the lack of stdlib. I can fix these

Not gonna try and commit at the same time as you but copying the trait impls from the other test should fix it.

Trying to wrap up a separate bug right now, but will get back to this shortly.
One more thing to note is implementing this in the new elaborator as well. I will add that before merging.

Ah, it's due to the lack of stdlib. ~I can fix these~ Not gonna try and commit at the same time as you but copying the trait impls from the other test should fix it.

Ok noirc_frontend tests are updated and should be passing. Added some basic formatter tests as well

Looks like the formatter is injecting unwanted spaces before the fish.

Are we planning to add docs for this now or later?

Are we planning to add docs for this now or later?

I'll do a follow-up as this is a pretty old PR so let's get this in first

Looks like the formatter is injecting unwanted spaces before the fish.

Hmm I'll look again I thought I had it working locally

In light of https://github.com/noir-lang/noir/pull/5049 I'm going to double check how turbofish arguments are stored for the monomorphizer. Please hold off on merging until then. (I can't request changes)

This should be ready again

LGTM

Ok going to merge

Tried using it and got the error on the simplest example:
use dep::std::unsafe::zeroed;

fn main() -> pub Field {
    fun::<2>()
}

fn fun<N>() -> Field {
    0
}

error: expected type Field, found type ()
  ┌─ /Users/leonidlogvinov/Dev/ZK/trait_repro/src/main.nr:3:18
  │
3 │   fn main() -> pub Field {
  │                    ----- expected Field because of return type
  │ ╭────────────────────────'
4 │ │     fun::<2>()
5 │ │ }
  │ ╰─' () returned here
  │

error: Unexpected ::, expected one of binary operator, Ident
  ┌─ /Users/leonidlogvinov/Dev/ZK/trait_repro/src/main.nr:4:8
  │
4 │     fun::<2>()
  │        ---
  │

Aborting due to 2 previous errors

I'm on Noir 0.30.0

Turbofish isn't in the 0.30.0 release, this code compiles fine on master.