Why gradients don't seem to pass through Embedding ?

I'm not sure if the gradients are passing through the embedding layer properly:

import tensorflow as tf

import keras.backend as K
from keras.models import Sequential, Model
from keras.layers import Dense, concatenate, Input, Conv2D, Embedding, \
                         Bidirectional, LSTM, Lambda, TimeDistributed, \
                         RepeatVector, Activation

vocabSize = 3
embDim = 5
rnn = LSTM(vocabSize, return_sequences=True)
embedding = Embedding(vocabSize, embDim)

input_questions = Input(shape=(None,), name='question')
embed = embedding(input_questions)
rnn_output = rnn(embed)
softmax = TimeDistributed(Activation('softmax'))(rnn_output)

# these gradients don't work, FIXME!
grad = tf.gradients(xs=input_questions, ys=rnn_output)
print('grad (xs=input_questions, ys=rnn_output):   ', grad)
grad = tf.gradients(xs=input_questions, ys=embed)
print('grad (xs=input_questions, ys=embed):        ', grad)
grad = tf.gradients(xs=input_questions, ys=softmax)
print('grad (xs=input_questions, ys=softmax):      ', grad)
grad = tf.gradients(xs=embed, ys=softmax)
print('grad (xs=embed, ys=softmax):                ', grad)

model = Model(inputs=input_questions, outputs=softmax)

The output of this code is
grad (xs=input_questions, ys=rnn_output):    [None]
grad (xs=input_questions, ys=embed):         [None]
grad (xs=input_questions, ys=softmax):       [None]
grad (xs=embed, ys=softmax):                 [<tf.Tensor 'gradients_10/lstm_3/transpose_grad/transpose:0' shape=(?, ?, 5) dtype=float32>]

any news @gabrieldemarmiesse ??

The embedding layer is implemented as K.gather which is not differentiable, so there is no gradient.

Thanks @Dref360 for looking into this. Closing the issue as this is the expected behaviour of the embedding layer.

The embedding layer is implemented as K.gather which is not differentiable, so there is no gradient.

In the build method of the layer a new trainable weight is added by add_weight with trainable=True by default:
def build(self, input_shape):
        self.embeddings = self.add_weight(
            shape=(self.input_dim, self.output_dim),
            initializer=self.embeddings_initializer,
            name='embeddings',
            regularizer=self.embeddings_regularizer,
            constraint=self.embeddings_constraint,
            dtype=self.dtype)
        self.built = True

Doesn't this make the weights of Embedding layer trainable?


refactor(ui): Use JSON search params for table sorting state

To avoid having to manually format search params for table formatting, use
TanStack Router's ability to use JSON values in search params [1]. This
makes the logic easier to reason with, especially when implementing sorting
by multiple columns later.
While at it, align the sorting state used in search params with the data
model required by TanStack Table.
Signed-off-by: Mikko Murto<EMAIL_ADDRESS>

Commit message (and PR description) nit: missing the reference [1].

Otherwise, LGTM, and I'll need to rebase mine then, to align with this PR after it's merged.


Upgrade terraform-provider-bigip to v1.22.2

This PR was generated via $ upgrade-provider pulumi/pulumi-f5bigip.

Upgrading terraform-provider-bigip from 1.22.1  to 1.22.2.
Fixes #504

Waiting on https://github.com/pulumi/pulumi-f5bigip/pull/513 to merge.


Leaderhub website setup

Added services
Added scheduling (book now)
Next: FAQs

Added FAQs
Added Office hours
Added social proof
Next: About Us, Contact Us, ToS, Privacy

Added About Us and Contact Us
Added Free consultation scheduling page
Next: Add service pages (mentorship and interview prep)

Added Mentoring page
Next: Add Interview page

Added Interview pages
Next: Courses and blogs


Fixing unique titles and level 2 headings in topics for US 1889327

Fixes #Issue_Number (if available)

Hi, Liz, Number of files updated: 10

starting fresh with a new re-forked repo

closed the PR


Can Gitea support Azure file storage?

Feature Description
I see https://github.com/go-gitea/gitea/issues/22527 and this is asking for Azure file storage support. I'm trying to deploy Gitea on ARO with Azure file storage, according to https://help.thorntech.com/docs/next/sftp-gateway-azure/azure-file-storage-mount/#caveats-and-limitations , with Azure file storage, it is impossible to do chmod.
This is my app.ini and I have PVC mount to /data:
APP_NAME = Gitea: Git with a cup of tea
RUN_MODE = prod
RUN_USER = git

[repository]
ROOT = /data/git/repositories
ENABLE_PUSH_CREATE_USER = true
ENABLE_PUSH_CREATE_ORG  = true
DEFAULT_PRIVATE         = public
FORCE_PRIVATE           = false

[repository.local]
LOCAL_COPY_PATH = /data/gitea/tmp/local-repo

[repository.upload]
TEMP_PATH = /data/gitea/uploads

[server]
APP_DATA_PATH    = /data/gitea
DOMAIN           = {{DOMAIN_NAME}}
SSH_DOMAIN       = localhost
HTTP_PORT        = 3000
ROOT_URL         = %(PROTOCOL)s://%(DOMAIN)s
DISABLE_SSH      = false
SSH_PORT         = 22
SSH_LISTEN_PORT  = 22
LFS_START_SERVER = false
PROTOCOL         = https
CERT_FILE        = /data/gitea/conf/tls.crt
KEY_FILE         = /data/gitea/conf/tls.key

[lfs]
PATH = /data/git/lfs

[database]
PATH    = /data/gitea/gitea.db
DB_TYPE = sqlite3
HOST    = localhost:3306
NAME    = gitea
USER    = root
PASSWD  =

[indexer]
ISSUE_INDEXER_PATH = /data/gitea/indexers/issues.bleve

[session]
PROVIDER_CONFIG = /data/gitea/sessions
PROVIDER        = file

[picture]
AVATAR_UPLOAD_PATH            = /data/gitea/avatars
REPOSITORY_AVATAR_UPLOAD_PATH = /data/gitea/repo-avatars
DISABLE_GRAVATAR              = false
ENABLE_FEDERATED_AVATAR       = true

[attachment]
PATH = /data/gitea/attachments

[log]
ROOT_PATH = /data/gitea/log
MODE      = file, console

[security]
INSTALL_LOCK   = true
SECRET_KEY     =

[service]
DISABLE_REGISTRATION              = false
REQUIRE_SIGNIN_VIEW               = false
REGISTER_EMAIL_CONFIRM            = false
ENABLE_NOTIFY_MAIL                = false
ALLOW_ONLY_EXTERNAL_REGISTRATION  = false
ENABLE_CAPTCHA                    = false
DEFAULT_KEEP_EMAIL_PRIVATE        = false
DEFAULT_ALLOW_CREATE_ORGANIZATION = true
DEFAULT_ENABLE_TIMETRACKING       = true
NO_REPLY_ADDRESS                  = noreply.localhost

[mailer]
ENABLED = false

[openid]
ENABLE_OPENID_SIGNIN = true
ENABLE_OPENID_SIGNUP = true

The first issue I met is Gitea pod can't be started with error:
Server listening on :: port 22.
Server listening on <IP_ADDRESS> port 22.
2024/01/16 02:42:26 cmd/web.go:105:runWeb() [I] Starting Gitea on PID: 15
2024/01/16 02:42:26 cmd/web.go:159:runWeb() [I] Global init
2024/01/16 02:42:27 routers/init.go:70:mustInitCtx() [F] code.gitea.io/gitea/modules/git.InitFull(ctx) failed: failed to set git global config user.email, err: exit status 4 - error: chmod on /data/gitea/home/.gitconfig.lock failed: Operation not permitted
	 - error: chmod on /data/gitea/home/.gitconfig.lock failed: Operation not permitted

Received signal 15; terminating.

After some investigate I'm able to fix it by adding below to app.ini because I mount /data/git as emptyDir so change permission is fine in this folder:
[git]
HOME_PATH=/data/git

But then I meet another permission issue when trying to login Gitea from UI:
2024/01/16 03:45:18 ...ers/web/auth/auth.go:312:handleSignInFull() [E] [65a5fbce] RegenerateSession: regenerate session: chtimes /data/gitea/sessions/7/8/78238946019cfcae: operation not permitted
2024/01/16 03:45:18 [65a5fbce] router: completed POST /user/login for <IP_ADDRESS>:55512, 500 Internal Server Error in 260.8ms @ auth/auth.go:170(auth.SignInPost)

And error when trying to create an organization:
2024/01/16 03:48:03 ...rs/api/v1/org/org.go:272:Create() [E] [65a5fc73] CreateOrganization: generate random avatar: Failed to create dir 43aa32a241c84f3e6df8e5651ed81e76: chmod /data/gitea/avatars/43aa32a241c84f3e6df8e5651ed81e76: operation not permitted
2024/01/16 03:48:03 [65a5fc73] router: completed POST /api/v1/orgs?token=b45f8e88e9e77742a7ce89523fe094cabf274290 for <IP_ADDRESS>:47868, 500 Internal Server Error in 245.4ms @ org/org.go:223(org.Create)

So unless we remove the PVC mount, it is impossible to use Azure file storage? Does Gitea support Azure file storage?
Screenshots
No response

Looks like your file system is readonly.

@lunny Yes it is readonly file system according to our security requirement, below is the deployment yaml file:
kind: Deployment
apiVersion: apps/v1
metadata:
  name: icp4adeploy-gitea-deploy
  labels:
    app: icp4adeploy-gitea-deploy
