Rails 4 support

Do you think to provide rails 4 support for this gem?
Recently i tried to include your gem in a project and i got the following trace error when i run
rails g ror_push_notifications:migrations

/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/dynamic_matchers.rb:26:in `method_missing': undefined method `attr_accessible' for #<Class:0x007fbf2a1461a8> (NoMethodError)
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/bundler/gems/ror-push-notifications-4aea09c92ffd/lib/ror_push_notifications/app/models/rpn/apns_config.rb:9:in `<class:ApnsConfig>'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/bundler/gems/ror-push-notifications-4aea09c92ffd/lib/ror_push_notifications/app/models/rpn/apns_config.rb:1:in `<top (required)>'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activesupport-4.1.7/lib/active_support/dependencies.rb:247:in `require'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activesupport-4.1.7/lib/active_support/dependencies.rb:247:in `block in require'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activesupport-4.1.7/lib/active_support/dependencies.rb:232:in `load_dependency'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activesupport-4.1.7/lib/active_support/dependencies.rb:247:in `require'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/bundler/gems/ror-push-notifications-4aea09c92ffd/lib/ror_push_notifications.rb:2:in `<top (required)>'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.7.13/lib/bundler/runtime.rb:76:in `require'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.7.13/lib/bundler/runtime.rb:76:in `block (2 levels) in require'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.7.13/lib/bundler/runtime.rb:72:in `each'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.7.13/lib/bundler/runtime.rb:72:in `block in require'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.7.13/lib/bundler/runtime.rb:61:in `each'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.7.13/lib/bundler/runtime.rb:61:in `require'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.7.13/lib/bundler.rb:134:in `require'
	from /Users/carlosleon/sources/solid-finger/config/application.rb:7:in `<top (required)>'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/spring-1.3.2/lib/spring/application.rb:82:in `require'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/spring-1.3.2/lib/spring/application.rb:82:in `preload'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/spring-1.3.2/lib/spring/application.rb:143:in `serve'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/spring-1.3.2/lib/spring/application.rb:131:in `block in run'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/spring-1.3.2/lib/spring/application.rb:125:in `loop'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/spring-1.3.2/lib/spring/application.rb:125:in `run'
	from /Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/spring-1.3.2/lib/spring/application/boot.rb:18:in `<top (required)>'
	from /Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from /Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
	from -e:1:in `<main>'

Mmmm, you're right. I'll do it. Just give me a couple of days please.

I opened https://github.com/calonso/rails-push-notifications/tree/rails4 branch to add rails 4 support.
Can you please switch to this branch and let me know if works as expected?

@calonso
I tried the new branch and no migrations were created.
iMac-de-Admin01:solid-finger carlosleon$ rails generate ror_push_notifications:migrations
WARNING: Could not find "create_rpn_configs.rb" in any of your source paths. Your current source paths are:
/Users/carlosleon/.rvm/gems/ruby-2.2.0/bundler/gems/ror-push-notifications-7c475f6e5569/lib/generators/ror_push_notifications/templates/migrations
WARNING: Could not find "create_rpn_devices.rb" in any of your source paths. Your current source paths are:
/Users/carlosleon/.rvm/gems/ruby-2.2.0/bundler/gems/ror-push-notifications-7c475f6e5569/lib/generators/ror_push_notifications/templates/migrations
WARNING: Could not find "create_rpn_notifications.rb" in any of your source paths. Your current source paths are:
/Users/carlosleon/.rvm/gems/ruby-2.2.0/bundler/gems/ror-push-notifications-7c475f6e5569/lib/generators/ror_push_notifications/templates/migrations

Ok, I fixed that one as well.
Could you please try again?

Now i have:
iMac-de-Admin01:solid-finger carlosleon$ rails generate ror_push_notifications:migrations
      create  db/migrate/20150220133825_create_rpn_configs.rb
      create  db/migrate/20150220133825_create_rpn_devices.rb
      create  db/migrate/20150220133825_create_rpn_notifications.rb
iMac-de-Admin01:solid-finger carlosleon$ rake db:migrate
rake aborted!
ActiveRecord::DuplicateMigrationVersionError:

Multiple migrations have the version number<PHONE_NUMBER>3825

/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:1013:in `validate'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:916:in `initialize'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:807:in `new'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:807:in `up'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:785:in `migrate'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)

Ok, can you delete the generated files at db/migrate and rerun again?
Should be fixed now.

The same results:
iMac-de-Admin01:solid-finger carlosleon$ rails generate ror_push_notifications:migrations
      create  db/migrate/20150220140233_create_rpn_configs.rb
      create  db/migrate/20150220140233_create_rpn_devices.rb
      create  db/migrate/20150220140233_create_rpn_notifications.rb
iMac-de-Admin01:solid-finger carlosleon$ rake db:migrate
rake aborted!
ActiveRecord::DuplicateMigrationVersionError:

Multiple migrations have the version number<PHONE_NUMBER>0233

/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:1013:in `validate'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:916:in `initialize'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:807:in `new'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:807:in `up'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:785:in `migrate'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)
iMac-de-Admin01:solid-finger carlosleon$ rake db:migrate --trace
** Invoke db:migrate (first_time)
** Invoke environment (first_time)
** Execute environment
** Invoke db:load_config (first_time)
** Execute db:load_config
** Execute db:migrate
rake aborted!
ActiveRecord::DuplicateMigrationVersionError:

Multiple migrations have the version number<PHONE_NUMBER>0233

