Added the SVG function.

I implemented the SVG function.
The current implementation of the SVG tag does not work because SVG attributes cannot be set directly, they have to be set by calling a setAttribute function.
More information can be found here:
https://github.com/Matt-Esch/virtual-dom/issues/55
The solution is to create a hook for each attribute, and call that attribute hook when the attribute is set.
Mercury implements this function, and I basically copied their implementation:
https://github.com/Raynos/virtual-hyperscript/blob/master/svg.js
There are many things unclear to me though.  So please take a look at the code before accepting it.
I think eventually SVG should have its own type because normal HTML nodes cannot be nested within SVG elements, and the current implementation does not check that.

Alright, I started on the elm-svg package for this, but I have stalled on figuring out the entire spec.
As this thread sorts out, the W3 docs seem to be the best reference (elements, attributes, properties) and I think we should go from there. So I'm going to close this for now, and if you are interested in taking a swing at elm-svg, that would be amazing!


merge2- added support for new import syntax

This will support the new import syntax e.g.
import * as merge2 from "merge2";

As well as
import merge2 = require("merge2");

@stephenlautier thanks mate!


Bug: Incorrect focus when normal text is selected

When we create a list of elements, and the last element is empty, then selecting 'normal text' creates a paragraph, but there is no focus on it
Steps To Reproduce

Make a list of several items
In the very last element, do not write anything and choose 'normal text'

Link to code example: https://playground.lexical.dev/
The current behavior
https://youtu.be/VP4XkFs7NKY
A paragraph is being created, but there is no focus on it
The expected behavior
Focus on the paragraph

I think we just have to add editor.focus(); to to the end of the callback for that dropdown button. Want to have a go at submitting a PR @darfilp? 🙂

@thegreatercurve
It didn't help to just add an asynchronous function and first remove the selection, and then add it, but it seems to me this option is not beautiful
      editor.update(
        () => {
          const selection = $getSelection()
          if ($isRangeSelection(selection)) {
            $wrapNodes(selection, () => $createParagraphNode())
          }
        }
      )

      setTimeout(() => {
        editor.blur()
        editor.focus()
      }, 0)

@thegreatercurve
It didn't help, so I did it differently. I added an asynchronous function, then removed and added focus. But I think this solution is not beautiful
      editor.update(
        () => {
          const selection = $getSelection()
          if ($isRangeSelection(selection)) {
            $wrapNodes(selection, () => $createParagraphNode())
          }
        }
      )

      setTimeout(() => {
        editor.blur()
        editor.focus()
      }, 0)

@darfilp I've not had a chance to dig into it but it's therefore probably an issue with the insertAfter or replace logic on the ListItemNode


Add a full C++20 & C++23 compatibility layer

This PR focuses on building the infrastructure to allow the use of modern C++20 and C++23 features if available. Implementing the library features into the project is outside this PR's scope. Instead, this PR is focused on laying the foundation so that we can gradually add newer features to the library while still maintaining backward support with C++17!

My first initial revision of what this would look like has been finished. I would though like to request permission to add C++20 and C++23 to the CI so we can properly test against this.

Applied requested changes and also added in a few more items that I found were missing.

Also applied an example of how in the future we can use std variants while still providing a C++17 variant also with std::source_location. Though to get the internal source_location to work with std::source_location I did have to redo how we currently handled the struct.

I've come across a strange error with the current approach I've never experienced before. Currently the preprocessor gets mega confused with the project with how one would traditionally switch between two implementations with macros if one target is compiling for C++20 but another target is compiling for C++17. It appears this trips up the preprocessor and causes a link time error. What is happening is essentially as follows:

libassert internally sets its compile option to C++17.
The target demo then sets its compile options to C++20.
The preprocessor sees C++20 and then copy and pastes the correct items for C++20.
Then the linker trys to perform linking but instead sees C++17 for some reason.
This causes a linker error and the project fails.

If both targets are using the same C++ version then this issue does not occur.
Some of this is speculation based on what I've observed through debugging and its a strange issue. I'm not 100% sure what would be the best way to approach it without doing some compilation checking through cmake or something to verify what C++ version we are using, but this would be much more work.
What are your thoughts on this issue?

I haven’t read the new changes yet but this sounds expected. If you conditionally enable something based on the standard and that makes changes in the compiled library then it won’t be compatible with code built with a different standard. You’re lucky you got a linker error, this can easily be a nasty ODR violation that doesn’t manifest until it causes a segfault :P
I see no reason to go out of the way to use newer C++ features like this. The C++17 version works and I’m not sure I see the benefit in this. It can only lead to complexity, code duplication, and ODR problems. I’m happy to support newer things if it makes a difference for end-users, though.

I haven’t read the new changes yet but this sounds expected. If you conditionally enable something based on the standard and that makes changes in the compiled library then it won’t be compatible with code built with a different standard. You’re lucky you got a linker error, this can easily be a nasty ODR violation that doesn’t manifest until it causes a segfault :P
I see no reason to go out of the way to use newer C++ features like this. The C++17 version works and I’m not sure I see the benefit in this. It can only lead to complexity, code duplication, and ODR problems. I’m happy to support newer things if it makes a difference for end-users, though.

That is fine. I'll make a final adjustment and get everything together.

Thank you 🙏

For proof of concept on the user generated static_assert you can see it in action here:
https://godbolt.org/z/hY7fz5rKG
For info on what it is here is the specification:
https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2023/p2741r1.pdf

MSVC is breaking because of using __VA_OPT__ https://godbolt.org/z/P16d3Gr5c

Since this doesn't appear to be an issue you introduced I'm going to go ahead and merge and fix on dev

Oh, it was introduced here due to #define LIBASSERT_CPLUSPLUS _MSVC_LANG. But we can workaround that.


refactor(concerto-ui): Collapse concerto-ui-core and concerto-ui-react

Addresses #21 by combining the concerto-ui packages into a single package called concerto-ui.
This is a BREAKING CHANGE because it renames the package. Specifically, the following packages will no longer exist:

@accordproject/concerto-ui-core
@accordproject/concerto-ui-react

Something weird is happening where already merged commits (e6a3704 80be87a 61891b4) are here now, possibly from the merges (5966516 8a62739). It could be worth starting from a clean branch?


Registry error message

I get the following error :

eslint-config-plugin:flowtype   😟  MISSING!  Not installed.
😟  PKG ERR!  Not in the package.json. Found in: /.eslintrc.json
⛔  NPM ERR!  Registry error Package eslint-config-plugin:flowtype doesn't exist

I'm getting similar registry errors for ones that do actually exist.

I have the same issue with eslint-config-plugin:flowtype
In package.json
"devDependencies": {
    "eslint-plugin-flowtype": "2.35.0",
   ...
}

In .eslintrc.js
  plugins: [
    "flowtype",
    ...
  ],

But npm-check emits
eslint-config-plugin:flowtype   😟  MISSING!  Not installed.
                                😟  PKG ERR!  Not in the package.json. Found in: /.eslintrc.js
                                ⛔  NPM ERR!  Registry error Package `eslint-config-plugin:flowtype` doesn't exist

This does not suppress the error
--ignore eslint-plugin-flowtype
But this does
--ignore eslint-config-plugin:flowtype
What's strange is that I have other eslint plugins that do not cause any problems. What could be unique about flowtype?


github/smarthook.js is sending replying with 500 from the webtask

I used this guide to set up a simple github-webhook-connected webtask: https://webtask.io/docs/sample_github
It works fine up to the point where the response of the webtask is read by GitHub. This leads to the task working perfectly fine, but the very unattractive side effect that the callback for error and/or success messages does not work properly.
Steps to reproduce

Follow guide that is linked above
Check deliveries in the settings of your github repo
Find HTPP {500} responses here

Log of one execution of the webhook:
[20:11:01.939Z]  INFO wt: connected to streaming logs (container=wt-koljaz-***-0)
[20:11:12.779Z]  INFO wt: webtask container assigned
[20:11:13.880Z]  INFO wt:
    {
      "code": 500,
      "error": "Script generated an unhandled asynchronous exception.",
      "details": "ReferenceError: writeHead is not defined",
      "name": "ReferenceError",
      "message": "writeHead is not defined",
      "stack": "ReferenceError: writeHead is not defined\n    at args (/data/smarthook.js:99:21)\n    at Request.eval [as _callback] (eval at <anonymous> (/data/smarthook.js:55:69), <anonymous>:49:28)\n    at Request.self.callback (/data/_verquire/request/2.56.0/node_modules/request/request.js:354:22)\n    at Request.emit (events.js:110:17)\n    at Request.<anonymous> (/data/_verquire/request/2.56.0/node_modules/request/request.js:1207:14)\n    at Request.emit (events.js:129:20)\n    at IncomingMessage.<anonymous> (/data/_verquire/request/2.56.0/node_modules/request/request.js:1153:12)\n    at IncomingMessage.emit (events.js:129:20)\n    at _stream_readable.js:908:16\n    at process._tickDomainCallback (node.js:381:11)"
    }
[20:11:13.880Z]  INFO wt:
    {
      "code": 500,
      "error": "Script generated an unhandled asynchronous exception.",
      "details": "ReferenceError: writeHead is not defined",
      "name": "ReferenceError",
      "message": "writeHead is not defined",
      "stack": "ReferenceError: writeHead is not defined\n    at args (/data/smarthook.js:99:21)\n    at Request.eval [as _callback] (eval at <anonymous> (/data/smarthook.js:55:69), <anonymous>:49:28)\n    at Request.self.callback (/data/_verquire/request/2.56.0/node_modules/request/request.js:354:22)\n    at Request.emit (events.js:110:17)\n    at Request.<anonymous> (/data/_verquire/request/2.56.0/node_modules/request/request.js:1207:14)\n    at Request.emit (events.js:129:20)\n    at IncomingMessage.<anonymous> (/data/_verquire/request/2.56.0/node_modules/request/request.js:1153:12)\n    at IncomingMessage.emit (events.js:129:20)\n    at _stream_readable.js:908:16\n    at process._tickDomainCallback (node.js:381:11)"
    }
[20:11:13.882Z]  INFO wt:
    {
      "code": 500,
      "error": "Script generated an unhandled asynchronous exception.",
      "details": "ReferenceError: writeHead is not defined",
      "name": "ReferenceError",
      "message": "writeHead is not defined",
      "stack": "ReferenceError: writeHead is not defined\n    at args (/data/smarthook.js:99:21)\n    at Request.eval [as _callback] (eval at <anonymous> (/data/smarthook.js:55:69), <anonymous>:49:28)\n    at Request.self.callback (/data/_verquire/request/2.56.0/node_modules/request/request.js:354:22)\n    at Request.emit (events.js:110:17)\n    at Request.<anonymous> (/data/_verquire/request/2.56.0/node_modules/request/request.js:1207:14)\n    at Request.emit (events.js:129:20)\n    at IncomingMessage.<anonymous> (/data/_verquire/request/2.56.0/node_modules/request/request.js:1153:12)\n    at IncomingMessage.emit (events.js:129:20)\n    at _stream_readable.js:908:16\n    at process._tickDomainCallback (node.js:381:11)"
    }
