Are x/mint tokens minted daily or weekly?

Context
https://github.com/osmosis-labs/osmosis/blob/9e1ca7beb15efaf027282946b7231a4bdfc4f32f/x/mint/README.md?plain=1#L26
Problem
As far as I can tell, new tokens are minted in the epoch block that occurs daily not weekly.

Source: https://www.mintscan.io/osmosis/parameters
Proposal

Update any relevant code in the x/mint module to set the default to one day not one week.
Update this line in the README

Additional supporting evidence
https://github.com/osmosis-labs/osmosis/blob/9e1ca7beb15efaf027282946b7231a4bdfc4f32f/x/epochs/README.md?plain=1#L29

It is one day. Sorry, might be outdated. If you PR an update, we would appreciate the help


Errors leave fifo/pipes behind

Running many kcr commands in an incorrect way leaves behind a fifo/named pipe in the current directory. If not removed these can clutter and cause a mess. Would it be possible to instead place them in the /tmp folder where they would not be likely to cause issues and would eventually not require manual removal?

How can I reproduce?
FIFOs are normally generated using File.tempname.
Example
crystal eval 'puts File.tempname'
# /run/user/1000/20210316-20946-r2p2z2

Been playing with it more and whilst for me crystal eval 'puts File.tempname' usually correctly outputs something like /tmp/20210316-11394-1qcbr4k, for some reason, when run in a shell spawned by kakoune (kcr doesnt matter) crystal eval 'puts File.tempname' will simply output something like: 20210316-11762-78pds8 causing it to be created in the current directory. This actually breaks many kcr commands as if the shells current directory is different from kakounes then the pipe is opened and never written to as kakoune instead writes them to a new text file of the same name in its directory.
So this is a problem of how shells spawned by kakoune handle it differently for some reason. I am unsure if this maybe something wrong with my configuration, although opening a kakoune session with no kakrc after renaming it and then initing kcr leads to the same problems.

To sum up, the culprit is tmux.kak which sets your TMPDIR to an empty value?

my TMPDIR is normally empty, but it didnt cause problems untill tmux.kak sets it to be nothing again and breaks it for some reason

Ah, yes that seems to be what's happening, thanks.

Closing, as not a bug from kakoune.cr: it correctly honors the TMPDIR value.

@Elither Do you mind opening an issue upstream?  It looks @topisani has the same problem.

https://github.com/mawww/kakoune/issues/4161


WebClient Failed to execute 'createObjectURL' on 'URL'

app.js:139 Uncaught TypeError: Failed to execute 'createObjectURL' on 'URL': No function was found that matched the signature provided.
at HTMLButtonElement.onRemoteStreamAdded (app.js:139)

Closed with #315

Warning: the website doc still points to an old version of the web client with this bug not corrected!


Media Source Extensions Article

Staged here: https://milkbone.googleplex.com/web/fundamentals/getting-started/primers/media-source-extensions

Formatting issues at URL.createObjectURL() is itself synchronous; however, it processes the

Back to you, Pete.


contrib\cmake: version_info.cc not found

System information

OS Windows 10
TensorFlow version: lastest on master branch
Python version: 3.5
GCC/Compiler version (if compiling from source): Visual-studio 14 2015 win64
CUDA/cuDNN version: 9.0
GPU model and memory: 6.1/8Gb

Describe the problem
I followed the instruction in contrib/cmake to build tensorflow on windows, in generation step:
`          Configuring done
CMake Error at tf_core_framework.cmake:332 (add_library):
Cannot find source file:
E:/work_space/projectcpp/tensorflow/tensorflow/tensorflow/core/util/version_info.cc

Tried extensions .c .C .c++ .cc .cpp .cxx .cu .m .M .mm .h .hh .h++ .hm
       .hpp .hxx .in .txx
      Call Stack (most recent call first):
       CMakeLists.txt:587 (include)

`
It seems like a known-bug but it is still there, please help.
Thank

We encourage you to use Bazel instead of Cmake as we no longer support cmake for Windows.

Are you satisfied with the resolution of your issue?
Yes
No

version_info.cc
/*  Generated by gen_git_source.py  */
#include <string>
const char* tf_git_version() {return "b'unknown'";}
const char* tf_compiler_version() {return __VERSION__;}
const int tf_cxx11_abi_flag() {
#ifdef _GLIBCXX_USE_CXX11_ABI
  return _GLIBCXX_USE_CXX11_ABI;
#else
  return 0;
#endif
}
const int tf_monolithic_build() {
#ifdef TENSORFLOW_MONOLITHIC_BUILD
  return 1;
#else
  return 0;
#endif
}


How to Send Order Confirmation Email After Successful Payment in Magento 2--paytm

Magento version:2.1.7
Plugin version: 1
Description

Customer chooses to pay by Paytm -> Is redirected to Paytm gateway -> Magento IMMEDIATELY sends out an Order Confirmation Email to the customer, before he even completes the payment.How to Send Order Confirmation Email After Successful Payment in Magento 2--paytm

Hi @chalapathipakkela,
This extension is for Magento1. I think you are referring to a other gateway then Adyen so I would advise you to contact them.
Regards,
Rik
Adyen


#86 Self host Google Fonts and Material Symbols

With this PR, Roboto font files and Material Symbols woff2 files will be loaded using relative urls to the location of beer.min.css file instead of relying on the Google hosted version as default behavior.

Resolves https://github.com/beercss/beercss/issues/86


SmaCC: Commenting out %root leaves Grammar view in wrong state

I would like to comment out %root since I don't want all my AST nodes inheriting the Spec fields.

So I expand %root, add a comment in front and save the grammar.

And this is what I end up with. Killing the SmaCC coder and re-opening it fixes the issue but

then %root becomes uncommented again.

I was able to remove %root using the Source view.
I then lost the AST and ended up with just a parse tree, something to be expected.
Then I removed %suffix and made an undefined and non-production class the root of my AST which worked perfectly.
%prefix AST;
%root Node;

Still, I think the Grammar view should let me delete %root without jumping through hoops.

When you save a grammar, if there is some syntax error in a rule, then it displays only the rules with syntax errors since they must be fixed before saving. In this case, when you commented out the rule, it could no longer parse the rule as a %root directive. We should probably allow commented out rules to saved. Also, we need some visual clue that only rules with syntax errors are being displayed.

Same thing happened when I removed %root entirely.


Outdated

Refers to RDP to head node. Windows clusters are gone. Article should be updated with steps for Linux.
Refers to Hive command line which is deprecated. Article should be updated with steps for beeline.

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

ID: 9783f450-14dc-ae85-878d-38e359f82818
Version Independent ID: 5a8fea1d-f736-878e-1b6a-ca677edc87ff
Content: Explore data in a Hadoop cluster - Team Data Science Process
Content Source: articles/machine-learning/team-data-science-process/hive-walkthrough.md
Service: machine-learning
Sub-service: team-data-science-process
GitHub Login: @marktab
Microsoft Alias: tdsp

@desarkar Thank you for your feedback, we will investigate it and get back to you soon.
@marktab Hi, could you please check this issue and update the document? Thank you.

@garyericson It's time to remove all the "Worked-Out Examples" -- please advise on process, thanks

@desarkar it was a former team who created and maintained these examples.  We do not have nor anticipate having support for them in the future.  The reason is that our effort has moved to https://docs.microsoft.com by product.  In this case, please refer to https://docs.microsoft.com/en-us/azure/hdinsight/ for correct and updated product information

@marktab Thank for the information, is there any plan to merge the document or remove the old document?

@desarkar
We will now proceed to close this thread since the problem of this issue has been mitigated. If there are further questions regarding this matter, please respond here and @YutongTie-MSFT and we will gladly continue the discussion.

@marktab Thanks for the information, is there any plan to merge the document or remove the old document?

@YutongTie-MSFT we are removing the information, but @garyericson has been our coach on how to best complete that removal

@marktab Thank you very much.


Add dash character to ID token.

As requested here.

Thanks @gleize.
Pending resolution of discussion in https://github.com/facebookresearch/hydra/pull/2094.

This is now available via a pypi dev release: pip install omegaconf==2.3.0.dev1.


Fix of execution getComputedStyle on window

When mqListener is included in <head>, i'm getting error:
Uncaught TypeError: Failed to execute 'getComputedStyle' on 'Window': parameter 1 is not of type 'Element'.
I think that error occurs because document.body was not ready.

Nice catch, thanks!

You're welcome)


Get_bytes call too many times

Hello ,
Before anything thanks for the works done on this AudioStream module.
I have an issue that i can't find a solution.  I have a python Kivy app who use  the Threadsource method. so i cut my sound in step
1 step = 1/4 BPM = (samplerate 15/BPM)  samples   so it should call the function Get_bytes 4BPM but it's call way more so my sound is read very fast can you help me ?
Thanks in advance

👋 We use the issue tracker exclusively for bug reports and feature requests.
However, this issue appears to be a support request. Please use our   support channels            to get help with the project.
Let us know if this comment was made in error, and we'll be happy to reopen the issue.


Implement Timeout for healthchecks

This PR enables checks to have an individual timeout.
It's based on a CancellationTokenSource that provides a CancellationToken to notify check. Meanwhile the CancellationTokenSource is also enrolled with the CancellationToken received in parameter (for connection aborted or timeout of publisher).
As agreed here : https://github.com/aspnet/Extensions/pull/1129#issuecomment-465855605

Rebased to take in account other changes and updated according to the review comments !

My pleasure, thanks for you feedback ! 😄


let setuptools link doc2md.py into bin directory

Hey, by the way, do you know how the scripts parameter differs from the console_scripts entrypoint?

No idea. I just installed the package and noticed it didn't link, and this seemed to work.

Ok, fine anyway.
By the way, I'm not using this package anymore (using native ReST READMEs instead) and wouldn't really recommend using it;)


Release matlab-whole-body-simulator 3.0.0

fyi @VenusPasandi , if you think there is some relevant change to document in the changelog feel free to mention it.
Fix https://github.com/ami-iit/matlab-whole-body-simulator/issues/73 .

@fabiodinatale thanks!

@traversaro please consider also #75 in the release version.

@traversaro please consider also #75 in the release version.

Ok thanks.


on focus

How can I know when a user has clicked on the search bar? on press seems to only be for when they hit search or done, but i need to take an action when they just click on the search bar.

Add onFocus inide textInputProps
textInputProps={{
    onFocus: () => yourCallback(),
}}

Do you know how to retrieve an event arg in onFocus function?  Thank you

Were you able to find how? @MaxInMoon

textInputProps={{
onFocus: () => yourCallback(),
}}

Most Useful thank you

Still can't seem to retrieve the event arg in the onFocus function, anyone have any idea?

