CRITICAL: the plugin doesn't work. Files are not uploaded to GCS

Everything worked fine until the latest update and no files can be uploaded since December 22.
Here's some of the outputs from the logs
2023-12-05 11:58:25: â° Event: New Upload (ed589c29-admin-ajax.png)
2023-12-05 11:58:26: ðŸ—’ï¸ Trying Media Title
2023-12-05 11:58:26: ðŸ˜ Title EXIF not found.
2023-12-26 18:53:29: â° Event: New Upload (maxresdefault.jpg)
2023-12-26 18:53:29: ðŸ—’ï¸ Trying Media Title
2023-12-26 18:53:30: ðŸ˜ Title EXIF not found.
2023-12-26 18:55:54: â° Event: New Upload (maxresdefault.jpg)
2023-12-26 18:55:54: ðŸ—’ï¸ Trying Media Title
2023-12-26 18:55:55: ðŸ˜ Title EXIF not found.
2023-12-26 18:56:01: â° Event: New Upload (40M_Money [RO, Press Quality, 2013].pdf)
2023-12-26 18:56:02: ðŸ—’ï¸ Trying Media Title
2023-12-26 18:56:03: ðŸ˜ Title EXIF not found.
2023-12-26 19:17:31: â° Event: New Upload (maxresdefault.jpg)
2023-12-26 19:17:31: ðŸ—’ï¸ Trying Media Title
2023-12-26 19:17:32: ðŸ˜ Title EXIF not found.
2023-12-26 19:20:22: â° Event: New Upload (photo_2023-09-23 20.03.22.jpeg)
2023-12-26 19:20:23: ðŸ—’ï¸ Trying Media Title
2023-12-26 19:20:23: ðŸ˜ Title EXIF not found.

2023/12/26 19:21:17 [error] 108273#108273: *1319477 FastCGI sent in stderr: "PHP message: PHP Warning: exif_imagetype(gs://stateless-moldovacrestina-md/2023/12/d25b3a7d-maxresdefault.jpg): Failed to open stream: "wpCloud\StatelessMedia\StreamWrapper::stream_open" call failed in /www/moldovacrestina_617/public/wp-includes/functions.php on line 3310; PHP message: PHP Warning: file_get_contents(gs://stateless-moldovacrestina-md/2023/12/d25b3a7d-maxresdefault.jpg): Failed to open stream: "wpCloud\StatelessMedia\StreamWrapper::stream_open" call failed in /www/moldovacrestina_617/public/wp-includes/functions.php on line 3332" while reading response header from upstream, client: <IP_ADDRESS>, server: moldovacrestina.md, request: "POST /wp-admin/async-upload.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php8.2-fpm-moldovacrestina.sock:", host: "moldovacrestina.md:47900", referrer: "https://moldovacrestina.md/wp-admin/media-new.php"
2023/12/26 19:20:25 [error] 108273#108273: *1319294 FastCGI sent in stderr: "PHP message: ⏰ Event: New Upload (photo_2023-09-23 20.03.22.jpeg); PHP message: 🗒 Trying Media Title; PHP message: 😭 Title EXIF not found.; PHP message: PHP Warning: exif_imagetype(gs://stateless-moldovacrestina-md/2023/12/475915fb-photo_2023-09-23-200322.jpeg): Failed to open stream: "wpCloud\StatelessMedia\StreamWrapper::stream_open" call failed in /www/moldovacrestina_617/public/wp-includes/functions.php on line 3310; PHP message: PHP Warning: file_get_contents(gs://stateless-moldovacrestina-md/2023/12/475915fb-photo_2023-09-23-200322.jpeg): Failed to open stream: "wpCloud\StatelessMedia\StreamWrapper::stream_open" call failed in /www/moldovacrestina_617/public/wp-includes/functions.php on line 3332" while reading response header from upstream, client: <IP_ADDRESS>, server: moldovacrestina.md, request: "POST /wp-admin/async-upload.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php8.2-fpm-moldovacrestina.sock:", host: "moldovacrestina.md:47900", referrer: "https://moldovacrestina.md/wp-admin/media-new.php"
2023/12/26 19:17:34 [error] 108273#108273: *1318837 FastCGI sent in stderr: "PHP message: ⏰ Event: New Upload (maxresdefault.jpg); PHP message: 🗒 Trying Media Title; PHP message: 😭 Title EXIF not found.; PHP message: PHP Warning: exif_imagetype(gs://stateless-moldovacrestina-md/2023/12/01fe0609-maxresdefault.jpg): Failed to open stream: "wpCloud\StatelessMedia\StreamWrapper::stream_open" call failed in /www/moldovacrestina_617/public/wp-includes/functions.php on line 3310; PHP message: PHP Warning: file_get_contents(gs://stateless-moldovacrestina-md/2023/12/01fe0609-maxresdefault.jpg): Failed to open stream: "wpCloud\StatelessMedia\StreamWrapper::stream_open" call failed in /www/moldovacrestina_617/public/wp-includes/functions.php on line 3332" while reading response header from upstream, client: <IP_ADDRESS>, server: moldovacrestina.md, request: "POST /wp-admin/async-upload.php HTTP/2.0", upstream: "fastcgi://unix:/var/run/php8.2-fpm-moldovacrestina.sock:", host: "moldovacrestina.md:47900", referrer: "https://moldovacrestina.md/wp-admin/media-new.php"

Hello @davidfilat
Can you please provide more details about your System configurations, WordPress version, WP-Stateless settings - which mode do you use, etc.

@planv I'm using the Stateless mode
### wp-core ###

version: 6.4.2
site_language: ro_RO
user_language: ro_RO
permalink: /%postname%/
https_status: true
multisite: false
user_registration: 0
blog_public: 1
default_comment_status: closed
environment_type: production
user_count: 108
dotorg_communication: true

### wp-paths-sizes ###

wordpress_size: 1,67 Go<PHONE_NUMBER> bytes)
uploads_path: gs://<bucket-name>/2023/12
uploads_size: 0,00 o (0 bytes)
themes_path: /www/public/wp-content/themes
themes_size: 92,75 Mo (97251170 bytes)
plugins_path: /www/public/wp-content/plugins
plugins_size: 316,26 Mo (331622432 bytes)
database_size: 1,37 Go<PHONE_NUMBER> bytes)
total_size: 3,44 Go<PHONE_NUMBER> bytes)

### wp-active-theme ###

name: Moldova Crestina (moldovacrestina)
version: 1.1
author: Anonim
author_website: (undefined)
parent_theme: Genesis (genesis)
theme_features: core-block-patterns, menus, post-thumbnails, title-tag, automatic-feed-links, body-open, genesis-inpost-layouts, genesis-archive-layouts, genesis-admin-menu, genesis-import-export-menu, genesis-readme-menu, genesis-customizer-theme-settings, genesis-customizer-seo-settings, genesis-auto-updates, genesis-breadcrumbs, genesis-menus, genesis-structural-wraps, widgets, html5, genesis-responsive-viewport, genesis-footer-widgets, widgets-block-editor
theme_path: /www/public/wp-content/themes/moldovacrestina
auto_update: Auto-updates are not available for this theme.
genesis_recommendations: This theme uses theme supports that are no longer required in Genesis: "genesis-responsive-viewport" theme support can be removed

### wp-parent-theme ###

name: Genesis (genesis)
version: 3.4.0
author: StudioPress
author_website: https://www.studiopress.com/
theme_path: /www/public/wp-content/themes/genesis
auto_update: Enable update checks at Appearance → Customize → Theme Settings → Updates.

### wp-themes-inactive (4) ###

Twenty Twenty-Four: version: 1.0, author: echipa WordPress, Actualizările automate sunt dezactivate
Twenty Twenty-One: version: 2.0, author: echipa WordPress, Actualizările automate sunt dezactivate
Twenty Twenty-Three: version: 1.3, author: echipa WordPress, Actualizările automate sunt dezactivate
Twenty Twenty-Two: version: 1.6, author: echipa WordPress, Actualizările automate sunt dezactivate

### wp-mu-plugins (2) ###

Kinsta Must-use Plugins: version: 3.0.1, author: Kinsta Team
WP Password bcrypt: version: 1.0, author: Roots

### wp-plugins-active (55) ###

