Use ... args in log for multiple prints

fixes log probably also i really want to fix callset for multiple args but idk

this is a good pr


Migrating in Azure

Can this procedure be used to migrate a custom domain from one Web App to another in Azure (for example, when creating a new app plan to scale up to PremiumV2)?
The customer's specific concern in this situation is whether mapping a custom domain to a new app would remove the mapping from the old app.

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

ID: d435391c-b16d-8392-c53f-ebbc2b707630
Version Independent ID: edb59400-bfdd-1287-7c7c-d34f513f4c51
Content: Migrate an active DNS name to Azure App Service
Content Source: articles/app-service/app-service-custom-domain-name-migrate.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

@dcbrown16 Thanks for the feedback! We are currently investigating and will update you shortly.

This is the exact scenario I am facing and would be great if we could use this same approach to migrating internal to Azure. I want to move a site to a PremiumV2 App Instance with 0 downtime.

@dcbrown16 and @ryanlward I do not see why you could not attempt this with two current app services.
Another option would be to use Azure Traffic Manager. Turn on the endpoint for the premium site when you are ready. Once you verify traffic is hitting the premium site, turn off the old endpoint.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

@BryanTrach-MSFT @ryanlward
I discovered that there actually is a restriction in moving custom domains from Azure to Azure.
https://blogs.msdn.microsoft.com/appserviceteam/2017/06/21/custom-hostnames-with-app-service/
Per that blog, if your new and old web apps happen to be on the same scale unit, the old binding will be lost when you register the new binding. You can't have the same domain tied to multiple apps on the same scale unit.
@BryanTrach-MSFT can we reopen this and request that this limitation be added to the documentation for future reference? Thanks!

@dcbrown16 I just verified and yes, you cannot have a custom domain on the same scale unit. The workaround would be to have your destination site in a different scale unit. That means though you won't be able to use the 'change app service plan' blade as it requires the source and destination ASP to be in the same scale unit. The workaround then would be to either clone or manually move your site files.
I have reopened the issue and assigned it to the doc author to investigate if an update is required.

Thanks for checking, @BryanTrach-MSFT . In my understanding, there's no foolproof way to ensure that you end up on a different scale unit when creating a new ASP (other than going to another region). In fact, as originally indicated, in this case the customer was trying to scale from Standard to Premium v2 and unable to select Premium v2 on the original Web App, so I'm confused as to how the new Premium v2 Web App ended up on the same scale unit as the old Standard one.
If it doesn't make sense on the doc linked to this issue, the other place this warning might work would be the Custom Domain tutorial.
https://docs.microsoft.com/en-us/Azure/app-service/app-service-web-tutorial-custom-domain

do we have any links explaining the ways to get access to GoDaddy's account that we create during the process of buying a custom domain using azure credit at Azure portal please!

@sanjaygdrrad please create a ticket of your own for separate inquiries.

@dcbrown16 Sorry for the delay. I've updated the doc with the information now and it should be published sometime today. #please-close


Allow Hystrix  to be used as lambda

The end game here is to be able to use Hystrix with java 8 lambdas
    try (HystrixRequestContext context = HystrixRequestContext.initializeContext();)
    {
      int result = execute(asKey("unittest"), () -> number * 10);
      Assert.assertEquals(70, result);
    }

NetflixOSS » Hystrix » Hystrix-pull-requests #360 SUCCESS
This pull request looks good

My initial thought is that this is a fine thing to do, but belongs outside of hystrix-core.  This change essentially separates out HystrixCommand into 3 pieces: GroupKey, execution behavior, and fallback behavior.
There's much more that's possible to configure on a HystrixCommand, and I think matching the config capabilities of a direct HystrixCommand object takes away from the readability gains of the lambda-syntax.
hystrix-core also has functionality which you haven't modeled yet: HystrixObservableCommand, and the queue(),observe(), toObservable() method of executing commands.  It's completely fine to not model those pieces of functionality if your use case doesn't require them, but then this code should be outside of hystrix-core.
Would anyone else in the community use this feature if added?

Also, I think adding the Closeable interface makes sense, regardless of the rest of the PR.  If you'd like to submit that as a standalone PR, I'd be happy to merge that in.

Done...
https://github.com/Netflix/Hystrix/pull/1111

NetflixOSS » Hystrix » Hystrix-pull-requests #363 FAILURE
Looks like there's a problem with this pull request

