Documentation for ValidateScopes and ValidateOnBuild in minimal apis

Hi,
I can't find any documentation that says ValidateScopes and ValidateOnBuild  are enabled by default in the Development mode in minimal APIs and WebApplicationBuilder. I think this doc should be enhanced for clarifying ValidateScopes and ValidateOnBuild  for both minimal and none-minimal api host builders
for example:

CreateDefaultBuilder and WebApplicationBuilder in minimal apis sets ServiceProviderOptions.ValidateScopes and ServiceProviderOptions.ValidateOnBuild to true if the app's environment is Development.

EDIT by @Rick-Anderson add the folllowing meta-data
Page URL
https://learn.microsoft.com/en-us/aspnet/core/fundamentals/minimal-apis?view=aspnetcore-8.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/fundamentals/minimal-apis.md
Document ID
b09824ab-b051-75a1-13b7-b0e281cc46e0
Article author
Rick-Anderson

Associated WorkItem - 177294

@thomaslevesque  @mehdihadeli  That's not the results I'm getting from the following code:
var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();

if (app.Environment.IsDevelopment())
    Console.WriteLine("Development environment");
else
    Console.WriteLine("Release environment");

builder.Host.UseDefaultServiceProvider(options =>
{
    Console.WriteLine($"ValidateScopes = {options.ValidateScopes}");
    Console.WriteLine($"ValidateOnBuild = {options.ValidateOnBuild}");
});

app.MapGet("/", () => "Hello World!");

app.Run();

// OUPUT:
//Development environment
//ValidateScopes = False
//ValidateOnBuild = False

Uh. I was pretty sure ValidateScopes was enabled in Development. Maybe it has changed at some point?

@captainsafia  I'm closing this issue because it's not true. See the following code
var builder = WebApplication.CreateBuilder(args);
var app = builder.Build();

if (app.Environment.IsDevelopment())
    Console.WriteLine("Development environment");
else
    Console.WriteLine("Release environment");

builder.Host.UseDefaultServiceProvider(options =>
{
    Console.WriteLine($"ValidateScopes = {options.ValidateScopes}");
    Console.WriteLine($"ValidateOnBuild = {options.ValidateOnBuild}");
});

app.MapGet("/", () => "Hello World!");

app.Run();

// OUPUT:
//Development environment
//ValidateScopes = False
//ValidateOnBuild = False

On further examination, the following code doesn't write the correct state:
builder.Host.UseDefaultServiceProvider(options =>
{
    Console.WriteLine($"ValidateScopes = {options.ValidateScopes}");
    Console.WriteLine($"ValidateOnBuild = {options.ValidateOnBuild}");
});

The following code throws in development but not release mode:
var builder = WebApplication.CreateBuilder(args);

builder.Services.AddScoped<MyScopedService>();

var app = builder.Build();

if (app.Environment.IsDevelopment())
{
    Console.WriteLine("Development environment");
}
else
{
    Console.WriteLine("Release environment");
}

app.MapGet("/", context =>
{
    // Intentionally getting service provider from app, not from the request
    // This causes an exception from attempting to resolve a scoped service
    // outside of a scope.
    var service = app.Services.GetRequiredService<MyScopedService>();
    return context.Response.WriteAsync( "Service resolved");
});

app.Run();

public class MyScopedService { }

@thomaslevesque  @mehdihadeli  see https://github.com/dotnet/AspNetCore.Docs.Samples/pull/237 which provides sample code to demonstrate this issue.


Encoding a physical description outside the FRBR module not possible

Various refactoring steps since MEI 3.0 have made it not possible to use <physDesc> outside the FRBR module. This is problematic for cases where the metadata is about a single source and where providing some metadata about the physical description is desirable. In MEI 3.0, it was possible to do
<source>
   <titleStmt>
      <title>Soprani</title>
   </titleStmt>
   <physDesc>
      <!-- ... -->
   </physDesc>
</source>

and I think this is still desirable.
Furthermore, <physDesc> is part of the header module, and it seems awkward that it cannot be used without FRBR. See a related discussion here
I would suggest to investigate a possible fix by allowing (back) <physDesc> within <source> but I have not evaluated the consequences of this. Any thoughts?

Pinging @music-encoding/ig-metadata

The header and frbr modules in MEI should be independent, but the issue is that there is currently no way to use parts of header without frbr. <physDesc> can't be used without going through <item>, as it is the only valid parent element.
So I think the intent of this change is to simply make them independent again.
Good point about <source> being for secondary literature... We'll have to check that out.

As for why: I have my own, personal, and largely negative views of FRBR. I think we should still provide FRBR functionality within MEI, but I also think there should be alternatives for those who do not want to do so. There will be no changes to the FRBR output so those who wish to do so can still do it, but fixing this will also let those who do not want to use FRBR to do that too.
(I could write several pages of why I think FRBR is very bad, but I will save you all from this... Let's just say I used to be a fan, but now think it's actively malicious for most cataloguing purposes.)

Yes, some header element are only available in elements from the frbr module. I also think that it should be possible to make them more independent. We'll have to evaluate on this, because I think there is more to do that just add physDesc to another element. Thanks for bringing this up!

@doerners I had a look at <source>