[20:11:13.882Z]  INFO wt:
    {
      "code": 500,
      "error": "Script generated an unhandled asynchronous exception.",
      "details": "ReferenceError: writeHead is not defined",
      "name": "ReferenceError",
      "message": "writeHead is not defined",
      "stack": "ReferenceError: writeHead is not defined\n    at args (/data/smarthook.js:99:21)\n    at Request.eval [as _callback] (eval at <anonymous> (/data/smarthook.js:55:69), <anonymous>:49:28)\n    at Request.self.callback (/data/_verquire/request/2.56.0/node_modules/request/request.js:354:22)\n    at Request.emit (events.js:110:17)\n    at Request.<anonymous> (/data/_verquire/request/2.56.0/node_modules/request/request.js:1207:14)\n    at Request.emit (events.js:129:20)\n    at IncomingMessage.<anonymous> (/data/_verquire/request/2.56.0/node_modules/request/request.js:1153:12)\n    at IncomingMessage.emit (events.js:129:20)\n    at _stream_readable.js:908:16\n    at process._tickDomainCallback (node.js:381:11)"
    }
[20:11:13.883Z]  INFO wt:
    Code generated an uncaught exception:  ReferenceError: writeHead is not defined
        at args (/data/smarthook.js:99:21)
        at Request.eval [as _callback] (eval at <anonymous> (/data/smarthook.js:55:69), <anonymous>:49:28)
        at Request.self.callback (/data/_verquire/request/2.56.0/node_modules/request/request.js:354:22)
        at Request.emit (events.js:110:17)
        at Request.<anonymous> (/data/_verquire/request/2.56.0/node_modules/request/request.js:1207:14)
        at Request.emit (events.js:129:20)
        at IncomingMessage.<anonymous> (/data/_verquire/request/2.56.0/node_modules/request/request.js:1153:12)
        at IncomingMessage.emit (events.js:129:20)
        at _stream_readable.js:908:16
        at process._tickDomainCallback (node.js:381:11)
[20:11:14.533Z]  INFO wt: webtask container recycled

The problem here seems to be that the writeHead() is not a function in this scope, but rather has to be called on the response (res). Adding this actually solves the issue, the log looks afterwards like:
[20:31:30.122Z]  INFO wt: connected to streaming logs (container=wt-koljaz-***-0)
[20:32:35.974Z]  INFO wt: webtask container assigned
[20:33:25.738Z]  INFO wt: webtask container recycled

And the responses are with valid codes, for both errors and successes. I will send a pull request to fix this shortly.

@ArSn Thanks! I'm using your version and it works fine.

@ArSn your PR has been merged :)

@chenkie Awesome, thanks!


Add package.json so module can be imported via npm

I've added a minimal package.json file so that this plugin can be imported via npm. You may want to add further info. See https://docs.npmjs.com/files/package.json
I removed _0.7 from the repo name because npm apparently couldn't handle the underscore in the url. If you add this to the npm repo, it can be imported without referencing github and this problem can be avoided.
https://www.npmjs.com/
Here's the entry in package.json for the app that consumes this plugin.
"leaflet-singleclick": "github:azavea/leaflet-singleclick#feature/lf/module"
And in the file that imports the plugin.
import L from 'leaflet';
import 'leaflet-singleclick';

Any update on when this will be merged?  It would be nice to have via npm


Not working with nuxt3

Doesnt render anything after including in the nuxt component
is there a specific setup for this ?

import Slider from '@vueform/slider';
then loading in components
components: {
Slider,
},

Did you include the style as well :
<style<EMAIL_ADDRESS>

Working fine for me after including the styles.
You could also add import<EMAIL_ADDRESS>inside your


fix: upgrade dependencies

📝 Changed routes:

/articles/[slug]

(view full size)

