Fix - LoginScreen email keyboard type and autoCorrect

@HorusGoul
I have read the CLA Document and I hereby sign the CLA
Details

We are using the default react native text input props autoCompleteType={false} and keyboardType={email-address}.
Fixed Issues

Fixes #1524
Tests

Go to the login screen and click on the enter your phone or email field, email type keyboard will open and when user type the email auto correct is disabled.
QA Steps

1. Run the application
2. Login screen show
3. Click on the enter your phone or email field
4. Email type keyboard will show and auto correct is disabled

Tested On

[ ✅] Web
[ ✅] Mobile Web
[ ✅] Desktop
[✅ ] iOS
[✅] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

I have read the CLA Document and I hereby sign the CLA


Idea: replace underscore in project name into dashes

Hello,
First of all, thanks a lot for the project. I think it could be interesting in your template if you could convert the underscore into dashes in the clojure namespace.
Best regards,
David

Hi, sorry, I am lost. Can you explain more what you mean?

Yes, sorry for the imprecision.
Whenever you make a new project with lein new volcano app_name the namespace generated by lein will have app_name in the namespace name. But it is easy to circumvent the issue, just write app-name in Lein.


Cannot install on M1 Mac

Hi,
I'm trying to install pg_query on an Apple M1 Mac (OSX 12.6)
❯ ruby -v
ruby 2.7.6p219 (2022-04-12 revision c9c2245c0a) [arm64-darwin21]

Here's the error I'm getting:
current directory: /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query
/Users/cezar/.rbenv/versions/2.7.6/bin/ruby -I /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/2.7.0 -r ./siteconf20221024-19799-7z9osf.rb extconf.rb
creating Makefile

current directory: /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query
make "DESTDIR=" clean

current directory: /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query
make "DESTDIR="
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_utils_mmgr_mcxt.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_utils_error_elog.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/pg_query_split.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_utils_mmgr_aset.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/pg_query.pb-c.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_common_string.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_common_encnames.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_port_random.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_nodes_value.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/pg_query_outfuncs_protobuf.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_nodes_makefuncs.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_pl_plpgsql_src_pl_handler.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_common_stringinfo.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_nodes_extensible.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_utils_adt_format_type.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_parser_parser.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_port_snprintf.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
/Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_port_snprintf.c:1028:11: warning: 'sprintf' is deprecated: This function is provided for compatibility reasons only.  Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead. [-Wdeprecated-declarations]
        vallen = sprintf(convert, "%p", value);
                 ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:188:1: note: 'sprintf' has been explicitly marked deprecated here
__deprecated_msg("This function is provided for compatibility reasons only.  Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead.")
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:215:48: note: expanded from macro '__deprecated_msg'
        #define __deprecated_msg(_msg) __attribute__((__deprecated__(_msg)))
                                                      ^
/Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_port_snprintf.c:1210:13: warning: 'sprintf' is deprecated: This function is provided for compatibility reasons only.  Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead. [-Wdeprecated-declarations]
                        vallen = sprintf(convert, fmt, prec, value);
                                 ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:188:1: note: 'sprintf' has been explicitly marked deprecated here
__deprecated_msg("This function is provided for compatibility reasons only.  Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead.")
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:215:48: note: expanded from macro '__deprecated_msg'
        #define __deprecated_msg(_msg) __attribute__((__deprecated__(_msg)))
                                                      ^
/Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_port_snprintf.c:1217:13: warning: 'sprintf' is deprecated: This function is provided for compatibility reasons only.  Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead. [-Wdeprecated-declarations]
                        vallen = sprintf(convert, fmt, value);
                                 ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/stdio.h:188:1: note: 'sprintf' has been explicitly marked deprecated here
__deprecated_msg("This function is provided for compatibility reasons only.  Due to security concerns inherent in the design of sprintf(3), it is highly recommended that you use snprintf(3) instead.")
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:215:48: note: expanded from macro '__deprecated_msg'
        #define __deprecated_msg(_msg) __attribute__((__deprecated__(_msg)))
                                                      ^
5 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_parser_parse_expr.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/pg_query_normalize.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/pg_query_fingerprint.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_libpq_pqcomm.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_port_pgstrcasecmp.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_postmaster_postmaster.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_common_wchar.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_port_strerror.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_pl_plpgsql_src_pl_scanner.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/pg_query.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/guc-file.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_nodes_nodeFuncs.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/pg_query_ruby.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_nodes_equalfuncs.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/xxhash.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
2 warnings generated.
compiling /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_parser_gram.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
In file included from gram.y:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/socket.h:425:1: error: expected ';' after top level declarator
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr, sockaddr);
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:587:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
#define __CCT_DECLARE_CONSTRAINED_PTR_TYPES(basetype, basetag)                                      \
                                                                                ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:415:1: note: expanded from here
__CCT_DECLARE_CONSTRAINED_PTR_TYPE_3
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:563:14: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPE_3'
        __CCT_DEFER(__CONCAT, basetag,  __CCT_CONTRACT_LIST_TO_TAGGED_SUFFIX_1(kind))
                    ^
In file included from gram.y:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/socket.h:425:1: error: expected ';' after top level declarator
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:588:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
__CCT_DECLARE_CONSTRAINED_PTR_TYPE(basetype, basetag, REF);                                         \
                                                                                ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:420:1: note: expanded from here
__CCT_DECLARE_CONSTRAINED_PTR_TYPE_4
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:567:11: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPE_4'
                 * __CCT_CONTRACT_TO_ATTR(kind2)                                                        \
                 ^
In file included from gram.y:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/socket.h:471:1: error: typedef redefinition with different types ('struct sockaddr_storage *' vs 'struct sockaddr *')
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr_storage, sockaddr_storage);
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:587:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
#define __CCT_DECLARE_CONSTRAINED_PTR_TYPES(basetype, basetag)                                      \
                                                                                ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 4 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:540:38: note: expanded from macro '__CCT_CONTRACT_TO_ATTR'
#define __CCT_CONTRACT_TO_ATTR(kind) __CONCAT(__CCT_CONTRACT_ATTR_, kind)
                                     ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:429:1: note: expanded from here
__CCT_CONTRACT_ATTR_582
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/socket.h:425:1: note: previous definition is here
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr, sockaddr);
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:588:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
__CCT_DECLARE_CONSTRAINED_PTR_TYPE(basetype, basetag, REF);                                         \
                                                                                ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 4 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:540:38: note: expanded from macro '__CCT_CONTRACT_TO_ATTR'
