Please release with a Java 21-compatible ByteBuddy

Describe the bug
Using Gradle, the latest released version of AssertJ requires a version of ByteBuddy that is incompatible with Java 21. Both Mockito 5.7.0 and AssertJ 3.24.2 use ByteBuddy and somehow the version of ByteBuddy is picked up from AssertJ's dependencies, not Mockito's. Mockito then fails because the version of ByteBuddy being picked up is not its own dependency.
Manually declaring a dependency to the latest version of ByteBuddy fixes the issue, but it shouldn't be the case for an important version such as 21. So please either release 3.25.0 if it's ready or 3.24.3 with just your dependency of ByteBuddy bumped to a Java 21-compatible version if all tests pass.

assertj core version: 3.24.2
java version: JDK 21 with Mockito 5.7.0
test framework version:
os (if relevant):

3.25.0 will be released soon. Meanwhile, as you mentioned, the workaround is to declare ByteBuddy explicitly.


Thanke for your great job.

By the way,if i want to simulate the different keff, how i can made it ?

First, thanks for using this code. The code was not designed with the modification of keff in mind, so you may need to revise it.


Expose env to disable auto Markdown feature.

Updated README with instructions and reason.

Released on v0.0.7.


Styling with Less

Is it possible to have the styling with Less? I would like to integrate the styling into an existing Less workflow, so I can use the same color variables.

I am doing this so it's defiantly possible but not by default.

@Martinomagnifico Just copy the CSS of chartist into chartist.less and make it dynamic where you need to. There is no base support for LESS and there won't be until there is a 100% working transpiler from Sass to LESS see #84


Update code-generators and fix discovered bugs

What this PR does
Update the code generators to 0.31.1 so that we can
consume new features, like options tracker
in fake clients.
This update exposed a bug in virtctl imageupload ds handling.
Also, since with the new fakeclient we are able to track the options
passed to the requests, the dryrun test in the pod-eviction-admitter
was re-enabled.
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

Update code-generators to 1.31.1

regarding the imageupload fix: FYI @codingben
/cc @0xFelix @xpivarc

@acardace for the re-enabling of the pod-eviction-admitter test

@0xFelix @xpivarc Fixed the typo in the commit message


Ensured default user_id set correctly in rack and rails3 middlewares

Currently the user_id doesn't exist on report and has no impact even if an accessor is provided.
This ensures the user id field is set to the user's Id in both rails3 and rack.

Coverage remained the same at 78.283% when pulling 5436b9297f687f121767c661b77abc137c499cb3 on cawllec/v5-user-id-fix into 03a1ebd7721775e4af1ee503b4e6f78cc44bdd3e on v5.


Fix Geo viewer bug.

This will filter all results that don't have the type field. This will prevent the bug from occurring again.

This change is

Ratel Preview:

looks good, please release @MichelDiz

looks good, please release @MichelDiz


installation instructions should mention dependency on crun

Instead of making a pull request that would fix this I just describe the problem here, since I am not sure how things are on other distros than Debian.
The problem:
$ ansible-bender build ./simple-playbook.yaml
12:52:40.734 utils.py          ERROR  error running container: error creating container for [/bin/true]: : exec: "crun": executable file not found in $PATH
12:52:40.738 utils.py          ERROR  error while running runtime: exit status 1
12:52:40.739 utils.py          ERROR  level=error msg="exit status 1"
12:52:40.740 buildah_builder.py ERROR  Unable to create or run a container using docker.io/python:3-alpine with buildah
error running container: error creating container for [/bin/true]: : exec: "crun": executable file not found in $PATH
error while running runtime: exit status 1
level=error msg="exit status 1"
There was an error during execution: Command '['buildah', 'run', 'a-very-nice-image-20211228-125236421634-cont-20211228125236499354', 'true']' returned non-zero exit status 1.

This is a Debian stable ("bullseye") system.
The solution:
$ sudo apt install crun

Should the crun dependency be mentioned in the docu here?

This sounds like a packaging mistake in Debian packaging: I'd say that installing buildah should install crun as well.
On the other hand, I don't see any harm in mentioning this in the readme.
So I'm closing this issue and will accept your PR.


F128 isn't getting correctly passed to variadic function in WebAssembly

The test was passing before. This is related to the change made to shadow memory.


[BUG] Sidebar and Flashcards are not updated after Obsidian syncs files from the cloud

Describe the bug
I am using several computers and rely on Obsidian sync to stay up to date on all of them. Though, it looks like the plugin is not updating its state after Obsidian updated the files and I get files in my "to review" list which have already been reviewed.
The state of the sidebar is updated when I force a reload (resp. restart Obsidian).
To Reproduce
Steps to reproduce the behavior:

Review a lot of files one one computer
Open Obsidian on another
Observe that the Spaced Repetition Plugin suggests the same list of files to review even after Obsidian has synced them

Expected behavior
The SR Plugin should reload its state after all files are synchronized. I assume that there's a hook or event provided by Obsidian to react to when the sync is done (or files change)?
Versions (please complete the following information):

OS: seen on iOS, macOS, Windows, and Linux
Obsidian version: v0.12.10
Plugin version: v1.5.7

Yes, the event's there (on 'modify'). I'll work on fixing this.


Enable PIN code function

As per draft LUD
https://github.com/bitcoin-ring/luds/blob/withdraw-pin/xx.md
https://github.com/lnurl/luds/pull/200/files#diff-b03763e9ce2c6b65c01f6808159d6fea9a31cfdda3482bd71dee60cf117a4a5a

related branches
https://github.com/boltcard/boltcard-wallet/tree/card-pin-number
https://github.com/boltcard/boltcard-lndhub/tree/card-pin-number
related issues
https://github.com/boltcard/bolt-nfc-android-app/issues/32
https://github.com/boltcard/bolt-card-pos/issues/15

https://github.com/boltcard/boltcard/tree/card-pin-number
card table database fields

pin_enable
pin_number
pin_limit_sats

added for

createboltcard
updateboltcard

internal api calls
TODO:
callback interactions as in
https://github.com/bitcoin-ring/luds/blob/withdraw-pin/xx.md

3d9e742dc1137ac12a8fe08b90898b91cb87ae62
lnurlw response includes pinLimit when configured in the card record

Database records for PIN can be set with the internal API [done]
LNURLw includes the pinLimit when the card record is set (pin_enable, pin_number, pin_limit_sats) [done]
PIN number check on LNURLw callback [to do]

I don't understand what this pin is solving?
PoS can still ie "I will only take x, honest, now give me the pin"
Its still possible to get the pin if the card is stolen.
It all seems pointless

I don't understand what this pin is solving?
PoS can still ie "I will only take x, honest, now give me the pin"
Its still possible to get the pin if the card is stolen.
It all seems pointless

I think this discussion should be in:
https://github.com/bitcoin-ring/luds/blob/withdraw-pin/xx.md
or
https://t.me/lnurl/34810

Thanks for your comment - this issue is really only for part of the implementation.
There is some discussion on the LUD here that you might find useful.
https://t.me/bolt_card/4154
Feel free to come to the group and discuss it some more 👍

I don't understand what this pin is solving?
PoS can still ie "I will only take x, honest, now give me the pin"
Its still possible to get the pin if the card is stolen.
It all seems pointless

Thanks for your comment - this issue is really only for part of the implementation.
There is some discussion on the LUD here that you might find useful.
https://t.me/bolt_card/4154
Feel free to come to the group and discuss it some more 👍

