Inner class issue:  NullPointException

class A{
public class B {}
}
A a = JSONObject.parseObject("{}", A.class);    // it works
A.B b = JSONObject.parseObject("{}", A.B.class); // will throw NullPointException

你试试，new B 出来看看，这个是你语法问题。不是fastjson
然后我觉得，fastjson不需要支持这种问题。

Here i provide a easy way to handle it.
See https://github.com/ianate/fastjson/blob/directInner/src/main/java/com/alibaba/fastjson/parser/deserializer/JavaBeanDeserializer.java
it's not perfect and you can improve it on your own.
But in my opinion, once you define the class as a inner class, you should use it as a inner.
so i don't think you really need that solution. i do it simply because Gson can deserialize it normally, and there will be not PR.
我觉得既然你要将其定义为内部类，那你应该只把它作为内部类来使用

这个内部类用static的修饰

does it work with
A a = new A();
// Have seen this syntax
A.B b = a.new B();
JSONObject.parseObject("{}",a.B.class);


test: fat incomplete

[x] Missing new test system (test.py)
[x] Missing README
[x] Does not compile
[x] Automation (port test.sh to python?)

This is actually two tests in one. Should we split this up into either two folders or two sub-folders?
test/fat16
test/fat32

or
test/fat/fat16
test/fat/fat32

This is now fixed. fat is now split into fat16 and fat32. If someone wants to put them in a subfolder, go ahead, and have fun with pathing 😉


Should Template.render() return a safe string?

I just stumbled upon an interesting difference between Jinja2 and the Django template language.
Template.render() returns a safe string in Django. It's likely an accident of the implementation more than a design choice. It happens because NodeList.render() calls mark_safe() on its output, even at the top level.
I believe that Template.render() doesn't return a safe string in Jinja2. To achieve this effect, one would have to wrap the return value here in Markup().
It's unclear to me that one behavior has significant advantages over the other. I thought I'd bring it up here in case someone has an opinion.
It would be nice to resolve this inconsistency because it can cause non-trivial bugs such as https://github.com/torchbox/wagtail/issues/2541.

Rendering a template could produce an unsafe string, we don't know how it's going to be used after rendering.  Seems better to be explicit about it.

Indeed it could produce an unsafe string, all the more since Jinja2 disables autoescaping by default.
I reversed this default in Django's Jinja2 backend; this could be an argument for making the change only in Django's Jinja2 backend and not in Jinja2 itself.

I also brought up the question on the django-developers mailing-list: https://groups.google.com/forum/#!topic/django-developers/UVCc9CyGZaA

It's tricky to change this now, so I will close this.


Update Pages “DoTermitesEatHardwoodPage”

Automatically generated by Netlify CMS

👷 Deploy Preview for chic-shortbread-66a66b processing.

Name
Link

🔨 Latest commit
f33ef75bcba94b9bc9b3e491508d9d651dc5b954

🔍 Latest deploy log
https://app.netlify.com/sites/chic-shortbread-66a66b/deploys/655d9ec270b75200083cfc26


Question: How to use an EC2 Instance role for accessing S3/DynamoDB?

I cannot find any reference to the default credential chain in the code, can anyone help me?

Hi! It's managed by delta-rs and rusoto-s3, the default instance creds should work just fine. In addition you can even assume role via sts, please see https://github.com/delta-io/delta-rs/blob/main/rust/src/storage/s3/mod.rs#L30-L86


BUG: Move InputSpaceName, OutputSpaceName from Transform to Transform…

…Base
These were added to support features of the OME-Zarr transform proposals. However, they need to be available in itk::TransformBase instead of itk::Transform for access in TransformIO classes.

Thanks Matt! It looks fine to me, to move those two data members from itk::Transform<TParametersValueType, VInputDimension, VOutputDimension> to itk::TransformBase. Especially because they don't depend on VInputDimension or VOutputDimension anyway. 👍 By the way, I would call it an ENH, rather than a BUG.
Of course I would have liked to see unit tests of the form:
    itk::TransformBase & transformBase = ...; // Arrange
    transformBase.SetInputSpaceName(exampleSpaceName); // Act
    EXPECT_EQ(transformBase.GetInputSpaceName(), exampleSpaceName); // Assert

Following the AAA pattern: Arrange-Act-Assert. Maybe to consider for a follow-up....?

Any consideration for putting these into the meta-data dictionary over member variables? Would we get serialization for free with any transform IO's if we did that?

Any consideration for putting these into the meta-data dictionary over member variables?

I guess, the question could be, are these "space names" fundamental general properties of any transform, or are they very much application specific? (In the latter case, I guess it would be better to have them as meta-data dictionary entries, rather than member variables.)
Having said so, the decision was made already two years ago, by adding them to itk::Transform. So maybe it's best to just leave them as member variables now  🤷

Having said so, the decision was made already almost two years ago, by adding them to itk::Transform: pull request #3470 commit 0575485. So maybe it's best to just leave them as member variables now 🤷

They could still have setter and getter member functions even if they are in the meta-data dictionary. It is more of a question if having them in the dictionary would make serialization easier.
Yes, this question is incidental to the intent of this PR.

Thanks for the reviews.
@N-Dekker I added the extra coverage requested.
Regarding metadata vs member, I think member is more appropriate in this case: this is an explicit property that we want all tooling / IO to eventually interpret and the explicit interface is helpful. In practice it is easier to work with, including for IO, when the explicit interface is available.


Where does console.log show up?

We are trying to investigate the value of fields from the computed fields. Usually, when coding we use console.log to see the proposed output before returning it. We try to use, console.log in the code area, but the value doesn't show up anywhere. how do we access console.log value?

The value logged in console.log should show up in the browser devtools.
E.g.
console.log({title});
return title;

Logs the title every time the title field value is changed or when I press the "Execute code" button.


Why was purchase() removed

Probably a historical question for @amacneil : Why was the purchase() method removed from this gateway?

Oh, right. Well the e-commerce platform I originally wrote Omnipay for allowed the admin to specify whether they wanted a payment gateway to authorize or purchase during checkout. The manual gateway was used to record payment by check / cash etc. The flow for this is that the payment was recorded as "authorized" during the checkout flow, then when the store received cash, they would mark it as "captured". It was unwanted/unsafe to allow the manual gateway to perform purchase() during checkout, because that would mean customers could potentially mark their order as paid without actually paying any money.
All this is historical of course, and it could be overwritten/enforced by any ecommerce platform that wanted similar behavior. So if it makes sense to add purchase back to the manual gateway, then go ahead :)

OK I'll add it back in then.  It's a no-op anyway like all of the other methods but I think it's an application decision to decide whether money has actually changed hands or not.


Unable to build lldb on MacOS M1

