Mobile nav bug fixes

Buggy behavior in the mobile menu (FF) https://github.com/threlte/threlte/issues/545
I changed default behaviour of ViewTransitions to fallback to "none" when they are not supported. There are two other options but I'm more confident in only having any ViewTransitions at all if they are fully supported (chrome) or none at all.
I tested for a little bit and it seemed to have worked on my Firefox. Can you let me know if the issue is also gone for you @ixxie ?
Fix mobile layout to display Search on top. https://github.com/threlte/threlte/issues/554
Search and menu were both using z-50 as we initially assumed that menu will be always on top.

Yes, that seems to have fixed the issues in FF mobile! Well done!


Make JCE provider configurable

Purpose
Resolves - https://github.com/wso2/product-is/issues/15428
Merge this PR after merging https://github.com/wso2/carbon-kernel/pull/3497

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4121433195

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4121433195
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4131033991

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4131033991
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4131981025

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4131981025
Status: failure

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4136356723
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4140544799

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4140544799
Status: success

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4220538411

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4220538411
Status: success


climate error

Эта ошибка возникла в кастомной интеграции.
Logger: homeassistant.loader
Source: custom_components/xiaomi_gateway3/climate.py:39
Integration: Xiaomi Gateway 3 (documentation, issues)
First occurred: 23:25:41 (2 occurrences)
Last logged: 23:53:20
Unexpected exception importing platform custom_components.xiaomi_gateway3.climate
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/loader.py", line 744, in get_platform
cache[full_name] = self._import_platform(platform_name)
File "/usr/src/homeassistant/homeassistant/loader.py", line 761, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
File "/usr/local/lib/python3.10/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1050, in _gcd_import
File "", line 1027, in _find_and_load
File "", line 1006, in _find_and_load_unlocked
File "", line 688, in _load_unlocked
File "", line 883, in exec_module
File "", line 241, in _call_with_frames_removed
File "/config/custom_components/xiaomi_gateway3/climate.py", line 32, in
class XiaomiClimate(XEntity, ClimateEntity):
File "/config/custom_components/xiaomi_gateway3/climate.py", line 39, in XiaomiClimate
_attr_temperature_unit = TEMP_CELSIUS
NameError: name 'TEMP_CELSIUS' is not defined

This error appeared after updating the Home Assistant Core to version 2023.1.0.

This error appeared after updating the Home Assistant Core to version 2023.1.0.
Here is the second message in the logs:
Logger: homeassistant.setup
Source: setup.py:340
First occurred: 5 января 2023 г., 23:25:41 (2 occurrences)
Last logged: 5 января 2023 г., 23:53:20
Unable to prepare setup for platform xiaomi_gateway3.climate: Platform not found (Exception importing custom_components.xiaomi_gateway3.climate).

This error appeared after updating the Home Assistant Core to version 2023.1.0.
Here is the second message in the logs:
Logger: homeassistant.setup
Source: setup.py:340
First occurred: 5 января 2023 г., 23:25:41 (2 occurrences)
Last logged: 5 января 2023 г., 23:53:20
Unable to prepare setup for platform xiaomi_gateway3.climate: Platform not found (Exception importing custom_components.xiaomi_gateway3.climate).

full error log:
Unable to prepare setup for platform xiaomi_gateway3.climate: Platform not found (Exception importing custom_components.xiaomi_gateway3.climate).

Unexpected exception importing platform custom_components.xiaomi_gateway3.climate

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/loader.py", line 744, in get_platform
    cache[full_name] = self._import_platform(platform_name)
  File "/usr/src/homeassistant/homeassistant/loader.py", line 761, in _import_platform
    return importlib.import_module(f"{self.pkg_path}.{platform_name}")
  File "/usr/local/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/config/custom_components/xiaomi_gateway3/climate.py", line 32, in <module>
    class XiaomiClimate(XEntity, ClimateEntity):
  File "/config/custom_components/xiaomi_gateway3/climate.py", line 39, in XiaomiClimate
    _attr_temperature_unit = TEMP_CELSIUS
NameError: name 'TEMP_CELSIUS' is not defined

duplicate of #899


Failed to install search-guard incompatible with ES 2.2

-> Installing com.floragunn/search-guard-2/2.2.0...
Trying https://download.elastic.co/com.floragunn/search-guard-2/search-guard-2-2.2.0.zip ...
Trying https://search.maven.org/remotecontent?filepath=com/floragunn/search-guard-2/2.2.0/search-guard-2-2.2.0.zip ...
Trying https://oss.sonatype.org/service/local/repositories/releases/content/com/floragunn/search-guard-2/2.2.0/search-guard-2-2.2.0.zip ...
Trying https://github.com/com.floragunn/search-guard-2/archive/2.2.0.zip ...
Trying https://github.com/com.floragunn/search-guard-2/archive/master.zip ...
ERROR: failed to download out of all possible locations..., use --verbose to get detailed information
Using ES: 2.2
"version" : {
"number" : "2.2.0"
}

We are currently in beta status, there is no final release yet. The most recent beta is for elasticsearch 2.3.1 only

sudo bin/plugin install com.floragunn/search-guard-ssl/<IP_ADDRESS>.1
sudo bin/plugin install com.floragunn/search-guard-2/<IP_ADDRESS>-beta1


Add ocamllsp to list of lsp servers

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: rgrinberg sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I would certainly recommend the lsp server that we maintain at OCaml Labs. However, it’s probably better if @freebroccolo decides on whether his server should be removed from the list.
On Mar 3, 2020, 4:54 PM +0000, Remy Suen<EMAIL_ADDRESS>wrote:

@rcjsuen commented on this pull request.
In _implementors/servers.md:

| OCaml/Reason | freebroccolo | ocaml-language-server | TypeScript |

+| OCaml/Reason | OCaml Labs | ocamllsp | OCaml |
Should the entry above this be deleted? 🤔
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

I will merge the PR then.


File not found: trying to export Model.bim from command line

What are you trying to achieve?
I am trying to export the Model.bim from a local instance of Power BI Desktop running using Tabular Editor on the command line
cmd /C ""C:\Program Files (x86)\Tabular Editor\TabularEditor.exe" "localhost:59430\bfa61830-1b97-4dcb-b7b2-d0c34303f77f" -B output "C:\temp""
I am getting an error
File not found: localhost:59430\bfa61830-1b97-4dcb-b7b2-d0c34303f77f
Is it possible to connect to the local Power BI Desktop tabular instance and export the Model.bim from the command line?

I used Procmon to see how your external tool is doing it and figured out the correct syntax, thanks!
"C:\Program Files (x86)\Tabular Editor\TabularEditor.exe" "localhost:59430" "bfa61830-1b97-4dcb-b7b2-d0c34303f77f" -B "C:\Users\XXXXXX\Model.bim"


numpy pinned to an old version

The setup.py file pins the version of numpy by having the requirement line:
"numpy<1.21"

The current version of numpy is 1.25.2. As a result attempting to install pygraphblas un-installs the current version of numpy.
Worse, the Numpy team no longer make binary wheels available for pre-1.21 numpy versions. As a result not only will the current version be removed but the old version will need to be built from source in many situation. Building numpy from source is both slow and prone to failures because of its extensive dependencies.
It would be very helpful if pygraphblas could officially support a current version of numpy so that it can be installed reliably without having to resort to manual dependency installation.

@michelp @marci543 could you guys remove this numpy<1.21 pin and debug the tests?
just needing to speed up nx.pagerank for a clinical medical project and thought I could try this.
I cloned the repo and removed <1.21 and pip install -U -e . did work, however "pytest tests/did not work.py.test -n 2 tests/` failed the same way, implying these tests can be parallelized.

Looks like most of the issue is with suitesparse_graphblas having evolved a bit, the numpy upgrade seems OK or at least doesn't cause the issues..
Proposal:

[x] add Makefile with "debug" and "debug-command" and "test"
[x] add nodemon.json to rerun "debug-command" when we change code
[ ] debug the code until it passes the old tests <-- need maintainer for this

https://github.com/Graphegon/pygraphblas/pull/106 Created!


cmd/go: go mod download should follow symlinks

When constructing a module zip, follow symlinks and include the linked files.
One application: nested modules can symlink to the LICENSE file at repo root instead of copying it, to avoid skew when the root file is modified.
Example: https://github.com/apache/arrow, which isn't exclusively Go code, has a module at go/arrow. The license at repo root is intended to cover the module, but since it isn't in the module tree, it's not in the zip, so the module appears to have no license. The maintainer would like to symlink the license at repo root (apache/arrow#7351).

Unfortunately, we can't make any changes to the set of files that get packed into a zip file for a given version. That would change the hashes of the resulting zip files. Even if we gated this on the go version in go.mod, older versions of the go command would disagree with newer versions.
For reference, before #27093, the go command followed symbolic links to files and directories. They were stored and extracted as regular files and directories (symbolic links can't be reliably represented in the zip format, and they can't be extracted on all platforms). This caused problems for tests, so it was decided to ignore them. The fix for that changed hashes between 1.11.3 and 1.11.4, which haunted us for a long time.
About LICENSE: the go command will pull in a file named LICENSE from the repository root directory when building the zip for any module in a subdirectory. Unfortunately for github.com/apache/arrow, their file is named LICENSE.txt, so it doesn't get pulled in. They could either rename the file to LICENSE or copy LICENSE.txt to the go/arrow directory.