I don't understand what this pin is solving? PoS can still ie "I will only take x, honest, now give me the pin" Its still possible to get the pin if the card is stolen. It all seems pointless
@arcbtc
The pin solves for when the card is misplaced by the user and someone else picks it up, not a mitigation for a dishonest merchant.
The pin is not stored on the card so unsure how it can be stolen.
This feature was requested by the biggest bolt card user in Brazil he sets up hundreds / thousands of bolt cards for kids to pay for fruit at their school..

PIN number check on LNURLw callback [done]


[new] Update Readme.md and repair bugs with the modification of fastnlp 0.4.5

Description：简要描述这次PR的内容
Main reason: 做出这次修改的原因
Checklist  检查下面各项是否完成
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [$CATEGORY] (例如[bugfix]修复bug，[new]添加新功能，[test]修改测试，[rm]删除旧代码)
[ ] Changes are complete (i.e. I finished coding on this PR)  修改完成才提PR
[ ] All changes have test coverage  修改的部分顺利通过测试。对于fastnlp/fastnlp/的修改，测试代码必须提供在fastnlp/test/。
[ ] Code is well-documented  注释写好，API文档会从注释中抽取
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change  修改导致例子或tutorial有变化，请找核心开发人员

Changes: 逐项描述修改的内容

添加了新模型；用于句子分类的CNN，来自Yoon Kim的Convolutional Neural Networks for Sentence Classification
修改dataset.py中过时的和不合规则的注释 #286
添加对var-LSTM的测试代码

Mention: 找人review你的PR
@修改过这个文件的人
@核心开发人员

Codecov Report

Merging #190 into dev0.5.0 will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           dev0.5.0     #190   +/-   ##
=========================================
  Coverage     60.74%   60.74%
=========================================
  Files           101      101
  Lines         10305    10305
=========================================
  Hits           6260     6260
  Misses         4045     4045

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 1dd8db7...ec08564. Read the comment docs.


Bottom nav is behaving wierdly

Hi,
I am trying to use the nav system you used in this project in one of mine. But I am facing some issues. It'd be great if you could help me out.
I have two subgraphs - Instrument and Transaction, which are also shown on the bottom bar. When I press instruments, it does not navigate to instrument, but starts switching between instrument and transaction. I've attached a screen recording below.
Here is a link to project repo

I just tested it and it seems to work fine. You already fixed it, right?


Add Roboto Condensed

https://fonts.google.com/specimen/Roboto+Condensed

Roboto Condensed was already in the repo, under the Roboto Sans folder. I just updated it with the most recent files from the Roboto (Sans) GitHub repo.


Fix: Copy SVG properties into the child in react-native-svg

Copy SVG properties into its children.
Fixes #1478 , where icons are blacked out after OTA updates. Some related issues in react-native-svg, where children properties are not copied by default:
https://github.com/software-mansion/react-native-svg/issues/1284
https://github.com/software-mansion/react-native-svg/issues/1287
We might want to also consider removing the stroke, fill, etc off the defaultAttributes as they get over-ridden anyways, and to have them only apply to the children elements instead of the parent <Svg> element. I kept them there since I'm not sure if removing them off the  element would cause unwanted behavior in some cases.

Tnx for the fix!


multiple terminal window

I could not find any methods to open multiple terminals using Code App. (opening multiple terminal tabs)
Supporting multiple integrated terminals (exactly like in VSCode) may help many users to work with this app better.

Ran into this limitation, too. My repository requires a script to be running, so need a second terminal for running other commands in the background.

@brandonsheppard You can now open multiple windows in iPadOS. It will allow you to run two terminals at the same time.


Allow running more than once

Repeated runs fail with [conda/stderr] mkdir: cannot create directory ‘_temp_home’: File exists . How do you develop this interactively (trial and error during development of an AppImage)?
Similar,
Running process: /home/me/linuxdeploy-plugin-conda.sh --appdir AppDir
[conda/stdout] Error: directory exists: AppDir/usr/conda
ERROR: Failed to run plugin: conda (exit code: 1)

Duplicate of #10.

No, #10 is about not downloading repeatedly.

#10 explains why it's necessary to error out to prevent running more than once.

Then this is my feature request to make it so that one can run multiple times, like linuxdeployqt. It is necessary for efficient trial-and-error development.

Same as https://github.com/linuxdeploy/linuxdeploy-plugin-conda/issues/10#issuecomment-494590494.

This plugin should be idempotent with some exceptions.

