Unable to create Prisma Docker image for AWS EC Graviton instance

Bug description
After building a Prisma Docker image on a EC2 Graviton instance, I launched this image and get this error message
UnhandledPromiseRejectionWarning: Error: Unknown PRISMA_QUERY_ENGINE_LIBRARY undefined. Possible binaryTargets: darwin, darwin-arm64, debian-openssl-1.0.x, debian-openssl-1.1.x, rhel-openssl-1.0.x, rhel-openssl-1.1.x, linux-arm64-openssl-1.1.x, linux-arm64-openssl-1.0.x, linux-arm-openssl-1.1.x, linux-arm-openssl-1.0.x, linux-musl, linux-nixos, windows, freebsd11, freebsd12, openbsd, netbsd, arm, native or a path to the query engine library.
You may have to run prisma generate for your changes to take effect.
    at Object.getPlatform (/home/node/app/node_modules/@prisma/client/runtime/index.js:36103:13)
    at async Object.instantiateLibrary (/home/node/app/node_modules/@prisma/client/runtime/index.js:36094:21)

So apparently the Prisma engine cannot be found.
The odd thing is that the error should not occur because I am currently building the image directly on the EC2 Graviton instance and I have set the build-target to native in my schema:
generator client {
  provider = "prisma-client-js"
  binaryTargets = ["native"]
}

When I set the build-target to arm only, it gave this error message:
Warning: Your current platform `linux-arm64-openssl-1.1.x` is not included in your generator's `binaryTargets` configuration ["arm"].
    To fix it, use this generator config in your schema.prisma:
    generator client {
  provider      = "prisma-client-js"
  binaryTargets = ["native", "arm"]
}
    Note, that by providing `native`, Prisma Client automatically resolves `linux-arm64-openssl-1.1.x`.
    Read more about deploying Prisma Client: https://github.com/prisma/prisma/blob/main/docs/core/generators/prisma-client-js.md

If I set the platform linux-arm64-openssl-1.1.x directly as build-target, it makes no difference. So the platform linux-arm64-openssl-1.1.x does not seem to work.
How to reproduce

Get an AWS EC2 Graviton instance with Ubuntu 20.04
Install docker and follow the postinstall
Install docker-compose with sudo apt install docker-compose
Load the broken repository git clone https://github.com/friebetill/nestjs-prisma-starter-debug-arm.git
Copy the env file cp .env.example .env
Build the docker image docker buildx build --platform linux/aarch64 --tag nestjs-prisma-starter-debug-arm_nest-api .
Start the docker image docker-compose up -d
Take a look at the logs with docker logs [id-of-container]

Expected behavior
I expected that the server would start and there would be no problems. Instead I see the following error message:
(node:1) UnhandledPromiseRejectionWarning: Error: Unknown PRISMA_QUERY_ENGINE_LIBRARY undefined. Possible binaryTargets: darwin, darwin-arm64, debian-openssl-1.0.x, debian-openssl-1.1.x, rhel-openssl-1.0.x, rhel-openssl-1.1.x, linux-arm64-openssl-1.1.x, linux-arm64-openssl-1.0.x, linux-arm-openssl-1.1.x, linux-arm-openssl-1.0.x, linux-musl, linux-nixos, windows, freebsd11, freebsd12, openbsd, netbsd, arm, native or a path to the query engine library.
You may have to run prisma generate for your changes to take effect.
    at Object.getPlatform (/home/node/app/node_modules/@prisma/client/runtime/index.js:36111:13)
    at async Object.instantiateLibrary (/home/node/app/node_modules/@prisma/client/runtime/index.js:36102:21)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Prisma information
All the information is inside the repository
Environment & setup

OS: Ubuntu 20.04
Database: PostgreSQL
Node.js version: node:lts