@jayconrod, would it be possible for go to recognize and package LICENSE.txt (or LICENSE*) from the repository root, too? In this case the case of #39318, the Arrow maintainers were quick help make pkg.go.dev work, but more flexibility would help other projects.
As a very rough metric, I counted ~3000 Github repositories containing Go code that use LICENSE.txt (vs ~80000 with LICENSE) using Bigquery. Or ~2000 (vs ~61000) with Go listed as their first language, in case that means most lines of code (also Bigquery).

I won't say it's impossible, but it's very difficult to make any change to the set of files that get included in a module .zip file.
If different versions of Go choose different sets of files, they won't generate the same hashes, so when a module is downloaded by an old version of the go command it will look like someone has tampered with the module after it was released. That could be somewhat mitigated by gating the change on a new go version in go.mod. We'd have to choose a version far enough in the future (at least a year, probably more) that by the time it was current, versions of Go that don't support this are no longer supported.
It's also hard to decide what files to actually include: LICENSE, LICENSE.txt, sure. How about COPYING.html? copyright-license.pdf? pkg.go.dev has a list of names they use, and we'd probably use the same list. Not sure what they do if there are multiple matching files.

Not sure what they do if there are multiple matching files.

We remember all of them. In this case, the proxy would copy all of them.

Just to close the loop on this: @bcmills, @matloob, and I discussed this last week, and we decided not to change anything here. Some mitigations are possible, but fundamentally, this would cause different versions of the go command to produce different sums for the same module, which would cause security errors. The cost of that outweighs the benefit.


ci: update MAINTAINERS.yaml based on CODEOWNERS changes

Description
This PR updates the MAINTAINERS.yaml file based on the changes made in the CODEOWNERS file. The workflow takes the repository name as input and adds it to the MAINTAINERS.yaml file.
When a new code owner is added, a corresponding maintainer object is created in the MAINTAINERS.yaml file with the repository name and the Twitter username of the code owner added to the object. It fetches the Twitter username using the GitHub API.
Similarly, when a code owner is removed, the corresponding maintainer object is removed from the MAINTAINERS.yaml file. The removal process checks if the maintainer has any other repositories before removing them from the MAINTAINERS.yaml file.
I have tested this workflow on my testRepo by adding a new code owner, and the MAINTAINERS.yaml file was updated with the new code owner object and repository name. Here are the logs from the workflow: https://github.com/14Richa/testRepo/actions/runs/5563061192/jobs/10161768757
Similarly, when a code owner is removed MAINTAINERS.yaml file was updated accordingly with the maintainer object removed from the file. Here are the logs from the workflow: https://github.com/14Richa/testRepo/actions/runs/5529277200/jobs/10087118152

/rtm


DCIR setup is removed after cutout and cannot be added.

appedb = Edb(edbpath="Galileo.aedb", edbversion="2021.2")
settings = appedb.core_siwave.get_siwave_dc_setup_template()
appedb.core_siwave.add_siwave_dc_analysis()
appedb.save_edb_as("full_board.aedb")
Save the full board with dc analysis. Everything is fine here.
appedb.create_cutout(["A0_N", "A0_P"], ["GND"])
appedb.save_edb_as("cutout.aedb")
After cutout, the dc analysis is gone.
appedb.core_siwave.add_siwave_dc_analysis()
appedb.save_edb_as("cut_out_add_DC_again.aedb")
DC analysis cannot be added in the cutout design

@ring630 @MaxJPRey Fixed in #704

@maxcapodi78 I confirm it is fixed.


HAWKULAR-49  - prevent timeout on add()

HAWKULAR-49  Do not start a ping on add, as this may block the add()
method for too long. Instead ping every 20 seconds.

The 20 seconds pings will demo much better than 1 minute pings.


refactor(pluginInfo): Update JSON fields and entries

Replace former fields and dummy data entries with correct fields and information respectively.
refs #359, resolves #329

@Asylcreek Good morning, please review.


Use DataPipe not IterDataPipe as the type hints for DataLoader2 related code

🐛 Describe the bug
There are a couple of places that DataLoader2 uses IterDataPipe as the type hint (here, here, etc.)
We should add a type called DataPipe = Union[IterDataPipe, MapDataPipe] as the type hint, and use this new type hint for all functions.
Versions
main branch

Let's not label it as the good first issue.

Need to be very careful. As for example here https://github.com/pytorch/data/blob/12cfaf8899b1337981cd4edf9deef127f925f1bd/torchdata/dataloader2/reading_service.py#L17 is should be IterDataPipe as any MapDataPipe supposed to be wrapped to sampler before passing to DataLoader.

Closing as it has been solved


Initial plumbing for metrics.

Reviewers: Looking for comments on the flow/structure. There is a bunch more to do. But, wanted to ensure that the plumbing and the approach looks okay before proceeding further.
This implements

metrics received from participant.
callback to room.
room distributes it to all other participants (excluding the sending participant).
other participants forward to client.
counting metrics bytes in data channel stats

TODO:

recording/processing/batching
should recording/processing/batching happen on publisher side or subscriber side?
should metrics be echoed back to publisher?
grants to publish/subscribe metrics.

@reviewers, marking this ready for review. This will forward metrics as-is to participants with CanSubscribeMetrics permissions. Please let me know what you think about METRICS-TODO-QUESTIONS part, especially the part about destination identities. Do we need that?
I think we can ignore the batching part for now. We can discuss that when figuring out sending to analytics for offline processing.
Another thing is time stamps. Want to get this pipeline flowing first before doing more work. Would really like to understand what real time clients are going to do with this and figure out how to deal with time stamps.


DF and SparseERI for UHF

Added functions for handling DF and Sparse ERI's. Added tests for both.

Codecov Report

Merging #98 (a64f757) into master (7734183) will increase coverage by 0.86%.
The diff coverage is 99.03%.

@@            Coverage Diff             @@
##           master      #98      +/-   ##
==========================================
+ Coverage   71.57%   72.44%   +0.86%
==========================================
  Files          36       36
  Lines        2850     2943      +93
==========================================
+ Hits         2040     2132      +92
- Misses        810      811       +1

Impacted Files
Coverage Δ

src/Methods/HartreeFock/HartreeFock.jl
91.66% <ø> (ø)

src/Methods/HartreeFock/UHF/UHFHelper.jl
98.40% <99.00%> (+1.52%)
:arrow_up:

src/Methods/HartreeFock/UHF/UHFa.jl
97.72% <100.00%> (ø)

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 7734183...a64f757. Read the comment docs.

I just saw this. I will go through it carefully, but it is looking good!


SwiftPM support

SwiftPM is Swift's official package manager. In the near future it will replace Carthage and CocoaPods.
Here some articles about SwiftPM:

An Introduction to the Swift Package Manager
Swift Dependency Management for iOS
Getting Started with Swift Package Manager (SwiftPM)
Swift.org: Package Manager

When your component is compatible with SwiftPM add on your README.md  badge on top and add a section for the installation with SwiftPM.

Swift PM does not yet support iOS projects. Closing this for now.


HTTP vs. HTTPS namespace on the SHACL playground

It seems the examples of the SHACL playground use a shape graph with an HTTPS URI for the sh: prefix while the W3C Rec mentions an HTTP URI.
I noticed that because when I am copy-pasting my own shapes, none gets registered after clicking 'Update'.

Oops, this must be a recent regression. Will look.

Has been fixed in the meantime. Thanks for the report!


Add navbar styling, template pages for games, setup admin page, added requirements.txt, updated README

Description
I updated the navbar to look better, but I still need to add things such as images and better styling based on the desired appearance. Made templates for each game in the user study and added them to the navbar. Set up the main page and styling to be ready for database functionality. Created a requirements.txt file for installing needed packages and updated the README.md file accordingly.
Requirements
The website should be run from a new virtual environment using the requirements.txt file to ensure all dependencies are included. The website should be tested to ensure the navbar is displayed correctly and goes to the right page. The admin page should be displayed correctly and allow users to select files in the table, but not be able to use the buttons as intended yet.
Issues Referenced

Fixes #4

Documentation update
Link to a change in documentation (if any)
Notes for Reviewer
File functions will be added for button functionality on the admin page as well as authenticating the user once the database is implemented. This will also include displaying files in the database rather than temporary placeholders.
Testing

Follow the steps in the README.md located in the website folder to ensure it is accurate and can properly display the website.
Make sure local database has at least one user, admin user should have user_id == 1
Login as the admin user
Click on each navbar item. The current tab should have an outline and if the mouse hovers over a tab another outline should be displayed. Ensure that each webpage displays correctly.
Click the link label "Admin"
Click on one of the "Select" boxes within the table. The selected box should display a checkmark.
Logout and go to http://<IP_ADDRESS>:5000/admin

Results

A new user should be able to follow the README.md and be able to launch the website.
Each page should display correctly when using the navbar.
When logged out the admin tab on navbar should be hidden
When logged out and trying to access the admin page by the URL you should be redirected to the landing page and a message should appear at the top of the screen.

Feature Tests
TODO
Checklist to allow merge

[ ] All dependent repositories used were on branch master
Software

[ ] Get approval from the reviewer
[ ] Passed testing on Windows

Screenshots:

So idk why but I am having issues running the application. I made a new environment and ran  pip install -r requirements.txt. Everything installed correctly but I get an error that says
from db_connection import DatabaseConnection
File "C:\Users\magni\OneDrive\Documents\school\CS\CS 425 (Senior Projects)\SP website\EmotiGame\website\db_connection.py", line 5, in
from dotenv import load_dotenv
ModuleNotFoundError: No module named 'dotenv'
This library is in the requirements file so I'm not sure why I'm getting this and I don't know if I missed a step.