subsequent runs should recognize existing conda environment and not recreate the environment from scratch
installation of dependencies should be called normally, and should not (but that's not a hard requirement) update anything already installed


Best practice to implement "notebook like" interface

Is there a straight forward way to implement notebook like interface using this library (like jupyterlite / jupyterlab)? I I have been experimenting with usePythonConsole and I've found that it might work quite well.
I'm asking this mainly because the whole Pyodide ecosystem is new and there is not much info out there, especially regarding notebook interfaces which should now be relatively easy to implement with libraries like this one.
Thanks for any suggestions and keep up the good work.

A basic notebook interface should be quite straightforward as you only need to worry about UI/UX, however replicating all of the features from Jupyter notebooks would require a lot of work.
The usePythonConsole hook is probably the best way to achieve this. You would need to reuse a single Python instance to retain variables.
One major feature of Jupyter is that they seem to have detection for popular data visualisation libraries, such as matplotlib plt.show() which isn't trivial to do and you would probably require custom handling for each library.

Ideally I just need the option to retain variables and pass some data from js to python. From what I've read, Pyodide supports this

Reusing the same Python instance will retain variables, as it spawns a web worker which stays active until you terminate it or a user refreshes the page.
Support for accessing the Python scope is being tracked here #67 and is not yet implemented in react-py. This would allow for direct getting/setting data in Python from the JS side. There are methods in Pyodide which make this possible, but interacting with web workers adds a lot of complexity.


Implement dirichlet process over trial-switch components

This would go along with #14

Since a dirichlet process prior requires multiple traces, changepoints on a single-trial may not be shared across traces.
This will require a post-processing step to align changepoints across traces.
This can be done by fitting a GMM to the mode of each changepoint in a single trial - that is, there will be a 1D histogram where the points are the modes of changepoints across trials. Once the changepoints are clustered, we can potentially merge their histograms.

Since a dirichlet process prior requires multiple traces, changepoints on a single-trial may not be shared across traces.
This will require a post-processing step to align changepoints across traces.
This can be done by fitting a GMM to the mode of each changepoint in a single trial - that is, there will be a 1D histogram where the points are the modes of changepoints across trials. Once the changepoints are clustered, we can potentially merge their histograms.


Hobbies

Add your hobbies (including images)

Post hobby stuff here or with the other information on the "About Yourself" issue.


[graph_models] Depict association classes

This is a feature-request for the graph_models extension: Intermediary models could be shown as UML association classes.

We receive Pull Requests anytime, if you want to can contribute too. Thank you.


UI refresh

Video showing how the UI looks like, currently:
https://user-images.githubusercontent.com/81253203/138315961-c0593e89-afe3-41e9-ba84-4e328cc695da.mp4

I think the UI refresh is done, so this PR is almost ready to be merged.

I am also not able to think of a better design for Recording UI rn. I will try to create some designs and post them here.

For reference, this is how the Windows Voice Recorder app looks while recording:

The app is not in its final Windows-11-style form, but it's a good start.

@nahomebssa that's how I was inspired to make it in the previous versions of Fluent Screen Recorder. Whatever, we've had a discussion about it on Discord and we've decided to make a tiny bar like Xbox game bar from recording and expanding it afterwards

You should specify padding in ScrollViewer
Windows Apps:

Your changed app:

https://github.com/itsWindows11/Fluent-Screen-Recorder/blob/ui-refresh/FluentScreenRecorder/Views/SettingsPage.xaml#L86

You should specify padding in ScrollViewer
Windows Apps:

Your changed app:

https://github.com/itsWindows11/Fluent-Screen-Recorder/blob/ui-refresh/FluentScreenRecorder/Views/SettingsPage.xaml#L86

Created PR.

Created PR.

Closed because there are too many conflicts to handle, also the work will move to another PR.


Error on installing and testing DevKit

Hi, I'm new in ROR and I'm trying to install DevKit but I get some errors. I use Win7-64bit and i installed DevKit-mingw64-64-4.7.2-20130224-1432-sfx.
Honestly, the errors are not clear and I can't find out what I should do to fix the problem.
     C:\Devkit>type config.yml
This configuration file contains the absolute path locations of all
installed Rubies to be enhanced to work with the DevKit. This config
file is generated by the 'ruby dk.rb init' step and may be modified
before running the 'ruby dk.rb install' step. To include any installed
Rubies that were not automagically discovered, simply add a line below
the triple hyphens with the absolute path to the Ruby root directory.
Example:
---
- C:/ruby19trunk
- C:/ruby192dev
---
- C:/Ruby22

C:\Devkit>ruby dk.rb install
[INFO] Skipping existing gem override for 'C:/Ruby22'
[WARN] Skipping existing DevKit helper library for 'C:/Ruby22'

C:\Devkit>gem install json --platform=ruby
Temporarily enhancing PATH to include DevKit...
Building native extensions.  This could take a while...
ERROR:  Error installing json:
        ERROR: Failed to build gem native extension.

    C:/Ruby22/bin/ruby.exe -r ./siteconf20150524-7692-son84q.rb extconf.rb
creating Makefile

make "DESTDIR=" clean

make "DESTDIR="
generating generator-i386-mingw32.def
compiling generator.c
In file included from c:/Ruby22/include/ruby-2.2.0/ruby.h:33:0,
                 from ../fbuffer/fbuffer.h:5,
                 from generator.c:1:
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:111:14: error: size of array 'ruby_chec
k_sizeof_voidp' is negative
In file included from c:/Ruby22/include/ruby-2.2.0/ruby.h:33:0,
                 from ../fbuffer/fbuffer.h:5,
                 from generator.c:1:
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h: In function 'rb_obj_freeze_inline':
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1156:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1157:2: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1158:6: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1158:27: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h: In function 'rb_data_object_get':
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1192:13: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h: In function 'rb_obj_written':
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1271:10: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1271:34: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h: In function 'rb_num2char_inline':
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1344:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1344:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1344:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1344:36: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1344:36: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1344:36: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1345:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1345:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1345:9: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h: In function 'rb_class_of':
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1670:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h: In function 'rb_type':
c:/Ruby22/include/ruby-2.2.0/ruby/ruby.h:1687:12: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
In file included from generator.c:1:0:
../fbuffer/fbuffer.h: In function 'fbuffer_append_str':
../fbuffer/fbuffer.h:127:25: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
../fbuffer/fbuffer.h:127:25: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
../fbuffer/fbuffer.h:127:25: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'convert_UTF8_to_JSON_ASCII':
generator.c:129:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:129:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:129:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:130:38: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:130:38: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:130:38: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'convert_UTF8_to_JSON':
generator.c:227:23: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:227:23: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:227:23: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:228:25: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:228:25: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:228:25: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'cState_configure':
generator.c:559:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:559:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:559:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:560:34: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:560:34: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:560:34: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:567:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:567:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:567:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:568:33: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:568:33: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:568:33: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:575:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:575:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:575:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:576:40: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:576:40: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:576:40: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:583:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:583:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:583:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:584:36: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:584:36: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:584:36: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:591:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:591:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:591:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:592:37: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:592:37: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:592:37: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'set_state_ivars':
generator.c:640:21: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:640:21: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:640:21: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:642:24: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:642:24: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:642:24: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'generate_json_object':
generator.c:727:20: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:727:20: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:727:20: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'generate_json_array':
generator.c:773:20: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:773:20: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:773:20: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'isArrayOrObject':
generator.c:930:23: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:930:23: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:930:23: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:931:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:931:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:931:15: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'cState_indent_set':
generator.c:1055:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1055:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1055:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1064:32: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1064:32: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1064:32: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'cState_space_set':
generator.c:1093:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1093:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1093:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1102:31: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1102:31: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1102:31: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'cState_space_before_set':
generator.c:1129:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1129:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1129:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1138:38: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1138:38: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1138:38: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'cState_object_nl_set':
generator.c:1167:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1167:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1167:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1175:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1175:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1175:35: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c: In function 'cState_array_nl_set':
generator.c:1202:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1202:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1202:11: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1210:34: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1210:34: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
generator.c:1210:34: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
make: *** [generator.o] Error 1

make failed, exit code 2

Gem files will remain installed in C:/Ruby22/lib/ruby/gems/2.2.0/gems/json-1.8.2
 for inspection.
Results logged to C:/Ruby22/lib/ruby/gems/2.2.0/extensions/x86-mingw32/2.2.0/jso
n-1.8.2/gem_make.out

It looks like you have the i386 (x86) or 32-bit Ruby version and are trying to use the 64-bit DevKit.
Try using the mingw64-32-4.7.1 DevKit instead.

Closing due to inactivity


May I ask if the contracts in this folder can be tested on the remix official website

They can with the proper test values, I actually used it for initial dev. Fair warning that this code is not production ready.


Module versions list scroll bar does not work

The scroll bar does not seem to show up in some modules on deno.land/x, this is showing on the main page on e.g<EMAIL_ADDRESS>
Scrolling down and viewing older versions is not possible.

those are all the versions that the system knows. did you maybe only publish it on the registry after 2.6.2?

That's probably it, I forgot I renamed this module a while ago and republished. Closing this.


Black screen in landscape view. Realme 5 phone android 9

I don't have such device, I will try it on simulator

Try to resolve issues on physical latest version devices because your app works well on emulators but gives results like above on real devices.

Comments following lines in SampleActivity is working for me
if (Build.VERSION.SDK_INT < 16) {
            getWindow().setFlags(WindowManager.LayoutParams.FLAG_FULLSCREEN,
                    WindowManager.LayoutParams.FLAG_FULLSCREEN);
        } else {
            mPageFlipView.setSystemUiVisibility(
                    View.SYSTEM_UI_FLAG_FULLSCREEN |
                            View.SYSTEM_UI_FLAG_LAYOUT_STABLE |
                            View.SYSTEM_UI_FLAG_LAYOUT_HIDE_NAVIGATION |
                            View.SYSTEM_UI_FLAG_IMMERSIVE |
                            View.SYSTEM_UI_FLAG_HIDE_NAVIGATION);
        }


Edge performance problems

Hi Stefan!
There's a known performance problems for rendering attribute rules by Edge. A dedicated research (here)[https://medium.com/@andreygoncharov/edge-hates-you-attributes-d15faf162939]. Would you consider moving to classes in the next major version?

Sorry for the broken link “Edge hates you attributes” https://medium.com/@andreygoncharov/edge-hates-you-attributes-d15faf162939


Distinguish official KRM functions and community functions.

We can have different GCR to hold first-party and third-party functions.

cc @mengqiy

@mengqiy I think this has been finished?


Project Logo

Everybody knows that every awesome OSS project needs an awesome logo.
I'm thinking maybe the @artsy logo, but with a different font. Or maybe just slightly different kerning.
/cc @orta

I think the one in the Readme now is :100:


⚠ Bofrost.es has degraded performance

In ee56afa, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1473 ms

Resolved: Bofrost.es performance has improved in cbd3c20 after 17 minutes.


Wekan snap build stuck

@kubiko
When I look at Wekan build status at:
https://code.launchpad.net/~ondrak/+snap/wekan-devel
It says this, and has been stuck since yesterday, time estimate does not change:
"Needs building | in 8 hours (estimated) | amd64 | Primary Archive for Ubuntu"

hi @xet7
this was caused by long queue on build servers as we restarted package import from debian archive once ubuntu 17.10 was released. Unfortunately at the same time one region went down, so queue got even longer. It should settle and I can see it already improving. So nothing to worry about  :)