/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:1013:in `validate'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:916:in `initialize'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:807:in `new'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:807:in `up'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/migration.rb:785:in `migrate'
/Users/carlosleon/.rvm/gems/ruby-2.2.0/gems/activerecord-4.1.7/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/task.rb:240:in `call'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/task.rb:240:in `block in execute'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/task.rb:235:in `each'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/task.rb:235:in `execute'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/task.rb:179:in `block in invoke_with_call_chain'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/monitor.rb:211:in `mon_synchronize'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/task.rb:172:in `invoke_with_call_chain'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/task.rb:165:in `invoke'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/application.rb:150:in `invoke_task'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/application.rb:106:in `block (2 levels) in top_level'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/application.rb:106:in `each'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/application.rb:106:in `block in top_level'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/application.rb:115:in `run_with_threads'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/application.rb:100:in `top_level'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/application.rb:78:in `block in run'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/application.rb:176:in `standard_exception_handling'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/lib/ruby/2.2.0/rake/application.rb:75:in `run'
/Users/carlosleon/.rvm/rubies/ruby-2.2.0/bin/rake:33:in `<main>'
Tasks: TOP => db:migrate

Sounds weird...Did you updated the branch?
bundle update rails-push-notifications

Works!
Thank you!


Need to persist certificates in a volume with docker-letsencrypt-nginx-proxy-companion v2.0.0+

To avoid hitting https://letsencrypt.org/docs/rate-limits/ with v2.0.0+ of https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion I think we need to persist certificates. From their README:

The single most important change is that the container now requires a volume mounted to /etc/acme.sh in order to persist ACME account keys and SSL certificates.

Still figuring out how to update my docker-compose*.yml files but thought I'd open this issue in case anyone else encounters issues with hitting the Let's Encrypt rate limits.

Ah actually it's easy to just add a volume:
diff --git a/docker-compose.staging.yml b/docker-compose.staging.yml
index 8bd5855..4e9d1d5 100644
--- a/docker-compose.staging.yml
+++ b/docker-compose.staging.yml
@@ -10,6 +10,7 @@ services:
       - certs:/etc/nginx/certs
       - html:/usr/share/nginx/html
       - vhost:/etc/nginx/vhost.d
+      - acme:/etc/acme.sh
     depends_on:
       - nginx-proxy

@@ -68,3 +69,4 @@ volumes:
   certs:
   html:
   vhost:
+  acme:

Examples for reference: https://github.com/nginx-proxy/docker-letsencrypt-nginx-proxy-companion/blob/v2.0.2/docs/Docker-Compose.md


reindeer: unstable-2023-05-31 -> unstable-2023-06-20

Description of changes
Update reindeer to a newer revision and use the upstream Cargo.lock.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Hello again @figsoda! Perhaps the usage of the upstream Cargo.lock will finally ensure reindeer is auto upgraded by @r-ryantm.

Looks like r-ryantm just hasn't tried to update reindeer :D
but this is an improvement nonetheless

huh, welp! Let's hope for the best!

https://github.com/ofborg build reindeer

@ofborg build reindeer


Consider updating HTML so can pass W3C validator

The W3C validator complains about 2 issues regarding the generated HTML:

Script tags should not define charset="utf-8"
A language tag should be added to the HTML tag.

For Number 1, headers.erb would need to be modified to remove charset= in Script tags.
Number 2 is not a concern I think, but would be nice to specify as a command-line option, like yardoc lang=en.
Steps to reproduce

Run the following command: yard doc
Copy produced HTML source from "index.html" (or any others)
Go to https://validator.w3.org/#validate_by_input
Paste in HTML source from Step 2
Click "Check"

Actual Output
Error: The charset attribute on the link element is obsolete. Use an HTTP Content-Type header on the linked resource instead.
Warning: This document appears to be written in English. Consider adding lang="en" (or variant) to the html start tag.
Expected Output
No errors/warnings.

Thanks for bringing this up. This would be an easy PR to take on if you're interested!

Thanks for merging my pull request.
HTML lang is just a warning, so probably not needed.


Add better angular velocity friction to car

Compared to the linear velocity the angular velocity doesn't get kept in check nearly as much resulting in very long drifting which messes up responsiveness of the car.

Benefits of 44ee075 already improve this issue, hopefully a real fix soon

fixed with e9286ea61316e88be92792064698ed2ede752d48 more improvements would be general fixups so closing


update Core_version according to substrate

Substrate uses parsing and decoding of runtime blob than execution in recent runtimes. See
https://github.com/paritytech/substrate/blob/polkadot-v0.9.8/client/executor/src/wasm_runtime.rs#L381

Decided to close the issue. Will implement https://github.com/soramitsu/kagome/issues/1374 instead


Add Sylvania Northview HS

@websterwh Please provide us with:

the school official website URL
the school street address, including city and country

https://www.sylvaniaschools.org/
5403 Silica Dr, Sylvania, OH 43560

@websterwh  Thank you for the clarifications. Pull request merged.
FTR: Domain ownership proof: https://filecabinet9.eschoolview.com/21DD6721-F6A5-43B5-A5D1-EC1ABB8F0D64/SwimLessonsFlyerMay.pdf


Added a parameter 'apiTimeout' to allow customization

to the Apache timeout.
The default is set to 60s which we do set for
HAProxy timeouts currently.
To be able to change the HAProxy value based on the apiTimeout with any update (and not just the first time) the code adds a custom annotation "api.placement.openstack.org/timeout" with the value that was initially set, this way flags it as being set by the placement-operator.
Timeout is global for both api and metadata and they are set from placement lvl
There will be follow up patch in openstack-operator to utilize the method 'SetDefaultRouteAnnotations' to set these default route annotations in openstack-operator
resolve: https://issues.redhat.com/browse/OSPRH-10962

/retest


Regarding the No-Focus issue

Hello,
I'm M.Samuel who reported about the flashing cursor not focused in the search box. I'm on Firefox v57 (Quantum) which was released just yesterday and it's a fresh clean install in a Windows 7 x64. I started to believe it's not related to the extension because the "LastPass" extension doesn't have focus too. I think it may be related to a browser bug. I'm not sure though.
Many thanks for your efforts.

Duplicate of #13


File stat (e.g., mtime) timestamps

This introduces a modular way to extract dates from files. This is useful to use the mtime stat instead of parsing the filename, as mentioned in #19.
The modularity is added by adding a Matcher object, an implementation that use the Filename, and another that uses the Stat information

@xolox Ok, this PR is good to go. Care to take a look?
Essentially, this adds a --stat-timestamp argument that uses the mtime of the file instead of trying to extract the date from the filename. To do so, I split out the date-extraction logic into a generic interface, so this potentially paves the way to other ways to get the date out.


MediaElement to use for audio playback

Hello! I am using MediaElement to play audio and video files in a chat.
On Windows, sound files look great:

But on Android, they don't look very good, and it's not very intuitive how to control playback (if you don't click on the control button element, you can't see anything):

I tried creating my element but it's not very stable:

Maybe you know how you can customize the display of MediaElement on Android to play audio files? I would be very grateful for your help!

@kravchenko-vi it might be best to ask this question over on the development repository at https://github.com/CommunityToolkit/Maui

More of a how to question than a docs issue. Closing this here.


Windows displays rubbish symbols in cmd

The same in Powershell and in ConEmu.
Maybe it is better to display just plain text in Windows env

Eaahh. It is... I know... Can anyone with Windows make PR with just text instead of emoji and utf-8 (♻)?

why was this closed ? The issue is still present.

Yes, but still need to be fixed. Anyone want to contribute?

I will probably get to it, during the holidays or sooner. But it is only one file Informer.php, that needs to be changed.

Can be temporary fixed with chcp 65001 before running deployer


Issue trying to set bounds using google_map_flutter

screenshot
Steps to Reproduce
The problem arose when I included the bounds
cameraTargetBounds: new CameraTargetBounds(
                    new LatLngBounds(
                      northeast: uniCampusNE,
                      southwest: uniCampusSW,
                    ),

_userLocation == null // If user location has not been found
              ? Center(
                  // Display Progress Indicator
                  child: CircularProgressIndicator(
                    backgroundColor: UniColors.primaryColour[500],
                  ),
                )
              : GoogleMap(
                  // Show Campus Map
                  onMapCreated: _onMapCreated,
                  initialCameraPosition: // required parameter that sets the starting camera position. Camera position describes which part of the world you want the map to point at.
                      CameraPosition(
                          target: _userLocation, zoom: defaultZoom, tilt: 0.0),
                  scrollGesturesEnabled: true,
                  tiltGesturesEnabled: true,
                  trafficEnabled: false,
                  compassEnabled: true,
                  rotateGesturesEnabled: true,
                  myLocationEnabled: true,
                  mapType: _currentMapType,
                  zoomGesturesEnabled: true,
                  cameraTargetBounds: new CameraTargetBounds(
                    new LatLngBounds(
                      northeast: uniCampusNE,
                      southwest: uniCampusSW,
                    ),
                  ),
                ),

Both iOS and Android, but testing on Android in the first instance

 Logs
I/flutter (20121): ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
[   +1 ms] I/flutter (20121): The following assertion was thrown building TheMap(dirty, state: _TheMapState#a687e):
[        ] I/flutter (20121): 'package:google_maps_flutter/src/location.dart': Failed assertion: line 68 pos 16:
[   +1 ms] I/flutter (20121): 'southwest.latitude <= northeast.latitude': is not true.
[        ] I/flutter (20121):
[        ] I/flutter (20121): Either the assertion indicates an error in the framework itself, or we should provide substantially
[        ] I/flutter (20121): more information in this error message to help you determine and fix the underlying cause.
[        ] I/flutter (20121): In either case, please report this assertion by filing a bug on GitHub:
[        ] I/flutter (20121):   https://github.com/flutter/flutter/issues/new?template=BUG.md
[        ] I/flutter (20121):
[        ] I/flutter (20121): Widget creation tracking is currently disabled. Enabling it enables improved error messages. It can
[        ] I/flutter (20121): be enabled by passing `--track-widget-creation` to `flutter run` or `flutter test`.
[        ] I/flutter (20121):
[   +5 ms] I/flutter (20121): When the exception was thrown, this was the stack:
[   +1 ms] I/flutter (20121): #2      new LatLngBounds (package:google_maps_flutter/src/location.dart:68:16)
[        ] I/flutter (20121): #3      _TheMapState.build (package:ManchesterMaps/widgets/home_pages/the_map/the_map.dart:155:25)
[        ] I/flutter (20121): #4      StatefulElement.build (package:flutter/src/widgets/framework.dart:4047:27)
[        ] I/flutter (20121): #5      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3941:15)
[        ] I/flutter (20121): #6      Element.rebuild (package:flutter/src/widgets/framework.dart:3738:5)
[        ] I/flutter (20121): #7      BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2348:33)
[   +1 ms] I/flutter (20121): #8      WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:760:20)
[        ] I/flutter (20121): #9      RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:280:5)
[   +1 ms] I/flutter (20121): #10     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1033:15)
[        ] I/flutter (20121): #11     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:975:9)
[        ] I/flutter (20121): #12     SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:891:5)
[        ] I/flutter (20121): #16     _invoke (dart:ui/hooks.dart:249:10)
[        ] I/flutter (20121): #17     _drawFrame (dart:ui/hooks.dart:207:3)
[        ] I/flutter (20121): (elided 5 frames from class _AssertionError and package dart:async)
[        ] I/flutter (20121):
[   +6 ms] I/flutter (20121): ════════════════════════════════════════════════════════════════════════════════════════════════════

flutter doctor
[√] Flutter (Channel stable, v1.9.1+hotfix.5, on Microsoft Windows [Version 6.1.7601], locale en-GB)
    • Flutter version 1.9.1+hotfix.5 at C:\SRC\flutter
    • Framework revision 1aedbb1835 (3 weeks ago), 2019-10-17 08:37:27 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\Users\mdehsasw\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 40.1.2
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] VS Code (version 1.39.2)
    • VS Code at C:\Users\mdehsasw\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.5.1

[√] Connected device (1 available)
    • SM G950F • ce041714c3a618da0d • android-arm64 • Android 9 (API 28)

• No issues found!

Hi @mdehsasw
for what I can see from the logs, the error
[        ] I/flutter (20121): 'package:google_maps_flutter/src/location.dart': Failed assertion: line 68 pos 16:
[   +1 ms] I/flutter (20121): 'southwest.latitude <= northeast.latitude': is not true.

I recommend you to check the code and satisfy the assertion that can be found in the plugin's code:
  LatLngBounds({@required this.southwest, @required this.northeast})
      : assert(southwest != null),
        assert(northeast != null),
        assert(southwest.latitude <= northeast.latitude);

This platform is not met for assistance on personal code.
Please see https://flutter.dev/community for resources for asking questions like this,
you may also get some help if you post it on Stack Overflow.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
Thank you


Replace/add to the custom plugin with a comment plugin

This will better demonstrate what we mean by an "active" editor. Such a plugin would allow comments to be entered, modified and deleted as well as listed separately in their own right.

Created a basic version which allows the user to create, update, resolve and delete comments.


fix crasher in subscription manager

CI stuck in allocating node. Since last commit passed, I just canceled it and am merging now.


Add model parallelism

We add our open sources related with the Transformers :)
The half moon is used to indicate that only a part of the model is running on a specific GPU.

I commit them !


#1865 Adjustments and refactor according to the reviewers suggestions

Description
Refactor InputFile.web.js
About #1865
Additional changes for #2012

Before fixing my comments please look at the following thing
After more detailed research i think we don't need getImageWithSrc & getReducedDataUrlFromImage
We already have getBase64FromImageUrl() in src/lib/API/api.js that loads image as base64 by its url and we have src/lib/utils/resizeBase64Image.js which resizes image given as base64
So everything you needed could be implemented using those two already existing helpers
Are there other reasons (probably performance) why you've added and used getImageWithSrc & getReducedDataUrlFromImage in this particular case ?

First of all this piece of code wasn't written by me.
As I see the main reason why getImageWithSrc used here is to get the width and height of the initial uploaded image to make further scale and resize manipulations.
getReducedDataUrlFromImage resizes and scale the image to be not more than 600x600.
I will try to get rid of these functions and use the existed two that you mention.

@yaroslav-fedyshyn-nordwhale please check my adjustments

Approved. Could be merged


--create-table-only配置项无效

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
flink-doris-connector-1.19-1.6.1
What's Wrong?
是否只仅仅创建表的结构
配置了仅创建，表的数据还是过去了
What You Expected?
是否只仅仅创建表的结构
配置了仅创建，表的数据还是过去了
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@raboof

Can you post the specific configuration?


Move hub/subscriber startup module tests to integration test module

Purpose

$Subject as port openings ideally should happen in the integration test framework.

Fixes #20001
Fixes #19891
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #20455   +/-   ##
=======================================
  Coverage   15.21%   15.21%
=======================================
  Files          50       50
  Lines        1341     1341
  Branches      208      208
=======================================
  Hits          204      204
  Misses       1121     1121
  Partials       16       16

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6a0dbdd...8bfaf3f. Read the comment docs.


[FEATURE REQUEST] add support for dash to panel

hi, i recently switch to dash to panel to have more customization option and minimalistic look, but it look like cronomix buttons dont want to jump on dash to panel, is there any possibility for that?.
thank you.
I use GNOME 45, on ubuntu 23.10.

just i send this screenshot for more details:
I left the original panel visible for the screenshot,
, but generally I make it disappear with the just perfection extension, normally to make the panel disappear I could have used the option included in dash to panel "keep original gnome-shell top panel", but if I deactivate this option to make the panel disappear, this causes a bug on other extensions which use the position of the panel to display their gui; but I think that will be the subject of another discussion if you allow me. THANKS.

i solve the problem it was a misunderstood with the way dash to panel organize the is panel,
thank you.


[Feature Request] Auto early stopping in Sklearn API

Is it possible to perform early stopping using cross-validation or automatically sampling data from the provided train set without explicitly specifying an eval set?

xgboost.cv() supports early stopping via cross-validated metrics.

@hcho3 modified the title. This is not available in the Sklearn API right?

No.

I will look into this one later.

Optuna actually does this for LightGBM through the LightGBMTunerCV method. But this is for automatic tuning. Something similar could be useful for XGBoost


Not validating New Numbers for India

http://libphonenumber.appspot.com/phonenumberparser?number=8660447360&country=IN
http://libphonenumber.appspot.com/phonenumberparser?number=7980123638&country=IN
These are new Numbers in India.
Even with the latest 7.7.3 version of the PHP API, we are Seeing these numbers as isValidNumber() false.
Kindly look into.

@Jayad ,
Thanks for providing all the details we need! We've accepted this issue and
will fix this in an upcoming release.
Please note that you have submitted this information with the knowledge that we
may use, modify, reproduce, publicly display, and distribute the information in
accordance with our open source policies. Please let us know if you did not
intend to submit the information for such use.

Please add and let me know the package version.

Sure.. :)

We do use this package and facing issues whenever a new vendor gets added as a client.
Like Reliance JIO user base is quiet huge in India now and launched a month or two back.
How to avoid such cases where new numbers (series) are getting from Service Providers added. Can there be a contributor role?

Hi Jayad,
What you did is right.
Once you verified in our demo that any valid number is marked as invalid, you can raise a bug from results page itself and provide supporting details to us. Please see our contribution
guidelines.
This issue is fixed in today's release 7.7.4
http://libphonenumber.appspot.com/phonenumberparser?number=8660447360&country=IN
In this release we added support for quite a number of Reliance Jio ranges based on evidences that we got.


DFD Algorithm integration

The DFD algorithm written by Patrick Schulze is a DUCC-like FD-discovery algorithm that is not yet integrated into Metanome. Hence, the following tasks need to be done:

extend the algorithm with a Metanome-konform wrapper that implements all required interfaces
place the extended algorithm into our algorithm repository and integrate it in the build process of this repository
test the algorithm in a Metanome instance on some datasets and enshure that the results are equal to the results of e.g. TANE, fdep, etc.

-first version is available in dfdIntegration branch of the algorithms repository
-it works correctly in Metanome
Todo:
review (maybe sdifferent run modes should be supported?) + integrate in build process


Crash when saving over existing file in x86 Windows builds (crashes before asking to replace)

Steps:

Create an x86 Windows build containing the BasicSampleScene in this repo.
Run the application and press "Save File" on the left buttons.
Choose an existing file (intention to overwrite).
Save.
Instead of the dialog asking to replace the file, the build will crash.

On x64 builds this does not happen (nor in the editor, which is also 64 bits). Any ideas of why this might be? Maybe this is a known problem.
We are testing this in Unity 2018.4.5f1, although this also happens on a production build made with 2017.4.11f1 (where we found the problem). We are using Mono (the build process crashes when using IL2CPP and we don't need it right now) and .NET 4.x Equivalent as the scripting runtime.
Best regards,
Daniel Lobo

I assume that, if confirmed, this would actually be an error in the dll for Windows.Forms...? (that is what the UnityStandaloneFileBrowser uses, right? Or some incompatibility between it and my system.

Sorry to ask again, but any ideas about this?


Label studio integration

What changes are proposed in this pull request?
A new annotation backend with Label Studio.
At the moment, images only.
How is this patch tested? If it is not, please explain why.
Integration testing is done with connecting to a local instance of Label Studio.

Get Label Studio up-and-running with pip or docker

pip install label-studio
label-studio start
# or docker
 docker run -d -p 8080:8080 \
            --name labelstudio \
            -v /tmp/labelstudio:/data \
            labelstudio/labelstudio

Get access token from account settings, set url and token in the environment:

export FIFTYONE_LABELSTUDIO_URL=<url>
export FIFTYONE_LABELSTUDIO_TOKEN=<token>

Release Notes
Is this a user-facing change that should be mentioned in the release notes?

[ ] No. You can skip the rest of this section.
[x] Yes. Give a description of this change to be included in the release
notes for FiftyOne users.
[x] Integration page write-up.

Annotate image classes, detections, polygons, etc. with Label Studio.
What areas of FiftyOne does this PR affect?

[ ] App: FiftyOne application changes
[ ] Build: Build and test infrastructure changes
[x] Core: Core fiftyone Python library changes
[x] Documentation: FiftyOne documentation changes
[ ] Other

Ah, yup, I needed to upgrade label-studio, I was on 1.4 previously. We'll need to make sure to set the requirements to label-studio>=1.5.0. Things are working great now!

That's on server side. We do not expect fiftyone to handle that, right? Maybe we can query the server version and give a warning if it's below 1.5.0? As for sdk version, can we specify a specific version with fou.lazy_import()?

Hey there, any updates on this?

@Rusteam Sorry for the delay! Yeah, you can require a minimum version of the sdk through the lazy import. It looks like this:
ls = fou.lazy_import(
    "label_studio_sdk", callback=lambda: fou.ensure_package("label_studio_sdk>=0.0.13")
)

But you're right, getting the version of the server would need to be done through a request and manual verification of the version. It seems that this would do it:
from packaging import version
server_version = self._client.make_request("GET", "/api/version").json()["release"]
version.parse(server_version) >= version.parse("1.5.0")

After this and the supports_attributes updates, I want to play with it a bit more, but then it will likely be ready to merge! Thanks again for making this PR, this is really good work!

thanks @ehofesmann  for a clear guide on how to use this integration and other updates.

Hi! I would be very interested in this integration. Is there an ETA for when it will be merged into FiftyOne? Thanks!

It's already merged and available as of fiftyone==0.18!
https://voxel51.com/docs/fiftyone/integrations/labelstudio.html

@brimoor ouch, you’re right, I didn’t notice the merged label! Thanks


Can we only do hyper parameter search?

Hey,
there is no option such as "do_hpo_only" since you would have to specify an architecture. What you could do of course, is to update the search space to only allow for one architecture (e.g. a mlpnet with 1 layer and 20 units) using the updating api demonstrated on the main page.

@LMZimmer Allowing only one architecture seems great idea. And developing it further, I suggest that  we do hyper parameter search with custom fixed architecture.
We can do further to set certain part of architecture fixed and certain part of architecture searched. Anyway for my purpose right now, I would do appreciate if I could do hyperparameter search with my custom pytorch model :)


Flip the order of gamma and beta in function get_qaoa_circuit

Flip the order of gamma and beta in function get_qaoa_circuit present in qaoa_circuit_maxcut.py circuit generation

I think #38 refers to flipping the order of the gamma and beta arguments to be consistent with other parts of qokit (which may involve additional modifications to code that calls this function), not the order of circuit generation.

thanks the review


How to find cause of RedisCommandTimeoutException from log

【lettuce-version】5.1.2.RELEASE
【redis-version】3.2.9
【spring-data-redis】2.1.2 RELEASE
Question Report
Hello~ I am a rookie in using lettuce, when using lettuce in the project and set timeout= 150ms, sometimes I can see QueryTimeoutException as below, and I don't know why it happened...I have tried to change the configurations like socket、 tcp-keepalive and use a connection pool to solve it but failed.
The Exception is：
[GET]Failed.key=xxxxxx
org.springframework.dao.QueryTimeoutException: Redis command timed out; nested exception is io.lettuce.core.RedisCommandTimeoutException: Command timed out after 150 millisecond(s)
        at org.springframework.data.redis.connection.lettuce.LettuceExceptionConverter.convert(LettuceExceptionConverter.java:70)
        at org.springframework.data.redis.connection.lettuce.LettuceExceptionConverter.convert(LettuceExceptionConverter.java:41)
        at org.springframework.data.redis.PassThroughExceptionTranslationStrategy.translate(PassThroughExceptionTranslationStrategy.java:44)
        at org.springframework.data.redis.FallbackExceptionTranslationStrategy.translate(FallbackExceptionTranslationStrategy.java:42)
        at org.springframework.data.redis.connection.lettuce.LettuceConnection.convertLettuceAccessException(LettuceConnection.java:268)
        at org.springframework.data.redis.connection.lettuce.LettuceStringCommands.convertLettuceAccessException(LettuceStringCommands.java:799)
        at org.springframework.data.redis.connection.lettuce.LettuceStringCommands.get(LettuceStringCommands.java:68)
        at org.springframework.data.redis.connection.DefaultedRedisConnection.get(DefaultedRedisConnection.java:253)
        at org.springframework.data.redis.connection.DefaultStringRedisConnection.get(DefaultStringRedisConnection.java:377)
        at org.springframework.data.redis.core.DefaultValueOperations$1.inRedis(DefaultValueOperations.java:57)
        at org.springframework.data.redis.core.AbstractOperations$ValueDeserializingRedisCallback.doInRedis(AbstractOperations.java:59)
        at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:224)
        at org.springframework.data.redis.core.RedisTemplate.execute(RedisTemplate.java:184)
        at org.springframework.data.redis.core.AbstractOperations.execute(AbstractOperations.java:95)
        at org.springframework.data.redis.core.DefaultValueOperations.get(DefaultValueOperations.java:53)
        at com.netease.mail.yanxuan.rms.cache.redis.spring.AbstractRedisClient.get(AbstractRedisClient.java:496)
       。。。。。。
Caused by: io.lettuce.core.RedisCommandTimeoutException: Command timed out after 150 millisecond(s)
        at io.lettuce.core.ExceptionFactory.createTimeoutException(ExceptionFactory.java:51)
        at io.lettuce.core.LettuceFutures.awaitOrCancel(LettuceFutures.java:114)
        at io.lettuce.core.cluster.ClusterFutureSyncInvocationHandler.handleInvocation(ClusterFutureSyncInvocationHandler.java:123)
        at io.lettuce.core.internal.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:80)
        at com.sun.proxy.$Proxy69.get(Unknown Source)
        at org.springframework.data.redis.connection.lettuce.LettuceStringCommands.get(LettuceStringCommands.java:66)
        ... 66 common frames omitted

after checking the debug log, it seems that the timeout happened after
00:57:43.525 [lettuce-nioEventLoop-4-6] DEBUG i.l.core.protocol.CommandHandler - [channel=0x833d0c11, /<IP_ADDRESS>:29547 -> /<IP_ADDRESS>:16380, chid=0x1e] write(ctx, ClusterCommand [command=AsyncCommand [type=GET, output=ValueOutput [output=null, error='null'], commandType=io.lettuce.core.protocol.Command], redirections=0, maxRedirections=5], promise)

after this log, the next log is printed at 00:57:44.113, means timeout
happened. I can see other commands without timeout  have two more logs with prefix like lettuce-nioEventLoop-a-b (together 3 logs) , such as:
00:57:43.525 [lettuce-nioEventLoop-4-8] DEBUG i.l.core.protocol.CommandHandler - [channel=0x742eb139, /<IP_ADDRESS>:50634 -> /<IP_ADDRESS>:16380, chid=0x20] Received: 11 bytes, 1 commands in the stack
00:57:43.525 [lettuce-nioEventLoop-4-8] DEBUG i.l.core.protocol.CommandHandler - [channel=0x742eb139, /<IP_ADDRESS>:50634 -> /<IP_ADDRESS>:16380, chid=0x20] Stack contains: 1 commands

but the command which caused timeout not (just 1 log), so .. how can I find why timeout happened?
Another question
the log stack contains is always 1 command, is it normal? For example
1 commands in the stack
Stack contains: 1 commands

Sorry my English is pool, thank for your time to look at my question~

Command timeouts are usual to happen. If Redis responds with a lot of data, Redis Cluster issues redirects, you have very small timeouts or if you set setAutoFlushCommands(…), then timeouts are likely to happen.
The log above contains multiple times the exact same time value (00:57:43.525) for different connections. It's easy to tell these are different connections because different connections typically run on different event loop threads. Also, channel Id's are different. When analyzing a command message flow, make sure to group same channelId's.

the log stack contains is always 1 command, is it normal? For example

Yes, if there is a single command that was sent, a single command awaits response processing. On systems with higher loads, these numbers are higher.

how can I find why timeout happened?

You need to analyze the log to reconstruct the command flow to see which command took a long time to execute.
There's nothing more we can do from our side, therefore closing this ticket.

Thank you for your help~ what I mean is [lettuce-nioEventLoop-4-6] and [lettuce-nioEventLoop-4-8] happens at the same time, and [lettuce-nioEventLoop-4-8] is normal which has three logs, the [lettuce-nioEventLoop-4-6] is one of timeout commands so it just has 1 log, because of the timeout it didn't have the log including 'Received:'.
I will check If Redis responds with a lot of data and the setAutoFlushCommands , thank you

The log event above indicates that the command was written to the transport. So it's now outside of the client and somewhere between your network interface and your Redis server. If there was no received log event this means that Redis didn't respond.

The log event above indicates that the command was written to the transport. So it's now outside of the client and somewhere between your network interface and your Redis server. If there was no received log event this means that Redis didn't respond.

Thank you very much!


High CPU when editing C# files in large project. Mono process blows up to 170% on Macbook Air 2020 i5

Hi there
My Angular/.Net Core application (w/ VS Code) is fairly large, when I go and start editing C# files. I have an issue with the C# extension by Omnisharp. The running process 'mono' will run at 170% of my CPU. The fans kick on and in most situations don't stop. In some cases, I'll have to restart VS Code and open it back up again.
In most cases the CPU% and fan will subside, but it might take 20-30 seconds of little or no code editing. If I edit specific files (ex. automapper mapping code) the CPU% goes up to 170% and doesn't stop. I can leave the room and come back 10 minutes later and it's still wizzing away at 170%. All coming from the 'mono' process (C# extension by Omnisharp) in the activity monitor.
QUESTION - Are there log files somewhere that I can capture and look at to see if there are errors in the different  projects that might be causing this issue? If yes how do I capture/get them?
The solution structure is an Angular app for the client. A .Net Core app for the backend (controllers, DTO's, etc) and then I have 2 other .Net dll's that are for the models, enums, etc and one for the DB stuff like DB access and other 3rd party services.
FYI - I posted my issue on SO here - https://stackoverflow.com/questions/69775717/c-sharp-extension-for-visual-studio-code-blowing-up-my-macbook-air-2020-intel-i5
I'm using the C# extension v1.23.16
here is my >dotnet --info
.NET SDK (reflecting any global.json):
Version:   5.0.100
Commit:    5044b93829
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.15
OS Platform: Darwin
RID:         osx.10.15-x64
Base Path:   /usr/local/share/dotnet/sdk/5.0.100/
Host (useful for support):
Version: 5.0.0
Commit:  cf258a14b7
.NET SDKs installed:
3.1.201 [/usr/local/share/dotnet/sdk]
3.1.301 [/usr/local/share/dotnet/sdk]
5.0.100 [/usr/local/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 3.1.3 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.5 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.3 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download

@chuckdawit I am currently having a similar problem caused by working on a large codebase using VSCode's remote features via OmniSharp. Although the remote machine (Ubuntu 20.04) is equipped with the latest AMD processor and a huge amount of RAM, the mono process runs for about 6 hours on this codebase, consuming about 1.2 GB of RAM (only!). Disabling editor.CodeLens helped to work around this problem for me. This causes the mono process to finish in about 1:45 minutes, while still consuming about the same amount of main memory.


Update docs to clarify that an implicit collection can not have an index

Signed-off-by: Matthew B White<EMAIL_ADDRESS>

Type of change

Documentation update

Description
An updated tutorial on private data collections to note that the implicit collections can not have indexes
Related issues
FAB-17916 https://jira.hyperledger.org/browse/FAB-17916

@mergifyio backport release-2.3

@mergifyio backport release-2.2


Feature/esy 6224 design guide update

 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.


Use quotes instead of angles for an  include in compute/global_operations

What component of google-cloud-cpp is this related to?
google/cloud/compute/global_operations
Describe the bug
This autogenerated line
https://github.com/googleapis/google-cloud-cpp/blob/1d94ab4a94ae5ddae44056e868aa15feaa2a9b29/google/cloud/compute/global_operations/v1/global_operations_connection_idempotency_policy.h#L24
should be quoted.
To Reproduce Steps to reproduce the behavior:
cc_binary(
name = "gcp_bug",
srcs = ["gcp_bug.cc"],
deps = [
"@com_github_googleapis_google_cloud_cpp//:compute_instances",
],
)
bazel build : gcp_bug
results in:
external/com_github_googleapis_google_cloud_cpp_2/google/cloud/compute/global_operations/v1/global_operations_connection_idempotency_policy.h:24:10: error: 'google/cloud/compute/global_operations/v1/global_operations.pb.h' file not found with <angled> include; use "quotes" instead
#include <google/cloud/compute/global_operations/v1/global_operations.pb.h>

Expected behavior
It should build.
Operating system:
PRETTY_NAME="Debian GNU/Linux rodete"
What compiler and version are you using?
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 13.2.0-4' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs --enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-13 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-13-oyarai/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-oyarai/gcc-13-13.2.0/debian/tmp-gcn/usr --enable-offload-defaulted --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-serialization=28
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Debian 13.2.0-4)
What version of google-cloud-cpp are you using?
https://github.com/googleapis/google-cloud-cpp/archive/v2.16.0.tar.gz
Additional context
I see that this might be intentional.
https://github.com/googleapis/google-cloud-cpp/issues/3598
If so, can you suggest changes on my side to fix this.

I see that this might be intentional.
https://github.com/googleapis/google-cloud-cpp/issues/3598
If so, can you suggest changes on my side to fix this.

Yes.  But maybe we can change our intentions.  Some background: with MSVC, the code generated by Protobuf has more warnings that one cares to deal with.  We wanted to see warnings in our code, and suppress warnings for code in Protobuf, or gRPC, or any "external" projects.  We use these:
https://github.com/googleapis/google-cloud-cpp/blob/1d94ab4a94ae5ddae44056e868aa15feaa2a9b29/ci/gha/builds/lib/bazel.sh#L63-L69
You may be able to enable angle brackets in your code with something like this:
https://github.com/googleapis/google-cloud-cpp/blob/main/bazel/googleapis.BUILD
Which you would enable in your workspace file (or workspace function):
https://github.com/googleapis/google-cloud-cpp/blob/1d94ab4a94ae5ddae44056e868aa15feaa2a9b29/bazel/google_cloud_cpp_deps.bzl#L164
Maybe we should add the includes directive to our Bazel files (at least for the proto libraries) so folks don't need to add the directive themselves.  Let me give that a try.
/FYI: @scotthart

I am not clever enough to use  includes in our Bazel files.  All my attempts end-up with Bazel telling me off.
Changing all the code to include with quotes is "easy".  But requires changes to the code generator, and then changes to the CMake build scripts, and then changes to the CI scripts.

Thnx @coryan for getting back to me! The idea you proposed does not seems to work, as we have confirmed offline.
It does seem that the switch to using quotes would be beneficial for the adoption of this SDK, even though it does require a few steps on your side.

Thanks for the detailed bug report.  The fixes are available from the main branch on GitHub.  If you prefer to use a release, the next release should happen around the first week of 2023-11.


Remove POST /search retry logic (reverts b2a87f)

Codecov Report

Merging #429 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #429      +/-   ##
==========================================
+ Coverage   85.63%   85.68%   +0.04%
==========================================
  Files          39       39
  Lines        1859     1844      -15
==========================================
- Hits         1592     1580      -12
+ Misses        267      264       -3

Impacted Files
Coverage Δ

hca/util/__init__.py
86.66% <100%> (+0.26%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update daed677...3e1543e. Read the comment docs.

Codecov Report

Merging #429 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #429      +/-   ##
==========================================
+ Coverage   85.63%   85.68%   +0.04%
==========================================
  Files          39       39
  Lines        1859     1844      -15
==========================================
- Hits         1592     1580      -12
+ Misses        267      264       -3

Impacted Files
Coverage Δ

hca/util/__init__.py
86.66% <100%> (+0.26%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update daed677...3e1543e. Read the comment docs.


GCP align spring cloud 2021.0.0

GCP align spring cloud 2021.0.0

@m1ngyuan can you please add some mere description (link to the doc/issue) why artifact changed? Thanks!

Nevermind, I've found. :)
Spring Cloud GCP is no longer part of the Spring Cloud release train. The new repository location is https://github.com/GoogleCloudPlatform/spring-cloud-gcp. If you are upgrading from version 1.x, take a look at the migration guide to upgrade from version 1.x to 2.0.0 (or later).
https://spring.io/projects/spring-cloud-gcp


coqa not working

This happened once before and got fixed: https://github.com/EleutherAI/lm-evaluation-harness/issues/898
But now it seems not working again with same error, at least on my end.
  File "/home/lchu/.conda/envs/main/lib/python3.9/site-packages/datasets/builder.py", line 1726, in _prepare_split_single
    for key, record in generator:
  File "/lustre/.cache/huggingface/modules/datasets_modules/datasets/EleutherAI--coqa/9ee0502938f8c0d66e6801438f1d1814a99e5a6cbe1e4298869bfb62c2c7596d/coqa.py", line 183, in _generate_examples
    data = json.load(f)
  File "/home/lchu/.conda/envs/main/lib/python3.9/json/__init__.py", line 293, in load
    return loads(fp.read(),
  File "/home/lchu/.conda/envs/main/lib/python3.9/json/__init__.py", line 346, in loads
    return _default_decoder.decode(s)
  File "/home/lchu/.conda/envs/main/lib/python3.9/json/decoder.py", line 337, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/home/lchu/.conda/envs/main/lib/python3.9/json/decoder.py", line 355, in raw_decode
    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Thanks for the report, will have to take a look at the dataset!

@haileyschoelkopf Still experiencing the same error on CoQA, are there any updates on this one?


Extremely low yields in PIX 2021

Please, check the Compare years results.
In KRN, several yields were low, but some were greater than in 2020.
In PIX, *all yields are much lower. We need to confirm that there are no errors in calculations or field measurements.

Visually the subunits at PIX looked pretty low this year. I need to check through the calculations. One issue (maybe unrelated) that I noticed is that we did not survey subunit 5, but it still has values in the calculations. It's an upland unit

OK. We identified VP globalid == {43322E8E-D9FB-422C-9DA2-5F3D993DFEAA} as being incorrectly classified as unit 5 but it should be PIX-4. I will correct in data correction step of main script and follow up with Eric.
Based on conversations with RB and TB, the low values in PIX are consistent with field observations. This issue is closed.


add getModerationOptions

Checklist

[ ] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[ ] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[ ] I have updated/added tests for new/updated/fixed functionality.
[ ] I have updated/added dartdoc comments with ///.

Breaking Change

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

Related Issues

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (2914f8e) 80.39% compared to head (9f2ad2e) 83.75%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1031      +/-   ##
==========================================
+ Coverage   80.39%   83.75%   +3.36%
==========================================
  Files         318       20     -298
  Lines        4044      197    -3847
==========================================
- Hits         3251      165    -3086
+ Misses        793       32     -761

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Screen corrupts on Wayland

The screen is distorted with high rate with flutter 3.7.0.

It seems this symptom depends on Ubuntu 22 (GNOME).

Is this issue possibly related to https://github.com/flutter/flutter/issues/119601? Does it only occur under some specific conditions (Ubuntu/Wayland)?

Could be. Thanks for the information. Actually, I was not able to reproduce this issue on X11 backend and Sway (Wayland compositor). I can reproduce it only on Ubuntu 22 (GNOME, Weston).

Can you patch this when building flutter engine in CI pipeline? From my testing, the following patch solves this issue:
diff --git a/shell/platform/embedder/embedder_surface_gl.cc b/shell/platform/embedder/embedder_surface_gl.cc
index 44b1fddf80..5b64ad2e28 100644
--- a/shell/platform/embedder/embedder_surface_gl.cc
+++ b/shell/platform/embedder/embedder_surface_gl.cc
@@ -88,8 +88,7 @@ SurfaceFrame::FramebufferInfo EmbedderSurfaceGL::GLContextFramebufferInfo()
   // Enable partial repaint by default on the embedders.
   auto info = SurfaceFrame::FramebufferInfo{};
   info.supports_readback = true;
-  info.supports_partial_repaint =
-      gl_dispatch_table_.gl_populate_existing_damage != nullptr;
+  info.supports_partial_repaint = false;
   return info;
 }

I'm considering adding populate_existing_damage support instead.


[Enchancement] Allow arrays for styling bar charts on per dataset basis

I am working with data that requires comparing the relative numbers of crime types, and as such I only have one dataset at a time, but I would like each bar to be colored in relation to the crime it represents.
While I already have the code ready, and am about to make a PR, the guidelines for contributing stated I should open an issue as well.
While I saw a different PR for doing this with the fillColors, I wanted a solution that would work with all four of the styling options.

Hello, I'm sorry this issue hasn't received much attention yet. It seems this is an implementation question, could you please post your question to StackOverflow with the Chart.js tag and include a link here. This will ensure your question reaches the largest audience.
https://stackoverflow.com/questions/tagged/chart.js

This issue is more of a formality, I suppose, as I've already done the work to implement this. I opened this issue because the guidelines for contributing stated we should have an issue before a PR, except I'd already done the coding before I read the guidelines, so this doesn't serve much of a purpose, I suppose.
My PR for this is #922
Other PR's that touch on some aspect of this, in reverse chronological order, are #942 and #681.

Closing as this is supported in v2 natively.


Clean natting rules for a bridge on delete

Codecov Report

Merging #173 into 1.1.0-alpha will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           1.1.0-alpha     #173   +/-   ##
============================================
  Coverage        16.81%   16.81%
============================================
  Files               15       15
  Lines             1029     1029
============================================
  Hits               173      173
  Misses             845      845
  Partials            11       11

Impacted Files
Coverage Δ

base/pm/pm.go
0% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7550171...f20a34e. Read the comment docs.


Moved @aws-sdk/types to peer dependencies to resolve incompatibilities

Issue #, if available:
#439
Description of changes:
As title, based off customer's comment and AWS SDK recommendation. This way, we will be able to use whatever version of @aws-sdk/types is provided by the customer, which should resolve the error reported in #439. Tested on a sample app to verify instrumentation still works.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/cc @alexforsyth from AWS SDK V3

Codecov Report

Merging #449 (56d9d97) into master (73e6ba8) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #449   +/-   ##
=======================================
  Coverage   82.48%   82.48%
=======================================
  Files          36       36
  Lines        1741     1741
=======================================
  Hits         1436     1436
  Misses        305      305

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 73e6ba8...56d9d97. Read the comment docs.

Actually, after testing this with verdaccio, I realized this change will cause an issue similar to #411 in that users of this SDK who do not use the AWS SDK V3 (and therefore do not have @aws-sdk/types package available) will fail to compile. Therefore to maintain functionality for all users of this SDK, we must keep the types package as a proper dependency.

I think that with npm v6 and yarn, the non-installed peer dependencies are just logged as a warning during the install. And I see the npm v7 installs them by default now (https://stackoverflow.com/questions/35207380/how-to-install-npm-peer-dependencies-automatically).
I recall AWS SDK or some other libs have peer dependency on some frontend stuff for react etc., that is not needed nor installed when developing for Node.JS.
Let me check how it behaves on my own as well.

That is interesting that npm v7 installs them by default - sounds like that will solve this long-term but I think many people are still using npm 6 or less. It does in fact work with native JS (as long as you don't call the captureAWSV3Client API, which you wouldn't if you don't have an AWS SDK V3 dependency). Where it fails for me is running tsc on a project that uses aws-xray-sdk-core and does not satisfy the @aws-sdk/types dependency.

Ok, I reproduced the same on my own, and I see the problem.
I hoped that this: https://stackoverflow.com/a/63905376/2512304 can be the solution, but a quick test with changing the
import { Client } from '@aws-sdk/types';

to
import type { Client } from '@aws-sdk/types';

still results in a tsc error when @aws-sdk/types is not installed (in the client module that uses aws-xray-sdk-core). I either did something wrong or it's not a solution for this problem (again, only did a quick test).
I see that for the AWS SDK v2 you ignore the type completely: https://github.com/willarmiros/aws-xray-sdk-node/blob/peer-types/packages/core/lib/patchers/aws_p.d.ts#L7
While it would be best to have the captureAWSv3Client() fully typed, maybe it's better to not use @aws-sdk/types at all and do a similar signature here?
export declare function captureAWSClient<T>(client: T, manualSegment?: SegmentLike): T

As I see it:

right now, the client type is checked only if I match the same @aws-sdk/types version as the xray lib uses,
otherwise, I have to disable type checking on my own (with client as any).

Since you won't be releasing a new xray lib version every time there is a new AWS SDK v3 release, keeping @aws-sdk/types in sync would require using the old AWS SDK v3 lib version (that xray lib uses) and never update. In practice, I guess everyone will have to use as any. So from my perspective, it's far better to release the type restriction on the xray lib itself, getting rid of @aws-sdk/types completely here and making the function signature similar to the one for AWS SDK v2.
Well, it's my opinion and I can be wrong here, so please let me know what you think. It just hurts me when I have to do captureAWSv3Client(client as any) in my code 😄

@willarmiros Can there be a decision made about how to deal with this issue? Either kill this PR so it doesn't appear in searches as a possible solution, or make a PR that addresses the problem by removing types. I have trained up 5 developers on using XRay now and every single one of them would have run into this issue and been confused if I hadn't built my own wrapper library around XRay to specifically as any (and then I have to explain to them why they have to use my library and ignore all the online documentation about how to wrap AWS SDK clients in XRay).
It seems like a pretty major issue that capture simply does not work per all the documentation about how to use it for a (growing) number AWS SDK v3 clients.

@thesuavehog sorry for your frustration with this issue. I'll add it to the agenda for our team to discuss next week.
In the meantime have you considered using the AWS Distro for OpenTelemetry (ADOT) - JavaScript solution?
OTel JS gets a lot of support from many devs and we announced GA support for it last year. All components are upstream and ready for you to use to trace with OTel JS and AWS X-Ray 🙂 We've been recommending users check that out so maybe you'll find excellent instrumentation there with minimal changes needed to get it working?
Let me know if you have any questions!


Failure to solve on Raspberry PI

Following on from the indilib forum msgs I’ve finally managed to get an image.
It solves using the inbuilt, local astrometry.net and astap on the Pi and also the online astrometry.net and online Watney solvers. However the local Watney just says failed. I have the watneyqd-08-09-20 and 00-07-20 quad dbs installed.
Attached are the fits file and a screenshot of the Pi

and the fits file
solve1fail.zip

Hi @nigeldun!
It would seem that you were indeed unlucky with this one. I'm hoping this is more of an exception than the norm for you. Looking at the log, looks like you're using the Internal SEP for star extraction, which is good. Watney also comes with its internal star detection algorithm which is quite crude but most of the time works just fine. When using KStars I've personally used the Internal SEP (with the default settings) with Watney with no problems for 99% of the time - it's good, no doubt about that.
So: internal SEP extractor is good but in case you find better and more consistent success with the Watney internal ("BuiltIn Method") star detector then maybe consider switching to that. I suppose trial and error will tell you which one works better for you. I think your case mostly boils down to pure luck with how the stars were detected and ranked and how the quads were formed from them. When there aren't a lot of stars visible, even a single star can make a big difference.
As you noted, it solved using astrometry.net, ASTAP and the Watney's online solver (it uses the Watney's own default star detector). Also running your sample FITS image through the console solver with default parameters (again using Watney's own star detector) it solved fine. I was actually worried that the bayering pattern in your image would have resulted in less accepted stars but it didn't cause any notable problems.
So as a summary, depending on a lot of things your mileage may vary. Not a very helpful answer I know ;) but it can happen. Maybe tweaking the star extractor profile or picking another profile will help to provide a better experience.

hmm, unfortunately I’ve failed every time i’ve tried to use it so it’s not just that particular image. It will be the approx same setup and exposure though so possibly a lack of stars or whatever.
Is there a debug switch I can apply to get more detail as it does seem to fail very (very) quickly? Just in case it’s something like a permission’s problem or something else.

I see. First things first, is your configuration correct? Is the path to the quad database correct?
Secondly you can test if the image solves from command line:
cd /path/to/watney
./watney-solve blind -i /path/to/image.fits

Also to get log output, you can use --log-file /path/to/logfile.txt
The image you attached here should solve - it does for me. Also if your configuration is incorrect, it's likely you'll get an error and you can then post it here if it's cryptic.
You can also turn on the logging from KStars. Open Ekos, click the Logs button, make sure it's set to verbose and in Astrometry select LOG_ALL, tick the box to "Separate log file" and set a file name where to write the log. The next solve you make in KStars should then write to the log file.

Also just in case, the wiki has a quickstart guide: https://github.com/Jusas/WatneyAstrometry/wiki/Quickstart-Guide

Ah there’s another logging switch is there. Thought I had turned them all on.
I will give your suggestions a try and see what happens.

I’ve tried running watney from the cmdline however it crashes. I’ve deleted and reinstalled both the program and quad db but with the same result. I’ve attached the log file
watney.log

Thanks, this was very helpful. It's indeed a bug - I'll have to take a closer look. Can you tell me which Raspberry Pi you're using, and also the operating system?

It’s a Raspberry Pi 4 4gb with astroberry 2.04 installed and updated.

Oh, one more thing, can you run uname -a in terminal and post the output?

astroberry@astroberry:~ $ uname -a
Linux astroberry 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux
astroberry@astroberry:~ $

Thanks!
I ran this on my Pi4B running Ubuntu Mate 64bit and that seemed to run fine using the arm64 build. I did run the benchmarks using this setup so I'm fairly sure it's fine. Now going back to my old Pi (it's Pi2 I think, and installed Raspberry Pi OS 32bit on it) I managed to reproduce this bug - this should significantly help to nail this down. So I think the 64bit OS has no issues but the 32bit does.
I can't yet say how easy or quick it is to fix this but now at least I can confirm it and work on it.

@nigeldun I just pushed a fix, and on my end it looks like this did indeed fix the issue. Can you please confirm by downloading the latest development build (the ones with "latest" in the name), available here: https://github.com/Jusas/WatneyAstrometry/releases/tag/bleeding-cli
I think the one you need is this: https://github.com/Jusas/WatneyAstrometry/releases/download/bleeding-cli/watney-solve-bleeding-latest-linux-arm.tar.gz
If this runs your solve without errors, I'll publish this as a new stable version.

@Jusas ok I’ve tried it and it now returns successfully with what are I believe the correct coords.
In blind mode it seemed to take a while to solve while in nearby mode it was under 2 secs.  For comparison astap took around the same time - I assume doing a nearby solve as well.

Yeah not to worry, the blind solve is expectedly slow especially on something like the Pi - bottom line is, the problem is fixed. I'll release a new stable version v1.1.2 shortly but you may keep using what you now have as it's effectively the same thing.
Thanks for reporting this because it appears that this was an issue that affected all 32bit ARM processors with 32bit Linux installations running on ARM processors so I'm really glad it was spotted. Testing this on several platforms and operating systems is a lot of work and things like this can slip in unnoticed.
I hope this works out for you, and clear skies :)
I'm closing this issue as the problem is resolved.


fix: add export providePGlite and injectPGlite

Whoops, thank you for catching that!
Looks good, could you please add a patch changeset using pnpm changeset at the root level of the repo and following the instructions?
I have added patch changeset, please review again.

I'm running into this issue, when can we expect 0.2.8?

Hopefully tomorrow, and if not Thursday.


Code-like data should be in a monospaced font

This makes reading all the data in the tables much easier to process, as it is in code.

Hrm, looks like you should only need to set this CSS for 'table' but the reset rules are making it more complicated. The reset block should really set "font: inherit" with a separate rule to set the default font for the toolbar. I can patch that in the morning if that wasn't clear.
Also, could you share the font list used for the "code" tag a bit lower in the CSS?

I've updated the font reset to be easier to override.  I kind of prefer the existing mono fonts, and just on the tbody contents instead of the headers too.
Take a look at this and let me know what you think: https://github.com/mgood/flask-debugtoolbar/commit/93008a8e53b83db8b5565ede9e131acb785f2f21

Awesome, thanks ;)


webkit-fake-mousemove-fix patch

I applied the patch to all browsers mindlessly, it turns out that "event.movementX" and "event.movementY" are Webkit-specific event properties.
I apologize for my mistake. Please be merciful.

Hmm, this has reminded me I still don't have coverage in the unit tests for DOM events triggering the interrupt :(

I need to figure out how to do that for the webapp I'm making, so if you haven't added any by the time I start making those, I'll create a pull request to add them.

I do have a test, but it's commented out (see https://github.com/HackedByChinese/ng-idle/blob/develop/src/idle/idle.spec.js#L389) because of the reasons mentioned in the comment. I (or someone) just need to figure out the deal with that and then we're covered. However, we'll want to add another test to cover WebKit, which prompts the suggestion that we change your commit to not reference navigator directly, but try to access it off $window so it is more easily unit tested.

I've changed the code to use the $window object so that when one of us figures out how to fix the unit tests there will be no compatibility issues.

I think I have fixed that unit test.  I could be wrong, but it's in my pull request.  I have two unit tests which covers the standard interrupts, and also one which covers my use case for uninterrupting.  I know the tests have passed, but I'm a bit of a noob when it comes to angular unit testing so be gentle if you find something wrong with it.

@joero4 I think he's referring more to the fact that we need unit tests for all the interrupt events in order to check for bugs in at least the major browsers, but if your unit tests pass then maybe we should use them as an example for further expansion of unit tests.

They do pass, and testing only the 'mousedown' event right now.  It's simply a jquery trigger of the event, so no real browser testing.
The comment in the code in the test is...
// HACK: the body event listener is only respected the first time, and thus always checks the first Idle instance we created rather than the one we created last.
      // in practice, the functionality works fine, but here the test always fails. dunno how to fix it right now.

I'm not sure I understand his note on checking he first instance vs the last.  Maybe it's my lack of understanding for angular unit tests.  Also his test failed, but I found some errors in the code, which I think was due to some older code which was updated, but the test was never updated to reflect the updates.  Just a guess though.  Either way the test now passes, and seems to work as expected.

A more recent set of changes to address this issue will supercede this PR.


Move gluon model zoo tests to nightly

Moving model zoo tests to nightly would cut ~10m from each CI round.
test_gluon_model_zoo.test_models ... testing forward for resnet18_v1
testing forward for resnet34_v1
testing forward for resnet50_v1
testing forward for resnet101_v1
testing forward for resnet152_v1
testing forward for resnet18_v2
testing forward for resnet34_v2
testing forward for resnet50_v2
testing forward for resnet101_v2
testing forward for resnet152_v2
testing forward for vgg11
testing forward for vgg13
testing forward for vgg16
testing forward for vgg19
testing forward for vgg11_bn
testing forward for vgg13_bn
testing forward for vgg16_bn
testing forward for vgg19_bn
testing forward for alexnet
testing forward for inceptionv3
testing forward for densenet121
testing forward for densenet161
testing forward for densenet169
testing forward for densenet201
testing forward for squeezenet1.0
testing forward for squeezenet1.1
testing forward for mobilenet1.0
testing forward for mobilenet0.75
testing forward for mobilenet0.5
testing forward for mobilenet0.25
testing forward for mobilenetv2_1.0
testing forward for mobilenetv2_0.75
testing forward for mobilenetv2_0.5
testing forward for mobilenetv2_0.25
ok (480.3409s)

@mxnet-label-bot add [Test, Gluon]

https://github.com/apache/incubator-mxnet/issues/14636

@larroy This makes sense. Is there any PR in the works or do we need a discussion on this before moving?

not that I know of.


[MM-18992] Migrate 'components/status_icon.jsx' to TypeScript

Summary
Migrate 'components/status_icon.jsx' to TypeScript
Ticket Link
https://github.com/mattermost/mattermost-server/issues/12437

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-5223.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

Test server destroyed


image tags not saving after upload

Hi,
We're experiencing a bug when an image is uploaded and you can tag it straight away, the tags don't get saved, Our users need to go into images, then click on the image, and add tags a second time for them to stick.
i have a feeling we had this before but it was fixed? but I could be wrong.
Thanks
Joss

I can confirm this. Steps to reproduce:

Select 'Images' from the admin side bar.
Press 'Add an image' button in the header.
Drag-drop/click to upload an image or three to upload. Number or method do not seem to matter here.
Once they have uploaded, add a tag to one of the images, and hit 'Update'.
Navigate back to 'Images', and select the newly uploaded image.
On the edit page, note the lack of tags.

You can successfully tag images from edit page, but not from the inline quick editor.

Looking in to it a bit more, it seems that tags entered are not POSTed to the backend from the multiuploader page, but are POSTed properly from the regular edit page.

Alright, I tracked it down. That was an annoying bug...
It seems that tagit is getting initialised twice for this one input. Once through the <script> tag appended to the AdminTagWidget output, and once from add-multiple.js. This double up, combined with the generic nature of the .tag_field input selector, ultimately means that the generated input for the first tagit instance is turned in to another tagit instance, and the tags entered in to the new tagit instance are not saved to the real input. Thus, no tags.

hier oder dort?
On Sun, 24 Jan 2016 18:29:52 -0800, Tim Heap<EMAIL_ADDRESS>wrote :

Alright, I tracked it down. That was an annoying bug...
It seems that tagit is getting initialised twice for this one input.
Once through the <script> tag appended to the AdminTagWidget
output, and once from
add-multiple.js.
This double up, combined with the generic nature of the .tag_field input selector, ultimately means that the generated input for the
first tagit instance is turned in to another tagit instance, and the
tags entered in to the new tagit instance are not saved to the real
input. Thus, no tags.

Reply to this email directly or view it on GitHub:
https://github.com/torchbox/wagtail/issues/2142#issuecomment-174373793

Thanks for the report @jossingram and for the fix @timheap!


Added code to add secrets via cli

Added code to prompt user to provide secrets for keys in config-github.json file.

I'm getting
Installing dependencies from lock file
Warning: The lock file is not up to date with the latest changes in pyproject.toml. You may be getting outdated dependencies. Run update to update them.

  SolverProblemError

  Because django-configuration-management depends on PyNaCl (^1.4.0) which doesn't match any versions, version solving failed.

when I try to poetry install


Run CI on Julia nightly

This will be useful for CompatHelper. On Julia nightly, CompatHelper workflows will now fail if they are not able to use the new version of the dependency.
This feature requires Julia 1.7, and thus is currently only available in Julia nightly.

Codecov Report

Merging #540 (1929b12) into dev (93ac515) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev     #540   +/-   ##
=======================================
  Coverage   84.87%   84.87%
=======================================
  Files          36       36
  Lines        3034     3034
=======================================
  Hits         2575     2575
  Misses        459      459

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 93ac515...1929b12. Read the comment docs.

This will make sure that if CompatHelper opens a PR, but the new version of the dependency is being held back by one thing else, then the CI job will fail on Julia nightly.

How will I know that is the reason, and not some other problem with nightly itself? Will I have to dig into the log?

Right now, you will need to look at the log unfortunately.

Of course, this change will be available in Julia 1.7. So once Julia 1.7 is released, if you see that CI is failing on Julia 1.7, you'll know that there is an actual problem (since Julia 1.7 will be stable, and thus not susceptible to spurious problems).


Example appears to be out of date

The Example in the README appears to be out of date.
These imports don't exist in utils 2.x:
import { promises as fs } from 'fs';
import { importDirectory } from '@iconify/tools/lib/import/directory';
import { cleanupSVG } from '@iconify/tools/lib/svg/cleanup';
import { runSVGO } from '@iconify/tools/lib/optimise/svgo';
import { parseColors, isEmptyColor } from '@iconify/tools/lib/colors/parse';

What are the new ones? 😊

They do exist.

utils 2.x

Maybe you have confused Iconify Utils and Iconify Tools? These are different packages for different purposes.

You are totally right. I'm not sure how I ended up here!


QC: Equal exact synonyms

The following classes have equal oboInOwl:hasExactSynonym annotations. While this is not always wrong, this is usually a copy paste error, so I mention it here:
FYPO:0000598	vacuolar transport: decreased
FYPO:0002653	vacuolar transport: decreased
FYPO:0006790	suppression of meiotic drive
FYPO:0006793	suppression of meiotic drive
FYPO:0004609	SPBs present in increased numbers during meiosis
FYPO:0006316	SPBs present in increased numbers during meiosis
FYPO:0002054	septation following abnormal chromosome segregation during cellular response to hydroxyurea
FYPO:0005669	septation following abnormal chromosome segregation during cellular response to hydroxyurea
FYPO:0000373	RNA modification: decreased rate
FYPO:0006557	RNA modification: decreased rate
FYPO:0001379	resistant to tacrolimus
FYPO:0001473	resistant to tacrolimus
FYPO:0002588	resistant to nickel
FYPO:0002589	resistant to nickel
FYPO:0001450	resistance to cold during vegetative growth
FYPO:0005260	resistance to cold during vegetative growth
FYPO:0003427	reduced queuosine level in tRNA
FYPO:0003480	reduced queuosine level in tRNA
FYPO:0003427	reduced queuosine content of tRNA
FYPO:0003480	reduced queuosine content of tRNA
FYPO:0002470	reduced protein phosphorylation during cellular response to IR
FYPO:0004261	reduced protein phosphorylation during cellular response to IR
FYPO:0004443	reduced protein localization to prospore membrane during meiosis II
FYPO:0005133	reduced protein localization to prospore membrane during meiosis II
FYPO:0004068	reduced phosphorylation of RNA polymerase II C-terminal domain serine 5 residues during vegetative growth
FYPO:0005061	reduced phosphorylation of RNA polymerase II C-terminal domain serine 5 residues during vegetative growth
FYPO:0001605	reduced level of substance in cytosol
FYPO:0001948	reduced level of substance in cytosol
FYPO:0005012	reduced histone H4-K5 acetylation during vegetative growth
FYPO:0005013	reduced histone H4-K5 acetylation during vegetative growth
FYPO:0001060	reduced glutamate import
FYPO:0001649	reduced glutamate import
FYPO:0003997	reduced DNA primase activity
FYPO:0005484	reduced DNA primase activity
FYPO:0001819	phosphoribosylformylglycinamidine cyclo-ligase activity abolished
FYPO:0002857	phosphoribosylformylglycinamidine cyclo-ligase activity abolished
FYPO:0003787	nuclear envelope protrusion with long mitotic spindle microtubules protruding beyond spindle pole body
FYPO:0004724	nuclear envelope protrusion with long mitotic spindle microtubules protruding beyond spindle pole body
FYPO:0003128	nuclear division arrest without septation (elongated cell)
FYPO:0005321	nuclear division arrest without septation (elongated cell)
FYPO:0000963	normal vegetative cell population growth on hydroxyurea
FYPO:0005776	normal vegetative cell population growth on hydroxyurea
FYPO:0001435	normal vegetative cell population growth on erythromycin
FYPO:0006150	normal vegetative cell population growth on erythromycin
FYPO:0002967	normal protein localization to spindle pole body during vegetative growth
FYPO:0002968	normal protein localization to spindle pole body during vegetative growth
FYPO:0001258	normal protein level during cellular response to increased oxygen tension
FYPO:0001260	normal protein level during cellular response to increased oxygen tension
FYPO:0001368	normal mitotic contractile ring assembly
FYPO:0006879	normal mitotic contractile ring assembly
FYPO:0001637	normal level of glycine in cell
FYPO:0006632	normal level of glycine in cell
FYPO:0005864	normal histone H3K9me at subtelomeric heterochromatin during vegetative growth
FYPO:0006429	normal histone H3K9me at subtelomeric heterochromatin during vegetative growth
FYPO:0000914	normal GS activity
FYPO:0002267	normal GS activity
FYPO:0001133	normal DNA replication during vegetative growth
FYPO:0004629	normal DNA replication during vegetative growth
FYPO:0001368	normal cytokinetic contractile ring assembly
FYPO:0006879	normal cytokinetic contractile ring assembly
FYPO:0001368	normal cytokinesis, actomyosin contractile ring assembly
FYPO:0006879	normal cytokinesis, actomyosin contractile ring assembly
FYPO:0001368	normal contractile ring assembly
FYPO:0006879	normal contractile ring assembly
FYPO:0000644	normal cellular protein localization
FYPO:0003627	normal cellular protein localization
FYPO:0001497	mitotic interphase arrested elongated inviable vegetative cell
FYPO:0004197	mitotic interphase arrested elongated inviable vegetative cell
FYPO:0003548	mitotic G1/S phase transition abolished after recovery from nitrogen starvation-induced G1 arrest
FYPO:0006909	mitotic G1/S phase transition abolished after recovery from nitrogen starvation-induced G1 arrest
FYPO:0003548	mitotic cell cycle G1/S phase transition abolished following nitrogen starvation-induced G1 phase arrest
FYPO:0006909	mitotic cell cycle G1/S phase transition abolished following nitrogen starvation-induced G1 phase arrest
FYPO:0002337	lethal; elongated mononucleate vegetative cell with mislocalized nucleus
FYPO:0006339	lethal; elongated mononucleate vegetative cell with mislocalized nucleus
FYPO:0001110	inviable germinated spore, multiple cell divisions, normal morphology
FYPO:0002430	inviable germinated spore, multiple cell divisions, normal morphology
FYPO:0004114	inviable after spore germination, without cell division, abnormal septum formation
FYPO:0004115	inviable after spore germination, without cell division, abnormal septum formation
FYPO:0004654	incomplete secondary cell septum with reduced thickness
FYPO:0005840	incomplete secondary cell septum with reduced thickness
FYPO:0004654	incomplete secondary cell septum with decreased thickness
FYPO:0005840	incomplete secondary cell septum with decreased thickness
FYPO:0001190	hypersensitive to cell wall-degrading enzymes
FYPO:0002720	hypersensitive to cell wall-degrading enzymes
FYPO:0001253	elongated multinucleate multiseptate cell, single septa between nuclei during vegetative growth
FYPO:0003344	elongated multinucleate multiseptate cell, single septa between nuclei during vegetative growth
FYPO:0002349	delayed onset of cytoplasmic stress granule assembly
FYPO:0002352	delayed onset of cytoplasmic stress granule assembly
FYPO:0005226	decreased ubiquitinated protein level during vegetative growth
FYPO:0005476	decreased ubiquitinated protein level during vegetative growth
FYPO:0004955	decreased PtdIns-3-P binding
FYPO:0006776	decreased PtdIns-3-P binding
FYPO:0004056	decreased protein localization in nucleus, with protein mislocalized to cytoplasm
FYPO:0006191	decreased protein localization in nucleus, with protein mislocalized to cytoplasm
FYPO:0006623	decreased plasma membrane phosphatidylinositol-3,4,5-trisphosphate level
FYPO:0006624	decreased plasma membrane phosphatidylinositol-3,4,5-trisphosphate level
FYPO:0006625	decreased plasma membrane phosphatidylinositol-3,4,5-trisphosphate level
FYPO:0005039	decreased phosphorylation of RNA polymerase II C-terminal domain serine 2 residues during nitrogen deprivation
FYPO:0005040	decreased phosphorylation of RNA polymerase II C-terminal domain serine 2 residues during nitrogen deprivation
FYPO:0006623	decreased phosphatidylinositol-3,4,5-trisphosphate level in cell membrane
FYPO:0006624	decreased phosphatidylinositol-3,4,5-trisphosphate level in cell membrane
FYPO:0006625	decreased phosphatidylinositol-3,4,5-trisphosphate level in cell membrane
FYPO:0004516	decreased number of Rad22 foci during vegetative growth
FYPO:0006421	decreased number of Rad22 foci during vegetative growth
FYPO:0000418	decreased mitotic cytokinesis
FYPO:0001261	decreased mitotic cytokinesis
FYPO:0006337	decreased microtubule nucleation from spindle pole body during interphase of mitotic cell cycle
FYPO:0006593	decreased microtubule nucleation from spindle pole body during interphase of mitotic cell cycle
FYPO:0002622	decreased malate dehydrogenase (oxaloacetate-decarboxylating) activity
FYPO:0003418	decreased malate dehydrogenase (oxaloacetate-decarboxylating) activity
FYPO:0003419	decreased malate dehydrogenase (oxaloacetate-decarboxylating) activity
FYPO:0001060	decreased L-glutamate import
FYPO:0001649	decreased L-glutamate import
FYPO:0006998	decreased histone exchange at transposon
FYPO:0007004	decreased histone exchange at transposon
FYPO:0001060	decreased glutamate uptake
FYPO:0001649	decreased glutamate uptake
FYPO:0001060	decreased glutamate import into cell
FYPO:0001649	decreased glutamate import into cell
FYPO:0006357	decreased chromatin modeling during glucose starvation
FYPO:0006358	decreased chromatin modeling during glucose starvation
FYPO:0006485	decreased cellular 1-phosphatidyl-1D-myo-inositol 3,4-bisphosphate level
FYPO:0006487	decreased cellular 1-phosphatidyl-1D-myo-inositol 3,4-bisphosphate level
FYPO:0006486	decreased cellular 1-phosphatidyl-1D-myo-inositol 3,4,5-trisphosphate level
FYPO:0006488	decreased cellular 1-phosphatidyl-1D-myo-inositol 3,4,5-trisphosphate level
FYPO:0000664	catalytic activity abolished
FYPO:0002117	catalytic activity abolished
FYPO:0003350	abolished protein localization to spindle midzone during mitotic anaphase B
FYPO:0004832	abolished protein localization to spindle midzone during mitotic anaphase B
FYPO:0000669	abolished protease activity
FYPO:0001206	abolished protease activity
FYPO:0003917	abolished nuclear-transcribed mRNA catabolic process, nonsense-mediated decay
FYPO:0003918	abolished nuclear-transcribed mRNA catabolic process, nonsense-mediated decay
FYPO:0002347	abnormal stress granule assembly during vegetative growth
FYPO:0002350	abnormal stress granule assembly during vegetative growth
FYPO:0002092	abnormal sister chromatid cohesion during meiosis
FYPO:0002093	abnormal sister chromatid cohesion during meiosis
FYPO:0001971	abnormal septum digestion after cytokinesis resulting in septated cell
FYPO:0001972	abnormal septum digestion after cytokinesis resulting in septated cell
FYPO:0002860	abnormal RNA uridylyltransferase activity
FYPO:0002861	abnormal RNA uridylyltransferase activity
FYPO:0003567	abnormal mitotic SPB insertion into nuclear envelope
FYPO:0006595	abnormal mitotic SPB insertion into nuclear envelope
FYPO:0005385	abnormal meiotic cell cycle arrest in metaphase I
FYPO:0006769	abnormal meiotic cell cycle arrest in metaphase I
FYPO:0001654	abnormal L-arginine import across plasma membrane
FYPO:0001656	abnormal L-arginine import across plasma membrane
FYPO:0000209	abnormal kinetochore orientation at meiosis I
FYPO:0005642	abnormal kinetochore orientation at meiosis I
FYPO:0000889	abnormal histone H3-K9 trimethylation at centromeric outer repeat region during vegetative growth
FYPO:0000890	abnormal histone H3-K9 trimethylation at centromeric outer repeat region during vegetative growth
FYPO:0000885	abnormal histone H3-K9 trimethylation at centromere otr during vegetative growth
FYPO:0000889	abnormal histone H3-K9 trimethylation at centromere otr during vegetative growth
FYPO:0000890	abnormal histone H3-K9 trimethylation at centromere otr during vegetative growth
FYPO:0000886	abnormal histone H3-K9 dimethylation at centromeric outer repeat region during vegetative growth
FYPO:0000887	abnormal histone H3-K9 dimethylation at centromeric outer repeat region during vegetative growth
FYPO:0000888	abnormal histone H3-K9 dimethylation at centromeric outer repeat region during vegetative growth
FYPO:0000886	abnormal histone H3-K9 dimethylation at centromere otr during vegetative growth
FYPO:0000887	abnormal histone H3-K9 dimethylation at centromere otr during vegetative growth
FYPO:0000888	abnormal histone H3-K9 dimethylation at centromere otr during vegetative growth
FYPO:0000965	abnormal histone H3-K14 acetylation at centromeric outer repeat region during vegetative growth
FYPO:0000966	abnormal histone H3-K14 acetylation at centromeric outer repeat region during vegetative growth
FYPO:0000967	abnormal histone H3-K14 acetylation at centromeric outer repeat region during vegetative growth
FYPO:0000965	abnormal histone H3-K14 acetylation at centromere otr during vegetative growth
FYPO:0000966	abnormal histone H3-K14 acetylation at centromere otr during vegetative growth
FYPO:0000967	abnormal histone H3-K14 acetylation at centromere otr during vegetative growth
FYPO:0002631	abnormal dTTP biosynthetic process during vegetative growth
FYPO:0002632	abnormal dTTP biosynthetic process during vegetative growth
FYPO:0002631	abnormal dTTP biosynthesis
FYPO:0002632	abnormal dTTP biosynthesis
FYPO:0004128	abnormal cysteine protease activity
FYPO:0004644	abnormal cysteine protease activity
FYPO:0002373	abnormal actin patch localization during mitosis
FYPO:0003028	abnormal actin patch localization during mitosis

release is commit 2be3bcf4483328de6d11b83e850df8417a9c73f9


refactor(dbm-services): 优化请求日志记录

关联研发信息
dev_branch: refactor/optimization_record_request_log/#809
target_branch: v1.2.0


ConfigMap and docker login configs support

Are there any plans to be able to add support for creating configmaps or docker login configs from vault secrets?

@MichaelSPaik, so sorry for the delay on the response, somehow this issue became unnoticed.
If you mean dockerconfigjson secrets for imagePullSecrets this is supported today, just use the right secret type for this: kubernetes.io/dockerconfigjson.
There's no plan to support ConfigMap as a secret sink as it's not a good practice.
On the other hand, there're plans to support other secrets source really soon, so stay tuned!

@fcgravalos
I am trying to create secret  type: kubernetes.io/tls with Secrets_manager version 2.1.0 but not able to create it..
apiVersion: secrets-manager.tuenti.io/v1alpha1
kind: SecretDefinition
metadata:
name: k8s-webhook-cert
namespace: k8s-webhook
spec:
name: k8s-webhook-cert
keysMap:
tls.crt:
path: {{ .Values.tls.cert }}
key: webhook-server.pem
tls.key:
path: {{ .Values.tls.key }}
key: webhook-server-key.pem
type: kubernetes.io/tls
Backend vault is Hashi and its failing with invalid type


Inclusion of NDepend logo on the readme.

The folks at NDepend have graciously contributed a license to their NDepend product for use within Azure DevOps for use by the DNN Platform team to monitor code-quality.
Adding an attribution to them at the bottom of our ReadMe, just like what was done for the .NET Foundation.

Do we do that on the other repositories too ?

@valadas Only need to do it here, as it will be added to the build process on the main DNN.Platform build only.  As it only analyses C# Code.

@mitchelsellers  But we also have C# code in the other repositories right ?