Commit be64610ef86abf1ff555f5b03914d8ddc0221843 (https://demo-marketing-site-nextjs-nf7qj72tw.sanity.build).


[office-addin-lint] support TypeScript 3.8 syntax

The new syntax in TypeScript 3.8 is not supported.
Could you update the dependent packages?
import type { IObjectWithKey } from "@uifabric/utilities";

  1:14  error  Parsing error: '=' expected  prettier/prettier

Thank you.

Thank you for reporting the issue @clavx .
We were work on a fix as part of our summer release.

Re-assigning. Update Prettier and Typescript

Form what I can see this has already been updated.  @clavx, can you confirm if this is still a problem for you?

Thank you for your response.
I've confirmed that it works fine.
I think this issue was resolved by upgrading the eslint version from "6.8.0" to "7.20.0" by the https://github.com/OfficeDev/Office-Addin-Scripts/pull/388.


Namespaces, unbinding and the .on() syntax

Hi,
it would be nice to manipulate hoverIntent with jQuery's .on syntax which offers namespacing and easy unbinding with .off(). When there would be no listeners left, the bindings should be automatically removed to prevent memory leaks (no need for the manual destruction suggested in #43).
$(selector).on('hoverIntent.namespace' [, selector] , handlerIn, handlerOut);
// or
$(selector).on('hoverIntent.namespace' [, selector] , handlerInOut);
// and then
$(selector).off('hoverIntent.namespace');
// or
$(selector).off('.namespace');

It should be possible to hook on jQuery's event system to make it happen. Thank you

Is there any information about this issue? Was this functionality implemented?

Hi @louisameline and @dim2k2006! Thanks for the ping on this. This might be a good idea, though can you please let me know if unbinding events via $(selector).off('.hoverIntent') would be a sufficient solution for your use case?
I'd just like some more discussion before deciding whether or not this is a common enough use case to include it in the upcoming milestone. :)

Hello, no, I need to apply my own namespaces. It feels wrong that you ask me to use your namespace anyway, it's precisely done for the user to customize his stuff. Jquery's event system is built exactly to handle libraries like hoverintent and you're missing features by not using it. I can't feel comfortable with this library if you don't handle events the way jquery does, this is a jquery plugin after all. And I really mean no offense but as a developer, the fact that this library is missing that point doesn't make me confident about the author's skills and doesn't make me want to use it.  I mean it's just the impression it gives. But that might just me. Thank you.

Hi @louisameline! I'm sorry, but I actually took offense... which is usually what happens when you ask someone not to ;)
You should be confident in the author's and maintainer's skills, and the quality of the code, when a plugin (never part of the core library) is still compatible and actively in-use 10 YEARS after it was created... and the only open issues are of the feature-request variety.
We've made changes to modernize hoverIntent before. Per this issue (#55) I'm not opposed to extending how hoverIntent is applied to elements so long as it can be done without breaking existing implementations. Someone just needs to write the pull request.

Hello, I apologize for hurting your feelings.
It's a good thing that this library works after 10 years, kudos for that :) What I tried to say, with the wrong words, is that IMHO it would need a fresh paint coat to meet the API quality I expect from a modern plugin.
As for breaking existing implementations, that's what major versions are for in semver, I see no issue here. The current API is unpractical and will be redundant with jQuery's event system, so it should be removed from a v2.
As a side note, the unbinding thing is real issue though, it leads to memory leaks. I was initially discouraged to make a PR as I was not sure if this project was still maintained. It seems that a v1.9 by @usmonster has been in the works for a long time, but his fork has many branches, maybe he could clarify where we can find the latest project files? It would be nice if there was a dev branch here on this project instead.
Thanks.

Hi @louisameline!

It seems that a v1.9 by @usmonster has been in the works for a long time, but his fork has many branches, maybe he could clarify where we can find the latest project files?

To address your question/misunderstandings:

v1.9 (not yet released) is the master branch of this repository. Other versions are tagged.
My personal fork's branches are meaningless for you, as the repo description says. ;)
Yes, the milestone has 3 "easy" non-dev tasks left, which haven't been done for a while. My bad! In any case, the master branch is functionally equivalent to what will eventually be  v1.9 and is safe to use in production.

As for the change you propose, I agree with your reasoning to use the "jQuery way" of event handling, especially in preference over #43. Still, you shouldn't be surprised that we'd of course want to discuss your specific use case to see if there's general enough need, to make sure the problem (memory leak) exists on the current version, and only then decide if & how to prioritize it.
All that said, I think a PR would be welcome for this, if you're willing to make one. If not for v1.9, I can see this in a v2.0, if @briancherne agrees.

Ok, thank you for your explanations.


Preliminary support for stream guard.

This adds some basic support for cuda streams #234.
Note that this has not been tested yet and is even unlikely to compile as I don't have access to a cuda enabled box at the moment.
Usage would be as follow.
let stream = tch::CudaStream::from_pool(/*high_priority=*/false, /*device_idx=*/1);
let _guard = tch::CudaStreamGuard::new(stream);
// The operations should here and until the end of the scope should take place in the created stream.

There are still some difficulties to get this merged.

The PyTorch C++ headers this require have references to the standard cuda headers.This PyTorch issue has been opened to see if we can get around this. In the meantime adding some .include("/usr/lib/cuda/include") in torch-sys/build.rs might help.
This may require linking with c10_cuda, e.g. by adding the following line to torch-sys/build.rs.

println!("cargo:rustc-link-lib=c10_cuda");

It may also be required to link cudart explicitely.

Hey, curious if there is any movement on adding the stream api to tch-rs. I am working on an inference pipeline where having control over the cuda stream would be beneficial for eeking out some more performance.

Not much progress I'm afraid. The change in this PR is pretty straightforward but the trickiness is that the required headers end up depending on the cuda headers and these headers may not be installed if cuda was vendored with pytorch rather than properly installed. The related PyTorch issue https://github.com/pytorch/pytorch/issues/55454 hasn't seen much activity, (also related is https://github.com/pytorch/pytorch/issues/47743 ).
Having these headers available would unlock both support of cuda stream and cuda graph for tch so would be great to have but it's a bit stuck at the moment.

Vendoring the cuda headers might be a bit tricky. A specific version of tch is tied to a specific release of libtorch but these may used different versions of cuda (which I guess is pretty helpful to users with older gpus/nvidia drivers).
No clue how much effort it would be to host fully self-contained binaries, but I guess it might be non-trivial as these would have to run in a wide variety of environments - maybe there are some specific bits of the PyTorch ecosystem that could be leveraged for this e.g. pytorch/builder.
Another possibility would be for tch to try and detect the cuda install and only activate the advanced cuda functionalities (cuda guards and all) if these are available.
Overall the best would certainly be if the libtorch binaries could embed a bit more of the header files but indeed there hasn't been much progress on this over the last year so we should probably find a good way around this.


HomeLoanRateRuleBook example not working

Hello,
Was trying to run through your HomeLoan example and it doesn't appear to be returning any result.  I have the ApplicantBean and the Main classes copied verbatim.  However instantiating the HomeLoanRateRuleBook object gives me a compile error because the following is incompatible:
HomeLoanRateRuleBook homeLoanRateRuleBook = RuleBookBuilder.create(HomeLoanRateRuleBook).withResultType(Double.class)       .build();
Results in "Incompatible types".  Required HomeLoanRateRuleBook, found RuleBook
If I try casting as HomeLoanRateRuleBook or even setting the variable as:
RuleBook<Double> homeLoanRateRuleBook = RuleBookBuilder.create(HomeLoanRateRuleBook).withResultType(Double.class)       .build();
It does not work.  Any time I run through the steps the RuleBook result (_result) is coming back null.  Only when I specify a defaultResult does it return a value back.  Any ideas?

There was a little errata in that example. I just corrected it and verified that the example ran. so, thanks for pointing that out. It looks like it was left over from the v0.5 README update.
If you set a Result type then you will need to specify a default result. The reason for this is because the Result is chained across rules and the default result initializes it so that there's something to chain.
I used the following code to run it.
public class ExampleSolution {
    public static void main(String[] args) {
        HomeLoanRateRuleBook homeLoanRateRuleBook = (HomeLoanRateRuleBook)RuleBookBuilder.create(HomeLoanRateRuleBook.class).withResultType(Double.class)
                .withDefaultResult(4.5)
                .build();
        NameValueReferableMap facts = new FactMap();
        facts.setValue("applicant", new ApplicantBean(650, 20000.0, true));
        homeLoanRateRuleBook.run(facts);

        homeLoanRateRuleBook.getResult().ifPresent(result -> System.out.println("Applicant qualified for the following rate: " + result));
    }
}

You can also declare the rulebook like this.
RuleBook<Double> homeLoanRateRuleBook = RuleBookBuilder.create(HomeLoanRateRuleBook.class).withResultType(Double.class)
                .withDefaultResult(4.5)
                .build();

Or like this
HomeLoanRateRuleBook homeLoanRateRuleBook = (HomeLoanRateRuleBook)RuleBookBuilder.create(HomeLoanRateRuleBook.class).withResultType(Double.class)
                .withDefaultResult(4.5)
                .build();

Thank you for the update.  I think ensuring the developer sets a defaultResult is an important call out.


How to create Python extension module that uses TensorFlow C API?

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): macOS 10.13.6
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary
TensorFlow version: 1.14.0
Python version: 3.7.3
Installed using virtualenv? pip? conda?: conda
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: n/a
GPU model and memory: n/a

Describe the problem
I've written a Python extension module that uses TensorFlow through the C API. I installed the API as described in https://www.tensorflow.org/install/lang_c. On its own, my module works correctly. But if I import my extension module and then also import tensorflow, Python crashes with this error.
[libprotobuf ERROR external/protobuf_archive/src/google/protobuf/descriptor_database.cc:58] File already exists in database: tensorflow/core/protobuf/master.proto
[libprotobuf FATAL external/protobuf_archive/src/google/protobuf/descriptor.cc:1370] CHECK failed: GeneratedDatabase()->Add(encoded_file_descriptor, size):
libc++abi.dylib: terminating with uncaught exception of type google::protobuf::FatalException: CHECK failed: GeneratedDatabase()->Add(encoded_file_descriptor, size):
Abort trap: 6

I believe this happens because the C API includes its own complete copy of TensorFlow, so now I get two different copies loaded into the same process at the same time.
What is the solution to this? How can I have Python code that uses TensorFlow, and also invokes C code that uses TensorFlow?
Provide the exact sequence of commands / steps that you executed before running into the problem
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@peastman Please take a look at the similar issue and let me know if it helps. Thanks!

Thanks.  I'm not sure what that has to do with this case?  None of my code does anything with protobuf directly.  I just have a module that links against the libtensorflow that comes with the C API.  Then I open up a Python console and try importing modules.  I can either import the module I wrote or import TensorFlow and either one works.  But if I try to import both, Python immediately crashes.

Is there any solution to this problem?

Having the same issue on Mac OS Catalina. Found this solve by downgrading pyarrow, but it does not work for me:
https://superuser.com/questions/1491364/attempted-import-of-apache-beam-in-python3-on-mac-throws-fatal-protobuf-error

I'm still having the same issue. I tried using pyarrow 0.14.0 and the newest 0.15.1. those pyarrow didn't works in my catalina

reinstalling tensorflow works for me

Hi There,
We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help.
This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information.

This problem is still present in TensorFlow 2.x.  Nothing has changed since I filed this issue a year and a half ago.  Do not close this issue.

Please reopen this issue!  It has not been fixed.  It is still present in the most recent version of TensorFlow.  Nothing at all has changed.
Why was this closed?  Will anyone from the TensorFlow team even so much as post to acknowledge the existence of this issue, which is a showstopper and has forced me to put all TensorFlow support on hold?

Hi @peastman , I also encountered the same problem when building my c++ project. I found that when I import tensorflow before my lib, everything works normally. Maybe you can try it.
See like this:
root@f2ddedcd3964:/# ipython
Python 3.7.7 (default, Mar 23 2020, 22:36:06)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.13.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import mylib

In [2]: import tensorflow
[libprotobuf ERROR external/com_google_protobuf/src/google/protobuf/descriptor_database.cc:118] File already exists in database: tensorflow/core/framework/tensor.proto
[libprotobuf FATAL external/com_google_protobuf/src/google/protobuf/descriptor.cc:1367] CHECK failed: GeneratedDatabase()->Add(encoded_file_descriptor, size):
terminate called after throwing an instance of 'google::protobuf::FatalException'
  what():  CHECK failed: GeneratedDatabase()->Add(encoded_file_descriptor, size):
Aborted (core dumped)
root@f2ddedcd3964:/# ipython
Python 3.7.7 (default, Mar 23 2020, 22:36:06)
Type 'copyright', 'credits' or 'license' for more information
IPython 7.13.0 -- An enhanced Interactive Python. Type '?' for help.

In [1]: import tensorflow

In [2]: import mylib

In [3]:

Ideally you could use the python versions implementation for your C extension. I.e. don't link TensorFlow but use the C header files. For this to work you'd need to still import tensorflow in your extension. If you want to make it work both if you have only the C library version and a full tensorflow python binding install, then you could check in your extensuion whether to dlopen() (or windows equivalent) the C library... i.e. check if you can find the symbols are already available somehow with dlsym() ... This is definitely in a tricky area where using the python install if possible even for your C extension is preferable.

@peastman ,
Can you please check this comment from the developer and test with the latest tensorflow stable v2.8.It helps.Thanks!

I long ago gave up on trying to support TensorFlow.  And there's no longer any demand for it.  In the field I work in (molecular simulation), nearly everyone has moved to PyTorch.

@peastman ,
Could you please feel free to move this issue to closed status.Thanks!

I don't think the issue should be closed until it's actually fixed.  The comment you linked above doesn't indicate a fix.  It just suggests a very complicated workaround.  I'm no longer using TensorFlow, but this is still a serious problem that will affect other people who are.

@peastman Could you please follow the steps below to create a python extension module that uses TF C API;

Install the TensorFlow C library
Write a C file that will implement your extension module
Compile your extension module
Install your extension module.
Once your extension module is compiled, you can install it using the Python pip package manager.

Thank you!

As I said above, I haven't used TensorFlow in years.  I gave up on it, because this was a showstopper and it didn't seem likely to ever get fixed.
In any case, the series of steps you listed is exactly what I was doing.  Has the problem been fixed, or will it still crash if you try to import both modules as once?

I am also hitting this, and I agree this is related to having two copies of tensorflow being loaded. For example, in my case the pip tensorflow package includes its own tensorflow .so, and there's also a system tensorflow .so (for the C API). This issue happens despite them being from the same version of tensorflow.

FWIW I found that for my case, this happens because of libtensorflow_framework.so being re-used. First the system tensorflow_framework.so is loaded, then when you attempt to import tensorflow, rather than using its own libtensorflow_framework.so (which its libtensorflow_cc.so should link to normally), it re-uses the already loaded version of libtensorflow_framework.so which causes the issue. For now, I'm working around this by patching the .so files in the python tensorflow package to be a different version, for example:
sudo mv libtensorflow_framework.so.2 libtensorflow_framework.so.3
find -name '*.so' | xargs -n 1 sudo patchelf --replace-needed libtensorflow_framework.so.2 libtensorflow_framework.so.3

It would be nice if I didn't have to do this, though. Other suggested work-arounds like RTLD_DEEPBIND didn't work for me, I /guess/ because of the re-direction through libtensorflow_framework I mentioned above. Two issues related to this are:
https://github.com/tensorflow/tensorflow/issues/13963
https://github.com/protocolbuffers/protobuf/issues/5914
which are both closed both with the rationale that it isn't the issue of that project, AFAICT.
It seems likely to me that there are multiple ways this error can manifest, by the way.

i would like to resolve this issue


PropTypes are missing in info panel in static build

Couldn't find this issue anywhere so I am reporting it here.
It seems that when using the info-addon, the proptypes to a components works when you run storybook locally, but all proptypes are defaulted to type node in a static build of storybook.
The required field is also reset to no in a static build. Default seems to work though.
Here is a picture of it running locally

And here is how it looks once it's built static

Versions are

@storybook/react v3.2.4
@storybook/addon-info v3.2.4

I think I know what's happening here. On prod, PropTypes get stripped out because it's not necessary in the traditional prod environment sense. Also, the babel-plugin-react-docgen doesn't run.

Am also facing this issue with static builds of storybook. Any suggested workarounds until a fix is put in?

There's really no workaround unfortunately. I don't think you can use a custom .babelrc for static builds.
I'll fix it when I get a chance.

A custom .babelrc would only be employed on non-static builds?

@DanielJRutledge unfortunately, yes. I think I'm gonna add it into the prod babel config for now and refactor the function that takes the custom babelrc later.

Think this issue has been fixed when we refactored the server code to the core package.


Turn some of the "Source generator cookbook" into official documentation

On https://learn.microsoft.com/en-us/dotnet/csharp/roslyn-sdk/source-generators-overview, it says "The Source Generators Cookbook goes over some of these examples with some recommended approaches to solving them."
I recently finished writing a source generator, and the Source Generators Cookbook was incredibly valuable 🙂
I'd like to ask that some of the Source Generators Cookbook be turned into official documentation on https://learn.microsoft.com/
In particular, I found these parts to be very helpful:

Use functionality from NuGet packages
Consume MSBuild properties and metadata
Issue Diagnostics

Thanks! 🙂

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

ID: 99a4410c-4c8d-0107-845b-9a951bb76682
Version Independent ID: f1ed9873-3e29-b4bd-2dbb-44dd9a05d790
Content: Source Generators
Content Source: docs/csharp/roslyn-sdk/source-generators-overview.md
Product: dotnet-csharp
Technology: csharp-roslyn
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Adding @KathleenDollard
This is the direction we're heading toward.


kubo and transmission modules conflict on wmem_max

Describe the bug
Attempting to upgrade from 22.05 to 23.11, the kubo and transmission modules have a conflict:
error: The option `boot.kernel.sysctl."net.core.wmem_max"' is defined multiple times while it's expected to be unique.

       Definition values:
       - In `/nix/store/9fpv0kjq9a80isa1wkkvrdqsh9dpcn05-source/nixos/modules/services/network-filesystems/kubo.nix': 2500000
       - In `/nix/store/9fpv0kjq9a80isa1wkkvrdqsh9dpcn05-source/nixos/modules/services/torrent/transmission.nix': "1048576"
       Use `lib.mkForce value` or `lib.mkDefault value` to change the priority on any of these definitions.
(use '--show-trace' to show detailed location information)

Steps To Reproduce
Steps to reproduce the behavior:

Enable services.kubo and services.transmission on 23.11
nixos-rebuild build

Expected behavior
An error-free build
Notify maintainers
@fpletz @astsmtl @vcunat @wizeman
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.85, NixOS, 22.05 (Quokka), 22.05.20230531.380be19`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.9.1`
 - channels(root): `"nixos-22.05"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Add a :+1: reaction to issues you find important.

Metadata after disabling transmission and upgrading:
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.82, NixOS, 23.11 (Tapir), 23.11.20240328.219951b`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos-22.05"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`


Add Neumorphic Login Screen

Description
Added a Neumorphic Login Screen. Solves #9

Dependencies added:
flutter_neumorphic
google_fonts
Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings

Hey @Aaliya-Ali there is some merge conflict, please resolve it first

Done, please check now.

Congrats @Aaliya-Ali 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐

SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.

@Roshaen Thanks for merging my PR! ✨
Here's the link to my Profile: https://www.clueless.tech/profile/102774315265495534997

Nice work @Aaliya-Ali 🎉


Pass in response to function call.

@darbyfrey what we worked on earlier :)