Blog posts

borsi

[ ] SNTeam Q1 goals, metrics and achievements
[ ] Q2 goals - where are we going?
[x] We moved to Github
[ ] Sensenet 5% - The FreeFriday project

@balazskeszei
snteam

[ ] Why NuGet? - @tusmester maybe?
[ ] Why JWT?
[ ] SN UI with Aurelia and React

Write an introduction to "sensenet ECM 7.0 components" description in the blog section.
Write an overview about CTD, why is it good? How do clients (should) use it?


optimize acc_offsets

optimize acc_offsets by eliminating creation of multiple copies of reversed upcasted_i in nested loops

this is less readable, please see https://github.com/tinygrad/tinygrad/?tab=readme-ov-file#contributing

this is less readable, please see https://github.com/tinygrad/tinygrad/?tab=readme-ov-file#contributing

Thank you, @chenyuxyz - I've renamed the variable to upcasted_i_reversed on my branch. Do you think it's better this way, or still not sufficiently readable?


Improve column filter UI

The X on column filters can be easily misconstrued for a close button

Filters should also close automatically when clicked past. MudPopover doesn't support it, but MudMenu might be a replacement.


Return uncofirmed utxos when listing & Support filtering by address

With this, ocean returns the list of unconfirmed utxos in the ListUtxosForAccount rpc. This also allows to filter account utxos by a set of addresses.
Please @louisinger review.

while signing a pset with an uncomfirmed utxo, I got "no wallet utxos found in given transaction" errors raised by findLockedInputs


Amend PCA coordinate label for "Molecular characterization of foveal versus peripheral human retina by single-cell RNA sequencing."

PCA coordinates are labeled as UMAP when they should be tSNE.
https://cellxgene.cziscience.com/collections/7edef704-f63a-462c-8636-4bc86a9472bd
I have already fixed the h5ad and can re-submit when revisions are possible.

@rachadele - since you'll be revising the collection, would you also edit the collection title and remove the '.'. It's a minor editorial issue, but doesn't match the style of existing collections ...

@brianraymor what is the ETA on enabling such a revision?
I am trying to determine if Rachel will have time to re-submit and then we migrate the re-submission, or if we should just lump the update in with the migration.

Based on outstanding issues in the epic and the need for additional testing, I expect that revisions is still +3 weeks out.

I will plan on this being included in the migration. If the opportunity presents itself, then Rachel can update via re-submission between now and then.
@rachadele is that the only change you were planning to make to this dataset?
I have moved the Collection title update to #102

@jahilton yes, I think so. I could also get rid of the cell_type field and final_cluster_labels since they seem redundant?

It seems like celltype & final_cluster_labels do group cells equally in this dataset. However, each might have their own value as either/both may be used in the paper when referencing the data. So we tend to view the free text cell type annotations & cluster labels as non-redundant, even in these cases.

New issue we uncovered today with this Dataset. The max value in .X is 8.821655. There is no raw.X layer, so the .X should be the raw values. Non-integer values less than 10 indicate the values are not raw.
@rachadele are raw (non-scaled, non-normalized) values available for this dataset?

Given the lack of raw counts, and no response from the researcher, we are deleting this dataset. Being done in https://github.com/chanzuckerberg/single-cell-data-portal/issues/1467


[bug]After reboot some apps may not showing in app list

This happens every time when my phone rebooting, after restart launcher twice, all fine

Can you be specific on which apps do this? I am resolving similar issue just now.

Can you retry on latest version?

@volnes, is this still a problem?

Please reopen if this is still issue on v59.


Identifiers validation failed for dataset Ecología poblacional de Abies hickelii en el Pico de Orizaba, Veracruz

Identifier validation failed for the dataset Ecología poblacional de Abies hickelii en el Pico de Orizaba, Veracruz:

Crawler attempt: 323
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 368
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 368 total records; 368 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3740102/step

New IDs sample:

Old IDs sample:

21b735487f80d974130664ab27ad986f
2eae10b48b1ba5f6d34c4bc75d3e22e8
347dc3e5cd55d56a203467c720f70467
4e8786668295d3e9af84113c3dd5db7b
4fb5e917aaec02f180fd0f9ddba21cf4
57cc1af9a475b0ad576a047665ed3f41
592b98f78f7a56f1203dc898e7674844
5f59b0efcfe165b801cc024cbc9732bc
60691eb43119377654fa15cd4a1a38c5
6328c5784acdafa3969fe5056fea625f

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Ecología poblacional de Abies hickelii en el Pico de Orizaba, Veracruz : https://doi.org/10.15468/fyesjz.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Ecología poblacional de Abies hickelii en el Pico de Orizaba, Veracruz:

Crawler attempt: 324
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 368
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 368 total records; 368 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741066/step

New IDs sample:

Old IDs sample:

21b735487f80d974130664ab27ad986f
2eae10b48b1ba5f6d34c4bc75d3e22e8
347dc3e5cd55d56a203467c720f70467
4e8786668295d3e9af84113c3dd5db7b
4fb5e917aaec02f180fd0f9ddba21cf4
57cc1af9a475b0ad576a047665ed3f41
592b98f78f7a56f1203dc898e7674844
5f59b0efcfe165b801cc024cbc9732bc
60691eb43119377654fa15cd4a1a38c5
6328c5784acdafa3969fe5056fea625f

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Ecología poblacional de Abies hickelii en el Pico de Orizaba, Veracruz : https://doi.org/10.15468/fyesjz.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Ecología poblacional de Abies hickelii en el Pico de Orizaba, Veracruz:

Crawler attempt: 326
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 368
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 368 total records; 368 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741677/step

New IDs sample:

Old IDs sample:

21b735487f80d974130664ab27ad986f
2eae10b48b1ba5f6d34c4bc75d3e22e8
347dc3e5cd55d56a203467c720f70467
4e8786668295d3e9af84113c3dd5db7b
4fb5e917aaec02f180fd0f9ddba21cf4
57cc1af9a475b0ad576a047665ed3f41
592b98f78f7a56f1203dc898e7674844
5f59b0efcfe165b801cc024cbc9732bc
60691eb43119377654fa15cd4a1a38c5
6328c5784acdafa3969fe5056fea625f

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Ecología poblacional de Abies hickelii en el Pico de Orizaba, Veracruz : https://doi.org/10.15468/fyesjz.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


Added in comments in .nvmrc

Overview
I added in support for comments in the .nvmrc file.
List of Updates

Modified the nvm_rc_version to strip comments
Removed support for spaces and #'s inside nvm aliases

So, would you like to delete this pull request, remove nvm cat, remove comment support, or keep both?

I think before deciding what code changes are needed, to this PR or nvm itself, we should have nonzero discussion about what the goal is, and why this feature is needed.

I think before deciding what code changes are needed, to this PR or nvm itself, we should have nonzero discussion about what the goal is, and why this feature is needed.