ACF Content Analysis for Yoast SEO: version: 3.1, author: Thomas Kräftner, ViktorFroberg, marol87, pekz0r, angrycreative, Team Yoast, Actualizările automate sunt dezactivate
Admin Columns: version: 4.6.1, author: AdminColumns.com, Actualizările automate sunt dezactivate
Advanced Custom Fields Multilingual: version: 2.0.5, author: OnTheGoSystems, Actualizările automate sunt dezactivate
Advanced Custom Fields PRO: version: 6.2.4, author: WP Engine, Actualizările automate sunt dezactivate
Advanced Database Cleaner PRO: version: 3.2.3, author: Younes JFR., Actualizările automate sunt dezactivate
Author Image: version: 4.9.3, author: Denis de Bernardy & Mike Koepke, Actualizările automate sunt dezactivate
Automatic Video Posts: version: 5.2.7, author: Ternstyle LLC (Matthew Praetzel), Actualizările automate sunt dezactivate
Auto Upload Images: version: 3.3.2, author: Ali Irani, Actualizările automate sunt dezactivate
Category Order and Taxonomy Terms Order: version: 1.7.9, author: Nsp-Code, Actualizările automate sunt dezactivate
Classic Editor: version: 1.6.3, author: WordPress Contributors, Actualizările automate sunt dezactivate
Clickable Links: version: 1.7.0, author: Uriel Wilson, Actualizările automate sunt dezactivate
Dashboard Columns: version: 1.3.1, author: Polygon Themes, Actualizările automate sunt dezactivate
Disable Responsive Images Complete: version: 2.6.1, author: Jeff Starr, Actualizările automate sunt dezactivate
Easy FancyBox: version: 1.9.5, author: RavanH, Actualizările automate sunt dezactivate
ElasticPress: version: 5.0.1, author: 10up, Actualizările automate sunt dezactivate
ElasticPress Proxy: version: 1.0.0, author: 10up | ElasticPress.io, Actualizările automate sunt dezactivate
Facebook Video Embed: version: 1.0.2, author: Irfan Ansari, Actualizările automate sunt dezactivate
Google Analytics for WordPress by MonsterInsights: version: 8.23.1, author: MonsterInsights, Actualizările automate sunt dezactivate
Hide Title: version: 1.0.9, author: Dojo Digital, Actualizările automate sunt dezactivate
Jetpack: version: 12.9.3, author: Automattic, Actualizările automate sunt dezactivate
Notify Admins: version: 1.0, author: Dan Lapteacru, Actualizările automate sunt dezactivate
Parent Category Toggler: version: 1.3.4, author: Ben Lobaugh, Actualizările automate sunt dezactivate
PDF Embedder: version: 4.6.4, author: WP PDF Embedder Team, Actualizările automate sunt dezactivate
Post Type Switcher: version: 3.2.1, author: Triple J Software, Inc., Actualizările automate sunt dezactivate
PublishPress Future: version: 3.1.6, author: PublishPress, Actualizările automate sunt dezactivate
Simple Blog Stats: version: 20231025, author: Jeff Starr, Actualizările automate sunt dezactivate
Simple Custom Post Order: version: 2.5.7, author: Colorlib, Actualizările automate sunt dezactivate
Site Kit by Google: version: 1.116.0, author: Google, Actualizările automate sunt dezactivate
Social Warfare: version: 4.4.4, author: Warfare Plugins, Actualizările automate sunt dezactivate
Social Warfare - Pro: version: 4.4.4, author: Warfare Plugins, Actualizările automate sunt dezactivate
SVG Support: version: 2.5.5, author: Benbodhi, Actualizările automate sunt dezactivate
TablePress: version: 2.2.4, author: Tobias Bäthge, Actualizările automate sunt dezactivate
TablePress Extension: Automatic URL conversion: version: 1.3, author: Tobias Bäthge, Actualizările automate sunt dezactivate
TablePress Extension: Responsive Tables: version: 1.8, author: Tobias Bäthge, Actualizările automate sunt dezactivate
Ultimate Category Excluder: version: 1.7, author: Marios Alexandrou, Actualizările automate sunt dezactivate
User Role Editor: version: 4.64.1, author: Vladimir Garagulya, Actualizările automate sunt dezactivate
Webcraftic Cyrlitera – transliteration of links and file names: version: 1.1.8, author: Webcraftic<EMAIL_ADDRESS>Actualizările automate sunt dezactivate
WP-Stateless: version: 3.3.0, author: UDX, Actualizările automate sunt dezactivate
WPForms: version: <IP_ADDRESS>, author: WPForms, Actualizările automate sunt dezactivate
WPForms AJAX Submit: version: 1.2.4, author: John A. Huebner II, Actualizările automate sunt dezactivate
WPForms Brevo: version: 1.3.0, author: WPForms, Actualizările automate sunt dezactivate
WPForms Form Pages: version: 1.5.1, author: WPForms, Actualizările automate sunt dezactivate
WPForms Mailchimp: version: 2.3.0, author: WPForms, Actualizările automate sunt dezactivate
WPForms Surveys and Polls: version: 1.9.0, author: WPForms, Actualizările automate sunt dezactivate
WP Mail SMTP: version: 3.11.0, author: WP Mail SMTP, Actualizările automate sunt dezactivate
WPML CMS Nav: version: 1.5.5, author: OnTheGoSystems, Actualizările automate sunt dezactivate
WPML ElasticPress: version: 2.0.3, author: OnTheGoSystems, Actualizările automate sunt dezactivate
WPML Media: version: 2.7.3, author: OnTheGoSystems, Actualizările automate sunt dezactivate
WPML Multilingual CMS: version: 4.6.8, author: OnTheGoSystems, Actualizările automate sunt dezactivate
WPML SEO: version: 2.1.0, author: OnTheGoSystems, Actualizările automate sunt dezactivate
WPML Sticky Links: version: 1.5.4, author: OnTheGoSystems, Actualizările automate sunt dezactivate
WPML String Translation: version: 3.2.8, author: OnTheGoSystems, Actualizările automate sunt dezactivate
Yoast SEO: version: 21.7, author: Team Yoast, Actualizările automate sunt dezactivate
Yoast SEO Premium: version: 21.7, author: Team Yoast, Actualizările automate sunt dezactivate
Youtube Playlist Video Player: version: 1.9.0, author: Rik de Vos, Actualizările automate sunt dezactivate

### wp-plugins-inactive (4) ###

Elasticpress Custom REST Endpoing for Moldova Creștină: version: 1.0, author: David Filat, Actualizările automate sunt dezactivate
Media File Renamer: Rename Files (Manual, Auto, AI): version: 5.7.8, author: Jordy Meow, Actualizările automate sunt dezactivate
Quick Featured Images Pro: version: 9.3.0, author: Martin Stehle, Actualizările automate sunt dezactivate
ShortPixel Image Optimizer: version: 5.5.2, author: ShortPixel - Convert WebP/AVIF & Optimize Images, Actualizările automate sunt dezactivate

### wp-media ###

image_editor: WP_Image_Editor_GD
imagick_module_version: 1690
imagemagick_version: ImageMagick 6.9.10-23 Q16 x86_64 20190101 https://imagemagick.org
imagick_version: 3.7.0
file_uploads: 1
post_max_size: 128M
upload_max_filesize: 128M
max_effective_size: 128 Mo
max_file_uploads: 20
gd_version: 2.3.3
gd_formats: GIF, JPEG, PNG, WebP, BMP, AVIF, XPM
ghostscript_version: unknown

### wp-server ###

server_architecture: Linux 5.4.0-1116-gcp x86_64
httpd_software: nginx/1.25.2
php_version: 8.2.8 64bit
php_sapi: fpm-fcgi
max_input_variables: 10000
time_limit: 300
memory_limit: 512M
admin_memory_limit: 1024M
max_input_time: 300
upload_max_filesize: 128M
php_post_max_size: 128M
curl_version: 7.68.0 OpenSSL/1.1.1f
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: true
current: 2023-12-26T21:10:23+00:00
utc-time: Tuesday, 26-Dec-23 21:10:23 UTC
server-time: 2023-12-26T23:10:15+02:00

### wp-database ###

extension: mysqli
server_version: 10.11.5-MariaDB-1:10.11.5+maria~ubu2004
client_version: mysqlnd 8.2.8
max_allowed_packet: 33554432
max_connections: 10

### wp-constants ###

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /www/public/wp-content
WP_PLUGIN_DIR: /www/public/wp-content/plugins
WP_MEMORY_LIMIT: 512M
WP_MAX_MEMORY_LIMIT: 1024M
WP_DEBUG: false
WP_DEBUG_DISPLAY: false
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: Nedefinită
WP_DEVELOPMENT_MODE: undefined
DB_CHARSET: utf8
DB_COLLATE: utf8_unicode_ci

### wp-filesystem ###

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
mu-plugins: writable

### ep-last-sync ###

method: WP Dashboard
is_full_sync: No
start_date_time: 2023/11/18 12:27:14 pm
end_date_time: 2023/11/18 12:27:18 pm
total_time: 0 ore, 0 minute, 5 secunde
total: 98
synced: 98
skipped: undefined
failed: undefined
errors:
trigger: manual
final_status: success

### genesis ###

theme_version: 3.3.1
db_version: 3301
first_version: 2.0.2
update: 1
site_layout: content-sidebar
blog_title: image
breadcrumb_posts_page: 1
content_archive: full
image_size: thumbnail
image_alignment: alignleft
posts_nav: numeric
blog_cat_num: 5
upgrade: 1
footer_text: [footer_copyright before="Copyright "] · [footer_childtheme_link before="" after=" on"] [footer_genesis_link url="https://www.studiopress.com/" before=""] · [footer_wordpress_link] · [footer_loginout]
entry_meta_before_content: [post_date] by [post_author_posts_link] [post_comments] [post_edit]
entry_meta_after_content: [post_categories] [post_tags]

### wpforms ###

version: <IP_ADDRESS>
lite: februarie 1, 2018 at 22:05
pro: noiembrie 27, 2016 at 10:53
upload_dir: Writable
total_forms: 38
total_entries: 13649
license_status: Valid
license: Plus
license_location: option

After a little more investigation I also found this error
 in apply_filters called at ? (?)
 in call_user_func_array called at /www/moldovacrestina_617/public/wp-content/plugins/post-expirator/src/Framework/WordPress/Facade/HooksFacade.php (44)
 in PublishPress\Future\Framework\WordPress\Facade\HooksFacade::applyFilters called at /www/moldovacrestina_617/public/wp-content/plugins/post-expirator/services.php (108)
 in {closure} called at /www/moldovacrestina_617/public/wp-content/plugins/post-expirator/src/Core/DI/Container.php (90)
 in PublishPress\Future\Core\DI\Container::get called at /www/moldovacrestina_617/public/wp-content/plugins/post-expirator/services.php (119)
 in {closure} called at /www/moldovacrestina_617/public/wp-content/plugins/post-expirator/src/Core/DI/Container.php (90)
 in PublishPress\Future\Core\DI\Container::get called at /www/moldovacrestina_617/public/wp-content/plugins/post-expirator/post-expirator.php (126)
 in PublishPress\Future\{closure} called at /www/moldovacrestina_617/public/wp-includes/class-wp-hook.php (324)
 in WP_Hook::apply_filters called at /www/moldovacrestina_617/public/wp-includes/class-wp-hook.php (350)
 in WP_Hook::do_action called at /www/moldovacrestina_617/public/wp-includes/plugin.php (531)
 in do_action called at /www/moldovacrestina_617/public/wp-settings.php (643)
 in require_once called at /www/moldovacrestina_617/public/wp-config.php (51)
 in require_once called at /www/moldovacrestina_617/public/wp-load.php (50)
 in require_once called at /www/moldovacrestina_617/public/wp-blog-header.php (13)
 in require called at /www/moldovacrestina_617/public/index.php (17)

@planv I also have to mention that downgrading to version 3.2.5 or 3.2.4 didn't help

I have some progress: switching to ephemeral mode seems to have solved the issue.

Stateless and Ephemeral modes use different methods to upload files.
If your server allows you to save files, then it’s better to use the Stateless mode.

My server allows me, but the stateless mode simply doesn't work
On Dec 27, 2023 at 15:44 +0200, Vladimir @.***>, wrote:

Stateless and Ephemeral modes use different methods to upload files.
If your server allows you to save files, then it’s better to use the Stateless mode.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

My server allows me, but the stateless mode simply doesn't work

Sorry, I mean better to use mode Ephemeral.

In that case I'll leave it as it is. But it is strange that it worked just fine before December 22...
thank you for your support!
On 27 Dec 2023 at 15:58 +0200, Vladimir @.***>, wrote:

My server allows me, but the stateless mode simply doesn't work
Sorry, I meant better to use mode Ephemeral.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


 Delete the others, including these Instructions.
{{cask_file}} represents the cask file you’re submitting/editing (if applicable).
If there’s a checkbox you can’t complete for any reason, that’s OK. Just explain in detail why you weren’t able to do so.

Changes to a cask
Editing an existing cask

[ ] Commit message includes cask’s name (and new version, if applicable).
[ ] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} left no offenses.

Adding a new cask

[ ] Checked there aren’t open pull requests for the same cask.
[ ] Checked there aren’t closed issues where that cask was already refused.
[ ] When naming the cask, followed the token reference.
[ ] Commit message includes cask’s name.
[ ] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} left no offenses.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.

Changes to the core

[ ] Followed hacking.md.

Next time, please follow the instructions.

Thank you for the contribution. It needed some fixes, so they were made in 53e16a25794dcd6ad4dd63ab1859f4a829567e4c. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


Performance attributes of repo

Since it seems like the main purpose of this seed/starter is Angular Universal, Webpack2, and AOT; I feel like the README should include some performance stats of the current build of the starter. Since it does not have this info yet, I wanted to share what I'm seeing on my machine atm.

Times listed for No throttling / Regular 3G.

Dev Mode
npm start

29 requests
5.8 MB
1300ms / 66000ms DOMContentLoaded
1350ms / 66000ms load

Universal
npm run universal

16 requests
363 KB
928ms / 4480ms DOMContentLoaded
973ms / 5020ms load