Prisma Version
Environment variables loaded from .env
prisma                  : 3.8.1
@prisma/client          : 3.8.1
Current platform        : linux-arm64-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f (at<EMAIL_ADDRESS>Default Engines Hash    : 34df67547cf5598f5a6cd3eb45f14ee70c3fb86f
Studio                  : 0.452.0

As far as I understand it, it means that either

the binary of the Prisma engine does not exist for linux-arm64-openssl-1.1.x and therefore cannot be found when running the Prisma server or
that the engine exists, but is linked incorrectly.

My guess is that the binary does not exist precompiled, so I would have to compile the engine myself. I found this post to compile the engine and adapted my Dockerfile accordingly:
### Build the Prisma engine
FROM rust:1.58.1-alpine3.14 as prisma
ENV RUSTFLAGS="-C target-feature=-crt-static"
RUN apk --no-cache add openssl direnv git musl-dev openssl-dev build-base perl protoc
RUN git clone --depth=1 --branch=3.9.0 https://github.com/prisma/prisma-engines.git /prisma
WORKDIR /prisma
RUN cargo build --release --jobs 1

# To reduce the image size we use a multi-stage build approach, see https://bit.ly/3vMZjNu.
### First stage ###
FROM node:lts AS builder

RUN apt-get install -y curl openssl

WORKDIR /app

ENV PRISMA_QUERY_ENGINE_BINARY=/prisma-engines/query-engine \
  PRISMA_MIGRATION_ENGINE_BINARY=/prisma-engines/migration-engine \
  PRISMA_INTROSPECTION_ENGINE_BINARY=/prisma-engines/introspection-engine \
  PRISMA_FMT_BINARY=/prisma-engines/prisma-fmt \
  PRISMA_CLI_QUERY_ENGINE_TYPE=binary \
  PRISMA_CLIENT_ENGINE_TYPE=binary
COPY --from=prisma /prisma/target/release/query-engine /prisma/target/release/migration-engine /prisma/target/release/introspection-engine /prisma/target/release/prisma-fmt /prisma-engines/

COPY ./yarn.lock ./package.json ./

COPY . .

RUN yarn install --frozen-lockfile

RUN yarn prisma generate
RUN yarn build

RUN npm prune --production

####################

### Second stage ###
FROM alpine:3.14.0

RUN apk add --update nodejs

RUN addgroup -S node && adduser -S node -G node

USER node

WORKDIR /home/node/app

COPY --from=builder --chown=node:node /app ./

EXPOSE 3000

CMD ["node", "dist/main.js"]

But unfortunately at the step RUN yarn prisma generate the following error occurs:
><EMAIL_ADDRESS>prisma:generate
> yarn prisma generate

yarn run v1.22.18
$ /app/node_modules/.bin/prisma generate
Environment variables loaded from .env
Prisma schema loaded from prisma/schema.prisma
Error: Get config: Error: Command failed with ENOENT: /prisma-engines/query-engine cli get-config --ignoreEnvVarErrors
spawn /prisma-engines/query-engine ENOENT
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Apparently there is some problem with the Prisma engine, which is why it won't start. But I don't really know how to get further, does anyone have a tip?

The error message spawn /prisma-engines/query-engine ENOENT indicates that no file /prisma-engines/query-engine exists. Are you sure the file was copied to that location correctly?

Thanks for your tip @janpio. These files exist in builders filesystem:
# ls -lha /prisma-engines
total 116M
drwxr-xr-x 1 root root 4.0K May  4 06:28 .
drwxr-xr-x 1 root root 4.0K May  4 06:25 ..
-rwxr-xr-x 1 root root  31M May  2 11:03 introspection-engine
-rwxr-xr-x 1 root root  33M May  2 10:59 migration-engine
-rwxr-xr-x 1 root root 8.9M May  2 10:49 prisma-fmt
-rwxr-xr-x 1 root root  44M May  2 11:15 query-engine

But something is strange, because I can't execute the binaries directly with e.g. ./query-engine cli get-config --ignoreEnvVarErrors. It's not because I don't have access to it, because I am root (tested with whoami) and the binaries also have execute access.
According to this stackoverflow response, it's probably because the binary is designed for 32 bit and I'm trying to run it on a 64 bit system.
But when I examine the file with e.g. file query-engine I get the following output:
query-engine: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-musl-aarch64.so.1, with debug_info, not stripped

Based on this, it does indeed look like the binary is for 64 bit systems. But I noticed that the interpreter /lib/ld-musl-aarch64.so.1 does not exist to execute the executable. Instead there is only the interpreter ld-linux-aarch64.so.1 in the /lib folder.
Now I'm not sure if I can just reinstall the interpreter or if the file is already compiled incorrectly. But after I have installed the interpreter with:
apt-get update -y
apt-get install -y musl

I can run the binary with ./query-engine cli get-config --ignoreEnvVarErrors and get the following error message:

My guess is that the binary does not exist precompiled, so I would have to compile the engine myself.

We have a ecosystem-test that runs on AWS Graviton: https://github.com/prisma/ecosystem-tests/tree/dev/platforms/aws-graviton
It can successfully execute queries, using the libquery_engine-linux-arm64-openssl-1.0.x.so.node or query-engine-linux-arm64-openssl-1.0.x Query Engine:
https://github.com/prisma/ecosystem-tests/blob/b3e395f3ec54fcc7944eb13b78d57ed789353ad4/platforms/aws-graviton/code/index.test.js#L28-L46
So I think you took a wrong assumption and turn there, and the problem is actually a different one. Possible?

Thanks I have now managed to get the server to start up

without Docker (simply with yarn start) and
with Docker without the alpine image.

The server does not start with an Alpine image, but it looks like many are having problems with it.. The Docker image is now 2.8GB without Alpine instead of 700MB, but I can live with that for now. Thanks for your tips @janpio!


Fix for Firewall issue #590

The dl_type=ARP (or any other dl_type) is overwritten if dst-ip or src-ip are specified later on in the json object. I added condition that only overwrites the field if it hasn't been already specified.

@chechoRP Thanks for the patch!


Fix name of ip2_right bias

closes #574

@danst18 would you mind reviewing the change? Thanks!

@gheinrich Looks good to me. Thanks.


tensorflow protobuf problem about:A protocolmessage was rejected because it was too big (more than 67108864 bytes)

I got this problem when trying to run a chief worker of distribute tensorflow. The tensorflow was installed by pip,not from source. Then I uninstalled protobuf by pip and then download the source and changed 256 << 20 in coded_stream.h .
And I installed protobuf as Readme said.But the same problem occurred, It seems that tensorflow did not use the new compiled libprotobuf.  How could I fixed this issue? If I have to reinstall tensorflow? Or someone can give me a updated protobuf that can fix the 64m limit? Thanks If someone could help me, I am going to mad about this issue(T_T)

Duplicate of #3938
Please see https://github.com/tensorflow/tensorflow/blob/master/tensorflow/g3doc/get_started/os_setup.md#protobuf-library-related-issues


Analyzer extension method resolution is incorrect for nullable types

The following program resolves an extension on T? to an int? receiver, which should result in T being resolved to int, and hence the return type of foo being int:
extension Test<T> on T? {
  T get foo => this!;
}

void main() {
  int? a;
  a.foo.isEven;
}

The analyzer currently emits an incorrect error on this indicating that the return type of foo is nullable.
leafp-macbookpro:tmp leafp$ /Users/leafp/src/dart-repo/sdk/xcodebuild/ReleaseX64NNBD/dart-sdk/bin/dartanalyzer --enable-experiment=non-nullable ~/tmp/test4.dart
Analyzing /Users/leafp/tmp/test4.dart...
  error • The expression is nullable and must be null-checked before it can be used. • test4.dart:26:3 • unchecked_use_of_nullable_value

cc @scheglov

https://dart-review.googlesource.com/c/sdk/+/138790
Well, method body inference is not specified, so I don't know for sure if I'm doing it right.
But this CL fixes the test case.


AZ Rebalance gets suspendend by default in v17.22.0

Description
Our tf code is adding on the worker autoscaling groups the AZRebalance as a suspending process.
I had to go to .terraform/modules/eks/locals.tf and from there locate the default values of workers_group and change suspended_processes from ["AZRebalance"] to null.
But we use a pipeline to apply the terraform code and manually edit the .terraform folder is not an option.
Can you please advise?

you can change this via input workers_group_defaults (applicable to all workers):
workers_group_defaults = {
   suspended_processes = null
}

or by defining to particular worker group:
 worker_groups = [
   {
     name                          = "worker-group-1"
     instance_type                 = "t3.small"
     additional_userdata           = "echo foo bar"
     asg_desired_capacity          = 2
     additional_security_group_ids = [aws_security_group.worker_group_mgmt_one.id]
   },
   {
     name                          = "worker-group-2"
     instance_type                 = "t3.medium"
     additional_userdata           = "echo foo bar"
     additional_security_group_ids = [aws_security_group.worker_group_mgmt_two.id]
     asg_desired_capacity          = 1
     suspended_processes = null
   },
 ]

Thank you Dawid.


Fix Xcode 7 warnings

I think we should consider adding:
- (instancetype)init NS_UNAVAILABLE;

... to the class extension interface, too.

2.0 pods does not seem to have this fix. At least Xcode 7 gives the error.

It won't be in cocoa pods until there is a new release.

Will try and get one out soon.

2.1 should include this.


Don't create packets on encryption levels already done

After dropping keys for an encryption level, we should not create packets that use the dropped key.
Currently ATS tries to create INITIAL packets after dropping keys for the encryption level, and it seems like to cause an abort below.
[Mar 15 16:30:37.113] [ET_NET 6] DEBUG: <QUICPacketFactory.cc:309 (_create_encrypted_packet> (v_quic_packet       ) [83411b05-e5a129af] Encrypting INITIAL packet #2 using CLEARTEXT
=================================================================
==447==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7f5a4c080a28 at pc 0x000000eb431b bp 0x7f5a4c080870 sp 0x7f5a4c080860
READ of size 1 at 0x7f5a4c080a28 thread T8 ([ET_NET 6])
    #0 0xeb431a in QUICPacketPayloadProtector::_gen_nonce(unsigned char*, unsigned long&, unsigned long, unsigned char const*, unsigned long) const /usr/local/src/trafficserver/iocore/net/quic/QUICPacketPayloadProtector.cc:98
    #1 0xeb461b in QUICPacketPayloadProtector::_protect(unsigned char*, unsigned long&, unsigned long, unsigned char const*, unsigned long, unsigned long, unsigned char const*, unsigned long, unsigned char const*, unsigned char const*, unsigned long, evp_cipher_st const*, unsigned long) const /usr/local/src/trafficserver/iocore/net/quic/QUICPacketPayloadProtector_openssl.cc:40
    #2 0xeb3a12 in QUICPacketPayloadProtector::protect(unsigned char*, unsigned long&, unsigned long, unsigned char const*, unsigned long, unsigned long, unsigned char const*, unsigned long, QUICKeyPhase) const /usr/local/src/trafficserver/iocore/net/quic/QUICPacketPayloadProtector.cc:45
    #3 0xe5b17a in QUICPacketFactory::_create_encrypted_packet(std::unique_ptr<QUICPacketHeader, void (*)(QUICPacketHeader*)>, bool, bool) /usr/local/src/trafficserver/iocore/net/quic/QUICPacketFactory.cc:312
    #4 0xe58705 in QUICPacketFactory::create_initial_packet(QUICConnectionId, QUICConnectionId, unsigned long, std::unique_ptr<unsigned char [], ats_unique_buf_deleter>, unsigned long, bool, bool, bool, std::unique_ptr<unsigned char [], ats_unique_buf_deleter>, unsigned long) /usr/local/src/trafficserver/iocore/net/quic/QUICPacketFactory.cc:208

Testing on the public test server.

Yeh, I'm not too sure how it should be like at the moment. We may need to change the logic when we support new frames for key management but this is my best guess.
A good news is that it seems like the change solved the abort issue.


Add integration tests covering etcd snapshots.

Describe the solution you'd like
Using Ginko and Gomega, develop integration tests to serve as a model for future tests. These will focus on the etcd snapshot feature recently added.
Additional context
Related issues for etcd snapshot commands
https://github.com/k3s-io/k3s/issues/3309
https://github.com/k3s-io/k3s/issues/3278
https://github.com/k3s-io/k3s/issues/3240

Closing this as it only concerned testing.


Modified LAR is spelled wrong

Modified is spelled Modifed - should be corrected.

Adding two additional very small changes:

Can the F in LAR Formatting be capitalized on the home page?
When selecting Tools from the home page and navigating to https://ffiec.cfpb.gov/tools/, can the t in "HMDA tools" be capitalized as well?


Feature/additional callbacks

Coverage decreased (-1.4%) to 87.734% when pulling e6ec02b9893a541311f95f3fe5940fe9b757be4b on feature/additional-callbacks into 31c366cdd2786fdfb9bda1eaf7cbd7fe33480616 on master.


Added new descriptions to Login and Onboarding views.

Name of the PR
:recycle: Current situation & Problem
Describe the current situation (if possible, with an exemplary (or real) code snippet and/or where this is used)
Please link any open issue that is addressed with this PR
:bulb: Proposed solution
Describe the solution and how this affects the project and internal structure
:gear: Release Notes
Add a summary of the feature and possible migration guides if this is a breaking change so this section can be added to the release notes.
Include code snippets that provide examples of the feature implemented if it appends or changes the public interface.
:heavy_plus_sign: Additional Information
Provide some additional information if possible
Related PRs
Reference the related PRs
Testing
Are there tests included? If yes, which situations are tested, and which corner cases are missing?
Reviewer Nudging
Where should the reviewer start? Where is a good entry point?
Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[ ] I agree to follow the Code of Conduct and Contributing Guidelines.

@dguo8412 is this PR ready for review? Or are you planning to make any more changes?


wait for lazycachemanager in parallel

wait for the lazycachemanager in parallel, outside of the mutex
Signed-off-by: Alex Couture-Beil<EMAIL_ADDRESS>

example earthly update https://github.com/earthly/earthly/pull/2022


Add new total constructed and total preserved housing units by geography

Medium PR, should have two reviewers 🏠
Addresses issue #291. I chose to call the new code from the wrapper function pivot_add_total to keep the <geography>_hny_units_con_type function simpler.
The files for internal review can be un-committed after this PR is approved, no need to merge them in

New commits should both those concerns


Tweak CSR constraints for more even read/write distribution

Where contraints allow a CSR to be both read and written read-only vs
read-write (and write-only) operation was effectively chosen by which
register or immediate was randomly chosen. This made read-only accesses
to such CSRs rare.
Now we explicitly choose to do a read or a read-write with an explicit
random bit that is solved before the register or immediate.
Even with this change the distruibution skews to read-write operation as
the CSRRW and CSRRWI instructions cannot be read-only and that is chosen
independently of the explicit read-only/read-write decision introduced
by this commit. Fixing this so we get a 50/50 distribution of
read-only/read-write is significantly more complex but isn't required as
the read-only case is now sufficiently common.
This also allows the removal of the macro used to define the expression
for a writeable CSR giving neater code.

@ctopal @marnovandermaas @hcallahan-lowrisc PTAL

Yes, there's a list of supported CSRs supplied in the core setting file. On top of that there is a list of CSRs that can be written to, which you can add and remove things from via plusargs or through modifying the list before the test begins.

@weicaiyang PTAL


use ~> 1.0.0 in readme

Now that 1.0.0 has been released.

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:


KOS v<IP_ADDRESS>

Resolves #52 : build paths are updated to new version
Resolves #53 : v<IP_ADDRESS> is supplied as deb-package, that installs all required dependencies
Resolves #43 : logger from 86786e1 is included in this pull-request
Resolves #28 : see comment for this issue
Also .hex and .apj Ardupilot firmware (build from branch 'ardupilot') is added

LGTM


Visual Script's dictionary variable in the members' window shows its keys in the A to Z format regardless of their index

Godot version:

Godot 3.2.4 beta4

OS/device including version:

Issue description:

Visual Script's dictionary variable in the members' window shows its keys in the A to Z format regardless of their index, as shown in the screenshot below:

This is very confusing especially when trying to get the keys by their index, as shown in the screenshot below:

I tested this in GDScript also which confirmed that the dictionary's keys are not related to their alphabet order, as shown in the screenshot below:

I expected the dictionary variable to show its keys based on their index in the members' windows.
Steps to reproduce:

Create a dictionary variable in Visual Script.
Add some keys.
See the value in the members' window.
Try to print and get the keys' index.

Minimal reproduction project:

test.zip

This issue still presents as of Godot v3.4.3.rc2.official [0ea54d07f], as shown in the screenshot below:

However, this issue is fixed in Godot 4 as of v4.0.alpha2.official [79077e6c1], as shown in the screenshot below:

Note: the variable type icon in the members' window incorrectly shows as the array type due to issue #58117.
I also upload a reproduction project for Godot 4 below:
G4Test.zip
I don't know whether I should close this issue since it's already fixed in Godot 4 but not Godot 3.

I think we can close it as fixed in 4.0. But anyone is welcome to PR a fix for 3.x too if wanted.


Adapters

Implemented the adapter idea in https://github.com/jprochazk/garde/issues/82#issuecomment-1849100734

Released in v0.18


Upgrade Boot to 2.0.2 and Cloud to Finchley.RC2

Just for a note: once we have Finchley GA, I believe that we don't need explicit Boot version...

@artembilan Thanks, I made a note of it in #726.


Publish a DomainEventMessage outside of an aggregate

Hello,
it's more a question or feature request than an issue.
I'm working in the Smart Home/IoT-domain and our system consumes events (messages) from gateways/devices via AMQP. The events represent domain events and we want to store them in the event store (keyword: event sourcing). Gateways/devices are our aggregate roots and we want to able to reconstruct their state based on events (keyword: digital twins).
I need a way to apply a GenericDomainEventMessage outside of an aggregate. The simplest solution would be to to use the EventBus to publish the GenericDomainEventMessage. The Event Message could have a field with an @TargetAggregateIdentifier annotation. The EventBus then knows how to set the aggregateIdentifier in the event store and how to increase the sequenceNumber.
What do you think?

Hi @RobWin,
Interesting use case you've got there. Typically I'd not be overly enthusiastic to let outside sources influence your aggregates, but this seems a little different from the other use cases I've come across.
I've discussed it with @abuijze and we've not reached the point that it should be a feature in the framework yet, but created this yourself should be fairly easy.
So, what I'd suggest to do is the following:

You'll need the latest sequence number to set your domain events at the right spot in the store. To grab the latest sequence id for a given aggregate, you can use the EventStore#lastSequenceNumberFor(String aggregateIdentifier).
To instantiate the GenericDomainEventMessage you're going to append you can just call the constructor of the GenericDomainEventMessage, providing the aggregate type, the aggregateIdentifier (which you've previously used to pull the sequence number), the sequenceNumber you've retrieved in the previous operation and the payload, being the event you've received. You can additionally provide you own meta data as a Map, which could contain the correlation id of the AMQP message, a message identifier and a timestamp. I'd suggest to leave the latter two to the GenericDomainEventMessage constructor, but you could provide your own if necessary.
After you've created your GenericDomainEventMessage, you can call the EventBus#publish(List<? extends EventMessage<?>> events) function to publish your event. If you're using the EmbeddedEventStore (which I guess you will), the event will be stored, and after that handled by any Event Listeners you have.

The only caveat to this is that the EventStore#lastSequenceNumberFor(String aggregateIdentifier) is not in a release yet. It's already part of 3.2 though, which should be released somewhere end of month.
Would this solution work out for you @RobWin?

Yes, but how can I make sure that the sequenceNumber is not increased in parallel by another node/thread?
I need a way to increase the sequenceNumer atomically so that this number can solely be used by my thread.
I assume EventStore#lastSequenceNumberFor does not increase the sequence number for me?

What is the reason that EventBus#publish does not increase the sequenceNumber?

Since atomic counters (sequence numbers) in distributed systems are slow and difficult to implement, wouldn't it be possible that EventStore#readEvents(String aggregateIdentifier) orders events by creation timestamp and uses the event identifier or hash of the timestamp as an offset (sequence number)?
Isn't the sequence number anway an implementation detail of the Eventstore? The event producer should not know anything about this. Only event consumers are interesting in the offset.

Hi Robert,
I think you may be mixing up two different things here. The sequence number is used by an Aggregate as it emits events to ensure its internal consistency. It is not used by the event store to order events globally. Since an Aggregate is a unit of consistency (by definition of Domain Driven Design), there shouldn't normally be any conflicts here. An Aggregate is responsible for maintaining its own state.
Consumers don't need this sequence number. They either subscribe to Events (using a SubscribingEventProcessor) or they pull Events in (using a TrackingEventProcessor). In the latter case, they are ordered as much as possible in the order as they were published, depending on what the underlying implementation is able to do. This ordering has nothing to do with the sequence number.
You said "As a User of an API I don't want to handle incremental sequence numbers :(". Good news: you don't, normally. If you implement an aggregate, all you need to do is apply() your events, and Axon will update your sequence number for that specific Aggregate automatically.
If you don't use Aggregates, but just have a Command handling component that emits events, then you probably don't need sequence numbers at all. These are only necessary if you have Aggregates you want to source from its past events.
If you do want to be able to track events to a specific (conceptual) Aggregate, but without using an Aggregate itself, then as of Axon 3.2, it will be possible to retrieve the last used sequence number for that Aggregate. Again, there shouldn't be any conflicts here, because the Aggregate should not be concurrently accessed. If it is, then you should be glad a Duplicate Key conflict (or whatever the underlying store reports) is thrown to notify you of a potential consistency breach.
Hope this clarifies things.

Hi,
thank you for your clarification.
Our scenario looks as follows.
A client sends a command to a real device and the real device emits an event when the command has been processed. We want to update the cloud representation (digital twin) of the device.
I guess I have to translate incoming event messages from devices into commands which are handled by a device aggregate (digital twin) which itself emits/applies a similar internal event. It's like simulating the real communication. Seems fine to me.

Hi guys
I think that I have similar problem.
Concretely I use sagas to handle payment transaction. My scenario is following:

Clients send starts/end payment commands PaymentStartCommad and PaymentEndCommad to command handler what is same class as my aggregate BankAccount
with aggregate identifier uid
Command handler (within my aggregate) just applies PaymentStartedEvent and PaymentEndEvent to saga instance
Saga handles PaymentStartedEvent(@EndSaga) by way that schedules other event PaymentExpiredEvent(after 30 seconds) that something wrong and payment is aborted
Saga also handles PaymentEndEvent(@EndSaga) and cancel scheduled event PaymentExpiredEvent

When PaymentExpiredEvent occurs it is stored into db where event identifier is same as aggregate identifier column . That means that such event can not be used during event sourcing of my aggregate.
Q: Am I right? Is this correct behaviour?
If so, what I can do as RobWin mentioned is to trigger another PaymentExpiredCommand from saga and create similar ExpiredEvent which will be joind with aggregate. But I want to avoid this if possible.
Q: What can I do?
thank you very much


Internationalization (i18n) Afrikaans

Added Afrikaans translation
This pull request includes a

[ ] Bug fix
[ ] New feature
[x] Translation

The following changes were made

Translations added for Afrikaans

Hi @pjjroux, thanks for contributing!  Unfortunately, we cannot accept PRs that make changes directly to dist/.  Please make your changes in src/js/select2/i18n only, as per the contributing guide.  Thanks!

@pjjroux I am closing this as a duplicate of #4850.  Could you please take a look at that PR and make any suggestions you have for improvement, in that thread?


Add documentation about inactivity/abort timeout

@gvdongen I think we need a general page that describes the suspension behavior, and then how to tune these parameters, that we can link when people stumble on the inactivity/abort timeout. WDYT?


watch doesn't work since 2.2.0-rc.7

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
When using webpack --watch --config my.config.js with webpack 2.2.0 rc7 it processes all files, then terminates without an error. It just behaves like running without the --watch option. Last working version was 2.2.0 rc6
If the current behavior is a bug, please provide the steps to reproduce.
Here's the complete webpack.config.js : http://pastebin.com/xpZ4eGnA

What is the expected behavior?
It's expected to behave just like in version 2.2.0 rc6. This means: Don't terminate, but instead keep watching for file changes.
If this is a feature request, what is motivation or use case for changing the behavior?
It's a bug
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Ubuntu 16.10 , Node.js 7.4.0 , webpack 2.2.0 rc7

+1

Could you try again with 2.2.0-rc.8?

@benneq
No such problem for me on rc7 or rc8.
You might have reached the Kernel inotify watch limit. Check this.

Great

No it was a bug in the RC. We should have it fixed. I just want to have a confirmation from @benneq to close it.

Tested on 2.2.0 it works fine again, this can be closed. Here is the issue: https://github.com/webpack/webpack/issues/2664.

Tested on rc8 and final. WORKS! :+1:


Adding duplicate service provider to UAA IdP causes 500 Server Error

If service provider with the same entityID already exists, POST /saml/service-providers causes 500 Internal Server Error.
UAA logs: SecurityFilterChainPostProcessor$HttpsEnforcementFilter: org.springframework.web.util.NestedServletException: Request processing failed; nested exception is error="sp_exists", error_description="integrity constraint violation: unique constraint or index violation: ENTITY_IN_ZONE”.
POST call should then return 409 Conflict instead of 500.  Similar to how it’s done for identity providers or in the original GE implementation of "UAA as saml IdP".

https://github.com/GESoftware-CF/uaa/tree/uaa_as_saml_idp_3.0.0
Pull request: https://github.com/cloudfoundry/uaa/pull/303/files#diff-6f05571741ade271bc64070f20f29992
https://github.com/GESoftware-CF/uaa/blob/uaa_as_saml_idp_3.0.0/server/src/main/java/org/cloudfoundry/identity/uaa/provider/saml/idp/SamlServiceProviderConfigurator.java line 171-173

In the original implementation:

adding service provider with the same entityID and the same alias would replace existing one with new.
adding service provider with the same entityID and different alias as the existing one would cause "Duplicate entity id..." MetadataProviderException and result in 409 Conflict response.

This story has been picked up and will be available as part of UAA 3.8.0


Fix rolling of request log files.

There's a small bug in the naming of requests's log files. Files created at midnight roll have the yyyy-MM-dd'T'HH:mm:.. DateFormat and files created on druid (re)start have the yyyy-MM-dd DateFormat.

👍


Deleting a State Frame from Treeview should ask about deleting calls to state in state strings

Deleting a State Frame from Treeview should ask about deleting calls to state in state strings.

Does this automatically and warns user. https://github.com/JKISoftware/JKI-State-Machine-Editor/releases/tag/2<IP_ADDRESS>


Updated meltano.yml in cookeicutter to match tutorial

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/112
Originally created by @aaronsteers on 2021-04-22 17:14:17

As follow-on to the tutorial here, we should update the meltano.yml with capabilities and settings.

View 3 previous comments from the original issue on GitLab


Add salt, tomato and onion to c tags and make recipes use them

This pull request adds Bon Appetit's salt, tomato and onion items to the c tags for these items, so that other mods with their own salt, tomatoes or onions that use the tags can use Bon Appetit's in their recipes. This pull request also makes all of Bon Appetit's recipes involving these three items use the tags instead, so that other mods' salt, tomatoes and onions can be used in its recipes.
I didn't make the salt block recipe use #c:salt, as the salt block is more specific to this mod's salt in particular.
This is a good thing to have for compatibility with other mods that use these tags, such as Sandwichable or Croptopia.

Thank you my friend, we appreciate your help <3

Thank you my friend, we appreciate your help <3


Test failures on Window 32 bit

Running OpenEXRTest in Visual Studio 2022 in 32 bit mode will cause multiple test failures.
One example:

=======
Running testOptimizedInterleavePatterns
Testing SSE optimisation with different interleave patterns (large images) ...
0, 0: RGBHalf read as RGBHalf...                            OK OPTIMISED
0, 1: RGBHalf read as RGBAHalf...                           OK OPTIMISED
0, 2: RGBHalf read as ABGRHalf...                           OK
0, 3: RGBHalf read as RGBFloat...
error reading back channel B pixel 72,88 got -nan expected -nan
Assertion failed: writtenHalf.bits () == readHalf.bits (), file C:\work\BlocksDesign\common\openexr\src\test\OpenEXRTest\testOptimizedInterleavePatterns.cpp, line 268

I am testing in Debug mode.
This test passes in 64bit mode.

I encouterd same error on Linux i686.
The same treatment against random-generated image seems to be applied
similar to https://github.com/AcademySoftwareFoundation/openexr/issues/570 .
Following patch seems to fix this.
diff -up ./src/test/OpenEXRTest/testOptimizedInterleavePatterns.cpp.32 ./src/test/OpenEXRTest/testOptimizedInterleavePatterns.cpp
--- ./src/test/OpenEXRTest/testOptimizedInterleavePatterns.cpp.32       2021-08-01 04:57:32.000000000 +0900
+++ ./src/test/OpenEXRTest/testOptimizedInterleavePatterns.cpp  2022-12-04 02:08:25.171731619 +0900
@@ -350,9 +350,12 @@ setupBuffer (const Header& hdr,       //
      int chan=0;
      for (int i=0;i<samples;i++)
      {
-         unsigned short int values = random_int(std::numeric_limits<unsigned short>::max());
          half v;
-         v.setBits(values);
+         do {
+             unsigned short int values = random_int(std::numeric_limits<unsigned short>::max());
+             v.setBits(values);
+         } while( v.isNan() );
+
          if (pt==NULL || pt[chan]==IMF::HALF)
          {
              *(half*)write_ptr = half(v);


Display contact details for publisher

Relates to #4. There’s a contact address in both the dataset and the publisher metadata, though they don’t always agree.
I guess we should prefer the dataset contact address.

This can live on the summary page.

It occurs to me this might well be breaking some GDPR rules @JamesCoe…


Tracking Issue: Enable WebGPU graph execution

### Tasks
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1239
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1240
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1241
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1255
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1258
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1259
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1266
- [x] Investigate if we can manually influence the limits and have that actually affect something (blocked by WebGPU Device Limits gfx-rs/wgpu#3299?)
- [x] Make compilation server cache requests
- [ ] Automatically include Draw Canvas node in the output
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1298
- [ ] Add feature gate to only display GPU-based nodes when wgpu is available
- [ ] Add documentation + tests + improve the API
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1296
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1299
- [ ] Modularize GPU blend mode as a merge node
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1295
- [ ] Add nodes for updating existing buffers
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1300
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1293
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1297
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1302
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1303
- [ ] https://github.com/GraphiteEditor/Graphite/issues/1307

The latest browser support status

Safari: now behind a flag in Technical Preview as of December 21, 2023 (https://webkit.org/blog/14879/webgpu-now-available-for-testing-in-safari-technology-preview/)
Firefox: behind a flag in Nightly (https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features#webgpu_api), progress towards stabilization tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=1616739
Chromium: shipped for all users on Windows 10+, Mac, and ChromeOS. Linux and Android are behind a flag (and require Canary?)

See also:

caniuse
MDN compat table

Moved to #https://github.com/GraphiteEditor/Graphite/issues/144.


Api

In this pull request

Use LeaderBoard API
Add send feature that sends the data to API POST
Receive the data from API

Hi @Hassaanjbaig-code 😊,
While you made a great effort in this project, I cannot proceed to review your code.
Invalid Code Review Request 🛑 💀
You have submitted a project, that doesn't contain future features section in the README.
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Add channel points support now that there is an API

What should be added?
The ability to

Earn periodic channel points like on the website
Redeem the bonus channel points
Spend channel points

Why should it be added?
Because this has been requested many times and denied in the past, but now there is an API for it: https://blog.twitch.tv/en/2020/11/13/twitch-developer-day-2020-introducing-the-channel-points-api-eventsub-and-more/

As mentioned in the blog post you linked, the new API enables developers to ...

Just because it says "Channel points API" it doesn't necessarily mean it gives us what we want. I gotta say twitch just made a big "bait" by "introducing the channel points API".

I hoped I was just reading it wrong. Oh well.

Duplicate of https://github.com/Chatterino/chatterino2/issues/1455


Add more detailed error handling and logging

As a developer, I want to have more detailed logging of INFO, WARNING, and ERROR severity to be able to quickly understand what was going on on the server before it failed or if there were any configuration or other service connection issues.
Cases to be handled:

User provide bad config info in .env file or it is not provided at all.
Connection to the SlackAPI was refused or 400-500 response was sent.

Think of other possible scenarios that could go wrong during the runtime.

https://api.slack.com/methods/chat.postMessage#errors


Compatibility with Sphinx 3.x

Hi there,
we found building the docs to fail on crate/crate when upgrading to Sphinx 3.x, see [1]. While I can confirm it happened there [2], I can also confirm it works just fine when following these steps.
Setup
https://github.com/crate/crate
cd crate
virtualenv .venv --python=python3.8
source .venv/bin/activate
pip install -r docs/requirements.txt
pip install sphinx==3.3.1

Check versions
sphinx-build --version
sphinx-build 3.3.1

>>> import crate.theme.rtd
>>> crate.theme.rtd.VERSION
(0, 11, 0)

Build the docs
sphinx-build -n -W --keep-going -c docs/ -b html -E docs/ docs/out/html
open docs/out/html/index.html

With kind regards,
Andreas.
[1] https://github.com/crate/crate/pull/10831#issuecomment-734895613
[2] https://jenkins.crate.io/blue/organizations/jenkins/CrateDB%2Fcrate_on_pr/detail/crate_on_pr/12338/pipeline

However, when looking closer at [2], we see that
Collecting crate-docs-theme
  Using cached crate_docs_theme-0.10.17-py3-none-any.whl (3.8 MB)

Collecting crate-docs-theme
  Using cached crate_docs_theme-0.10.16-py3-none-any.whl (3.8 MB)

Collecting crate-docs-theme
  Using cached crate_docs_theme-0.10.15-py3-none-any.whl (3.8 MB)

Collecting crate-docs-theme
  Using cached crate_docs_theme-0.10.14-py3-none-any.whl (3.8 MB)

[...]

Collecting crate-docs-theme
  Using cached crate_docs_theme-0.5.71-py3-none-any.whl (3.8 MB)

Collecting crate-docs-theme
  Using cached crate_docs_theme-0.5.70-py3-none-any.whl (3.8 MB)

Collecting crate-docs-theme
  Downloading crate_docs_theme-0.5.69-py3-none-any.whl (3.8 MB)

So, the process is actually installing the lowest possible version of crate_docs_theme available on our custom python package server.
  Attempting uninstall: crate-docs-theme
    Found existing installation: crate-docs-theme 0.11.0
    Uninstalling crate-docs-theme-0.11.0:
      Successfully uninstalled crate-docs-theme-0.11.0
Successfully installed crate-docs-theme-0.5.69

This is really outdated. I don't wonder that this fails.
So, the process of running on Jenkins and/or using the alternate installation method through [3,4] is apparently the culprit here.
[3] https://github.com/crate/crate/blob/4.3.2/blackbox/bootstrap.sh
[4] https://github.com/crate/crate/blob/4.3.2/blackbox/requirements.txt

As I can see crate-docs-theme is already available on PyPI these days [5], I suggest to drop all relevant packages from the custom python package server completely.
However, I still wonder why the installation process would choose the oldest version available from there.
[5] https://pypi.org/project/crate-docs-theme

I believe crate-docs-theme is compatible with Sphinx 3.x, so closing this.


Ember cli rails breaks when deprecations(warnings) are found on Ember

Linux 64-bits, Manjaro(Arch Linux)
ruby 2.1.8
npm 3.9.5
ember-cli 2.6.2
rails 4.2.6
ember-cli-rails gem 0.7.4
ember-cli-rails-addon 0.7.0
application server webrick
#config/initializers/ember.rb
EmberCli.configure do |c|
  c.app :frontend
end

contents of the Rails' view
<%= render_ember_app :frontend do |head, body| %>
<% end %>

route.rb
mount_ember_app    :frontend, to: '/cursos', controller: 'ember_loader'
mount_ember_assets :frontend, to: '/'

There is a problem on ember-cli-rails, every deprecation raise like a BuildError, which is not good, a deprecation example:
DEPRECATION: Overriding init without calling this._super is deprecated

Pull Request: #465

@victor95pc https://github.com/thoughtbot/ember-cli-rails/pull/468 should address this.
Would you mind pulling down master and testing whether it has been resolved?

@seanpdoyle @mhaylock Thx guys for your work, sorry for the delay, this PR work perfect and cover all use cases.

@victor95pc thanks for clarifying!


Disable automatic pathname encoding

In #442 and #445 automatic encoding of pathname was added. This change breaks my application and I could not find a good workaround except reverting to<EMAIL_ADDRESS>The app uses react-router and URLs that look like /view/:id, where ids can contains # and other special characters (e.g. a link to id #abc is encoded <Link to="/view/%23abc" />). With<EMAIL_ADDRESS>and earlier, everything worked fine; the app takes care to correctly encode the id and links work.
After upgrading to v4.6.0 and v4.6.1, when clicking the link /view/%23abc (or when using history.push on the same URL), the browser address bar unexpectedly shows /view/%2523abc. Note the double encoding of the # character.
Below is a standalone repro of the issue, comparing pushState with<EMAIL_ADDRESS>push, against window.location.pathname.
To run it, save the file locally, then npm i http-server && node node_modules/.bin/http-server -a <IP_ADDRESS> -p 8080.
<!doctype html>

In the console output, note the double encoding of # when using history.push:
after pushState /%23pushState true
after history.push /%2523history.push false

When the first


Use same thread for AsyncResultCallback

What is the story (motivation) behind this change?

Investigation with @losipiuk and @findepi (could be related to https://github.com/square/okio/issues/624)


Prevent adding Clone to Dome

Hi,
I have two List A and B. I want to drag from list A into B clone way. But want to prevent adding clone to list B dom.
Thanks

https://github.com/RubaXa/Sortable/blob/master/CONTRIBUTING.md#issue


t option and custom option arguments are tricky to handle correctly

So this is sort of a subtly weird thing that can trip you up if you're not careful.
Say you have a python fun like this:
    def say_hi(self, to_whom=None, greeting='hi'):
        if to_whom:
            return(f'{self.name} says {greeting} to {to_whom.name}')
        else:
            return(f'{self.name} says {greeting}')

Given that to_whom takes None in the python, you decide to make it explicit in the OCaml binding.
  val say_hi : t -> to_whom:t option -> greeting:string option -> unit -> string

However, this generates code that has the wrong signature
  let say_hi t ~to_whom ~greeting () =
    let callable = Py.Object.find_attr_string t "say_hi" in
    let kwargs =
      filter_opt
        [
          Some ("to_whom", to_pyobject to_whom);
          Some
            ( "greeting",
              (function Some x -> Py.String.of_string x | None -> Py.none)
                greeting );
        ]
    in
    Py.String.to_string
    @@ Py.Callable.to_function_with_keywords callable [||] kwargs

That sig is val say_hi : t -> to_whom:t -> greeting:string option -> unit -> string.
To make that arg actually optional with t, you would have to do this instead.
  val say_hi2 : t -> ?to_whom:t -> greeting:string option -> unit -> string

Note that this problem is only there for t option and custom option eg Doc.t option.
Fixing it
It's not straightforward to fix as t option as an argument passed to a python function and t option as a return type of an OCaml function need to be treated differently (and that depends on the --of-pyo-ret-type flag).
Short term fix is to document the weirdness and give an error when users try to use t option in this way.  Currently, the bindings will be generated and you won't know something is wrong until you try to build it.
Long term is to actually handle t option properly as an arg and also properly as a return type.

The other thing to keep in mind is if you have a Python function that returns either a custom object or None, the t option return type will be wrong too.
class Person:
    def __init__(self, name, age):
        self.name = name
        self.age = age

    def maybe_make_friend(self, color):
        if color == 'orange':
            return(Person(f'{self.name}\'s friend, Orange Soda', 33))
        else:
            return(None)

You would think to bind it like this:
  val maybe_make_friend : t -> color:string -> unit -> t option

That generates
  let maybe_make_friend t ~color () =
    let callable = Py.Object.find_attr_string t "maybe_make_friend" in
    let kwargs = filter_opt [ Some ("color", Py.String.of_string color) ] in
    of_pyobject @@ Py.Callable.to_function_with_keywords callable [||] kwargs

When the user is expecting it to generate something more like this:
let f t () =
  let callable = Py.Object.find_attr_string t "f" in
  let kwargs = filter_opt [ ] in
  (fun x -> if Py.is_none x then None else Some (of_pyobject x))
  @@ Py.Callable.to_function_with_keywords callable [||] kwargs

As above it has to do with the way --of-pyo-ret-type is working with things.  And the fact that t and custom types are treating differently from something like int option.


Improve and expand the prediction making process

This issue is created as a merge between Issue #1, Issue #2, and Issue #5, as all three point towards a common target. The said issues will be thus closed, and all activity will move here.
The prediction making should not be limited to the number of data files entries, and should work for both isobars and isotherms. Isosurfaces should also be predicted, probably using isotherms since they are easier to calculate.

The workflow for predictions has been greatly improved and isobars have been included in the script. However, due to difficulties in data storage and reading, predictions for isosurfaces have been left out. As such, Issue #5 will be reopened.


labels

can we predict the moving object without lables?

Hey @May-sysu, thanks for following our work. Our method currently using the proposed binary labels to achieve MOS.
If you want to remove dynamics without using labels, you may have a look at the map-based approaches, which can also detect moving objects without training.

yep，i know that。however, supervised classification is out-performer.  can we generate the moving object predictions with pretrained model in different scene？for example, we use pretrained model based on kitti datasets to predict the moving object in the mining area, like transfer application. and what do we need to focus on ? thanks for your answer

Good idea! We didn't test it so far. You may give it a try. The only problem I see here is that if the types of LIDAR sensors change, it usually cannot generalize very well.

Hey @May-sysu, thanks for the suggestion again! Since this is more about future work, I therefore would like to close this issue. If you are interested in this topic, we could discuss it further via email.

thanks for your generosity。after converting kitti-64 to kitti-16, this algorithm still works well。however, in the mining area, there is no accurate pose information ,which is a great blow to it because of residual image. whatever，i think this light algorithm maybe is better in the object detection.

Great to know that it works with different types of LIDAR sensors. We could also discuss this more while WeChat. My WeChat number is : Chen_Xieyuanli
I will appreciate it if you could also star this repo if you find it useful. Thanks!


SDM adoption roadmap in existing enterprise

When we enable an SDM it should not perform unexpected builds or deployments.
It will be receiving pushes. It should try to set up CI integration on pushes, which will enable richer behavior (eg move to SDM initiating build with existing build provider)...

Should it start adding github statuses to everyone’s commits?


Update of compiled package

as title. The release package is out of version that much feature is not implemented.

@terry182 I've updated the compiled files. You could find them at Lit releases page now. :)


Refactor

[ ] consistent tagId / tagPath in backend (rename from album_folder)
[x] move tasks into invoker. consistent api
[x] consistent casing: probably best practice is to keep camelCase in TS and snake_case in python, and to also use snake_case for anything going over the api.

tagId and tagPath renaming should be unified to always get both
casing convention is camel in frontend, snake in python and REST


WIP path curves between through dummy nodes

Currently blocked as I want to write it to compute the control points using a explict system of equations solved with \ rather than in the way they have it with Thomas's algorithm.
But i seem to be getting the math wrong

Codecov Report

Merging #24 (279efc4) into master (aca93eb) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 279efc4 differs from pull request most recent head a8ec203. Consider uploading reports for the commit a8ec203 to get more accurate results

@@           Coverage Diff           @@
##           master      #24   +/-   ##
=======================================
  Coverage   93.91%   93.91%
=======================================
  Files           6        5    -1
  Lines         148      148
=======================================
  Hits          139      139
  Misses          9        9

Flag
Coverage Δ

unittests
93.91% <100.00%> (ø)

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

Impacted Files
Coverage Δ

src/graph_viz.jl
88.88% <100.00%> (+0.31%)
:arrow_up:

src/ProjectManagement.jl

Continue to review full report at Codecov.

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

Whe should handly 3 points as a specil case.
That uses 1 curve passing through all points,
ratehr than 2 curves (one per segment)


PS Illegal Argument: minecraft

I downloaded your script and have attempted to get it working. However a lot of the commands that I try to run give me an error saying "ps: illegal argument: minecraft" commands such as start, stop, restart, delete, disable (and others). (A note when I run disable or delete they still work but the error comes up). I am trying to run a server called "OldServer" for testing purposes of this script so I know what to do for my actual server called "ServerMinecraft" (great naming convention I know). I am running minecraft through a jail in my FreeNAS server. I will attach a ssh log below of the whole error message. Thanks you the help.
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.02.13 11:44:21 =~=~=~=~=~=~=~=~=~=~=~=
login as: root

Last login: Fri Feb 13 11:06:12 2015 from <IP_ADDRESS>

FreeBSD 9.2-RELEASE-p9 (FREENAS.amd64) #0 r262572+cc525fe: Thu Jul  3 14:22:45 PDT 2014

	FreeNAS (c) 2009-2014, The FreeNAS Development Team
	All rights reserved.
	FreeNAS is released under the modified BSD license.

	For more information, documentation, help or support, go here:
 	http://freenas.org
Welcome to the Rye Family File Server.
]0;root@RyeFamily:~[root@RyeFamily] ~# jexec 1 /bin/sh

# cd /home/
/home/mcgame          /home/Mianite         /home/minecraft
/home/ServerMinecraft /home/Simplify

# cd /home/minecraft/
#
.cshrc            .login            .login_conf       .mail_aliases
.mailrc           .profile          .rhosts           .shrc
backups           maps              minecraft_server  versions.json
versions.json.bak worlds            worlds-disabled

# cd /home/minecraft/worlds/
/home/minecraft/worlds/OldServer       /home/minecraft/worlds/ServerMinecraft

# cd /home/minecraft/worlds/OldServer/
/home/minecraft/worlds/OldServer/backup
/home/minecraft/worlds/OldServer/banned-ips.txt
/home/minecraft/worlds/OldServer/banned-players.txt
/home/minecraft/worlds/OldServer/bukkit.yml
/home/minecraft/worlds/OldServer/commands.yml
/home/minecraft/worlds/OldServer/craftbukkit-dev.jar
/home/minecraft/worlds/OldServer/crash-reports
/home/minecraft/worlds/OldServer/debug
/home/minecraft/worlds/OldServer/download
/home/minecraft/worlds/OldServer/help.yml
/home/minecraft/worlds/OldServer/logs
/home/minecraft/worlds/OldServer/minecraft_server.1.7.2.jar
/home/minecraft/worlds/OldServer/nas_server_world
/home/minecraft/worlds/OldServer/nas_server_world_nether
/home/minecraft/worlds/OldServer/nas_server_world_the_end
/home/minecraft/worlds/OldServer/ops.txt
/home/minecraft/worlds/OldServer/permissions.yml
/home/minecraft/worlds/OldServer/plugins
/home/minecraft/worlds/OldServer/save
/home/minecraft/worlds/OldServer/server.properties
/home/minecraft/worlds/OldServer/snapshots
/home/minecraft/worlds/OldServer/wepif.yml
/home/minecraft/worlds/OldServer/white-list.txt

# cd /home/minecraft/worlds/OldServer/
# su minecraft
$ cd ~/
$ /etc/init.d/minecraft_server start OldServer
Starting Minecraft Server:ps: illegal argument: minecraft
usage: ps [-aCcdefHhjlmrSTuvwXxZ] [-O fmt | -o fmt] [-G gid[,gid...]]
          [-M core] [-N system]
          [-p pid[,pid...]] [-t tty[,tty...]] [-U user[,user...]]
       ps [-L]
 OldServerError updating the Minecraft server software.
$ exit
# exit
]0;root@RyeFamily:~[root@RyeFamily] ~# exit

logout

This is happening because it looks like the version of ps on FreeBSD has a slightly different command line syntax.  If you change the -u to a -U on line 343, does that fix the problem?
 ps -a -u $USER_NAME -o pid,comm,args |

 ps -a -U $USER_NAME -o pid,comm,args |

After reading through the docs of the Linux and FreeBSD man pages for ps and running tests (on Linux), I sent commit 6f600fb22cd201d9efcbe65d7587f04c7405362a to hopefully fix the problem for you.  The -u option is not synonymous to -U on FreeBSD like it is on Linux, and -U is what you need on FreeBSD.

Yes that fixed that issue perfectly! Thanks so much. I ran into a few other issues but I believe this is due to improper settings on my end at the moment so I'll do some digging before I post again.

No problem, glad that worked for you.  I like easy fixes like this.

Hey @GamerMan7799 , is it possible to publish your changes of "Makefile" and the script to get it working on your FreeNAS?


feat: Add WYSIWYG keymap to change to task list

Please check if the PR fulfills these requirements

[x] It's the right issue type on the title
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[x] It does not introduce a breaking change or has a description of the breaking change

Description
This keymap already exists on the Markdown view. The command also already exists, so I've just registered it as it's done on Markdown and added tests.
I also propose to change some function names to make it more similar to what's in Markdown, and because "toggle" in some other places in the code means toggling between [ ] to [x].
This will make it easier to understand when this toggling command and keymap is added to WYSIWYG as well (which I would like to propose in a separate Pull Request).

If it helps to bring the proposed renames into context, this is another commit I'll want to suggest: https://github.com/egrajeda/tui.editor/commit/5b4e33875de3e5cc47e2d6e614a5411f73039d91. It adds the same functionality that Markdown already has to toggle a task.


KAFKA-15784: Ensure atomicity of in memory update and write when transactionally committing offsets

Rewrote the verification flow to pass a callback when we start verification to execute after verification completes.
For the produce path, we will just continue with appendRecords, but for the TxnOffsetCommit, we will call doTxnCommitOffsets. This allows us to do offset validations post verification.
I've reorganized the verification code and group coordinator code to make these code paths clearer. Non-transaction verification code should be minimally affected by verification now and the code should be logically separated more clearly.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@jolshan : Thanks for the PR. Should we fix the append call in CoordinatorRuntime (https://github.com/apache/kafka/pull/14705) too? There, a partition level lock in CoordinatorRuntime is held while checking/updating the coordinator state and calling append.

@junrao Thanks for taking a look. I was just rewriting the code to make this clearer. I will take a look at @artemlivshits and your questions about locking now.

@junrao @jolshan I work on implementing the transactional offset commits in the new world. I will take care of adding the verification steps there when this PR is done. We can replicate the same pattern there.

I took a look at the tests and the only one that looked suspicious were the mirrorIntegration tests related to delete.retention.ms not being configured correctly. I saw some flakes in trunk and other PRs and that seems unrelated to this change.
Note, although the last build had a failure for a version, the previous build succeeded and only included a minor code change. Given the nature of the change and the failure, I believe this is non-blocking.
I ran system tests and noticed an issue with GroupModeTransactionsTest when bouncing brokers. After investigating with @hachikuji we believe it is unrelated. He will file a JIRA as a followup.


[BEAM-8231] Fix state sampler dropping the stage and step name from reported curr…

…ent state
Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @chamikaramj

Run Java PostCommit

LGTM. Thanks.


Python classes in numba cuda?

I am working on a project with numba cuda. It is convenience to write a cuda function in python. I am wondering if numba supports python class in the cuda kernel. I appreciate if anyone has ideas about it.

We do not have support for jitclasses on the GPU, but this is something we will think about when we update jitclasses.

Thanks @seibert. Yeah, it would be great if jitclasses is supported on the GPU.

Has it been included? I have required this feature at multiple places, wanted to check on updates

@SundarRamanP2000 thank you for asking, but jitclasses have not become available to GPU based codes.

Thanks for the prompt reply. Any clue on when it will be made available/supported on GPUs if it's planned already?

@SundarRamanP2000 TTBOMK this work has not been selected and scheduled as of yet.

And for reference, a workaround to using the __init__ and self constructs of a Python class is using environment variables. For example:
Define:
import os
from importlib import reload
os.environ["USE_64"] = "0"
from numba.<module> import <moduleA>
reload(numba.<module>.<moduleA>.)

Load:
import os
USE_64 = bool(os.environ.get("USE_64", "0"))

The reload was important for me when I wasn't restarting the Python kernel every time (otherwise it was only using the environment variable the first time it was set) ([source](source: https://stackoverflow.com/a/1254379/13697228)). This can also be pretty important whenever using cuda.local.array which generally depends on having a non-constant shape variable defined at the top-level to retain performance and be error-free.


Call of the Wild and Tabletop Tweaks

Greetings, @Vek17!
Thankee for making and publishing your Tabletop Tweaks mod!
Pathfinder: Kingmaker had an extensive mod called Call of the Wild which, as of this writing, hasn't been ported to Wrath of the Righteous.
Call of the Wild's GitHub is here.  Talk with its author (Holic) about porting that to Wrath of the Righteous.
If you still seek further material to include in your WotR mods, consider my suggestions to Holic for his mods.  He included some material I mentioned in this document already.  (Some of my favorite content to be included that hasn't already to my knowledge is the Razmiran Priest Sorcerer archetype, Planar Binding spell series, the Gate spell, a RAW implementation of Animate Dead, the Infernal Healing spell series, Teleport, Telekinesis, and Craft Construct.)
Thankee again!

If TT can make a great combination and improvement on the base of COTW, we will get a wonderful overhaul for base game.

@Vek17
To clarify, Kingmaker has plenty of NexusMods, meaning WotR can be made that much better by porting over their content or/and remaking it!


Incorrect device class

Entity sensor._previous_presence_end (<class 'custom_components.eight_sleep.sensor.EightUserSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/lukas-clarke/eight_sleep/issues
Entity sensor._next_alarm (<class 'custom_components.eight_sleep.sensor.EightUserSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/lukas-clarke/eight_sleep/issues
Entity sensor._previous_presence_start (<class 'custom_components.eight_sleep.sensor.EightUserSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/lukas-clarke/eight_sleep/issues
Entity sensor._previous_presence_end (<class 'custom_components.eight_sleep.sensor.EightUserSensor'>) is using state class 'measurement' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/lukas-clarke/eight_sleep/issues
Entity sensor.eight_sleep_last_prime (<class 'custom_components.eight_sleep.sensor.EightRoomSensor'>) is using state class 'timestamp' which is impossible considering device class ('timestamp') it is using; expected None; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/lukas-clarke/eight_sleep/issues

Issue fixed in latest release

sensor._next_alarm is still having issues in the latest version.
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 668, in state
numerical_value = float(value)  # type:ignore[arg-type]
^^^^^^^^^^^^
TypeError: float() argument must be a string or a real number, not 'datetime.datetime'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 580, in _async_add_entities
await coro
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 890, in _async_add_entity
await entity.add_to_platform_finish()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1334, in add_to_platform_finish
self.async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 998, in async_write_ha_state
self._async_write_ha_state()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1119, in _async_write_ha_state
state, attr, capabilities, shadowed_attr = self.__async_calculate_state()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1056, in __async_calculate_state
state = self._stringify_state(available)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1004, in _stringify_state
if (state := self.state) is None:
^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 670, in state
raise ValueError(
ValueError: Sensor sensor._next_alarm has device class 'None', state class 'measurement' unit 'None' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: '2024-04-22 07:00:00-05:00' (<class 'datetime.datetime'>)

@gkwok1, thanks for the catch. Just released a new release with hotfix for this

Updated and it's working now. Thank you for the hot fix.


Flag screen has black bars

To reproduce

Login to the app.
Go to Explore > Flag.
Observe the warning message.
Tap OK, Thank you..

Current behavior
Flag screen has black bars at the top and bottom (see screenshot).
Expected behavior
Flag screen is expected to be consistent with other screens.
Screenshots

Platform & App Version

iOS (likely both)
2.7.0

✅ Test Case 1

Login to the app.
Go to Explore > Flag.
Observe the warning message.
Tap OK, Thank you..
Observe Flag screen is consistent with other screens.


Add option to override default commit limit

See issue #4 this is just an option to override the default so the user can go bigger or smaller if necessary.

#7 Fixes this


feat: optional get raw headers as string

Purpose
Most libraries expect raw headers to be a string instead of an array  so I added an optional argument which will return the raw headers as a string rather than a string[].
Changes
Added an optional argument to the headers.raw() function to return the header values as a string in case this is set to `true.
Additional information
I could also create a second function like: headers.rawAsString() instead of adding an argument to the existing function.

[ ] I updated readme
[x] I added unit test(s)

Doesn't fix but is related to #783

ideally ppl should just stop depending on raw headers all together.
the hope is for ppl to just stop depending node-fetch all together and use built in fetch when it's available.
The reason ppl wanted to have raw in the first place was cuz the fetch spec decided that they should normalize the headers to be joined by , if one header is appended more than once.
some ppl where not happy about this cuz it made reading set-cookies hard that could include , in the value.
so ppl requested the raw and we implemented it...
now there is a new spec that mention iterating over headers that dose not combine the set-cookies but instead yields the everything.
ppl should really be using [...response.headers] or Object.fromEntires(response.headers) or even Headers.prototype.getSetCookie
that is what every other environment have agree upon of how it should work.
it essentially match our raw method.
I think that out raw method should be deprecated and ppl should stop using it and strive more towards cross compatible solutions with other env / fetch implementations.
so i'm generally -1 on this.

there are some new Header methods / spec things we need to fix...

Okay, I'm using Object.fromEntires(response.headers) now but I thought that it would be useful to other people too who get into the same situation.
Does this mean I should just close this PR?

i can close it for you.
if you like you could make a suggestion in the readme that the best way to access the headers would be to either use:
[...response.headers] or Object.fromEntires(response.headers) instead of using the legacy/non-standard raw method
and perhaps maybe even put a deprecation warning on using the raw option.
i did work on a more spec'ed Header classed here https://www.npmjs.com/package/fetch-headers the idea was for node-fetch to adapt it and let headers live on a separate place. as it has very little to do with fetch/request/response and is mostly isolated from everything else. then node-fetch would extend it to include the raw option (just for backwards comp. reasons)
if you feel like you are willing to bring in fetch-headers into node-fetch and replace our own than that would be appreciated as well.
fetch-headers runs it own test against WPT so some test in node-fetch could be removed.
the missing thing is getSetCookies


nixos/pulseaudio: don't create config file or enable avahi when pulse…

… is disabled
Description of changes
Currently if the configured pulseaudio packages has zerconf capabilities, the avahi service is turned on even when pulseaudio is disabled. This is some spooky action at a distance which we normally do not have when a service is not enabled.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I don't really know much about the Pulseaudio side of things, you want @lovek323.

does pipewire in any way rely on this config?

I've been using this on a pipwire machine with plasma5 for a while and didn't notice anything different.
If pipewire was using this file it was definitely unintended as it enforces turning of pulseaudio.
The extraConfig might have been read but I would classify this as unintended side effects.

With this change it would make sense to remove the systemWide and nonSystemWide variables set at the top

good catch, fixed that


New constrain / layout algorithm.

Problem:

Label widgets with text folding have multiple minimum-2D extents. The minimum-height of a label becomes non-linearly larger with smaller minimum-width.
The toolbar will have multiple lines of tool-widgets the number of lines change depending on how many tools can be layed out on each line.

What to do?

On widget_constraints replace minimum/preferred with a list of minimums. Leave maximum as-is.

During layout select one of the minimum based on the main-axis of the container.

Add decimal-line as well as base-line.

What heuristic to use to determine how many different text-foldings are done for each text.

Make a new 2D grid-layout and flex-layout algorithm which minimizes the number of possible constraints.

add generator<extent2> get_minimums() for each widget. To reduce number of allocations.

Consider using flex layout.

I looked at flexbox and cassoway, neither handles non-linear relation between the width and height. It needs a new algorithm that solves layout in 2D.
However we need a flexbox-like container for the new toolbar. But it needs to be more advanced to actually handle user widgets that have multiple minimum sizes.


update README.md

Open-Source is added to the readme.md

Fixes Issue

Changes proposed

Screenshots

Note to reviewers

@siddhant-khisty It has been more than three weeks since this request was submitted, kindly review it.


custom-select menu arrows missing in Firefox on v4-alpha5

Since updating to Bootstrap v4-alpha-5, I've noticed that the little up-down arrows on the select.custom-select menus have disappeared in Firefox.  IE, Edge, and Chrome still appear to work.
Info:
Windows 10
Firefox 49.0.2
JSFiddle: https://jsfiddle.net/hy74z6gh/
This problem is also visible in the Bootstrap alpha documentation page: http://v4-alpha.getbootstrap.com/components/forms/#select-menu

Duplicate of https://github.com/twbs/bootstrap/issues/20956


[Console] Facebook IdP outbound provisioning connector details edit page fields are not visible

Describe the issue:
Outbound provisioning connectors details page fields are not visible for any of the connectors.
And also OutBound should correct as Outbound

How to reproduce:

Log in to the Console and click on Develop tab
Click on "Identity Providers"
Click on "New Identity Provider" and select "Facebook"
Provide the required details and create an IdP
Click on Update icon in the created IdP
Go to "Outbound Provisioning" tab and click on "New connector"

Expected behavior:
Required connector detail fields should display.
Environment information

Product Version: 5.12.0-M1
OS: Mac
Database: MySQL 5.7
Browser: Safari - 14v

This issue will be closed as it is not reproducible in the product version mentioned.


Doesn't render layout on mentioned breakpoint values

I used the default responsive HOC to render a responsive layout. My breakpoints are 1200, 996, 768 for lg, md & sm. However, while simple testing, I found out the UI will not change on specified values. Rather it goes off the mark like 50-100px at each breakpoint stop and then renders new layout.
For example, a 'md' screen breakpoint should change layout at 996/997px, but not on 1060px or 1020px. Why does it happen like this?

[x] Bug
[ ] Feature Request
[ ] Question

Here is the WebpackBin Template for the corresponding bug.
http://www.webpackbin.com/V1iIRintG
Open developer tools console and notice the log messages that prints the breakpoints sizes.
Please advise.

I can't reproduce it so I'll close it for now


Please confirm the group name

Instead of "Update channel: Choose Semi-Annual Channel for the installation package for the pilot group"
should say "Update channel: Choose Semi-Annual Channel for the installation package for the BROAD group"

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

ID: e56455cc-de1d-7daa-bae1-8a344625bc71
Version Independent ID: 8bafdb99-1562-bc9d-c27b-596250dee4e2
Content: Deploy Office 365 ProPlus from the cloud
Content Source: DeployOffice/deploy-office-365-proplus-from-the-cloud.md
Service: o365-proplus-itpro
GitHub Login: @jwhit-MSFT
Microsoft Alias: jwhit

Thanks for catching that--I just updated it. Should be live soon. We love getting feedback through these discussions, but you're also welcome to submit these changes directly as a pull request, if you want to next time--that'll get you listed as a contributor on the article :-)

Thanks for catching that--I just updated it. Should be live soon. We love getting feedback through these discussions, but you're also welcome to submit these changes directly as a pull request, if you want to next time--that'll get you listed as a contributor on the article :-)

Great, didn’t know that, will do next time. :thumbs:
On 13 Feb 2019, at 18:56, J Whitmarsh <notifications<EMAIL_ADDRESS>wrote:
Thanks for catching that--I just updated it. Should be live soon. We love getting feedback through these discussions, but you're also welcome to submit these changes directly as a pull request, if you want to next time--that'll get you listed as a contributor on the article :-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/OfficeDocs-DeployOffice/issues/275#issuecomment-463322201, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIjqqH5Fni125TdK_q3xpRFFszVxPjRdks5vNF_4gaJpZM4a2kdA.

Just to had that in step 3 you are saving the Broad Group .xml file as config-pilot-SAC.xml but in point 5 you mention it as \Server\Share\O365\config-broad-SAC.xml.


Update stacklevel and add warning for get_output_shape_for

Added stacklevel=2 in a few places, stacklevel=3 for preprocessor functions.
Added a warning to Layer.compute_output_shape: if a class defines get_output_shape_for but is still using the default implementation of compute_output_shape from Layer, it prints a warning.
This script tests that the warnings all point to the correct lines in the test file (if the stacklevel is set correctly).
This probably isn't everything. The get_output_shape_for warning should save some heartache. Does anyone know other hot-spots that need extra warnings?
from keras.models import Model
from keras.layers import Dense, Input, merge, Embedding, Layer, Merge
from keras.regularizers import L1L2
import numpy as np

n=100
_x = np.random.random((n, 10))
_y = np.sum(_x, axis=-1, keepdims=True)

x = Input((_x.shape[1],))
y = Dense(_y.shape[1], W_regularizer=L1L2(1e-6,1e-6))(x)
m = Model(input=[x], output=[y])
m.compile("adam","mean_squared_error")
def gen():
    while True:
        yield _x, _y
m.fit(_x, _y, nb_epoch=5, verbose=0)
m.fit_generator(generator=gen(), samples_per_epoch=32, nb_epoch=5, verbose=0)

embedding = Embedding(50, 100, dropout=0.5)

class L1(Layer):
    def get_output_shape_for(self, s):
        return s
class L2(Layer):
    def dummy(self):
        pass

l1=L1()
l2=L2()
l1.compute_output_shape((10,))
l2.compute_output_shape((10,))

z = Input((_x.shape[1],))
merge_layer = Merge(mode='concat')
merged = merge([x, z], mode="concat")

D:/Projects/keras/keras/legacy_warning_test.py:11: UserWarning: Update your Dense call to the Keras 2 API: Dense(1, kernel_regularizer=<keras.reg...)
y = Dense(_y.shape[1], W_regularizer=L1L2(1e-6,1e-6))(x)
D:/Projects/keras/keras/legacy_warning_test.py:12: UserWarning: Update your Model call to the Keras 2 API: Model(outputs=[Elemwise{..., inputs=[/input_1])
m = Model(input=[x], output=[y])
D:/Projects/keras/keras/legacy_warning_test.py:17: UserWarning: The nb_epoch argument in fit has been renamed epochs.
m.fit(_x, _y, nb_epoch=5, verbose=0)
D:/Projects/keras/keras/legacy_warning_test.py:18: UserWarning: The semantics of the Keras 2 argument  steps_per_epoch is not the same as the Keras 1 argument samples_per_epoch. steps_per_epoch is the number of batches to draw from the generator at each epoch. Update your method calls accordingly.
m.fit_generator(generator=gen(), samples_per_epoch=32, nb_epoch=5, verbose=0)
D:/Projects/keras/keras/legacy_warning_test.py:18: UserWarning: Update your fit_generator call to the Keras 2 API: fit_generator(verbose=0, generator=<generator..., steps_per_epoch=32, epochs=5)
m.fit_generator(generator=gen(), samples_per_epoch=32, nb_epoch=5, verbose=0)
D:/Projects/keras/keras/legacy_warning_test.py:20: UserWarning: The dropout argument is no longer support in Embedding. You can apply a keras.layers.SpatialDropout1D layer right after the Embedding layer to get the same behavior.
embedding = Embedding(50, 100, dropout=0.5)
D:/Projects/keras/keras/legacy_warning_test.py:31: UserWarning: Class __main__.L1 defines get_output_shape_for but does not override compute_output_shape. If this is a Keras 1 layer, please implement compute_output_shape to support Keras 2.
l1.compute_output_shape((10,))
D:/Projects/keras/keras/legacy_warning_test.py:35: UserWarning: The Merge layer is deprecated and will be removed after 08/2017. Use instead layers from keras.layers.merge, e.g. add, concatenate, etc.
merge_layer = Merge(mode='concat')
D:/Projects/keras/keras/legacy_warning_test.py:36: UserWarning: The merge function is deprecated and will be removed after 08/2017. Use instead layers from keras.layers.merge, e.g. sum, concatenate, etc.
merged = merge([x, z], mode="concat")

Cheers!

LGTM, thanks


Improved support for Amazon Workspaces Windows

For my job, I have to use Amazon Workspaces Windows to develop Windows software. However, I prefer the command line and TUIs so I want to use Micro as my editor, which is based on tcell.
This is a version 1890 of windows server datacenter 2019. It is windows 10 compatible, but while it can support some ANSI escape sequences in cmd.exe shell, it has no support for the new virtual PTY Win32 console API. This means the new Terminal Application doesn't work yet. More importantly WSL also doesn't work.
Seeing that I don't have much choice, I tried to use micro and the test of this library in MinTTY, and while the output sort of works, the input is limited. Mouse doesn't work without winpty, and even with winpty many key combinations don't work correctly. I understand that using this library with MinTTY, with cygwin or msys2 is less than ideal, especially because they emulate Posix on a source code level. I also tried ConEmu but that also has input issues with the mouse and some keyboard combinations not working correctly. And the problem with using cmd.exe is that the font support is rather poor.
Therefore, it would be very useful for me and others who are stuck on this strange version of Windows that Amazon provides for remote corporate use if tcell could work better somehow with MinTTY.   It might be possible to use cgo in this library on windows, and call the termios C functions of msys2, in order to create a new screen type, to get it to work with MinTTY. Or, maybe we can figure out what it is that winpty is doing and do that ourselves?
Thanks for your consideration.

Thanks for the advice. I'll ask my employer once if I can somehow upgrade to a Win11 image but it might not be that easy.
Actually, at least when it comes to Go, mintty and mingw are troublesome because they are source level POSIX ports only,  so , in stead I run conhhost with an elvish shell in it. Actually, at least on the input level, conhost is quite good in tcell. The output is less good, due to conhost font and style limitations, and a few small tcell bugs and unimplemented features, but all in all it's easier to use Micro, etc when the mouse input works well. So for now I'm using conhost to do my windows software development. If I find any bugs that I can fix I'll supply some PRs for them for people who are in my situation.
I will probably also read the source code of winpty and see if it is something that can be done in Go or not.

I just took that quick look at winpty, and I learned that it is more of a hack: it uses a hidden win32 window with a hidden Windows Console to catch the user input and then redirects that to the mingw-ish terminal environment. It's not something that we could do reasonably in Go, actually, even with C it's iffy.
But actually with Go it's probably not even needed. Many go tools work well on Windows because the Go team has made the windows port directly on top of the win32 api functions in the common Windows DLLs and didn't rely on any C libraries to wrap that. You don't even need a C compiler or CGO to develop Windows software in Go, which is great. I'll probably install more go tools and use them in stead of mingw in the conhost. :)

That's correct, writing Windows code in Go is not too bad.
The winpty thing is awful , and I kind of remember it.  I think the whole mingw/mintty thing is an unfortunate catastrophe, and I cannot imagine why anyone would use it given modern systems with WSL.  Or just run a regular VM or Docker container.


Are "sections" the way to do conditional rendering?

Thank you for Mustache. It's been a great help but as the scope of my project grew, so did my requirements. I'm now looking to do some easy work without React where I need to have conditional rendering.
Here's how my data looks exactly, coming back from the server:
attachment: {
    title: Attachment,
    slug: attachment,
    state: {
        installed: true,
        active: false
    }
},
post: {
    title: Post,
    slug: post,
    state: {
        installed: true,
        active: true
    }
},

For each one of these items, I render a <li> containing the details but depending on its [key].state.installed/active, I might choose to render it different or even show some buttons. For example, if an item comes back with the active: false, installed: true state, I will have to hide the install button and instead show the activate one.
How can I tell Mustache that I want it to do this?

Yes, sections and inverted sections is the way to go for both:

iterating through an array
conditionals

Have you read through our docs for sections and inverted sections or given them a shot?

Closing this for now due to lack of response from the issue author. Don't hesitate to re-open if more explanation than what could be found in the mentioned docs would be helpful.


Minor fix to settings behavior

Main change is making the settings no longer depend on the pause modal in order to pause game activity. In addition:
-Made rotationCmp a global rather than local variable, and renamed it to coinRotationValue to make it clearer.
-Changed variable and png file names so that the coin rotation images would be called in a more logical order (actual animation unchanged).

@Germlord Great, thanks!


getElementById

drawPlanetPhase(document.getElementById('container'), 0.15, true);

This doesn't seem to work. Only document.body. Any idea why?

That code works ok for me, have you tried debugging to see what the problem is? Do you get any errors?

I attempted to debug it but every value I sent to console.log didn't return anything useful. I am not sure why it wasn't working. It's okay I built and alternative solution.

I attempted to debug it but every value I sent to console.log didn't return anything useful. I am not sure why it wasn't working. It's okay I built and alternative solution. However I may test the DIV issue a little more, though I recommend you check it out it as well.

I attempted to debug it but every value I sent to console.log didn't return anything useful. I am not sure why it wasn't working. It's okay I built and alternative solution. However I may test the DIV issue a little more, though I recommend you check it out it as well.


Direct users to spreadsheet when they want to track their total microCOVIDs over time

We have gotten a lot of user feedback about wanting to track their activity over the last 10 days on the calculator.
The spreadsheet is the (current) solution to this use case. We might want to add some clear place on the calculator to direct people to the spreadsheet.
My top-of-mind idea: In the explanation section (after the points display), add a button/link that basically says Want to track your activities and see your budget total for the week? Click here to use the spreadsheet →

Would you consider a feature that allowed you to save a scenarios (or the final number of microcovids) to a list like that to track total microcovids over time? I know the spreadsheet works but it'd be nice to have it on the site for convenience

@jpnelson That's one of our most frequently requested features. At this time, we're directing everyone to use the spreadsheet rather than considering adding it to the website.


Record reaction count for a file

Only a simple total count of all reactions.

You must know the exact reaction you want to list user details for, which is the way to get a total count per reaction... bit inefficient, but thats okay, might work.
ENV setup a list of common emoji to use, but default to, fire, heart
That would be 2 additional API requests per message.


subset lb: support matching any value in list metadata

Currently the subset lb treats the value of each metadata key as an opaque Value, comparing the comparing the hash of the value specified in the routing metadata with the hash of the corresponding value in the host metadata.
It would be useful to have the subset lb treat a ListValue metadata on the host as providing any of the list values as a value to the metadata key:
Given a host with metadata labels: [label1, label2] it would match both labels: label1 and labels: label2 criteria.
Today this is representable by adding label1: true, label2: true and matching on the individual keys, but this means that the cluster subsets need to be updated whenever a label is added, which requires rebuilding the cluster.
Implementing this should hopefully be fairly easy: if this is enabled for a given subset key and the host has a ListValue for this key, add a subset value for each element in the list. Some care will have to be taken to ensure that things work correctly when a single host contains multiple values for the same metadata key, as I believe the current invariants ensure that there is only a single value per key for each host.

fwiw this as asked about early this year: https://groups.google.com/d/topic/envoy-users/WMt9Ob0NKkg/discussion


Excluding users from highlighting you do not get saved in settings

Add a user

restart

same issue for the Highlights->Users tab


Remove border & background from invisible disabled buttons

Removes the background and border from disabled invisible Button and IconButton by updating the shared ButtonBase CSS styles. It looks like ButtonBase is fully shipped to CSS Modules so we don't have to update any styled-system styles for this.

Closes https://github.com/primer/react/issues/5421

Before:

After (video to show hover/active styling):
https://github.com/user-attachments/assets/fcd28aa1-bd81-4bc0-a0cb-fed90dd4a466
Changelog

New

Changed

Removes border & background from disabled invisible buttons

Removed

Rollout strategy

[x] Patch release
[ ] Minor release
[ ] Major release; if selected, include a written rollout or migration plan
[ ] None; if selected, include a brief description as to why

Testing & Reviewing

Merge checklist

[ ] Added/updated tests
[ ] Added/updated documentation
[ ] Added/updated previews (Storybook)
[ ] Changes are SSR compatible
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge
[ ] (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

Closing this in favor of https://github.com/primer/react/pull/5440


Support for Non-Square Images

I have trying to use the implementation for non-square Images and getting error : RuntimeError: Sizes of tensors must match except in dimension 3. Got 135 and 136 (The offending index is 0).
I had set:
input_size = (1920,1080)
random_size = 0
mscale = 0

1080 is not multiple of 32, plz pad to 1088 to solve this issue.

1080 is not a multiple of 32, plz pad to 1088 to solve this issue.

Thank you for your reply. Do I have to manually change my input (adding the pad) or will the script handles it automatically?
Is there as specific reason for 32?


CSS-Loader documentation update

CSS-LOADER documentation update
The default value for esModule given in the grid is false which should be changed to true in options section of css-loader
PFB the screenshot:

Link: https://webpack.js.org/loaders/css-loader/
[ ] I am willing to work on this issue and submit a pull request.

That option is not released yet, we can update the docs once released

Yes, ETA is the current week

Fixed