#define __CCT_CONTRACT_TO_ATTR(kind) __CONCAT(__CCT_CONTRACT_ATTR_, kind)
                                     ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:421:1: note: expanded from here
__CCT_CONTRACT_ATTR_582
^
In file included from gram.y:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/socket.h:471:1: error: expected ';' after top level declarator
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr_storage, sockaddr_storage);
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:587:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
#define __CCT_DECLARE_CONSTRAINED_PTR_TYPES(basetype, basetag)                                      \
                                                                                ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:428:1: note: expanded from here
__CCT_DECLARE_CONSTRAINED_PTR_TYPE_3
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:563:14: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPE_3'
        __CCT_DEFER(__CONCAT, basetag,  __CCT_CONTRACT_LIST_TO_TAGGED_SUFFIX_1(kind))
                    ^
In file included from gram.y:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/socket.h:471:1: error: typedef redefinition with different types ('struct sockaddr_storage *' vs 'struct sockaddr *')
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:588:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
__CCT_DECLARE_CONSTRAINED_PTR_TYPE(basetype, basetag, REF);                                         \
                                                                                ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 4 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:540:38: note: expanded from macro '__CCT_CONTRACT_TO_ATTR'
#define __CCT_CONTRACT_TO_ATTR(kind) __CONCAT(__CCT_CONTRACT_ATTR_, kind)
                                     ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:6:1: note: expanded from here
__CCT_CONTRACT_ATTR_582
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/socket.h:425:1: note: previous definition is here
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr, sockaddr);
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:588:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
__CCT_DECLARE_CONSTRAINED_PTR_TYPE(basetype, basetag, REF);                                         \
                                                                                ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 4 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:540:38: note: expanded from macro '__CCT_CONTRACT_TO_ATTR'
#define __CCT_CONTRACT_TO_ATTR(kind) __CONCAT(__CCT_CONTRACT_ATTR_, kind)
                                     ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:421:1: note: expanded from here
__CCT_CONTRACT_ATTR_582
^
In file included from gram.y:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/socket.h:471:1: error: expected ';' after top level declarator
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr_storage, sockaddr_storage);
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:588:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
__CCT_DECLARE_CONSTRAINED_PTR_TYPE(basetype, basetag, REF);                                         \
                                                                                ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:5:1: note: expanded from here
__CCT_DECLARE_CONSTRAINED_PTR_TYPE_4
^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:567:11: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPE_4'
                 * __CCT_CONTRACT_TO_ATTR(kind2)                                                        \
                 ^
2 warnings and 6 errors generated.
make: *** [/Users/cezar/.rbenv/versions/2.7.6/lib/ruby/gems/2.7.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_parser_gram.o] Error 1

make failed, exit code 2

Got it working with xcode-select --install.

Same issue for me today with pg_query 2.1.4 on an Apple M1 Mac (OSX 13) with xcode 14.1:

Building native extensions. This could take a while...
ERROR:  Error installing pg_query:
	ERROR: Failed to build gem native extension.

    current directory: /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query
/Users/arnaud/.rbenv/versions/3.1.2/bin/ruby -I /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/3.1.0 -r ./siteconf20221102-7575-bt8897.rb extconf.rb
creating Makefile

current directory: /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query
make DESTDIR\= clean

current directory: /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query
make DESTDIR\=
compiling /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/guc-file.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
...
compiling /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/src_backend_parser_gram.c
warning: unknown warning option '-Wno-clobbered' [-Wunknown-warning-option]
warning: unknown warning option '-Wno-discarded-qualifiers'; did you mean '-Wno-ignored-qualifiers'? [-Wunknown-warning-option]
In file included from gram.y:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/socket.h:425:1: error: expected ';' after top level declarator
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr, sockaddr);
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:587:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
#define __CCT_DECLARE_CONSTRAINED_PTR_TYPES(basetype, basetag)                                      \
                                                                                ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:415:1: note: expanded from here
__CCT_DECLARE_CONSTRAINED_PTR_TYPE_3
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:563:14: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPE_3'
        __CCT_DEFER(__CONCAT, basetag,  __CCT_CONTRACT_LIST_TO_TAGGED_SUFFIX_1(kind))
                    ^
In file included from gram.y:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/socket.h:425:1: error: expected ';' after top level declarator
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:588:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
__CCT_DECLARE_CONSTRAINED_PTR_TYPE(basetype, basetag, REF);                                         \
                                                                                ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:420:1: note: expanded from here
__CCT_DECLARE_CONSTRAINED_PTR_TYPE_4
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:567:11: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPE_4'
                 * __CCT_CONTRACT_TO_ATTR(kind2)                                                        \
                 ^
In file included from gram.y:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/socket.h:471:1: error: typedef redefinition with different types ('struct sockaddr_storage *' vs 'struct sockaddr *')
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr_storage, sockaddr_storage);
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:587:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
#define __CCT_DECLARE_CONSTRAINED_PTR_TYPES(basetype, basetag)                                      \
                                                                                ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 4 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:540:38: note: expanded from macro '__CCT_CONTRACT_TO_ATTR'
#define __CCT_CONTRACT_TO_ATTR(kind) __CONCAT(__CCT_CONTRACT_ATTR_, kind)
                                     ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:429:1: note: expanded from here
__CCT_CONTRACT_ATTR_582
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/socket.h:425:1: note: previous definition is here
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr, sockaddr);
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:588:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
__CCT_DECLARE_CONSTRAINED_PTR_TYPE(basetype, basetag, REF);                                         \
                                                                                ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 4 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:540:38: note: expanded from macro '__CCT_CONTRACT_TO_ATTR'
#define __CCT_CONTRACT_TO_ATTR(kind) __CONCAT(__CCT_CONTRACT_ATTR_, kind)
                                     ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:421:1: note: expanded from here
__CCT_CONTRACT_ATTR_582
^
In file included from gram.y:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/socket.h:471:1: error: expected ';' after top level declarator
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr_storage, sockaddr_storage);
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:587:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
#define __CCT_DECLARE_CONSTRAINED_PTR_TYPES(basetype, basetag)                                      \
                                                                                ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:428:1: note: expanded from here
__CCT_DECLARE_CONSTRAINED_PTR_TYPE_3
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:563:14: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPE_3'
        __CCT_DEFER(__CONCAT, basetag,  __CCT_CONTRACT_LIST_TO_TAGGED_SUFFIX_1(kind))
                    ^