There was a small typo in the README, not sure if you copy and pasted straight from there. I updated the README to fix this. It is also possible to check the environment file by doing:
cd /bin
ls
then it should display all the libraries installed.
Another thing was to make sure the .env file with passwords is in the website folder. I was having issues when it was database.env

Make sure that when you are writing out the testing steps you don't say make sure you do this. If I am creating an admin user you should tell me how to do that or set it up. I know it's nitpicky, but it's what Sean and Nitin (my other coworker) made me do for every PR I opened. Just go in and get that fixed up really quickly.


Problem with trailing "/" when optional url param is empty (11 version) - 308 redirect

Have problem with version 11 - new router redirects with 308 code request like /path to /path/, if route /path/{param?} exists
External servers  that call me in prod (like Google push ), don't follow redirects, I have to write both /path and /path/{param}, without optional parameters support.
Is it possible to add also the old fasthttp router, or solve this issue somehow?

Hi @micshome,
I will review it.
Thanks for your issue.

Hi @micshome,
Fixed in v11.0.2! 🎉

Thank you, works like a charm!


Clear macOS GL context after creating window and initial size

Run into issues when using multiple GL UIs with pugl.
Opening new GL UI can mess up the state of existing UIs.
This was partly at fault.

I suspect there are other problems if this fixed anything, but resetting the GL context is a good idea anyway.  Merged as c98ee49, thanks.


feat(ui)!: unify UI components: cmp, wilder, floats

https://github.com/ayamir/nvimdots/pull/718#issuecomment-1567045025. Further changes:

Used branch: refactor/syntax-highlighting that has not yet been merged:

ui["Jint-lzxy/nvim"] = {
	lazy = false,
	branch = "refactor/syntax-highlighting",
	name = "catppuccin",
	config = require("ui.catppuccin"),
}

Simplified cmp.formatting.format()
Pinned cmp-treesitter at commit c8e3a74 b/c we probably don't need that new feature, and it's also a source of trouble.

---------
Signed-off-by: Jint-lzxy<EMAIL_ADDRESS>Co-authored-by: huge-pancake<EMAIL_ADDRESS>

cc @huge-pancake

LGTM for current UI, but seems lack the change of lspsaga outline and lualine.

Current at school so that can't review now. Will have a look on this weekend.

But after the entry name like [LSP] set, other completion candidates provided by vanilla nvim which have no such entry name look like something is missing. Maybe we should disable it at later commits.

The __index metamethod would do the trick :)

Is some candidates got cross out intended?

I disabled nvim built-in completion by set complete = "" and completeopt = "" in options.lua but didn't work. So the candidates without menu may be produced by other sources.

https://github.com/ayamir/nvimdots/pull/772/commits/c81165b6e1cc6bae94cfafba53d83b67b889b575

Addition on ayamir mentioned, is some candidates got cross out intended?

Ys they are defined by the language server (usually denoting this entry is deprecated).

I disabled nvim built-in completion by set complete = "" and completeopt = "" in options.lua but didn't work. So the candidates without menu may be produced by other sources.

Can't wrap my head around this 😢 I've never encountered this issue before (copilot disabled)
Is it related to completefunc? :h complete-functions

I disabled nvim built-in completion by set complete = "" and completeopt = "" in options.lua but didn't work. So the candidates without menu may be produced by other sources.

Can't wrap my head around this 😢 I've never encountered this issue before (copilot disabled)
Is it related to completefunc? :h complete-functions

OK now, the unknown source is treesitter.


Add scroll to top button to main registry page

Hello!

Vote on this issue by adding a 👍 reaction
If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)

Issue details

When scrolling down on the main registry page, it would be helpful to have a scroll to top button that brings you back to the top of the page in order to use the provider filters section.
There are scroll to top buttons used on provider pages in the registry.

Affected area/feature
Registry; the main page here.

Linking this issue on scroll to top usability improvements as the resulting style changes should be included here.


The Deleted Extension can't delete perfectly.

I mistakely installed Time++ extension and it take some some space in panel, and when i was delete it from extension manager, it uninstall from extension manager but not leave panel , its working on panel without installing.

Probably won't be an issue in the latest version.


Kafka connect could also be listed as a source here.

Issue in ./help/sources/connectors/streaming/http.md
We have documentation about Kafka connect ingestion here - https://experienceleague.adobe.com/docs/experience-platform/ingestion/streaming/kafka.html?lang=en
But we could also include it as a possible source in the sources documentation.

Thank you for logging this issue.
We will review the documentation and update accordingly.
Internal Tracking: https://jira.corp.adobe.com/browse/PLAT-104093


Enhancement in Readme.md file of this project

Is your feature request related to a problem? Please describe.
The contributor should make new enhancements in the main Readme.MD of this project
The path to the readme file: ../../Readme.md
Describe the solution you'd like
None
Describe alternatives you've considered
None
Additional context
Please create a fork and a new branch while making changes to the main readme.md file

What are the guidelines and standards for creating a comprehensive and effective Readme.md file, and what should be included in the file to make it most useful for users and contributors?

What are the guidelines and standards for creating a comprehensive and effective Readme.md file, and what should be included in the file to make it most useful for users and contributors?

Hey @imtiazpy, I have gone through a great resource while I was creating this project, here's the link
https://www.freecodecamp.org/news/how-to-write-a-good-readme-file/

Can you suggest some of the projects for ideas that should I follow ?

As for talking about projects, check out
Open source with pradumna by clicking the link below. It is a great project and it has helped me a lot
https://github.com/Pradumnasaraf/open-source-with-pradumna

@hasnainmakada-99 I am a beginner to open source , I would like to contribute README.md
Sending a PR in sometime!


Can't place freestanding wire on other freestanding wire

Forge: <IP_ADDRESS>9
Charset: 0.0.3-build 1

This one I knew about.

https://github.com/asiekierka/CharsetMC/commit/7c119924a23452c604349fe81bb01ee8bed7c17b


[#121479497] View opportunity response

Completes this story: https://www.pivotaltracker.com/story/show/121479497
New results page looks like this (NOTE brand new updated screenshot with 2/3 columns and padding):

This introduces quite a lot of DOS-specific logic into the frontend app, which is pretty horrible.  I can't see any way around it for this page though, and it's all in the one "results page" template.
New flow (always to result page) analytics change (&result=success/fail parameter) has been discussed with Ash and he just needs to know when this gets released.
Words on the page have been iterated with @ralph-hawkins and @superroz quite a lot, so try not to find anything else.

You could have mentioned it last week when I sent all the screenshots :)
I'll see if I can work it out now.

You’re right, sorry I missed it. It was in the original pivotal story.

I'm a bit concerned about how tied this page is to our current question options etc (like a special case for 'an' before 'Interview'). And it feels like we need to think about making boolean questions less scary.
But it looks like we need this for labs tomorrow and I don't see any obvious quick ways of improving this, so 👍

I agree, it's not really ideal at all.... sorry.


net: l2: ieee802154: L2/L3 decoupling

This fixes #48585.
It also contains some minor documentation and formatting improvements - see individual commits.

Unfortunately some commits had an "author" field with an email that no longer exists. Fixed the author fields now (this is the only change of the new push).

While testing this stuff on a real device I found more places where the assumption was made that all interfaces necessarily have an IP configured. Could you please review those changes again?

Thanks everyone, this was a great first contributor experience. Makes me want to contribute much more to the Zephyr project. My holidays are almost over so now its the weekend schedule.


A IRQ is lost when conflicting with another one

The DCF code uses two IRQ :

one linked to internal timer. Used to step one second local clock change
one linked to DCF radio signal decoder. Used to process bit sequence received on the radio channel
When the DCF related IRQ goes wrong (e.g. when a lot of parasitic signals are received on IRQ gpio pin) it happens that the internal timer IRQ is canceled.
Modification on the push button driver debounce algorithm improved the robustness but error still occurs.
-- Channel 1 (yellow ) : the audio signal converted in signal envelope that triggs an IRQ on both rising and falling edge.
-- Channel 2 (blue ) : the local timer IRQ handler.

this commit has removed the issue. It is a simple workaround, nort really a solution.

The last version DCF77_TextUI v2.py with IRQ based local timer seems more robust,


PipeableOperatorsOnlyRule.js fails silently when RXJS 6 is installed

As recommended by the angular update guide, I updated to rxjs 6 before running rxjs-5-to-6-migrate.
rxjs-5-to-6-migrate ran without errors, and correctly fixed the imports, but left patched operator calls unchanged.
Looking at the implementation of the PipeableOperatorsOnlyRule.js, I noticed that is uses the typeChecker to identity instance operator calls. Suspecting that the type checker needs the source code to compile, and therefore the old rxjs in node_modules, I ran
npm install<EMAIL_ADDRESS>rxjs-5-to-6-migrate -p src/tsconfig.app.json

and the patched operator calls were rewritten correctly.
Please consider emitting an error message if the wrong rxjs version is installed - if I hadn't seen rxjs-5-to-6-migrate rewrite patched operator calls in another project, I would have assumed it incapable of doing so, and missed out on a great feature.

Thansk @bedag-moo - saved my day.

should be on readme first page

I am so glad I perused rxjs-tslint issues when this tool failed to update the operators... Thank you @bedag-moo

@bedag-moo just went through a sample migration. When you run ng update @angular/core, Angular CLI would install rxjs-compat. PipeableOperatorsOnlyRule will take the typings from there and the migration should go as expected.
I'll update the readme once again.