Thanks @ywong19, just published the new version to NPM
https://www.npmjs.com/package/apigee-mock


Facebook tracking appendix

Hi.
How to antitrack FB appendix? :
url.com/?fbclid=...
Is No-Skip-Parameter "fbclid" ok?
thx

Not sure what you are after, if you want to remove tracking parameters, there are better extensions for that.

Not sure what you are after, if you want to remove tracking parameters, there are better extensions for that.

ok, thanks. Which extensions do you know for that?

ClearURLs
Neat URL


Fixed a typo in docs/source/Transactional_Email/index.html

I changed a spelling issue which was annoying me.:
It deserved to be fly-swatted into oblivion.:

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.8 out of 9 committers have signed the CLA.:white_check_mark: elainechan:white_check_mark: mollyfriederich:white_check_mark: ksigler7:white_check_mark: LinkedList:white_check_mark: PAPERPANKS:white_check_mark: nalinbhardwaj:white_check_mark: thepriefy:white_check_mark: kstolteYDI:x: Ashwath SinghAshwath Singh seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @ApolloJamie  - thanks for your effort here!
So, on this pull request, you've created a pull from develop to master. In order to do a pull request to our main docs repo, you need to do a pull request into our Develop branch. You can do this by clicking on "compare across forks" on the create pull request page

Make sure the base fork is sendgrid/docs, and the base branch is develop, and then switch the head fork to be your personal fork, and the head branch to be the one in your fork you want to merge from.
I'm going to close this and let you create a new pull request.
Let me know if you have any questions!


Don't render empty \overline

\overline{ } without argument creates a small horizontal bar in Firefox/Linux. The expected behavior when compared to LaTeX is not rendering anything. The issue came up here: https://de.wikipedia.org/wiki/Wikipedia:Verbesserungsvorschläge#Rendering-Probleme

The expected behavior when compared to LaTeX is not rendering anything.

That's almost, but not quite always true.
I suppose the TeX input jax could ignore \overline and \underline if their arguments are empty.  It turns out that TeX is inconsistent with this, as accents like \hat{} will prices the hat, and \overrightarrow{} will produce the arrow.  So \overline and \underline are outliers in this sense.

Thanks for clarifying and sorry for being imprecise, I did not expect TeX to be so inconsistent.


Implement async LambdaInvokeFunctionOperator

Implement Async AwsLambdaInvokeFunctionOperator
Acceptance Criteria:

[ ] Unit Tests coverage in the PR (80% Code Coverage -- We will need to add CodeCov separately to measure code cov) with all of them passing
[ ] Example DAG using the async Operator that can be used to run Integration tests that are parametrized via Environment variables. Example - https://github.com/apache/airflow/blob/8a03a505e1df0f9de276038c5509135ac569a667/airflow/providers/google/cloud/example_dags/example_bigquery_to_gcs.py#L33-L35
[ ] Add proper docstrings for each of the methods and functions including Example DAG on how it should be used (populate
[ ] Exception Handling in case of errors
[ ] Improve the OSS Docs to make sure it covers the following:
[ ] Has an example DAG for the sync version
[ ] How to add a connection via Environment Variable & explain each of the fields. Example - https://airflow.apache.org/docs/apache-airflow-providers-postgres/stable/connections/postgres.html
[ ] How to use Guide for the Operator - example: https://airflow.apache.org/docs/apache-airflow-providers-postgres/stable/operators/postgres_operator_howto_guide.html

Explored the sync version of Operator, created a test Lambda function in our account, created a AWS policy to access this Lambda function and assigned to our integration-test user in AWS. Created an example DAG with the sync version and it runs fine. So, we're setup with the needed AWS configuration.
Will work next on figuring out how to implement the async version.

I am able to invoke a function using the asynchronous mode given by the library. It does invoke the function asynchronously & gives  a request ID in the response, however I don’t seem to find a utility given by AWS / boto3 to poll & fetch the status of this request ID.
Following is the response we get after invoking the function asynchronously,
Lambda response metadata: {'RequestId': '1307e121-e051-4961-ad8d-e1b62cda3f93', 'HTTPStatusCode': 202, 'HTTPHeaders': {'date': 'Wed, 13 Jul 2022 09:08:40 GMT', 'content-length': '0', 'connection': 'keep-alive', 'x-amzn-requestid': '1307e121-e051-4961-ad8d-e1b62cda3f93', 'x-amzn-remapped-content-length': '0', 'x-amzn-trace-id': 'root=1-62ce8b98-692e899a2d0ca16679e4f984;sampled=0'}, 'RetryAttempts': 0}
[2022-07-13, 09:08:40 UTC] {aws_lambda.py:101} INFO - Lambda function invocation succeeded: {'RequestId': '1307e121-e051-4961-ad8d-e1b62cda3f93', 'HTTPStatusCode': 202, 'HTTPHeaders': {'date': 'Wed, 13 Jul 2022 09:08:40 GMT', 'content-length': '0', 'connection': 'keep-alive', 'x-amzn-requestid': '1307e121-e051-4961-ad8d-e1b62cda3f93', 'x-amzn-remapped-content-length': '0', 'x-amzn-trace-id': 'root=1-62ce8b98-692e899a2d0ca16679e4f984;sampled=0'}, 'RetryAttempts': 0}

Boto3 Lambda functions list: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lambda.html#Lambda.Client.invoke

Why cant we do it as mentioned in this link?
https://stackoverflow.com/questions/66505773/how-to-get-the-status-of-a-aws-lambda-function-with-boto3
On Wed, Jul 13, 2022 at 3:17 PM Pankaj Koti @.***>
wrote:

I am able to invoke a function using the asynchronous mode given by the
library. It does invoke the function asynchronously & gives a request ID in
the response, however I don’t seem to find a utility given by AWS / boto3
to poll & fetch the status of this request ID.
Following is the response we get after invoking the function
asynchronously,
Lambda response metadata: {'RequestId': '1307e121-e051-4961-ad8d-e1b62cda3f93', 'HTTPStatusCode': 202, 'HTTPHeaders': {'date': 'Wed, 13 Jul 2022 09:08:40 GMT', 'content-length': '0', 'connection': 'keep-alive', 'x-amzn-requestid': '1307e121-e051-4961-ad8d-e1b62cda3f93', 'x-amzn-remapped-content-length': '0', 'x-amzn-trace-id': 'root=1-62ce8b98-692e899a2d0ca16679e4f984;sampled=0'}, 'RetryAttempts': 0}
[2022-07-13, 09:08:40 UTC] {aws_lambda.py:101} INFO - Lambda function invocation succeeded: {'RequestId': '1307e121-e051-4961-ad8d-e1b62cda3f93', 'HTTPStatusCode': 202, 'HTTPHeaders': {'date': 'Wed, 13 Jul 2022 09:08:40 GMT', 'content-length': '0', 'connection': 'keep-alive', 'x-amzn-requestid': '1307e121-e051-4961-ad8d-e1b62cda3f93', 'x-amzn-remapped-content-length': '0', 'x-amzn-trace-id': 'root=1-62ce8b98-692e899a2d0ca16679e4f984;sampled=0'}, 'RetryAttempts': 0}
—
Reply to this email directly, view it on GitHub
https://github.com/astronomer/astronomer-providers/issues/507#issuecomment-1183008904,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWQBBMPIP4PL6MNDBSPCOMTVT2GC7ANCNFSM53CT4PPQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

@phanikumv The answer in the link is not to get the status of the function invocation but it instead is invoking the function in synchronous mode and waiting by itself for the completion of the function.
InvocationType="RequestResponse" means synchronous invocation, InvocationType="Event" means asynchronous invocation, but there does not seem to be a subsequent method to fetch the status of the asynchronous invocation.

As mentioned in the docs here: https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lambda.html#Lambda.Client.invoke , the parameter values for invocation_type are described as:
InvocationType (string) --
Choose from the following options.
RequestResponse (default) - Invoke the function synchronously. Keep the connection open until the function returns a response or times out. The API response includes the function response and additional data.
Event - Invoke the function asynchronously. Send events that fail multiple times to the function's dead-letter queue (if it's configured). The API response only includes a status code.
DryRun - Validate parameter values and verify that the user or role has permission to invoke the function.