@ljharb
Sure, in this PR or a new issue

Might as well talk about it here :-)

Might as well talk about it here :-)

Sure

@ljharb Do we want to take action on this one with the intention of getting it merged ?

@sladyn98 I'm still not convinced it's worth the complexity.

@ljharb if you plan to not merge in the future don't you think we should close it

Would be very useful for "make sure you update the <docker container/CI config> too!" style comments

Do you mean allowing a .nvmrc, like this?:
“some comment”
node

The reason that this shouldn’t be added is because it removes support for aliases with double quotes and anyways, the following works:
# some comment
node

No, I mean the feature (as you propose it) would be useful for adding comments to the .nvmrc to remind people to change values elsewhere.
This was partially in response to

why this feature is needed

further up.

@penx isn't a CI job that fails when those aren't in sync much more effective than a comment?

@ljharb yes it would, but it may not always be feasible or convenient
e.g.

the place to keep in sync is not within the repository, such as a wiki or external repository
the format to keep in sync is hard to parse e.g. numbers contained in paragraphs in a markdown readme where there may be multiple mentions and the wording could change ("prerequisites: node >= 12 and <= 14.*, npm 7")
the number in .nvmrc doesn't exactly match the number of what you're trying to sync with
the management of the CI pipelines are done by a different team/company and it is not trivial to add new ones or modify existing ones

Another useful example of a useful comment (and one that isn't particularly suited for git commit messages, IMO):
14.0.0

# symlinked as .nvmrc/.node-version to support nvm, nodenv and asdf with a single file
# until such time as https://github.com/nodejs/version-management/issues/13 is resolved

@jasonkarns i mean, the symlink part is already self-evident from "the actual symlinks in the filesystem"; it's just the issue URL that has no place to go. but fair, that's a good use case.

@ljharb if we assume that it being a symlink is even evident at all.
Some ides/editors don't distinguish that a file is a symlink; and even those that do, don't necessarily make it -obvious-.
Add insult to injury, these are hidden files so many project views wouldn't show them in a listing.
All that to say: I -had- this exact comment in a symlink in a project recently and had to remove it for compatibility. :)

First, about why you want comments in the .nvmrc file:
git log is horrible for file type discovery. git log .nvmrc is going to show "Initial commit" for 100% of my projects.
If you are explaining what an .nvmrc file is for, wouldn't that be better put in a docs/DEVELOPMENT.md file? Your project readme files should explain what tools and commands are needed for development and how they are used. Having new developers poke around in all the files and to try to figure out what is important and why is not a great onboarding strategy. However, having an intern make notes about project files (even if the notes are "???") and then tasking them with expanding a project's developer docs is a GREAT intern task, @danielrob.
Several people have pointed this out above, so I'd like to reiterate the main reason I have comments in configuration files is to document bugs that force me to use a specific configuration option, .e.g. "Bug X causes Y so we set our config to Z as a work-around. [link to issue]" That kind of information needs to be right next to the configuration or someone (maybe even me!) will "fix it" later not realizing it causes a bug, e.g. "Huh, this file is out-of-date. The value of v14.13.1 should be updated to the latest v14.19.1. Oops. I broke something."
IMO, I think all configuration files should be able to have comments in them. Don't get me started on .json files for configuration.
Lastly, I was looking at the code this PR changes and noticed this line in the original nvm.sh file:
NVM_RC_VERSION="$(command head -n 1 "${NVMRC_PATH}" | command tr -d '\r')" || command printf ''

Only the first line in .nvmrc is ever used to determine the value of NVM_RC_VERSION. That means all the other lines in .nvmrc can be used for comments without any code changes. I tested this by creating a .nvmrc file with an intentionally blank first line:

v14

And I got an error: Warning: empty .nvmrc file found
And when I changed the file to:
v14
# This is a comment
// And so is this
And so is this

The nvm use command reported Found '.nvmrc' with version <14> and ignored all other lines except the first.
So, all we really need to do is make this officially supported in docs; no code changes, afaics.

@ljharb said:

if you do that, it's guaranteed to break in the future, because eventually nvm will support parsing additional content from successive lines.

Agreed.
From my previous comment:

…all we really need to do is make this officially supported in docs… (emphasis added)

Which is why I said we need to decide how to document how comments should work.
Right now, afaics, the entire .nvmrc syntax specification is:

The first line must contain a Node.js version number; see https://github.com/nvm-sh/nvm#nvmrc
Other lines are currently ignored but are reserved for future usage.

To add the official ability to comment the file we need to decide what format comments are allowed to use. And whether we want to reserve the second or third lines for forward compatibility with future features.
FYI, I prefer the # comment syntax as it matches most of the other dot file comment syntaxes.

Several people have pointed this out above, so I'd like to reiterate the main reason I have comments in configuration files is to document bugs that force me to use a specific configuration option, .e.g. "Bug X causes Y so we set our config to Z as a work-around. [link to issue]" That kind of information needs to be right next to the configuration or someone (maybe even me!) will "fix it" later not realizing it causes a bug, e.g. "Huh, this file is out-of-date. The value of v14.13.1 should be updated to the latest v14.19.1. Oops. I broke something."

This is our exact use case
We pin a project to a specific node version and I would like to leave a comment in nvmrc to say why we are using that version (e.g. "don't upgrade to v16 yet because X breaks")
Yes we could put that comment somewhere else in documentation, but this seems like the best place to leave a reminder (so that the person bumping the version will see it)

I created a new issue so we can discuss adding comments to .nvmrc without mixing that discussion up with our opinions about the code in this PR.
#3336 Allow comments in .nvmrc config file


[Wireguard] Dashboard shows part of public key in table of Endpoint

Describe the bug
When using the dashboard for Wireguard, it shows the public keys of the endpoint to identify the endpoints. I would have expected to see the name of the endpoint instead.
To Reproduce
Steps to reproduce the behavior:

Setup WireGuard VPN Service
Add Wireguard to the Dashboard
Save the dashboard
See part of the public key in the list under endpoints

Expected behavior
The actual name for each VPN client in the column of Endpoint
Screenshots

Environment
OPNsense 21.1-amd64
FreeBSD 12.1-RELEASE-p12-HBSD
OpenSSL 1.1.1i 8 Dec 2020
AMD GX-412TC SOC (4 cores)
PC Engines apu4

There is actually already an old issue for this: #1958
And a PR that's been cooking for a while: #1970
So if you want to you can manually edit the php files with the changes from that PR.
(Offtopic, fellow AFOL eh? 😃 )

Thanks,  I’ll take a look.
(Offtopic: yep and proud of it… ;-) Was planning to visit Billund this year, but considering the restrictions do not think it will happen this year… )

On 3 Mar 2021, at 14:38, Sorano<EMAIL_ADDRESS>wrote:
There is actually already an old issue for this: #1958 https://github.com/opnsense/plugins/issues/1958
And a PR that's been cooking for a while: #1970 https://github.com/opnsense/plugins/pull/1970
So if you want to you can manually edit the php files with the changes from that PR.
(Offtopic, fellow AFOL eh? 😃 )
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/opnsense/plugins/issues/2217#issuecomment-789719739, or unsubscribe https://github.com/notifications/unsubscribe-auth/AALAPGUVEX34KVN4EGA6GXDTBY3V3ANCNFSM4XEZBEUQ.

You might also consider using
https://github.com/warner/wireguard-vanity-address
for generating public keys that start with a string that has some meaning to you.


Experimental support for Apple Silicon M1 (darwin_arm64), fixes #2338