@mattrjacobs I prefer to include queue(), observe(), toObservable() =D
So, how does it feel to be able to do this:
    try (HystrixRequestContext context = initializeContext();) {
      int result = queue(asKey("unittest"), () -> number / 0, () -> -1)
          .get(1, TimeUnit.SECONDS);

observable:
    try (HystrixRequestContext context = initializeContext();) {
      observe(asKey("unittest"), () -> number / 0)
        .map(arg -> arg.byteValue())
        .toBlocking()
        .forEach(asByte -> System.out.println(asByte));
    }

How do you intend to pass constructor arguments to command instances?

Overloading with HystrixCommand.setter should cover all constructor arguments right?
    try (HystrixRequestContext context = initializeContext();) {
      int result = queue(
          Setter
              .withGroupKey(asKey("unittest"))
              .andThreadPoolKey(HystrixThreadPoolKey.Factory.asKey("testpool")),
          () -> number / 0,
          () -> -1)
              .get(1, TimeUnit.SECONDS);

So far I have only used HystrixCommandGroupKey, shame on me

That's one aspect of this - configuration of commands is sometime fairly detailed, sometimes not.
The other aspect is that almost all useful concrete impls of HystrixCommand accept domain arguments (customer ID, country, widget ID, etc...)
So straightline code without your syntactic sugar looks something like:
HystrixCommand<Widget> cmd = new WidgetCommand(12345L, Country.US)
Observable<Widget> w = cmd.observe();

In this case assume that run() / getFallback() are implemented in a standard way.
So in your lambda case, your closures for run() / getFallback() would be able to use variables from the current scope.  So, I don't think there's a loss of functionality.
I'm still on the fence about whether to include this proposal or not.  Is anyone on the sidelines willing to chime in and say whether you think that would be a useful addition?

Closing due to inactivity.  Please re-open if there's more to discuss.


Haproxy 1.8.9

Motivation for this change
This fixes CVE-2018-10184 a potential remote denial of service in the
http/2 module and CVE-2018-11469. The version bump also includes various other changes that
are described in the changelog [1]:
2018/05/18 : 1.8.9
    - BUG/MINOR: pattern: Add a missing HA_SPIN_INIT() in pat_ref_newid()
    - BUG/MAJOR: channel: Fix crash when trying to read from a closed socket
    - BUG/MINOR: log: t_idle (%Ti) is not set for some requests
    - BUG/MEDIUM: lua: Fix segmentation fault if a Lua task exits
    - MINOR: h2: detect presence of CONNECT and/or content-length
    - BUG/MEDIUM: h2: implement missing support for chunked encoded uploads
    - BUG/MINOR: lua/threads: Make lua's tasks sticky to the current thread
    - BUG/MINOR: config: disable http-reuse on TCP proxies
    - BUG/MINOR: checks: Fix check->health computation for flapping servers
    - BUG/MEDIUM: threads: Fix the sync point for more than 32 threads
    - BUG/MINOR: lua: Put tasks to sleep when waiting for data
    - DOC/MINOR: clean up LUA documentation re: servers & array/table.
    - BUG/MINOR: map: correctly track reference to the last ref_elt being dumped
    - BUG/MEDIUM: task: Don't free a task that is about to be run.
    - BUG/MINOR: lua: schedule socket task upon lua connect()
    - BUG/MINOR: lua: ensure large proxy IDs can be represented
    - BUG/MEDIUM: http: don't always abort transfers on CF_SHUTR
    - BUG/MEDIUM: pollers: Use a global list for fd shared between threads.
    - BUG/MEDIUM: ssl: properly protect SSL cert generation
    - BUG/MINOR: spoe: Mistake in error message about SPOE configuration

2018/04/19 : 1.8.8
    - BUG/MEDIUM: threads: Fix the max/min calculation because of name clashes
    - BUG/MEDIUM: connection: Make sure we have a mux before calling detach().
    - BUG/MINOR: http: Return an error in proxy mode when url2sa fails
    - BUG/MEDIUM: kqueue: When adding new events, provide an output to get errors.
    - BUG/MINOR: cli: Guard against NULL messages when using CLI_ST_PRINT_FREE
    - MINOR: cli: Ensure the CLI always outputs an error when it should
    - DOC: lua: update the links to the config and Lua API
    - BUG/CRITICAL: h2: fix incorrect frame length check

2018/04/07 : 1.8.7
    - BUG/MAJOR: cache: always initialize newly created objects
    - MINOR: servers: Support alphanumeric characters for the server templates names

2018/04/05 : 1.8.6
    - BUG/MINOR: lua: the function returns anything
    - BUG/MINOR: lua funtion hlua_socket_settimeout don't check negative values
    - BUILD/MINOR: fix build when USE_THREAD is not defined
    - MINOR: cli/threads: make "show fd" report thread_sync_io_handler instead of "unknown"
    - MINOR: cli: make "show fd" report the mux and mux_ctx pointers when available
    - BUILD/MINOR: cli: fix a build warning introduced by last commit
    - BUG/MINOR: hpack: fix harmless use of uninitialized value in hpack_dht_insert
    - CLEANUP: h2: rename misleading h2c_stream_close() to h2s_close()
    - MINOR: h2: provide and use h2s_detach() and h2s_free()
    - BUG/MAJOR: h2: remove orphaned streams from the send list before closing
    - MINOR: h2: always call h2s_detach() in h2_detach()
    - MINOR: h2: fuse h2s_detach() and h2s_free() into h2s_destroy()
    - BUG/MEDIUM: h2/threads: never release the task outside of the task handler
    - BUG/MEDIUM: h2: don't consider pending data on detach if connection is in error
    - BUILD/MINOR: threads: always export thread_sync_io_handler()
    - BUG/MEDIUM: h2: always add a stream to the send or fctl list when blocked
    - BUG/MINOR: checks: check the conn_stream's readiness and not the connection
    - BUG/MINOR: email-alert: Set the mailer port during alert initialization
    - BUG/MINOR: cache: fix "show cache" output
    - BUG/MINOR: fd: Don't clear the update_mask in fd_insert.
    - BUG/MAJOR: cache: fix random crashes caused by incorrect delete() on non-first blocks
    - BUG/MINOR: spoe: Initialize variables used during conf parsing before any check
    - BUG/MINOR: spoe: Don't release the context buffer in .check_timeouts callbaclk

2018/03/23 : 1.8.5
    - BUG/MINOR: threads: fix missing thread lock labels for 1.8
    - BUG/MEDIUM: ssl: Don't always treat SSL_ERROR_SYSCALL as unrecovarable.
    - BUG/MEDIUM: ssl: Shutdown the connection for reading on SSL_ERROR_SYSCALL
    - BUG/MINOR: init: Add missing brackets in the code parsing -sf/-st
    - BUG/MINOR: ssl/threads: Make management of the TLS ticket keys files thread-safe
    - BUG/MEDIUM: http: Switch the HTTP response in tunnel mode as earlier as possible
    - BUG/MEDIUM: ssl/sample: ssl_bc_* fetch keywords are broken.
    - DOC: lua: new prototype for function "register_action()"
    - DOC: cfgparse: Warn on option (tcp|http)log in backend
    - BUG/MINOR: debug/pools: properly handle out-of-memory when building with DEBUG_UAF
    - MINOR: debug/pools: make DEBUG_UAF also detect underflows
    - BUG/MINOR: h2: Set the target of dbuf_wait to h2c
    - MINOR: stats: display the number of threads in the statistics.
    - BUG/MEDIUM: h2: always consume any trailing data after end of output buffers
    - BUG/MEDIUM: buffer: Fix the wrapping case in bo_putblk
    - BUG/MEDIUM: buffer: Fix the wrapping case in bi_putblk
    - Revert "BUG/MINOR: send-proxy-v2: string size must include ('\0')"
    - MINOR: systemd: Add section for SystemD sandboxing to unit file
    - MINOR: systemd: Add SystemD's Protect*= options to the unit file
    - MINOR: systemd: Add SystemD's SystemCallFilter option to the unit file
    - MINOR/BUILD: fix Lua build on Mac OS X
    - BUILD/MINOR: fix Lua build on Mac OS X (again)
    - BUG/MINOR: session: Fix tcp-request session failure if handshake.
    - CLEANUP: .gitignore: Ignore binaries from the contrib directory
    - BUG/MINOR: unix: Don't mess up when removing the socket from the xfer_sock_list.
    - BUG/MEDIUM: h2: also arm the h2 timeout when sending
    - BUG/MINOR: cli: Fix a crash when passing a negative or too large value to "show fd"
    - CLEANUP: ssl: Remove a duplicated #include
    - CLEANUP: cli: Remove a leftover debug message
    - BUG/MINOR: cli: Fix a typo in the 'set rate-limit' usage
    - BUG/MEDIUM: fix a 100% cpu usage with cpu-map and nbthread/nbproc
    - BUG/MINOR: force-persist and ignore-persist only apply to backends
    - BUG/MEDIUM: spoe: Remove idle applets from idle list when HAProxy is stopping
    - BUG/MEDIUM: threads/unix: Fix a deadlock when a listener is temporarily disabled
    - BUG/MAJOR: threads/queue: Fix thread-safety issues on the queues management
    - BUG/MINOR: dns: don't downgrade DNS accepted payload size automatically
    - BUG/MINOR: seemless reload: Fix crash when an interface is specified.
    - BUG/MINOR: cli: Fix a crash when sending a command with too many arguments
    - BUILD: ssl: Fix build with OpenSSL without NPN capability
    - BUG/MINOR: spoa-example: unexpected behavior for more than 127 args
    - BUG/MINOR: lua: return bad error messages
    - BUG/MEDIUM: tcp-check: single connect rule can't detect DOWN servers
    - BUG/MINOR: tcp-check: use the server's service port as a fallback
    - BUG/MEDIUM: threads/queue: wake up other threads upon dequeue
    - MINOR: log: stop emitting alerts when it's not possible to write on the socket
    - BUILD/BUG: enable -fno-strict-overflow by default
    - DOC: log: more than 2 log servers are allowed
    - DOC: don't suggest using http-server-close
    - BUG/MEDIUM: h2: properly account for DATA padding in flow control
    - BUG/MINOR: h2: ensure we can never send an RST_STREAM in response to an RST_STREAM
    - BUG/MINOR: listener: Don't decrease actconn twice when a new session is rejected

[1] haproxy.org/download/1.8/src/CHANGELOG
Probably obsoletes #37998 as soon as the Darwin build succeeds.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build haproxy

Success on x86_64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
moving /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/doc to /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/share/doc
shrinking RPATHs of ELF executables and libraries in /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9
shrinking /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/sbin/haproxy
gzipping man pages under /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/share/man/
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/sbin
patching script interpreter paths in /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9
checking for references to /build in /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9...
moving /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/sbin/* to /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/bin
/nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9

Failure on x86_64-darwin (full log)
Attempted: haproxy
Partial log (click to expand)
include/proto/fd.h:154:31: error: use of undeclared identifier 'all_threads_mask'
        if ((fdtab[fd].update_mask & all_threads_mask) == 0) {
                                     ^
src/ev_poll.c:115:30: error: use of undeclared identifier 'all_threads_mask'
                        fdtab[fd].update_mask &= ~all_threads_mask;
                                                  ^
2 errors generated.
make: *** [Makefile:909: src/ev_poll.o] Error 1
builder for '/nix/store/6g9i8i7y2h1g4yfizmnla2riv57j66ad-haproxy-1.8.9.drv' failed with exit code 2
error: build of '/nix/store/6g9i8i7y2h1g4yfizmnla2riv57j66ad-haproxy-1.8.9.drv' failed

Success on aarch64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
moving /nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9/doc to /nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9/share/doc
shrinking RPATHs of ELF executables and libraries in /nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9
shrinking /nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9/sbin/haproxy
gzipping man pages under /nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9/share/man/
strip is /nix/store/qg2agrqkf240s656d207zqhipl0bc2id-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9/sbin
patching script interpreter paths in /nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9
checking for references to /build in /nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9...
moving /nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9/sbin/* to /nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9/bin
/nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9

Success on aarch64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9

Failure on x86_64-darwin (full log)
Attempted: haproxy
Partial log (click to expand)
include/proto/fd.h:154:31: error: use of undeclared identifier 'all_threads_mask'
        if ((fdtab[fd].update_mask & all_threads_mask) == 0) {
                                     ^
src/ev_poll.c:115:30: error: use of undeclared identifier 'all_threads_mask'
                        fdtab[fd].update_mask &= ~all_threads_mask;
                                                  ^
2 errors generated.
make: *** [Makefile:909: src/ev_poll.o] Error 1
builder for '/nix/store/6g9i8i7y2h1g4yfizmnla2riv57j66ad-haproxy-1.8.9.drv' failed with exit code 2
error: build of '/nix/store/6g9i8i7y2h1g4yfizmnla2riv57j66ad-haproxy-1.8.9.drv' failed

Success on x86_64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9

@GrahamcOfBorg build haproxy

Success on aarch64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9

Failure on x86_64-darwin (full log)
Attempted: haproxy
Partial log (click to expand)
include/proto/fd.h:154:31: error: use of undeclared identifier 'all_threads_mask'
        if ((fdtab[fd].update_mask & all_threads_mask) == 0) {
                                     ^
src/ev_poll.c:115:30: error: use of undeclared identifier 'all_threads_mask'
                        fdtab[fd].update_mask &= ~all_threads_mask;
                                                  ^
2 errors generated.
make: *** [Makefile:909: src/ev_poll.o] Error 1
builder for '/nix/store/xd7a0f7czj4niasxf32nh99qxmblz2ik-haproxy-1.8.9.drv' failed with exit code 2
error: build of '/nix/store/xd7a0f7czj4niasxf32nh99qxmblz2ik-haproxy-1.8.9.drv' failed

Success on x86_64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
moving /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/doc to /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/share/doc
shrinking RPATHs of ELF executables and libraries in /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9
shrinking /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/sbin/haproxy
gzipping man pages under /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/share/man/
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/sbin
patching script interpreter paths in /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9
checking for references to /build in /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9...
moving /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/sbin/* to /nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9/bin
/nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9

Success on x86_64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9

Success on aarch64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9

Failure on x86_64-darwin (full log)
Attempted: haproxy
Partial log (click to expand)
include/proto/fd.h:154:31: error: use of undeclared identifier 'all_threads_mask'
        if ((fdtab[fd].update_mask & all_threads_mask) == 0) {
                                     ^
src/ev_poll.c:115:30: error: use of undeclared identifier 'all_threads_mask'
                        fdtab[fd].update_mask &= ~all_threads_mask;
                                                  ^
2 errors generated.
make: *** [Makefile:909: src/ev_poll.o] Error 1
builder for '/nix/store/xd7a0f7czj4niasxf32nh99qxmblz2ik-haproxy-1.8.9.drv' failed with exit code 2
error: build of '/nix/store/xd7a0f7czj4niasxf32nh99qxmblz2ik-haproxy-1.8.9.drv' failed

@GrahamcOfBorg build haproxy

Success on aarch64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9

Failure on x86_64-darwin (full log)
Attempted: haproxy
Partial log (click to expand)
include/proto/fd.h:154:31: error: use of undeclared identifier 'all_threads_mask'
        if ((fdtab[fd].update_mask & all_threads_mask) == 0) {
                                     ^
src/ev_poll.c:115:30: error: use of undeclared identifier 'all_threads_mask'
                        fdtab[fd].update_mask &= ~all_threads_mask;
                                                  ^
2 errors generated.
make: *** [Makefile:909: src/ev_poll.o] Error 1
builder for '/nix/store/xd7a0f7czj4niasxf32nh99qxmblz2ik-haproxy-1.8.9.drv' failed with exit code 2
error: build of '/nix/store/xd7a0f7czj4niasxf32nh99qxmblz2ik-haproxy-1.8.9.drv' failed

Success on x86_64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9

@GrahamcOfBorg test haproxy

Success on x86_64-linux (full log)
Attempted: tests.haproxy
Partial log (click to expand)
machine: running command: sync
machine# [   33.377054] dhcpcd[778]: eth0: Router Advertisement from fe80::2
machine# [   33.378207] dhcpcd[778]: eth0: adding address fec0::5054:ff:fe12:3456/64
machine: exit status 0
test script finished in 35.25s
cleaning up
killing machine (pid 593)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/3qa06d9wzqiip12msi247skf1vh0zq1p-vm-test-run-haproxy

Success on x86_64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9

Failure on x86_64-darwin (full log)
Attempted: haproxy
Partial log (click to expand)
include/proto/fd.h:154:31: error: use of undeclared identifier 'all_threads_mask'
        if ((fdtab[fd].update_mask & all_threads_mask) == 0) {
                                     ^
src/ev_poll.c:115:30: error: use of undeclared identifier 'all_threads_mask'
                        fdtab[fd].update_mask &= ~all_threads_mask;
                                                  ^
2 errors generated.
make: *** [Makefile:909: src/ev_poll.o] Error 1
builder for '/nix/store/xd7a0f7czj4niasxf32nh99qxmblz2ik-haproxy-1.8.9.drv' failed with exit code 2
error: build of '/nix/store/xd7a0f7czj4niasxf32nh99qxmblz2ik-haproxy-1.8.9.drv' failed

Success on aarch64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9

@matthewbauer You had a strong opinion about breaking haproxy on darwin in #37998. Do you have any way to test a build on darwin? Ideally to provide a fix.
I've made several attempts at picking some of the upstream build fixes but they don't seem to fix (the complete) mess we get on darwin right now.
As I lack access to any kind of Mac system and start to question the benefit of spending a few more hours getting a hackintosh setup to debug this
I would propose to drop support for Darwin. At least until upstream addressed the issues or released a more stable version. To put it in perspective they are rewriting larger parts of the threading code on a minor/patch version...
cc the maintainers @garbas @fuzzy-id

Success on x86_64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9

@GrahamcOfBorg build haproxy

Success on x86_64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/04vnsms7jsxnqa2026whq5azx7wqcb5q-haproxy-1.8.9

Success on aarch64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9

Success on x86_64-darwin (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/38rmfgbsbzszszv8hcj3cjg7mlxj87ax-haproxy-1.8.9

Success on x86_64-darwin (full log)
Attempted: haproxy
Partial log (click to expand)
        install -m 644 doc/$x.txt "/nix/store/38rmfgbsbzszszv8hcj3cjg7mlxj87ax-haproxy-1.8.9/doc/haproxy" ; \
done
post-installation fixup
moving /nix/store/38rmfgbsbzszszv8hcj3cjg7mlxj87ax-haproxy-1.8.9/doc to /nix/store/38rmfgbsbzszszv8hcj3cjg7mlxj87ax-haproxy-1.8.9/share/doc
gzipping man pages under /nix/store/38rmfgbsbzszszv8hcj3cjg7mlxj87ax-haproxy-1.8.9/share/man/
strip is /nix/store/yyak5sjv68n9vdgnkd2cb5djk1l9sqj5-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/38rmfgbsbzszszv8hcj3cjg7mlxj87ax-haproxy-1.8.9/sbin
patching script interpreter paths in /nix/store/38rmfgbsbzszszv8hcj3cjg7mlxj87ax-haproxy-1.8.9
moving /nix/store/38rmfgbsbzszszv8hcj3cjg7mlxj87ax-haproxy-1.8.9/sbin/* to /nix/store/38rmfgbsbzszszv8hcj3cjg7mlxj87ax-haproxy-1.8.9/bin
/nix/store/38rmfgbsbzszszv8hcj3cjg7mlxj87ax-haproxy-1.8.9

Success on aarch64-linux (full log)
Attempted: haproxy
Partial log (click to expand)
/nix/store/ddvad5m093khg6px9wa05m82f86ipxrd-haproxy-1.8.9

seems that was the right cherry pick :-)

@andir Not sure why applying the patch didn't fail, but it was html content instead of the raw patch.

@LnL7 Thanks! I thought I caught that already. Well this is done and my life can go on :)

Success on aarch64-linux (full log)
Attempted: tests.haproxy
Partial log (click to expand)
machine: exit status 1
syncing
machine: running command: sync
machine: exit status 0
test script finished in 21.19s
cleaning up
killing machine (pid 627)
vde_switch: EOF on stdin, cleaning up and exiting
vde_switch: Could not remove ctl dir '/build/vde1.ctl': Directory not empty
/nix/store/qh1hfrkz259fcl2dg11qkcszqyqmp9vm-vm-test-run-haproxy


Suresoft - continued

@jlinx: @braunms has contributed sth. on suresoft in https://github.com/CaptainSifff/paper_teaching-learning-RSE/pull/67
Do you want ot contribute sth. here?

There was a nicely long paragraph in the Competencies paper, which was compressed into a short mention and then moved to this file for future usage: https://github.com/CaptainSifff/paper_teaching-learning-RSE/blob/6f793779f36897f0dbc35fab4843b5429b85ced3/related-work-training.md#suresoft
I understand this issue as closed.


Support simulating data center disaster

Feature Request
Describe the feature you'd like:
We usually use label to distinguish different data center. To simulating data center disaster, it can provide an API to make all nodes that have the same label crash. To test features like asynchronous replication, it's also required to make those nodes keep offline.
A simple alternative is constructing a network partition between data center.

#262 and #264 support an approach to control nemeses on the test client-side and have provided a new NemesisGeneator named NewCoordinationKillGenerator, you can use it to kill specified nodes when checking.
Here gives a demo shows how to control nemesis in test client:
func (c *Case) Start(ctx context.Context, cfg interface{}, clientNodes []types.ClientNode) error {
	control := ctx.Value("control").(*control.Controller)

	for i := 1; i <= 3; i++ {
		killGenerator, nemesisControl := nemesis.NewCoordinationKillGenerator(c.nodes[0:i])
		control.UpdateNemesisGenerators(core.NewOneRoundNemesisGenerators(killGenerator))
		// Start blocks until nemesis is prepared to start
		nemesisControl.Start(ctx)

		log.Info("nemesis starts")
		time.Sleep(5 * time.Minute)
		log.Info("5 minutes later...")

		// recover nemesis, but won't block.
		nemesisControl.Rollback(ctx)
                ...
	}
        ...
}

Thanks!


Add mobile Station Extension support

Cosmos-Kit now supports a bunch of good mobile options like Keplr or Comsosstation
As a developer looking to use Cosmos-Kit
I want Mobile Station support powered by walletConnect
so that I can offer a full station experience to users on both mobile and web.

signed
Am Mo., 21. Aug. 2023 um 14:00 Uhr schrieb 0xFable @.***

:

Cosmos-Kit now supports a bunch of good mobile options like Keplr or
Comsosstation
As a developer looking to use Cosmos-Kit
I want Mobile Station support powered by walletConnect
so that I can offer a full station experience to users on both mobile and
web.
—
Reply to this email directly, view it on GitHub
https://github.com/cosmology-tech/cosmos-kit/issues/299, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC6MWVJS2FC6ZV2O4NJDUEDXWNEXRANCNFSM6AAAAAA3YIV3VE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi, @0xFable
Usually the wallet integration is implemented by the the wallet developers or the one who need it. Can you help integrate station-mobile in if possible?
https://docs.cosmoskit.com/integrating-wallets/adding-new-wallets#quickly-add-mobile-wallets
Or ask if the developer of @cosmos-kit/station-extension can help to integrate it?
https://github.com/cosmology-tech/cosmos-kit/blob/a3638f3983c0ca3f72a776de2c53f8d90c548a25/wallets/station-extension/package.json#L5

@0xFable Can you confirm that Station Mobile App supports WalletConnect ?
It seems that Station Mobile doesn't support WalletConnect.
https://walletconnect.com/explorer?search=station
Station is not in the result list.


[space-in-parens] doesn't handle comments

tslint: 5.7.0
typescript: 2.5.2
tslint.json:
"rules": {
    "space-in-parens": [true, "never"]
}

Code:
foo(/* test */ 'bar');

Actual behavior:
ERROR: there should be no spaces inside this paren.

Expected  behavior:
Should not throw an error
See:
eslint demo
eslint test

Hey @Patrik-Lundqvist, thanks for logging this bug report.
Please, feel free to open a PR for fixing this, if you'd like to :)

This bug breaks Webpack's named import feature, even if there is no space between the comment and the path.
import(/* webpackChunkName: "dashboard-chunk" */'./views/Dashboard')


Database List Fails to Load

Issue Type: Bug

Connect to Server with 5000 databases (Maximum allowed in Azure).
Attempt to use Servers->Databases.
Error will show "Object Exporer task didn't complete within 45 seconds"

I had already lengthened the timeout in the advance properties of the connection to 120 seconds, but to no avail.  It doesn't seem like listing the DBs should take any appreciable amount of time unless it's trying to run some metadata queries on each one too.
Azure Data Studio version: azuredatastudio 1.3.1-insider (bd53e685d0091f9fe09c2662c30e0e506c402561, 2018-11-09T19:34:35.108Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz (8 x 2904)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.85GB (12.49GB free)

Process Argv
C:\Program Files\Azure Data Studio\azuredatastudio.exe

Screen Reader
no

VM
0%

Extensions: none

Any chance this is likely to make it into a near-term release?  This is the only thing that really holds me back from using this great tool.

Same here.
We "only" have 300 databases but I am also facing this issue with the default timeout of 45 seconds.
I have the same remark: could you perhaps quickly display all databases, then, eventually when required, fetch each database properties in background (on demand).

Getting the same issue after updating to 1.8.0
We have only 10 databases

@g-rad are you getting the error "Object Exporer task didn't complete within 45 seconds" or is the list just failing to expand?

@kburtram I updated my comment. The issue was resolved by using a different db user, I guess it's something to do with permissions.

This persists for me on 1.10.   Even on servers with only 300 databases it will time out.  Oddly, the list of of databases in the Search Widget on the Server Dashboard loads them just fine.  Even when there are 5k DBs.  So it seems like the code that fetches the list of DBs in the Search widget is different than the code that fetches the list of databases in the Servers Pane.

I am also facing same issue with only 100 databases.. Please let me know if any solution for it

Moreover the "Search" area in the server details is able to list all databases quickly, but the Connections explorer does not.
I think you should at least try to use a lightweight query (using master db) to populate the nodes, then perform the long request on background, or only on demand for each node.

Same issue with less than 20 databases !
I'm using user token as authentication method and connecting to Azure SQL database server.

Any chance this issue can be raised further. It has been an issue for coming up to two years and has spanned many versions. It is not like this is an intermittent or isolated issue to a specific version. This is a chronic issue which happens constantly.
I have multiple Azure SQL Servers with varying numbers of databases from as few as 2 up to as much as 60. And this error appears for all.
Error and version details attached:

Same issue on latest version with <100 databases.

Still an issue Please fix this it's really annoying. It makes every task and navigation much more complicated.

Yes, still an issue for me too.
Unfortunately turning it off and turning it back on doesn't fix this one 🙄
Please fix as it's a really annoying issue and it has been open for over two years.

Still an issue for a co-worker who has version 1.29.0 installed. His account can see all databases and objects in SSMS (everything works as you would expect there), but he cannot see them in his Connections window (under the databases folder).

This works for me when there are few databases on the server.  But if there are more than 100 databases this times out for me and I can't browse the databases.
If I create a query I can jump between the databases in the database dropdown fine.  It's just that navigation in the Object Explorer that is not working.

Same issue, 3 years running now, times out even though there are only about 50 databases on the server.
Running a query and connecting immediately shows all the databases in the dropdown. Wish this would get some attention for once.

Happens to me, version 1.34.0.
Heading back to SSMS for now I guess.

Still having this issue in 2022.

Same for me. Please fix this

Kindly update your Azure data studio. Fixed the issue on my end.

Nop, not here.

Well, I thought I'd just share the solution that has just worked for me 30 minutes ago when I faced the same exact issue.

No pb, it reminded me to also check, thanks :)

Please fix this!  I have to keep SSMS running just to use the object explorer!

Same issue for me.

Same error: "Object Exporer task didn't complete within 45 seconds"
Version: 1.39.1 (system setup)
Commit: https://github.com/microsoft/azuredatastudio/commit/7553f799e175f471b7590302dd65c997b838b29b
Date: 2022-08-30T01:11:13.047Z
VS Code: 1.62.0
Electron: 13.6.6
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043

Same issue for me,
Version: 1.39.1 (user setup)
Commit: 7553f799e175f471b7590302dd65c997b838b29b
Date: 2022-08-30T01:11:13.047Z
VS Code: 1.62.0
Electron: 13.6.6
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000

Issue is now fixed with https://github.com/microsoft/azuredatastudio/issues/21475 addressed.
The latest insiders build contains fix, it will be available in the next stable release.


Add USGS association in CAN github

Now that we have more links thanks to Dave, should we add them in our own ?
Or should we use this opportunity to show that nodes does not necessary have symmetric content ?

So long as the USGS node is indexed by Google we should be okay. Perhaps we wait to see if it's crawled...

@denevers is this still relevant?

I can't make sense of it.. good sign it's "no".


Any workaround for the delta~ object?

I'm using the delta~ object in a patch to create a bubbling sound but there doesn't seem to be an alternative for it in heavylib. Any suggestions? The patch itself is based off Andy Farnell's running_water3.pd.

Ended up finding a workaround that didn't use the delta object, but I'm still curious as to whether there's an official workaround with this object.


Allow multiple Audience values on passive STS SAML Assertions

Requirement:
Requirement implies allowing for multiple Audience values on the SAML Assertion responses (RTS) upon successful authentication within the STS authentication flow. This change should apply for both SAML 1.1 and 2.0 issued tokens.
Functional context:
In WS-Trust, returning SAML Assertion has an element called Audience.  By default, it is a single value.
Technical context:
This improvement should be applied to all components associated to the processing of STS SAML Assertions, as well as UI elements associated with the registration of Audiences in the context of the STS service run by the IDP, for specific service providers.

This is a preview image of the IS management console (5.10.0) UI with all associated changes implemented.


Does Obfuscar work with Android Xamarin?

I have tried to adding this to my .csproj file.   The solution builded but error out on "Unable to resolve dependency:  Mono.Android".   How do I get this to work?  Thank you.
<Target Name="AfterBuild">
    <Exec Command=""$(SolutionDir)packages\Obfuscar.2.2.3\tools\Obfuscar.Console.exe"  $(SolutionDir)obfuscar.xml" />
  </Target>

Error Output
1>Target "AfterBuild" in project "D:\Project\App\App\TestApp.csproj" (target "Build" depends on it):
1>Using "Exec" task from assembly "Microsoft.Build.Tasks.Core, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a".
1>Task "Exec"
1>  "D:\Project\App\packages\Obfuscar.2.2.3\tools\Obfuscar.Console.exe"  D:\Project\App\obfuscar.xml
1>  Loading project D:\Project\App\obfuscar.xml...Processing assembly: TestApp, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
1>  Loading assemblies...Extra framework folders:
1>  An error occurred during processing:
1>  Unable to resolve dependency:  Mono.Android
1>D:\Project\App\App\TestApp.csproj(88,5): error MSB3073: The command ""D:\Project\App\packages\Obfuscar.2.2.3\tools\Obfuscar.Console.exe"  D:\Project\App\obfuscar.xml" exited with code 1.
1>Done executing task "Exec" -- FAILED.
1>Done building target "AfterBuild" in project "Http.csproj" -- FAILED.
1>
1>Build FAILED.

Hi,
Is it possible to get Obfuscar to work with Xamarin ?  Thank you.

The current dependency assembly resolution is .NET Framework/PCL only. If you want to target Xamarin.Android, you can try to copy those dependencies manually to the output folder, then Obfuscar will be able to load them. That's a workaround you can try out.

@alberk8
There is now a  tag that you can specify to add the Xamarin assemblies for assembly resolution.

As AOT is coming to Xamarin.Android (see Xamarin's announcement at Build 2017), you can safely use that to obfuscate your code in all necessary aspects without Obfuscar.

AOT for Android is just an option, and it can't be used for some cases, for example, dynamic code generation and expressions trees are only possible with JIT. So there is still value in this.

I hope that the AOT feature will be made available to VS Community version.  :)

@alberk8
There is now a tag that you can specify to add the Xamarin assemblies for assembly resolution.

Which tag is it, not found in doc


Python 3 encoding issue

When reading gzipped VCF you get an error since you compare bytes input (gzip.open) with a unicode string:
  File "/mnt/hds/proj/bioinfo/SERVER/miniconda/envs/stage3/lib/python3.6/site-packages/cg/meta/upload/observations.py", line 31, in upload
    results = self.loqus.load(data['family'], data['pedigree'], data['vcf'])
  File "/mnt/hds/proj/bioinfo/SERVER/miniconda/envs/stage3/lib/python3.6/site-packages/cg/apps/loqus.py", line 19, in load
    nr_variants = check_vcf(variant_handle)
  File "/mnt/hds/proj/bioinfo/SERVER/miniconda/envs/stage3/lib/python3.6/site-packages/loqusdb/vcf_tools/vcf.py", line 70, in check_vcf
    if variant_line.startswith('#'):
TypeError: startswith first arg must be bytes or a tuple of bytes, not str

I could resolve it using:
if file_path.endswith('.gz'):
    file_handle = gzip.open(file_path, 'rt', encoding='utf-8')

However, I'm not sure if this option is only available in Python 3...

This will be fixed by using cyvcf2. I will add that asap


'prompt -p' breakes the prompt line

Please check the existing issues to make sure you're not duplicating a report.
For bug reports, please provide the following information:

Zim commit ref: zsh-zim-git r250.b55ed8a-1
gist of .zimrc: EMPTY
Zsh version: 5.2
gist of .zshrc: EMPTY
$(uname -mosr):Linux 4.8.10-1-ARCH x86_64 GNU/Linux

Description
On a clean install from AUR, running 'prompt -p' doesn't show the themese correctly and breaks the current prompt. After running the command the prompt becomes:
$purpleshak${${reset_color} at $orangesaber${${reset_color} in $limegreen~${${reset_color} $vcs_info_msg_0_$(virtualenv_info)${reset_color}
$ (CURSOR)

Steps to reproduce
current theme is the default (steeph)
Just run 'prompt -p'
Images or other information

it's liquidprompt.
You can verify by running prompt -p liquidprompt

I can reproduce this issue.

In case it helps anyone:
# prompt -p liquidprompt

No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
liquidprompt theme:
[root@li1524-158:~] # command arg1 arg2 ... argn

$purpleroot${${reset_color} at $orangeli1524-158${${reset_color} in $limegreen~${${reset_color} $vcs_info_msg_0_$(virtualenv_info)${reset_color}


cmd/go: "--" after the first "--" is not considered as file

What version of Go are you using (go version)?

$ go version
go version devel +429d2c548d Wed Jun 3 22:07:42 2020 +0000 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

What did you do?
$ cat main.go
package main

import (
	"fmt"
)

func main() {
	fmt.Println("Hello, playground")
}
$ go run -- main.go -- anything

What did you expect to see?
Run fails, error reports like any *nix commands:
$ cat -- main.go -- anything
...
cat: --: No such file or directory
cat: anything: No such file or directory

What did you see instead?
Run success.

--, in gnu flags speak, says to the flag parser, _anything after -- is not a flag, even if it starts with a -. It's still up the program what it wants to do with those arguments.
[/var/folders/wh/k4ydm2jx2tb5tgfvdcddl3ym0000gn/T/go-build621388717/b001/exe/main -- anything]
(~/src) % cat main.go
package main

import (
        "fmt"
        "os"
)

func main() {
        fmt.Println(os.Args)
}
(~/src) % go run -- main.go -- anything
[/var/folders/wh/k4ydm2jx2tb5tgfvdcddl3ym0000gn/T/go-build725222586/b001/exe/main -- anything]

--, in gnu flags speak, says to the flag parser, anything after -- is not a flag, even if it starts with a -. It's still up the program what it wants to do with those arguments.

(~/src) % cat main.go

package main

import (

        "fmt"

        "os"

)

func main() {

        fmt.Println(os.Args)

}

(~/src) % go run -- main.go -- anything

[/var/folders/wh/k4ydm2jx2tb5tgfvdcddl3ym0000gn/T/go-build725222586/b001/exe/main -- anything]

In the case of the cat example you gave, cat expects each of the arguments provided it to be files, so the second -- is treated as a file named --. I don't see why go run should follow those semantics

IIRC, it’s POSIX.
Maybe at least we should add documentation for that?

IIRC, it’s POSIX.

Yes, you are completely correct. I realised after I wrote this that -- probably isn't just a GNUism.

Maybe at least we should add documentation for that?

I don't understand what there is to document, the second -- isn't interpreted as a file because its passed to main.go as os.Args. If anything its the operation of the first -- that is confusing to me.


Streaming=True not working when i integrate Langchain.

import os
from langchain import PromptTemplate, OpenAI, LLMChain
import chainlit as cl
#os.environ["OPENAI_API_KEY"] = "YOUR_OPEN_AI_API_KEY"
template = """Question: {question}
Answer: Let's think step by step."""
llm=OpenAI(temperature=0,streaming=True)
@cl.langchain_factory
def factory():
prompt = PromptTemplate(template=template, input_variables=["question"])
llm_chain = LLMChain(prompt=prompt, llm=llm , verbose=True)

return llm_chain

At the moment the intermediate steps should be streamed and not the final response. Is that the case or even the intermediate steps are not being streamed? You can see https://github.com/Chainlit/chainlit/issues/7#issuecomment-1569969095 for context

import os from langchain import PromptTemplate, OpenAI, LLMChain import chainlit as cl
#os.environ["OPENAI_API_KEY"] = "YOUR_OPEN_AI_API_KEY"
template = """Question: {question}
Answer: Let's think step by step."""
llm=OpenAI(temperature=0,streaming=True)
@cl.langchain_factory def factory():
prompt = PromptTemplate(template=template, input_variables=["question"])
llm_chain = LLMChain(prompt=prompt, llm=llm , verbose=True)

return llm_chain

Since you are using an LLMChain the streamed content will be inside the working box that appears. If you ask it to tell you a 200 word story and then expand the box. You will see that the content within is streaming.
Please confirm if this is working for you so we can close this issue.
If instead you want to stream the content directly. Below is a simple example of how to feed a message directly back to the UI using streaming.
import chainlit as cl

from langchain.chat_models import ChatOpenAI
from langchain.schema import HumanMessage

llm = ChatOpenAI(streaming=True)

@cl.on_message
def main(message: str):
    cl.Message(content="") # Need to set the Message content to be blank before trigging the llm.
    llm([HumanMessage(content=message)])

The above work around using cl.Message(content="") is needed and will be fixed in a future release. It is required as of version 0.2.109

thanks


chore(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/kms-all-inclusive/ibm (source)
module
minor
4.16.11 -> 4.17.0

terraform-ibm-modules/scc-workload-protection/ibm (source)
module
patch
v1.4.2 -> v1.4.3

Release Notes

terraform-ibm-modules/terraform-ibm-kms-all-inclusive (terraform-ibm-modules/kms-all-inclusive/ibm)
v4.17.0
Compare Source
Features

exposed the ability to set the provider_visibility in the DA. Learn more. (#586) (53580ae)

terraform-ibm-modules/terraform-ibm-scc-workload-protection (terraform-ibm-modules/scc-workload-protection/ibm)
v1.4.3
Compare Source
Bug Fixes

deps: bump cbr rule and zone to 1.29.0 (#160) (9b185b3)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

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


 I was on V16, now back on V15.2 but the problem still persists. I'm 400k blocks behind and my node tries to broadcast non-existent blocks constantly.
[2018-09-19 09:49:48.639582]: Broadcasting confirm req for block B955951E6FC69CF10A5A1869CFFF7522B34D68B36BA24697BCA9163CB35E3BEB to 10 representatives
[2018-09-19 09:49:48.639610]: Broadcasting confirm req for block 9F3BBF37BFEFC6CBC01752EBBB40CED6129EFDF7EB8F347094B2D135B618232D to 10 representatives
[2018-09-19 09:49:48.639950]: Broadcasting confirm req for block 9F3BBF37BFEFC6CBC01752EBBB40CED6129EFDF7EB8F347094B2D135B618232D to 10 representatives
[2018-09-19 09:49:48.639994]: Broadcasting confirm req for block 9AEFCC10A6B3C8873FE4EE6DE1FEC55383C9D9FC60DF52391DC76854BDF49D3F to 10 representatives
[2018-09-19 09:49:48.640232]: Broadcasting confirm req for block 9AEFCC10A6B3C8873FE4EE6DE1FEC55383C9D9FC60DF52391DC76854BDF49D3F to 10 representatives
[2018-09-19 09:49:48.640273]: Broadcasting confirm req for block 5D29CA71702D83B49B8C9F46967A3A4B42B6881A37C2CF459F6493224D613244 to 10 representatives
[2018-09-19 09:49:48.640522]: Broadcasting confirm req for block 5D29CA71702D83B49B8C9F46967A3A4B42B6881A37C2CF459F6493224D613244 to 10 representatives
[2018-09-19 09:49:48.640540]: Broadcasting confirm req for block 83E282046E957CA206E0E71EEAFCC7CB9C0A5BFCB97D3059E0DB2499FE2DA899 to 10 representatives
[2018-09-19 09:49:48.640754]: Broadcasting confirm req for block ECBFDA8AB2B44E71C70B3F4240D65A3786EBE570990718674AF5D17971A7E30F to 10 representatives
[2018-09-19 09:49:48.640801]: Broadcasting confirm req for block 83E282046E957CA206E0E71EEAFCC7CB9C0A5BFCB97D3059E0DB2499FE2DA899 to 10 representatives
[2018-09-19 09:49:48.640892]: Broadcasting confirm req for block 8C6D735A64F1760800A91E65C385CF813A666126C9D2B7A3163FDEC7E29FCB05 to 10 representatives
[2018-09-19 09:49:48.641007]: Broadcasting confirm req for block ECBFDA8AB2B44E71C70B3F4240D65A3786EBE570990718674AF5D17971A7E30F to 10 representatives
[2018-09-19 09:49:48.641215]: Broadcasting confirm req for block F2CE57A6F90D6A1D7F09ADD199B66B25555C6D49F961D8DB0BFAD1451428761F to 10 representatives
[2018-09-19 09:49:48.641240]: Broadcasting confirm req for block 8C6D735A64F1760800A91E65C385CF813A666126C9D2B7A3163FDEC7E29FCB05 to 10 representatives
[2018-09-19 09:49:48.641453]: Broadcasting confirm req for block A25ED67250D503A6FAACE16AAD46F9351DF9D324C7B309F0FBF195AF01243D19 to 10 representatives
[2018-09-19 09:49:48.641616]: Broadcasting confirm req for block F2CE57A6F90D6A1D7F09ADD199B66B25555C6D49F961D8DB0BFAD1451428761F to 10 representatives

It seems like some kind of fork happened after my update to V16. I always use this guide to (re)build rai_node: https://github.com/nanocurrency/raiblocks/wiki/Build-rai_node-samples
Could it be that I updated to a version that started recieving blocks from the beta network?

Is it possible these are blocks from the beta network and we can resolve this by implementing #1135 ?

This is not beta block, just forks to resolve

@Tox1city is it still unsynced?

I re-downloaded the current data.db file and re-imported my seeds. This fixed the issue. I make sure to check-out stable branches only from now on (I think by following the tutorial I checked out a beta branch which caused the fork).

Thanks!
Will close issue, please reopen it if problem returns


[MM-33892] Replace em dash with double dash for commands

Summary
There is an issue where an iPhone with Smart Punctuation enabled will convert -- with an em dash —. Many commands rely on double dashes being preserved in the submitted text. This PR makes it so if a command is being submitted, the em dashes are replaced with double dashes.
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-33892

Building app in separate branch.

Successfully building:
https://circleci.com/gh/mattermost/mattermost-mobile/14736
https://circleci.com/gh/mattermost/mattermost-mobile/14735

Artifact links:
https://14736-70265724-gh.circle-artifacts.com/0/tmp/artifacts/Mattermost_Beta.ipa
https://14735-70265724-gh.circle-artifacts.com/0/tmp/artifacts/Mattermost_Beta.apk

@mickmister @DHaussermann Should this be cherry-picked to v1.42? Or is this just for master/future release?

/cherry-pick release-1.42

Cherry pick is scheduled.


Hunter 0.9.2

I used master because I actually need a new branch for hunter-0.9.2 based on version 0.9.2 of Thrift. Let me try pushing that myself.

Ah github is having issues. Let me retry this.


Controller Z axis?

I have 2x PS Eyes and every time I use the Calibration Mat my controllers and cameras are 4 to 6 feet above my head. I don't have positional tracking on my HMD. So, I'm just using "Standing". I've tried changing the z axis in "C:\Users<username>\AppData\Roaming\PSMoveService\Controller_mac_address.json" but nothing changes. Where can I manually change these values. I would also like to be able to rotate the cameras because they are about 30 degrees off to the left.
Also, since the past few updates I only have one controller (I'm using the x64 build). I hate to have so many questions, but I'm at my wit's end.. hehe You guys have done an amazing job and I thank you for making this even possible.

The simple solution would be to place the calibration mat 4 to 6 feet lower but I realise that may not be possible. Try re-running room setup and changing the height you input for the HMD. What HMD are you using? If it's VRidge then you can adjust the height using FreePIE to send the data via FreeTrack.
Do you have SteamVR running when you calibrate because this could effect the co-registration.
Without seeing the logs it's hard to think why you only have one controller. Is the red LED stable on you second one?

Aww, I never thought of placing the calibration mat lower. So, the cal mat should really be used on the floor or closer to it. I have both of my cameras on the left and right side of my desk using tripods and they are set to round 6 feet. I need to put them higher and point them more to the ground. I'm currently using my dk1. I have a freefly that I use with my Galaxy s6, but I prefer the dk1 due to less lag. So, would the .json file I listed above for the controller not be where I need to change the z axis? If I understood the configuration files a little better then I would be more than happy to start working on a tool in Visual Studio to manually adjust those settings.
I can work through the controller issue. I was just wondering what changed. I can get it back by unpairing both controllers and then re-pairing them again. Wait.. just a thought, but whichever controller I pair first.. Should this be the controller I turn on first everytime? Plus, to turn off my controllers I unplug my bluetooth adapter. Thanks for your help @zelmon64!

I haven't looked into that .json file so I don't really know how it works but @HipsterSloth will be able to tell you later. Since you're using a dk1 how are you getting head movement?
You should only have to pair the PSMove controllers once. To turn them off simply hold the PS button for >10s (if a client is running it may complain/crash). It should not matter which you turn back on first. To let the computer know that the controllers are disconnected I usually disable my bt in the device manager (because otherwise they disrupt the controller I use for Kodi for some reason).
Is the controller not reconnecting to windows or is it just not seen in SteamVR? Do you use the new pairing function in the configuration tool or the original programs?

You can adjust the the y-axis (y is up in steamvr and in psmove service) in the '
TrackerManagerConfig.json' config file. Look for the 'hmd_tracking_space' section and adjust the y-value there. That position and orientation is the hmd position and facing in steamvr's coordinate system of the hmd when centered facing forward
on the calibration mat. I'be been meaning to document the config files but have been swamped with trying finish features of the service. Sorry it's so opaque right now. If you do create a manual offset tool i'd prefer it go in the config tool client, but if you want to write a quick standalone thing to edit the json file that's fine too.
As for the controller dissappearing, is it not even in the controllers list in the config tool or just in game? If it's only in game this is a steam vr issue that happened in the most recent update. Valve tweaked how controller roles worked and it broke hand assignment for games using the default unity steamvr vr plugin. The fix for that will be in the next steamvr beta. Details are in issue #94

Thanks @HipsterSloth ! I'll change the Y axis in 'TrakermanagerConfig.json'. I downloaded VS 2013 yesterday. If I do make anything I'll add it to the config tool client. When I grabbed the project earlier I only had 2015 installed at home and 2010 and 2015 at work.  No need for apologies this is shaping up nicely and well worth the wait. it really baffles me at the lack of companies not trying to create controllers for hand presences. You would think Razer would update their Hydras, but they are planing to use a 3rd party glove.. but yea I think my controller issue is just from the latest update, because windows sees both motion controllers and so does the config tool. I was just wanting to verify. Thanks again for the speedy response!
@zelmon64 I'll start disabling it in device manager. I'm suprised at how well the config tool tracks it. It would be cool to add an led strip to the front for tracking or something close to the PSVR. Thanks for your help!

@xMindweaverx FWIW we're in the middle of making psmoveservice compile with MSVC 2015. There is a 2015 branch that is almost ready. Hopefully that will be pushed up to master by the end of this week.

@HipsterSloth changing the y axis in "orientation" didn't change the height. Decreasing the value rotated everything to the right.
Here is my file content.
{     "version": "2",     "default_tracker_profile": {         "exposure": "56",         "gain": "56",         "color_preset": {             "magenta": {                 "hue_center": "150",                 "hue_range": "20",                 "saturation_center": "80",                 "saturation_range": "97",                 "value_center": "245",                 "value_range": "32"             },             "cyan": {                 "hue_center": "90",                 "hue_range": "10",                 "saturation_center": "255",                 "saturation_range": "32",                 "value_center": "255",                 "value_range": "32"             },             "yellow": {                 "hue_center": "30",                 "hue_range": "10",                 "saturation_center": "255",                 "saturation_range": "32",                 "value_center": "255",                 "value_range": "32"             },             "red": {                 "hue_center": "0",                 "hue_range": "10",                 "saturation_center": "255",                 "saturation_range": "32",                 "value_center": "255",                 "value_range": "32"             },             "green": {                 "hue_center": "60",                 "hue_range": "10",                 "saturation_center": "255",                 "saturation_range": "32",                 "value_center": "255",                 "value_range": "32"             },             "blue": {                 "hue_center": "120",                 "hue_range": "10",                 "saturation_center": "255",                 "saturation_range": "32",                 "value_center": "255",                 "value_range": "32"             }         }     },     "hmd_tracking_space": {         "orientation": {             "w": "0.910448611",             "x": "0",             "y": "0.41362223",             "z": "0"         },         "position": {             "x": "-10.1344433",             "y": "3.16747022",             "z": "17.1889973"         }     } }

Oh sorry I should have been more clear. You want to modify the y value in the "position" section, not the orientation. The orientation value is a quaternion used to define the rotation of the tracking space and almost certainly not what you want to tweak.

Ok I don't know what's going on, but I changed the y axis in "position" and both trackers and controller are behind me at the same height.

Huh. I could have sworn we were using the OpenGL coordinate system where +Y is up. Try the "z" value instead. Sorry for the guess work.

z axis didn't do anything. I'm closing SteamVR and then the PS Move Service then I'm editing the .json file with Notepad++. Then I'm starting the service and then steamvr. I've changed x, y, z values in "position" and non of those lower the cameras or the controller.

Hmm.  Does the dk1 even work in oculus home at this point? I'm kind of out of obvious things to try. I might just have to try and repro this at home, but it''s going to be this weekend at the earliest before I can get to that.

Yea, I'm recalibrating it now. I'm currently using Oculus runtime 0.8. I'm going to mess around with it a little bit more tonight. If I figure out anything I'll let you know tomorrow. Thanks again!

So, I didn't get far last night before I ran out of gas... lol I plan to recalibrate tonight. I just seen your "Manual psmove tracking color calibration" video @HipsterSloth on Youtube. You should link to those videos in your Wiki. I think my calibration is off. I backup my "_C:\Users\AppData\Roaming\PSMoveService_" folder often. The best setup I had previously was when I calibrated during the day and had more light in the room. Reloading that backup made a big difference. I also raised my Trackers up to around 7' from 6'. I'm 6'4" so I wanted the trackers above my head.
Also, this morning I notice about an hour after I went to bed Steam released a new SteamVR beta. I hope this one fixes the controller issue.

Thanks for the heads up about the steamvr update. I'll check to see if that fixed the hand issue.
Your comment about the config backups reminds me, I want to add a feature for saving multiple color calibration profiles (daytime, nighttime, etc).
As for videos we actually have someone polishing up a setup tutorial video now that's much better than the quick test videos I made.

No problem. I look forward to the video. I wrote this:
If you have WinRAR copy and paste the below into a text file and save to desktop and then set the extension to ".bat". Then double click the file to execute. <-- This is for anyone that doesn't know.
`@echo off
:: variables
set tt=%time:~0,2%_%time:~3,2%_Backup
set BackupLocation="%~dp0\PSMoveService_Backup"
set backup="%BackupLocation%%date:/=-% %tt%.rar"
set Saveme="%USERPROFILE%\AppData\Roaming\PSMoveService"
IF NOT EXIST %BackupLocation% mkdir %backuplocation%
"%programfiles%\winrar\rar" a -ep %backup% %Saveme%
@pause
::echo ### Finished on %date% %time%
::echo Backup Complete!`
If you don't have WinRAR
`@echo off
:: variables
set BackupLocation="%~dp0\PSMoveService_Backup"
set Saveme="%USERPROFILE%\AppData\Roaming\PSMoveService"
set tt=%time:~0,2%_%time:~3,2%_Backup
set folder=%date:/=-% %tt%
set backupcmd=xcopy /s /c /d /e /h /i /r /k /y
color 9F
echo ### Mindweaver's Backup Plain
%backupcmd% "%Saveme%*.*" "%BackupLocation%%folder%%file%"
:: Comment the next 2 lines below if you don't want to set attributes.
echo ### Setting Attribute's
attrib +r -h %BackupLocation%* /s /d
echo This Backup was created on Date (%date%), Time (%time%). >> "%BackupLocation%%folder%\Backuplog.txt"
echo Backup Complete!
@pause`

Ok more testing tonight and was able to get both controller working. When I manually set the controller colors I was taking the the other one out of calibration. I didn't realize the left side (Color Calibration) is one setting for all colors. The only settings that you can save with each color are the settings on the right side (Controller Calibration). So by changing the Color Calibration settings on the second color I was taking the 1st color out of calibration... Now I just set the Color Calibration that works for both colors (1st Magenta, and 2nd Cyan). Then I set the Controller Calibration and save the settings for both colors. Now both controllers are in SteamVR and Games.
So, next Controller and Tracker height. I changed the Y setting and still I don't see any changes.  Next I tried changing the Z axis and still nothing. It's crazy because moving my hmd up or down causes the controllers and camera to raise and lower the same offset difference. It's as if the HMD is on the floor and the controllers and camera are at the right height, but in the holodeck like in SteamVR my HMD is off the ground correctly. I've tried doing the Calibration Mat with the HMD on the floor. I have Steam VR Standing set to 76" and I even tried putting it to 0" and my HMD is in the floor. I'm wondering in the TrackermanagerConfig.json for orientation which of the 4x (w,x,y,z) is the HMD height and which is for controller Height? Can you post your hmd tracking space settings @HipsterSloth ? Mine are below.
"hmd_tracking_space": {
        "orientation": {
            "w": "0.855038047",
            "x": "0",
            "y": "0.518565297",
            "z": "0"
        },
        "position": {
            "x": "-11.2541981",
            "y": "3.22888947",
            "z": "20.2555428"
        }
    }

Here is my tracking space settings:
    "hmd_tracking_space": {
        "orientation": {
            "w": "0.999944746",
            "x": "0",
            "y": "0.0105108134",
            "z": "0"
        },
        "position": {
            "x": "28.3204651",
            "y": "-41.3078918",
            "z": "31.3759708"
        }
    }

Also important point about this:

I'm wondering in the TrackermanagerConfig.json for orientation which of the 4x (w,x,y,z) is the HMD height and which is for controller Height?

None of the 4 values (w,x,y,z) in the "Orientation" block have anything to to do with HMD height or controller height. Allow me to explain...
SteamVR has one tracking coordinate system whose origin is somewhere relative to your HMD tracking camera. PSMove Service has it's own completely independent coordinate system whose origin and facing you define with the calibration mat. In order to get the psmove controllers in the same coordinate system as steam VR we have to know where the two coordinate systems are relative to each other. The "orientation" and "position" of the "hmd_tracking_space" are the position and rotation of your HMD in steamVRs coordinate system when it's placed at the center of the calibration mat facing forward during the last step of the tracking setup tool.
So in my calibration data above when a psmove controller is placed at the center of the calibration mat, it's actually at x=28.3204651, y=-41.3078918, z= 31.3759708 in steamVR's coordinate system (units in centimeters).
As I mentioned before, the "orientation" is a rotation stored as a quaternion, where:

w=cos(angle/2)
x=rotation_axis.x * sin(angle/2)
y=rotation_axis.y * sin(angle/2)
z=rotation_axis.z * sin(angle/2)

Or about a 70 degree rotation about the y-axis in the case of my setting.
The thing that confuses this further is that steamvr actually has multiple coordinate systems. The steam vr coordinate system I was just referring to is actually the "steamvr raw device coordinate system". When you define your room calibration, you actually create a new "standing coordinate system" that's relative to "raw device" system.
So what's making this confusing is that you have two knobs your's adjusting that are interfering with each other, the tracker settings file and the steam vr standing height.
I would say it's probably easiest to just set the standing height to zero and only play with the "position" y-value tracking settings file, but as you said, that wasn't working for you. You are restarting steamvr each time you change the  tracking settings file right? PSMoveService doesn't currently notify steamvr when the "hmd_tracking_space" settings change (though I plan on fixing this).

Aww, ok that clears things up a bit for me.  Also, with those numbers at the 9th decimal place I was making really small incremental moves.. Thinking most of the adjustment was in the decimal place. I never took my Y axis below "-6.16747022" and that was only when I was frustrated... lol So, it was probably moving but not enough for me to see it in space.
I'm ready to go home and try it using your setting of "-41.3078918". My orientation is close to yours so that makes me feel better.
I was going to ask if you could put a rest button or button that calls the form load. Now the other frustrating this is now I can't just unplug my hdmi cable and re-seat it to clear SteamVR's "steamvr compositor is not available" error. This happened a couple updates back. Do you know of another method to clear that error other than restarting the PC? Thanks again!

I was going to ask if you could put a rest button or button that calls the form load

Yeah I definitely want to do that. In fact I'll re-label this issue as such for tracking purposes.

Also, with those numbers at the 9th decimal place I was making really small incremental moves.. Thinking most of the adjustment was in the decimal place.

Oh ha! Yeah with the units being in centimeters any digit smaller that then second decimal place is just noise. At some point I really need to write up some docs explaining what the values mean in the configuration files.

Now the other frustrating thing is now I can't just unplug my hdmi cable and re-seat it to clear SteamVR's "steamvr compositor is not available" error.

That's a new issue to me. It's possible that the one of the steamvr processes is getting stuck running and is stuck not reconnecting to the vrcompositor process. Maybe try looking in process explorer and make sure none of the steamvr processes are still running (vrcompositor, vrserver, vrdashboard) after shutting down steamvr?

Nice! Yea, it would be nice to maybe add just a comment in the file it self only for people that tinker around with the config file. I don't think that part really needs to be apart of the Wiki so not to confuse people that never plan to edit that file directly.
I have killed every steam process and nothing to fix the compositor issue in SteamVR. But it just hit me that there use to be a feature in SteamVR to reset the HMD and in the beginning when you disconnected and re connected the hdmi cable you still had to reset the HMD in SteamVR. I don't know what they changed but it was really nice being able to just reconnect the hdmi to resolve that issue.. and honestly it could have been an update for windows or on the Nvidia driver that changed. I'll look tonight to see how windows is seeing the HMD (Main or Extended). If it's setting it to Extended then I'll try to set it to Main. Thanks again!

Okay, so check it out. I had to set my "Y" axis to "-150.000000000". It floored me when I set it to "-41.000000000" and it didn't look like it change at all. I then set it to "-120.000000000"... and I had movement! It actually was below my head for the first time. Sorry, for the excitement, but I just had to share my success!.. lol

This feature request was made moot by the addition of the SteamVR start+select alignment.


[Backend] As a user, I can logout

Resolve https://github.com/Lahphim/go-crawler-challenge/issues/12
What happened 👀
Revoke the user's session once the he makes a request to logout his account.
Insight 📝

[x]  Revoke the user's session
[x]  Redirect to the root page

Extra:

Create a dashboard page for authenticated user can access
Update policy in root page for any user can access
Re-design policy workflow and assign to each action in the controller instead of just only within the controller

Policy Workflow:
controllers/base.go
type BaseController struct {
	actionPolicy map[string]Policy
}

type Policy struct {
	requireAuthenticatedUser bool
	requireGuestUser         bool
}

func (c *BaseController) Prepare() {
        c.actionPolicy = make(map[string]Policy)

        app, ok := c.AppController.(NestPreparer)
	if ok {
		app.NestPrepare()
	}
}

func (c *BaseController) handleAuthorizeRequest() {
       ...
}

controllers/session.go
type SessionController struct {
	BaseController
}

func (c *SessionController) NestPrepare() {
	c.actionPolicyMapping()
}

func (c *SessionController) actionPolicyMapping() {
        // All user can access
        c.MappingPolicy("Index", Policy{})

        // Only guest user can access
	c.MappingPolicy("New", Policy{requireGuestUser: true})
	c.MappingPolicy("Create", Policy{requireGuestUser: true})

        // Only authenticated user can access
	c.MappingPolicy("Delete", Policy{requireAuthenticatedUser: true})
}

Proof Of Work 📹

State of session

Before Sign In

Signed In

After Sign out

Demo

All green with testing

@Lahphim Should we also change the redirect path after login to dashboard?


(ready for review) Add .zenodo.json file

@tennlee please review
@nicholasloveday if this is of interest, please feel free to review
This PR adds a .zenodo.json file.
At present, Zenodo draws metadata from our CITATION.cff file. However, if I have understood correctly, if we add a .zenodo.json file, Zenodo will instead draw metadata from the .zenodo.json file (see: https://support.zenodo.org/help/en-gb/24-github-integration/96-how-does-a-citation-cff-file-affect-metadata-of-my-github-release).
The .zenodo.json file includes information not contained in the CITATION.cff file. I think it would be preferable to have both a .zenodo.json and a CITATION.cff file - so they can be optimised for their different purposes.
To create the .zenodo.json file, I attempted to follow the instructions here: https://developers.zenodo.org/?python#add-metadata-to-your-github-repository-release
Some questions regarding the contents of .zenodo.json:

I used the same "keywords" we used for the JOSS article. If these keywords should be changed, or any additional keywords added, please let me know.
I have not included any information about "Zenodo Communities" - simply because I didn't know whether this was relevant for us, and if so, which communities to list. If any should be added, please let me know.
I didn't include any "funding information, via the grants field. If there is anything that should be added, please let me know.

I validated the JSON file here: https://jsonformatter.curiousconcept.com/ . (It did suggest I remove the trailing comma at the end of the keywords section, which I haven't done - if you would like the trailing comma removed, please let me know).
I think there may be a Zenodo sandbox that can maybe be used for further testing, but I wasn't sure how that works and what can be tested there.

It's not clear to me what the Zenodo json file will do. Will it change the citation on https://zenodo.org/records/12702856 ? Or will it add some other info?

It's not clear to me what the Zenodo json file will do. Will it change the citation on https://zenodo.org/records/12702856 ? Or will it add some other info?

I don't think it will change existing entries (I don't know that for sure, but I would be pretty surprised it if changed existing entries). The purpose would be to further automate, streamline and reduce the risk of errors for Zenodo metadata going forward.
At present, each time Tennessee makes a release on GitHub, that version is automatically archived in Zenodo. Each time this occurs, Zenodo draws some metadata (off the top of my head, I think: title of package, author names and I think author ORCIDs) from the CITATION.cff file.
However, as the CITATION.cff file doesn't include information regarding the license, Zenodo auto-populates the license field with a license that is not Apache-2.0. So Tennessee has to remember to go and manually edit the license each time (and if he were to forget, Zenodo would record the incorrect license for that version).
Additionally, each release Tennesse has to manually add the affiliations for each author, and also has to remove an auto-populated field regarding preferred citation (to date he has removed the preferred citation field entirely).
The hope is adding a .zenodo.json file will mean Zenodo auto-populates the metadata with the correct license, title, author names, ORCIDs, affiliations and possibly the preferred citation. If so, this will remove much of the manual work and also reduce the likelihood of errors from manually inputting information each time, or forgetting to include the correct license.
Tennessee also manually adjusts the "notes" section - but if this gets overlooked, it probably won't matter as much. (Compared to say, listing the incorrect license).
An additional reason to have a .zenodo.json in addition the CITATION.cff file, is over time the author list may change. For example, if someone contributes code who wasn't an author on the JOSS paper - they may wish to be listed as an author on the Zenodo release. If so, their details can be added to .zenodo.json so their details are included in the Zenodo archive for the next release. (Which can then be cited using the Zenodo DOI).
While the files archived on Zenodo cannot be changed after the fact, fortunately Zenodo metadata can be updated manually afterwards. So any issues can usually be resolved. But it looks like adding a .zenodo.json will reduce the amount of manual updates required and hopefully reduce the risk of incorrect metadata being used in the first place.

Okay that sounds like a lot of great reasons for including it. Thanks for explaining!
It looks good to me.

Also, the first release that went to Zenodo was 0.9.3. It is now set up to automatically archive all releases from that point onwards. (Hence why versions prior to 0.9.3 are not archived on Zenodo).


grpc::node::Server::ShutdownServer() - Cannot create a handle without a HandleScope

Seen with node v6.9.1 + grpc-1.2.3 at least 3 times, but seems pretty random - I won't be able to extract/post the workload that lead to this, sorry. Hopefully you can think of a simple fix for this. Looks race-condition-ish when garbage collection kicks in?
 Seems to be caused by just a certain amount of calls and then it fails. I encounter this in my tests.

That's interesting. The stacktrace above shows that this specific failure happens when the Server gets garbage collected. That shouldn't be happening at all if the server is supposed to be handling calls.

This should be fixed in gRPC 1.2.4


Show number of feed errors on the "Feeds" top bar

Currently, the "Unread" link shows the number of unread items.
To avoid situations where feeds error out without notice, the "Feeds" link could have a similar number that contained the numbers of feeds that are in an error state. This could be styled in red, for example, just to make it clear there are errors.
I'm OK with solving those issues manually, I just want to know they exist without entering the Feeds page manually. I'm also OK with having this value cached for a long time, like several hours, it's not urgent information.
Just avoiding going for days with feed errors because the site changed the URL without notice nor redirects (sigh).

I agree an indication would be nice, but I think putting a number in there would be confusing. I was thinking more of a small Unicode danger sign (⚠) or maybe changing the text colour.

That's a possibility too, now that I think about it the number is not really relevant.

I found the Unicode danger character to be obnoxious once I had it in there. 🤷♂ I went with a number because I figured if someone is having long-term difficulty with a feed, then the number would let them know additional feeds were not working. It also only counts if the feeds have stopped updating due to too many errors (e.g. so occasional timeouts in updating won't be distracting).


[Bug]: PostgreSqlBuilder ERROR: exec: "-c": executable file not found in $PATH: unknown"

Testcontainers version
3.10.0
Using the latest Testcontainers version?
 (Docker Inc.)
Version:  v1.0.5
Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version:  v1.3.0
Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version:  0.6.0
Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
scout: Docker Scout (Docker Inc.)
Version:  v1.13.0
Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe
Server:
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 4
Server Version: 27.2.0
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 nvidia runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 8fc6bcff51318944179630522a095cc9dbf9f353
runc version: v1.1.13-0-g58aa920
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: <IP_ADDRESS>-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 7.664GiB
Name: docker-desktop
ID: e6b9f3e8-b556-4edd-b490-24cb6bf1b6cf
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Labels:
com.docker.desktop.address=npipe://\.\pipe\docker_cli
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
<IP_ADDRESS>/8
Registry Mirrors:
https://mirror.gcr.io/
https://daocloud.io/
https://c.163.com/
https://registry.docker-cn.com/
Live Restore Enabled: false
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profile
What happened?
Created a docker image based on a docker container (used "docker commit ...").
Therefore, the last two commands in the layers
CMD ["postgres" "-c" "listen_addresses=<IP_ADDRESS>" "-c" "shared_buffers=256MB" "-c" "shared_preload_libraries=ldc_cache,verstamp_xid"]
and
postgres -c listen_addresses=0.0 .0.0 -c shared_buffers=256MB -c shared_preload_libraries=ldc_cache,verstamp_xid
Last command appears after "docker commit ..."
Then I want to use:
private const string PostgresImage = "path to my image";
private PostgreSqlContainer pgContainer;
this.pgContainer = new PostgreSqlBuilder()
.WithImage(PostgresImage)
.WithName($"pg_test_db_{Guid.NewGuid()}")
.WithDatabase("MY_AUTOTEST")
.WithPortBinding(5435, true)
.WithUsername("postgres")
.WithPassword("passw4")
.WithAutoRemove(true)
.WithCleanUp(true)
.Build();
await this.pgContainer.StartAsync();
But when StartAsync, I get an error
Docker.DotNet.DockerApiException : Docker API responded with status code=BadRequest, response={"message":"failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "-c": executable file not found in $PATH: unknown"}
I think problem with layer
postgres -c listen_addresses=0.0 .0.0 -c shared_buffers=256MB -c shared_preload_libraries=ldc_cache,verstamp_xid
But why ok working ContainerBuilder with the same image?
        this.pgContainer = new ContainerBuilder()
            .WithImage(PostgresImage)
            .WithPortBinding(5435, true)
            .WithName($"pg_test_db_{Guid.NewGuid()}")
            .WithEnvironment(new Dictionary<string, string>
            {
                { "POSTGRES_USER", "postgres"},
                { "POSTGRES_PASSWORD", "passw4"},
                { "POSTGRES_DB", "MY_AUTOTEST"},
            })
            .WithAutoRemove(true)
            .WithCleanUp(true)
            .Build();

Relevant log output
No response
Additional information
No response

Created a docker image based on a docker container (used "docker commit ...").

If you are using a "custom" image, you cannot expect a module to work with it. Modules are pre-configured and opinionated. In this case, use the generic builder ContainerBuilder instead.

We mention that the modules are pre-configured, but I agree that we do not explicitly say they are opinionated and may not work with every image customization. In that case, the generic container builder would be the way to go. Are you interested in updating the documentation?

Are you interested in updating the documentation?
No, thanks for helping me understand


Feature/babelify index.js

This PR babelify index.js
closes https://github.com/punkave/sanitize-html/issues/189

Upon reflection, there's no need for me to nitpick about using babel in node. It broadens support for old versions of node at no real cost. Thanks for the work.


gophernotes: use newer version packaged in nixpkgs

The more recent gophernotes version (0.7.0 → 0.7.1) is used from the nixpkgs. Therefore the nixpkgs needed to be updated.

The MacOS test was not passing, I relaunched it.

I'm not quite sure, but it seems like bumping the nixpkgs breaks some tests on macOS.

I have the impression it's some other package that is broken for Mac in Nixpkgs at this moment. Updating Nixpkgs here is always delicate, so I prefer to not do it right now.
But if you are willing, I would accept an update of gophernotes to the latest version.

Okay, I have modified the Pull Request to just bump gophernotes to its latest release.

Thanks!


Command pallete automatically closes in non-file editor

System Information
Version: 1.36.0-insider (user setup)
Commit: 7f53e50cbf316dff94fbbe5406d8f352dac99a6b
Date: 2019-06-18T09:31:11.619Z
Electron: 4.2.4
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Windows_NT ia32 6.1.7601
issue type: bug
Steps to reproduce:
1 open any non-file editor, like preview for markdown
2 open ("Command palette"/"Color Theme"/"File Theme") from activity bar>settings icon

What happened to the bug? Was it solved or is it in the process of being fixed?

@COD3BREAK3R i dont know, i'm just report bug

Something must draw focus. @bpasero I remember you mentioning this issue? /cc @sbatten

Quite sure this is the webview taking focus to workaround Electron focus issues.

/duplicate #75209


fix(aws-ecs)/ec2 container service role does not use managed policy

Bug
When using @aws-cdk/aws-ecs.Cluster.addCapacity, the instance role created would simply use the AmazonEC2ContainerServiceforEC2Role managed policy, as described in the ECS documentation. However, it seems like it creates a completely new policy with hardcoded permissions.
To Reproduce
const cluster = new ecs.Cluster(this, 'Cluster', {
    clusterName: 'MyECSCluster',
    vpc: this.vpc
});
cluster.addCapacity('ASG', {
    instanceType: new ec2.InstanceType('c5.large'),
    taskDrainTimeSeconds: 0
});

A new ClusterASGInstanceRoleDefaultPolicyXXXXXXXX policy is created.
Fix
I think this is due to the way the addCapacity operates in cluster.ts: the method first creates and then calls the addAutoScalingGroup method defined in the Cluster class. This method defines manually the required permissions in a policy statement attached to the role associated with the autoscaling group.
As done in eks-cluster.ts, I fixed it by using attachManagedPolicy to the autoscalingGroup role with the AmazonEC2ContainerServiceforEC2Role that was previously created manually.
close #2827
Pull Request Checklist

[x] Testing

Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
CLI change?: coordinate update of integration tests with team
cdk-init template change?: coordinated update of integration tests with team

[x] Docs

jsdocs: All public APIs documented
README: README and/or documentation topic updated
Design: For significant features, design document added to design folder

[x] Title and Description

Change type: title prefixed with fix, feat and module name in parens, which will appear in changelog
Title: use lower-case and doesn't end with a period
Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"

[x] Sensitive Modules (requires 2 PR approvers)

IAM Policy Document (in @aws-cdk/aws-iam)
EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
Grant APIs (only if not based on official documentation with a reference)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

Hi @made2591.
This behavior is in purpose. Not sure why you're classifying it as a bug. What is it breaking for you?

Hi @rix0rrr ... I supposed it was better using managed policy whenever it's possible: am I wrong? Let's say tomorrow the set of permissions will change for some reason: if the list of permissions is hardcoded inside cdk, then the wrong set of permissions will be attached. On the other hand, if we refer to a managed policy is up to AWS keep that aligned with the minimum required permission... am I misunderstanding something? 🤔

The reason why we choose to inline policies is because managed policies must necessarily always have resource: * statements, whereas we can often generate more targeted policies, which are only able to affect the intended resources.
If you are replacing resource-* statements, I feel less strongly about this, but if the statements are targeted, I feel the least permissions boundary is preferable.

Ok, makes sense: I thought it was fine because it was already like this (.addAllResources());) even before introducing the managed one. Feel free to discard the change if you want ;)

PS: then it makes sense maybe applying the same logic in eks (source) - I was just wondering, no rush...

@rix0rrr any news on this? At least regarding the eks package

I'm going to assign this to @eladb who is working on the EKS package right now.

Sorry for the delay. @eladb was this addressed in the EKS package, and/or should we close this?

Unless proven otherwise, I will close this as intended behavior.


Train Loss and Val Loss as nan

I am training the model with the BDD-100K dataset for a single class with an input dim of 256 x 512. I have resized the images from BDD original dim of 720 x1280 to 256 x 512 before adding them to the TFrecords.
I am getting an error specific to train and val loss being nan. I have already removed images with no lane markings from the dataset. Still, I am getting the same error.
I ran an experiment for 10 epochs which results are attached below

@letdivedeep Check whether the instance loss reach into nan. You need to adjust the instance loss params if so:)

@MaybeShewill-CV  thanks for your reply
I found that the instance loss was ard 15.92 it didn't reach nan

the eval result

@letdivedeep instnace segmentation have learned something but seems not converged very well:)

@MaybeShewill-CV thanks for your reply

@letdivedeep Check whether the instance loss reaches into nan. You need to adjust the instance loss params if so:)

what do you mean by instance loss params and where to find it?

and any specific values we need to set for bdd dataset?

I tried to change this config in the yaml and not the iloss is moving ard 6 not decreasing future :
POSTPROCESS:
    MIN_AREA_THRESHOLD: 150
    DBSCAN_EPS: 0.40
    DBSCAN_MIN_SAMPLES: 1500

I am training the model with the BDD-100K dataset for a single class with an input dim of 256 x 512. I have resized the images from BDD original dim of 720 x1280 to 256 x 512 before adding them to the TFrecords.
I am getting an error specific to train and val loss being nan. I have already removed images with no lane markings from the dataset. Still, I am getting the same error.
I ran an experiment for 10 epochs which results are attached below

may i ask you two questions?

how do you know whether one image has lane markings or not?
images in bdd100k/drivable_maps/labels are "binary segmentation label" mentioned in the readme of this project, right?  however, i find all images in that path are pure black...

@letdivedeep What you changed before had nothing relative to instance segmentation. The params was used in postprocess cluster procedure. Check this https://github.com/MaybeShewill-CV/lanenet-lane-detection/blob/66d7405d8e5284767addf31bab6a7ba17274d187/lanenet_model/lanenet_back_end.py#L157-L162

@beiweixiaoxu 1. Check https://github.com/MaybeShewill-CV/lanenet-lane-detection/blob/66d7405d8e5284767addf31bab6a7ba17274d187/tools/test_lanenet.py#L125-L130 The mask will be empty if no lane exists
2.You may compare the BDD100K dataset with Tusimple dataset to find the difference:)

@beiweixiaoxu 1. Check
https://github.com/MaybeShewill-CV/lanenet-lane-detection/blob/66d7405d8e5284767addf31bab6a7ba17274d187/tools/test_lanenet.py#L125-L130
The mask will be empty if no lane exists
2.You may compare the BDD100K dataset with Tusimple dataset to find the difference:)
Thanks for replying, i'm training on Tusimple now, then i'll train on BDD100K. Thanks again.

@beiweixiaoxu Welcome:)

@beiweixiaoxu 1. Check
https://github.com/MaybeShewill-CV/lanenet-lane-detection/blob/66d7405d8e5284767addf31bab6a7ba17274d187/tools/test_lanenet.py#L125-L130
The mask will be empty if no lane exists
2.You may compare the BDD100K dataset with Tusimple dataset to find the difference:)

thanks for the guidances the iloss started decreasing. i did the following changes
            instance_segmentation_loss, l_var, l_dist, l_reg = \
                    lanenet_discriminative_loss.discriminative_loss(
                        pix_embedding, instance_label, self._embedding_dims,
                        pix_image_shape, 0.3, 2.0, 1.0, 1.0, 0.001
                    )

<img width="1680" alt="Screenshot 2020-11-23 at 11 37 22 AM" src="https://user-images.githubusercontent.com/74127861/99933275-8c6dc500-2d80-11eb-95ac-b69a80116cb9.png">

@letdivedeep What you changed before had nothing relative to instance segmentation. The params was used in postprocess cluster procedure. Check this
https://github.com/MaybeShewill-CV/lanenet-lane-detection/blob/66d7405d8e5284767addf31bab6a7ba17274d187/lanenet_model/lanenet_back_end.py#L157-L162

thanks for the guidances the iloss started decreasing. I did the following changes
```
instance_segmentation_loss, l_var, l_dist, l_reg =
lanenet_discriminative_loss.discriminative_loss(
pix_embedding, instance_label, self._embedding_dims,
pix_image_shape, 0.3, 2.0, 1.0, 1.0, 0.001
)

@letdivedeep First you need to make sure which loss reach to nan. It's binary loss or instance seg loss. If it's the instance loss which reach to nan then you need to adjust the params above again:)

@letdivedeep First you need to make sure which loss reach to nan. It's binary loss or instance seg loss. If it's the instance loss which reach to nan then you need to adjust the params above again:)

@MaybeShewill-CV ..Sure will keep track of this... Thanks once again

@letdivedeep Welcome:)

@MaybeShewill-CV .. I used the above config of instance segmentation params
I trained the model with this param for 550 epochs. where my binary loss is ard 0.23 and iloss is ard 3.4.
the iloss was moving ard 3.2 to 4 from 100 epochs itself but it's not going below that.
any point what may be wrong  ?

@letdivedeep Can not point out which params is wrong precisely. Sry:)

@MaybeShewill-CV, not a concern. Thanks, I will notify if found anything on this

@letdivedeep Thanks for sharing:)


Update Jest to 29.4.2

Summary:
Why 29.4.2?
We're currently using 29.2.1, and the latest is 29.6.2

29.4.2 is the first release to include #13859 ("Instrument significant lifecycle events with performance.mark()"), and part of the motivation for this work is to get that instrumentation running internally at Meta.
Jest 29.4.2 contains a small set of breaking changes relative to our previous 29.2.1 (#13503, #13692, #13700). 29.4.3 contains larger breaking changes related to changed mock reset/restore behaviour that it'll take more time to accommodate (or patch upstream).

React Native
Note that this does not update the user-facing template - only the internal monorepo setup is affected.
Changelog: [Internal]
Differential Revision: D48190805

Closing as abandoned internally


Algolia: Add Products Pages items in the algolia index, to get it shown in the search results

Description: currently the algolia index items are being fetch fro /docs content.
We now need to include the https://www.zesty.io/product pages inside the index.
Solution: modify the crawler config found in -> https://crawler.algolia.com/admin/crawlers/80e939d4-8b7e-4175-9d53-0f59510f6106/overview
to include the products pages as well

Fix adjusted the crawler to crawl product pages as well and it's showing in the search result already

No need to create PR update were done from crawler