text:
Prevents an exchange rate of 0 or below

Issue/Task Number: T454
Overview
This PR prevents creating or updating an exchange pair with a rate of zero or below.
Changes

Update ExchangePair's changeset to validate for a rate greater than 0
Added tests for the controllers

Implementation Details
Straightforward use of Ecto.Changeset.validate_number/3
Usage
Try /exchange_pair.create or /exchange_pair.update with rate of 0 or below. They should return invalid_parameter error with the description explaining the validation error.
Impact
Code changes only. No changes to the DB schema or API request/response format.

@unnawut Could you also check and prevent an exchange from happening that would result in one of the amount being lower than the lowest integer (including subunit_to_unit)?
So if I send from_amount=null, to_amount=1 (as in 0.01 with subunit_to_unit=2) and rate between the tokens=2, from_amount should not be 0.5 and I should get an error instead?

@T-Dnzt Please check again

authors: T-Dnzt unnawut

repo: omisego/ewallet


text:
Refactor transaction validation into a single method

Closes #38
This is a relatively small change - pulls out each individual validation into one method that throws if the transaction is invalid. All tests pass.
Note:
Makes a small change to setup.py to fix ImportError: cannot import name 'force_text' as per #40. Unable to run py.test otherwise.

LGTM

source: gharchive/pull-request

authors: DavidKnott kfichter

repo: omisego/plasma-mvp

license: MIT

license_type: permissive

license_source: github-api


text:
WIP: OpenMM 6.3

I would prefer to get this right the first time, so no merge yet.

+1.  When will these be posted?  After this gets merged, or shortly thereafter?

This works for Linux and OSX, so it can probably be merged. Still needs some work for Win-64 I think, but we can do that later.

Thanks!  I'm still debugging some issues with Jenkins failing all of a sudden, so give me a few more min before we merge.

See #270

OK, I think we're sorted now.

Merging #269 first just to double-check everything works as intended.

Any chance you could retrigger the appveyor build for this PR?  I wonder if #271 fixed your issues.

authors: jchodera rmcgibbo swails

repo: omnia-md/conda-recipes

license: mit

license_source: bigquery


text:
Developer provider not working under Rails 7.0.2.3

Please complete all sections.
Configuration

Provider Gem: omniauth-2.0.4
Ruby Version: 2.7.5
Framework: rails 7.0.2.3
Platform: ubuntu

Expected Behavior
Gemfile
gem 'omniauth'
gem "omniauth-rails_csrf_protection"

config/initializers/omniauth.rb
Rails.application.config.middleware.use OmniAuth::Builder do
  provider :developer
end

app/views/sessions/new.html.erb
<%= form_tag('/auth/developer', method: 'post') do %>
  <button type='submit'>Login with Developer</button>
<% end %>

Clicking on Login should render the developer form and log you in using fake credentials.
Actual Behavior
The only thing in the log is:
Started POST "/auth/developer" for 127.0.0.1 at 2022-03-21 21:58:57 +0100
D, [2022-03-21T21:58:57.950088 #3941647] DEBUG -- : (developer) Request phase initiated.

So the middleware is hit, but there is nothing after this.
Steps to Reproduce
gem install rails --version 7.0.2.3
rails new --css bootstrap
Add the code in expected behaviour.
bundle install
rails s
click Login

I also am unable to get omniauth-keycloak to work in Rails 7, so that is probably related to omniauth having some issues with rails 7. My gut feeling is that it might be something to do with middleware handling, but I cannot put my finger on the root cause atm.

I think this might be the new turbo links being strange. Changed the view to:
<%= form_tag('/auth/developer', method: 'post', data: {turbo: false}) do %>
  <button type='submit'>Login with Developer</button>
<% end %>

Then that seems to work.

@barttenbrinke glad you got it working, would you mind making a PR to the readme calling out this, and/or add to the wiki?

@BobbyMcWho The Readme is sort of lacking some valuable info :) I will look into it tomorrow.

@BobbyMcWho The PR is here ^^.

I have an issue with the code proposed in the readme in a vanilla rails 7 app
https://github.com/omniauth/omniauth#rails-without-devise
I hit http://0.0.0.0:3000/auth/developer and this is the form:
<%= form_tag('/auth/developer', method: 'post', data: { turbo: false }) do %>
  <button type='submit'>Login with Developer</button>
<% end %>

I submit but:
DEBUG -- omniauth: (developer) Callback phase initiated.
ActionController::RoutingError (No route matches [POST] "/auth/developer/callback"):

for some reason omniauth callback calls the callback in POST, in the routes we have defined a get.
even if I switch to POST I get csrf issues.

I proposed some further changes in the linked PR above, also putting back a skip_before_action that was there before the rewrite

I'd just like to add that you don't have to use a form_tag, you can just use a button_to:
<%= button_to "Sign in with Github", "/auth/github", data: { turbo: false } %>

I proposed some further changes in the linked PR above, also putting back a skip_before_action that was there before the rewrite

The skip_before_action is no longer needed with the gem "omniauth-rails_csrf_protection" gem.

I'm also getting the same errors with the developer provider.
Looking at the source: https://github.com/omniauth/omniauth/blob/master/lib/omniauth/strategies/developer.rb#L38
The developer provider clearly creates a form that sends a POST request to the callback URL, without a CSRF token. How should this work without also allowing POST requests and disabling CSRF protection for create?

gem "omniauth-rails_csrf_protection" should take care of that.

Following the steps in the README, I am also running into this issue with the :developer provider.
The csrf_proctection gem only handles validation of tokens, but the developer form does not have an authenticity token anywhere...
My current solution is to do what other's have suggested, which is to skip verification on the /callback  route, but only in development.
The OmniAuth developer form should probably include some authenticity token, though I'll be honest, I'm not immediately sure how to best do this... I'm not versed enough in the Rails internals to be able to generate an authenticity_token from within the omniauth middleware setup.
I was exploring playing with a monkey patch, and it's not hard to find a spot to inject a new hidden field into the form. (This could be an option passed to the provider function. But I didn't have the time to figure out how to actually generate a token rails would accept.
class OmniAuth::Strategies::Developer
  def request_phase
    token = '.....SOMETHING....'
    form = OmniAuth::Form.new(:title => 'User Info', url: '/auth/developer/callback')
    options.fields.each do |field|
      form.text_field field.to_s.capitalize.tr('_', ' '), field.to_s
    end
    form.html("\n<input type='hidden' name='authenticity_token' value='#{token}' />")
    form.button 'Sign In'
    form.to_response
  end
end

Having the same issue. That would be great if it gets patched soon. @cycomachead thanks for the PR

Thank you @cycomachead for the patch!

source: gharchive/issue

authors: BobbyMcWho abartov barttenbrinke cycomachead dutow masterkain spryffee yshmarov

repo: omniauth/omniauth


text:
you should add sensitive true to the file_create call

Right now you print out the certs by default and this could dangerous if you are retrieving certs from a data bag.
https://github.com/onddo/ssl_certificate-cookbook/blob/master/libraries/provider_ssl_certificate.rb#L56

@jchauncey, thanks for reporting. Fixed in master.

Released in 1.5.0.

authors: jchauncey zuazo


text:
updating links to repo and gh-pages

updating links to repo and gh-pages after migration to new org

No changes to the license shield required?

No changes to the license shield required?

thanks. Also updated across couple other places

make test

Look at the last few lines of the file below, link to gh-pages also goes through redirect. I think
https://raw.githubusercontent.com/napetrov/daal/dev/napetrov-badge/FAQ.md

Yes, but i really don't want to touch FAQ file now. it have lot of not relevant content and i think that we should go ahead and remove it.  Is this ok for you?

The instructions for cloning the repo require an update:
https://github.com/napetrov/daal/blob/dev/napetrov-badge/docs/README.md

Yes, but i really don't want to touch FAQ file now. it have lot of not relevant content and i think that we should go ahead and remove it. Is this ok for you?

Not sure about removing it, but not updating is OK with me

authors: napetrov outoftardis

repo: oneapi-src/oneDAL


text:
Update names of parameter for SVM

Renamed next params:
k->scale
b->shift
coefficients->coeffs

/intelci: run

@rlnx , @michael-smirnov please, review this changes

I will merge with master, after review or approve.

/intelci: run

/intelci: run


text:
slicing within the same element yields incorrect results

These fail for small slices:
import bitarray
var ba = create_bitarray(64)
ba[0] = true
ba[1] = true
ba[2] = true
ba[7] = true
assert ba[0..4] == 7
assert ba[2..4] == 1

@JorySchossau – obviously haven't been using that functionality... so many thanks for the catch and fix! Do you want to submit a PR? In testing your code out here I have one together, but please open and happy to merge from you if you'd prefer.
Otherwise, I'll merge in my new PR (#4) in a day or so and bump the version release. Thanks again!

Hi Nick,
This is my first github contribution, so I'm figuring this out. Thanks for
giving me the opportunity to finish the PR!

Jory

On Thu, Feb 25, 2016 at 1:32 PM, Nick Greenfield notifications@github.com
wrote:

@JorySchossau https://github.com/JorySchossau – obviously haven't been
using that functionality... so many thanks for the catch and fix! Do you
want to submit a PR? In testing your code out here I have one together, but
please open and happy to merge from you if you'd prefer.
Otherwise, I'll merge in my new PR (#4
https://github.com/onecodex/nim-bitarray/pull/4) in a day or so and
bump the version release. Thanks again!
—
Reply to this email directly or view it on GitHub
https://github.com/onecodex/nim-bitarray/issues/3#issuecomment-188893469
.

No problem! Thanks for flagging this.

authors: JorySchossau boydgreenfield

repo: onecodex/nim-bitarray


text:
Download image from Post request

Hello sir, in my SwiftUI app i am storing images to IPFS Data Store and they have recently made the url as a POST request from GET request. In that case the third party library is not able to render the image. How can i resolve this?
This is the example url i am trying to render
https://ipfs.infura.io:5001/api/v0/cat?arg=QmVHLDEY4DhzJeW7G47QgpdibU6QX8g8He6CS83qRbpcDB

Maybe try the request modifier. Something like this:
KF.url(url)
  .requestModifier { $0.httpMethod = "POST" }
  .set(to: imageView)

For more information, you can check the related wiki.

Oh, for SwiftUI app, use the KFImage instead of KF, and there is also a same .requestModifier modifier.

Oh, for SwiftUI app, use the KFImage instead of KF, and there is also a same .requestModifier modifier.

yeah let me try

.set(to: imageView)

not working

.set(to: imageView)

not working

not able to use .set and i am using SwiftUI

can you give me an swift ui example @onevcat

For SwiftUI, just change to KFImage:
KFImage.url(url)
  .requestModifier { $0.httpMethod = "POST" }

repo: onevcat/Kingfisher


text:
When calling UIImageVIew.kf.setImage multiple times on the same UIImageVIew, completion blocks aren't cancelled properly.

Check List
Thanks for considering to open an issue. Before you submit your issue, please confirm these boxes are checked.

[X] I have read the wiki page and cheat sheet, but there is no information I need.
[X] I have searched in existing issues, but did not find a same one.
[X] I want to report a problem instead of asking a question. It'd better to use kingfisher tag in Stack Overflow to ask a question.

Issue Description
What
When calling UIImageVIew.kf.setImage multiple times on the same UIImageVIew after the first call, I'm expecting that all completion blocks, that didn't return before next call, are canceled.
But all completion blocks are called. And the four parameters (image, error, cacheType, url) in the completion blocks don't provide enough info to tell if this UIImageVIew.kf.setImage was canceled by a consecutive call or not.
Reproduce
In the screenshot, I called imageView.kf.setImage twice, I were expecting the first completion block is canceled (not called), but it's called.
PS: the two pictures are cached in disk