The Problem/Issue/Bug:
darwin_arm64 provisional support. This is rough and needs work yet, but here it is.
https://twitter.com/randyfay/status/1337208925289005062
Congrats to @dennisameling for laying all the groundwork for this!
TODO

[ ] Only use gotip for the darwin_arm64 build (figure out how to do it). That's not a very stable way to do things! golang v1.16 will come out in Jan or Feb
[x] Production build in circleci (and then github actions)
[x] Signing and notarizing
[ ] mkcert darwin_arm64 version, may need to be notarized. If darwin_arm64 is done, change install_ddev.sh
[x] Use of golang-build-container is error-prone
[ ] Cleaner recipe for sign and notarize (currently copy-paste)

How this PR Solves The Problem:
Manual Testing Instructions:
Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

@rfay do you know how to install Docker Edge directly? because it now ships as a combined package, and the default Docker won't install to be able to turn on Edge.

@mglaman There is no more edge; they just discontinued it. The Docker M1 Tech Preview link is in (failed) release https://github.com/drud/ddev/releases/tag/v1.17.0-alpha1 - I'll try again in a few minutes. Somehow dropped some lines out of the Makefile.

@mglaman it's ready for you to test, full instructions at https://github.com/drud/ddev/releases/tag/v1.17.0-alpha1

So close!
ddev start
Starting {PROJECT}..
Error response from daemon: Get https://registry-1.docker.io/v2/: x509: certificate has expired or is not yet valid
Failed to start people: exit status 1

Just experiment with docker pull, for example docker pull ubuntu to figure this out. I haven't seen this.  Just tested and saw nothing of the kind. And I don't believe this has anything to do with docker desktop. Is it possible you have  an odd docker client binary laying around, not the one that ships with the tech preview?


OpenSSL 1.1.1a: openssl executable is crashing on AIX

Various (I believe TLS 1.3 related) test cases are failing and return EINVAL, I show only test_comp as an example here:
bash-4.2$ gmake test V=1 TESTS=test_comp
gmake depend && gmake _tests
gmake[1]: Entering directory `/.../openssl-1.1.1a'
gmake[1]: Leaving directory `/.../openssl-1.1.1a'
gmake[1]: Entering directory `/.../openssl-1.1.1a'
( cd test; \
  mkdir -p test-runs; \
  SRCTOP=../. \
  BLDTOP=../.
Proxy started on port [::1]:61382
Server command: ../../util/shlib_wrap.sh ../../apps/openssl s_server -max_protocol TLSv1.3 -no_comp -rev -engine ossltest -ext_cache -accept [::1]:0 -cert ../../apps/server.pem -cert2 ../../apps/server.pem -naccept 1 -cipher AES128-SHA -ciphersuites TLS_AES_128_GCM_SHA256
engine "ossltest" set.
Using default temp DH parameters
ACCEPT [::1]:61383
Server responds on [::1]:61383
unable to connect: Invalid argument
Dubious, test returned 22 (wstat 5632, 0x1600)
No subtests run

Test Summary Report
-------------------
../test/recipes/70-test_comp.t (Wstat: 5632 Tests: 0 Failed: 0)
  Non-zero exit status: 22
  Parse errors: No plan found in TAP output
Files=1, Tests=0,  1 wallclock secs ( 0.01 usr  0.00 sys +  0.07 cusr  0.01 csys =  0.09 CPU)
Result: FAIL
gmake[1]: *** [_tests] Error 1
gmake[1]: Leaving directory `/.../openssl-1.1.1a'
gmake: *** [tests] Error 2

Digging a bit deeper a core-dump appears in test/test-runs which is from apps/openssl. The stack trace from dbx:
bash-4.2$ dbx -p "../../util/.."="." apps/openssl test/test-runs/core
Type 'help' for help.
[using memory image in test/test-runs/core]
reading symbolic information ...

Quit in naccept at 0x90000000010d004 ($t1)
0x90000000010d004 (naccept+0x284) e8410028             ld   r2,0x28(r1)
(dbx) where
naccept(??, ??, ??) at 0x90000000010d004
BIO_accept_ex(accept_sock = 3, addr_ = 0x00000001100941b0, options = 0), line 289 in "b_sock2.c"
unnamed block in do_server(accept_sock = 0x000000011000a368, host = "::1", port = "0", family = 0, type = 1, protocol = 0, cb = 0x0000000110014a58, context = (nil), naccept = 1, bio_s_out = 0x00000001100631b0), line 337 in "s_socket.c"
do_server(accept_sock = 0x000000011000a368, host = "::1", port = "0", family = 0, type = 1, protocol = 0, cb = 0x0000000110014a58, context = (nil), naccept = 1, bio_s_out = 0x00000001100631b0), line 337 in "s_socket.c"
s_server_main(argc = 0, argv = 0x0ffffffffffff5c8), line 2143 in "s_server.c"
do_cmd(prog = 0x000000011005edb0, argc = 20, argv = 0x0ffffffffffff528), line 564 in "openssl.c"
main(argc = 20, argv = 0x0ffffffffffff528), line 183 in "openssl.c"

Local variables one level up:
(dbx) dump
BIO_accept_ex(accept_sock = 3, addr_ = 0x00000001100941b0, options = 0), line 289 in "b_sock2.c"
locaddr = [union]
accepted_sock = 0
addr = 0x00000001100941b0
len = 1028
__func__ = "BIO_accept_ex"

Hm ... something bugs me about the value of len. It is implemented as len = sizeof(*addr), but isn't the size of sockaddr requested? I'll check that tomorrow ...

len is the size of the BIO_ADDR. You say to accept() what the maximum size is, and accept will write the real size in it. It's this structure:
union bio_addr_st {
    struct sockaddr sa;
# ifdef AF_INET6
    struct sockaddr_in6 s_in6;
# endif
    struct sockaddr_in s_in;
# ifdef AF_UNIX
    struct sockaddr_un s_un;
# endif
};

Where on Linux the largest one is:
#define UNIX_PATH_MAX   108

struct sockaddr_un {
        __kernel_sa_family_t sun_family; /* AF_UNIX */
        char sun_path[UNIX_PATH_MAX];   /* pathname */
};

I guess it's possible that on AIX up to 1024 chars are supported.
Anyway, it's hard to see what we can be doing wrong that is causing a crash there.

The sizes: sa = s_in = 16, s_in6 = 28 and s_un = 1025. But this doesn't change anything. Checking aliasing rules (-qalias=ansi -qinfo=als), next.

-qalias=ansi didn't change anything.
Editing the aix64-cc build rule to issue "-O0 -qalias=ansi -qinfo=als" leaves me with roughly about 1000 messages like:
        cc  -I. -Icrypto/include -Iinclude -qpic -q64 -qmaxmem=16384 -qro -qroconst -qthreaded -O0 -qalias=ansi -qinfo=als -DB_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_A