Like someone mentioned here: https://stackoverflow.com/questions/72165019/how-can-i-track-the-progress-status-of-an-asynchronous-aws-lambda-invocation , there seems to be no built-in way to track the status of async Lambda function invocation.

I asked on the Airflow OSS channel in the #airflow-aws channel. So far have got only reply mentioning the same that it may not be possible.
@phanikumv please check what should we do on this Spike.

Mark Richman, Senior Solutions Architect at AWS has confirmed that there is no way currently to get the invocation status. Hence, I believe it is not feasible to implement an async operator to await the status of a Lambda function invocation.

Closing the spike as the implementation is not feasible.


Set cursor not allowed when dragging too many files

PR Checklist

[ ] Merge dependent PR: https://github.com/vivid-planet/comet/pull/2151
[x] Verify if the change requires a changeset. See CONTRIBUTING.md
[x] Link to the respective task if one exists: COM-819

We decided against doing doing this, as the OS will generally override the cursor while dragging files.


Move integration tests to separate file set

This PR attempts to split unit tests from integration tests. The current unit tests require a running SurrealDB instance either locally or more recently as test containers in docker which makes them integration tests by definition. Not having used gradle before I simply adopted the standard grade pattern for integration tests with a new fileset rather than renaming them as *IT.java or something like that and use pattern matching to exclude them from unit tests.
Running gradle check will execute them along with checkstyle.

@phughk any further views on this PR?  Would be nice to code up some actual unit tests as I can see a possible NPE.


[zh] Localize service-accounts.md into Chinese

Fix #43355
Add zh text to this page:
content/zh-cn/docs/concepts/security/service-accounts.md

See preview please.

/lgtm


Add auth header to get requests

For supporting private repos

@bwyap any chance this could get reviewed and merged?

@benedfit will look into it!


Parameter example not set if its a path-sourced parameter

If I set an example for a parameter that is meant to be bound to a path variable, the example value is not output in the swagger docs.

fixed in v<IP_ADDRESS>-beta
thanks for reporting!


Clear partial texture using scissor test, fix regression in y-flipping PR in cases of resolution multiples

Fixes #6842
https://codepen.io/sukantpal/pen/YzqOdPo?editors=1010
Description of change

Use the scissor test when a render-texture only cover a portion of its base-texture
Fix the regression in the y-flipped #6873 PR. It is really sad nobody caught the error in the calculation - I was using renderer.screen.height instead of renderer.height (the latter is resolution-multiplied, like the viewportFrame). All the examples were rendering by a wrong offset (if your resolution was not 1): https://pixijs.io/examples/#/demos-basic/container.js

https://github.com/pixijs/pixi.js/blob/b7881eb680afd7cad410821dc70027146bef7729/packages/core/src/renderTexture/RenderTextureSystem.ts#L165
vs
https://github.com/pixijs/pixi.js/blob/b7881eb680afd7cad410821dc70027146bef7729/packages/core/src/mask/ScissorSystem.ts#L116
Pre-Merge Checklist

[x] Documentation is changed or added
[x] Lint process passed (npm run lint)
[x] Tests passed (npm run test)

Codecov Report

Merging #6892 into dev will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               dev     #6892   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          671       671
=========================================
  Hits           671       671

Continue to review full report at Codecov.

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

Can we please not use renderer.height and renderer.width anywhere? it should be renderer.view.width , or we can store values from gl context backbuffer fields, i forgot the name.  renderer.width is ambigious.

@SukantPal could you follow up on Ivan's feedback here? I think that's valid.

Followed up :)!

Codecov Report

Merging #6892 into dev will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               dev     #6892   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           15        15
  Lines          671       671
=========================================
  Hits           671       671

Continue to review full report at Codecov.

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

Thanks @SukantPal


ROCm: Error in hipBLAS dgmm

From https://github.com/cupy/cupy/pull/4217#issuecomment-749783900:
$ pytest tests/cupyx_tests/test_cupyx.py tests/cupy_tests/test_cublas.py tests/cupy_tests/test_cusolver.py
...
======================================================================= short test summary info =======================================================================
FAILED tests/cupy_tests/test_cublas.py::TestDgmm_param_5_{ordera='C', orderc='F', shape=(9, 10), side='R'}::test_dgmm_incx_minus_one - AssertionError:
FAILED tests/cupy_tests/test_cublas.py::TestDgmm_param_7_{ordera='C', orderc='F', shape=(10, 9), side='R'}::test_dgmm_incx_minus_one - AssertionError:
FAILED tests/cupy_tests/test_cublas.py::TestDgmm_param_12_{ordera='F', orderc='F', shape=(9, 10), side='L'}::test_dgmm_incx_minus_one - AssertionError:
FAILED tests/cupy_tests/test_cublas.py::TestDgmm_param_14_{ordera='F', orderc='F', shape=(10, 9), side='L'}::test_dgmm_incx_minus_one - AssertionError:
============================================================ 4 failed, 2434 passed, 640 skipped in 10.53s =============================================================

It seems the trigger condition is

mode=0
incx=-1

I suspect this is a hipBLAS bug.

cc: @amathews-amd

M=rows, N=cols seems reversed for ROCm compared with CUDA; Internal Ticket: SWDEV-309804


Feature Request (Submitted by 4305)

Description
I'd like to be able to see if any users are actively looking to trade for a card that I own. And on the flip-side I'd like to be able to broadcast that I'm looking to trade for card X.
With this I could much easier see if another user and I could have a potential trade going, rather than reaching out to everyone who owns the card(s) I'm after one-by-one.
Desired Functionality

Ability to mark any owned or unowned card as "I'm looking to trade for this card"
Ability to view users on the trade market who are looking for one or more cards that I own

Will need to make another db table and logic behind that

This isn't a bad idea, but it seems like something that the discord or forum can do for now

Add a trade search instead?

Closing because we want to do this but differently.


Build wheels for macOS and Windows

The cibuildwheel project seems like a good option for this   and seems easy enough to add to this repo.
What do you think?
If there's interest, I can start work on a PR 🙂

Going to pass for now, thanks.

@edgarrmondragon would you be interested in starting a new fork? My colleagues really need a Windows version of this package so we can use the latest SQLite features on their systems. cibuildwheel seems like a great project.

@mihow yeah, something like a pysqlite3-wheels package that just pulls this repo and builds all the right wheels should be good enough for a lot of folks. I might be able to give it a try on the weekend.

Please have a look at my fork which builds wheels for all platforms using cibuildwheel.
https://github.com/Dobatymo/pysqlite3
https://pypi.org/project/pysqlite3-wheels/

Awesome, thanks @Dobatymo I will test your fork.


Utilize i.n.u.internal.ObjectUtil Preconditions (commons) (#11170)

Motivation:
NullChecks resulting in a NullPointerException or IllegalArgumentException, numeric ranges (>0, >=0) checks, not empty strings/arrays checks must never be anonymous but with the parameter or variable name which is checked. They must be specific and should not be done with an "OR-Logic" (if a == null || b == null) throw new NullPointerEx.
Modifications:

Add some checks to ObjectUtil not present today but utilized in the code.
Add unit test for ObjectUtil
Update commmons internal usage with ObjectUtil

Result:
All checks needed are present, subsequent changes of usage of ObjectUtil are possible.
Fixes for https://github.com/netty/netty/issues/11170
One PR for each subproject to ease review.

@normanmaurer Thanks for your offer to check this. The build failed but I cannot see the relation between change and error. Looks like an infrastructure topic? Could you please check and advise?

@rkapsi PTAL again

LGTM

@boris-unckel thanks a lot!


sched: remove duplicate functions

Summary
sched: remove duplicate functions
nxsched_critmon_cpuload has two identical implementations
Impact
Testing
sim

[Experimental Bot, please feedback here]
This PR appears to meet the basic NuttX requirements, but could use more details for a comprehensive review. Here's a breakdown:
Strengths:

Clear Summary: You've clearly stated the "why" (duplicate functions) and "what" (removing one implementation).
Testing Done:  You've indicated testing on a simulator.

Areas for Improvement:

Summary - How: Be more specific about which implementation is removed or if you're consolidating into a single function.
Impact:  While removing duplicates is generally low impact, address all points.

Feature:  NO (unless removing one implementation impacts functionality)
User/Build: Likely NO, but state explicitly
Hardware: Likely NO, but state explicitly
Documentation:  Maybe YES if function names changed, requiring API doc updates
Security/Compatibility: Likely NO, but confirm

Testing:

Build Host: Specify your OS, compiler, and version for reproducibility.
Target:  "sim" is vague. Which simulator and architecture?
Logs:  Provide snippets of relevant logs showing the change's effect (e.g., function call before/after, resource usage).

Example for Improvement (Testing):
## Testing

I confirm that changes are verified on local setup and works as intended:
* Build Host(s): Ubuntu 20.04, GCC 9.4.0
* Target(s): qemu-system-arm (Cortex-M3), configs/sim/nsh/defconfig

Testing logs before change:

[sched] Starting CPU load monitor
[sched] nxsched_critmon_cpuload: CPU load = 15% (implementation 1)

Testing logs after change:

[sched] Starting CPU load monitor
[sched] nxsched_critmon_cpuload: CPU load = 15% (consolidated implementation)


Add unlabelled words

I guess, now, since we are only including the entries in the dictionary that already have a "description" field, we do not need the verified tags. But I think it is possible to include the lexical entries of those with just the chatGPT description and invite people to add in their definitions and examples, etc.
This could be done as an additional feature


Can I make a custom filter function using ReflectionFunction?

I'm not sure if this is a documentation gap or a functionality gap, but it isn't clear to me how I can create a generic filter function using ReflectionFunction. For example, the function distinct does not exist in the runtime yet (#732) and I was thinking I would replicate it. Ideally, I could pass it a table along with a formula that gets evaluated to determine what to operate over.

This depends on #643

https://github.com/microsoft/Power-Fx/issues/643 is closed.


zoom is pretty broken when called on node smaller than the  node

If you apply a zoom to a <rect /> within an <svg />, the behavior can be very strange if the <rect /> is smaller than the <svg />. This happens because d3 uses the parent <svg />'s size to determine the zoom extent rather than using the size of the element that it's applied to. Relevant source.
Behaviors I see:

translateExtent is often not properly applied. Through combinations of panning and zooming out, I can cause it to translate way beyond the translateExtent.
Strange jerkiness.

Here's a gist that demonstrates these issues: https://bl.ocks.org/mrcslws/565393a63d5e017d095686b8fbf5a2f3
Here's the workaround that I'm using.
function svgRectExtent() {
  var e = this, w, h;

  return [[0, 0],
          [e.width.baseVal.value,
           e.height.baseVal.value]];
}

// On my zoom
var zoom = d3.zoom()
  .extent(svgRectExtent);

This workaround is just telling it to use the dimensions of the element that it's applying the zoom to, and this makes everything work as expected.

The problem is that you’ve defined a translate (or “world”) extent that is smaller than the zoom (or “viewport”) extent; related #50. It is thus impossible to constrain the view inside the world.
Given the default zoom extent you’re using, which as documented is the bounds of the ancestor SVG element, you’ll want to change the zoom.translateExtent to something like:
var zoom = d3.zoom()
    .scaleExtent([1, 40])
    .translateExtent([[0, 0], [+svg.attr("width"), +svg.attr("height")]])
    .on("zoom", zoomed);

Alternatively, you could define a compatible zoom.extent as follows:
var zoom = d3.zoom()
    .scaleExtent([1, 40])
    .translateExtent([[0, 0], [width, height]])
    .extent([[0, 0], [width, height]])
    .on("zoom", zoomed);

I can’t think of a smarter default for zoom.extent, since the zoomable content can be modified dynamically; I don’t think using node.getBBox would be very predictable, either. So really unless the zoom behavior applies to the entire SVG, you should be specifying the zoom.extent explicitly rather than relying on the default.

@mbostock Thanks for spending time on this. I totally overlooked that zoom.extent() was part of the documented API. That's my bad.
I don't think zoom.extent() is used in any any of the zoom examples. An example that uses zoom.extent would have helped me. (Context: I was porting these to d3 4.0, and getting zooming to work again took a long time.) That's just an FYI -- with d3 you've already done a lot for me!
I'm still seeing some other quirkiness -- I'll file a separate issue: #87


Update bcpkix-jdk15on, bcprov-jdk15on to 1.71.1

Updates

org.bouncycastle:bcpkix-jdk15on
org.bouncycastle:bcprov-jdk15on

from 1.70 to 1.71.1.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (1.70).
You might want to review and update them manually.
docs/images/webshop-example-1.svg

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.bouncycastle" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.bouncycastle" }
}]