In the current implementation, the downloading for the first image will not canceled automatically for you when a new one started. You could either:

Call cancel on the returned task before setting another image to get an error
let task = imageView.kf.setImage(with: url1)
task.cacnel()
_ = imageView.kf.setImage(with: url2)

Or, compare the webURL to imageURL in the callback to see whether it is the current set one:
imageView.kf.setImage(with: url ) {_, _, _, imageURL in
    if imageView.kf.webURL == imageURL {
        // Second set
    }
}

@onevcat
Thanks for the response.
The method 1 doesn't work all the time. In the case that url1 is already cached in disk, there won't be an error passed in the completion. (see screenshot)
While the method 2 totally works!

authors: ShaneQi onevcat


text:
vagrant fails

vagrant build fails due to missing tzdata=2014j-0wheezy1 dependency
==> default: Error: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install tzdata=2014j-0wheezy1' returned 100: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: E: Version '2014j-0wheezy1' for 'tzdata' was not found
==> default:
==> default: Error: /Stage[main]/Main/Package[tzdata]/ensure: change from 2015f-0+deb7u1 to 2014j-0wheezy1 failed: Could not update: Execution of '/usr/bin/apt-get -q -y -o DPkg::Options::=--force-confold --force-yes install tzdata=2014j-0wheezy1' returned 100: Reading package lists...
==> default: Building dependency tree...
==> default: Reading state information...
==> default: E: Version '2014j-0wheezy1' for 'tzdata' was not found
==> default:
==> default: Notice: /Stage[main]/Elasticsearch/Anchor[elasticsearch::end]: Dependency Package[tzdata] has failures: true
==> default: Warning: /Stage[main]/Elasticsearch/Anchor[elasticsearch::end]: Skipping because of failed dependencies
==> default: Notice: /Stage[main]/Elasticsearch/Anchor[elasticsearch::begin]: Dependency Package[tzdata] has failures: true
==> default: Warning: /Stage[main]/Elasticsearch/Anchor[elasticsearch::begin]: Skipping because of failed dependencies
==> default: Notice: /Stage[main]/Elasticsearch::Java/Package[openjdk-7-jre-headless]: Dependency Package[tzdata] has failures: true
==> default: Warning: /Stage[main]/Elasticsearch::Java/Package[openjdk-7-jre-headless]: Skipping because of failed dependencies

and so on ..

Going to fix this by migrating to ubuntu

No longer occurring with ubuntu:
https://github.com/ongr-io/ongr-sandbox/blob/master/src/ONGR/DemoBundle/Resources/doc/index.rst
https://github.com/ongr-io/testing-vm

authors: ddpkts kazgurs

repo: ongr-io/ongr-sandbox


text:
4月分

全172本、新規83本

[x] N4974 Wroclaw meeting information
[x] N4975 2024 WG21 admin telecon meetings
[x] N4976 WG21 agenda: 18-23 March 2024, Tokyo, Japan
[x] N4978 WG21 2024-03 Admin telecon minutes
[x] N4979 Hagenberg Meeting Invitation and Information
[x] N4980 WG21 2024-03 Tokyo Minutes of Meeting
[x] N4981 Working Draft, Programming Languages -- C++
[x] N4982 Editors' Report, Programming Languages -- C++
[x] 🎈 P0562R2 Trailing Commas in Base-clauses and Ctor-initializers
[x] 🎈 P1317R1 Remove return type deduction in std::apply
[x] 🏋 P2135R1 P2055R1: A Relaxed Guide to memory_order_relaxed
[x] P2127R0 Making C++ Software Allocator Aware
[x] P2993R0 Constrained Numbers
[x] P3049R0 node-handles for lists
[x] 🏋 P3064R0 How to Avoid OOTA Without Really Trying
[x] P3097R0 Contracts for C++: Support for virtual functions
[x] P3119R0 Tokyo Technical Fixes to Contracts
[x] P3159R0 C++ Range Adaptors and Parallel Algorithms
[x] P3161R1 Unified integer overflow arithmetic
[x] P3162R0 LEWG [[nodiscard]] policy
[x] P3164R0 Improving diagnostics for sender expressions
[x] P3165R0 Contracts on virtual functions for the Contracts MVP
[x] 🏋 P3166R0 Static Exception Specifications
[x] P3167R0 Attributes for the result name in a postcondition assertion
[x] P3168R1 Give std::optional Range Support
[x] P3169R0 Inherited contracts
[x] P3170R0 sinkable exception error message
[x] P3171R0 Adding functionality to placeholder types
[x] P3172R0 Using this in constructor preconditions
[x] P3173R0 P2900R6 may be minimimal, but it is not viable
[x] 🎈 P3174R0 SG16: Unicode meeting summaries 2023-10-11 through 2024-02-21
[x] P3175R0 Reconsidering the std::execution::on algorithm
[x] P3176R0 The Oxford variadic comma
[x] P3177R0 const prvalues in the conditional operator
[x] P3179R0 C++ parallel range algorithms
[x] 🎈 P3180R0 C++ Standard Library Ready Issues to be moved in Tokyo, Mar. 2024
[x] P3181R0 Atomic stores and object lifetimes
[x] P3182R0 Add pop_value methods to container adaptors
[x] P3183R0 Contract testing support
[x] P3187R1 remove ensure_started and start_detached from P2300
[x] P3188R0 Proxy: A Pointer-Semantics-Based Polymorphism Library - Presentation slides for P3086R1
[x] 🎈 P3189R0 Slides for LEWG presentation of P2900R6: Contracts for C++
[x] 🎈 P3190R0 Slides for EWG presentation of D2900R7: Contracts for C++
[x] P3191R0 Feedback on the scalability of contract violation handlers in P2900
[x] 🎈 P3192R0 LEWGI/SG18 Presentation of P3104R1 Bit Permutations
[x] 🎈 P3194R0 LEWGI/SG18 Presentation of P3105R1 constexpr std::uncaught_exceptions()
[x] 🎈 P3196R0 Core Language Working Group "ready" Issues for the March, 2024 meeting
[x] P3197R0 A response to the Tokyo EWG polls on the Contracts MVP (P2900R6)
[x] P3198R0 A takeaway from the Tokyo LEWG meeting on Contracts MVP
[x] P3199R0 Choices for make_optional and value()
[x] P3201R1 LEWG [[nodiscard]] policy
[x] P3203R0 Implementation defined coroutine extensions
[x] P3205R0 Throwing from a noexcept function should be a contract violation.
[x] P3207R0 More & like
[x] P3208R0 import std; and stream macros
[x] P3210R0 A Postcondition is a Pattern Match
[x] P3211R0 views::transform_join
[x] 🎈 P3213R0 2024-04 Library Evolution Polls
[x] 🎈 P3215R0 Slides: Thread Attributes as Designators (P3072R2 presentation)
[x] P3216R0 views::slice
[x] P3217R0 Adjoints to "Enabling list-initialization for algorithms": find_last
[x] P3218R0 const references to constexpr variables
[x] P3220R0 views::delimit
[x] P3221R0 Disable pointers to contracted functions
[x] P3222R0 Fix C++26 by adding transposed special cases for P2642 layouts
[x] P3223R0 Making std::basic_istream::ignore less surprising
[x] 🎈 P3224R0 Slides for P3087 - Make direct-initialization for enumeration types at least as permissive as direct
[x] 🎈 P3225R0 Slides for P3140 std::int_least128_t
[x] P3226R0 Contracts for C++: Naming the "Louis semantic"
[x] P3228R0 Contracts for C++: Revisiting contract check elision and duplication
[x] P3230R0 views::(take|drop)_exactly
[x] P3232R0 User-defined erroneous behaviour
[x] P3233R0 Issues with P2786 (Trivial Relocatability For C++26)
[x] P3234R0 Utility to check if a pointer is in a given range
[x] P3236R0 Please reject P2786 and adopt P1144
[x] P3237R0 Matrix Representation of Contract Semantics
[x] 🎈 P3240R0 Slides for EWGI presentation on allocators, Tokyo 2024
[x] 🎈 P3241R0 Slides for LEWG presentation on trivial relocation, April 2024
[x] P3242R0 Copy and fill for mdspan
[x] P3243R0 Give std::optional Range Support - Presentation, Tokyo 2024
[x] P3244R0 [[nodiscard]] Policy - Presentation, Tokyo 2024
[x] P3245R0 Allow [[nodiscard]] in type alias declarations
[x] P3247R0 Deprecate the notion of trivial types

手伝ってくださる場合

上のリストから終わっていないのを選んで解説をお願いします

私は基本的に上から順番に1日1〜2くらいのペースでやっていくと思います

選んだ提案はコメントによって宣言しておいてください
書く先はこのリポジトリのhttps://github.com/onihusube/blog/blob/master/2024/wg21_paper_202404.md を更新してPRにしてください

あるいは、ご自分のブログやQiita/zenn等に書いて、そのリンクを貼るという形式でもokです

期限は私が上のリストを全部埋めるまでの間です（たぶん2ヶ月くらい？

末尾の 5 つから書いていきます。

P3242R0 Copy and fill for mdspan
P3243R0 Give std::optional Range Support - Presentation, Tokyo 2024
P3244R0 [[nodiscard]] Policy - Presentation, Tokyo 2024
P3245R0 Allow [[nodiscard]] in type alias declarations
P3247R0 Deprecate the notion of trivial types

完了しました、ご協力ありがとうございました！！

authors: Reputeless onihusube

repo: onihusube/blog


text:
Infinite "Processing" State for Invalid URLs

Handling #12
This pull request introduces several enhancements and features to the Paste Viewer component, aimed at improving user experience and functionality.
Changes Made:
Error Handling:
Added comprehensive error handling when fetching paste data from the API. If the paste ID is invalid or non-existent, a user-friendly error message is displayed.
The error message prompts users to check the URL and informs them that the paste may have expired or been removed.

For invalid URL it is showing properly

But for valid url the paste is not loading / it is showing blank

Instead it should show something like this


text:
Feature/from image

Updated FROM in docker image for new naming convention, fixed bootstrap.sh so it would actually complete successfully.

This is the image that is missing the giant tarball of php versions required for
things to work. We need to solve that problem before we can merge this and mark
everything as done.

I'm closing this PR for now as there are other issues in the image to take care of first.

authors: chosenken fiveisprime

repo: onmodulus/docker-run-php


text:
Support for recurrent_v2 layers for TF 2.0

In #607, it was observed that TensorFlow versions before 2.0 can have problems converting TF 2.0 compatible models because the classes are expected to be the previous API. For example in TF 1.14 the v2 compatible classes are present in tensorflow.keras.layers.recurrent_v2, but do not match tensorflow.keras.layers. This PR resolves #607 by adding support for these layers. For versions of TensorFlow that are above 2.0, this is not a problem because tensorflow.keras.layers uses the v2 layers.
This strategy is tested by expanding the RNN_CLASSES list in the tests, so that recurrent_v2 classes are tested if present.

@wenbingl, it looks like the linux-conda-ci build is still waiting to start. Any ideas on how to resolve it?

/azp run linux-conda-ci

@wenbingl, it looks like the linux-conda-ci build is still waiting to start. Any ideas on how to resolve it?

this is the recent random failure of azp, we don't have a good way to fix it.
And recently, ONNX sig add a DCO requirement which you needs sign your commit. After you sign the commit, I can try to manually run the checker and forcedly merge it if the azp issue still exists.

Ok, got it. I re-committed and force-pushed the change since it was buried under a few merges.

This PR fails on linux-tf-keras CI build for tensorflow==1.15.0. The fix is here.

authors: cjermain jiafatom wenbingl

repo: onnx/keras-onnx


text:
DequantLinear Operator output is fp32 or fp16?

I have a question about the onnx-mlir tool.In the onnx model, the input is defined as int8 data type and the output is defined as fp16 data type. However, after converting the onnx model to mlir using onnx-mlir, the output of the DequantizeLinear operator becomes fp32 data type. Is the DequantizeLinear operator in onnx-mlir by default only supporting fp32 output? How can I make sure the output type matches the original onnx model?

It looks like fp16 is supported since DequantizeLinear opset 19, while onnx-mlir still supports opset 13 in which the output is fp32: https://onnx.ai/onnx/operators/onnx__DequantizeLinear.html
In summary, yes, onnx-mlir is now supporting fp32 only.

ok，thanks very much.
When will the DequantizeLinear operator's opset19 be supported, approximately?

We don't have a concrete plan for this and totally depend on contribution from community. We really appreciate it if you could contribute to this support.

@lingHu-123 - one option is to write your own pass to handle this operator and apply suitable conversion; but that is exactly what @tungld is requesting be upstreamed to this repo. Its a who-will-bell-the-cat ?

So seems like the ops definition itself is correct https://github.com/onnx/onnx-mlir/blob/main/src/Dialect/ONNX/ONNXOps.td.inc for DequantizeLinear; somewhere the builder is causing the problem of deciding the type.
@lingHu-123 - can you share your source MLIR file that is causing the problem ?

authors: arcturusannamalai lingHu-123 tungld

repo: onnx/onnx-mlir


text:
setScheduledCharging format

I am not sure how to send a message to the setScheduledCharging. I am sending this via a function:
// msg.command = 'setScheduledCharging';
msg.commandArgs = {
enable: 1,
time: "2 AM"
};
return msg;
It does seem to kind of work, but no matter what I send, in the app it changes it to 00:00. I tried different time formats (02:00, 2:00AM, 02:00 AM etc.), but same result. Any ideas what I am doing wrong? Also tried enable: true, didnt work either. Thanks in advance!

If I remember well, time is numeric (minutes since midnight local time)
Le mer. 5 juil. 2023 à 21:22, Ivaylo Hitsov @.***> a
écrit :

I am not sure how to send a message to the setScheduledCharging. I am
sending this via a function:
// msg.command = 'setScheduledCharging';
msg.commandArgs = {
enable: 1,
time: "2 AM"
};
return msg;
It does seem to kind of work, but no matter what I send, in the app it
changes it to 00:00. I tried different time formats (02:00, 2:00AM, 02:00
AM etc.), but same result. Any ideas what I am doing wrong? Thanks in
advance!
—
Reply to this email directly, view it on GitHub
https://github.com/onokje/node-red-contrib-tesla/issues/65, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADUNWNNJBMU4KXH2XWIPDCLXOW5IBANCNFSM6AAAAAAZ7L7VEE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you, this works!

'enable' should also be a boolean

authors: GaPhi ihitsov

repo: onokje/node-red-contrib-tesla


text:
Add option to show only text (no symbols)

I use neovim on multiple OSes and multiple PCs and I don't feel inclined to download and install a font on every machine. This means that all the symbols are usually broken.
I would suggest adding a text_only option rather than having a configuration that sets all the symbol_map fields to an empty string ""
Configuration would look like this:
-- nvim-cmp setting:
    formatting = {
        format = lspkind.cmp_format({
            text_only = true,
            menu = ({
                buffer = "[buff]",
                nvim_lsp = "[lsp]",
                luasnip = "[snip]",
                path = "[path]"
            })
        })
    }

-- default lsp config

require('lspkind').init({
    text_only = false,
    -- [... snip other config stuff ...]
})

Note that when text_only is set it would override the with_text setting since we can't have with_text = false when showing only text.
The popup would look like this:

You can find a working example in this fork.

What if we introduce a mode option with possible values text, text_symbol, symbol_text, symbol? related to #28

@onsails I think its a good idea. Do we remove with_text and add the mode option or leave it for backwards compatibility?

I'd leave this option with a deprecation error notice.

fixed in #35

authors: mattrobineau onsails

repo: onsails/lspkind-nvim


text:
The log crate can't be search but can be browsed through url

[bug] Search with keyword log and can't find crate log,
but can browse it through https://docs.rs/log.

See #111. Unfortunately docs.rs search doesn't work as expected and needs a bit work.

Same for hyper

authors: onur polachok xusss


text:
Update cargo to latest revision

I believe this patch is ready, but needs to be properly tested.
Fixes: #65

I don't know if it's the news you want to get, but no new releases have been rendered since this was merged.

Yes @bluss, this update also fixed #46.
docs.rs is building missing google-* crates right now and its taking a while.

Aha, so we are stuck in the backlog, that's fine. Would it be an idea to mark crates as being equivalent in all arches? It seems like a waste and I'd do it if it leads to faster publishing. I mean, it's a very useful thing when it matters, but often it doesn't.

I am not sure if it is possible to detect arch-specific documentation differences before building a crate.

authors: bluss onur


text:
Bad Authentication

Hi, I have struggled on this question for a long time. I downloaded the whole project and use ./gradlew -Pversion=4.x.y-DEV createExe to generate the jar file. However, when I try to log in with my correct google account, it kept returning Bad Authentication.  I can use the exact same google account to log in the prebuild binaries provided.

Am 22.04.2019 07:56, schrieb Amagician:

Hi, I have struggled on this question for a long time. I downloaded
the whole project and use .|/gradlew -Pversion=4.x.y-DEV createExe| to
generate the jar file. However, when I try to log in with my correct
google account, it kept returning Bad Authentication. I can use the
exact same google account to log in the prebuild binaries provided.
image
https://user-images.githubusercontent.com/38928662/56485058-2f20dc00-6498-11e9-80b5-38bd08c81dd2.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/onyxbits/raccoon4/issues/57, or mute the thread
https://github.com/notifications/unsubscribe-auth/AADOTAPGNPIEBQEBDUFRDMTPRVHSHANCNFSM4HHNSYTQ.

The official binaries are build from the published source without any
modification.
This is a support issue, for that, you will need to open a support
ticket. You can do so from the "Help|Support" menu item.

Is there any update on this, I'm facing the exact same problem

Am 14.07.2019 12:54, schrieb Chris Georgoulis:

Is there any update on this, I'm facing the exact same problem
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/onyxbits/raccoon4/issues/57?email_source=notifications&email_token=AADOTAPZYX5MEUHZ3PMF7ITP7MAWTA5CNFSM4HHNSYT2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ4C4EQ#issuecomment-511192594,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADOTAILPDKKJXF53FVKXSDP7MAWTANCNFSM4HHNSYTQ.

Sorry, the bug tracker is for development questions. For support, please
open a ticket under  "Help|Support"

I'm having the same issue, was anyone able to figure it out (I used it successfully a few weeks ago)

Update: Login with my older Google account throw BadAuth every time, but a newly created Google account works fine.

Pretty much sounds as if something triggered the "Account was stolen" alarm. Solution in this case is to log in via browser and confirm the login attempt. I'll probably publish DummyDroid 2.0 today or tomorrow, which should have better error reporting.

Indeed, I logged in and was asked to confirm it was me.
But even after confirming the login attempt, I continue to get BadAuth

Raccoon works again after I changed the password

authors: Amagicians cgeo7 onyxbits paulo-raca


text:
how i use mongo database?

data save to disk how to change to mongo database?

Duplicate of #77

authors: ahmedRSA ookamiiixd

repo: ookamiiixd/baileys-api


text:
update tag/push to accept multiple values

Updates scripts/tag.sh and scripts/push.sh to accept a list of tags to be usedin:

policy-tag-action
policy-push-action
example job that uses the new actions: https://github.com/gimmyxd/test-release-action/blob/main/.github/workflows/build-release-policy.yaml

Pull Request Test Coverage Report for Build 1611266222

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 7.473%

Totals

Change from base Build 1607510756:
0.0%

Covered Lines:
126

Relevant Lines:
1686

💛  - Coveralls

authors: coveralls gimmyxd

repo: opcr-io/policy


text:
Set default field manager

Signed-off-by: Jian Qiu jqiu@redhat.com

/lgtm

repo: open-cluster-management-io/api


text:
build: create metrics service when installing hub

Co-authored-by: Maggie Chen magchen@redhat.com
Signed-off-by: Tomer Figenblat tfigenbl@redhat.com

/hold

/approve
/lgtm

/assign @qiujian16
Hi @qiujian16 , could you help review and approve this PR? Thanks!

Standalone deployment modified in https://github.com/open-cluster-management-io/multicloud-operators-subscription/pull/259.

/unhold

/approve
/lgtm

repo: open-cluster-management-io/clusteradm


text:
✨ Add a configmap to handle the proxy ca bundle

Summary
This is a follow-up of PR https://github.com/open-cluster-management-io/ocm/pull/760, in this PR, it will handle the ca bundle for proxy config, a configmap containing the ca bundle will be created and mounted to the agent deployments/daemonsets. and the mounted ca bundle file path will be injected as the environment CA_BUNDLE_FILE_PATH to the deployments/daemonsets. Addon developers can use the environment to get the ca bundle data.
Related issue(s)
https://github.com/open-cluster-management-io/ocm/issues/761
Fixes #

/cc @qiujian16 @elgnay

/lgtm

repo: open-cluster-management-io/ocm


text:
Test updates

Cherry-pick latest test updates to release-2.4

/cc @zlayne

repo: open-cluster-management/grc-ui


text:
Can't overwrite a KUBECONFIG that's in use

This line will cause issues if a user is still using the file to login to the ClusterPool cluster:
https://github.com/open-cluster-management/lifeguard/blob/0ce949b7e2d9997a1d5e0511e3b8ba4af946c165/clusterclaims/apply.sh#L389

Should be fairly straightforward (?) to check up-front whether the KUBECONFIG in use is a lifeguard/clusterclaims/*/kubeconfig file

I've addressed it in startrhacm this way:
https://github.com/dhaiducek/startrhacm/blob/e271da0a72ce8ac0ea4b4eb86e2936e68e77219d/startrhacm.sh#L70-L72

repo: open-cluster-management/lifeguard


text:
switch to use clusterrole to replace roles in each cluster namespace

https://github.com/open-cluster-management/backlog/issues/10004

Do we need to special handle the upgrade case - to remove the role in managedcluster namespace?

@clyang82
yes, I will add the code to handle the upgrade in another pr

/approved
/lgtm

/retest

/retest

/retest

/retest

/retest

/retest


text:
handle observatorium cr for pvc resize forbidden.

ref: https://github.com/open-cluster-management/backlog/issues/14103
Signed-off-by: morvencao lcao@redhat.com

/test test-e2e

/test test-e2e

/test test-e2e

close this in favor of https://github.com/open-cluster-management/multicluster-observability-operator/pull/681


text:
Participants cannot be modified

@nclaidiere reported that participant information cannot be modified. That is, if you create a participant and then go back and modify the information, the following error appears:

I haven't been able to reproduce this myself (with v0.6.0). @nclaidiere Can you still reproduce this, and if so, what are the exact steps?

I'm closing this because it was due to cross-domain policy.

repo: open-cogsci/omm-server


text:
add additional blueprint media type to blueprint downloader

Description

Added a blueprint mediatype to the blueprint downloader.
What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents

Related Issue # (issue)
Closes # (issue)
Fixes # (issue)

Remove if not applicable

Screenshots

Added tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help
[ ] Separate ticket for tests # (issue/pr)

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?

[ ] 📜 README.md
[ ] 🙅 no documentation needed

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@fabianburth , don't mind about the PR failure for blackduck. This is because GitHub does not use the secrets maintained in the target repo and therefore always fails when using secrets different from GITHUB_TOKEN in forks...

authors: fabianburth morri-son

repo: open-component-model/ocm


text:
Management commands: Use logger instead of print()

See https://docs.djangoproject.com/en/3.1/topics/logging/#using-logging
Also, please use plain English like "Importing..." not "Importingg!!!!!!!!". In general, no messages need exclamation marks. Update: Fixed.

Nevermind - not worth the complexity of configuring LOGGING.


text:
feat: Add --quiet option to decrease verbosity, closes #248. Always print output for manual command fetch-award-by-id-and-supplier. chore: Remove quick-returns to simplify logic (loops will not run on empty lists/dicts). Remove noisy "Mail sent and status updated" output.

closes #248. Always print output for manual command fetch-award-by-id-and-supplier. chore: Remove quick-returns to simplify logic (loops will not run on empty lists/dicts). Remove noisy "Mail sent and status updated" output.
After deploying Docker, add -q to the cron jobs (e.g. python -m app.commands -q fetch-awards)

Pull Request Test Coverage Report for Build 10493896595
Details

21 of 22 (95.45%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 84.765%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/commands.py
21
22
95.45%

Totals

Change from base Build 10491586074:
0.01%

Covered Lines:
1786

Relevant Lines:
2107

💛  - Coveralls

authors: coveralls jpmckinney

repo: open-contracting/credere-backend


text:
Rename org and repo

We need to be Global.Health not open-covid-data and we need a repo name that is not temporary.
https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/renaming-an-organization
https://docs.github.com/en/github/administering-a-repository/renaming-a-repository
Happy to volunteer and break everyone once we have a repo name and are ready to go.

@attwad Who needs to make the decision on this?

Long term owners (so not us), perhaps Jared, Moritz and Spencer?

@JaredHawkins Please make the call or direct this to someone who can.

Moritz owns this repo, though perhaps we should have it transferred over to BCH as part of the handoff?

@mougk over to you.

did we make a final call here ?

as per slack poll, it will be globaldothealth/list, will prepare the changes now.

Thanks @attwad!

authors: JaredHawkins attwad dakrownie outbreakprepared

repo: open-covid-data/healthmap-gdo-temp


text:
https error?

https://clidewoodrealm.localplayer.dev/

fixed

repo: open-domains/register


text:
./env/bin/pip install -r pip_requirements.txt -i https://pypi.douban.com/simple

hello!
the dashboard
when installed on centos6.6 python2.7,report the question "CertificateError: hostname 'pypi.doubanio.com' doesn't match '*.ucdl.pp.uc.cn'"
it appeared in virtualenv environment, but it was installed sucessfully in system python environment
./env/bin/pip install -r pip_requirements.txt -i https://pypi.douban.com/simple

run this: ./env/bin/pip install -r pip_requirements.txt

vi  pip_requirements.txt
edit      gunicorn ~> 19.5.0
to         gunicorn == 19.5.0
fu*k

@kiddkyd1412  fixed https://github.com/open-falcon/dashboard/commit/b487bc60e3b19fba1f1594c0027f128f17abfd07
@Mrhjx2  fixed https://github.com/open-falcon/dashboard/commit/8120ef889c64ed03d0d3f67096096725ffe7dd2d

repo: open-falcon/dashboard


text:
关于模块版本管理问题

目前的版本和其更改记录是在 const.go 进行记录，比如 nodata 模块：
// changelog:
// 0.0.1 init project
// 0.0.2 make mock item.Ts one step after now(), rm sending log, add flood in proc
// 0.0.3 mv common to falcon.common, simplify nodata's codes, mv cfgcenter to nodata
// 0.0.4 fix bug of nil response on collecting from query
// 0.0.5 collect items concurrently from query
// 0.0.6 clear send buffer when blocking
// 0.0.7 use gauss distribution to get threshold, sync judge and sender, fix bug of collector's cache
// 0.0.8 simplify project

const (
	VERSION = "0.0.8"
)

这不太好：

在代码中记录 changelog。
读取版本号麻烦。

我知道，你可以这样获取版本：
cat modules/nodata/g/const.go | grep VERSION | cut -f2 -d '"'

也许可以接受吧 :smile:。

谢谢你的建议，我在这个PR https://github.com/open-falcon/falcon-plus/pull/816 中，把各个模块的版本修改为主版本一致了。否则容易混淆。 @shaneing

authors: laiwei shaneing

repo: open-falcon/falcon-plus


text:
chore: add angular sdk to ecosystem

This PR

adds angular

Notes
Depends on some minor changes to the Angular readme.
https://github.com/open-feature/js-sdk/pull/1013

Converting to draft until the SDK readme has been updated.


text:
Bug🐛: hub/lfedge_mgmt_hub.md links are incorrect

Describe the bug.
The hub/lfedge_mgmt_hub.md markdown page uses the full https:// URL to internal references.  These can be changed to relative paths. For example,  [Hub admin](../admin/multitenancy.md#user-types]
./hub/lfedge_mgmt_hub.md:1. Authenticate with the Hub as a [Hub admin](https://open-horizon.github.io/docs/admin/multi_tenancy.html#user-types).
./hub/lfedge_mgmt_hub.md:4. Create the new user account (add -A if the account is for an [Organization admin](https://open-horizon.github.io/docs/admin/multi_tenancy.html#user-types)):

Describe the steps to reproduce the behavior
No response
Expected behavior.
No response
Screenshots.
No response
Operating environment
all
Additional context
No response

Hi @johnwalicki I happy to provide the quick fix for this issue. Could you please assign this issue to me?

@johnwalicki I have implement the fix and created a draft PR #454. If you could please review the same and let me know if its good to be merged.

authors: dipesh-rawat johnwalicki


text:
DB2 ERROR: Did not recognize type 'BOOLEAN'

Affected module
Backend
Describe the bug
OM can not recognize BOOLEAN data type
To Reproduce
Ingest a table which has column with "BOOLEAN" data type
Get the warning message:
[2024-06-17T15:45:21.465+0800] {logging_mixin.py:188} WARNING - /opt/airflow/lib64/python3.9/site-packages/ibm_db_sa/reflection.py:292 SAWarning: Did not recognize type 'BOOLEAN' of column 'XXX'
some discussion are in the slack thread: https://openmetadata.slack.com/archives/C02B6955S4S/p1712336244151299
Expected behavior
can ingest DB2 metadata without this error
Version:

OS: Redhat8.9
Python version: 3.9
OpenMetadata version: 1.4.1
OpenMetadata Ingestion package version:

Additional context
Add any other context about the problem here.

fixed with https://github.com/open-metadata/OpenMetadata/pull/16718

repo: open-metadata/OpenMetadata


text:
gt_boxes key_error

https://github.com/open-mmlab/OpenPCDet/blob/master/pcdet/datasets/nuscenes/nuscenes_dataset.py#L143
Could we add 'gt_boxes' in data_dict: in above line to avoid key_error? Because I want to just inference some middle sweep frames without annos.

Hi !Same question as yours, I had to set SET_NAN_VELOCITY_TO_ZEROS: False.
Did you resolve it?

@Raiden-cn  maybe just refer to https://github.com/open-mmlab/OpenPCDet/blob/master/pcdet/datasets/nuscenes/nuscenes_dataset.py#L148

authors: Raiden-cn SakuraRiven

repo: open-mmlab/OpenPCDet


text:
KITTI

Hello， How Can I set the configure files if I only want to train 'Car' about KITTI datasets？

Please try to change CLASS_NAMES and ANCHOR_GENERATOR_CONFIG to make them only include 'Car' category.


text:
GroundingDINO 检测问题

在远景目标识别中，模型经常把人的头部识别成瓶子。

这可能是算法缺陷。我们会在下一版本中尝试解决这个问题

authors: hhaAndroid lybllybl

repo: open-mmlab/mmdetection


text:
consummating xml_style.py

During the training process, I found that some xml files may not have a size field, but the remaining content in these files is complete, so I think it is beneficial to consummate this file

Thanks for your contribution! Could you fix the linting errors?

Hi!
@yuzhj
First of all, we want to express our gratitude for your significant PR in the OpenMMLab project. Your contribution is highly appreciated, and we are grateful for your efforts in helping improve this open-source project during your personal time. We believe that many developers will benefit from your PR.
We would also like to invite you to join our Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/UjgXkPWNqA
If you have WeChat account，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤

authors: OpenMMLab-Assistant-007 hellock yuzhj


text:
fix py3.8 dict changed during iteration

Motivation
In python3.8, changing the key of a dictionary during iteration is forbidden.
BC-breaking (Optional)
None

"RuntimeError: dictionary changed size during iteration" is a common bug. see dictionary-iterators. It not a version-specific bug of py38.

authors: Jason-cpp jshilong


text:
console driver loglevel is broken.

42.51711|ISTEP 21. 3
[   43.001463146,5] SkiBoot 6916c2a starting...
[   43.001466225,5] initial console log level: memory 7, driver 5
[   43.001469168,6] CPU: P8 generation processor(max 8 threads/core)
[   43.001471742,7] CPU: Boot CPU PIR is 0x0068 PVR is 0x004d0200
[   43.001474588,7] CPU: Initial max PIR set to 0x1fff
[   43.001961041,5] OPAL table: 0x300d6840 .. 0x300d6d00, branch table: 0x30002000
[   43.001965830,5] Assigning physical memory map table for unused
[   43.001969452,5] FDT: Parsing fdt @0xff00000
[   43.006070254,5] XSCOM: chip 0x0 at 0x3fc0000000000 [P8 DD2.0]
[   43.006079319,6] XSTOP: XSCOM addr = 0x2010c82, FIR bit = 31
[   43.006082563,6] MFSI 0:0: Initialized
[   43.006084668,6] MFSI 0:2: Initialized
[   43.006086747,6] MFSI 0:1: Initialized
[   43.006440425,5] LPC: LPC[000]: Initialized, access via XSCOM @0xb0020
[   43.006447804,5] LPC: LPC: Default bus on chip 0x0
[   43.006564365,6] MEM: parsing reserved memory from node /ibm,hostboot/reserved-memory
[   43.006573687,7] HOMER: Init chip 0
[   43.006576531,7]   PBA BAR0 : 0x0000001ffd800000
[   43.006579227,7]   PBA MASK0: 0x0000000000300000
[   43.006581836,7]   HOMER Image at 0x1ffd800000 size 4MB
[   43.006585340,7]   PBA BAR2 : 0x4000001ffda00000
[   43.006588002,7]   PBA MASK2: 0x0000000000000000
[   43.006590396,7]   SLW Image at 0x1ffda00000 size 1MB
[   43.006593691,7]   PBA BAR3 : 0x0000001fff800000
[   43.006596200,7]   PBA MASK3: 0x0000000000700000
[   43.006598682,7]   OCC Common Area at 0x1fff800000 size 8MB
[   43.006622658,7] CPU idle state device tree init
[   43.006626086,5] SLW: HB-provided idle states property found
[   43.006630135,5] SLW: Enabling: nap
[   43.006632249,5] SLW: Enabling: fastsleep_
[   43.006634754,5] SLW: Enabling: winkle
[   43.006847499,5] PLAT: Fixing up PSI BAR on chip 0 BAR=3fffe80000001
[   43.006877027,7] AST: PNOR LPC offset: 0x0c000000
[   43.006945141,5] PLAT: Using virtual UART
[   43.007246750,7] UART: Using LPC IRQ 4
[   43.311158472,5] PLAT: Detected Habanero platform
[   43.322590643,5] PLAT: Detected BMC platform AMI
[   43.323613620,5] CENTAUR: Found centaur for chip 0x0 channel 0
[   43.334138327,5] CENTAUR:   FSI host: 0x0 cMFSI0 port 3
[   43.350026745,5] CENTAUR: Found centaur for chip 0x0 channel 1
[   43.366102333,5] CENTAUR:   FSI host: 0x0 cMFSI0 port 2
[   43.383896580,5] CENTAUR: Found centaur for chip 0x0 channel 4
[   43.393383788,5] CENTAUR:   FSI host: 0x0 cMFSI0 port 7
[   43.404720509,5] CENTAUR: Found centaur for chip 0x0 channel 5
[   43.416367459,5] CENTAUR:   FSI host: 0x0 cMFSI0 port 6
[   43.425851621,5] PSI[0x000]: Found PSI bridge [active=0]
[   43.447681608,5] CPU: All 80 processors called in...
[    2.218214723,5] FLASH: Found system flash: Macronix MXxxL51235F id:0
[    2.218358437,5] BT: Interface initialized, IO 0x00e4
[    3.167440144,5] NVRAM: Size is 576 KB
[    3.354493685,5] STB: secure mode off
[    3.354542095,5] STB: trusted mode off
[    3.354608990,5] OPAL: Using OPAL UART console
[    3.354814492,5] CAPI: Preloading ucode 200ea
[    3.364143038,5] FLASH: Queueing preload of 2/200ea
[    3.375586452,5] FLASH: Queueing preload of 0/0
[    3.392341159,5] FLASH: Queueing preload of 1/0
[    3.392357392,7] FFS: Partition map size: 0x1000
[    3.402830344,7] FLASH: CAPP partition has ECC
[    3.404365099,7] FLASH: CAPP partition isn't signed
[    3.404366411,7] FLASH: flash subpartition eyecatcher CAPP
[    3.404367589,7] FLASH: Computed CAPP partition size: 73728 (subpart 131306 size 36432 offset 4096)
[    3.439382606,5] STB: sb_verify skipped resource 2, secure_mode=0
[    3.439384269,5] STB: tb_measure skipped resource 2, trusted_mode=0
[    3.465655309,7] FFS: Partition map size: 0x1000
[    3.488395337,7] FLASH: BOOTKERNEL partition doesn't have ECC
[    3.498746743,7] FLASH: BOOTKERNEL partition isn't signed
[    3.498747971,7] FLASH: computed BOOTKERNEL size 15640424
[    4.097233036,5] Chip 0 Found PBCQ0 at /xscom@3fc0000000000/pbcq@2012000
[    4.139139162,5] Chip 0 Found PBCQ1 at /xscom@3fc0000000000/pbcq@2012400
[    4.223097454,5] Chip 0 Found PBCQ2 at /xscom@3fc0000000000/pbcq@2012800
[    4.453931311,3] PHB#0000: Base location code not found !
[    7.252082527,3] PHB#0001: Base location code not found !
[    9.089793625,3] PHB#0002: Base location code not found !
[   10.355795914,5] PCI: Resetting PHBs...
[   13.258329459,5] PCI: Probing slots...
[   13.419102110,5] STB: sb_verify skipped resource 0, secure_mode=0
[   13.419122521,7] BT: seq 0x09 netfn 0x06 cmd 0x35: IPMI MSG done
[   13.419123905,7] IPMI read event 35 complete: 16 bytes. cc: 00
[   13.419125232,6] IPMI: dropping System Event Record SEL
[   13.421756971,7] PCI: Checking slot table against detected devices
[   13.421761105,7] PCI Summary:
[   13.421769283,5] PHB#0000:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..01 SLOT=Slot3
[   13.421777952,5] PHB#0000:01:00.0 [EP  ] 14e4 168a R:10 C:020000 (      ethernet) LOC_CODE=Slot3
[   13.421785001,5] PHB#0000:01:00.1 [EP  ] 14e4 168a R:10 C:020000 (      ethernet) LOC_CODE=Slot3
[   13.421791793,5] PHB#0000:01:00.2 [EP  ] 14e4 168a R:10 C:020000 (      ethernet) LOC_CODE=Slot3
[   13.421798572,5] PHB#0000:01:00.3 [EP  ] 14e4 168a R:10 C:020000 (      ethernet) LOC_CODE=Slot3
[   13.421807807,5] PHB#0001:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..15 SLOT=Backplane PLX
[   13.421816188,5] PHB#0001:01:00.0 [SWUP] 10b5 8748 R:ca C:060400 B:02..15 LOC_CODE=Backplane PLX
[   13.421832784,5] PHB#0001:02:01.0 [SWDN] 10b5 8748 R:ca C:060400 B:03..07 SLOT=Network Mezz
[   13.421845487,5] PHB#0001:02:08.0 [SWDN] 10b5 8748 R:ca C:060400 B:08..08 SLOT=Storage Mezz
[   13.421854847,5] PHB#0001:08:00.0 [LGCY] 1b4b 9235 R:11 C:010601 (          sata) LOC_CODE=Storage Mezz
[   13.421865713,5] PHB#0001:02:09.0 [SWDN] 10b5 8748 R:ca C:060400 B:09..09 SLOT=Backplane USB
[   13.421875637,5] PHB#0001:09:00.0 [EP  ] 104c 8241 R:02 C:0c0330 (      usb-xhci) LOC_CODE=Backplane USB
[   13.421886671,5] PHB#0001:02:0a.0 [SWDN] 10b5 8748 R:ca C:060400 B:0a..0b SLOT=Backplane BMC
[   13.421896873,5] PHB#0001:0a:00.0 [ETOX] 1a03 1150 R:03 C:060400 B:0b..0b LOC_CODE=Backplane BMC
[   13.433540961,5] PHB#0001:0b:00.0 [PCID] 1a03 2000 R:30 C:030000 (           vga) LOC_CODE=Backplane BMC
[   13.433552110,5] PHB#0001:02:10.0 [SWDN] 10b5 8748 R:ca C:060400 B:0c..10 SLOT=Slot2
[   13.433564759,5] PHB#0001:02:11.0 [SWDN] 10b5 8748 R:ca C:060400 B:11..15 SLOT=Slot1
[   13.433575597,5] PHB#0002:00:00.0 [ROOT] 1014 03dc R:00 C:060400 B:01..ff SLOT=Slot4
[   13.433582460,6] IPMI: setting fw progress sensor 05 to 07
[   14.194616142,7] BT: seq 0x0a netfn 0x04 cmd 0x30: Message sent to host
[   14.273925460,5] irq 10 name: psi:fsp (7/0)
[   43.001466225,5] initial console log level: memory 7, driver 5
so we have console log level for driver we set to 5, But i am seeing loglevel 6 and 7 also logged to the driver. But all 6 and 7 loglevels are logged to memory as expected. But for driver some INFO and DEBUG log level messages are logging(Not all messages). is it expected?

FWIW, looks like this patch (and associated series) from @oohal attempts to fix it https://patchwork.ozlabs.org/patch/707655/

Should be closed as not updated for nearly 18 months. Please reopen if needed.

Looks like this fix went in

authors: gery-toulouse mikey pridhiviraj sammj

repo: open-power/skiboot


text:
First Linux Only Version

open-pwa cli
open-pwa install window-manager
open-pwa install create-shortcut-linux
module.exports = {
  apps : [{
    name        : "worker",
    script      : "./worker.js",
    watch       : true,
    env: {
      "NODE_ENV": "development",
    },
    env_production : {
       "NODE_ENV": "production"
    }
  },{
    name       : "api-app",
    script     : "./api.js",
    instances  : 4,
    exec_mode  : "cluster"
  }]
}

{
  "apps" : [{
    "name"        : "worker",
    "script"      : "./worker.js",
    "watch"       : true,
    "env": {
      "NODE_ENV": "development",
    },
    "env_production" : {
       "NODE_ENV": "production"
    }
  },{
    name       : "api-app",
    script     : "./api.js",
    instances  : 4,
    exec_mode  : "cluster"
  }]
}

https://github.com/Shubham-Kumar-2000/protocol-registry/blob/main/src/linux/postinstall.js

repo: open-pwa/open-pwa


text:
Fix for exact search

Updates exact search to use similarity search with tanimoto threshold of 1.0; fixes #36
Not quite sure how to handle mixed exact and similarity search with the rdkit postgres cartridge (can only set the threshold once per query)

@connorcoley tests are passing now

repo: open-reaction-database/ord-interface


text:
Graph generation dependencies for campaigns

When directly executing the generate_graph function on a campaign(not a suite), the necessary dependencies: pandas matplotlib seaborn are not automatically added.
Error occured on: campaign.generate_graph(         plot_name="scatterplot",         x="nb_threads",         y="counter",         #hue="clarity",     )
Stacktrace:
  File "/home/pi/Documents/benchkit/benchkit/lwchart.py", line 158, in generate_chart_from_single_csv
    df = _read_csv(csv_pathname=csv_pathname)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pi/Documents/benchkit/benchkit/lwchart.py", line 105, in _read_csv
    return pd.read_csv(
           ^^
NameError: name 'pd' is not defined. Did you mean: 'id'?

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/pi/Documents/benchkit/examples/counter/bench.py", line 252, in <module>
    campaign.generate_graph(
  File "/home/pi/Documents/benchkit/benchkit/campaign.py", line 242, in generate_graph
    generate_chart_from_single_csv(
  File "/home/pi/Documents/benchkit/benchkit/lwchart.py", line 159, in generate_chart_from_single_csv
    except pd.errors.EmptyDataError:
           ^^
NameError: name 'pd' is not defined. Did you mean: 'id'?```

Normally, when the dependencies are not there, lwchart should skip the graph generation. You hit a bug. I'm going to investigate.

authors: ThomasVandermotten apaolillo


text:
Added student profile diogoamvasconcelos.md

Added my student profile diogoamvasconcelos.md

@diogoamvasconcelos thanks for enrolling! :smile:

Thank you for this initiative.
On 4 October 2015 at 21:49, Eric Douglas notifications@github.com wrote:

@diogoamvasconcelos https://github.com/diogoamvasconcelos thanks for
enrolling! [image: :smile:]
—
Reply to this email directly or view it on GitHub
https://github.com/open-source-society/computer-science-and-engineering/pull/25#issuecomment-145386572
.

@diogoamvasconcelos
I updated the manner to enrolling in our course to be more scalable.
Can you create your profile here again?
Sorry for that, but in that way will be much more easy for all of us :smile:

authors: diogoamvasconcelos ericdouglas


text:
not able to disable resource detector

What happened?
Steps to Reproduce

enable auto instrument on k8s

 annotations:
        # enable opentelemetry auto-instrument
        instrumentation.opentelemetry.io/inject-nodejs: "my-instrument"

enable only env for resource detector using environment variable

...
      containers:
        - name: app
          image: app-image
          envFrom:
            - configMapRef:
                name: my-config
          env:
          - name: OTEL_SERVICE_NAME
            value: my-app
          - name: OTEL_NODE_RESOURCE_DETECTORS
            value: "env"
...

enable http logs in the application, and I can see it tries to get meta data for gcp and alibaba cloud.

HTTP 29: SOCKET ERROR: ECS metadata api request timed out. Error: ECS metadata api request timed out.
    at Timeout._onTimeout (/otel-auto-instrumentation/node_modules/@opentelemetry/resource-detector-alibaba-cloud/build/src/detectors/AlibabaCloudEcsDetector.js:87:29)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)

HTTP 1: SOCKET ERROR: getaddrinfo ENOTFOUND metadata.google.internal. Error: getaddrinfo ENOTFOUND metadata.google.internal.
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:108:26)

we also see some errors when the init container starts, not sure if this will be a problem as well, we are running container as non-root

...
cp: can't preserve ownership of '/otel-auto-instrumentation/./node_modules/protobufjs/dist/protobuf.min.js': Operation not permittedcp: can't preserve ownership of '/otel-auto-instrumentation/./node_modules/protobufjs/dist/protobuf.min.js.map': Operation not permittedcp: can't preserve ownership of '/otel-auto-instrumentation/./node_modules/protobufjs/dist': Operation not permittedcp: can't preserve ownership of '/otel-auto-instrumentation/./node_modules/protobufjs/ext/debug/README.md': Operation not permittedcp: can't preserve ownership of '/otel-auto-instrumentation/./node_modules/protobufjs/ext/debug/index.js': Operation not permittedcp: can't preserve ownership of '/otel-auto-instrumentation/./node_modules/protobufjs/ext/debug': Operation not permitted
...

Expected Result
auto instrument should not try to get meta data for google or alibaba cloud
Actual Result
it tries to query the infra meta data which does not exist
Additional Details
image version: otel/autoinstrumentation-nodejs:0.44.0
OpenTelemetry Setup Code
No response
package.json
No response
Relevant log output
No response

Yes, I can see that this is a pain if the auto-instrumentation is used in this way. 🤔
However, I'm removing the bug label and adding enhancement as this is not a feature that already exists and is broken but a request for a feature that is currently not implemented. I'd definetly be useful to have though, so I'd be happy to see a contribution in this repo that allows for allow-listing resource detectors, adding up-for-grabs 🙂

Same situation here. I'm sorry @pichlermarc but I didn't quite understand why this would be a feature and not a bug - could you elaborate? The README says we can use OTEL_NODE_RESOURCE_DETECTORS to enable only certain resource detectors.
https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/metapackages/auto-instrumentations-node/README.md#usage-auto-instrumentation

@illrill thanks for asking. To be honest I don't fully remember my what my train of through was back then. Looks to me like I  made a mistake. Sorry about that.
This should work - are you also using the operator? Looking at the code, they set the resource detectors directly when instantiating NodeSDK, so that would looks to me like it should be filed in the operator repo: https://github.com/open-telemetry/opentelemetry-operator
If you're using it like node --require '@opentelemetry/auto-instrumentations-node/register'  and it's not working then this repo here is actually the correct place to report the bug. The same is true for getResourceDetectorsFromEnv(). If this is what you're using and it's not working then this also belongs here.

@pichlermarc Thank you for the reply and guidance. You definitely nailed it, I'm using the auto-injection feature of the Operator (looks like @droger88 is also doing so). I've opened an issue in that repo instead 👍

@pichlermarc Thank you for the reply and guidance. You definitely nailed it, I'm using the auto-injection feature of the Operator (looks like @droger88 is also doing so). I've opened an issue in that repo instead 👍

Thanks for following up. I'll close the issue right here as the one over at the operator repo can be used for further tracking. :+1:

authors: droger88 illrill pichlermarc

repo: open-telemetry/opentelemetry-js-contrib


text:
[next] merge main

Update with latest changes from main

I'm going to try to merge this with a merge commit instead of a squash to try to get the histories between branches to look nice again. All work here is previously reviewed.

repo: open-telemetry/opentelemetry-js


text:
refactor: Extract Instrumentation Registry Gem

This change is the first in many steps that will allow us to move instrumentation gems into the contrib repo.
It copies the existing Registry into its own gem and will allow us to release it without breaking the SDK
or Instrumentations.
Once published we can update existing dependencies to use the opentelemetry-registry gem.
See https://github.com/open-telemetry/opentelemetry-ruby-contrib/issues/1
See https://github.com/open-telemetry/opentelemetry-ruby/discussions/776

Leaving the base gem in the main repo means any changes to the Base class would require coordination with the contrib repo. That isn't necessarily true for the registry, which hasn't changed much.
The tight coupling between the instrumentations and the Base class made me think isolating the registry would make maintenance easier for us.

Why this change makes sense from my perspective

Having the registry decoupled from the sdk allows a hypothetical third party sdk to make us of it, and by extension all the instrumentation.
The registry has little to no churn, and is more closely related to the SDK than anything else.
I think it'll improve ease of development for instrumentation packages (in the contrib repo) if some changes need to be made in the base class and you want to see if they’re compatible immediately as part of ci, and not when you do a gem bump.

@robertlaurin It looks like there are intermittent test failures in Linux JRuby. Has that come up before?
https://github.com/open-telemetry/opentelemetry-ruby/runs/5853687205?check_suite_focus=true

authors: arielvalentin robertlaurin

repo: open-telemetry/opentelemetry-ruby


text:
[Discussion] OTel distributions: Where to list them? Should we?

An interesting question arose in #3774 concerning OpenTelemetry distributions, such as Honeycomb's, Splunk's, and so on: Should we list them in the Registry, perhaps creating a new category, put them in https://opentelemetry.io/ecosystem/vendors/, or do something else?
I'd go for the vendor route, creating a subpage just for distributions, or even pages for each distribution (that would have to be created and maintained by distribution owners). Each section or page would point to the repository and present the main differences or features of the distribution, ideally in a table. For Collector distributions we could even list the components, as they're currently metadata in YAML format.

With my AWS Distro for OpenTelemetry (ADOT) product hat on: +1 to create a sub-page for distributions (one page per distro seems too much for starters).

I tried to write a reply to this now for a few times, because I am conflicted if and how to promote distributions:
On the one hand I think that by giving them a dedicated page, or by giving them more space on the vendors page (i.e. by updating the column with "Distribution: yes/no" to a link to the same), we give end-users (and especially vendors!) the feeling that a distribution is a must have and that without one a vendor is maybe worse than one that has a distribution. We experience this already when people add their vendor to the list, they keep the "checkbox checked" until we ask them to provide proof that their distro exists.
This goes against (my!) perception of distributions: having a distribution is a neutral thing, it is a design decision, that a vendor should make based on their specific requirements. Many will live happy without their own distribution, while others figure out that a distro for their platform/backend/pipeline/... is what they need.
On the other thand, I think it's a good thing to let people know that for specific cases there is a distribution that they can use to make their live easier. It can be the one click solution to get started with a specific vendor, or it can be the piece that makes your cloud services fly with otel. So by not mentioning them people might struggle with building their own collector, using vanilla SDKs, while a solution is around the corner.
To make a long story short: We should have them in our ecosystem pages, but we need to make sure that we communicate well enough that distributions are not simply a checkbox that makes your solution automatically better.

I think the single page solution could work if we open it by stating what distributions are and that they're not necessary to fully harness the power of OpenTelemetry.

I think the single page solution could work if we open it by stating what distributions are and that they're not necessary to fully harness the power of OpenTelemetry.

Fair point.

@svrnm Happy to give this one a try. It's fairly simple for me to find the Collector distros — less so with APM stuff. Where could I find data for an initial list?

@theletterf good question, we have the honeycomb one in the registry, the lumigo in the PR, and a list of "yes" on the vendor page (@mhausenblas can point you to ADOT). I don't think we need to start with a perfect list, collect ~5 and make a draft how it may look like and we go from there

authors: mhausenblas svrnm theletterf


text:
Update to OTel Collector v0.102.x

The steps for this update are documented in CONTRIBUTING.md.
Version 0.102.x was released this week.

The build failure appears to be some sort of regression in go work functionality.
I have removed the go.work file and added replace statements via crosslink, the same tool collector(-contrib) uses.
The use of crosslink is not automated, will have to be sorted out.
It will not be possible to go install or go run the Arrow collector from the repo until this is resolved (as it is with the OTel Collector(-Contrib) repos).

repo: open-telemetry/otel-arrow


text:
[http] Publish migration plan for HTTP semconv changes.

I was looking through https://github.com/open-telemetry/semantic-conventions/tree/main/docs/http#semantic-conventions-for-http and I am worried that users looking to understand how the breaking changes of the semantic convention will not have a clear path to understanding. I don't spend a lot of time in the spec/semconv, but I spend a lot of time in the project and I feel confused about certain things - I am worried about users who are purely consumers of OTEL.
My current questions:

Is the warning in https://github.com/open-telemetry/semantic-conventions/tree/main/docs/http#semantic-conventions-for-http still accurate?
Is the Oct 1st 2023 deadline still applicable (meaning Instrumentation Libraries are free to drop the env var support with the next stable release?

Ultimately I would love to see a page dedicated to outlining the migration steps. As a user I want to see exactly what values changed, what was dropped, what was added, etc. I'd also want to see which languages support the new values, and any important deadlines.
I feel the blog post was really good and I know a lot of details went into the changelog, but both of those locations aren't great for discoverability.  Important details in release notes, blog posts, and changelogs get moved downward as time goes on, making them harder to find.  I really want a permanent, dedicated, discoverable space for us to communicate this changes to our end users.
Hopefully any patterns we do now can help with any future semconv breaking changes.

yes (was there something that led you to think it isn't accurate, so we can fix that?)

My general confusion of the doc is that as a reader I'm not sure if it is applicable to me.  It gives a warning about using v1.20.0 or prior, but to be able to answer that I have to know what my instrumentation is using.  That's all possible to research, but it isn't something I expect the average OTel consumers to know. Ultimately it feels like a message for the SDK maintainers, and not something for an end user to consume (which is fine). But if an end user finds it I think it creates confusion. As an end user all I want to see is how the SDK I'm using is handling the breaking change.
https://opentelemetry.io/blog/2023/http-conventions-declared-stable/#summary-of-changes is what I'm looking for, but in a more permanent/discoverable place.  My worry is that down the road when some enterprise bumps their java/dotnet instrumentation from 1.0 to 2.0 they need to be able to find these changes or they'll feel pain. Of course we'd hope that they'd take advantage of the env var while in 1.0, but who knows.

maybe we should introduce a compliance matrix in the semantic conventions repo similar to https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md?

I think this is a great idea.  Listing of the version where the env var was added and then removed, and which sdks have done that, would be very helpful.
I think a combination of the blog content and a matrix is exactly what end users will need to successfully navigate this change. And once we have those docs, updating the warning section to guide end users to those docs.

I think this is a great idea. Listing of the version where the env var was added and then removed, and which sdks have done that, would be very helpful.
I think a combination of the blog content and a matrix is exactly what end users will need to successfully navigate this change. And once we have those docs, updating the warning section to guide end users to those docs.

I think that's a great start, but the real problem I see are instrumentations. SDKs have I think little to do with the support of the env variable. What really affect users are the instrumentation libraries they are using, and those won't be reflected in such matrix. It is also impracticable to list in a matrix all instrumentations in the spec/semconv repo.
Maybe what we can do is request that each SIG/contrib repo that have HTTP instrumentations to highlight such thing? Because as a developer, say working with .NET/ASP.NET I know the OTel .NET repo and if I have an overview of which version is supporting which semconv I think that's a better migration. Maybe such thing can even be part of the OTel website, under each language.

Mmm, I don't think this needs to be per-language. I would rather lean on release notes for the library instead, which can link to a more central migration page that explains what changed and how to approach it.

I see that both Java and DotNet are preparing their repos to drop support for the old HTTP semantic convention. I am very worried that if we don't solve this communication problem before that happens that we'll have a lot of upset users.

Java is preparing to publish a 2.x version which produces the new stable HTTP conventions, but will continue to support the 1.x version some undecided period of time. I think I heard > 6 months today. The 1.x version produces the old HTTP conventions with the ability to opt into the new ones.
cc @open-telemetry/java-instrumentation-maintainers

It is also impracticable to list in a matrix all instrumentations in the spec/semconv repo.

I think a matrix of all HTTP instrumentations published under the OpenTelemetry GitHub org could be feasible, and could be useful for our own internal tracking too (the third phase of the HTTP semconv stability WG is supposed to include driving these changes across existing implementations).
I'll explore what that might look like.
The question remains for me though where it is most likely that users would look for this information, and I tend to think that the first place they would look is the release notes for the given instrumentation library they are using.

I'll explore what that might look like.

thought on #571?

The question remains for me though where it is most likely that users would look for this information, and I tend to think that the first place they would look is the release notes for the given instrumentation library(ies) they are using.

I agree that we definitely want something in release notes (and I think how it is phrased should be standardized between languages.) But since it is a lot of information to convey, I support creating content that each changelog could link back to that details the specific changes that occurred.

thought on https://github.com/open-telemetry/semantic-conventions/pull/571?

Love it.  I recognize that something like that matrix adds cognitive load to OTel maintainers, but I think it is worth it.

Looks good, but I'm just afraid of how/who will be responsible of keeping this up-to-date? Our compatibility matrix is often outdated (SIG maintainers don't always come to tick the box when they add a feature), imagine the vast amount of instrumentations. I liked the idea of having a template, that maybe is maintained by the semconv repo, but that then each instrumentation is required to add to their README somehow? I feel this way the chance of things being outdated is less.

I liked the idea of having a template, that maybe is maintained by the semconv repo, but that then each instrumentation is required to add to their README somehow?

We should definitely do this.  I view this as the bare minimum we (semconv sig) should be doing for users to ensure the release notes make it clear that the breaking changes affect end users.

Possible Release note template:
Breaking Changes
The following {{library names}} now emit only the stable HTTP semantic conventions:

Library Name 1
Library Name 2
...
Library Name N

Impact
This breaking change updates these libraries to emit new attribute names, such as http.response.status_code instead of http.status_code.  If you already depend on the old names of the attributes emitted by these libraries in down downstream locations, such as collector configuration, alerts, or dashboards you will be affected by this change.
What is Changing
See HTTP semantic conventions declared stable for full details.
Common attributes across HTTP client and server spans

Change
Comments

http.method → http.request.method
Now captures only 9 common HTTP methods by default (configurable) plus _OTHER

http.status_code → http.response.status_code

http.request.header.<key>
• Dash ("-") to underscore ("_") normalization in <key> has been removed• On HTTP server spans: now must be provided to sampler

http.response.header.<key>
Dash ("-") to underscore ("_") normalization in <key> has been removed

http.request_content_length → http.request.body.size
• Recommended → Opt-In• Not marked stable yet

http.response_content_length → http.response.body.size
• Recommended → Opt-In• Not marked stable yet

user_agent.original
• On HTTP client spans: Recommended → Opt-In• On HTTP server spans: now must be provided to sampler• See note if migrating from <= v1.18.0

net.protocol.name → network.protocol.name
Recommended → Conditionally required if not http and network.protocol.version is set

net.protocol.version → network.protocol.version
• Examples fixed: 2.0 → 2 and 3.0 → 3• See note if migrating from <= v1.19.0

net.sock.family
Removed

net.sock.peer.addr → network.peer.address
On HTTP server spans: if http.client_ip was unknown, then also net.sock.peer.addr → client.address; client.address must be provided to sampler

net.sock.peer.port → network.peer.port
Now captured even if same as server.port

net.sock.peer.name
Removed

New: http.request.method_original
Only captured when http.request.method is _OTHER

New: error.type

References:

Common attributes v1.20.0
Common attributes v1.23.0 (stable)

HTTP client span attributes

Change
Comments

http.url → url.full

http.resend_count → http.request.resend_count

net.peer.name → server.address

net.peer.port → server.port
Now captured even when same as default port for scheme

{.td-initial .table .table-responsive .ot-table-first-row-60}

References:

HTTP client span attributes v1.20.0
HTTP client span attributes v1.23.0 (stable)

HTTP server span attributes

Change
Comments

http.route
No change

http.target → url.path and url.query
Split into two separate attributes

http.scheme → url.scheme
Now factors in X-Forwarded-Proto, Forwarded#proto headers

http.client_ip → client.address
If http.client_ip was unknown (i.e., no X-Forwarded-For, Forwarded#for headers), then net.sock.peer.addr → client.address; now must be provided to sampler

net.host.name → server.address
Now based only on Host, :authority, X-Forwarded-Host, Forwarded#host headers

net.host.port → server.port
Now based only on Host, :authority, X-Forwarded-Host, Forwarded#host headers

References:

HTTP server span attributes v1.20.0
HTTP server span attributes v1.23.0 (stable)

HTTP client and server span names
The {http.method} portion of span names is replace by HTTP when
{http.method} is _OTHER.
See note if migrating from <= v1.17.0.
References:

HTTP client and server span names v1.20.0
HTTP client and server span names v1.23.0 (stable)

HTTP client duration metric
Metric changes:

Name: http.client.duration → http.client.request.duration
Unit: ms → s
Description: Measures the duration of inbound HTTP requests. →
Duration of HTTP server requests.
Histogram buckets: boundaries updated to reflect change from milliseconds
to seconds, and zero bucket boundary removed
Attributes: see table below

Attribute change
Comments

http.method → http.request.method
Now captures only 9 common HTTP methods by default plus _OTHER

http.status_code → http.response.status_code

net.peer.name → server.address

net.peer.port → server.port
Now captured even when same as default port for scheme

net.sock.peer.addr
Removed

net.protocol.name → network.protocol.name
Recommended → Conditionally required if not http and network.protocol.version is set

net.protocol.version → network.protocol.version
Examples fixed: 2.0 → 2 and 3.0 → 3; see note if migrating from <= v1.19.0

New: error.type

References:

Metric http.client.duration v1.20.0
Metric http.client.request.duration v1.23.0 (stable)

HTTP server duration metric
Metric changes:

Name: http.server.duration → http.server.request.duration
Unit: ms → s
Description: Measures the duration of inbound HTTP requests. →
Duration of HTTP server requests.
Histogram buckets: boundaries updated to reflect change from milliseconds
to seconds, and zero bucket boundary removed
Attributes: see table below

Attribute change
Comments

http.route
No change

http.method → http.request.method
Now captures only 9 common HTTP methods by default plus _OTHER

http.status_code → http.response.status_code

http.scheme → url.scheme
Now factors in X-Forwarded-Proto span, Forwarded#proto span headers

net.protocol.name → network.protocol.name
Recommended → Conditionally required if not http and network.protocol.version is set

net.protocol.version → network.protocol.version
Examples fixed: 2.0 → 2 and 3.0 → 3; see note if migrating from <= v1.19.0

net.host.name → server.address
• Recommended → Opt-In (due to high-cardinality vulnerability since based on HTTP headers)• Now based only on Host span, :authority span, X-Forwarded-Host span, Forwarded#host span headers

net.host.port → server.port
• Recommended → Opt-In (due to high-cardinality vulnerability since based on HTTP headers)• Now based only on Host span, :authority span, X-Forwarded-Host span, Forwarded#host span headers

New: error.type

References:

Metric http.server.duration v1.20.0
Metric http.server.request.duration v1.23.0 (stable)

Please check out #612

We discussed the impact of the http semantic convention changes to the Operator during our SIG call.  The consensus was that it is worrying haha The operator adds an extra layer of obfuscation to all the changes, which makes the release notes of the languages even more important.  I'd like to continue to push for a standardized template for all languages to use.  I also still push for each language to make it abundantly clear exactly which libraries are affected.
For the operator specifically we've created https://github.com/open-telemetry/opentelemetry-operator/issues/2542 to track our discussion on how we'll help our users understand the impact of these changes.

I also still push for each language to make it abundantly clear exactly which libraries are affected.

On this topic I'd very much like to revisit the idea of a matrix.  We created https://docs.honeycomb.io/getting-data-in/semconv/ and would very much like to contribute it somewhere(s) meaningful.

On this topic I'd very much like to revisit the idea of a matrix. We created docs.honeycomb.io/getting-data-in/semconv and would very much like to contribute it somewhere(s) meaningful.

I think that is a great starting point to adopt/follow. But I still think this should not be placed/managed in the semconv repo, but in each SDK/Instrumentation repo.

but in each SDK/Instrumentation repo.

I thinking about this problem more and more I agree.  As an end users, I should be able to look at any changelog/release and instantly comprehend that there are breaking changes that affect me. I should also be able to look at any instrumentation's documentation and instantly understand if it is emitting stable http semantic conventions or allows the use of the OTEL_SEMCONV_STABILITY_OPT_IN env variable.

We discussed this a bit in the TC.   Regarding having every language SiG provide consistent documentation on what has been broken, the following is true:

Languages were in inconsistent states of compliance w/ Semconv previously (as semconv was not stable).
Language SIGs should be responsible for updating/notifying users of breaking changes.
Semconv is responsible for updating Language SIGs on breaking changes.

Going forward, we're going to institute a policy where semconv WG's (and semconv itself) directly notifies language SIGs (via opened issues) on breaking changes and expectations.   For HTTP, e.g., this bug would include the details on what changed in semconv (from the blog post) and would ask Language SIGs to update their instrumetnation to be in compliance.   We can also call out central documentation areas where languages can contribute their migration paths.  Then it would be up to language SiGs to fill out information as they perform the migration.
We do not think we can centrally own the migration, instead relying on the current Specification Change -> Language/Collector SiG notification channel, so let's improve how that communication happens.

authors: TylerHelmuth cartermp jack-berg joaopgrassi jsuereth trask

repo: open-telemetry/semantic-conventions


text:
[PoC]of attribute ref renaming

This is a proof of concept on the viability of using renaming of attributes to duplicate the functionality of attribute embedding in https://github.com/open-telemetry/semantic-conventions/issues/1264
This adds another field to the ref attributes that allows you to rename the attribute.  This lets you import multiple copies of the same reference into an attribute group. as demonstrated in the test.
This is a Proof of Concept please don't merge.

@MadVikingGod or @trisch-me -  Are we entertaining this PoC anymore or should we close this PR as stale at this point?

As I mentioned during one of the meetings we already have working old way of embedding the attributes in weaver including renaming.
As we are moving slowly forward with embed I propose to implement everything there.

authors: MadVikingGod jsuereth trisch-me

repo: open-telemetry/weaver


text:
[docs] recommend vscode prettier plugin

I think we should recommend the vscode prettier plugin for vscode

Not stale

I agree - came here trying to figure out why the prettier config doesn't seem to do much in vscode. I'm still none the wiser - even after running  npm run format:prettier the code still looks bad.

authors: LarsDenBakker davie-robertson

repo: open-wc/open-wc


text:
Update languages.json - Addede Danish

I have added the danish languest

Looks like you forgot to include the actual translation.json file.

repo: open-webui/open-webui


text:
i18n: Update catalan translation.json

i18n: Catalan Translation updated.
Last commit with the most recentr translations did not end up in 0.3.11. Trying it again.
Cheers.

Thanks!

authors: aleixdorca tjbck


text:
Update README.md

Some clarifications on editable mode and venvs.

Perfekt. Danke.

authors: MyHomeMyData SanMiggel


text:
Shall we add explicit lines for response in im000_BequeathYourDataAndDie diagram to depict serial workflow of callbacks

As per understanding, the callbacks of /v1/bequeath-your-data-and-die happens in a serial fashion.
That is, the next callback gets processed and triggered only after the response of the previous callback is received.
Can we also depict this in diagram  with a response line to OldRelease.
I hope including this in diagram will explicitly depict the above understanding ( that the next callback gets processed and triggered only after the response of the previous callback is received)  . Kindly let me know your views.

Responses added as proposed.

authors: IswaryaaS openBackhaul

repo: openBackhaul/ApplicationLayerTopology


text:
[Code] Update oas according to newer version of Controller OAS

Current MWDI spec is still based on Controller OAS from 2022
added new OAS in #13 (07/2023)

new controller OAS may not yet include latest changes made to ltp-augment for MWDI
still only GET requests are relevant (new OAS also contains patch operation, which was not there before)
identation between old OAS and new one are different (the old file always has twice as many leading blanks as the new one)
as for the first release of MWDI there's only a limited scope of services, new services need to be added to the list for v2-0-0, but it's of no consequence if they are missing in the old list of services
components however must be modified, if there were changes!

sometimes only the order of attributes in enumerations is scrambled
not all records under components need to be kept; only those related to the control construct data (the controller supports requests unrelated to the control construct as well!)
e.g. for ALARM_TYPE_ID_TYPE lots of entries from the old OAS are no longer included, but this component might not even be needed

Es gibt einige Abweichungen, im Parser ist noch ein Fehler bei den Parametern.
In den Pfaden (und unter den Parametern) sind z.B. value-name, value-name1, value-name2, value-name3, die unter den components aber alle die exakt gleiche Beschreibung haben; also entweder wurden die fälschlicherweise angelegt (vermutlich) oder da ist was mit den Schemas schief gelaufen; in den meisten Fällen dürfte der Unterschied, wenn es einen gibt nur in der Description liegen, die aber hier ggf. falsch übernommen wurde (falls es richtig ist, dass da mehrere Instanzen angelegt wurden).
Zwischenergebnisse (nicht konsolidiert):
Zwischenergebnis.zip

Bei der geparsten alten OAS, gibt es auch local-id, local-id1 und local-id2 mit der gleichen Parameter-Definition, aber es kommt vor, dass es in bestimmten Pfaden mehrere local-ids gibt und die muss man unterscheiden können:
	/node={mount-name}/yang-ext:mount/core-model-1-4:control-construct/logical-termination-point={uuid}/embedded-clock={local-id}/encapsulated-fc={uuid1}/fc-port={local-id1}:
		parameters:
			- $ref: '#/components/parameters/mount-name'
			- $ref: '#/components/parameters/uuid'
			- $ref: '#/components/parameters/local-id'
			- $ref: '#/components/parameters/uuid1'
			- $ref: '#/components/parameters/local-id1'

Die extrahierten OASen vom Controller unterscheiden sich und sind nicht für alle Devices gleich!
Vgl. Stand 07/2023 für NEs 530253433 znd 305277070

repo: openBackhaul/MicroWaveDeviceInventory


text:
raw data - order

This is not an issue but a suggestion:
Could you order the raw data ( https://www.corona-data.ch/ ) in descending order so that the latest data/date is at the top? (headers/cantons disappear when scrolled down)

@smalos this is not the repository of corona-data.ch, the repository you're looking for is here:
https://github.com/daenuprobst/covid19-cases-switzerland

authors: metaodi smalos


text:
Error Merge cantonal CSVs

Run swinton/screenshot-website@v1.x
Uploading chunk of size 580180 bytes at offset 0 with content range: bytes 0-580179/580180
Total size of all the files uploaded is 580180 bytes
##[error]connect ETIMEDOUT 13.107.42.16:443

works again, probably just a glitch.


text:
California State Data

In contact with a few people as per a state-wide address dataset. No returned e-mails since 2/3/2017... But I did find this; perhaps a state-wide parcel dataset for residential areas?
http://services.gis.ca.gov/arcgis/rest/services/Boundaries/Parcels_Residential/MapServer/0

Just got off the phone with john - he cannot share data as per license agreement. He does have a UCD dataset of parcels with only APN field. Although this will not help us, I asked for it anyway ;)
He said several counties in the state are under agreement w third party vendor http://www.parcelquest.com/

Most the remaining small counties in California are locked up in Parcel
Quest, sadly.
On Mon, Mar 6, 2017 at 11:54 AM, Justin Meyers notifications@github.com
wrote:

Just got off the phone with john - he cannot share data as per license
agreement. He does have a UCD dataset of parcels with only APN field.
Although this will not help us, I asked for it anyway ;)
He said several counties in the state are under agreement w third party
vendor http://www.parcelquest.com/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openaddresses/openaddresses/issues/2596#issuecomment-284512476,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0EO8SF4uUQSKEXGQnfNjrQNsirsna1ks5rjGSBgaJpZM4MNfus
.

no state wide initiative (according to John) for a pacel/ address dataset.

We have almost all of the data in California anyhow.
For completeness on the 1/2 dozen missing counties it might be interesting
to get a list of addresses from the county in question, and then run them
thru Mapzen search to geocode them using the Tiger information. I suspect a
lot of address point data we get from counties start off life that way, and
then is moved onto buildings in a cleanup step. Right now this isn’t
priority.
On Mon, Mar 6, 2017 at 12:01 PM, Justin Meyers notifications@github.com
wrote:

no state wide initiative (according to John) for a pacel/ address dataset.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/openaddresses/openaddresses/issues/2596#issuecomment-284514460,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0EOwFo4PDKc3-cOlNh6JabUSseZiCNks5rjGYIgaJpZM4MNfus
.

@justinelliotmeyers I'm not sure if this data different than the what you linked to on services.gis.ca.gov so just throwing this into the mix. I've come across this statewide parcel boundary dataset before. Unfortunately, it only only contains the geometries and the parcel ID:
https://egis3.lacounty.gov/dataportal/2015/09/11/california-statewide-parcel-boundaries/
That page points to a ~3.1 GB zip file:
http://egis3.lacounty.gov/dataportal/wp-content/uploads/ShapefilePackages/Parcels_CA_2014.zip
@nvkelso I never thought about reverse geocoding to attach known address points to parcels... that's an interesting idea.

(Note that OpenAddresses is looking for primary sourced data, so I wouldn't want us to ingest generated data like geocoded address lists)

@iandees yes, I veered the discussion off course there... didn't mean to imply that was suitable for ingestion into openaddresses, but instead as a potential use of openaddresses' sourced data.

No worries. I didn't mean to halt conversation.

Stale

authors: iandees ingalls jalessio justinelliotmeyers nvkelso

repo: openaddresses/openaddresses


text:
Can not download pretrained models, logs and samples

Hi,
I tried to get the Pretrained models, logs and samples with the following command
wget https://storage.googleapis.com/glow-demo/logs/abl-[reverse/shuffle/1x1]-[add/aff].tar
but I get the following error. Could someone please help me with this?
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
BlobNotFound
<Message>The specified blob does not exist. RequestId:a3ecffb0-201e-00e2-451e-3ce1ee000000 Time:2021-04-28T11:03:31.4383873Z</Message>
</Error>

I have the same question

following

It seems the authors have moved the data to a different server.
I found the checkpoints under
wget https://openaipublic.azureedge.net/glow-demo/logs/abl-1x1-add.tar  # additive coupling blocks
wget https://openaipublic.azureedge.net/glow-demo/logs/abl-1x1-aff.tar  # affine coupling blocks
# etc for the other ablations

authors: LeeeLiu ardizzone mkhoshle nsping13

repo: openai/glow


text:
Issue with custom transport

Confirm this is an issue with the Python library and not an underlying OpenAI API

[X] This is an issue with the Python library

Describe the bug
So, I'm trying to resolve https://github.com/pyodide/pyodide/issues/4292
With these fixes in place: https://github.com/urllib3/urllib3/pull/3195, https://github.com/encode/httpx/discussions/2994, and the custom transport feature in the library the solution is more feasible.
To Reproduce
Testing environment: https://jupyter.org/try-jupyter/lab/
import micropip
await micropip.install('https://raw.githubusercontent.com/psymbio/pyodide_wheels/main/multidict/multidict-4.7.6-py3-none-any.whl', keep_going=True)
await micropip.install('https://raw.githubusercontent.com/psymbio/pyodide_wheels/main/frozenlist/frozenlist-1.4.0-py3-none-any.whl', keep_going=True)
await micropip.install('https://raw.githubusercontent.com/psymbio/pyodide_wheels/main/aiohttp/aiohttp-4.0.0a2.dev0-py3-none-any.whl', keep_going=True)
await micropip.install('https://raw.githubusercontent.com/psymbio/pyodide_wheels/main/openai/openai-1.3.7-py3-none-any.whl', keep_going=True)
await micropip.install('https://raw.githubusercontent.com/psymbio/pyodide_wheels/main/urllib3/urllib3-2.1.0-py3-none-any.whl', keep_going=True)
await micropip.install("ssl")
import ssl
await micropip.install("httpx", keep_going=True)
import httpx
await micropip.install('https://raw.githubusercontent.com/psymbio/pyodide_wheels/main/urllib3/urllib3-2.1.0-py3-none-any.whl', keep_going=True)
import urllib3
urllib3.disable_warnings(urllib3.exceptions.InsecureRequestWarning)
import json

class URLLib3Transport(httpx.BaseTransport):
    def __init__(self):
        self.pool = urllib3.PoolManager()

    def handle_request(self, request: httpx.Request):
        urllib3_response = self.pool.request('GET', str(request.url))  # Convert httpx.URL to string
        content = json.loads(urllib3_response.data.decode('utf-8'))  # Decode the data and load as JSON
        stream = httpx.ByteStream(json.dumps(content).encode("utf-8"))  # Convert back to JSON and encode
        headers = [(b"content-type", b"application/json")]
        return httpx.Response(200, headers=headers, stream=stream)

client = httpx.Client(transport=URLLib3Transport())
from openai import OpenAI

openai_client = OpenAI(
    base_url="https://api.openai.com/v1",
    api_key="xxx",
    http_client=client
)
response = openai_client.chat.completions.with_raw_response.create(
    messages=[{
        "role": "user",
        "content": "Say this is a test",
    }],
    model="gpt-3.5-turbo",
)
completion = response.parse()
print(completion)

But I get this output:
ChatCompletion(id=None, choices=None, created=None, model=None, object=None, system_fingerprint=None, usage=None, error={'message': "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.", 'type': 'invalid_request_error', 'param': None, 'code': None})

I have provided the API key - so what am I doing wrong here?
Code snippets
No response
OS
Pyodide
Python version
Python v3.11.3
Library version
openai v1.3.7

Hi @psymbio , thanks for sharing your findings. Unfortunately we can't commit to providing support to help debug issues with user code in this way.
In this case, this line looks suspect to me:
urllib3_response = self.pool.request('GET', str(request.url))

You don't seem to be passing the request headers along here (or the body, and the method looks incorrect as well).
If you need further help from here, you may be able to ask fellow developers in the OpenAI Discord server.

You were right, thanks!
The correct way of doing it was:
class URLLib3Transport(httpx.BaseTransport):
    def __init__(self):
        self.pool = urllib3.PoolManager()

    def handle_request(self, request: httpx.Request):
        payload = json.loads(request.content.decode("utf-8").replace("'",'"'))
        urllib3_response = self.pool.request(request.method, str(request.url), headers=request.headers, json=payload)  # Convert httpx.URL to string
        content = json.loads(urllib3_response.data.decode('utf-8'))  # Decode the data and load as JSON
        stream = httpx.ByteStream(json.dumps(content).encode("utf-8"))  # Convert back to JSON and encode
        headers = [(b"content-type", b"application/json")]
        return httpx.Response(200, headers=headers, stream=stream)

authors: psymbio rattrayalex

repo: openai/openai-python