I did something like this, works ok
return (
  <View
    onLayout={event => {
      const layout = event.nativeEvent.layout;
      setLocationFieldY(layout.y);
    }}>
    <LocationField
      props={{
        onInputFocus: e => {
            props.scrollToLocation(locationFieldY);
        },


API Review tool should support package types

It would be nice to have support for package types, so that they don't need to be represented as 'other'.

Done, it's not the most amazing icon though. If you have a better options I'm open to replacing the current one.


Compilation error with 1.6.0-dev

Hi! I'm getting the following error trying to compile my factory file. For the life of me, I can't seem to spot the problem and I figure it's maybe an issue between ExMachina and the last version of 1.6.0-dev + Erlang 20:
== Compilation error in file test/support/factory.ex ==
** (CompileError) test/support/factory.ex:6: definitions with multiple clauses and default values require a header. Instead of:

    def foo(:first_clause, b \\ :default) do ... end
    def foo(:second_clause, b) do ... end

one should write:

    def foo(a, b \\ :default)
    def foo(:first_clause, b) do ... end
    def foo(:second_clause, b) do ... end

def build/2 has multiple clauses and defines defaults in one or more clauses
    test/support/factory.ex:6: (module)
    (stdlib) erl_eval.erl:670: :erl_eval.do_apply/6

Elixir head is f042738
Erlang is OTP 20.1.7
It's possible it's just something I'm doing but I think maybe I'm catching a potential problem with 1.6 or Erlang 20

For reference, here's my factory file:
defmodule ItsAParty.Factory do
  # with Ecto
  use ExMachina.Ecto, repo: ItsAParty.Repo

  # without Ecto
  use ExMachina

  def user_factory do
    %ItsAParty.Accounts.User{
      first_name: "Jane",
      last_name: "Smith",
      roles: [],
      credential: build(:credential),
    }
  end

  def credential_factory do
    %ItsAParty.Accounts.Credential{
      email: sequence(:email, &"email-#{&1}@example.com"),
      password: "password12",
      password_confirmation: "password12"
    }
  end

end

Ha! I get it -- I didn't see the two imports above aren't supposed to be used together. Oops!


Is this a mistake?

I have only started type level programming fairly recently; I was wondering if the FilterNum example in the readme file is missing the infer keywords before Head and Tail.

I made a pull request.

Thanks so much! Merged.


Stripe requesting card info twice when 3D Secure is required

Laravel Version: 5.8.35
Cashier Version: 10.2.1
PHP Version: 7.2.22

Description:
When 3D Secure is required on card user needs to be redirected to cashier.payment, which is all correct, but page requires to repeat card information for second time.
Steps To Reproduce:
 try {
     $payment = $user->newSubscription('main', $plan->stripe_plan)->create($method->id);
 }   catch (IncompletePayment $exception) {
     return redirect()->route(
          'cashier.payment',
         [$exception->payment->id, 'redirect' => route('home')]
    );
 }

If the original blade is not changed you will get empty card form again.
Possible solution:
As per https://stripe.com/docs/stripe-js/reference#stripe-handle-card-payment-no-element
Workaround (might not be very secure, but...) is to pass the same payment method to the redirection route like this:
$token = StripeToken::retrieve($request->stripeToken, Cashier::stripeOptions());
return redirect()->route(
    'cashier.payment',
    [
        $exception->payment->id,
        'redirect' => route('home'),
        'card_token' => $token->card->id
    ]
);

Publish blade files:
php artisan vendor:publish --tag="cashier-views"
Make the cashier.payment blade trigger this.confirmPayment() on mounted().
And change stripe.handleCardPayment to:
stripe.handleCardPayment(
    '{{ $payment->clientSecret() }}', {
        payment_method: '{{ request()->get('card_token') }}',
    }, {
        payment_method_data: {
            billing_details: { name: this.name }
        }
    }
)

Also name on card should be passed on initial card charge attempt, cause cashier.payment blade will instantly ask for 3DS authentication.
Now user is not forced to fill card info again.
All the page design changes and loading spinner is up to you.

I see you're using a stripe token which is unfortunately deprecated in the new cashier. we only support the payment methods api.

So here you have support for that :). Please @deprecate then.
yeah i see now, my code has a mix of old 7.0 and new 10.2 Cashier.
so just to be clear, payment setup logic is as follows:

Setup Payment Intent
Show user Card form (process 3Ds if needed)
Get that payment method and charge or subscribe over it

am i correct ?

I think it's best that if you need support for older versions that you try a support channel, sorry.

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

I don't need support for old version. As per issue details Cashier version was 10.2. But i think you are right, i should get support there.


Fix typo in method name in subnetwork module

@bgyori this was really uncontroversial so I went ahead and merged it so I could reuse this in another PR


Optional slices must be a pointer

I'm using the models generated by Prisma, and optional slices are not outputted as pointers because slices are already nilable values. However, when I try to use the model with graphql-go, I receive the following error
panic: field "Where": field "IDIn": []string is not a pointer

Is this behavior correct? The issue is resolved if I manually change the slices in my model to be pointers to slices, but this does not seem like the correct solution because a pointer to a slice does not make much sense.
I looked through the graphql-go code, and it looks like there are no special considerations for lists and any optional parameters must be pointers. Is this something that can be fixed? I can make the change, but I just want to check if there is a reason for the current behavior.
Here is a snippet of my model:
type SpaceWhereInput struct {
	ID                       *string           `json:"id,omitempty"`
	IDNot                    *string           `json:"id_not,omitempty"`
	IDIn                     []string          `json:"id_in,omitempty"`
	IDNotIn                  []string          `json:"id_not_in,omitempty"`
	IDLt                     *string           `json:"id_lt,omitempty"`
	IDLte                    *string           `json:"id_lte,omitempty"`
	IDGt                     *string           `json:"id_gt,omitempty"`
	IDGte                    *string           `json:"id_gte,omitempty"`
	IDContains               *string           `json:"id_contains,omitempty"`
	IDNotContains            *string           `json:"id_not_contains,omitempty"`
	IDStartsWith             *string           `json:"id_starts_with,omitempty"`
...

Here is the associated graphql model
input SpaceWhereInput {
  id: ID
  id_not: ID
  id_in: [ID!]
  id_not_in: [ID!]
  id_lt: ID
  id_lte: ID
  id_gt: ID
  id_gte: ID
  id_contains: ID
  id_not_contains: ID
  id_starts_with: ID
...

I do not see any problem with that. Indeed there are some cases when you would want to distinguish between empty slice and a nil slice. However, these cases are extremely rare. In the vast majority of cases you should have a non-nullable slice of non-nullable elements, for example:
id_in: [ID!]!

There is a difference between a nil slice and a nil pointer to a slice. What I think @kevinwmiller is getting at is that a pointer to a slice doesn't make sense because a slice is already a pointer (like channels and maps), so you can still easily distinguish between a nil slice and an empty slice.
package main

import "fmt"

func main() {
	var ptest *[]string
	var test []string
	fmt.Println("zero values")
	fmt.Println("it's nil", ptest == nil)
	fmt.Println("it's nil", test == nil)
	ptest = &test
	fmt.Println("ptest = &test")
	fmt.Println("it's nil", ptest == nil)
	fmt.Println("it's nil", test == nil)
	fmt.Println("it's nil", *ptest == nil)
	test = make([]string, 0)
	fmt.Println("test = make([]string, 0)")
	fmt.Println("it's nil", ptest == nil)
	fmt.Println("it's nil", test == nil)
	fmt.Println("it's nil", *ptest == nil)
}

Output
zero values
it's nil true
it's nil true
ptest = &test
it's nil false
it's nil true
it's nil true
test = make([]string, 0)
it's nil false
it's nil false
it's nil false

His slices could be nil, but if he goes with id_in: [ID!]! and they are nil, it will error out because it's not declared that way.

@kevinwmiller When I started using the library it was already like this. We need to be careful with changes like this. Your comment makes total sense, however, changing that would probably introduce a breaking change for existing users of the library, right? At this point I would be skeptical with any type of breaking changes. Pointer to a slice seems like a good workaround for now. Maybe we need to make this a schema option and allow users to override the default behaviour 🤔
I'd be happy to accept a PR if it doesn't introduce a breaking change...

@pavelnikolov I completely agree that making a breaking change to accommodate this issue would be unacceptable. I can take a closer look and see if I can come up with a solution that does not break existing functionality

Should the issue be reopened or do you want to leave it marked as closed?

TBH this already has a simple workaround that doesn't cause too much pain. I'd be happy to leave it closed. If this is blocking you or cause a serious problem, then I'd reopen it. It is not really a bug, it's more like a decision that was made initially and now we have to stick to it. The only possible way to change it is with a opt-in schema option at creation time. Otherwise, changing this behaviour would break compatibility with existing users...
I'd consider merging a PR that adds an opt-in fix.


Simplify use of abseil in add_subdirectory mode

We use abseil with CMake FetchContent and add_subdirectory. We also use googletest in the same way.
This produces a conflict because googletest is now included twice. This option would solves this problem.

@googlebot I signed it!

Hello and Have a great time


Indentation disappears when formating table

Keep indentation

b4 pressing tab we need to check if we are inside a table or not.

@takumisoft68 can we also have shift+tab to go to prev cell ?

@ctf0 Do you say another issue?

more of a feature really.

@ctf0 Thanks for a new idea.
But this ticket is not an idea inventry.
New idea needs a new ticket, so I have created another ticket #5.


Retrieve transactions

Hi,
How we can retrieve transactions from affilinet ? as we are an advertiser and we display shops, products on our website now when user purchase using our website we have an issue to retrieve transactions of those users, there is no help please guide.
We have account here: http://publisher.affili.net/Help/Help.aspx
Thanks

Dear Muhammad,
if you are registered as a publishers with affilinet, you can retrieve transactions via the publisher statistics webservice. Please have a look here for documentation: http://developer.affili.net/publisher-webservices/documentation/
Best regards
Till


[KeyVault] - Fix incorrect paths to keyvault-common

What
-Ensure all imports to keyvault-common go through the src directory
Why
We noticed that rollup failed to find imports from keyvault common when we updated our test dependencies to use the published KV Keys version.
This is not an issue when we were using the version of KV Keys on master because of the way rush would use symlinks; however,
this is an issue in a certain edge case and therefore should be fixed,
Longer term we'd like to run at least one of our packages against the published version to find issues like this sooner.

/check-enforcer override


Added support for VS Code Remote Development

Hi Waldek,
Context:

https://code.visualstudio.com/docs/remote/remote-overview

Changes:

I started from the "node" sample template

https://github.com/microsoft/vscode-remote-try-node/blob/master/.devcontainer/Dockerfile

I merged with the docker-spfx template
I created the .devcontainer.json

Added ports to map
Added user spfx

Tested on:

Windows 10 1903
VS Code 1.35.0-insider (user setup)
Docker Desktop <IP_ADDRESS> (edge)

Feel free to reject and add in a separate folder as you see fit.
Christian D.

Thanks! Let me take a look at it and we'll take it from there. Appreciate your help! 👏

Thinking more of it, I think it would belong more in SPFx projects than in the base image itself.


[Light-Client] parachain-compatibility without checking for finalization proofs

All the preliminary work to have dynamic light-client initialization has been done. For parachain compatibility, we will now implement a mini light client, which does not check finalization.
The core logic should be the same as we have for GrandpaLightValidation, but we will remove all the grandpa-specific stuff.
For now, we could call it SimpleLightValidation, as it will not check for any finalization proof. Checking finalization proof of the parachain will be kept for a later issue.
Tasks:

[ ] Implement the Validation trait for SimpleLightValidation
[ ] Add LightClientInitParam variant: Parachain
[ ] Dynamically initialize the light client as discussed with @mullefel.

Reopening this, as we are not yet parachain compatible:
https://github.com/integritee-network/worker/blob/4325de7d4c6939755a6cd9b21b312b40ba306268/service/src/main.rs#L707-L709


angr

Project description
angr is a python framework for analyzing binaries. It combines both static and dynamic symbolic ("concolic") analysis, making it applicable to a variety of tasks.
Metadata

homepage URL: https://angr.io/
source URL: https://github.com/angr
license: bsd2
platforms: linux

I started looking into this, but it's taking some time. There are a lot of dependencies that need to be added in addition to angr.

I have been writing PRs, for packaging missing angr requirements into pythonPackages.
Some are being accepted, some are still pending; But unfortunately, some may not have their place in this repo: as per  @jonringer's comment on #68428 .

I started wondering couple of weeks ago if I should not even put all my work from angr in a repo separated from nixpkgs (something like mozilla/nixpkgs-mozilla).
This would be much less troublesome to maintain, especially considering the poor state of their engineering practices (although they are deploying efforts to improve it).
However, I do not have time, nor the knowledge, to make such a repository; And it is very unlikely that the core angr team will do, as they have a very small user base using NixOS, and other engineering priorities.
In the end, I learned about NUR very recently, so that might be a way to go to get the package available quickly, and leave time to make a solution the angr team can have more control on.

although angr looks like an active repo/community, unfortunately cooldict didn't really hit a standard bar with me. Another committer might disagree and feel fine with it, I just didn't :/
it should be easy enough to get a pipenv or virtualenv going, and use pip to install it though

@jonringer, I am not sure how to interpret your last statement:
You mean pip install it as part of the building of the angr package?

$ nix-shell -p python3Packages.virtualenv
$ virtualenv venv
$ source venv/bin/activate
$ pip install angr

FYI, angr updated its code not to be dependent on cooldict anymore: https://github.com/angr/angr/commit/aace252da92c78dcb9eb70e9bda9ceb2fe4aa17e .

I have started angr/nixpkgs!
As per the discussion above, it seems more pertinent to isolate the "home-developed" angr related packages into a dedicated repository, made available on NUR.
Packages for which I had a PR waiting in NixOS/nixpkgs, are already migrated.
Expressions for other angr components will follow.
As my development environment is a bit messy right now (using my fork, the normal nixpkgs, plus the new NUR repo in local), I will wait to have tidied a bit before sharing my nix expressions as examples in angr/nixpkgs.
Feel free to reach out if you have questions :)

Keep persevering @Pamplemousse, this looks really neat.

@risicle Thanks for the support!
As discussed earlier, angr has found its place in NUR: https://github.com/angr/nixpkgs.
I will happily take feedback over there: I am still quite a beginner at Nix/Nixpkgs, so reviews would be extra helpful.
You are welcome to open issues or submit PRs for comments and proposals :)
And I have finally added angr to it! :tada:

@jonringer, @armijnhemel
Should this issue be closed as angr is available via NUR?

I'm not familiar with the package, but if it there's broad appeal, then i would say continue the good fight.
Most of my hesitation was around some of the dependencies which were unmaintained for over a year (such as cooldict, which was later removed as a dependency).

I would certainly appreciate having pyvex available to me in nixpkgs...

(same goes for archinfo)

@Pamplemousse I would try to upstream it, my major concern is if it only works on python2, which according to pypi, it does not.

@jonringer angr drops its support for Python2 on their latest major release: https://angr.io/blog/moving_to_angr_8/ .
Hence, it only works on Python3!

I think if the PR was updated to the latest version, this is still applicable to be added to nixpkgs

TL;DR: I am going to stick with contributing to angr/nixpkgs, and won't spend time or energy trying to package angr (and its dependencies) here.

Because it's being "cutting-edge" by nature (developed in a academic research environment), I don't think it is worth trying to put angr (nor the dependencies the angr team develops - archinfo, claripy, cle, pyvex, etc.) in nixpkgs.

They have now a "fast" release cycle: they started doing a "stable" release every week, but slowed down lately (unsure why, but might be related to the fact that the process is not completely automated - so dependent on the workload of the core contributors);
Their definition of "stable" is... disconcerting: they often rely on non-stable features of their dependencies, or custom forks. See angr/cle#255, angr/cle#257 for recent examples of that;
They sometimes introduce dependencies that might not be up to nixpkgs expectations: a recent example is pyxbe (one maintainer, created recently, so hard to tell if it won't become stale).

Which means that updating the angr package would often requires repackaging dependencies, sometimes creating expression for custom forks.
Plus, if one wanted to keep up with their "fast" release cycle, it would imply a decent amount of maintenance here.
Quoting myself from a comment above, I believe NUR is more adapted.:

This would be much less troublesome to maintain (less load on nixpkgs, lower standards for custom packages), especially considering the poor state of their engineering practices (although they are deploying efforts to improve it).

This makes sense :-)

There was already a fair amount of work done. I will continue that effort.

There was already a fair amount of work done. I will continue that effort.

as long as the package additions don't look like massive maintenance burdens and the upstreams are semi-active, I don't mind bringing in what else is needed.
Originally, I just had issues with cooldict, and you can see from the commit history https://github.com/zardus/cooldict/commits/master that it's not super active, and has a few other red flags (no releases, commit history is... weird, profanity for the purpose of being "edgy")

as long as the package additions don't look like massive maintenance burdens and the upstreams are semi-active, I don't mind bringing in what else is needed.
Originally, I just had issues with cooldict, and you can see from the commit history https://github.com/zardus/cooldict/commits/master that it's not super active, and has a few other red flags (no releases, commit history is... weird, profanity for the purpose of being "edgy")

angr is now available.

It is marked as broken :/
Is it because of this: https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/python-modules/angr/default.nix#L121 ?

It is marked as broken :/

Yes, it marked as broken on master. stable should be fine. angr is sensitive to unicorn releases. It could work.

Is the versionAtLeast in the broken attribute quite right? versionAtLeast is true on an exact match, but I think the version in the string there is the one that angr is pinning unicorn at, so an exact match is what would make this non-broken.


If structure contains SRU-Group User can't click 'Calculated Values' button - nothing happens after clicking.

Affected Version: Standalone , Remote (Multiple S-Groups)
Steps to Reproduce:

Create chain structure.
Add SRU-polymer S-Group.
Click 'Calculated Values' button.

Expected Result:
In 'Chemical Formula' field displays correct formula, all another fields contains message: "error: Cannot calculate mass for structure with repeating units"

Actual Result:
If structure contains SRU-Group User can't click 'Calculated Values' button - nothing happens after clicking. The same behavior is with Multiple S-Groups that are on the end of Structure. (Multiple S-Groups behavior reproduces in Remote mode too.)

Here is 2 independent cases.

Standalone and SRU-Group in the middle.  Caused by  https://github.com/epam/Indigo/issues/299. When the linked ticket will be fixed, behavior would be the same as on Remote
Standalone and Remove and SRU-Group at the end of the structure. Caused by invalid molecule structure, in this case molecule even couldn't be saved. Enhancement suggested https://github.com/epam/ketcher/issues/251

For now both cases  were improved with showing error message to user.

Here is 2 independent cases.

Standalone and SRU-Group in the middle.  Caused by  https://github.com/epam/Indigo/issues/299. When the linked ticket will be fixed, behavior would be the same as on Remote
Standalone and Remove and SRU-Group at the end of the structure. Caused by invalid molecule structure, in this case molecule even couldn't be saved. Enhancement suggested https://github.com/epam/ketcher/issues/251

For now both cases  were improved with showing error message to user.

Issue is closed as partially fixed.
When Structure contains SRU-polymer group on the end of Structure now error message appears.
When Structure in Standalone mode contains SRU-polymer group in the middle of Structure - 'Calculated Values' window opens with zero values.

Issue is closed as partially fixed.
When Structure contains SRU-polymer group on the end of Structure now error message appears.
When Structure in Standalone mode contains SRU-polymer group in the middle of Structure - 'Calculated Values' window opens with zero values.


PR: Update for VS 2022

update solution & projects
fix obsolete methods

Ops sorry, targetted this agianst the worng repo. :embarassed face:


Update example to use Chart.js 2.0

:)

Dazzle does not depend on Chart JS but the examples use it. We can certainly update it!


K3s and Flexvolume on read-only file system like RedHat CoreOS

Version:
v1.17.4+k3s1 (3eee8ac3)

K3s arguments:

Describe the bug
I run k3s on RedHat CoreOS, which has a partially read-only file system. In logs I see:
Apr 25 09:13:18 k3s-0-server k3s[1637]: W0425 09:13:18.062008    1637 probe.go:268] Flexvolume plugin directory at /usr/libexec/kubernetes/kubelet-plugins/volume/exec/ does not exist. Recreating.
Apr 25 09:13:18 k3s-0-server k3s[1637]: E0425 09:13:18.062064    1637 plugins.go:599] Error initializing dynamic plugin prober: Error (re-)creating driver directory: mkdir /usr/libexec/kubernetes: read-only file system