Hello,
When I try to build lldb as described here I get the following error:
[2/1197] Building CXX object tools/lldb/source/Core/CMakeFiles/lldbCore.dir/DumpDataExtractor.cpp.o
FAILED: tools/lldb/source/Core/CMakeFiles/lldbCore.dir/DumpDataExtractor.cpp.o
/Library/Developer/CommandLineTools/usr/bin/c++ -DGTEST_HAS_RTTI=0 -DHAVE_ROUND -DLLDB_CONFIGURATION_DEBUG -D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/tools/lldb/source/Core -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/source/Core -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/tools/lldb/source -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/include -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/tools/lldb/include -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/include -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/llvm/include -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/llvm/../clang/include -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/tools/lldb/../clang/include -I/opt/homebrew/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/libxml2 -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/source/. -I/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color -Wno-deprecated-declarations -Wno-unknown-pragmas -Wno-strict-aliasing -Wno-deprecated-register -Wno-vla-extension -g -arch arm64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk -mmacosx-version-min=12.6  -fno-exceptions -fno-rtti -std=c++14 -MD -MT tools/lldb/source/Core/CMakeFiles/lldbCore.dir/DumpDataExtractor.cpp.o -MF tools/lldb/source/Core/CMakeFiles/lldbCore.dir/DumpDataExtractor.cpp.o.d -o tools/lldb/source/Core/CMakeFiles/lldbCore.dir/DumpDataExtractor.cpp.o -c /Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/source/Core/DumpDataExtractor.cpp
/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/source/Core/DumpDataExtractor.cpp:241:12: error: expected unqualified-id
  if (std::isnan(f)) {
           ^
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/math.h:165:5: note: expanded from macro 'isnan'
    ( sizeof(x) == sizeof(float)  ? __inline_isnanf((float)(x))          \
    ^
/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/source/Core/DumpDataExtractor.cpp:242:14: error: expected unqualified-id
    if (std::signbit(f))
             ^
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/math.h:170:5: note: expanded from macro 'signbit'
    ( sizeof(x) == sizeof(float)  ? __inline_signbitf((float)(x))        \
    ^
/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/source/Core/DumpDataExtractor.cpp:247:12: error: expected unqualified-id
  if (std::isinf(f)) {
           ^
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/math.h:160:5: note: expanded from macro 'isinf'
    ( sizeof(x) == sizeof(float)  ? __inline_isinff((float)(x))          \
    ^
/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/source/Core/DumpDataExtractor.cpp:248:14: error: expected unqualified-id
    if (std::signbit(f))
             ^
/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/math.h:170:5: note: expanded from macro 'signbit'
    ( sizeof(x) == sizeof(float)  ? __inline_signbitf((float)(x))        \
    ^
4 errors generated.
[13/1197] Building CXX object tools/lldb/source/DataFormatters/CMakeFiles/lldbDataFormatters.dir/TypeSummary.cpp.o
ninja: build stopped: subcommand failed.

This happens on my MacOS M1 environment.
Any idea on how to solve it?
Thanks

Update: if I just remove the std:: prefix for the functions generating the error (for instance std::isnan(f)), it temporarily solves the problem, but then I bump into a new one:
FAILED: tools/lldb/source/Plugins/ExpressionParser/Clang/CMakeFiles/lldbPluginExpressionParserClang.dir/IRDynamicChecks.cpp.o
/Library/Developer/CommandLineTools/usr/bin/c++ -DGTEST_HAS_RTTI=0 -DHAVE_ROUND -DLLDB_CONFIGURATION_DEBUG -D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/tools/lldb/source/Plugins/ExpressionParser/Clang -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/source/Plugins/ExpressionParser/Clang -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/tools/lldb/source -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/include -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/tools/lldb/include -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/include -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/llvm/include -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/llvm/../clang/include -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/tools/lldb/../clang/include -I/opt/homebrew/include -I/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include/libxml2 -I/Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/source/. -I/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color -Wno-deprecated-declarations -Wno-unknown-pragmas -Wno-strict-aliasing -Wno-deprecated-register -Wno-vla-extension -g -arch arm64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk -mmacosx-version-min=12.6  -fno-exceptions -fno-rtti -std=c++14 -MD -MT tools/lldb/source/Plugins/ExpressionParser/Clang/CMakeFiles/lldbPluginExpressionParserClang.dir/IRDynamicChecks.cpp.o -MF tools/lldb/source/Plugins/ExpressionParser/Clang/CMakeFiles/lldbPluginExpressionParserClang.dir/IRDynamicChecks.cpp.o.d -o tools/lldb/source/Plugins/ExpressionParser/Clang/CMakeFiles/lldbPluginExpressionParserClang.dir/IRDynamicChecks.cpp.o -c /Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/source/Plugins/ExpressionParser/Clang/IRDynamicChecks.cpp
In file included from /Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/lldb/source/Plugins/ExpressionParser/Clang/IRDynamicChecks.cpp:9:
In file included from /Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/include/llvm/IR/Constants.h:23:
In file included from /Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/include/llvm/ADT/APFloat.h:19:
In file included from /Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/include/llvm/ADT/APInt.h:19:
In file included from /Users/eloparco/dev/wasm-micro-runtime/core/deps/llvm/build/include/llvm/Support/MathExtras.h:19:
/Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk/usr/include/c++/v1/cmath:642:26: error: no template named 'numeric_limits'
    bool _FloatBigger = (numeric_limits<_FloatT>::digits > numeric_limits<_IntT>::digits),
                         ^
/Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk/usr/include/c++/v1/cmath:642:60: error: no template named 'numeric_limits'
    bool _FloatBigger = (numeric_limits<_FloatT>::digits > numeric_limits<_IntT>::digits),
                                                           ^
/Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk/usr/include/c++/v1/cmath:643:18: error: no template named 'numeric_limits'
    int _Bits = (numeric_limits<_IntT>::digits - numeric_limits<_FloatT>::digits)>
                 ^
/Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk/usr/include/c++/v1/cmath:643:50: error: no template named 'numeric_limits'
    int _Bits = (numeric_limits<_IntT>::digits - numeric_limits<_FloatT>::digits)>
                                                 ^
/Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk/usr/include/c++/v1/cmath:648:17: error: no template named 'numeric_limits'
  static_assert(numeric_limits<_FloatT>::radix == 2, "FloatT has incorrect radix");
                ^
/Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk/usr/include/c++/v1/cmath:651:25: error: no template named 'numeric_limits'
  return _FloatBigger ? numeric_limits<_IntT>::max() :  (numeric_limits<_IntT>::max() >> _Bits << _Bits);
                        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk/usr/include/c++/v1/cmath:651:58: error: no template named 'numeric_limits'
  return _FloatBigger ? numeric_limits<_IntT>::max() :  (numeric_limits<_IntT>::max() >> _Bits << _Bits);
                                                         ^
/Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk/usr/include/c++/v1/cmath:661:16: error: no template named 'numeric_limits'
  using _Lim = numeric_limits<_IntT>;
               ^
/Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk/usr/include/c++/v1/cmath:664:12: error: use of undeclared identifier '_Lim'
    return _Lim::max();
           ^
/Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk/usr/include/c++/v1/cmath:665:21: error: use of undeclared identifier '_Lim'
  } else if (__r <= _Lim::lowest()) {
                    ^
/Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk/usr/include/c++/v1/cmath:666:12: error: use of undeclared identifier '_Lim'
    return _Lim::min();
           ^
11 errors generated.
[14/1060] Building CXX object tools/lldb/source/Plugins/Language/CPlusPlus/CMakeFiles/lldbPluginCPlusPlusLanguage.dir/BlockPointer.cpp.o
ninja: build stopped: subcommand failed.

Hi @eloparco; I think it's not an issue with WAMR, but rather with LLVM. However, I looked into that briefly, and I think the problem is with the way CMake generates compilation command and set of include directives, especially those two look suspicious to me:
 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX13.0.sdk
-I/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk/usr/include

as I 1) wouldn't expect the sdk to be included twice, 2) I'd expect those paths to point to the same SDK. I'm mainly developing on Linux but also have MacOS M1 so I can try to reproduce and debug it tomorrow.

I just fixed it by deleting one of the SDK versions from /Library/Developer/CommandLineTools/SDKs, to avoid headers being picked from different versions.
This is an issue already raised on the llvm project repo: https://github.com/llvm/llvm-project/issues/54988.


bug: $tabs-striped-off-color is not used

Type: bug
Platform: all
_variables.scss includes the $tabs-striped-off-color variable, which isn't used anywhere.
The fix would be to either remove it from _variables.scss or change tabs.scss to use it to color non-active striped tabs as expected.

I've since noticed that many variables in Ionic v1 go unused or used in part. I'm glad to see this is being improved upon in v2.


Remove future annotations to fix issue with ClassVar ForwardRef

Fixed in https://github.com/pydantic/pydantic/pull/10347


move MNE-MATLAB docs from MNE-Python site & merge into README

we're no longer going to host the MNE-MATLAB page on the MNE-Python docs (as of https://github.com/mne-tools/mne-python/pull/12043), so let's move it here so that the info is not lost.

Thanks @drammock


modules/hyprland/backend: handle empty socket response

Issues:

Resolves https://github.com/Alexays/Waybar/issues/3388
Resolves https://github.com/Alexays/Waybar/issues/3365

This PR:

We will check for an empty response from getSocketReply before trying to parse JSON. Before the empty response check we get the JSON parse error from the JSON module. After the change, we wont try and parse the message that will cause the crash.
Also includes some clangd cleanup.
Added test to verify we dont crash when we receive an empty socket response.

Thanks!


Bump roslyn packages to 3.0.0

This PR bumps the Roslyn package versions to 3.0.0 release packages.

thanks for the PR - however we already moved to Roslyn 3.1 beta 😀so i will close this one


Basic authentication fails if realm is single quoted and has a blank in the value

Using Cryptomator for Android, we stumbled over the following problem: Davros server does respond with an single quoted basic realm: "WWW-Authenticate: Basic realm='Sandstorm API'". This together with the fact, that the realm has a blank in the value, leads to not creating a challange in HttpHeaders.Buffer.readChallengeHeader()
Using OkHttp "WWW-Authenticate: Basic realm=\"Sandstorm API\"" and "WWW-Authenticate: Basic realm='SandstormAPI'" works but "WWW-Authenticate: Basic realm='Sandstorm API'" not.
As also mentioned in https://github.com/mnutt/davros/issues/74#issuecomment-873618239, RFC7617#section-2 only says that it can be a quoted string with the example "WallyWorld". I just tested it with a list of common WebDAV servers which all responds with the double quoted variant. But other clients also accepts blanks in single quoted string. So I really don't know exactly which party I should ask to fix this as also mentioned in https://github.com/mnutt/davros/issues/74#issuecomment-873618239.
The easiest way to reproduce it, is to add those two tests to HeadersTest.java:
  // works
  @Test public void basicSingleQuoteNoBlankChallenge() {
    Headers headers = new Headers.Builder()
            .add("WWW-Authenticate: Basic realm='protected'")
            .build();
    assertThat(HttpHeaders.parseChallenges(headers, "WWW-Authenticate")).isEqualTo(
            singletonList(new Challenge("Basic", singletonMap("realm", "'protected'"))));
  }

  // fails
  @Test public void basicSingleQuoteWithBlankChallenge() {
    Headers headers = new Headers.Builder()
            .add("WWW-Authenticate: Basic realm='protected area'")
            .build();
    assertThat(HttpHeaders.parseChallenges(headers, "WWW-Authenticate")).isEqualTo(
            singletonList(new Challenge("Basic", singletonMap("realm", "'protected area'"))));
  }

I think given the ambiguity and risk of breaking existing behaviour, we'd be more inclined to change this given examples from Web Browsers e.g. Chrome or Firefox.  What do they do?

What do they do?

Firefox and curl allows blanks in single quoted realm values.
According to the RFC, a blank is allowed in the value of the realm. From my point of view, the RFC does not specify whether it has to be double quotes or it can be single quotes as well, but a blank is explicitly allowed. In my opinion, if OkHttp already supports single quotes in general, blanks in single quotes should be supported too.

I think technically that's covered here https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6
3.2.6.  Field Value Components

   Most HTTP header field values are defined using common syntax
   components (token, quoted-string, and comment) separated by
   whitespace or specific delimiting characters.  Delimiters are chosen
   from the set of US-ASCII visual characters not allowed in a token
   (DQUOTE and "(),/:;<=>?@[\]{}").

     token          = 1*tchar

     tchar          = "!" / "#" / "$" / "%" / "&" / "'" / "*"
                    / "+" / "-" / "." / "^" / "_" / "`" / "|" / "~"
                    / DIGIT / ALPHA
                    ; any VCHAR, except delimiters

   A string of text is parsed as a single value if it is quoted using
   double-quote marks.

     quoted-string  = DQUOTE *( qdtext / quoted-pair ) DQUOTE
     qdtext         = HTAB / SP /%x21 / %x23-5B / %x5D-7E / obs-text
     obs-text       = %x80-FF

I think technically that's covered here https://datatracker.ietf.org/doc/html/rfc7230#section-3.2.6

Ah nice, thanks :+1:, that sounds very clear but still raises the question why single quotes in general are supported but blanks in single quotes not :thinking:.

Yeah, I don't know the answer here. But at least for headers double quotes are "quotes" I believe.

Going to close this given it's outside spec, and I'd be nervous about breaking current behaviour. I doubt we will fix based on the rare occurence here.


The documentation is a little off: crypto.checkAndMarkNonce returns boolean

The file arangodb/Documentation/Books/Manual/Appendix/JavaScriptModules/Crypto.md contains the documentation for crypto.checkAndMarkNonce which does not match the underlying native code as seen in https://github.com/arangodb/arangodb/blob/3.1/lib/Basics/Nonce.cpp.
The correct documentation would be something like (the glue code in v8-utils.cpp passes the result on):
createNonce
crypto.createNonce(): string
Creates a random cryptographic nonce consisting of 32 bits for a timestamp and 64 bits of randomness.
Returns the created nonce.
checkAndMarkNonce
crypto.checkAndMarkNonce(nonce): boolean
Checks and marks a nonce.
Arguments

nonce: string
The nonce to check and mark.

Returns true if the nonce was not seen before and stores the nonce for when it is might be used again.

Also, can the devs comment a little bit more in the documentation how the checkAndMarkNonce function works? Does it store previously seen nonce' in memory? Do the nonce' have any expiration period?

Hi @artjomb,
This ticket is being closed as inactive due to the date of the last activity on it.
If you believe this was done in error, please comment or create a new issue.


Member can be removed without authentication even when auth is enabled.

If authentication is enabled, removing a member from the cluster should not be possible.
We tested this with 3.1-rc1.

@zbindenren thanks for your report. The issue is solved in this PR: https://github.com/coreos/etcd/pull/6903
It is in the master branch but not backported to v3.1. Is it possible to backport the commits to the stable release? @gyuho

@mitake https://github.com/coreos/etcd/pull/6903 is already in release-3.1 branch?
We will release 3.1 this week. Thanks.

@gyuho Ah sorry, I checked the commit in v3.1-rc1 tag. @zbindenren could you try the release-3.1 branch?

I believe this is fixed in 3.1 branch. So closing.


Plotly asset

Hey thought I'd publish a small component I used for my thesis' presentation. It supports a fullscreen Plotly embedded widget by wrapping the iframe like the youtube component. Proceed how you want to :), maybe others will need it too.
Usage:

Create chart here
Make use of it! (edit: set slide layout: none)<Plotly link="//plotly.com/~jorekai/3.embed"/>
// setting width and height is not recommended
<Plotly link="//plotly.com/~jorekai/3.embed"/ width="100px" height="100px">

Great seeing someone integrating Plotly here.
Somehow I think a more universal iframe component would be more suitable to be built-in? Call it a <Browser> or something, cause this is basically what it does.
I'm also figuring out a more convenient way to use a Vue component installed directly from yarn add ..., maybe you can consider publishing the vue component as an npm package? Just a thought.
I really don't know how much and to what extent should Slidev include 3rd party components as built-ins. It would be fantastic if we have a curated Slidev components registry where we can just find the component, yarn add and integrate without much configuration.

Thanks for the contributions. But as this is basically a thin wrapper for iframe, I don't really see much value to introduce a built-in component for it (you can either use iframe directly in markdown, or create components under your local ./components).
For now, I'd like to keep Slidev's built-in components simple and for more general and common usages. Maybe later we could consider having a shared components lib as @dizys proposed.

Hey completely understandable decision. I like the idea of slidev providing some kind of additional, loosely coupled library. This would improve the slide creation speed in general. So @dizys approach also makes much sense to me.
Especially with clear contribution guidelines and snapshot testing this would invite maintainable contributions. If you are thinking about initializing such a library I'd definitely support it myself. I think you will get many more contributors on your project as time goes by.
I personally enjoyed using this over power point so much, keep up the good work :)


Bump PHP container's DRUSH_VERSION to 8.4.11

The Issue
When running i.e ddev drush pm-update in a D7 project with PHP 8.0.26, current drush version 8.4.8 fail with:
pm-updatestatus failed.
Drush command terminated abnormally due to an unrecoverable error

(Same happen when using ddev ssh and then drush pm-update)
How This PR Solves The Issue
Using latest Drush 8.x version fix the issue.
Manual Testing Instructions
A quick test is to run ddev ssh followed by drush pm-updatestatus and watch it fail.
Then, while still in the same ssh session, composer global require drush/drush:8.* and, finally drush pm-updatestatus
Automated Testing Overview

Related Issue Link(s)
Release/Deployment Notes

Thanks for doing the PR, but unfortunately, newer version of drush 8.4 don't work with PHP 7.x. Please see

https://github.com/drud/ddev/issues/4189
https://github.com/drud/ddev/pull/3882
https://github.com/drush-ops/drush/issues/4979

Why do you need or want the newer drush? Almost everybody these days has drush site-installed, so it should only be needed for Drupal 6/7...
If you need 8.4.11 badly though, it's super easy to install it with a .ddev/web-build/Dockerfile or a post-start hook.

Thanks for the quick feedback.
Just took over a few sites with Drupal 7 on PHP 8.0 and ran into the issue.
Unfortunately I didn't see the previous issue covering this.
I'll go with the post-start hook for now - sorry for the noise.

As you know, Drush 8.4 is barely on life support, I think because Pantheon still uses it. If you can figure out some path around this problem, I'd love to solve it.
I see there was a commit that referenced this last fall, https://github.com/drush-ops/drush/commit/f167114e429e7472f6dec8545aecf55a7ad417ba - would love to have you take a look and see if the problem is solved.

Hi @rfay ,
Not entirely sure if I'm fully understanding your request but here goes:
$ ddev version
 ITEM             VALUE
 DDEV version     v1.21.4
 architecture     amd64
 db               drud/ddev-dbserver-mariadb-10.4:v1.21.4
 dba              phpmyadmin:5
 ddev-ssh-agent   drud/ddev-ssh-agent:v1.21.4
 docker           20.10.22
 docker-compose   v2.14.0
 docker-platform  jornf-kubuntu-vm
 mutagen          0.16.0
 os               linux
 router           drud/ddev-router:v1.21.4
 web              drud/ddev-webserver:v1.21.4

With drush 8.4.11 built as phar on PHP 7.3 and installed to /usr/local/bin using:
ddev exec composer global require drush/drush:8.4.11 --prefer-source --no-cache
ddev exec -d ~/.composer/vendor/drush/drush composer install
ddev exec -d ~/.composer/vendor/drush/drush composer run-script phar:install-tools
ddev exec -d ~/.composer/vendor/drush/drush composer run-script phar:build
ddev exec -d ~/.composer/vendor/drush/drush sudo install drush.phar /usr/local/bin/drush-8.4.11

I get the following output (some values are redacted) from ddev exec drush-8.4.11 st:
$ ddev exec drush-8.4.11 st
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/strongarm/strongarm.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/webform/webform.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/backup_migrate/includes/backup_migrate.drush.inc PharStreamWrapper.php:487                                                                 [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/ctools/drush/ctools.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/eck/includes/eck.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/l10n_update/l10n_update.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/libraries/libraries.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/metatag/metatag_importer/metatag_importer.drush.inc PharStreamWrapper.php:487                                                              [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/metatag/metatag.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/node_export/node_export.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/rules/rules_scheduler/rules_scheduler.drush.inc PharStreamWrapper.php:487                                                                  [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/scheduler/scheduler.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/smtp/smtp.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/superfish/superfish.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/token/token.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/uuid/uuid.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/views_bulk_operations/views_bulk_operations.drush.inc PharStreamWrapper.php:487                                                            [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/views_slideshow/contrib/views_slideshow_cycle/views_slideshow_cycle.drush.inc PharStreamWrapper.php:487                                    [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/views/drush/views.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/ds/drush/ds.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/features/features.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/redirect/redirect.drush.inc PharStreamWrapper.php:487                                                                                [warning]
stat(): stat failed for phar:///usr/local/bin/drush-8.4.11/.box/bin/sites/all/modules/rules/rules.drush.inc PharStreamWrapper.php:487                                                                                [warning]
 Drupal version                  :  7.94
 Site URI                        :  http://redacted.ddev.site
 Database driver                 :  mysql
 Database hostname               :  db
 Database port                   :  3306
 Database username               :  db
 Database name                   :  db
 Database                        :  Connected
 Drupal bootstrap                :  Successful
 Drupal user                     :
 Default theme                   :  redacted_foundation
 Administration theme            :  redacted_admin
 PHP configuration               :  /etc/php/7.3/cli/php.ini
 PHP OS                          :  Linux
 Drush script                    :  /usr/local/bin/drush-8.4.11
 Drush version                   :  8.4.11
 Drush temp directory            :  /tmp
 Drush configuration             :  /var/www/html/web/sites/default/drushrc.php
 Drush alias files               :
 Install profile                 :  standard
 Drupal root                     :  /var/www/html/web
 Drupal Settings File            :  sites/default/settings.php
 Site path                       :  sites/default
 File directory path             :  sites/default/files
 Private file directory path     :  sites/default/files/private
 Temporary file directory path   :  /tmp

With drush 8.4.12-dev built as phar on PHP 7.3 and installed to /usr/local/bin using:
ddev exec composer global require drush/drush:8.*-dev --prefer-source --no-cache
ddev exec -d ~/.composer/vendor/drush/drush composer install
ddev exec -d ~/.composer/vendor/drush/drush composer run-script phar:install-tools
ddev exec -d ~/.composer/vendor/drush/drush composer run-script phar:build
ddev exec -d ~/.composer/vendor/drush/drush sudo install drush.phar /usr/local/bin/drush-8.4.12-dev

I get the following output (some values are redacted) from ddev exec drush-8.4.12-dev st:
$ ddev exec drush-8.4.12-dev st
 Drupal version                  :  7.94
 Site URI                        :  http://redacted.ddev.site
 Database driver                 :  mysql
 Database hostname               :  db
 Database port                   :  3306
 Database username               :  db
 Database name                   :  db
 Database                        :  Connected
 Drupal bootstrap                :  Successful
 Drupal user                     :
 Default theme                   :  redacted_foundation
 Administration theme            :  redacted_admin
 PHP configuration               :  /etc/php/7.3/cli/php.ini
 PHP OS                          :  Linux
 Drush script                    :  /usr/local/bin/drush-8.4.12-dev
 Drush version                   :  8.4.12-dev
 Drush temp directory            :  /tmp
 Drush configuration             :  /var/www/html/web/sites/default/drushrc.php
 Drush alias files               :
 Install profile                 :  standard
 Drupal root                     :  /var/www/html/web
 Drupal Settings File            :  sites/default/settings.php
 Site path                       :  sites/default
 File directory path             :  sites/default/files
 Private file directory path     :  sites/default/files/private
 Temporary file directory path   :  /tmp

Same process for PHP 8.0.26:
ddev exec composer global require drush/drush:8.4.11 --prefer-source --no-cache
ddev exec -d ~/.composer/vendor/drush/drush composer install
ddev exec -d ~/.composer/vendor/drush/drush composer run-script phar:install-tools
ddev exec -d ~/.composer/vendor/drush/drush composer run-script phar:build
ddev exec -d ~/.composer/vendor/drush/drush sudo install drush.phar /usr/local/bin/drush-8.4.11

ddev exec drush-8.4.11 st give this output:
$ ddev exec drush-8.4.11 st
 Drupal version                  :  7.94
 Site URI                        :  http://redacted
 Database driver                 :  mysql
 Database hostname               :  db
 Database port                   :  3306
 Database username               :  db
 Database name                   :  db
 Database                        :  Connected
 Drupal bootstrap                :  Successful
 Drupal user                     :
 Default theme                   :  redacted
 Administration theme            :  redacted_admin
 PHP configuration               :  /etc/php/8.0/cli/php.ini
 PHP OS                          :  Linux
 Drush script                    :  /usr/local/bin/drush-8.4.11
 Drush version                   :  8.4.11
 Drush temp directory            :  /tmp
 Drush configuration             :
 Drush alias files               :
 Install profile                 :  standard
 Drupal root                     :  /var/www/html/web
 Drupal Settings File            :  sites/default/settings.php
 Site path                       :  sites/default
 File directory path             :  sites/default/files
 Private file directory path     :  sites/default/files/private
 Temporary file directory path   :  /tmp

With drush 8.4.12-dev:
ddev exec composer global require drush/drush:8.*-dev --prefer-source --no-cache
ddev exec -d ~/.composer/vendor/drush/drush composer install
ddev exec -d ~/.composer/vendor/drush/drush composer run-script phar:install-tools
ddev exec -d ~/.composer/vendor/drush/drush composer run-script phar:build
ddev exec -d ~/.composer/vendor/drush/drush sudo install drush.phar /usr/local/bin/drush-8.4.12-dev

ddev exec drush-8.4.12-dev st give this output:
$ ddev exec drush-8.4.12-dev st
 Drupal version                  :  7.94
 Site URI                        :  http://redacted
 Database driver                 :  mysql
 Database hostname               :  db
 Database port                   :  3306
 Database username               :  db
 Database name                   :  db
 Database                        :  Connected
 Drupal bootstrap                :  Successful
 Drupal user                     :
 Default theme                   :  redacted
 Administration theme            :  redacted_admin
 PHP configuration               :  /etc/php/8.0/cli/php.ini
 PHP OS                          :  Linux
 Drush script                    :  /usr/local/bin/drush-8.4.12-dev
 Drush version                   :  8.4.12-dev
 Drush temp directory            :  /tmp
 Drush configuration             :
 Drush alias files               :
 Install profile                 :  standard
 Drupal root                     :  /var/www/html/web
 Drupal Settings File            :  sites/default/settings.php
 Site path                       :  sites/default
 File directory path             :  sites/default/files
 Private file directory path     :  sites/default/files/private
 Temporary file directory path   :  /tmp

With drush 8.4.11 built as phar it appears as if drush commands work as expected, though with the mentioned stat() warnings on PHP < 8.x.
With drush 8.4.12-dev the stat() warnings are gone and it seems to work similar on both PHP 7.x PHP 8.x.

Maybe we can ask for a release? Sounds like progress! Thanks for exploring.

I added a request there.

Thanks  a lot for following up on this!


TEM2015 Test 02: Wave Watch III Waves and Winds

Layer is not drawing in the portal map viewer
id: id=e6ebb3b7d87141b0a10ce8920f4ec5e5

@topowright The service associated with this portal service item does exist ( ags/rest/services/Military/WaveWatchIII/ImageServer) and does display in the portal map viewer.

HMMM. I just looked for this service and it didn't show up.
Must be slow startup time. Maybe it is the same issue as #1343

This works now, seems to be strictly a performance issue.

@conklinbd @elinz I have verified that this service now draws successfully.


Add support for weather icon in template card and template chip

Description
Add support for weather svg icon in template card and template chip

Related Issue

This PR fixes or closes issue: fixes https://github.com/piitaya/lovelace-mushroom/issues/1070
Motivation and Context

How Has This Been Tested

Types of changes

[ ] 🐛 Bug fix (non-breaking change which fixes an issue)
[x] 🚀 New feature (non-breaking change which adds functionality)
[ ] 🌎 Translation (addition or update a translation)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have tested the change locally.
[ ] I followed the steps if I add a new language .

Can you please add code to the docs that explains how to do this? I can't find an example anywhere.... Im just trying to use my weather entity icon in my mushroom-template-card.


iPhone Headphone button triggers pause than play immediately

OS: macOS High Sierra 10.13.4
GPMDP Version: 4.5.0
Issue Descriptions: Using a (regular, P2, non-lightning) iPhone headphone plugged on Macbook audio port, it register volume and play/pause buttons correctly. When pressing the pause button, GPMDP pauses for a split second than plays again. This doesn't happen if pressing media button on keyboard.
Steps to Reproduce: Get a P2 iPhone headphone (probably a regular one with buttons would work as well), plug on a Macbook computer and test. Perhaps this happens on Windows / Linux as well. Could test on Monday at work.

Just seen pull request #3063. Probably the same issue.

Same issue here. Using Apple EarPods on Mac OS High Sierra with v4.6.0 of GPMDP.

Also occuring with a V-MODA Crossfade M100 media control on the cable.

Happens for me with V-Moda Crossfade M100s too and some cheaper IEMs I have. I'm guessing it's any inline headphone remotes that will cause it.
Disabling the RCD daemon does work (thank you), but you have to disable SIP to turn it off on 10.13.6 at least, which really doesn't make it a viable solution for everyone. I don't use iTunes, but I imagine it impacts media key functionality in there as well.

Since Google Play Music may be discontinued in favor of YouTube Music, I moved to the latter and use this app for Mac.
My EarPods controls work out of the box with that. The best third party support for media keys I've seen so far. Even the VOX player with it's dedicated Mac plugin didn't manage to ... well, manage the media keys appropriately.

@samtstern workaround is working.
but let's leave this bug open


Store the PIP cache in a specific directory  - #1149

Updated easyinstall to download the SOURCE pip packages to $HOME/.pip_cache. The web startup script was updated to install the packages from this directory

@rdmark - I'm curious what you think about this change. With the start.sh changes, all of the pip packages will need to be downloaded by easyinstall.sh first. Is this going to be a problem?
We could add some error handling potentially where if the pip install from the cached dir fails, it will try to re-run the command and pull from the internet.

It's an interesting solution! I can see how we bypass the network instability factor this way.
A drawback is that the libraries won't ever be refreshed unless you run easyinstall again, but I guess that's acceptable?
Some of the libraries have C extensions that need to be compiled, right? How does this work on an RPi? Does pip3 kick off the compilation on runtime?

After thinking about it for a while I would argue that giving easyinstall.sh the responsibility to manage the caching of python libraries is a step in the wrong direction. It might make troubleshooting even hairier if f.e. the cached libraries end up in a bad state. Plus it constitutes feature creep for easyinstall. Let's leave the python lib management to pip. ;)
Just my 2 cents!

No objections to me! I'm going to cancel this PR for now. We can dust it off again later if needed.

I want to try this again!

Moved the cache dir to $HOME/.cache/piscsi. I think that's a fine convention.
The current blocker is that one dependent library has a C wrapper that can't be build from source with pip, so this method doesn't work fully out of the box. Some more research and testing on a real RPi is needed. I'm not targeting this for the upcoming "Bookworm" release.

For binary packages you can manually specify the platform(s) to download binaries for storage in the local file cache. You'd probably want to separate them out from the existing requirements.txt package list though.
eg: For amd64 it's python3 -m pip download --only-binary=:all: --platform linux_x86_64 SomePkg
There are other options that you may want to specify as well, such as python version, ABI, etc. See https://pip.pypa.io/en/stable/cli/pip_download/ - Scroll down to the examples, specifically example 6 for multiple platforms.
Other notes on this:

May want to consider wrapping the pip pieces in their own functions in a separate shell file, then using source in bash to bring it into the easyinstall.sh and web/start.sh scripts (so it's all in one place).
Could wrap the download functions in a test to see if pypi.org is resolvable by DNS (eg: getent hosts pypi.org and check for an exit level not 0) before doing the download, to avoid pip taking ages to fail to connect when not online. This could allow you to try to download the latest files when online (eg: for dev tests) and fail through to the local cache when offline.


Can't auto complete UNWIND

As the title states.

Yes, many newly added keywords are not added to completion map: https://github.com/vesoft-inc/nebula-console/blob/master/completer/completer.go
You can have a try

Yes, many newly added keywords are not added to completion map: https://github.com/vesoft-inc/nebula-console/blob/master/completer/completer.go
You can have a try


no html bitbucket

Type
enhancement

Description

Introduced conditional rendering of PR feedback in Markdown to enhance compatibility with Bitbucket.
When GitHub Flavored Markdown (GFM) is not supported, the PR feedback is now formatted using Markdown bullet points instead of HTML tables.
This change ensures that the PR feedback is displayed correctly in environments that do not support HTML, such as Bitbucket.

Changes walkthrough
Relevant filesEnhancement

utils.pyEnhance Markdown Formatting for Bitbucket Compatibility

pr_agent/algo/utils.py
Conditional HTML table formatting based on gfm_supported flag.  For non-GFM environments, uses markdown bullet points instead of HTML table.  Enhances compatibility with Bitbucket by avoiding HTML when not supported.

+9/-4

 ✨ Usage guide:
Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.
When commenting, to edit configurations related to the describe tool (pr_description section), use the following template:
/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:
[pr_description]
some_config1=...
some_config2=...

  Enabling\disabling automation

When you first install the app, the default mode for the describe tool is:

pr_commands = ["/describe --pr_description.add_original_user_description=true"
                         "--pr_description.keep_original_user_title=true", ...]

meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.

Markers are an alternative way to control the generated description, to give maximal control to the user. If you set:

pr_commands = ["/describe --pr_description.use_description_markers=true", ...]

the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following:

type: the PR type.
summary: the PR summary.
walkthrough: the PR walkthrough.

Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

  Custom labels
The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other].
If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:

Main topic:performance - pr_agent:The main topic of this PR is performance
New endpoint - pr_agent:A new endpoint was added in this PR
SQL query - pr_agent:A new SQL query was added in this PR
Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile
...

The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

  Inline File Walkthrough 💎
For enhanced user experience, the describe tool can add file summaries directly to the "Files changed" tab in the PR page.
This will enable you to quickly understand the changes in each file, while reviewing the code changes (diffs).
To enable inline file summary, set pr_description.inline_file_summary in the configuration file, possible values are:

'table': File changes walkthrough table will be displayed on the top of the "Files changed" tab, in addition to the "Conversation" tab.
true: A collapsable file comment with changes title and a changes summary for each file in the PR.
false (default): File changes walkthrough will be added only to the "Conversation" tab.

  Utilizing extra instructions
The describe tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.
Examples for extra instructions:
[pr_description]
extra_instructions="""
- The PR title should be in the format: '<PR type>: <title>'
- The title should be short and concise (up to 10 words)
- ...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

  More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the describe usage page for a comprehensive guide on using this tool.

/review auto_approve

Preparing review...

Persistent review updated to latest commit https://github.com/Codium-ai/pr-agent/commit/54a989d30fde2124c2df440c273cb8460124abc3

Preparing review...

PR Analysis

🎯 Main theme: Enhancing Markdown Formatting for Bitbucket Compatibility
📝 PR summary: This PR introduces conditional rendering of PR feedback in Markdown to enhance compatibility with Bitbucket. It uses Markdown bullet points instead of HTML tables when GitHub Flavored Markdown (GFM) is not supported, ensuring that the PR feedback is displayed correctly in environments that do not support HTML.
📌 Type of PR: Enhancement
🧪 Relevant tests added: No
⏱ Estimated effort to review [1-5]: 2, because the changes are relatively straightforward and involve conditional rendering based on a flag.
🔒 Security concerns: No security concerns found

PR Feedback
💡 General suggestions: The PR is well-structured and the changes are clear. It would be beneficial to add tests to ensure that the markdown is formatted correctly based on the gfm_supported flag. Also, consider handling the case where value is a list or dictionary in the non-GFM environment.
 🤖 Code feedback:relevant filepr_agent/algo/utils.pysuggestion
Consider handling the case where value is a list or dictionary in the non-GFM environment. Currently, it seems that the code will just concatenate the list or dictionary as a string, which might not be the desired behavior. [important]
relevant line"+            if len(value.split()) > 1:"

 ✨ Usage guide:
Overview:
The review tool scans the PR code changes, and generates a PR review. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on any PR.
When commenting, to edit configurations related to the review tool (pr_reviewer section), use the following template:
/review --pr_reviewer.some_config1=... --pr_reviewer.some_config2=...

With a configuration file, use the following template:
[pr_reviewer]
some_config1=...
some_config2=...

  Utilizing extra instructions
The review tool can be configured with extra instructions, which can be used to guide the model to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Specify the relevant sub-tool, and the relevant aspects of the PR that you want to emphasize.
Examples for extra instructions:
[pr_reviewer] # /review #
extra_instructions="""
In the 'general suggestions' section, emphasize the following:
- Does the code logic cover relevant edge cases?
- Is the code logic clear and easy to understand?
- Is the code logic efficient?
...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

  How to enable\disable automation

When you first install PR-Agent app, the default mode for the review tool is:

pr_commands = ["/review", ...]

meaning the review tool will run automatically on every PR, with the default configuration.
Edit this field to enable/disable the tool, or to change the used configurations

  Auto-labels
The review tool can auto-generate two specific types of labels for a PR:

a possible security issue label, that detects possible security issues (enable_review_labels_security flag)
a Review effort [1-5]: x label, where x is the estimated effort to review the PR (enable_review_labels_effort flag)

  Extra sub-tools
The review tool provides a collection of possible feedbacks about a PR.
It is recommended to review the possible options, and choose the ones relevant for your use case.
Some of the feature that are disabled by default are quite useful, and should be considered for enabling. For example:
require_score_review, require_soc2_ticket, and more.

  Auto-approve PRs
By invoking:
/review auto_approve

The tool will automatically approve the PR, and add a comment with the approval.
To ensure safety, the auto-approval feature is disabled by default. To enable auto-approval, you need to actively set in a pre-defined configuration file the following:
[pr_reviewer]
enable_auto_approval = true

(this specific flag cannot be set with a command line argument, only in the configuration file, committed to the repository)
You can also enable auto-approval only if the PR meets certain requirements, such as that the estimated_review_effort is equal or below a certain threshold, by adjusting the flag:
[pr_reviewer]
maximal_review_effort = 5

  More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the review usage page for a comprehensive guide on using this tool.


Invalid URL No schema supplied

I get the below error while trying to run the script:
Traceback (most recent call last):
  File "/usr/local/bin/gimme-aws-creds", line 4, in <module>
    __import__('pkg_resources').run_script('gimme-aws-creds==0.1.3', 'gimme-aws-creds')
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 739, in run_script
    self.require(requires)[0].run_script(script_name, ns)
  File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 1501, in run_script
    exec(script_code, namespace, namespace)
  File "/usr/local/lib/python3.6/site-packages/gimme_aws_creds-0.1.3-py3.6.egg/EGG-INFO/scripts/gimme-aws-creds", line 175, in <module>
  File "/usr/local/lib/python3.6/site-packages/gimme_aws_creds-0.1.3-py3.6.egg/EGG-INFO/scripts/gimme-aws-creds", line 113, in run
  File "/usr/local/lib/python3.6/site-packages/gimme_aws_creds-0.1.3-py3.6.egg/gimme_aws_creds/config.py", line 97, in get_okta_api_key
  File "/usr/local/lib/python3.6/site-packages/cerberus_python_client-0.3-py3.6.egg/cerberus/client.py", line 39, in __init__
  File "/usr/local/lib/python3.6/site-packages/cerberus_python_client-0.3-py3.6.egg/cerberus/client.py", line 47, in set_token
  File "/usr/local/lib/python3.6/site-packages/cerberus_python_client-0.3-py3.6.egg/cerberus/user_auth.py", line 40, in get_token
  File "/usr/local/lib/python3.6/site-packages/cerberus_python_client-0.3-py3.6.egg/cerberus/user_auth.py", line 31, in get_auth
  File "/usr/local/lib/python3.6/site-packages/requests-2.14.2-py3.6.egg/requests/api.py", line 72, in get
    return request('get', url, params=params, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests-2.14.2-py3.6.egg/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests-2.14.2-py3.6.egg/requests/sessions.py", line 504, in request
    prep = self.prepare_request(req)
  File "/usr/local/lib/python3.6/site-packages/requests-2.14.2-py3.6.egg/requests/sessions.py", line 436, in prepare_request
    hooks=merge_hooks(request.hooks, self.hooks),
  File "/usr/local/lib/python3.6/site-packages/requests-2.14.2-py3.6.egg/requests/models.py", line 302, in prepare
    self.prepare_url(url, params)
  File "/usr/local/lib/python3.6/site-packages/requests-2.14.2-py3.6.egg/requests/models.py", line 382, in prepare_url
    raise MissingSchema(error)
requests.exceptions.MissingSchema: Invalid URL '/v2/auth/user': No schema supplied. Perhaps you meant http:///v2/auth/user?

Given below is how my config file looks:
[DEFAULT]
idp_entry_url =
write_aws_creds = True
cred_profile = default
aws_appname = ''
aws_rolename = ''
cerberus_url =
Could you kindly let me know what is going wrong. Thanks.

Hi,
You need to supply your Okta idp_entry_url - This is your Okta entry url, which is typically something like https://companyname.okta.com.
Let me know if that fixes the issue.

Hi,
No, I still get the same error.

Hi - the error is coming from cerberus.client, if you aren't using cerberus you will need to set your  OKTA_API_KEY environment variable.

Added some error-handling to make the problem more clear to the end-user.  Can be found in the conf-profile branch.


it skips all repositories after a symlinked repository

If the root directory has a symlinked repository, all repositories after that are skipped.
$ git config --get-all ghq.root
/tmp/hoge

$ mkdir -p /tmp/hoge/{10fuga,20fuga,30fuga}/.git

$ ls -l /tmp/hoge
total 0
drwxr-xr-x 3 delphinus wheel 102 10 12 21:33 10fuga
drwxr-xr-x 3 delphinus wheel 102 10 12 21:33 20fuga
drwxr-xr-x 3 delphinus wheel 102 10 12 21:33 30fuga

$ ghq list -p
/private/tmp/hoge/10fuga
/private/tmp/hoge/20fuga
/private/tmp/hoge/30fuga

$ mkdir -p /tmp/original/.git

$ ln -s /tmp/original /tmp/hoge/15target

$ ls -l /tmp/hoge
total 8
drwxr-xr-x 3 delphinus wheel 102 10 12 21:33 10fuga
lrwxr-xr-x 1 delphinus wheel  13 10 12 21:33 15target -> /tmp/original
drwxr-xr-x 3 delphinus wheel 102 10 12 21:33 20fuga
drwxr-xr-x 3 delphinus wheel 102 10 12 21:33 30fuga

$ ghq list -p
/private/tmp/hoge/10fuga
/private/tmp/hoge/15target

# 20fuga and 30fuga are disappeared!

In v0.6, this did not occur because symlinked directories are ignored in this part. But by this commit, it started to scan symlinks and can reach this return if the symlinks have vcsDirs under themselves.
This return returns filepath.SkipDir, which has no means essentially if it would be a directory. I think it must reach this return if the path is a directory or a directory-like staff, so it does not need to return filepath.SkipDir.

Completely reverted the code by #66, so closing this issue, thanks.


Make greater use of conda-lock.

Finally figured out how to use conda-lock, which turned out to require micromamba to work properly.
Add lockfiles to the build and deploy stages to increase reproducibility. It will still not be perfect but better than it is now.
Do not remove the original requirements files since the resulting lockfiles are difficult for humans to read.
Also add documentation on why and how conda-lock is being used.

The deployment stage also needs a new installation stage with a compiler, which will require a virtual environment of some sort anyway. The custom wheels will still not be reproducible, which is disappointing but unavoidable.


Fragalysis uploads 2020_05_07

Fragalysis link to follow.
Fragalysis_upload_2020_05_07.xlsx

Thanks @Daren-fearon

@morraa-postera , Can I get you to add those from the file above not currently in fragalysis_structures.csv?

@mc-robinson here is an updated version of the file from yesterday with all the structures as of the end of this week:
Fragalysis_upload_2020_05_08.xlsx

Hey @Daren-fearon, sorry I've just seen this and all the trouble you have gone to to map the IDs. In the future, just send it my way first and I have code written that can do all of it for you! Happy to help instead of making you do all of that!


DnsServerScavenging: Add new resource

Pull Request (PR) description

Added new resource

DnsServerScavenging - resource to enforce scavenging settings (issue #189).

This Pull Request (PR) fixes the following issues

Fixes #189

Task list

[x] Added an entry to the change log under the Unreleased section of the
file CHANGELOG.md. Entry should say what was changed and how that
affects users (if applicable), and reference the issue being resolved
(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.
[ ] 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 Community Testing Guidelines.
[x] Integration tests added/updated (where possible). See DSC Community Testing Guidelines.
[x] New/changed code adheres to DSC Community Style Guidelines.

This change is

@Sudman1 I finished it earlier than expected. I think the unit test came out good to, prepared for Pester 5. If you have time to review this it would be awesome! 🙂
I think the localization code should be moved from DnsRecordBase to ResourceBase in some way. Maybe we should do that, if possible, in another PR?

As an aside: with all this customization through subclassing and abstracting away a lot of the processing that comes with it, we may want (need?) to document somewhere how these classes are intended to be used so that a new contributor isn't overwhelmed trying to reverse engineer the calls back up and down the inheritance hierarchies just to get started.

Definitely. I will create an issue to track that.


pd.PeriodIndex is a lot slower since version 0.15.2

PeriodIndex is one of the key methods used for time series analysis. Its performance has deteriorated significantly since pandas version 0.15.2. The code snippet below is easy to profile.
python --version & python -c "import pandas as pd; print('Pandas version', pd.__version__)" & python -m timeit "import pandas as pd; pd.PeriodIndex(pd.date_range('2015-1-1', '2016-1-1', freq='D').to_pydatetime(), freq='D')"

Python 3.4.4
Pandas version 0.15.2
10 loops, best of 3: 3.27 msec per loop

Python 3.4.4
Pandas version 0.16.2
10 loops, best of 3: 94.8 msec per loop

Python 3.4.3 :: Continuum Analytics, Inc.
Pandas version 0.17.0
10 loops, best of 3: 221 msec per loop

Python 3.5.1 :: Anaconda 4.0.0 (32-bit)
Pandas version 0.18.0
10 loops, best of 3: 220 msec per loop

In [10]: %timeit pd.PeriodIndex(pd.date_range('2015-1-1', '2016-1-1', freq='D').to_pydatetime(), freq='D')
100 loops, best of 3: 12.8 ms per loop

In [11]: %timeit pd.PeriodIndex(pd.date_range('2015-1-1', '2016-1-1', freq='D'))
10000 loops, best of 3: 192 µs per loop

In [13]: %timeit pd.date_range('2015-1-1', '2016-1-1', freq='D').to_period()
1000 loops, best of 3: 205 µs per loop

In [15]: %timeit pd.period_range('2015-1-1','2016-1-1',freq='D')
1000 loops, best of 3: 447 µs per loop

that's a quite convoluted way of creating a PI, as are convering to python objects multiple times. many other much better ways.

Jeff, any recommendations for an alternative way of creating a PI?

@rs2 Jeff showed 3 alternative ways above to create a PI. Or is it the problem you cannot avoid to start with python datetime.datetime objects?
@jreback But, this is potentially related to the slowdown in timeseries plotting #11831, as I see for the above timeit a similar difference between python 2 and python 3 (ca 20ms vs ca 300 ms, both with 0.17.1)

@jorisvandenbossche  thank you

@jorisvandenbossche that sounds right
can u link that plotting issue here

@jreback , @jorisvandenbossche : I need to have a PeriodIndex with irregular dates. Performance of the following snippet has deteriorated significantly after 0.15.2. Can you recommend an alternative way of creating a Series with data at irregular intervals while preserving those irregular dates rather than resampling the series with interpolation?
pd.PeriodIndex(['20160101', '20160106'], freq='D')


Add missing '\n' to the end of package.json file

Does npm produce a file with trailing newline by default?

@gaearon yes, npm does.

Interesting issue to track just to see the discussion that unfolds: https://github.com/yarnpkg/yarn/issues/2675.

Seems fine then.

Thanks!


Add fragment delegate

Add a fragment delegate and remove duplicated code. This allows reusing the fragment code without extending TiFragment or TiDialogFragment.

Current coverage is 51.16% (diff: 0.00%)

No coverage report found for master at f3a7299.

Powered by Codecov. Last update f3a7299...b574492

@vRallev thank you for you contribution!


DateTime field doesn't allow direct input or even time?

Describe the bug
I am trying to use the DateTime field, it's working and showing but without the Time fields (only date) and doesn't allow direct input.
Photo:

To Reproduce
Steps to reproduce the behavior:

In my Screen I am using the following code:

DateTimer::make('test.queued_for')
                    ->title('Queued For')
                    ->allowInput()
                    ->enableTime()
                    ->required(),

Expected behavior
To show time selection and allow direct input like this:
https://orchid.software/assets/img/ui/datatime.png
Desktop (please complete the following information):

OS: Windows.
Browser: Chrome.
Version: 89.0.4389.128.

Server (please complete the following information):

Platfrom Version: 10.0
Laravel Version: 8.12
PHP Version:  8.0
Database:  MySQL
Database Version:  8.0.24

@AlaaElrifaie I've just been looking at this, i'm not seeing the same results:
return Layout::rows([
    \Orchid\Screen\Fields\DateTimer::make('date')
        ->required()
        ->title(__('Select sale Date:'))
        ->format('Y-m-d')
        ->value((new \Carbon\Carbon()))
        ->allowInput()
        ->enableTime()
]);

Gives me:

The only obvious differences I can see are you're on 10.0 and i've tried on both 9.7 and 10.1 (both working for me).


Requiring unknown module "react-native-vector-icons/FontAwesome"?

First time user here, after completing all the instructions and ran the project, got this error, help?
Requiring unknown module "react-native-vector-icons/FontAwesome". If you are sure the module is there, try restarting the packager.

To me it looks like you didn't npm install it, but it's really hard to know what you did wrong without more info. Did you try restarting packager?

Yes, it's installed via npm, as seen here:

and yes, restarted everything (xcode, iphone simulator, terminal window).
Btw, I'm using<EMAIL_ADDRESS>with npm@3, and here's my code:
var Icon = require('react-native-vector-icons/FontAwesome');
var myIcon = (<Icon name="rocket" size={30} color="#900" style={styles.icon} />)

I was wondering it might be of great help if you could record the settings in xcode step by step to prevent any silly misconfigurations?

This should not have anything todo with Xcode, it's rather a npm/packager issue. Can you run one of the example projects? (Don't forget to npm install in side them first)
Does your app work at all or are you stuck on a red screen?

Ah ha, the example IconExplorer did work for me, will have to dig deeper to find why it's not working for my tiny test project, will report back!

Ended up reinstalling react-native-vector-icons did the trick, now everything's working fine, thanks for the excellent work and support! 👍👍👍


[Enhancement] Output Improvements

Proposed Improvements

[x] #558 snowpack build - No more dev console, ALL Console output is logged linearly by default so that CI doesn't jank. Would be great to have some handling so that plugins either run serially, but not required.
[x] snowpack dev - Console output should be logged linearly by default, with the ability for plugins to log to your own section where it makes sense (ex: TypeScript output). Currently, this isn't well defined.
[x] snowpack dev - Console output is only cleared when the file system is changed. Currently, it changes when you refresh the page, which is unexpected.
[x] snowpack dev - Preserve install output across by default for the first X seconds, or only clear manually ("press space to clear"). Currently, it clears instantly which means you miss warnings.
[x] snowpack install - Add back concise "install" output for development.
[x] Discussionsnowpack install - Remove ora usage, it's no longer needed and causing issues for some.
[x] Merge https://github.com/pikapkg/snowpack/pull/611 Merge #796

Mainly completed in #762!
There's still some cleanup/tidying work to do as a part of testing before release, but check out the screenshots in #762 for a preview.

We no longer clear the terminal at all actually, and instead preserve the entire stream of logs for you to scroll back up to.

snowpack 2.18.4 still clears terminal at
snowpack

▼ Console

[snowpack] ! installing dependencies...

not nice!

--output stream should get you the behavior that you want

aah yes. i only looked for "clear" in the docs
// snowpack.config.js

  devOptions: {
    output: 'stream', // dont clear terminal
  },


Improvements to the blob cache manager

Several improvements to the nydusd blob cache manager.

Others LGTM!

@nan1994 please help test this with the latest fscache kernel, thanks!

I have tested this with the latest fscache kernel and it works well.


Link Bulma CSS framework to html pages

WE NEED the Bootstrap CSS framework page linked to the three different html pages SO THAT our templates will load into the project.

Kyle K working on.


WIP: initial commit of golang build scripts

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold


Update tabl_enhancement_category.ts

May be useful to get a hint to report RS_DDIC_CLASSIFICATION_FINAL which allows mass adjustment

@stefan-riedel-seifert thanks, welcome to abaplint as a contributor 🎉


Bugfix/home page typo

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: juergenbr sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Upgrade code coverage tasks

We seem to be hitting the same code coverage issue on Ubuntu:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=3812144&view=logs&j=d321cacd-258d-5801-407f-101c556a68a1&t=4f851582-5e94-5e97-26ba-3d2666559adb


Fastify v5 deprecation

We should handle this deprecation

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Feature]: to make entire add books section forms accessible 🚀✨

Description
Description

As part of our commitment to inclusivity and ensuring equal access to our website's services, we need to address the accessibility concerns related to our "Add Books" section Form. Currently, the form may present challenges to users with disabilities, hindering their ability to reach out and engage with us effectively.

Key Points to Address

Keyboard Navigation: The form should be operable using keyboard inputs alone, without relying on mouse interaction. This is essential for individuals who navigate the web using assistive technologies.

Screen Readers Compatibility: The form elements and associated feedback messages need to be appropriately labeled and structured, ensuring compatibility with screen readers. Proper semantic markup will enhance the understanding of the form's purpose and improve the overall user experience.

Contrast and Visual Cues: Evaluate the form's color contrast to ensure readability for users with low vision or color blindness. Additionally, consider providing visual cues for form validation errors, alerts, and success messages.

Focus Indicators: Implement clear focus indicators to indicate the active form element. This is crucial for users who rely on focus indicators to navigate through web pages.

Responsive Design: Confirm that the form is responsive and adapts well to different screen sizes and devices, including mobile phones and tablets.

Validation and Error Handling: Enhance form validation to provide meaningful and descriptive error messages, guiding users on how to correct their input when errors occur.

Alternative Contact Options: In conjunction with the form, consider providing alternative contact methods, such as a dedicated email address or phone number, for users who may encounter difficulties with the form.

Expected Outcome

By addressing the above points, we aim to make our "Add Books" page Form more inclusive and accessible to all users, regardless of their abilities or disabilities. This will not only align with web accessibility standards but also demonstrate our commitment to providing an inclusive experience for everyone using our Food Recipes Website.

Screenshots

We can't capture accessibility changes through screenshots as opposed to code changes since accessibility modifications are often imperceptible to the user, as their purpose is to assist disabled individuals.

Checklist

[X] I have checked the existing issues
[X] I have read the [Contributing Guidelines]
[X] I have read the discussion tab thoroughly and got the project idea
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

Hey there @SiddhantPawar03, @rohansx, @crocmons, @s2sharpit 👋🏻
Please make sure to assign this issue to me to make the work done!
Thank you.


Has this command been depreciated?

I've run this command in our hybrid environment as global admin and while it doesn't error out, it doesn't return anything either.

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

ID: 9015c432-658e-461c-dfda-2b78024e0696
Version Independent ID: b9f92b15-cfd3-3a89-71ea-3946fd42806d
Content: Get-HybridMailflow (exchange)
Content Source: exchange/exchange-ps/exchange/federation-and-hybrid/Get-HybridMailflow.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@officedocsbot assign @yogkumgit

Hi @Canis-Lupis, thank you for your feedback.
I have tested in one environment and I have experienced the same behavior. Could you please let me know what onpremises Exchange version do you have?
@chrisda could you help here? Looks like there are more people with the same issue but I think it worked at some point:

Also, I think HCW uses this cmdlet.
Thanks!

It is Exchange 2013.
From: Dario Woitasen<EMAIL_ADDRESS>Sent: Wednesday, October 2, 2019 12:25 PM
To: MicrosoftDocs/office-docs-powershell<EMAIL_ADDRESS>Cc: David Tessmann<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/office-docs-powershell] Has this command been depreciated? (#4104)
Hi @Canis-Lupishttps://github.com/Canis-Lupis, thank you for your feedback.
I have tested in one environment and I have experienced the same behavior. Could you please let me know what onpremises Exchange version do you have?
@chrisdahttps://github.com/chrisda could you help here? Looks like there are more people with the same issue but I think it worked at some point:
[image]https://user-images.githubusercontent.com/33589238/66066565-27be2e00-e520-11e9-8a3f-004fce65d74e.png
Also, I think HCW uses this cmdlet.
Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/office-docs-powershell/issues/4104?email_source=notifications&email_token=AMUD2TFB5PYHUNBLQVORYWLQMTKOJA5CNFSM4I4V7IOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAFRDEI#issuecomment-537596305, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AMUD2TB44XAYULBWITY4TKLQMTKOJANCNFSM4I4V7IOA.

I've confirmed that this cmdlet and Get-HbridMailflowDatacenterIPs are basically deprecated. They're present for some customers, but aren't really used anymore, and I've updated the topics accordingly.
Thanks for the feedback.

Awesome Chris! Thank you!


Parser ignores parenthisis

Code:
float a, b, c;
float d = (a + b) * (b - c) * 3.0;

Becomes:
float a;
float b;
float c;
float d = a + b * b - c * 3.0;

I wouldn't mind if fixed AST becomes (each operation separate line / temporary):
float a;
float b;
float c;
float tmp0 = a + b;
float tmp1 = b - c;
float tmp2 = tmp0 * tmp1;
float d = tmp2 * 3.0;

The parser doesn't ignore parentheses. It understands them and operator precedence. The AST represents the correct order of operations always. Otherwise the AST would be ambigious. The problem is the outputter which walks the AST forgets to add parens around binary expressions. I fixed this in 78f8ec27

The technique you're describing where each operation gets its own variable like that is called SSA (Single Static Assignment) that is an optional pass that occurs after AST. Typically during code generation. glsl-parser doesn't concern itself with that ;) The word parser is in the name for a reason. I would like to do a compiler eventually targeting other output shader languages (HLSL, ESSL, and maybe SPIRV) but I doubt the effort is worth it.

Yeah, I know what SSA is, it was my cunning plan attempt to word it in the way to get you to do it, otherwise I have to do it... :)


Internal Python Language Server error

Description
What steps will reproduce the problem?

Select object in python file and select "Go to definition".
Traceback
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pyls_jsonrpc/endpoint.py", line 113, in consume
    self._handle_request(message['id'], message['method'], message.get('params'))
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pyls_jsonrpc/endpoint.py", line 182, in _handle_request
    handler_result = handler(params)
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pyls_jsonrpc/dispatchers.py", line 23, in handler
    return method(**(params or {}))
  File "/Users/rclary/Documents/Python/spyder/external-deps/python-language-server/pyls/python_ls.py", line 325, in m_text_document__definition
    return self.definitions(textDocument['uri'], position)
  File "/Users/rclary/Documents/Python/spyder/external-deps/python-language-server/pyls/python_ls.py", line 247, in definitions
    return flatten(self._hook('pyls_definitions', doc_uri, position=position))
  File "/Users/rclary/Documents/Python/spyder/external-deps/python-language-server/pyls/python_ls.py", line 156, in _hook
    return hook_handlers(config=self.config, workspace=workspace, document=doc, **kwargs)
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pluggy/hooks.py", line 286, in __call__
    return self._hookexec(self, self.get_hookimpls(), kwargs)
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pluggy/manager.py", line 93, in _hookexec
    return self._inner_hookexec(hook, methods, kwargs)
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pluggy/manager.py", line 337, in traced_hookexec
    return outcome.get_result()
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pluggy/callers.py", line 80, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pluggy/callers.py", line 52, in from_call
    result = func()
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pluggy/manager.py", line 335, in <lambda>
    outcome = _Result.from_call(lambda: oldcall(hook, hook_impls, kwargs))
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pluggy/manager.py", line 87, in <lambda>
    firstresult=hook.spec.opts.get("firstresult") if hook.spec else False,
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pluggy/callers.py", line 208, in _multicall
    return outcome.get_result()
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pluggy/callers.py", line 80, in get_result
    raise ex[1].with_traceback(ex[2])
  File "/Users/rclary/opt/miniconda3/envs/spy-dev-lite/lib/python3.7/site-packages/pluggy/callers.py", line 187, in _multicall
    res = hook_impl.function(*args)
  File "/Users/rclary/Documents/Python/spyder/external-deps/python-language-server/pyls/plugins/definition.py", line 25, in pyls_definitions
    for d in definitions if d.is_definition() and _not_internal_definition(d)
  File "/Users/rclary/Documents/Python/spyder/external-deps/python-language-server/pyls/plugins/definition.py", line 25, in <listcomp>
    for d in definitions if d.is_definition() and _not_internal_definition(d)
  File "/Users/rclary/Documents/Python/spyder/external-deps/python-language-server/pyls/uris.py", line 88, in uri_with
    path, _netloc = _normalize_win_path(path)
  File "/Users/rclary/Documents/Python/spyder/external-deps/python-language-server/pyls/uris.py", line 110, in _normalize_win_path
    if path[:2] == '//':

TypeError: 'PosixPath' object is not subscriptabl

Versions

Spyder version: 4.2.0.dev0 59f8d6bf0
Python version: 3.7.7
Qt version: 5.9.6
PyQt5 version: 5.9.2
Operating System: Darwin 19.6.0

Dependencies

# Mandatory:
applaunchservices >=0.1.7      :  0.2.1 (OK)
atomicwrites >=1.2.0           :  1.4.0 (OK)
chardet >=2.0.0                :  3.0.4 (OK)
cloudpickle >=0.5.0            :  1.5.0 (OK)
diff_match_patch >=20181111    :  20200713 (OK)
intervaltree                   :  None (OK)
IPython >=4.0                  :  7.16.1 (OK)
jedi =0.17.1                   :  0.17.2 (OK)
nbconvert >=4.0                :  5.6.1 (OK)
numpydoc >=0.6.0               :  1.1.0 (OK)
parso =0.7.0                   :  0.7.0 (OK)
pexpect >=4.4.0                :  4.8.0 (OK)
pickleshare >=0.4              :  0.7.5 (OK)
psutil >=5.3                   :  5.7.0 (OK)
pygments >=2.0                 :  2.6.1 (OK)
pylint >=1.0                   :  2.5.3 (OK)
pyls >=0.34.0;<1.0.0           :  build-08 (OK)
qdarkstyle >=2.8               :  2.8.1 (OK)
qtawesome >=0.5.7              :  0.7.2 (OK)
qtconsole >=4.6.0              :  4.7.5 (OK)
qtpy >=1.5.0                   :  1.9.0 (OK)
rtree >=0.8.3                  :  0.9.4 (OK)
sphinx >=0.6.6                 :  3.1.2 (OK)
spyder_kernels >=1.9.2;<1.10.0 :  1.10.0.dev0 (OK)
watchdog                       :  None (OK)
zmq >=17                       :  19.0.1 (OK)

# Optional:
cython >=0.21                  :  None (OK)
matplotlib >=2.0.0             :  None (OK)
numpy >=1.7                    :  None (OK)
pandas >=0.13.1                :  None (OK)
scipy >=0.17.0                 :  None (OK)
sympy >=0.7.3                  :  None (OK)

Hi @mrclary,
I cannot reproduce this in actual 4.x branch, can you please provide me a reproducible case or please upload a gif with this behavior.
Thanks for reporting!

@mrclary, I think the problem is with Jedi 0.17.2. Could you downgrade to 0.17.1 and check again?

@ccordoba12, thanks for tipping me off! The issue was, indeed, the Jedi version, however 0.17.2 is okay and the problem is with 0.17.2dev0. In my testing I had forgotten that I installed the latest Jedi from source (beyond the official 0.17.2).
To be clear, the official release of Jedi 0.17.2 works fine.
@steff456, sorry for the trouble; I'll close this issue.

Oh yeah, master of Jedi doesn't work with the latest Python Language Server because (I think) they switched from strings to Path objects for paths.


Checkout the new AWS S3 bucket type, s3tables.  See how that may displace the need for AWS Glue as the Apache Iceberg catalog in the project.

https://aws.amazon.com/blogs/aws/new-amazon-s3-tables-storage-optimized-for-analytics-workloads/

https://aws.amazon.com/blogs/aws/new-amazon-s3-tables-storage-optimized-for-analytics-workloads/
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3tables_namespace


Sw dspdc 1077 process file metadata

Transforming the file metadata:

file_id and file_version are parsed out of the name of the data file
the entity id and version are parsed out of the name of the metadata file (the same way they are for the rest of the metadata)
the checksum value is read from the json

Just looked back through the design doc and realized I need to update a few more things... so hold off on reviewing this for the moment

Okay, ready for review now 👍


Create hydrogen.md

I added my static-site generator called Hydrogen to the list

@calavera @h3rald @zeke Hey, I would like an update about this PR please :pray:

Hello. Not sure why you pinged me. I'm not an owner of this repo. But hello anyway! 👋

@zeke Sorry for the ping 🙏 Not too sure who to get into contact with regarding PRs on this repo 😅

Thanks, Hydrogen looks cool!
Note: 11ty is a popular static site generator that also has a red balloon in it's branding (albeit tied to a possum). Probably not a big deal, just mentioning.
Thanks for opening!

@erquhart Thanks Shawn :pray:


[poem-openapi] Expose generated json

Description of the feature
Hi, first of all good work with poem and poem-openapi, I'm enjoying a lot using them and I'll probably migrate some projects to it.
Anyway, I'd like to be able to get (and maybe serve) the generated .json file that contains the open api specification; it would also be nice to be able to deactivate the ui feature entirely.
This is because I prefer redoc and I'd like to inspect/edit the final open api document.
Code example (if possible)
#[tokio::main]
async fn main() -> Result<(), std::io::Error> {
    let api_service = OpenApiService::new(Api)
        .title("Hello World")
        .server("http://localhost:3000/api");

    // Get open api spec
    let openapi_spec = api_service.get_spec();

    let listener = TcpListener::bind("<IP_ADDRESS>:3000");

    poem::Server::new(listener)
        .await?
        .run(
            Route::new()
                .nest("/api", api_service)
                .nest("/openapi.json", serve_openapi_spec(openapi_spec))
        )
        .await
}

Released in v1.0.2 😁

Is there any example of how to implement this?

Still no example for this?

You can use the .spec() (json) or .spec_yaml() method for writing the openapi specs to a file like this:
let mut file = File::create("openapi.json")?;
file.write_all(api_service.spec().as_bytes())?;

There is also and endpoint .spec_endpoint() and .spec_endpoint_yaml():
Server::new(TcpListener::bind("<IP_ADDRESS>:3000"))
    .run(Route::new()
        .nest("/spec", api_service.spec_endpoint_yaml())
        .nest("/", ui))
    .await


I want change scale center to left , but some problem

private func configureAttributes(for attributes: UICollectionViewLayoutAttributes) {
    guard let collection = collectionView else { return }
    var visibleRect = CGRect()
    visibleRect.origin = collection.contentOffset
    visibleRect.size = collection.bounds.size
    let collectionLeft =  itemSize.width / 2
    let offset = collection.contentOffset.x
    let normalizedLeft =  attributes.center.x  - offset

    let maxDistance =  self.itemSize.width
    let distance = min(abs(collectionLeft - normalizedLeft), maxDistance)
    let ratio = (maxDistance - distance)/maxDistance
    let scale = ratio * (1 - sideItemScale) + sideItemScale

    var t = CATransform3DIdentity
    t = CATransform3DScale(t,  scale, scale, 1.0)
    attributes.zIndex = Int(scale * 10)
    attributes.transform3D = t
    //  change item space,

}

You already opened the same issue in a different repository. Please don’t post unrelated things.