labels: library-update, old-version-remains, commit-count:1

Superseded by #1355.


[WIP] add multiline support to TCP

This is my proposal for multiline support in TCP
It's not finished yet, but please see if this is acceptable direction

moving encoding and multiline to helper to reuse it in TCP
create reader for TCP input operator

Sorry for the quality, but I want to get feedback of general idea quickly to resume work on that Tomorrow

@sumo-drosiek, Thanks for taking a crack at this.
I agree with moving encoding and multiline to helper. I may have some minor comments later, but overall this looks great.
However, I don't see the value of the Reader. Can we just enhance goHandleMessages to make use of encoding and multiline? Maybe I am missing something, but this seems like an unnecessary abstraction.

I change multiline to return splitFunc directly and renamed MaxBufferSize to MaxLogSize

ready to go :tada:


Pause for lagging validators.

@bachase Unit tests are not here as yet, I'm hoping for some suggestions on how to integrate into the CSF, please.

Jenkins Build Summary
Built from this commit
Built at 20190223 - 03:39:55
Test Results

Build Type
Log
Result
Status

rpm
logfile
1145 cases, 0 failed, t: n/a
PASS :white_check_mark:

msvc.Debug
console
no test results, t: n/a
FAIL :red_circle:

msvc.Debug, NINJA_BUILD=true
console
no test results, t: n/a
FAIL :red_circle:

msvc.Debug -Dunity=OFF
console
no test results, t: n/a
FAIL :red_circle:

msvc.Release
console
no test results, t: n/a
FAIL :red_circle:

gcc.Release -Dassert=ON, MANUAL_TESTS=true
logfile
915 cases, 0 failed, t: 6m9s
PASS :white_check_mark:

docs, TARGET=docs
logfile
1 cases, 0 failed, t: 0m1s
PASS :white_check_mark:

clang.Debug
logfile
no test results, t: 60s
FAIL :red_circle:

clang.Debug -Dunity=OFF
logfile
no test results, t: 47s
FAIL :red_circle:

gcc.Debug
logfile
1145 cases, 0 failed, t: 3m29s
PASS :white_check_mark:

gcc.Debug -Dcoverage=ON, TARGET=coverage_report, SKIP_TESTS=true
logfile
1145 cases, 0 failed, t: 17m16s
PASS :white_check_mark:

clang.Release -Dassert=ON
logfile
no test results, t: 126s
FAIL :red_circle:

gcc.Debug -Dunity=OFF
logfile
1145 cases, 0 failed, t: 7m12s
PASS :white_check_mark:

gcc.Release -Dassert=ON
logfile
1145 cases, 0 failed, t: 6m13s
PASS :white_check_mark:

gcc.Debug -Dstatic=OFF
logfile
1145 cases, 0 failed, t: 3m28s
PASS :white_check_mark:

gcc.Debug -Dstatic=OFF -DBUILD_SHARED_LIBS=ON
logfile
1145 cases, 0 failed, t: 3m29s
PASS :white_check_mark:

clang.Debug -Dunity=OFF -Dsan=address, PARALLEL_TESTS=false, DEBUGGER=false
logfile
no test results, t: 72s
FAIL :red_circle:

clang.Debug -Dunity=OFF -Dsan=undefined, PARALLEL_TESTS=false
logfile
no test results, t: 53s
FAIL :red_circle:

gcc.Debug, NINJA_BUILD=true
logfile
1145 cases, 0 failed, t: 3m3s
PASS :white_check_mark:

@mtrippled I attempted to add the proper support to csf::Peer in https://github.com/bachase/rippled/commit/f1d39f0877db0b289c8bad64302c875c2c245f00, but there were some existing compilation errors on os x that I did not attempt to fix.
I also added a unit test in https://github.com/bachase/rippled/commit/ef2b793d01bda2b1e33d840fd830a6e788de9a3c which simulates a few validators getting ahead of the rest of the network. I believe making that test pass a sign your changes improve recovery.
I still need to review your actual changes and the implementation.

o

I'll work on fleshing out the test functions to make this work. I have tested this already--the fix works like it's supposed to, but I agree that unit tests should also be in place.
One thing I've noticed about the test that you helped with is that the current node is at seq 25 with the last validated at 500. The problem I'm addressing is in reverse: when the current node is past last validated. I'll try to figure that out too, but if something comes to mind for you, please let me know.

@mtrippled I attempted to add the proper support to csf::Peer in bachase@f1d39f0, but there were some existing compilation errors on os x that I did not attempt to fix.
I also added a unit test in bachase@ef2b793 which simulates a few validators getting ahead of the rest of the network. I believe making that test pass is a sign your changes improve recovery.
I still need to review your actual changes and the implementation.

@bachase The new unit test now works--and the fast peers slow down in the process of regaining sync with the network (which is the intent of this PR).

@mtrippled. I made a bit more progress. I am confused at how the unit tests passed when the trustedKeys were not being set in the csf/Peer class.
I don't think unit tests passed until I set trustedKeys. I agree they shouldn't have.

The other main question is whether shouldPause is actually pausing in the case when there are no laggards.

It is not.

@ximinez @bachase Both of you were curious why to cycle through phases instead of staying at the 100% threshold once the last phase was exceeded. It's because no phase is probably intrinsically better than the other--the lower the threshold, the less likely to reach consensus. But the higher the threshold, the longer the likely resulting pause. And I think 100% is slightly less desirable to fixate upon because the potential of a single dawdling peer to slow down everything else. So if we accept that no phase is any better than any other phase, but that all of them will potentially enable us to arrive at consensus, cycling through them seems to be appropriate. Also emphasize that if we even reach the point of having to cycle back around (or stay fixated), that something else out of the scope of this fix is wrong with the network.
I'm OK with fixing it at 100% if you guys still think it's the best thing to do, but I want mainly to convey my rationale for cycling through: each threshold has trade-offs, so none in particular should be preferred over all.

I don't have particularly strong feelings about the resolution of cycling vs not.  But I encourage you to include as comments in the source code the motivations for a particular choice.  For example, if you stick with cycling the justification you just provided should also be a comment in the source code.

I don't have particularly strong feelings about the resolution of cycling vs not. But I encourage you to include as comments in the source code the motivations for a particular choice. For example, if you stick with cycling the justification you just provided should also be a comment in the source code.

voila! https://github.com/ripple/rippled/pull/2865/files#diff-dab2766c14d0ef8e760dc5e353fa7b9dR1194


INTEGRA-516 need to keep docs in synch

need to keep docs in synch between Anapedia and GitHub so the ReadMe now points
to  blob/master/doc/AnaplanConnectorforMuleSoft-Guide.pdf  instead of to
raw/develop

Hi Thomas - Please update this pull request to merge with Develop and assign it to me.

Closing again, thought I could change the branch names here. Thomas, when creating the pull-request, make sure that the branch its going to merge into is "develop", not "master". If you see the statement above "wants to merge 1 commit into master from feature/INTEGRA-516", it needs to say "wants to merge 1 commit into develop from feature/INTEGRA-516"

Yes. You are correct. I will verify more carefully in the future. Thanks.


feat: adding footer

@Shurtu-gal Please review!

@all-contributors please add @starkjay21 for code.


Issue with k8s.io/docs/tutorials/kubernetes-basics/update/update-interactive/

This is a Bug Report

Problem:
The gcr.io/google-samples/kubernetes-bootcamp:v10 did not exist any more.

kubectl set image deployments/kubernetes-bootcamp kubernetes-bootcamp=gcr.io/google-samples/kubernetes-bootcamp:v10

Events:
  Type     Reason            Age                From               Message
  ----     ------            ----               ----               -------
  Warning  FailedScheduling  75s (x2 over 75s)  default-scheduler  0/1 nodes are available: 1 node(s) had taints that the pod didn't tolerate.
  Normal   Scheduled         70s                default-scheduler  Successfully assigned default/kubernetes-bootcamp-886577c5d-tmh69 to minikube
  Normal   Pulling           30s (x3 over 68s)  kubelet, minikube  Pulling image "gcr.io/google-samples/kubernetes-bootcamp:v10"
  Warning  Failed            30s (x3 over 67s)  kubelet, minikube  Failed to pull image "gcr.io/google-samples/kubernetes-bootcamp:v10": rpc error: code = Unknown desc = Error response from daemon: manifest for gcr.io/google-samples/kubernetes-bootcamp:v10 not found: manifest unknown: Failed to fetch "v10" from request "/v2/google-samples/kubernetes-bootcamp/manifests/v10".
  Warning  Failed            30s (x3 over 67s)  kubelet, minikube  Error: ErrImagePull
  Normal   BackOff           6s (x5 over 67s)   kubelet, minikube  Back-off pulling image "gcr.io/google-samples/kubernetes-bootcamp:v10"
  Warning  Failed            6s (x5 over 67s)   kubelet, minikube  Error: ImagePullBackOff

Proposed Solution:
Select a stable resource for the tutorials.
Page to Update:
https://kubernetes.io/...

Filed in error, close it by myself


Add social website svg icon

What does this pull request aim to achieve? 💯
Add social website svg icon
closes #1043

No, it should be complete. Did I miss something? 😂


serialization/de-serialization for all methods

can you please add serialization/de-serialization for all methods specified here https://github.com/ton-blockchain/ton/blob/master/tl/generate/scheme/lite_api.tl#L60
currently i see only getTime in example?

Hi, we are currently working on it, will be available soon.

Thanks.
i am eagerly waiting.


Add crusj/structrue-go.nvim

A better structured display of golang symbol information
structrue-go

Just FYI, you'll need to make a PR to add a plug-in to the list: CONTRIBUTING.md

Just FYI, I think you'll need to make a PR to add a plug-in to the list: CONTRIBUTING.md

Ok


High CPU time from Cyclic capabilities of items in RefinedStorage system

Minecraft version & Mod Version:
1.12.2 (forge 2493)
Cyclic-1.12-1.8.6.jar
Single player or Server:
SMP (ATM3 official)
Describe problem (what you were doing / what happened):
Seeing very high CPU usage from cyclic Capabilities call traces. Initially it looked like RefinedStorage but as I kept drilling down, cyclic's capabilities method was at the heart of it.
Crash log (if any):

snapshot-1506730916397.zip

The mod id for cyclic is "com.lothrazar.cyclicmagic"  .


support for protocol-relative paths

works (http):
@CHARSET "UTF-8";
@import url(http://example.org/some.css);
$bgColor: red;
body {
	background: $bgColor;
}

works (https):
@CHARSET "UTF-8";
@import url(https://example.org/some.css);
$bgColor: red;
body {
	background: $bgColor;
}

does not work (//):
@CHARSET "UTF-8";
@import url(//example.org/some.css);
$bgColor: red;
body {
	background: $bgColor;
}

output instead:
@charset "UTF-8";
@import url(//example.org/some.css);
$bgColor: red;
body {
  background: ;
}

scssphp and libsass appear to both treat //example.org/some.css); as a comment.


Ubuntu 22.10, deb package: missing libssl.so.1.1

On Ubuntu 22.10, after installing pachtop_0.3.1_amd64.deb, the application can't be started, complaining about a missing library:
pachtop: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
The AppImage version works.
Ubuntu 22.10 comes with libssl3, (openssl v3), and it doesn't seem to me 1.1 would be available. Possible to build against it?

Hello, That's unfortunate. Pachtop is still in development and isn't stable. I used Tauri  to package the application and cross-compile them into binaries. Perhaps I should adjust the version targets when compiling the binaries?
I found a post that shares a similar: https://stackoverflow.com/questions/72133316/libssl-so-1-1-cannot-open-shared-object-file-no-such-file-or-directory
I'm glad the app image works though.


Fix Orpheus' incorrect grammar

Closes #170.

❤

Going to merge. @ifvictr: are you interested in refactoring this with pluralize?

@MaxWofford At a future time, when I learn more about Ruby.


(fix) add magic-link to dependencies

Signed-off-by: Brent Hoover<EMAIL_ADDRESS>Resolves #36
Issue in dependency repo: https://github.com/accounts-js/accounts/issues/1156

:tada: This PR is included in version 2.2.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Prevent AttributeError to be raised when pool is already None

Calling close() multiple times will not result into an error now.

Mind bringing this up to date with the current master?

Codecov Report

Merging #1279 into master will decrease coverage by 0.05%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #1279      +/-   ##
==========================================
- Coverage     100%   99.94%   -0.06%
==========================================
  Files          21       21
  Lines        1985     1987       +2
==========================================
+ Hits         1985     1986       +1
- Misses          0        1       +1

Impacted Files
Coverage Δ

urllib3/connectionpool.py
99.6% <50%> (-0.4%)
:arrow_down:

Continue to review full report at Codecov.

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

Do i have to add a test?

I'd want to see a test - obviously we were missing a flow where self.pool was None, but that'd be up to @Lukasa. Should be straightforward to create a pool, and then close it twice, asserting that it doesn't raise.

        try:
            pool.close()
        except AttributeError:
            pytest.fail("AttributeError raised.")

Would be this ok?
Here: https://github.com/shazow/urllib3/blob/master/test/test_connectionpool.py#L248

@IceflowRE, you'll probably want to make a new test to test this issue specifically. You can use the structure from the test you linked to for building up the new test.
Also using the pytest.raises context manager is probably preferable to a try/except block.

Yup, adding a new test is the way to go. I also recommend adding a few positive assertions (that is, active assert rather than just let the test complete with no failing assertions).

Ok, iam not familiar with pytest itself.
But i think pytest.raises must raise an exception?

I actually think the code block you have above should work; you'll just want it in its own test, and you'll also want to write a more explicit string about the test failure than "AttributeError raised."

Did it.


addressed diagnostic messages

just cleaned some stuff up!

@kurtbuilds im not sure how to address this conflict..

i think this needs to be updated, you still have the derive-enum crate

@kurtbuilds whoops. i force pushed hehe


ExchangeEnvironmentName to connect to Exchange Online PowerShell in sovereigns cloud

To connect to sovereign environment -ExchangeEnvironmentName parameter is needed.
Example for GCC High:
Connect-ExchangeOnline -Credential $UserCredential -ShowProgress $true -ConnectionUri https://outlook.office365.us/powershell-liveid/ -ExchangeEnvironmentName O365USGovGCCHigh
Information can be found here but could be reflected on this page in the examples of commands to connect.

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

ID: 39fbe5a2-c138-b566-c094-82ffc3d1b734
Version Independent ID: 4d69ee5d-5a6d-a203-69fe-bf5441a8b5eb
Content: Connect to Exchange Online PowerShell
Content Source: exchange/docs-conceptual/connect-to-exchange-online-powershell.md
Service: exchange-online
GitHub Login: @chrisda
Microsoft Alias: chrisda

@ZelMul, I think your example requires ExchangeEnvironmentName because you didn't use AzureADAuthorizationEndPointUri. If you use ConnectionUri and AzureADAuthorizationEndPointUri in the command, you should be able to connect without using ExchangeEnvironmentName.
Can you confirm?

@chrisda Yes this also work, I was following the section "Without using MFA" which doesn't mention AzureADAuthorizationEndPointUri nor ExchangeEnvironmentName and thus didn't work for me.

@ZelMul, interesting. I thought AzureADAuthorizationEndPointUri was only required for multi-factor authentication (MFA). But you're saying it's required for non-MFA connections?
But I have a new angle for you: If you use the ExchangeEnvironmentName parameter, you don't need to use the ConnectionUri or AzureADAuthorizationEndPointUri parameters. That parameter has only recently been fully tested and approved in the EXO V2 module, so I'm updating the MFA and non-MFA connection instructions to use it exclusively.
Thanks for the feedback.
Closing


Merge hitemp hitran methods

Addressed #368

I made a common parent class MdbCommonHitempHitran both for MdbHitemp and MdbHitran
also renamed the option for nonair broadening

Use tests/integration/api/api_hitran_hitemp_test.py to check the results.

I apologize for not reviewing it sooner. I have confirmed that the test program works. Thank you!


[Bug] MiniCPM-V 2.6 model doesn't work

Checklist

[X] 1. I have searched related issues but cannot get the expected help.
[X] 2. The bug has not been fixed in the latest version.
[X] 3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.

Describe the bug
When I try to setup api server or gradio using MiniCPM-V 2.6 model, once it tries to convert to turbomind format, it throws error from deploy/target_model/fp.py line that, saying the Nonetype has no property called cuda. I am using the latest release of LMdeploy
Reproduction
lmdeploy serve gradio openbmb/MiniCPM-V-2_6
lmdeploy serve api_server openbmb/MiniCPM-V-2_6
Environment
sys.platform: linux
Python: 3.12.5 (main, Aug 17 2024, 16:46:05) [GCC 11.4.0]
CUDA available: True
MUSA available: False
numpy_random_seed:<PHONE_NUMBER>
GPU 0: NVIDIA L4
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 12.2, V12.2.140
GCC: x86_64-linux-gnu-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
PyTorch: 2.3.1+cu121
PyTorch compiling details: PyTorch built with:
  - GCC 9.3
  - C++ Version: 201703
  - Intel(R) oneAPI Math Kernel Library Version 2022.2-Product Build 20220804 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v3.3.6 (Git Hash 86e6af5974177e513fd3fee58425e1063e7f1361)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - LAPACK is enabled (usually provided by MKL)
  - NNPACK is enabled
  - CPU capability usage: AVX2
  - CUDA Runtime 12.1
  - NVCC architecture flags: -gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_90,code=sm_90
  - CuDNN 8.9.2
  - Magma 2.6.1
  - Build settings: BLAS_INFO=mkl, BUILD_TYPE=Release, CUDA_VERSION=12.1, CUDNN_VERSION=8.9.2, CXX_COMPILER=/opt/rh/devtoolset-9/root/usr/bin/c++, CXX_FLAGS= -D_GLIBCXX_USE_CXX11_ABI=0 -fabi-version=11 -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -DNDEBUG -DUSE_KINETO -DLIBKINETO_NOROCTRACER -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -O2 -fPIC -Wall -Wextra -Werror=return-type -Werror=non-virtual-dtor -Werror=bool-operation -Wnarrowing -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-unused-parameter -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-stringop-overflow -Wsuggest-override -Wno-psabi -Wno-error=pedantic -Wno-error=old-style-cast -Wno-missing-braces -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, LAPACK_INFO=mkl, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, TORCH_VERSION=2.3.1, USE_CUDA=ON, USE_CUDNN=ON, USE_CUSPARSELT=1, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_GLOO=ON, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=1, USE_NNPACK=ON, USE_OPENMP=ON, USE_ROCM=OFF, USE_ROCM_KERNEL_ASSERT=OFF,

TorchVision: 0.18.1+cu121
LMDeploy: 0.5.3+
transformers: 4.44.2
gradio: 4.42.0
fastapi: 0.112.1
pydantic: 2.8.2
triton: 2.3.1
NVIDIA Topology:
        GPU0    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      0-3             N/A             N/A

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

Error traceback
No response

The latest pypi package (0.5.3) doesn't support minicpm-v-2_6, we will release next version this weak. You can download the nightly build from here https://github.com/zhyncs/lmdeploy-build/releases/tag/ada7285

LMDeploy 0.6.0 is recommended.

Thanks! I already did.


Documentation unclear for configuring # of remembered work or school accounts for UWP apps (save more than 3 and introduce a scroll bar?).

This documentation does not include information about configuring saved user limit.
It appears to stop at 3 - is it possible to configure more saved users and add a scroll bar?
https://docs.microsoft.com/en-us/azure/active-directory/develop/tutorial-v2-windows-uwp

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

ID: f2333c6b-140e-6cc8-91ad-00e47935bc6b
Version Independent ID: 738f87e1-d839-62f7-0c5c-6562b39e8d1c
Content: Microsoft identity platform UWP getting started
Content Source: articles/active-directory/develop/tutorial-v2-windows-uwp.md
Service: active-directory
Sub-service: develop
GitHub Login: @jmprieur
Microsoft Alias: jmprieur

@kndrewa , Thanks for reaching out. We will investigate and update this thread.

Hi @kndrewa, I've reached out to ask what the limit is. I don't believe there is one but have not found documentation to confirm.

We confirmed with the folks who own this control (WAB - windows authentication broker) and there is no limit. They stated:
Accounts Control shows the following saved accounts:
1)	All accounts known by the OS.
2)	All accounts given to Accounts Control by the app.

MSAL can only give 1 account via login hint as far as I know.

After 5 accounts a horizontal scroll bar appears.

Thanks @bgavrilMS! Closing this out.


The messages should still go to the logstash-{date} index as it does today, just need a more accurate pattern for the RFC5424 openstack pattern I believe.  I suspect that this pattern is the place to start looking:
OPENSTACK_RFC5424_MESSAGE %{OPENSTACK_COMPONENT}: %{OPENSTACK_MESSAGE}|%{OPENSTACK_COMPONENT}: %{GREEDYDATA}
Let's talk about it on standup today.

turns out ceilometer is the generator of these messages.  They seem to really have no purpose in syslog.  considering shutting of the redirection of syslog messages from ceilometer since it's not one of the core projects we're interested in monitoring.
it does compel me to continue to refactor the logstash patterns since they are a bit long in the tooth, and we've learned a lot since then (and are pretty close to having a good way to write pattern and filter tests).

I'm opting for not configuring ceilometer for a few reasons:

not a core project for goldstone to observe
upcoming goldstone_events would remove other dependencies on ceilometer
3a) future plans to provide our own log shipper will give us more control to do patterning and classification on the sending side, which will simplify receiver side rules.
3b) This change would be complicated pattern and filter surgery


suggestion: leaderboard

user performance rankings by adjustable criteria (volume, gains, etc.) over adjustable time horizons.
Make it easy for everyone (including lurkers) to find the hidden sages.

I don't think this is actually possible to do in a decentralized manner in any fashion where it doesn't take hours to load.  Should be a separate thing from main ui and main ui could display it or something if someone makes one


Colors

We need colors 😄
It makes the output so much more readable.
Read NO_COLOR environment variable and add a flag --no-color to disable it.

Tracking this one internally.


rename D.F.I.Lifecycle.Rule.Settlement to D.F.I.Lifecycle.Rule.Claim

suggestion to rename D.F.I.Lifecycle.Rule.Settlement and its choice Claim to D.F.I.Lifecycle.Rule.Claim and Effectuate, respectively.


[move source language] Add handling of new script arg rules

#5138 changed the rules for script arguments, this brings the source language in line
The new rules are the same rules that apply to constants (primitive types and any combos of them)

Test Plan

updated tests

Related PRs
#5138

@bors-libra r=dariorussi

:pushpin: Commit 3841cb1 has been approved by dariorussi

:hourglass: Testing commit 3841cb1b2f6bf77baf1fba698338c602339860e4 with merge ac68524328e2b228d2719dbd63f795041bfd0f96...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: dariorussi
Pushing ac68524328e2b228d2719dbd63f795041bfd0f96 to master...


Dealing with directories being larger than a single block

Both raw_pdb and Llvm can't deal with pdbs that have more block indices than what fits in a single block. The DIA SDK seems to handle this case fine however. Although this rarely happens, we are dealing with pdb files that fail this (directoryBlockCount > blockIndicesPerBlock) validation check. This problem led us to move away from the Llvm implementation in favor of the DIA SDK's.
After some investigation on the problematic pdb files, which we unfortunately can not share, we found a workaround.
We assume that block indices will spill to the next block(s). Inspecting the block values confirmed this assumption with our problematic pdbs. For example, a pdb file that has 824 blocks in the directory but can only fit 256 indices per block will use 4 consecutives blocks for storing indices. In our case, all the indices are consecutives, even crossing block boundaries, and the last block of indices is zero-filled after the last index.
directoryBlockCount = 824
blockIndicesPerBlock = 256
superBlock->blockSize = 1024
superBlock->freeBlockMapIndex = 2
superBlock->blockCount = 210763
superBlock->directorySize = 843148
superBlock->unknown = 0
superBlock->directoryIndicesBlockIndex = 210754
superBlock->directorySize / superBlock->blockSize = 823
num_indices_blocks = 4

The workaround currently consists of making sure that blocks are contiguous in memory (which I think is always the case thanks to the CoalescedMSFStream(?)). This way, indexing from the address of the first index block will safely overflow to the subsequent index block(s). We could add some additional validation, like making sure the indices are in a valid range, and that the last block is indeed zero-filled after the last index. In any case, the fix seems to be working for us, but I'm curious to get your thoughts on the approach.
Do you have pdb files that trigger the check? I'll keep searching for such pdb files which I could share.
Thanks!

Thanks for bringing this to my attention!
I haven't seen any PDBs like this yet, it would be appreciated if you had a PDB to share.
In this case, I think the block indices have to be contiguous in memory:
The directory tells us which streams are made up of which blocks, which serves as an indirection and allows PDBs to store their data block-interleaved. In this case, we are reading the block directory, so there is no other indirection available that could tell us where blocks go if they were to be found at another offset in the file.
I'll fix this as soon as I get a PDB file to verify.

Ok, thanks for the input! So I scanned over 9K pdb files, and it seems I only have 2 that exhibit the problem, and I can't share them. I'll keep searching. At least this is documented and might help anyone running into the same problem.

Thanks to @rovarma who helped me find PDBs that exhibit this behaviour.
This issue has been fixed in 83516ec2d1bbedce14b0a5d5eb1f3dd1db9a3c36.

Thanks to @rovarma who helped me find PDBs that exhibit this behaviour. This issue has been fixed in 83516ec.

IMO that's hardly a fix. If you don't want to implement the case where these blocks are non-contiguous at least do verification of that.

IMO that's hardly a fix. If you don't want to implement the case where these blocks are non-contiguous at least do verification of that.

That case is implemented, because non-contiguous blocks are all over the place in PDB files.
In this particular case, it is being taken care of by the ContiguousMSFStream in the RawFile, see https://github.com/MolecularMatters/raw_pdb/blob/main/src/PDB_RawFile.cpp#L44.
The bug that needed fixing was the wrong assumption that the indices of all directory blocks will fit into one single block, which is not true for some PDBs.

IMO that's hardly a fix. If you don't want to implement the case where these blocks are non-contiguous at least do verification of that.

That case is implemented, because non-contiguous blocks are all over the place in PDB files. In this particular case, it is being taken care of by the CoalescedMSFStream in the RawFile, see https://github.com/MolecularMatters/raw_pdb/blob/main/src/PDB_RawFile.cpp#L44.
The bug that needed fixing was the wrong assumption that the indices of all directory blocks will fit into one single block, which is not true for some PDBs.

I'm talking specifically about referenced commit and the block map. Unless I'm missing something it seems to me like you are assuming that the stream directory block map is now a contiguous array of indices that can span across multiple blocks.
uint32_t directoryIndicesBlockIndex; // index of the first block that contains an array of indices of directory blocks, where the array itself can span several blocks

However to me it would seem that this definition is not correct and should be as so:
uint32_t directoryIndicesBlockIndices[]; // indices of the blocks that contain array of indices of directory blocks, ...

Ah, I see what you mean.
I am under the assumption that the MSF SuperBlock is a fixed-size thing, so the block index to the first block that stores the directory indices really is just a single uint32_t index, and not an array of uint32_t indices.
LLVM agrees with this definition: https://llvm.org/docs/PDB/MsfFile.html#msf-superblock
More specifically, it states "The number of ulittle32_t’s in this array is given by ceil(NumDirectoryBytes / BlockSize)." which is also what the current code assumes.
Of course, the LLVM format docs could be wrong, and I'd be happy to implement this in case the SuperBlock contains an array of indices.

I checked the PDB files I have to verify this, and they indeed store an array of indices in the SuperBlock, rather than a single index.
Thank you @JustasMasiulis for pointing that out, I will fix this accordingly.

LLVM agrees with this definition: https://llvm.org/docs/PDB/MsfFile.html#msf-superblock More specifically, it states "The number of ulittle32_t’s in this array is given by ceil(NumDirectoryBytes / BlockSize)." which is also what the current code assumes.

LLVM has a lot of assumptions that may not hold up for PDBs not generated by LLVM itself.
I'd suggest either reading microsoft's horrendous code base and doing some reversing of DIA or using https://github.com/willglynn/pdb like a middle point of "good enough", as while it's probably the most accurate open source implementation it still falls short on what the actual implementation is supposed to be like (IE the address translation).

Fixed in 66dccb0ba06952691c1fc0b1635f87f109099ee9.

Very nice! Many thanks, @MolecularMatters !


service.json generation

overview
When generating services with models, we should build the service.json dynamically, by including the definitions defined in each model, rather then using a single template with handlebars.
Eventually, this will need to be built from multiple assets (hooks, filters etcs) but for now it will just be built from models as those are the only prompt configurations that are supported right now.
tasks

[x] grab service.json from model templates
[x] overwrite {{options.template}}.json in file pipeline
[x] ensure that all service.json have sane defaults for non generated resources

Next step is to hook into meta.json for prompt based configuration and then figure out how to merge filter and hook configurations into the service.json overwrite.