AOT mode
npm run compile + npm run prodserver

16 requests
301 KB
432ms / 3530ms DOMContentLoaded
495ms / 3930ms load

Universal + AOT
npm run universal:aot or npm run compile:universal+ npm run prodserver

16 requests
392 KB
494ms / 4410ms DOMContentLoaded
535ms / 5030ms load

Tests run on

Chrome 57.0.2951.0 canary (64-bit)
MacBook Pro (Retina, 15-inch, Mid 2014)
2.8 GHz Intel Core i7
16 GB 1600 MHz DDR3
OS X El Capitan 10.11.6 (15G1212)
NodeJS 6.7.0

Now I know that Universal and AOT are still undergoing a lot of breaking changes and needed improvements, but I found it a little odd that the combination was slower than the build with AOT alone.
Since the angular-cli isn't supporting Universal + AOT yet, I was looking to find a solid seed for Universal, AOT, Webpack2, Material2, etc. and this one seems to be the closest that I can find which isn't broken.
But with the numbers above, I wonder if I should even bother with Universal at this point. Then I thought, well it should help get that initial paint a lot faster. But on anything 3G+, the time between initial paint and interactivity is under 50ms and isn't even noticeable. If I drop down to Regular 2G, then I do see the initial DOM loaded for about 2s before the page is interactive and rendered properly.
Perhaps part of this issue is that the app doesn't have an appShell (it's just a white Loading... page), but either way I'm not sure that I should go to the extra trouble of running a NodeJS server for Universal at this point rather than just hosting a client-only app in Firebase. SEO is something that I really need, but I'm not convinced that Universal will work properly here and deliver the desired results.
Maybe I should just stick with AOT until Universal gets better support from Angular core (in progress). It's nice that this seed makes that a well supported option. Thanks for your hard work and sharing what's working for you!
PS. This is the first time I've tried this repo, please let me know if I should be running different commands for one of the combinations. I tried to go by what the README suggested.

@Splaktar you're correct in the fact that Universal is underperforming, but that's mostly because we're only spitting it out in JIT mode instead AOT. Personally, I've been leaning towards using AOT only in my real projects mostly because of the current incompatibility with Material. Until they fully transfer Universal to the main angular branch and start testing against it, it's support will lag behind the rest of angular.
There does appear to be ways to get AOT running with Universal (at least there seemed to be a few weeks ago), I just haven't gotten around to it yet as I will have to make a ton of changes and I haven't been using Universal in my real project, so it isn't a top priority for me. Universal is stuck on Angular 2.1.2 as far as compatibility and you have to do some hacks to get it to work with AOT, so the current support there is not great.

@Splaktar that's some great data! It would be awesome if you could write a benchmark script (using perhaps Protractor) that automatically generates a report like that. Add it as a command in the package.json and submit a pull request.

Unfortunately, that is not something that I have cycles to work on at this time. I'm also not sure how to capture the correct perf/size metrics with Protractor. I am going with a similar approach to that mentioned above, just using AOT and waiting for Universal to be merged into core and stabilized.

@qdouble Now that Universal is part of Angular 4, is this issue still relevant ?

@keenkiran actually, I'll close. Perf is such a specific element that if we are not comparing apples to apples it does become a bit irrelevant.


Fix wrong image route in production build

Description
In production build, images larger than 10,000 bytes generates wrong
path and it generates 404 error.
Related issue is here : #1328

Changes/Tasks

[ ] Changed code

Motivation and Context

Screenshots (if appropriate):

Types of changes

[ ] Refactoring/add tests (refactoring or adding test which isn't a fix or add a feature)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] I have updated the documentation accordingly
[ ] I have updated the CHANGELOG with a summary of my changes
[ ] My changes have tests around them

M
Vào 10:41, Th 4, 20 thg 5, 2020 Sangwon Choi<EMAIL_ADDRESS>đã
viết:

Description
In production build, images larger than 10,000 bytes generates wrong
path and it generates 404 error.
Related issue is here : #1328
https://github.com/react-static/react-static/issues/1328
Changes/Tasks

Changed code

Motivation and Context Screenshots (if appropriate): Types of changes

Refactoring/add tests (refactoring or adding test which isn't a fix
or add a feature)
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing
functionality to not work as expected)

Checklist:

I have updated the documentation accordingly
I have updated the CHANGELOG with a summary of my changes
My changes have tests around them

You can view, comment on, or merge this pull request online at:
https://github.com/react-static/react-static/pull/1425
Commit Summary

Fix wrong image route in production build

File Changes

M packages/react-static/src/static/webpack/rules/fileLoader.js
https://github.com/react-static/react-static/pull/1425/files#diff-d44ecb9574546a6551bd0bbc1eeacc94
(1)

Patch Links:

https://github.com/react-static/react-static/pull/1425.patch
https://github.com/react-static/react-static/pull/1425.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/react-static/react-static/pull/1425, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN55CQAPN6A4BRYE3NF5FY3RSNGO7ANCNFSM4NFRZKZA
.

@SleeplessByte I added this to CHANGELOG.md


Upgrade to 18.31.2 Destroys Cluster IAM Roles and Worker IAM Roles

Description
I've did some reading on a couple of issues where people raise this exact same query, but even though I follow the examples provided on those threads, I still only see the destruction of Cluster IAM role and not the creation of them.
We are upgrading from 17.x to 18.31.2. We already have the Cluster IAM Role and Worker IAM Role created in IAM and we want to continue using them if possible. We want to avoid having to recreate the cluster at all costs.
The code:
module "eks_tooling" {
  source  = "terraform-aws-modules/eks/aws"
  version = "18.31.2"

  prefix_separator                       = ""
  create_iam_role = false
  iam_role_arn = "arn:aws:iam::$ACCOUNT_NUMBER:role/$ROLE_NAME"
  # iam_role_use_name_prefix = false

Even with the above where we specify the arn of the Role that already exists for the Cluster, we see:
  # module.k8s-cluster-tooling.module.eks_tooling.aws_iam_role.cluster[0] will be destroyed
  # (because aws_iam_role.cluster is not in configuration)

I've followed the steps here with regards to mving the resource from aws_iam_role.cluster[0] to aws_iam_role.this[0] but it still tries to delete it with the following output
  # module.k8s-cluster-tooling.module.eks_tooling.aws_iam_role.this[0] will be destroyed
  # (because index [0] is out of range for count)

I tried to add these lines and it doesn't do anything but destroy the IAM Role.
I can't really seem to win with this, if I specify create_iam_role as false and give it the existing role arn, it tries to delete it because "it does not exist in configuration", and if I perform a terraform mv to rename it to this[0], it complains and says that index[0] is out of range for count because I've not set create_iam_role to true. and if i do set it to true, it tries to change the properties of the IAM role that I performed the terraform mv on, which leads to the control plane being recreated because the IAM role has changed.
We are using version 1.4.2 of Terraform.
Lastly, this also is the same for the worker IAM Roles, I've specified not to create the role and use the existing one and it goes and it still destroys the existing Role for that ARN anyways and all of the policies attached and doesn't recreate it anywhere. Although I'm less bothered with the workers as we can create the IAM role fresh for those as most things node related aren't destructive to the cluster and are normally ephemeral anyways.

Just going through this myself.
Set create back to true and then move.
terraform state mv  'module.eks.aws_iam_role.cluster[0]' 'module.eks.aws_iam_role.this[0]'

@reedjosh  Yep, we've tried that as noted here:

"I can't really seem to win with this, if I specify create_iam_role as false and give it the existing role arn, it tries to delete it because "it does not exist in configuration", and if I perform a terraform mv to rename it to this[0], it complains and says that index[0] is out of range for count because I've not set create_iam_role to true. and if i do set it to true this performs a recreation of the cluster."

...because I've not set create_iam_role to true

What you've written is contradictory.
I'm saying to set it to true and then try.
If you have tried setting it to true and the state move still doesn't work, then fine, but your wording is that you have it set to false when running the move command.

Yep, but the next sentence later is "and if i do set it to true, it tries to change the properties of the IAM role that I performed the terraform mv on, which leads to the control plane being recreated because the IAM role has changed.". Either way, whether create_iam_role is true or false the Cluster is recreated

I see. Yeah, if the role's drifted then I guess your stuck. Good luck, and hope you find a solution. : )

I'm not sure if the role has drifted as it was created with previous versions of the EKS module, and we definitely don't externally modify any resources that are provisioned with Terraform. I was somewhat hoping there was a bug for our case.... but I'm starting doubt that the longer we look at it

I tried about a half hour ago with a similar situation, and I had luck giving it the role arn w/create = false. One thing I did that I'm not sure would change anythign was to comment out the   prefix_separator  = "" field.
IDK, but yeah it seems many issues are just not being addressed by the maintainers lately.
They're probably mostly volunteers? IDK
I'm looking pretty closely at CrossPlane myself.

we are here - the issues are not actionable

Can you please elaborate though?
Here's my issue from 5 days ago. I did try to provided the requested details.
https://github.com/terraform-aws-modules/terraform-aws-eks/issues/2553
I appreciate your response. But without additional input we don't know what's makes our particular issues not actionable.

done - left a comment 😃

almost all of these issues the users have deliberately deleted the bit about provided a reproduction so we can properly triage and troubleshoot - but then ya'll go on that nobody is maintaining or providing support. I don't know, seems odd to me 😬

Also @ChrisJBurns , I personally had better luck jumping to v19.12.0 directly. I'd suggest doing the same.
v18 made a lot of security group assumptions around node groups (not bad ones) and was really an oddball release ver.
v19 is actually easier to transition to.

v18 made a lot of security group assumptions around node groups (not bad ones) and was really an oddball release ver.

You mean we took user feedback that security groups are too permissive and then we took further feedback that people don't know what ports their applications typically use to communicate on? I think its a bit harsh to call these things "oddball releases"

@reedjosh do you know Adam Cushner or Lee Winikor (sorry - looked and saw you were @ Ripple)?

You mean we took user feedback that security groups are too permissive and then we took further feedback that people don't know what ports their applications typically use to communicate on? I think its a bit harsh to call these things "oddball releases"

Please don't take anything I'm saying offensively. I actually think a security group per node group is great. It's just really difficult to transition to v18. And most of those changes were backed out in v19. In that regard v18 is a bit of an oddball.

the users have deliberately deleted the bit about provided a reproduction.

I'll check my issue shortly, but I know for me there's 2 main hurdles there.
1). When filing an issue against this repo there are just a lot of asks. They're all probably super reasonable, but I'm actually fairly new to Terraform, and it's hard for me to follow all the details. I do understand you may need those details and you cannot hand hold everyone on this.
2). A lot of my code has stuff I'd have to . In my issue in particular I tried to give the minimal relevant code, but I also understand it may not be enough to reproduce.

@reedjosh do you know Adam Cushner or Lee Winikor (sorry - looked and saw you were @ Ripple)?

I do not, and they don't show on Slack. Interesting 🤔