After 3 months, my memory is a bit hazy ... I guess it is possible that I ran npm install<EMAIL_ADDRESS>rather than ng update because I didn't realize that the phrase

Use ng update or your normal package manager tools to identify and update other dependencies.

was not meant to include rxjs.
In any case, rxjs-5-to-6-migrate should error if it can not resolve the Observable type rather than silently doing nothing.


cts CharBuf selection is based on buffer with the max capacitance

Signed-off-by: habibayassin<EMAIL_ADDRESS>

I should have mentioned DCO to you.  When you commit you need to use '-s' to sign your commits.  I use a git alias for this so I don't forget.  Please click the Details link by DCO to get instructions on how to fix this up.

I followed the instruction in the Details link by DCO. Is there anything else I should do?

Something seems to have gone quite wrong - you have a ton of conflicts in unrelated code.

yes I have noticed, trying to solve the problem

@maliberty You need to kick off the scan workflow.


Bot Token

Hello,
just want to report, i think its, a bug.
The First Part of my Token that Discord gave me ist 2 Characters to long,
so i cannot put my Token into the instance of Discord.
Sry for my bad English.

Hi, thank you for the report.
This is already fixed since release v1.1.5.
Currently v1.1.6 is available via NPM or GitHub.

Did it. Thx :-).


[App Service] az logicapp deploy : Implement logicapp zip deployment

Description

Implements logic app zip deployments using the pre-existing functionapp zip deploy.
Previous work by Parth here: #19675
Testing Guide

azdev test --live test_logicapp_zip_deploy_e2e
History Notes

This checklist is used to make sure that common guidelines for a pull request are followed.

[X] The PR title and description has followed the guideline in Submitting Pull Requests.

[X] I adhere to the Command Guidelines.

[X] I adhere to the Error Handling Guidelines.

The CI tests are failing with vcr.errors.CannotOverwriteExistingCassetteException for some reason even though the command succeeds locally

App Service

Could you fix the CI issues?

Converting to draft while I test with linux logic apps

This will be superseded by an upcoming PR from @haroonf


chore: bdd-spring-1583951475 to 0.0.1

chore: Promote bdd-spring-1583951475 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[BUG]: Current Node.js version file is on the 21, not 20, 18, or 16

Description of the bug
Node.js build trigger in last_nodejs.txt is in 21.
Environment

Steps To Reproduce

Additional Information
I'd recommend creating 3 separate nodejs LTS files and trigger build only the changed version.
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.

Node.js version checking will check each 2 latest/still maintained LTS and current version from Node.js instead of only checking the latest current version from GitHub.
Docker image build only triggers for the updated version instead of building each version.
Bun and Node.js versioning will be cached into versions.json instead of a different file.
Bun will support the latest and canary releases by checking from npm instead of only the latest version from GitHub.
Docker image tagging will support version rollback by defining the docker image tag with format almost similar to docker-node versioning: imbios/bun-node:BUN_VERSION-NODE_VERSION-LINUX_DISTRO, and support semver latest tagging as example below:

e.g. latest stable bun version 1.0.11, latest canary bun version 1.0.11-canary; latest current node version 21.7.0, latest lts node version 20.9.0, second latest node version 18.2.0; distro alpine, debian-slim, debian; then we will build image like below:

imbios/bun-node:1.0.11-21.7.0-alpine; tags: 1.0-21.7.0-alpine, 1-21.7.0-alpine, latest-21.7.0-alpine, 1.0.11-21.7-alpine, 1.0.11-21-alpine, 1.0.11-latest-alpine, latest-alpine

Given the examples:

Bun versions: 1.0.11, 1.0.11-canary
Node.js versions: 21.7.0 (current), 20.9.0 (latest LTS), 18.2.0 (second latest LTS)
Linux distributions: alpine, debian-slim, debian

Bun version 1.0.11 with Node.js version 21.7.0 (Current)

For alpine, debian-slim, and debian:

imbios/bun-node:1.0.11-21.7.0-DISTRO
imbios/bun-node:1.0-21.7.0-DISTRO
imbios/bun-node:1-21.7.0-DISTRO
imbios/bun-node:latest-21.7.0-DISTRO
imbios/bun-node:1.0.11-21.7-DISTRO
imbios/bun-node:1.0.11-21-DISTRO
imbios/bun-node:1.0.11-latest-DISTRO
imbios/bun-node:latest-DISTRO

Bun version 1.0.11-canary with Node.js version 21.7.0 (Current)

Replace 1.0.11 with canary in each tag from above.

Bun version 1.0.11 with Node.js version 20.9.0 (Latest LTS, Iron)

Replace 21.7.0 with 20.9.0 and add lts and iron in each tag from 1.
Example: imbios/bun-node:1.0.11-20.9.0-lts-DISTRO, imbios/bun-node:1.0.11-20.9.0-iron-DISTRO

Bun version 1.0.11-canary with Node.js version 20.9.0 (Latest LTS, Iron)

Replace 1.0.11 with canary and follow the pattern from 3.

Bun version 1.0.11 with Node.js version 18.2.0 (Second Latest LTS, Hydrogen)

Replace 21.7.0 with 18.2.0 and add hydrogen in each tag from 1.
Example: imbios/bun-node:1.0.11-18.2.0-hydrogen-DISTRO

Bun version 1.0.11-canary with Node.js version 18.2.0 (Second Latest LTS, Hydrogen)

Replace 1.0.11 with canary and follow the pattern from 5.

Canary tag

imbios/bun-node:canary-latest-debian

Latest LTS tag

imbios/bun-node:latest-lts-debian

This approach provides a comprehensive tagging system that includes various versions and distros, accommodating version rollbacks and specific version needs.


add more documantation about cluster.restart()

#825  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @BelSasha and the rest of your teammates on  Graphite

Merge activity

May 23, 1:50 PM EDT: @rohinb2 started a stack merge that includes this pull request via Graphite.


removed rows

📝 Changed routes:

/

(view full size)