In file included from gram.y:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/socket.h:471:1: error: typedef redefinition with different types ('struct sockaddr_storage *' vs 'struct sockaddr *')
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:588:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
__CCT_DECLARE_CONSTRAINED_PTR_TYPE(basetype, basetag, REF);                                         \
                                                                                ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 4 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:540:38: note: expanded from macro '__CCT_CONTRACT_TO_ATTR'
#define __CCT_CONTRACT_TO_ATTR(kind) __CONCAT(__CCT_CONTRACT_ATTR_, kind)
                                     ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:6:1: note: expanded from here
__CCT_CONTRACT_ATTR_582
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/socket.h:425:1: note: previous definition is here
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr, sockaddr);
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:588:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
__CCT_DECLARE_CONSTRAINED_PTR_TYPE(basetype, basetag, REF);                                         \
                                                                                ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 4 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:540:38: note: expanded from macro '__CCT_CONTRACT_TO_ATTR'
#define __CCT_CONTRACT_TO_ATTR(kind) __CONCAT(__CCT_CONTRACT_ATTR_, kind)
                                     ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:421:1: note: expanded from here
__CCT_CONTRACT_ATTR_582
^
In file included from gram.y:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/postgres.h:46:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/c.h:1330:
In file included from /Users/arnaud/.rbenv/versions/3.1.2/lib/ruby/gems/3.1.0/gems/pg_query-2.1.4/ext/pg_query/include/port.h:17:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netdb.h:91:
In file included from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/netinet/in.h:81:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/socket.h:471:1: error: expected ';' after top level declarator
__CCT_DECLARE_CONSTRAINED_PTR_TYPES(struct sockaddr_storage, sockaddr_storage);
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:588:101: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPES'
__CCT_DECLARE_CONSTRAINED_PTR_TYPE(basetype, basetag, REF);                                         \
                                                                                ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:580:2: note: expanded from macro '\
__CCT_DECLARE_CONSTRAINED_PTR_TYPE'
        __CCT_DISPATCH(__CCT_DECLARE_CONSTRAINED_PTR_TYPE, basetype, basetag, __VA_ARGS__)
        ^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:548:2: note: expanded from macro '__CCT_DISPATCH'
        __CCT_DISPATCH1(base, __CCT_COUNT_ARGS(__VA_ARGS__), __VA_ARGS__)
        ^