spec:
  replicas: 1
  selector:
    matchLabels:
      app: icp4adeploy-gitea-deploy
  template:
    metadata:
      creationTimestamp: null
      labels:
        app: icp4adeploy-gitea-deploy
    spec:
      restartPolicy: Always
      initContainers:
        - resources: {}
          terminationMessagePath: /dev/termination-log
          name: icp4adeploy-gitea-prereqs
          command:
            - sh
            - '-cx'
            - |
              set -o errexit
              set -o pipefail

              mkdir -p /data/gitea/conf
              mkdir -p /data/gitea/log
              rm -rf /data/git/.gitconfig.lock

              cp /opt/ansible/share/gitea_* /data/gitea/conf/
              cp /rootca/tls.crt /data/gitea/conf/root_ca_crt.crt
              cp /tlssecret/* /data/gitea/conf/
              chown -R git:git /data/gitea
              mv /data/gitea/conf/gitea_app.ini /data/gitea/conf/app.ini
          env:
            - name: USER_UID
              value: '1000'
            - name: USER_GID
              value: '1000'
          securityContext:
            readOnlyRootFilesystem: true
          imagePullPolicy: IfNotPresent
          volumeMounts:
            - name: gitea-data
              mountPath: /data
            - name: operator-shared-folder
              mountPath: /opt/ansible/share
            - name: tlssecret
              mountPath: /tlssecret
            - name: rootcasecret
              mountPath: /rootca
          terminationMessagePolicy: File
          image: >-
            cp.icr.io/cp/cp4a/demo/gitea@sha256:30540b7b97dd483f69a1a51d0bf0d5b8c0262a0d976658fe21469563aa2c007b
        - resources: {}
          terminationMessagePath: /dev/termination-log
          name: folder-prepare-container
          command:
            - /bin/bash
            - '-ecx'
            - >
              rm -rf /s6-folder/* && cp -rp /etc/s6/* /s6-folder && rm -rf
              /etc-ssh-folder/* && cp -rp /etc/ssh/* /etc-ssh-folder && rm -rf
              /app-gitea-folder/* && cp -rp /app/gitea/* /app-gitea-folder && rm
              -rf /run-folder/* && cp -rp /run/* /run-folder
          securityContext:
            readOnlyRootFilesystem: true
          imagePullPolicy: IfNotPresent
          volumeMounts:
            - name: s6-folder-pvc
              mountPath: /s6-folder
            - name: etc-ssh-folder-pvc
              mountPath: /etc-ssh-folder
            - name: app-gitea-folder-pvc
              mountPath: /app-gitea-folder
            - name: run-folder-pvc
              mountPath: /run-folder
          terminationMessagePolicy: File
          image: >-
            cp.icr.io/cp/cp4a/demo/gitea@sha256:30540b7b97dd483f69a1a51d0bf0d5b8c0262a0d976658fe21469563aa2c007b
      serviceAccountName: ibm-cp4ba-anyuid
      schedulerName: default-scheduler
      affinity:
        nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - amd64
                      - s390x
                      - ppc64le
          preferredDuringSchedulingIgnoredDuringExecution:
            - weight: 3
              preference:
                matchExpressions:
                  - key: kubernetes.io/arch
                    operator: In
                    values:
                      - amd64
                      - s390x
                      - ppc64le
      terminationGracePeriodSeconds: 30
      securityContext: {}
      containers:
        - resources:
            limits:
              cpu: 500m
              memory: 512Mi
            requests:
              cpu: 100m
              memory: 256Mi
          readinessProbe:
            httpGet:
              path: /
              port: 3000
              scheme: HTTPS
            initialDelaySeconds: 30
            timeoutSeconds: 5
            periodSeconds: 10
            successThreshold: 1
            failureThreshold: 3
          terminationMessagePath: /dev/termination-log
          name: icp4adeploy-gitea-deploy
          livenessProbe:
            httpGet:
              path: /
              port: 3000
              scheme: HTTPS
            initialDelaySeconds: 30
            timeoutSeconds: 5
            periodSeconds: 10
            successThreshold: 1
            failureThreshold: 3
          env:
            - name: USER_UID
              value: '1000'
            - name: USER_GID
              value: '1000'
            - name: DOMAIN
              value: gitea-demo.apps.kragon.eastus.aroapp.io
            - name: INSTALL_LOCK
              value: 'true'
          securityContext:
            readOnlyRootFilesystem: true
          ports:
            - name: https
              containerPort: 3000
              protocol: TCP
            - name: ssh
              containerPort: 22
              protocol: TCP
          imagePullPolicy: IfNotPresent
          volumeMounts:
            - name: gitea-data
              mountPath: /data
            - name: root-folder-pvc
              mountPath: /root
            - name: gitea-folder-pvc
              mountPath: /gitea
            - name: git-folder-pvc
              mountPath: /data/git
            - name: ssh-folder-pvc
              mountPath: /data/ssh
            - name: s6-folder-pvc
              mountPath: /etc/s6
            - name: etc-ssh-folder-pvc
              mountPath: /etc/ssh
            - name: app-gitea-folder-pvc
              mountPath: /app/gitea
            - name: run-folder-pvc
              mountPath: /run
          terminationMessagePolicy: File
          image: >-
            cp.icr.io/cp/cp4a/demo/gitea@sha256:30540b7b97dd483f69a1a51d0bf0d5b8c0262a0d976658fe21469563aa2c007b
      serviceAccount: ibm-cp4ba-anyuid
      volumes:
        - name: operator-shared-folder
          persistentVolumeClaim:
            claimName: operator-shared-pvc
        - name: gitea-data
          persistentVolumeClaim:
            claimName: gitea-filestore-pvc
        - name: rootcasecret
          secret:
            secretName: icp4adeploy-root-ca
            defaultMode: 420
        - name: tlssecret
          secret:
            secretName: icp4adeploy-prereq-ext-tls-secret
            defaultMode: 420
        - name: root-folder-pvc
          emptyDir: {}
        - name: gitea-folder-pvc
          emptyDir: {}
        - name: git-folder-pvc
          emptyDir: {}
        - name: ssh-folder-pvc
          emptyDir: {}
        - name: s6-folder-pvc
          emptyDir: {}
        - name: etc-ssh-folder-pvc
          emptyDir: {}
        - name: app-gitea-folder-pvc
          emptyDir: {}
        - name: run-folder-pvc
          emptyDir: {}

Could you pls let me is this a configuration issue or Gitea has limitation on supporting Azure file storage? I feel unless I remove the PVC, I can't make it work....

Gitea will not know the real file system after you mount. So I don't think this is a problem can be resolved from Gitea side. It should be a configuration problem.


Changes not being detected

Cannot detect changes because of this error :(
fatal: detected dubious ownership in repository at '/github/workspace'
To add an exception for this directory, call:
	git config --global --add safe.directory /github/workspace

add a task with run: and --add safe.directory before running the one with uses


<> are being escaped automatically to &lt and &gt

This is what I get in my logs!
Duplicate key 9900
I have manually set 	to false and still problem is present.
Reporter.setEscapeHtml(false);
Thing is in the following line the < and > are taken is &lt and &gt. What am I supposed to do?
Reporter.log("Duplicate key " + AfterSplit[0]+"");
if i set escape html to true it becomes

Duplicate key 9900

I assume the Reporter.setEscapeHtml method is intended to turn off escaping in the default TestNG HTML reporter, it's not part of ReportNG. To turn off escaping for the ReportNG reporter you need to set the system property "org.uncommons.reportng.escape-output" to false. Full list of supported properties is on the home page: http://reportng.uncommons.org.


What if user id is not integer?

In my project, I defined user ids as uuid. When I use the built-in 'doctrine' channel, I get the following error:
"An error has occurred during the notification process of message \"transaction_state_change\" for channel \"Yokai\\MessengerBundle\\Channel\\DoctrineChannel\". Exception : Doctrine\\DBAL\\DBALException - An exception occurred while executing 'INSERT INTO yokai_messenger_notification (subject, body, recorded_at, recipient_class, recipient_id, delivered_at) VALUES (?, ?, ?, ?, ?, ?)' with params [\"Transaction status change\", \"0c0bbf47-f5ba-4b3c-9aa7-8810ca97230c\\n\", \"2018-09-04 20:24:58\", \"App\\\\Entity\\\\User\", \"a1385654-fb9e-48ef-864b-9c9de4b8193f\", null]:\n\nNotice: Object of class App\\Entity\\Id\\UserUuid could not be converted to int"

How can I override the Notification entity to use uuid as the user type? (May be this issue can help?
I'm using your yokai-token-bundle and there you define user id as varchar(255) which is ok in my case.
If the only way to override bundle mappings is thru overriding an xml config, it would be great to reflect it in the documentation because I guess it's an often used case when people want to bind Notification entity to User thru relations and vice versa.

Seems that overriding xml mappings doesn't work, here another issue I've just opened https://github.com/doctrine/DoctrineBundle/issues/846

The easiest solution for me is to change the field type to a string.
Mapping overriding in doctrine is painful, I don't want to document something like this.
The last possible solution I see, is that you implement your own channel.

Yes, convert id to string just for consistency with your other bundle. You see it appears that overriding in doctrine is broken or not documented enough, let's see how the related issue resolves. I've checked the source, there's nothing wrong in built-in doctrine channel, it's type-agnostic against recpientId.

May be it's even better if messenger-bundle doesn't provide Entity at all but requires it's user to create such Notification entity (of course with known interface) by himself and configure the bundle providing the class name then?

Yes, it is. But currenly I've not enough time to prepare the bundle for this.
(I'm already thinking about the next major, with more abstraction everywhere)


Is it possible to push stream from a texturesurface instead of camera?

Is it possible to push stream from a texturesurface instead of camera?

The surfacemodeexample and texturemodeexample both failed the test in an android 10 phone.

It is possible but no by default. You need modify the library to do it.
Can you provide any logcat or info about your error? It is working for me in oneplus 7T with android 10.

Thks!
I changed the "RtspCamera2" to "RtspCamera1", and "RtmpCamera2" to "RtmpCamera1", then they both succeed.
Sometimes there is need to push stream from one texturesurface, otherwise I could only use the fullscreen stream-push. About modifying the library, I'll find some time and give it a try.


Fail detection when appended content is too big

If we still can't match the license, we use a fancy math thing called the Sørensen–Dice coefficient, which is really good at calculating the similarity between two strings. By calculating the percent changed from the known license to the license file, you can tell, e.g., that a given license is 95% similar to the MIT license, that 5% likely representing legally insignificant changes to the license text.

The issue with this strategy is that if, according to a license, you need to append notices about included/bundled libraries to a LICENSE file, then the appended notice may be too big, sometimes bigger than the actual licence, and cross the threshold.
Examples:

https://github.com/apache/spark/blob/master/LICENSE
https://github.com/gradle/gradle/blob/master/LICENSE
https://github.com/apache/zest-java/blob/develop/LICENSE.txt
https://github.com/apache/accumulo/blob/master/LICENSE
etc...

according to a license, you need to append notices about included/bundled libraries to a LICENSE file

@eskatos can you provide some examples of licenses that require the attribution be append to the license file itself?

Sure. ASF instructions to apply Apache 2 License: http://www.apache.org/dev/licensing-howto.html#permissive-deps

@mlinksva have you seen this before? Any thoughts on how best to handle this?

I don't think any license says "you need to append notices about included/bundled libraries to a LICENSE file" ... said notices could be provided in a different file.
I've seen the practice of appending subcomponent licenses to the LICENSE file but didn't know it is following an ASF instruction. Seems that instruction is not precise enough to allow for machine detection.
I could imagine licensee doing something to accommodate this convention -- maybe something like if Apache-2.0 with long text following, ignore long text if it contains string "subcomponent". Not at all sure that's a good idea.
Otherwise we can continue to not detect a license with a bunch of extra text. At least we won't get false positives.
If machine detection is important, longer term it'd be nice if Apache updated its recommendation to document subcomponent notices in a machine readable file, probably SPDX.

I could imagine licensee doing something to accommodate this convention -- maybe something like if Apache-2.0 with long text following, ignore long text if it contains string "subcomponent". Not at all sure that's a good idea.

This could work for the bunch of ASF projects and others out of the ASF that do just that.
Yes, SPDX would be nice but if/when ASF recommends it, it will take a lot of time for projects to change their license data.

@eskatos can you provide some examples of licenses that require the attribution be append to the license file itself?

@benbalter I was not referring to attribution but to bundled components notices.
About attribution, with the example LICENSE files I linked in the issue, licensee take the first bundled component attribution as the project attribution.
For example, here is the output for Apache Zest:
user@host ~/zest-java $ licensee
License file: LICENSE.txt
Attribution: Copyright 2014 jQuery Foundation and other contributors.
License: Not detected

Here's the closest licenses:

Apache Zest bundles jQuery but the attribution is wrongly detected in this case. I tried to add the Apache License boilerplate with the correct attribution in the README of that project but it didn't help. That's probably a different issue than the length of appended content though.


Select :input elements

The following fails with Failed: invalid selector: An invalid or illegal selector was specified.
it('should contain exactly 4 input elements of any kind', function() {
  expect(element.all(by.css(':input')).count()).toBe(4);
});

So...any chance of supporting an :input selector as does jQuery?
In jQuery, the :input selector is a shortcut that will also match textarea, select and button elements. This would be useful in scenarios where we want to assert anything having to do with the testing the input "class" of elements being used, including:

Count total number of input elements
Differentiate between <input type="submit" name="action" ../> vs. <button type="submit" n-me="action" .../>
Index input elements by type, for caching, etc.

I don't see this as introducing any breaking changes (i.e. non-existent).

Node Version: 4.3.1
Protractor Version: 3.1.1
Browser(s): Chrome 48.0.2564.116 m
Operating System and Version Windows 7

This sounds like a feature request, could you update your issue with the items from the issue template.
Personally I don't see a huge win over being more explicit with your selectors but maybe that's just me :smile:

Updated.

Nevermind, I figured it out:
// Equivalent to $(':input')
// Reference: https://api.jquery.com/input-selector/

var allInputs = function() {
  return element.all(by.deepCss('input,textarea,button,select'));
}

it('should contain :input elements', function() {
  expect(allInputs().count()).toBe(4);
});

Sounds like a great solution. Thanks for checking back in!


Disambiguate variable named "netmask" when meaning CIDR prefix bits

The use of the variable name netmask for a variable that actually specifies the number of bits in the cidr prefix is confusing. While adding the cidr support, I initially converted /24 to its mask form <IP_ADDRESS> and used it as the argument. It did not work, but did not error, either.

For the curious, I used the hub command to attach my feature/issue-5 branch to this pull request.  I had to make sure that your copy of the redjack/ipset repo is called origin, and then I ran
$ hub pull-request -i 5 -b develop

Rebased onto develop


[Request] Sort functionality in Pivot Table

Hi SuperSet community.
The Sort functionality in Pivot table seem to be lacking. I think this would be an interesting feature when creating pivot table with ordinal features.
An example :

Here it would be amazing to be able to sort both level 1 and level 2 of this table, as we would do in SQL.
In particular it would be great to be able to sort like this:
Level 1: sorted alphabetically
Level 2: sorted with custom SQL like: Trusted > Neutral > Low > Medium > High
What do you guys think ?

@lctdulac we have a new pivot table available soon. https://github.com/apache-superset/superset-ui/pull/1023
thanks to @kgabryje
I'm not sure we can support sorting to this extent though.

@junlincc thanks! the new pivot table looks great. I still think it would be amazing to be able to sort at least one level for ordinal data.

@junlincc
I just checked the new Pivot Table v2 viz, it's a great improvement.
About the sorting, currently it supports sorting the rows and columns based on keys or values.
In case of values, by default it considers right most column values or the last(bottom) row values, so it would be great if we can have a 'Sort By' option in Query section to decide what value to be used for sorting both rows and columns.


Do not count a number of skipped actions in progress log

Sample:
Before:
[1/2] clangsa analyzed simple1.cpp successfully.

After:
[1/1] clangsa analyzed simple1.cpp successfully.

What do you think about extending the output with the number of the skipped compile commands?
[] - Successfully analyzed
[] -   clangsa: 1
[] - Total analyzed compilation commands: 1
[] - Skipped compilation commands: 1

What do you think about extending the output with the number of the skipped compile commands?
[] - Successfully analyzed
[] -   clangsa: 1
[] - Total analyzed compilation commands: 1
[] - Skipped compilation commands: 1

Done.

Done.

Gentle ping)

Sorry for the slow reply.
Thanks for the changes!


[Feature Request]: Provide symbol options for point_data layers

Provide a clear and concise description of what you want to happen.
Currently, point_data layers in PRISM are shown as circles, with the exception of RBD's crop change data where have applied a hex_display parameter as true. When more than one point_data layer is shown, using a single symbol make is impossible to differentiate the layers if they use similar legends.
We should add the ability to choose a symbol for point_data layers and allow an icon to be included in the image folder as a source. It's also worth considering creating a few icons in a shared location that any PRISM deployment could make use of.
MapLibre symbol specification for reference: https://maplibre.org/maplibre-style-spec/layers/#symbol
Is there anything else you can add about the proposal? You might want to link to related issues here, if you haven't already.
This example from Cambodia showing Google Floods plus EWS-1294 river levels side by side illustrates why we need the ability apply different symbols for a layer. The circles on the map come from a combination of both layers.

@gislawill @ericboucher - interested to hear your thoughts on this suggested feature.

Good catch, @wadhwamatic. Adding custom symbols for layers should be pretty straightforward — I've included a snippet we should be able to use in our PointDataLayer component.
We should also consider supporting an icon library like Iconify to build in more flexibility. This would allow us to use any icon in their library rather than needing to upload and bundle a new image file for new icon.
const MapComponent = () => {
  const mapRef = useRef();

  useEffect(() => {
    const map = mapRef.current?.getMap();

    if (map) {
      map.loadImage('/path/to/custom-icon.png', (error, image) => {
        if (error) throw error;
        if (!map.hasImage('custom-icon')) {
          map.addImage('custom-icon', image);
        }
      });
    }
  }, [mapLoaded]);

  const layerStyle = {
    id: 'points',
    type: 'symbol',
    source: 'my-data',
    layout: {
      'icon-image': 'custom-icon',
      'icon-size': 0.5,
      'icon-anchor': 'bottom',
    },
  };

  return (
    <Map>
      <Source id="my-data" type="geojson" data={geojsonData}>
        <Layer {...layerStyle} />
      </Source>
    </Map>
  );
};

Great, thanks @gislawill! And good recommendation to use an existing icon library. We already include Material icons FYI


No such image from aws ecs registry

Cookbook version
2.13.9
Chef-client version
12.18.31
Platform Details
CentOS 7
Docker: 1.13.0
Scenario:
try pull docker image from ecs registry via chef docker cookbook
Steps to Reproduce:

Push docker image to aws ecs registry
Get aws login in the host (aws ecr get-login --region eu-west-1)
Run chef recipe like
docker_image 'docker-app-experiments-image' do
repo 544444444.dkr.ecr.eu-west-1.amazonaws.com/my2experiments
tag 1
action :pull
read_timeout 600
end

Expected Result:
Pulled docker image
Actual Result:
Docker::Error::NotFoundError
----------------------------
No such image: 544444444.dkr.ecr.eu-west-1.amazonaws.com/my2experiments:17

Try manual
docker pull 544444444.dkr.ecr.eu-west-1.amazonaws.com/my2experiments:17
works success

I tried trick like
`  # get-aws-docker-registry credls
template '/root/.aws/credentials' do
source 'credentials.erb'
action :create
mode '0600'
end
get-aws-docker-registry credls
template '/etc/get-aws-credls.sh' do
source 'get-aws-credls.sh.erb'
action :create
mode '0744'
end
cron 'get-aws-docker-registry-credls' do
minute '30'
command '/etc/get-aws-credls.sh'
notifies :run, 'execute[get-dkr-credls]', :immediately
end
execute "get-dkr-credls" do
command "bash /etc/get-aws-credls.sh"
action :nothing
end
require 'json'
file = File.read('/root/.docker/config.json')
data_hash = JSON.parse(file)
docker_registry 'https://544444444.dkr.ecr.eu-west-1.amazonaws.com' do
username 'AWS'
password "#{data_hash['auths']['544444444.dkr.ecr.eu-west-1.amazonaws.com']['auth']}"
end`
but authentication failed.
Then I runned command from command line all was fine.

Unrelated but how did you get Docker to even install?  The install script doesn't even work on Amazon Linux right now:
https://github.com/chef-cookbooks/docker/issues/812

Hi @oleg-filiutsich , I got it working based on your "workaround". You just missed that auth information in .docker/config.json is base64 encoded. Here's my code:
`require 'json'
require 'base64'
bash "get ECR credentials" do
code "eval $(aws ecr get-login --region us-east-1)"
end
file = File.read('/root/.docker/config.json')
docker_config = JSON.parse(file)
docker_registry 'https://1234567890.dkr.ecr.us-east-1.amazonaws.com' do
username Base64.decode64(docker_config['auths']['https://1234567890.dkr.ecr.us-east-1.amazonaws.com']['auth']).split(':').first
password Base64.decode64(docker_config['auths']['https://1§234567890.dkr.ecr.us-east-1.amazonaws.com']['auth']).split(':').last
end`

Closing this and linking to https://github.com/chef-cookbooks/docker/issues/826

@lifeofguenter We switched to https://github.com/awslabs/amazon-ecr-credential-helper

thanks @zvymazal - solved the issue, turns out  you first need a docker_image resource before using the image directly in docker_container...


Feature request: Monoidal and Cartesian Categories

These would be great for experimentation.
See: http://conal.net/papers/compiling-to-categories/
Also see: https://gist.github.com/paf31/5c1279796d66fe04a177e34b0d674ac6
It gives you a lambda calculus that can be compiled into a Cartesian category at runtime. We'd probably want a few more levels in the typeclasses though.

I don't fully grasp the paper, but we can give it a try. The basic type-classes seem to be easy to implement. It would be better to have a working Haskell module for reference, though.

This is the one that we can compile lambda calculus to for that incremental computation and automatic derivatives:
http://hackage.haskell.org/package/categories-1.0.7/docs/Control-Category-Cartesian-Closed.html
There is a lot of levels to the typeclass. I'm not sure if we should go as deep. We could just go CCC extending Category directly, and just combine all the methods in CCC.

The CCC in the 2nd link is probably enough:
https://gist.github.com/paf31/5c1279796d66fe04a177e34b0d674ac6
The hackage one seems like overkill.

I opened a branch category-ccc for playing around, and started with the easiest class :-D

Cheers. I've been to busy to play with this lately... you were very quick, nice work.

I may play with you some time on the same branch... make sure we debug it first before it becomes a part of master branch.

I had a quick browse of your code by eye, and nice work! What I like about CCC is that it preserves the meaning of the code, and when you feed it different category to can have different evaluation strategies which gives different interpretation of the same code.
One category I've been bugging people to try out in other repositories is:
data IncF a b = IncF (a -> (b, IncF2 a b))
data IncF2 a b = IncF2 (Δa -> (Δb, IncF2 a b))

Which is a little tricky in Java because we do not have type families. But what it provides is an interpretation that incrementally updates a computation on change in input. The reason I'm interested in this one is that it can replace virtual dom, eliminating the need for diffing algorithms. Diffing algorithms partly involve finding the longest common subset of a set, which I believe is NP-Hard. So as the number of interactive elements on your screen become large, a diffing algorithm suffers quite significantly.
Conal Elliott demonstrates quite a few different categories in his paper. In his paper lambda calculus is compiled to CCC via a compiler plugin. And the drawing of the graphs in his paper is actually produced directly from the code via a category suitable for producing graph drawings.
In the 2nd link, Phil Freeman shows how to compile lambda calculus to CCC at runtime rather than a compile plugin. Which would be achievable for us in Java. His Untyped debugging category is similar to Conal's graph drawing category in that it lets you see the source code of the computation.

To be honest, I have no idea what I'm doing, but it is kind of fun. I'll see how it goes with Cast

Would be awesome one lam and ($) is going. It would mean we can runtime compile lambda calculus into CCC.

We may have a few more options for lam. Here is the blog post that goes with Phil Freeman's code.
https://blog.functorial.com/posts/2017-10-08-HOAS-CCCs.html
We may find a way that works nicer for Java .

In java we may not even need Cast because we can do things like <A extends Something>. I'll have a play around with the same code soon.

I created a KTest in the tests package. It shows a couple of tests from the 2nd link.

I think the Lam2CCC class is too tricky to use for nontrivial code, and the end-user would have to supply really long type signtures to make it work. What might be better is a simple deeply embedded DSL for the lambda calculus itself, then transform the lambda calculus into CCC via the transformation methods given in Conal's paper (1st link).
Any ideas on a nice DSL for lambda calculus?

I could only find simple untyped DSLs like https://github.com/noti0na1/LambdaCalculus-java
I'm not sure wether this can help us.
While searching I found this interesting, but unfortunately outdated paper: http://web.cs.ucla.edu/~palsberg/tba/papers/wright-jagannathan-ungureanu-hertzmann-tic98.pdf

Not sure if STLC can be fully inspected to make it convertable to a CCC, because of that lambda held by Lam.

Actually, something like this might work:
data STLC repr a where
  Lam :: (STLC repr a -> STLC repr b) -> STLC repr (a -> b)
  Ap :: STLC repr (a -> b) -> STLC repr a -> STLC repr b
  Lift :: repr a -> STLC repr a
  Var :: Int -> STLC repr a

Then if I send a Var attached to a unique integer into the lambda held by Lam, then it would reveal the the structure inside the lambda held by Lam.

Here is a rough sketch of the Code in Java: https://gist.github.com/clinuxrulz/c29f063c5b3e8fc54cd07010f77b4c54
System.out.println(LC.lam(x -> LC.lam(y -> x)).toString());
produces:
(\v0 -> (\v1 -> v0))
which means the lambda can be fully inspected, and compiled down to CCC using the steps in the paper in the 1st link.

I've almost got her work out. Just very challenging. And it looks like we might need Cartesian as well, not just CCC, and extend CCC from Cartesian. Because it is not possible to implement apply, curry, uncurry for some of the interesting category, yet when optimising the CCC in most cases we can eliminate the requirement of theses methods be left with just a Cartesian Category.... so maybe just 1 level deeper in the typeclass.

Getting closer, check it out :wink:
System.out.println(toCCC(K.ccc(), LC.lam(x -> LC.lam(y -> x))).map(Hkt::asK).map(K::optimize).map(K::prettyPrint).getOrElse(""));

Produces:
uncurry id . (curry (fst . snd) &&& id)

Not quite optimised yet.

One optimization we can add is:
apply . (curry h `fork` g) = h . (id `fork` g)
It should be enough to help us move from CCC to Cartesian.

Implementing the rest of the tests from the 2nd link reveals a seg fault in the java compiler.

OK. Defining the IncF in Java was easier than I thought it would be. We could be onto something exciting here. A replacement for virtual dom just looks just like elm architecture code-usage-wise.
Here is a taste of how IncF could be defined in Java:
https://gist.github.com/clinuxrulz/21cad00a3c75b2395187ace02a6acb97
I don't believe this stuff will be over your head seeing the code you've already written. Is it the hom and tensor that is confusing?... hom is just like a lambda or function (F1), and tensor is just like our tuples (T2). The only reason they exist as type variable is just to increase the flexibility for instances of Cartesian and CCC, and there may be time when theses type are defined in terms of the category they are for too.
We have enough under the hood at the moment to create an experimental project called something like vdom-experiment and see how far we can go. It can use HighJ for creating a lambda calculus DSL that can perform incremental updates, and be sitting on top of GWT so we can test it on a real dom.
If the experiment is a success, we can translate the ideas to a highly used language for web app development, such as TypeScript. Rinse and Repeat.

I'm going to have a bit of a play here:
https://github.com/clinuxrulz/vdom_escape
its only dependency is the category-ccc branch of highj. I'll let ya know how it turns out.

First successful compilation from lambda calculus to incremental functions.
        IncF<Integer, Integer> x1 =
            Hkt.asIncF(
                FreeCCC
                    .narrow(
                        LC.<__<__<__<FreeCCC.µ, IncF.µ>, T2Tensor.µ>, Hom>, T2Tensor.µ, Hom, Integer, Integer>toCCC(
                            FreeCCC.ccc(),
                            LC.lam(x -> x) // <-- code goes here. E.g. model -> view
                        ).get()
                    )
                    .reduceToCartesian(T2Tensor.tensorDontDependOnK, IncF.cartesian()).get()
            );

I'm just struggling with TeaVM, when I compile some code with a public static void main(String[] params) method, that method does not seem to get generated in the javascript produced.
Have you had some experience with TeaVM before?
I was gonna use it to demonstrate a incremental dom.

never mind mvn package was what i needed to type :smile:

Fighting type signatures at the moment. Its interesting that it is possible rearrange the code to hide the details of LC & CCC from the end user.
E.g. An incremental tuple constructor
    public static <Hom,A,B> LC<__<__<__<FreeCCC.µ, IncF.µ>, T2Tensor.µ>, Hom>, Hom, __3<T2Tensor.µ, __<__<__<FreeCCC.µ, IncF.µ>, T2Tensor.µ>, Hom>, Integer, Integer>> t2(
        LC<__<__<__<FreeCCC.µ, IncF.µ>, T2Tensor.µ>, Hom>,Hom,A> a,
        LC<__<__<__<FreeCCC.µ, IncF.µ>, T2Tensor.µ>, Hom>,Hom,B> b
    ) {
        CCC<__<__<__<FreeCCC.µ, IncF.µ>, T2Tensor.µ>, Hom>, T2Tensor.µ, Hom> ccc = FreeCCC.ccc();
        return LC.ap(LC.ap(LC.lift(ccc.curry(ccc.identity())), a), b);
    }

The LC stuff could all be wrapped up by a new type... call it something like ILC (incremental-lambda calculus). The type-signature becomes:
public static <A,B> ILC<T2<A,B>> t2(ILC<A> a, ILC<B> b) { ... }
With enough wrapping it might be possible to keep the end-user unaware they are using anything complicated, it would just feel like normal functional programming.
Still a bit of work to do, need to incremental constructors for the dom elements themselves.

We can probably do away with the k type parameter being passed to the Tensor & Hom.
This implementation does without it:
https://hackage.haskell.org/package/category-extras-0.53.0/docs/Control-Category-Cartesian-Closed.html
Also it would make that FreeCCC a bit easier to use (in vdom_escape). That change would get rid of the TensorDoesntDependOnK & HomDoesNotDependOnK type classes I needed to use FreeCCC for rule-rewrites before developing the IncF.

OK. I think I've come to the conclusion that creating a lambda calculus dsl and compiling it to ccc is complete overkill for a vdom replacement. We can just use IncF directly and wrap it up however we like.
    public static <I> IncF<I,Element> el2(
        String element,
        __2<IncF.µ,I,Atomic<String>> text,
        __2<IncF.µ,I,IMap<String,Atomic<String>>> attributes,
        __2<IncF.µ,I,IMap<String,Atomic<Consumer<DomEvent>>>> handlers,
        __2<IncF.µ,I,IMap<Integer,Element>> children
    ) {
        return IncF.narrow(IncF.semigroupoid.dot(
            incFEl2(element),
            t2(text, t2(attributes, t2(handlers, children)))
        ));
    }

    public static <I,A,B> IncF<I,__3<T2Tensor.µ, IncF.µ, A, B>> t2(
        __2<IncF.µ,I,A> a,
        __2<IncF.µ,I,B> b
    ) {
        return IncF.narrow(IncF.cartesian.fork(a, b));
    }

Quite easy to define an incremental element that way. I here is just our environment type, (the type signature of the model).
I'll go down that path instead, no need to have a CCC or Cartesian type classes in highj, but could become useful one day.


Updates to tests

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


collections within collections

I'm not sure if I'm doing something wrong here or not...I imagine I am since this seems like a very common use-case:
I've got one class extended from Backbone.collection, which is meant to contain another class extended from Backbone.collection.
The problem I hit was that when I'd call outerClass.add(instanceOfInnerClass); that for some reason I was getting an extra collection object in between...in other words, the structure looked something like this:
outerClass
    2ndInstanceOfOuter
        innerClass
I tracked down the "problem" to this function:
// Prepare a model to be added to this collection
    _prepareModel: function(model, options) {
      if (!(model instanceof Backbone.Model)) {
        var attrs = model;
        model = new this.model(attrs, {collection: this});
        if (model.validate && !model._performValidation(attrs, options)) model = false;
      } else if (!model.collection) {
        model.collection = this;
      }
      return model;
    },

what was happening is that my "instanceOfInner" was not an instance of model (but of collection), and therefore this function was creating a new object and passing instanceOfInner into it...this line is the important one:
 if (!(model instanceof Backbone.Model)) {

changing it to this has solved my problem, but it's nagging me that there's something I'm missing:
  if (!(model instanceof Backbone.Model) && !(model instanceof Backbone.Collection) ) {

Can anyone offer any insight?

You're not intended to nest collections and models in this fashion. Instead, simply:
outerCollection.innerCollection = instanceOfInnerCollection


Grouping with Where on a navigation prop fails

Version: "7.0.0-rc1-*
Query:
from o in nwind.Orders
where o.Shipper.CompanyName == "Speedy Express"
group o by o.OrderDate;

Message:
Expression of type '...' cannot be used for parameter of type '...' of method '...'

Full sample: https://github.com/AlekseyMartynov/ef7-bugs/tree/group-navigation-where

Verified that this query throws an ArgumentException in EntityFramework.MicrosoftSqlServer 7.0.0-rc1-final, but the exception is not thrown in current dev.
The returned results appear to be incorrect due to a related issue (#5179) with navigations.

@mikary can you verify now that #5179 is fixed

Verified and added test coverage to prevent future regressions.


Tooling/dotnetcore

This looks massive, but the code is actually unchanged (except for a couple of fixes in the test code, see the last commits). However, I have moved it to a folder structure more common when using dotnet.
I have also bumped the version to 0.1.0 - seemed appropriate, with a new target framework :)
The two maintenance scripts CreateNuget.cmd and DeployNuget.cmd are gone; the corresponding actions can now be done with the CLI:

dotnet pack -c Release -o "$(pwd)\nuget_packages" (from powershell) creates packages in the nuget_packages folder (as before)
dotnet push nuget_packages/FSharpFriendlyDotnet.0.1.0.nupkg -k <your-api-key> pushes the both the package and the symbols package to NuGet.org

Also, if this library is abandoned and you'd like me to take over, just let me know. You could either send me the NuGet API keys to be able to update the package, or I'll upload it under another name under my own account.

Nice PR. Many thanks. I would keep the scripts but change them into the dotnet commands you show here in the PR. Remember to generate and push symbols. See https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages packages without symbols are pure rage inducing ;-)
I don't get to code F# alot these days, so sure you are welcome onboard the project. Do you have any ideas in mind for the future?

Ah, I didn't realize you had appveyor hooked up. Do you want me to create an appveyor.yml with config?
I don't really have any specific ideas for the future, more than realizing that I'll probably find more APIs that could use a facade once I start using the library.

I usually script creation of packages so I don't forget. I prefer manual release rather than on each push ;) appveyor for testing would be a blast ;-)

One workflow for releases I've used successfully is to build with AppVeyor and push pre-release packages on every build, and then push "real" packages on tagged releases, which can be created from the GitHub UI. That allows for manual control of what code goes into a new release of the package, while making incremental improvements available for consumption anyway.

@kbilsted There, there is now an .appveyor.yml that configures the build to run dotnet build, dotnet pack and dotnet test and exposes the created nuget packages as build artifacts for inspection. It doesn't push any packages; if you want that, I can do that in a separate PR. For a streamlined flow there, it would probably be nice to bring in something like GitVersion to manage version numbering.
If you wouldn't mind, it would be awesome if this could be merged and released to nuget.org, because I want to use it in one of my projects :)

many thanks for the changes ;)

reading https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages  it looks like we need nuget push MyPackage.symbols.nupkg -source https://nuget.smbsrc.net/ instead

Based on this I think not; dotnet nuget push seems to do both.
In any case, it should be easy to test (for you, who has the API key) - if you run the current DeployNuget.cmd, does it push symbols?

info : Pushing FSharpFriendlyDotNet.0.1.0.nupkg to 'https://nuget.org'...
info :   PUT https://nuget.org/api/v2/package/
info :   Created https://nuget.org/api/v2/package/ 13111ms
info : Your package was pushed.
info : Pushing FSharpFriendlyDotNet.0.1.0.symbols.nupkg to 'https://nuget.org'...
info :   PUT https://nuget.org/api/v2/package/
info :   Conflict https://nuget.org/api/v2/package/ 646ms
error: Response status code does not indicate success: 409 (A package with ID 'FSharpFriendlyDotNet' and version '0.1.0'
already exists and cannot be modified.).

for fun i tried
dotnet nuget push *.symbols.nupkg --source https://nuget.org
dotnet nuget push *.nupkg --source https://nuget.org
on a 0.1.1 release.
this gives me the reverse error ;)
C:\src\FSharpFriendlyDotNet\nuget_packages>dotnet nuget push *.symbols.nupkg --source https://nuget.org
info : Pushing FSharpFriendlyDotNet.0.1.1.symbols.nupkg to 'https://nuget.org'...
info :   PUT https://nuget.org/api/v2/package/
info :   Created https://nuget.org/api/v2/package/ 12797ms
info : Your package was pushed.
C:\src\FSharpFriendlyDotNet\nuget_packages>dotnet nuget push *.nupkg --source https://nuget.org
info : Pushing FSharpFriendlyDotNet.0.1.1.nupkg to 'https://nuget.org'...
info :   PUT https://nuget.org/api/v2/package/
info :   Conflict https://nuget.org/api/v2/package/ 1379ms
error: Response status code does not indicate success: 409 (A package with ID 'FSharpFriendlyDotNet' and version '0.1.1'
already exists and cannot be modified.).
Lets see in a couple of hours if the symbols have been pushed ;)

Hum; interesting. I was under the impression that it would automatically use https://nuget.smbsrc.net/ as the source for the symbols package. Could you try
dotnet push *.nupkg --source https://nuget.org --symbol-source https://nuget.smbsrc.net/

and see if that does the right thing? Otherwise we might have to just issue two commands (and word them smartly to not include the symbols package in the first one...).

C:\src\FSharpFriendlyDotNet\nuget_packages>dotnet nuget push *.nupkg --source https://nuget.org --symbol-source https://
nuget.smbsrc.net/
info : Pushing FSharpFriendlyDotNet.0.1.1.nupkg to 'https://nuget.org'...
info :   PUT https://nuget.org/api/v2/package/
info :   Conflict https://nuget.org/api/v2/package/ 1556ms
error: Response status code does not indicate success: 409 (A package with ID 'FSharpFriendlyDotNet' and version '0.1.1'
already exists and cannot be modified.).

C:\src\FSharpFriendlyDotNet\nuget_packages>dotnet nuget push *.nupkg --source https://nuget.org --symbol-source https://
nuget.smbsrc.net/
info : Pushing FSharpFriendlyDotNet.0.1.2.nupkg to 'https://nuget.org'...
info :   PUT https://nuget.org/api/v2/package/
info :   Created https://nuget.org/api/v2/package/ 12898ms
info : Your package was pushed.
info : Pushing FSharpFriendlyDotNet.0.1.2.symbols.nupkg to 'https://nuget.org'...
info :   PUT https://nuget.org/api/v2/package/
info :   Conflict https://nuget.org/api/v2/package/ 513ms
error: Response status code does not indicate success: 409 (A package with ID 'FSharpFriendlyDotNet' and version '0.1.2'
already exists and cannot be modified.).

Argh. It doesn't seem to recognize that this is a symbols package... 🤔 I'll take a look when I get some time to spare, if you don't get to it before me...

it doesn't seem to be pushing any symbols only pushing the symbols file..


Remove license appendix.

This change is

LICENSE line 194 at r1 (raw file):
Previously, dan-starkware wrote…
I think this should remain.

I'm confused, isn't it a part of the appendix, which we are removing?

LICENSE line 194 at r1 (raw file):
Previously, ilyalesokhin-starkware wrote…
I'm confused, isn't it a part of the appendix, which we are removing?

No. This is where we apply the license.
Up to line 175 is description of Apache license.
Remove the appendix (lines 175-190)
Line 190 onward is applying the license.
https://www.apache.org/licenses/LICENSE-2.0

LICENSE line 190 at r3 (raw file):
Previously, dan-starkware wrote…
I still think StarkWare Industries should appear somewhere.

Maybe, but I don't know where to put it.


Make status code configurable

POC for https://lists.apache.org/thread/svjh13gswbsl4n6z3hd03r67xlktyydz

This PR doesn't appear to change the current behaviour.

The intention of the PR was to demonstrate if we could safely not close a connection on a application sent 4xx but always safely close it on HTTP parsing failures. I wanted to get feedback on the approach before I sink more time into this since there were concerns in the mailing list that attempting to do such a thing was not safe at all.

Ah, understood. My view is that this is a neat trick but it isn't sufficient. There are a bunch of places where Tomcat calls response.sendError(400,"reason") where we also want the connection to be closed. e.g. CoyoteAdapter. I don't see how we can differentiate between those calls and calls from the application that do not need to be fatal.
I keep coming back to the view that applications should not be using 400 responses for this. Those applications that need to use HTTP response codes should define their own 4xx status code(s).

@markt-asf I think Tomcat reserving existing HTTP 4xx responses solely for its internal use is very restrictive to the application.
What do you feel about, adding a new field in the CoyoteResponse called shouldCloseConnection that defaults to true and we set it to false once we are sure we are entering application layer. On how we detect we are entering the application layer is something I would need to deep dive on.

Tomcat isn't reserving all 4xx responses. It will close the connection if a small sub-set of those status codes is used and does so to avoid various potential security issues. Applications still have over 70 4xx codes to use that have not been defined by any RFC.
The use of async has made determining if an error is set by the application or the container quite a bit trickier.
I remain to be convinced both that applications should be using the 400 status code and that differentiating between an application set 400 status code and container set 400 status code is possible without excessive complexity.

I'm not seeing a clean way to differentiate between container set 400 status and application set. Closing this draft PR. I'd be happy to consider a PR if a clean solution can be found.


 So when you add a package and then run pipenv lock, it will update everything in that file, including other packages you may not be aware of. So the best workflow for changing the Pipfile is:

Run pipenv lock
Assuming that Pipfile.lock has changed, commit it to git with a generic message like "Update pipenv dependencies"
Edit Pipfile
Run pipenv lock again
Stage Pipfile and Pipfile.lock to git, committing them with a message about the packages you are changing.

The reason that this workflow is preferred is because if an update in some other package causes unforeseen problems, it makes it slightly easier to debug this when using git bisect.

Almost lgtm! f413e90 and f737008 should be squashed together, then lgtm! You may want to consult with @nre-ableton on whether a generic "update Pipfile lock" commit is needed before doing "Add black and remove flake8-commas" (and its associated Pipfile.lock changes).

Update Pipfile lock commit not needed 😄

@ablbot rebase

@ablbot rebase

Why is ae1be28 touching Pipfile.lock? This doesn't feel right.

Turns out we needed to coerce pyparsing to not use 2.4.1. We made another commit for this which also changes the Pipfile 😄

I didn't dig into the diffs of the lockfile, but I wouldn't be surprised if pipenv is doing other stuff we aren't intending here. Let's just squash https://github.com/AbletonDevTools/groovylint/pull/72/commits/ebcd972045ce3c87ff7d54cdff988713a0b25a9e into https://github.com/AbletonDevTools/groovylint/pull/72/commits/83cee4d7c6d283c0e9e805dedf447eed9df33b7f (which is just as well since ebcd972045ce3c87ff7d54cdff988713a0b25a9e had a typo in the commit message 😅) and be done with it.
LGTM post squash!


Updating the link

Fixes: https://github.com/vaadin/framework/issues/10804

This change is

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

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


allow devise < 4.7

Tests pass and my app works with it, too, but maybe someone with a more complicated setup could test it a little bit more.
Note: I had to explicitly require 'devise/orm/active_record' in config/initializers/devise_token_auth.rb or else I had some errors about missing method devise in my models. Before I didn't had it and everything worked, but maybe now it is required? Not sure if this should be added to lib/generators/devise_token_auth/templates/devise_token_auth.rb here, too.
(Devise < 4.6 has a security issue, so I think it should be updated as fast as possible)

I hope you don't mind I updated the ruby versions in CI, fixed the sqlite3 issue and added a CI test against rails 6.0.beta (except mongoid since I think it does not support rails 6 yet) in this MR, too. 🤞 that tests pass now.

I think now it's ready with only the minimal changes needed.

Can we get a patch version bump for this?

@dkniffin @Polidoro I released v1.1.0 which includes some features and bug fixes (e.g. Mongo support), if you need it in v1.0.0 let me know and I can create a PR for that. If you were using master, you won't have any issue.
You can see the differences in https://github.com/lynndylanhurley/devise_token_auth/compare/v1.0.0...master


ETA on next release

Hello all,
A critical bug blocking our workflow is fixed as a part of #50dc0a2 when can we expect the next release? I see there are no milestones set on this repo.
TIA

7.0.0 has entered QA and will be released in the coming weeks.


Roadmap: Task 4c: HPC installable packages

Build HPC-installable conda or hashdist packages making it simpler to install simulation code like ADH on ERDC HPC systems

Need to ensure that all EarthSim packages are HPC installable.

I believe this was completed, and should be re-raised either as part of the new work or as a separate public issue.


Wrong offset of the 1st message with fromOffset: true

Bug Report
When I use simple Consumer with fromOffset: true I get messages starting from a wrong offsets for some values of offsets to start from. The topic was initially created as a gzipped topic. The issue isn't reproduced on a non-compressed topic.
Environment

Node version: v10.10.0
Kafka-node version: 4.0.4 and 4.1.0
Kafka version: 2.12-2.1.1

For specific cases also provide

Number of Brokers: 1
Number partitions for topic: 1

Include Sample Code to reproduce behavior
Client code
// kafka-node-test.js file

const kafkaLogging = require('kafka-node/logging')
kafkaLogging.setLoggerProvider((name) => {
  return {
    debug: (message) => console.debug(`[${name}] ${message}`),
    info: (message) => console.log(`[${name}] ${message}`),
    warn: (message) => console.warn(`[${name}] ${message}`),
    error: (message) => console.error(`[${name}] ${message}`),
  }
})

const { KafkaClient, Consumer } = require('kafka-node')
const clientId = 'a-client-id'
const groupId = 'a-group-id-3'

const client = new KafkaClient({ clientId })
const payload = [{
  topic: 'a-gzip-topic',
  partition: 0,
  offset: parseInt(process.env.TEST_KAFKA_NODE_OFFSET, 10),
}]
const consumer = new Consumer(client, payload, {
  autoCommit: false,
  fromOffset: true,
  groupId,
})

consumer.on('message', (message) => {
  console.log(`[INFO] Message: ${JSON.stringify(message)}`)
})

consumer.on('error', (error) => {
  console.error(`[ERR] ${JSON.stringify(error)}`)
})

consumer.on('offsetOutOfRange', (error) => {
  console.error(`[ERR] Offset out of range: ${JSON.stringify(error)}`)
})

Include output with Debug turned on
# creating a gzipped topic
aMac:kafka_2.12-2.1.1 viktor_molokostov$ bin/kafka-topics.sh --zookeeper localhost:2181 --create --topic a-gzip-topic --partitions 1 --replication-factor 1 --config retention.ms=86400000 --config compression.type=gzip
Created topic "a-gzip-topic".

# adding messages on top of messages which were previously in the topic
aMac:kafka_2.12-2.1.1 viktor_molokostov$ bin/kafka-console-producer.sh --broker-list localhost:9092     --topic a-gzip-topic
>123
>123
>123
>123
>123

# starting from offset 20
aMac:local-poc viktor_molokostov$ export TEST_KAFKA_NODE_OFFSET=20 && node kafka-node-test.js
[kafka-node:KafkaClient] Connect attempt 1
[kafka-node:KafkaClient] Trying to connect to host: localhost port: 9092
[kafka-node:KafkaClient] a-client-id createBroker localhost:9092
[kafka-node:KafkaClient] a-client-id sending versions request to localhost:9092
[kafka-node:KafkaClient] broker socket connected %j
[kafka-node:KafkaClient] connected to socket, trying to load initial metadata
[kafka-node:KafkaClient] missing apiSupport waiting until broker is ready...
[kafka-node:KafkaClient] waitUntilReady [BrokerWrapper localhost:9092 (connected: true) (ready: false) (idle: false) (needAuthentication: false) (authenticated: false)]
[kafka-node:KafkaClient] Received versions response from localhost:9092
[kafka-node:KafkaClient] setting api support to %j
[kafka-node:KafkaClient] broker is now ready
[kafka-node:KafkaClient] a-client-id updated internal metadata
[kafka-node:Consumer] consumer ready
[kafka-node:KafkaClient] a-client-id updated internal metadata
[kafka-node:KafkaClient] a-client-id createBroker <IP_ADDRESS>:9092
[kafka-node:KafkaClient] waitUntilReady [BrokerWrapper <IP_ADDRESS>:9092 (connected: true) (ready: false) (idle: false) (needAuthentication: false) (authenticated: false)]
[kafka-node:KafkaClient] a-client-id sending versions request to <IP_ADDRESS>:9092
[kafka-node:KafkaClient] Received versions response from <IP_ADDRESS>:9092
[kafka-node:KafkaClient] setting api support to %j
[kafka-node:KafkaClient] broker is now ready
[INFO] Message: {"topic":"a-gzip-topic","value":"22","offset":20,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":21,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":22,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":23,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":24,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":25,"partition":0,"highWaterOffset":26,"key":null}
# ^ it is ok, messages start from offset 20

# starting from 21
aMac:local-poc viktor_molokostov$ export TEST_KAFKA_NODE_OFFSET=21 && node kafka-node-test.js
# ... client initialization logs
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":21,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":22,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":23,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":24,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":25,"partition":0,"highWaterOffset":26,"key":null}
# ^ OK, messages start from 21

# starting from 22
aMac:local-poc viktor_molokostov$ export TEST_KAFKA_NODE_OFFSET=22 && node kafka-node-test.js
# ... client initialization logs
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":21,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":22,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":23,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":24,"partition":0,"highWaterOffset":26,"key":null}
[INFO] Message: {"topic":"a-gzip-topic","value":"123","offset":25,"partition":0,"highWaterOffset":26,"key":null
# ^ the issue, messages start from 21

When I go further it continues this way:

for 23 - OK
for 24 - starts from 23
for 25 - OK

I don't see exact correlation between starting offsets and the ones I get, but hopefully it is enough to give you some clue.

As we were discussing on the other ticket, gzipped topics are currently not supported correctly.
If you use 4.0.4 with a non gzipped topic and ensure your producer sets the attributes flag to compress the message individually instead, then things should work better.
I do not recommend using 4.1.0 at all.

I observed interesting behavior with these gziped topics. It seems they can give you more offsets than requested (but never less).
Interestingly if you send every message as separate requests instead of batching them you are able to consume at the requested offset.
For now, you could discard just those offsets perhaps kafka-node can do this for you in the future.

@hyperlink it is expected according to the protocol, which is what this was for: https://github.com/SOHU-Co/kafka-node/commit/91e361d8c012838b9931236ba0799cb04fcaca0d#diff-67e91725f6be46be7b40345ceb6d5654R1145
Some of my changes didn't get lost in the recent updates did it?

@aikar that code did not change but since he's using a regular consumer it doesn't hit that code.

@hyperlink why wouldnt it? regular consumer still uses kafkaClient?
Didn't we drop support for legacy zookeeper clients?

We did remove zk but your validator code is coupled with ConsumerGroup concepts. I think that's why you opted it to have it call the original fetch code instead.

@hyperlink https://github.com/SOHU-Co/kafka-node/blob/397ae179dd11dbc69a12268e1519e8a569dfc1cd/lib/consumer.js#L180
This still calls sendFetchRequest on the KafkaClient:
https://github.com/SOHU-Co/kafka-node/blob/825a89a8354be544aece92085a2bb97cbc1d9c5f/lib/kafkaClient.js#L1221
Does appear all Consumers should be using that state validator. the validators checks on member/group ID's should remain the same though.

Doh nevermind I just noticed this:
https://github.com/SOHU-Co/kafka-node/blob/825a89a8354be544aece92085a2bb97cbc1d9c5f/lib/kafkaClient.js#L1233
I guess that is falling back to Client
Not sure if this is actually desirable?

As we were discussing on the other ticket, gzipped topics are currently not supported correctly.
If you use 4.0.4 with a non gzipped topic and ensure your producer sets the attributes flag to compress the message individually instead, then things should work better.
I do not recommend using 4.1.0 at all.

Unfortunately, I don't have control over producer. But thanks anyway - we'll do some workaround


TP: Provide way to enable or disable cachegroup localization methods

With support via the TO API, add the ability to enable/disable localization methods (CZ, DEEP_CZ, GEO) in the cachegroup view.
This is done by having a checkbox per localization method (by default all are checked) which is then translated into an array of enabled localization methods that the API expects. This more naturally mapped to having a select with the multiple attribute which actually binds to an array in angularjs, but I think that provided a worse UX compared to checkboxes.
This depends on the API implementation in #2557

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/2159/
Test PASSed.

@rawlinp See https://github.com/apache/trafficcontrol/pull/2605 for your API Test fixes


Fix issues with losing state when navigating or opening/closing items, while filtering.

Bug/issue #, if applicable: 90843762
Summary
This PR fixes a few issues we have noticed during testing:

[x] rdar://90841554 ([TESTFEST] Navigation collapses on searched term when performing a search, expanding and then selecting a subsection)
[x] rdar://90843762 ([TESTFEST] Filtering for Sample Code yields inconsistent UI experience)
[x] Navigating across pages while filtering, re-opens all previously closed items.

Dependencies
NA
Testing
You can use any doccarchive with an index.
Steps:

Apply a generic enough filter
Start opening/closing items.
Assert there are no items being lost when opening/closing.
Try to find a parent item that has no children matches. Assert it renders as closed initially, but you can expand and see it's children.
Try cmd + click to open all siblings. Assert its all working as expected.
Try alt + click to open all nested children. Assert they are all rendered in correct order.
Close some items and start navigating across links in the page OR by clicking navigator items.
Assert the collapsed items are not opened, unless your current page is in one of them.
Try the same with going back/forward in the browser.
Clear the filters and assert the only open items are the ones leading to the current page.
Assert that opening/closing items without a filter works as expected.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[ ] Added tests
[ ] Ran npm test, and it succeeded
[ ] Updated documentation if necessary

Sorry, GitHub decided to double all my review comments...

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test


macOS/iOS testapp

macOS almost done
iOS is coming next

Apple changed std::filesystem. it's not available any more in experimental. cool.


Update some info to reflect status of project

Updated README and classifier to better reflect the status of the project. For the classifier while the literal version is not an alpha, the project is more in the alpha state than the planning state as production level projects rely on s3transfer but there may be more features added to s3transfer before it goes GA.
Addresses https://github.com/boto/s3transfer/issues/74
cc @jamesls @JordonPhillips @stealthycoin

I updated the README based on that wording and also added a sentence about boto3. Merging.


What model are you using?

Which model are you using?  And how did you convert to tfjs?
I'd like to try a model that'll increase accuracy (at a performance cost).
Also, thanks for this!

If I remember correctly I loaded the original MiDaS v1 model from torchhub, converted to ONNX and then to tf.js with quantization. However, I'm sure the underlying model and export process is outdated by this point, so you might want to start from scratch.


⚠ Bofrost.lu has degraded performance

In c4828e6, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1053 ms

Resolved: Bofrost.lu performance has improved in 42dfb57 after 1 hour, 55 minutes.


next-contentlayer should have contentlayer as peerDependency

Issue
The package next-contentlayer has a constraints system to ensure that same versions for next-contentlayer and contentlayer are installed.
At the build time it will run require(contentlayer/package.json).version which result in Error: next-contentlayer tried to access contentlayer when using latest Yarn version
Workaround
By using the packageExtensions configuration in .yarnrc.yml we can actually define ourself peerDependencies of dependent packages:
packageExtensions:
  'next-contentlayer@*':
    peerDependencies:
      'contentlayer': '*'

Versions
Yarn: v3.5.1
contentlayer: v0.3.1
next-contentlayer: v0.3.1
next: v13.3.4
Complete error
docs:build: > Build error occurred
docs:build: Error: next-contentlayer tried to access contentlayer, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.
docs:build:
docs:build: Required package: contentlayer (via "contentlayer/package.json")
docs:build: Required by: next-contentlayer@virtual:ba56dc173c7ece72e1480aefcd1d10cda16[29](https://github.com/kerwanp/notion-render/actions/runs/4874086636/jobs/8694558349#step:5:30)de2daa7f61b603fae838675c08883d872a9392eb3e84cc5[30](https://github.com/kerwanp/notion-render/actions/runs/4874086636/jobs/8694558349#step:5:31)eed79a8c2786d69c2798b8351fc0bd584f41a8d550#npm:0.3.1 (via /home/runner/work/notion-render/notion-render/.yarn/__virtual__/next-contentlayer-virtual-9ee7926468/0/cache/next-contentlayer-npm-0.3.1-3684bca467-c18922951a.zip/node_modules/next-contentlayer/dist/)
docs:build:
docs:build: Require stack:
docs:build: - /home/runner/work/notion-render/notion-render/.yarn/__virtual__/next-contentlayer-virtual-9ee7926468/0/cache/next-contentlayer-npm-0.3.1-3684bca467-c18922951a.zip/node_modules/next-contentlayer/dist/check-constraints.js
docs:build:     at require$$0.Module._resolveFilename (/home/runner/work/notion-render/notion-render/.pnp.cjs:20868:13)
docs:build:     at /home/runner/work/notion-render/notion-render/.yarn/__virtual__/next-virtual-fcd7735f2b/0/cache/next-npm-13.3.4-25a697b4ce-ed3a2e39a2.zip/node_modules/next/dist/server/require-hook.js:108:36
docs:build:     at require$$0.Module._load (/home/runner/work/notion-render/notion-render/.pnp.cjs:20718:42)
docs:build:     at Module.require (node:internal/modules/cjs/loader:1141:19)
docs:build:     at require (node:internal/modules/cjs/helpers:110:18)
docs:build:     at getPackageVersion (file:///home/runner/work/notion-render/notion-render/.yarn/__virtual__/next-contentlayer-virtual-9ee7926468/0/cache/next-contentlayer-npm-0.3.1-3684bca467-c18922951a.zip/node_modules/next-contentlayer/dist/check-constraints.js:27:44)
docs:build:     at checkContentlayerVersionsMatch (file:///home/runner/work/notion-render/notion-render/.yarn/__virtual__/next-contentlayer-virtual-9ee7926468/0/cache/next-contentlayer-npm-0.3.1-3684bca467-c18922951a.zip/node_modules/next-contentlayer/dist/check-constraints.js:16:33)
docs:build:     at checkConstraints (file:///home/runner/work/notion-render/notion-render/.yarn/__virtual__/next-contentlayer-virtual-9ee7926468/0/cache/next-contentlayer-npm-0.3.1-3684bca467-c18922951a.zip/node_modules/next-contentlayer/dist/check-constraints.js:4:5)
docs:build:     at Object.redirects (/home/runner/work/notion-render/notion-render/.yarn/__virtual__/next-contentlayer-virtual-9ee7926468/0/cache/next-contentlayer-npm-0.3.1-3684bca467-c18922951a.zip/node_modules/next-contentlayer/dist/index-cjs.cjs:[31](https://github.com/kerwanp/notion-render/actions/runs/4874086636/jobs/8694558349#step:5:32):17)
docs:build:     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
docs:build: ERROR: command finished with error: command (/home/runner/work/notion-render/notion-render/apps/docs) yarn run build exited (1)

Thanks for opening this issue. Can you please provide minimal a reproduction repo with instructions how to reproduce the problem you're experiencing? Thank you!

I encountered this issue when working on the @notion-render documentation: https://github.com/kerwanp/notion-render
You can reproduce by removing thoses lines from the .yarnrc.yml https://github.com/kerwanp/notion-render/blob/d5107bf20244d355e193d2ed914839d65c74e29c/.yarnrc.yml#LL1C1-L5C1

This should be addressed with the 0.3.4 release. 🎉


Generated crates suggest to use deprecated aws_config::load_from_env

Describe the issue
https://docs.rs/aws-sdk-appconfigdata/latest/aws_sdk_appconfigdata/client/index.html
Suggests the following:
let config = aws_config::load_from_env().await;
let client = aws_sdk_appconfigdata::Client::new(&config);

Not sure if this was intentional, but load_from_env is deprecated by default (behavior-version-latest disabled by default). The documentation should change to suggest construction like so:
let config = aws_config::load_from_env().await;
let client = aws_sdk_appconfigdata::Client::new(&config);

Alternative the doc could inform users the feature flag is required to make the example work.
Links
https://docs.rs/aws-sdk-appconfigdata/latest/aws_sdk_appconfigdata/client/index.html
https://docs.rs/aws-config/1.1.7/aws_config/fn.load_from_env.html

Thanks for filing this. I think we just need to switch it over to calling load_defaults with BehaviorVersion::latest() instead.


[utils] Adjust logic in clear-container-cache. factoryCache -> factoryManagerCache

This change should fix things related to https://github.com/toranb/ember-cli-hot-loader/issues/48 for now, at least based on testing I have done with a vanilla CLI app.
We should all organize and have a discussion about the future of Ember's component and component manager interfaces so that eventually this addon can rely on public APIs instead of private ones. cc @toranb @MiguelMadero
See comments here for more on this topic.
Also: https://github.com/emberjs/ember.js/issues/15057

Looks like tests have failed. Is there a good way I can run them locally to fix things up?

@alexhancock I've thrown up another PR that solves this build issue for everything except ember 1.13 (ember-try issue atm). Asked @MiguelMadero to give it a look before we merge tomorrow

@alexhancock huge huge thank you! Not sure why I never tried the cache factory clear like you did here! So thankful for your time and involvement today! I'll likely close out this PR (if that's cool w/ you) and ask that either you take credit in PR #52  or re-do that PR (after we make a decision on the ember 1.13 ember-try config). I'm not looking for credit/glory here but do think we need that ember-cli upgrade
Just let me know how you want to proceed later in the week

@toranb No problem! Happy to just close this one in favor of that! In terms of credit, maybe you could just @ mention me in the commit message, but anything is fine really.
I will keep an eye on that change to see what the fix for the ENV issues ends up being.
Thanks!

Closing in favor of https://github.com/toranb/ember-cli-hot-loader/pull/52


ls

Expected Behavior

Current Behavior

Steps to Reproduce (for bugs)

Versions

Homebridge: homebridge --version
Node:       node --version
OS:

Configuration

Homebridge Log / Command Output

???


Update Blog “assessing-the-impact-of-state-policies-on-us-life-expectancy-trends”

Automatically generated by Netlify CMS

👷 Deploy Preview for koytak processing.

Name
Link

🔨 Latest commit
3f657caacae0455b0d3c5fbfd8901beee0581f32

🔍 Latest deploy log
https://app.netlify.com/sites/koytak/deploys/653741688d794e00080c346a


Added WithStepsReversed LineType

Type of PR: enhancement
PR checklist:

[ ] Addresses an existing issue: fixes #
[x] Includes tests
[ ] Documentation update

Overview of change:
Changes these steps:

To these:

Is there anything you'd like reviewers to focus on?
Allows for creating depth charts

I was unsure about the naming and am more then happy to change it.

It seems that this implementation is related to https://github.com/tradingview/lightweight-charts/issues/195#issuecomment-1009096133, thus @0xAozora would you mind to:

create an issue first with the description what you'd like to get in the end and why
provide a few more examples

Re to the issue, I think it shouldn't different type of line but another option for line chart where to align the step of step line. And bunch of graphic tests is required here for sure (especially for coloring steps with different colors).


add_validation_block_in_ocp_version

Description
Add validation block on ocp_version variable
issue:  https://github.com/terraform-ibm-modules/terraform-ibm-base-ocp-vpc/issues/63
No release required

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

Release required

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

Release notes content
Replace this text with information that users need to know about the bug fixes, features, and breaking changes. This information helps the merger write the commit message that is published in the release notes for the module.

Checklist for reviewers

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

Merge actions for mergers

Merge by using "Squash and merge".

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

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


Stack corruption on arm64 when using DES methods

with the default build of the library, if you use DES methods on arm64, stack corruption will occur.
the reason is the definition of DES_LONG in opensslconf.h - the config header is taken from the first platform being built - x86_64 by default. for this platform however, DES_LONG is set to 'unsigned int', whereas for all other platforms it is set to 'unsigned long'.
thus you will be passing ints to a method that thinks it has longs it can write to.
to reproduce, run this on arm64:
DES_cblock key;
key[0] = 0x54; key[1] = 0x22; key[2] = 0x54; key[3] = 0x6a;
key[4] = 0x43; key[5] = 0x89; key[6] = 0xc8; key[7] = 0x66;

DES_key_schedule ks;
memset(&ks, 0, sizeof(ks));

uint8_t buf[200];
memset(buf, 0, 200);

DES_set_key_unchecked(&key, &ks);

for (int n = 0; n < 200; n++) {
    if (buf[n] != 0) {
        printf("stack corrupted!\n");
    }
}

Is this still open?

Quite sure it is, since it depends on PR #134.

Fixed by #142


removing webpack-command

In response to #2447
describe your changes...

[ ] Read and sign the CLA. PRs that haven't signed it won't be accepted.
[ ] Make sure your PR complies with the writer's guide.
[ ] Review the diff carefully as sometimes this can reveal issues.
Remove these instructions from your PR as they are for your eyes only.

Thanks!


SOLR-15853 Solr paramset impl

https://issues.apache.org/jira/browse/SOLR-15853
Description
A screen where paramset can be created has been added to the admin tool. You can set a new paramset on this screen and bring this paramset. When the get paramset button is pressed, you can see all the paramsets that this collection has. You can only display it by typing a paramset whose name you know in the input field.
In addition, a new section has been added to the query screen, enabling the use of the paramset desired to be used in this field. Multiple selection is also possible here. If you select the paramsets you want to use and say execute query, you will see that this paramset is added to the url as useParam=paramset_name and returns the correct results.
I applied the films example in this link to test it, it gave the expected results.
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.
[ ] I have added tests for my changes.
[ ] I have added documentation for the Reference Guide

You can also check this newly added feature from the screenshots I have added.

This is Super Exciting!    I am going to go through and test this, but probably not till Monday.
One thing is, I wonder, now that we are exposing this in the UI, I wonder if the best name is ParamSets?    I am going to start a thread on the Dev list about the name of this feature.   It may amount to some bikeshedding, or now may be the time to come up with a better name to describe configuring a Solr end point.

Of course, I think it would be useful to ask on the dev list and get
everyone's opinion to find the most suitable name.
Also, we can change the icon too :-)
Eric Pugh @.***>, 4 Şub 2022 Cum, 17:34 tarihinde şunu
yazdı:

This is Super Exciting! I am going to go through and test this, but
probably not till Monday.
One thing is, I wonder, now that we are exposing this in the UI, I wonder
if the best name is ParamSets? I am going to start a thread on the Dev list
about the name of this feature. It may amount to some bikeshedding, or now
may be the time to come up with a better name to describe configuring a
Solr end point.
—
Reply to this email directly, view it on GitHub
https://github.com/apache/solr/pull/594#issuecomment-1030043563, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AKSKE2HL4EK7RHB6ZCRQSCDUZPPWHANCNFSM5NRXL3UQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

looks like angular-ui-select is also either based or inspired by selectize.js!

is package.json actually integrated into the build?  I think we've never had one before...

hey! I deleted package.json and package-lock.json. They are not related with the improvement, I just added while I was trying some things :) And I didn't send the improvement on paramset screen yet. I'll send it in some hours, I am just checking and doing final touches. Sorry for late reply it's just 3 am in the morning in turkey :) I am excited for the results!!

Improvement done. It works correctly according to my tests. Instead of copying the placeholder, it made more sense to show a sample json and have it copied...
On the query screen, you can change the order of paramsets by drag&drop. And it goes directly to the UI with the chosen order.

I don't have comments on the functionality of this. I think there is one existing review comment not addressed.
#745 and this PR both try to pull in a UI framework for selection. @epugh did you get to see which one is better to go with?
I also saw @epugh left a video comment in https://issues.apache.org/jira/browse/SOLR-15853?focusedCommentId=17491578&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17491578 - I didn't watch it but it seems like @epugh would be a good one to take another look.

I just deleted the comment. @epugh maybe you can give another look at the code!

I did a bunch of work, but for some reason couldn't push to the existing branch, so I had to create a new pull request at https://github.com/apache/solr/pull/923, so closing this one in favour of the new one!


implementing cards

i makde css for cards...
can see a demo of these cards at the use base_url('/Welcome/cardtest')
revised MY_Controller things use base_url

has meed manually merged through command line


ENH: reduce sizeof(NI_WatershedElement) by 20%

On 64-bit platform, the NI_WatershedElement structure size can be reduced from 40 to 32 bytes by rearranging the fields according to their sizes in decreasing order.
See https://www.viva64.com/en/w/v802/

Interesting, learned something. This is a more extensive explanation: http://www.catb.org/esr/structure-packing/
Thanks @cgohlke


Add positive test cases for arrays

Purpose

$subject. Adding some of the unit tests I missed earlier

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@35aad66). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #14396   +/-   ##
=========================================
  Coverage          ?   64.26%
  Complexity        ?      425
=========================================
  Files             ?     2187
  Lines             ?    96929
  Branches          ?    12964
=========================================
  Hits              ?    62296
  Misses            ?    29672
  Partials          ?     4961

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 35aad66...b75ccf5. Read the comment docs.


Skynet  Integration

Make example with skynet integration.

Nice suggestion; great to have on Celo Sage or Celo Examples, not on Celo Composer.
Closing issue.


Console app Build related property pages

Get the Build and Build events and Reference Paths pages up.
CSharp-ConsoleApplication

[ ]  Build Properties Page
[ ]  BuildEvent Properties Page
[ ]  ReferencesPath Properties Page

VB-ConsoleApplication

[ ] Compile Properties Page
[ ] References Properties Page

Pending List

[ ]  Build Properties Advance Page: CheckForOverflowUnderflow
[ ]  References Page: Implement GetCurrentImportsList()
[ ]  References Page: Add Service Reference not working


How to parse/change "Additional Email Recipients" with PowerShell

Hi,
We manage lots of tenants on behalf of our clients, how can we parse or change the 'Additional Email Recipients' for Azure AD Connect via PowerShell rather than the GUI console?

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

ID: 35b52f01-3dee-6d41-f9f6-7710e461ffeb
Version Independent ID: c8ef08a8-d503-b52f-9de8-21b13cfa3d72
Content: Azure Active Directory Connect Health operations
Content Source: articles/active-directory/hybrid/how-to-connect-health-operations.md
Service: active-directory
GitHub Login: @zhiweiwangmsft
Microsoft Alias: billmath

@Kav7, Thanks for the question! We are taking a look into this and will get back to you soon.

@Kav7 I checked this in my lab and currently we do not have an powershell command to parse or change "additional email recipients" for Azure AD connect. The Additional Email recipient setting currently seems available through azure portal only. While I understand that from a IT governance perspective , powershell would have been a better solution , however I would suggest to use a group DL and set that up for the tenants that you manage . And then you can add or remove users within that DL without an issue using powershell.  I hope this solution will work in your case where you have to manage multiple tenants. In case you would like to see this functionality I would suggest to open a feedback request on uservoice which can be voted by like minded customers and prioritized by Product managers accordingly. We will now close this issue. Should you have any further query, feel free to tag me to your reply .
Thank you.

Thanks for suggestion, however as mentioned we are an IT service provider who manages lots of tenants on behalf of our tenants, we would have to set this up manually on each one - not ideal. I will submit via user voice. I thought Microsoft was all about 'Powershell First' approach? Anyway.


Android sometimes crashes on production with: undefined is not an object (evaluating 'this.map.setNativeProps')

Is this a bug report?
yes
Have you read the Installation Instructions?
yes
Environment
Please specify the react, react-native, react-native-maps versions, eg:
react-native: 0.55.4
react: 16.3.1
react-native-maps: 0.21.0

Steps to Reproduce
I got this map component:

const Map = class extends React.Component<Props, State> {
  state = {
    animatedRegion: new AnimatedRegion({
      ...DEFAULT_REGION,
    }),
  }

  componentDidMount() {
    this.animateToRegion(this.props.region || DEFAULT_REGION)
  }

  animateToRegion(region) {
    this.state.animatedRegion
      .timing({
        duration: 1000,
        latitudeDelta: LATITUDE_DELTA,
        longitudeDelta: LONGITUDE_DELTA,
        ...region,
      })
      .start()
  }

  componentDidUpdate(oldProps) {
    const newRegion = this.props.region || DEFAULT_REGION
    if (oldProps.region !== newRegion) {
      this.animateToRegion(newRegion)
    }
  }
  onRegionChange = region => {
    this.state.animatedRegion.setValue(region)
  }

  render() {
    const {
      style,
      coordinates,
      theme,
      strokeColor,
      strokeWidth = STROKE_WIDTH,
    } = this.props
    return (
      <Container style={style}>
        <StyledMap
          onRegionChange={this.onRegionChange}
          region={this.state.animatedRegion}
        >
          {coordinates &&
            coordinates.length > 0 && (
              <Polyline
                coordinates={coordinates}
                strokeColor={strokeColor || theme.colors.primary}
                strokeWidth={strokeWidth}
              />
            )}
          {coordinates && coordinates.length > 0 ? (
            <Marker coordinate={first(coordinates)}>
              <StartPoint />
            </Marker>
          ) : null}
          {coordinates && coordinates.length > 1 ? (
            <Marker coordinate={last(coordinates)}>
              <StartPoint />
            </Marker>
          ) : null}
        </StyledMap>
      </Container>
    )
  }
}

Expected Behavior
should not crash
Actual Behavior
works on both android and ios, but sometimes i get
undefined is not an object (evaluating 'this.map.setNativeProps') and the app crashes.
It looks like the this.map is not set, which would contain the ref, but i am not sure when this can happend and how i can guard it

Hi there! I was coming to report the same issue. I've an app in production and this crash happens for a small percentage of users: multiple android versions (6,7,8 and 8.1) and multiple devices (Pixel XL, Samsung's, LG's, Huwaei). If I can help with something just say. I've the same environment.

@macrozone did you manage to fix this?

What's StyledMap ? I think there is the problem as I don't see in your code anything related to the code it crashes on.

@rborn ah sorry, that's just a styled map via styled components:
import { Animated } from 'react-native-maps'
import styled from 'styled-components'

//

const StyledMap = styled(Animated)`
  flex: 1;
`

@pedrolopes10 actually yes:
The problem may happen in
 componentDidMount() {
    this.animateToRegion(this.props.region || DEFAULT_REGION)
  }

you can change this with:
 onMapReady = () => {
    this.animateToRegion(this.props.region || DEFAULT_REGION)
  }

// in render:

 <Map
          onMapReady={this.onMapReady}

        >

@macrozone @pedrolopes10  oh, I'm blind - yes, you can call map methods ONLY after is ready, not after it mounted as the map has to do more stuff.

@rborn Can you point out what kind of props that should not be passed to the map before it is ready? I'm having a hard time figuring out which props I define that cause the error.

@vanydeasy you can pass any prop to the map before is ready, you cannot act on them though until is ready. The most sensitive are the ones that make the map change the region/zoom etc as these are not available yet.

Guyssss, i'm still having problem, anyone still active on that issue 🥲