SM -DSHA512_ASM -DKECCAK1600_ASM -DAES_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -D_THREAD_SAFE -DNDEBUG   -c
-o crypto/x509v3/v3_ncons.o crypto/x509v3/v3_ncons.c
"crypto/x509v3/v3_ncons.c", line 524.11: 1506-1393 (I) Dereference may not conform to the current aliasing rules.
"crypto/x509v3/v3_ncons.c", line 524.11: 1506-1394 (I) The dereferenced expression has type "struct X509_name_st". "nm" may point to "stmp" which has incompatible type "struct asn1_string_st".
"crypto/x509v3/v3_ncons.c", line 524.11: 1506-1395 (I) Check pointer assignment at line 406 column 21 of crypto/x509v3/v3_ncons.c.
"crypto/x509v3/v3_ncons.c", line 524.11: 1506-1395 (I) Check pointer assignment at line 430 column 21 of crypto/x509v3/v3_ncons.c.
"crypto/x509v3/v3_ncons.c", line 524.11: 1506-1395 (I) Check pointer assignment at line 459 column 28 of crypto/x509v3/v3_ncons.c.
"crypto/x509v3/v3_ncons.c", line 524.11: 1506-1395 (I) Check pointer assignment at line 494 column 21 of crypto/x509v3/v3_ncons.c.
        /usr/lpp/X11/bin/makedepend -f- -Y --  -I. -Icrypto/include -Iinclude -qpic -q64 -qmaxmem=16384 -qro -qroconst -qthreaded -O0 -qalias=ansi -qinfo=als -DB_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSS
L_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DAES_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib/engines-1
.1\"" -D_THREAD_SAFE -DNDEBUG  -- crypto/x509v3/v3_ncons.c 2>/dev/null  > crypto/x509v3/v3_ncons.d

The whole thing isn't complete as the build later breaks with ...
        cc  -I. -Iinclude -qpic -q64 -qmaxmem=16384 -qro -qroconst -qthreaded -O0 -qalias=ansi -qinfo=als -DB_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_BN_ASM_MONT -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -
DKECCAK1600_ASM -DAES_ASM -DVPAES_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" -D_THREAD_SAFE -DNDEBUG   -c -o ssl/record/ssl
3_record.o ssl/record/ssl3_record.c
/opt/IBM/xlC/13.1.3/bin/.orig/cc: 1501-230 (S) Internal compiler error; please contact your Service Representative. For more information visit:
http://www.ibm.com/support/[...]
make: The error code from the last command is 251.

Stop.
make: 1254-004 The error code from the last command is 2.

Stop.

I'll have a closer look tomorrow ...

The proxy is designed as a man-in-the-middle between s_server and s_client. The ossltest engine disables all things like MAC checking so that we can complete a full handshake even though the proxy fiddles with the messages being passed between the two peers. Both sides need to use the ossltest engine, otherwise you'll never get a complete handshake.
The whole point of the TLSProxy based tests is to make changes to the messages (perhaps making them invalid in some way) in order to reach codepaths that you can't normally reach. It is entirely possible that the crashes you are experiencing are highly test specific.
Are all TLSProxy tests failing? Or just some of them?

Hm ... Nope, wrong path. SIGQUIT is intentionally raised in Proxy.pm->connect_to_server as $IP_factory returns "Invalid Argument" ... checking Perl installation ...

IO::Socket::INET6->new() needs Domain => AF_INET6 specified. Making a complete test suite run to verify ...

That's it. Unfortunately IO::Socket::IP has this parameter as Family.
Do I understand it correctly, that if $have_IPv6 is set, the Proxy module is operating in AF_INET6 mode anyway? In this case it could just be added to the $IP_factory definition:
        $IP_factory = sub { IO::Socket::INET6->new(Domain => AF_INET6, @_); };

... and leave all other code alone.


Update scripts on protocol contracts

Summary

Add deployment scripts
Update references

@andresaiello couldn't do "Suggest changes" on GH, so I pushed changes to fix imports.

I'm getting the following when trying to deploy:
npx hardhat run ./scripts/deployments/core/deploy.ts --network athens

Getting tss address from athens: athens.
Getting tssUpdater address from athens: athens.
Error: resolver or addr is not configured for ENS name (argument="name", value="", code=INVALID_ARGUMENT, version=contracts/5.6.2)
    at Logger.makeError (/Users/fadeev/github.com/zeta-chain/protocol-contracts/node_modules/@ethersproject/logger/src.ts/index.ts:269:28)
    at Logger.throwError (/Users/fadeev/github.com/zeta-chain/protocol-contracts/node_modules/@ethersproject/logger/src.ts/index.ts:281:20)
    at Logger.throwArgumentError (/Users/fadeev/github.com/zeta-chain/protocol-contracts/node_modules/@ethersproject/logger/src.ts/index.ts:285:21)
    at /Users/fadeev/github.com/zeta-chain/protocol-contracts/node_modules/@ethersproject/contracts/src.ts/index.ts:140:16
    at step (/Users/fadeev/github.com/zeta-chain/protocol-contracts/node_modules/@ethersproject/contracts/lib/index.js:48:23)
    at Object.next (/Users/fadeev/github.com/zeta-chain/protocol-contracts/node_modules/@ethersproject/contracts/lib/index.js:29:53)
    at fulfilled (/Users/fadeev/github.com/zeta-chain/protocol-contracts/node_modules/@ethersproject/contracts/lib/index.js:20:58) {
  reason: 'resolver or addr is not configured for ENS name',
  code: 'INVALID_ARGUMENT',
  argument: 'name',
  value: ''
}

I'm sure it's just me doing something wrong. I'd love to document the process (and just generally the repo) to make it accessible to external contributors, but I might need some guidance.

I'm getting:
npx hardhat run scripts/deployments/core/deploy.ts --network polygon-mumbai

Deploying ZetaConnector to polygon-mumbai
Getting zetaToken address from athens: polygon-mumbai.
Getting tss address from athens: polygon-mumbai.
Getting tssUpdater address from athens: polygon-mumbai.
Getting tssUpdater address from athens: polygon-mumbai.
Getting tss address from athens: polygon-mumbai.
Getting tssUpdater address from athens: polygon-mumbai.
Getting tss address from athens: polygon-mumbai.
Getting tssUpdater address from athens: polygon-mumbai.
Getting zetaToken address from athens: polygon-mumbai.
Updating
Getting tss address from athens: polygon-mumbai.
Getting connector address from athens: polygon-mumbai.
ProviderError: INTERNAL_ERROR: could not replace existing tx
    at HttpProvider.request (/Users/fadeev/github.com/zeta-chain/protocol-contracts/node_modules/hardhat/src/internal/core/providers/http.ts:88:21)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async EthersProviderWrapper.send (/Users/fadeev/github.com/zeta-chain/protocol-contracts/node_modules/@nomiclabs/hardhat-ethers/src/internal/ethers-provider-wrapper.ts:13:20)


Multiple pods opened in Iframe

Thanks for your great open source service in data science community.
I have multiple shiny apps running in shinyproxy framework. I am trying to embed shinyproxy URL in the other static app (run by IT team) via Iframe. When one user visits the link it opens more than 10 containers (should be ideally 2 one for shinyproxy and shiny app). I tested on both docker compose and kubernete based deployment. In kubernete it opens more than 10 pods. This issue exists in both the deployments. It also returns 404 error of JS and CSS resources.
I tried this solution but didn't work -
https://github.com/openanalytics/shinyproxy/issues/142
I also tried this in ingress but no success -
https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/websocket
Mostly errors are
"Refused to apply style from because its MIME type ('text/html') is not a supported stylesheet MIME type, and strict MIME checking is enabled"

Hi
I think the issue is that every request in the iframe (e.g. for css, js, .. files) ShinyProxy is starting a new container. This could be caused because ShinyProxy is identifying every request as a different user. I suspect some isolation or misconfiguration of cookies could cause this. You could try the following to debug the issue:

open the network tab of your browser (a.k.a developer tools)
open the application
check which requests are preformed and have a look at which cookies are sent. If every request has a different value for the session cookie, this is the cause of the issue.
check the console tab for any error or warnings relating to cookies (e.g. sameSite policy, secure flag etc).

