Error: Too many tokens predicted

Why is this being thrown as an error?
https://github.com/Atome-FE/llama-node/blob/649457a2528b6d3b2ef5d35e0507c4022419973a/packages/llama-cpp/src/llama.rs#L120
Forgive my ignorance if I'm missing something, but seems like this should just set response.completed = true;
Context for error:
prompt is a String, ex "Hello World, "
tokens is Integer, ex 128
this.model.createCompletion({
    nThreads: 4,
    nTokPredict: tokens,
    topK: 40,
    topP: 0.1,
    temp: 0.2,
    repeatPenalty: 1,
    prompt,
}, (response) => {
    completition.push(response.token)
    console.log(response.token)
    if(response.completed || count == tokens) {
        resolve(completition)
        return;
    }
}).catch((error) => {
    reject(new Error("Failed to generate completition: " + error));
});

Again, if I'm not missing something it seems clunky to have to check it the error is actually just because we have hit the end token.

Installed updated version compiled direct from repo instead of npm registry and it seems to have resolved the issue.


[Python][Remove Six] Remove Six dependency part II

Description
Remove six dependency since now we only support Python3.
Changes included

Replace six.moves.urllib with urllib.
Replace six.moves.cStringIO() with io.StringIO().
Replace six.binary_type with bytes.
Replace six.moves.queue with queue.
Replace six.moves.zip_longest with itertools.zip_longest.
Remove unused import six.
Remove six.PY3 and six.PY2 flag.

Testing

Passed all CI tests.

@gnossen PTALA


puppeteer ,Deprecated API: page.waitFor and frame.waitFor

Puppeteer  project :
https://github.com/puppeteer/
Had released a new version
https://github.com/puppeteer/puppeteer/releases/tag/v5.3.0
It had Deprecated API: page.waitFor and frame.waitFor
Is there is any updates to  puppeteer-sharp?