@reedjosh Yep, we were aware that there is definitely a "you're on your own" attitude to some degree because every use case is different, so I agree with the maintainers of the module in that sense because it's impossible for them to know all of the different permutations of installations. I guess I raised the issue incase I'd stumbled on the possible chance there was a bug (or someone has run into it before), before having to accept that if we wanted to upgrade we had to recreate all clusters.
In general the changes in v18 are actually good in the sense we get to have a bit more control around the node groups etc and we love the IRSA support, the only kicker for us is the IAM role that forces a replacement of the control plane. I'll see if we can upgrade to 19 and see if that makes any difference in the amount of changes.
Perhaps a Slack/Discord channel be setup for queries that could just be a simple ask like the question I've asked here https://github.com/terraform-aws-modules/terraform-aws-eks/issues/2536 ?

my bad 🙈 - Ripple != Rippling
In terms of the issue templates - yes, we sometimes can triage with minimum information but more times than not, a repro is required. Its just the nature of Terraform where we need to start where you are and venture down the same path as you to see what you are encountering and why

and we love the IRSA support

then you'll love IRSAv2 where we are aiming to simplify the user experience. You can check out some of the initial mock-ups here - feedback and inputs are welcomed (this is all experimental, it does not work yet today - just FYI)
https://github.com/clowdhaus/terraform-aws-irsa-v2

@reedjosh (cc @bryantbiggs just because my case may stick in your mind for future debugging sessions)
So, just tried this and the config that works for me is the following:
  prefix_separator                       = ""
  create_iam_role = true
  iam_role_name = "ROLE_NAME"
  iam_role_arn = "ROLE_ARN" # dont think this is needed anymore
  iam_role_use_name_prefix = false

So I think what's happening is that when I told it not to create the iam role with create_iam_role false, it basically tried to delete both aws_iam_role.cluster[0] because it doesn't exist in the config anymore because its been removed in 18.0.0, and when I do the terraform state mv aws_iam_role.cluster[0] aws_iam_role.cluster.this[0], it also tries to destroy aws_iam_role.this[0] because create_iam_role is set to false so the count doesn't get set.
It's only when I set the create_iam_role to true and give it the iam_role_name of the existing IAM role that exists, that I manage to "trick" it into not creating it, but just updating it with the stuff that's missing. This then means the IAM role hasn't been destroyed and the control plane doesn't get affected.
I say all this, I've only done a plan, not an apply, I still have to look through the changes that it's making with regards to the policies that its removing.. but positive so far

Am closing because I resolved with my above comment.


Maps CDA->FHIR generate "v3:value" for some elements

Examples:
MedicationStatement.dosage.sequence:
<sequence v3:value="1"/>
(e.g. input\generated-files\ch-emed-2-3-MedicationTreatmentPlan.xml,
input\generated-files\ch-emed-2-7-MedicationCard.xml)
MedicationDispense.dosageInstruction.sequence:
<sequence v3:value="1"/>
(e.g. input\generated-files\ch-emed-2-4-MedicationDispense.xml)
MedicationRequest.dispenseRequest.numberOfRepeatsAllowed:
<numberOfRepeatsAllowed v3:value="2"/>
(e.g. input\generated-files\ch-emed-2-6-MedicationPrescription.xml)
Map: CdaChEmedToBundle
group DosageInstructionsEntryDosageChange
entry.sequenceNumber as sequenceNumber -> dosage.sequence = sequenceNumber "sequenceNumber";

group PrescriptionItemEntryContentModule
src.repeatNumber as repeatNumber -> medicationRequest.dispenseRequest as dispenseRequest then {
    repeatNumber -> dispenseRequest.numberOfRepeatsAllowed = repeatNumber "repeatNumber";
} "repeats";

issue fixing verified


Wrong kernel started