Hi @markwsac
After thinking about this a bit more, I think I know the cause of this issue. ShinyProxy 2.5.0 sends a session cookie to the browser without a same site cookie policy. Modern browsers are blocking these kind of cookies in a third-party context. (to be precise, browsers are treating them as cookies with a Lax policy). Therefore ShinyProxy is unable to identify a session for each of the requests and thus starts a new container for each request.
The solution is to change the same site cookie policy to None and to enable secure cookies. Unfortunately it is not yet possible to change this policy in ShinyProxy 2.5.0 (unless you are using Redis for session persistence). The good news is that in the next version of ShinyProxy this will be possible.
You can already start using a snapshot of the next release by using the docker container  (use 2.6.0-SNAPSHOT-20210730.120255 tag)or the jar. You then need to use the following config:
server:
   secure-cookies: true

proxy:
  same-site-cookie: None

Note that this will only work if you access ShinyProxy using a HTTPS connection. Otherwise some browsers will block the cookies again.


[labs/ssr] Can't render light DOM custom elements server side

Description
I'm trying to SSR custom elements that render to light DOM. Everything seems to work correctly when rendering to shadow DOM.
Steps to Reproduce

I'm not using LitElement as my base class. I use https://github.com/webtides/element-js/. I only use lit-html for rendering. And I do render to light DOM by default.

I'm using the following versions:

"@lit-labs/ssr": "1.0.0-rc.1",
"lit-html": "^2.0.0-rc.3",

import {render} from<EMAIL_ADDRESS>import {TemplateElement} from '@webtides/element-js';
import {html} from "lit-html";

class MyRenderer extends ElementRenderer {/*...*/}

class LightElement extends TemplateElement {
    template() {
        return html`

Parent light DOM element

            <nested-light-element></nested-light-element>
        `;
    }
}
customElements.define('light-element', LightElement);

class NestedLightElement extends TemplateElement {
    template() {
        return html`

Nested light DOM element

        `;
    }
}
customElements.define('nested-light-element', NestedLightElement);

const template = html`
   <light-element></light-element>
`;

render(template, {
    elementRenderers: [MyRenderer],
    customElementInstanceStack: [],
    customElementHostStack: [],
})

Everything seems to work fine at first. Both elements (light-element and nested-light-element) are rendered on the server. Both elements get hydraded correctly. I can update the nested element (nested-light-element) by changing properties or attributes and it will re-render. But when I update the parent element (light-element) by changing properties or attributes it will destroy the nested element's template and it won't recover from that. The parent element will re-render just fine but the nested element can't ever render again.
When I opt into rendering to shadow DOM instead, everything works as expected.
From what I can tell by looking at the source (@lit-labs/ssr/lib/render-lit-html.js:300), it will always assume shadow DOM. There is no TemplateOpcode for light DOM.
Looking further in the source (@lit-labs/ssr/lib/render-lit-html.js:498), it will always wrap the template with a declarative shadow root template element. There seems to be no case for rendering light DOM server side here.
Also the renderLight method in my ElementRenderer never gets called. Wouldn't it make sense to let the ElementRenderer decide whether to render to light DOM or to shadow DOM?

Expected Results

I can SSR nested custom elements that render to light DOM.
Actual Results

Nested custom element's templates break when rendered to light DOM

You're right, currently the LitElement ElementRenderer only supports rendering to shadow root; we haven't made a pattern for render-lit-html render LitElements that render directly to their light DOM.
While we see users find utility in rendering an element's template to its light DOM (i.e. in LitElement, by overriding createRenderRoot), this is not a generally interoperable pattern because it leaves undefined what happens with children that are rendered by the element's owner to its light DOM (e.g. do they stay? are they overwritten? what order do they go in w.r.t. the DOM the CE renders into itself? what happens when additional nodes are added to the light DOM after the initial render?).

<some-host-element>

outer scope

rendered by some-host-element

</some-host-element>

The design of web components (the combination of both custom elements and shadow DOM) make the scope of node ownership explicit and interoperable:

<some-host-element>

outer scope

  #shadow-root

rendered by some-host-element

    <slot></slot>
  #/shadow-root
</some-host-element>

We've speculatively added renderLight to the ElementRenderer interface to explore a better pattern for "light DOM rendering" than having elements render directly to their light DOM. For Lit, it goes along with the renderLight directive found in @lit-labs/ssr-client.  We need to add better examples and documentation to help explain how we see it used and to get feedback on it.
The design of renderLight helps to avoid ambiguity around the ownership of elements that comes along with light-DOM rendering. The some-host-element no longer autonomously renders nodes to the outer scope which is technically not in its scope of ownership; its renderLight template is only rendered when the owner of some-host-element uses the renderLight directive to tell Lit where it wants the light DOM children rendered:
html`

  <some-host-element>

outer scope

    ${renderLight()}
</some-host-element>

In this way, the ownership is clear, in that the outer scope always controls what gets rendered to its scope; renderLight becomes an explicit delegation mechanism from the outer scope to the inner scope, which removes the ambiguity. Effectively, the outer scope "asks" the custom element to render some child nodes to a spot of the outer scope's choosing. While this affects how users use the custom element (it's no longer fully autonomous), we think this is a better architectural approach that does not violate principles of ownership and source-of-truth in the DOM tree.
All that said, while we'd much rather fully embrace the interoperability provided by Shadow DOM and design light DOM rendering patterns on top of that, we could revisit whether there could be an alternate signal to automatically call renderLight on the ElementRenderer rather than require the outer scope to always use a signal like the renderLight directive.


Don't work

Why don't work???
http://joxi.ru/8AnqkYVUqwKy12

Did you add many keys?
I have same problem, but when I deleted some keys from top, I was can see some another keys.
I think this phenomenon is a bug.

It's stopped working for me as well inside of chrome.  Randomly will display all of the passwords as I had them before, but now when re-pasting the exported source text that I'd saved earlier (I backup each time I add new accounts), it simply lists the account name/site as it should, but instead of showing the 2FA code, it displays a bunch of square dots.
Please let me know if there is some way to fix this, much appreciated!


fix: enable save & continue button after photo deletion

The type of this PR is: BugFix
This PR resolves SWA-287
Description
This PR fixes the problem that after deleting a photo in the Upload Photos step, the Save & Continue button becomes disabled.
Videos
https://user-images.githubusercontent.com/42584148/156786411-c4af53d4-f78f-4208-b63d-7cd285a287e0.mp4
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Warnings

:warning:

❌ An error occurred while validating your changelog, please make sure you provided a valid changelog.

  Generated by :no_entry_sign: dangerJS against 49629e567c56baa545a340e151210cce9fad47cc


Establish user access levels

Currently, the only security determination is logged on or not. Establish the following security levels; within this list, each one can also perform the tasks of those above it.

[x] Establish user levels (described below)
[x] Place restrictions on existing functionality according to those levels. UI elements that are not allowed should not be displayed (i.e., unless the user can delete a post, the "Delete" link should not be shown). The server must also verify this access for each request.
[x] Provide a user maintenance page, where WebLogAdmins and Administrators can assign their level or below to other users of the current web log
[x] When creating a web log, if this is the first one, assign the user Administrator permissions; otherwise, assign them WebLogAdmin permissions
[x] Provide a CLI upgrade-user option that will take a URL base and an e-mail address, and promote that user to Administrator status

Access Levels

Author can create new posts / pages and edit posts / pages they authored.
Editor can edit posts / pages they did not author, but may not delete them.
WebLogAdmin can delete posts / pages, as well as manage all web log settings (the current "logged on" level)
Administrator will be able to manage themes (#20), and may have other installation-wide controls as they are developed.

Fixed in beta 5