Commit 2e576fa490567d12ec2ca3374a34a6a9139c05a0 (https://earth-as7jyivv5-anthropogenic.vercel.app).


Allow 2 invocations to the same method

At least 2 is really useful for common scenarios of doing something with
a value if that value is present:
my_hash['xxx'] = something.value if something.value

@rafatower , @javitonino , @gfiorav , agree?

The warning with two uses is sometimes useful, but I agree that most of the time is giving warnings based on the pattern you mentioned (nil checks on an attribute). So :+1: for me.

:+1:


WIP: Binary Release

Codecov Report
Base: 33.33% // Head: 33.33% // No change to project coverage :thumbsup:

Coverage data is based on head (59bf53b) compared to base (fc5e530).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #3   +/-   ##
=======================================
  Coverage   33.33%   33.33%
=======================================
  Files           1        1
  Lines           3        3
=======================================
  Hits            1        1
  Misses          2        2

Flag
Coverage Δ

unittests
33.33% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


(TokenExchangeService): The authentication token has expired and does not update components work.

Description
After deployment Greengrass receive an auth token using tokenExchangeRole with an expiration time of 3600 sec (1 hour). During another component work that works with a StreamManager, the token becomes expired after 1 hour and it does not update without component redeploy.
Expected
As it was expected, the exchange token service will update the token as soon as it expires.
Actual
Token remains expired without a new trigger - component redeployment (the component also has a HARD depend on TokenExchangeService).
As a result, the component receives the error "Failed to upload data to S3. The provided token has expired."
Question
Are there any ways to activate auto renewal for auth token using TokenExchangeService? Or any other possible solutions for this case?

Hello,
The token is automatically refreshed when it expires and a a component requests new credentials. TES will request new credentials 5 minutes before expiration of the old token.
Please verify that your device's clock is correct. If the clock is in accurate, then Greengrass will not know that it needs to get updated credentials.
If you believe that your clock is accurate, please provide debug level logs from Greengrass showing the time that it gets the credentials and from the time that the S3 operation happens without credentials.

Hello.
@MikeDombo Clocks are synchronized for now.
Also we log "AWS_CONTAINER_AUTHORIZATION_TOKEN" env in our application and we have the same token every time.
greengrass.log
StreamManager.log

@roman-hizatulin-ge is this related to the original question, I see that you are not the person who creates this issue?
The container auth token being the same is normal. This is not the AWS credential used to talk to AWS. It is only a token to allow you to request AWS credentials from Greengrass.

@MikeDombo "is this related to the original question" yes

You said clocks are synchronized for now.
Was the clock correct previously?
Please provide all raw logs from /greengrass/v2/logs. Open a support case through the AWS Console if you want to share privately.

There was a one hour before inside a docker container.

There was an hour before inside a docker container.

I'm not sure what you mean by this. Are you saying that the system clock was wrong by 1 hour?
Or are you talking about the logs? Please provide all the logs in their raw format. The log files provided do not look like raw logs from greengrass, some are missing timestamps and context.

I'm not sure what you mean by this. Are you saying that the system clock was wrong by 1 hour?
Yes, you are right
Please provide all the logs in their raw format. The log files provided do not look like raw logs from greengrass, some are missing timestamps and context.
I'm collecting them

I believe you have corrected the clock but just to make clear the requirements.
For the avoidance of doubt, the system clock can use any timezone as long as the time and timezone is set correctly. Logs are always written with UTC time. It is currently 14:28 UTC, so if the most recent logs have a different time than that, the clock is not set correctly.

Please look at these files (with timestamps)
StreamManager.log
greengrass.log

Thank you, I will look more in a little while.
I see at the end of the stream manager log that it has nothing to upload, please make sure that stream manager does have work to do so we can see if it succeeds or fails.

Please find "Failed to upload data to S3" in the SM.log

Yes I see errors at 13:22 to 13:22. Uploads succeeded before that time. No uploads were attempted after that time.
That's why I'm requesting that you give stream manager more work to do, to see if it will succeed given that the system clock is correct now.

Did you change any of the default options of stream manager? It looks like it has loaded aws credentials from environment variables instead of loading them from greengrass, this should not happen.
You said greengrass was in docker. Do you have aws credential environment variables passed into the container? You must remove those if you do.

Yes I see errors at 13:21 to 13:22. Uploads succeeded before that time. No uploads were attempted after that time.
That's why I'm requesting that you give stream manager more work to do, to see if it will succeed given that the system clock is correct now.

Uploaded new files
StramManager17.00.log
greengrass17.00.log

Based on the logs and your description, it looks like Stream Manager is getting credentials from environment variables instead of the Token Exchange Service. You could further validate this by looking in /proc/<pid of stream manager process>/environ for AWS_ACCESS_KEY_ID. These environment variables are not set by Greengrass, but may be inherited from your environment. You must remove those environment variables in order for Stream Manager to work properly by requesting live credentials from TES.

Based on the logs and your description, it looks like Stream Manager is getting credentials from environment variables instead of the Token Exchange Service. You could further validate this by looking in /proc/<pid of stream manager process>/environ for AWS_ACCESS_KEY_ID. These environment variables are not set by Greengrass, but may be inherited from your environment. You must remove those environment variables in order for Stream Manager to work properly by requesting live credentials from TES.

It seems you're right, we have the env var. Will try to unset

Sounds like this issue should be resolved, closing since there have not been any updates.
Reopen as needed.

Hello @MikeDombo
Yes, the reason is the "AWS_ACCESS_KEY_ID" env var.
We are working on a fix now.
Thx for your big support. 🤝🏻

Hello. @MikeDombo could you please help with the next question:
We need the "AWS_ACCESS_KEY_ID" variable during the green-grass installation to provision a thing and all components.
After installation this variable should be unset (we've already tried that, but unsuccessfully).
Do you know | have any workaround to achieve this?

I believe you said that you are using Docker right?

I generally advise against using Docker as many people get confused about where their data is located and where exactly the processes are executing. You may not have this confusion, but I still will advise you to run Greengrass natively, not in a container.
You do not necessarily need to use automatic provisioning, which is the only thing that requires the AWS environment variables. You could use manual provisioning or fleet provisioning by claim.
How did you try to unset the variable? Environment variables are explicitly passed into docker containers, so if you run the docker container without passing in the environment variable then it cannot possibly be set in the container.
You could set the credentials in a credential file instead of environment variables. Then delete the file.

Stream Manager v2.1.12 is just released now. This new version will always prefer the credentials from Greengrass instead of the default order which will use credentials from environment variables.
Other components, including components that you write yourself, will not have this credential order change so you should still work on a solution to remove the environment variable credentials.

Hello @MikeDombo. Sorry for late. Yes, we use a GG as a docker container. For now we have already updated a GG StreamManager to the latest version and chosen the latest option (4th - credential file) you proposed and it is fixes our issue. Thanks a lot.
🤝🏻


Add section for configuring Okta as an auth backend

What
Adds a section under Reference on configuring Okta auth
How
teams.md: add blurbs on Okta and SAML auth backend configuration options
setup-okta-team.md: detailed instructions on how to configure a team with Okta
Why
It's kinda complicated for someone to figure out on their own
I wanted to add in pictures too, but wasn't sure exactly how to go about that. Also, not entirely sure if this is the place to make these changes or if there's somewhere else I need to change. Guidance would be awesome

For screenshot examples, see sft-osx.md and enrolling-a-client.md. Basically:

Resize the window to something sane, if it's a browser, hide your extensions.
Screenshot with ⌘ + ⇧ + 4, then hit spacebar, then click on the window you want to capture.
Copy the screenshot into docs/static.
Set a max-height on the image that is 50% of the actual height in pixels. This is because retina screenshots are at 2x resolution. Don't set a height or width, as that will mess up the aspect ratio on narrow screens.

If you have any terminal output that you'd like to display, search for {{% terminal %}} to find examples.

+1


Implement HTTPS

An opportunity to try out https://letsencrypt.org

Implemented on local development environment. Hosting using HTTPS on prod now taken as a given.


Jonathon - HIVE3 CensuScope Blocker

Reilan was manually uploading assemblies from GISAID per my request. I gave her all of the same assemblies and information that ran correctly for me. This was a test. Her computations failed at 20% via CensuScope. Emma's computations have also failed, but I am not sure if it is caused by CensuScope. Id like to get this fixed before I meet with Vahan and ask for his help. See her slide attached below.

The slidedeck is here.

In the meeting wednesday with Vahan and @kee007ney they said they would set up a time to at the NT tax and fix the censuscope

@kee007ney hey I am assuming this will go along with the HIVE3 code updates?

I ran a censuscope computation via the URL link. The computation completed at 100% but gave no available downloads. @kee007ney confirmed that there was nothing in the back end. He also suggested that the images may have been suppressed. This will need to be looked at further and discusses with Vahan

@kee007ney do we know if this has been fixed?

So this does no display any file outputs or images, but censuscope is on HIVE3

@kee007ney What is the update for Censuscope on HIVE3? Is the output files and figures visible now?

@kee007ney I am still getting Censuscope issues on HIVE3

Hey @kee007ney do you know the updates with Lam? Was he successful in adding the kraken to HIVE3 as a replacement for Censuscope? My computations are running perfectly fine, but I wasn't sure if he had added this yet.

@kee007ney and Lam are still troubleshooting but it is not affecting the computations at all


Add formatting to table values

The values should use a delimiter for large numbers to be more readable.
What
This change formats the numbers to use locale based format delimiters.
Why
Number in tables do not display with delimiter.
Screenshots
Before

After

Review Checklist

[x] Changes in scope.
[x] Added/updated feature tests.
[ ] Added to trello card.

 (1) Page data - Table numbers should have commas


[ERROR LOG]

hello:
I have started this elastalert for about two weeks, and everything goes fine until yesterday, I find a error log in elastalert and it seemed hanged and never alert again, here is my error log:
{"log":"ERROR:root:Traceback (most recent call last):\n","stream":"stdout","time":"2018-06-21T09:11:26.909030632Z"}
{"log":"  File \"/usr/local/lib/python2.7/site-packages/elastalert-0.1.29-py2.7.egg/elastalert/elastalert.py\", line 1274, in alert\n","stream":"stdout","time":"2018-06-21T09:11:26.909035999Z"}
{"log":"    return self.send_alert(matches, rule, alert_time=alert_time, retried=retried)\n","stream":"stdout","time":"2018-06-21T09:11:26.909040744Z"}
{"log":"  File \"/usr/local/lib/python2.7/site-packages/elastalert-0.1.29-py2.7.egg/elastalert/elastalert.py\", line 1363, in send_alert\n","stream":"stdout","time":"2018-06-21T09:11:26.90906386Z"}
{"log":"    alert.alert(matches)\n","stream":"stdout","time":"2018-06-21T09:11:26.90907852Z"}
{"log":"  File \"/usr/local/lib/python2.7/site-packages/elastalert-0.1.29-py2.7.egg/elastalert/alerts.py\", line 467, in alert\n","stream":"stdout","time":"2018-06-21T09:11:26.909082248Z"}
{"log":"    self.smtp.sendmail(self.from_addr, to_addr, email_msg.as_string())\n","stream":"stdout","time":"2018-06-21T09:11:26.909085973Z"}
{"log":"  File \"/usr/local/lib/python2.7/smtplib.py\", line 752, in sendmail\n","stream":"stdout","time":"2018-06-21T09:11:26.909095675Z"}
{"log":"    raise SMTPDataError(code, resp)\n","stream":"stdout","time":"2018-06-21T09:11:26.909099182Z"}
{"log":"SMTPDataError: (450, 'Requested action not taken: AQAAfwBHHZPQaytblI0CAA--.18457S3, please try again')\n","stream":"stdout","time":"2018-06-21T09:11:26.909102966Z"}
{"log":"\n","stream":"stdout","time":"2018-06-21T09:11:26.909106518Z"}
{"log":"\n","stream":"stdout","time":"2018-06-21T09:11:26.909109545Z"}
{"log":"2018-06-21 17:11:26,909 DEBG 'elastalert' stderr output:\n","stream":"stdout","time":"2018-06-21T09:11:26.909539524Z"}
{"log":"ERROR:root:Uncaught exception running rule LOG ERROR WATCH PPSEC: (450, 'Requested action not taken: AQAAfwBHHZPQaytblI0CAA--.18457S3, please try again')\n","stream":"stdout","time":"2018-06-21T09:11:26.909550807Z"}
{"log":"\n","stream":"stdout","time":"2018-06-21T09:11:26.909554715Z"}

when restart elartalert, everything goes fine and starting alert, why this SMTPDataError happen ?

Google is your friend. I found:
https://www.mail4any.com/smtp-error-codes/
"450 - Requested Action not Taken
The server could not access the mailbox to deliver the message. Typically a transient error. Often followed by a second SMTP error code that has more specific context."

@Qmando I restarted my app and watched for about one week, it had not happened until now, I would like to close it, then continue to monitor the log


Implement Optimization Algorithm

I would like to contribute the Ant Colony Optimization Algorithm (as described https://en.wikipedia.org/wiki/Ant_colony_optimization_algorithms). Should I proceed with the implementation ?
Thanks

Hi @gthd ,
Of course, feel free to proceed, and let us know if you need any inputs in the process!

Hello,
I believe I can help contribute to this issue, please let me know which tests to run the algorithm against, both for efficiency and type safety. Thank you.
I will follow these guidelines for contributing.
https://facebookresearch.github.io/nevergrad/contributing.html


Don't set the max lumi default value for MC

fixes #7910

I was afraid there could be a use case that we wouldn't have that env var set, but that can't happen since all the service operations are done with the manage script (which loads the config.py).
I think this fix is safe (and neat!) However, timing a few different ways of doings this, the following seems to be more than an order of magnitude quicker
### line 31 or so
self.args.setdefault('MaxLumisPerElement', os.environ.get('MAX_LUMIS_PER_WQE'))
### then line 71
if self.args['MaxLumisPerElement'] and nLumis > int(self.args['MaxLumisPerElement']):

Thanks Alan, I updated the patch as you suggested


dd: /dev/md4: Invalid argument on u-boot installation for banana-pi

During the image creation process the setup.sh burns the various boot loader files to the image.
Installing U-Boot files
+ dd if=/usr/local/share/u-boot/u-boot-bananapi/sunxi-spl.bin of=/dev/md4 bs=1024 seek=8
dd: /dev/md4: Invalid argument
486+1 records in
486+0 records out
497664 bytes transferred in 5.784579 secs (86033 bytes/sec)

I am building in a jail with the following flags allow.mount=true,enforce_statfs=1

This is also happening for me. 11.0-STABLE, not using jails.

And me too.

And me too

Here too.

So, is crochet completely unusable right now? The offending line is https://github.com/freebsd/crochet/blob/master/lib/disk.sh#L47 but I don't know what to do with it.

Ah, no, that line has nothing to do with the problem.

To debug this, you can (temporarily) edit board/BananaPi/setup.sh to print out more information at the top of the allwinner_partition_image() function.  In particular, it would probably make sense to try ls -l /dev/${DISK_MD} to make sure the md device was created, and maybe mdconfig -l to list all the existing md devices.

@loos-br might be right.  If /usr/local/share/u-boot/u-boot-bananapi/sunxi-spl.bin is not a multiple of the block size, then adding conv=sync to the dd command originally mentioned may fix it.

I believe #199 fixes this; please try and let us know.


fix crash in device

fix stringByAppendingString crash in ios9.3.2 iPhone device, not crash in Simulator.

This is a little strange, but thanks for this pull request! :+1:


Validate access to image

Boto3 returns an image object, if the image exists, even if the user
does not access to the image. This change ensure that the user also
has access to the image before proceeding. This ensures that there are
no unexpected errors downstream.

Looks good, but can you add a comment so that the next person understands what you're trying to do?


Found a Bug in Streaming.cpp

I found a bug in Streaming.cpp. Fixing the bug dramatically improves the performance.
The statements -
if (c1 != 0x00 && c2 != 0x80 && c3 != 0x00 && c4 != 0x80) {
Should be -
if ((c1 != 0x00) || (c2 != 0x80) || (c3 != 0x00) || (c4 != 0x80)) {
The spectrums now look good and the audio is much better.

@robojay  I found the last problem that was causing trouble.
Fixing the statements above cleaned up the spectrums. The read routine was returning more values than were requested - that was overflowing the data buffer and crashing the program. Taking care of those two problems - it now works pretty good.

Very cool - thanks for digging into this!  I'll see if I can try it out on my radio over the next couple of days.  It's been a while since I've used Soapy...

@righthalfplane I am not using IC8600 now, make a pull request, and I will add your changes to the code.

There is still some strangeness - sometimes when you change sample rates a dip in the response occurs, but if you select the sample rate a second time - the dip goes away. That is what happens with SdrGlut - I am not sure what happens with other programs

@robojay @dmitryelj - I put in the pull request

Request merged, thanks


Expose command that uses extract/legacy-word and/or provide option to use it by default

tpope/vim-sexp-mappings-for-regular-people re-defines the word text-object to include punctuation such that vim.fn.expand is considered a single word. Prior to Conjure using treesitter to extract the word text object, it had abided to vim-sexp-mappings-for-regular-people's new definition of a word. Now, with treesitter enabled and vim-sexp-mappings-for-regular-people installed, executing ConjureEvalWord with the cursor on the "v" in vim.fn.expand would eval just eval vim instead of vim.fn.expand. I found it quite useful to be able to eval the entire word including the punctuation, particularly when configuring Neovim.
Would you consider adding a command that uses extract/legacy-word and/or provide a per language option for defaulting to extract/legacy-word?

I have made a pull request (#461) to illustrate what I have in mind and am happy to make adjustments if necessary!

I think what we really want here is to adjust the "extract word" tree sitter implementation so it takes the whole word into account, like the sexp mappings plugin does. I'd rather not use the legacy word function if we can avoid it but will still keep an open mind. Avoiding another config option would be nice too, there's already so many!
I'll have a quick play with the TS code, I have a feeling it used to work like you described at some point, maybe the TS definition changed at some point 🤔 it's annoyed me personally too, definitely prefer the whole symbol idea, we're not dealing with words, we're dealing with symbols which can contain .s etc.

Should be fixed! We now look up one level at the parent to check if it's type is multi_symbol. If so, we use that node instead of the lowest child that the tree sitter API reported initially.

I agree that evaluating symbols by default is preferred! I am now using develop branch and it is working as expected. I will let you know if I notice anything odd. Thank you for looking into this!


Error when using sassc-rails

Hi and many thanks for your work to build a Ruby gem for tabler UI.
I've started with a fresh Rails (<IP_ADDRESS>) app which uses sassc-rails instead of sass-railsdue to the deprecation  warnings for sass.
When I start the (development) server with rails s I get the following error:
Traceback (most recent call last):
bin/rails: Bootsnap::LoadPathCache::FallbackScan
	50: from bin/rails:3:in `<main>'
	49: from bin/rails:3:in `load'
	48: from /Users/<username>/<app path>/bin/spring:15:in `<top (required)>'
	47: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	46: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	45: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `<top (required)>'
	44: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `load'
	43: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/spring-2.0.2/bin/spring:49:in `<top (required)>'
	42: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/spring-2.0.2/lib/spring/client.rb:30:in `run'
	41: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/spring-2.0.2/lib/spring/client/command.rb:7:in `call'
	40: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `call'
	39: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `load'
	38: from /Users/<username>/<app path>/bin/rails:9:in `<top (required)>'
	37: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `require'
	36: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:257:in `load_dependency'
	35: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `block in require'
	34: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in `require'
	33: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in `require_with_bootsnap_lfi'
	32: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/loaded_features_index.rb:83:in `register'
	31: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `block in require_with_bootsnap_lfi'
	30: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `require'
	29: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands.rb:18:in `<main>'
	28: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/command.rb:46:in `invoke'
	27: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/command/base.rb:65:in `perform'
	26: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
	25: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
	24: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
	23: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/server/server_command.rb:142:in `perform'
	22: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/server/server_command.rb:142:in `tap'
	21: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/railties-<IP_ADDRESS>/lib/rails/commands/server/server_command.rb:145:in `block in perform'
	20: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `require'
	19: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:257:in `load_dependency'
	18: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/dependencies.rb:291:in `block in require'
	17: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in `require'
	16: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in `require_with_bootsnap_lfi'
	15: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/loaded_features_index.rb:83:in `register'
	14: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `block in require_with_bootsnap_lfi'
	13: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `require'
	12: from /Users/<username>/<app path>/config/application.rb:18:in `<main>'
	11: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bundler-2.0.1/lib/bundler.rb:114:in `require'
	10: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bundler-2.0.1/lib/bundler/runtime.rb:65:in `require'
	 9: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bundler-2.0.1/lib/bundler/runtime.rb:65:in `each'
	 8: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bundler-2.0.1/lib/bundler/runtime.rb:76:in `block in require'
	 7: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bundler-2.0.1/lib/bundler/runtime.rb:76:in `each'
	 6: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bundler-2.0.1/lib/bundler/runtime.rb:81:in `block (2 levels) in require'
	 5: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:25:in `require'
	 4: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:36:in `rescue in require'
	 3: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in `require_with_bootsnap_lfi'
	 2: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/loaded_features_index.rb:80:in `register'
	 1: from /Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `block in require_with_bootsnap_lfi'
/Users/<username>/.rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/bootsnap-1.4.1/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `require': cannot load such file -- tabler-rubygem (LoadError)

I think this error originates from your require 'sass' statement in line 53 of the rubygem.rb file. Currently I use the following work around
  gem 'sass-rails', '~> 5.0.7', require: false
  gem 'sassc-rails', '~> 2.1.0'

Do you have any idea why this isn't working?
Many thanks..!

I'm thinking about trying to fix this because we just hit this issue as I wanted to remove ruby sass as it's EOL now.
@lightyrs what approach do you prefer? Checking sassc presence first and fallback to sass or can we just use sassc since sass isn't supported anymore?
If we go with only using sassc then what do you think about including it as a dependency?
I was surprised first that the gem is requiring and referencing sass but only as an implicit dependency :(

I'm thinking about trying to fix this because we just hit this issue as I wanted to remove ruby sass as it's EOL now.
@lightyrs what approach do you prefer? Checking sassc presence first and fallback to sass or can we just use sassc since sass isn't supported anymore?
If we go with only using sassc then what do you think about including it as a dependency?
I was surprised first that the gem is requiring and referencing sass but only as an implicit dependency :(

@vbalazs Ideally we would provide backwards compatibility (sassc fallback to sass), however, if sass isn't actually required as a dependency (and maybe it doesn't need to be), then getting rid of it would be the best approach (I think).

What is the purpose of this sass setup?
What do you think about adding boostrap gem as a runtime dependency (even the dummy rails app depends on it)? That already depends on sassc and everything seems to work if we remove that configure_sass piece of code and have the bootstrap gem included 🤔

What is the purpose of this sass setup?
What do you think about adding boostrap gem as a runtime dependency (even the dummy rails app depends on it)? That already depends on sassc and everything seems to work if we remove that configure_sass piece of code and have the bootstrap gem included 🤔

That seems look a good plan @vbalazs.

Is there a work around this?

@alejandrodevs in the referenced closed PR, you can find some solutions

Why don't we merge this fix?
https://github.com/lingokids/tabler-rubygem

@alejandrodevs I'm just curious about backwards-compatibility and it doesn't seem like the readme reflects anything about these changes.

@lightyrs what about having a new version with this fix and support the old one in another development line to for a while until we decided to stop supporting it.

Honestly, I'd need someone else to help manage the project. I don't really use tabler anymore but I still see the value in this project. Any interest?


Update release workflow

As needed in https://github.com/quarkiverse/quarkiverse-devops/issues/210

@gastaldi you are fast as lightning!


[WIP] Initial conda support v2

Hi all,
I created a different initial conda support branch, trying to keep things simple where I can.
My approach tries to follow all tox' hooks a bit more closely and converts the dependencies to a conda environment.yaml which can be installed in a single go (instead of having to switch envs and doing pips manually).
It's not bug free yet, as tox is still picking up some wrong environment variables. kalefranz's get_activated_env_vars seems related, but the cmdbuilder commands are rather unwieldy..
The main issue this currently has, is that tox expects the python executable to be in ./.tox/testenv/Scripts while conda puts that in the parent directory (testenv) and that's hard wired in the config (there's an assert in place preventing you from changing that). I tried making a symlink from within Python, but it complains about execution rights to do so.
Please take a look to see if it's of any use :)

@kalefranz care to do a review of this? just so we can validate the approach generally is good :+1:

I'll try to prettify some code and add some basic tests before merging.

I finally got this to work on my Windows machine for the conda environment variables (getting the env_var_map)
def set_conda_env_args(venv):
    """Get environment variables for an activated conda environment."""

    envdir = str(venv.path)

    if on_win:
        activate = ["activate.bat"]
    else:
        activate = ["conda", "activate"]
    activate.append(envdir)

    concat = ["&&"]

    envfile = os.path.join(envdir, "env.json")
    envdump = [
        "python",
        "-c",
        "import os, json; json.dump(dict(os.environ), open(\"{0}\", 'w'))".format(
            envfile.replace("\\", "\\\\")
        ),
    ]

    args = activate + concat + envdump
    env = venv._getenv(testcommand=False)
    redirect = venv.session.config.option.verbose_level < 2

    with venv.session.newaction(venv, "activate") as action:
        action.popen(args, env=env, redirect=redirect)

    with open(envfile, "r") as f:
        env_var_map = json.load(f)
    os.remove(envfile)

    # TODO: Store the environment variables in the right place:
    # Something along the lines of venv.envconfig.setenv.definitions.update(env_var_map)
    # That breaks the installation process though

I would love to re-ignite the efforts here, soon (August 20th ish). However, the questions regarding the Python interpreters and environment variable management remain unresolved.
@kalefranz or @gaborbernat , any ideas on the best path going forward?
Environment and config variables
I was thinking of just dabbling in both tox and tox-conda configs until I get some prototype working and see where that gets me. However, I could be getting the interpreters all wrong. E.g. which python executable in the tox config variables just orchestrates tox and which ones correspond to actual test environments. I still can't suppress the feeling there is some duplication of variable storage there.
If the discussion on the tox mailing list is any indication, it seems that tox relies rather a lot on the python versions on PATH, which is definitely not where conda exposes them by default (let alone strictly naming them pyXY). Hence the importance and delicacy of updating the env_var_map.
Tests
Having some tests run in at least pytest would be great. But tox-ception is always a bit of an issue here. Not sure if we need a lot of separate tests, or just try and run the default tox ones with this plugin hooked up.

Hi @TiemenSch, thanks for pushing this forward!

I was thinking of just dabbling in both tox and tox-conda configs until I get some prototype working and see where that gets me.

I think this is the best way forward (and looking a bit more into how tox handles these things). If you have concrete questions then that stump you, please ask here and hopefully someone can nudge you along.

Hi all, I have been looking into an implementation of tox-conda myself and have gotten started with a prototype. I hope you don't mind if I join the discussion and add some comments? Does @TiemenSch intend to continue with this effort? I might consider opening a PR myself just for another discussion point.

Closing since this has been superseded by #5.


Not Working

I have install Autoprefixer from Package Controller as the documentation on windows machine
and make sure that i have node installed with version v5.3.0
but it is not working. when i use the shortcut ctrl+alt+x

Does it work when using it from the command palette (Cmd+Shift+P)?

Probably a duplicate of https://github.com/sindresorhus/sublime-autoprefixer/issues/68#issuecomment-192837311.

I thought he wasn't able to use it, not that he couldn't find it?

Oh, I linked to the wrong issue, but the deal is that he probably tried to autoprefix something that didn't need prefixing and nothing happened.

Probably, yeah.

i try box-shadow but didn't work

box-shadow doesn't need prefixing.

Could you give me something to test :D

Try flex: 0 0 100%.


[release/1.7] Prepare release notes for api v1.7.19

Like in the main branch, the API module must be tagged first and go.mod updated before a release which includes api changes.
Test run: https://github.com/dmcgowan/containerd/releases/tag/api%2Fv1.7.19-rc.0

Welcome to the api/v1.7.19 release of containerd!
The first dedicated release for the containerd 1.7 API. This release is
separately tagged from the main 1.7.x releases after the v1.7.18
release but follows the versioning.
Highlights

Add API go module (#10189)

Please try out the release binaries and report any issues at
https://github.com/containerd/containerd/issues.
Contributors

Derek McGowan
Akhil Mohan
Phil Estes
Sebastiaan van Stijn

Changes
7 commits

436feeb0d Prepare api release for v1.7.19
: api: update github.com/containerd/ttrpc v1.2.5 to align with containerd 1.7 module (#10364)

2a6aa6ddf [release/1.7] api: update github.com/containerd/ttrpc v1.2.5

Add API go module (#10189)

3be919f3c Add support for 1.8 interfaces
a3a7431bc Add api go submodule
4b82470f6 refactor: move plugin/fieldpath to api/types/

Dependency Changes

github.com/containerd/ttrpc                v1.2.4 -> v1.2.5
github.com/golang/protobuf                 v1.5.4 -> v1.5.3
google.golang.org/genproto/googleapis/rpc  d307bd883b97 -> b8732ec3820d

Previous release can be found at v1.7.18

/retest

All green ✅ now 🎉


Submersion of Homalosorus into Diplaziopsis

Author(s) of proposal
Chris Hoess
Name of taxon
Homalosorus, Diplaziopsis
Rank of taxon
Genus
Approximate number of species affected
4
Description of change
The genus Homalosorus Pic.-Serm. is subsumed into an expanded Diplaziopsis C.Chr. to provide a circumscription stable against future evidence about the placement of D. flavoviridis. A diagnosis for the new genus is provided as it is neither identical with that from PPG I nor with the circumscription of M.G. Price.
Reason for change
The genus Diplaziopsis was erected by Christensen in his Index Filicum as a replacement name for Allantodia sensu Wallich. As defined by Christensen, it contained a single species, Diplaziopsis javanica (Blume) C.Chr. (syn. Allantodia brunoniana Wall.), with sausage-shaped sori and indusia along straight parallel veins extending more or less perpendicularly from the costa and becoming reticulate as they approached the margin. This reticulation forms the most noticeable feature differentiating it from Diplazium. Christensen would subsequently recognize a second and very similar species, D. cavaleriana (Christ) C.Chr., within the genus.
In 1935, John Kunkel Small described the genus Homalosorus for a single North American species, Asplenium pycnocarpon Spreng., which he felt could not be placed with either Asplenium, Athyrium, or Diplazium (in which last he included American Deparia). In his diagnosis, he noted the even branching of lateral veins in the pinna, terminating at the sinuses of crenations on the pinnae margin, with regular, almost exactly parallel sori lying along the veins (which fork once from the costa and run parallel, without reticulation). However, he did not validate the genus with a Latin diagnosis. This was corrected by Pichi-Sermolli in 1977, who reiterated Small’s characters. He appears to have been principally concerned with separating it from Diplazium s.s. and did not address Diplaziopsis in his diagnosis.
In 1973, Tryon and Tryon observed in passing a relationship between the species of Homalosorus and Diplaziopsis as described above (which they subsumed in Diplazium) but made no further comment. Kato & Darnaedi noted an even closer relationship between Diplazium flavoviride Alston, a Malesian species, and Diplazium pynocarpon (= Homalosorus pycnocarpos). The two are quite similar in gross morphology, including venation, and in chromosome number and spore character, although they are distinguishable by prominent trophophores, a creeping rhizome, and slightly dimorphic pinnae in H. pycnocarpos. While Kato & Darnaedi preferred to leave these species in a broadly defined Diplazium, they noted their close affinity to Diplaziopsis, including the presence of a V-shaped rachis groove (rather than U-shaped as in Diplazium). This affinity was further developed by M.G. Price, who effected the transfer of D. pycnocarpon and D. flavoviride to Diplaziopsis. Since this abolished the distally-reticulate venation as a character for the genus, Price recircumscribed Diplaziopsis, differentiating it from Diplazium based on its light-colored roots and rhizome, lacking sclerenchyma (rather than dark-colored), brown, concolorous, untoothed scales, and V-shaped rachis groove. However, Price also included two species of Dictyodroma which share distally-reticulate venation with the original concept of Diplaziopsis but which have since been phylogenetically placed in Deparia by Sano et al. and Kuo et al.
A plastid phylogeny of Diplaziopsidaceae by Chunxiang et al. showed D. cavaleriana and D. javanica (as D. brunoniana) to be sister taxa, with Homalosorus basal to the clade encompassing those two species. Unfortunately, while Diplazium flavoviride was cultivated in the Tokyo Botanical Gardens at the time of Kato & Darnaedi’s study, no genetic data from this species has as yet been produced.
By adopting Price’s diagnosis, PPG I implicitly includes Diplazium flavoviride in Diplaziopsis while recognizing Homalosorus. While this is not inconsistent with current phylogeny, the morphological similarity between D. flavoviridis and H. pycnocarpos makes it very difficult to support their separation at the generic level. Two alternative classifications of Diplaziopsidaceae were considered.
One would be to recognize two genera, Diplaziopsis and Homalosorus, the former containing the species with distally-reticulate venation, D. cavaleriana and D. javanica, and the latter containing the one-forking, parallel-veined species D. flavoviridis and H. pycnocarpos, for which separation at the generic level seems untenable. This has the advantage of relatively clear morphological diagnosis. However, the uncertain phylogenetic placement of D. flavoviridis endangers the stability of this classification. If the parallel-veined species form a basal grade rather than a clade, Homalosorus in the sense proposed would not be monophyletic. Furthermore, while the distally-reticulate venation of Diplaziopsis s.s. makes it easy to distinguish from Diplazium, it is insufficient to separate it from the former species of Dictyodroma.
Accordingly, a second alternative is proposed, to place all four species in Diplaziopsis and treat Homalosorus as a junior synonym of that genus, rendering Diplaziopsidaceae monotypic. While Diplaziopsis s.l. is not as morphologically coherent as the two-genus alternative, it is more likely to be stable in light of new phylogenetic evidence.
As the basis of a diagnosis, Sundue & Rothfels noted “white, fleshy roots” as a synapomorphy for Diplaziopsidaceae (Diplaziopsis + Homalosorus). However, this yields an imperfect separation from the former Dictyodroma, e.g., a specimen of Deparia formosana (Kramer, Zogg. & Gassner 7679, Naturalis) notes “roots fleshy” on the label, and one of Deparia heterophlebia (Hennipman 3432, MICH) notes “roots fleshy, greenish”. Nonetheless, this remains an important character in separating Diplaziopsidaceae from almost all similar species.
Price’s diagnosis for Diplaziopsis is here modified to accommodate this distinction. Roots white and fleshy (versus dark in Diplazium and Athyrium), rhizome with brown, concolorous entire scales, rachis groove V-shaped and discontinuous from costal grooves (versus U-shaped and continuous in Diplazium), leaf lamina once-pinnate with lateral pinna veins once-forking and parallel and pinna apex pinnatifid, or once-pinnate with lateral pinna veins reticulate near the margin and terminal pinna conform (versus lamina wholly or apically pinnatifid with pinnatifid apex in the “DI clade” of Kuo et al. in Deparia), veins terminating near but not on the pinna margin, sori long, thick, and indusiate along veins.

Christensen, Carl. Index Filicum  (1906). Copenhagen: H. Hagerup. p. 227 https://www.biodiversitylibrary.org/page/3524304
Chunxiang, Li et al. (2011) Phylogenetic Positions of the Enigmatic Asiatic Fern Genera Diplaziopsis and Rhachidosorus from Analyses of Four Plastid Genes, Amer. Fern J., 101(3): 142-155.
Kato, Masahiro & Dedy Darnaedi (1988) Taxonomic and Phytogeographic Relationships of Diplazium flavoviride, D. pycnocarpon, and Diplaziopsis, Amer. Fern J., 78(3): 77-85. https://doi.org/10.2307/1547626
Kuo, Li-Yaung et al. (2018) Infrageneric Revision of the Fern Genus Deparia (Athyriaceae, Aspleniineae, Polypodiales), Syst. Bot., 43(3): 645-655.
Pichi-Sermolli, Rodolfo E. G. Fragmenta Pteridologiae—VI, Webbia, 31(1): 237-259.
https://doi.org/10.1080/00837792.1977.10670073
Price, Michael G. (1990) Philippine Fern Notes Contr. Univ. Mich. Herb., 17: 267-278.
Sano, Ryosuke et al. (2000) Deparia formosana (Rosenst.) Sano, a New Name for Diplazium formosanum Rosenst. Acta Phytotax. Geobot., 51(1): 17-20.
Small, John Kunkel (1935) Ferns of the Vicinity of New York Lancaster, Pennsylvania: Science Press. p. 80
Sundue, Michael A. & Carl J. Rothfels (2014) Stasis and convergence characterize morphological evolution in eupolypod II ferns, Ann. Bot., 113: 35-54. https://doi.org/10.1093/aob/mct247
Tryon, Alice & Rolla Tryon (1973) Thelypteris in Northeastern North America, Amer. Fern J., 63(3): 65-76. https://doi.org/10.2307/1546181
Wallich, Nathaniel (1830) Plantae Asiaticae Rariores London: Treuttel and Würtz. 1: 44 https://www.biodiversitylibrary.org/page/449536

Reference(s) for publication of the name

Christensen, Carl. Index Filicum  (1906). Copenhagen: H. Hagerup. p. 227 https://www.biodiversitylibrary.org/page/3524304
Pichi-Sermolli, Rodolfo E. G. Fragmenta Pteridologiae—VI, Webbia, 31(1): 237-259.
https://doi.org/10.1080/00837792.1977.10670073

List the numbers of any related issues
No response
Code of Conduct

[X] I agree to follow the PPG Code of Conduct

This is terrible timing - I should have chimed in much sooner in the discussion period. Sorry!! But I would just like to let it be known that I have unpublished molecular data placing D. flavoviride sister to H. pycnocarpos. So that could potentially support a two-genus system, although the proposed treatment would also work.

Oh, now you tell me. :) Having gotten this far, I think I'm happy with lumping, but when you publish, erect subgenera Homalosorus and Diplaziopsis and we can revisit the question in another cycle.

It's painful to admit, but I've been sitting on the data for far too long... thank you @choess for the motivation to get it out!

This is a very last-minute comment... but It sounds like a one-genus classification is preferable both because it is compatible with any conceivable phylogeny, and because both morphological and genetic differences between the narrower genera seem rather minor.

This proposal was voted on during PPG Ballot 12 (voting period July 2024). A total of 68 votes were cast. There were 51 'Yes' votes (75%) and 17 'No' votes (25%). The proposal passes.

It is interesting to note that none of the discussion proposed subgenera instead of splitting.


Fix Header

Update header to match caesars.com/careers/ site

Working on fixing the CSS alignment and removing unnecessary pieces from the header that are no longer needed due to the way Sign In will work

Still need to implement sign in functionality. Waiting on Caesars team for the info


Run integration tests against Yoda: first version

Many thanks @stsnel, that is indeed so helpful.
@qubixes In our testing we will have to make a distinction since indeed a normal user in Yoda should not be able to change any acls on their home group collection. Maybe we can rewrite the test for changing acls so that this is done in a subcollection also for our general iRODS tests.


Error deploying test pod

Hi, I'm trying to do some test using Confidential Containers on a server with Intel SGX. I followed the quickstart to do the installation, but when I try to deploy the test pod with the enclave-cc runtime I get this error:

I did kubectl describe to get more information and seems like it can't get the SGX evidence

I have the attestation module deployed in docker, just like it appears in the quickstart:

Here you can see the log of the kbs container when I try to deploy the pod:

I've also tried to change some parameters of the attestation configuration, but nothing seems to fix this issue. I have the Intel PCCS and Intel AESMD services running.
Any idea where's the issue and how can I solve it?
Thanks in advance

I had the same problem at#212，You solved it？brother @BigThor12

Hi @qiaofu1024 , I still haven't been able to solve the problem.

Hi @qiaofu1024 , I still haven't been able to solve the problem.

can we close this and follow-up in #212


Default participants and split

With the current defaults (no participant checked), at least one interaction with the participant list is necessary to be able to save an expense. I have to "select all" participants almost every time.
Considering there is no use case where saving without any interactions is possible, having the expense split evenly across all group members may be a better default.

I wrote a quick draft of what I imagined in #59. So far I am just assuming that "split evenly with everyone" is the most common use case, without any discussions or metrics to base my assumption on, so I am keen to hear your opinions.

I also thought of this. My main group is with 1 other person, so we are definitely always choosing to split for both.
I, being a self proclaimed coward, was thinking that I would open an issue with a toggle on group level wether to add all or none by default, so it's switchable by group
But my guess is that you would rather have the default being all chosen over none, as well.

Great to hear that my first suggestion (small as it may be) is received so positively!

I would open an issue with a toggle on group level wether to add all or none by default, so it's switchable by group

That was an option I had in mind as well, but I thought it was better to start out with a simpler approach unless we know there is demand for a more sophisticated solution.