https://bugzilla.redhat.com/show_bug.cgi?id=1667606
RedHat solved this by using a different location, specifically /etc/kubernetes/kubelet-plugins/volume/exec.
To Reproduce
Run k3s in any environment with read-only file system.
Expected behavior
K3s will either detect RedHat CoreOS and Fedora CoreOS as having a read-only file system and automatically use the available writable location, or k3s will offer a runtime parameter to customize the location.
Actual behavior
K3s raises an error and continues running.
Additional context / logs

@stellirin we ran into this as well, see https://github.com/rancher/k3os/issues/282#issuecomment-554771553. A reasonable work-around is to pass --kube-controller-arg=flex-volume-plugin-dir=/etc/kubernetes/kubelet-plugins/volume/exec to k3s server


⚠ Bofrost.at has degraded performance

In f3f7729, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 3409 ms

Resolved: Bofrost.at performance has improved in 6423657 after 14 minutes.


Is there a way to set the GPU ID for multi-GPU systems?

In app.py, after Caffe is imported on line 41, we have:
import caffe
  if settings.caffevis_mode_gpu:
            caffe.set_mode_gpu()
            print 'CaffeVisApp mode (in main thread):     GPU'
        else:
            caffe.set_mode_cpu()

I would propose modifying this to something like:
import caffe
gpu_id = settings.gpu_id
  if settings.caffevis_mode_gpu:
            caffe.set_mode_gpu()
            if gpu_id is not None:
                       caffe.set_device(gpu_id)
            print 'CaffeVisApp mode (in main thread):     GPU'
        else:
            caffe.set_mode_cpu()

I can make and submit this change if you're open to it.

Setting the CUDA_VISIBLE_DEVICES environment variable is a more standard way, e.g.:
CUDA_VISIBLE_DEVICES=0 ./run_toolbox.py


ec2-instance-connect support

Support for EC2InstanceConnect would be awesome. Will open up a PR if I get a change to implement unless someone beats me to it.

Taken care of in #2639 just waiting on merge.


Support the new quantum engine processor_selector in engine_client

The update is no longer a breaking change.  Note that I force pushed (because the refactor was quite heavy), so most comments from the first round are outdated.