My perception was that  points to secondary literature rather than e.g. a manuscript (maybe I'm mistaken here).

In this instance I think that the "bibliographic description" is referring to the original source that was used to create an electronic copy. So it would be acceptable to reference the book (with all its bibliographic and/or physical descriptions) that a particular musical piece was taken from.
This is how it is used in some of the Sample Encodings.

If the encoder does'nt want to use the FRBR module (for whatever reason this might be) this could have a negative effect on data interoperability. Especially since the introduction of RDA my perception was that the FRBR concepts are essential in cataloguing practice (at least for larger GLAM institutions) and it would probably be very hard to exchange data with e.g. libraries.

Possibly. One could also argue that not using FBRB where this is not clearly necessary of where the model is not really appropriate - by being maybve either too simple or too complicated – then you would increase interoperability with other encodings, such as TEI for example. It would not be a one to one mapping but it would have a much more similar structure. There are many cases where, for good reasons, MEI follows a similar but not identical approach to TEI, and that would be another one.

Thanks @ahankinson and @lpugin for the helpful comments and of course for bringing this up. @riedde and me had a quick chat about this issue yesterday and our conclusion was that this seems to be a larger/more complicated issue we should discuss further. We will bring it up during the next ig meeting and if you (@ahankinson, @lpugin) find the time to join us we think this could really help the discussion. The meeting will take place on Wed, 1.3., 15h (UTC +1).

I'd like to propose adding a new member to the biblLike class, the members of which are allowed in <source>.  The<biblFull> element's content model will allow a mixture of data hitherto allowed only by the FRBR module.  That is, it will contain a mixture of work-, expression-, and manifestation-level info.
This addition will fix this issue.  Also, since <biblFull> will allow physical description of a manifestation, #1122 can be closed as well.
PR to follow soon.


icon can't set in my windows app

flet pack is OK  ,  set the app icon ,  on windows app
but  I use cx_Freeze  to pack my app  ,  the app icon is can't set
window title icon
window task bar icon
Hope to add icon setting properties as soon as possible

This is actually not a Flet issue. Search on how that is done in cxFreeze...


cyan is not defined in Github Dark Legacy and Github Light Legacy color schemes

Describe the bug
Unable to parse color value var(cyan) at Packages/GitHub Theme/schemes/GitHub Dark Legacy.sublime-color-scheme:34:32
Unable to parse color value var(cyan) at Packages/GitHub Theme/schemes/GitHub Dark Legacy.sublime-color-scheme:59:28
Unable to parse color value var(cyan) at Packages/GitHub Theme/schemes/GitHub Light Legacy.sublime-color-scheme:34:32
Unable to parse color value var(cyan) at Packages/GitHub Theme/schemes/GitHub Light Legacy.sublime-color-scheme:59:28

Thanks @AmjadHD I will fix it ASAP.


Cannot apply lemma involving type class

I'm not totally sure what's happening here and unfortunately I haven't been able to figure out how to narrow this down to a minimal example so far.
I have a rule for a certain monad homomorphism:
{-# RULES "liftR-hom" [~]
      forall x f.
        liftR x >>= (liftR . f)
          =
        liftR (x >>= f)
  #-}

and I can transform a certain piece of code into:
(>>=) ▲ $dMonad ▲ ▲ (liftR ▲ (buttonE (I# 0)))
      ((.) ▲ ▲ ▲ (liftR ▲)
           (λ r →
              (>>) ▲ $fMonadR' ▲ ▲ (ledE (I# 0) r) (ledE (I# 1) (notB r))))

(everything before this line performs this transformation)
This looks like it fits the RULE to me, but I can't use lemmaForward "liftR-hom" (or more generally, anyBU $ lemmaForward "liftR-hom").
I think I ran into the same problem earlier with RULES regarding the left monad identity and monad associativity laws. I ended up working around it so I didn't need those transformations, but I'm pretty sure I really need this one.
It seems like it might have something to do with the type quantifiers or the type class dictionaries, but providing explicit types in the RULE doesn't seem to help.
Just in case, I also tried introducing lets for the lambda and for the application of buttonE to make it look even more like the RULE (in fact, it looked pretty much identical to it at that point), but that didn't lead anywhere.

If I recall from Drew's dissertation presentation, you have to specialize the rule to the particular type you are working with.
See the use of inst-lemma from his defense slides here:
http://www.ittc.ku.edu/~afarmer/talks/defense.html#(23)
An entire proof of the left identity law for the list monad is shown on http://www.ittc.ku.edu/~afarmer/talks/defense.html#(27), hopefully that helps too.

@ecaustin It looks like it is already instantiated to the specific Monad (there is no m :: * -> * to instantiate):
HERMIT> eval "set-pp-type Detailed"
<...>

HERMIT> eval "show-lemma liftR-hom"
liftR-hom (Not Proven)
  ∀ (b ∷ *)
    (a ∷ *)
    ($dMonad ∷ Monad (StateT ([Bool], [Bool])
                             (ReaderT DeviceContext IO)))
    (x ∷ R' a)
    (f ∷ a → R' b).
  (>>=) (StateT ([Bool], [Bool]) (ReaderT DeviceContext IO)) $dMonad
        a b (liftR a x)
        ((.) (R' b) (StateT ([Bool], [Bool]) (ReaderT DeviceContext IO) b)
             a (liftR b) f)
  ≡
  liftR b ((>>=) R' $fMonadR' a b x f)
[Done]

Also, I was able to use the >> version of that lemma (liftR-hom_) successfully. I'm probably using the liftR-hom in a different way somehow, but I'm not sure which difference is the difference that's causing the problem.

Can you set-pp-type Detailed and show both the target code and the rule?

@xich Sorry for the late reply! Here's what it looks like:
HERMIT> display
(>>=) R $fMonadR Bool ()
      ((>>=) R $fMonadR (E Bool) Bool (buttonE (I# 0))
             (λ (x ∷ E Bool) → return R $fMonadR Bool (unLit x)))
      (λ (b ∷ Bool) →
         (>>) R $fMonadR () () (ledE (I# 0) (lit b))
              ((>>) R $fMonadR () () (ledE (I# 1) (lit (not b)))
                    (wait (I# 100))))
[Done]

HERMIT> lemmaForward ">>=-assoc"
*** Exception: server failure: Object (fromList [("exception",String "Rewrite failed:expression did not match left-hand side")]) : Rewrite failed:expression did not match left-hand side
HERMIT> eval "show-lemma \">>=-assoc\""
>>=-assoc (Assumed)
  ∀ (m ∷ * → *)
    (b ∷ *)
    (a ∷ *)
    (a ∷ *)
    ($dMonad ∷ Monad m)
    (m ∷ m a)
    (f ∷ a → m a)
    (g ∷ a → m b).
  (>>=) m $dMonad a b ((>>=) m $dMonad a a m f) g
  ≡
  (>>=) m $dMonad a b m (λ (e ∷ a) → (>>=) m $dMonad a b (f e) g)
[Done]

The code is here (the immediately relevant files are src/Main.hs and src/MainScript.hs): https://github.com/roboguy13/sunken/tree/2667c7000613edb7f9089606e752a871be15dd4b

Hmmm, that does look right... can you unshadow the lemma (to distinguish the a's) just to make sure?
I guess I'll start improving the error messages until I can figure out why.

I might not understand how to unshadow it. I keep getting errors:
hermit<0> set-pp-type Detailed
module Main where
  unLit ∷ E Bool → Bool
  main ∷ IO ()
  main ∷ IO ()
hermit<0> rule-to-lemma ">>=-assoc"
>>=-assoc (Not Proven)
  ∀ (m ∷ * → *) (b ∷ *) (a ∷ *) (a ∷ *) ($dMonad ∷ Monad m) (m ∷ m a) (f ∷ a → m a) (g ∷ a → m b).
  (>>=) m $dMonad a b ((>>=) m $dMonad a a m f) g
  ≡
  (>>=) m $dMonad a b m (λ (e ∷ a) → (>>=) m $dMonad a b (f e) g)
hermit<1> prove-lemma ">>=-assoc"
Goal:
  ∀ (m ∷ * → *) (b ∷ *) (a ∷ *) (a ∷ *) ($dMonad ∷ Monad m) (m ∷ m a) (f ∷ a → m a) (g ∷ a → m b).
  (>>=) m $dMonad a b ((>>=) m $dMonad a a m f) g
  ≡
  (>>=) m $dMonad a b m (λ (e ∷ a) → (>>=) m $dMonad a b (f e) g)
proof<2> lhs unshadow
Error in expression: lhs unshadow
catchesM failed
proof<2> rhs unshadow
Error in expression: rhs unshadow
catchesM failed
proof<2> unshadow
Error in expression: unshadow
This rewrite can only succeed at core nodes.

Ahh, thanks. Here's what that looks like:
proof<2> unshadow-quantified
Goal:
  ∀ (m ∷ * → *) (b ∷ *) (a ∷ *) (a0 ∷ *) ($dMonad ∷ Monad m) (m0 ∷ m a) (f ∷ a → m a0) (g ∷ a0 → m b).
  (>>=) m $dMonad a0 b ((>>=) m $dMonad a a0 m0 f) g
  ≡
  (>>=) m $dMonad a b m0 (λ (e ∷ a) → (>>=) m $dMonad a0 b (f e) g)

Well, I've been trying to trace the Equality list in birewrite, but that's proving harder than I thought it would be. I found ppEqualityT, but it looks like it ultimately needs to be in HermitM.

Some debugging tips:

All the monadic layers involved should have liftIO instances, so liftIO $ print ... is your friend.
A lot of things can be turned into strings with showPpr. The DynFlags argument can be gotten from getDynFlags in most places.
This particular problem is most likely to do with runFoldMatches and filterOutOfScope here:
https://github.com/ku-fpg/hermit/blob/master/src/HERMIT/Dictionary/Fold.hs#L123

@xich Thanks! I'll take a look at those later. I found that if I monomorphize the RULE, it works fine. Maybe I need to monomorphize it in HERMIT somehow (I think I tried instDictionaries a week or two ago, and it didn't seem to work)?
This is what I ended up with:
{-# RULES ">>=-assoc" [~]
      forall (m :: R a) (f :: a -> R b) (g :: b -> R c).
        (m >>= f) >>= g
          =
        m >>= (\e -> f e >>= g)
  #-}

Glad there is a workaround, but there is no fundamental reason that the more general rule shouldn't work... I suspect there is an interesting thing going on with the dictionary binders, but haven't had a chance to sit down and debug it.

@xich Unfortunately, the functions I've been looking at so far (runFoldMatches and filterOutOfScope) don't seem to have a way to get at a DynFlags value. I see that there is a unsafeGlobalDynFlags :: DynFlags, but that doesn't sound very safe...
Also, it looks like neither CoreExpr and Equality are Outputable.
I might be going in the wrong direction with this altogether, though

Ah yes, those functions are pure... so trace is your friend (I believe HERMIT.GHC exports it, or you can use the one from Debug.Trace).
That is weird about Outputable... CoreExpr definitely was in versions prior to 7.10. Makes me wonder how this is compiling: https://github.com/ku-fpg/hermit/blob/master/src/HERMIT/PrettyPrinter/GHC.hs
Feel free to add a DynFlags argument to those functions while you debug.


Button text shouldn't be uppercase

Button text shouldn't be uppercase (at least by default)
https://daisyui.com/components/button/

Google (Chrome, web), Amazon, Microsoft (Windows, web), GitHub, Apple (iOS, macOS, web), Android, Facebook, KDE/Qt, GNOME... don't do that
Other web UI libs don't do that: Bootstrap, Mantine, MUI BaseUI, Spectrum, Chakra, Ant Design, PrimeReact, Grommet, Bulma, standard HTML...

Without uppercase (padding should be reduced btw):

Also this makes btn-link inconsistent with link:

vs

Other web UI libs don't do that: Bootstrap, Mantine, MUI BaseUI, Spectrum, Chakra, Ant Design, PrimeReact, Grommet, Bulma, standard HTML...

Material design has uppercase button text by default: https://m2.material.io/components/buttons
So does Material UI: https://mui.com/material-ui/react-button/
It's not uppercase in daisyUI by default.
It is uppercase in daisyUI's built-in themes.
But you don't have to use the built-in themes. You can customize them or you can make your own theme and use "--btn-text-case": "none" CSS variable if you don't want uppercase text:
// tailwind.config.js
module.exports = {
  plugins: [require('daisyui')],

  daisyui: {
    themes: [
      {
        light: {
          ...require("daisyui/src/theming/themes")["[data-theme=light]"],
          "--btn-text-case": "none",
        },
      },
    ],
  },
}

Material design has uppercase button text by default

Material Design dropped uppercase buttons: https://m3.material.io/components/all-buttons
As for MUI it is based on old Material Design v2 guidelines: new v6 will be based on Material Design v3 guidelines.
Also by the same team, BaseUI and JoyUI don't have uppercase buttons.

I didn't know that.
However I don't see any reasons to drop the uppercase for the built-in default theme.
Some people prefer uppercase, some don't.
Changing this variable for the built-in themes affects all the websites made by daisyUI that use the default themes and this decision is not going to be in favor of for the people who prefer uppercase by default.
It's easy to change the CSS variable if you don't like the uppercase

Defaults should be carefully considered: they should embody the best practices (mainly accessibility here) and not the author's personal preferences.
This is what makes the difference between a good and an excellent product.
It's not a question of "easy to change if you don't like uppercase".

Beside uppercase buttons, borderless inputs by default is also bad.

https://coyleandrew.medium.com/form-design-best-practices-9525c321d759#5759
Others don't do that: Bootstrap, Mantine, MUI BaseUI, MUI JoyUI, Spectrum, Chakra, Ant Design, PrimeReact, Bulma, standard HTML, Qt/KDE, GNOME/GTK+, Apple, Microsoft...

When there is a consensus you need strong reasons not to follow them.

I think I should make something clear here.
daisyUI is the library that provides the ability to make your own theme by defining colors (and other variables)
The built-in default themes only exist as a starting point to see how each component would look like with different colors and styles. I even made a theme generator page to encourage developers to make their own theme with custom colors and styles.
The uppercase text was not a random decision. It was already being used in Material design (used in various Google products and almost every Android)
The advantage of uppercase is gaining more attention for the buttons and makes it more obvious that it's an ACTION BUTTON. It is loud but I don't see any downside.
If there's a downside of having uppercase text for buttons, please let me know.
About inputs, it's important to make it obvious. It can be using borders or other design decisions. The article you mentioned is about forms. There are other ways to make an input obvious for example an icon, a placeholder text and a search button would make it obvious where is a search input. Design best practices are not absolute.

The article you mentioned is about forms [...] Design best practices are not absolute

Don't miss the part where Google discover after a 4 months study and over 600 participants that fields should have a "rectangular (box) shape"

This is DaisyUI default field:

And users thinking "it's the default way so it must be the best way!"
Don't get me wrong: I love DaisyUI, its approach and the great work you put in it. I just think it could be better thx to sensible defaults.

And users thinking "it's the default way so it must be the best way!"

That wouldn't be a correct. The default is the bare minimum style of a component which can be modifier with modifier class names or Tailwind's utility classes.
It makes more sense if the default is without border and we use a modifier class name to add something (border) to it, that using a modifier class name to remove something from it.

If there's a downside of having uppercase text for buttons, please let me know

https://material.angular.io/components/button/overview#capitalization
"[capitalizing] buttons [...] can cause issues in certain locales. [Also] using ALL CAPS in the text itself causes issues for screen-readers, which will read the text character-by-character"

when they say "According to the Material design spec" they are referring to the old spec - v2 instead of v3

I need more info

Couldn't find any details
Found this interesting comment that recaps all issues with ALL CAPS:
https://github.com/humanmade/hm-pattern-library/issues/75#issuecomment-235672885
Found this in Angular Material repo (nothing new :-/):

https://github.com/angular/components/issues/4821 (https://github.com/angular/components/pull/4829)
https://github.com/angular/components/issues/4496
https://github.com/angular/components/pull/4567

It makes more sense if the default is without border and we use a modifier class name to add something (border)

From a technical point of vue, yes it feels satisfying and clean. However not from the user (accessibility) point of vue given the Google study.
So I would do this opposite (even if it's better from a technical point of vue to avoid negation):
<input class="input" /> // Bordered by default
<input class="input-borderless" />

<textarea class="textarea"></textarea> // Bordered by default
<textarea class="textarea-borderless"></textarea>

<select class="select"></select> // Bordered by default
<select class="select-borderless"></select>


[SPARK-50421]Fix executor related memory config incorrect when multiple resource profile worked

What changes were proposed in this pull request?
Reset the executor's env memory related config when resource profile is not as the default resource profile!
Why are the changes needed?
When multiple resource profile exists in the same spark application, now the executor's memory related config is not override by resource profile's memory size, which will cause maxOffHeap in UnifiedMemoryManager is not correct.
See https://issues.apache.org/jira/browse/SPARK-50421 for more details
Does this PR introduce any user-facing change?
No
How was this patch tested?
To be added
Was this patch authored or co-authored using generative AI tooling?
No

@tgravescs Would you help to review this commit?

@tgravescs I just updated the commit as the comments. Please help review when you have free time.

what all testing have you done with this?  It would be nice to have a integration test with it but I know this would be difficult.

what all testing have you done with this? It would be nice to have a integration test with it but I know this would be difficult.

I have test this in our inner spark version and UnifiedMemoryManager worked as expected. I just tried to add a integration test but found it's hard since there no easy way to mock driver and executor to test the code.

+1 looks fine to me.

Thanks! Would you help merge it?
I think this also should be included in spark 3.5.4

Due to the Structured Log change, this patch is not applicable to branch-3.5.
Please make a backporting PR to branch-3.5, @zjuwangg .

BTW, I added you to Apache Spark Contributor group in JIRA and assigned SPARK-50421 to you, @zjuwangg .
Welcome to the Apache Spark community and thank you again.

Due to the Structured Log change, this patch is not applicable to branch-3.5.
Please make a backporting PR to branch-3.5, @zjuwangg .

I'll make a backporting PR to branch-3.5 soon.

Due to the Structured Log change, this patch is not applicable to branch-3.5.
Please make a backporting PR to branch-3.5, @zjuwangg .

I'll make a backporting PR to branch-3.5 soon.

Backporting PR: https://github.com/apache/spark/pull/49090


Update enshrined/svg-sanitize to 0.14.0.

Summary
Now that 0.14.0 is released and PRs we need patches for were merged https://github.com/darylldoyle/svg-sanitizer/pull/45 and https://github.com/darylldoyle/svg-sanitizer/pull/42.
Background: https://twitter.com/enshrined/status/1352199027702583300?s=21
Relevant Technical Choices

To-do

User-facing changes

Testing Instructions

Fixes #

Hmm looks like it needs another composer update enshrined/svg-sanitize, otherwise composer's complaining

Hmm looks like it needs another composer update enshrined/svg-sanitize, otherwise composer's complaining


openai migrate fails to translate multiple except blocks with old openai.error objects

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

[X] This is an issue with the Python library

Describe the bug
I am running openai migrate on a codebase written for 0.28.1, and it doesn't correctly process a try/except with multiple except blocks.  E.g.
try:
   [calling the completions API]
except openai.error.RateLimitError as e:
   [handle it]
except openai.error.AuthenticationError as e:
   [handle it]
[other except blocks with other openai.error.* types...]

The migrate command translates just the first except block to use the newer class (openai.RateLimitError, e.g.) and ignores the later ones.
Each time I re-run openai migrate it translates one more except block, so that is a simple workaround.
To Reproduce

Write a simple test case like the above code.
Run openai migrate
See it translates only one except block.

Code snippets
No response
OS
Linux
Python version
Python v3.10.12
Library version
openai v1.12.0

Thanks for the report!
Cc @morgante

Fix should be out shortly: https://github.com/getgrit/stdlib/pull/114

Thanks for reporting @liffiton and for fixing @morgante !


Add .github and .firebaserc to .npmignore

In this Pull Request
Added the folder .github ant the .firebaserc to th npmignore file to avoid to publish in the npm package.

Btw, I'm thinking that the folder src is not used to import the tokens, so really it is not necessary either

Btw, I'm thinking that the folder src and the file postcss.config.js are not used to import the props, so really it are not necessary either

postcss.config.js could be removed yeah, but src/ should stay so folks can unpkg reference src files if they want


fix: resolve symlinks in d.ts imports

I have tried to implement realPath conditionally where it is used.
However, I realized that it is ultimately up to rollup-plugin-dts, which uses ts.sys but does not implement realpathSync, to fix the problem.
So we should set preserveSymlinks: false as default.
I have written a test which mimics pnpm symlinks and fails without preserveSymlinks: false.
Closes #69

@privatenumber anything holding back?

Thanks for your contribution @jrson83 Hope we collaborate again in the future!

:tada: This issue has been resolved in version 2.4.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Refactor S3Bucket block

Update S3Bucket to make it compliant with ObjectStorageBlock, and refactor a lot along the way, like making AwsClientParameters modifyable on the UI and merging MinIOCredentials into aws_credentials field.
Closes a bunch
https://github.com/PrefectHQ/prefect-aws/issues/149
https://github.com/PrefectHQ/prefect-aws/issues/150
https://github.com/PrefectHQ/prefect-aws/issues/146
https://github.com/PrefectHQ/prefect-aws/issues/162
https://github.com/PrefectHQ/prefect-aws/issues/124
Example

See readme
Screenshots

Checklist

[x] References any related issue by including "Closes #" or "Closes ".

If no issue exists and your change is not a small fix, please create an issue first.

[x] Includes tests or only affects documentation.
[x] Passes pre-commit checks.

Run pre-commit install && pre-commit run --all locally for formatting and linting.

[x] Includes screenshots of documentation updates.

Run mkdocs serve view documentation locally.

[x] Summarizes PR's changes in CHANGELOG.md


[release/hotfix] backmerge - release/4.0.0-beta-33.0.3

Se cambia el discount id por el campaign id al ir a buscar los Términos y condiciones de la campaña.

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@042d5de). Click here to learn what that means.
The diff coverage is 0%.

@@            Coverage Diff             @@
##             develop    #1113   +/-   ##
==========================================
  Coverage           ?   29.25%
==========================================
  Files              ?      326
  Lines              ?    14688
  Branches           ?     1337
==========================================
  Hits               ?     4297
  Misses             ?     9884
  Partials           ?      507

Impacted Files
Coverage Δ

...mercadopago/onetap/components/OneTapContainer.java
0% <0%> (ø)

...go/review_and_confirm/ReviewAndConfirmBuilder.java
0% <0%> (ø)

...rc/main/java/com/mercadopago/CheckoutActivity.java
0% <0%> (ø)

Continue to review full report at Codecov.

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


Added new boxed variables for partPaymentAllowed and overPaymentAllowed

Hey @mattsegers, I've add the JsonAlias tag to partPayment and overPayment so if the JSON contains either partPaymentAllowed or partPayment, they will be deserialised to partPayment (same for over payment)


[BUG] Hidden components throw error

Environment
Please provide as many details as you can:

Hosting type

[] Form.io
[x ] Local deployment

Version:

Formio.js version: 4.10.0-rc.4
angular-material-formio version: 1.26.0
Frontend framework: Angular9
Browser: Firefox
Browser version:

Steps to Reproduce

Create wizzard and in a page create a hiddenComponent from SpecialComponents

Expected behavior
Hidden component should not be showed
Observed behavior
When page showed the next error is showed in browser console:
Input type "hidden" isn't supported by matInput.
When using wizzard can't go to next pages

@osantos1910 Thanks for reaching out! Can you please provide a JSfiddle of this issue occurring on your side?
Thank you.


Add an imported_at (or similar) column to most/all data tables

Often we want to know when a row was imported into a table to understand how up-to-date the data is, without looking at the sync log.

Do we have knowledge  of which tables   this change is not needed ?
also now that this  is  only a migration  , we could tackle this together with https://github.com/mergestat/fuse/issues/136
@patrickdevivo  @amenowanna  what do you guys  think ?

Sure - so this additional column is only needed in tables on the public schema right now, which are our "data" tables - what users will query and what the syncs populate. The idea here is to provide some context to the data in the database so the user can see how "fresh" it is (when were rows added). It may even make sense to prefix the column names here with something like mergestat_imported_at or just _imported_at.
@amenowanna what do you think?

also, for the #136, I'd rather handle in two separate PRs since the functionality is quite different

@patrick and I had a quick side bar on this and landed on _mergestat_synced_at since we are calling the things that do the work syncs. Adding the _mergestat prefix makes it very clear it is internal data. Moving forward we should use this prefix. I think we will eventually need to add more columns like _mergestat_synced_at and _mergestat_synced_at but we will add those when they are needed.


Constraint matches dialog redraw fix

SwingUI Constraint matches dialog now redraws correctly when viewed multiple times in a single solver run

Decided to refactor a bit (we now create a dialog each time and let the GC take care of it afterwards). I tried just about every combination of (re|in|^)validate and repaint, none of which worked reliably. Also, as this is a modal dialog window, it really makes sense to create it and throw away afterwards.

dear Jenkins, retest this please (just for checking the phrase is accepted and test results are correctly reported)

I can't reproduce this issue (haven't applied the code changes yet). Might you remember a reproduce recipe?

@oskopek This is good to merge, if we can prove that there is indeed a redraw issue currently (I can't seem to reproduce it).

Great! I'll take a look at this on Thu.
On Jan 26, 2016 2:24 PM, "Geoffrey De Smet"<EMAIL_ADDRESS>wrote:

@oskopek This is good to merge, if we can prove that there is indeed a
redraw issue currently (I can't seem to reproduce it).
—
Reply to this email directly or view it on GitHub.

Cannot reproduce either.
Some other change must have fixed it, or my updated system/JRE did. Closing.


default_service_name property for single instance

default_service_name property
description of property in readme

Check List

[x] New functionality includes testing.
[x] New functionality has been documented in the README if applicable
[x] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

Some tests failed but It's not up to me.

Nice addition. In the future we have tooling that does the changelog and metadata so you can skip that part.


Inference DiffSinger

Hello! Thank you so much for your work!
I have a question about inference DiffSinger. I trained my DiffSinger model and set the selected_param = "tension" parameter during training. When I try to run inference of model from the checkpoint, the tension parameter is required from me in the .ds file, how can I get around this error?
 Seems like you are not using our repository directly. In this case, you should turn to the owner of the repo you are using, and we are not able to provide help, sorry.

There is no selected_param in this repository. Seems like you are not using our repository directly. In this case, you should turn to the owner of the repo you are using, and we are not able to provide help, sorry.

Yes, I'm sorry, the parameter is not from your work. My question is about your repository. If I use tension emb in training, but do not apply for tension in the inference, can this spoil the quality of the prediction?

Your acoustic model using tension_embed means that it must consume a tension input, otherwise it cannot even produce reasonable outputs. You should consider training a variance model that predicts tension for it.

Сan I train a DiffSinger model without any variance embeddings? Will the DiffSinger train and predict singing?

You can turn off all variance embeddings. But why not train a variance model to gain more controls? Variance models are relatively small and cost less computational resources.


Add the SMA Docker executor code to edgex-go.

The work done in this PR is per Issue #1118.

Signed-off-by: Akram Ahmad<EMAIL_ADDRESS>

I will add reviewers once this PR is ready for review.
Meanwhile, I have created this PR to ensure the code builds cleanly on Jenkins 👍

@akramtexas is this PR ready for review yet?

@akramtexas is this PR ready for review yet?

@anonymouse64 Not yet. I'm getting it readied for review, which is why I haven't added any reviewers. Meanwhile, I had created a PR so I can find if there might be any potential issue(s) with building the code in Jenkins - I'll be sure to add you as a reviewer once it's ready for review.

Recheck

Recheck

Recheck

Recheck

Hmm... The build edgex-go-master-verify-go has started failing. It fails on reaching the step to do:  go mod download...

@anonymouse64 @tsconn23 All comments have been addressed and the squashed commit pushed to the remote repo (and the Jenkins build checks triggered and running at this time) 👍

Recheck

Recheck

@anonymouse64 @tsconn23 All comments have been addressed and the squashed commit pushed to the remote repo (and the Jenkins build checks triggered and running at this time) 👍

@anonymouse64 @tsconn23  With all checks passing, please do a final review and approve, thanks.


feat!: use composition and inheritance to build service managers

This pull request enhances the API of slurm_ops to use composition and inheritance to build the Slurm service operations managers. This makes it easier for us to construct managers around slurmctld, slurmd, slurmdbd, and slurmrestd and share logic for configuration and service management between them.
Some use cases
bulk update the configuration of slurmctld:
from charms.hpc_libs.v0.slurm_ops import SlurmManagerBase, ServiceType

slurmctld = SlurmManagerBase(ServiceType.SLURMCTLD)
slurmctld.config.set({"option1": "value1", "option2": "value2"})

set a new munge key:
from charms.hpc_libs.v0.slurm_ops import SlurmManagerBase, ServiceType

slurmd = SlurmManagerBase(ServiceType.SLURMD)
slurmd.munge.set_key("encodedmungekey")
slurmd.munge.restart()

start slurmrestd:
from charms.hpc_libs.v0.slurm_ops import SlurmManagerBase, ServiceType

slurmrestd = SlurmManagerBase(ServiceType.SLURMRESTD)
slurmrestd.enable()

add additional, charm-specific functionality:
from charms.hpc_libs.v0.slurm_ops import SlurmManagerBase, ServiceType

class SlurmctldManager(SlurmManagerBase)

    def __init__(self) -> None:
        super().__init__(ServiceType.SLURMCTLD)

        # Compose additional manager functionality.
        self.cgroup = ...

Misc.
Adds kebabizer from @jedel1043. The function format_key(...) will be used to format Slurm configuration keys before passing off to the Slurm configuration editor.

@jedel1043 good catch with pyfakefs! Ready for review again :mag_right:

Also, for future reference before we merge, we need to bump the lib patch version so that the updated lib will get published to Charmhub


compile error

I downloaded the GTS master file for windows.
I followed the instruction for the windows compilation. I compiled both third party software (fltk & libtiff)
then I run the command "one_step_build_vc2013" but I am getting these two error :
libtiff-4.0.3-vc2013-32.lib(tif_unix.obj) : error LNK2019: unresolved external symbol __imp____iob_func referenced in function __tiffUnmapProc
libtiff-4.0.3-vc2013-32.lib(tif_unix.obj) : error LNK2019: unresolved external symbol __imp__vfprintf referenced in function __tiffUnmapProc
any idea how to sole these issues ?

Is it not that the version of the compiler is different between the environment where libtiff was built and the environment currently developed?


Make exfile-b2 working with async HTTPoison response

As I understood this library correctly, it's working in this chain:

Get download url
Download file to the server
Send file to the user

The problem is, if the file is too big, it's kinda long to wait for the response. Best solution here, in my mind, is to use httpoison async response ability. Idea is slightly complicate alghorhythm to make it working significanlty faster:

Get download url
Start async request
On receiving headers start to response
On receiving headers start to write file to LocalCache.

WDYT?

Interesting.  My concern is that processors don't support streaming right now, so this would only work if there are no processors in the pipeline -- that is probably an acceptable compromise until a good asynchronous streaming processor API can be implemented.

@keichan34 by the way I found b2 problems with sending big files to us - videos aren't playing correctly and downloading in the small speed. Have you experienced this bug?

I haven't, but most of my files are anywhere between 1 and 15 MB -- are your files a lot bigger than that?

Yeah.


Ballerina Composer cannot be opened

Description:
Ballerina Composer cannot be opened. When command composer is given, the output is 'Error: Could not find or load main class org.ballerinalang.composer.server.launcher.ServerLauncher'
Steps to reproduce:
I used windows command prompt as the terminal emulator.
Affected Versions:
Ballerina 0.975.1
OS, DB, other environment details and versions:
Windows 10 Education
Related Issues (optional):

Suggested Labels (optional):
Composer,Bug
Suggested Assignees (optional):

I could resolve the issue by replacing
FOR %%C in ("%BALLERINA_HOME%\lib\resources\composer\services*.jar") DO set BALLERINA_CLASSPATH=!BALLERINA_CLASSPATH!;".\lib\resources\composer\services%%~nC%%~xC"
with
FOR %%C in ("%BALLERINA_HOME%\lib\resources\composer\services*.jar") DO set BALLERINA_CLASSPATH=!BALLERINA_CLASSPATH!;"%BALLERINA_HOME%\lib\resources\composer\services%%~nC%%~xC"

then what is a command to command line for run composer.

@yohanym95 just run the composer.bat script from command line. This particular class loading issue has been fixed in the latest distributions

i use 0.970.1 ballerina  version and i run the composer.bat in command line but can't open to composer.


@SuperBuilder dont generate any code

IDE
IntelliJ

Plugin
IntelliJ Lombok plugin v 0.22.2018.2

Dependency
org.projectlombok.lombok:1.18.4

@SuperBuilder
@Getter
public class CellBaseData {
    public enum HorizontalAlignment {
        LEFT, CENTER, RIGHT
    }

    @Setter
    private Row row;

    private Color backgroundColor;
    private Color borderColor;
    private int span = 1;
    private HorizontalAlignment alignment = HorizontalAlignment.LEFT;
    private float paddingLeft = 4;
    private float borderWidthTop = 0;

    public boolean hasBorderTop() {
        return getBorderWidthTop() > 0;
    }
}

@SuperBuilder
@Getter
public class CellText extends CellBaseData {
    private final String text;
    private final PDFont font;

     public PDFont getFont() {
        return Optional.ofNullable(font).orElse(getRow().getFont());
    }
}

The problem
For this example lombok dosn't generate any code for the  @SuperBuilder-annotation.
When I try to access the builder via CellBaseDate.builder() or CellText.builder(), then IntelliJ says, that this method is missing.

It's currently not supported by lombok-plugin for Intellij: https://github.com/mplushnikov/lombok-intellij-plugin/issues/513

Ok, thanks.

Hi @mplushnikov, is there any other way to use @SuperBuilder with intelliJ ?

@dvsingh9 Unfortunately not. Only when this functionality was implemented in the plugin, which unfortunately proved to be more difficult than initially thought.


CORE-16620 Implement interop identity delete endpoint

Changes

Add delete endpoint
Fix an error with interop identity deletion in the interop processor

I think this approach is fine but i'd be eager to see what the the impact on deleting an identity mid flow is ... I imagine we'd break things pretty badly. It's an area we'd want to test


GH2519: Changes for stable Visual Studio 2019 release

Changes regarding the release of Visual Studio 2019.
Fixes #2519

For some reason, I cannot access the bitrise ci to check why it failed.

@Roemer said...
For some reason, I cannot access the bitrise ci to check why it failed.

Unfortunately, the bitrise builds can't be made public :-(
Looking at the log, this is nothing to do with your change, so don't worry about it.  Something we need to fix.

Unfortunately, the bitrise builds can't be made public :-(

Actually they now can, but they need to be recreated, I've recreated the Ubuntu Bitrise build and disabled old build, changed which is required for PRs to the new.
Issue was an expired ssh key, new build uses https which is what they allow for public projects.

Bitrise macOS build now recreated and public. Old OSX disabled.

So how do we go on from here? Are any more changes needed?

@Roemer your changes have been merged, thanks for your contribution 👍

@devlead Hi, do you know when will it be in a release?
(Or is there a better way for me to find that out without asking here?)

It'll be in a release as we're happy with what's in the current milestone
https://github.com/cake-build/cake/milestone/59
Then we'll announce it before release at
https://twitter.com/cakebuildnet
https://gitter.im/cake-build/cake
https://gitter.im/cake-contrib/Lobby
A realease will appear at
https://github.com/cake-build/cake/releases
new packages here:
https://www.nuget.org/profiles/cake-build
A tweet will notify when package is out at
https://twitter.com/cakebuildnet
https://gitter.im/cake-build/cake
https://gitter.im/cake-contrib/Lobby
A blog post here:
https://cakebuild.net/blog/Release-Notes/
We'll also post to medium and linked in and a few other places
There's a recent YouTube video showing the process when Gary live streamed the release of 0.33.0 available at
https://youtu.be/cHtrJAc7sAQ


Support Symfony3 components

As per title

The upgrade would drop support for php 5.4. I don't think that upgrading dependencies this way is  useful. Symfony components aren't core feature of phpqa. I guess that when robo releases v1.0, then components will be updated. No need to hurry, isn't it?

Is there a reason you couldn't do "~2.8|~3.0"?
The reason I'm asking is that packages I have installed globally (like I also want phpqa) such as some laravel components require ~3.0 or ^3.0 (can't check, on mobile now) which makes me unable to install phpqa due to dependency conflicts.

Also, php 5.4 is unsupported now. The only supported release from the 5 line is 5.6. I see a value in keeping support for older versions, such as 5.5, but php 5.4 support ended 9 months ago ago (September 2015)
Source: http://php.net/eol.php

5.5 is also supported, but not for long

Is there a reason you couldn't do "~2.8|~3.0"

That's fine. I thought that 2.X version is dropped.
Can you create a PR?

This tools looks interesting, but it seems like a bit of a show-stopper that it's not possible to install it locally into a project using one of (or the) most popular PHP framework (Laravel) for months?
I know i could install it globally (and i read your opinion about having a per-project composer.json style install), but we don't have the option to install it globally on the CI server. Our required "binaries" (phpunit, phpqa, etc...) must go in .../vendors/bin/ in our project... so adding this tool to our project's composer.json is what we want to do.
I am referring to the fact that phpqa requires the old Symfony 2.8 components, but we cannot downgrade all our Symfony components just to install phpqa.
Is this going to be possible in the near future?

@g4z: can you please confirm that https://github.com/EdgedesignCZ/phpqa/pull/30 solves the issue?

thanks for the speedy update! yes, it seems to have resolved the issue. i can install correctly now.
but due to our minimum-stability policy, i had to test in a tmp branch and force dev-master versions for phpqa and henrikbjorn/lurker. this pulls in other newer versions of hoa/core, which seems to break half of our unit tests :( but that's another issue.
thanks for the update! i hope to get this tool integrated into various projects soon.

Version 1.7 is released, but you still need dev-master dependencies


Tracker grpc refactor

issues:

service-interfce :fixed
old service-interfce

// old service/NodeAccountService api
    Login(obdClient *ObdNode, msgData string) (retData interface{}, err error)
	Logout(obdClient *ObdNode) (err error)
	UserLogin(obdClient *ObdNode, msgData string) (retData interface{}, err error)
	UserLogout(obdClient *ObdNode, msgData string) (err error)
	UpdateUserInfo(obdP2pNodeId, obdClientId, userId string) (retData interface{}, err error)
	UpdateUsers(obdClient *ObdNode, msgData string) (err error)
	GetNodeInfoByP2pAddress(context *gin.Context)
	GetUserState(context *gin.Context)
	GetUserP2pNodeId(context *gin.Context)
	GetAllUsers(context *gin.Context)
	GetAllObdNodes(context *gin.Context)

	// service/channel api:
   func (manager *channelManager) updateChannelInfo(obdP2pNodeId string, msgData string) (err error)
   func (manager *channelManager) GetChannelState(context *gin.Context)
   func (manager *channelManager) GetChannels(context *gin.Context)

	// service/htlc api:
	func (manager *htlcManager) getPath(msgData string) (path interface{}, err error)
	func (manager *htlcManager) updateHtlcInfo( msgData string) (err error)
	func (manager *htlcManager) GetHtlcCurrState(context *gin.Context)

the old intrerface: have none document;input/output parameter with week type; mixed gin-handler and data-api service
new service api,define with protobuf ,detail in tracker/tkrpc/info-tracker.proto
new interface api
service InfoTracker {
rpc HeartBeat (stream UpdateNodeInfoReq) returns (EmptyRes);
//map to old func Logout Login
rpc UpdateNodeInfo (UpdateNodeInfoReq) returns (EmptyRes);
//map to old func userLogout userLogin
rpc UpdateUserInfo (UpdateUserInfoReq) returns (EmptyRes);
//map to old func updateUsers
rpc UpdateUserInfos (UpdateUserInfosReq) returns (EmptyRes);
//map to old func: GetUserState , GetUserP2pNodeId
//Request:SetUserInfoReq{user_id,node_Id}
//old GetUserP2pNodeId use request:SetUserInfoReq{user_id} ;  may not work when user login on multi node
rpc GetUserInfo (UpdateUserInfoReq) returns (UserInfo);
//Map to old function GetAllUsers
rpc GetUserInfos (ListReq) returns (UserInfosRes);
//map old function GetAllObdNodes
rpc GetNodes (ListReq) returns (NodeInfosRes);
// map to old ChannelService.updateChannelInfo

rpc UpdateChannelInfo(ChannelInfo)returns(ChannelInfo);
rpc UpdateChannelInfos(UpdateChannelInfosReq)returns(EmptyRes);
//map to old ChannelService.GetChannelState
rpc GetChannelInfo(SimpleFilter)returns(ChannelInfo);
rpc GetChannels(ListReq)returns (NodeInfosRes);

// map old function updateHtlcInfo
rpc UpdateHtlcInfo(HtlcInfo)returns (HtlcInfo);
//map old function getPath
rpc HtlcGetPath(HtlcGetPathReq)returns (HtlcGetPathRes);
//map old function GetHtlcCurrState
rpc GetHtlcInfo(GetHtlcInfoReq)returns (HtlcInfo);
}

//obd-user-info
message UserInfo {
    int32 id = 1;
    //user_peer_id
    string  user_id = 2;
    //node_peer_id
    string  node_id = 3;
    // 1 online 2 offline
    int32 is_online = 4;
    string access_ip = 5;
    //unix timestamp in seconds ; google.protobuf.Timestamp will more better,but sql database not support protobuf.Timestamp.
    int64  updated_at = 6;
    int64  created_at = 7;
}
...
...

strong-type;can add some comment as document in the proto, and the document pass to proto genrated go-files, and can pass to swagger document too, even pass to jsdk which invoke the rpc-service.

one user use multi obd-node call getUserP2pNodeId,this will not work. fixed:now only one tracker
tracker side updateUsers not set userinfo.ObdP2pNodeId. userInfo should sync thie field. fixed
omnibolt-report-final.pdf refer: OBD uses not maintained dependencies ( ile-rotatelogs, asdine/storm, etc.).   fixed:storm is delete ,Tracker use gorm database model now.
tracker/dao/pojo.go UserInfo.ObdNodeId fieldname hard to undstand .fixed
func (manager *htlcManager) getPath(obdClient *ObdNode, msgData string) (path interface{}, err error) at  tracker/service/htlc_service.go  lines 40.
the reutred paramter path may string or a map; when consume function,you should use reflect to detect  type of return value at  lightclient/connect_tracker.go lines 107,it's a bad desgin
https://github.com/omnilaboratory/obd/blob/58293151d0122daf331a518cea5105bd2e619374/lightclient/connect_tracker.go#L98-L114
userState manange, userOnlineOfOtherObdMap  .fixed
old code
https://github.com/omnilaboratory/obd/blob/58293151d0122daf331a518cea5105bd2e619374/tracker/service/p2p_service.go#L213-L245
it's hard too guess the mean of the var-params at line 225 from the code context,you must lookup the message source too get the mean; no anyone can't maintance it directly.   parallel map is a problom too..

the new version code:
func (s *ImpInfoServer) UpdateUserInfo(ctx context.Context, req *tkrpc.UpdateUserInfoReq) (*tkrpc.EmptyRes, error) {
	uinfo := new(tkrpc.UserInfo)
	err := Orm.FirstOrCreate(uinfo, tkrpc.UserInfo{UserId: req.UserId, NodeId: req.NodeId}).Assign(tkrpc.UserInfo{IsOnline: req.IsOnline}).Error
	return &tkrpc.EmptyRes{}, err
}

two dumplicate function:  tracker/service/p2p_service.go sendChannelUnlockInfoToObd SendChannelLockInfoToObd .fixed
https://github.com/omnilaboratory/obd/blob/58293151d0122daf331a518cea5105bd2e619374/tracker/service/p2p_service.go#L266-L300
https://github.com/omnilaboratory/obd/blob/58293151d0122daf331a518cea5105bd2e619374/tracker/service/p2p_service.go#L349-L385
channelInfo will update on tracker and obd-server both side; every obd start ,obd's  channels-Info data will cover the tracker data,the tracker's update will lost. the sync mode between obd and tracker is a problom.
channelInfo's fields is diffrent from the obd.
when obd commit channelInfo to tracker, now we have some convert code:

    //infoRequest is the data submit to tracker
	infoRequest.PeerIdA = channelInfo.PeerIdA
	infoRequest.PeerIdB = channelInfo.PeerIdB

	infoRequest.IsAlice = false
	if commitmentTx.Id > 0 {
		if commitmentTx.Owner == channelInfo.PeerIdA {
			infoRequest.IsAlice = true
			infoRequest.AmountA = commitmentTx.AmountToRSMC
			infoRequest.AmountB = commitmentTx.AmountToCounterparty
		} else {
			infoRequest.AmountB = commitmentTx.AmountToRSMC
			infoRequest.AmountA = commitmentTx.AmountToCounterparty
		}
	}

we should modify  channelInfo's fields same as the tracker.  we will easy a bit  when tune the sync mode between the obd and tracker.
channelInfo.IsAlice should be function,it's a commputed filed. example:
func (c *channelInfo)IsAlice(currentUserPeerID) bool{
	return c.PeerIdA==currentUserPeerID
}

func (manager *htlcManager) getPath(msgData string) (path interface{}, err error) shoud have a document: the main fllow,and how to use the return value.
https://github.com/omnilaboratory/obd/blob/58293151d0122daf331a518cea5105bd2e619374/tracker/service/htlc_service.go#L40-L83

obd/service/user.go line 60 code call noticeTrackerUserLogin().sendMsgToTracker()  .fixed
https://github.com/omnilaboratory/obd/blob/58293151d0122daf331a518cea5105bd2e619374/service/user.go#L20-L76

issue 1: if some err,we should not invoke it. if it noticeTrackerUserLogin just record a audit-log, we can ignore the err and invoke it.
issue 2:  obd/service is just a database/data operate module, it should not  call sendMsgToTracker to send async message; obd/lightclient module is async message center,now 95% async messages are recived and send here, all the client-websocket-conn p2p-conn are init here  ; obd/service/htlc_tx_forward.go PayerRequestFindPath invoke "sendMsgToTracker(enum.MsgType_Tracker_GetHtlcPath_351, pathRequest)"  have the same probolem
now i have fix the two issue, and obd/service.sendMsgToTracker have disbled,  and blow  messages submit by grpc-conn now,no need to sync userInfo/channelInfo/htlcInfo to tracker with complex async message Goroutines. the old msgList:

MsgType_Tracker_UpdateChannelInfo_350
MsgType_Tracker_UserLogin_304
MsgType_Tracker_UserLogout_305
MsgType_Tracker_UpdateHtlcTxState_352

may be we should design the obd-tracker info sync-mode and security first. maybe after design above work is no need.

now tracker's websocket server-api can switch to grc-server.
but need more test.

Related dicussions have been put in the following issues:
https://github.com/omnilaboratory/obd/issues/55
https://github.com/omnilaboratory/obd/issues/56
https://github.com/omnilaboratory/obd/issues/57
https://github.com/omnilaboratory/obd/issues/58


Task11,Task14,Task19,Task22,Task23

@poojakolhe84
this PR closed by yourself I'm unable to review  your code reopen it


Rebuild for metis 5.1.0

Checklist

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

I currently can't install moab with mpas_tools because of a dependency constraint within mpas_tools (via python-igraph via suitesparse) that requires metis >=5.1.0,<<IP_ADDRESS>a0.
This seems to be related to a recent change in how metis gets pinned (to the patch version) but I can't say I fully understand it.  A migrator that is in the works might help but for now I need this fix to be able to install moab and mpas_tools in the same environment.

@conda-forge-admin, please rerender

The SuiteSparse dependency is not needed for pytho-igraph or igraph, see https://github.com/conda-forge/python-igraph-feedstock/issues/74 and https://github.com/conda-forge/igraph-feedstock/issues/56

@szhorvat, Ah, wonderful!  That would be the easier fix.


use absolute url for grafana link

https://github.com/stolostron/backlog/issues/21045
Signed-off-by: Marco<EMAIL_ADDRESS>

/retest

/hold

/unhold


Milestone 006:Deploy portfolio website on github pages.

The following tasks were achieved in this milestone:

The portfolio website was deployed on github pages.See it live here. ✔
Implemented additional security with https.✔
Updated the links in the url to point to the deployed site.✔

Thankyou so much @danmainah .


Support for Deno v1.13 FFI

With the release of v1.13 Deno has replaced their native Rust plugin system with a more generic FFI interface (https://deno.com/blog/v1.13#experimental-ffi-replaces-native-plugin-system). Sadly Deno.openPlugin is now gone so deno_dom doesn't work w/ v1.13 and higher.
Are there plans to implement an FFI compatible version of deno_dom? We'd be happy to contribute to this effort if you can point us in the right direction.

Yes, I plan to implement it. If you're interested you can take a jab at it. However, it doesn't support buffers yet. It can only pass number types. When they implement buffers I'll definitely get the native backend working again.
For reference, here's the (open as of this writing) PR tracking string and buffer support for the new FFI interface https://github.com/denoland/deno/pull/11648

Okay, great to know that FFI is on your radar and hope that the string and buffer support lands soon.
I think that https://github.com/b-fuze/deno-dom/issues/64 would likely be enough for us until FFI lands, in the case that we did also want to try using the native plugin version (as that would give us the perf win both at load time for deno_dom code path and of course at runtime) do you still have reservations about the Deno plugin system stability? (saw these noted here: https://github.com/b-fuze/deno-dom/issues/48). We'd be running with Deno v1.12.2 (the last version to support native plugins).

do you still have reservations about the Deno plugin system stability?
Yes. The previous incarnation of the plugin system was very unstable. If you want to use the last stable version of the native plugin you'll need to use v0.1.9-alpha with Deno v1.9 as v1.10 introduced the new and buggy native plugin interface.

Okay in that case I think we’ll stick with WASM for now as we need some
bundler improvements introduced after v1.9
On Sun, Sep 5, 2021 at 5:17 PM b-fuze @.***> wrote:

do you still have reservations about the Deno plugin system stability?
Yes. The previous incarnation of the plugin system was very unstable. If
you want to use the last stable version of the native plugin you'll need to
use v0.1.9-alpha with Deno v1.9 as v1.10 introduced the new and buggy
native plugin interface.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/b-fuze/deno-dom/issues/63#issuecomment-913228970, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAZPR2NQBQKD5ORT6V3BV3UAPM5FANCNFSM5DPC6YYA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Deno DOM Native works with FFI now, closing this


[BUG][Map] points should update when place updates

When on a page with a points layer & changing the location, the page doesn't wait for the points layer to update before removing the page spinner
To reproduce:

go to: datacommons.org/tools/map#%26sv%3DCount_Person%26pc%3D0%26denom%3DCount_Person%26pd%3DgeoId%2F42%26ept%3DCounty%26ppt%3DEpaReportingFacility%26mp%3D1
change place to USA & place type to State
See that the original map points will appear & if you wait for a bit, then the points will update

geoId/26

switched to country/USA

Taking a quick look, I believe this has to do with ready_hooks (specifically render_ready) not waiting on map points

moved to buganizer


Set the project when creating/destroying pd disks.

@quinton-hoole

LGTM https://github.com/brendandburns/kubernetes/commit/3a2e20307f44344fa917d620c4ffab39500b2f6e

Please don't merge until @brendandburns givers the go-ahead confirming that e2e tests succeeded.

Confirming that this passed w/ both gcloud set project something-bad and gcloud set project correct-e2e-project
this is good to submit.

Merging, as this only affects PD e2e tests, which are currently failing 100% in the absence of this PR.


Unit order is not preserved

Unit order is not preserved (or it's not obvious for the naive user how to achieve this).
Please consider this minimal example (https://godbolt.org/z/G8aG8c8hz):
#include <mp-units/core.h>
#include <mp-units/systems/si.h>

#include <print>

using namespace mp_units::si::unit_symbols;

inline constexpr auto kWh = kW * h;

int main()
{
    std::println("{}", 123 * kWh);
    std::println("{}", 456 * kW * h);
    return 0;
}

Expected output:
123 kW h
456 kW h

Or even:
123 kWh
456 kWh

Actual output:
123 h kW
456 h kW

Unfortunately, I do not know how to preserve the unit order here 😢 We have to simplify the expression templates, and to do this, we have to sort the types in some arbitrary order. More info on this can be found in our docs.
Also, the text output is not meant for scientific usage. Some people even call it a "debug text output". Otherwise, we should probably provide LaTeX and HTML generators as well, which is far beyond the scope of such unit libraries.

Broadly speaking, my assessment is that "the juice isn't worth the squeeze".  If we were determined to do this, I think we could figure out a way, but I expect the cost of the extra complexity would outweigh the benefit of printing unit symbols in a more familiar order.
In fact --- is order preservation really what you're looking for?  Or is it that you want certain combinations of units to show up in a particular expected order, no matter which order they appear as inputs?  Wouldn't you, as a human reader, prefer that (2 * h) * ((228 * kW) to produce 456 kW h, rather than 456 h kW?
If there were some single, global ordering for a subset of units, such that symbols for units earlier in the list were always written before symbols later in the list, then I think it wouldn't be too bad to do this.  We could define the canonical ordering to use this ordering first (when available), and to use whatever-we're-using-now as a tiebreaker.
Meanwhile, there's a reasonable workaround.  You can define a custom unit, kilowatt_hour, with the kWh symbol.  I believe this will participate in every computation in just the same way as if it were a simple ad hoc combination of kW and h.  But if you use this new unit for your quantity types, and in particular whenever printing, then you'll see the unit label you expect: https://godbolt.org/z/s7GbKzrzv

If there were some single, global ordering for a subset of units, such that symbols for units earlier in the list were always written before symbols later in the list, then I think it wouldn't be too bad to do this. We could define the canonical ordering to use this ordering first (when available), and to use whatever-we're-using-now as a tiebreaker.

Unfortunately, even international standards like SI are explicitly inconsistent here 😞

My naive expectation was that definition order would be preserved. Exactly for the reason that proper unit order might be domain specific. Anyway: I totally see the benefit of normalizing unit order. Even more named_unit is easy enough to use.
 I have to admit that I really didn't care enough about implementation details to even consider reading that section before.
One more thing @mpusz: When you call these unit strings "debug text output", do you refer to the automatically generated text, or also to the explicitly named units? Asking as I tried to add wchar_t (or even char16_t) support for use with Qt, and in contrast to #557 being marked as "good first issue" this seems like pretty complex code with impressively deep stacktraces.

I wonder if it could be seen as a formatting task.
Something along those lines:
inline constexpr struct kilowatt_hour final :
named_unit<“kWh”, kW * h> {} kilowatt_hour;
inline constexpr auto kWh = kilowatt_hour;

std::println(“{::U[kWh]}”, 456 * kW * h); // -> "456 kWh"

Maybe it's worth to mention normalized unit order at some more basic section of the documentation

That is a good idea. I will do it soon. Probably I will add a short note about it next to units introduction and will put a longer description in FAQ. Thanks!

Even more named_unit is easy enough to use.

I will add this to "Use cases" or FAQ as well.

Don't be.

When you call these unit strings "debug text output", do you refer to the automatically generated text, or also to the explicitly named units?

Actually, that is not me who invented and use this term. That is why our docs do not have "Debug" next to the "Text Output" chapter 😉 I've heard this term in the ISO C++ Committee. They are partially right, though. This is mostly used to ensure/present that the program works as expected. Something like printf-like debugging.

Asking as I tried to add wchar_t (or even char16_t) support for use with Qt, and in contrast to https://github.com/mpusz/mp-units/issues/557 being marked as "good first issue" this seems like pretty complex code with impressively deep stacktraces.

I am not sure what the Qt constraints are here. By this issue #557, I meant to provide support for std::wcout and std::format() taking [std::wformat_string](http://en.cppreference.com/w/cpp/utility/format/basic_format_string)<Args...>.
You should not need to change anything else. There is no need to change named_unit or symbol_text in particular.
To provide a properly encoded input to wcout and format (and possibly for char16_t if you need it), a runtime text conversion from char8_t or portable char text should be performed.

But I would also like it to be part of the formatting task (e.g. for the purpose of i8n or user preferences)
Something along those lines:
std::println(“{::in(kWh)}”, 456 * kW * h); // -> "456 kWh"

@Spammed, if I understand it correctly, you would like to use this for internationalization, which can vary on runtime depending on the user settings. However, a unit conversion requires a destination unit to be known at compile time.
I assume you want the framework just to use the text provided, but I wouldn't do that without verification. To verify, we would need to find a way to convert this textual representation to the actual type kWh (which I really do not know how to do with current C++ rules). After that, we would need to check if we can convert from the current to the given unit, followed by a potential quantity value scaling to a new unit.
Taking the above into account, I do not think it is doable. So, we probably have to stick with the current syntax:
std::println(“{}”, (456 * kW * h).in(kWh)); // -> "456 kWh"

Please let me know if I am missing something here.

...if I understand it correctly, you would like to use this for internationalization, which can vary on runtime depending on the user settings.

Yes, that would be one of my use cases.

I assume you want the framework just to use the text provided,

No, not just to.
I maintain an older structural analysis program in which the user can switch at runtime back and forth between different units (m, cm, mm, inches, feed, N, pond, lp, rad, °, etc.) on the one hand and between English and German on the other and the display updates itself accordingly. To make things a little more complicated, the user can select different units and languages for output on 'paper' and output on screen.
To minimize confusion, ALL data is ALWAYS stored and handled internally in SI units (without any 'quantity' intelligence). So that different units are 'only' a problem of input and output.
I am following your efforts with great interest and hope that one day the compiler will point out my physically nonsensical expressions :-).
If such a framework also presents the units 'nicely' (depending on runtime decisions), that would of course also be very welcome.

I'm sorry, but I think we can't do much for your use case without #483.

Don't feel sorry. Powerful compiletime functionality has immense added value and runtime features can be added on top. I look forward to what may come.
(#483 is an interesting read)

@mpusz: I have seen your new FAQ note about, the topic:

[...] 42 * kWh / (2 * h) will result with 21 kWh/h

OK. Then, it's feels better to me to use '.in()' on every output and "kWh" only for that purpose.
std::println("{}", (42 * kW * h).in(kWh)); // -> "42 kWh"
std::println("{}", (42 * kW * h / 2 *h)).in(Wh)); // -> "21 Wh"

The second line seems wrong

Sorry, yes.

Sorry, yes.

Notice that you do not need to convert the unit in the second case.

So I still see it purely as a question of output

The generated unit type will also be more user-friendly.

As stated above, we can't do anything to mirror the multiplication order in the units order.
I extended the documentation to clearly state it so other users will not be confused (if they read the docs :wink:):

FAQ
Note in System of Units

With the above, I think we can close this comment.
If you have thoughts on improving here, please reopen and share your ideas.


mapping between event frames and RGB frames

Hi,
I notice the code https://github.com/uzh-rpg/DSEC/issues/25#issuecomment-956491275 you provided that generates event frames (640x480) from RGB frames (1440x1080). The mapping in the code could get the positions of the points of event frames in RGB frames.  I am wondering whether you could provide the mappings by which we could get the positions of the points of RGB frames in event frames. Thank you so much

Hi @wshku
The code you linked in your response actually does what you are asking for: It warps the image of the left global shutter camera to the left event camera frame.

@wshku if my answer solves your issue, please close the issue. Otherwise, let me know


warning: supporting new formats is a breaking change!

You need to add the #[non_exhaustive] attribute to the following types. Otherwise, changing them is a violation of semantic versioning and will break dependant crates:

nom_exif::error::Error
nom_exif::exif::tags::ExifTag
nom_exif::file::FileFormat

In other words, it's a breaking change to support new formats, make new errors, or add to the recognized EXIF tag list! See: https://rust-lang.github.io/rust-clippy/rust-1.81.0/index.html#/exhaustive_enums
To prevent this after the next major version, please consider adding the following to Cargo.toml:
# other stuff...

[lints.clippy]
"exhaustive_enums" = "deny" # all `pub enum`s are `#[non_exhaustive]`

Note that adding this attribute is also a breaking change! It really does require a major version bump... 😄

You need to add the #[non_exhaustive] attribute to the following types. Otherwise, changing them is a violation of semantic versioning and will break dependant crates:

nom_exif::error::Error
nom_exif::exif::tags::ExifTag
nom_exif::file::FileFormat

In other words, it's a breaking change to support new formats, make new errors, or add to the recognized EXIF tag list! See: https://rust-lang.github.io/rust-clippy/rust-1.81.0/index.html#/exhaustive_enums
To prevent this after the next major version, please consider adding the following to Cargo.toml:
# other stuff...

[lints.clippy]
"exhaustive_enums" = "deny" # all `pub enum`s are `#[non_exhaustive]`

Thank you for your reminder and suggestions!
I'm currently working on the next major version, and it has a lot of changes, with a fresh new API design, some new file types supports, performance improved, etc.
Although not completely finished, the sync API already works and all test cases pass. The Async API and documentation work will take a while yet.
If you are interested, you can check out this branch.
About the #[non_exhaustive] attribute, I thought about this issue and finally decided not to add this attribute for the time being. Because this property will mask and hide the problem. For example, if a new enum variant is added that may be important to users, but users are completely unaware of it, this may lead to some potential, difficult-to-detect errors or problems. Rather than hiding problems, it may be better to raise them, which may be more consistent with Rust's safety philosophy.
In addition:

The FileFormat type has been deprecated in v2, and the new MediaSource no longer relies on the enumeration type.
Error types I prefer to remain stable within a major version.
ExifTag is where I mainly consider whether to add this attribute. But considering that the API does not actually rely on the enumeration definition (it is just an alias for users to specify tags), users can always judge the tag/get the entry value through the tag code. Moreover, most users will not actually match all these variants. If someone wants to enumerate all variants, adding this attribute will make him unaware of the newly added attribute. For the above reasons, I have not yet made up my mind to add this attribute.

If you have more other considerations in this regard, please feel free to convince me, thank you!

Here's what the new API looks like:
use nom_exif::*;

fn main() -> Result<()> {
    let mut parser = MediaParser::new();

    // The file can be an image, a video, or an audio.
    let ms = MediaSource::file_path("./testdata/exif.heic")?;
    if ms.has_exif() {
        // Parse the file as an Exif-compatible file
        let mut iter: ExifIter = parser.parse(ms)?;
        let exif: Exif = iter.into();
        assert_eq!(exif.get(ExifTag::Make).unwrap().as_str().unwrap(), "Apple");
    } else if ms.has_track() {
        // Parse the file as a track
    }

    let ms = MediaSource::file_path("./testdata/meta.mov")?;
    if ms.has_track() {
        // Parse the file as a track
        let info: TrackInfo = parser.parse(ms)?;
        assert_eq!(info.get(TrackInfoTag::Make), Some(&"Apple".into()));
        assert_eq!(info.get(TrackInfoTag::Model), Some(&"iPhone X".into()));
        assert_eq!(info.get(TrackInfoTag::GpsIso6709), Some(&"+27.1281+100.2508+000.000/".into()));
        assert_eq!(info.get_gps_info().unwrap().latitude_ref, 'N');
        assert_eq!(
            info.get_gps_info().unwrap().latitude,
            [(27, 1), (7, 1), (68, 100)].into(),
        );
    }

    Ok(())
}

After rethinking it, I decided to add the #[non_exhaustive] attribute to
ExifTag and TrackInfoTag.
Thank you for your reminder and suggestions, which made me rethink and make this decision! And, v2.0.0 has been released!


[UI] update accordion to match stackview height

Update the accordion to have the same height as the stackview until the design aligning the stackview, accordion and stepper is complete.
closes #2452
Signed-off-by: Cory Rylan<EMAIL_ADDRESS>

Design review requests:

Accordion text weight should match stackview
Accordion remove leftside bar
Stackview fix caret padding to match Accordion


Add  method "getContinueGeneratingButton"

Hi all, I added this method for my own use and thought about open a PR for it, let me know if it is useful.
cheers!

Yes it is useful thanks @meiraleal!


undefined: time.Until while trying to install dependencies

i am trying to Install dependencies
and i got this.,
[root@btc tmp]# go get github.com/btcsuite/btcd
github.com/btcsuite/btcd
/root/projects/src/src/github.com/btcsuite/btcd/server.go:1233: undefined: time.Until

You need to update your version of Go. time.Until was added in 1.8.


[Storage] Change datetime for copy

Description

previous --destination-if-modified-since and --destination-if-unmodified-since should be datetime object with rfc format, which will cause error in command line.
Using ISO format is typical method for time related change. Here is to accept iso string as date time.
Testing Guide

History Notes

[Storage] BREAKING CHANGE: az storage blob copy start: Fix format issue for --destination-if-modified-since and --destination-if-unmodified-since
[Storage] BREAKING CHANGE: az storage blob incremental-copy start: Fix format issue for --destination-if-modified-since and --destination-if-unmodified-since

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

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

Storage


Added test namespace, and mentioned it in project.clj as :main.

As I added the small file try_out.clj for myself, I thought I push it, in case you find it helpful.

This is quite handy. Thanks for contributing this, @zenon!


forward_train

Hi, I am very interested in your wonderful docking work and want to know how to train the training method in this branch, Can you give me some helpful information? @HBioquant

Hi, @lfs119,
The repository provides functions for training, but does not provide a dataloader for training and a complete training script. We will consider making the whole training code open source when the 2.0 version is released.
Best


Add SIL SinkAddressProjections utility to avoid address phis.

Enable this utility during jump-threading in SimplifyCFG.
Ultimately, the SIL verifier should prevent all address-phis and we'll
need to use this utility in a few more places.
Fixes rdar://problem/55320867 SIL verification failed: Unknown
formal access pattern: storage

@swift-ci test

@swift-ci benchmark

@swift-ci test source compatibility

Performance: -O

Regression
OLD
NEW
DELTA
RATIO

FlattenListFlatMap
6876
8257
+20.1%
0.83x (?)

Code size: -O
Performance: -Osize

Improvement
OLD
NEW
DELTA
RATIO

Dictionary2
1180
965
-18.2%
1.22x

Dictionary
680
565
-16.9%
1.20x

NSStringConversion.UTF8
847
777
-8.3%
1.09x (?)

Code size: -Osize
Performance: -Onone

Regression
OLD
NEW
DELTA
RATIO

ObjectiveCBridgeStubFromNSDateRef
4310
4720
+9.5%
0.91x (?)

Improvement
OLD
NEW
DELTA
RATIO

Dictionary2
1590
1380
-13.2%
1.15x (?)

Data.hash.Small
354
329
-7.1%
1.08x (?)

Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB


Advanced Project Management

Experience
Anytype.20240505.182237.49.zip
Title
Advanced Project Management
Screenshots

Description
Manage projects by creating milestones and goals, track tasks, and manage your risks.
Categories
Project tracking
Language
en-US
Terms

[X] I agree that this Experience is licensed under the MIT License.
[X] I have intellectual property rights and/or permission to contribute the Experience and its content.
[X] I confirm that the Experience does not contain any harmful or malicious content.

/gallery approve


License info missing in classifiers and/or meta data

Sorry to bother you.
Larger enterprises scan packages before allowing them into their internal pypi index, and one of the things they scan for is the license information.  This is typically done via scanning the meta data (whatever pip show reports) and  classifiers in pyproject.toml.  Please can you add the necessary license information in both places?  Thanks much!
You can mirror what the main pydantic package is doing because that one is working and passed our internal scanner.

Would you mind sending a PR with it? I'll shortly make a release with it. I thought everything was fine license wise, but I can see it's not mentioned on PyPI.

Sorry about the delay.  I've created the PR at https://github.com/pydantic/bump-pydantic/pull/131
First PR ever in github so please excuse me for missing stuff.  Thanks.

Closed by https://github.com/pydantic/bump-pydantic/pull/131


fix: Fix Talkback focus cursor movement when inside Dialogs

Closes https://github.com/adobe/react-spectrum/issues/7471
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
Test the iframe Dialog story, especially in Firefox and make sure you can properly click into the input field and type without focus being lost. Also test the RAC Modal example in the docs with Talkback and make sure you can still move focus around via swipes. Will need smoke tests in general to make sure nothing else is broken
🧢 Your Project:
RSP

Closing for now, trying to figure out an alternative fix. Filed https://issuetracker.google.com/issues/384844019 to see what has changed recently, but also noticed several other libraries don't have this issue with most notably Material UI exhibiting something similar via https://mui.com/material-ui/react-dialog/ but not with https://base-ui.com/react/components/dialog so maybe there is something we can gather from there


TokenUsage when using streaming

added the possibility to set the option include_usage when streaming

handling the usage message chunk

currently only for OpenAI, I don't know how Claude handles usage when streaming

Does anyone know how to get the usage when using Claude and Ollama?

I'm ok if we do not support others yet.

I'm ok if we do not support others yet.

Alright

@linusbierhoff can you rebase/merge with latest main branch.

Can someone please check if we can merge?


¿Its possible to add stopPropagation() in the contextMenu ?

I want to add  stopPropagation() when i click some function my dropdown closes immediately. its is possible ?

Hi @theseeker16, what's the use case for this?

@josetaira I am wondering the same thing. The use case would be if you had some functionality that required the menu to remain open on click. e.g., editing the name of something inline (menu-item text becomes an input)

Seems like a valid use-case. Reopening this. @lucasprograms or anyone, if you would like to submit a PR, please free to do so. It'll be some time before I can get back to working on this.


Add position() and fn()

Just two ideas:

We could add a function for retrieving the position of an svg element (similar to http://stackoverflow.com/questions/13040685/finding-offset-position-of-svg-element)
We could add a function that enabled you to call a custom function on a selection e.g.: selection.fn(function(d,i) { //do something with d and i })

For the position function we could use getBoundingClientRect what is the difference between fn and each?

@moklick the problem with getBoundingClientRect is mentioned in http://stackoverflow.com/a/20407357 : "doesn't account for scroll position or the element's container position relative to the document".
You are right, each is sufficient for the task i was imagining :+1: .

@chrtze Ok.. so I think we need position and offset

@moklick yep!


Create a repo for the NATS "example release"

[ ] Create a github repository for it
[ ] Talk to the guys at SAP to get the latest work
[ ] Test to see everything works
[ ] Update the fissile README to point to the new repo

@viovanov We have a Git repo internally which we call something like fissile-dev area. It is a Git repo that contains a README and the minimum required configuration to have a simple flow from creating a BOSH relate to generating Docker images and Helm Charts to be deployed on Kubernetes. We use this for doing fissile PRs. We use nginx as the BOSH release. Is that comparable to what you have in mind here or do I misunderstand the issue here? Thanks for your feedback.

@HeavyWombat do you mind sharing the instructions on how to come from bosh release to imager+helm chart? I'd be interested in how much the information differs from what's in https://github.com/SUSE/fissile/blob/master/docs/configuration.md
Should all of that information probably even go into that document or an additional document in this repo?

@HeavyWombat I think so. We might put these into a sub folder first, like examples.  @viovanov  mentioned it would be great to have a release which is clusterable, like nats.
It would be great to test fissile images with minikube.

Ok, let's do it like this: I will create a repo under my user to show what we have plus a lot of disclaimers since we aimed for the smallest possible setup and took every short cut and trick we could find. The fissile configuration that was mentioned is the full truth, where what we did is more the TL;DR version.
We have a simple one BOSH release version and one with multiple releases that was used for the development of the colocated container change in fissile. If you want you could look into providing a nats-based version of the set-up that is clusterable as another branch or so.

@manno @voelzmo This is the repo which @qu1queee and I used for some fissile development work in the past: https://github.com/HeavyWombat/fissile-dev
@smoser-ibm FYI

@HeavyWombat  this is great. I just created https://github.com/SUSE/nats-containerized-release
It's still work in progress, but I managed to deploy it to minikube.


Handle differences in how Z3 and CVC5 parse :pattern

Hi @loganrjmurphy,
Running tasks asynchronously in Lean didn't work out, so I'm creating this simple wrapper to run Z3 and CVC5 in parallel. Currently, it does not handle :pattern. I remember you mentioned Z3 and CVC5 have different syntax for :pattern?

It may not necessarily be a syntax issue, but there seem to be some different constraints on what patterns could be specified.
For example, the version of cvc5 I am using accepts this theory specification (from the Coq project)
example1.smt2.txt , whereas z3 throws a number of errors:
(error "line 574 column 45: patterns cannot be variables or quantifiers")
(error "line 621 column 70: patterns cannot be variables or quantifiers")
(error "line 1091 column 95: patterns cannot be variables or quantifiers")
(error "line 1109 column 47: patterns cannot be variables or quantifiers")
(error "line 1222 column 99: patterns cannot be variables or quantifiers")


Update customizing-mappings.md

Added additional filter expressions

:x: Organization membership check failed
Members of the MicrosoftDocs organization should use the private repo. Please move your changes to https://github.com/MicrosoftDocs/Dynamics-365-Operations, and close this pull request.

It needs a column header and code inline markings. I'll add those after it's merged.

I am not sure how to move this, typically in the other repos I just use a separate branch, edit, and submit. Are there some instructions on how to move this?
From: Buckley Guderian @.>
Sent: Monday, August 16, 2021 1:15 PM
To: MicrosoftDocs/dynamics-365-unified-operations-public @.>
Cc: Nathan Helgren @.>; Author @.>
Subject: Re: [MicrosoftDocs/dynamics-365-unified-operations-public] Update customizing-mappings.md (#3510)
❌ Organization membership check failed
Members of the MicrosoftDocs organization should use the private repo. Please move your changes to https://github.com/MicrosoftDocs/Dynamics-365-Operationshttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FDynamics-365-Operations&data=04|01|nhelgren%40microsoft.com|d96547c6617f42a6dd6508d960f28023|72f988bf86f141af91ab2d7cd011db47|1|0|637647416931087764|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=psk6bybYNM6cP8WhCD%2BGK%2F1YK%2FtG5U%2FWP6zqLBWB6B8%3D&reserved=0, and close this pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fdynamics-365-unified-operations-public%2Fpull%2F3510%23issuecomment-899789845&data=04|01|nhelgren%40microsoft.com|d96547c6617f42a6dd6508d960f28023|72f988bf86f141af91ab2d7cd011db47|1|0|637647416931087764|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=ZGGCOxFlNquQ75gPUkL2gR6zNa9KqWEvimGENHvi3rI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALJTDT4BVZKZ4ZMUYBK3K6DT5FWTTANCNFSM5CINRRFQ&data=04|01|nhelgren%40microsoft.com|d96547c6617f42a6dd6508d960f28023|72f988bf86f141af91ab2d7cd011db47|1|0|637647416931097756|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=iHrKBFaPfbpPCggRQPD%2F8TFocYqT7cnUGenY%2BSTHbfc%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|nhelgren%40microsoft.com|d96547c6617f42a6dd6508d960f28023|72f988bf86f141af91ab2d7cd011db47|1|0|637647416931097756|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=dloowelRO7PGiAchpefFIUuEgnbklpwwXkCUd45gaLg%3D&reserved=0 or Androidhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26utm_campaign%3Dnotification-email&data=04|01|nhelgren%40microsoft.com|d96547c6617f42a6dd6508d960f28023|72f988bf86f141af91ab2d7cd011db47|1|0|637647416931107754|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=uz6oXkbuoPR2xVpKMk%2FwAZktHIxtguO4yqkXh9AcybI%3D&reserved=0.


Fix typo in README

This pull request removes a backslash that I am assuming is here by mistake. Due to being very minimal, I didn't see an issue being necessary but happy to create one if needed.

It's there to be compatible with different shells. Because the argument is not in quoted strings, some shells like zsh will get upset if you use a bare ? in the argument.

It's there to be compatible with different shells. Because the argument is not in quoted strings, some shells like zsh will get upset if you use a bare ? in the argument.

Interesting, I did not realise this, does that mean that this example probably wants to be updated?
A maximal example using all parameters looks like:
$ websocat "ws://localhost:6008/subscribe?wantedCollections=app.bsky.feed.post&wantedCollections=app.bsky.feed.like&wantedCollections=app.bsky.graph.follow&wantedDids=did:plc:q6gjnaw2blty4crticxkmujt&cursor=1725519626134432"

The argument to websocat in that case is in quotes so the ? doesn't need escaping

The argument to websocat in that case is in quotes so the ? doesn't need escaping

My bad!
Wonders off to get eyes tested


about the use of ”Latent Image Guidance“

Hello, I tested the following combinations of parameters on my own test images, and their output results are all the same. Is this a normal phenomenon or a code issue?
--use_guidance --g_scale 400 --g_t_start 200
--use_guidance --g_scale 800 --g_t_start 200
--use_guidance --g_scale 800 --g_t_start 1000
--use_guidance --g_scale 800 --g_t_start 0

This is not a normal phenomenon. The output will become more smooth when g_scale grows.

I also have the same problem.


[IN PROGRESS] karma.config.parseConfig error handling

Work in progress. Description TBD.
Related: #3631

Before I clean up comments and attempt to write tests for the new code, I was hoping to get feedback on this first attempt.

Before I clean up comments and attempt to write tests for the new code, I was hoping to get feedback on this first attempt.

:white_check_mark: Build karma 2885 completed (commit https://github.com/karma-runner/karma/commit/efd3debc07 by @npetruzzelli)

:white_check_mark: Build karma 2885 completed (commit https://github.com/karma-runner/karma/commit/efd3debc07 by @npetruzzelli)

@googlebot I signed it!

@googlebot I signed it!

:x: Build karma 2886 failed (commit https://github.com/karma-runner/karma/commit/2e2583226a by @npetruzzelli)

:x: Build karma 2886 failed (commit https://github.com/karma-runner/karma/commit/2e2583226a by @npetruzzelli)

:white_check_mark: Build karma 2887 completed (commit https://github.com/karma-runner/karma/commit/cdc64a3510 by @npetruzzelli)

:white_check_mark: Build karma 2887 completed (commit https://github.com/karma-runner/karma/commit/cdc64a3510 by @npetruzzelli)

:white_check_mark: Build karma 2888 completed (commit https://github.com/karma-runner/karma/commit/3a1cd83c70 by @npetruzzelli)

:white_check_mark: Build karma 2888 completed (commit https://github.com/karma-runner/karma/commit/3a1cd83c70 by @npetruzzelli)

I wasn't sure if you intended for fail to be used outside of parseConfig. If that was the case, the signature would need only a minor change.
function fail (logArgs, failOptions) {
    const _logArgs = Array.isArray(logArgs) ? logArgs : [logArgs]
    log.error(..._logArgs )
    if (failOptions && failOptions.throwErrors === true) {
    // ...
}
// in `parseConfig`
fail (message, parseOptions)
fail ([message, e], parseOptions)

// -- OR --

function fail (logArgs, throwErrors) {
    const _logArgs = Array.isArray(logArgs) ? logArgs : [logArgs]
    log.error(..._logArgs )
    if (throwErrors === true) {
    // ...
}

I wasn't sure if you intended for fail to be used outside of parseConfig. If that was the case, the signature would need only a minor change.
function fail (logArgs, failOptions) {
    const _logArgs = Array.isArray(logArgs) ? logArgs : [logArgs]
    log.error(..._logArgs )
    if (failOptions && failOptions.throwErrors === true) {
    // ...
}
// in `parseConfig`
fail (message, parseOptions)
fail ([message, e], parseOptions)

// -- OR --

function fail (logArgs, throwErrors) {
    const _logArgs = Array.isArray(logArgs) ? logArgs : [logArgs]
    log.error(..._logArgs )
    if (throwErrors === true) {
    // ...
}

I wasn't sure if you intended for fail to be used outside of parseConfig. If that was the case, the signature would need only a minor change.

Good to know! Let's keep it simple here and we can adjust the signature in the next PR (if/when necessary).

I wasn't sure if you intended for fail to be used outside of parseConfig. If that was the case, the signature would need only a minor change.

Good to know! Let's keep it simple here and we can adjust the signature in the next PR (if/when necessary).

:white_check_mark: Build karma 2892 completed (commit https://github.com/karma-runner/karma/commit/078db6fc9f by @npetruzzelli)

:white_check_mark: Build karma 2892 completed (commit https://github.com/karma-runner/karma/commit/078db6fc9f by @npetruzzelli)

:white_check_mark: Build karma 2895 completed (commit https://github.com/karma-runner/karma/commit/7991b9c9e2 by @npetruzzelli)

:white_check_mark: Build karma 2895 completed (commit https://github.com/karma-runner/karma/commit/7991b9c9e2 by @npetruzzelli)

@johnjbarton I think this is ready to land. Can you take a look?

Thanks!  For future reference, after a few commits, esp ones that revert changes, its probably better to squash the commits on your branch and push -f to the PR so all we see are the diffs that matter.


How to apply if else loop to the filter

I am not an expert here, but i want to know how can i add if else so in case if there is swear in the line it will disabled the button and enable after a check if there is not swear words

If you look at the demo, there's a callback function that is invoked around the profaneText.
// code:
$('#five').profanityFilter({
    customSwears: ['ass'],
    filter: true,
    externalSwears: 'swearWords.json',
    profaneText: function(data) {
        $('#five')
            .css('color', 'blue');
            console.log(data);
    }
});

you can do whatever you like within the callback, so I suggest just disabling the button in there.


Add a notify_release_stages option

Hey @jarednorman,
Thnx for building this package!
The official Ruby package has an option called notify_release_stages which states in what rack environments it is going to report errors.
Is there such an option in this package? If not, I'd be willing to do it through a pull request, just wondering if you're interested in merging it in.
Thnx.

That sounds reasonable. @mootpointer is maintaining this currently though.

@mootpointer This was fixed by #43  and can be closed.

Thanks.