My focus is now on playwright that (https://github.com/hardkoded/playwright-sharp)
But I don't see any blocker in the feature you mentioned. They are dropping and extra function.


CloudWatch Logs output plugin

As per me and @s12v's discussion in #8, probably we can include CloudWatch Logs output plugin within awsbeats.
Anyone has a specific use-case for that? Any concrete feature you'd like to have?

I'd love for filebeat to output to cloudwatch logs!  The cloudwatch logs agent doesn't have a 'processors' feature, or really any concept of fields.  This makes adding cloud metadata to events really difficult.
My current experiment is to try filebeat -> kinesis -> lambda -> cwlogs -> kinesis -> logstash -> es.
A CWLogs output plugin would skip the intermediate kinesis -> lambda.


A few feature requests

Sorry for making too much noises lately -- I'm quite excited experimenting with this project and think it might make scientific computing viable in CL!
A few feature requests, in the order of precedence:

matmul (seems that ceigen_lite already has it, but not exported to Lisp yet)
some primitives to help work with NaN values, like numpy.isnan and numpy.nan_to_num. The other numpy.nan* family of operators is useful as well, but they are easy to implement on top of isnan and nan_to_num (I have my own slow-as-molass implemention).
least square fitting primitives (lapack's GELS, eigen should have something similar as well).
matmul with arbitrary axis, or more generally, einsum
selection operator like numpy.select or numpy.choose

I wish I can help, but not quite sure where to start yet. It seems that there are some deprecated code in blas.lisp.bak that used to do some of the above?
Thank you for the amazing work!

least square fitting primitives (lapack's GELS, eigen should have something similar as well).

Seems that solve already does this for over-determined input!

matmul

It seems that matmul was present in an earlier version but I missed it while refactoring: https://github.com/digikar99/numericals/blob/2024.01.0/src/ranked-functions/matmul.lisp
Perhaps there should be also be an additional separate tests system with simple tests to ensure no such feature loss occurs during refactors.

einsum

I'd love to have this implemented, but I haven't been able to wrap my head around it.

Should we fix the single number case to make it consistent with vector behavior?

I'm probably leaning towards making the CFFI behavior consistent with the lisp image. Post that, anyone who wants to mask float traps can use float-features:with-float-traps-masked.

Should we also provide is-nan, as a thin wrapper of /=, to mirror NumPy API?

As a start, implementing this looks good. I lean towards making the names lispier nan-p, positive-infinity-p etc. float-features can be useful for this.
For efficiency, in terms of reducing memory access, there is a pending task to implement a vectorization function. Earlier, this was called with-elementwise-operations: https://github.com/digikar99/numericals/blob/8cec0a8f61db11cfad923d49a1280212f20dd660/src/with-elementwise-operations.lisp#L84 This probably requires more sophistication, since now instead of SIMD operations, we will be calling CFFI functions. So, ideally, reviving this should happen first.

Thanks for the comments! I'm trying to implement a selection primitive ((where condition-array then-array else-array)). Do you think it's important to do this in SIMD, or pure Lisp would be enough?

I'm understanding this to mean:
out = [condition * then] + [(1 - condition) * else]

There are SIMD primitives for multiplication, subtraction, and addition. So, I'll expect an SIMD solution to be much faster than an optimized Lisp solution.

There are SIMD primitives for multiplication, subtraction, and addition.

It's a bit different in the presence of NaN and Inf, so if we want SIMD with the correct behavior, we probably need to add bmas primitives (_mm256_blend*). I took a look at bmas implementation and seems that because this is a 3-argument operator we'll need to write 16 different cases for every subset of 3 input + 1 output to have stride = 1, which is scaring me off a bit…

Ah, yes, blend looks more suitable for this, and much more efficient as well!
This brings up another problem I haven't thought about: might there be a way to generate the 8 or 16 cases programatically, say using the CSP or otherwise? Or even sidestep the generation altogether?


What is the value of γ ?

Hi, I'm just implementing your ablation study.
There are 3 gaze mask fields on your code (gazenet.py).
γ=1, γ=2, γ=5
When you train the methods "one-scale", what is the value of γ about the gaze fields?
because the bigger one is the default setting, I think that γ is 5. but I'm not sure.
+ Could I know When does Epoch converge?

@BLUENCE
We set γ=1 for "one-scale" case. See table 1 in the paper.
15 epoch will be enough if I remember correctly.

Oh, I misunderstood. The cone becomes narrower as the number increases.
Thank you for your answer.


How to run model on my own data?

@arsalyou You can refer to the CelebA data format and modified the code in data.py to adapt your data.

@arsalyou see here.


fix(kit): InputFiles fix drag over detection when zone.js event coalescing is enabled

Closes #7004

@splincode thanks for merging the PR.
RoutableDialog: should works after switching tabs e2e test failure seems to be related to zone.js event coalescing. Might want to check that.


Fix CI CD pipeline issue of this repo

if there is any conflict of automation kindly remove it

if there is any conflict of automation kindly remove it

assign this to me @Yashgabani845

i tried but cannot resolve the issue @Yashgabani845 please assign this to someone esle


Can't add more than one ISY Scene?

I've tried to add more than one ISY scenes doing the following
.....
"includeAllScenes": false,
"includedScenes": [
"27346",
"43224"
],
.......
But no matter what, it does not work with multiple entries.  I have to remove the , and second entry.  I've successfully tried many single entries and all work fine, so I know it's not an issue with the names being the same, etc.
Is anyone else able to do multiple scenes?
Thanks

Has anyone else experienced this?

I haven't, but my regression test only works with a single scene. It's possible a recent update broke this. I'll have a look tonight.

Confirmed. There was a bug in the code which picked which scenes to return. It only worked when there was only one scene in your list of supported scenes. Just goes to show you that you get what you test -- and I only tested the case with one scene.
I've fixed it and pushed a new version to npm. V0.0.9 should have the fix.


The user will be redirected to the main menu when they have left the game.

Resolved with commit: updated leave game


Resource Embedding with Foreign Table Wrapper

PostgREST needs FOREIGN KEY constraints to be able to do Resource Embedding. What about foreign tables? Is it necessary to create a view in order to solve this issue?

I think you might be interested in reading:

https://github.com/PostgREST/postgrest/issues/915#issuecomment-780035727
https://github.com/PostgREST/postgrest/issues/1179

TLDR: Your best bet is to create a virtual column via function, that contains the embedding of the foreign table.

This is now documented on https://postgrest.org/en/stable/api.html#computed-relationships


Index in php

Hi,
First of all, nice job with this project. I only have one issue, I want to run this as a php file instead of html, how can I solve this?

If you could explain WHY you would want to mix it up with PHP, I might be able to provide an answer for you. It makes zero sense to just "run it as php", since it's a single page application that relies on a node.js backend.


Fix docs styling

Which issue does this PR close?

Closes #2864 .
Rationale for this change

What changes are included in this PR?

Update to latest sphinx and related libraries for building docs
fix doc linking issues
remove old template that throws warnings during docs build and doesn't appear to have been used anyway
enable prettier checklists in docs (sql status)
lock pydata-sphix-theme to version that matches look of main Arrow project

Are there any user-facing changes?

Nicer formatting

Codecov Report

Merging #2865 (90a58b1) into master (a2da720) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2865   +/-   ##
=======================================
  Coverage   85.24%   85.25%
=======================================
  Files         275      275
  Lines       49002    49001    -1
=======================================
+ Hits        41773    41775    +2
+ Misses       7229     7226    -3

Impacted Files
Coverage Δ

datafusion/core/src/execution/memory_manager.rs
69.95% <0.00%> (-0.31%)
:arrow_down:

datafusion/physical-expr/src/expressions/binary.rs
95.03% <0.00%> (-0.09%)
:arrow_down:

datafusion/expr/src/logical_plan/plan.rs
74.50% <0.00%> (+0.19%)
:arrow_up:

datafusion/sql/src/utils.rs
51.95% <0.00%> (+0.40%)
:arrow_up:

datafusion/core/src/physical_plan/metrics/value.rs
87.43% <0.00%> (+0.50%)
:arrow_up:

datafusion/expr/src/window_frame.rs
93.27% <0.00%> (+0.84%)
:arrow_up:

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 a2da720...90a58b1. Read the comment docs.

Thanks @kmitchener  and @xudong963 !


Unwearable Enderman Head

I was sad to discover, the enderman head can't be worn.

That would be cool


When add listener in ListView or RecyclerView, a problem happened

When add listener in ListView or RecyclerView,we cannot show reveal effect in 5.0+ ,or selector effect in each item...u can see this problem in ur sample app

The background in the custom views was not set. It's just a matter of adding:
    android:background="?android:attr/selectableItemBackground"

to the background to have it. I will be updating the sample with it.


Question -Is the cloaking random or algorithmic?

I'm curious whether the cloaking that this program performs is random or algorithmic?
Let's say, for instance, someone uses Fawkes to cloak a facial image. If that same original facial image were to be cloaked by Fawkes in a separate instance, would the output be a completely unique cloaked image? Or would it be the same as the first cloaked image?

The cloaking is randomize. It is randomized by the target label selection and also some inherent randomness in the stochastic optimization.


from collections import defaultdict

Hi all,
When I have installed CPLEX Studio12.9 I have noticed in the installation directory, there is a folder named "example". Since I am programming with python I was interested in the relevant session.
I have two questions:
One is what is the following library which is imported and used in some example files:
from collections import defaultdict
Is this LINK  refers to the above library?
Two is that I know CPLEX provides tools for multi-objective problems. Now is there an easy example for the sake of learning and introducing the tools and parameters?
The following link is where I referred but could not digest most of it:
LINK
Basically, is there a small example showing how to use the following commands (provided that they are the correct ones) and set the parameters of multi-objective problems' Parameters
mdl.set_multi_objective()
mdl.set_multi_objective_exprs()
Thanks

Hi,
Those questions are not docplex related. The cplex team is monitoring questions on https://stackoverflow.com/questions/tagged/cplex so you should ask there for questions about the CPLEX examples.
However, here's some answers:
1 - collections is the collections package from python. See https://docs.python.org/3/library/collections.html
2 - Please have a look at the diet.py examples (in cplex/examples/src/python). It demonstrates how to set a second objective,

I really appreciated your time.


Wrong logging of config settings

Fix: https://github.com/exuvo/Kodgen/commit/8db8e24562790a097fa680cf7ab06d537be6bd98

Fixed. Thanks.


fix(isolated-declarations): report an error for parameters if they are  ObjectPattern or ArrayPattern without an explicit type

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#3810  👈
#3809
#3808
#3807
#3806
#3805
#3804
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite


refactor: Subnav for integrations

Splits out the integrations into subfolders as they were growing!
WARNING! When releasing this to prod we need to update the links in the integration_data production feature flag

We could do this in a non-breaking way by adding a category field to the remote config items

We could do this in a non-breaking way by adding a category field to the remote config items

Might be nice to do this and then split out the integrations on the front end too - but simpler to just update the links regardless

Ah, I see what you mean now - the "docs" properties, yep ok with you now


Miss naming of classes and div in checkout steps

If you check frontend/register/steps.tpl and register.less there are one class 'step--payment' that are not used. Also in steps.tpl file, the second step payment are named with block "register".
{* Second Step - Payment *}
{block name='frontend_register_steps_register'}
This is my first comment here, can anyone more experienced can check if this needs improvement?
thanks

Description

Questions
Answers

Why?
Please describe why your change is necessary.

BC breaks?
yes/no

Tests exists & pass?
yes/no

Related tickets?
If this PR fixes an existing issue ticket, please add there url here.

How to test?
Please describe how to best verify that this PR is correct.

Requirements met?
Does your PR fulfil our contribution requirements?

Hey @tkapet, thanks for your contribution and welcome to the Shopware Community. Please fill all the fields in the table below your comment to fit our contribution guides.

This PR was closed due to inactivity. If this change is still important to you, feel free to create a new pull request.
For more information about our contribution guidelines, see https://developers.shopware.com/contributing/contribution-guideline/.


Clarification of Platform Support

I believe this is similar to #248  in that I'm attempting to use Surfman to support GLES on Linux. According to that issue that is not currently possible without forking the code and adding that support.
My reading of the code suggests this is still the case.
If this is so, I'd suggest clarifying the related README similar to what follows:
The library supports the following platforms:

...

* Windows, with OpenGL ES via Google's ANGLE library.
...

* Android P and up, with OpenGL ES.

Fwiw, I hit the same issue when doing a quick hack to get Servo running on a Pinephone Pro device (see https://fosstodon.org/@capyloon/111032248243803371).
We run under a wayland compositor so by default we are handled a GL api, while the device actually supports GL ES. I'm not sure if there is a way to do better runtime detection.


better clarification for semantics of orthogonal regions and the final states for each regions

Please consider the following example:
class X{
  sm{
    s1{
      -> s2;
     r1{
       e1-> w1;
     }
     w1{
       e2-> w2;
     }
     final w2{}

     ||

     r2{
       e3-> m1;
     }
     m1{
      e4-> m2;
     }
     final m2{}
    }
    s2{
      h2-> fState;
    }
    final fState{}
  }
}

Region r and region r2 have their own final states and there is an auto-transition for the super state s1. Currently, Umple considers this as an unguarded event and removes all internal transition for state s1.
if I'm not wrong, the auto transition must be activated once both regions are in their final states. It means we should not remove those internal transitions.
This needs more clarification. I might miss sth.

Could you please comment on this issue. I might be wrong
@TimLethbridge
@opeyemiAdesina

@vahdat-ab after reading through UML 2.5, and browsing through other resources, I believe that this behaviour is formally referred to as Completion Transitions and Completion Events.
Here are some of the search terms I used:
"orthogonal regions final states"
"completion transitions state machines"
"completion events state machines"

UML 2.5 Definition

<IP_ADDRESS>.3 Completion Transitions and completion events
A special kind of Transition is a completion Transition, which has an implicit trigger. The event that enables this trigger is called a completion event and it signifies that all Behaviors associated with the source State of the completion Transition have completed execution. In case of simple States, a completion event is generated when the associated entry and doActivity Behaviors have completed executing. If no such Behaviors are defined, the completion event is generated upon entry into the State. For composite or submachine States, a completion event is generated under the following circumstances:

All internal activities (e.g., entry and doActivity Behaviors) have completed execution, and
if the State is a composite State, all its orthogonal Regions have reached a FinalState, or
if the State is a submachine State, the submachine StateMachine execution has reached a FinalState.

In the example you've provided, I believe the completion event is when r1 reaches its final state w2, and r2 reaches its final state m2. The completion transition is -> s2.

Here are more resources I found that provide information regarding "Completion transitions and completion events":
Orthogonal Region Example
Non-Concurrent "ATM" Example --> Note the eventless transition from ServingCustomer to Idle
I also found this Orthogonal Region "CourseAttempt" Example from a website
that I believe is @TimLethbridge's.
It is also contained in the UML 2.5 documentation Figure 14.9 Composite State with Regions
From this page on the same website:

A transition to a final state represents the completion of behavior in the enclosing region. Completion of behavior in all orthogonal regions represents completion of behavior by the enclosing state and triggers a completion event on the enclosing state. Completion of the topmost regions of an object corresponds to its termination.

Here is a StackOverflow page in which Join and Completion Event and Transition are compared.
I think we've partially implemented the Join behaviour from the solution for #140, since delete()is only called when all of the state machines within an orthogonal region are in their final states. If we implement the completion transition, I think it would require replacing the delete() call with a call to the completion transition. In your example, the call would be __autotransition1__()

This will require me to study what we said recently about another issue where we discussed auto-transitions. Could you please find me that to save me time. Then I can look at all the semantics together.

@TimLethbridge from #140 here is the link that @vahdat-ab referenced regarding his concern of how auto-transitions are supposed to be handled in orthogonal regions in Umple.
You followed up to his comment with:

I acnknowledge @vahdat-ab 's concern. He pointed to a link showing UML semantics that includes regions that can independently reach final states, but not terminate the enclosing state, with a 'completion' transition occurring when all regions do reach their final state. Presumably, the same logic in UML would apply in any nested state (i.e. just one region in a state). The example Vahdat pointed to also shows joins. We have not implemented this sort of thing in Umple currently and it would be a considerable piece of work to do so.

In the same issue, one of the earliest comments suggested that a Done keyword should be added to Umple. I did not find any further discussion on it but I've put it here for your reference:

We have also agreed to add another keyword done that is actually a real state that can
exist in any state machine.
Done will work as follows:
We will add automatic outgoing transitions ( transitions without any event on it)
If there is an automatic transition then a transition to Done will cause this to be
taken (subject to guards, and of course there can be more than one such transition
with different guards, however to prevent getting 'stuck' in a state at Done, there
would need to always be one unguarded automatic transition, even if it is just a loop
back to the same state).
In the case of a state with concurrent regions. then the automatic transition will
take place when all of the regions reach done.
There will be a warning if there is a transition to Done without the presence of any
automatic transition.
Done is not syntactically shown as a state, so there can be no entry actions, exit
actions or do activities while in done state.

OK. I see the long-ago discussion about having 'done' as a transition indicating 'final within a nested state', and retaining 'final' to mean 'delete the object'. However it seems we have deviated from that. I am willing now to accept the logic that says 'auto transition must be activated once both regions are in their final states. It means we should not remove those internal transitions.

To give whomever is assigned this issue a head start, here are the main steps that are required for this change:

Update the checkStateForDuplicateEvents method in UmpleInternalParser_CodeStateMachine.ump so that W054 is not thrown for auto-transitions when there are user-defined final states. If you compile Vahdat's example, you'll see this warning is currently generated.

For nested-state machines, update the prepareFinalStatesFor method in Generator_CodeJava.ump so that auto-transitions are called when the state machine transitions into a user-defined final state.

For concurrent state machines (orthogonal regions), update prepareConcurrentFinalStatesFor in Generator_CodeJava.ump so that auto-transitions are called when all orthogonal regions are in their user-defined final states.

There is an excellent new example in #1499. A workaround showing manual 'done' semantics is shown there.  'done' semantics could be added such that it can be generated automatically.


[New app]: Edge WebView2

What is the new application?
Edge WebView2 includes an evergreen standalone installer and a fixed version installer
Vendor site
https://developer.microsoft.com/en-us/microsoft-edge/webview2/
Have you reviewed the list of supported applications?

[X] Support apps at: https://stealthpuppy.com/evergreen/apps/

ARM64: https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/1dab5915-49a4-45bd-93ce-d06c1cdf83ce/MicrosoftEdgeWebView2RuntimeInstallerARM64.exe
x64: https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/455fca72-907d-487c-a4bd-e4f76eb91b1a/MicrosoftEdgeWebView2RuntimeInstallerX64.exe
x86: https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/b0172457-f75a-4bb6-9742-17f70964d29d/MicrosoftEdgeWebView2RuntimeInstallerX86.exe

Bootstrapper: https://go.microsoft.com/fwlink/p/?LinkId=2124703


Add video dubbing API client sample code.

Purpose
Add video dubbing API client tool which can be used as console tool or API sample code.
Pull Request Type
Add new video dubbing API client sample code.

[ ] Bugfix
[x ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

please move to a standalone folder if you don't use SDK in this sample, refer to batch-synthesis


pygame.error: No available video device

When the program run to render.py，
srf = pygame.display.set_mode(viewport, pygame.OPENGL | pygame.DOUBLEBUF)
I meeted the error "pygame.error: No available video device". I searched for a lot of solutions like "os.environ["SDL_VIDEODRIVER"] = "dummy", but raised another error "pygame.error: OpenGL not available" .
I installed all the packages as requirements.txt, could anyone give any advice to fix this problem?

@JaniceXiong Hello， did you fix this problem, I got the same issue with you. Hope you can help me. Thanks a lot!

Maybe you use ssh serviece to connect linux server, you can try mobile xterm or other software which support X11 to run main.py.


chore(deps): update dependencies

should all be safe updates

tests fail with j8: Caused by: java.lang.UnsupportedClassVersionError: org/mockito/junit/jupiter/MockitoExtension has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Allow overriding the used transport

This allows users of axios inside electron to provide the net module as the http transport instead of using nodes http/https modules.  This gives a whole bunch of things to Electron users including automatic proxy resolution.

Create an issue explaining the feature.

Only saw this after making the change 😆 It's only a few lines so happy to discuss here 👍

Coverage remained the same at 93.812% when pulling b01ce193a567dcf3a7c2c62cff5d582f264daae2 on MarshallOfSound:patch-1 into 07a7b7c84c3ea82ea3f624330be9e0d3f738ac70 on mzabriskie:master.

@MarshallOfSound Thank you!


Feature/175 async transactions

See #175 for notes about implementation and other fun stuff.

Sorry, I'm shooting int the dark for the build errors.  my local environment is not the same as travis in some strange way.  Nothing travis has brought up has been incorrect, it is just frustrating to have to bounce off travis for changes.  😠

Wow, its literally the difference between clang-4.0 from Ubuntu 16.04 official repositories and clang-4.0 from llvm's release repository.
granted that is effectively 4.0.0 vs 4.0.1 but still.  Anyway... now that I have a local build environment I can agree with Travis... its building fine 😜


remove code copied from gist

the code has no license specified
if it turns out that we need this test code, we will need to either see if scalatest supports retries now (eventually works well)
or approach the author to see if he will grant us permission to license the gist

I think this can be replaced with what I did in https://github.com/apache/incubator-pekko/pull/471 or with something like
lazy val root = Project("test", file(".")).
  settings(commands += Command.command("testUntilFailed") { state =>
    "test" :: "testUntilFailed" :: state
  })

Which lets you run tests until they fail. I am actually thinking of putting both of these into an sbt-plugin (under my org) because they are generally useful.


Estimates not Showing

Describe the bug
Estimates not showing.
To Reproduce
They never show, no error reported in DevTools (F12)
Expected behavior
Display status (Injured etc.)
Screenshots
If applicable, add screenshots to help explain your problem.
Game Specifics (please complete the following information):

Game System and version: PF2e 5.15.2
Module Version 31.8.8

Additional context
It was working, but some time ago - was hoping an update would fix it but no luck!

Have you had any luck with this? I haven't managed to reproduce this error back then, and there were no changes to the PF2e provider since 31.8.0.

I managed to discover a workaround. If I switch the text to RGB, they show again. Switching them to B&W makes them disappear

Hm, still couldn't reproduce it. That's super odd, disabling colors doesn't change anything in the way the module works.
Could you try resetting the Style Settings and then disabling the colors?

Sorted, thanks!


[Feature Request] Auto-Docstring generation for Schema bearing Models

Feature Request
This request is to have Pydantic models auto-generate their doc strings for their parameters, reading the parameters' Schema objects for more information. The end result would be Model classes who's __doc__ provides details about the parameters the model has. This would have use for people who generate docs for their models though a program like Sphinx to auto create the more complete docstring.
This can, and probably should be an optional thing the user sets or calls since it will require overwriting the __doc__ variable.
This may turn out to be too dependent on individual user preferences of doc style flavors to have any viable officially supported flavor(s) in pydantic, but I wanted to propose anyways.
Below I have a crude toy implementation with examples to show the outputs. I have tested this in Python 3.6 and 3.7 with Pydantic Versions 0.26 and 0.29 and should run as with no external dependencies beyond pydantic itself)
Foreseeable difficulties:

Hard to catch every combination and case to ensure doc is formatted correctly
Very dependent on the internal pydantic representation structure (See code where I have to check for pre 0.28 and post 0.28)
Requires overwriting doc variable
Documentation style could be in debate (e.g. NumPy, Google, reStructuredText, Epytext, etc.)
Not sure how this would effect speed
How to handle model nesting
How to handle mixed documented through Schema and not variables

Known issues with toy implementation:

Very crude
Does not support mixed Schema vs. non-Schema parameters
Nesting pydantic models requires the nested model to have its own Description
Have not tested all combinations of parameters
Formats to NumPy Docstring style
Formats some things to Sphinx cross-reference style (e.g. nested models get cast to :class: TargetClass instead of any further docstring description which would in Sphinx's RST format as a link to that class in the docs, not exactly helpful in all cases though)

from enum import Enum
from textwrap import dedent, indent
from typing import Tuple, Dict

from pydantic import BaseModel, Schema, confloat, BaseSettings, validator, ValidationError

####################################
# Start of Auto-Doc Generation block
####################################

class _JsonRefModel(BaseModel):
    """
    Reference model for Json replacement fillers

    Matches style of:

    ``'allOf': [{'$ref': '#/definitions/something'}]}``

    and will always be a length 1 list
    """
    allOf: Tuple[Dict[str, str]]

    @validator("allOf", whole=True)
    def all_of_entries(cls, v):
        value = v[0]
        if len(value) != 1:
            raise ValueError("Dict must be of length 1")
        elif '$ref' not in value:
            raise ValueError("Dict needs to have key $ref")
        elif not isinstance(value["$ref"], str) or not value["$ref"].startswith('#/'):
            raise ValueError("$ref should be formatted as #/definitions/...")
        return v

def doc_formatter(target_object):
    """
    Set the docstring for a Pydantic object automatically based on the parameters

    This could use improvement.
    """
    doc = target_object.__doc__

    # Handle non-pydantic objects
    if doc is None:
        new_doc = ''
    elif 'Parameters\n' in doc or not (issubclass(target_object, BaseSettings) or issubclass(target_object, BaseModel)):
        new_doc = doc
    else:
        type_formatter = {'boolan': 'bool',
                          'string': 'str',
                          'integer': 'int',
                          'number': 'float'
                          }
        # Add the white space
        if not doc.endswith('\n\n'):
            doc += "\n\n"
        new_doc = dedent(doc) + "Parameters\n----------\n"
        target_schema = target_object.schema()
        # Go through each property
        for prop_name, prop in target_schema['properties'].items():
            # Catch lookups for other Pydantic objects
            if '$ref' in prop:
                # Pre 0.28 lookup
                lookup = prop['$ref'].split('/')[-1]
                prop = target_schema['definitions'][lookup]
            elif 'allOf' in prop:
                # Post 0.28 lookup
                try:
                    # Validation, we don't need output, just the object
                    _JsonRefModel(**prop)
                    lookup = prop['allOf'][0]['$ref'].split('/')[-1]
                    prop = target_schema['definitions'][lookup]
                except ValidationError:
                    # Doesn't conform, pass on
                    pass
            # Get common properties
            prop_type = prop["type"]
            new_doc += prop_name + " : "
            prop_desc = prop['description']

            # Check for enumeration
            if 'enum' in prop:
                new_doc += '{' + ', '.join(prop['enum']) + '}'

            # Set the name/type of object
            else:
                if prop_type == 'object':
                    prop_field = prop['title']
                else:
                    prop_field = prop_type
                new_doc += f'{type_formatter[prop_field] if prop_field in type_formatter else prop_field}'

            # Handle Classes so as not to re-copy pydantic descriptions
            if prop_type == 'object':
                if not ('required' in target_schema and prop_name in target_schema['required']):
                    new_doc += ", Optional"
                prop_desc = f":class:`{prop['title']}`"

            # Handle non-classes
            else:
                if 'default' in prop:
                    default = prop['default']
                    try:
                        # Get the explicit default value for enum classes
                        if issubclass(default, Enum):
                            default = default.value
                    except TypeError:
                        pass
                    new_doc += f", Default: {default}"
                elif not ('required' in target_schema and prop_name in target_schema['required']):
                    new_doc += ", Optional"

            # Finally, write the detailed doc string
            new_doc += "\n" + indent(prop_desc, "    ") + "\n"

    # Assign the new doc string
    target_object.__doc__ = new_doc

########################
# Start of Example block
########################

class FruitEnum(str, Enum):
    apple = "apple"
    orange = "orange"

class Taxes(BaseModel):
    """The State and Federal Taxes charged for operation"""
    state: float = 0.06
    federal: float = 0.08
    city: float = None

class FruitStandNoDoc(BaseModel):
    """
    My fruit stand that I sell various things from
    """
    fruit: FruitEnum = FruitEnum.apple
    stock: int
    price: confloat(ge=0) = 0.6
    advertising: str = None
    currently_open: bool = False
    taxes: Taxes = Taxes()

class FruitStand(BaseModel):
    """
    My fruit stand that I sell various things from
    """
    fruit: FruitEnum = Schema(
        FruitEnum.apple,
        description="The fruit which I have available at my stand"
    )
    stock: int = Schema(
        ...,
        description="How many of each fruit to keep on hand"
    )
    price: float = Schema(
        0.60,
        description="Price per piece of fruit",
        ge=0
    )
    advertising: str = Schema(
        None,
        description="Advertising message to display"
    )
    currently_open: bool = Schema(
        False,
        description="Is the fruit stand open or not?"
    )
    taxes: Taxes = Schema(
        Taxes(),
        description="Taxes charged by the state and local level"
    )

print(FruitStandNoDoc.__doc__)
print('-'*20)
print(FruitStand.__doc__)
print('-'*20)
doc_formatter(FruitStand)
print(FruitStand.__doc__)

Outputs the following lines:
    My fruit stand that I sell various things from

--------------------

    My fruit stand that I sell various things from

--------------------

My fruit stand that I sell various things from

Parameters
----------
fruit : {apple, orange}, Default: apple
    The fruit which I have available at my stand
stock : int
    How many of each fruit to keep on hand
price : float, Default: 0.6
    Price per piece of fruit
advertising : str, Optional
    Advertising message to display
currently_open : boolean, Default: False
    Is the fruit stand open or not?
taxes : Taxes, Optional
    :class:`Taxes`

I'm not opposed to it, my questions/feedback would be:

how useful would this actually be? I think I only ever look at docstings in code
how much will it slow things down? Big python applications can become noticeably slow to load, we wouldn't want to slow things down by default
could we add a util function to do create/set a docstring so it has to be called manually?
we could have a config parameter defaulting to no that could be no / if_missing / always

Before we add it, would anyone else want this?

I think this would be pretty popular as it would interface with canonical Sphinx documentation tech. Effectively auto-docs so that you do not need to write this twice.
For speed, we could use the @property decorator so that the doc string would only be evaluated when called (often during docs generation or Jupyter notebooks).

I'm quite in favor of this, as I've been beginning to create docs for an API client I'm writing using Pydantic for data validation/coersion and such, and having to re-write my docstrings, especially for inherited models, is a bit tedious. I would gladly switch all my definitions to Schema()/Field() defs, if I could get auto-generated docs for each attribute.

See an example of the autogenerated docs here. This is something that we would still be quite interested in getting into Pydantic.

@dgasmith For what it's worth, you could implement it without modifying metaclass by making use of __init_subclass__; that would probably be preferable to prevent metaclass conflicts.
So ProtoModel would become:
class ProtoModel(BaseModel):
    def __init_subclass__(cls) -> None:
        cls.__doc__ = AutoPydanticDocGenerator(cls, always_apply=True)

@dmontagu Thanks! I was not aware of this.

@dmontagu 's comment was very helpful for finding a way to autogenerate my own documentation.  I really like the __init_subclass__ solution. After quite a bit of experimentation I feel like this would be afeature that doesn't have to be part of pydantic. Instead, what might be extremely useful is to simply add a little section to pydantic's documentation showing how a user could achieve this. A small example would suffice. If you decide this is a good approach I can submit a pull request.

Just a note, that environ-config library provides method generate_help, see https://environ-config.readthedocs.io/en/stable/tutorial.html#debugging (with implementation at https://github.com/hynek/environ-config/blob/0bd960a602878be39cdc24f2d52d2d767d5056a4/src/environ/_environ_config.py#L352 )

Just a note, that environ-config library provides method generate_help, see https://environ-config.readthedocs.io/en/stable/tutorial.html#debugging (with implementation at https://github.com/hynek/environ-config/blob/0bd960a602878be39cdc24f2d52d2d767d5056a4/src/environ/_environ_config.py#L352 )

Since this might be related, I created a sphinx autodoc extension called autodoc_pydantic that seamlessly integrates with sphinx autodoc to document pydantic models/settings. It is mainly based upon object inspection like reading field's description or alias attributes but uses standard doc strings.
We use pydantic settings for many applications but lacked a proper way to document them appropriately within our sphinx documentation (e.g. sphinx autodoc does not show default values for fields, it is hard to distinguish validators from standard class methods etc...). It might be helpful for you, too.

@mansenfranzen , autodoc_pydantic looks really great! Thanks for creating that sphinx autodoc extension! I found it the other day and have already started using it in my projects! It's also  definitely related to this issue!
There's one more thing, and I wonder if autodoc_pydantic can do it...
One of the ideas presented in this issue was wanting to be able to set the class's __doc__ string. That way, users can access the class's docstring by using, for example help(MyPydanticModel).
That way, if I were writing code  in a jupyter notebook I can type help(MyPydanticModel) to access the docstring.
Of course, there are pros and cons to setting a class's docstring, as discussed above. Moreover, If people are using tools like autodoc_pydantic, then who in their right mind would use help(MyPydanticModel)? They would instead browse the sphinx documentation!
Anyway, I was just curious what you think about it. Adding this capability (of setting a model's docstring) to pydantic is probably not wise. Offloading this functionality to tools like autodoc_pydantic seems much better, but now people must use Sphinx, and can't access their docstring via help()... so many pros and cons either way.

@nicobako I'm glad you're happy with autodoc_pydantic :-).
To support the ipykernel's help() function, I like the solution you already came up with (using __init_subclass__). This works at least for pydantic models that employ this functionality.
To provide the same functionality for all pydantic models regardless of whether they have the appropriate doc string or not, you'll need to overload/patch the help function. Monkey patching existing models does not seem appropriate to me.
Patching the help function should not be too difficult (even though also not very elegant). This functionality should be moved to a separate package, though. I don't think autodoc_pydantic should provide such functionality since it is mainly concerned with sphinx docs. However, the inspection methods and doc creation logic are common to both use cases (sphinx and jupyter's help). Hence, it could be also placed in autodoc_pydantic as two separate functionalities with different dependencies like pip install autodoc_pydantic[sphinx] and pip install autodoc_pydantic[jupyter].

@mansenfranzen sorry it has taken me a long time to respond to you.
I agree with you that autodoc_pydantic shouldn't support this functionality. I also agree that this functionality, if it came into being, should not be part of pydantic. Even if it were a separate package, the truth is that it would be very difficult to standardize how a pydantic Model gets represented as a docstring... We would have endless debates about whether to use numpy-style, google-style, etc.
 My hope is that it will give people the tools they need to implement custom autodoc functionality themselves.

What's the recommended way to get this feature in 2022? I am thinking about using pydantic to validate kwargs and generate document for it. Do I have to build this from scratch or are there some tools that could be used as a start point?

What's the recommended way to get this feature in 2022? I am thinking about using pydantic to validate kwargs and generate document for it. Do I have to build this from scratch or are there some tools that could be used as a start point?

Hey @link89 , I don't think there are any tools that will do this for you, but pydantic has a really nice API, and let's you introspect your models quite easily.
I wrote up a blog post a while ago on how you could builds this functionality yourself: https://blog.nicobako.dev/articles/pydantic_autodoc.html
I think you'll find building your own solution to be easy, and enjoyable!

See https://github.com/pydantic/pydantic-settings/issues/2 for a related
discussion.
On Mon, 28 Nov 2022, 19:55 Nico Bako, @.***> wrote:

What's the recommended way to get this feature in 2022? I am thinking
about using pydantic to validate kwargs and generate document for it. Do I
have to build this from scratch or are there some tools that could be used
as a start point?
Hey @link89 https://github.com/link89 , I don't think there are any
tools that will do this for you, but pydantic has a really nice API, and
let's you introspect your models quite easily.
I wrote up a blog post a while ago on how you could builds this
functionality yourself:
https://blog.nicobako.dev/articles/pydantic_autodoc.html
I think you'll find building your own solution to be easy, and enjoyable!
—
Reply to this email directly, view it on GitHub
https://github.com/pydantic/pydantic/issues/638#issuecomment-1329676890,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA62GGNTM2Z7MYWCJJQAT73WKUEZPANCNFSM4H5HSZ7A
.
You are receiving this because you commented.Message ID:
@.***>

I'll just note here that for compatibility with v2, you'll probably need to change from using __init_subclass__ to __pydantic_init_subclass__ since due to refactors in the metaclass, __init_subclass__ gets called before the fields are accessible. We added __pydantic_init_subclass__ explicitly to address this shortcoming, and it should function basically the same as __init_subclass__, it just doesn't get called until class creation is finished.
Because it seems that this issue has a good solution (namely, the docstring can be configured automatically in the __pydantic_init_subclass__), I'm going to close this issue now. But feel free to request it be reopened, or even better, create a new issue identifying precisely the change desired (as the target evolved a bit over the course of discussion in this issue.)

When https://github.com/pydantic/pydantic/pull/6563 is released (not in 2.6.0, unfortunately) use_attribute_docstrings in the model config will copy docstrings underneath field declarations into the field description.


ICS data missing correct TZ setup

Just used the TB meeting ICS link
http://arewemeetingyet.com/Los Angeles/2015-04-07/12:00/b/Thunderbird Meeting
Afais the ICS data is incomplete to resolve it for other timezones (like mine living in Germany).
You have
    DTSTART;TZID=America/Los_Angeles:20150421T120000

But there is no VTIMEZONE block like this:
    BEGIN:VTIMEZONE
    TZID:Europe/Berlin
    X-LIC-LOCATION:Europe/Berlin
    BEGIN:DAYLIGHT
    TZOFFSETFROM:+0100
    TZOFFSETTO:+0200
    TZNAME:CEST
    DTSTART:19700329T020000
    RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=-1SU
    END:DAYLIGHT
    BEGIN:STANDARD
    TZOFFSETFROM:+0200
    TZOFFSETTO:+0100
    TZNAME:CET
    DTSTART:19701025T030000
    RRULE:FREQ=YEARLY;BYMONTH=10;BYDAY=-1SU
    END:STANDARD
    END:VTIMEZONE

For an international meeting it makes sense to have it complete?

This should be fine given rfc 7809. Most clients support this. I'd suggest to close.

Yay, thanks for bringing in your spec knowledge!


Add Reviewer as member to an engagement

Description of changes:

Add Reviewer membership type and group
Add separate resource to fetch single user details
Refactor validation for user group

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #1721 (739ebee) into main (6c21381) will decrease coverage by 0.16%.
The diff coverage is 42.69%.

@@            Coverage Diff             @@
##             main    #1721      +/-   ##
==========================================
- Coverage   71.60%   71.45%   -0.16%
==========================================
  Files         371      371
  Lines       10965    11027      +62
  Branches      845      846       +1
==========================================
+ Hits         7852     7879      +27
- Misses       2981     3015      +34
- Partials      132      133       +1

Flag
Coverage Δ

metapi
78.82% <43.20%> (-0.36%)
:arrow_down:

metweb
64.94% <37.50%> (-0.05%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

met-web/src/apiManager/endpoints/index.ts
100.00% <ø> (ø)

met-web/src/models/user.ts
100.00% <ø> (ø)

met-api/src/met_api/services/staff_user_service.py
64.28% <27.77%> (-5.04%)
:arrow_down:

met-api/src/met_api/services/membership_service.py
43.75% <28.57%> (-6.25%)
:arrow_down:

met-web/src/services/userService/api/index.tsx
30.43% <28.57%> (-4.86%)
:arrow_down:

met-api/src/met_api/models/staff_user.py
89.47% <66.66%> (-1.27%)
:arrow_down:

met-api/src/met_api/utils/constants.py
73.33% <69.23%> (-26.67%)
:arrow_down:

met-api/src/met_api/resources/staff_user.py
76.25% <72.72%> (-0.90%)
:arrow_down:

met-api/src/met_api/constants/membership_type.py
100.00% <100.00%> (ø)

...s/userManagement/listing/UserManagementListing.tsx
95.65% <100.00%> (ø)


Optionally use public images

- Description of the problem which is fixed/What is the use case
Current build assumes the developer is a RH employee and uses images not publicly available.
Closes #268
- What I did

Updated Dockerfile to take images as arguments
Updated current make target to include (the same) images as arguments when building docker images.
Added make targets for building docker images from public images.

- How to verify it
Build with existing make targets:
make docker-build
make docker-buildx

Build with public images:
make docker-build-public
make docker-buildx-public

- Description for the changelog

Added support for building with public images for development and testing outside RedHat.

@cpmeadors @jensfr ptal

/ok-to-test

I am concerned with these changes.  I understand the desire to have everything build-able for the community.  No one thinks we should have private RH images required.  The problem I see is that this is working around a problem that cause by internal RH build processes.  The proper solution is to use all publicly available resources here and fix downstream.

/hold

/hold

Yes, I might have over-engineered a bit. 😀 I've simplified Makefile changes to simply allow overriding the images and added documentation to DEVELOPMENT.md with the appropriate public images.
The PR still does not address @cpmeadors comment about always having public images, but perhaps it's a step in the right direction?

@gkurz ptal

@gkurz ptal

Ack @bpradipt . Sorry @smuda  for the delay...


how to use without vpn

closed with https://github.com/iam4x/bobarr/commit/aaed3e58cd091f5604e1fa3038eddf7e1202e9bc


Onnx convversion

@bbepoch  thanks for opensourcing the code base just wanted to knw will support be given for onnx conversion of the pre trained model ? THanks in advance

It is not in our checklist, but welcome to contribute to this repo.


WearOS 2.0 support

Can this be used on smart watches? Although wearOS 2.0 supports HCE, it is not available after trying. I use Huawei Watch 2.0.

This sample has been deprecated/archived (check README for more information on newer samples related to this technology).
As recommended by GitHub, we are closing all issues and pull requests.


Overridable defaults

The defaults should be overridable.

Hi @retr0h, thanks!
I am not fully convinced of this approach, tho. My initial idea was to have the relevant parameters (ideally all the available parameters) configured inside the roles. Default values would be the defaults used by each project, according to the official doc. Then, you can override defaults using role variables.
So if you need to add more parameters, it could be better to add those and set them to openstack default value in defaults/main.yml

Hey @dguerri. IMO - the preferred approach to writing roles, is to provide all defaults in defaults.  They can then be overriden in host vars, group vars, inventory, or through parametrized roles.
I feel that the variabilization provides more flexibility.  People don't have to do it, but if they find they need to they can.

I don't know. Need to think a bit about it.
Defaults are already in defaults: you can override all of them just using role variables. And, in general, i would prefer to be more explicit (defining as much attributes as possible with default values).
I can see your point (the added flexibility) and I agree that replacing the set of attributes would be optional. But replacing them with a subset would make the solution more dependent from the initial configuration provided by the packagers.
Let's keep discussing, I am open to your solution.

@dguerri Yeah, once you start changing attributes, you are on your own, and I would assume you know what you are doing.  I would tend to agree with that.  It also means you can break things in bad ways too.
I don't have a particular use case at the moment to override these values.  I personally liked the code organization better with them in defaults, and could see myself needing to override options down the road.
Let me put this PR on hold.  I'm just now starting to integrate against these roles against OSP5, then quickly to OSP7.  Probably see a lot more from me in the future.  Including running Keystone behind Apache.

That's brilliant!


Exception if python binary != python2.7 on nodes

I'm using a modified AMI Amazon Linux AMI release 2015.09, which seems to default to python 2.6 when firing python. On cluster launch I get:
[<IP_ADDRESS>] Configuring ephemeral storage...
At least one node raised an error: Traceback (most recent call last):
  File "/tmp/setup-ephemeral-storage.py", line 158, in <module>
    non_root_block_devices = get_non_root_block_devices()
  File "/tmp/setup-ephemeral-storage.py", line 53, in get_non_root_block_devices
    block_devices_raw = subprocess.check_output([
AttributeError: 'module' object has no attribute 'check_output'

This is from using python 2.6:
root@ip-172-31-30-154 tmp]$ python26 --version
Python 2.6.9
root@ip-172-31-30-154 tmp]$ python26 setup-ephemeral-storage.py
Traceback (most recent call last):
  File "setup-ephemeral-storage.py", line 158, in <module>
    non_root_block_devices = get_non_root_block_devices()
  File "setup-ephemeral-storage.py", line 53, in get_non_root_block_devices
    block_devices_raw = subprocess.check_output([
AttributeError: 'module' object has no attribute 'check_output'

Python 2.7 is in the path but it isn't called
root@ip-172-31-30-154 tmp]$ python27 --version
Python 2.7.10
root@ip-172-31-30-154 tmp]$ python27 /tmp/setup-ephemeral-storage.py
{"ephemeral": ["/media/ephemeral0", "/media/ephemeral1"], "root": "/media/root"}

Python 3.5 also fails for me:
root@ip-172-31-30-154 tmp]$ python3.5 setup-ephemeral-storage.py
Traceback (most recent call last):
  File "setup-ephemeral-storage.py", line 171, in <module>
    format_devices(ephemeral_devices)
  File "setup-ephemeral-storage.py", line 102, in format_devices
    "Format process returned non-zero exit code: {c}".format(c=return_code))
Exception: Format process returned non-zero exit code: 1

Based on https://github.com/nchammas/flintrock/blob/master/flintrock/core.py#L481 and these exceptions, it seems like python from the PATH must be only 2.7 in order for for setup-ephemeral-storage.py to work.

Thanks for the report @ereed-tesla.
I did assume that setup-ephemeral-storage.py would run under Python 2.7, though I didn't call that out explicitly enough.
The problem with Python 2.6 is that it does not have subprocess.check_output(). That was added only in Python 2.7.

I'm using a modified AMI Amazon Linux AMI release 2015.09

I normally test Flintrock against vanilla Amazon Linux, where the default Python for ec2-user is 2.7.
Did you explicitly change the default Python when you created your custom AMI?

Required mitigation:

Provide a clean error message from setup-ephemeral-storage.py about supported Python versions.

Extra credit:

Make setup-ephemeral-storage.py compatible with Python 2.7+ and 3.4+. We should probably do this anyway for forward-looking Linux distributions like Fedora, where Python 3.4+ is the default and Python 2 isn't even installed.

What I'd really like to avoid:

Making changes for the sake of Python 2.6. RHEL be damned!

Ahaa I didn't see that comment. The base AMI is the present from around spark_ec2.py ~v1.4 (maybe earlier) -- Anaconda is installed so the default is python --version -> Python 3.5.1 :: Anaconda 2.4.1 (64-bit)
However, a .bashrc/.profile is not fired in the cluster launch script so the default becomes the AMI default of 2.6:
$ ssh root@XYZ python --version
Python 2.6.9

Ah, the spark-ec2 AMIs.
They are packed with lots of goodies, but they have not been updated in 2 years, lack a slew of security updates (no biggie for short-lived clusters, perhaps), and have many other rough edges like depending on you logging in as root.
My strong recommendation is to use something else. Is there something in particular about the spark-ec2 AMIs that you are looking for?

I agree. The main reason I'm testing using a variant of the spark-ec2 AMI is because it has all the dependencies/packages for my workflow setup (unrelated to spark), and since it works, I of course hasn't changed it. Thanks for the advice -- closing this issue.

No worries.
You may be able to recreate what you need with Flintrock pretty easily using vanilla Amazon Linux and a combination of Flintrock's copy-file (e.g. to upload a script) and run-command commands to setup stuff you need on the cluster.
I'll keep this issue open to address the error message and Python 3 compatibility that should be added, per my earlier comment.


doesnt work for ubuntu

try it on ubuntu none of the stick movement works

I've tried with Linux Mint, based from Ubuntu. Work perfect.
You should close Arduino IDE and similar Software and restart. Arduino catch the USB Ports and make it unusable for other Software.


Long descriptions are not visible in the expenses list on campaign page

Which area(s) of Podkrepi.bg are affected? (leave empty if unsure)
Campaigns
Describe the Bug
If the descriptions is too long - it cannot be easily read in the expenses list on the campaign page.

To Reproduce
You will need some expenses in order to be able to test it.
Best use an admin login.
Expected Behavior
May be we can add a mui popover when rendering the cell.
It would be best to extract this as a separate component.
Which browser are you using? (if relevant)
No response

is this the column you mean ?


Fixed KuzzleErrorPage

Fixes #329
An error prevented the KuzzleErrorPage to be displayed, which resulted in being stuck on the "Loading" page. The error is fixed.

Codecov Report

Merging #339 into 2.x will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              2.x     #339   +/-   ##
=======================================
  Coverage   77.02%   77.02%
=======================================
  Files          39       39
  Lines         753      753
=======================================
  Hits          580      580
  Misses        173      173

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 645912c...3dda834. Read the comment docs.


Make API filtering on a charfield be case insensitive

Relates to https://openscience.atlassian.net/browse/OSF-5029
Purpose
Filtering by filename in the API fails if you don't use the correct case.
As described on Jira by @brianjgeiger:
https://staging-api.osf.io/v2/nodes/ck8hm/files/s3/?filter[name]=Renamed will always fail, even if there's a file named Renamed, but https://staging-api.osf.io/v2/nodes/ck8hm/files/s3/?filter[name]=renamed will succeed.
Changes

When parsing the filter on a CharField, the API will make the query term lowercase
Add test to make sure that a search of the incorrect case returns the desired results

SideEffects
If any API filtering was relying on exact case of search terms for a charField, this will break.

@erinspace There's a lot of noise in the history for this PR. Can you please resubmit a new PR with commits containing only your changes?


Fix flaky CUDAarray tests

Close #4865. This patch is verified using the stress test (https://github.com/cupy/cupy/issues/4865#issuecomment-804272731).
There are two separate bugs fixed in this PR:

The copy routine in texture.pyx does not respect the current stream, leading to surprises.
The tests in test_texture.py generate input data on the default stream, but run the copy routine on a separate stream without first establishing a proper stream order.

Both have to be fixed to make the stress test pass.
I also did a few cosmetic changes in test_texture.py that were not possible with older dependencies. Should be obvious ones.

Jenkins, test this please

Jenkins CI test (for commit a9def844eeb81098f40c95ee70d73da086bc2910, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit a9def844eeb81098f40c95ee70d73da086bc2910, target branch master) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit a9def844eeb81098f40c95ee70d73da086bc2910, target branch master) failed with status FAILURE.

pfnCI, test this please.

Jenkins CI test (for commit a9def844eeb81098f40c95ee70d73da086bc2910, target branch master) failed with status FAILURE.

OSError: [Errno 28] No space left on device

Ithink it is ok to merge this

Thanks @emcastillo!


Unable to render a Dynamics 365 account record in a Teams Stage view

I am trying to render a stage view with the url that redirects to a Dynamics 365 account record, currently when I follow the Microsoft Documentation and pass the Dynamics 365 encoded URL of an account entity, I see a pop with message - {Teams app name} is unable to show this view
Contact your IT admin if the problem persists.
I have added the domain "*.dynamics.com" in the valid domain section in the app manifest too.
My objective is to render a Dynamics 365 url using a Teams Stage view

App name - Peppermint Connect new local

This question is tracked on https://techcommunity.microsoft.com/t5/teams-developer/microsoft-teams-stage-view-fails-to-load-dynamics-365/m-p/3604341#M6251. We are closing this issue here.


Investigate failure scenario when groupmessage is unable to find a peer's pubkey

Report from @rodkeys:

Moderator dispute conversation: I sent a message in a dispute case, recipients confirmed receiving and seeing the message but message cannot be seen by me (the moderator) after re-loading the order discussion page
Here's what else I'm seeing if this helps: After sending my message to the vendor my client has been frozen and any other page I attempt to go to, whether it's my store, someone else's store, etc, basically any API call, refuses to load and I am stuck looking at a loading symbol for the last ~20min
The dispute was caused because the vendor has been offline/unresponsive. From what I know the vendor has been offline for a long time
The dispute resolution seemed to have worked, the buyer accepted the resolution and the transaction went through* (edited)
The group message is what started the issue AFAICT, instead of failing gracefully it seems to lock up the client for a really long time

Next steps:

[ ] investigate root cause and post findings

Thanks Mike, I'll add a quick edit to my post that only the buyer confirmed receiving/seeing the message. I have not heard anything from the vendor side and I assume they never saw the message.


Remove casm from StarknetContractArtifactPaths

We should never load it from scarb, always use the usc to simplify the logic and make the contract safer (scarb does not guarantee anything about casm)

We should just aways compile here
https://github.com/foundry-rs/starknet-foundry/blob/6ae992c45c937a640cb8f90e38c610e75b8b7192/crates/scarb-api/src/lib.rs#L56


AUDIT: Various kinds of observations

Surfaced from @informalsystems audit of Stride at commit f9736fe0

finding:
id: IF-STRIDE-OBSERVATIONS
title: Various kinds of observations
severity: Informational
impact: None
exploitability: None
type: Implementation
issue:
status: Unresolved
Description

There are no invariants defined in Stride codebase. In the context of the Cosmos SDK, an Invariant is a function that checks for a particular invariant at the end of each block. These functions are useful to detect bugs early on and act upon them to limit their potential consequences (e.g. by halting the chain). They are also useful in the development process of the application to detect bugs via simulations.
Simulation tests not implemented. The Cosmos SDK offers a full-fledged simulation framework to fuzz-test every message defined by a module. Although Stride modules contain scaffolded skeletons for simulation messages, they are not implemented (e.g. LiquidStake msg):

    func SimulateMsgLiquidStake(
  ak types.AccountKeeper,
  bk types.BankKeeper,
  k keeper.Keeper,
    ) simtypes.Operation {
  return func(r *rand.Rand, app *baseapp.BaseApp, ctx sdk.Context, accs []simtypes.Account, chainID string,
      ) (simtypes.OperationMsg, []simtypes.FutureOperation, error) {
    simAccount, _ := simtypes.RandomAcc(r, accs)
    msg := &types.MsgLiquidStake{
      Creator: simAccount.Address.String(),
    }

    // TODO: Handling the LiquidStake simulation

    return simtypes.NoOpMsg(types.ModuleName, msg.Type(), "LiquidStake simulation not implemented"), nil, nil
      }
    }

HostZoneUnbonding's status EXIT_TRANSFER_QUEUE was set twice, before and after burning stTokens during UndelegateCallback.

SetWithdrawalAddressOnHost is being called on every epoch.

Flags: HostZoneUnbonding_UNBONDING_IN_PROGRESS and HostZoneUnbonding_EXIT_TRANSFER_IN_PROGRESS seem to be unused.

Problem Scenarios
Recommendation

Think about adding some invariants. Describe and check conditions on Stride which should be fulfilled at every block execution or on every epoch.
If there is a need for fuzzy testing, you could utilize cosmos sdk simulator by implementing messages of interest. These are simulated with random field values. The sender of the operation is also assigned randomly. The simulator can test parameter changes at random as well. Finally, you could create a randomized genesis file.
Consider representing amount fields with string type (if their type int64 or uint64). The way protobuf json marshaling works, it encodes the uint64 as a string. This also allows for larger amounts such as uint256 to be sent across chains. An example of this approach can be found in proto/ibc/applications/transfer/v2/packet.proto:

message FungibleTokenPacketData {
  // the token denomination to be transferred
  string denom = 1;
  // the token amount to be transferred
  string amount = 2;
  // the sender address
  string sender = 3;
  // the recipient address on the destination chain
  string receiver = 4;
}

Set HostZoneUnbonding's status EXIT_TRANSFER_QUEUE either before or after burning stTokens during UndelegateCallback.
SetWithdrawalAddressOnHost should not be called on every epoch.
Define only necessary flags for HostZoneUnbonding_Status. Probably HostZoneUnbonding_UNBONDING_IN_PROGRESS and HostZoneUnbonding_EXIT_TRANSFER_IN_PROGRESS should be removed.

@asalzmann do you know what they mean by the last bullet

Define only necessary flags for HostZoneUnbonding_Status. Probably HostZoneUnbonding_UNBONDING_IN_PROGRESS and HostZoneUnbonding_EXIT_TRANSFER_IN_PROGRESS should be removed.

I think those are used (implicitly) and should not be removed. They're also useful for our monitoring

Yes, it's used implicitly. For example, here https://github.com/Stride-Labs/stride/blob/0dbbbd867ffad5b331d09c155dca53a3f581ad5c/x/stakeibc/keeper/unbonding_records.go#L295
If we didn't have another state, we wouldn't know which records to process. It's also useful for monitoring. Removing that comment here and will ping informal/

Yeah I think so @sampocs , I have checked it and commented I this https://github.com/Stride-Labs/stride/issues/525


Add Ollama compatibility

Hello,
I use Olama locally and I quickly looked into making SystemSculpt compatible. Since Olama already supports the OpenAI API for messages, only the models retrieval needs to be adapted.

The API "/v1/models" should be replaced with "/api/tags" and the mapping needs to be slightly modified as the response format is not exactly the same, for example:

if (response.status === 200) {
  const data = response.json;
  return data.models.map((model: any) => ({
    id: model.name,
    name: model.name,
    isLocal: true,
    provider: 'local',
  }));
}

In ModelSettings.ts, I simplify getAvailableModels() to use AIService.getModels() instead the current duplicate implementation.

=> Tada, it works like a charm for me.
Maybe it can help you to add ollama support in next release.
source:
https://github.com/ollama/ollama/blob/main/docs/api.md#list-local-models
Regards

Great insight! Will include this in the next update, 0.4.3. Cheers! Thanks so much for the great info, highly appreciated.

@ncoquelet just implemented in the latest 0.4.5 release, let me know if everything works well (ollama doesn't allow for streaming without going through a lot of hoops currently, hopefully that changes in the future, for now it generates the response in entirety before pasting it in as the answer)


Fix Issue121 122

Pull Request (PR) description
Fixes issue #121 - Max password age fails when setting to 0
Fixes issue #122 - Domain_controller_LDAP_server_signing_requirements - Require Signing
This Pull Request (PR) fixes the following issues
Fixes issue #121
Fixes issue #122
Task list

[x] Added an entry under the Unreleased section of the change log in the README.md.
Entry should say what was changed, and how that affects users (if applicable).
[x] Resource documentation added/updated in README.md.
[x] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[x] Comment-based help added/updated.
[x] Localization strings added/updated in all localization files as appropriate.
[x] Examples appropriately added/updated.
[x] Unit tests added/updated. See DSC Resource Testing Guidelines.
[x] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #125 into dev will decrease coverage by <1%.
The diff coverage is 83%.

@@        Coverage Diff         @@
##           dev   #125   +/-   ##
==================================
- Coverage   89%    89%   -1%
==================================
  Files        5      5
  Lines      493    497    +4
==================================
+ Hits       443    446    +3
- Misses      50     51    +1


[Wrong Version Reported] - Health Checker

Provide Version Number
<IP_ADDRESS>6
Describe the issue
Health Checker is reporting the wrong Exchange version number. I am on Exchange 2019 CU10, it is reporting Exchange 2019 CU11.
Expected behavior
It should report the correct Exchange version and CU #.
Sample Output:
Name: EXCH_2019_SERVER
Generation Time: 01/31/2022 20:52:36
Version: Exchange 2019 CU11
Build Number: 15.02.0922.020

@CAFMATS could you please run the script with the -SaveDebugLog switch and share the log via ExToolsFeedback[at]microsoft[dot]com ?


“Websocket” communication specification. Alternative (non-REST) way to communicate

Hi everybody,
Dunno if OpenAPI guys are interested in that thing. Maybe HTTP2.0 going to replace websocket and we can easily forgot about this topic. anyways...
Client can receive messages even without sending any requests. It can be some status messages, chat messages, or whatever you want.
This is full duplex connection. So it’s two way communication. Client can send messages and receive response for it. Can send messages and not wait for response (unbelievable situation, but why not). Client can wait for messages from server and not send any request to server. When it receive message from server, then it can send back to server response message.
Websocket connection is alive for the whole runtime lifecycle of the application. This is the main goal in most scenarios
We have new keyword - "message". It is not request or response. It is message. And we need also mechanism to answer with messages to some messages, if we need it, in any direction.
With best regards,
Artem

https://github.com/swagger-api/swagger-socket/issues/47#issuecomment-163627431

this is good article to understand the difference
https://blogs.oracle.com/PavelBucek/entry/websocket_vs_rest1
and understand that it is not really replacement of REST, but simply another technology to communicate
this is very good presentation also - https://www.youtube.com/watch?v=B-ElrhYxPQU1 - on 25 min they talk about SOAP on websocket. very interesting to investigate

You can kind of represent it like this:
https://github.com/swagger-api/swagger-spec/issues/396

Okay. But what it gives to represent it in swagger, but without tooling? more interesting is to extend swagger api and then extend tools. I'm 100% ready to do it. Just want to ask for help from community to show me some starting point or whatever.

Ok but it starts with somebody making a proposal, this is my shot at that proposal. If people like it, we can agree on it being a worthwhile extension and add it to tooling.

Parent issue #586

Agree, should be added as the specification part.

+1 anyone is working on this?

Too bad that there is no news about it. Will have to write it manually like a simple html doc or something like that...

@gioppoluca @Somebi To my knowledge, no.  There are lots of other HTTP specific issues that we are working on first.
To be honest, I don't really understand why someone would want to take a specification designed for describing a HTTP API and then try and use it to describe a non-HTTP API.  The existing HTTP constructs are just going to get in the way of describing the websocket payload and if extensions were made to support websocket description it would just add complexity for those people trying to describe HTTP APIs.
It would seem to make more sense, to create a new spec for websockets.  Perhaps someone could fork the existing spec and create a variant designed specifically for websockets.

why is http different from websockets?
Isn't swagger just a way to describe a contract for an API that just happens to default to the http transport?
the message is
method, path, version
headers
body
sent over tcp
I can do that with many different transports. This message format is almost a 1:1 match amqp for example.

@casualjim HTTP isn't a transport, it is an application protocol.  The HTTP methods have semantic meaning, as do the status codes and the HTTP headers.  Sure, if you want to re-implement HTTP message semantics over web sockets, then you can use Open API to describe it.  But then what is the point of using Web Sockets.  If you try and reuse HTTP messaging then every time you try and take advantage of the benefits of Web Sockets you are going to run into unspecified areas of HTTP.  Web Sockets exists in part to enable bi-directional communication which isn't supported in HTTP.  Web sockets is effectively a transport and requires you to build an application protocol that will take advantage of the capabilities it enables.
WSDL was a way to describe a contract for an API that was independent of transport. OpenAPI isn't.

Interesting, because I thought that webhooks etc all serve as the bi-di side. So squinting a bit you can get the bi-di communication flow using various http supported additions, as we can see in a number of other issues.
https://github.com/OAI/OpenAPI-Specification/issues/770
https://github.com/OAI/OpenAPI-Specification/issues/716
https://github.com/OAI/OpenAPI-Specification/issues/396

Webhooks require an explicit step where a call back URL is registered and the return call is standard request/response.  It is publish/subscribe convention that has been layered on top of the HTTP semantics.
HTTP/2 push is not bi-directional, it is simply a server initiated prediction of a future request and piggybacking one response on another.  Again in that issue I argued against any native Open API description of it.
SSE is very much a new application protocol that can be squeezed into HTTP using long polling.
Personally, I don't believe SSE payloads should be natively described by OpenAPI.  This is consistent with the fact that in the callbacks PR there is no specification of payloads for event identification and subscription formats.  I think standardization of WebHooks would be a great thing, I just think that standardization effort should be independent of the OpenAPI spec.
These are just my opinions, I'm not making any claims about OpenAPI will do in the future.   I'm just saying what I think is best for the long term success of OpenAPI.
I realize that there are lots of valuable features that could be added to OpenAPI, but scope creep can be a real problem in spec design.

+1

We have a service that combines REST and Websockets. They work together and are part of a single application.
For us, if there was just a way to add a new operation, like message we could use OpenAPI to describe the main aspects of our web socket interface. It would get us at least 90% of the way there as we could describe the body of the message, its use, etc.

@rberger What kind of information would you like to describe in an operation that you currently cannot do?

@darrelmiller Isn't websocket built on top of http? Handshake is implemented on http level if i'm not mistaken.

Only the negotiation

We cannot create one json document where http and websocket will be described. Have to generate http spec separately and then modify and fill it already at UI/docs stage... Would be nice if docs generate one spec for http and websocket.

Agree with @Somebi, it would be useful feature. My projects on Spring framework, usually, have two endpoints for the same action: one with ReqeustMapping (http) and one with MessageMapping (websockets). It would be very nice if I had both together in generated docs.

May I suggest a limited goal of supporting the WebSocket handshake interaction, which is HTTP.    I'd like to specify that a certain operation initiates a websocket connection.    The initial handshake can be understood as a normal REST request with additional request headers, resulting in 101 - Switching Protocols.   It would be nice to articulate that at a high-level way rather than in a literal way.
I see a few open issues that mention websockets, but all seem to relate to post-handshake communication.

I believe that usage of both HTTP REST APIs and WebSockets are quite common in modern web applications, especially with the popularity of highly interactive and dynamic SPA applications (Angular/React).
From the developers perspective it would be extremely useful to have a single instrument (standard/specification) to define both styles of our web APIs because we are working with a single domain model and it would be great to share common properties, schemas and definitions (e.g. OAS components) and to not duplicate them in two different specifications. Open API itself is a very good effort to standardize the documentation and modelling processes of modern web APIs and it would be a good pragmatic step to take WebSocket (or it's abstraction) under the hood as well.

@darrelmiller this is indeed exactly what the industry needs! The reality (one that the maintainers of the OpenAPI spec seems finding hard to acknowledge) is that most API's out there are a mix between synchronous REST + synchronous Pub/Sub. The addition of web-hooks is actually only a small commitment to acknowledge that reality, not nearly enough to cut the deal.
In the meanwhile, many companies are maintaining in-house developed solutions to cover this obvious gap.
Any plans to integrate https://www.asyncapi.com in a v4 of the OpenAPI specification?

@boeboe

The reality [...] is that most API's out there are a mix between synchronous REST + synchronous Pub/Sub

are there numbers available which support that? Possibly the range of API's currently being described by OAS is self-selecting out this majority, but I slightly doubt it.

Any plans to integrate https://www.asyncapi.com in a v4 of the OpenAPI specification?

Lines of communication are open between OpenAPI and AsyncAPI folk, but the exact nature of future collaboration is still being discussed.
@slavafomin

it would be great to share common properties, schemas and definitions (e.g. OAS components)

OpenAPI 3.x and AsyncAPI 1.x are very closely aligned today, and there should be no problem sharing common components such as schema objects between the two using external $refs.

@MikeRalphson
In a microservice context with a high degree of spokes, REST is often abandoned in favor of losely coupled pub/sub. Currently PACT is adressing this issues on the testing part (PACT files are not really contracts like OAS, although they won't agree... it's really just a BDD tool).
Towards public facing API's I agree with your statement of majority.  Given the fact that MS architectures are being deployed so often... there is truly a gap in the contractual space. One option is Avro schemas from kafka... but this would result in maintaining 2 contracts per microservice... one for sync, one for async.
Really curious on your view on this? Just can't really see a downside for OAS to also embrace async...

@boeboe The maintainers of the OAS do recognize there is an industry need to describe async/messaging APIs.  We have spent a significant amount of time discussing how the OAI can help.  AsyncAPI is a great effort that shares many concepts with OpenAPI and is sufficient for many people's needs.
The challenge that OAS faces is that currently it describes an HTTP API using HTTP semantics.  Many messaging/async APIs don't use those same semantics.  Blending the two sets of distinct semantics into a single spec might be the best solution, or creating two distinct specs that can reuse elements from each other may be the better solution.  We have not yet been able to reach consensus on this.
Rather than rathole on the topic, we have been working on other hopefully easier challenges like alternativeSchemas, encryption/signing, overlays, client certificates and conformance testing.  There is no lack of desire to address the needs of the async community, but at the moment, AsyncApi is doing a good job of that on its own and we have only so many hours in the day and so many hands.
Additionally, describing APIs that are not "REST" styled APIs is currently not in the charter of the OAI.  Therefore we need to update our charter in order to bring this work into scope.  Hence, the problem is more than just a technical one, it becomes an issue for all of our corporate members.  We have done work towards the goal of broadening the scope of our charter, but as soon as you open this door, the follow-up question is how broad should it be?

@darrelmiller Thanks for suggesting Async API, for us who want to support a specification with Websocket and asynchronous APIs.
Although, I second @slavafomin 's point that we need one tool that will describe our whole API instead of seperating our API into multiple products of multiple different tools made with different specifications. At one point it really gets troublesome and confusing to deal with more than one specifications for just one objective (API specification).
Let alone companies who may have the people to support that, but for a small team of people or individuals, it gets expotentially harder to support specifications when we are in need for them, if we have to deal with many tools at once for doing one job.
Of course, you may have other priorities for now, but I and I suppose other developers would support much the decision of OpenAPI supporting Websocket specification. After all, its name is OpenAPI, not httpAPI. :P Thanks for your work nonetheless.

Totally support this, and additionally support features to add RPC specs (refs #801). These two additions would make OAS a functionally complete documentation language for all modern API schemes except GraphQL, which is self-documenting and I don't see much of a need to include in the OAS. Would love to see some movement here.

Hi. I think swagger may be just enough to describe websocket/subscription/notifications. In short: client behave itself as a server (so it can receive regular rest calls from server).
How I see this:

create server schema for server operations
create client schema for client operations
Generate 4 stubs

Now server provide rest api endpoint, so client can call it using generated client code. Client can call "subscribe" function for example.
And client provide rest api endpoint, so server can use generated client code to access client operations (basically push notifications).
So all what is needed is support for a protocol (HTTP/2, or websocket). And generating server/client stub, which gonna support this flow.

And client provide rest api endpoint

Doesn't work for browsers which can only act as a http client or websocket client.
The same is true for phones and other clients that are behind a firewall/NAT (so most consumer devices) because they can only act as a TCP (which includes http & ws)/UDP client(/initiating party).
Reverse tunneling for example would be possible for the latter but that's not really supported by most technology stacks (and far from ideal).

Duplicate of https://github.com/OAI/OpenAPI-Specification/issues/55

is there a limitation of url length of websocket protocol? or is there a limitation of url length of websocket client for code implementation？


Upgrade Azure Storage Blob Client and Support OAuth2 for Storage Account

Hello,
This originally for my own use case but might be useful to merge it back. Please contact me if further discussion is needed.
The change is mainly migrating authentication method from storage key to MSI-based oauth token, as I feel it's a security risk to store secret in a file and look for similar experience of fluentd-s3, which relies on instance profile to auth s3 buckets.
Changes involved:

Upgrade Azure SDK to azure-blob-client 1.1.0. At the time of write Azure SDK is divided into submodules and distributed separately. Blob client is the only one needed here.

Introduce new config params azure_instance_msi and azure_oauth_refresh_interval to support OAuth, details is added in Authentication section in readme.

Change config param auto_create_container to false, now Azure by default makes container private, returns 404 for get_properties, and invalidates ensure_container(). Hence users need to adjust the properties of their account if they'd like to enable creation. Making default value to false to enforce user to be aware of this fact.

Consolidate all commits in another pull request.


Get-CsUserCallingSettings fails when a delegate has been deleted from AzureAD

Hi,
The Get-CsUserCallingSettings fails when a user is removed from office 365. If it cannot lookup the object id the whole command fails;
Example;
PS > Get-CsUserCallingSettings -Identity<EMAIL_ADDRESS>Get-CsUserCallingSettings : Exception occured while trying to resolve delegate identity. Fix the identity before trying again. 63xxxxb-exx1-4xx-bcbd-0dxxxxxf1942
To reproduce add a delegate to a user and then delete the delegate from Office 365.
The only way to fix this is via the Teams client

@dappleby300 Thanks for the feedback. Yes, this is a known issue that we are working to address. The work-around is to remove the delegate using the ObjectId being shown.
An example:
Assume<EMAIL_ADDRESS>with ObjectId 8480c6e7-0507-4eaa-8394-bc46aefba8ec has<EMAIL_ADDRESS>with ObjectId 481efae7-f1c9-407f-8cf4-6ee41049fae3 as a delegate.
<EMAIL_ADDRESS>is removed from Microsoft 365 (soft-delete which means the account stays around for 30 days).
Get-CsUserCallingSettings -identity<EMAIL_ADDRESS>will show
Get-CsUserCallingSettings : Exception occurred while trying to resolve delegate identity. Fix the identity before trying again. 481efae7-f1c9-407f-8cf4-6ee41049fae3
The work-around is to use Remove-CsUserCallingDelegate with the ObjectId, like Remove-CsUserCallingDelegate -Identity<EMAIL_ADDRESS>-Delegate 481efae7-f1c9-407f-8cf4-6ee41049fae3
The work-around also works for the reverse scenario.
When the user is hard-deleted (after 30 days or explicitly), the situation cures itself.
Feel free to close this issue.

@dappleby300 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Thanks for the info.


fix: #1583 mismatch language condition when rendering unpublish

Description
Fixes https://github.com/payloadcms/payload/issues/1583
The variable statusToRender is assigned the translated value which is then being compared to the English counterpart to conditionally render the button.
This pull assigns the statusToRender using English and then renders the translated values when used in the DOM

[ ] I have read and understand the CONTRIBUTING.md document in this repository

Type of change

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

Checklist:

[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Existing test suite passes locally with my changes
[ ] I have made corresponding changes to the documentation

This looks great, thank you!


Sometimes builder works without redstone signal

At least with this setup

If there is a log a redstone signal is given.
But the builder keeps running and breaks the sapling.

What are the settings of the builder? On ForgeCraft 2 I did something similar but I used a piston to move the tree up as soon as it had grown so that the sapling was always out of reach of the builder

keep running with redstone signal.
I fixed it by breaking the lowest log with an usual block breaker


[Godot 4] Polygon 2d texture messing up

Godot version
v4.0.beta5.official [89a33d28f]
System information
Manjaro Linux Xfce, GLES3, AMD RX 580
Issue description
Creating 2d polygons with texture assigned (following the 2d skeleton tutorial) in the 4.0 beta renders some of the polygons incorrectly:

There are no bones, simply a couple of polygon 2ds with texture and UV points setup. Some polygons become messed up, some seem to be fine.
A way to 100% break a polygon, is by assigning a 2d skeleton (event empty one, without any bones and without assigning any weights).

Steps to reproduce
The project is very very simple, just a 2d scene with a couple of polygon 2ds.
Simply opening it should break the polygons, if not, assigning a skeleton to them should do the trick.
I have been able to reproduce this on two different computers, one running Manjaro Xfce on full AMD, one running custom Manjaro with tilling window manager running on intel GPU.
Minimal reproduction project
example.zip

When I was looking through possibly related issues, I got to this one https://github.com/godotengine/godot/issues/59451, which seems like the same bug, but it was closed in March and also related to Vulkan + mobile.

This was fixed in beta 6: see the release post here: https://godotengine.org/article/dev-snapshot-godot-4-0-beta-6

Ah my bad, completely missed the release, sorry!


(For David) Creates SiftImpl class, removes instance API, adds resume hook

This PR does several things:

Moves instance logic out of Sift and into SiftImpl
Adds onResume hook
Adds new activity to test app

TODO: update README.md and marketing site docs. Also, write how-to-upgrade doc to accompany new GitHub tag.


BUG: NotificationHistory being passed instead of Notification (Prod)

Describe the bug
send_complaint_to_vanotify.apply_async(
        [str(complaint.id), notification.template.name],
        queue=QueueNames.NOTIFY
    )

AttributeError: 'NotificationHistory' object has no attribute 'template'
This method expects notification to be Notification type. For some reason it's sometimes appearing as a NotificationHistory object.
Track down what could cause it to look up the history and implement a solution.
To Reproduce
I'm uncertain of the behavior to reproduce. There are logs however.
Expected behavior
AttributeErrors are not raised and the complaint is handled appropriately.
Screenshots

Additional context
CloudWatch log

Hey team! Please add your planning poker estimate with Zenhub @EvanParish @jakehova @ianperera @k-macmillan

Still an issue, per Kyle.


Feature/sanitizer

New pull request with asan build and llvm coverage

Codecov Report

Merging #20 into develop will decrease coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop      #20      +/-   ##
===========================================
- Coverage    99.29%   99.29%   -0.01%
===========================================
  Files          246      246
  Lines        20020    20019       -1
===========================================
- Hits         19879    19878       -1
  Misses         141      141

Impacted Files
Coverage Δ

ATK/EQ/ToneStackFilter.h
100% <ø> (ø)
:arrow_up:

ATK/EQ/TimeVaryingSecondOrderSVFFilter.h
100% <ø> (ø)
:arrow_up:

Python/ATK/Special/Special.cpp
100% <ø> (ø)
:arrow_up:

ATK/EQ/PedalToneStackFilter.h
100% <ø> (ø)
:arrow_up:

Python/ATK/EQ/SecondOrderFilter.cpp
100% <ø> (ø)
:arrow_up:

ATK/Tools/OversamplingFilter.h
100% <ø> (ø)
:arrow_up:

Python/ATK/EQ/MainFilter.h
100% <ø> (ø)
:arrow_up:

Python/ATK/EQ/TimeVaryingIIRFilter.cpp
100% <100%> (ø)
:arrow_up:

Python/ATK/EQ/EQ.cpp
100% <100%> (ø)
:arrow_up:

Python/ATK/Tools/Tools.cpp
100% <100%> (ø)
:arrow_up:

... and 2 more

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 ba42530...98ccc9d. Read the comment docs.


Default file open configuration

Opening this just for discussion.
See https://github.com/Tolriq/CatSpy/commit/8dd18e0ea76bfeac62918ae49f34823825428faf
Usually details view + sort by most recent change is the most needed default values to open logs.
Since it bothered me a lot to do tons of click I've quickly added this hack, but maybe there's something to be done here as default or setting?

It supports dragging file into HomePanel or FileLogPanel

I'm under Gnome wayland with half pop_os cosmic and drag and drop fails for many use cases. But I guess it can works for the others so no need to add this on your side so.I'm under Gnome wayland with half pop_os cosmic and drag and drop fails for many use cases. But I guess it can works for the others so no need to add this on your side so.


Introduction to the MongoDB and Mongoose Challenges: Glitch link to boilerplate broken

Describe your problem and - if possible - how to reproduce it
The Glitch link to the boilerplate in the challenge gives error sometimes
Project Not Found
Maybe a typo? Or maybe it's been renamed?

Issue seems similar to #17971
Add a Link to the page with the problem
Challenge link: https://learn.freecodecamp.org/apis-and-microservices/mongodb-and-mongoose/
Glitch link: https://glitch.com/#!/import/github/freeCodeCamp/boilerplate-mongomongoose/
Tell us about your browser and operating system

Browser Name: Chrome
Browser Version:  68.0.3440.84
Operating System: Windows 10

If possible, add a screenshot here

@ezioda004 The link worked for me, perhaps it has been fixed - are you still having problems?

@moT01 No, but it happens sometimes I suspect its because as mentioned in this thread https://github.com/freeCodeCamp/freeCodeCamp/issues/17586 all the boilerplates have node engine explicitly set at 4.4.5 which is no longer supported by glitch.

There's also bunch of errors in the console due to this
Maybe thats why it happens?

The link is not broken anymore but I would suggest changing the link color previous to being clicked or to put some text decoration like underline or so, in order to jump to eyesight easily.
I lost so much time in this challenge due to not using the correct boilerplate as the tests did not pass even if my code was correct for the exercise. I'm sure I'm not the first one with this issue.
Also, the engines portion of package.json should definitely be changed to at least node 10 or completely removed so glitch can run the code.

I am closing this issue as the link and page have changed completely, and the issue is no longer present.


Able to view the whole source code in the production build when I run it locally using pushstate-server

Able to view the whole source code of the project in the chrome debugger when running the build using pushstate-server. Not sure whether this is a known issue or an expected behavior.
NOTE:
I haven't ejected the project.
Steps to reproduce:

Initialize a project with CRA create-react-app testApp
Run yarn run build to bundle the project
Deploy the build using pushstate-server using pushstate-server build
Go to localhost:9000 and go to sources in chrome debugger.

Now go to sources and see the following path top -> webpack:// -> . -> src.
Actual Behavior
Here you can see the whole code of the project in the production build.
Expected Behavior
The source code is not supposed to be exposed in the production build.
Discussion
Can anyone confirm whether this is a bug or just an expected behavior.
The following image shows the code when I deployed the project locally using pushstate-server

This is expected. You can delete .map files from the build output if you want to disable it, although you'll get console warnings about them missing.
There is no harm in leaving them in though in my opinion. Client code is already available to the user’s machine so there’s no secrets in it.

Just wanted to know, thanks for the clarification @gaearon