ClipRect does not clip a sized child Column

This issue has been reported before but falsely declared as "solved" through a workaround, and timed out in the other instance.
I created a DartPad example of the problem. The column width ignores the available space given by its parent, instead using the width of the clipper's parent.

$ flutter doctor -v
[√] Flutter (Channel stable, 2.0.5, on Microsoft Windows [Version
    10.0.19042.928], locale en-US)
    • Flutter version 2.0.5 at C:\flutter
    • Framework revision adc687823a (2 weeks ago), 2021-04-16
      09:40:20 -0700
    • Engine revision b09f014e96
    • Dart version 2.12.3

[√] Android toolchain - develop for Android devices (Android SDK
    version 30.0.3)
    • Android SDK at C:\Users\-\AppData\Local\Android\Sdk\
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = C:\Users\-\AppData\Local\Android\Sdk\
    • ANDROID_SDK_ROOT = C:\Users\-\AppData\Local\Android\Sdk\
    • Java binary at: C:\Program Files\Android\Android
      Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files
      (x86)\Google\Chrome\Application\chrome.exe

[√] Visual Studio - develop for Windows (Visual Studio Community 2019
    16.8.3)
    • Visual Studio at C:\Program Files (x86)\Microsoft Visual
      Studio\2019\Community
    • Visual Studio Community 2019 version 16.8.30804.86
    • Windows 10 SDK version 10.0.18362.0

[√] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 32.0.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b01)

[√] IntelliJ IDEA Ultimate Edition (version 2021.1)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2019.1.1
    • Flutter plugin version 55.1.5
    • Dart plugin version 211.6693.108

[√] VS Code (version 1.55.2)
    • VS Code at C:\Users\-\AppData\Local\Programs\Microsoft VS
      Code
    • Flutter extension version 3.1.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft
      Windows [Version 10.0.19042.928]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome
      90.0.4430.93
    • Edge (web)        • edge    • web-javascript • Microsoft Edge
      90.0.818.49

• No issues found!

 flutter doctor -v

[✓] Flutter (Channel stable, 2.0.6, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-GB)
    • Flutter version 2.0.6 at /Users/dhs/documents/fluttersdk/flutter
    • Framework revision 1d9032c7e1 (3 days ago), 2021-04-29 17:37:58 -0700
    • Engine revision 05e680e202
    • Dart version 2.12.3

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.55.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (3 available)
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729 • ios
      • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                               •
      web-javascript • Google Chrome 90.0.4430.93

! Doctor found issues in 1 category.

Tested on latest stable and master version. Issue still persists.
As a test, I have added a LayoutBuilder to the widget tree to see what the constraints are and the log suggests that the width is 200.
Modified build method
  @override
  Widget build(BuildContext context) {
    return SizedBox(
      width: 200,
      child: ClipRect(
        clipper: RectClipper(),
        child: SizedBox(
          width: 10000,
          child: LayoutBuilder(
            builder: (context, constraints) {
              debugPrint('Contraints: $constraints');
              return Column(
                children: const [
                  Text(
                    'This line is longer than 200 units and should simply be clipped, '
                    'not wrapped, using the 10000 units allocated by its parent cointainer. '
                    'Note that instead of a text widget, where this could be achieved with '
                    'maxLines and overflow, the behavior should work on an arbitrary widget '
                    'that does not have these properties.',
                  ),
                ],
              );
            },
          ),
        ),
      ),
    );
  }

Logs
flutter: Contraints: BoxConstraints(w=200.0, 0.0<=h<=926.0)

Screenshot of Flutter devtools:

In the image above, you can see in the hover tooltip that it shows the SizedBox as receiving 10000 as a width but in the LayoutExplorer, the width is shown as 200. I'm not sure if the width in the Layout Explorer is before clipping or after.
flutter doctor -v
[✓] Flutter (Channel master, 2.13.0-0.0.pre.914, on macOS 12.3.1 21E258 darwin-arm, locale en-US)
    • Flutter version 2.13.0-0.0.pre.914 at /Users/nabeelparkar/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision ceea3a6175 (3 hours ago), 2022-05-05 03:04:06 -0400
    • Engine revision f14e879b94
    • Dart version 2.18.0 (build 2.18.0-85.0.dev)
    • DevTools version 2.13.0

[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0-rc1)
    • Android SDK at /Users/nabeelparkar/Library/Android/sdk/
    • Platform android-32, build-tools 32.0.0-rc1
    • ANDROID_SDK_ROOT = /Users/nabeelparkar/Library/Android/sdk/
    • Java binary at: /opt/homebrew/opt/openjdk@11/bin/java
    • Java version OpenJDK Runtime Environment Homebrew (build 11.0.15+0)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /Applications/Brave Browser.app/Contents/MacOS/Brave Browser

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).

[✓] IntelliJ IDEA Ultimate Edition (version 2022.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 67.0.4
    • Dart plugin version 221.5588

[✓] VS Code (version 1.66.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.40.0

[✓] Connected device (3 available)
    • iPhone 13 Pro Max (mobile) • F9E7F1F9-285A-4DE8-94CD-78FE97310572 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-15-4 (simulator)
    • macOS (desktop)            • macos                                • darwin-arm64   • macOS 12.3.1 21E258 darwin-arm
    • Chrome (web)               • chrome                               • web-javascript • Brave Browser <IP_ADDRESS>

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Screenshots
Example of issue

Full code sample
import 'package:flutter/material.dart';

const Color darkBlue = Color.fromARGB(255, 18, 32, 47);

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData.dark().copyWith(scaffoldBackgroundColor: darkBlue),
      debugShowCheckedModeBanner: false,
      home: const Scaffold(
        body: Center(
          child: MyWidget(),
        ),
      ),
    );
  }
}

class MyWidget extends StatelessWidget {
  const MyWidget({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return SizedBox(
      width: 200,
      child: ClipRect(
        clipper: RectClipper(),
        child: SizedBox(
          width: 10000,
          child: LayoutBuilder(
            builder: (context, constraints) {
              debugPrint('Contraints: $constraints');
              return Column(
                children: const [
                  Text(
                    'This line is longer than 200 units and should simply be clipped, '
                    'not wrapped, using the 10000 units allocated by its parent cointainer. '
                    'Note that instead of a text widget, where this could be achieved with '
                    'maxLines and overflow, the behavior should work on an arbitrary widget '
                    'that does not have these properties.',
                  ),
                ],
              );
            },
          ),
        ),
      ),
    );
  }
}

class RectClipper extends CustomClipper<Rect> {
  @override
  Rect getClip(Size size) {
    return Rect.fromLTRB(0, 0, size.width, size.height);
  }

  @override
  bool shouldReclip(covariant CustomClipper<Rect> oldClipper) {
    return true;
  }
}

Seems like I too have bumped into this issue. Pity it is not resolved yet 😒

Wait, how to solve this? Do we even know where the issue is sourced, or is there a workaround yet?


Update permissions-reference.md

Accuracy changes for Device.ReadWrite.All

Thank you @DanielBradley1 for suggesting this change. The permissions reference is autogenerated weekly from information in the Microsoft Graph service principal object so any manual updates will get overwritten in the next refresh. Please file a customer issue instead (scroll to the bottom of the article and submit feedback for this page) and I'll escalate it internally for engineering to investigate and resolve. The permissions reference will be updated after the information is fixed upstream.

Thank you @DanielBradley1 for suggesting this change. The permissions reference is autogenerated weekly from information in the Microsoft Graph service principal object so any manual updates will get overwritten in the next refresh. Please file a customer issue instead (scroll to the bottom of the article and submit feedback for this page) and I'll escalate it internally for engineering to investigate and resolve. The permissions reference will be updated after the information is fixed upstream.

Thank you Faith, I will do this now. Out of interest, I am contributing to these documents as they aid in the renewal of my MVP. How would I demonstrate this as a contribution if I cannot prove I contributed towards it through a GitHub Pull Request?

Thank you @DanielBradley1 for suggesting this change. The permissions reference is autogenerated weekly from information in the Microsoft Graph service principal object so any manual updates will get overwritten in the next refresh. Please file a customer issue instead (scroll to the bottom of the article and submit feedback for this page) and I'll escalate it internally for engineering to investigate and resolve. The permissions reference will be updated after the information is fixed upstream.

Thank you Faith, I will do this now. Out of interest, I am contributing to these documents as they aid in the renewal of my MVP. How would I demonstrate this as a contribution if I cannot prove I contributed towards it through a GitHub Pull Request?

Ah, I'm not sure if filing GitHub issues also counts @DanielBradley1. But feel free to raise PRs against other non-autogenerated articles. See contributions from community members: Do's and Don'ts (I'll update it to mention permissions in the Don'ts).


Avoid loss of precision in to_default_float when input is a python float

PR type: bugfix
Summary
It seems that to_default_float can result in a loss of precision when the input value is a python float. This was previously not the case because to_default_float used to use gpflow's cast function internally, which used tf.convert_to_tensor(..., dtype=tf.float64) in the case that the input is a python float.
However, this function was declared obsolete in gpflow 2.6.1, and was replaced by Tensorflow's tf.cast instead. The implementation of tf.cast is such that it converts the python float to a tf.float32 tensor (thereby losing precision), which it then casts to tf.float64.
You can see the essence of the problem as follows (note that 0.99999999 and 1.0 are distinct at 64 bit precision, so the fact that the lhs is rounded to 1.0 demonstrates a loss of precision):
lhs = tf.cast(0.99999999, dtype=tf.float64)
rhs = tf.convert_to_tensor(1.0, dtype=tf.float64)
assert lhs != rhs

Release notes
Fully backwards compatible: yes
PR checklist

[ ] New features: code is well-documented

[ ] detailed docstrings (API documentation)
[ ] notebook examples (usage demonstration)

[x] The bug case / new feature is covered by unit tests
[x] Code has type annotations
[x] Build checks

[x] I ran the black+isort formatter (make format)
[x] I locally tested that the tests pass (make check-all)

[x] Release management

[x] RELEASE.md updated with entry for this change
[x] New contributors: I've added myself to CONTRIBUTORS.md

Closing to recreate with master as target to facilitate doing a quick release (recreated PR).


Using asset_path in component previews

Steps to reproduce

put image.png in app/assets/images/image.png
create an example component that accepts an image argument, with a preview file
in the preview file, add render ExampleComponent.new(image: image_path("image.png")
this will trigger a NoMethodError
add include ActionView::Helpers::AssetUrlHelper at the top of the preview class

class ExampleComponent < ApplicationComponent
  def initialize(image:)
    @image = image
  end

  def call
    image_tag @image
  end
end

class ExampleComponentPreview < ViewComponent::Preview
  include ActionView::Helpers::AssetUrlHelper

  def default
    render(ExampleComponent.new(image: image_path("image.png")))
  end
end

Expected behavior
The preview renders the image with path /assets/image-80b04a6277839296f66f0e7de1fb03a3061322fad2273b18a375bf2f5381c41f.png.
Actual behavior
The preview renders but the image path is /images/image.png.
System configuration
Rails version: <IP_ADDRESS>
Ruby version: 2.7.4
Gem version: 2.40.0

@Spone I forgot about this issue. Does https://github.com/github/view_component/pull/1119 close it?

@joelhawksley nope, I still have the issue on main... but I no longer have to include ActionView::Helpers::AssetUrlHelper for the preview to render.
The image path is still wrong though:

instead of:

TL;DR
ActionView::Helpers::AssetUrlHelper does not provide the correct logic for loading an asset through the asset pipeline (Sprockets). The easiest (incredibly ugly) workaround is to include the sprockets-rails helper and its configuration into your preview class.
class ExampleComponentPreview < ViewComponent::Preview
    include Sprockets::Rails::Helper
    self.debug_assets = Rails.application.config.assets.debug
    self.digest_assets = Rails.application.config.assets.digest
    self.assets_prefix = Rails.application.config.assets.prefix
    self.assets_precompile = Rails.application.config.assets.precompile
    self.assets_environment = Rails.application.assets
    self.assets_manifest = Rails.application.assets_manifest
    self.resolve_assets_with = Rails.application.config.assets.resolve_with
    self.check_precompiled_asset = Rails.application.config.assets.check_precompiled_asset
    self.unknown_asset_fallback = Rails.application.config.assets.unknown_asset_fallback
    # Expose the Rails.application precompiled asset check to the view
    self.precompiled_asset_checker = -> logical_path { Rails.application.asset_precompiled? logical_path }

   ...
end

This will set up the context in your Preview class the same way sprockets-rails currently sets up the context in ActionView::Base which allows you to use asset helpers in views. Not only is this a lot of ugly boilerplate code (which you should at least wrap in a module) but it is liable to break if sprockets-rails changes its railtie. For more information and better ideas keep reading.

Disclaimer: I do not have the deepest understanding of the inner workings of Rails and even less of an understanding of Sprockets. These are observations I made from reading the source code, so expect parts of my interpretations to be incorrect.

image_path along with other asset helpers, unless passed a truthy value in the skip_pipeline: option will get the path of the asset from a method in the same module named compute_asset_path. If told to skip the pipeline the public_compute_asset_path method is used instead, which appears to be intended to be used for assets manually placed in the public/ folder.
By default these path resolving methods are actually aliases, which is why image_path acts as though it was passed skip_pipeline: true and resolves to /images/image.png. compute_asset_path is meant to be overridden by the gem that manages the asset pipeline (in your case Sprockets).
sprockets-rails has its own compute_asset_path method in a helper module that gets included (and configured) in ActionView::Base on load by a the sprockets-rails railtie. The new compute_asset_path method relies on configuration options included in the ActionView context by said railtie. The above solution works by basically copying the loading logic in the railtie.
In my opinion, the dynamic nature of the ActionView::Base context ought to disqualify solutions like the one above (and the current include ActionView::Helpers::AssetTagHelper in ViewComponent::Preview, which can lead its users to believe that they can use asset helpers in a preview). We should either disallow view helpers in previews or commit to allowing helper methods to be used via a helpers accessor initialized with ViewComponentsController's view_context, similar to the way you might delegate :method, to: :helpers in a component. This way we can stay consistent and avoid misleading users by only including a subset of ActionView::Base.

Please don't disallow view helpers in previews — I need to use them, and I suspect I'm not the only one.
See https://github.com/github/view_component/discussions/1451 for more detail on what I'm doing (though allowing component tests to do expect(page).to have_rendered_component(ExampleComponent) would also solve my problem here, but that's a different issue :)

I got beaten by this again today. @joelhawksley how do you want to tackle this?

@Spone I think the first step we should take is to see if these same helpers work in ActionMailer previews, and if so, how they work there. Would you be interested in taking a look?

I guess the relevant part of ActionMailer is here: https://github.com/rails/rails/blob/main/actionmailer/lib/action_mailer/railtie.rb#L38-L40

@Spone would you like to take a crack at seeing if that works for us?

Just spent a few hours banging my head against the wall because we used image_tag inside our view component, and tried to use a component (rendering-only) test built using render_inline.  In our CI env, when component tests are executed, we don't have any assets built, so when image_tag is encountered, manifest.js is sought (in order to determine the image src path), and never found (because in this non-system test, we didn't have assets precompiled).

@gap777 can we close this issue then ?

Why? Is it fixed? 🧐

@reeganviljoen @Spone is right -- this isn't really fixed.
I got to this issue because what I was doing was related to

view components
render inline
My belief that I shouldn't need assets from asset pipeline, since a browser wasn't being launched

Perhaps my comment should drive a separate ticket / PR that updates the documentation around testing view components... even if you're using render_inline, IF you're using any view helpers that rely on the assets pipeline (like image_tag), you're going to need assets available for that test to execute/pass.

@gap777 personally when ever I run tests in ci I precomile the assets as a setup step, maybe we should state that  in docs

@reeganviljoen We have 2 parallel workflows in our CI: those requiring the assets, and those that do not (unit tests, static code analysis/rubocop, etc). My mistake was that I had tried to reduce the size of the one and move these render_inline based tests into the other.
Yes, I think documentation calling attention to this idea would be helpful... all view component tests should be executed in an environment that has assets available, since, after all, these are view tests!

@gap777 we could also add a check in rener_inline to compile the assets if not present


Newsletters: add 313 (2024-07-26)

[ ] Lede, releases/RCs, topic entries @harding
[ ] Bitcoin Stack Exachange section @bitschmidty
[ ] Merges @Gustavojfe

@Gustavojfe after you push, could you please review the Netlify CI status in the CI box near the bottom of the PR.  It should progress from yellow to green (it typically takes about 10 minutes, so I usually do something else for a bit and then come back to it) .  If it turns red, you can click into details and see what test failed.  If the error message is clear, it'd be great if you could fix it, created another commit, and push it.  If the error is unintelligible or doesn't seem to apply to your section, please leave a comment here and I'll fix it.  Thanks!
Note: the Travis CI status will always be red up until near the time the PR is ready to be merged.

Pushed edits for all feedback so far, thanks @LarryRuane @vostrnad @jirijakes !  Also added lede, releases/RCs, and topic entries.

Pushed edits for all comments from @glozow and @LarryRuane (thanks!).

Pushed a couple topic fixups, and added the BIP379 link back in (it is an .md and not mediawiki BIP so our regular linker fails currently)


Error in Sublime 4 console UnicodeDecodeError

I'm getting this error in my Sublime Text 4 console on startup and whenever I try to enable ColorHighlight: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 207. It might have something to do with the beta version of Package Control I had to install. See https://github.com/wbond/package_control/issues/1612#issuecomment-1636034709. Of course, ColorHighlight doesn't do anything at all in my editor.
I realize this package hasn't been worked on in 5 years right now, I just figured someone else might also find this helpful. I'm now trying out ColorHelper to see if it gives me what I'm looking for.

Hi did you get anywhere with color highlighting in Sublime Text 4?

Good question. I followed the instructions in this comment in the issue I linked to above.

It's not really closed, but it's not really open either ¯_(ツ)_/¯


TypeError: Cannot read property 'name' of null

I am getting the following error right after choosing a connection =>
Exception in template helper: TypeError: Cannot read property 'name' of null
    at Object.<anonymous> (http://<my-server>/app/client/templateHelpers.js?78f7cb0a6e053cd469eeee4e27c3eb4719eaa31a:60:26)
    at http://<my-server>/packages/blaze.js?9391df93ba5076c2cfc61ee68724eb79b65f00d9:2986:16
    at http://<my-server>/packages/blaze.js?9391df93ba5076c2cfc61ee68724eb79b65f00d9:1650:16
    at http://<my-server>/packages/blaze.js?9391df93ba5076c2cfc61ee68724eb79b65f00d9:3038:66
    at Function.Template._withTemplateInstanceFunc (http://<my-server>/packages/blaze.js?9391df93ba5076c2cfc61ee68724eb79b65f00d9:3671:12)
    at http://<my-server>/packages/blaze.js?9391df93ba5076c2cfc61ee68724eb79b65f00d9:3037:27
    at Spacebars.call (http://<my-server>/packages/spacebars.js?1aedcc2aa3ae9ff5d860d73516110cedd77c033e:167:18)
    at Spacebars.mustacheImpl (http://<my-server>/packages/spacebars.js?1aedcc2aa3ae9ff5d860d73516110cedd77c033e:104:25)
    at Object.Spacebars.mustache (http://<my-server>/packages/spacebars.js?1aedcc2aa3ae9ff5d860d73516110cedd77c033e:108:39)
    at Template.DatabaseDashboard.HTML.DIV.HTML.H4.HTML.A.href (http://<my-server>/app/client/views/DatabaseDashboard/template.DatabaseDashboard.js?e6cbfb67b5846b3c87cfa4d74107d220be4c8e24:30:24)

Check: https://github.com/DrMongo/DrMongo/blob/fade48ae50746b886db0936972cfcf6ef12bbbad/client/templateHelpers.js#L52
Template.registerHelper('pathForConsole', function (params) {
  params = params.hash || {};
  const data = {
    database: params.data.name, // TypeError: Cannot read property 'name' of null
    connection: params.data.connection().slug
  };

  return FlowRouter.path('Console', data);
});

hi, on which page you see this error? and how is your mongo URI looks like?

I get this error when I click on a defined connection directly after the connection page is displayed.
This is how my URI looks like:
mongodb://<user>:<pass>@<server>:<port>/<database>

can you try this connection: mongodb://drmongo:drmongo@ds061454.mongolab.com:61454/drmongotest
you will get this error Meteor does not currently support objects other than ObjectID as ids on documents list, but at least it will load the database and related collections

Just did, error persists, I am also getting the Error: Meteor does not currently support objects other than ObjectID as ids but the TypeError: Cannot read property 'name' of null is still there...

hmm that error TypeError: Cannot read property 'name' of null is strange... I just installed current master and don't see that error... try reinstall DrMongo pls

just did a fresh git clone... error still there...

We are currently rewriting the code in React and this is not occurring to me at all now. So this might have been removed. The react branch is still in progress, I do not suggest using it, yet.


[IMPAC-272] Better info panel display (NEW)

I decided to not hide title in the widget but just to display it above the widget by changing CSS directive info-panel.

:+1: included in https://github.com/maestrano/impac-angular/pull/236


Scheduler just terminates randomly for no apparent reason

Strange problem: In my scenario Rufus Scheduler terminates at different points during task execution for no apparent reason.
This is my config/initializers/task_scheduler.rb:
require 'rufus/scheduler'

$scheduler = Rufus::Scheduler.start_new

$scheduler.every("5m") do
  custom_log("Keep-Alive Rufus log, time: #{Time.now}")
end

if %w!production staging!.include? Rails.env
  $scheduler.every("45m") do
    custom_log("autocomplete:generate, time: #{Time.now}")
    Rake::Task["autocomplete:generate"].invoke
  end

  $scheduler.every("30m") do
    custom_log("ts:index, time: #{Time.now}")
    Rake::Task["ts:index"].invoke
  end

  $scheduler.every('30m') do
    custom_log("Checking for new contact requests in Contact.unsent.inspect - time: #{Time.now}")
    Contact.unsent.each do |contact|
      Mailer.deliver_mimi_contact_request(contact)
      Mailer.deliver_mimi_contact_requested(contact)
      contact.update_attribute(:notification_sent, true)
    end
  end
end

Now, when I restart passenger I always get mixed results how "far" rufus gets before he terminates:
This is from today:
# Restart passenger
Keep-Alive Rufus log, time: Wed Dec 01 12:06:36 -0800 2010
Keep-Alive Rufus log, time: Wed Dec 01 12:11:36 -0800 2010
Keep-Alive Rufus log, time: Wed Dec 01 12:16:36 -0800 2010
Keep-Alive Rufus log, time: Wed Dec 01 12:21:36 -0800 2010
Keep-Alive Rufus log, time: Wed Dec 01 12:26:36 -0800 2010
Keep-Alive Rufus log, time: Wed Dec 01 12:31:36 -0800 2010
ts:index, time: Wed Dec 01 12:31:36 -0800 2010
Checking for new contact requests in Contact.unsent.inspect - time: Wed Dec 01 12:31:36 -0800 2010
Keep-Alive Rufus log, time: Wed Dec 01 12:36:36 -0800 2010
Keep-Alive Rufus log, time: Wed Dec 01 12:41:36 -0800 2010
Keep-Alive Rufus log, time: Wed Dec 01 12:46:35 -0800 2010
autocomplete:generate, time: Wed Dec 01 12:46:35 -0800 2010
# -> nothing more after here

2 days before:
# Restart passenger
Keep-Alive Rufus log, time: Mon Nov 29 01:26:32 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 01:31:31 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 01:36:31 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 01:41:31 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 01:46:31 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 01:51:31 -0800 2010
ts:index, time: Mon Nov 29 01:51:31 -0800 2010
Checking for new contact requests in Contact.unsent.inspect - time: Mon Nov 29 01:51:31 -0800 2010
# -> nothing more after here

From the same day:
# Restart passenger
Keep-Alive Rufus log, time: Mon Nov 29 15:39:19 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 15:44:20 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 15:49:19 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 15:54:20 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 15:59:19 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 16:04:20 -0800 2010
ts:index, time: Mon Nov 29 16:04:20 -0800 2010
Checking for new contact requests in Contact.unsent.inspect - time: Mon Nov 29 16:04:20 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 16:09:20 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 16:14:19 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 16:19:20 -0800 2010
autocomplete:generate, time: Mon Nov 29 16:19:20 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 16:24:19 -0800 2010
Keep-Alive Rufus log, time: Mon Nov 29 16:29:20 -0800 2010
# -> nothing more after here

As you can see, the scheduler just kind of stops working at seemingly random points. All of the jobs in my scheduler file run fine when executed by hand and, even worse, also fine by the scheduler because I can see in the logs that every job has been executed successfully multiple times.
I tried a lot of things:

Playing around with intervalls as I suspected some weird concurrency issue

Disabling / Enabling all possible mutations of running jobs

The result is always the frustrating one from - I can't see any system / logic behind Rufus just stopping to work.
How can I debug this further?
Sys-Info:
ruby -v
ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-linux]
gem -v
1.3.6
gem list rails
rails (2.3.5)

Unfortunately, none of the above worked for me. The only thing that is actually working for me is setting:
PassengerSpawnMethod conservative
In the VirtualHost at the apache.conf file
I will keep my eyes and ears opened for a better solution :)


trian

Traceback (most recent call last):
File "train.py", line 66, in
train(train_img_path, train_gt_path, pths_path, batch_size, lr, num_workers, epoch_iter, save_interval)
File "train.py", line 35, in train
for i, (img, gt_score, gt_geo, ignored_map) in enumerate(train_loader):
File "/usr/local/lib/python3.5/dist-packages/torch/utils/data/dataloader.py", line 637, in next
return self._process_next_batch(batch)
File "/usr/local/lib/python3.5/dist-packages/torch/utils/data/dataloader.py", line 658, in _process_next_batch
raise batch.exc_type(batch.exc_msg)
TypeError: function takes exactly 5 arguments (1 given)
How can I fix it?

Waiting for your response!

@wangyuxin87 hi, the code has been only tested on my environment, which is shown in README. So if you are using another environment which causes that bug, change num_workers to 0 and try again. I hope this helps : )

Thanks for your code and response!
I have some new issue, can you help me?
root@bfd0e7a2dba1:/home/yxwang/pytorch/EAST# CUDA_VISIBLE_DEVICES=6,7 python3 train.py
Traceback (most recent call last):
File "train.py", line 66, in
train(train_img_path, train_gt_path, pths_path, batch_size, lr, num_workers, epoch_iter, save_interval)
File "train.py", line 35, in train
for i, (img, gt_score, gt_geo, ignored_map) in enumerate(train_loader):
File "/usr/local/lib/python3.5/dist-packages/torch/utils/data/dataloader.py", line 615, in next
batch = self.collate_fn([self.dataset[i] for i in indices])
File "/usr/local/lib/python3.5/dist-packages/torch/utils/data/dataloader.py", line 615, in
batch = self.collate_fn([self.dataset[i] for i in indices])
File "/home/yxwang/pytorch/EAST/dataset.py", line 384, in getitem
lines = f.readlines()
File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xef in position 0: ordinal not in range(128)
Waiting for your response!

Putting #coding=utf-8 in the 1st line may help

I try # coding=utf-8 or # coding:utf-8 in the 1st line of dataset.py, it does not work.... Do you have any other idea? Thanks

you may refer to https://stackoverflow.com/questions/35028683/python3-unicodedecodeerror-with-readlines-method

Thanks! It has worked. Do you add ICDAR 2013 in your training images? I think it will improve the performance.

The data distribution in 13 and 15 still exists difference, so you can try and welcome to share the results : )

The results get worse when I change the basic network to Resnet50, do you have any idea?
By the way, it obtains the same performance with extra dataset(ICDAR2013).


Lack of source code documentation

Tried to dig in documentation in order to add my ideas into source but I see that the source code lacks documentation HUGELY.
Is this on purpose?

The source is the documentation.

@olhor to put this more delicately, the source code is intended to read as documentation. Turbo isn't littered with source code comments so as to not litter the source code.
I'm not saying this is right or wrong, it's just how the hotwired team chose to approach their source code documentation.

@ParamagicDev Thanks for clarification. It was just odd to me after comparing such approach to Rails which is written in (self-documenting) Ruby where still documentation exists. I hope it will not change in the future. Folks got used to it imho.

@olhor I think part of the reason for that is the rails docs leverage the documentation you see in the source code to generate the API docs. In addition Rails is a much larger project with a lot more moving parts, so self documenting code hits a point of diminishing returns when you get to a project size as large as Rails.


Add bower.json

I think this is required to be able to deploy to webjars.org as a Bower package.

Not sure if this would be merged. See https://github.com/vuejs/vue/issues/4040

Thanks for the feedback @rpkilby. Didn't know about this, I just assumed the file was missing in this particular repository because I saw there are other projects under vue/ that do have a bower.json file. For example vuejs/vuex/blob/dev/bower.json.

ping @fnlctrl @yyx990803

@rpkilby I think it's ok to have a simple bower.json file contributed that doesn't need any (or almost any) maintenance. We still recommend using npm 😁

@rpkilby I think it's ok to have a simple bower.json file contributed that doesn't need any (or almost any) maintenance. We still recommend using npm 😁


Add page about useful method pragmas

<script> and <script: '1 inspect'>
<example>

others?

It should go in the "CoolToKnowForBeginners" page

I think it should be a separate page. Or maybe "CoolToKnowForBeginners" should be a folder with this page in it. Otherwise if you put everything inside a single "CoolToKnowForBeginners" page, it will be too big. It would be cool to have description of every pragma with examples and instructions on how to define your own pragmas.

After talking with Oleks we think that we should have a page dedicated to Pragmas in general and a subpart with the useful pragmas that are already used in Pharo.


remove ts-sinon dependency, upgrade sinon

ts-sinon is no longer maintained, and doesn't seem to be very useful for us.
Upgrade sinon and @types/sinon to latest.

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

Project coverage is 98.71%. Comparing base (a5d66bf) to head (1a31128).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #804      +/-   ##
==========================================
+ Coverage   98.70%   98.71%   +0.01%
==========================================
  Files          73       74       +1
  Lines       11335    11469     +134
  Branches     1631     1652      +21
==========================================
+ Hits        11188    11322     +134
  Misses        141      141
  Partials        6        6

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

Really unfortunate that we now need to reference real object now for stubbing...

Yeah :/ I wish the sinon squad would have taken over support for that wrapper. A few people have forked it, but none that seem worth taking in as a dep.


Update engine CLI reference with latest changes from 19.03

fixes https://github.com/docker/docker.github.io/pull/11430
@usha-mandya @maximillianfx ptal

Thanks, LGTM! 😄


Are tests working ok?

 Are they working ok for you?
→ npm test

><EMAIL_ADDRESS>pretest /Users/andrew/Personal/git-devel/botkit-storage-dynamodb
> jscs ./

><EMAIL_ADDRESS>test /Users/andrew/Personal/git-devel/botkit-storage-dynamodb
> istanbul cover --report lcov --dir coverage/ _mocha ./tests --grep ./tests/*.js -- --colors

  Dynamo
    Initialization
      1) should throw an error if config is missing
      2) should throw an error if dynamoRegion is missing
      3) should throw an error if dynamoAccessKey is missing
      4) should throw an error if dynamoAccessSecret is missing
      ✓ should initialize dynasty with dynamoRegion, dynamoAccessKey, dynamoAccessSecret
    teams.get
      5) should call find with callback
    teams.save
      6) should call update
    teams.all
      7) should call findAll
    channels.get
      8) should call find with callback
    channels.save
      9) should call update
    channels.all
      10) should call findAll
    users.get
      11) should call find with callback
    users.save
      12) should call update
    users.all
      13) should call findAll

  1 passing (175ms)
  13 failing

  1) Dynamo Initialization should throw an error if config is missing:
     AssertionError: expected Function {
  name: '(config){__cov_wBJJ_XJenSJcZMEPIh8EXg.f[\'1\']++;__cov_wBJJ_XJenSJcZMEPIh8EXg.s[\'2\']++;if((__cov_wBJJ_XJenSJcZMEPIh8EXg.b[\'2\'][0]++,!config)||(__cov_wBJJ_XJenSJcZMEPIh8EXg.b[\'2\'][1]++,!config.dynamoRegion)||(__cov_wBJJ_XJenSJcZMEPIh8EXg.b[\'2\'][2]++,!config.dynamoAccessKey)||'
} to throw exception with a message matching 'Need to provide dynamo dynamoRegion, dynamoAccessKey, dynamoAccessSecret', but got 'Need to provide dynamoRegion, dynamoAccessKey, dynamoAccessSecret'
      at Assertion.fail (node_modules/should/lib/assertion.js:92:17)
      at Assertion.Object.defineProperty.value (node_modules/should/lib/assertion.js:164:19)
      at Context.<anonymous> (tests/index.js:36:33)

  2) Dynamo Initialization should throw an error if dynamoRegion is missing:
     AssertionError: expected Function { name: '' } to throw exception with a message matching 'Need to provide dynamo dynamoRegion, dynamoAccessKey, dynamoAccessSecret', but got 'Need to provide dynamoRegion, dynamoAccessKey, dynamoAccessSecret'
      at Assertion.fail (node_modules/should/lib/assertion.js:92:17)
      at Assertion.Object.defineProperty.value (node_modules/should/lib/assertion.js:164:19)
      at Context.<anonymous> (tests/index.js:42:57)

  3) Dynamo Initialization should throw an error if dynamoAccessKey is missing:
     AssertionError: expected Function { name: '' } to throw exception with a message matching 'Need to provide dynamo dynamoRegion, dynamoAccessKey, dynamoAccessSecret', but got 'Need to provide dynamoRegion, dynamoAccessKey, dynamoAccessSecret'
      at Assertion.fail (node_modules/should/lib/assertion.js:92:17)
      at Assertion.Object.defineProperty.value (node_modules/should/lib/assertion.js:164:19)
      at Context.<anonymous> (tests/index.js:48:57)

  4) Dynamo Initialization should throw an error if dynamoAccessSecret is missing:
     AssertionError: expected Function { name: '' } to throw exception with a message matching 'Need to provide dynamo dynamoRegion, dynamoAccessKey, dynamoAccessSecret', but got 'Need to provide dynamoRegion, dynamoAccessKey, dynamoAccessSecret'
      at Assertion.fail (node_modules/should/lib/assertion.js:92:17)
      at Assertion.Object.defineProperty.value (node_modules/should/lib/assertion.js:164:19)
      at Context.<anonymous> (tests/index.js:54:57)

  5) Dynamo teams.get should call find with callback:
     TypeError: Cannot read property 'then' of undefined
      at Object.get (src/index.js:9:1609)
      at Context.<anonymous> (tests/index.js:74:41)

  6) Dynamo teams.save should call update:
     TypeError: Cannot read property 'then' of undefined
      at Object.save (src/index.js:9:2370)
      at Context.<anonymous> (tests/index.js:84:41)

  7) Dynamo teams.all should call findAll:
     TypeError: Cannot read property 'then' of undefined
      at Object.all (src/index.js:9:2850)
      at Context.<anonymous> (tests/index.js:96:41)

  8) Dynamo channels.get should call find with callback:
     TypeError: Cannot read property 'then' of undefined
      at Object.get (src/index.js:9:1609)
      at Context.<anonymous> (tests/index.js:74:41)

  9) Dynamo channels.save should call update:
     TypeError: Cannot read property 'then' of undefined
      at Object.save (src/index.js:9:2370)
      at Context.<anonymous> (tests/index.js:84:41)

  10) Dynamo channels.all should call findAll:
     TypeError: Cannot read property 'then' of undefined
      at Object.all (src/index.js:9:2850)
      at Context.<anonymous> (tests/index.js:96:41)

  11) Dynamo users.get should call find with callback:
     TypeError: Cannot read property 'then' of undefined
      at Object.get (src/index.js:9:1609)
      at Context.<anonymous> (tests/index.js:74:41)

  12) Dynamo users.save should call update:
     TypeError: Cannot read property 'then' of undefined
      at Object.save (src/index.js:9:2370)
      at Context.<anonymous> (tests/index.js:84:41)

  13) Dynamo users.all should call findAll:
     TypeError: Cannot read property 'then' of undefined
      at Object.all (src/index.js:9:2850)
      at Context.<anonymous> (tests/index.js:96:41)

=============================================================================
Writing coverage object [/Users/andrew/Personal/git-devel/botkit-storage-dynamodb/coverage/coverage.json]
Writing coverage reports at [/Users/andrew/Personal/git-devel/botkit-storage-dynamodb/coverage]
=============================================================================

=============================== Coverage summary ===============================
Statements   : 63.33% ( 19/30 )
Branches     : 50% ( 8/16 )
Functions    : 53.85% ( 7/13 )
Lines        : 63.33% ( 19/30 )
================================================================================
npm ERR! Test failed.  See above for more details.

Sorry Andrew. I was away for a while and unable to answer emails, etc. I just saw this notification.
Tests don't pass because I'm not sure how to test JavaScript Promises. If you do or someone you know does and would like to make these tests pass, please do. :-)

Latest PR fixes the tests. Thanks to @miklosaubert :-)


Lite: Batch_to_space-ND support

Arbitrary dimension support added.
Add ref: #21526

See also https://github.com/tensorflow/tensorflow/pull/27867. Once we confirm these 2 PRs unblock the model execution, we can proceed.

See also https://github.com/tensorflow/tensorflow/pull/27867. Once we confirm these 2 PRs unblock the model execution, we can proceed.

@ANSHUMAN87 Can you please resolve conflicts? Thanks!

@gbaned : The conflict is resolved, would you please help get it reviewed and merged, Thanks!

See also #27867. Once we confirm these 2 PRs unblock the model execution, we can proceed.

Thanks for the contribution, @ANSHUMAN87
Any reply to jdduke's previous comment?

See also #27867. Once we confirm these 2 PRs unblock the model execution, we can proceed.

Thanks for the contribution, @ANSHUMAN87
Any reply to jdduke's previous comment?

@miaout17 : I have verified, the solution works fine! Please refer #27867 also, both are done together as related. Thanks!

Can one of the admins verify this patch?

@ANSHUMAN87 Can you please resolve conflicts? Thanks!

Resolved!

@miaout17 Can you please take a look on this PR? Thanks!

@gbaned : The conflicts are resolved now, Thanks!

@ANSHUMAN87 Can you please resolve conflicts? Thanks!

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

@gbaned : I will resolve the conflicts possibly by Saturday. Thanks!

@gbaned : The conflicts are resolved now. Thanks!

As a high-level comment, is it possible to define local variables of type NdArrayDesc<8> instead of introducing new temporary tensors? We are unlikely to support dimensions > 8.

I found a performance regression with your PR on my Pixel 3.
The input size is [400,30,30,100 ] and batch_size is [20, 20], crops  is [[1,1],[1,1]].
The performance before and after your pr:
before 57.826ms
after 99.597ms
Could you double check on performance?

Hey @ANSHUMAN87, we're working on an overhaul for >4D kernel support, so I think it's best if we table this PR for now (and 1 or 2 of the related PRs) as we work toward that end. Thanks for your patience in iterating on this and pushing for generalization, and apologies we couldn't land this more promptly.


Identify unit testing gaps and fill them

Identify any gaps in unit test coverage and areas that need some more and fill them. Out of the three areas (code generator tool, runtime library, and generated code), the runtime library does need more coverage. The code generator tool probably needs some cleanup and maybe more tests for what remains.
### Tasks
- [ ] Check that the new `hashcode()` and `equals()` methods are tested in the generated code, including corner cases
- [ ] #28
- [ ] To do - add more specific tasks

Not sure about any corner cases, but the generated Test files for models include dedicated tests for the generated equals() and hashCode() methods. So I'm resolving that task.

In the recent PR #166 , the coverage has been improved for the code that seemed worth covering. The remaining gaps don't seem critical and can be tackled as we modify the code in the future.


stencil uses snabbdom.

I will love to see why do they need to fork it, if anyone has more info about it

They are manually handling the slot projection.
There's also some adaptation to handle server side rendering.

@zigomir Why did you close the PR? We would like to have it on the list with the requested changes 😄

@blikblum is there anything that we can do in snabbdom directly to accomodate those two features? One of my projects is doing something similar with slots without having to patch snabbdom, maybe we could document how to do so. As for server side rendering, we will need more info about what was patched, to see if we can accomodate that too.
Please, reopen the PR, update the link according to our request, so we can merge it :)

Hey, sorry for closing this, I just didn't bother editing :P. Now I can't reopen it because of: The patch-1 branch was force-pushed or recreated.

Sorry, i don't have enough info to answer that, i'm just a snabbdom user that also follows stencil development.
Incidentally i'm interested in a snabbdom implementation of slot projection for custom elements without shadowDOM

Incidentally i'm interested in a snabbdom implementation of slot projection for custom elements without shadowDOM

me too! /cc @diervo
Rant
The main situation today is that as part of the patching process (going thru modules) does not allow you to rearrange the children list, because that reference is cached before patching the node. As a result, you have to do some gymnastics, e.g.:
// in your snabbdom module, update/create method:
const { data: { slots }, children } = vnode;
const newChildrenCollection = rearrangeChildrenAndSlots(children, slots);
vnode.children.length = 0;
Array.prototype.push.apply(vnode.children, newChildrenCollection);

note: the code above mutates the original children list provided to the vnode, which means it might have side effects, not good.
This is somehow horrendous, and error prompt. Maybe we should not cache that value, and just collect it after the patching of the element finishes, and before patching the children, so modules can actually replace the vnode.children with a new computed list of children.


caret dependency ranges

Ref. https://github.com/observablehq/plot/pull/2020
Observable Plot depends on<EMAIL_ADDRESS>but the semver range is meaningless since D3’s package.json specifies only major versions — you get<EMAIL_ADDRESS>but you might get an older version of d3-scale-chromatic that doesn’t have schemeObservable10. This ensures that whatever version of d3 you have, you have at least the latest corresponding transitive dependency version, which makes sense given that d3 re-exports these transitive dependencies.

Do you know when will this be released? Latest on NPM is still 7.9.0 https://www.npmjs.com/package/d3/v/7.9.0


Convert to .Net Standard

Need to remove the requirement to the Robots Nuget package - probably can throw together a really basic implementation to read the rows of a "robots" file to find sitemaps.

Converted in d452fcc though "Robots.txt" functionality has been removed. Will be re-added at a later stage (see #2).


use the word-count example in example analysis

https://github.com/coderefinery/word-count is the perfect example project to play around with in notebook.

visualizations
debug
extend the code to plot the full zipf distributions
interactive widget fitting of Zipfs law to the data
etc

fixed in 662dae3


Create initial Entity Diagram

Create a diagram of entities in the code for use both in DB schema and REST API architecture.


Freeze tooz version

tooz 1.21.0 breaks test and unleashes monsters from the pits of hell. So until
the gods have mercy on us and fix the break freeze to last known version.
Test test_over_threshold (tests.unit.policies.test_concurrency.ConcurrencyPolicyTest)
woudl simply block.

Good catch. :+1:

God bless you!


Cannot run in DEBUG mode in IOS & android

Current behavior
The application ran successfully without debug mode but when we ran debug mode we got the error "Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication). A frequent cause of the error is that the application entry file path is incorrect."

Expected behavior
Platform

[✓] Android
[✓] iOS

React Native Version
React: 17.0.2
React Native: 0.66.3
React Native Compressor Version
Reproducible Steps And Demo

you should provider minimal reproduce code or repo

I have run test 0.73 on IOS it error script @numandev1

thanks @chanphiromsok I just generated the same version, react native 0.66.3, and also experienced an error, the repo is at https://github.com/ariefmanda/rn-test-key @numandev1

The same error when I try to use Keys object.
"react-native": "0.71.8",
"react-native-keys": "^0.7.10",

android/app/build.gradle
project.ext.keyFiles = [
  debug: "keys.development.json",
  release: "keys.staging.json",
]

apply from: "../../node_modules/react-native-keys/android/RNKeys.gradle"


Vectorizer exception not goes into commandProcess flow.

will close, https://github.com/stargate/data-api/pull/1742.
To main, then cherry-pick to dec-hotfix


import normalize_axis_index from numpy.lib on numpy>=2

This currently emits a warning, not an error (i.e. not that urgent), but I did notice this a couple of times in xarray's CI.
I'm not too happy about having to move the definition of module_available above the import (isort might revert that?), but I didn't know whether it would be fine to move that function to a separate module (and I was too lazy to try figuring out a good name for that module).

Thanks for doing this!


Migrate to faust-streaming bis

Follow up to https://github.com/marcosschroh/cookiecutter-faust/commit/b35e13b8ba3734b4321a7ac3f682b5c87fe18f2e

Hi @AntonOfTheWoods
Could you also update the README specifying that it is for faust-streaming fork? :-)

I thought about removing the "+" from the 3.7, as in order to have >3.7 and use the highly recommended rocksdb, you need to create your own rocksdb image (as there is only a 3.7 base image available). I guess I could submit a PR for a 3.9 rocksdb image if you are interested...

Hi @AntonOfTheWoods
Sorry for the huge delay. A PR is welcome!


Update BlazorCallWebAPI

Fixes #16609
Thanks @Ozkr16! ⛄

@danroth27 Did you want to take a last look? :eyes:


Front-end authentication?

Do we want to authenticate access to the front end, authenticate connection to the pi, or both?

 See ssl certs


Type links are invalid

When using the {@type mytype()} syntax, a link is generated to #type-mytype but the ExDoc equivalent should be #t:mytype/0 it seems.

@eproxus, I'm not sure this is dealt with by the plugin. I also have a similar issue when using {@link ...}. I'm also not sure this is an ex_doc issue, tbh. Maybe @starbelly knows best if this is from the chunk generation, or something else (?)

@starbelly, tested this again, and, as-is, this throws an exception with ex_doc but generates  a proper link with EDoc.

I will take a gander.

Yeah, I'm also setting this up to see if it's easily fixable next to ex_doc.

@paulo-ferraz-oliveira  An example would be good, it works for me, but @eproxus is referencing a form with curly brackets, which I'm not familar with. Also, edoc complains saying @type is deprecated btw.

Yeah, I can't get all of EDoc to work as per its documentation either.
The form @eproxus is mentioning is indeed deprecated, but still supported by EDoc...

Technically speaking @type period is deprecated AFAIK. The {@type {option, thing()@}} I could only find used in edoc itself and two places in epp_dodger. Its use seems limited to when you have a property list for options, but maybe there's other uses for it? A tad off subject from the fact that it can cause a crash, but still interesting and all simply a "FWIW".

Yeah, I'll let you decide on this one. If the ex_doc fix lands maybe we can close this, unless @eproxus is interested in writing some tests cases for which we'd need to see the code pass 😉

The pull request mentioned above was merged. No further changes regarding {@type ...} are expected. I don't think that this addresses your issue, but ex_doc's maintainers preferred a simpler solution (simply not crash).
I referred "Links are not usable, because generated HTML..." and ultimate we got "I'd strip out the  and just leave  but it definitely doesn't hurt to keep it this way for now."

The mentioned pull request is already merged, tagged, released (ex_doc) and imported and released here (rebar3_ex_doc). Closing...

Didn't exactly understand what was said here. What would the alternative to {@type ...} be to achieve type links using EDoc + the ex_doc plugin?

@eproxus, there is no alternative, as of this moment.
Fwiw:

@type is deprecated in Erlang since OTP 24
ex_doc (via the pull request) didn't accept that valid links are generated: https://github.com/elixir-lang/ex_doc/pull/1787#issuecomment-1744295489

So I don't think that, at least now, the plugin can move much more forward on this.


Issues with orchestrator, fastapi and gemini-1.5-pro

I'm using Gemini-1.5-pro and running the code within a fastapi app

Orchestrator always returns to human after first agent response, I had to modify llama_agents/orchestrators/agent.py line 107  response = await self.llm.apredict_and_call(tools_plus_human,...) to use only tools to get it to work properly.
To get the thing to even run within fastapi, I had to comment out llama_agents/launchers/local.py line 188 "signal.signal(signal.SIGINT, shutdown_handler)" otherwise it would just crash
FunctionCallingAgentWorker says Gemini-1.5-pro doesn't support Function calling API yet ReActAgent works just fine with function calling (although I suspect it may be throwing off the Orchestrator)

In general I'd advocate for people writing their own orchestrators. We have some changes upcoming that would make this easier to do
Are you running this inside an existing fast api server? The local launcher is meant to startup individual fastapi servers, and shouldn't be launched within an already running server
Makes sense, react is not great. Only gemini over vertex supports function calling right now

In general I'd advocate for people writing their own orchestrators. We have some changes upcoming that would make this easier to do
Are you running this inside an existing fast api server? The local launcher is meant to startup individual fastapi servers, and shouldn't be launched within an already running server
Makes sense, react is not great. Only gemini over vertex supports function calling right now

Thanks for your response.

Fair enough, I'll look into creating my own orchestrator (any idea on ETA on those changes that make it easier?)
Yes, I'm running launch_single within an existing fastapi server.. I realize it is running its own fastapi server although there isn't any other launcher I can use -> perhaps I shouldn't be using this library in the first place and should just build my own multi-agent setup with llama-index? I was just trying to leverage the orchestration and message queues, etc.. (à la autogen groupchat)
What surprised me is that ReActAgent is able to use function calling with gemini-1.5-pro but FunctionCallingAgentWorker doesn't

ETA 2 weeks ish? There's going to be some changes to llama-index-core, and that new abstraction will make its way over to llama-agents in a way that makes sense
I think the intention here would be to have llama-agents running separately from your existing fast-api server, and it interacts with the llama-agents system using a the client 👀 I hope that makes sense 😅 There's maybe room to make LocalLauncher have more than just launch_single() and instead launch everything into the existing async loop perpetually 🤔
React uses a prompting-based method to get the LLM to pick a tool. FunctionCallingAgentWorker relies on the LLM having some sort of tool calling built into the LLMs API (i.e. providing tools to OpenAI or anthropic requires no special prompting, its just a parameter in the api request)

https://github.com/run-llama/llama-agents/issues/156

We've done a major refactor, and I don't think this issue is relevant anymore


feat(jsonrpc): switch to spec 0.6.0

Moving away from JSON-RPC v0.5.1 to v0.6.0. Applications really should use v0.6.0 unless they have a very good reason to stay on v0.5.1.

Switched to Juno v0.8.0 for the integration tests as unfortunately Pathfinder v0.10.1 has a number of issues with its v0.6.0 implementation. Testing with Juno is more flaky though, as it doesn't implement automatic retry on rate limit errors. Will switch back to Pathfinder once the issues are resolved with a new release.


application/json responses fail for integer values

I expect to be able to

set the response content type to application/json
call res.send with an integer value for the response body
receive the integer value in the response body

the actual behavior is this exception:
TypeError: Argument must be a string
    at ServerResponse.send

Here is the failing example app: https://gist.github.com/1271167
using express version 2.2.0

the correct solution is to use res.json


How to enable/disable xeditable

Is it possible to enable/diasble the xeditable feature.
something  like: http://vitalets.github.io/x-editable/demo-bs3.html?c=inline#

I was surprised to see it has been added such functionality yet. I'm very interested to contribute to this feature. Currently I have a form where some part can be edited depending on user role.

I think this can be closed due to #235


[LogMeIn.LastPass version <IP_ADDRESS>6] Installer hash does not match

Should be fixed in https://github.com/microsoft/winget-pkgs/pull/28472.


Compress middleware: add option to configure the minimum body size

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

Feature
What did you expect to see?
A configurable option to configure the minimum body size for the compress middleware.
For example:
[http.middlewares]
  [http.middlewares.test-compress.compress]
    minimumBodySizeBytes = 5000

Hello ^^
I would love to get into contributing to traefik and this seems like a nice issue to start with.
Would it be possible for me to give it a try?

Hello @lus,
If you would like to give it a go, please open a PR! The community is always welcome to contribute.
You can find the contribution guides and information here: (https://doc.traefik.io/traefik/contributing/thank-you/)

Alright, I'll open a PR tomorrow.
Thanks for your reply :D


Support Request : If condition=true Then Libs.Halt

Hello,
I am very thankful for this tool, I hope you can offer some help.
I want to create a rule so that "if a text_string is found in the current webpage, then the rule should stop". I need the rule to stop if certain words appear, so that the user can regain control and manually move to the next stage.
This has to be related to the Before function, right ? This is what I (badly) came up with...
var rules = [{
url: "my_url",
name: "page 2",
"before": function(resolve, context) {
var original_content = window;
var strFound;
strFound=original_content.find("my_searched_string");
if (strfound) Libs.halt;
resolve(Libs.halt("Custom message to be displayed"));
},
fields: [{
selector: "input[name='finishButton']",
value: Libs.h.click
}]
}];
Please help me :)
Thanks a lot,
Xavier

Hi,
Form-O-Fill will usually run a rule just once when a match occurs.
Do you want one rule to be executed over and over again on a single page and then stop once the string is found or just once but only if the string is not found?
Cheers,
Frank

Ok this is what I came up with. Perhaps it can guide you a little :)
var rules = [{
  url: /Some-URL-REGEX/,
  name: "Slot available or not?",
  before: function(resolve, context) {
    // Search for <p> with content "no slot is available"
    // Change this to whatever jQuery selector you need!
    // If you use "contains": No quotes inside the ().
    context.findHtml("p:contains(no slot is available)").then(function(html) {
      // See help: "Using the HTML finder in a before/after function"
      // The selector was not found. Happy face ;)
      if (html.length === 0) {
        resolve(Libs.halt("There seems to be an opening!"));
      } else {
        // No slots available found. Sorry :(
        resolve();
      }
    });
  },
  fields: [{
    selector: "input[name='finishButton']",
    value: Libs.h.click
  }]
}
];

Cheers

\o/
Wow, man, you rock. I was worried because the text was not inside a "p" but inside a "form". Yet, it worked great :
(...)
context.findHtml("form:contains(plus de plage horaire libre)").then(function(html) {
(...)
All the best to you !
Cheers


Customizing number of threads to use

It seems PySmartDL doesn't support custom threads number, as it always uses 5.
I think this would be an useful option.

Hi @iTaybb
Your downloader package is the best ever python downloader ever, it is like the python version of IDM but it  is missing the option to change amount of threads to be use directly from the SmartDL class, parameter inputs and basically only need to be changed to:
SmartDL(self, urls, dest=None, progress_bar=True, fix_urls=True, logger=None, connect_default_logger=False, threads_count=12):
self.threads_count = threads_count
I am using python 3 and are install you package through pip, thus this change would be greatly appreciated if it effects the package available on the PYPI website.
Thank you for such an amazing downloader keep up the great work

I'll add it later today.

Thank you @iTaybb. I can't say this enough you downloader are amazing and brilliant downloader, you account for most everything need for a Smart downloader package.

Added in pySmartDL 1.2.5.


Reuse existing cache if commit is the same (not timestamp)

Optimization improvements. Will result in more cache hits and smaller cache size if many requests are made to different timestamps between the same two commit times.

Arkiveres, lukkes


cmd/go: should GOINSECURE imply GONOSUMDB?

What version of Go are you using (go version)?

$ go version
go version go1.14.1 linux/amd64

Does this issue reproduce with the latest release?
Yes.
It also reproduces with the current gotip.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN="/home/manlio/.local/bin"
GOCACHE="/home/manlio/.cache/go-build"
GOENV="/home/manlio/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE="*.local"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/manlio/.local/lib/go:/home/manlio/src/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build165827450=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.14.1 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.14.1
uname -sr: Linux 5.5.11-arch1-1
/usr/lib/libc.so.6: GNU C Library (GNU libc) stable release version 2.31.
gdb --version: GNU gdb (GDB) 9.1

What did you do?
The documentation in https://golang.org/pkg/cmd/go/#hdr-Module_authentication_failures says
If GOSUMDB is set to "off", or if "go get" is invoked with the -insecure flag, the checksum database is not consulted, and all unrecognized modules are accepted, at the cost of giving up the security guarantee of verified repeatable downloads for all modules

However when GOINSECURE is set for a module, GOSUMDB is consulted for that module.
If https://github.com/golang/go/issues/37519 is implemented, then GOINSECURE will have a different semantic compared to the -insecure flag.
Thanks.

@bcmills @matloob @jayconrod

@FiloSottile, do you have any insight on this?

I'm inclined to say that GOINSECURE and GONOSUMDB (which controls which modules are checked in the sumdb) should be independent.
Here's my reasoning: if you are blocked from an HTTPS connection to the origin, but the sumdb server is able to fetch from the origin via HTTPS, then the origin can serve a plain-HTTP response to you and you can combine that with the checksum from the database to obtain a trustworthy copy of the module, even if that module is not available from any proxy that you can reach. (Recall that a proxy can provide access to signed sum.golang.org checksums even if proxy.golang.org is blocked.)

Or, to put it another way: the difference between GOINSECURE and the -insecure flag is intentional. GOINSECURE provides very tightly-targeted exceptions for specific problems, whereas -insecure is one big hammer that disables everything.
Since you can also set GONOSUMDB (perhaps via GOPRIVATE), you can still fetch any module that you would have been able to fetch using -insecure — you just have to explicitly disable the two layers of security (TLS signatures and module checksums) independently.

The checksum database is more, not less, important for GOINSECURE fetches, as there is no transport security to rely on. We should definitely keep them independent, also because we should encourage setting GOPRIVATE for private modules, not GOINSECURE (unless needed).

Thanks.
I opened the issue  because I found the behavior between GOINSECURE and -insecure different, and I was not sure if it was intentional.  Since it is intentional, the issue can be closed.
I'm not sure if the difference between GOINSECURE and -insecure deserves additional documentation.   It should probably mentioned in https://github.com/golang/go/issues/37519.

Thanks for checking. I added a note on that issue.


Fix extension by upgrading vscode

I was getting a lot of null/undefined errors when trying to use the extension (after months of happily using it without issue).
I pulled the code down and I wasn't able to do a clean yarn install because the typings file being downloaded in the postinstall script was 404'ing. So the only change I made was to run yarn upgrade vscode and that not only fixed the install issue, but also appears to have fixed the extension for me.
4 years is a long time. Please let me know if the project is still maintained and you're willing and able to publish this patch to the vscode store so the extension keeps working. If not, I'm happy to talk about taking it on under the @testdouble org.

Assuming I won't hear back, I released a fix as this extension for now https://marketplace.visualstudio.com/items?itemName=testdouble.vscode-alternate-alternate-file


Stage shows Running verifications even when all are Failed

Description
All my AnalysisRuns are Failed:
$ k get ar
NAME                                     STATUS   AGE
dev.01j02dz4tbp75sf7zmvgkw3d3j.9e5f6ab   Failed   44h
dev.01j02hycta7xsjz7xczamptk6c.9d167fb   Failed   43h
dev.01j047c0f8qcgq8fyj3mn6sa0r.ab22279   Failed   28h
dev.01j03w1h1njwvj432nbh8m7xvk.a72c52c   Failed   31h
dev.01j03wxxntp3a3xm5pbpdzzzkd.bd13218   Failed   31h
dev.01j047080w47q6bvgdaqc11tws.d8df953   Failed   28h
dev.01j046aze40vzfvbwfc3mpvpc4.1bda081   Failed   28h
dev.01j03z1dzstgnx5tw85ty3apxr.97465d1   Failed   30h
dev.01j05679g7kccfehb2spejqcx7.151cea4   Failed   19h
dev.01j059yc9xmrej9hna0yspwxsz.3e53240   Failed   18h
dev.01j05me1tzty93z5mgvgpykvp3.1128f45   Failed   15h

Yet the UI still shows some as Running:

Steps to Reproduce
I have a feeling https://github.com/akuity/kargo/issues/2142 may have something to do with this (e.g. we are only processing the last one)
Version
v0.7.0

Logs
Paste any relevant application logs here.

@jessesuen and I spoke about this offline and it looks like this may be a backend bug. The UI uses the raw Status of the AnalysisRun to generate the icon, so there shouldn't be a way for the mismatch between CLI/UI above to occur. It's possible this was already fixed inadvertently

Correct @jessesuen , not sure but this could be related to https://github.com/akuity/kargo/issues/2128
UI relies on stage's freight histroy which has verification history. When user runs multiple promotions for same stage, and verifications for those run in parallel without waiting on one-another. Some of the previous verifications status freeze in stage's status but if you open the details of the verification from the UI, the status is correct and exactly what you see when you run k get ar for the particular analysis.
There are multiple solutions to this that I can think of.
First one being, we fix (sorry for this word, this might be expected behaviour please enlighten me if I am wrong) the verification history such that any previous analysis run statuses are available in history.
Second, UI should stop relying on freight history. It can directly query the AnalysisRun resources by labels filter. But I am not sure to rely on uniqueness of labels.
In any case, I would like to hear your thoughts - @jessesuen @krancour @hiddeco

Controller bug. It freezes AR status in the Stage's status -> freightHistory -> verificationHistory. I have reproducible.

Create dummy warehouse and stage.
Create 2 freights. Create dummy Analysis Template that takes around 10-20 seconds (doesn't matter as long as you transition promotion without one to finish).
Now promote first freight to stage, immediately promote second freight to stage and once again immediately promote first to stage. Check verification history or read from YAML kubectl describe stage and then Inside status field

I looked into this, and the problem is that the reconciler only looks at the AnalysisRun for the current Freight and not any previous ones that may have been replaced due to #2128.
While solving #2128 would cure the symptoms, we need to change the logic in the reconciler to ensure it's more resilient to these types of logical issues. For example, by listing all AnalysisRuns for a Stage and then processing their results.


Consider adding a pure PyTorch function for segment_mm and gather_mm

segment_mm and gather_mm are borderline in scope for this repo but they would still be useful additions. DGL provides some nice functions but installing it is non trivial.
https://docs.dgl.ai/generated/dgl.ops.gather_mm.html
https://docs.dgl.ai/generated/dgl.ops.segment_mm.html
https://pyg-lib.readthedocs.io/en/latest/modules/ops.html#pyg_lib.ops.segment_matmul
A workaround for gather_mm is found here and would be a good starting point for inclusion in torchsparsegradutils  (just needs a unit test):
https://github.com/pytorch/pytorch/issues/136747

For the record, the initial workaround
def my_gather_mm(a, b, idx_b):
  # mimic https://docs.dgl.ai/generated/dgl.ops.gather_mm.html
  R,D1,D2 = b.shape
  N = idx_b.shape[0]

  # Sanity check sizes
  assert(a.shape[0]==N and a.shape[1]==D1)

  torchdevice = a.device
  src_idx = torch.arange(N,device=torchdevice)

  # Ideally the conversions below to nested tensor would be handled without for looops and withour copy
  nested_a = torch.nested.as_nested_tensor(
      [torch.index_select(a,dim=0,index=torch.nonzero(idx_b==i).squeeze()) for i in range(R)] )
  src_idx_reshuffled = torch.cat(
      [torch.index_select(src_idx,dim=0,index=torch.nonzero(idx_b==i).squeeze()) for i in range(R)] )
  nested_b = torch.nested.as_nested_tensor(
      [b[i,:,:].squeeze() for i in range(R)] )

  # The actual gather matmul computation
  nested_ab = torch.matmul(nested_a,nested_b)

  # Convert back to tensors, again, ideally this would be handled natively with no copy
  ab_segmented = torch.cat(nested_ab.unbind(),dim=0)
  ab = torch.empty((N,D2),device=torchdevice)
  ab[src_idx_reshuffled] = ab_segmented
  return ab

can be simplified a bit
def my_gather_mm(a, b, idx_b):
  # mimic https://docs.dgl.ai/generated/dgl.ops.gather_mm.html
  R,D1,D2 = b.shape
  N = idx_b.shape[0]

  # Sanity check sizes
  assert(a.shape[0]==N and a.shape[1]==D1)

  torchdevice = a.device
  src_idx = torch.arange(N,device=torchdevice)

  # Ideally the conversions below to nested tensor would be handled without for looops and without copy
  #nested_a = torch.nested.as_nested_tensor(
  #    [torch.index_select(a,dim=0,index=torch.nonzero(idx_b==i).squeeze()) for i in range(R)] )
  nested_a = torch.nested.as_nested_tensor([a[idx_b==i,:] for i in range(R)] )
  #src_idx_reshuffled = torch.cat(
  #    [torch.index_select(src_idx,dim=0,index=torch.nonzero(idx_b==i).squeeze()) for i in range(R)] )
  src_idx_reshuffled = torch.cat( [src_idx[idx_b==i] for i in range(R)] )
  nested_b = torch.nested.as_nested_tensor(
      [b[i,:,:].squeeze() for i in range(R)] )

  # The actual gather matmul computation
  nested_ab = torch.matmul(nested_a,nested_b)

  # Convert back to tensors, again, ideally this would be handled natively with no copy
  ab_segmented = torch.cat(nested_ab.unbind(),dim=0)
  ab = torch.empty((N,D2),device=torchdevice)
  ab[src_idx_reshuffled] = ab_segmented
  return ab


First argument of mix() is not optional

polished version: 1.7.0

Mixin/Helper/Shortand you were using and how you were using it:
polished.mix('#fff', '#f00');

What you are seeing:
polished.js:1480 Uncaught Error: Passed an incorrect argument to a color function, please pass a string representation of a color.
    at parseToRgb (polished.js:1480)
    at mix (polished.js:2213)
    at fn (polished.js:1874)
    at <anonymous>:1:1

What you expected to see:
"#ff7f7f"

The first argument of the mix() function (the weight argument) is not "optional" however in the docs it's explicit that it should be optional and it's implied from the code.
It is optional in the sense that if you pass undefined then the default 0.5 will be used but you can't use it with 2 arguments only.
A solution could be to either refactor the function to check the number of arguments or to update the docs + remove the question mark from the related code. Also the 3rd option is to just modify the docs to reflect that you need to pass undefined which doesn't make much sense to me. Neither of these options should be a breaking change.

@mxstbr Sorry, how can we have multiple definitions for a single function in Flow?

@bhough Isn't it better to have another issue/discussion specifically on API design topic?

@morajabi we won’t change the API for these, it is too ingrained in how they all work. This is specifically how to handle the odd case of mix since it is the only one off the top of my head that is trying to set a default for the first argument.

@Prinzhorn Already ahead of you! The docs will be updated soon: https://github.com/styled-components/polished/blob/docs-types-review/src/color/mix.js

@bhough nice 😘

Addressed by #327 and merged into version-2


Option for preserving whitespace within JSXChildren

Would it be acceptable to add an option to preserve whitespace within JSXChildren? I am building a framework for generating source code with JSX and in that context whitespace is important to preserve. In particular, if I had something like:
function PythonFunction({name}) {
  return <>
    def {name}():
      <PythonFunctionBody />
  </>
}

which compiled to something like: ["\n    def ", name, "():\n      ", $createComponent(PythonFunctionBody, {})], then I can use the leading whitespace for the first text node to establish the baseline indent level, and book-keep subsequent indent level increases within my render function.

This seems reasonable. I'm not sure if this would impact walks at all. It should be the same and match up I imagine. But that would be my main consideration.


Re-used content from USB Storage Blocking

This page appears to re-use content related to blocking USB storage so is very confusing to follow - especially the screenshots in most of the steps, where they show Removable Media related configuration, but the sample file link beneath them links to the correct printer related file.

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

ID: b3162a66-262e-660c-a6d2-512b9b7d3199
Version Independent ID: b3162a66-262e-660c-a6d2-512b9b7d3199
Content: Deploy and manage printer protection using Intune
Content Source: microsoft-365/security/defender-endpoint/deploy-and-manage-using-intune.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @nimishasatapathy
Microsoft Alias: dansimp

@nimishasatapathy Please help us in resolving this issue. Thanks


Correct macro use

Hello,
I was trying to get you example template to fill in the jinja2 fields but I never could. I made sure mkdocs-macros was installed and I was able to load the config test just fine on my home page with {{ macros_info() }}
When creating the PDFs I get no errors, and the resulting PDF looks perfect, except the field are still just the field {{ whatever }}.
I feel like there's some config I'm missing but I'm at a loss. Any idea where to look next?
Other then that thanks so much for this extension. Makes a beautiful PDF!

Hello @wbste,
Did you make sure to load the exporter plugin before the macros one?
It should work out of the box.
For reference, feel free to check out the mkdocs.yml configuration file used for this project's documentation.

Of course!
You should be able to do so by creating a Python functions that returns the page's name and reference it as the download attribute of the button.
See this page for more details.


Download: XHR failed when installing plugin via vscode

Does this issue occur when all extensions are disabled?: No

VS Code Version: 1.65.2
OS Version: macOS 11.6.4

Steps to Reproduce:

When trying to install a plugin, i get an error "Download: XHR failed"
I manually installed the downloaded VSIX and it works fine.
The strange thing is that I can't install the 3.14.0 version of this plugin via VSCode, but the old version can be installed.
I have referred to this issue, and installing this version with VPN off also failed

it works now...

it works now but i do nothing


Facing issue while compiling etcd in Windows7 64 bit

Bug reporting
I have one query and facing one issue related to it:

Is it possible to compile etcd software in windows?
If yes then how to achieve this:

i have done the following till now to achieve this:
i) installed mingw64
ii) installed gcc for windows 64 bit
iii) placed the additional dependecy files libdl.dll, libdl.dll.a in lib folder and dlfcn.h in include folder present inside C:\MinGW\mingw64\x86_64-w64-mingw32 folder.
Now on compling etcd i am getting the below error:

Did you just run go build github.com/coreos/etcd? You should build with https://github.com/coreos/etcd/blob/master/build.ps1 Powershell script.

Thanks gyuho it worked!


This PR changes the path counter for a timestamp. The counter was subscribing another paths.

Platforms affected
iOS
What does this PR do?
This PR changes the path counter for a timestamp. The counter was subscribing another paths.
What testing has been done on this change?
Only used on my application.
Checklist

[ ] Reported an issue in the JIRA database
[ ] Commit message follows the format: "CB-3232: (android) Fix bug with resolving file paths", where CB-xxxx is the JIRA ID & "android" is the platform affected.
[ ] Added automated test coverage as appropriate for this change.

this PR did a similar thing https://github.com/apache/cordova-plugin-camera/pull/306 and it's merged, closing


how to install only one iconset?

I would like only to install one iconset which is Ionicons and I don't need the other fontset. How do i install it?
can I do this?
yarn add react-native-vector-icons/Ionicons

I did that but it's not working

We’ve just released a major new version with significant changes and improvements. If you’re still experiencing this issue after upgrading, please open a new issue with updated details. We're closing all the very old issues to get on top of things. Thanks for your patience!


Start checking Python code in Github CI

Start simple with checking, just run Ruff and Mypy on **.py (i.e. all Python source files) with CPython 3.10.
Config for these tools is in pyproject.toml and are hopefully reasonable defaults.

Might be nice to add a badge to show CI is being run when this gets merged
Would be something like:
[![CI](https://github.com/OctopusET/sway-contrib/actions/workflows/ci.yaml/badge.svg)](https://github.com/OctopusET/sway-contrib/actions/workflows/ci.yaml)

Which would look like  when merged, but this will be broken until it's merged.
Also probably worth changing the triggers around so it's only run on pull requests (i.e. on: pull_request in .github/workflows/ci.yaml), it's currently on: push so I could test a run.


Feature/add structured logging interface2

Description
Follow up on PR #126 .
Implements structured logging with custom sinks.
Implements an absl sink that will format the structured logging and pipe it in absl logs.
Type of change
Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

Checklist before requesting a review

[x] I have performed a self-review of my code.
[x] If it is a core feature, I have added thorough tests.
[x] If this is a new component I have added examples.
[ ] I updated the README and related documentation.

Missing

[ ] fmt like interface
[ ] should the Logger wait on destruction that all messages are consumed?
[ ] try out and document alternative usage of fields (like suggested by fillipo)

had to jump will do the description later

@filippobrizzi @lievenvanderheide thanks for the reviews!
@lievenvanderheide do you have thoughts ad suggestions on the logging interface itself? does it feel comfortable to you (since we will use that in many places probably)
BTW when I resolve comments without further comment it means I accept the changes and implement as suggested.

Question. MessageQueueConsumer automatically processes data, right? IMO, we want the ability to trigger processing manually, such as to e.g. add logs to a frame, and then send out the aggregated logs all at once, at frame rate.

added an issue to discuss this independantly since its out of scope
https://github.com/olympus-robotics/hephaestus/issues/204

Question. MessageQueueConsumer automatically processes data, right? IMO, we want the ability to trigger processing manually, such as to e.g. add logs to a frame, and then send out the aggregated logs all at once, at frame rate.

@lhruby what is the use case for this? if it is performance, the way the sink flushes the data can be tuned and depends on the sink implementation.
If want to define grouping than this is a requirement on the frontend. Right now by design each log line is a different LogEntry and no grouping can be defined, other than in the database by module name or tags.

connected to #205

So I guess we finally converged to a common interface design.
heph::log(heph::Level::WARN, "my message",{"num",num},{"other_field", val});

I will merge this PR from my fork to olympis-robotics/hephaistus branch and do the refactor there since this PR has a lot of scattered info everywhere.


Updates and tests for plan serialization and deserialization

Motivation and Context
The change improves the serialization and deserialization of Plan objects.
Description
Allows deserialization of Plans without a context. Adds unit tests for the Plan and ContextVariables classes, which cover various scenarios and edge cases of serializing and deserializing plans and context variables.
Details:

Updates the custom converter for the ContextVariables class, which serializes and deserializes the key-value pairs as an array of objects, instead of a dictionary. This improves the efficiency and readability of the JSON format.
Add a new file PlanSerializationTests.cs to the SemanticKernel.UnitTests project, which contains unit tests for the Plan class. The tests verify that a plan can be serialized and deserialized correctly, and that the plan state is updated correctly after each step execution. The tests also check for invalid JSON strings.
Add a new file ContextVariablesConverterTests.cs to the SemanticKernel.UnitTests project, which contains unit tests for the ContextVariablesConverter class. The tests verify that the converter can correctly serialize and deserialize context variables to and from JSON, and handle null, empty, and invalid inputs.

Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
[x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

Currently holding for #598


dbeaver: use JDK17 for Maven build

The build of the dbeaver package is currently failing on master. This popped up while working on #229144. The reason for the failure is that while the JDK to run DBeaver was correctly set to JDK17, the JDK used to run the Maven build somehow implicitly went to JDK19. You'll only see this if you touch the checksum, otherwise the package is just read from cache. Not sure how that can even happen :thinking:
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] 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

[ ] 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
[ ] 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.

Result of nixpkgs-review pr 238211 run on x86_64-linux 1

1 package built:

dbeaver

Result of nixpkgs-review pr 238211 run on x86_64-linux 1

1 package built:

dbeaver


[Camel 3.16] rest-json example compliation error

Error:  COMPILATION ERROR :
[INFO] -------------------------------------------------------------
Error:  /home/runner/work/camel-quarkus/camel-quarkus/camel-quarkus-examples/rest-json/src/main/java/org/acme/rest/json/Routes.java:[51,17] cannot find symbol
  symbol:   method route()
  location: class org.apache.camel.model.rest.RestDefinition
Error:  /home/runner/work/camel-quarkus/camel-quarkus/camel-quarkus-examples/rest-json/src/main/java/org/acme/rest/json/Routes.java:[64,17] cannot find symbol
  symbol:   method route()
  location: class org.apache.camel.model.rest.RestDefinition

It should be related to [CAMEL-17675] Rest DSL - Removed inlined routes

Fixed in https://github.com/apache/camel-quarkus-examples/pull/81.


Modernize build system to use CMake

First pass at modernizing the build:
$ cmake ..
-- Using compiler cache
-- The C compiler identification is AppleClang <IP_ADDRESS>01145
-- The CXX compiler identification is AppleClang <IP_ADDRESS>01145
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++
-- Check for working CXX compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Performing Test COMPILER_SUPPORTS_FUNROLL_LOOPS
-- Performing Test COMPILER_SUPPORTS_FUNROLL_LOOPS - Success
-- Performing Test COMPILER_SUPPORTS_FNOSTACKLIMITS
-- Performing Test COMPILER_SUPPORTS_FNOSTACKLIMITS - Failed
-- Performing Test COMPILER_SUPPORTS_WALL
-- Performing Test COMPILER_SUPPORTS_WALL - Success
-- Performing Test COMPILER_SUPPORTS_MARCH_NATIVE
-- Performing Test COMPILER_SUPPORTS_MARCH_NATIVE - Success
-- Found MPI_C: /usr/local/Cellar/open-mpi/4.0.0/lib/libmpi.dylib (found version "3.1")
-- Found MPI_CXX: /usr/local/Cellar/open-mpi/4.0.0/lib/libmpi.dylib (found version "3.1")
-- Found MPI: TRUE (found version "3.1")
-- Could NOT find OpenMP_C (missing: OpenMP_C_FLAGS OpenMP_C_LIB_NAMES)
-- Could NOT find OpenMP_CXX (missing: OpenMP_CXX_FLAGS OpenMP_CXX_LIB_NAMES)
-- Could NOT find OpenMP (missing: OpenMP_C_FOUND OpenMP_CXX_FOUND)
CMake Warning at CMakeLists.txt:46 (message):
  OpenMP not available, activating workaround

-- Configuring done
-- Generating done
-- Build files have been written to: /Users/dluxen/Coding/KaHIP/build

and then
$ time make
Scanning dependencies of target libkaffpa
[  1%] Building CXX object CMakeFiles/libkaffpa.dir/lib/data_structure/graph_hierarchy.cpp.o
[  2%] Building CXX object CMakeFiles/libkaffpa.dir/lib/algorithms/strongly_connected_components.cpp.o
[  3%] Building CXX object CMakeFiles/libkaffpa.dir/lib/algorithms/topological_sort.cpp.o
[  4%] Building CXX object CMakeFiles/libkaffpa.dir/lib/algorithms/push_relabel.cpp.o
[  5%] Building CXX object CMakeFiles/libkaffpa.dir/lib/io/graph_io.cpp.o
...
Scanning dependencies of target evaluator
[ 99%] Building CXX object CMakeFiles/evaluator.dir/app/evaluator.cpp.o
[100%] Linking CXX executable evaluator
[100%] Built target evaluator

real	0m47.557s
user	0m38.318s
sys	0m8.008s

Tested compiler configurations:

Linux
macOS (Mojave

GCC
4.9.4 5.5 6.4 7.3 8.2
8.3

Clang
6.0 7.0.1
AppleClang 10.0.0 7.0.1

OpenMP is activated and deactivated based on availability.


CreateWorkItem@1 | Task not recognized.

Task Documentation: https://marketplace.visualstudio.com/items?itemName=mspremier.CreateWorkItem
Problem on VSCode:

Use case eg:
    - task: CreateWorkItem@1
      displayName: Azure Boards Create Bug Card
      inputs:
        teamProject: #
        areaPath: #
        iterationPath: #
        workItemType: bug
        title: #
        fieldMappings: |
          #

I just open this Issue to help on documentation, i will try make a PR for this correction, its ok to core developers?

@50Wliu Do you believe that this would have to be valid even if it is a task supported by Microsoft's own team?

Yes, no matter who it's published by, if it's not installed by default on a fresh Azure DevOps organization, we won't include it in the schema.


How to create an sbt task that is assembly without the tests.

I am trying to create a custom task that runs sbt assembly without running any tests.
lazy val assemblyWithoutTest = taskKey[sbt.File]
assemblyWithoutTest := {
  assembly
}

assemblyWithoutTest.settings := {
  assembly.settings
}

test in assemblyWithoutTest := {}

I have seen the issue https://github.com/sbt/sbt-assembly/issues/140 but it does not satisfy the requirement we have been and it should be a separate task.
I also tried this:
import sbtassembly.AssemblyKeys._
assemblyWithoutTest= assemblySettings
test in assemblyWithoutTest := {}

But it does not compile
I have been going through the source code and I found this:
assembly := Assembly.assemblyTask(assembly).value

What is this define and assign? It's really confusing.

I concur that sbt assembly shouldn't be running tests. It makes the system less stable and less flexible. You would expect sbt coverage test coverageReport clean compile assembly to make sense as a sequence of actions and binding these together makes the system confusing, inconsistent, slower and more fragile. It's not good design. Do one thing and do it well.


♻  Move unchanged_toast loading to wal pipeline server

#472  👈
main

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

Join @RTLS and the rest of your teammates on  Graphite


Use an EOA for our spender, simplify tutorial

Significantly speeds up the quickstart to use an EOA for our spender.

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1

Review Error for ilikesymmetry @ 2024-11-08 20:05:00 UTC
User cannot review their own commit


cannot reuse already awaited coroutine

I'm building an async stream and started getting this error:
future: <Future finished exception=RuntimeError('cannot reuse already awaited coroutine')>
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/tornado/gen.py", line 501, in callback
    result_list.append(f.result())
RuntimeError: cannot reuse already awaited coroutine

It doesn't crash anything, but I'm still interested in how to prevent it.
Here's the structure of the stream:

The error only appears when I add the left hand of the stream (from get_metadata). My understanding is that without it there's only one sink and so each coroutine produced by the source is only awaited once. How do I handle multiple sinks in this case?

Do all sinks get the expected data?

Yes, I tested this with a mock source that produces a fixed number of rows and it looks like all of them reach the target database even when there are these errors.


some question about nlp metrics

hello~ I see that the model uses the "same settings" in the paper, so I directly quote the results of the paper.
I have two questions.

What is the definition of "same settings"? Taking the R2gen paper as an example, the batch size of R2gen is not consistent with the 4 GPUs and batch size of 8 mentioned in this paper. So does the same settings only include the model setting but not the training setting?
Secondly, I noticed that there is no test score for cider in the R2gen paper. How did you get this score?

Hi, sorry for the confusion. The "same settings" in our paper means that we use their annotation files for dataset split and pre-processing including data wrangling (report cleaning).  We re-ran their public codes and added the CIDEr metric for evaluation. However, we did not achieve the same performances for other metrics they reported in the paper. So, we just cited other metric values and presented the CIDEr.

Hi, sorry for the confusion. The "same settings" in our paper means that we use their annotation files for dataset split and pre-processing including data wrangling (report cleaning). We re-ran their public codes and added the CIDEr metric for evaluation. However, we did not achieve the same performances for other metrics they reported in the paper. So, we just cited other metric values and presented the CIDEr.

Hi, I have run R2Gen and got close results on most metrics. However, my added CIDER score was only about 0.15, which is far from the 0.25 reported in your paper. Have you met this issue before? Thank you.


[BUG] Bloxstrap_20241215T090642Z

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[X] I did not answer truthfully to all the above checkboxes.

Bloxstrap Version
v2.5.4.exe
What problem did you encounter?