Slider to change chart viewing range

Great charts!
Will there be a viewing range slider any time soon?  Slide the left and right to change the breadth of data shown?

Honestly this doesn't sound like a bad idea, probably wouldn't be in core though.

@dtruel: I've just recently added a rage slider to my chart on a stats page I was building.
I cobbled it together with noUiSlider + wNumb
It didn't take very long to do, but if you'd like I can put together a Gist that shows what I did
@jakesyl I agree it doesn't need to be in the core, there are hooks for all the events you'd need, already exposed, but creating it as a plugin would be pretty great (I might take a bash at it sometime this evening)

@schme16 creating a plugin would be a good idea.

I had a quick go in my spare time at work today; it's rough at the moment, but I'll be cleaning it up over the next few days!
Patches welcome, of course, as is any advice about the way I'm creating the plugin!
https://github.com/schme16/Chart.js-RangeSlider

Closing since this won't be in the core and @schme16 made an awesome plugin to add this functionality.


Firefox hangs when searching with / and a text input field is open, only when there's a match

Whenever I search with / and I have a page open which contains a text input field and there is a match, Firefox hangs. This did not happen on previous versions of Firefox, and doesn't happen without Pentadactyl (i.e. when searching with Ctrl+F). I'm using Mozilla Firefox 45.8.0 from Gentoo and Pentadactyl hg7290. I'm not sure how to provide more debug info since Firefox completely hangs when this happens. I provide the last 50 lines of an strace below. My session consisted of opening this page, writing "if" in the text field, and then searching for "if" with /. Firefox then hangs and I send SIGTERM to it. If the entire strace would be useful I can provide it (are there no privacy issues in doing so?).
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5bfda4c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f49d5bfda48, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5bfda4c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f49d5bfda48, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7f49d5bfda4c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f49d5bfda48, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5bfda4c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f49d5bfda48, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7f49d5bfda4c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f49d5bfda48, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7f49d5bfda4c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f49d5bfda48, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7f49d5bfda4c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f49d5bfda48, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5bfda4c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f49d5bfda48, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
mmap(0x249d7b11a000, 65536, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x249d7b11a000
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7f49d5bfda4c, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0x7f49d5bfda48, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7f49d5c00040, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
futex(0x7f49d5c00040, FUTEX_WAKE_PRIVATE, 1) = 0
--- SIGTERM {si_signo=SIGTERM, si_code=SI_USER, si_pid=4565, si_uid=0} ---
unlink("/home/ff/.mozilla/firefox/32lkn570.default/lock") = 0
close(7)                                = 0
rt_sigaction(SIGTERM, {SIG_DFL, [], SA_RESTORER, 0x7f49d6d62ec0}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [TERM], NULL, 8) = 0
tgkill(1920, 1920, SIGTERM)             = 0
--- SIGTERM {si_signo=SIGTERM, si_code=SI_TKILL, si_pid=1920, si_uid=1001} ---
+++ killed by SIGTERM +++

Okay, I was able to pinpoint the issue. It's an infinite loop in common/modules/finder.jsm:491. That is, in the highlight function of the RangeFind class. Link. When removing that loop the issue disappears entirely (though highlighting results also breaks).
I got to this by placing a breakpoint before and after the loop (after trying other spots at finder.jsm). It reaches the first breakpoint, I press play, but it never reaches the second - Firefox becomes irresponsible and I have to kill it.
I am testing it on a more recent version of Firefox than I previously reported:
:version
Pentadactyl 1.2pre (created 2017/05/31 22:07:30) running on:
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Can any devs take a look at this?

Any news here, if this can be fixed?

This seems to work sometimes, but now always.
For instance: Search an IP address if some edit field is open.
How to reproduce:

Sign in to Wikipedia and edit a wiki
https://de.wikipedia.org/w/index.php?title=Private_IP-Adresse&action=edit
Search for an IP Adress:
/<IP_ADDRESS>

..freezing.

This is still unstable, last freeze on https://forums.gentoo.org, writing a comment, preview, search by /, freeze. Which is most annoying as all the comment is lost...


Update trillian dependency

This PR updates to trillian @ HEAD, which no longer contains verification logic.  It removes calls to the trillian verifier and replaces them with calls to a new rekor verify package!
The verify package currently only verifies the signed log root.

Nice! I want @bobcallaway to have a look here too.

OK, we tested that this can get rolled out safely.


The new "How-To: Install Dapr CLI" doc's powershell script errors and stops executing

Expected Behavior
I expect the power shell scripts in these documents to work.
Actual Behavior
I was NOT running powershell as admin since the doc said nothing about that.  I executed the below script copy/pasted from the document and got the following error:
PS C:> powershell -Command "$script=iwr -useb https://raw.githubusercontent.com/dapr/cli/master/install/install.ps1; $block=[ScriptBlock]::Create($script); invoke-command -ScriptBlock $block -ArgumentList 1.0.0-rc.2"
powershell : At line:1 char:106
At line:1 char:1

powershell -Command "$script=iwr -useb https://raw.githubusercontent. ...

  + CategoryInfo          : NotSpecified: (At line:1 char:106:String) [], RemoteException
  + FullyQualifiedErrorId : NativeCommandError

... /dapr/cli/master/install/install.ps1; =[ScriptBlock]::Create(); invok ...

                                                             ~

An expression was expected after '('.
+ CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : ExpectedExpression
PS  I ran the script in the pre 11/17/20 version of this document and it worked fine.  Here it is:
powershell -Command "iwr -useb https://raw.githubusercontent.com/dapr/cli/master/install/install.ps1 | iex"
Steps to Reproduce the Problem
Follow the instructions in the How-To document without being logged in as admin.
Release Note

RELEASE NOTE:

Thanks for the feedback! As a workaround please run in Command Prompt and we'll update our docs/command to work as expected.


Fastlane not setting the proper provisioning profile

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
Match is not managing my provisioning profiles. I have separate app identifiers for each lane, but it is not setting the matching provisioning profile during the build process and therefore failing the build with:
INFO [2018-02-08 12:34:11.52]: ▸ ❌  Code Signing Error: "assessmentmobile" requires a provisioning profile. Select a provisioning profile for the "Release" build configuration in the project editor.
INFO [2018-02-08 12:34:11.58]: ▸ ** ARCHIVE FAILED **
INFO [2018-02-08 12:34:11.58]: ▸ The following build commands failed:
INFO [2018-02-08 12:34:11.58]: ▸ Check dependencies
INFO [2018-02-08 12:34:11.58]: ▸ (1 failure)
ERROR [2018-02-08 12:34:11.60]: Exit status: 65
INFO [2018-02-08 12:34:11.67]: ▸ === BUILD TARGET assessmentmobile OF PROJECT assessmentmobile WITH CONFIGURATION Release ===
INFO [2018-02-08 12:34:11.67]: ▸ Check dependencies
INFO [2018-02-08 12:34:11.67]: ▸ Code Signing Error: "assessmentmobile" requires a provisioning profile. Select a provisioning profile for the "Release" build configuration in the project editor.
INFO [2018-02-08 12:34:11.67]: ▸ Code Signing Error: Code signing is required for product type 'Application' in SDK 'iOS 11.2'
INFO [2018-02-08 12:34:11.67]:
ERROR [2018-02-08 12:34:11.67]: ⬆  Check out the few lines of raw `xcodebuild` output above for potential hints on how to solve this error
WARN [2018-02-08 12:34:11.67]: 📋  For the complete and more detailed error log, check the full log at:
WARN [2018-02-08 12:34:11.67]: 📋  /Users/jwaldrip/Library/Logs/gym/assessmentmobile-CT-Assess Staging.log
INFO [2018-02-08 12:34:11.67]:
ERROR [2018-02-08 12:34:11.67]: Looks like fastlane ran into a build/archive error with your project
ERROR [2018-02-08 12:34:11.67]: It's hard to tell what's causing the error, so we wrote some guides on how
ERROR [2018-02-08 12:34:11.67]: to troubleshoot build and signing issues: https://docs.fastlane.tools/codesigning/getting-started/
ERROR [2018-02-08 12:34:11.67]: Before submitting an issue on GitHub, please follow the guide above and make
ERROR [2018-02-08 12:34:11.67]: sure your project is set up correctly.
ERROR [2018-02-08 12:34:11.67]: fastlane uses `xcodebuild` commands to generate your binary, you can see the
ERROR [2018-02-08 12:34:11.67]: the full commands printed out in yellow in the above log.
ERROR [2018-02-08 12:34:11.67]: Make sure to inspect the output above, as usually you'll find more error information there

Complete output when running fastlane, including the stack trace and command used

https://gist.github.com/jwaldrip/d59dfa4b38f78de9fe5a7ecbf29c7ba2
Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.13.3

Ruby
2.3.1

Bundler?
false

Git
git version 2.15.1

Installation Source
~/.gem/ruby/2.3.1/bin/fastlane

Host
Mac OS X 10.13.3 (17D47)

Ruby Lib Dir
~/.rubies/ruby-2.3.1/lib

OpenSSL Version
OpenSSL 1.0.2j  26 Sep 2016

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
9.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

if ENV["CI"]
  setup_travis
  ENV["MATCH_READONLY"] = false.to_s
end

IOS_PROJECT = "./ios/assessmentmobile.xcodeproj"
APP_IDENTIFIER = "com.commercialtribe.assessment-mobile"
APP_NAME = "CT Assess"
ENV['ENVFILE'] = ".env.production"

before_all do
  ensure_git_status_clean
end

after_all do
  reset_git_repo skip_clean: true
end

error do
  reset_git_repo skip_clean: true
end

private_lane :label_icons do |top: nil, bottom: nil|
  command = "label-icons"
  command << " --top=\"#{top}\"" if top
  command << " --bottom=\"#{bottom}\"" if bottom
  yarn command: command
end

platform :ios do
  private_lane :compile_app do |channel: nil, **options|
    # Set up some vars
    app_name = APP_NAME
    app_identifier = APP_IDENTIFIER
    version_number = get_version_number xcodeproj: IOS_PROJECT
    build_number = ENV["TRAVIS_BUILD_NUMBER"] || raise("Missing TRAVIS_BUILD_NUMBER")
    increment_build_number xcodeproj: IOS_PROJECT, build_number: build_number

    # If a channel is specfied, update the project to reflect it
    if channel
      app_name = app_name + " (#{channel})"
      app_identifier = "com.commercialtribe.assessment-mobile.#{channel}"
      update_info_plist(
        xcodeproj: IOS_PROJECT,
        plist_path: "assessmentmobile/Info.plist",
        app_identifier: app_identifier,
      )
      label_icons top: channel, bottom: "v#{version_number}b#{build_number}"
    end

    # Ensure the app is created on iTunes Connect
    produce(
      app_identifier: app_identifier,
      app_name: app_name,
      language: 'English',
      app_version: version_number,
    )

    # Sync the code signing
    sync_code_signing(
      type: "appstore",
      app_identifier: app_identifier,
      git_url: "git@github.com:CommercialTribe/assessment-certificates.git"
    )

    # Build the app
    build_ios_app(
      **options,
      project: IOS_PROJECT
    )

    # Return the app id
    app_identifier
  end

  desc "Push a new alpha build to TestFlight"
  lane :alpha do
    ENV['ENVFILE'] = ".env.staging"
    compile_app(channel: "alpha", scheme: "CT-Assess Staging")
    upload_to_testflight
  end

  desc "Push a new beta build to TestFlight"
  lane :beta do
    app_identifier = compile_app(channel: "beta", scheme: "CT-Assess Prod")
    upload_to_testflight(
      app_identifier: app_identifier
    )
  end

  desc "Release a version to the app store"
  lane :release do
    raise "Can only release from travis tag" unless (version_number = ENV['TRAVIS_TAG'])
    commit_version_bump xcodeproj: IOS_PROJECT, version_number: version_number
    compile_app scheme: "CT-Assess Prod"
    deliver(force: true, submit_for_review: true, automatic_release: true)
  end
end

platform  :android do
  desc "Push a new alpha build to the play store"
  lane :alpha do
    version_code = ENV["TRAVIS_BUILD_NUMBER"] || raise("Missing TRAVIS_BUILD_NUMBER")
    increment_version_code version_code: version_code
    ENV['ENVFILE'] = ".env.staging"
    gradle(
      task: 'assemble',
      build_type: 'Release',
      project_dir: 'android',
      print_command: false,
      properties: {
          "android.injected.signing.store.file" => ENV["ANDROID_KEYSTORE_PATH"],
          "android.injected.signing.store.password" => ENV["ANDROID_KEYSTORE_PASSWORD"],
          "android.injected.signing.key.alias" => ENV["ANDROID_KEYSTORE_ALIAS"],
          "android.injected.signing.key.password" => ENV["ANDROID_KEYSTORE_PASSWORD"],
        }
    )
    upload_to_play_store(track: 'alpha')
  end
end

`./fastlane/Appfile`
app_identifier "com.commercialtribe.assessment-mobile" # The bundle identifier of your app
apple_id<EMAIL_ADDRESS># Your Apple email address

itc_team_id "117943466" # iTunes Connect Team ID
team_id "9AZS5LT7UB" # Developer Portal Team ID

package_name "com.commercialtribe.assessment.mobile" # Android Package Name
json_key_file "/tmp/google_play.json" # Google Play Service Account Credentials

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.80.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-yarn
1.0
✅ Up-To-Date

fastlane-plugin-increment_version_code
0.4.3
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.0.0

slack-notifier
2.3.2

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

commander-fastlane
4.4.5

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

mini_magick
4.5.1

multi_xml
0.6.0

security
0.1.3

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

mime-types-data
3.2016.0521

mime-types
3.1

httpclient
2.8.3

google-api-client
0.13.6

highline
1.7.10

io-console
0.4.5

excon
0.60.0

rubyzip
1.2.1

CFPropertyList
2.3.6

mini_portile2
2.2.0

nokogiri
1.8.0

plist
3.4.0

faraday
0.14.0

os
0.9.6

googleauth
0.6.2

unf
0.1.4

domain_name
0.5.20170404

faraday_middleware
0.12.2

signet
0.8.1

fastimage
2.1.1

json
2.1.0

atomos
0.1.2

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.5.6

bundler
1.14.6

terminal-table
1.8.0

unicode-display_width
1.3.0

fastlane-plugin-yarn
1.0

fastlane-plugin-increment_version_code
0.4.3

generated on: 2018-02-08

@fastlane-bot your right, but the troubleshooting guide isn't very helpful in this regard.

This has been the most frustrating day in a long time wrestling with this issue. It looks like the export options are not being generated. Is this a known issue, or am I wrong and are they actually being generated? If so where are they generated to and how can I confirm?

Yeah, this is a huge pain.
Have you done this yet:

Open project in Xcode (9)
Archive the project
Once archived, export the generated .xcarchive file to an IPA file

During this process Xcode will should put an exportOptionsPlist file next to the generated IPA file that has the configuration it used.

You can take this file and edit it to fit your needs.

I think you could have a look at my fastlane lane.

This work for me , as follow:
    lane :release do

        disable_automatic_code_signing(path: "test.xcodeproj",
          team_id: "Y737MXXXXXX"
        )

        match(
          git_url: "https://git.coding.net/XXXXXXXX.git",
          app_identifier: "com.xxxxxxxx.test",
          type: "appstore"
        )

        update_project_provisioning(
          xcodeproj: "test.xcodeproj",
          target_filter: "test",
          profile:ENV["sigh_com.xxxxxxxx.test_appstore_profile-path"],
          build_configuration: "Release"
        )

        gym(
          workspace: "test.xcworkspace",
          scheme:"test",
          configuration: "Release",
          clean: true,
          export_method: "app-store",
          output_directory:"./build/",
          export_options: {
            method: "app-store",
            provisioningProfiles: {
              "com.xxxxxxxx.test" => ENV["sigh_com.xxxxxxxx.test_appstore_profile-name"]
            }
          },
          codesigning_identity:"iPhone Distribution: XXXXXX Common Name(XXXXXX)",
          output_name: "test_prod.ipa"
        )

        upload_symbols_to_crashlytics(
          dsym_path: "./build/test_prod.app.dSYM.zip",
          api_token: "ac2a264f7834a17a7d54ad806130ae1f23ad7c77"
        )

    end

Well @wade0317 that did it! Be sure to claim the bounty at the top of this issue.


Test power consumption of SGTL5000 under sleep mode

SGTL doesn't really have a sleep mode. Has a set of registers that can be disabled. But the disable in the library doesn't actually disable them. See https://github.com/PaulStoffregen/Audio/blob/master/control_sgtl5000.h#L44
Could benefit from an LDO.
To test, see power consumption BEFORE enable versus after.

The SGTL power consumption was tested by having the chip off for a number of cycles and then enabling it.

Mode
Current (mA)
Power (mW)

Dis
-125
-502

Dis
-125
-501

Dis
-125
-501

Dis
-125
-501

En
-125
-501

En
-125
-501

En
-125
-501

This test seemed unsuccessful.

Conclusion is to add an optional LDO for the SGTL in #16


python3 in client docker complains about missing numpy

[szheyu@zheyu-pc-infervision tensorrt-inference-server]$ docker run -it --rm --net=host tensorrtserver_client
root@zheyu-pc-infervision:/workspace# cd install/python/
root@zheyu-pc-infervision:/workspace/install/python# python3 image_client.py -m resnet50_netdef -s INCEPTION /workspace/images/mug.jpg
Traceback (most recent call last):
  File "image_client.py", line 30, in <module>
    import numpy as np
ModuleNotFoundError: No module named 'numpy'
root@zheyu-pc-infervision:/workspace/install/python# python image_client.py -m resnet50_netdef -s INCEPTION /workspace/images/mug.jpg
Request 0, batch size 1
Image '/workspace/images/mug.jpg':
    504 (COFFEE MUG) = 0.777365028858
root@zheyu-pc-infervision:/workspace/install/python#

This client Dockerfile installs pip for python2 and uses pip for installing numpy and a few libraries. You can change this to python3 if you wish to use the client with python3.

I encountered the same issue when I followed the docs here, so I think this is more of a documentation mismatch issue, because running the command with python works as expected.

There is some issue with the get-pip.py file for python3.
Here is the fix for the same.
# gets necessary dependencies
apt-get install python3-distutils
# gets installs python3-pip
curl -O https://bootstrap.pypa.io/get-pip.py && \
    python3 get-pip.py && \
    rm get-pip.py
# install tensorrtserver, numpy ..
pip3 install --upgrade install/python/tensorrtserver-*.whl numpy pillow


Bumping DNS extension version suppression to 0.0.2.

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

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

View a preview at https://prompt.ws/r/Azure/azure-cli/5915
This is an experimental preview for @microsoft users.


The Calendar does not refresh when a different year is selected (archived/future)

T500: Verifying the Calendar view for past events (current year)
https://memser.testrail.io/index.php?/tests/view/500
Steps to reproduce:

Launch the AUT url: https://events-qa.on.fleek.co/
Click on the Calendar icon on the view panel
Once the Calendar view is displayed, from the filters panel-select an archived/future year.

Expected Result:

The Calendar should get refreshed displaying the related events of the year
The 1st event of the year should automatically get displayed

Actual Result:

The Calendar does not gets refreshed displaying the related events of the year
The Calendar does not gets refreshed and remains on the same month

Fixed the above issue. @WinsCodes  Please verify

Verified and found the issue resolved (build tested: QA Build 004)


[JDK 24] Enable JEP 493 in Temurin 24 builds

Description
JEP 493 has this summary:
Reduce the size of the JDK by approximately 25% by enabling the jlink tool
to create custom run-time images without using the JDK's JMOD files. This
feature must be enabled when the JDK is built; it will not be enabled by
default, and some JDK vendors may choose not to enable it.

Proposal
Add --enable-linkable-runtime to Temurin 24 builds so as to enable this feature. It only affects users running jlink so as to produce custom runtimes. The nice property would be that the Temurin 24 JDK would ship without jmods directory by default. In order to cover cases where a link from the run-time image is not suitable I suggest to also package the jmods image as a separate artefact (like testimage, static-libs and friends) and make those available for each build via the API for users actually needing them.
Pros
By default, the Temurin 24 JDK download shrinks in size without any restrictions in terms of run-time needs. jlink users should be able to use it to link custom runtimes.
Cons
Certain use-cases might not be possible. For example, cross linking, linking from a modified runtime. See JEP 493 for details. For those users there would be the option to download the jmods artefact separately and get the same features as JDK 23+ had.

Test build (locked) with the parameter enabled is at https://github.com/adoptium/temurin-build/issues/4035 if anyone wants to play

The jemods  (like testimage, static-libs and friends)  should be also separate rpms subpkg.

The jmods (like testimage, static-libs and friends) should be also separate rpms subpkg.

Please file this in https://github.com/adoptium/installer/issues Thanks!

Agreed to enable this for JDK 24 at the PMC meeting on Wednesday Nov. 13. For now we won't package the jmods image, which might change if there is user-demand.

Quick point of note - this is all documented somewhere but we do have multiple options for where such options can be set:

The pipeline configs - probably the easiest to start with as it can be easily added only to the jdk24 one
linux.sh and friends in the temurin-build repo
The stuff in sbin in the temurin-build repo

PR enabling this option is here: https://github.com/adoptium/temurin-build/pull/4039

PR enabling this option is here: #4039

I'm working on added smoke tests for this. Any build with it should have this output in jlink --help
$ ./jdk-24+23/bin/jlink --help | tail -n2
Capabilities:
      Linking from run-time image enabled

PR with a smoke test is here: #4040


[material-ui][Table]  How to insert a row after a row and before a row on current page

Steps to reproduce
Link to live example: (required)
Please find below Link for live code: https://stackblitz.com/edit/ashok-reddy?file=muidatagrid.tsx,POC.css,index.tsx
from the Live code of an example Whenever i delete row in middle of rows or first row or middle of row on current page, it is being deleting row only last row from current page  , Even though if i delete any row of middle it is been always deleting last row only on current page .Therefore  issue here was On current page if delete or remove any middle row it always keep on deleting the last row only?
Current behavior
Whenever i delete row in middle of rows or first row or any row other than last row  on current page, it is being deleting row only last row from current page  ,
The following screenshot  where highlighted row i'm trying to delete it

The following screenshot where i deleted the highlighted row but was deleted the last row ::: error :::this was an error 👍

Expected behavior
Whenever i delete the particular row then it should only delete that particular row only.
Context
Whenever i delete row in middle of rows or first row or any row other than last row  on current page, then it should only delete that particular row only on current page.
Your environment

npx @mui/envinfo
Material-UI | 5.15.6
React | 18.2.19
browser | chome
react-hook-form| 7.51.2

Search keywords: MUI table

can you please change subject from this issue was how to insert a row after a row and before a row? I've resolved the [Not deleting the specified row from the current page from current live code ? now i was expressing the new was like can you please assist me How to insert a row after a row and before a row?

So, @ashokReddy00931993 , The link for code shared in this issue. I think the issue is already resolved whether adding a new row or deleting an existing row. Can you confirm?
If not can you please share the steps here. Thanks!


removing humane and replacing with alertify

Humane doesn't work well with require and causes unit tests to fail. I've replaced it with alertify.

I don't understand. Humane works fine on many projects using ng-admin, and tests pass (but not yours).
Did you bower cache clean?

No feedback for 9 days, closing.


Website Monitoring feedback 202302 and 202303

I have expanded the scope of this issue to be feedback on the various website-monitoring reports that have come in during 202302 and 202303.  I'll consider this done when we have a first draft that I would feel comfortable sharing with other leaders and not needing to be there to answer/explain it.  After that we can develop a separate process for how we report ongoing observations, questions, and suggestions.

This concerns https://github.com/protocol/network-measurements/blob/master/reports/2023/calendar-week-7/ipfs/README.md#website-monitoring
First off, thanks for adding this!  Good stuff.
A few things that I think would be helpful to document:

What is the configuration of the node monitoring these sites?  For example, is it stalk Chromium phantoms node?  (I think we should be explicit that Companion (for intercepting IPFS URLs) is not in the mix.

Is the cache cleared between each run?

I assume "Page Load" is https://github.com/macbre/phantomas/blob/devel/docs/metrics.md#performancetimingpageload .  I don't find their docs helpful.  There is so much that goes into loading a page.  That said, I assume this is the "Load" metric that shows up in one's web inspector (screenshot - red vertical bar).  I could imagine it would be better to get DOMContentLoaded (blue vertical) since that isn't as susceptible to the JS processing on the page I believe (but does capture the network traffic up front fetching JS).  (That said, this isn't my expertise and I know there are a lot of intricacies.  @lidel will likely have a good suggestion here.). Regardless, I'd love to be more specific than "page load", or at least point people to something like https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming so they have more insight into what that means)

Week over week trends - It would be great to have a mechanism to detect if this radically changes week over week.  One idea would be to pick a few sites and a few regions and plot the p50 and p90 of time to first bye (since that shouldn't be susceptible to the content of the page).

Other sites I could imagine adding:

ipfs.tech
blog.ipfs.tech
docs.libp2p.io
blog.libp2p.io
Or maybe it would be worth just syncing to whatever set of sites are being pinned to the collab cluster

Agree with @BigLep, we should  add 1 paragraph that defines what we mean by "The time it took to fully load the page.".
I know  @guseggert was looking into doing way more than measuring how long HTML took to transfer, and more than DOMContentLoaded – he was waiting for DOMContentLoaded AND also for all images on a page to load as well.  Not sure what ended up being the final metric, but we should document it to remove guesswork/confusion.
+ small nits:

add https://en.wikipedia-on-ipfs.org/wiki/ to reduce bias
replace ipfs.io with ipfs.tech  (context: https://github.com/protocol/bifrost-infra/issues/2018)

Great, thanks for your the feedback!

What is the configuration of the node monitoring these sites? For example, is it stalk Chromium phantoms node? (I think we should be explicit that Companion (for intercepting IPFS URLs) is not in the mix.

We run website measurements every six hours. Each of these measurements we consider a measurement run.
In each run, we start six Kubo nodes around the world in different AWS regions. As soon as their API is reachable, we wait for 10s to let the node settle, and then request these websites one by one. We request each website three times. Then we wait 10 minutes and request the set of websites again. We thought that this may simulate a warm(er) Kubo node that has a "better" routing table. The graphs in the weekly report don't yet distinguish between cold and warm nodes.
Actually, we're not only starting six Kubo nodes but twelve because we want to test the most recent stable Kubo version (v0.18.0) and the most popular according to our network crawls (v0.17.0 - up until last week, now it's also v0.18.0).
Another detail: in each run, we are also requesting every website via plain HTTP without going through the local Kubo node. This means we could compare both protocols.
We can easily change all of the above parameters (4x a day, 6 regions, settle times, 3 retries, 2 Kubo versions, etc.).
We are running the Kubo nodes on AWS's t3.medium instances and request the website through Kubo's local gateway. E.g., a website request looks like this: http://<IP_ADDRESS>:8080/ipns/filecoin.io. We thought that this would come close to the Companion's performance. However, IIUC if a user browses to, e.g., https://filecoin.io, the x-ipfs-path header gets intercepted and only the remaining resources will be loaded via IPFS. I think, with our experiments, we're simulating the case where a user would directly browse to ipns://filecoin.io.

Is the cache cleared between each run?

Yes, between each retry we run ipfs repo gc. However, the first website request is likely slower than the subsequent ones because BitSwap will discover the provider immediately in later requests.

I assume "Page Load" is https://github.com/macbre/phantomas/blob/devel/docs/metrics.md#performancetimingpageload

That's right :+1:

That said, I assume this is the "Load" metric that shows up in one's web inspector (screenshot - red vertical bar).

Not sure which screenshot you're referring to :/

Regardless, I'd love to be more specific than "page load"

Totally agree! Just to clarify what the performanceTimingPageLoad measures. I just looked it up (source) and it measures the difference between

loadEventStart - representing the time immediately before the current document's load event handler starts. The load event is fired when the whole page has loaded, including all dependent resources such as stylesheets, scripts, iframes, and images. This is in contrast to DOMContentLoaded, which is fired as soon as the page DOM has been loaded, without waiting for resources to finish loading.
navigationStart - a depracated feature "representing the moment [...] right after the prompt for unload terminates on the previous document"

@lidel phantomas already measures the DOMContentLoaded 👍 So I'll just replace the performanceTimingPageLoad metric with the DOMContentLoaded one?

Week over week trends - It would be great to have a mechanism to detect if this radically changes week over week. One idea would be to pick a few sites and a few regions and plot the p50 and p90 of time to first bye (since that shouldn't be susceptible to the content of the page).

Yup, I also wanted to have that but couldn't come up with a nice visualization that nicely captures all dimensions (latency, datetime, region, website, data points). What you're suggesting is actually a nice trade-off I think.
Suggestion: take ipfs.tech + en.wikipedia-on-ipfs.org/wiki/ p50 + p90 timeToFirstByte latencies from eu-central-1 and report these numbers every week.

Other sites I could imagine adding:

Updated list of websites: https://github.com/protocol/probelab-infra/pull/17

@dennis-tra : again, this is awesome, and thanks for the great reply.
A few followups...
Questions around the definition of a run

How are you combining all the datapoints for a <region,site,run>?  If I understand correctly, the <region,site,run> tuple is collecting 12 datapoints: 2 kubo version x 3 tries x 2 modes in http (direct-to-domain )and non-http (through local Kubo HTTP gateway)?

However, IIUC if a user browses to, e.g., https://filecoin.io, the x-ipfs-path header gets intercepted and only the remaining resources will be loaded via IPFS. I think, with our experiments, we're simulating the case where a user would directly browse to ipns://filecoin.io.

Yeah, you're right that there are some differences with companion vs. hitting the local Kubo HTTP gateway, but I think your approach is good/clean/simple.  Companion with time learns which domains are available via non-HTTP, and so future domain accesses is able to re-route the URL to the configured IPFS HTTP gateway.  (I believe there's more nuance here, but I think what you're capturing here is good/fine.)

Another implication of your "companion" approximation by loading through the local Kubo HTTP gateway is that page resources that don't live under the root domain will be fetched via HTTP.  In the companion case, they may get intercepted and fetched using non-http.

As a contrived example, for ipfs.tech, any assets (images, CSS, JS, etc) under ipfs.tech will continue to be fetched via non-http when you do http://<IP_ADDRESS>:8080/ipns/ipfs.tech, but if the top-level ipfs.tech page has <img src="https://libp2p.io/logo.png"/> that will be fetched via HTTP since Phanotms doesn't have the intelligence to know that libp2p.io assets can be fetched via non-http.  I think this is fine, but I think this caveat should be documented.

It's great we're clearing Kubo's cache.  What about the browser (phantoms) cache?

Events we're measuring around the page lifecycle
Doh, I added the screenshot to my original post - thanks.
load vs DOMContentLoaded - I've got a few things to say around this but am not necessarily laying out the points in the best way.

I think "load" event is actually what we want because it is doing what Lidel and Gus were looking at of waiting for all the images, JS, CSS, etc. to load.  We want all this network traffic for comparing fetching a site via non-http (local Kubo HTTP gateway) and HTTP (hitting the domain direct).
That said, in its current presentation, it will cause confusion because "load" times aren't necessarily comparable across sites.  Yes, smaller load time is better, but it also generally doesn't mater from a UX regard if the above the fold content is interactable sooner.  There are more objective assertions that can be made around DOMContentLoaded where studies have done to show that users report a site is "fast" if that event happens within X ms.  (I'm not up on the latest studies here.)  Something like DOMContentLoaded is more comparable in that sense.  That said, our goal here isn't to provide feedback to site creators on whether their site is meeting ideal UX targets....
By default when some people see https://github.com/protocol/network-measurements/blob/master/reports/2023/calendar-week-7/ipfs/README.md#performance-timing-page-load, they're going to think "What?  How is protocol.ai so slow?  It takes 1 second for me to load in my browser?  There must be something up with the measurements, or fetch via non-http is really slow?"
Most aren't going to know that the "load" event means.  We're going to need to caveat this.
Some may not realize that the "load" time is heavily affected by your browser cache and whether you've visited this site recently.
The critical thing we want to show is how does "load" time compare when using http vs. non-http.  At the minimum, non-http should have higher availability.  (If it doesn't, then what good is our tech?). It's ideal for it to also be more performant, but I'm not expecting we'll hit that given 1) most website assets are small and don't take advantage of block deduplication or tricks of fetching blocks from multiple peers and 2) so much has gone into optimizing HTTP for websites over the decades with CDNs, etc.
My big picture comment here is that I actually think the metrics you have are good, but we have to provide a view comparing http with non-http for a given site.

We can compare TTFB across the sites because that is more compatible (because not affected by page content), and it may lead to interesting questions as to "why is TTFB 3x slower for website X than website Y".

Week-over-week reporting
I like the idea of what you're suggesting but would add a bit:
Sites

ipfs.tech
en.wikipedia-on-ipfs.org/wiki/

Regions:

eu-central-1
us-east-1 or 2 (I added this given geography can matter a lot when it comes to latency)

Modes: (I added this, and maybe we do one graph for HTTP and one for non-http).

non-http
HTTP

Metric

p50 timeToFirstByte Latency
p90 timeToFirstByte Latency

The reason I think we want to plot HTTP vs non-http is:

non-http captures improvements in Kubo (or whatever IPFS implementation is used) (e.g., code optimizations, network routing improvements, data transfer improvements)
http mode benefits from all of the above plus HTTP specific things like CDNs.
Breaking them out lets credit be given where credit is due.  For example, I don't want Kubo/IPFS getting credit when the website TTFB goes down just because someone improved the HTTP CDN.

Meta
We have lots of good/important notes about this topic at this point.  Where is the durable place it's going to live?  While I do think we need some explanatory text in the report, I'm also fine for it to link to a more thorough document for more info.  You don't need to block on my review, but please include me when this is available for review.
Again, good stuff, and thanks!

I know @guseggert was looking into doing way more than measuring how long HTML took to transfer, and more than DOMContentLoaded – he was waiting for DOMContentLoaded AND also for all images on a page to load as well. Not sure what ended up being the final metric, but we should document it to remove guesswork/confusion.

(sorry didn't mean to close)

I have expanded the scope of this issue to be feedback on the various website-monitoring reports that have come in during 202302 and 202303.  I'll consider this done when we have a first draft that I would feel comfortable sharing with other leaders and not needing to be there to answer/explain it.  After that we can develop a separate process for how we report ongoing observations, questions, and suggestions.

Fresh observations from looking at week 9
Time First Byte

(nit) The asterisk "*" doesn't resolve to a link on the page.
(nit) "Note: the color scales are different in each graph." → "Note: the color scales are different in each percentile graph."
(nit) "Definitely check the sample size that went into the measurement of each website. The numnber is stated at the bottom of the graph."  This seems redundant.  (I agree with you though anytime we're talking about percentiles we need to be showing the sample size).
I like the idea of the "change since last week percentage", but I don't think it's very useful in practice because there isn't an ability to dive in to see what the trend is.  If previous weeks were very stable and then we see a sudden sustained jump or a slow creep up that is indicative of a problem.  That is what leads me to going with a smaller number of sites points that we plot over time.
I think the waters are further muddied here by combining http and non-http.  I agree that combining tells us if there is a root underlying issue like a provider of the content is misbehaving (e.g., like we had with Fleek) as that affects the http and non-http path but after that, getting insight likely requires separating them out.
We talk about when the stopwatch ends.  Lets also talk about when it starts.

DOMContentLoaded

Per before, I agree that DOMContentLoaded is a more comparable metric between sites because we want all sites to "DOMContentLoad" fast since that better mirrors the customer experience.  That said, this has a lot to do with a site's page layout, included JS, etc.  I don't think with these reports that we want to get into the business of helping site creators realize that their sites could be better optimized or are slow compared to other properties.   As a result, I don't think we should be surfacing here.  (I'm sorry I wasn't more clear on that last time, and certainly feel free to disagree.)
(Ignore if we drop this graph.)  If we keep it, why are we saying "These numbers don't account for the network latencies!".  I thought the stopwatch starts before the network calls have been made to load the page: https://developer.mozilla.org/en-US/docs/Web/API/PerformanceNavigationTiming

HTTP vs. Kubo

I don't think our sample sizes are big enough to use p99.
I think this is most meaningful to see week-over-week trends so we can see if there issues in Kubo, DHT, Gateway provider infra.

One idea would be to have a p90 graph for each tuple of <region,site>.  That graph would have two lines: HTTP and non-http.  This would be a matrix of graphs.  They could be small (200x200 pixels), but big enough for someone to see a trend line.  They can then click it to load a larger version of it.
I agree that we also want to make clear the sample size if looking at percentiles (thanks for adding to it).  Maybe we can add it as a column to the table of graphs above so someone can spot check to know that that sample size is reasonable.

In practice, here is what I'm suggesting:

Feel free to disagree and I'm up for discussing other options.

Also, what are the thoughts capturing all the meta-details?  Per before, we have lots of good/important notes about this topic. I want to make sure we have a durable place for it.  This could be in the report itself or listed somewhere else.
I think we also need a way where we can capture notes/investigations that were done.  I don't think slack threads will scale since it won't make it easy to see prior answers/investigations.  Ideally there is a self-surface way for anyone to see what investigations have done for a given week, or what our callouts/observations are for that week.  I think that likely means having an accompanying github issue, page, or Notion doc for each weekly report.  Some content will carry forward between reports and that's ok.  I'm happy to discuss this more.

Hi @BigLep,
sorry for the late reply. I have been working on improving our measurement setup. I spent some time last week putting our website measurement infrastructure on a new foundation and I'm much more confident about the data we are gathering now. I plan to document everything in this repository (note that we have created a ProbeLab GitHub organization, so this and other private repositories will eventually be migrated to that org). I have also explained my reasoning for the new setup here.
Because of this new setup, we don't have enough data to report in this week's report.
Some notes regarding the metrics we want to report: Further up in this issue, we focussed on the TTFB and domContentLoaded metrics. While working on our website monitoring infrastructure last week I read up on how to measure website performance and came across this list:
https://developer.mozilla.org/en-US/docs/Learn/Performance/Perceived_performance
To quote the website:

Performance metrics
There is no single metric or test that can be run on a site to evaluate how a user "feels". However, there are a number of metrics that can be "helpful indicators":
First paint
The time to start of first paint operation. Note that this change may not be visible; it can be a simple background color update or something even less noticeable.
First Contentful Paint (FCP)
The time until first significant rendering (e.g. of text, foreground or background image, canvas or SVG, etc.). Note that this content is not necessarily useful or meaningful.
First Meaningful Paint (FMP)
The time at which useful content is rendered to the screen.
Largest Contentful Paint (LCP)
The render time of the largest content element visible in the viewport.
Speed index
Measures the average time for pixels on the visible screen to be painted.
Time to interactive
Time until the UI is available for user interaction (i.e. the last long task of the load process finishes).

I think the relevant metrics on this list for us are First Contentful Paint, Largest Contentful Paint, and Time to interactive. First Meaningful Paint is deprecated (you can see that if you follow the link) and they recommend: "[...] consider using the LargestContentfulPaint API instead.".
First paint would include changes that "may not be visible", so I'm not particularly fond of this metric.
Speed index seems to be very much website-specific. With that, I mean that the network wouldn't play a role in this metric. We would measure the performance of the website itself. I would argue  that this is not something we want.
Besides the above metrics, we should still measure timeToFirstByte. According to https://web.dev/ttfb/ the metric would be the time difference between startTime and responseStart:

In the above graph you can also see the two timestamps domContentLoadedEventStart and domContentLoadedEventEnd. So I would think that the domContentLoaded metric would just be the difference between the two. However, this seems to only account for the processing time of the HTML (+ deferred JS scripts).
We could instead define domContentLoaded as the time difference between startTime and domContentLoadedEventEnd.

The revised measurement setup currently gathers the following data:

timeToFirstByte - as defined above
firstContentfulPaint
largestContentfulPaint
The full PerformanceNavigationTiming object

We could also include:

Time to interactive
domContentLoaded - as defined above

If I had the choice between only two metrics, I would choose timeToFirstByte and largestContentfulPaint.

Just want to note that the ask for week-over-week graphs was not unheard! I'm also working on this and will come back here when I have news. I'll try to address all your remarks from the last comment.
Also, I don't have a better place to discuss these things right now. Instead of GH we could use Notion or discuss.ipfs.io. I'll chat with @yiannisbot and @iand and come back here with a proposal. I'd document this discussion in the new location.

Explained the new website measurement methodology here: https://github.com/dennis-tra/tiros

Thanks @dennis-tra for the update.
Infra
Good call on getting good underpinning.
Thanks for sharing https://github.com/dennis-tra/tiros
I like all the defenses to prevent caching.
The only issue I'm wondering there is about: what advantage is Kubo getting for successive runs because it is already connected with the providers of all the website content.  I assume it's effectively getting to bypass content routing via DHT/IPNI and rely on Bitswap's content discovery.
Metrics we're reporting
Agreed on TTFB since that does measure HTTP vs. non-HTTP and is not dependent on the site's initial HTML payload.  It is comparable across sites.
Per before, "I don't think with these reports that we want to get into the business of helping site creators realize that their sites could be better optimized or are slow compared to other properties."  I'm a bit worried we're heading into these waters by talking about firstContentfulPaint, largestContentfulPaint, etc.  I think we should message our rationale with something like "We're including this metric because it helps a site owner see about the impact of using IPFS protocols over HTTP before their site is interactive.  HTTP vs. IPFS protocols have some impact on this metric, but they aren't the only culprit.  There have been many tools developed over the last decades of the modern web to help."  With a message like that, I guess it makes me think we should aslo prefer Time to interactive rather than largestContentfulPaint.  (I can see arguments either way but I would give preference ot interactivity rather than rendering of largestContentfulPaint because of how annoying the user experience is when you can't interact with the page to scroll or click.  Anyways, I'll defer here.)
Discussion place for weekly reports
I like the idea of having a discuss post per week (e.g., https://discuss.ipfs.tech/t/ipfs-measurement-report-calendar-week-10-2023/16114/2 ).  A couple of things:

We should maybe make this its own Discuss category so someone can subscribe to the category for notifications.
(nit) but I think it would be good to get an ISO date into the title: "🌌 IPFS Measurement Report - 2023-03-12"

The only issue I'm wondering there is about: what advantage is Kubo getting for successive runs because it is already connected with the providers of all the website content. I assume it's effectively getting to bypass content routing via DHT/IPNI and rely on Bitswap's content discovery.

We (ProbeLab) also discussed this previously and also assume that a subsequent request will likely be served directly via Bitswap. Since we're tracking if it's the first, second, third, etc., request in the Kubo node's lifetime, we could produce a graph that only considers the first requests. The sample size would be very small, though. Alternatively, we could actively disconnect from the content provider after each request. However, I don't think Kubo gives us information from which peer it fetched the data. If that were the case, we could certainly do that. Then we'd always measure the worst-case performance where we'd need to reach out to the DHT (although we could still, by chance, be connected to another providing peer).
On another note, we're complementing these website measurements with DHT performance measurements, where we directly measure the publication and lookup latencies.

I don't think with these reports that we want to get into the business of helping site creators realize that their sites could be better optimized or are slow compared to other properties.

I also think so, and that's exactly why I argued against the Speed index metric. firstContentfulPaint, and largestContentfulPaint will include latencies for subsequent requests from e.g., script, img, link tags, which may then also be served by Kubo (though, I saw that some websites make cross-origin requests which would then not be served by Kubo). That's why I think these two metrics will depend on Kubo's performance and are worth measuring - but it's certainly muddy.
However, that's also the case for the TTI metric. From the docs:

Time to Interactive (TTI) is a non-standardized web performance 'progress' metric defined as the point in time when the last Long Task finished and was followed by 5 seconds of network and main thread inactivity.

And a "Long Task":

Long tasks that block the main thread for 50ms or more cause, among other issues:

Delayed Time to interactive (TTI).
High/variable input latency.
High/variable event handling latency.
Janky animations and scrolling.

A long task is any uninterrupted period where the main UI thread is busy for 50ms or longer. Common examples include:

Long-running event handlers.
Expensive reflows and other re-renders.
Work the browser does between different turns of the event loop that exceeds 50 ms.

Especially the list of common examples sounds very website specific to me. I could imagine a SPA spending too much time on the main thread rendering the page. This wouldn't have something to do with Kubo's performance IMO.

I think measuring the TTI definitely won't hurt, so I'll try to track it regardless of whether we will eventually report it 👍

We should maybe make this its own Discuss category so someone can subscribe to the category for notifications.

Totally! We could also rename "Testing & Experiments" to something like "Measurements" (just to limit the number of categories). Who owns the forum? I believe I don't have the necessary permissions to create new categories.

(nit) but I think it would be good to get an ISO date into the title: "🌌 IPFS Measurement Report - 2023-03-12"

seems like I can't edit the post anymore :/ will do for the next 👍

Thanks @dennis-tra:
Kubo nodes having established connections to peers in successive runs

I think it's fine to leave as it.  I think we can make the case that it's expected that as IPFS protocols become more prevalent that your likelihood of being connected to a peer that already has the content goes up.  This is the "advantage" that the Kubo/IPFS path gets, just as the HTTP path is getting the advantage of server-side CDN caching.
It does hit on that we need to have a way for someone to find out all the persistent callouts/caveats about a given graph (i.e., someone should be able to see our hypothesis that runs 2+ for a given site will be more performant because of existing connections).  They don't have to be "in your face", but it should be self-service for someone to learn all the caveats (similar to what we're doing in https://www.notion.so/pl-strflt/IPFS-KPIs-f331f51033cc45979d5ccf50f591ee01 ).

Forum
For now I created a measurements subcategory: https://discuss.ipfs.tech/c/testing-and-experiments/measurements/39
I moved and renamed https://discuss.ipfs.tech/t/ipfs-measurement-report-2023-week-10-2023-03-12/16114
I also gave you moderation access.

It does hit on that we need to have a way for someone to find out all the persistent callouts/caveats about a given graph (i.e., someone should be able to see our hypothesis that runs 2+ for a given site will be more performant because of existing connections). They don't have to be "in your face", but it should be self-service for someone to learn all the caveats (similar to what we're doing in https://www.notion.so/pl-strflt/IPFS-KPIs-f331f51033cc45979d5ccf50f591ee01 ).

Totally, with our planned probelab website we want to give detailed description about the graphs and their measurement methodology.


add boats

⚠ EDIT THIS TEMPLATE AND REMOVE THIS MESSAGE WHEN YOU'RE DONE ⚠
Outline
Write a few sentences describing the suggestion you want to add. Be as concise as possible.
How?
Add more details about how this feature should work. Be as descriptive as possible, however, still concise.
Photos, videos, sketches (optional)
If you have any resoures documenting your idea, put them here!

duplicate


Install MediaWiki

Install MediaWiki into dev environment (#2). MediaWiki should go on Dev01, and auxiliary services (such as Shellbox) should go on Dev02.

[x] Install MediaWiki

[ ] Document MediaWiki install

[ ] Install Score

[ ] Document Score install

[ ] Install Shellbox

[ ] Document Shellbox

[ ] Install Firejail

[ ] Document Firejail

[ ] Shellbox and Firejail should not be installed adjacently, so it would be best to figure out how to "hot swap" them in and out of production.

[ ] Document dual setup

MediaWiki has been installed on capstone-01, but not yet configured. Apache also needs to be configured to do rewrites for pretty URLs. Docs for MediaWiki install should also be added to the wiki.

MediaWiki has been installed with Score. No protection systems have yet been added.


Trying to fix 4.0

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

@conda-forge-admin, please rerender

Looks good to me - then I close https://github.com/conda-forge/siesta-feedstock/pull/14 in favor of this one.

@jan-janssen thanks for helping with the upgrades! They solved some issues and made me understand the things a bit better! :)
I'll manage the 4.1 release as it gets released! I'll keep you as maintainer for now.


ISPN-5951 Fix NonIndexedRemoteContinuousQueryTest.testContinuousQuery

https://issues.jboss.org/browse/ISPN-5951

Pulling ....

Integrated. Thanks @danberindei !

Backported to 8.0.x too.


Fix: error if user doesn't specify 'classes' in options (Droppable).

...by adding defaults. Droppable currently throws an error if options is empty or the user doesn't specify 'classes'. Could check hasOwnProperty in getClassNameFor, but instead just used the defaults/Object.assign pattern that Draggables is already using.

Closing, will fix ESLint issue


[cli] changing back a bucket name that was used to test a recent feature

to @jacknagz
cc @airbnb/streamalert-maintainers

Renaming secrets bucket back to the right name. This was changed to test catching a bucket not found error and properly report it.

👍


GH-15234: [C#] Modify TestWebFactory to use a dynamic port to avoid port conflicts

Closes: #15234

@github-actions crossbow submit verify-rc-source-csharp-macos-arm64


Flow failed during LEF LVS

Description
yonga_modbus_controller is a MPW shuttle design. Its running part of regression in CI here
Latest regression run here: https://github.com/The-OpenROAD-Project/OpenLane-MPW-CI/pull/77/checks?check_run_id=8172372160
Till OpenLane 2022.09.02 flow completes successfully.
From OpenLane tag 2022.09.03 its Failed during Running LEF LVS
The difference i see wrt., netgen update.
logs/signoff/33-user_project_wrapper.lef.log as follows:
(no matching pin)                          |io_oeb[3]
(no matching pin)                          |io_oeb[2]
(no matching pin)                          |io_oeb[1]
(no matching pin)                          |io_oeb[0]
---------------------------------------------------------------------------------------
Cell pin lists for user_project_wrapper and user_project_wrapper altered to match.
Cells failed matching, or top level cell failed pin matching.

Expected behavior
Flow should pass all stages.
Environment
Kernel: Linux v3.10.0-1160.49.1.el7.x86_64
Distribution: centos 7
Python: v3.6.8 (OK)
Container Engine: docker v20.10.16 (OK)
OpenLane Git Version: OL_Tag_09_03-dev (Testing OpenLane tag: [2022.09.03](https://github.com/The-OpenROAD-Project/OpenLane/releases/tag/2022.09.03))
pip: INSTALLED
python-venv: INSTALLED
---
PDK Version Verification Status: OK
---

Reproduction Material
Required files for running netgen can be downloaded from here: https://jenkins.openroad.tools/job/OpenLane-MPW-CI-Public/job/production-small-3/job/PR-77/lastFailedBuild/artifact/OpenLane/designs/yonga_modbus_controller/runs/RUN_2022.09.03_22.22.18/
Logs
[STEP 33]
[INFO]: Running LEF LVS...
[ERROR]: There are LVS errors in the design: See 'logs/signoff/33-user_project_wrapper.lvs.lef.log' for details.
[INFO]: Saving current set of views in 'results/final'...
[INFO]: Generating final set of reports...
[INFO]: Created manufacturability report at 'reports/manufacturability.rpt'.
[INFO]: Created metrics report at 'reports/metrics.csv'.
[INFO]: Saving runtime environment...
[ERROR]: Flow failed.
[INFO]: The failure may have been because of the following warnings:
[WARNING]: Skipping Tap/Decap Insertion.

    while executing
"flow_fail"
    (procedure "quit_on_lvs_error" line 12)
    invoked from within
"quit_on_lvs_error -log $count_lvs_log"
    (procedure "run_lvs" line 79)
    invoked from within
"run_lvs"
    (procedure "run_lvs_step" line 10)
    invoked from within
"[lindex $step_exe 0] [lindex $step_exe 1] "
    (procedure "run_non_interactive_mode" line 52)
    invoked from within
"run_non_interactive_mode {*}$argv"
    invoked from within
"if { [info exists flags_map(-interactive)] || [info exists flags_map(-it)] } {
    if { [info exists arg_values(-file)] } {
        run_file [file nor..."
    (file "./flow.tcl" line 401)
make: *** [Makefile:175: quick_run] Error 1
make: Leaving directory '/tmp/workspace/_Public_production-small-3_PR-77@2/OpenLane'

@vijayank88 is this still an issue?

@kareefardi
Still facing LVS error:

(no matching pin)                          |io_oeb[37]
.
.
(no matching pin)                          |io_oeb[6]
(no matching pin)                          |io_oeb[5]
(no matching pin)                          |io_oeb[4]
(no matching pin)                          |io_oeb[3]
(no matching pin)                          |io_oeb[2]
(no matching pin)                          |io_oeb[1]
(no matching pin)                          |io_oeb[0]

@vijayank88 You could try adding this to the magic extraction command.
ext2spice short resistor

Without this, only one of the shorted pins remains in the extracted netlist. With this, all the pins remain with a virtual resistor between shorted pins (which matches the verilog netlist).
This won't work with SRAM designs though.

@d-m-bailey
For assign io_oeb = {MPRJ_IO_PADS{wb_rst_i}};`
In generated netlist
assign io_oeb = { wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i, wb_rst_i };

All reset pin connected to io_oeb. But why LVS throws error as unmatched pins?

In the layout, all the io_oeb[*] pins are shorted to one net.
Without ext2spice short resistor, only one of the shorted nets remains in the final extracted netlist - the pins connected to the shorted nets are removed causing the unmatched pins error.

Ok. I will try to include above option and let you know. thanks

@d-m-bailey Thanks. After updating ext2spice short resistor LVS issue got fixed.
Is that ok to add that variable permanently  or its need to be added only specific scenarios?

It doesn't work with openram, but any design other than that might be ok.


Target jdk version

What is the target JDK? It seems to me that some projects are in 1.6 and others in 1.7.
A+jyt

Thanks for reporting! Adding an FAQ entry and notes.


An AlignPointElem has a non-zero height

Description
A line of - - should have a very small height, as shown in the left two boxes' rendering; but after inserting & to this line, the line gains a visible height, as shown in the right two boxes.
#box($ - - $, fill: silver)
#box($ a \ - - $, fill: silver)
#box($ - &- $, fill: silver)
#box($ a \ - &- $, fill: silver)

However, the height of a MathFragment::Align (inserted by impl LayoutMath for Packed<AlignPointElem>) is supposed to be zero, according to https://github.com/typst/typst/blob/4f8bbb01ce2f333383f7209fe0d83ee847d6eb48/crates/typst/src/math/fragment.rs#L45-L52
Reproduction URL
No response
Operating system
Web app, Linux
Typst version

[X] I am using the latest version of Typst

This is because in MathRun::into_line_frame(), the line's frame height is calculated by adding the line's ascent() and descent(), which are in turn calculated by adding the maximum ascent() and maximum descent() along all MathFragments in this line (MathRun).
In a line with - (a MathFragment::Glyph) only, every fragment has ascent 2.7pt and descent -2.3pt (negative), so the line's height is 2.7pt + (-2.3pt) = 0.4pt. If the line contains a MathFragment::Align, that fragment's ascent and descent are 0pt, so the max ascent of all fragments in this line is still 2.7pt, but the descent of all fragments in this line becomes 0pt (instead of -2.3pt), so the line's height becomes 2.7pt + 0pt = 2.7pt.

I think ascent and descent should be clamped to zero there.

Clamping to zero may lead to unintended results, because a glyph's lowest part could indeed be higher than the baseline. For example, if MathRun::descent() is modified like this
    pub fn descent(&self) -> Abs {
        self.iter()
-           .map(MathFragment::descent)
+           .map(|e| e.descent().max(Abs::zero()))
            .max()
            .unwrap_or_default()

then one of the broken test (math-underover-brackets) shows

More obvious:
$ overbrace(equiv) $

Output: , Reference:

Clamping to zero may lead to unintended results, because a glyph's lowest point could indeed be higher than the baseline, and therefore having a negative descent. For example, if MathRun::descent() is modified like this
    pub fn descent(&self) -> Abs {
        self.iter()
-           .map(MathFragment::descent)
+           .map(|e| e.descent().max(Abs::zero()))
            .max()
            .unwrap_or_default()
    }

then one of the broken test (math-underover-brackets) shows

More obvious:
$ overbrace(equiv) $

Output: , Reference:

Clamping to zero may lead to unintended results, because a glyph's lowest point could indeed be higher than the baseline, and therefore having a negative descent. For example, if MathRun::descent() is modified like this
    pub fn descent(&self) -> Abs {
        self.iter()
-           .map(MathFragment::descent)
+           .map(|e| e.descent().max(Abs::zero()))
            .max()
            .unwrap_or_default()
    }

then one of the broken tests,math-underover-brackets, shows

More obvious: $ overbrace(equiv) $
Output: , Reference:

Instead, I suggest this change below (all tests passing). The idea is that some MathFragments are not real fragments to be layouted, but are in-band control signals to instruct how fragments shall be layouted. Therefore, these fragments are "shapeless"/"sizeless" -- it is not the same as "having a zero size"; the notion of "shape"/"size" itself is absent for these fragments.
diff --git a/crates/typst/src/math/fragment.rs b/crates/typst/src/math/fragment.rs
index ef865b38..596c3c16 100644
--- a/crates/typst/src/math/fragment.rs
+++ b/crates/typst/src/math/fragment.rs
@@ -139,6 +139,10 @@ impl MathFragment {
         }
     }

+    pub fn is_shapeless(&self) -> bool {
+        matches!(self, MathFragment::Align | MathFragment::Linebreak)
+    }
+
     pub fn italics_correction(&self) -> Abs {
         match self {
             Self::Glyph(glyph) => glyph.italics_correction,
diff --git a/crates/typst/src/math/row.rs b/crates/typst/src/math/row.rs
index 6454f491..6577abf5 100644
--- a/crates/typst/src/math/row.rs
+++ b/crates/typst/src/math/row.rs
@@ -117,11 +117,17 @@ impl MathRun {
     }

     pub fn ascent(&self) -> Abs {
-        self.iter().map(MathFragment::ascent).max().unwrap_or_default()
+        self.iter()
+            .filter_map(|e| if e.is_shapeless() { None } else { Some(e.ascent()) })
+            .max()
+            .unwrap_or_default()
     }

     pub fn descent(&self) -> Abs {
-        self.iter().map(MathFragment::descent).max().unwrap_or_default()
+        self.iter()
+            .filter_map(|e| if e.is_shapeless() { None } else { Some(e.descent()) })
+            .max()
+            .unwrap_or_default()
     }


Add "sorted" macro to JSON data types

fixes: #125

Just FYI, I had to install the insta command to review changes made to the snapshots with:
cargo install cargo-insta

Might be nice to mention that somewhere in the documentation eventually.

insta is pretty nice, right? You're right, mentioning that would be good

Thanks for the PR @travishathaway ! Already looks good to me!
I agree about insta, maybe you can create another issue or PR for that?

@travishathaway I think we're happy to merge the PR but holding back since you haven't marked it as ready for review yet. Happy to merge whenever you're ready! :)

Ready to merge 😎


Frontend Deploy Action Script

Set up FE deploy script

If as a team you decided that deployments will be done from the production branch, it would be nice to protect that branch as well (same as main is protected now), otherwise, someone may push to it accidentally from their laptops. @tim-macphail has privileges to configure that
on the other hand, just wanted to let you know that in industry, on large codebases, on highly audited industries, and even on publicly traded companies, some people just deploy to production after merging, without staging branches, just creating PR directly to main/trunk/whatever, many times a day. Some people call it DevOps.
How do you deploy a partial feature? one solution is feature flagging
Whether DevOps or traditional Waterfall is the right choice and the deployment strategy you'll use, please take that decision as a team. I'm happy with whatever you choose

If as a team you decided that deployments will be done from the production branch, it would be nice to protect that branch as well (same as main is protected now), otherwise, someone may push to it accidentally from their laptops. @tim-macphail has privileges to configure that
on the other hand, just wanted to let you know that in industry, on large codebases, on highly audited industries, and even on publicly traded companies, some people just deploy to production after merging, without staging branches, just creating PR directly to main/trunk/whatever, many times a day. Some people call it DevOps.
How do you deploy a partial feature? one solution is feature flagging
Whether DevOps or traditional Waterfall is the right choice and the deployment strategy you'll use, please take that decision as a team. I'm happy with whatever you choose

DevOps is good and I would actually prefer it when it's desired in work. But I wasn't thinking about it for our project at all.
It's good to execute a little more advanced practice, but my biggest concern would be that we aren't as agile, audited nor demanding to the level that makes DevOps a thing and work to bring any benefit to us. I doubt that we should spend carefulness and time to make sure that every pr is 'perfect' to be deploy right away, to be the most responsible to end users.
Feature flag works for both approaches. Traditional generally makes us have fewer to none flags. Why make flags when we can avoid them?
My justification would be that it's not necessary and we could have the same effort practicing it to be used for development and NLP. Traditional is a default, it is suitable for us and easier to everyone's life, when life is already so hard ;)
@tim-macphail make the call here.

@cloudyyoung @kamadorueda Let's go for the traditional method of using a production branch 🙂

@tim-macphail  Please remember to protect the production branch
I already pointed lifeline.techstartucalgary.com to techstartucalgary.github.io using a CNAME, so all you would need to do is deploy the website into the production-build branch, and enable pages in the configuration options to read data from that branch

@tim-macphail  Please remember to protect the production branch
I already pointed lifeline.techstartucalgary.com to techstartucalgary.github.io using a CNAME, so all you would need to do is deploy the website into the production-build branch, and enable pages in the configuration options to read data from that branch

Love that, thank you Kevin!!


Incomplete AlertManager API Documentation

@mxinden
Either I don't know what I am doing or the Alert Manager API is not working as expected.
Your assistance is greatly appreciated.
I am trying to get a list of active alerts using a filter and it does not work as expected.
In all cases, I receive the complete list of active alarms.
Example 1:
curl -X GET http://<IP_ADDRESS>:9093/api/v2/alerts
Here I get the full list of active alerts.
So far so good!
Example 2:
curl -X GET http://<IP_ADDRESS>:9093/api/v2/alerts?name=my_receiver
Here I still get the full list of active alerts.
Example 2:
curl -X GET http://<IP_ADDRESS>:9093/api/v2/alerts?alertname=my_alert.*
Here I still get the full list of active alerts.
Unfortunately the AlertManager API documentation is poor vs Prometheus Server API documentation.
See link below:
https://prometheus.io/docs/alerting/management_api/
Below is the Alert Manager OPEN API spec but I don't know how to use it:
https://github.com/prometheus/alertmanager/blob/master/api/v2/openapi.yaml
/alerts:
get:
tags:
- alert
operationId: getAlerts
description: Get a list of alerts
parameters:
- in: query
name: active
type: boolean
description: Show active alerts
default: true
- in: query
name: silenced
type: boolean
description: Show silenced alerts
default: true
- in: query
name: inhibited
type: boolean
description: Show inhibited alerts
default: true
- in: query
name: unprocessed
type: boolean
description: Show unprocessed alerts
default: true
- name: filter
in: query
description: A list of matchers to filter alerts by
required: false
type: array
collectionFormat: multi
items:
type: string
- name: receiver
in: query
description: A regex matching receivers to filter alerts by
required: false
type: string
Can you provide examples showing how to construct alert queries with filters?

Unfortunately the AlertManager API documentation is poor vs Prometheus Server API documentation. See link below: https://prometheus.io/docs/alerting/management_api/

This only documents the API documentation. Given that you stumbled over it, it might make sense to add a note in there. (PRs are welcome.)

Can you provide examples showing how to construct alert queries with filters?

On the projects readme there is an API section which should give some more insights.
The easiest way to construct your curl commands is probably the interactive swagger ui.
Let me know if this helps. Again, as this is an open source project it heavily depends on contributions, especially in the form of documentation. Thus if you find anything that would have helped you, please file a pull request.

I agree with @mxinden: it would be good to mention the API specification in the official documentation.

@mxinden
Thank you very much for the tip.
Both swagger and amtool work for me.
The only question left is to know the syntax for querying alerts based on the receiver name using amtool.
It works with swagger but it does not work with amtool.
This is what I am using so far:
amtool alert query receiver="receiver-name" --alertmanager.url
The response is an empty list.
Help please :)

I don't have much experience with amtool. In addition as this would be a usage question the mailing list is the best place to ask https://groups.google.com/forum/#!forum/prometheus-users.

if in bash, use | jq to handle output
curl -X GET http://localhost:9093/api/v2/alerts/ | jq '{ alertname: .[].labels.alertname, instance: .[].labels.instance }'

if in bash, use | jq to handle output
curl -X GET http://localhost:9093/api/v2/alerts/ | jq '{ alertname: .[].labels.alertname, instance: .[].labels.instance }'

@mxinden, I see this ticket is still open, hence commenting the API calls I have used for reference:
To GET Active Alerts:
api/v1/alerts/?active=true
To GET Inactive Alerts:
api/v1/alerts/?active=false
To GET filtered Alerts based on a matcher:
api/v1/alerts/?filter=["alertsrc=ElasticSearch"]
To GET all Silences:
To DELETE a Silence:
api/v1/silence/e89f213c-bb20-4786-9f2d-0f102830fca9

does AM support silences filtering only based on match label?What if i want to get only the active silences?
I ran this call ,same as browser does in backend when AM UI is used for filtering the active silences:
curl -X GET http://<IP_ADDRESS>:9093/api/v2/silences?active=true
Unfortunately i get all silences,active and expired

Don't work for me:
curl -X GET http://localhost:9093/api/v1/alerts/?filter=["alertname=my_alert.*"]
In browser: http://example.com:9093/api/v1/alerts?filter=["project=vm"]
{"status":"error","errorType":"bad_data","error":"bad matcher format: ["project=vm"]"}
what am I doing wrong?


Suggestion: Put mod on modrinth

Modrinth is a place for Minecraft mods, like curseforge (also has better UI imo), have you though of putting Architects Palette there

https://modrinth.com/mod/architects-palette


fix: Missing audio on playing a loaded url

Description
A clear and concise description of what the bug is.
Steps To Reproduce

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected Behavior
A clear and concise description of what you expected to happen.
Screenshots

If applicable, add screenshots to help explain your problem.
Additional Context
Add any other context about the problem here.
I am loading a url from firebase(printed in the above screenshot then calling play on the fetched url but there is no sound. Here is the exception.
[ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: 'package:flutter_soloud/src/soloud.dart': Failed assertion: line 579 pos 11: '_activeSounds
E/flutter ( 5630):                   .where((sound) => sound.soundHash == ret.sound!.soundHash)
E/flutter ( 5630):                   .length ==
E/flutter ( 5630):               1': Sound is already loaded but missing from _activeSounds. This is probably a bug in flutter_soloud, please file.

Hi @chotixity,
I never tried to use FireBase with SoLoud.instance.loadUrl(). It would be nice to see some relevant code you used.
That error could occur if the same url is used more than once when calling the above loadUrl within about 10ms. Maybe you called it while FireBase was getting chunks of the mp3 file?

Feel free to reopen if the problem still exists.


Hardware offload to PowerConnect 6200 switch

System Description: Dell Ethernet Switch
System Up Time: 0 days, 11h:33m:16s
System Contact:
System Name: switch01
System Location:
Burned In MAC Address: 0025.642A.C55F
System Object ID: <IP_ADDRESS>.4.1.674.10895.3011
System Model ID: PCT6248
Machine Type: PowerConnect 6248

Expected Behavior

It may be possible to implement this with SNMP, otherwise ssh + tftp might be a good solution
Current Behavior

Is there any support for offload to other switches?  Not certain.
Possible Solution

SNMP
ssh + tftp
Context

I understand that a great deal of the network configuration happens with a software bridge.  I don't want this to be a bottleneck when I have a piece of hardware with a 20+GE backplane
Your Environment

Calico version

$ sudo ~/bin/calicoctl version
Client Version:    v3.17.1
Git commit:        8871aca3
invalid configuration: no configuration has been provided

$ sudo ~/bin/calicoctl node status
Calico process is running.

IPv4 BGP status
+---------------+-------------------+-------+------------+-------------+
| PEER ADDRESS  |     PEER TYPE     | STATE |   SINCE    |    INFO     |
+---------------+-------------------+-------+------------+-------------+
| <IP_ADDRESS> | node-to-node mesh | up    | 2021-02-04 | Established |
| <IP_ADDRESS> | node-to-node mesh | up    | 2021-01-31 | Established |
| <IP_ADDRESS> | node-to-node mesh | up    | 2021-01-31 | Established |
| <IP_ADDRESS> | node-to-node mesh | up    | 2021-01-31 | Established |
| <IP_ADDRESS> | node-to-node mesh | up    | 2021-01-31 | Established |
| <IP_ADDRESS> | node-to-node mesh | up    | 2021-02-01 | Established |
+---------------+-------------------+-------+------------+-------------+

IPv6 BGP status
No IPv6 peers found.

Orchestrator version (e.g. kubernetes, mesos, rkt):

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-13T13:28:09Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-13T13:20:00Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}

Operating System and version:

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.2 LTS
Release:	20.04
Codename:	focal

Link to your project (optional):

https://wp.colliertech.org/cj/?cat=163

Calico route packet to container directly. There is no software bridge involved. So I guess the answer is no? @neiljerram WDYT?

I heard there's experimental VPP work.  Is this true?
On Thu, Feb 25, 2021 at 9:14 AM Song Jiang<EMAIL_ADDRESS>wrote:

Calico route packet to container directly. There is no software bridge
involved. So I guess the answer is no? @neiljerram
https://github.com/neiljerram WDYT?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/projectcalico/calico/issues/4371#issuecomment-786061718,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAM6UTILFJBARA7YFXNS4DTA2AOFANCNFSM4XFS5RYQ
.

I heard there's experimental VPP work.  Is this true?

@cjac Indeed there is: https://github.com/projectcalico/vpp-dataplane
In general our architecture allows user-space dataplane implementations to be plugged in, instead of the kernel / iptables / eBPF implementation, but someone needs to write them.

Calico route packet to container directly. There is no software bridge involved. So I guess the answer is no? @neiljerram WDYT?

Well there is the "swdev" work in the Linux kernel, whose general purpose I believe is to allow kernel networking things to be offloaded to specific switches.  @cjac Do you know if there is any particular "swdev" work for the PowerConnect switch?

Indeed there is: https://github.com/projectcalico/vpp-dataplane

Thank you!  Perhaps I could and should open this issue with that project instead.

Do you know if there is any particular "swdev" work for the PowerConnect switch?

I don't, but I'm curious to find out.


Ambiguous documentation

The reference manual says that relationship style can accept both style dashed and dashed true.
Could you please clarify there the difference and when to use one or the other?

Thanks, this is what I suspected.


docs-bug(mat-tab-group): mat-tab-stretch exists and is not documented anywhere

Documentation Feedback
It would be very useful to have all properties that affect a given component clearly and visibly documented. Today I found out about mat-tab-stretch after hacking away for a while with no success.
Scouring https://material.angular.io/components/tabs/api and related provided no hint of its existence, and was only mentioned on this S.O. thread - https://stackoverflow.com/questions/48839430/make-tab-labels-stretch-to-full-width-in-material-design-for-angular
Affected documentation page: https://material.angular.io/components/tabs/api

It is just an attribute in css with little styles.
We could add MatTabStretch directive and it will be available through API tab.
But I guess it's too much for a 4 lines of scss code.

Closing because there is already an example using mat-tab-stretch.


Captiveportal: missing interface in config?

[23-Mar-2015 14:53:03 Europe/Berlin] PHP Fatal error:  Call to a member function __toString() on null in /usr/local/opnsense/mvc/app/models/OPNsense/CaptivePortal/Rules.php on line 306
via https://forum.opnsense.org/index.php?topic=237.0

Updated code with additional check in  https://github.com/opnsense/core/commit/bc1601085f96544f37ed82c337680cd56d26c48e

Error is gone. Forum issue is not related to CP directly. Will trace this down via another issue.


home_sidebar does not work properly

Hello,
Thanks for building the nbdev!
The sidebar (navigation on the left side of the page) looks fine at the Overview (https://fastai.github.io/deck_of_cards/), but when I click on either Card or Deck (https://fastai.github.io/deck_of_cards/deck.html) the sidebar is minimized. It is not a big issue if there are only 1 or 2 items in the sidebar, but it would be inconvenient if there are 5-10 items.
Note that the sidebar works perfectly on the nbdev document page.
https://nbdev.fast.ai/
https://nbdev.fast.ai/sync.html
If possible, please config the nbdev_template so that the sidebar is properly displayed.
Thanks.

Should be fixed in v2

Thanks a lot, Jeremy, for the heads up. I look forward to trying nbdev v2 when it is officially released!


fixing actionlib BUG in Ubuntu 20

This fixes the BUG on Ubuntu 20:
[ERROR] [1626285660.006720060, 10.360000000] : (ros.Astrobee.actionlib) BUG: Got a transition to CommState [ACTIVE] when in SimpleGoalState [DONE]
[ WARN] [1626285661.000143376, 11.360000000] : (ros.Astrobee) Freeflyer action timed out on going active.
[ERROR] [1626285663.010712617, 13.368000000] : (ros.Astrobee.actionlib) BUG: Got a second transition to DONE
I tested the perching, cargo transport and reacquire position commands
The delay ended up being 0.1, same as poll, so I don't think it will influence the overall performance.
Let me know if there's anything we can improve to make this fix 'cleaner'

Sorry to be so picky... can you mention in the comment that it only shows up in ubuntu 20 / ros whatever?

@bcoltin Is it ok now?

Perfect thanks!


bats-file npm package removed by security team

According to https://www.npmjs.com/package/bats-file:

Security holding package
This package contained malicious code and was removed from the registry by the npm security team. A placeholder was published to ensure users are not affected in the future.
Please refer to www.npmjs.com/advisories?search=bats-file for more information.

Clicking the link goes to github advisories, but nothing is listed there for bats-file.
Do you have any context on this?

Thanks for the report. This is the first time I hear about that. We will have to inquire with npm to geht more details. I See following potential reasons:

The code is too old
The code triggered eine false positive in automated security Scans
We actually have some backdoors in the package, either due to an oversight or due to a breach like https://thehackernews.com/2021/09/travis-ci-flaw-exposes-secrets-of.html

Anyway we will have to investigate.

The description text mentioned above is gone now.

I did not yet hear back from the npm team.
However, internal discussion showed that we never published a bats-file package. This means the package you linked to was published by a third party.
Unfortunately, this means we don't know what was in that package.

bats-file (this repo) was forked from a long-time bats community member's bats-file.
The original repo contained a package.json that was initially used primarily as a means to simplify the installation of sibling bats projects for testing. I don't believe the package.json was ever used as a means of publishing bats-file itself. This is demonstrated by it being configured as private: true; which prevents publishing. It has remained private for as long as our fork has existed. The package published on npm is not by the bats-core org nor published by any member of the `bats-core org](https://www.npmjs.com/org/bats-core).

I see the issue is still open and no final resolution posted.
Are there plans to adding bats-file as a bats-core org provided npm package?
In that sense, as far as I can see when looking to bats-support and bats-assert, these packages are also only owned by a bats-core member @jasonkarns but not the org itself.
Are there plans to change this situation in the future so that everyone is able to use npm install bats-file as an officially supported package owned by bats-org?

There has been internal discussion about this topic but there is no final decision or timeline, yet.

@martin-schulze-vireso please include me in the internal discussion about this, I have a natural interest on "packaging" tasks and I have experience with most of the different distros and language-related package. :)
I also recently joined the chat, will ping you there :wave:

I am not sure which chat you are talking about exactly. We are still evaluating where to bundle internal communication.
With regard to this issue: the current idea is to provide official npm packages under the bats scope to prevent a vacuum that can be filled by nefarious actors.


Prime Factor [CPP]

This issue is about Prime Factor.

[x] Issue Title is in form Prime Factor [CPP].
[x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
[x] This Algo/DS is worth adding to this repository.
[x] Assign this issue to me (I want to work on this).

[x] I ensure that I am not already assigned to 2 or more issues.

[x] I will send my PR only after I'm assigned to this issue by any maintainer.
[x] I understand that I will be unassigned from this issue if I fail to send a PR for this within a week.

@iiitv/algo-maintainers is this up for grab? then please provide me


Stats: improve JSON support, add missing structs

Hi there! We are delighted to have the opportunity to utilize pion's webrtc-stats implementation for unmarshalling JSON stats at our backend. I have put in some effort to make it feasible and would love to contribute it.
Description:

Fix json marshalling of stats containing enums
Add UnmarshalStatsJSON helper
Add marshalling/unmarshalling tests
Add missing AudioSourceStats, VideoSourceStats, AudioPlayoutStats defined in https://www.w3.org/TR/webrtc-stats
Deprecate ICECandidateStats' NetworkType, use plain string instead of enum which does not suite the definition: https://www.w3.org/TR/2018/WD-webrtc-stats-20180627/#rtcnetworktype-enum

Amazing feature. We really need this

This looks great @aalekseevx lets get it merged!
I will review tonight. If you don’t hear from me please ping here and on https://pion.ly/slack
Lots of stuff going on sometimes get pulled away :/

@Sean-Der, hi! I made some fixes for CI checks, do you have some time to complete the review now?

Any updates?

Fantastic work @aalekseevx! sorry I didn't get a chance to review sooner

Can we drop the dependency? Outside of tests we have 0 3rd party dependencies, would be nice to keep that :)

Can you move the testdata into the files that use them? I don't feel strongly either way, I just would like to follow the established pattern.

Thank you so much for doing this work. It is a very important contribution. Sorry I did't respond sooner, personal life has just kept me busy. thank you!

@aalekseevx nope you did a great job! I will merge and tag today.
thank you for pinging me. This is super important contribution. Sorry I have been distracted with OBS dev.

Merged and tagged with v3.2.15 thank you @aalekseevx !


Update examples and docs for subscribing to configuration stores

Description
Doc changes and add examples to subscribe to config stores
Issue reference
Please reference the issue this PR will close: #465
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[ ] Created/updated tests
[X] Extended the documentation

approved!


admin: gebouwen

### Functionality
- [ ] New button and Edit button send the user to the 'edit data' screen and starts adding (new) building there.
- [ ] Filter and sort buttons open a small menu to select the kind of filter/sorting method.
- [ ] An active button, filter or searchbar has a lightblue background and darkblue text.
- [ ] Photos scroll horizontally
- [ ] Right mouse button on photo/comment will open a menu with delete and edit option.
- [x] Google maps view must have an enlarge button
- [ ] Manual view must have an enlarge button
- [ ] 'Stuur bericht' sends the user to the 'berichten' screen
- [ ] 'Deze week' opens calendar menu to select week. (Notes and photos depend on the week.)

Update: an extra card with the planning for the week should be added. Wait until the component from the add data is finished. You can copy paste that one or abstract it into a component.


PVC resource should not be created by default

When a new component is created, then a PVC is automatically added to the project/namespace.
odo create openjdk18 sb1 --binary ./target/ocp-fmp-build-install-1.0-exec.jar
Please wait, creating sb1 component ...
...
oc get pvc
NAME          STATUS    VOLUME    CAPACITY   ACCESS MODES   STORAGECLASS   AGE
sb1-s2idata   Bound     pv0044    100Gi      RWO,ROX,RWX                   22m

I propose that such pvc creation should be optional and defined using a parameter

Closing this one.

We really need some kind of persistent storage to store source code. No way around that.
No volume is used for git components.
created https://github.com/openshift/odo/issues/1793 to add "refereneOwner"


NFC: Cleanup ConcretizeTileAmongstWorkgroupsPass.

The refactoring silos everything required for removing unit-trip loop
counts under a flag with future changes trying to use the affine min
canonicalization without removing the loop itself. Goal is to verify
performance overhead that keeping the unit loop around adds.
Lot of the complication in this pass was introduced to get the types
of the outputs and inputs in this pass and propogating that
information to the launch configuration computation. Instead use of
the ViewOpInterface allows the operation itself to get the types of
the untiled operands using a simple traversal. Cleans up the pass
quite a bit.
Also cleanup some of the command line options handling in
configuration computation, i.e. override the default configuration
picked using the tiles sizes/workgroup sizes specified on command
line.
Fixes #5311

This is the follow up PR based out of PR #5283 . Only the last commit here is relevant. I am happy to fold this into that PR, but I felt reviewing them separately might be easier.
(Keeping this a draft since I have some compilations errors because of mostly unrelated change to the generic op configuration setting. Fixing that but this is ready to review).

Cool, thanks! I forgot about the ViewLikeOpInterface trick!