note: (skipping 1 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:113:26: note: expanded from macro '__CONCAT'
#define __CONCAT(x, y)   x ## y
                         ^
<scratch space>:5:1: note: expanded from here
__CCT_DECLARE_CONSTRAINED_PTR_TYPE_4
^
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/constrained_ctypes.h:567:11: note: expanded from macro '__CCT_DECLARE_CONSTRAINED_PTR_TYPE_4'
                 * __CCT_CONTRACT_TO_ATTR(kind2)                                                        \
                 ^

This should be reopened, the build is broken with xcode CLT 14 and 14.1 and if you're on macOS 13, you cannot downgrade. I've been unable to find any workaround to get it to compile.

Yes. I tried to reinstall Xcode and it's tools but I don't find any solution. If I downgrade Xcode, Homebrew doesn't work.

Tracked in https://github.com/pganalyze/pg_query/issues/263 - we should have a release out shortly.

This has been released as 2.2.0!

Thanks for the quick fix.


support of streaming

I am using the last version, and I notice that the application doesn't support stream item yet.
Will it be supported later?

蛮重要的支持


add translation and rotation to fiber agents

Problem
#332
Up until now, fibers have been required to put their subpoints into fully transformed world space, and position and rotation required to be 0.  However, our updated fiber rendering does now support full transformations.
Solution
Add a code path to actually use agent position and rotation to transform fiber vertices.  Also add a simple javascript test simulator to demonstrate translation and rotation.
Type of change

New feature (non-breaking change which adds functionality)

Change summary:
Add transformation to the shader.  Add code path to send data in.  This required adding a whole new buffer for the rotation data.  This could be inefficient if rotations are nearly always 0 - we are just passing around a buffer of 0s and doing a little extra math with them.
Steps to Verify:
Can clone and select the "TEST_SINGLE_FIBER" in the demo viewer.
Screenshots (optional):
https://github.com/simularium/simularium-viewer/assets/2193409/3eae4d6d-529f-4dd6-8f80-fb4f3adbe993

The shader part is a bit over my head (although based on context clues it looks reasonable), so looks good to me!


Fatal error while cloning

Hi,
While cloning the FastSpectrum repository (followed the instructions: git clone https://github.com/a-nasikun/FastSpectrum --recursive)
I got a fatal error:

Did you see such an error before? Do you know how to fix it?
Thanks!

Hey Naama,
Thank you for reaching out. I tried again to clone and run it on my
computer, and it works perfectly. The CGAL submodule that causes problems
on your side was all fine.
Some of my recommendations:

If you're using github (I was using github desktop), it works better to
clone it via the command line. Repository -> Open in Command Prompt ->
navigate to directory that you want -> then "git clone
https://github.com/a-nasikun/FastSpectrum --recursive"
Internally, CGAL is not used in my program/module within the program.
So, even if you cannot get the cgal within the system, the algorithm might
still run.

Kind regards
[image: image.png]
=====================================================
Ahmad Nasikun
PhD student – Geometry ProcessingTU Delft / Computer Graphics and
Visualization
Room 6.E.420 | Building 28 | Van Mourik Broekmanweg 6, 2628 XE Delft
Webpage:  @.*>
http://graphics.tudelft.nl/ahmad-nasikun/
On Tue, Feb 15, 2022 at 4:48 PM naama-alon @.***> wrote:

Hi!
While cloning the FastSpectrum repository (followed the instructions: git
clone https://github.com/a-nasikun/FastSpectrum --recursive)
I got a fatal error:
[image: image]
https://user-images.githubusercontent.com/33179653/154097345-5b4a55af-a26f-48d6-ae9f-0827e7ad13f3.png
Did you see such an error before? do you know how to fix it?
Thanks,
Naama Alon
—
Reply to this email directly, view it on GitHub
https://github.com/a-nasikun/FastSpectrum/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIXZDD4T5YVC2TX3WAZ5E3U3JYVDANCNFSM5OO5TALQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you for your response.
I ran it without cgal and It worked!
Regards,
Naama Alon

You are very welcome. Thank you for trying out our tools. It's a prototype
for research work, so there would be some bugs on it. Would be super happy
for a pull request or a coding suggestion.
Kind regards,
A. Nasikun
On Thu, Feb 17, 2022, 3:15 PM Naama Alon @.***> wrote:

Thank you for your response.
I ran it without cgal and It worked!
Regards,
Naama Alon
—
Reply to this email directly, view it on GitHub
https://github.com/a-nasikun/FastSpectrum/issues/2#issuecomment-1042994569,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIXZDGP65TUFRDRYU3764DU3T7ILANCNFSM5OO5TALQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>


Minor variable updates

Two updates here to support changes to tachyons-sass in https://github.com/tachyons-css/tachyons-sass/issues/26

Update the --sans-serif variable in _variables.scss to be on a single line due to the suggestion here.
Create a new variable --spacing-copy-separator as suggested here.

I ran npm run build and the CSS didn't change (as expected, I believe), but a package-lock.json was generated. Should I include that on this PR?
Edit: If I wasn't supposed to make changes directly to these files as well, sorry! I may have misunderstood how this works and you can feel free to close / suggest changes.

Thanks!


CommandValueId missing for Button

We are using attribute CommandValueId on Button elements to pass button specific information to javascript methods to implement generic methods that behave differently depending on this value.
This is also very good when dynamically populating flyouts.
Documentation on button attributes: https://msdn.microsoft.com/en-us/library/gg334536.aspx
Documentation on CrmParameter: https://msdn.microsoft.com/en-us/library/gg309332.aspx
In RibbonWorkbench this attribute is not visible, and I have a gut feeling the attribute is removed entirely if using RWB to update a solution.
Could support for CommandValueId be implemented in RWB? :)

Hi Jonas,
The Ribbon Workbench shouldn't remove it if you have it already in your xml - if it does, then it's a bug!
Have you had success using CommandValueId in all versions of Dynamics? I stopped using it myself back in CRM2015 because it stopped working in some situations. Instead I use the Button ID.

Hi Scott,
Yes, I recall we had a discussion about this a couple of years ago...
Aparently I had forgotten that it did not work when I recently started designing new buttons and used this feature - and it definitely works now in 2016, I guess in 365 too...

That is good to know! You can look forward to the return of this attribute in the next version!

Lovely! 👍


feat: add ability to attach access tags to resources

Description
provide the ability to add access tags to resources created by the module
Types of changes in this PR
No release required

[ ] Examples or tests (addition or updates of examples or tests)
[ ] Documentation update
[ ] CI-related update (pipeline, etc.)
[ ] Other changes that don't affect Terraform code

Release required

[ ] Bug fix (patch release (x.x.X): Change that fixes an issue and is compatible with earlier versions)
[x] New feature (minor release (x.X.x): Change that adds functionality and is compatible with earlier versions)
[ ] Breaking change (major release (X.x.x): Change that is likely incompatible with previous versions)

Release notes content
Add ability to attach access tags to resources created by the module, consumers who want to use the access tags will need additional permissions for Tagging service at the Administrator level

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

Merge actions for mergers

Merge by using "Squash and merge".

Use a relevant conventional commit message that is based on the PR contents and any release notes provided by the PR author.
The commit message determines whether a new version of the module is needed, and if so, which semver increment to use (major, minor, or patch).

Skipping upgrade test, tested upgrade path manually and saw no destroys when not providing access tags, after providing access tags only the resource tag was add to the terraform state and nothing was destroyed. Here is the plan after applying the main branch:
Terraform will perform the following actions:

  # module.key_protect_module.ibm_resource_tag.key_protect_tag[0] will be created
  + resource "ibm_resource_tag" "key_protect_tag" {
      + acccount_id = (known after apply)
      + id          = (known after apply)
      + resource_id = "crn:v1:bluemix:public:kms:eu-gb:a/abac0df06b644a9cabc6e44f55b3880e:7e3b1271-02e6-41b3-8571-77e1e716ae0f::"
      + tag_type    = "access"
      + tags        = [
          + "geretain-dev:permanent-test-tag-1",
          + "geretain-dev:permanent-test-tag-2",
        ]
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

module.key_protect_module.ibm_resource_tag.key_protect_tag[0]: Creating...
module.key_protect_module.ibm_resource_tag.key_protect_tag[0]: Creation complete after 1s [id=crn:v1:bluemix:public:kms:eu-gb:a/abac0df06b644a9cabc6e44f55b3880e:7e3b1271-02e6-41b3-8571-77e1e716ae0f::]

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

Note: upgrade test is failing due to passing the access_tags variable into the test which causes the main branch apply to fail due to the variable not being present in previous versions of the module.

:tada: This PR is included in version 2.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Queries in sidebar

What?
Splits the queries out to a separate Queries section in the sidebar and gives each query a separate page.
Why?
Having all the queries listed on a single page makes it difficult to read the documentation. Putting each query on a separate page and then providing navigation to these pages via a new Queries section in the sidebar makes it much easier to see what queries exist and to read this documentation.
Before

After

Closed, since this change was merged upstream via https://github.com/brettchalupa/graphql-docs/pull/156


Make SessionToken on QueryRequestOptions public

Description
Made SessionToken public on QueryRequestOptions to allow querying of multiple documents with SessionToken.
Type of change

[ ] New feature (non-breaking change which adds functionality)

Closing issues
Closes #973

 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: dpgregory sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

/azp run

/azp run

/azp run

/AzurePipelines run

/azp run

/AzurePipelines help

/AzurePipelines run

/azp run

/azp run

/azp run

Is there anything else I need to do on this, or is it just waiting for someone to be free to look at it?

@bchong95 , @sboshra please take a look.
Exposing this contract enables read-my-writes through queries as well.

/azp run

/azp run


Distributed compiled version

Right now your module only works with Browserify not Webpack.

Thanks. I fix this a new version.

New version work with webpack.

Thanks!


add the app to the F-droid repo

In relation to offering APK downloads ( https://github.com/mapswipe/mapswipe.github.io/commit/afcd39210e4a2cf2d556b6df2cd81ad923e771a6 ) it could be good to list the app on the f-droid repo.
As a user I quite like it just as a way of listing/finding open source apps, but also as an easy way to side-load apps on amazon devices, however...
I make this suggestion casually without really knowing what's involved, but I heard from @simonpoole (vespucci developer) that it's quite a hassle actually. In which case feel free to park this as a low priority idea.

The main issue with F-Droid is that it isn't simply a APK repo, they actually build the app with their own automated build system. This is OK to a certain point, but in the case of more complicated builds you tend to be depending on whoever setup the F-Droid side to do it correctly and have time when something goes wrong (which is btw why I would strongly suggest requiring a modified app version string for F-Droid or you will never notice build related issues that are specific to F-Droid),
The other problem is that they are fairly strict about only using open components which may or may not be an issue for you.

for now we're just going to stick with the apk. If you guys want to publish it on fdroid, feel free to, it's open source.

ooh yeah that does sound like a pain. Didn't realise f-droid builds the apps.

Any thoughts on this @laurentS ? 3 years old now.

Yes, this was actually the very first issue on mapswipe. Can't be done, because mapswipe uses non-FLOSS libraries (firebase). See details on the ticket linked. I'll close this ticket here as well


v1.5.2 just showing a blank screen on macOS

Expected Behavior

I would expect to see a cool GraphQL client.

Current Behavior

I see a blank white screen.

Possible Solution

Fix whatever broke in v1.5.2. :)

Steps to Reproduce (for bugs)

Launch v1.5.2 on macOS.

Context

v1.5.1 works fine.
Your Environment

Version used: 1.5.2
Environment name and application type (e.g. Chrome 39, chrome extension v1.4.7): darwin-x64
Operating System and version (e.g. Linux, v1.4.7): macOS Sierra 10.12.6

@wKovacs64 Thanks for mentioning it. I'd run the build again. The build was wrong and I ran it again, but apparently the build doesn't overwrite a previous build.
Pro Tip: To overwrite a release, delete the tag, then discard the draft of the tag. 😝


Request: Add centiliters as a measurement option

It would be nice if we could have metric cocktail measurements (centiliter) as a measurement option.
It's not that big of a deal given anyone can divide the milliliters by ten but cl is commonly used in recipes. Especially by the IBA (International Bartenders Association).
Thank you!

Hi @BradNut! Great Idea.
Currently centiliter is available when you create your own cocktails. But from you text i assume you would like to see the current recipes in cl.
That could be an option under settings. If you selected Metric as your Measurement system you should also have the choice to pick between ml and cl.

Hey @anton-gustafsson. Yes I meant being able to view current recipes in cl.
But I did not know that created cocktails could be created with cl so that is also good to know.

That could be an option under settings. If you selected Metric as your Measurement system you should also have the choice to pick between ml and cl.

Yeah that is where I would think cl would fit best in the app. Would be great to get that added eventually! Thank you!

@BradNut I agree that it would be a nice addition to the app. I will look into this
Thanks 🚀

Nice! Thank you @anton-gustafsson !


[AutoRelease] t2-managedservices-2024-11-04-44075(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/5670
Recording test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=1007

issue link:https://github.com/Azure/sdk-release-request/issues/5670


add unit tests for endpoints in fastapi

Currently we have unit tests for lower level methods, and we also make real api calls to test the public HTTP api of the cloudapi. I think it would be beneficial to also have unit tests for the CloudAPI endpoint methods.
This would make it possible to mock certain parts of the flow, making it easier to do setup for testing. Testing the issuer API currently needs interaction with the ledger, aca-py agent and the trust registry, which can be quite cumbersome to set up for every possible flow you want to test.
E.g. ACA-Py mocks that a request is made and calls the method that adds a route to the application directly: https://github.com/hyperledger/aries-cloudagent-python/blob/main/aries_cloudagent/wallet/tests/test_routes.py
Maybe we can use mock requests (as described here) or actually just call the method with fake input data (e.g. get_credential("cred_id", acapy_controller_mock))
Don't want to do a big refactor and change everything without some input. What do you think? (mainly @morrieinmaas)

@TimoGlastra I agree with you here. Not saying this as an excuse but ,atter of factly, the way it is now has quite frankly been a way to cut corners a bit due to "lack of devs". Where possible there is unit and e2e being a mix of each other and where only unit tests possible there is only unit tests. That said, again, I agree ideally that should be as you describe.


Update typescript compiler

Grab and minify the latest typescript.js and then this should allow for compiling: https://gist.github.com/lukehoban/9061216

Is there anything new? Honestly, I'd happily switch from CodePen to JS Bin just because of TypeScript, but currently it's just not working...


Do not calculate needed ave for PB

Added a check to the SolveCalculator to return the standard NA value. Added a test case.
Addresses #28

Closes #28


Remove DC from HSA and use state-level data to fix hospital metrics

@mikelehen here is a new snapshot built off of 728c98034eaa61d8d666907867495d8f976a12e0: https://covid-projections-git-bump-snapshot-3325-2141-covidactnow.vercel.app/?s=33252141
I notice that the DC metro is missing admissions data despite all of its counties having the necessary data--this is something I'll look into, but I think it makes sense to merge this in the meantime (if that sounds alright to you).


Memory usage keep growing

Hi @Jonathan-Livingston-Seagull I see you closed the issue before I could respond. Was the issue caused by the package or did it arise from something else? I'm interested to know if there is a memory leak somewhere.
Thanks.

@AndreBaltazar8 Many thanks for the response. It seems there were no memory leak. It was a false alarm from me. Sorry :) Awesome package and I love it.


transitions get started to dcos/examples

What are your changes?
What is the urgency level of this change?

[x] Blocker
[ ] High
[ ] Medium

I have completed these items:

[x] I have built locally and tested for broken links and formatting.
[ ] If appropriate, I have added redirects.

If you included a comment with your commit, it appears here:
@joel-hamill once we have https://github.com/dcos/dcos-docs/pull/724 merged this PR should be merged as well

retest this please

I did (and now again). Is above screen shot enough as a proof or what else do you need?


Add a timeout to the mutation test runner

Certain mutations will cause tests to enter infinite loops (e.g. while n < 5: -> while True:).
We should add a timeout to prevent that. Mutations which cause timeouts should be logged separately.
This shouldn't be difficult to do. I have a (concept) branch which contains a basic implementation of it (https://github.com/davidlibland/mutatest/tree/feat/timeout).

This sounds like a great feature to add. We'll have to think about the logic for naturally slow tests - you can see a few within mutatest that I've put pytest.mark.slow on, those may exceed the timeout setting but are not actually timeouts. If you feel good about the progress feel free to open an early PR and we can iterate on review that way too.

https://github.com/EvanKepner/mutatest/pull/18


autofuzz: Do not cast to non-public types

Fixes https://github.com/CodeIntelligenceTesting/jazzer/issues/465

Fixes the problem and describes the current limitations, approve +1
I still wonder if we could relax the restriction. Even though the current approach should work in most cases, I could think about situations where someone wants to test internal functionality and has to use package visible classes. Moving the fuzz test into that package should still work if package visible classes are allowed. This opens up other problems, e.g. how should we know the "target" package. In writing this I realized we should probably leave it like it is now smile

That's a valid point once we enable @FuzzTest for Autofuzz (which I'm actually thinking about doing soon). I will need to think about it. We can certainly relax visibility checks, but would then have to emit code that makes certain classes or methods available via reflection.


[macOS] Use editing intents from engine

Before
After

Fixes https://github.com/flutter/flutter/issues/85328
Requires https://github.com/flutter/engine/pull/33838
This PR removes most of macOS specific text editing shortcut definitions and instead listens to appropriate selector messages from the engine, translating them into intents.
In order for text editing tests to work correctly, FlutterTester translates unhandled key events (only when defaultTargetPlatform == macOS and active text input) to selectors, similarly to how the engine would.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Couple of issues:

We don't seem to have intents for PageUp and PageDown. Right now those are bounds to ScrollToDocumentBoundaryIntent and ExpandSelectionToDocumentBoundaryIntent, but that doesn't seem correct.
Escape key needs to be handled by the IME, which either hides the IME selection window or produces cancelOperation action if there is no IME selection window. We should probably have CancelOperationIntent for this that would be triggered by cancelOperation on macOS and escape key on other platforms / when not editing.

@LongCatIsLooong, @justinmc, any thoughts?

The change LGTM except for the one question.

This PR will need https://github.com/flutter/engine/pull/33838 to be rolled into flutter/flutter to avoid breaking. This might take a few days.

@dkwingsmt This should be aready in (https://github.com/flutter/flutter/pull/108602 merged).

@tgucio That was way faster than my past experience! Thanks for letting me know.

Is this PR ready to go? Shall we add auto-submit to it?


Error "It seems the App source is not there.." fixed

If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[ ] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[ ] Named the cask according to the token reference.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.
[ ] Checked there are no open pull requests for the same cask.
[ ] Checked the cask was not already refused in closed issues.
[ ] Checked the cask is submitted to the correct repo.

Thank you, but this has several problems. You’re adding unnecessary lines (why?); it has a “no newline at end of file” warning (those are actually meaningful); the commit message does not include the cask’s name.
Thank you again for the submission, fixing in a different PR.


Shape Up

https://basecamp.com/shapeup/0.1-foreword

https://github.com/mefengl/what-i-try/issues/7


Fixes #142 - Deploy the automatic build on Appveyor

Finally I decided to try Appveyor before using VS Team Services.
The draft project is available here: https://ci.appveyor.com/project/oleg-nenashev/winsw
TODOs:

[x] Appveyor should generate a temporary SNK file (temporary solution)
[x] Build process should be passing
[x] Appveyor should be launching and reporting tests from the DLL (NUnit 2?)
[x] Artifacts should be published for each build (WinSW.exe and maybe configuration sample)

@reviewbybees just in case

Well, now I just need to fix the test failures. Which is good...

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

@reviewbybees done.
Merging a a maintainer since it is not a code part && I want to unblock PR builder and test PRs. If there are any concerns, I will address them in follow-up patches


v1.11 backports 2023-05-28

[ ] #25674 -- envoy: Never use x-forwarded-for header, add for Cilium Ingress (@jrajahalme)

:warning: skip the second commit as related files are not available in 1.11

Once this PR is merged, you can update the PR labels via:
$ for pr in 25674; do contrib/backporting/set-labels.py $pr done 1.11; done

/test-backport-1.11

/test-1.18-4.9

/test-1.21-4.9

/test-1.21-5.4

test-1.21-5.4 failed due to Suite-k8s-1.21.K8sUpdates Tests upgrade and downgrade from a Cilium stable image to master, which seems to be a flake, re-run one more time to confirm if it's persistent.

/test-1.21-5.4


kubectl get statefulsets/X fails

$ kubectl describe statefulsets/my-statefulset
error: no kind "GetOptions" is registered for version "apps/v1"

Useful
Info

Versions
Rancher v2.0.6 UI: v2.0.61

Access
local admin

Route
containers.index

Please see https://github.com/kubernetes/kubernetes/issues/59867


Solitude Battle Locked Door Issue (Cutting Room Floor?)

Fought to the door to enter the castle but it was locked. Looked around and found a door I could go in for the Thalmor Headquarters (added by Cutting Room Floor). Doing so triggered the dialogue with Tullius and Rikke even though they were in an inaccessible part of the cell. When it got to the point in the script where they become hostile, Ulfric etc. went back outside, so the battle took place out on the castle walls. Otherwise, still worked mostly normally, give or take Galmar being stuck in bleedout animation.

This is probably due to the last stand of solitude fixes I haven’t gotten last stand of windhelm so idk if it works but the proper battle for windhelm as imperials functions perfectly fine

I’d just like to add that it is a good thing you are doing the stormcloak side as it allows me to focus on the imperials, one thing I do think you should do is intentionally lose the battle of solitude then lose all holds up to windhelm then win and lose windhelm then do the civil war as normal to ensure everything in the stormcloak side functions normally

Also test switching sides from imperials to stormcloaks during seasons unending

Also no this isn’t a cutting room floor thing, I have that installed as well
( I want to experience the true Skyrim not the one we got)

Additionally this sometimes applies to Markarths commanders door as that is also sometimes locked
while I don’t think this is a cutting room floor issue it is still worth looking into

Fought to the door to enter the castle but it was locked. Looked around and found a door I could go in for the Thalmor Headquarters (added by Cutting Room Floor). Doing so triggered the dialogue with Tullius and Rikke even though they were in an inaccessible part of the cell. When it got to the point in the script where they become hostile, Ulfric etc. went back outside, so the battle took place out on the castle walls. Otherwise, still worked mostly normally, give or take Galmar being stuck in bleedout animation.

question did you try the upstairs door as well?

There are 2 doors the bottom door and top door, if the bottom door was locked then try the top door

Fought to the door to enter the castle but it was locked. Looked around and found a door I could go in for the Thalmor Headquarters (added by Cutting Room Floor). Doing so triggered the dialogue with Tullius and Rikke even though they were in an inaccessible part of the cell. When it got to the point in the script where they become hostile, Ulfric etc. went back outside, so the battle took place out on the castle walls. Otherwise, still worked mostly normally, give or take Galmar being stuck in bleedout animation.

can you try to bleed out in the interior section?

I went into the Thalmor Headquarters, and that triggered things enough for them to come outside. At that point, they were outside, so no, I did not try any other doors.
Solitude is no longer on fire and people are going about their business as normal. Not sure how I'd manage to bleed out.

Wait so when you originally went in they were going about their normal business?

What I mean is after the battle outside solitude the battle inside solitude
1 is it burning
2 have you tried the normal 2 doors of castle dour?
3 have you tried bleeding out if point 1 is achieved?

No. They are now, after the battle, traveling away, etc. The quest is completed.

No. They are now, after the battle, traveling away, etc. The quest is completed.

Do you have the save to repeat the above points?

Also send a picture of the mcm menu when you are inside solitude

I want to make sure this isn’t an issue similar to the battle of Whiterun and Markarth where they don’t function properly additionally the bleed out is to see if it triggers a lose condition or if it triggers the victory scene

I also want you to download a mod from Bethesda.com called cheat room by bradenm he has a cheat spell which allows you to unlock locked doors, I want you to unlock that locked door and tell me if you can move when you enter castle dour

This could just be solitude locked door or it could be a bigger issue, we need to rule out the latter before we know it is the former

No, I did not make a save there.

No, I did not make a save there.

Damn

When I get home today I’ll test it with the latest release

https://github.com/schofida/CWORR/issues/44#issuecomment-1522663493
This is comment reference

Will test this when I get home

@LABWAZHERE @Eve-Knight I'm HERE! :)
I just pushed a release https://github.com/schofida/CWORR/releases/tag/v1.0.8a which makes many changes based on both of your feedback. I will be responding specifically to the issues to let you all know what was addressed tomorrow. I am on East Coast USA. It is 1:30 in the morning and I am very tired :)

Oof have a good night

I may not have much time to test this tonight as I wake up at 6am and am unavailable until like 5 or 6 pm, but I’ll test as much as I can

UPDATE: i have determined, this isn't a bug but an intentional feature, it make sense the bottom door would be locked and considering the fact that the upper door has a barricade defending it, this is intentional
what i did determine is that the freeze glitch occured for a bit until the kill scene

Just add a patch for cutting room floor to lock the thalmor embassy

Thank you @LABWAZHERE for testing. Will close


[now.json] Route methods not taken into account in Dev AND Prod

One of my route's "methods": ["POST"] directive is completely skipped both when running now dev and when deployed.
Reprod

Deployment : https://issue-now-route-methods.flawyte.now.sh/api/contact
Should return a 404 but instead returns a 200 with the message from the lambda.

Source : https://github.com/flawyte/issue-now-route-methods

Additional info

now --version : 16.3.1

Hey there @flawyte, thanks for the detailed repro instructions.
It turns out that this is a misunderstanding of how the routes array is processed. I have created a PR on your repo with my suggested fix and an explanation of the changes. Please take a look and let me know if you have any more questions. Cheers!


Accessing Perplexica at least within LAN should be allowed

Is your feature request related to a problem? Please describe.
Accessing Perplexica at least within LAN should be allowed
Describe the solution you'd like
Solving the "Uncaught (in promise) TypeError: NetworkError when attempting to fetch resource. " related to CORS cross origin issues (can be seen in the browser console when loading the frontend from another PC in the same network)
Describe alternatives you've considered
/
Additional context
It's just the CORS configuration that is missing (or by the way the root of the CORS problem), I think it would be nice to be able to either access Perplexica from LAN and/or use proxies (like cloudflare) to be able to access it on the go.

same issue had to change to device ip on network, and ollama is running on another device on network, must rebuild and not docker compose up -d


add getCurrent mode at ios,need read two times,please for example

I apologize for the late reply.
Thanks for helping out with the iOS portion of the plugin @wanghaiyang5241!
I would like to clarify your comment on line 34 in example/lib/main.dart. What do you mean by no push message from iOS to flutter?

I apologize for the late reply.
Thanks for helping out with the iOS portion of the plugin @wanghaiyang5241!
I would like to clarify your comment on line 34 in example/lib/main.dart. What do you mean by no push message from iOS to flutter?

Austrian, this in itself should start from the way ios judges the current mode
(1) They essentially call a piece of music to play, and then judge the current mode based on the interval.
(2) Every time I call this logic, I refer to other people’s plug-ins, but when they return to the mode, they are all in the callback of the swift function. However, flutter calls swift only synchronously, which is currently the case. . So if you only call it once, you need to write a piece of code again to send the pattern in the callback from the bottom of swift to flutter.
(3) Because of my limited working time, I can only store the callback value obtained from the first call in a variable, so that I only need to wait about 100ms in the flutter layer and get it again. In fact, I get that variable. It is the mobile phone mode before 100ms.
(4) This is the reason why I have to do it twice. The best way at present is to do stream notification, but my current work does not require real-time monitoring, as long as a certain instant judgment is enough.

I understand it better now. Thanks for the detailed explanation!
Thank you for taking your time to help out with the iOS portion of this plugin


[Tracking] [Wave Collect] [Quick Action] NewDot: Quick Action Button

Design Doc
Proposal
WN
Strategy: We’re migrating customers to our new superapp where an abundance of choice and feature discovery is at the forefront to encourage them to “land and expand” across a growing number of use cases. That said, it’s crucial that we maintain the streamlined usability our existing customers know and love. Getting the balance right is important for both the success of reunification, and the long term usability of our superapp.
Problem: We’ve over indexed Global Create to optimise for feature discovery, at the expense of our core use cases. Put plainly, it takes more steps to scan a receipt in NewDot than it does on the OldApp. This is important to address now as migration plans are in progress, to avoid the “first look” of our new app being one that adds more time and effort to perform an action taken a thousand times before, increasing the likelihood to return to Classic. Needless to say, this is already coming up with our employees as early adopters.
Solution: Add a quick action button to the bottom of global create. The button will record the last action you took (i.e Request Money > Scan) and the destination for it (i.e To: Duraflame, Inc.). When used for submitting receipts to a workspace like this example, we’ll also stop showing the confirmation page to enter additional expense details unless the workspace has required categories or tags for coding, a la “fire and forget” in OldApp.
Tasks

[x] Post Proposal (full Problem/Solution statement) in #whatsnext
[x] Wait at least one full business day, and until the post has a majority (2/3) of positive reactions (👍)
[x] Paste Proposal in the space above with a link to the Slack thread
[x] Email<EMAIL_ADDRESS>and paste in the Proposal
[x] Fill out the High-level overview of the problem, Timeline, and Terminology sections of the Design Doc
[x] Email<EMAIL_ADDRESS>(continue the same email chain as before) with the link to your Design Doc
[x] Host a pre-design meeting (example) in #expensify-open-source to discuss any necessary details in public before filling out the High-level of proposed solution section.
[x] Fill out the High-level of proposed solution section
[x] Email<EMAIL_ADDRESS>again with links to the doc and pre-design conversation in Slack
[x] Add the DesignDocReview label to get the High-level of proposed solution section reviewed
[x] Respond to any questions or concerns and bring up blockers in Slack to get a consensus if necessary
[x] Confirm that the doc has the minimum necessary number of reviews before proceeding
[x] Host another pre-design meeting in #expensify-open-source to ask for engineering feedback on the technical solution.
[x] Fill out the Detailed implementation of the solution and related sections.
[x] Re-add the DesignDocReview label to this issue
[x] Respond to any questions or concerns and bring up blockers in Slack to get consensus if necessary
[x] Confirm that the doc has the minimum necessary number of reviews before proceeding
[ ] Email<EMAIL_ADDRESS>one last time to let them know the Design Doc is moving into the implementation phase
[ ] Implement the changes
[ ] Add regression tests so that QA can test your feature with every deploy (instructions)
[ ] Send out a follow up email to<EMAIL_ADDRESS>once everything has been implemented and do a Project Wrap-Up retrospective that provides:

Summary of what we accomplished with this project
What went well?
What could we have done better?
What did we learn?

Implementation Issues

[x] https://github.com/Expensify/Expensify/issues/377599
[x] https://github.com/Expensify/Expensify/issues/377602
[x] https://github.com/Expensify/App/issues/38048
[ ] https://github.com/Expensify/App/issues/38050
[ ] https://github.com/Expensify/App/issues/38051
[ ] https://github.com/Expensify/App/issues/38054
[ ] https://github.com/Expensify/Expensify/issues/377606

Pre-design here. Threads are dying down, plan to get the HL doc together by the start of next week.

plan to get the HL doc together by the start of next week.

Alrighty, ideal nav ended up being ready to launch last week, so it knocked my timeline out by a couple of days. But the HL is now out for review.

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

Updated to #wave6, as we switch these features over from wave5 to wave6.

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

We have sufficient reviews, and @Gonals has made a start on the detailed!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

Issues created:

[ ] https://github.com/Expensify/Expensify/issues/377599
[ ] https://github.com/Expensify/Expensify/issues/377602
[ ] https://github.com/Expensify/App/issues/38048
[ ] https://github.com/Expensify/App/issues/38050
[ ] https://github.com/Expensify/App/issues/38051
[ ] https://github.com/Expensify/App/issues/38054
[ ] https://github.com/Expensify/Expensify/issues/377606

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

Wahoo! Let's get it! Few questions for yah here: https://expensify.slack.com/archives/C036QM0SLJK/p1710290076770649?thread_ts=1710203466.272029&cid=C036QM0SLJK

Auth PR in review
PHP PR in review (although unrelated tests are failing, but we don't need it to move on with App stuff)
Starting with App PRs tomorrow

Update here: https://expensify.slack.com/archives/C036QM0SLJK/p1710800428559829

Still cracking through the issues. https://github.com/Expensify/App/issues/38050 is the focus right now.

I have read and reviewed this Design Doc!

I have read and reviewed this Design Doc!

Working on Skipping confirmation! It is being a bit more cumbersome than expected!

Skipping confirmation finally in review! https://github.com/Expensify/App/pull/39413
I'll start adding tracking stuff soon

Latest update here.

Latest here.

Current PR situation:
Issues created:

[x] https://github.com/Expensify/Expensify/issues/377599
[x] https://github.com/Expensify/Expensify/issues/377602
[x] https://github.com/Expensify/App/issues/38048
[x] https://github.com/Expensify/App/issues/38050
[ ] https://github.com/Expensify/App/issues/38051
[ ] https://github.com/Expensify/App/issues/38054
[ ] https://github.com/Expensify/Expensify/issues/377606
[x] https://github.com/Expensify/Expensify/issues/386006
[ ] https://github.com/Expensify/Expensify/issues/385309
[ ] https://github.com/Expensify/Expensify/issues/386320
[ ] https://github.com/Expensify/Expensify/issues/378892

Latest here.

Latest here. We're launch ready!

Latest here. TL;DR - just the educational tooltip polish PR to go.

Educational tooltip PR still in review
Regression tests have been handed over to Applause

QA are adding regression tests and we have the educational tooltip polish PR deep in review!

Regression tests have been added, checking in on the tooltip.

Tooltip PR super close, that's it to close this out.

No change, merge freeze now.

Bumped @tienifr today on the final feedback.

Checked-in on the tooltip.

Conflicts to resolve, bumped on those and resolution of this final bug in the tooltip PR.

Latest.

Latest.

Latest. Over to Rocio and Alberto and we can finally get that merged. 🙏

PR has been merged! @Gonals, all set to send the wrap-up for the project and close this out. :)

Wrap-up sent. Couple of days to go on the regression period for the tooltip polish, and then we'll close this.

Regression period over, closing!


Crop overlay not showing in Chrome

Issue doesn't seem to depend on crop parameters.
I'm on  51.0.2704.103

What crop parameters are you getting this issue on?

Closing due to inactivity


Win Ver 10.0.19041.84 Isuue Listener State: Not Listening

Restart your computer - sometimes it's the only way to properly reload the terminal services. Make sure your antivirus program isn't getting in the way, make sure your .ini file isn't using unix line endings (#1191 )
Also, could you let us know whose .ini file you are using?

@robbak not the original reporter, but I have the same issue. I'm using the online .ini file, and I'm not finding a section in rdpwrap.ini for 10.0.19041.84.

@robbak found your comment in another issue re: affinityv's file. It does have the section. I'm assuming this will work now. Thanks!

Applicable to https://github.com/stascorp/rdpwrap/issues/1004


⚠ Bofrost.de has degraded performance

In b9145f6, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1313 ms

Resolved: Bofrost.de performance has improved in b88a0e3 after 1 hour, 1 minute.


Fix busted ellipsoid bounding spheres

The code fix is from @mramato, I just did some testing and fixed the unit tests.
Fixes #4866.

Tests and code example in #4866 all look good.

Warrants a CHANGES update since the forum reported this.  @emackey can you update master and also post on the forum in the linked issue?  Thanks.