In the last few commits I added the rewrite function to the deprecated parameter decorator. Now we only get requests for the quantum engine where processor_id is set instead of processor_ids in the processor selector . Therefore we can now delete processor_ids from the Quantum Engine API and refactor without affecting the cirq-google behavior.


[prometheus-cpp] Update to version 0.12.1

Update prometheus-cpp to 0.12.0. Locally tested on macOS.

Version 0.12.0 did not compile with C++17 on latest VS2019.

@gjasny ,Have you tested all these features?

Thanks for the review. I updated the portfile and also tested the feature flags permutations.

Awesome, thanks for the update!


App Crash on macOS Version:11.2.3

just open my app. on  macOS  version:11.2.3 ,then it crashed.
but other Mac is work well .
I can't find  the dsym files of FlutterMacOS. so have no idea about why this happend
Application Specific Information:
AppName(16739,0x70000f4aa000) malloc: Incorrect checksum for freed object 0x7fae454e5610: probably modified after being freed.
Corrupt value: 0x9000000000202022
Thread 6 Crashed:
0   libsystem_kernel.dylib          0xfffe4088c462      __pthread_kill
1   libsystem_c.dylib               0xfffe40715720      abort
2   libsystem_malloc.dylib          0xfffe40548430      malloc_vreport
3   libsystem_malloc.dylib          0xfffe4055c702      malloc_zone_error
4   libsystem_malloc.dylib          0xfffe4053fcb4      tiny_free_no_lock
5   libsystem_malloc.dylib          0xfffe4053f1f9      free_tiny
6   Metal                           0xfffe50900105      MTLLibraryBuilder::initLibraryContainerWithRequestData
7   Metal                           0xfffe509010d4      MTLLibraryBuilder::newLibraryWithRequestData
8   Metal                           0xfffe50902bbc      MTLLibraryBuilder::newLibraryWithSource
9   Metal                           0xfffe508da121      -[_MTLDevice newLibraryWithSource:options:completionHandler:]
10  FlutterMacOS                    0x10186b94a         delete[]
11  FlutterMacOS                    0x10186b704         delete[]
12  FlutterMacOS                    0x10185fdc0         delete[]
13  FlutterMacOS                    0x10185ea72         delete[]
14  FlutterMacOS                    0x101865dbf         delete[]
here is the whole crash file
13b214bd8d44486c852a0e6d2ad91d77-symbolicated.txt

Hi @Renqianbei
Is this issue reproducible locally? If so, can you please share the output of flutter run -v and a completed and minimal reproducible code sample?
Also, please provide the output of flutter doctor -v as well.
Thank you!

