text:
questions for mistral

Hi.
How do I get him to respond in only one language?
And how to remove the censorious language from him so that he can express himself obscenely?

How do I get him to respond in only one language?
Your prompt should tell 'him' that

And how to remove the censorious language from him so that he can express himself obscenely?

Which mistral model are you using? The last I checked, the mistral default models aren't censored

How do I get him to respond in only one language?

Your prompt should tell 'him' that

And how to remove the censorious language from him so that he can express himself obscenely?

Which mistral model are you using? The last I checked, the mistral default models aren't censored

I used 'ollama run mistral', is this the latest version?

I used 'ollama run mistral', is this the latest version?

Yes, that'll be the latest version

authors: VadimBoev seanmavley

repo: ollama/ollama


text:
feat: implemented a model export cli command

First pass at solving #335. Converted the bash script provided by supersonictw to golang.
Export a model by running ollama export <model> <output>. For example ollama export llama3:latest llama-backup.

Glad to see this export feature coming up. Any update on it? What shall we do to make it an official feature?

source: gharchive/pull-request

authors: JerrettDavis xinzweb

license: MIT

license_type: permissive

license_source: github-api


text:
remaining time sensor unavailable

I have a weird issue with my washer\dryer where the remaining time and initial time sensors are unavailable in HA but when I use the custom component it shows the time correctly and the progress bar.
why is that?

This is the same of issue #415 (and not a real issue)
Remaining time sensor is not unavailable but disabled, if you need that sensor just enable via UI.
The custom card use main sensor attributes and not dedicated sensor, for this reason the progress bar is properly displayed.
I close this.

source: gharchive/issue


text:
Fix for #156

Don't set xoauth_displayname for registered Google OAuth applications. Refs #156.

Tip of the hat to DanGer in #django for the proposed fix.

repo: omab/django-social-auth

license_source: bigquery


text:
Is it possible to reload the model viewer with setstate?

Describe the solution you'd like
If we can have our own webview controller assigned to the model-viewer, so we can re-render the model after changing the parameters

@Foldblade any update?

any update on this, I'm also stuck on animation updation by a button click. I've glb model inside animation want to update on Button Tap

My answer on this thread may help, you may need to play around with some of the Javascript to adjust different values though.
https://github.com/omchiii/model_viewer_plus.dart/issues/66#issuecomment-1431915525

authors: Aliasad9 AqeelAaqi JudahMcNicholl


text:
🛑 OME training server 2 is down

In edf9c74, OME training server 2 (https://workshop.openmicroscopy.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OME training server 2 is back up in 76c6fa3 after 18 minutes.

repo: ome/upptime


text:
Split demo in slots

Update day1 demos section

Merging and deploying before sending emails to participants doing demo


text:
Add new currencies

Add new currencies from the API's.

Added 6 new currencies in pull request #4

PS: Could you put a CONTRIBUTE file or make a contribution guide, it's better for contributors :)

Added all currencies available on the API in pull request #5

@Norech I am creating new issue :)

authors: Norech drowolath omergulen

repo: omergulen/telegram-currency-bot


text:
Intermodal containers

[x] Models
[x] Icons
[x] Doc
[x] Log

test me

👍

Build Passed :ok_hand:
You can safely merge 'feature-intermodal-containers' into 'develop'.

I took into consideration your comments except the rename of IntermodalOfficeContainer which appears to be less precise to me. The "intermodal" keyword is there to define the dimensions of the container. Let me know if you would like to change it and I will do it.

I checked google images for "intermodal office container" and "office container". It's true that the intermodal version is more precise on the container size, so that's probably a better choice.

repo: omichel/webots


text:
Merge master into revision

This should fix the change log link in the GitHub releases (we should also merge revision into develop subsequently).

Oops. There is a small conflict...


text:
Column filter

I changed the templates so the column filter will work again.
Also i changed the behavior of a text search, that will search now for parts not the exact value.
Feel free to merge this to have this functionality back!

@kathibeepboop What is the reason you closed this PR?

@kathibeepboop What is the reason you closed this PR?

I've decided to close this merge request due to the conditions set by the repository owner, who has requested a change in the package name before proceeding with any review. Given that this change requires significant effort and I am already using my fork, I believe it's more practical for me to continue with my current setup.

Do you mind if I re-submit your PR with the proposed changes?

Absolutly not! Feel free to use everything i did in the PR or in my fork as welll

I'm happy to review anything, it's just that I cannot accept changes that would break the release process of the bundle like the name   😉
I've actually RC'd an update yesterday for ORM 3 and DBAL 4 compatibility. We might want to shove this change in the 0.9 as well.

repo: omines/datatables-bundle


text:
Type unstable Data.Number

Was running some tests and just realised that Data.Number appears to be type unstable. E.g. :
julia>
       function foo(nx, ny)
           A_eff = (8*2)/1e9*nx*ny*sizeof(Data.Number)
       end
foo (generic function with 2 methods)

julia> @btime foo($20,$20)
  66.888 ns (2 allocations: 32 bytes)
5.12e-5

with

julia> @code_warntype foo(20, 20)
MethodInstance for foo(::Int64, ::Int64)
  from foo(nx, ny) @ Main ~/Desktop/Boris/MagmaThermoKinematics.jl/HydroMech2D_arrays.jl:289
Arguments
  #self#::Core.Const(foo)
  nx::Int64
  ny::Int64
Locals
  A_eff::Any
Body::Any
1 ─ %1 = (8 * 2)::Core.Const(16)
│   %2 = (%1 / 1.0e9)::Core.Const(1.6e-8)
│   %3 = Main.Data.Number::Any
│   %4 = Main.sizeof(%3)::Any
│   %5 = (%2 * nx * ny * %4)::Any
│        (A_eff = %5)
└──      return %5

@albert-de-montserrat Thanks for catching this! Making the type declarations in the Data module constant solves this:
julia> using ParallelStencil
[ Info: Precompiling ParallelStencil [94395366-693c-11ea-3b26-d9b7aac5d958]

julia> @init_parallel_stencil(package=Threads, numbertype=Float64)

julia> function foo(nx, ny)
                  A_eff = (8*2)/1e9*nx*ny*sizeof(Data.Number)
              end
foo (generic function with 1 method)

julia> @code_warntype foo(20, 20)
MethodInstance for foo(::Int64, ::Int64)
  from foo(nx, ny) @ Main REPL[4]:1
Arguments
  #self#::Core.Const(foo)
  nx::Int64
  ny::Int64
Locals
  A_eff::Float64
Body::Float64
1 ─ %1 = (8 * 2)::Core.Const(16)
│   %2 = (%1 / 1.0e9)::Core.Const(1.6e-8)
│   %3 = Main.Data.Number::Core.Const(Float64)
│   %4 = Main.sizeof(%3)::Core.Const(8)
│   %5 = (%2 * nx * ny * %4)::Float64
│        (A_eff = %5)
└──      return %5

PR coming up...

Great thanks!

authors: albert-de-montserrat omlins


text:
load dataset

Hi, Could you elaborate on the data structure foe me? I want to train my own dataset, thank you!
train_set = '/home/lkang/datasets/syn_60000_words/subset_20305words.txt' # 20305 words source domain
valid_set = '/home/lkang/datasets/iam_final_words/RWTH.iam_word_gt_final.valid.thresh'
test_set = '/home/lkang/datasets/iam_final_words/RWTH.iam_word_gt_final.test.thresh'
my source domain as train_set *****.jpg label
target domain are only images, not labels.

Hi,
Currently I am faced with the exact question that you had posted quite some time ago, I was wondering if you could figure it our eventually ?

repo: omni-us/research-WriterAdaptation-HTR


text:
Duplicate methods

It seems you guys may have merged branches inappropriately at some point. For example, there are duplicate def read_image_and_gt_with_original(img_files, gt_files, config): in dataGenerator.py

Thanks. When I have time I will change it.

authors: Sileadim mistiansen

repo: omni-us/squeezedet-keras


text:
[WIP] Skip building sphinxcontrib packages on win

Apparently, we can't build noarch packages on win:
[noarch_python] Error: Python noarch packages can currently not be created on Windows systems.

This PR skips builds of the new sphinxcontrib-* packages on win.

Though I wonder if the noarch thing is the reason these packages are not being uploaded.  They seem to be the only ones with noarch_python: True.

repo: omnia-md/conda-recipes

license: mit


text:
Document node interpolation (for non-leaf nodes)

This is a follow-up to https://github.com/omry/omegaconf/commit/5f471ecbb6105ea5a1f7f4b422e7cd75499f0de8#r46668217

looks like the build failures are from the docs (wrong string quotes). can you address?

Oops, hopefully should be ok now

authors: odelalleau omry

repo: omry/omegaconf


text:
The drop down menu for 'type' does not have more than 5 options

I see in the video that the dropdown menu for type contains many more options such as 4 options for  DATE & TIME, 4 options for NUMERIC, etc.
I only see these options for type: Text, Numeric, Integer, Real, None.
I'd like to be able to choose DATE
Please advise
using chrome, sqlite, ad block diabled

I see that it is a chrome issue, as more of the dropdown options for type are showing in Firefox.
However cookies for the site are enabled.

The data type selection is database-specific, so you will see different data types available for different database types. In your case, SQLite has only five data types (fun fact: those are not real data types; instead, SQLite uses the concept of data affinity). If you switch your DB to a different one, reload the app and start a new design, you should see a different data type set.
Sanity check: open the blank wwwsqldesigner page using a private browsing window. You should see the default (MySQL) data type selection.

authors: ondras sobopla

repo: ondras/wwwsqldesigner


text:
Fix growthbook chart ingress secret name

Proposed changes
This PR fixes the following issue: https://github.com/one-acre-fund/oaf-public-charts/issues/161.
The ingress template has an unset variable for the secretName which is causing this problem.
Checklist

[ ] Lint and unit tests pass locally with my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have added documentation to describe my feature.
[x] I have squashed my commits into logic units.
[x] I have described the changes in the commit messages.

Other information

@bisonlou @Yann-J @nzeugaa could you please take a look?

repo: one-acre-fund/oaf-public-charts


text:
FPGA new code sample - board_test

Adding a New Sample(s)
Description
board_test added to reference designs for FPGA. The test is for FPGA platform developers to check board interfaces and measure board metrics like host to device memory bandwidth, kernel to memory bandwidth, kernel clock frequency and kernel launch latency.
Checklist
Administrative

[X] Reviewed sample design with the appropriate Domain Expert: Yohann Uguen
[ ] If you have any new dependencies/binaries, inform the oneAPI Code Samples Project Manager

Code Development

[X] Implement coding guidelines and ensure code quality. see wiki for details
[X] Adhere to readme template
[X] Enforce format via clang-format config file
[X] Adhere to sample.json specification. https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-specification
[X] Ensure/create CI test configurations for sample (ciTests field) https://github.com/oneapi-src/oneAPI-samples/wiki/sample-json-ci-test-object
[X] Run jsonlint on sample.json to verify json syntax. www.jsonlint.com

Security and Legal

[ ] OSPDT Approval (see Project Manager for assistance)
[X] Compile using the following compiler flags and fix any warnings, the flags are: "/Wall -Wformat-security -Werror=format-security"
[ ] Bandit Scans (Python only)
[ ] Virus scan

Review

[ ] Review DPC++ code with Paul Peterseon. (GitHub User: pmpeter1)
[ ] Review readme with Tom Lenth(@tomlenth) and/or Project Manager
[X] Tested using Dev Cloud when applicable

Adding @tomlenth for the new README and @pmpeter1 for the SYCL code as this is a new sample.
Thanks!

I'm going to merge this commit, even without @pmpeter1 review because of internal deadlines.
Please still review the PR and we will implement your suggestions in a separate "fix" PR.

authors: aktole yuguen-intel

repo: oneapi-src/oneAPI-samples


text:
Upgrade rb-readline to version 0.5.1

See also https://github.com/luislavena/rb-readline/compare/v0.5.0...v0.5.1

I think that this is more or less outdated, since I had to build off the master branch for 2.2.
If I'm wrong let me know.

authors: Azolo tikkss

repo: oneclick/rubyinstaller


text:
not able to map AD groups in a 'memberOf' attribute to roles

With a configuration that is otherwise working (using 3.1.0), we are auto-provisioning users successfully. I am now trying to map wordpress roles based on AD group membership. For this example, trying to map a group being sent in the SAML response from my IdP to WP Editor. We have the attribute "memberOf" which is recursively sending all applicable AD groups for the user, each on a new attribute value line as follows:
...
			<saml2:Attribute Name="memberOf"
                NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:unspecified">
                <saml2:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">CN=Group.one,OU=Managed,OU=All Lists,DC=ad,DC=company,DC=com</saml2:AttributeValue>
                    <saml2:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">CN=Group.two,OU=Managed,OU=All Lists,DC=ad,DC=company,DC=com</saml2:AttributeValue>
                    <saml2:AttributeValue xmlns:xs="http://www.w3.org/2001/XMLSchema"
                    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="xs:string">CN=Group.three,OU=Managed,OU=All Lists,DC=ad,DC=company,DC=com</saml2:AttributeValue>
            </saml2:Attribute>
...

In the plugin settings I have:
Update User Data: Checked
Role: memberOf
Editor: CN=Group.two
Multiple Values: checked
Regular expression: /CN=([^,;]*)/
According to my research, testing this regex against the above SAML response results in a list as follows:
CN=Group.one
CN=Group.two
CN=Group.three

So, I was expecting my mapping of "CN=Group.two" to have the affect of updating a subscriber to Editor. However, it appeared not to do anything at next login. Later, I discovered that it has been RESETTING my user back to the default Subscriber no matter what (I can manually assign ADMIN, let the user login, and they get pushed to subscriber. I need to turn off Update User Data). Found Issue #86 that says the forced default is fixed in v3.1.1, but that version is not yet appearing in the Wordpress plugins repo. Is it stil in beta? Regardless, I am thinking it is not finding a value match to do the mapping properly.
So my question is, What should I try next? Is my SAML response an odd one? Do I need a better regex? Should I ask my IdP admin to reconfigure and supply the AD groups in just a single, comma-delimited value expression? should I have them strip out the CN=? What is the best way to set this up? Should I wait until I have 3.1.1 installed?
I turned on debugging in the plugin, but I cannot see messages. Where do logs go? I am using a Chrome plugin to view the SAML responses.
Thanks

Following up on this issue. . .
We were able to "unite" our 'memberOf' attribute values to get them into a SINGLE attribute value string, comma-delimited. Then, using the example/suggested regex, it parses the AD groups out of this single, long string value.
So, the answer for us was to have ALL AD groups listed together as a single value string.

@caver01 - How did you go about turning the multi-entry memberOf into a SINGLE attribute value string?  Can you provide your IdP filter/definition?

Sorry, the idp configuration was handled by another department, but they were able to do it. I know that does not help you. There are other attributes comma-delimited in the response string (so not perfect) but I was still able to pull the matching group name for a given role, so it worked.

repo: onelogin/wordpress-saml


text:
Gradient CImageProcessor

Hi,
I'm trying to create a gradient generator, using CIImage Filters.
I'm using the CIImageProcessor processor wrapper, but I didn't find how can I pass some parameters like the gradient colors and positions.
The code for achieving gradients is like this.
`struct GradientFilter: CIImageProcessor {
let identifier = "com.domain.CILinearGradient"

let filter = Filter { input in

    guard let colorFilter = CIFilter(name: "CILinearGradient") else { return nil }

    let startColor = CIColor(cgColor: UIColor.redColor.cgColor)
    var endColor = CIColor(cgColor: UIColor.clear.cgColor)
    var startVector = CIVector(x: 0, y: 0)
    var endVector = CIVector(x: input.extent.size.width, y: 100)

    colorFilter.setValue(startVector, forKey: "inputPoint0")
    colorFilter.setValue(endVector, forKey: "inputPoint1")
    colorFilter.setValue(startColor, forKey: "inputColor0")
    colorFilter.setValue(endColor, forKey: "inputColor1")

    let colorImage = colorFilter.outputImage
    let filter = CIFilter(name: "CISourceOverCompositing")!
    filter.setValue(colorImage, forKey: kCIInputImageKey)
    filter.setValue(input, forKey: kCIInputBackgroundImageKey)
    return filter.outputImage?.cropping(to: input.extent)

}

}`
I'm calling it like this.
processor = GradientFilter()
But I would like adding some parameters.
processor = GradientFilter(startColor: .red, endColor: .blue, startPosition: CGPoint(x:0,y:0), endPosition: CGPoint(x:0,y:1))
Thanks so much

Maybe you mean something like this?
struct GradientFilter: CIImageProcessor {

    let startColor: UIColor
    let endColor: UIColor

    let startVector: CIVector
    let endVector: CIVector

    var identifier: String {
        return "com.domain.CILinearGradient_#{startcolor}_#{endcolor}_#{startvector}_#{endvector}"
    }

    var filter: Filter {
        return Filter {
            input in
            guard let colorFilter = CIFilter(name: "CILinearGradient") else { return nil }

            let startColor = CIColor(cgColor: self.startColor.cgColor)
            let endColor = CIColor(cgColor: self.endColor.cgColor)

            colorFilter.setValue(self.startVector, forKey: "inputPoint0")
            colorFilter.setValue(self.endVector, forKey: "inputPoint1")
            colorFilter.setValue(startColor, forKey: "inputColor0")
            colorFilter.setValue(endColor, forKey: "inputColor1")

            let colorImage = colorFilter.outputImage
            let filter = CIFilter(name: "CISourceOverCompositing")!
            filter.setValue(colorImage, forKey: kCIInputImageKey)
            filter.setValue(input, forKey: kCIInputBackgroundImageKey)
            return filter.outputImage?.cropping(to: input.extent)
        }
    }
}

Please note that the identifier property should be identical, which says, for every combination of the startColor, endColor, startVector and endVector, the identifier should be different. Or Kingfisher will be confused when retrieving the images from cache.

Wow, that was it!!
thanks so much.

authors: mixmastertube onevcat

repo: onevcat/Kingfisher


text:
Add NSTextAttachment support

A better version of #1240

hello, i updated kingfisher library but can not find kf extension to NsTextAttachment

authors: fukemy onevcat


text:
Incorrect indentation

Let's say I have the following piece of code:
public enum LogLevel: Int {
	case Verbose
	case Debug
	case Info
	case Warn
	case Error
	case Off

	var code: String {
		let code = "\(self)"
		return String(code[code.startIndex])
	}
}

Now when I add a newline above var code: String { and type the /// shortcut, the indentation jumps a bit too far to the right:
public enum LogLevel: Int {
	case Verbose
	case Debug
	case Info
	case Warn
	case Error
	case Off

		/// <#Description#>
	var code: String {
		let code = "\(self)"
		return String(code[code.startIndex])
	}
}

The same also happens when I try to comment an instance variable of a class.
`class ViewController: UIViewController {
/*************************************************************/
// MARK: Instance Variables
/*************************************************************/

    /// <#Description#>
private var player: AVPlayer?

private let locationManager = CLLocationManager()`

The description moves extra tab.

It seems that the new version of Xcode adding the indentation before a pasting automatically. I will give it a fix soon.

@onevcat Thanks! Waiting for the fix!

Should be fixed in master.

authors: Zyphrax footyapps27 onevcat

repo: onevcat/VVDocumenter-Xcode


text:
feat(npm)!: use category "duration" for transition

Purpose
Instead of having a "transition" as a category, better to have "duration" one where all durations could be described.
For example:
--ods-duration-transition: 0.15s;
--ods-duration-animation: 0.3s;
// etc.

Such then we can group together when building a preview of all tokens (ongoing work).
Approach
Set a category to be "duration", and name of a property to be "transition".
Testing
Inspecting built npm files.
Risks
A breaking change for token --ods-transition-duration to have been renamed to --ods-duration-transition is addressed in a commit message.
Probably so far it is only used in Castor components.

What if we need transition-timing-function and transition-delay?
Wouldn't grouping them make sense too?
Also, we could probably get away with a single token and use multipliers, e.g.
--ods-duration-transition: 0.15s;
transition-duration: (calc(var(--ods-duration-transition) * 2));

Not sure how beneficial that is, since we'll be locked to a single variable.

I suppose let's wait for a 2nd such/similar token, then we can decide.
Putting this on hold for now.

authors: josokinas rabelloo

repo: onfido/castor-tokens


text:
chore: optimising sideEffect for importing CSS

Purpose
CSS can't be sideEffect free as it does not have an export, therefor when importing css into JS you lose it during the build process.
Approach
Excluding it from tree shaking.
Testing
N/A
Risks
There is no risk, apart from an effect on bundle size

To clarify, this is because Gatsby (and probably webpack) will tree-shake import '@onfido/castor/dist/castor.css'; out.
https://github.com/gatsbyjs/gatsby/issues/19446
Arguably, the side-effect is introduced by the bundler when it decides that a CSS import requires a DOM element to be created, not the import itself.
But semantics.
I do believe this is a good change overall, improves the lives of Gatsby/webpack users.

Such change is also needed on https://github.com/onfido/castor-tokens/tree/main/packages/npm package, which Castor is using behind the scenes.

authors: josokinas rabelloo zoeradkani

repo: onfido/castor


text:
v0.3.0 not supported on Linux

Hi! I just saw this project on the GUI list for NeoVim and decided to try it.
This is what I see on launch:
The output of nvim --version is:
NVIM v0.3.0-1063-g51af911a2
Build type: RelWithDebInfo
LuaJIT 2.0.5
Compilation: /usr/bin/gcc-5 -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -O2 -g -DMIN_LOG_LEVEL=3 -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -Wno-array-bounds -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -I/home/travis/build/neovim/bot-ci/build/neovim/build/config -I/home/travis/build/neovim/bot-ci/build/neovim/src -I/home/travis/build/neovim/bot-ci/build/neovim/.deps/usr/include -I/usr/include -I/home/travis/build/neovim/bot-ci/build/neovim/build/src/nvim/auto -I/home/travis/build/neovim/bot-ci/build/neovim/build/include
Compiled by travis@travis-job-ba9c2c6a-1035-4108-a5b3-def5d86b930b

Features: +acl +iconv +jemalloc +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "
/home/travis/build/neovim/bot-ci/build/neovim/build/nvim.AppDir/usr/share/nvim
"

Run :checkhealth for more info

I am running GalliumOS 2.1 (Ubuntu 16.04).
Let me know if there is any other information needed!

You need to update to Oni v0.3.4
Duplicate of #2105

Yep, that seemed to fix it. Thanks!

authors: DeltaEvo tilda

repo: onivim/oni


text:
ordering of channels, height , width

I wish to convert from keras to onnx,
My order is HWC [ Height, Width, Channels ] instead of CHW [ Channels, Height, Width]
How to specify this change of order while converting?

You only need specify channel_first_inputs in convert_keras, otherwise you don't need specify.

repo: onnx/keras-onnx


text:
Error when using separated krnl.iterate

I tested the following simple code:
func @simple_unroll(%arg0 : memref<8xf32>) {
  %ii = krnl.define_loops 1
  %ii1, %ii2 = krnl.block %ii 2 : (!krnl.loop) -> (!krnl.loop, !krnl.loop)
  krnl.unroll %ii2 : !krnl.loop
  krnl.iterate(%ii1) with (%ii -> %i = 0 to 8) {
    krnl.iterate(%ii2) with () {
      %i2 = krnl.get_induction_var_value(%ii2) : (!krnl.loop) -> index
      %foo = arith.addi %i2, %i2 : index
    }
  }
  return
}

When lowering to affine using convert-krnl-to-affine, I got:

onnx-mlir-opt: /home/tungld/dl/llvm-project/mlir/include/mlir/IR/OpDefinition.h:803: mlir::Block* >mlir::OpTrait::SingleBlock::getBody(uns
igned int) [with ConcreteType = mlir::AffineForOp]: Assertion `!region.empty() && "unexpected empty region"' failed.
PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace.

However, there is no problem if we use a singe krnl.iterate for %ii1 and %ii2, like this:
func @simple_unroll(%arg0 : memref<8xf32>) {
  %ii = krnl.define_loops 1
  %ii1, %ii2 = krnl.block %ii 2 : (!krnl.loop) -> (!krnl.loop, !krnl.loop)
  krnl.unroll %ii2 : !krnl.loop
  krnl.iterate(%ii1, %ii2) with (%ii -> %i = 0 to 8) {
    %foo = arith.addi %i, %i : index
  }
  return
}

I wonder if this is a bug or my way of writing that code is not recommended. @AlexandreEichenberger @tjingrant any thought?

@tungld currently the Krnl lowering is very finicky. What is missing here is the permute, in the first pattern. I found that for N nested loop with M unrolled loops, you need to declare all N together, then block, then have one permute with all of the N+M loop, even if some loops are not permuted and/or blocked, then one kernel iterate with if possible all of the bounds (safer that way), and then the loops.

The hope is that there might be a pattern that satisfies all conditions; I have currently a PR #981 that tries to use @tjingrant latest suggestion #688 but I think some pattern may not fit, to be determined yet.

func @simple_unroll(%arg0 : memref<8xf32>) {
  %ii = krnl.define_loops 1
  %ii1, %ii2 = krnl.block %ii 2 : (!krnl.loop) -> (!krnl.loop, !krnl.loop)
  krnl.unroll %ii2 : !krnl.loop
  krnl.iterate(%ii1) with (%ii -> %i = 0 to 8) {
    krnl.iterate(%ii2) with () {
      %i2 = krnl.get_induction_var_value(%ii2) : (!krnl.loop) -> index
      %foo = arith.addi %i2, %i2 : index
    }
  }
  return
}

This looks like a bug, %ii2 is marked as unroll so there is not AffineForOp for krnl.iterate(%ii2). Now krnl.get_induction_var_value(%ii2) will look for the induction variable of the corresponding AffineForOp, but AffineForOp does not exist, so empty region.

I believe you may need a permute because of the block, try it to see if it helps

I believe you may need a permute because of the block, try it to see if it helps

Thanks for your suggestion! I tried with permute but still got the same error. Now I know it is because unroll does not work well with get_induction_var. I am in the middle fixing the bug and can be partially generate code (without permute).

authors: AlexandreEichenberger tungld

repo: onnx/onnx-mlir


text:
Enable IsInf Positive and Negative Backend Tests

I was able to write the code to ensure the backend tests for both isinf_positive and isinf_negative pass. Also ensured the original path for simply isinf does not fail as well. Thank you so much to all who have helped me in this process. I have learned so much and very thankful that I continue to grow. Please provide your valuable feedback. Thanks!!!

Jenkins Linux ppc64le Build #10374 [push] Enable IsInf Positive an... started at 14:02

Jenkins Linux s390x Build #11327 [push] Enable IsInf Positive an... started at 13:56

Jenkins Linux amd64 Build #11317 [push] Enable IsInf Positive an... started at 12:57

Jenkins Linux amd64 Build #11317 [push] Enable IsInf Positive an... passed after 1 hr 13 min

Jenkins Linux s390x Build #11327 [push] Enable IsInf Positive an... passed after 1 hr 40 min

Jenkins Linux ppc64le Build #10374 [push] Enable IsInf Positive an... passed after 1 hr 58 min


text:
Parallel tune: go CPU parallel only when loops have enough work (systematically)

Added tests before setting a loop to parallel (when enabled). If not enough work is present, then no parallel is generated.
This is a first step; in a follow on PR, will try to exploit inner loop parallelism when profitable too.

Jenkins Linux amd64 Build #14961 [push] Parallel tune: go CPU pa... started at 07:59

Jenkins Linux ppc64le Build #13991 [push] Parallel tune: go CPU pa... started at 09:08

Jenkins Linux s390x Build #14966 [push] Parallel tune: go CPU pa... started at 08:59

Jenkins Linux amd64 Build #14961 [push] Parallel tune: go CPU pa... passed after 1 hr 8 min

Jenkins Linux ppc64le Build #13991 [push] Parallel tune: go CPU pa... aborted after 1 hr 16 min

Jenkins Linux s390x Build #14966 [push] Parallel tune: go CPU pa... aborted after 1 hr 16 min

authors: AlexandreEichenberger jenkins-droid


text:
[WIP] Initial version of support-instance-normalization

I will be adding the mlir tests to this. It has passed 32 tests in the local, 1 unsupported.

@xintin is this still WIP?

@xintin is this still WIP?

Can one of the admins verify this patch?

authors: caoimhinuibrian jenkins-droid xintin


text:
Fix instrument error on windows

Signed-off-by: Tong Chen chentong@us.ibm.com
The OM runtime library used libraries not available on windows. This temporary fix added #ifdef _WIN32' with TO BE FIXED` comment.
When instrumentation part becomes mature, we will add the corresponding part for windows.

@chentong319
new error, apparently:
:\a\1\onnx-mlir\src\Runtime\OMInstrument.inc(36,10): fatal error C1083: Cannot open include file: 'unistd.h': No such file or directory (compiling source file D:\a\1\onnx-mlir\src\Runtime\OMInstrument.c) [D:\a\1\onnx-mlir\build\src\Runtime\cruntime.vcxproj]

Fixed that one, hopefully. We need a windows env.

@chentong319 When did you push your latest changes? It is 9:15 am July 15th, and Windows CI shows 1h20 of computations.

Jenkins Linux s390x Build #1472 [push] Fix instrument error on ... started at 09:55

Jenkins Linux ppc64le Build #612 [push] Fix instrument error on ... started at 09:59

Jenkins Linux amd64 Build #1474 [push] Fix instrument error on ... started at 08:55

Jenkins Linux s390x Build #1472 [push] Fix instrument error on ... passed after 42 min

Jenkins Linux amd64 Build #1474 [push] Fix instrument error on ... passed after 51 min

Jenkins Linux ppc64le Build #612 [push] Fix instrument error on ... passed after 55 min


text:
Update reqwest to 0.9.x

Older reqwest versions depends on an old openssl crate which does not work with openssl 1.1.1.
I believe I have not introduced any new panics.
Fixes #43

This patch is solving the same issue on my env :+1:

Any chance this is going to be accepted, so something similar?

authors: clopnis droundy janderholm

repo: onur/acme-client


text:
🛑 Tooty.xyz is down

In 6bf46b0, Tooty.xyz (https://tooty.xyz) was down:

HTTP code: 403
Response time: 111 ms

Resolved: Tooty.xyz is back up in 56b95c2.


text:
Fix pcm-tsx-win BSOD

Testing pcm-tsx with a Jaketown processor caused the machine to blue screen due to memory corruption. Crash dump analysis determined this was whilst writing to MSR 0x187 (IA32_PERFEVTSEL1). On earlier architectures bit 32 is part of the reserved range whilst in Haswell and later it is the IN_TX value. pcm-tsx wrote to that bit on all architectures. Only setting that bit when it is on a supported architecture ensures that running the tool on an older architecture does not have an adverse impact.
This has been implemented as a white list of architectures as the "Intel 64 and IA-32 Software Developer's Manual: Volume 4" does not offer an explicit flag for that register but instead describes the architectures on which it applies.

Thanks for the PR. Pcm tsx checks if RTM (TSX) is supported using cpuid instruction BUT after programming PMU. That's the problem. I think a more robust resolution is to move this code before PCM program().instead. Could you please submit a new PR?

@ogbrugge please review

I have raised #144 which instead relocates the current checking code.

authors: alwaysbusy opcm

repo: opcm/pcm


text:
Inputs need to be passed to child ops even though they are defaulted in the child ops

The parent op is forced to send inputs to child ops, even though there are defaults set.

lol.. so @aserplus includes two reactions

authors: SudhindraKovalam chrisdostert

repo: opctl/opctl


text:
Release v1.4.0

@JuliaRegistrator register
Release notes:
What's Changed

Result store update by @DanTanAtAims in https://github.com/open-AIMS/ReefModEngine.jl/pull/18
rename scenario factors to be consistent with ReefModEngine by @DanTanAtAims in https://github.com/open-AIMS/ReefModEngine.jl/pull/19
rename cubes for ADRIA compatability by @DanTanAtAims in https://github.com/open-AIMS/ReefModEngine.jl/pull/20
Handle cases where there are no intervention scenarios by @ConnectedSystems in https://github.com/open-AIMS/ReefModEngine.jl/pull/22
Update documentation by @DanTanAtAims in https://github.com/open-AIMS/ReefModEngine.jl/pull/21

New Contributors

@DanTanAtAims made their first contribution in https://github.com/open-AIMS/ReefModEngine.jl/pull/18

Full Changelog: https://github.com/open-AIMS/ReefModEngine.jl/compare/v1.3.0...v1.4.0

Registration pull request created: JuliaRegistries/General/116871
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v1.4.0 -m "<description of version>" 40a68d6e986968994edeb8e9b55a34c43baf76a3
git push origin v1.4.0

authors: ConnectedSystems JuliaRegistrator


text:
Add authorization to the compliance event API endpoints

I need to ensure that the compliance history can only be written by authorized service accounts and viewed by users with appropriate ACM access.
Definition of Done for Engineering Story Owner (Checklist)

The read API endpoint is restricted based on a user's "get" access to corresponding ManagedCluster objects. This result will filter the requests returned in the SQL queries.
The write API endpoint must require the service account to have "patch" access to the "status" subresource of a policy in the corresponding managed cluster namespace.

Ref: https://issues.redhat.com/browse/ACM-6866
Signed-off-by: Yi Rae Kim yikim@redhat.com

I think we need to figure out the service account stuff for the tests.

SubjectAccessReview needs clusterrole or role so if the user doesn't have SubjectAccessReview GET role. That user will fail. I am not sure which one is better

Hi all, since I opened https://github.com/open-cluster-management-io/governance-policy-propagator/pull/167 after 167 merged that I will work on this 164 PR Thanks

I think we need to figure out the service account stuff for the tests.

SubjectAccessReview needs clusterrole or role so if the user doesn't have SubjectAccessReview GET role. That user will fail. I am not sure which one is better. Also, I should use SelfSubjectRulesReview(github.com/stolostron/rbac-api-utils) to get all roles at once. That needs to impersonate. Otherwise, like using SubjectAccessReview, I have to ping kubernetes API per a line. Do you have a good idea?

Limiting the number of API calls is a good reason to favor SelfSubjectRulesReview, I wasn't thinking about that.

@yiraeChristineKim could you please change the PR description since you are only handling the auth/authorization on the get API endpoint in this PR now?

authors: JustinKuli mprahl yiraeChristineKim


text:
add deprecated message for v1beta1 version.

ref: open-cluster-management/backlog#10749
based on #404

/lgtm


text:
[Request]Consider integrating MMT-Bench and CONTEXTUAL?

MMT-Bench: A Comprehensive Multimodal Benchmark for Evaluating Large Vision-Language Models Towards Multitask AGI
https://arxiv.org/pdf/2404.16006
CONTEXTUAL: Evaluating Context-Sensitive Text-Rich Visual Reasoning in Large Multimodal Models
https://arxiv.org/pdf/2401.13311

Thanks for your interest in MMT-Bench. We will integrate MMT-Bench ASAP.

Hi, @iamlockelightning
MMT-Bench has already been supported.

repo: open-compass/VLMEvalKit


text:
AwsApiCustomResource - A better AwsCustomResource

AwsCustomResource makes it possible to construct a custom resource simply by specifying a AwsSdkCall - any AWS SDK operation in any service.  This makes it possible for users to onboard any AWS service to CloudFormation themselves. It's a great way to create custom resources – if the API you are using can fit into that model.  Other call patterns, such as Lambda, REST, ApiGateway, StepFunctions, and custom call patterns are not well supported.
AwsApiCustomResource makes it possible to use other call patterns and support a wider set of AWS calls than can currently be used with AwsCustomResource.  This enables end users to onboard their own or others services, APIs and Lambdas to CloudFormation in a piecemeal fashion, without having to develop a CloudFormation service provider.
export interface AwsApiCall extends AwsSdkCall {
   /**
    * Fills in the outputPaths automatically based on requested attributes (those retrieved
    * by getResponeField/Reference). This automatically limits the response to just what
    * is used.  If the user specified outputPaths, then the requested outputPaths will be
    * added to the given list.
    */
   readonly boolean includeRequestedOutputPaths

  /**
   * Specifies a field in the API response that should be deserlized, such as
   * Payload when calling lambda:Invoke, or Body when calling s3:GetObject.
   * The response data will only contain fields from the deserialized object.
   */
  readonly responseBufferField?: string

  /** Specifies which return field has the status for isComplete calls.  */
  readonly statusField?: string
  /** Specifies which return field has the failure cause (if any). */
  readonly causeField?: string

  /** Specifies succeeded values for statusField */
  readonly successStatusValues?: string[]
  /** Specifies failed values for statusField */
  readonly failedStatusValues?: string[]
  /** Specifies running/in progress values for statusField */
  readonly runningStatusValues?: string[]

  /**
   * Default attribute values to use when the underlying API fails to return expected
   * response fields.  This allows the user to call getResponseField/Reference
   * when specifying ignoreErrorCodesMatching.
   */
  readonly defaultDataValues?: Record<string, string>
}

/**
 * Properties for AwsApiCustomResource.
 */
export interface AwsApiCustomResourceProps extends AwsCustomResourceProps {
  /** Properties from AwsCustomResource are replaced by these */
  readonly onCreate?: AwsApiCall;

  readonly onUpdate?: AwsApiCall;

  readonly onDelete?: AwsApiCall;

  /** Enables provider-like functionality for longer operations called from AwsApiCustomResource **/
  readonly onCreateIsComplete?: AwsApiCall;

  readonly onUpdateIsComplete?: AwsApiCall;

  readonly onDeleteIsComplete?: AwsApiCall;

  /**
   * Whether to run the resource every time the stack is rebuilt.  Adds a timestamp to the resource properties.
   */
  readonly runAlways?: boolean
}

 /** Allows an onEventIsComplete function to access an attribute returned as data from an onEvent
  *(onCreate/onUpdate/onDelete) call.  Reference this from the properties passed to the
  * onEventIsComplete AwsApiCall
  */
export class OnEventDataField {
  /* Returns a field from the onEvent call.  Can only be used in onEventIsComplete call properties. */
  static get(name: string): any
}

The runtime for AwsApiCustomResource should be public and easily customizable by the user, allowing at least the abitly to replace the API invoker and the response filter.

Hi, could you please provide an example of how and when to use this? I am not sure I get the use case.

For now this will move over to the cdk-orchestration package.

authors: hoegertn michanto

repo: open-constructs/aws-cdk-library


text:
add auth middleware that enforces user authentication

This will simplify things once we start enforcing auth on API calls.

 Set up a login and auth mechanism.

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


text:
[Feature Request] I would like to be able to input Direction Groups

When creating recipes, the ingredients can be grouped (for instance: dough and icing), but the same doesn't seem possible for directions (but it's quite useful, specially for desserts).

Makes since. An idea how you would want this to look? Or should it be similar to the ingredients.
Most recipes I use have a start to finish order. IE, you do one thing at a time then move on to the next. An example of why you need this order would also help.

For me just like the ingredients, indeed :)
An example is this one: https://www.willcookforsmiles.com/avocado-salmon-rice-bowl/
The recipe has three components. They can be made at any order, so it's really good to see them as groups.

I'd like to +1 this request, but also offer my process as a workaround. The linked recipe for avocado salmon rice bowl technically contains three recipes. Each recipe creates one of the three main components to the dish. In order for the ingredients and directions to be "categorized" in to the main components, I would create three recipes with a reference to each one. This obviously is less than idea, as you're having to pull up multiple pages for a single meal, but with sides, condiments, mains, and deserts all in separate recipes, you have to do that anyway.
To be clear, I don't think my workaround is idea. I'd rather have the requested grouping described herein. Just sharing how I do it.

I have that for recipes that use bechamel sauce, for instance. Since Bechamel is used in so many recipes, it makes sense to have it as a separate component, but not always the components on themselves make sense as a full separate recipe, I think. But indeed, it's a workaround.

Give this branch A try and see if it works as you would expect.
https://github.com/open-eats/openeats-web/pull/19

Perfect :ok_hand:

Added in https://github.com/open-eats/openeats-web/pull/19

authors: RyanNoelk renatolond rustymyers

repo: open-eats/OpenEats


text:
Service Icons

It would be helpful to include the icon for each service. When looking an architectural diagram I see different AWS icons, but don't know some of icons are stand for.

Good idea!

Maybe we should add a link to the AWS Architecture center (https://aws.amazon.com/architecture/icons/)? It includes the standard AWS icons in a number of usable formats, i.e. pptx, etc...

authors: Rivukis lobster1234 lynnlangit

repo: open-guides/og-aws


text:
Add note on API Gateway query params

API gateway does not have full support for nested query parameters. Based on personal experience and their docs. See the HTTP request query parameters section

Much to our everlasting frustration, you are correct. Thanks for pitching in!

authors: QuinnyPig shtaft


text:
404 error in messenger app

I am running open-intent via docker, bound to port 5000
When i access /messenger/chat, i am getting a 404 error. Is there anyway to debug, whats causing the issue?

Hello @rmdort ,
It's weird, can you please check the configuration files in the config/ directory of your bot and tell me if messenger is set to true in selection.json? I guess it is not. Just set it to true and restart your bot to check if it works.

repo: open-intent-io/open-intent


text:
SELF_SIGNUP setting doesn't work for LDAP authentication provider

Affected module
impact the UI
Describe the bug
The authenticate page shows the option "Create Account" when using ldap provider.
For the setting AUTHENTICATION_PROVIDER , when using basic value, this works fine. But if it's ldap, it's doesn't work as expected
To Reproduce

change the AUTHENTICATION_PROVIDER config to ldap
change the AUTHENTICATION_ENABLE_SELF_SIGNUP to false
open the main page (like image attachment)

Expected behavior
When setting the AUTHENTICATION_ENABLE_SELF_SIGNUP to false, it's expect that the user can't sign in creating new user because the account must exist in LDAP provider.
Version:

OS: AlmaLinux 9.2 using docker image openmetadata/server:1.2.4
Python version:
OpenMetadata version: 1.2.4
OpenMetadata Ingestion package version: not used

Thanks same issue!

authors: metalshanked thiagopirex

repo: open-metadata/OpenMetadata


text:
Where to get kitti_dbinfos_train.pkl file?

When I run
python -m pcdet.datasets.kitti.kitti_dataset create_kitti_infos tools/cfgs/dataset_configs/kitti_dataset.yaml
always raise Error below, I wonder what kitti_dbinfos_train.pkl actually is and how to generate/download this file, THX.
Traceback (most recent call last):   File "/home/jy/envoriment/local/anaconda3/envs/LidarDet/lib/python3.6/site-packages/ipdb/__main__.py", line 276, in main     pdb._runscript(mainpyfile)   File "/home/jt/envoriment/local/anaconda3/envs/LidarDet/lib/python3.6/pdb.py", line 1548, in _runscript     self.run(statement)   File "/home/jt/envoriment/local/anaconda3/envs/LidarDet/lib/python3.6/bdb.py", line 434, in run     exec(cmd, globals, locals)   File "<string>", line 1, in <module>   File "/home/jt/code/opensource/OpenLidarPerceptron/tmp.py", line 1, in <module>     from pcdet.datasets.kitti.kitti_dataset import create_kitti_infos   File "/home/jt/code/opensource/OpenLidarPerceptron/pcdet/datasets/kitti/kitti_dataset.py", line 379, in create_kitti_infos     dataset = KittiDataset(dataset_cfg=dataset_cfg, class_names=class_names, root_path=data_path)   File "/home/jt/code/opensource/OpenLidarPerceptron/pcdet/datasets/kitti/kitti_dataset.py", line 22, in __init__     dataset_cfg=dataset_cfg, class_names=class_names, training=training, root_path=root_path, logger=logger   File "/home/jt/code/opensource/OpenLidarPerceptron/pcdet/datasets/dataset.py", line 30, in __init__     ) if self.training else None   File "/home/jt/code/opensource/OpenLidarPerceptron/pcdet/datasets/augmentor/data_augmentor.py", line 24, in __init__     cur_augmentor = getattr(self, cur_cfg.NAME)(config=cur_cfg)   File "/home/jt/code/opensource/OpenLidarPerceptron/pcdet/datasets/augmentor/data_augmentor.py", line 32, in gt_sampling     logger=self.logger   File "/home/jt/code/opensource/OpenLidarPerceptron/pcdet/datasets/augmentor/database_sampler.py", line 19, in __init__     with open(str(db_info_path), 'rb') as f: FileNotFoundError: [Errno 2] No such file or directory: 'data/kitti/kitti_dbinfos_train.pkl' Uncaught exception. Entering post mortem debugging

Have you tried to pull the latest codes?
If not, please pull the latest codes and run it again. We fix a similar error in https://github.com/open-mmlab/OpenLidarPerceptron/commit/c6302949d86d83d59e562416d1fa046879fea908.

Have you tried to pull the latest codes?
If not, please pull the latest codes and run it again. We fix a similar error in c630294.

Thanks for reply, we already solve this problem

Have you tried to pull the latest codes?
If not, please pull the latest codes and run it again. We fix a similar error in c630294.

Thanks for reply, we already solve this problem

Can you share how you solved this problem ?

request this file too.

repo: open-mmlab/OpenPCDet


text:
How to test one module's runtime or inferring time, such as PV RCNN?

Hello, my dear friend, could I know how to test one module's runtime or inferring time, such as PV RCNN?

insert the following script before and after https://github.com/open-mmlab/OpenPCDet/blob/a07572f389a00dadb859b7186471ef837e044278/pcdet/models/detectors/pv_rcnn.py#L11
def get_time():
    torch.cuda.synchronize()
    return time.time()

calculate the time difference and store them in a dict with the module name. Then you can compute the average value in https://github.com/open-mmlab/OpenPCDet/blob/a07572f389a00dadb859b7186471ef837e044278/tools/eval_utils/eval_utils.py#L54


text:
meet error in load v1 text_encoder.safetensors

my scripts is  python gradio_PowerPaint.py

It looks like an issue with the model weights. Try manually downloading from https://huggingface.co/JunhaoZhuang/PowerPaint-v1 and then modify the path.

I downloaded the model directly from here, and I would encounter this problem. After I added the parameter of strict=False, it could be loaded normally.

repo: open-mmlab/PowerPaint


text:
Object tracking after model detection

Anybody tried implementing some algorithm (apart from standard IoU) for Object tracking in a split video sequence?
Just getting started on this, would love to know some proven tracks.

Object tracking is supported in MMTracking.

Object tracking is supported in MMTracking.

repo: open-mmlab/mmdetection


text:
Mobilenet v3

I think it is a good idea to add mobilenet v3
It is better than mobilenet v2 and more efficient than most backbones present here.
Are you planning on adding it soon ?

Thanks for your suggestion!

My suggestion has been moved to Done. What does this mean ? because I don't see any changes

authors: RangiLyu WassimBouatay


text:
[Feature]

What is the feature?
ImportError: cannot import name 'show_result_meshlab' from 'mmdet3d.apis' (E:\project\mmdetection3d\mmdet3d\apis_init_.py)
Any other context?
No response

Can you provide more detailed information following the template?

What is the feature?
ImportError: cannot import name 'show_result_meshlab' from 'mmdet3d.apis' (E:\project\mmdetection3d\mmdet3d\apis__init__.py)
Any other context?
No response
Is the problem solved? I am facing the same issue.


text:
Incompatible mmdet version when using docker file

Hi, I have built the docker file from your repo but I had the following errors when I try to verify the installation with the demo script (1). So I tried to use the 2.11.0 version of mmdet but I had the following error (2) :
Error

Traceback (most recent call last):
  File "pcd_demo.py", line 3, in <module>
    from mmdet3d.apis import inference_detector, init_detector, show_result_meshlab
  File "/mmdetection3d/mmdet3d/__init__.py", line 34, in <module>
    f'MMDET=={mmdet.__version__} is used but incompatible. ' \
AssertionError: MMDET==2.12.0 is used but incompatible. Please install mmdet>=2.10.0, <=2.11.0.

  File "pcd_demo.py", line 3, in <module>
    from mmdet3d.apis import inference_detector, init_detector, show_result_meshlab
  File "/mmdetection3d/mmdet3d/apis/__init__.py", line 1, in <module>
    from .inference import (convert_SyncBN, inference_detector,
  File "/mmdetection3d/mmdet3d/apis/inference.py", line 10, in <module>
    from mmdet3d.core import (Box3DMode, DepthInstance3DBoxes,
  File "/mmdetection3d/mmdet3d/core/__init__.py", line 2, in <module>
    from .bbox import *  # noqa: F401, F403
  File "/mmdetection3d/mmdet3d/core/bbox/__init__.py", line 4, in <module>
    from .iou_calculators import (AxisAlignedBboxOverlaps3D, BboxOverlaps3D,
  File "/mmdetection3d/mmdet3d/core/bbox/iou_calculators/__init__.py", line 1, in <module>
    from .iou3d_calculator import (AxisAlignedBboxOverlaps3D, BboxOverlaps3D,
  File "/mmdetection3d/mmdet3d/core/bbox/iou_calculators/iou3d_calculator.py", line 5, in <module>
    from ..structures import get_box_type
  File "/mmdetection3d/mmdet3d/core/bbox/structures/__init__.py", line 1, in <module>
    from .base_box3d import BaseInstance3DBoxes
  File "/mmdetection3d/mmdet3d/core/bbox/structures/base_box3d.py", line 5, in <module>
    from mmdet3d.ops.iou3d import iou3d_cuda
  File "/mmdetection3d/mmdet3d/ops/__init__.py", line 5, in <module>
    from .ball_query import ball_query
  File "/mmdetection3d/mmdet3d/ops/ball_query/__init__.py", line 1, in <module>
    from .ball_query import ball_query
  File "/mmdetection3d/mmdet3d/ops/ball_query/ball_query.py", line 4, in <module>
    from . import ball_query_ext
ImportError: cannot import name 'ball_query_ext' from 'mmdet3d.ops.ball_query' (/mmdetection3d/mmdet3d/ops/ball_query/__init__.py)

Reproduction

docker build -t mmdetection3d docker/
docker run --gpus all --shm-size=8g -it -v {DATA_DIR}:/mmdetection3d/data mmdetection3d
python demo/pcd_demo.py

docker build -t mmdetection3d docker/
docker run --gpus all --shm-size=8g -it -v {DATA_DIR}:/mmdetection3d/data mmdetection3d
pip install mmdet==2.11.0
python demo/pcd_demo.py

Environment
With python mmdet3d/utils/collect_env.py :
fatal: not a git repository (or any parent up to mount point /)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
sys.platform: linux
Python: 3.7.7 (default, May  7 2020, 21:25:33) [GCC 7.3.0]
CUDA available: True
GPU 0: GeForce GTX 1060
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 10.1, V10.1.243
GCC: gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
PyTorch: 1.6.0
PyTorch compiling details: PyTorch built with:
  - GCC 7.3
  - C++ Version: 201402
  - Intel(R) Math Kernel Library Version 2020.0.1 Product Build 20200208 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v1.5.0 (Git Hash e2ac1fac44c5078ca927cb9b90e1b3066a0b2ed0)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - NNPACK is enabled
  - CPU capability usage: AVX2
  - CUDA Runtime 10.1
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_37,code=compute_37
  - CuDNN 7.6.3
  - Magma 2.5.2
  - Build settings: BLAS=MKL, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DUSE_VULKAN_WRAPPER -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON, USE_STATIC_DISPATCH=OFF,

TorchVision: 0.7.0
OpenCV: 4.5.1
MMCV: 1.3.2
MMCV Compiler: GCC 7.3
MMCV CUDA Compiler: 10.1
MMDetection: 2.11.0
MMDetection3D: 0.13.0+

Hi @Vincentdaniele ,
MMDetection3D is currently not compatible with the latest release of MMDetection, see #506 .
As for your second question, please refer to #503 and check your platform environment?

Thanks you for your answer, your update on the Dockerfile did solve the first question.
My second problem was there because I replaced more than the data folder in the docker run command, it works well now.


text:
dist_eval.sh is wrong. And multi GPUs evaluation is not working

In the branch:main, use multi GPUs evaluation is meet a bug.
In the dist_eval.sh , it open tools/test.py, but in this branch ,the test.py is not exist.
even i edit to evaluation.py , it not worked.

Hi @roingbu , I strongly suggenst you to try branch 1.x, you can just use dist_test.sh or slurm_test.sh for all model evaluation.

Closing due to inactivity, please reopen if there are any further problems.

authors: plyfager roingbu zengyh1900

repo: open-mmlab/mmgeneration


text:
Problemas para registrar webhook

Estimados,
No podemos registrar el webhook con Magento 1.9.3.1. El plugin está instalado satisfactoriamente y funciona:

Pero al querer validar los webhook, nos da un error en OpenPay.
Los endpoints son los siguientes:
https://www.mundoterra.com/stores/payments/confirm
https://www.mundoterra.com/banks/payments/confirm
Y en el error_log nos da los siguientes errores:
2017-02-01T19:19:48+00:00 ERR (3): Notice: Trying to get property of non-object  in /opt/bitnami/apps/magento/htdocs/app/code/local/Openpay/Banks/controllers/PaymentsController.php on line 117
¡Saludos!

Podrías guardar en tu log la petición que envía Openpay para validar tu webhook. Es decir, mandar al log "$request->getRawBody()"
De aquí podríamos partir y hacer pruebas con Postman.
Quedo atento a tus comentarios.

@fedebalderas Lo hacemos, intentamos conectarnos y te compartimos el logfile.

@luiscosio Por ahí comente tu problema con soporte y me comentaron que tenían un problema: "Para ser especifico Openpay no pudo realizar la conexión a su server debido a que no puede obtener  el SSL."
Es decir, no es problema del plugin... Si quieres le damos seguimiento por correo: federico.balderas@openpay.mx

authors: fedebalderas luiscosio

repo: open-pay/openpay-magento


text:
Add test to validate 16G hugepage

Patch adds test to configure and validate 16G hugepages. The following steps are performed sequentially for validation.

Get the configured hugepages from LPAR profile
Update the LPAR grub with hugepage kernel commandline
parameters
Power off the LPAR and managed system
Configure sample hugepages through ASM
Power on the managed system
Update the LPAR profile with incremented hugepages
Power on the LPAR with the profile
Verify if 16G hugepages are configured properly at OS level
Revert LPAR profile config and kernel parameters

Signed-off-by: Harish harish@linux.ibm.com

Depends on #598
Test log: hp_16g.txt

@harihare Can you please review this?

Patch looks perfect for me. except the comment made in PR #598 .
In addition I request @abdhaleegit to review it.

repo: open-power/op-test


text:
Add support for SignalFx @Trace annotation

Otel-auto supports some 3rd-party annotations to mark methods that should create new spans. This support is implemented by io.opentelemetry.auto.instrumentation.traceannotation.TraceAnnotationsInstrumentation. Currently it does not support SignalFx com.signalfx.tracing.api.Trace.

This issue and PR relates to https://github.com/open-telemetry/opentelemetry-java/issues/813

It is certainly related, but I think they are still independent. As long as Otel wants to support proprietary APIs, it still has to support those 3rd party annotations. Even after Otel gains its own @Trace annotation.

authors: iNikem safris


text:
release ocb container image

It seems that there has already been some effort to make a ocb container image available. But its unclear where it should live?

https://github.com/open-telemetry/opentelemetry-collector/issues/5712
https://github.com/open-telemetry/opentelemetry-collector/pull/6451

According to the discussion in the collector repo, should it be released here?

note: As discussed in the collector sig call - we create the image here.

Hi all, going to work on adding the ocb release pipeline to the opentelemetry-collector-releases repo and go from there to take this up.

FTR: This topic was discussed during the SIG Call on March 1, 2023, 17:00 UTC SIG mtg. At that time I think recordings have been published on youtube. Unfortunately its not listed on the meeting recording list.


text:
Worker thread dies if log_subrequest is enabled

Describe your environment
I'm using the iquirino91/nginx-opentelemetry Docker image from @iquirino. See #81 and the Dockerfile here.
Steps to reproduce
The steps below assume you have Docker Compose installed. If you do not, you are welcome to just use the nginx.conf with log_subrequest and try to reproduce the issue.
Create a new folder named bug and put the following files into it.

docker-compose.yml
services:
  otel:
    image: otel/opentelemetry-collector:latest
    command: ["--config=/etc/otel-collector-config.yaml", "${OTELCOL_ARGS}"]
    volumes:
      - ./otel-collector-config.yaml:/etc/otel-collector-config.yaml
    ports:
      - "4317:4317"
    networks:
      - backend
  nginx-otel:
    image: iquirino91/nginx-opentelemetry@sha256:008914fd4d4aa8e060e14d7a2af56e48418d95832251473a8cffb5c348681703
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf
      - ./otel-nginx.toml:/conf/otel-nginx.toml
      - ./:/tmp/cores
    depends_on:
      - otel
    networks:
      - backend
networks:
  backend:

otel-nginx.toml
exporter = "otlp"
processor = "simple"

[exporters.otlp]
host = "otel"
port = 4317

[service]
name = "nginx-test-crash"

nginx.conf
load_module /etc/nginx/modules/otel_ngx_module.so;

worker_processes   auto;
error_log          /var/log/nginx/error.log debug;
working_directory  /tmp/cores/;
worker_rlimit_core 500M;

events {
}
http {
  opentelemetry_config /conf/otel-nginx.toml;
  log_subrequest on;

  server {
    opentelemetry on;
    listen 80;
    server_name otel_example;

    location = / {
      opentelemetry on;

      auth_request /auth;
    }

    location = /auth {
    }

  }
}

otel-collector-config.yaml
receivers:
  otlp:
    protocols:
      grpc:

exporters:
  logging:

processors:
  batch:

service:
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [logging]

Run docker-compose -p crash up in a terminal.
In another terminal, exec into Nginx with docker exec -it crash_nginx-otel_1 /bin/sh.

# apk add curl
# curl localhost:80

Observe the crash in your original terminal.

nginx-otel_1  | 2021/12/20 20:23:29 [error] 8#0: *1 open() "/etc/nginx/html/auth" failed (2: No such file or directory), client: 127.0.0.1, server: otel_example, request: "GET / HTTP/1.1", subrequest: "/auth", host: "localhost"
nginx-otel_1  | 127.0.0.1 - - [20/Dec/2021:20:23:29 +0000] "GET / HTTP/1.1" 404 0 "-" "curl/7.80.0"
nginx-otel_1  | 127.0.0.1 - - [20/Dec/2021:20:23:29 +0000] "GET / HTTP/1.1" 500 177 "-" "curl/7.80.0"
nginx-otel_1  | 2021/12/20 20:23:29 [error] 8#0: *1 auth request unexpected status: 404, client: 127.0.0.1, server: otel_example, request: "GET / HTTP/1.1", host: "localhost"
otel_1        | 2021-12-20T20:23:29.425Z	INFO	loggingexporter/logging_exporter.go:40	TracesExporter	{"#spans": 1}
nginx-otel_1  | 2021/12/20 20:23:29 [notice] 1#0: signal 17 (SIGCHLD) received from 8
nginx-otel_1  | 2021/12/20 20:23:29 [alert] 1#0: worker process 8 exited on signal 11 (core dumped)
nginx-otel_1  | 2021/12/20 20:23:29 [notice] 1#0: start worker process 57
nginx-otel_1  | 2021/12/20 20:23:29 [notice] 1#0: signal 29 (SIGIO) received

We can use gdb to check the crash in the Nginx terminal. The dump should be /tmp/cores/core. You can also just use your system since /tmp/cores is mounted to the working directory so the core file should be on your local disk as well. The SetAttribute call in FinishNgxSpan is causing the crash.

# apk add gdb
# gdb /etc/nginx/nginx /tmp/cores/core
(gdb) bt
#0  0x00007fac054e69b1 in opentelemetry::v1::sdk::trace::Span::SetAttribute(opentelemetry::v1::nostd::string_view, absl::lts_20210324::variant<bool, int, long, unsigned int, double, char const*, opentelemetry::v1::nostd::string_view, opentelemetry::v1::nostd::span<bool const, 18446744073709551615ul>, opentelemetry::v1::nostd::span<int const, 18446744073709551615ul>, opentelemetry::v1::nostd::span<long const, 18446744073709551615ul>, opentelemetry::v1::nostd::span<unsigned int const, 18446744073709551615ul>, opentelemetry::v1::nostd::span<double const, 18446744073709551615ul>, opentelemetry::v1::nostd::span<opentelemetry::v1::nostd::string_view const, 18446744073709551615ul>, unsigned long, opentelemetry::v1::nostd::span<unsigned long const, 18446744073709551615ul>, opentelemetry::v1::nostd::span<unsigned char const, 18446744073709551615ul> > const&) () from /etc/nginx/modules/otel_ngx_module.so
#1  0x00007fac054b9a5b in FinishNgxSpan(ngx_http_request_s*) () from /etc/nginx/modules/otel_ngx_module.so
#2  0x000055655d74482d in ngx_http_log_request (r=r@entry=0x7fac04a49370) at src/http/ngx_http_request.c:3753
#3  0x000055655d74613f in ngx_http_free_request (r=r@entry=0x7fac04a49370, rc=rc@entry=0) at src/http/ngx_http_request.c:3699
#4  0x000055655d746228 in ngx_http_close_request (r=r@entry=0x7fac04a49370, rc=rc@entry=0) at src/http/ngx_http_request.c:3645
#5  0x000055655d746c10 in ngx_http_finalize_connection (r=r@entry=0x7fac04a49370) at src/http/ngx_http_request.c:2788
#6  0x000055655d7474a7 in ngx_http_finalize_request (r=r@entry=0x7fac04a49370, rc=<optimized out>) at src/http/ngx_http_request.c:2661
#7  0x000055655d7471ad in ngx_http_finalize_request (r=r@entry=0x7fac04a49370, rc=500) at src/http/ngx_http_request.c:2547
#8  0x000055655d741a49 in ngx_http_core_access_phase (r=0x7fac04a49370, ph=0x7fac04a29b38) at src/http/ngx_http_core_module.c:1148
#9  0x000055655d73cf77 in ngx_http_core_run_phases (r=0x7fac04a49370) at src/http/ngx_http_core_module.c:875
#10 0x000055655d745e99 in ngx_http_run_posted_requests (c=c@entry=0x7fac04a035a0) at src/http/ngx_http_request.c:2450
#11 0x000055655d748536 in ngx_http_process_request_headers (rev=rev@entry=0x7fac049f6490) at src/http/ngx_http_request.c:1521
#12 0x000055655d7488ca in ngx_http_process_request_line (rev=rev@entry=0x7fac049f6490) at src/http/ngx_http_request.c:1165
#13 0x000055655d748a8c in ngx_http_wait_request_handler (rev=0x7fac049f6490) at src/http/ngx_http_request.c:503
#14 0x000055655d72f91a in ngx_epoll_process_events (cycle=<optimized out>, timer=<optimized out>, flags=<optimized out>) at src/event/modules/ngx_epoll_module.c:901
#15 0x000055655d725e6b in ngx_process_events_and_timers (cycle=cycle@entry=0x7fac0554b200) at src/event/ngx_event.c:247
#16 0x000055655d72dc2d in ngx_worker_process_cycle (cycle=0x7fac0554b200, data=<optimized out>) at src/os/unix/ngx_process_cycle.c:721
#17 0x000055655d72c290 in ngx_spawn_process (cycle=cycle@entry=0x7fac0554b200, proc=proc@entry=0x55655d72db52 <ngx_worker_process_cycle>, data=data@entry=0x0, name=name@entry=0x55655d7ab53d "worker process", respawn=respawn@entry=-3)
    at src/os/unix/ngx_process.c:199
#18 0x000055655d72ce7e in ngx_start_worker_processes (cycle=cycle@entry=0x7fac0554b200, n=8, type=type@entry=-3) at src/os/unix/ngx_process_cycle.c:344
#19 0x000055655d72e336 in ngx_master_process_cycle (cycle=cycle@entry=0x7fac0554b200) at src/os/unix/ngx_process_cycle.c:130
#20 0x000055655d70623d in main (argc=<optimized out>, argv=<optimized out>) at src/core/nginx.c:383

What is the expected behavior?
Using log_subrequest on; should not cause the worker thread to crash.
What is the actual behavior?
The worker thread crashes with log_subrequest on; in the Nginx configuration.

Tried to use GDB to figure things out but not sure if I really got anywhere...
Thread 1 "nginx" hit Breakpoint 6, FinishNgxSpan (req=0x7fa861534370) at /build/opentelemetry-cpp-contrib/instrumentation/nginx/src/otel_ngx_module.cpp:462
462	ngx_int_t FinishNgxSpan(ngx_http_request_t* req) {
(gdb) c
Continuing.

Thread 1 "nginx" hit Breakpoint 7, opentelemetry::v1::sdk::trace::Span::SetAttribute (this=0x7fa861548360, key=..., value=...) at /build/opentelemetry-cpp/sdk/src/trace/span.cc:95
95	{
(gdb) s
96	  std::lock_guard<std::mutex> lock_guard{mu_};
(gdb) s
std::lock_guard<std::mutex>::lock_guard (this=0x7ffca771b340, __m=...) at /usr/include/c++/10.3.1/bits/std_mutex.h:158
158	      explicit lock_guard(mutex_type& __m) : _M_device(__m)
(gdb) n
159	      { _M_device.lock(); }
(gdb) n
opentelemetry::v1::sdk::trace::Span::SetAttribute (this=0x7fa861548360, key=..., value=...) at /build/opentelemetry-cpp/sdk/src/trace/span.cc:98
98	  recordable_->SetAttribute(key, value);
(gdb) s
std::unique_ptr<opentelemetry::v1::sdk::trace::Recordable, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >::operator-> (this=0x7fa8615483a0) at /usr/include/c++/10.3.1/bits/unique_ptr.h:416
416		return get();
(gdb) s
std::unique_ptr<opentelemetry::v1::sdk::trace::Recordable, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >::get (this=0x7fa8615483a0) at /usr/include/c++/10.3.1/bits/unique_ptr.h:422
422	      { return _M_t._M_ptr(); }
(gdb) s
std::__uniq_ptr_impl<opentelemetry::v1::sdk::trace::Recordable, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >::_M_ptr (this=0x7fa8615483a0) at /usr/include/c++/10.3.1/bits/unique_ptr.h:173
173	      pointer    _M_ptr() const { return std::get<0>(_M_t); }
(gdb) s
std::get<0ul, opentelemetry::v1::sdk::trace::Recordable*, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> > (__t=...) at /usr/include/c++/10.3.1/tuple:1305
1305	    { return std::__get_helper<__i>(__t); }
(gdb) s
std::__get_helper<0ul, opentelemetry::v1::sdk::trace::Recordable*, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> > (__t=...) at /usr/include/c++/10.3.1/tuple:1293
1293	    { return _Tuple_impl<__i, _Head, _Tail...>::_M_head(__t); }
(gdb) s
std::_Tuple_impl<0ul, opentelemetry::v1::sdk::trace::Recordable*, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >::_M_head (__t=...) at /usr/include/c++/10.3.1/tuple:204
204	      _M_head(const _Tuple_impl& __t) noexcept { return _Base::_M_head(__t); }
(gdb) s
std::_Head_base<0ul, opentelemetry::v1::sdk::trace::Recordable*, false>::_M_head (__b=...) at /usr/include/c++/10.3.1/tuple:169
169	      _M_head(const _Head_base& __b) noexcept { return __b._M_head_impl; }
(gdb) s
std::_Tuple_impl<0ul, opentelemetry::v1::sdk::trace::Recordable*, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >::_M_head (__t=...) at /usr/include/c++/10.3.1/tuple:204
204	      _M_head(const _Tuple_impl& __t) noexcept { return _Base::_M_head(__t); }
(gdb) s
std::__get_helper<0ul, opentelemetry::v1::sdk::trace::Recordable*, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> > (__t=...) at /usr/include/c++/10.3.1/tuple:1293
1293	    { return _Tuple_impl<__i, _Head, _Tail...>::_M_head(__t); }
(gdb) s
std::get<0ul, opentelemetry::v1::sdk::trace::Recordable*, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> > (__t=...) at /usr/include/c++/10.3.1/tuple:1305
1305	    { return std::__get_helper<__i>(__t); }
(gdb) s
std::__uniq_ptr_impl<opentelemetry::v1::sdk::trace::Recordable, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >::_M_ptr (this=0x7fa8615483a0) at /usr/include/c++/10.3.1/bits/unique_ptr.h:173
173	      pointer    _M_ptr() const { return std::get<0>(_M_t); }
(gdb) s
std::unique_ptr<opentelemetry::v1::sdk::trace::Recordable, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >::get (this=0x7fa8615483a0) at /usr/include/c++/10.3.1/bits/unique_ptr.h:422
422	      { return _M_t._M_ptr(); }
(gdb) s
std::unique_ptr<opentelemetry::v1::sdk::trace::Recordable, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >::operator-> (this=0x7fa8615483a0) at /usr/include/c++/10.3.1/bits/unique_ptr.h:417
417	      }
(gdb) s
opentelemetry::v1::sdk::trace::Span::SetAttribute (this=0x7fa861548360, key=..., value=...) at /build/opentelemetry-cpp/sdk/src/trace/span.cc:98
98	  recordable_->SetAttribute(key, value);
(gdb) p recordable_
$17 = {
  _M_t = {<std::__uniq_ptr_impl<opentelemetry::v1::sdk::trace::Recordable, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >> = {
      _M_t = {<std::_Tuple_impl<0, opentelemetry::v1::sdk::trace::Recordable*, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >> = {<std::_Tuple_impl<1, std::default_delete<opentelemetry::v1::sdk::trace::Recordable> >> = {<std::_Head_base<1, std::default_delete<opentelemetry::v1::sdk::trace::Recordable>, true>> = {<std::default_delete<opentelemetry::v1::sdk::trace::Recordable>> = {<No data fields>}, <No data fields>}, <No data fields>}, <std::_Head_base<0, opentelemetry::v1::sdk::trace::Recordable*, false>> = {
            _M_head_impl = 0x0}, <No data fields>}, <No data fields>}}, <No data fields>}}
(gdb) s

Thread 1 "nginx" received signal SIGSEGV, Segmentation fault.
opentelemetry::v1::sdk::trace::Span::SetAttribute (this=0x7fa861548360, key=..., value=...) at /build/opentelemetry-cpp/sdk/src/trace/span.cc:98
98	  recordable_->SetAttribute(key, value);
(gdb)

The two requests passed to the FinishNgxSpan function are different (?) but the trace context is the same. Not sure if this is expected or not though. I presume the first call frees the first and then the second call dies? 🤔
(gdb) p req
$33 = (ngx_http_request_t *) 0x7f41d27f2220
(gdb) p context
$34 = (TraceContext *) 0x7f41d27f2d80

(gdb) p req
$35 = (ngx_http_request_t *) 0x7f41d27f3370
(gdb) p context
$36 = (TraceContext *) 0x7f41d27f2d80

https://github.com/open-telemetry/opentelemetry-cpp-contrib/blob/515b7a631a343b1a8ccb7bee99bd09c84c88b4b7/instrumentation/nginx/src/otel_ngx_module.cpp#L368-L373
I think this is because both the request and the subrequest shares the same variables member and it messes things up in StartNgxSpan?

I've opened #94 to address this. If it is not the proper fix I hope it will be of use to someone to help devise a correct fix. :)


text:
feat(TraceProvider): add shutdown and forceFlush to API

This PR exposes the shutdown and forcedFlush functions defined by the TraceProvider specs.
Providing these methods allow to gracefully shutdown instrumentations without data loss. Currently this is only possible with usage of the SDK specific implementations see
Context
Closes https://github.com/open-telemetry/opentelemetry-js/issues/3310

@secustor can you please re-apply this in https://github.com/open-telemetry/opentelemetry-js where this package is now moved?

authors: dyladan secustor

repo: open-telemetry/opentelemetry-js-api


text:
Process metrics should not be reported (at least by default) by the instrumentation libraries

Description
See https://github.com/open-telemetry/semantic-conventions/issues/1215 for the context
Node.js process instrumentation reports process metrics, which are not an intended for instrumentation libraries.
Individual runtimes are expected to report their own CPU and memory metrics even if process.* ones are suitable.
There is no clear conclusion on whether runtimes are not allowed to report them vs they should be opt-in.
Expected behavior
JS/node.js may define runtime-specific CPU/memory metrics and should not report process ones (by default)

These metrics have to be explicitly enabled (so they are not reported by default), so we think we are compliant here.

I believe the compliance means that the metric is reported with appropriate process resources being set, which instrumentation cannot guarantee. Still, the attachment to process resource is not documented and I'd not take any action on this bug until semconv issue is resolved.
I created this one to create more awareness wrt process vs runtime metrics. The approach we're taking (for java and .NET) is to  emit {runtime}.cpu.time metric and leave process ones for collector.  I.e. JS (node) should probably define new process-like metrics and report them instead.

authors: JamieDanielson lmolkova

repo: open-telemetry/opentelemetry-js-contrib


text:
Update Semantic conventions to export individual strings and stop using namespaces within the OTel packages

One significant minification issues is that for "common" strings such as the SemanticConventions if any single string is "used" then all of the members of the related SemanticConvension namespace also get included in the final bundle.
The suggestion here is to

export each "string" independently (as well as to continue to export as a single names (for backward compatability))
Ban the usage of the "namespace" within the OpenTelemetry packages and only use the individual exported strings (reducing the bundle size for individual components)

Example of change
Change from
// DO NOT EDIT, this is an Auto-generated file from scripts/semconv/templates//templates/SemanticAttributes.ts.j2
export const SemanticAttributes = {
  /**
   * The full invoked ARN as provided on the `Context` passed to the function (`Lambda-Runtime-Invoked-Function-Arn` header on the `/runtime/invocation/next` applicable).
   *
   * Note: This may be different from `faas.id` if an alias is involved.
   */
  AWS_LAMBDA_INVOKED_ARN: 'aws.lambda.invoked_arn',

  /**
   * An identifier for the database management system (DBMS) product being used. See below for a list of well-known identifiers.
   */
  DB_SYSTEM: 'db.system',

  ...
}

to

/**
 * The full invoked ARN as provided on the `Context` passed to the function (`Lambda-Runtime-Invoked-Function-Arn` header on the `/runtime/invocation/next` applicable).
 *
 * Note: This may be different from `faas.id` if an alias is involved.
 */
export const SEMCONV_AWS_LAMBDA_INVOKED_ARN = 'aws.lambda.invoked_arn';

/**
 * An identifier for the database management system (DBMS) product being used. See below for a list of well-known identifiers.
 */
export const SEMCONV_DB_SYSTEM = 'db.system';

// DO NOT EDIT, this is an Auto-generated file from scripts/semconv/templates//templates/SemanticAttributes.ts.j2
export const SemanticAttributes = {
  /**
   * The full invoked ARN as provided on the `Context` passed to the function (`Lambda-Runtime-Invoked-Function-Arn` header on the `/runtime/invocation/next` applicable).
   *
   * Note: This may be different from `faas.id` if an alias is involved.
   */
  AWS_LAMBDA_INVOKED_ARN: SEMCONV_AWS_LAMBDA_INVOKED_ARN',

  /**
   * An identifier for the database management system (DBMS) product being used. See below for a list of well-known identifiers.
   */
  DB_SYSTEM: SEMCONV_DB_SYSTEM,

  /**
}

And then internal usages would only reference the SEMCONV_ constants
I'm not married to the SEMCONV_ prefix (and a prefix is not actually required), I just included here to avoid confusion and to make it easier to call out the differences.

And yes, as this is an autogenerated file this would be a tooling update, and assuming that we continue to export a Namespaced version (the objects with the strings) this is actually backward compatible.

repo: open-telemetry/opentelemetry-js


text:
Experimental Features in Stable Packages

This issue is to discuss the possibilities for exposing experimental features in stable packages. Examples for experimental features are:

New APIs such as logs/events
Extensions to existing stable APIs like context/tracing/metrics
New SDK features such as file-based configuration
New behavior for existing APIs

For a concrete example of an extension to a stable API, see https://github.com/open-telemetry/opentelemetry-js-api/pull/123. This PR adds 2 new methods attach and detach to the context API and context manager interface. Currently, we are required to either add this to the stable API, or release an entirely separate experimental context API and context manager package.
package.json#exports
This option allows a package author to specify different entry points, for example @opentelemetry/api/experimental. It is currently used to export our SugaredTracer. It provides an explicit experimental package import path which signals to users that there may be breaking changes in minor versions. One major advantage of something like this is that it would allow us to also export experimental versions of existing APIs because they are an entirely separate export.
Problems
Complexity
This is just a complex option. For the example given above of adding new context API methods, the context API needs to be re-exported from the ./experimental export in a way that is a drop-in replacement, doesn't affect the existing export, and is obvious to the user. This makes the code a bit cumbersome. For an example, see https://github.com/open-telemetry/opentelemetry-js/pull/4669
Typescript Support
Typescript support is not great. Support was only added in 4.7 (we support 4.4 currently) and requires the user to enable Node16 module resolution. This in turn requires the user to set module: Node16, which emits ESM and not commonjs. This is fine for an experimental package, but if we want to be able to use these experimental exports in our SDK, we would also need to enable these features, which would be breaking for commonjs users.
A workaround for this is to not consume the /experimental namespace in our SDK packages. We would simply redeclare any types. Given the above example, we would have to declare an ExperimentalContextManager type in the AsyncHooksContextManager package and rely on typescript to recognize the compatible types.
@experimental JSDoc Tags
This tag marks an entity as experimental. It is a documentation-only solution, which means it is not enforced by tooling and may not be noticed by some users depending on their tooling. One major advantage of this solution is that it is very simple.
Problems
Overriding Methods
This requires the addition of a new experimental version of any API that needs experimental functionality. As an example, if we were going to experimentally change the behavior of the startSpan API, we would need to add a new method like experimentalStartSpan or similar because we can't override the existing API.

A workaround for this is to not consume the /experimental namespace in our SDK packages. We would simply redeclare any types. Given the above example, we would have to declare an ExperimentalContextManager type in the AsyncHooksContextManager package and rely on typescript to recognize the compatible types.

@dyladan and I talked about this offline yesterday:
We have to re-declare types from the API in the consuming packages anyway if the API is used as a peer dependency like >=1.0.0 <1.9.0. As users can use the package with an older version of the API, it might happen that they don't contain the types API types we're using which breaks users (see #4260).
To implement something like this we can go a similar way as proposed by #4622.

Overriding Methods
This requires the addition of a new experimental version of any API that needs experimental functionality. As an example, if we were going to experimentally change the behavior of the startSpan API, we would need to add a new method like experimentalStartSpan or similar because we can't override the existing API.

I think this may also be solvable by the same wrap()-approach. If wrap() is used we use the new behavior on the returned object in place of the old one.
Would you mind providing an example on which change would result in us having to change the API in such a way?

authors: dyladan pichlermarc


text:
chore: 0.8.1 release proposal

Release draft: https://github.com/open-telemetry/opentelemetry-js/releases/edit/untagged-f0de4c69e80bef340985

Waiting on #1059

Waiting on #1059/#1060

Would be nice if you can include #1055 (and strech #1050).

#1050 has only 2 approvals. Do we want to merge it, wait for more reviews, or just release this without it?

@dyladan I'm fine with merging it as-is, its just two new packages. There aren't yet documented elsewhere so there is no risk for me

@dyladan I'm fine with merging it as-is, its just two new packages. There aren't yet documented elsewhere so there is no risk for me

I agreed, I am fine with merging #1050.

authors: dyladan mayurkale22 vmarchaud


text:
fix(zipkin-exporter): round duration for zipkin

Which problem is this PR solving?
exporter-zipkin export traces correctly to zipkin.
Fixes #4056
Short description of the changes
Round the duration for zipkin.
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
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

[x] Unit tests for zipkin-exporter
[x] Tested in a project by using a patch

Checklist:

[x] Followed the style guidelines of this project
[x] Unit tests have been added
[ ] Documentation has been updated

Please update the changelog. I suggest something like fix(exporter-zipkin): round span durations to the nearest millisecond to be compliant with zipkin protocol

@dyladan thank you for the suggestion. I've updated the changelog

Any expected release date for this fix ?

authors: dyladan n0cloud rakeshlanjewar


text:
Java Metrics Documentation could use an update

I would like to re-write the Java Metrics documentation to follow a format similar to other languages, and include missing information on Exporters, Readers, and Views.
What needs to be changed?
The current java instrumentation -> metrics documentation is missing a lot of information. As a new user who wants to start using java OpenTelemetry metrics, there is not enough information provided on this page to actually get started. Right now it only provides a brief introduction to the different instrument types supported, with very basic code examples.
Other languages like Go, C++ and Javascript follow a more in depth and organized structure / content that cover several things that the current java documentation doesn't even touch on (Readers, Exporters, Views).
I plan to re-write this section of the java documentation to follow the structure of:

Intro
Initialize Metrics (MeterProvider)
Acquiring a Meter
Exporters and Metric Readers
Using Counters
Using UpDown Counters
Using Histograms
Using Observable (Async) Counters
Using Observable (Async) UpDown Counters
Using Observable (Async) Gauges
Adding Attributes
Metric Views

Path of the page that needs changed?
https://opentelemetry.io/docs/languages/java/instrumentation/#metrics
Additional Context / Notes
I wasn't sure if I should open this issue in the opentelemetry-java repo or this one, if I need to do anything else before contributing this change, please let me know.

Hey @jaydeluca, thanks for raising this issue and offering your help, this is the right place to ask for this (although I cc @open-telemetry/java-approvers for visibility).
Please go ahead and provide these updates to the Instrumentation Documentation, all I ask you to do is use the JavaScript and other documentation that is already in place as a blueprint for your additions. We try to create consistent documentation across languages right now, such that most of the non-code part of the documentation is the same, see
https://github.com/open-telemetry/opentelemetry.io/issues/3229

yes ❤❤❤

authors: jaydeluca svrnm trask


text:
Demo Architecture Diagram shows "unsupported markdown"

Suggested improvements for page: https://opentelemetry.io/docs/demo/architecture/
There is a rendering problem in the images, where there are currently lots of URLs shown as "Unsupported markdown: link" - both inside nodes and on edges. This makes the images hard to interpret.
Examples:

The text inside the graph source is much clearer, e.g.
            pr-http[/"Prometheus HTTP
listening on
http://localhost:9090"/]

@open-telemetry/demo-approvers PTAL>
@candlerb thanks for reporting

@svrnm has anything changed in the docs?
I'm pretty sure this was working before 🤔

This doesn't work in the Mermaid live editor either. Example.
There seems to be an issue with Mermaid: https://github.com/orgs/community/discussions/106690#discussioncomment-8698490
I couldn't find any bug in Mermaid's repo about this, though. As Mermaid is working as intended, I'll open a PR to sanitize the links by removing "http://"

There's this recent bug: https://github.com/mermaid-js/mermaid/issues/5824

@candlerb Good find! Seems critical enough to get fixed soon.
@svrnm We'd either wait or pin Mermaid to a previous version. Not sure when that regression was introduced, though.

I've patched the diagram, but let's follow up on that Mermaid bug.

authors: candlerb julianocosta89 svrnm theletterf


text:
Adding TypeScript to "Getting Started"

Ref #1800 and #1888
@svrnm @chalin @cartermp kindly take a look

Looks like you were right about the commits. Thanks for sticking it out like this. Looks like there's failures with respect to the main branch changes now, but once those are taken care of, I can approve.

Looks like you were right about the commits. Thanks for sticking it out like this. Looks like there's failures with respect to the main branch changes now, but once those are taken care of, I can approve.

Thanks for the information. It's been fixed 👍

@open-telemetry/javascript-approvers PTAL!

thanks for figthing this true! TY

Really want to have this merged soon, @kaiwalyakoparkar can you give the reviews another look?:)

Really want to have this merged soon, @kaiwalyakoparkar can you give the reviews another look?:)

Sure, I will commit the required changes soon

@open-telemetry/javascript-approvers please give this another look :-)

I will go ahead and merge, then we can address https://github.com/open-telemetry/opentelemetry.io/issues/1989 orthogonally, since it is all that remains. Thanks all, and especially @kaiwalyakoparkar for your diligence and patience across several PRs!

authors: cartermp kaiwalyakoparkar svrnm


text:
open wc stackblitz failing to load

Unable to load the stackblitz website for code samples, getting the following error:
https://open-wc-lit-demos.stackblitz.io/basic
Uncaught (in promise) Error: Preset not sepcified in configuration
at Object.config (webcontainer.7d044722a80339d7d45.js:15)
at t.config (webcontainer.7d044722a80339d7d45.js:15)
at Object.PREVIEW_INSTANTIATE_BUNDLE (preview-1cd940f8faa7073a7cacb.js:1)
at preview-1cd940f8faa7073a7cacb.js:1
at Array.map ()
at Object.dispatch (preview-1cd940f8faa7073a7cacb.js:1)
at preview-1cd940f8faa7073a7cacb.js:1

Hi, thanks for letting me know 🙂 this should be back up and running again, feel free to reopen if you still have issues

authors: jantillonc thepassle

repo: open-wc/open-wc


text:
some files causes openwebui to close without error

Bug Report
Installation Method
i use git clone and everything works until someone loads document with big table in it or big csv document. I can't find any error on logs even in debug mode.
Environment

Open WebUI Version: [e.g., v0.3.11]
only using chatgpt

Operating System: windows server 2019, pipeline works on docker i connect it succesfully with port. there is no rag customization. default settings is causing error also.

Browser (if applicable): all

Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[x] I have included the browser console logs.
[x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below.
[x] I have included the Docker container logs.

Actual Behavior:
i tried tika, changed extraction to chatgpt but still having the same issue. file is uploading correctly but when i submit it, it breaks the program and causes sudden shut down of service.
Description
Bug Summary:
Everything works until someone loads document with big table in it or big csv document. I can't find any error on logs even in debug mode.
i tried tika, changed extraction to chatgpt but still having the same issue. file is uploading correctly but when i submit it, it breaks the program and causes sudden shut down of service.
could you lead me to detailed logs of RAG or any environment variable or way to close big document uploads or file uploads all together. I can'e debug this error :/
there is no customization on the platform.

After weeks of struggling to find a solution, I finally gave in and opened an issue on GitHub. And guess what? Less than an hour later, I might have found the solution! 🎉 It seems like the problem was related to a bug involving uvicorn and asyncio on Windows, specifically in production with SSL.
I've got a long testing journey ahead, but right now, it looks like things are working. I’d like to leave this issue open for about a week, as I think it could help others facing similar problems. I’m actively working on it and will share my test results soon. A PR is also in the works!
Thanks for your patience!

repo: open-webui/open-webui


text:
Hide RAG References.

Is your feature request related to a problem? Please describe.
No. This is just an idea I'd like to have implemented.
Describe the solution you'd like
It would be great to have an option to "hide" the references coming from the RAG. If you use doc search, you see the references and the clear text from the document. There might be cases, where this is unwanted. E.g. I have "sensitive" contents that the LLM should filter out, yet I can see the entire documents.
Describe alternatives you've considered
I have a workaround by feeding the system prompt with the most important content needed. This needs a higher context size.
Additional context
I hope you understand what I mean.
Thank you for reading and considering my idea/suggestion. Keep up your good work. :)

Not sure this is really what you want, if the AI has access to the content, there's always someone who will find a way to make the AI rewrite that content verbatim.  This works until it doesn't, removing the sensitive information might be the only solution there.


text:
Fix: Add proper exception handling to langfuse filter pipeline

The example Langfuse filter pipeline had unhandled exceptions on startup when checking the auth state, which led the pipelines server to keep restarting when the Langfuse filter was loaded with the incorrect API keys.

🚀🚀

repo: open-webui/pipelines


text:
FcPortConnectedToLtp association does not connect to FcPort

FcPortConnectedToLtp association seems to be faulty.
It connects the Ltp twice, but not the FcPort.

The association on UML level looks good:
the first member is the "_fcPort" of type "FcPort" and the second member is the "_ltp" of type "LogicalTerminationPoint".  (see uml parts below)
@openBackhaul: Please re-test or/and provide more information - it might be the case that the display of the core-model uml in a Papyrus version later then Mars causes "wrong" display of the associations and its labels.
        <packagedElement xmi:type="uml:Association" xmi:id="_Ixb_8FYnEeOVGaP4lO41SQ" name="FcPortConnectedToLtp" memberEnd="_Ixb_8VYnEeOVGaP4lO41SQ _IxS2AFYnEeOVGaP4lO41SQ">

          <ownedEnd xmi:type="uml:Property" xmi:id="_Ixb_8VYnEeOVGaP4lO41SQ" name="_fcPort" type="_b_lUAFYgEeOVGaP4lO41SQ" association="_Ixb_8FYnEeOVGaP4lO41SQ">

            <lowerValue xmi:type="uml:LiteralInteger" xmi:id="_Ixb_8lYnEeOVGaP4lO41SQ"/>

            <upperValue xmi:type="uml:LiteralUnlimitedNatural" xmi:id="_Ixb_81YnEeOVGaP4lO41SQ" value="*"/>

          </ownedEnd>

        </packagedElement>

		[...]

		 <packagedElement xmi:type="uml:Class" xmi:id="_b_lUAFYgEeOVGaP4lO41SQ" name="FcPort">

		[...]

		<ownedAttribute xmi:type="uml:Property" xmi:id="_IxS2AFYnEeOVGaP4lO41SQ" name="_ltp" type="_eEpDMFX4EeOVGaP4lO41SQ" association="_Ixb_8FYnEeOVGaP4lO41SQ">

Seems to be fine in the YANG:
  grouping fc-port {
    leaf-list logical-termination-point {
      type leafref {
        path "/core-model:control-construct/core-model:logical-termination-point/core-model:uuid";
      }
      max-elements 2;
      description
        "....";
    }

AI @demx8as6: drive topic in OTCC OIM - tag label "UML_to_be_changed"

repo: openBackhaul/core


text:
fix: Change permission from CAMERA to WRITE EXTERNAL STORAGE

Fixes #141
Summary
Changed permission from CAMERA to WRITE EXTERNAL STORAGE when clicked on "share" in appbar in CustomerProfileActivity.
Observed Behaviour

Expected Behaviour

Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with ./gradlew check to make sure you didn't break anything

[x] If you have multiple commits please combine them into one commit by squashing them.

@abhijitramesh This PR is good to go.

repo: openMF/mifos-mobile-cn


text:
Update links to point to 2.8

2.8 got released, so the links needed to be updated. :bowtie:

download/index.html and download/other/index.html is fine.
The manuals and pdf usually get generated, so don't edit manually!

repo: openSUSE/obs-landing


text:
NEW URL for VD data

Hi,
I'm caring about datas for vd. Please find the new url : https://www.vd.ch/toutes-les-actualites/hotline-et-informations-sur-le-coronavirus/point-de-situation-statistique-dans-le-canton-de-vaud/
where you can find datas uptodate.
BR
JR

Thx @jeanbrouille !

@jeanbrouille will the figures regarding the patients in instensive care units also be published on that site?

We are currently consuming the datawrapper API of the website of VD, it seems the new URL still uses the same datawrapper source, so currently no change is needed on our side.

If I search in the code of this repository I can find this URL 3 times here : https://github.com/openZH/covid_19/search?q=https%3A%2F%2Fwww.vd.ch%2Ftoutes-les-actualites%2Fhotline-et-informations-sur-le-coronavirus%2F&unscoped_q=https%3A%2F%2Fwww.vd.ch%2Ftoutes-les-actualites%2Fhotline-et-informations-sur-le-coronavirus%2F

@stat1x true, I updated the SCRAPER_SOURCE so that the correct source is noted in the CSV.

@tlorusso "will the figures regarding the patients in instensive care units also be published on that site?" Yes new data coming up tomorrow.

authors: jeanbrouille metaodi stat1x tlorusso


text:
Add de_baca

Received via FOIA Request.
They are awesome and super helpful!

Tracking here: https://github.com/openaddresses/openaddresses/pull/3124

repo: openaddresses/openaddresses


text:
added other address layer props, added buildings/parcels layers

Updates:

added unit, city, and postcode to addresses layer
added parcels layer
added buildings layer

Re-run this please.

I'm not sure that the re-run thing works with "data-pls" (it was a feature of the older CI system). It looks like that job failed due to timeout. The server might not be up to handling the type of queries we make?

authors: iandees trescube