I have a problem opening an .ipynb file.
In the ipynb file:
 "metadata": {
  "kernelspec": {
   "display_name": "Python 2",
   "language": "python",
   "name": "python2"
  },

"jupyter kernelspec list" gives:
  freecad_kernel    /home/gael/.local/share/jupyter/kernels/freecad_kernel
  python2           /home/gael/.local/share/jupyter/kernels/python2
  python3           /home/gael/.local/share/jupyter/kernels/python3

When I open the ipynb file, a FreeCAD window appears. This is the beginning of the log
NotebookEditor created for /home/gael/11-projects/2015-taros_demo/experiments/notebooks/test.ipynb
notebook-editor.js:258 kernelGateway.stderr [KernelGatewayApp] The Jupyter Kernel Gateway is running at: http://localhost:8892

notebook-editor.js:262 Kernel:  freecad_kernel
notebook-editor.js:258 kernelGateway.stderr INFO:tornado.access:200 GET /api/kernelspecs?1458219661160 (<IP_ADDRESS>) 184.27ms
...

In the definition of freecad_kernel (kernel.json), I have "language": "python".
The notebook was saved within the web browser launched from jupyter-notebook.
I would love to see atom-notebook running. It looks great and I don't like editing in the browser. Thanks for providing it! Thank you helping me solving this issue!

Hi @galou. This is peculiar indeed. I would take a look at this line: https://github.com/jupyter/atom-notebook/blob/master/lib/notebook-editor.js#L261. In Atom, you can open the dev tools and set a breakpoint at this point in the execution (when opening a notebook file) and inspect the value of spec and kernelSpecs.kernelspecs to try to understand what it's spawning freecad kernel vs. python.

I tried to modify notebook-editor.js without success. When I load the module as development module I receive the error Cannot find module 'pathwatcher'. What I did was
cd $rep_path
git clone https://github.com/jupyter/atom-notebook.git jupyter-notebook
cd ~/.atom/dev/packages
ln -s $rep_path/jupyter-notebook
atom -d

So far, my modifications:
diff --git a/lib/notebook-editor.js b/lib/notebook-editor.js
index d3bfe38..d576e45 100644
--- a/lib/notebook-editor.js
+++ b/lib/notebook-editor.js
@@ -244,6 +244,7 @@ export default class NotebookEditor {
     }

     launchKernelGateway() {
+      let name = this.state.getIn(['metadata', 'kernelspec', 'name']);
       let language = this.state.getIn(['metadata', 'kernelspec', 'language']);
       portfinder.basePort = 8888;
       portfinder.getPort({host: 'localhost'}, (err, port) => {
@@ -258,17 +259,34 @@ export default class NotebookEditor {
           console.log('kernelGateway.stderr ' + data);
           if (data.toString().includes('The Jupyter Kernel Gateway is running at')) {
             getKernelSpecs({baseUrl: `http://localhost:${port}`}).then((kernelSpecs) => {
-              let spec = Object.keys(kernelSpecs.kernelspecs).find(kernel => kernelSpecs.kernelspecs[kernel].spec.language === language);
-              console.log('Kernel: ', spec);
-              if (spec) {
+              let kernel_name = Object.keys(kernelSpecs.kernelspecs).find(kernel => kernelSpecs.kernelspecs[kernel].name === name);
+              let spec;
+              if (kernel_name) {
+                spec = kernelSpecs.kernelspecs[kernel_name].spec;
+              }
+              console.log('Kernel (found by name): ', kernel_name);
+              if (spec && spec.language === language) {
                 startNewKernel({
                   baseUrl: `http://localhost:${port}`,
                   wsUrl: `ws://localhost:${port}`,
-                  name: spec
+                  name: kernel_name
                 }).then((kernel) => {
                   this.session = kernel;
                 });
               }
+              else {
+                let spec = Object.keys(kernelSpecs.kernelspecs).find(kernel => kernelSpecs.kernelspecs[kernel].spec.language === language);
+                console.log('Kernel (found by language): ', spec);
+                if (spec) {
+                  startNewKernel({
+                    baseUrl: `http://localhost:${port}`,
+                    wsUrl: `ws://localhost:${port}`,
+                    name: spec
+                  }).then((kernel) => {
+                    this.session = kernel;
+                  });
+                }
+              }
             });
           }
         });

This is my first experience with Javascript and plugin development with Atom. I'm stuck right now. I tried to first load a kernel by name (while checking the language) and then, if unsuccessful, by language.

Could someone help me further with this improvement?
Thanks!

@galou Thanks for taking a stab at this.
First, you will want to follow the dev install instructions (that's why you are seeing Cannot find module 'pathwatcher').
After that, you should be able to test you changes within Atom (be sure to reload Atom). You can always switch back to Atom's installed version of atom-notebook by running apm unlink in your atom-notebook directory.


Chore: Better Makefile clean target

Description

make clean should get the repository to the same state as it is after the fresh git checkout.
Additional context

Issue reference

coverage: 78.698%. remained the same
when pulling 04de9f315cb56f4891bd2634930edb13c8e6364a on chore/make-clean-repo
into 497de3990718f6a759ddec78115ca19314b20338 on main.


Show information about active, open projects.

If a project has tasks and is open to all OSM users, it should be possible to see analytics and such, even if the project is not set to "visible" and publicized.
A quick fix would be to restrict non visible projects to a small number of users (2 or 3?). Another way to do it would be to reorganize the UI around some other concept, like "Publicized" or whatever, where there is a central landing page for each project that has info about it, visible to anyone that might complete a task for the project.

All challenges are by design open to all to inspect and contribute to. It's up to the challenge author if they want to make the challenge discoverable (meaning it's displayed on the map + shows up in search results) but even if it's not, you can retrieve its details through the API easily.
Projects don't have users, just owners. Challenges have a count of how many users have participated, but I am not sure what limiting that number would solve?
I'm not saying there's not an issue here, but genuinely trying to find out what the problem is that you are looking to address. Looking forward to discussing more.
Bears on #214

(Nearly) complete information about a project should be discoverable by browsing the website. Right now, if I go to http://maproulette.org/map/2396/ I get redirected to an item, which makes sense, but then there is nothing about the project exposed, at least nothing that I can find. If I click around and click on "view metrics", I get sitewide metrics, rather than the project metrics I expect. So one part of it is that the discoverability setting shouldn't hide the metrics.
I'm proposing something like exposing a url like http://maproulette.org/info/2396, having a link to that page available in a fairly direct way from the item pages, and then listing the project owner and links to the analytics  and whatever else might make sense on that page. It'd be a good place for further documentation that doesn't fit into the item prompts.
The page would probably list information that is already available by clicking the right item on the right menu, the idea is to have a clear place where the details of a project are collected together for viewing.


Shutter target position is inverted

Hello, it seems to me that the target position between Loxone and Homebridge is opposite. In Homebridge 0% means closed, in Loxone 0% means open. Does that make sense or does it follow a logic?
Best regards
Sven

+1

THX; I think I get the point. "plus one" solves the problem, but cause and doubt remain. I'll close the ticket anyway and hope the answer helps the world.

@x-sven I don’t think that you understood my +1. It means I’m also complaining about that, because it works exactly opposite to the rest of the components, but cannot solve it.
I upvoted 😉


Package Initialization Error

Diagnostics
Request: GET https://api.teletype.atom.io/protocol-version

Versions
Teletype version: v0.13.4
Atom version: 1.41.0
Platform: win32

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀


Blazor WASM template missing when building + using from source

Describe the bug
When I build aspnetcore from source and then source activate.sh I get a dotnet that only has the blazor server template, not blazor wasm. If I follow the tutorial instructions from the official site I have both blazor server and wasm templates. As a result I can't 'dotnet new' a blazor wasm project when building from source.
If I try to use an existing blazor wasm project w/a from-source build of aspnetcore it doesn't work, but that seems expected.
To Reproduce

Build from source with build.sh on a master checkout
source ./activate.sh
cd .. ; mkdir blazortest ; cd blazortest ; dotnet new blazorwasm

Expected behavior
It works
Actual behavior
No templates matched the input template name: blazorwasm
And the installed templates list contains blazorserver but not blazorwasm.
Additional context
.NET Core SDK (reflecting any global.json):
 Version: 5.0.100-alpha1-013788
 Commit: 9df6ca668d

Runtime Environment:
 OS Name: Mac OS X
 OS Version: 10.15
 OS Platform: Darwin
 RID: osx.10.15-x64
 Base Path: /Users/katelyngadd/Projects/AspNetCore/.dotnet/sdk/5.0.100-alpha1-13788/

as per this docs https://docs.microsoft.com/en-us/aspnet/core/blazor/get-started?view=aspnetcore-3.0&tabs=visual-studio
You need to run the following command to obtain blazor assembly
dotnet new -i Microsoft.AspNetCore.Blazor.Templates::3.1.0-preview2.19528.8


QS: support files beyond PE binaries

[ ] #785
[ ] #786
[ ] shellcode blobs
[x] arbitrary files

via #776

what do we mean by "shellcode blobs"? how would you imagine this working?

Idea here is that if users know its shellcode (and specify it manually), we can disassemble functions and remove junk strings that are code.


[AutoPR network/resource-manager] Add network 2018-07-01 API to Go sdk

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3779

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/2598


feat: block syncer add dual db support config

Changes

Add dual DB config
Some chores

clean commit history, and merge by squash


Update to Avalonia preview 5

Initially This PR added a wrapper for ItemsRepeater but that has been moved to a separate package . So I will reuse this now to update to the latest preview and fix any breaking change
You can see the API changed here http://fuget.org/packages/Avalonia/11.0.0-preview5/lib/netstandard2.0/diff/11.0.0-preview4/
https://github.com/AvaloniaUI/Avalonia/wiki/Breaking-Changes/064853975091b5d212496e6cb2d1dcf9b61be98a

The dependency has been updated and now the app compiles . We need to keep adding controls , extensions


Feature Request: CLI build static site

Would it be possible to add something like vapid build . to generate the static site? Currently, it looks like you can only deploy via the Vapid hosting.
I see there's a Builder Class but not sure how to implement it. Any ideas/thoughts would be much appreciated.
Thanks for the cool project!

Is something like this going in the right direction? Or should I be looking at Generate instead of Build?? 🤔
const Builder = require('./node_modules/vapid-cli/lib/builder.js')
const { resolve } = require('path')

const templatesDir = resolve(__dirname, 'www')

async function build() {
  const builder = new Builder({ templatesDir })
  try {
    await builder.init()
    const files = await builder.build()
  } catch (err) {
    console.log(err)
  }
}

build()

It would be doubly awesome to have a way to generate a static site from the dashboard interface as well.

This is for me a MUST to use it in production. I want to deploy it to my vps.

@stursby:  Thanks for bringing this up. Answers inline (slightly reordered):

Currently, it looks like you can only deploy via the Vapid hosting.

True, vapid deploy posts to the Vapid hosting service, but you can definitely host Vapid elsewhere, like Heroku or any service that supports Node.js. So in that sense, you can deploy anywhere.
Would it be helpful if Vapid let you override vapid deploy so that it acted as some sort of alias to an NPM script? e.g. If vapid deploy kicked off git push heroku master?

Would it be possible to add something like vapid build . to generate the static site?

I'm curious to hear more about your use case (and from @trst and @KeizerDev too). Are you planning to use Vapid's dashboard to edit content on your production server? What is appealing about using Vapid over one of the existing static site generators, like Jekyll or Middleman?

I see there's a Builder Class but not sure how to implement it. Any ideas/thoughts would be much appreciated. Getting the following Error: TypeError: Cannot read property 'rebuild' of undefined

The error is happening because Builder is looking for the Section model, which gets passed into the constructor. In any case, I'm not sure that Builder is isolated enough to be used as a standalone class, like your example.
Let's chat about the first two points, and then hopefully I can shed some more light on the third.

I'm curious to hear more about your use case (and from @trst and @KeizerDev too). Are you planning to use Vapid's dashboard to edit content on your production server? What is appealing about using Vapid over one of the existing static site generators, like Jekyll or Middleman?

I would like to use the Vapid dashboard locally to maintain multiple sites and when I'm done I would deploy them on my vps like you would do with Jekyll. What I like about Vapid instead of Jekyll (I have no experience with middleman so can't say anything about that) is the way of just declaring a variable and then fill them with your data instead of the otherway around like you do in Jekyll. Same for articles (repeating content), it's a cleaner and more flexible way of working imho.
I would like to have some command like vapid build to just generate static html/css so I can serve it with apache/nginx and not have to worry about anything else like hosting an admin panel or again another service to hosts my sites on (i'd like to keep my own control over what I host).
Maybe this is not the way you designed it or not the way you liked it to be, this is just how it would suit for me and how I would liked it to be.
Let me know what you think @srobbin

If it were just for me, I might stick to a static generator, like Jekyll, however, I think Vapid really does benefit a client with less technical savvy than a developer. I would like to give clients an easy to update solution with the option to build statically for security purposes. These static files could be stored in a git repository through a cron job (or whatever), in case I have to roll back later on.
In a more technical team, it would be nice to just store the whole thing in git, clone the repository, fire it up locally to create content changes (or add a blog post, etc.), build it locally before committing or triggering a build via something like Netlify, and pulling in and serving the static files on a server via a webhook. That way the team can always keep the source material up to date without requiring too much heavy lifting from a server or exposing the possibility of a security breach of a dynamic interface.
Not to say that your security is poor, rather that I would just like to limit the attack surface as much as possible. Having flashbacks atm 😅

Static builds would be awesome

Absolutely a must have feature in my opinion.

Any updates on this? Happy to help implement 🙂

I agree with @trst and @KeizerDev , this should be mandatory in production. It would be a blast to generate static files and push them to netlify or any other similiar solution. The benefit of giving a user-friendly dashboard/backend to the client along with a opportunity to create a quick static build is the main reason we're looking into "new" cmses right now.

Any updates on this ?
I am also looking forward to this, so I can keep a dashboard locally to edit my client content and push a static site in production.

This still seems quite popular, maybe don't close it? 😅

Any new updates?
Would love to deploy this to Netlify.

👋 Hi all! Just making an announcement that I'll be looping back to this finally in the next few weeks – I have a new project that'll require it! Excited to dive in again 🙂

Will continue working in https://github.com/vapid/vapid/pull/99

This just shipped in v0.9.0. To update: npm install -g @vapid/cli
A huge thank you to @amiller-gh for adding this feature. It's a great addition to Vapid, and I'm grateful for his hard work.


Update to TF12 syntax

When is this going to be merged into master?

Sorry. I see it's in 1.1.1 release.


Make Nest.Json.Linq.JArray Public

I have a dynamic data model, that requires me to access this class, to perform additional logic before it gets served to the client app. Currently its set to Internal and, thus inaccessible to my implementation and makes thing like dynamic data models somewhat tricky...
public Dictionary<string, object> Attributes { get; set; }

In my service where the documents get created... I can construct something to the effect of
Attributes: {
   "foo":"bar",
   "something": [ "23432", "dsfdsf", "12321" ],
   // at any given time my source system could add other arrays/text items
}

During deserialization, I'm unable to do something like this for example
if (value is Nest.Json.Linq.JArray collection) //  <----- this complains.
{
      value = collection.ToArray<string>();
}

I've tested the above successfully in a sample app, where I emulated this functionality using NewtonSoft.JArray, but of course that doesn't help me much :P
Without the above, the array items get rendered like this in the client:
Attributes: {
   "foo":"bar",
   "something": [ [], [], [] ],
}

I'm open to suggestions, but failing the above, could we please update the Nest.Json.Linq.JArray to be Public?

These types are our internalized JSON.NET types where we rewrote the namespace to Nest.Json they are very much intentionally not public, have a gander at our release blog post for the back story here :smile:
https://www.elastic.co/blog/nest-elasticsearch-net-6-0-ga
If you need this types public its best to switch to the Nest.JsonNetSerializer package and configure the client to use it
This way you will get back public Newtonsoft.Json.Linq.JArray's instead 👍

@Mpdreamz damn... the Nest.JsonNetSerializer package doesn't have support for 2.0 yet :/ Would this be the place to request a version bump for that too?


ui: fix columns for exportacls csv

Description
Fixes #8862
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
ACL rules

CSV

How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan ui

@weizhouapache a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/9118 (QA-JID-352)

thanks @shwstppr
tested on https://qa.cloudstack.cloud/simulator/pr/9118/#/acllist/5f3185d4-4b78-4cc1-83fd-2fe141f730f2?tab=acl.list.rules
it looks startport and endport are missing

@weizhouapache should be fixed now

@blueorangutan ui

@shwstppr a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/9118 (QA-JID-354)

thanks @shwstppr
it works now


remove app in mac.

any one can help? how to fix this :( . I remove this app and cant installed again.

#mac
#macos
#remove apps

@xcv58 __**
**__

Can you try this? http://kb.mit.edu/confluence/display/mitcontrib/Cisco+Anyconnect+Manual+uninstall+Mac+OS

Maybe it was not completely deleted


Breaking Change between 16.3 and 16.4

Each major version of PostgreSQL (in theory) can come with breaking changes in their API and internals. One such breaking change was the non-optional addition of ALPN to the TLS connection process in PostgreSQL 17. As a result, libpg v17 contains this breaking change, so it is risky to link psql v16 against libpg v17.
In fact, The Official PostgreSQL Docker Container since tag 16.4 is linking against libpg v17 producing real problems in production: Once PostgreSQL v16 (!) is proxied (e. g. TLS termination is not performed by PostgreSQL itself but by Traefik, as typical in cloud environments etc.), psql v16 (!) fails to connect due to missing ALPN custom name postgresql (remember, only v16 is in use here on client and server, and ALPN support was invented in PostgreSQL v17 but does not exist officially in v16.x)!
As such a breaking change is counter intuitive (and forbidden by SemVer), I kindly ask the PostgreSQL Docker Community to link 16.x against libpg v16 instead of v17.
Disclaimer: The source of this information is Tom Lane, I just forwarded it.

Which variant is this? Is it just the alpine one or all of them?

I have reproduced it using using the latest tag on arm64. I have not tested other platforms or tags.


Upcoming drop: Wallstreet - change status

This is the next upcoming drop - from what I heard, it's going to be out tomorrow. Can we change the status from Ended to Soon or something similar?

Check it here: https://kodadot.xyz/ahp/drops

https://kodadot.xyz/ahp/drops/wallstreet


Add leading zeros so that files list in correct order

To correct this situation:

1-...
10-...
11-....
2-...

:+1:


Authentication Failure

Hey man,
First of all thanks for taking the initiative to make this gem!
I keep getting these Authentication Failures, you have any idea what could be causing them? I've tried quite a few things including changing my app secret, kind of ran out of options here, hehe. I am using other Omniauth providers btw so it's probably not something related to the gem itself.
Any help would be appreciated, here's the stack trace:
Started GET "/auth/discord" for <IP_ADDRESS> at 2016-07-02 04:30:59 -0300
I, [2016-07-02T04:30:59.658354 #46380]  INFO -- omniauth: (discord) Request phase initiated.

Started GET "/auth/discord/callback?state=d33ffea3855f9de566c83306159e799195bb694feb3c2c62&code=nrQbDuErRE2Vx0XncXEOlvogsCWFcK" for <IP_ADDRESS> at 2016-07-02 04:31:02 -0300
I, [2016-07-02T04:31:02.817329 #46380]  INFO -- omniauth: (discord) Callback phase initiated.
E, [2016-07-02T04:31:03.695007 #46380] ERROR -- omniauth: (discord) Authentication failure! invalid_credentials: OAuth2::Error,
<title>404 Not Found</title>

404 Not Found

nginx

Update: I just tried setting my app secret to a dummy string 'foo' and the error was different:
ERROR -- omniauth: (discord) Authentication failure! invalid_credentials: OAuth2::Error, invalid_client:
{"error": "invalid_client"}
```

Hello Pedro,
I'm working on this issue right now and we'll have some update today.

Issue fixed and closed! Thanks to @p2k!


update repository.txt

hi there, i've change the name of my library from unodepp to nodepp, but it does not appear in the arduino library manager.

@ArduinoBot


ClassToolBox: BlockView OnDrag problem?

Hi:
I use theme: ClassToolBox,  after apply cc0ff24 & f346ec9, the blockView drag function not working properly,
is it a bug?

Sorry. I have a quick fix for this. But the sub-toolbox won't hide automatically now. I'll figure out a better way in the future.

Sorry. I have a quick fix for this. But the sub-toolbox won't hide automatically now if you don't mind.  I will figure out a better way in the future.

Thanks for the quick fix.

Hi, I have a fixed commit 226a5649bca97fee6d40dc98c6601219abed3065 now. The sub-toolbox can hide automatically now, as google blockly. Sorry for the inconvenience.

Thanks for the fix, ClassicToolbox now works perfect.


[AWS Developer] Course Project. Migration from Serverless to AWS SDK

Copy the project description and it's material from
https://github.com/EPAM-JS-Competency-center/cloud-development-course-initial to our repository
Create a list of required AWS services (S3, SQS, etc.)

Refactor front-end

Course copied to nodejs-aws branch

Also forked Cart API Service and update it.
Migrate all task to AWS CDK.
Issue could be closed

@ThorsAngerVaNeT Thanks a ton! Great job!


address range limitation

When the size is larger than 31 bits, the extension does not decode the address

the first 3 lines, the tool is able to decode the address, but not the last 3 lines

This will be fixed in next version 0.0.5.

thanks


Backhandling on the ResultPage does not update the search

Describe the bug
When clicking the back button on the ResultPage the page should show the previous search if there was one. But the page does not update the results.
To Reproduce
Steps to reproduce the behavior:

Make a new search e.g. for "Frankfurt"
Make another search e.g. for "Berlin"
Click "back".
The ResultPage is still showing the result for "Berlin"

Expected behavior
After step 3 the ResultPage should show the results of "Frankfurt" agein.
Desktop (please complete the following information):

OS: all
Browser: all
Version: all

Smartphone (please complete the following information):

Device: all
OS: all
Browser: all
Version: all

There are multiple ways how to solve this.
First we can add some event handler for the browser navigation buttons and reload the data if the event is fired:

onpopstate event: https://developer.mozilla.org/de/docs/Web/API/WindowEventHandlers/onpopstate
backbutton event: https://stackoverflow.com/questions/47974777/can-i-handle-back-button-within-methods-in-vuejs-2

As second method we could use vue-router navigation guards to detect route changes or even simpler just set a watch at the route for the posts page and reload the data:

https://router.vuejs.org/guide/advanced/navigation-guards.html#in-component-guards
https://router.vuejs.org/guide/essentials/dynamic-matching.html#reacting-to-params-changes

We could also discuss by solving this bug, if we can split the hydrateStateFromRoute function and the currently involved loadPosts function to make them more independent.
By this we have to thing about when is the time to find the open post if the id of the post is given by the url. Currently we will search for this post directly in the hydrateStateFromRoute function. This is the reason why we have to load the posts list first, before we can find the open post from this list.

Just saw the issue #124. For a clearer independent behavior, every time a post is opend we could do a rest to the server to get the post deteils. By this the issue #124 could be easily fixed and also the functionalty in hydrateStateFromRoute could be splitted into own function calls.

Removed the loadPosts function call from hydrateStateFromRoute and added PostSerive.findById function in #333 PR.

@DianaPankratz have you checked if this is still a problem on the staging branch?

@xcaverxiii Still not working on staging


Fix mac integration tests

Please select one of the following

[ ] I am removing an existing difference between facebook/react-native and Microsoft/react-native :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into Microsoft/react-native :thumbsup:
[x] I am making a fix / change for the macOS implementation of react-native
[ ] I am making a change required for Microsoft usage of react-native

Microsoft Reviewers: Open in CodeFlow

/azp run


Move database connection information to environment variables

What does this PR do?
Moves the database connection information to the environment variables
Action points

Move database connection info to environment variables
Add the database connection information to heroku and travis-ci config variables

Coverage remained the same at 89.197% when pulling 7a0a50494384823cb171c02d827dd97ab19ac59c on move-db-to-secure-location into 3b682b2d0040f7d8e426138496be44bda4be9db7 on develop.


Support to a semi-supervised text recognition task in OCR

@Hhhhhhao @qianlanwyd Hi, do you have a plan to release a demo for the semi-supervised text recognition task in OCR?

we are not familiar with ocr task so we don't have this plan


fix or suppress test warnings

Fixes or suppresses a number of warnings that turn up in our upstream CI.
pd.Index.is_monotonic is an alias for pd.Index.is_monotonic_increasing and does not stand for pd.Index.is_monotonic_increasing or pd.Index.is_monotonic_decreasing.

Thanks a lot!


Feature Request:  Forced Export To GRID

It seems this is possible with alpha ess for LOOP and other providers around the world its also possible if using the modbus is there a way to access this feature via the API and push the battery into exporting to the grid?

The integration I'm using is not based on modbus so I cannot comment about that.  As for the official AlphaESS open API (which I am using) the AlphaESS team have stated that forced export to the grid is NOT a feature that the open api will support and that forced export as a feature is only available in a commercial api  suitable for power generation companies.
Here's a short thread on the topic.
https://github.com/alphaess-developer/alphacloud_open_api/issues/43


Let .kubeconfig populate ca/cert/key data in client configs

client.Config supports setting the actual data for CA, client cert and key as an alternative to using file references. This updates .kubeconfig to be able to do the same. This is primarily useful for encapsulating a complete client config in a single file (e.g. for distribution to a node, pod, or other API client).
I intentionally didn't update kubectl config commands since I expect this to be used by something that generates these files, rather than end-users. If they really really want to set the data, they can use kubectl config set/unset

@googlebot I'm with RedHat
/cc @derekwaynecarr now you've got me talking to the bot

/cc @deads2k

Not sure who is a good person to assign this review to.
@erictune?

@nikhiljindal
@jlowdermilk has been the victim in this area several times.

This is on the critical path to giving pods access to talk back to the master (as in, now .kubeconfig is a nice self contained bundle that we can ship around as a secret for @pmorie's secret change)

@deads2k updated and updated tests:

set-cluster disallows --insecure=true and --certificate-authority=...
set-cluster --insecure=true clears CA data and file
set-cluster --certificate-authority=... sets insecure=false and clears CA data
set-credentials disallows --token=... and --client-certificate=...
set-credentials --token=... clears client certificate and key files and data
set-credentials --client-certificate=... clears token

Jordan - per our chat today, can we allow a simple user name and password for clusters using basic auth over SSL as part of this PR?
Sent from my iPhone

On Feb 18, 2015, at 2:55 PM, Jordan Liggitt<EMAIL_ADDRESS>wrote:
@deads2k updated and updated tests:
set-cluster disallows --insecure=true and --certificate-authority=...
set-cluster --insecure=true clears CA data and file
set-cluster --certificate-authority=... sets insecure=false and clears CA data
set-credentials disallows --token=... and --client-certificate=...
set-credentials --token=... clears client certificate and key files and data
set-credentials --client-certificate=... clears token
—
Reply to this email directly or view it on GitHub.

@derekwaynecarr added

@deads2k I was hoping basic auth support would go away with .kubernetes_auth, but enough systems use it that that seems unlikely. Adding first-class support in .kubeconfig hopefully means we can deprecate .kubernetes_auth more easily.

Awesome to know it's already there.
Can we get an UPSTREAM patch in Origin tomorrow?
Sent from my iPhone

On Feb 18, 2015, at 10:04 PM, Jordan Liggitt<EMAIL_ADDRESS>wrote:
@derekwaynecarr added
—
Reply to this email directly or view it on GitHub.

@jlowdermilk updated validation and kubectl set-credentials to allow both client cert info and basic/bearer auth. let me know if you have any other comments

This is LGTM, but @jlowdermilk owns final sign off and review

A couple final tweaks regarding loading/writing kubeconfig files

Changed the default mode when creating a kubeconfig file 0600... world-readable files aren't great, especially when they can contain secrets (which it already did with bearer-token)
Added methods for loading/writing a config to a byte slice, for consumers that want to serialize/deserialize from things other than files

LGTM.


search api

Description
(Write your answer here.)
Checklist

[x] I am making a proper pull request, not spam.
[x] I've checked the issue list before deciding what to submit.

Related Issues or Pull Requests
(Write your answer here.)
Add relevant screenshot or video (if any)
(Add here)

image Api to search for images to upload


Third nav directional arrows appear at top of page

Not sure if just the documentation sample, but:

clasic absolute positioning bug. Fixed in #548


Accessing $stateParams values from controller

I am unable to get the values in stateParams when i use native-ui-sref along with native-ui-sref-opts.
How do i access these values?

Related to #35, I am gonna work on this today. sorry about that


Re-add the ability to get major edge lines.

Bump version from 14.0.0 (current release) to 14.1.0, because we're adding a method.
Added back get_major_edge_line_indices, which was removed by commit 9ff8564b4cab8b1196a78e3313a0324f4f2e94cc. However, it is (still) buggy (it misses the first and last index), so it is marked deprecated. This is just so that this can go into a release which is a minor rather than major version bump.
Added replacement get_major_edges_line_indices which returns the correct lines. However, it returns all relevant edges, rather than allowing selection of a single edge.
Removed unused use std::sync::Arc;.

Howdy -- this looks good to me. I'll try to make sure to remove the deprecated function next time I'm pushing a major revision.
I'll get this merged in.


Try out agenix

https://github.com/hlissner/dotfiles/commit/69d730f89d8900a372a06c05b8e1865e41355b49

https://github.com/ryantm/agenix

too similar to another issue


Elasticsearch search backends do not support ordering set by the reverse method on a QuerySet

Issue Summary
Elasticsearch search backends do not support ordering set by the reverse method on a QuerySet.
Steps to Reproduce

Setup a project with an Ealsticsearch search backend

Create 2 or more pages with title (or any other searchable content) containing "social".

Run the following code in a Django shell:
from wagtail.core.models import Page
from wagtail.search.backends import get_search_backend

search_query = 'social'
queryset = Page.objects.order_by('first_published_at')

sb = get_search_backend()
results = sb.search(search_query, queryset, operator=None, order_by_relevance=False)

for r in results[:10]:
    print(r.pk, r.title)

Then run the same code snippet but with with reverse set by the QuerySet.reverse method:
from wagtail.core.models import Page
from wagtail.search.backends import get_search_backend

search_query = 'social'
queryset = Page.objects.order_by('first_published_at')
queryset = queryset.reverse()

sb = get_search_backend()
results = sb.search(search_query, queryset, operator=None, order_by_relevance=False)

for r in results[:10]:
    print(r.pk, r.title)

Expected result: on the step 4 we get pages ordered in reverse order in comparison to pages from the step 3
Actual result: pages ordered in the same way

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: yes

Technical details
It looks like Elasticsearch backends do not detect reverse order set using the QuerySet.reverse method. Only using QuerySet.order_by:
https://github.com/wagtail/wagtail/blob/58135ccf6ea06095379c32e07578095545b37762/wagtail/search/backends/base.py#L120-L140
It was the reason behind #3514 (see https://github.com/wagtail/wagtail/issues/3514#issuecomment-494831614).
Note that wagtail.contrib.postgres_search.backend doesn't use _get_order_by method, so you will get expected results with the Postgres backend.

Python version: 3.6.4.
Elasticsearch 5
Django 2.1.3 and 2.1.5
Wagtail 2.3, 2.4, 2.5

I'm getting an identical stack trace, but with case-insensitive ordering, i.e.:
matches = MyModel.objects.child_of(self).live().public().order_by(Lower('title'))
matches = matches.search(query, order_by_relevance=False)

which results in
Traceback (most recent call last):
  File "django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
  File "django/core/handlers/base.py", line 197, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
…
    matches = matches.search(query, order_by_relevance=False)
  File "wagtail/search/queryset.py", line 18, in search
    return search_backend.search(
  File "wagtail/search/backends/base.py", line 432, in search
    return self._search(
  File "wagtail/search/backends/base.py", line 419, in _search
    search_query_compiler.check()
  File "wagtail/search/backends/base.py", line 221, in check
    list(self._get_order_by())
  File "wagtail/search/backends/base.py", line 174, in _get_order_by
    if field_name.startswith("-"):
AttributeError: 'Lower' object has no attribute 'startswith'

The docs say this should be all you have to do:

But it looks like the Elasticsearch backend makes some assumptions about what the field_name is.

@nutjob4life I think that's best treated as a separate issue to the one described here. Essentially, the Elasticsearch backend is replicating the Django Queryset API on an object that isn't a standard database query - implementing arbitrary functions such as Lower on order_by will be a much bigger task (if the Elasticsearch query language supports it at all) than just adding the reverse method.

Thanks @gasman. I see the point and made a separate issue.


Upcoming Release Changes

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
<EMAIL_ADDRESS>Patch Changes

f99b7fb
Thanks @ardatan! - Make inferred RouterInput params required

<EMAIL_ADDRESS>Patch Changes

Updated dependencies []:

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies
[f99b7fb]:

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies []:

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies
[f99b7fb]:

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies
[f99b7fb]:

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>Patch Changes

Updated dependencies
[f99b7fb]:

<EMAIL_ADDRESS>

💻 Website Preview
The latest changes are available as preview in: https://ec14e341.fets.pages.dev

💻 Website Preview
The latest changes are available as preview in: https://98ac9191.fets.pages.dev

💻 Website Preview
The latest changes are available as preview in: https://87814247.fets.pages.dev


Add Meta tags for social media

I want to work on this issue please assign me.

I want to work on this issue please assign me.

sure @MVENKATESH786

@MVENKATESH786 how's this going?

It’s almost done and should be completed by today.


Error 404 not found

Hello,
since a couple of weeks, with no changes on the configuration, my Start/Stop VMs v2 script goes on error 404 resource not found when trying to start the virtual machine.
The subscription ID is correct, and there is only one VM in the subscription.
I'm in the Function-Try step, with the following code:
{
    "function": {
        "name": "StartStopV2krk73u3tu4ozm/Scheduled",
        "id": "/subscriptions/MYSUBSCRIPTIONID/resourceGroups/RESOURCEGROUP/providers/Microsoft.Web/sites/StartStopV2krk73u3tu4ozm/functions/Scheduled",
        "type": "Microsoft.Web/sites/functions"
    },
    "body": {
        "Action": "start",
        "EnableClassic": false,
        "RequestScopes": {
            "ExcludedVMLists": [],
            "Subscriptions": [
                "/subscriptions/MYSUBSCRIPTIONID/"
            ]
        }
    }
}

(where MYSUBSCRIPTIONID is my number c61...-....-....-....-....... and RESOURCEGROUP is the resource group name)
The output says
{
    "statusCode": 404,
    "headers": {
        "Date": "Thu, 13 Jun 2024 05:15:02 GMT",
        "Request-Context": "appId=cid-v1:285f25a8-8630-40d1-a38d-aab9e9978435",
        "X-Content-Type-Options": "nosniff",
        "Content-Length": "0"
    }
}

Any suggestion on how to fix it?
Thank you,
Fabio

FYI: We've started seeing the same issue this morning.
Looking at the hosting function app's activity log we see that there was an UpdateWebSite event before these issues began.
The change history tab of that event shows the following:

Changed Property
Change Type
Change Category
Old Value
New Value

properties.appSettings["CentralizedLoggingOptions:Version"].value
Update
User
1.1.20240422.1
1.1.20240617.1

properties.appSettings["AzureClientOptions:AutoUpdateTemplateUri"].value
Update
User
https://startstopv2prod.blob.core.windows.net/artifacts/ssv2autoupdate.json
https://raw.githubusercontent.com/microsoft/startstopv2-deployments/main/artifacts/ssv2autoupdate.json

properties.appSettings["AzureClientOptions:AutoUpdateRegionsUri"].value
Update
User
https://startstopv2prod.blob.core.windows.net/artifacts/AutoUpdateRegionsGA.json
https://raw.githubusercontent.com/microsoft/startstopv2-deployments/main/artifacts/AutoUpdateRegionsGA.json

properties.appSettings["AzureClientOptions:Version"].value
Update
User
1.1.20240422.1
1.1.20240617.1

NB: We've also seen oddities in other start-stop function apps which MS have upgraded in the background, where the HeartBeatAvailabilityTest causes List Web Apps Functions Host Keys to show in the function app's event log 3 times every time it's run (i.e. every 5 mins).  For those, the update event's change history shows the same versions as above; i.e.

Changed Property
Change Type
Change Category
Old Value
New Value

properties.appSettings["CentralizedLoggingOptions:Version"].value
Update
User
1.1.20240422.1
1.1.20240617.1

properties.appSettings["AzureClientOptions:AutoUpdateTemplateUri"].value
Update
User
https://startstopv2prod.blob.core.windows.net/artifacts/ssv2autoupdate.json
https://raw.githubusercontent.com/microsoft/startstopv2-deployments/main/artifacts/ssv2autoupdate.json

properties.appSettings["AzureClientOptions:AutoUpdateRegionsUri"].value
Update
User
https://startstopv2prod.blob.core.windows.net/artifacts/AutoUpdateRegionsGA.json
https://raw.githubusercontent.com/microsoft/startstopv2-deployments/main/artifacts/AutoUpdateRegionsGA.json

properties.appSettings["AzureClientOptions:Version"].value
Update
User
1.1.20240422.1
1.1.20240617.1

NB: This may be the same issue; the reported symptom there being based on notifications whilst here it's based on logs.
#122
That includes a comment on how to resolve the issue (i.e. by redeploying the function): https://github.com/microsoft/startstopv2-deployments/issues/112#issuecomment-1961755579

I confirm that the comment of @JohnLBevan solves the issue, it's the same issue as #122  with a different error code. Thank you!

Thank you all for providing your inputs. Please see the official guidance on the following issue: https://github.com/microsoft/startstopv2-deployments/issues/116#issuecomment-2104845492


Error when using trigger to update timestamp

Check out this gist for a minimal example.
In short, I have a table with a trigger that changes the _last_updated row on each update.
CREATE TABLE Test (
	id integer primary key autoincrement,
	data text not null,
	_last_updated datetime default current_timestamp
);

CREATE TRIGGER update_test_timestamp
AFTER UPDATE ON Test BEGIN
UPDATE Test SET _last_updated = datetime("now") WHERE id = new.id;
END;

INSERT INTO Test(data) VALUES("blah blah blah");

When updating a row manually, such as with the sqlite repl, it works as expected.
sqlite> select * from test;
1|blah blah blah|2020-05-06 00:28:48
sqlite> update test set data="blah blah 2.0" where id=1;
sqlite> select * from test;
1|blah blah 2.0|2020-05-06 00:29:31

However, performing the same action with better-sqlite3 produces a very obscure error.
const connect = require('better-sqlite3')

const db = connect('test.db', { fileMustExist: true })

db.prepare('UPDATE Test SET data=? WHERE id=?').run('blah blah 3.0', 1)

/home/nmay/cur/tmp/sqlite-bug/update_db.js:5
db.prepare('UPDATE Test SET data=? WHERE id=?').run('blah blah 3.0', 1)
   ^
SqliteError: no such column: now
    at Object.<anonymous> (/home/nmay/cur/tmp/sqlite-bug/update_db.js:5:4)
    at Module._compile (internal/modules/cjs/loader.js:1156:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1176:10)
    at Module.load (internal/modules/cjs/loader.js:1000:32)
    at Function.Module._load (internal/modules/cjs/loader.js:899:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:74:12)
    at internal/main/run_main_module.js:18:47

Removing the trigger and recreating the database gets rid of this issue:
- CREATE TRIGGER update_test_timestamp
- AFTER UPDATE ON Test BEGIN
- UPDATE Test SET _last_updated = datetime("now") WHERE id = new.id;
- END;

I'm at a loss why the trigger would give rise to this error.
Versions:
OS             -- Ubuntu 18.04
sqlite3        -- 3.29.0
node           -- v12.16.2
better-sqlite3 -- 7.0.1

Let me know what other information you require :+1:

This error is happening because by default better-sqlite3 is compiled with the SQLITE_DQS=0 compile-time option. This compile-time option disables SQLite3's "double quoted string literal misfeature".
Long story short, the correct way to write a string in standard SQL is to use single quotes. In standard SQL, double quotes are used to identify columns and tables (for example, if the column name contains a space). When SQLite was first created, it allowed double quotes to be used for strings in situations where it could deduce that such a column/table name does not exist. This was originally done to be compatible with MySQL which also accepts double quotes as strings. However, both MySQL and SQLite now recommend that single quotes should always be used for strings, to be compliant with the SQL standard. SQLite still allows double quoted strings for legacy compatibility, but discourages the behavior, and even lists SQLITE_DQS=0 as one of its recommended compile-time options.
So you should change datetime("now") to datetime('now').


Check if slides is array

Currently it's possible to ng-repeat on an object and carousel works with bugs. When it's reached the last element it's not circled because of object.length is undefined and undefined + 1 is NaN in this peace of code:
scope.nextSlide = function(slideOptions) {
    var index = scope.carouselIndex + 1;
    if (index > currentSlides.length - 1) {
        index = 0;
    }
    if (!locked) {
        goToSlide(index, slideOptions);
    }
};

I can't write any tests because seems they are disabled (they are commented now all).

thanks


BUG:Accessibility: Invalid href attributes in multiple components

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Title:
Accessibility: Invalid href attributes in multiple components
Description:
Your application currently has several components with invalid href attributes, which negatively impact accessibility and user experience. These issues are identified by ESLint warnings and need to be addressed to ensure our application is accessible to all users.
Components and Lines Affected:

CanteenCard.jsx

Line 41: The href attribute requires a valid value to be accessible. Provide a valid, navigable address as the href value.
Line 51: The href attribute requires a valid value to be accessible. Provide a valid, navigable address as the href value.

Footer.jsx

Line 7: The href attribute requires a valid value to be accessible. Provide a valid, navigable address as the href value.
Line 19: The href attribute requires a valid value to be accessible. Provide a valid, navigable address as the href value.

Navbar.jsx

Line 32: The href attribute requires a valid value to be accessible. Provide a valid, navigable address as the href value.

Steps to Reproduce:

Run the application and inspect the elements in the specified components.
Observe that the href attributes do not contain valid values.

Expected Behavior:

All href attributes should contain valid, navigable addresses to ensure accessibility and proper functionality.

Actual Behavior:

Invalid href attributes cause accessibility issues, making the application less usable for users relying on screen readers and other assistive technologies.

Possible Solutions:

Provide Valid Links: Ensure that all href attributes contain valid URLs.
Use Buttons for Non-Navigational Actions: If an element is meant to look like a link but does not navigate to a new page, use a <button> element styled as a link instead.

Additional Context:
Refer to the eslint-plugin-jsx-a11y documentation for more information on fixing these issues.
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@iamabhishek2828 ok fix them

Ok


feat(Android): add all alarm types to trigger alarmManager

resolves #655
hi @helenaford
I tried to change all places I thought I should for this change, still I may have missed something
please let me know if there's any problem

Also I'm on windows and I didn't manage to use scripts or run E2E tests, I only managed to run jest tests

Oh I see I have to write a db migration, I'm not sure if I can do that
will try at some time later

again: Oh I see I don't have to 😅 the trigger object is saved in bytes and is retrieved at some point later

well I use notifee in my app (al-azan) as the core functionality of setting alarms for specific times
the launch intent, custom components and custom alarm types are the main features of notifee that are important to me
the reason for different alarm type is because depending on how you use them, they have different set of behaviors. and I think having setAlarmClock gives highest guarantee of delivery at the exact given time. Also it's what is recommended when you are setting an Alarm that is user-facing. but setAlarmClock was giving my Google Pixel users a bit of headache by messing up their adaptive charging feature. that's where I needed to use the setExactAndAllowWhileIdle by providing an option in my app UI. and so I came up with this PR. before this, I was simply changing the allowWhileIdle to always use setAlarmClock in my own branches of the notifee, that's why I never made a PR for it before.

also I remember adding some notes to the library, correct me if I have forgotten to
if there's anything else I have to add, please tell me

when can this PR be merged ? 🙏🏻

comment


DLDO - Run mass prePEX simulations

Run prePEX simulations on LDO generators based upon the simulation parameters mentioned in this document : https://docs.google.com/document/d/1WM2s7kAZDHakeOLUuvOx2q-YmuZw8De3YkUJe4TygyY/edit#heading=h.qdifo995vil5

@lulu9312 isn't this done?

The below document describes the process that is being used at the moment for running mass simulations: https://docs.google.com/document/d/1wMFu5eOOpW2XfONmhhN3L8_tzayvaHZzDn5S5-WR-jM/edit


Issue/ymax gsp graph (#133)

Pull Request
Description
Fix ymax on GSP plot to be the installed capacity of the GSP
Need to round up the ymax value to th following levels, so that y major ticks looked right
[3, 9, 20, 45, 60, 100, 200, 300, 450, 600];

Fixes #133
How Has This Been Tested?
ran locally

[x] Yes

If your changes affect data processing, have you plotted any changes? i.e. have you done a quick sanity check?

[ ] Yes

Checklist:

[x] My code follows OCF's coding style guidelines
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have checked my code and corrected any misspellings

Hey @dlinah . I got into trouble with undefined things, and number and strings. If you see anything obviously wrong please do point it out. (Fairly new to js)

LGTM 💯

thanks


Update project users API

hi. go-gitlab is helping me to create tools with my tool creation. Thanks for making.
I fixed the following problem and I want you to merge it.
problem

ListProjectsUsers does not correspond to [namepace/project] style request
No Test ListProjectsUsers

Thanks @lighttiger2505! LGTM!


Session frozen when you lose network for a few seconds (Unrecoverable)

freerdp version 2.3.2
I have used parameters such as +auto-reconnect and /timeout without result, the session is frozen.
Use case: Unplug the network wire for 15-20 seconds and plug it in again.
The log when the session has frozen but you already have a network connection:

@FutureKidBuu

does it recover after a few seconds?
The screenshot of the log is not very helpful ;)

@akallabeth No, the current session is no longer recoverable, I have to close the window and relaunch freerdp.

@akallabeth log, It can be hell ;) (due to xf_lock_x11_ methods
xf_unlock_x11_)
trace_freerdp.log

@FutureKidBuu ok, the log is missing quite a lot of stuff (and your compile did ignore lots of compile warnings about excessive/dangerous logging)

I´d try a xfreerdp <yourargs> 2>&1 |tee log.txt to get a consistent log with errors and warnings

client_auto_reconnect_ex 2nd prameter is NULL,  add windows message loop in window_events can fix it.

@2fly2 which version and client do you use?

@akallabeth  freerdp version 3.0.0-dev,  freerdp git version c1084c7, branch master.  on windows.   but is the same as linux.
for(x=0; x < 50; x++)
{
if(!ICALLRESULT(TRUE, window_event,  instance))
return FALSE;
Sleep(100);
}
window_event will not run because it is NULL.

@2fly2 xfreerdp and wlfreerdp will call handle_window_events (wayland is just a stub though)
the windows client uses the version without callback though, there it might happen that the window is not updated until the session is reconnected

@2fly2 xfreerdp and wlfreerdp will call handle_window_events (wayland is just a stub though) the windows client uses the version without callback though, there it might happen that the window is not updated until the session is reconnected

yes, you are right.   'xfreerdp' can reconnect normally, 'wfreerdp'  the window is not updated until the session is reconnected


Use ConfigMapList's resourceVersion for watching (w/ PropertySource)

Rationale: avoid ERROR notifications during rolling upgrades.
Alternative PR: #299.
Using the greatest resourceVersion of all the ConfigMaps returned
within the ConfigMapList works as expected for fresh deployments.
But, when performing a rolling upgrade (and depending on the upgrade
strategy), the watcher happens to frequently stop after having received
an ERROR notification:

[ERROR] [KubernetesConfigMapWatcher] [] Kubernetes API returned an
error for a ConfigMap watch event: ConfigMapWatchEvent{type=ERROR,
object=ConfigMap{metadata=Metadata{name='null', namespace='null',
uid='null', labels={}, resourceVersion=null}, data={}}}

What's actually streamed in that case is a Status object such as:
{
  "type": "ERROR",
  "object": {
    "kind": "Status",
    "apiVersion": "v1",
    "metadata": {},
    "status": "Expired",
    "message": "too old resource version: 123 (456)",
    "reason": "Gone",
    "code": 410
  }
}

A few references:

https://github.com/abonas/kubeclient/issues/452
https://www.baeldung.com/java-kubernetes-watch#1-resource-versions

It's possible to recover by adding some logic to reinstall the watcher
starting with the newly advertised resourceVersion, but this may be
avoided at all by starting the initial watch at the resourceVersion
of the ConfigMapList itself: this one won't expire.
The proposed implementation consists in storing last received
resourceVersion as an additional PropertySource (through a dedicated
name and version key) and later using it when installing the watcher.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

@rdesgroppes I prefer to use this way of resourceVersion tracking b/c of using the property source as a vehicle how to deliver and store the value that is effectively a dynamic configuration property. Though it would be great if the resource version would be updated on every add/modify event so we won't hit 504 | 410 in case of restart of the watcher.
You ok with it or do you prefer #299 for some reason?

#299 is the simplest @grollinger and I came up with, but #300 seems more forward looking, so I'd agree with you.


Migration step is not moving forward

Hi Team,
I am running CentOS7.9 with plesk 18.0.52
~  cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)
~  plesk -v
Product version: Plesk Obsidian <IP_ADDRESS>
OS version: CentOS 7.9.2009 x86_64
Build date: 2023/05/16 12:00
Revision: a3b74dbc9de2e47afd4e532d02fa7759b29d3fa5
   When i tired to perform the migration from centos7toalmalinux8 is stopping with below note

 ~  ./centos2alma

Do preparation checks...~
Please suggest how to proceed further. I have changed the permission as well mention in the steps

Could you please call centos2alma with --verbose option. After is stopped provide a feedback archive that could be created by centos2alma --prepare-feedback

Unfortunately, I cannot continue the investigation without the feedback archive. I have resolved similar issues in previous releases, so this issue might already be fixed.
You are welcome to reopen the issue with the feedback archive if you will be able reproduce the problem on the latest centos2alma version.


Custom dataset

Hey,
Has anybody succeeded in training it on custom dataset. I need to know what things to change in the training code for it to run on custom dataset.
Or is it possible if I arrange my dataset in activitynet format and run activitynet's training code?
Any help would be appreciated.
Thanks

You can make the custom data set in the format of either activitynet, thumos or charades. I Have tried with Thumos. Once you have the data set and related items, similar to the standard dataset, the code works without any issues.


OfficeOnlineServerFarm: Added hierarchy and LDAP:// support for FarmOU

Pull Request (PR) description
Added support for specifying LDAP:// syntax and OU hierarchy for FarmOU
It's now possible to specify FarmOU like this:
"Servers/OOS" or
"ldap://OU=OOS,OU=Servers"
ntds:// format is supported by the underlying Office Online Server Management Shell but is not implemented in OfficeOnlineServerDSC.
This Pull Request (PR) fixes the following issues

Fixes #58

Task list

[x] Added an entry to the change log under the Unreleased section of the
file CHANGELOG.md. Entry should say what was changed and how that
affects users (if applicable), and reference the issue being resolved
(if applicable).
[x] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Community Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Community Testing Guidelines.
[x] New/changed code adheres to DSC Community Style Guidelines.

This change is

@ykuijs Will it be possible to include this improvement anytime soon?

Sorry @johlju I don't have the environment for this available anymore. I don't expect that I will be able to contribute much to this right now as my focus is elsewhere. All I can say is that the changes worked fine in a manually edited version of this module with the suggested changes on the server used for OOS.

No worries, I understand. I will label this as abandond so another contributor can take over to verify this. I'm sure the code worked for you in your scenario, but I worried it will break existing configurations in other scenarios.