sorry ，its not locally, it happen at our customer‘s  Macbook.
here is the flutter doctor -v  result
^[[✓] Flutter (Channel unknown, 3.0.1, on macOS 11.6.7 20G630 darwin-x64, locale zh-Hans-CN)
• Flutter version 3.0.1 at /Users/renqianbei/Library/Application Support/fvm/versions/3.0.1
• Upstream repository unknown
• Framework revision fb57da5f94 (3 months ago), 2022-05-19 15:50:29 -0700
• Engine revision caaafc5604
• Dart version 2.17.1
• DevTools version 2.12.2
• Pub download mirror https://pub.flutter-io.cn
• Flutter download mirror https://storage.flutter-io.cn
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/renqianbei/Library/Android/sdk
✗ cmdline-tools component is missing
Run path/to/sdkmanager --install "cmdline-tools;latest"
See https://developer.android.com/studio/command-line for more details.
✗ Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.11.3
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2020.3)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
[✓] VS Code (version 1.51.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.16.0
[✓] Connected device (2 available)
• macOS (desktop) • macos  • darwin-x64     • macOS 11.6.7 20G630 darwin-x64
• Chrome (web)    • chrome • web-javascript • Google Chrome 103.0.5060.134
! Error: 任前辈的 iPhone is not connected. Xcode will continue when 任前辈的 iPhone is connected. (code -13)
[✓] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 1 category.

Hi @Renqianbei
Is this issue reproducible locally? If so, can you please share the output of flutter run -v and a completed and minimal reproducible code sample?
Also, please provide the output of flutter doctor -v as well.
Thank you!

sorry ，its not locally, it happen at our customer‘s Macbook.
here is the flutter doctor -v result
^[[✓] Flutter (Channel unknown, 3.0.1, on macOS 11.6.7 20G630 darwin-x64, locale zh-Hans-CN)
• Flutter version 3.0.1 at /Users/renqianbei/Library/Application Support/fvm/versions/3.0.1
• Upstream repository unknown
• Framework revision https://github.com/flutter/flutter/commit/fb57da5f945d02ef4f98dfd9409a72b7cce74268 (3 months ago), 2022-05-19 15:50:29 -0700
• Engine revision caaafc5604
• Dart version 2.17.1
• DevTools version 2.12.2
• Pub download mirror https://pub.flutter-io.cn
• Flutter download mirror https://storage.flutter-io.cn
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/renqianbei/Library/Android/sdk
✗ cmdline-tools component is missing
Run path/to/sdkmanager --install "cmdline-tools;latest"
See https://developer.android.com/studio/command-line for more details.
✗ Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 13.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• CocoaPods version 1.11.3
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 2020.3)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7281165)
[✓] VS Code (version 1.51.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.16.0
[✓] Connected device (2 available)
• macOS (desktop) • macos • darwin-x64 • macOS 11.6.7 20G630 darwin-x64
• Chrome (web) • chrome • web-javascript • Google Chrome 103.0.5060.134
! Error: 任前辈的 iPhone is not connected. Xcode will continue when 任前辈的 iPhone is connected. (code -13)
[✓] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 1 category.

@Renqianbei Could you try running your project with release mode to see if the issue reproduces?

@Renqianbei Could you try running your project with release mode to see if the issue reproduces?

I have run the project with release mode on my Mac , it doesn`t reproduces.
it doesn't happen on my Mac, by now it only happened on  macOS Version 11.2.3.
this crash log below may help
574f7034d2d64592891384ec588dd9af-symbolicated.txt

@Renqianbei thanks for your response. Labeling this issue for further investigation from the team.

Thank you for taking the time to file this issue. Without a reproduction case, we're unfortunately not sure how to resolve this issue, and the crashing thread doesn't appear to be specific to Flutter. I'm therefore reluctantly going to close this for now. Please don't hesitate to comment on the issue if you have any more information to add; we'll reopen it right away!
(Desktop Triage)


Fargate

Is this supported on Fargate? I get the error Fargate only supports network mode ‘awsvpc’

@steverecio i'm just hitting this issue (name of one container isn't resolving as a host in the other container) when using fargate with awsvpc. Did you manage to find the solution?

@steverecio @sadams How have you solved this issue ?


Merge changes upstream

Attempt to get some of these changes back into the upstream repo.
Throwing into a non-master branch so I can edit there.

Well this isn't gonna work - try #19 instead.


libnvinfer_plugin_tensorrt_llm.so: cannot open shared object file: Not a directory

run on colab A100
!git clone https://github.com/NVIDIA/TensorRT-LLM.git

!cd TensorRT-LLM && git lfs install && python setup.py install \
  && pip install -r examples/bloom/requirements.txt

!pip uninstall -y tensorrt
!pip install --no-cache-dir --extra-index-url https://pypi.nvidia.com tensorrt==9.2.0.post12.dev5

!cd TensorRT-LLM/examples/bloom \
  && rm -rf ./bloom/560M \
  && mkdir -p ./bloom/560M && git clone https://huggingface.co/bigscience/bloom-560m ./bloom/560M

# Single GPU on BLOOM 560M
!cd TensorRT-LLM/examples/bloom \
  && python convert_checkpoint.py --model_dir ./bloom/560M/ \
                --dtype float16 \
                --output_dir ./bloom/560M/trt_ckpt/fp16/1-gpu/

Traceback (most recent call last):
  File "/content/TensorRT-LLM/examples/bloom/convert_checkpoint.py", line 17, in <module>
    import tensorrt_llm
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm-0.6.1-py3.10-linux-x86_64.egg/tensorrt_llm/__init__.py", line 61, in <module>
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm-0.6.1-py3.10-linux-x86_64.egg/tensorrt_llm/_common.py", line 47, in _init
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm-0.6.1-py3.10-linux-x86_64.egg/tensorrt_llm/plugin/plugin.py", line 34, in _load_plugin_lib
  File "/usr/lib/python3.10/ctypes/__init__.py", line 374, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: /usr/local/lib/python3.10/dist-packages/tensorrt_llm-0.6.1-py3.10-linux-x86_64.egg/tensorrt_llm/libs/libnvinfer_plugin_tensorrt_llm.so: cannot open shared object file: Not a directory

Do you use docker image built on latest codes? If yes, could you share how do you build the docker?

@byshiue  don't use docker, just run on google-colab ... colab maybe don't run dockerd

I don't see you build the tensorrt_llm repo in your scripts (like python3 build_wheel.py && pip install xxx.whl. Please refer the document here https://github.com/NVIDIA/TensorRT-LLM/blob/main/docs/source/installation.md#build-tensorrt-llm-1.

run this scripts
%%bash
cd TensorRT-LLM && \
  python3 ./scripts/build_wheel.py --python_bindings --trt_root /usr/local/lib/python3.10/dist-packages/tensorrt_libs/ --clean \
  && pip install ./build/tensorrt_llm*.whl

```shell

Looking in indexes: https://pypi.org/simple, https://pypi.ngc.nvidia.com/
Requirement already satisfied: accelerate==0.20.3 in /usr/local/lib/python3.10/dist-packages/accelerate-0.20.3-py3.10.egg (from -r requirements.txt (line 1)) (0.20.3)
Requirement already satisfied: build in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 2)) (1.0.3)
Requirement already satisfied: colored in /usr/local/lib/python3.10/dist-packages/colored-2.2.3-py3.10.egg (from -r requirements.txt (line 3)) (2.2.3)
Requirement already satisfied: cuda-python==12.2.0 in /usr/local/lib/python3.10/dist-packages/cuda_python-12.2.0-py3.10-linux-x86_64.egg (from -r requirements.txt (line 4)) (12.2.0)
Requirement already satisfied: diffusers==0.15.0 in /usr/local/lib/python3.10/dist-packages/diffusers-0.15.0-py3.10.egg (from -r requirements.txt (line 5)) (0.15.0)
Requirement already satisfied: lark in /usr/local/lib/python3.10/dist-packages/lark-1.1.8-py3.10.egg (from -r requirements.txt (line 6)) (1.1.8)
Requirement already satisfied: mpi4py in /usr/local/lib/python3.10/dist-packages/mpi4py-3.1.5-py3.10-linux-x86_64.egg (from -r requirements.txt (line 7)) (3.1.5)
Requirement already satisfied: numpy in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 8)) (1.23.5)
Requirement already satisfied: onnx>=1.12.0 in /usr/local/lib/python3.10/dist-packages/onnx-1.15.0-py3.10-linux-x86_64.egg (from -r requirements.txt (line 9)) (1.15.0)
Requirement already satisfied: polygraphy in /usr/local/lib/python3.10/dist-packages/polygraphy-0.49.0-py3.10.egg (from -r requirements.txt (line 10)) (0.49.0)
Requirement already satisfied: sentencepiece>=0.1.99 in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 11)) (0.1.99)
Requirement already satisfied: tensorrt>=8.6.0 in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 12)) (9.2.0.post12.dev5)
Requirement already satisfied: torch in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 13)) (2.1.0+cu121)
Requirement already satisfied: transformers==4.33.1 in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 14)) (4.33.1)
Requirement already satisfied: wheel in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 15)) (0.42.0)
Requirement already satisfied: optimum in /usr/local/lib/python3.10/dist-packages/optimum-1.16.1-py3.10.egg (from -r requirements.txt (line 16)) (1.16.1)
Requirement already satisfied: evaluate in /usr/local/lib/python3.10/dist-packages (from -r requirements.txt (line 17)) (0.4.1)
Requirement already satisfied: datasets in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 2)) (2.14.7)
Requirement already satisfied: einops in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 3)) (0.7.0)
Requirement already satisfied: graphviz in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 5)) (0.20.1)
Requirement already satisfied: mypy in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 6)) (1.7.1)
Requirement already satisfied: parameterized in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 7)) (0.9.0)
Requirement already satisfied: pre-commit in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 8)) (3.6.0)
Requirement already satisfied: pybind11-stubgen in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 9)) (2.4.2)
Requirement already satisfied: pynvml>=11.5.0 in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 10)) (11.5.0)
Requirement already satisfied: pytest-cov in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 11)) (4.1.0)
Requirement already satisfied: pytest-forked in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 12)) (1.6.0)
Requirement already satisfied: pytest-xdist in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 13)) (3.5.0)
Requirement already satisfied: rouge_score in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 14)) (0.1.2)
Requirement already satisfied: typing-extensions==4.8.0 in /usr/local/lib/python3.10/dist-packages (from -r requirements-dev.txt (line 16)) (4.8.0)
Requirement already satisfied: packaging>=20.0 in /usr/local/lib/python3.10/dist-packages (from accelerate==0.20.3->-r requirements.txt (line 1)) (23.2)
Requirement already satisfied: psutil in /usr/local/lib/python3.10/dist-packages (from accelerate==0.20.3->-r requirements.txt (line 1)) (5.9.5)
Requirement already satisfied: pyyaml in /usr/local/lib/python3.10/dist-packages (from accelerate==0.20.3->-r requirements.txt (line 1)) (6.0.1)
Requirement already satisfied: cython in /usr/local/lib/python3.10/dist-packages (from cuda-python==12.2.0->-r requirements.txt (line 4)) (3.0.6)
Requirement already satisfied: Pillow in /usr/local/lib/python3.10/dist-packages (from diffusers==0.15.0->-r requirements.txt (line 5)) (9.4.0)
Requirement already satisfied: filelock in /usr/local/lib/python3.10/dist-packages (from diffusers==0.15.0->-r requirements.txt (line 5)) (3.13.1)
Requirement already satisfied: huggingface-hub>=0.13.2 in /usr/local/lib/python3.10/dist-packages (from diffusers==0.15.0->-r requirements.txt (line 5)) (0.19.4)
Requirement already satisfied: importlib-metadata in /usr/local/lib/python3.10/dist-packages (from diffusers==0.15.0->-r requirements.txt (line 5)) (7.0.0)
Requirement already satisfied: regex!=2019.12.17 in /usr/local/lib/python3.10/dist-packages (from diffusers==0.15.0->-r requirements.txt (line 5)) (2023.6.3)
Requirement already satisfied: requests in /usr/local/lib/python3.10/dist-packages (from diffusers==0.15.0->-r requirements.txt (line 5)) (2.31.0)
Requirement already satisfied: tokenizers!=0.11.3,<0.14,>=0.11.1 in /usr/local/lib/python3.10/dist-packages (from transformers==4.33.1->-r requirements.txt (line 14)) (0.13.3)
Requirement already satisfied: safetensors>=0.3.1 in /usr/local/lib/python3.10/dist-packages (from transformers==4.33.1->-r requirements.txt (line 14)) (0.4.1)
Requirement already satisfied: tqdm>=4.27 in /usr/local/lib/python3.10/dist-packages (from transformers==4.33.1->-r requirements.txt (line 14)) (4.66.1)
Requirement already satisfied: pyproject_hooks in /usr/local/lib/python3.10/dist-packages (from build->-r requirements.txt (line 2)) (1.0.0)
Requirement already satisfied: tomli>=1.1.0 in /usr/local/lib/python3.10/dist-packages (from build->-r requirements.txt (line 2)) (2.0.1)
Requirement already satisfied: protobuf>=3.20.2 in /usr/local/lib/python3.10/dist-packages (from onnx>=1.12.0->-r requirements.txt (line 9)) (4.23.4)
Requirement already satisfied: tensorrt-libs==9.2.0.post12.dev5 in /usr/local/lib/python3.10/dist-packages (from tensorrt>=8.6.0->-r requirements.txt (line 12)) (9.2.0.post12.dev5)
Requirement already satisfied: tensorrt-bindings==9.2.0.post12.dev5 in /usr/local/lib/python3.10/dist-packages (from tensorrt>=8.6.0->-r requirements.txt (line 12)) (9.2.0.post12.dev5)
Requirement already satisfied: nvidia-cuda-runtime-cu12 in /usr/local/lib/python3.10/dist-packages (from tensorrt-libs==9.2.0.post12.dev5->tensorrt>=8.6.0->-r requirements.txt (line 12)) (12.3.101)
Requirement already satisfied: nvidia-cudnn-cu12 in /usr/local/lib/python3.10/dist-packages (from tensorrt-libs==9.2.0.post12.dev5->tensorrt>=8.6.0->-r requirements.txt (line 12)) (<IP_ADDRESS>)
Requirement already satisfied: nvidia-cublas-cu12 in /usr/local/lib/python3.10/dist-packages (from tensorrt-libs==9.2.0.post12.dev5->tensorrt>=8.6.0->-r requirements.txt (line 12)) (<IP_ADDRESS>)
Requirement already satisfied: sympy in /usr/local/lib/python3.10/dist-packages (from torch->-r requirements.txt (line 13)) (1.12)
Requirement already satisfied: networkx in /usr/local/lib/python3.10/dist-packages (from torch->-r requirements.txt (line 13)) (3.2.1)
Requirement already satisfied: jinja2 in /usr/local/lib/python3.10/dist-packages (from torch->-r requirements.txt (line 13)) (3.1.2)
Requirement already satisfied: fsspec in /usr/local/lib/python3.10/dist-packages (from torch->-r requirements.txt (line 13)) (2023.6.0)
Requirement already satisfied: triton==2.1.0 in /usr/local/lib/python3.10/dist-packages (from torch->-r requirements.txt (line 13)) (2.1.0)
Requirement already satisfied: coloredlogs in /usr/local/lib/python3.10/dist-packages/coloredlogs-15.0.1-py3.10.egg (from optimum->-r requirements.txt (line 16)) (15.0.1)
Requirement already satisfied: dill in /usr/local/lib/python3.10/dist-packages (from evaluate->-r requirements.txt (line 17)) (0.3.7)
Requirement already satisfied: pandas in /usr/local/lib/python3.10/dist-packages (from evaluate->-r requirements.txt (line 17)) (1.5.3)
Requirement already satisfied: xxhash in /usr/local/lib/python3.10/dist-packages (from evaluate->-r requirements.txt (line 17)) (3.4.1)
Requirement already satisfied: multiprocess in /usr/local/lib/python3.10/dist-packages (from evaluate->-r requirements.txt (line 17)) (0.70.15)
Requirement already satisfied: responses<0.19 in /usr/local/lib/python3.10/dist-packages (from evaluate->-r requirements.txt (line 17)) (0.18.0)
Requirement already satisfied: pyarrow>=8.0.0 in /usr/local/lib/python3.10/dist-packages (from datasets->-r requirements-dev.txt (line 2)) (10.0.1)
Requirement already satisfied: pyarrow-hotfix in /usr/local/lib/python3.10/dist-packages (from datasets->-r requirements-dev.txt (line 2)) (0.6)
Requirement already satisfied: aiohttp in /usr/local/lib/python3.10/dist-packages (from datasets->-r requirements-dev.txt (line 2)) (3.9.1)
Requirement already satisfied: mypy-extensions>=1.0.0 in /usr/local/lib/python3.10/dist-packages (from mypy->-r requirements-dev.txt (line 6)) (1.0.0)
Requirement already satisfied: cfgv>=2.0.0 in /usr/local/lib/python3.10/dist-packages (from pre-commit->-r requirements-dev.txt (line 8)) (3.4.0)
Requirement already satisfied: identify>=1.0.0 in /usr/local/lib/python3.10/dist-packages (from pre-commit->-r requirements-dev.txt (line 8)) (2.5.33)
Requirement already satisfied: nodeenv>=0.11.1 in /usr/local/lib/python3.10/dist-packages (from pre-commit->-r requirements-dev.txt (line 8)) (1.8.0)
Requirement already satisfied: virtualenv>=20.10.0 in /usr/local/lib/python3.10/dist-packages (from pre-commit->-r requirements-dev.txt (line 8)) (20.25.0)
Requirement already satisfied: pytest>=4.6 in /usr/local/lib/python3.10/dist-packages (from pytest-cov->-r requirements-dev.txt (line 11)) (7.4.3)
Requirement already satisfied: coverage[toml]>=5.2.1 in /usr/local/lib/python3.10/dist-packages (from pytest-cov->-r requirements-dev.txt (line 11)) (7.3.3)
Requirement already satisfied: py in /usr/local/lib/python3.10/dist-packages (from pytest-forked->-r requirements-dev.txt (line 12)) (1.11.0)
Requirement already satisfied: execnet>=1.1 in /usr/local/lib/python3.10/dist-packages (from pytest-xdist->-r requirements-dev.txt (line 13)) (2.0.2)
Requirement already satisfied: absl-py in /usr/local/lib/python3.10/dist-packages (from rouge_score->-r requirements-dev.txt (line 14)) (1.4.0)
Requirement already satisfied: nltk in /usr/local/lib/python3.10/dist-packages (from rouge_score->-r requirements-dev.txt (line 14)) (3.8.1)
Requirement already satisfied: six>=1.14.0 in /usr/local/lib/python3.10/dist-packages (from rouge_score->-r requirements-dev.txt (line 14)) (1.16.0)
Requirement already satisfied: attrs>=17.3.0 in /usr/local/lib/python3.10/dist-packages (from aiohttp->datasets->-r requirements-dev.txt (line 2)) (23.1.0)
Requirement already satisfied: multidict<7.0,>=4.5 in /usr/local/lib/python3.10/dist-packages (from aiohttp->datasets->-r requirements-dev.txt (line 2)) (6.0.4)
Requirement already satisfied: yarl<2.0,>=1.0 in /usr/local/lib/python3.10/dist-packages (from aiohttp->datasets->-r requirements-dev.txt (line 2)) (1.9.4)
Requirement already satisfied: frozenlist>=1.1.1 in /usr/local/lib/python3.10/dist-packages (from aiohttp->datasets->-r requirements-dev.txt (line 2)) (1.4.0)
Requirement already satisfied: aiosignal>=1.1.2 in /usr/local/lib/python3.10/dist-packages (from aiohttp->datasets->-r requirements-dev.txt (line 2)) (1.3.1)
Requirement already satisfied: async-timeout<5.0,>=4.0 in /usr/local/lib/python3.10/dist-packages (from aiohttp->datasets->-r requirements-dev.txt (line 2)) (4.0.3)
Requirement already satisfied: setuptools in /usr/local/lib/python3.10/dist-packages (from nodeenv>=0.11.1->pre-commit->-r requirements-dev.txt (line 8)) (67.7.2)
Requirement already satisfied: iniconfig in /usr/local/lib/python3.10/dist-packages (from pytest>=4.6->pytest-cov->-r requirements-dev.txt (line 11)) (2.0.0)
Requirement already satisfied: pluggy<2.0,>=0.12 in /usr/local/lib/python3.10/dist-packages (from pytest>=4.6->pytest-cov->-r requirements-dev.txt (line 11)) (1.3.0)
Requirement already satisfied: exceptiongroup>=1.0.0rc8 in /usr/local/lib/python3.10/dist-packages (from pytest>=4.6->pytest-cov->-r requirements-dev.txt (line 11)) (1.2.0)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers==0.15.0->-r requirements.txt (line 5)) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers==0.15.0->-r requirements.txt (line 5)) (3.6)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers==0.15.0->-r requirements.txt (line 5)) (2.0.7)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.10/dist-packages (from requests->diffusers==0.15.0->-r requirements.txt (line 5)) (2023.11.17)
Requirement already satisfied: distlib<1,>=0.3.7 in /usr/local/lib/python3.10/dist-packages (from virtualenv>=20.10.0->pre-commit->-r requirements-dev.txt (line 8)) (0.3.8)
Requirement already satisfied: platformdirs<5,>=3.9.1 in /usr/local/lib/python3.10/dist-packages (from virtualenv>=20.10.0->pre-commit->-r requirements-dev.txt (line 8)) (4.1.0)
Requirement already satisfied: humanfriendly>=9.1 in /usr/local/lib/python3.10/dist-packages/humanfriendly-10.0-py3.10.egg (from coloredlogs->optimum->-r requirements.txt (line 16)) (10.0)
Requirement already satisfied: zipp>=0.5 in /usr/local/lib/python3.10/dist-packages (from importlib-metadata->diffusers==0.15.0->-r requirements.txt (line 5)) (3.17.0)
Requirement already satisfied: MarkupSafe>=2.0 in /usr/local/lib/python3.10/dist-packages (from jinja2->torch->-r requirements.txt (line 13)) (2.1.3)
Requirement already satisfied: click in /usr/local/lib/python3.10/dist-packages (from nltk->rouge_score->-r requirements-dev.txt (line 14)) (8.1.7)
Requirement already satisfied: joblib in /usr/local/lib/python3.10/dist-packages (from nltk->rouge_score->-r requirements-dev.txt (line 14)) (1.3.2)
Requirement already satisfied: python-dateutil>=2.8.1 in /usr/local/lib/python3.10/dist-packages (from pandas->evaluate->-r requirements.txt (line 17)) (2.8.2)
Requirement already satisfied: pytz>=2020.1 in /usr/local/lib/python3.10/dist-packages (from pandas->evaluate->-r requirements.txt (line 17)) (2023.3.post1)
Requirement already satisfied: mpmath>=0.19 in /usr/local/lib/python3.10/dist-packages (from sympy->torch->-r requirements.txt (line 13)) (1.3.0)
Requirement already satisfied: nvidia-cuda-nvrtc-cu12 in /usr/local/lib/python3.10/dist-packages (from nvidia-cudnn-cu12->tensorrt-libs==9.2.0.post12.dev5->tensorrt>=8.6.0->-r requirements.txt (line 12)) (12.3.103)
-- The CXX compiler identification is GNU 11.4.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- NVTX is disabled
-- Importing batch manager
-- Building PyTorch
-- Building Google tests
-- Building benchmarks
-- Looking for a CUDA compiler
-- Looking for a CUDA compiler - /usr/local/cuda/bin/nvcc
-- CUDA compiler: /usr/local/cuda/bin/nvcc
-- GPU architectures: 70-real;80-real;86-real;89-real;90-real
-- The C compiler identification is GNU 11.4.0
-- The CUDA compiler identification is NVIDIA 12.2.140
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CUDA compiler ABI info
-- Detecting CUDA compiler ABI info - done
-- Check for working CUDA compiler: /usr/local/cuda/bin/nvcc - skipped
-- Detecting CUDA compile features
-- Detecting CUDA compile features - done
-- Found CUDAToolkit: /usr/local/cuda/include (found version "12.2.140")
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- CUDA library status:
--     version: 12.2.140
--     libraries: /usr/local/cuda/lib64
--     include path: /usr/local/cuda/targets/x86_64-linux/include
-- ========================= Importing and creating target nvinfer ==========================
-- Looking for library nvinfer
-- Library that was found nvinfer_LIB_PATH-NOTFOUND
-- ==========================================================================================
-- CUDAToolkit_VERSION 12.2 is greater or equal than 11.0, enable -DENABLE_BF16 flag
-- CUDAToolkit_VERSION 12.2 is greater or equal than 11.8, enable -DENABLE_FP8 flag
-- Found MPI_C: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so (found version "3.1")
-- Found MPI_CXX: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so (found version "3.1")
-- Found MPI: TRUE (found version "3.1")
-- COMMON_HEADER_DIRS: /content/TensorRT-LLM/cpp;/usr/local/cuda/include
-- Found Python3: /usr/local/bin/python (found version "3.10.12") found components: Interpreter Development Development.Module Development.Embed
-- USE_CXX11_ABI is set by python Torch to 0
-- TORCH_CUDA_ARCH_LIST: 7.0;8.0;8.6;8.9;9.0
-- Found Python executable at /usr/local/bin/python
-- Found Python libraries at /usr/lib/x86_64-linux-gnu
-- Found CUDA: /usr/local/cuda (found version "12.2")
-- Found CUDAToolkit: /usr/local/cuda/include (found version "12.2.140")
-- Caffe2: CUDA detected: 12.2
-- Caffe2: CUDA nvcc is: /usr/local/cuda/bin/nvcc
-- Caffe2: CUDA toolkit directory: /usr/local/cuda
-- Caffe2: Header version is: 12.2
-- /usr/local/cuda-12.2/targets/x86_64-linux/lib/libnvrtc.so shorthash is 000ca627
-- USE_CUDNN is set to 0. Compiling without cuDNN support
-- USE_CUSPARSELT is set to 0. Compiling without cuSPARSELt support
-- Added CUDA NVCC flags for: -gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_86,code=sm_86;-gencode;arch=compute_89,code=sm_89;-gencode;arch=compute_90,code=sm_90
CMake Warning at /usr/local/lib/python3.10/dist-packages/torch/share/cmake/Torch/TorchConfig.cmake:22 (message):
static library kineto_LIBRARY-NOTFOUND not found.
Call Stack (most recent call first):
/usr/local/lib/python3.10/dist-packages/torch/share/cmake/Torch/TorchConfig.cmake:127 (append_torchlib_if_found)
CMakeLists.txt:337 (find_package)
-- Found Torch: /usr/local/lib/python3.10/dist-packages/torch/lib/libtorch.so
-- TORCH_CXX_FLAGS: -D_GLIBCXX_USE_CXX11_ABI=0
CMake Error at CMakeLists.txt:362 (file):
file STRINGS file
"/usr/local/lib/python3.10/dist-packages/tensorrt_libs//include/NvInferVersion.h"
cannot be read.
CMake Error at CMakeLists.txt:365 (string):
string sub-command REGEX, mode MATCH needs at least 5 arguments total to
command.
CMake Error at CMakeLists.txt:367 (string):
string sub-command REGEX, mode MATCH needs at least 5 arguments total to
command.
CMake Error at CMakeLists.txt:365 (string):
string sub-command REGEX, mode MATCH needs at least 5 arguments total to
command.
CMake Error at CMakeLists.txt:367 (string):
string sub-command REGEX, mode MATCH needs at least 5 arguments total to
command.
CMake Error at CMakeLists.txt:365 (string):
string sub-command REGEX, mode MATCH needs at least 5 arguments total to
command.
CMake Error at CMakeLists.txt:367 (string):
string sub-command REGEX, mode MATCH needs at least 5 arguments total to
command.
CMake Error at CMakeLists.txt:365 (string):
string sub-command REGEX, mode MATCH needs at least 5 arguments total to
command.
CMake Error at CMakeLists.txt:367 (string):
string sub-command REGEX, mode MATCH needs at least 5 arguments total to
command.
-- Building for TensorRT version: .., library version:
-- Using MPI_C_INCLUDE_DIRS: /usr/lib/x86_64-linux-gnu/openmpi/include;/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi
-- Using MPI_C_LIBRARIES: /usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so
-- CMAKE_SYSTEM_PROCESSOR: x86_64
-- Operating System: ubuntu, 22.04
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'pybind11'
ERRORpybind11 CMake directory not found.
CMake Error at tensorrt_llm/pybind/CMakeLists.txt:25 (find_package):
By not providing "Findpybind11.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "pybind11",
but CMake did not find one.
Could not find a package configuration file provided by "pybind11" with any
of the following names:
pybind11Config.cmake
pybind11-config.cmake

Add the installation prefix of "pybind11" to CMAKE_PREFIX_PATH or set
"pybind11_DIR" to a directory containing one of the above files.  If
"pybind11" provides a separate development package or SDK, be sure it has
been installed.
-- Configuring incomplete, errors occurred!
Traceback (most recent call last):
File "/content/TensorRT-LLM/./scripts/build_wheel.py", line 306, in
main(**vars(args))
File "/content/TensorRT-LLM/./scripts/build_wheel.py", line 160, in main
build_run(
File "/usr/lib/python3.10/subprocess.py", line 526, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'cmake -DCMAKE_BUILD_TYPE="Release" -DBUILD_PYT="ON" -DBUILD_PYBIND="ON"  -DTRT_LIB_DIR=/usr/local/lib/python3.10/dist-packages/tensorrt_libs//targets/x86_64-linux-gnu/lib -DTRT_INCLUDE_DIR=/usr/local/lib/python3.10/dist-packages/tensorrt_libs//include  -S "/content/TensorRT-LLM/cpp"' returned non-zero exit status 1.

env:
Linux 9988c5cb9588 6.1.58+ #1 SMP PREEMPT_DYNAMIC Sat Nov 18 15:31:17 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.3 LTS
Release:	22.04
Codename:	jammy
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Tue_Aug_15_22:02:13_PDT_2023
Cuda compilation tools, release 12.2, V12.2.140
Build cuda_12.2.r12.2/compiler.33191640_0

use tensorrt 9.2.0
!pip install --no-cache-dir --extra-index-url https://pypi.nvidia.com tensorrt==9.2.0.post12.dev5

It is a dependent packages issues, we will try to help but we might not able to provide too many help.

i am using docker image but i am also facing the same issue duiring the above scripts to build.
/bin/bash: line 1: cmake: command not found
Traceback (most recent call last):
File "/app/TensorRT-LLM/./scripts/build_wheel.py", line 306, in
main(**vars(args))
File "/app/TensorRT-LLM/./scripts/build_wheel.py", line 160, in main
build_run(
File "/usr/lib/python3.10/subprocess.py", line 526, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'cmake -DCMAKE_BUILD_TYPE="Release" -DBUILD_PYT="ON" -DBUILD_PYBIND="OFF"  -DTRT_LIB_DIR=/usr/local/tensorrt/targets/x86_64-linux-gnu/lib -DTRT_INCLUDE_DIR=/usr/local/tensorrt/include  -S "/app/TensorRT-LLM/cpp"' returned non-zero exit status 127.

following exact steps from here
https://github.com/triton-inference-server/tensorrtllm_backend

Please share your scripts directly. There are many scripts in the document and we are not sure which do you follow.


Initial implementation of gfxrecon-capture.py and gfxrecon.py

Change-Id: Id83e3abe93f14dd91ee0847a7a7228e654238777

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.David Pinedo 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.


Glyphs layers which don't have an associated master should be ignored

Designers may use Glyphs "layers" for various purposes - backup, testing, etc. - this creates layers in the Glyphs sources which are not associated with a known master. It's totally fine for a Glyphs layer to have an layerId which is not the id of a known master. (These appear as regular, not bold, in the glyphs layers list.)
Currently fontc errors if a layer has no associated master:
[2024-07-23T19:26:07.320205Z ThreadId(1) fontc::workload ERROR] Fe(Glyph([redacted])) failed No master [also redacted] exists. Referenced by glyph [redacted].

okay, thanks for the explanation. I'm currently working through a bunch of glyphs compiler errors so will hope to get to this shortly.

just a little clarification, as I was initially confused by the title of this issue mentioning "layers which don't have an associated master". As you know, all Glyphs layers have both a layerId and an associatedMasterId attributes. For "master" layers (layers which directly correspond to a given font-wide master), the layerId == associatedMasterId, in which case the latter is omitted in the .glyphs file; other non-master layers have a layerId != associatedMasterId, the latter being the id of the font master that layer is indirectly associated with (they appear nested below it in the UI). In this sense, technically there are no layers without an associatedMasterId. New layers' name (initially the current timestamp) appears in regular, non-bold, font initially after they are first created, and always fall below some the currently selected master layer (the latter's layerId becomes their associatedMasterId); these layers can be used, as @simoncozens said, for backup or testing purposes, in which case can be simply ignored when compiling.
But as soon as they gain any additional attributes (as one right clicks on them) these non-master layers can become either intermediate layers or alternate layers or various colorful layers (or all of them at the same time), and should not be ignored but handled correctly. See https://github.com/googlefonts/fontc/issues/62#issuecomment-1354776035
I think we currently only support intermediate (aka "brace") layers, but not the alternate ("bracket") layers (https://github.com/googlefonts/fontc/issues/533), nor any of the colored ones.

I suggest to rename this "non-master Glyphs layers without attributes should be ignored"

Also I'd like to stress this, in case it wasn't clear, if a .glyphs source omits the associatedMasterId attribute, it is assumed that the latter defaults to its layerId (which is required non optional attribute); thus, only master layers (i.e. layers directly corresponding to a font master, and whose layerId is among the font master's set of ids) have no associatedMasterId explicitly set. If a .glyphs file contains a layer where the associatedMasterId is omitted and its layerId does not correspond to any of the font masters, or the associatedMasterId points to a font master which is not present, then the source is in a bad state and contains an invalid layer, I don't think it's possible to create such invalid layers from the font editor's UI, one would have to hack the .glyphs source text by hand. These invalid layers should produce an compile error, if it isn't the case already.

Can we get specific steps to reproduce (e.g. do x,y,z in glyphs) or a sample source with the problem? - when I quickly tried adding a scratch layer (not-bold in the ui) to a test font it didn't seem to leave me in a state that crashed fontc. The layer in question does have an associated master id and I wasn't immediately able to produce a file that didn't via the Glyphs UI.

by the way, glyphs-reader already skips "draft" layers here:
https://github.com/googlefonts/fontc/blob/3d7a5892cab7320d16292e74faf42a02904806d2/glyphs-reader/src/font.rs#L649-L656
https://github.com/googlefonts/fontc/blob/3d7a5892cab7320d16292e74faf42a02904806d2/glyphs-reader/src/font.rs#L1757-L1760

The layer in question does have an associated master id

yeah, as I said, all layers belong to some master, either by being themselves directly a master layer or by having their associatedMasterId point to one of the existing masters.

I still don't know what "without attributes" concretely means - what attributes? - or how to reproduce any specific problem?

Closing, please reopen or file a new bug if there is yet something that kerplodes us.


Add\Machine Learning option not working

System Information (please complete the following information):

Model Builder or CLI Version: ML 2022 model builder. DotNET - 8.0.100-preview.4.23260.5
Visual Studio Version (if applicable): Version 17.7.0 Preview 1.0

Describe the bug

On which page of the tutorial did you run into an issue (URL): Right click project "Add\Machine Learning" is not available
Clear description of the problem: For Visual Basic projects (WPF) "Add\Machine Learning" option does not appear

To Reproduce
Steps to reproduce the behavior:

Go to '...' Create a new WPF VB project targetting .NET 8.
Click on '....' Right click on project, Add\ "Machine Learning" does not appear

Expected behavior
A clear and concise description of what you expected to happen.
If this option does not appear for VB projects, is there any other way? Does it declare anywhere that .NET is owned only by C# and rest 150 programming languages are only marketing?
Additional context
Unable to use ML model builder in VS2022 in Visual Basic Projects.

@rrvenki Currently Model Builder only supports C#  based projects, however, you can consume your Model Builder-trained Model in any project type.
@luisquintanilla @LittleLittleCloud  have more thoughts ?


ci: Automate the process of generating the rukpak release manifests

Summary
Automate the process of generating and attaching the rukpak.yaml release manifests that reference the container image tags built by goreleaser.
Changes

Add the quickstart target that's responsible for building the set of kustomize manifests in this repository, and substituting the default quay.io/operator-framework/rukpak:latest container image tag with the current image tags.
Ensure the release GHA workflow now calls this quickstart Makefile target during tag event triggers
Update the goreleaser template configuration file, and add a extra_files field in the release pipeline that attaches the rukpak.yaml file as an artifact.
Ignore the generated rukpak.yaml release manifests locally.

Misc.

Closes #337
Related to #210
See https://github.com/timflannagan/rukpak/releases/tag/v0.3.1 for an example release that was created from these changes.

I'm going to test this out once more time in my fork.
/hold

/hold cancel


Update gemspec metadata with new urls

@pmor you should be able to merge this and release a new patch version on rubygems whenever. let me know if you run into any issues pushing the gem.

It's just "administratrivia" so I'll merge and it will get released whenever there's something new to release


fix(command-reference): Remove duplicated Arguments table

One table is enough.

Fixes: https://github.com/prisma/docs/pull/1965


Fix for #163

p.s. Since the PackRules command automatically does rule verification there is no need to support checking default rules as part of the VerifyRules command so I removed that leaving it focused on checking user custom rules only hence a could of the argument changes you may notice.  Also, the TagDiff and TagTest commands do not need to specify default args that are already set by default now so misc stuff but primary purpose is for #163

You should take a look at what we do in DevSkim to pack the rules as part of the build itself (see my note above).  That means you won't have to manually remember to pack them, and the pipeline and your machine will build them the same way.  Let me know if you need a hand with that.  @daalcant might also be able to help.  I highly recommend not relying on manually remembering to pack the rules before checking them in.

You should take a look at what we do in DevSkim to pack the rules as part of the build itself (see my note above). That means you won't have to manually remember to pack them, and the pipeline and your machine will build them the same way. Let me know if you need a hand with that. @daalcant might also be able to help. I highly recommend not relying on manually remembering to pack the rules before checking them in.

I'll give that another look -we'll achieve that to enhance.  I thought we might have a chicken before the egg but I'll review again.  I'll be in touch by early afternoon if stuck.

Alright dudes it works.  Thanks to @gfs for the suggested solution -very clever.  @daalcant let's do have your final review as well and call it done.

Hmm @daalcant seeing a new error on the checks -doesn't look related to my change.  Please assist.

Also exclude the .exe - its not necessary, you can dotnet run the dll directly.

Checking windows now.

I think its a pipeline issue at this point - that still stops us from merging though because we won't be able to publish. I can build and run this fine on both Windows and Mac now. @daalcant can you take a look?

I've got it fixed.  Standby.  New commit coming.

Repeat from above for my ending comment: Ok. I did get it working locally complete with \ and dll but I see you committed a change that is similar. I had also removed the unnecessary files including the defaultRules.json. Thanks! We'll go with the changes you made.  If we're still having pipeline issues, will allow @daalcant to review for nuget or other related issues.  Thanks.

Checking this out. I'll add a pipeline fix to this branch.

I believe it's just an issue with working directories. Will make some changes and test it out, should be an easy fix.

Scratch that, not a working dir issue.
I can sporadically get the same pipeline error on my local builds. I think this is a race condition that we also saw with DevSkim, where the rule packing step is being executed twice (once for the CLI, once for the library) and locking itself out when trying to write the rules file.

The CLI doesn't have a rules packing step in its csproj, it should only be being triggered on the lib though.

The CLI doesn't have a rules packing step in its csproj, it should only be being triggered on the lib though.

Correct, but the lib dependency causes it to run again.

Troubleshooting this to see if there's a better prebuild event to target, or if we can perhaps find a way to ensure the rule packing is only executed once.

Identified that this behavior only occurs when using the "publish" command from the solution directory. I can work around it easily in the pipeline, but going to see if there's a "better" way before falling back to that.

Ok.  If we have we can separate out the packing operation but is the model being used is the same as DevSkim which isn't exhibiting the issue?  Ping me for more immediate response if needed.  Thx.

Per Davids research we believe this could occur in DevSkim we just hadn't encountered this. We should have a fix/workaround until they fix what appears to be an issue in .NET Core

Potentially related issue is: https://github.com/dotnet/sdk/issues/3707
Workarounds via csproj targets don't seem to be successful, so I will modify the pipeline to publish from the CLI directory which prevents the duplicate pre-build event.

Nice that should fix it because the CLI is built last.

Looks like the pipeline fix was successful. I'm going to verify all of the produced artifacts to make sure I didn't overlook anything before we merge.

Nice.  I'll get the branch and perform local testing once more also before merge.

Thanks.  All tests have passed.


[Bug]: The first letter of file titles is occluded when using Sliding-Panes (Andy's Mode)

Bug Description
The first letter of file titles is occluded when using Sliding-Panes (Andy's Mode).
I have noted the settings for Sliding-Panes in the current documentation.
Can you add an option for the style settings plugin to get around this issue?
Thanks for an amazing theme!
Relevant Screenshot

To Reproduce
No response
Obsidian Version
0.13.19
Installer Version
0.12.19
Which editor are you using?

[X] New Editor
[ ] Legacy Editor

In which mode(s) does the problem occur? (if applicable)

[X] Source (Edit)
[X] Reading (Preview)
[X] Live Preview

Which operating system?

[ ] macOS
[ ] Linux
[X] Windows
[ ] iOS
[ ] Android

Plugin-Specific Problems

[X] I took note of the specific instructions regarding those plugins.

Checklist

[X] I updated to the latest version of the theme (Settings → Appearance → Themes - Manage → Update).
[X] I made sure that the issue is related to this theme, by checking that the problem does not occur with other themes or the default theme.
[X] In case I am missing an UI element, I have checked that it cannot be re-enabled with the Style Settings plugin.

thanks, haven't noticed, is fixed.

That was fast. Thank you!

well, it was literally one line of code that needed to be added, such small stuff is easy to do during coffee break 🙂


The demo is broken

The demo is broken http://tnightingale.github.io/Leaflet.widget/demo.html

Yes, if you input custom geoJSON is reverts to the default when clicking on submit query


Update grafana-tools/sdk to latest version

Waiting on https://github.com/grafana-tools/sdk/pull/151
Should resolve any straggling unmarshal errors. Tested on K8s mixin.

Hi @hjet! Which binary is this affecting?

hey @gotjosh!! my bad, requested a review by accident before this was ready to go 🙃
i will add more context when it's ready for review, but tldr for now is it affects both v0.10.1 and main:
cortextool analyse grafana errors out on any dashboard with templating or a defined panel height due to JSON unmarshalling errors. the main fixes are in https://github.com/grafana-tools/sdk
will add the failure case here before pinging for review

@gotjosh updated PR description, let me know if any questions


chore: remove types.ftl.go

I don't really think these should be checked in, a lot of the ones in the repo are out of date anyway.

This seems to have unexpected consequences for go mod tidy, as it seems like the types.ftl.go files in some cases are the only actual FTL dependencies in the source.


Microsoft.EntityFrameworkCore.RawSqlStringInjectionDiagnosticAnalyzer Warning

Just started getting a build warning after updating Visual Studio. Can this be disabled as it doesn't seem to affect anything that I can tell, app builds, deploys and runs in Azure without a problem so not sure why this is a warning except maybe for that package developer. CSC : warning AD0001: Analyzer 'Microsoft.EntityFrameworkCore.RawSqlStringInjectionDiagnosticAnalyzer' threw an exception of type 'System.NullReferenceException' with message 'Object reference not set to an instance of an object.'.
I am not using the RawSqlStringInjectionDiagnosticAnalyzer but it may be a dependency so without feedback I am hesitant to do anything besides leave the warning display annoyingly 30 times every build.
Cheers Peter

This issue was moved to aspnet/EntityFrameworkCore#13474


Add support for add_note() / __notes__

Problem Statement
Python 3.11 added support for notes:
async def f4():
    try:
        await f3()
    except TypeError as e:
        e.add_note('this failed while trying to blah')
        raise

(Source: https://blog.sentry.io/python-3-11-release-top-5-things-to-know/#adding-notes-to-exceptions)
I don't see them in sentry.
Solution Brainstorm
Check if an exception has a __notes__ property and add them to the "message" field.

Good idea! Seems like something we should look into supporting. We would also be happy to accept PRs for this!


CB-6028 Enable Solr Ranger Authorization.

This enables Ranger authorization for Solr from 7.2.0 -> 7.2.7.
See detailed description in the commit message.

Swagger issue will be tracked under: https://jira.cloudera.com/browse/CB-9896


[RFE] Ability to deploy AWS external tree provider in RKE2

This is a placeholder ticket for AWS external tree provider in RKE2.
The external AWS cloud provider (CCM) deploys onto a cluster and relies on the hostname and/or --provider-id flag (kubelet) to describe the node and initialise into the cluster.
With v2-provisioning, the hostname is always set to a node pool naming convention (OS (see userdata example below) & with -hostname-override), and there appears to be no way of providing the values dynamically to the -provider-id flag.
Here is an example gist to demonstrate a single-node cluster built directly - https://gist.github.com/dkeightley/26607d6739429a174675a81cd6fe65d6
Note the provider_id variable retrieves the AZ and instance ID from EC2 metadata.
Repro steps:
Create an RKE2 cluster using the external cloudprovider (terraform example might be the easiest option)
The hostname is overriden, auto-detection of the instance can't be completed (as above)
The provider-id flag can't be set appropriately via userdata
SURE-4760

https://github.com/rancher/rancher-docs/pull/826

https://github.com/rancher/rancher-docs/pull/844

testing this on 1.27.6+rke2r1 using aws node driver is no longer working. I originally tested on 2.8-head and 2.8.0-alpha1.
Currently, 1.26.8 is working fine, and I can see it is using the aws-cloud-controller resource when creating upstream resources, i.e. LBs
when trying to provision 1.27.6 with the same steps however, the cluster hangs during provisioning. The control plane nodes are stuck with status Waiting for probes: calico, kube-apiserver, kube-controller-manager, kube-scheduler, kubelet. I have tried to find meaningful logs on both the etcd and control plane nodes, as well as through the local cluster's logs, but did not find anything. I can provide a setup with this problem upon request.
here's a snippet of the changes to the cluster.yaml that were being applied

  rkeConfig:
    additionalManifest: |-
      apiVersion: helm.cattle.io/v1
      kind: HelmChart
      metadata:
        name: aws-cloud-controller-manager
        namespace: kube-system
      spec:
        chart: aws-cloud-controller-manager
        repo: https://kubernetes.github.io/cloud-provider-aws
        targetNamespace: kube-system
        bootstrap: true
        valuesContent: |-
          hostNetworking: true
          nodeSelector:
            node-role.kubernetes.io/control-plane: "true"
          args:
            - --configure-cloud-routes=false
            - --v=5
            - --cloud-provider=aws
...
    machineGlobalConfig:
      cloud-provider-name: aws
...
machineSelectorConfig:
      - config:
          kubelet-arg:
            - cloud-provider=external
        machineLabelSelector:
          matchLabels:
            rke.cattle.io/etcd-role: 'true'
      - config:
          disable-cloud-controller: true
          kube-controller-manager-arg:
            - cloud-provider=external
          kubeapi-server-arg:
            - cloud-provider=external
        machineLabelSelector:
          matchLabels:
            rke.cattle.io/control-plane-role: 'true'
      - config:
          disable-cloud-controller: true
          kubelet-arg:
            - cloud-provider=external
        machineLabelSelector:
          matchLabels:
            rke.cattle.io/worker-role: 'true'
      - config:
          cloud-provider-name: aws
          protect-kernel-defaults: false
...

@slickwarren I looked into the issue and the issue is kubelet-arg is missing for control plane role nodes. I think this isn't a problem for 1.26 clusters because the default value aws still works but fails for 1.27 with kubelet crashing with invalid cloud provider value.
Also since config under machineSelectorConfig without selectors is the same as machineGlobalConfig, we don't need both of them.
Config below worked for v1.27.6+rke2r1 on v2.8-head:
  rkeConfig:
    additionalManifest: |-
      apiVersion: helm.cattle.io/v1
      kind: HelmChart
      metadata:
        name: aws-cloud-controller-manager
        namespace: kube-system
      spec:
        chart: aws-cloud-controller-manager
        repo: https://kubernetes.github.io/cloud-provider-aws
        targetNamespace: kube-system
        bootstrap: true
        valuesContent: |-
          hostNetworking: true
          nodeSelector:
            node-role.kubernetes.io/control-plane: "true"
          args:
            - --configure-cloud-routes=false
            - --v=5
            - --cloud-provider=aws
    machineSelectorConfig:
      - config:
          kubelet-arg:
            - cloud-provider=external
        machineLabelSelector:
          matchLabels:
            rke.cattle.io/etcd-role: 'true'
      - config:
          disable-cloud-controller: true
          kube-controller-manager-arg:
            - cloud-provider=external
          kubeapi-server-arg:
            - cloud-provider=external
          kubelet-arg:
            - cloud-provider=external
        machineLabelSelector:
          matchLabels:
            rke.cattle.io/control-plane-role: 'true'
      - config:
          disable-cloud-controller: true
          kubelet-arg:
            - cloud-provider=external
        machineLabelSelector:
          matchLabels:
            rke.cattle.io/worker-role: 'true'
      - config:
          cloud-provider-name: aws
          protect-kernel-defaults: false

there have been multiple reviews of the documentation to update based on all of the testing done - Should I reopen this ticket on behalf of the documentation, or will that be covered in the docs PR?

QA has given feedback in the documentation PR; assuming that is addressed, QA signs off on aws external provider deployment for rke1 and rke2.

https://github.com/rancher/rancher-docs/pull/844 is in good shape to follow up with testing. Sending "To Test" now.

We can close this issue now that the docs have been validated.


Data received from certain source application (collectd) not display >24 hours of data

I have come across an issue with my Graphite deployment. First of all, versions:
carbon           0.9.15
Django           1.7.11
django-tagging   0.4.5
graphite-web     0.9.15
whisper          0.9.15

The issue I'm seeing is that the Graphite-web dashboard will not display any data on graphs set to greater than 24 hours. This issue is independent of which host the data comes from. With that said, it does seem to only impact the graphing of Whipser files containing data sent from a collectd source. Whisper files created from netdata data, and all of those files seem to graph without issue regardless of how the graphs are zoomed.
At first, I suspected that it was due to a typo or misconfigured pattern or retention in my storage-schemas.conf. In response, I modified the collectd pattern and default pattern to mirror the netdata pattern (that functions as expected). File below:
# Carbon's internal metrics. This entry should match what is specified in
# CARBON_METRIC_PREFIX and CARBON_METRIC_INTERVAL settings

[collectd]
pattern = ^collectd\.
retentions = 10s:1d,1m:7d,10m:1y

[netdata]
pattern = ^netdata.*
retentions = 10s:1d,1m:7d,10m:1y

[default_1min_for_1day]
pattern = .*
retentions = 10s:1d,1m:7d,10m:1y

I then removed the collectd Whisper files and let them get re-created. I confirmed via whisper-info that they now showed the retention details that I expected.
~> whisper-info /var/lib/graphite/whisper/collectd/sunjian/interface-eth0/if_packets/rx.wsp
maxRetention: 31536000
xFilesFactor: 0.5
aggregationMethod: average
fileSize: 855412

Archive 0
retention: 86400
secondsPerPoint: 10
points: 8640
size: 103680
offset: 52

Archive 1
retention: 604800
secondsPerPoint: 60
points: 10080
size: 120960
offset: 103732

Archive 2
retention: 31536000
secondsPerPoint: 600
points: 52560
size: 630720
offset: 224692

Still, the graphs are completely empty when you zoom out to a greater span that 24 hours.
24 hours:

48 hours:

Chrome network inspect output from both:

Is there anything else obvious I should be looking for when troubleshooting this? I Googled a bit, but kept finding answers related to modifying the storage-schemas.conf file.
Any input is appreciated!

Are you sure that your collectd metrics are being emitted every 10s? For example, if they're only being emitted every 60s, they would not fulfill your xFilesFactor ratio and hence be rolled up to nulls in the second archive.
I explain it a bit more in this blog post.

@obfuscurity thanks for the info! I'll give that blog post a read and probably modify that ratio for the collectd data. I'll close the issue if that ends up resolving it.

@obfuscurity Looks like this was indeed my problem. Guess I need to RTFM a little more carefully next time. Thank you!

Glad to hear it, no problem! :heart: