[ALLUXIO-2426] Try using authenticated and login user rules to deflake PermissionCheckTest

https://alluxio.atlassian.net/browse/ALLUXIO-2426
PermissionCheckTest  still fails but for verifySetAcl now. This PR continues cleaning up the code by replacing setting the singleton by using rules for authenticated and login user.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13554/Build result: FAILURE[...truncated 2498 lines...][JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/common/target/alluxio-core-server-common-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-core-server-common/1.5.0-SNAPSHOT/alluxio-core-server-common-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/common/target/alluxio-core-server-common-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-server-common/1.5.0-SNAPSHOT/alluxio-core-server-common-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/pom.xml to org.alluxio/alluxio-underfs-hdfs/1.5.0-SNAPSHOT/alluxio-underfs-hdfs-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-hdfs/1.5.0-SNAPSHOT/alluxio-underfs-hdfs-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-hdfs/1.5.0-SNAPSHOT/alluxio-underfs-hdfs-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/pom.xml to org.alluxio/alluxio-underfs-swift/1.5.0-SNAPSHOT/alluxio-underfs-swift-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-swift/1.5.0-SNAPSHOT/alluxio-underfs-swift-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/swift/target/alluxio-underfs-swift-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-swift/1.5.0-SNAPSHOT/alluxio-underfs-swift-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/examples/pom.xml to org.alluxio/alluxio-examples/1.5.0-SNAPSHOT/alluxio-examples-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/pom.xml to org.alluxio/alluxio-underfs-s3a/1.5.0-SNAPSHOT/alluxio-underfs-s3a-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/target/alluxio-underfs-s3a-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-s3a/1.5.0-SNAPSHOT/alluxio-underfs-s3a-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/s3a/target/alluxio-underfs-s3a-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-s3a/1.5.0-SNAPSHOT/alluxio-underfs-s3a-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/server/pom.xml to org.alluxio/alluxio-core-server/1.5.0-SNAPSHOT/alluxio-core-server-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/common/pom.xml to org.alluxio/alluxio-keyvalue-common/1.5.0-SNAPSHOT/alluxio-keyvalue-common-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/pom.xml to org.alluxio/alluxio-underfs/1.5.0-SNAPSHOT/alluxio-underfs-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/pom.xml to org.alluxio/alluxio-underfs-glusterfs/1.5.0-SNAPSHOT/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-underfs-glusterfs/1.5.0-SNAPSHOT/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/glusterfs/target/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-underfs-glusterfs/1.5.0-SNAPSHOT/alluxio-underfs-glusterfs-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/integration/pom.xml to org.alluxio/alluxio-integration/1.5.0-SNAPSHOT/alluxio-integration-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/protobuf/dependency-reduced-pom.xml to org.alluxio/alluxio-core-protobuf/1.5.0-SNAPSHOT/alluxio-core-protobuf-1.5.0-SNAPSHOT.pom[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/protobuf/target/alluxio-core-protobuf-1.5.0-SNAPSHOT.jar to org.alluxio/alluxio-core-protobuf/1.5.0-SNAPSHOT/alluxio-core-protobuf-1.5.0-SNAPSHOT.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/core/protobuf/target/alluxio-core-protobuf-1.5.0-SNAPSHOT-sources.jar to org.alluxio/alluxio-core-protobuf/1.5.0-SNAPSHOT/alluxio-core-protobuf-1.5.0-SNAPSHOT-sources.jar[JENKINS] Archiving /home/jenkins/workspace/Alluxio-Pull-Request-Builder/keyvalue/pom.xml to org.alluxio/alluxio-keyvalue/1.5.0-SNAPSHOT/alluxio-keyvalue-1.5.0-SNAPSHOT.pomchannel stopped
Test FAILed.

Merged build finished. Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13555/Build result: ABORTED[...truncated 891 lines...][INFO] [INFO] <<< maven-source-plugin:2.3:jar (attach-sources) @ alluxio-underfs-hdfs <<<[INFO] [INFO] --- maven-source-plugin:2.3:jar (attach-sources) @ alluxio-underfs-hdfs ---[INFO] Building jar: /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.5.0-SNAPSHOT-sources.jar[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: Invalid object ID 27 iota=41[INFO] [INFO] --- maven-javadoc-plugin:2.9:jar (attach-javadoc) @ alluxio-underfs-hdfs ---[INFO] Skipping javadoc generation[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: Invalid object ID 27 iota=41[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @ alluxio-underfs-hdfs ---[INFO] Installing /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.5.0-SNAPSHOT.jar to /home/jenkins/.m2/repository/org/alluxio/alluxio-underfs-hdfs/1.5.0-SNAPSHOT/alluxio-underfs-hdfs-1.5.0-SNAPSHOT.jar[INFO] Installing /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/pom.xml to /home/jenkins/.m2/repository/org/alluxio/alluxio-underfs-hdfs/1.5.0-SNAPSHOT/alluxio-underfs-hdfs-1.5.0-SNAPSHOT.pom[INFO] Installing /home/jenkins/workspace/Alluxio-Pull-Request-Builder/underfs/hdfs/target/alluxio-underfs-hdfs-1.5.0-SNAPSHOT-sources.jar to /home/jenkins/.m2/repository/org/alluxio/alluxio-underfs-hdfs/1.5.0-SNAPSHOT/alluxio-underfs-hdfs-1.5.0-SNAPSHOT-sources.jar[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: Invalid object ID 27 iota=41Build was aborted[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: Invalid object ID 27 iota=41channel stopped[WARNING] Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: hudson.remoting.Channel$OrderlyShutdown[INFO]                                                                         [INFO] ------------------------------------------------------------------------[INFO] Building Alluxio Under File System - Gluster FS 1.5.0-SNAPSHOT[INFO] ------------------------------------------------------------------------
Test FAILed.

Jenkins, test this please.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13559/Build result: ABORTED[...truncated 3785 lines...][INFO] Alluxio Core - Server ............................. SUCCESS [1.547s][INFO] Alluxio Core - Server - Common Utilities .......... SUCCESS [15.230s][INFO] Alluxio Core - Server - Master .................... SUCCESS [42.168s][INFO] Alluxio Core - Server - Proxy ..................... SUCCESS [11.014s][INFO] Alluxio Core - Server - Worker .................... SUCCESS [52.606s][INFO] Alluxio Key Value ................................. SUCCESS [1.529s][INFO] Alluxio Key Value - Common Utilities .............. SUCCESS [14.120s][INFO] Alluxio Key Value - Client ........................ SUCCESS [12.784s][INFO] Alluxio Key Value - Server ........................ SUCCESS [9.501s][INFO] Alluxio Shell ..................................... SUCCESS [11.853s][INFO] Alluxio Examples .................................. SUCCESS [11.269s][INFO] Alluxio MiniCluster ............................... SUCCESS [9.032s][INFO] Alluxio Tests ..................................... FAILURE [1:51:48.660s][INFO] Alluxio Integration ............................... SKIPPED[INFO] Alluxio Integration - Mesos ....................... SKIPPED[INFO] Alluxio Integration - YARN ........................ SKIPPED[INFO] Alluxio Assemblies ................................ SKIPPED[INFO] ------------------------------------------------------------------------[INFO] BUILD FAILURE[INFO] ------------------------------------------------------------------------[INFO] Total time: 1:59:51.032s[INFO] Finished at: Mon Feb 27 10:51:26 PST 2017[INFO] Final Memory: 92M/2322M[INFO] ------------------------------------------------------------------------
Test FAILed.

Jenkins, test this please

@apc999 left a couple of comments ... the test failure looks like a deadlock to me ... we should add a conservative timeout to each test (e.g. 120 seconds) to make sure we can identify the tests that hang

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13810/
Test PASSed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13811/
Test PASSed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13812/
Test PASSed.

@jsimsa @ifcharming  after I merged this PR with master, no failure is seen. I suspect the previous build issue is not introduced by this PR.
PTAL

Jenkins, test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13829/
Test FAILed.

Merged build finished. Test FAILed.

Jenkins, test this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/13848/
Test PASSed.

@ifcharming PTAL

@apc999 mostly LGTM, do we also need to update integration tests which set LoginUser and AuthenticatedUser ?

@ifcharming there is a follow up PR to further refactor and clean the tests
https://github.com/apc999/alluxio/pull/1/files
After this PR merged, I will re-direct that PR.

LGTM, thanks for the fix!


Comprehensive marble tests for zip

Match current RxJS unit tests with marble tests for zip
Should adhere to the guidelines in our contribution docs.

There are still a lot of tests missing to mirror from RxJS 4 (see https://github.com/Reactive-Extensions/RxJS/blob/master/tests/observable/zip.js), so I feel like assigning myself to this task, unless @adrianomelo plans to continue doing marble tests for this like he started with #407.
@blesh ?

@staltz,
To be honest, I wasn't expecting replicate all the tests from RxJS 4, but seems fair. I can do this mirroring of tests for zip.

Done in #429
I didn't added a failing test. Should I create a new issue?
There is a commit with this test at https://github.com/adrianomelo/RxJS-1/commit/169c05aba266298b8d13f1d8488a29f5d44ef674.

This should be closed.


Remove mandatory doc_type from metric_aggregation

Hello,
I want to create an alert based on metric_aggregation to alert me everytime logstash_delay gets higher than a given value. However, I have multiple values for doc_type. So I would like to know if it's possible to remove it as a mandatory argument.
Also, since I am using ES6, issue #1362 also affects me.

@Qmando @Dmitry1987 any news or workaround about it?

hey sorry I'm just a dude, not a maintainer :D  don't know why people are tagging me.
regarding doc_type probably only maintainers can know, sorry :)

Have you tried using wildcards or comma separated lists?

sorry @Dmitry1987, I assume that because I saw some people asking your help :smile:

@Qmando, I had try wildcards, and didn't worked, but not with comma separated. It worked. However, I have a lot of doc_type types...
Since ES is not using _type anymore, is there any big problem about removing it from alert definition?
https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-type-field.html

@Qmando any news about this subject? Would be great to have some feedback about this, if it is on your roadmap and, if yes, an ETA for this. Thanks


Flutter Web With Obfuscate, Sentry Performance (No Transaction)

Platform
Dart
Obfuscation
Enabled
Debug Info
Disabled
Doctor
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.10.6, on Microsoft Windows [Version 10.0.22621.2428], locale en-ID)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Professional 2022 17.6.5)
[√] Android Studio (version 2021.2)
[√] IntelliJ IDEA Ultimate Edition (version 2023.1)
[√] VS Code (version 1.82.2)
[√] Connected device (3 available)
[√] Network resources
Version
7.12.0
Steps to Reproduce

implement sentry_dio: ^7.12.0.
Setup for auto instrument

dio.addSentry();

SentryNavigatorObserver(
          setRouteNameAsTransaction: true,
        ),

Expected Result

There is transaction in performance tab

Actual Result

There is no transaction

Are you willing to submit a PR?
None

See docs:

The Dio integration starts a span out of the active span bound to the scope

that means if there is no active span Sentry will discard it.
From our Flutter example:
final transaction = Sentry.getSpan() ??
    Sentry.startTransaction(
      'dio-web-request2,
      'request',
      bindToScope: true,
    );
final span = transaction.startChild(
  'dio',
  description: 'desc',
);
Response<String>? response;
try {
  response = await dio.get<String>('https://flutter.dev/');
  span.status = const SpanStatus.ok();
} catch (exception, stackTrace) {
  span.throwable = exception;
  span.status = const SpanStatus.internalError();
  await Sentry.captureException(exception, stackTrace: stackTrace);
} finally {
  await span.finish();
}
await transaction.finish();

This isn't extra clear in the docs so that should definitely be improved.
Also I do notice that our navigation observer doesn't properly function with dialogs, that's something to investigate

so that means, flutter web cannot use auto instrument right?
This code works in flutter mobile without obfuscate

oke thankyou sir

@hendra61298 Did it work for you?


Legacy to standalone client migration

Description
First I want to say thanks to the developers of this project, I appreciate the direction the project is going.
We have a large API that is based entirely on path parameters, e.g. /pets/{petId}. A sample OpenAPI client can be found here, or here:
openapi: 3.0.0
info:
  title: Widget Service
  version: 0.0.0
tags: []
paths:
  /pets/{petId}:
    get:
      operationId: Pets_read
      parameters:
        - name: petId
          in: path
          required: true
          schema:
            type: integer
            format: int32
      responses:
        '200':
          description: The request has succeeded.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Pet'
components:
  schemas:
    Pet:
      type: object
      required:
        - petId
      properties:
        petId:
          type: integer
          format: int32

Suppose we have the following openapi-ts.config.ts :
export default defineConfig({
    client: "<my client>",
    input: "sample.yaml",
    output: {
        format: "prettier",
        path: "./app/api/client/",
        lint: "eslint"
    },
})

The generated code changes pretty significantly between the legacy fetch client and the current @hey-api/client-fetch client:
import { petsRead } from '~/api/client';

// with legacy `fetch`:
const pet = await petsRead({ petId: 1 });

// with current `@hey-api/client-fetch`:
const pet = await petsRead({ path: { petId: 1 }});

Note the extra path parameter here. Is there any way to avoid having to specify this on the modern fetch client? It's pretty verbose and clunky, since every single call requires { path: { ... } } now.

@mrlubos Probably 50ish endpoints, which is why I didn't just wrap it. If it was say five endpoints I'd just write some helper functions.

That's going to be tough. Maybe your API has an explicit requirement for path parameters only, but what if you were to add query parameters in the future? The return types are also different btw, it's not just pet. I'd say gradual migration is still the easiest option here https://heyapi.vercel.app/openapi-ts/migrating.html#useoptions-true, but if you have a proposal for functionality, let me know (there are certainly ways to get it working with path params only APIs)

I'd like to imagine it should be possible to semi-intelligently merge query/path parameters into one blob; that is, suppose we had:
export type PetsReadData = {
  path: {
    petId: number;
  };
  query: {
    full: boolean;
  };
};

It could be entirely possible to merge these into one options object:
export type MergedData = {
  petId: number;
  full: boolean;
};

If there's a name collision then... 🤷 ? Emit a warning? Fail? Not sure. Another option could be added to either merge or separate path/query param objects.

You described it perfectly in the last sentence. I will close this issue for now, but if anyone thinks there's a viable approach we should consider, we can re-open.

And I'm bringing it back. I think resolving https://github.com/hey-api/openapi-ts/issues/558 correctly will unblock this issue

Might need to handle useOptions=false in this release too


Grid not working

I try to implement Row and Col elements.
First Question: Is there a difference between Col and Column and which one should I use?
As soon as I insert a Row element I get the following errors:
Warning: React.createElement: type should not be null, undefined, boolean, or number. It should be a string (for DOM elements) or a ReactClass (for composite components). Check the render method of "XXXPage".
Uncaught Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined. Check the render method of "XXXPage".
Uncaught Error: fail to get ".page__content" element.
Do not hesitate to ask for more Information.

Oh its an error, please look at Col and Row. Check out the repo demo folder
On Thursday, 12 May 2016, jonas-arkulpa<EMAIL_ADDRESS>wrote:

I try to implement Row and Col elements.
First Question: Is there a difference between Col
https://onsen.io/v2/docs/react/Col.html and Column
https://onsen.io/v2/docs/react/Column.html and which one should I use?
As soon as I insert a Row element I get the following errors:
Warning: React.createElement: type should not be null, undefined, boolean,
or number. It should be a string (for DOM elements) or a ReactClass (for
composite components). Check the render method of "XXXPage".
Uncaught Invariant Violation: Element type is invalid: expected a string
(for built-in components) or a class/function (for composite components)
but got: undefined. Check the render method of "XXXPage".
Uncaught Error: fail to get ".page__content" element.
Do not hesitate to ask for more Information.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/OnsenUI/react-onsenui/issues/25

@jonas-arkulpa probably you need to put it inside a page.

Have a look here https://github.com/OnsenUI/react-onsenui/blob/master/demo/examples/RowColumn.js

@philolo1 I do it exactly the same as explained in your example link.
It is already in a page element.

@jonas-arkulpa I think the website was updated before the actual version was released on npm.
It looks from your error that Row or Col is undefined so I think the reason is that you are using the previous version.
Try updating to the latest version and it should work. This component was added earlier today ;)

I made an example on Codepen and it looks like there is no problem in the latest version:
https://codepen.io/onsen/pen/aNMgVR

@argelius I updated from 0.2.5 to 0.2.6 and now it's working correct.
Thanks for your help.

@jonas-arkulpa Glad to be able to help! :+1:


Incorrect use in Zend_Mvc Quickstart

Reviewed, merged, and pushed to master --- thanks for the catch!


containerName parameter missing when processing storage blob

Configuration
title: Storage.Blobs
require:
- $(this-folder)/../readme.samples.md
- https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/storage/Azure.Storage.Blobs/swagger/readme.md
namespace: Azure.Storage.Blobs

Code model
- !<!Parameter> &ref_142
  schema: *ref_6
  implementation: Client
  required: true
  extensions:
    x-az-trace: true
    x-ms-priority: 0
    x-ms-skip-url-encoding: true
  language: !<!Languages>
    default:
      name: url
      description: 'The URL of the service account, container, or blob that is the targe of the desired operation.'
      serializedName: url
  protocol: !<!Protocols>
    http: !<!HttpParameter>
      in: uri

- !<!Parameter> &ref_146
  schema: *ref_13
  implementation: Client
  required: true
  extensions:
    x-ms-priority: 1
  language: !<!Languages>
    default:
      name: x-ms-version
      description: Specifies the version of the operation to use for this request.
      serializedName: x-ms-version
  protocol: !<!Protocols>
    http: !<!HttpParameter>
      in: header

  request: !<!Request>
      parameters:
      - *ref_142
      - !<!Parameter>
        schema: *ref_196
        implementation: Method
        required: true
        language: !<!Languages>
          default:
            name: comp
            description: MISSING·PARAMETER-DESCRIPTION
            serializedName: comp
        protocol: !<!Protocols>
          http: !<!HttpParameter>
            in: query
      - !<!Parameter>
        schema: *ref_145
        implementation: Method
        language: !<!Languages>
          default:
            name: timeout
            description: >-
              The timeout parameter is expressed in seconds. For more information, see Setting Timeouts for Blob
              Service Operations.
            serializedName: timeout
        protocol: !<!Protocols>
          http: !<!HttpParameter>
            in: query
      - *ref_146
      - !<!Parameter>
        schema: *ref_13
        implementation: Method
        language: !<!Languages>
          default:
            name: x-ms-client-request-id
            description: 'Provides a client-generated, opaque value with a 1 KB character limit that is recorded in the analytics logs when storage analytics logging is enabled.'
            serializedName: x-ms-client-request-id
        protocol: !<!Protocols>
          http: !<!HttpParameter>
            in: header
      language: !<!Languages>
        default:
          name: ''
          description: ''
      protocol: !<!Protocols>
        http: !<!HttpRequest>
          path: '/{containerName}/{blob}'
          method: put
          uri: '{url}'

Ok, I'm a bit confused here.
I see the operation in the source file:
https://github.com/Azure/azure-rest-api-specs/blob/12ff3b96ec4ede0a56a7315bcdaefe9ae8aa9168/specification/storage/data-plane/Microsoft.BlobStorage/preview/2019-02-02/blob.json#L2708-L3194
But I don't see a parameter for containerName  in the declared parameters.

Should the modeler error out for this situation?

Perhaps we should add a check for such a case to the (new linter) when we build that. I just hope that {...} isn't in an PATH somewhere.
It does require us to actually parse every PATH and see if it has things that look like parameters, and produce errors or warnings on that.

add to linting support:
https://github.com/Azure/autorest/issues/3359


Detect factory reset after deep sleep (IDFGH-1536)

Environment
Development Kit: Lolin32
Kit version
Module or chip used: ESP32-WROOM-32D
IDF version: v3.3-beta1-849-g630ffde6b
Build System: Make
Compiler version: crosstool-ng-1.22.0-80-g6c4433a5
Operating System: Windows
Power Supply: USB

Problem Description
If the factory reset gpio is asserted while booting from deep-sleep then the application is started with a possibly incorrect state because of preserved RTC memory but possibly different boot image and gone nvs and assumption that the firmware running before deep-sleep was the same.
Expected Behavior
One of three things:

The boot loader should do a clean restart after a factory reset during deep-sleep wake up
Or The factory reset should happen only on POWERON_RESET
Or The IDF gives us a way to detect that a factory reset just occurred

Actual Behavior
The application boots thinking it just woke from normal deep sleep and assumes its RTC variables and previous boot image are the same.
Steps to repropduce

Set factory reset gpio to 15
Set gpio 15 as a wake up source for deep sleep
Go to deep sleep
Hold gpio 15

Code to reproduce this issue

Debug Logs

Other items if possible

Good suggestion.  How about something like
#ifdef CONFIG_BOOTLOADER_OTA_DATA_ERASE
    RESET_REASON rst_res = rtc_get_reset_reason(0);
    uint32_t is_rev0 = (GET_PERI_REG_BITS2(EFUSE_BLK0_RDATA3_REG, 1, 15) == 0);
    if(rst_res == POWERON_RESET || (is_rev0 && rst_res == RTCWDT_RTC_RESET))
        ota_data_erase = true;
#endif

@negativekelvin That seems reasonable and the safest option.
Thank you for your code, I will use it for my current project and I hope that it eventually makes its way in esp-idf!


signaturehelper could handle rest union type.

Fixes #39227

I am so sorry for this (normally I'd review and iterate on this to merge it); but I've put up https://github.com/microsoft/TypeScript/pull/39317 with a more minimal change (as the change required to fix the bug really is quite small) - I already had it ready and didn't see someone'd already put up another PR to work on the bug until I went to post the PR. The approach is a little different than the one taken here.

@weswigham Oh, I jsut see your fix throgh the notification, and I also think it is better~


Load ViT Model in clip-training

Hello, @revantteotia ~
I would like to use your great code to train my dataset, but I want to load ViT-B/32 Model. I see you have finished the code of VisualTransformer, but I have a little question about the parameter--vision_patch_size.
I read other ViT model code which set patch_size = 32 when the image resolution is 224, so I want to ask if the 32 is right in model_config.yaml if my image_resolution is 224.

I got it! It's 32.


Enhance the instrumentation-http hooks or add new ones to allow users to add their own attributes to the server and client metrics

NB: Before opening a feature request against this repo, consider whether the feature should/could be implemented in the other OpenTelemetry client libraries. If so, please open an issue on opentelemetry-specification first.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
This is related to https://github.com/open-telemetry/opentelemetry-js/issues/3683.
Our need is to add extra attributes to the http_server and http_client metrics provided by the HTTP instrumentation.
That's not actually possible because of this https://github.com/open-telemetry/opentelemetry-js/issues/3683#issuecomment-1477373472.
Ideally we would use the requestHook https://open-telemetry.github.io/opentelemetry-js/interfaces/_opentelemetry_instrumentation_http.HttpInstrumentationConfig.html#requestHook to inject custom attributes to those metrics, but any additional hook would work as far as we can add additional attributes to http server and client duration metrics.
Describe alternatives you've considered
The alternative is actually using the instrumentation-express, which adds the http_route to the server metric. However, we have the need to add additional custom attributes to both, server and client metrics.
Additional context
Add any other context or screenshots about the feature request here.

I have also run into this issue of missing http_route attribute on the http_server_duration metric.
I want to only export metrics and if traces export is disabled OTEL_TRACES_EXPORTER: none then express instrumentation actually doesn't work - http_route attribute is not added to the http_server_duration metric.
Looks like a bug considering the similar setup (exporting only metrics) e.g. in Java instrumentation adds http_route to the http_server_duration metric.
@pichlermarc Not sure if it's worth raising a bug or if we get this feature-request fulfilled then it could help to workaround it?

I have also run into this issue of missing http_route attribute on the http_server_duration metric. I want to only export metrics and if traces export is disabled OTEL_TRACES_EXPORTER: none then express instrumentation actually doesn't work - http_route attribute is not added to the http_server_duration metric. Looks like a bug considering the similar setup (exporting only metrics) e.g. in Java instrumentation adds http_route to the http_server_duration metric.

@mivanilov I can see that this wouldn't work when tracing is disabled, as the info is passed around on the context :thinking:

@pichlermarc Not sure if it's worth raising a bug or if we get this feature-request fulfilled then it could help to workaround it?

It's worth opening a bug issue for this. If you can, please also include a minimal reproducer.

Is this being looked at? Looks like https://github.com/maciejnawrocki/opentelemetry-js/pull/1 would solve this?

@JohanBjoerklund I couldn't find this PR on this repo, it looks like this PR is not for this repo but their fork of it. :thinking:

@pichlermarc, is this being looked at? Can we have a final word of whether it will be implemented?

@mkrudele it's a very complex question. I opened another issue (#5051) to collect my thoughts and other requests in a single place. I raised actually this question last week with the other maintainers as it tends to be a recurring theme, but I was lacking enough research about previous requests.
I put all of this research now into #5051. Long story short: if we make the decision to add it we will have to reach out to the SemConv SIG first. We also need to implement two other things before we can add the feature (memory limiting for attributes, not exporting metrics that have not been written in the collection timeframe) to guard users who may misuse the API due to an unfamiliarity with how metrics work.
I'll bring it up again with the other maintainers this week. I've also reached out to a maintainer from the SemConv SIG to discuss the topic.

Hi all - I'm closing this request in favor of #5051 - this does NOT mean that the request is rejected. I'm just trying to move all requests to that new, more comprehensive tracking issue (there's currently a lot of duplicates of this issue floating around).
I took quite a bit of time summarizing everything on #5051. I also reached out to the semantic conventions SIG to see if this would even be allowed. They are now adding a clarifying text that this is an okay feature to add. Also the .NET SIG currently offers a similar feature already in the ASP.NET Core instrumentation, so we've covered our bases on that side.
We, as the maintainers group have not made a decision yet if we want to add this, but I'll continue to bring this up in discussions with the rest of the maintainers. In one of these conversations, @dyladan came up with an idea on how we could make that API a bit safer to use, so I've attached that proposed API to #5051
In any case: if we decide to implement this feature request we will have to implement #4095 and #4096 as safeguards first. I'll continue bringing this up in regular meetings until we have a decision on this - please keep in mind that since this is a feature request we'll continue to prioritize other topics such as bugfixes and reducing technical debt over adding this feature.


Standardize/optimize telemetry broadcasts for GUI

Now that we have a GUI, telemetry broadcasts should use a standardized system for sorting and sending data. Data should be sent as an array with the first element indicating datatype. Some examples: [0, 43.6] translates to Altitude: 43.6 meters. [2, 0.02, 0.15, 3.42] translates to Acceleration: {X: 0.02G, Y: 0.15G, Z: 3.42G}. [5, 250] translates to Calibrating gyroscope, time remaining: 4m,10s.

Check UI spec sheet for standard parameters

completed with #142 and #134


Can I join the project?

I'm intrested in maitaining and join this project.
Where can I get more information about this project

please join slack channel at https://quarkcoin.slack.com and meet dev team for more info.
see aslo:
https://bitcointalk.org/index.php?topic=2042673.0


Fasten in cpu

It is laggy in cpu. how can I optimize it?

You might need a Nvidia GPU that supports CUDA to run in realtime. For CPU, check if Tensorflow provides any optimization for it. And of course you can reduce the input image size or train a smaller model by yourself to get a speedup.

Can you please tell me how I can train my own model?

hi !
thanks for your work！
can you tell me what kind of data you used for training?

@Zumbalamambo
You need to feed placeholder with "input image", "center map", "joint heat map", please read the paper for more detail. I will release my training script after some refactors.
@justinluyao
I manually labeled thousands of images with 2D joint locations, and generate some 3D model images from LibHand. If you find publicly available dataset please let me know too.

do you mean you generate the hand images with LibHand and label the joints positions on the generated images by yourself?

LibHand can not only generate images but also with joints labels, by projecting 3D model joints onto 2D image spaces.

@timctho Hi timctho, thanking for you sharing of your project. I am doing my training with it. However I have some confusion about it, could you please do me a favor?

Need I feed background channel? cause I noticed that shihenw uses 4th channel which represents the background, and its values are all 0. actually I don't know why need to do this.  While in your project, the input image still have 3 channels, right? and I just need to generate background heatmap, then the total number of groundtruth heatmap is (nun_of_joints + 1), am i right?
The center of center_map is the center of torsobox, right?  but what is the sigma of it , how can I determine it?

Thank you very much!

1.For original CPM paper I think the input image only have rgb channels.
And yes you need to generate the background heatmap which is complement to
all the joint heatmaps.
2.Yes. In hand project, I remember the sigma is 7 or nearby. You can play
with it a little, while I find out little difference.
Best wishes,
Tim Ho (何哲廷)
On Mon, May 21, 2018 at 10:56 AM, sarahzhouUestc<EMAIL_ADDRESS>wrote:

@timctho https://github.com/timctho Hi timctho, thanking for you
sharing of your project. I am doing my training with it. However I have
some confusion about it, could you please do me a favor?

Need I feed background channel? cause I noticed that shihenw uses
4th channel which represents the background, and its values are all 0.
actually I don't know why need to do this. While in your project, the input
image still have 3 channels, right? and I just need to generate background
heatmap, then the total number of groundtruth heatmap is (nun_of_joints +
1), am i right?
The center of center_map is the center of torsobox, right? but what
is the sigma of it , how can I determine it?

Thank you very much!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/timctho/convolutional-pose-machines-tensorflow/issues/1#issuecomment-390540102,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFYMF0tOg8HVhoVIMUaEbbW_z_XJvd_rks5t0izigaJpZM4OuWRo
.


Dockerfile: Bump base image

Bump base image version to:
registry.access.redhat.com/ubi9/ubi-minimal:9.4-1194.

Tested against an OpenShift Virtualization 4.17 cluster.


Add support fot https

Great, great job with lib! Do you think you could add support for https? Currently, the calls to API are hardcoded to http in https://github.com/stuartmccoll/gitlab-changelog-generator/blob/master/changelog_generator/calls.py

Thanks for raising this - I'll take a look 👍.


md-select has to be .two-way bound explicitly

Although md-select is configured this way:
@bindable({
    defaultBindingMode: bindingMode.twoWay
  }) selected;

It seems like selected still needs to be bound .two-way explicitly to work correctly:
<select multiple md-select="selected.bind: selectedValues;">

does not update selectedValues while the following does:
<select multiple md-select="selected.two-way: selectedValues;">

https://github.com/aurelia/templating/issues/253?

That was fast. Very nice! :smile:
Thanks for linking.

Can you fork that plunker, and use <select> instead of <input>? If that doesnt work either, you should mention that in the issue

Sure, will do that later.

tbh I am not sure if this really shows the issue:
http://plnkr.co/edit/g2i582ZL29bhLEiXobhG?p=preview
Could you take a quick look before I post it to aurelia/templating?

http://plnkr.co/edit/UjmWYHElE4l09lyyQT29?p=preview
or
http://plnkr.co/edit/pQBcziEVQsf5wHJl1Qti?p=preview

http://plnkr.co/edit/pQBcziEVQsf5wHJl1Qti?p=preview
I knew I forgot something. :smile:

:)

Aurelia has been fixed :)


BigQuery: How to use runQuery by dryRun

$bigQuery = new BigQueryClient([
'projectId' => 'projectId',
]);
$queryResults = $bigQuery->runQuery(
'SELECT COUNT(id) FROM [table]',
['useLegacySql' => true]
);

OK!

$bigQuery = new BigQueryClient([
'projectId' => 'projectId',
]);
$queryResults = $bigQuery->runQuery(
'SELECT COUNT(id) FROM [table]',
['dryRun' => true]
);

error

Undefined index: jobId

dryRun supported?

Thanks for the report @YuK1Game, this seems like something we should be able to support.

Closed by #686.


Events are passed inside modal with another DnD lib.

Thanks for submitting an issue to RGL!
Please mark the type of this issue:

[X] Bug
[ ] Feature Request
[ ] Question

If you have a question or bug report, please use the WebpackBin Template
to demonstrate. It is much easier for us to help you if you do.
Hey,
I've experienced the bug shown on the video. It doesn't happen when using versions below 0.15.0 (eg. on 0.14.6 it works great). In the modal I'm using react-dnd lib with HTML5-backend. Is it possible that events from react-dnd are seen by RGL?

same issue

set props isDraggable={!this.state.openModal}

sam this issue.
try set props isDraggable={!this.state.openModal} but this event reRender grid item and remove modal

same problem with MUI Dialog. react-grid-layout "locks" the mouse after click on item.

same problem with MUI Dialog. react-grid-layout "locks" the mouse after click on item.

@fro3clr Did you find a workaround for this?


Update drive-stats.json

Fix for #1383 as reporting shouldn't use positions due to # of rows causes slowness.

Closing for now due to your find that drives dont match positions all the time.


Differences between here and ARPABET

According to http://www.speech.cs.cmu.edu/cgi-bin/cmudict#about, the CMU dictionary uses 2-letter ARPABET notation for representing sounds.
According to the wikipedia page for ARPABET (pointed to as the reference for translating to IPA on the above CMU page), the IPA correspondances would be (lowercased):
CMU_TO_IPA = {
    'aa'       : 'ɑ',   # balm, bot
    'ae'       : 'æ',   # bat
    'ah'       : 'ʌ',   # butt
    'ao'       : 'ɔ',   # story
    'aw'       : 'aʊ',  # bout
    'ax'       : 'ə',   # comma
    'axr'      : 'ɚ',   # letter
    'ay'       : 'aɪ',  # bite
    'eh'       : 'ɛ',   # bet
    'er'       : 'ɝ',   # bird
    'ey'       : 'eɪ',  # bait
    'ih'       : 'ɪ',   # bit
    'ix'       : 'ɨ',   # roses, rabbit
    'iy'       : 'i',   # beat
    'ow'       : 'oʊ',  # boat
    'oy'       : 'ɔɪ',  # boy
    'uh'       : 'ʊ',   # book
    'uw'       : 'u',   # boot
    'ux'       : 'ʉ',   # dude

    'b'        : 'b',   # buy
    'ch'       : 'tʃ',  # China
    'd'        : 'd',   # die
    'dh'       : 'ð',   # thy
    'dx'       : 'ɾ',   # butter
    'el'       : 'l̩',   # bottle
    'em'       : 'm̩',   # rhythm
    'en'       : 'n̩',   # button
    'f'        : 'f',   # fight
    'g'        : 'ɡ',   # guy
    'hh'       : 'h',   # high
    'h'        : 'h',   # high
    'jh'       : 'dʒ',  # jive
    'k'        : 'k',   # kite
    'l'        : 'l',   # lie
    'm'        : 'm',   # my
    'n'        : 'n',   # nigh
    'ng'       : 'ŋ',   # sing
    'nx'       : 'ɾ̃',   # winner
    'p'        : 'p',   # pie
    'q'        : 'ʔ',   # uh-oh
    'r'        : 'ɹ',   # rye
    's'        : 's',   # sigh
    'sh'       : 'ʃ',   # shy
    't'        : 't',   # tie
    'th'       : 'θ',   # thigh
    'v'        : 'v',   # vie
    'w'        : 'w',   # wise
    'wh'       : 'ʍ',   # why
    'y'        : 'j',   # yacht
    'z'        : 'z',   # zoo
    'zh'       : 'ʒ',   # pleasure
}

Whereas (slightly reorganised) I see on https://github.com/mphilli/English-to-IPA/blob/master/eng_to_ipa/transcribe.py#L98:
{
    "a": "ə",  #
    "ey": "e", #
    "aa": "ɑ",
    "ae": "æ",
    "ah": "ə", #
    "ao": "ɔ",
    "aw": "aʊ",
    "ay": "aɪ",
    "eh": "ɛ",
    "er": "ər", #
    "ih": "ɪ",
    "iy": "i",
    "ow": "oʊ",
    "oy": "ɔɪ",
    "uh": "ʊ",
    "uw": "u",
    "ch": "ʧ",
    "dh": "ð",
    "hh": "h",
    "jh": "ʤ",
    "ng": "ŋ",
    "sh": "ʃ",
    "th": "θ",
    "y": "j",
    "zh": "ʒ",
}

I have put a # next to the differences (the initial list also includes identical graphs). Is there a reason for the differences? I can understand 'er' but most of the others strike me as curious choices.

Of the identified, updating "ey" to "eɪ" is super valid. "er": "ər" is good, "ah": "ə" is fine ("ax" seems not to be used, there is only "ah0" and "ah1"), I don't think "a": "ə" is present so I'll leave as is so as not to break anything...


Help with Pull Requests

Not sure if someone can help me but I have been trying to contribute with GitHub Desktop. I viewed some videos on how to make pull requests but not sure I get how to do it properly. I did my code changes on my desktop but it seems like I only have one pull request with various commits. How do I make individual pull requests instead of only one with multiple commits?

I haven't done this myself yet but I think you have to create one branch for each issue and create a pull request from there to DotSpatial.Master. This seems to be the way @MatthiasSchilder went about it.
If you push everything into your master and then create a pull request to DotSpatial.Master you get the effect you've got now.

Oh wow? Really? One branch for each issue seems like a waste of resources. Ok Ill try to give that a shot.

You can delete the branch after the fix is accepted and merged.

Yes but doesn't that mean cloning and downloading the branch every time I want to suggest a fix?

@jany-tenaj I have a pull request with 4 commits. Hopefully the devs can take a look soon. I would like to contribute more now that I know the process. Many thanks.

I think there is a way to switch between branches in VS without having to download the whole source code again. I haven't tried it because I like having the source code once for each fix.
I can't promise that I can take a look, because I have a 4 month old baby taking up all my time. But you'll have to split your pull request before we can commit it.
In the current condition if later on we find that one of your fixes doesn't work as expected we'd have to revert everything you added. We furthermore can't refuse one of your fixes and accept another this way.

Yes but doesn't that mean cloning and downloading the branch every time I want to suggest a fix?

Just to be sure: you don't have to clone a working copy for every fix-branch you want to create. Clone a working copy once, create a local branch for your first fix, develop your fix and push your new branch with your fix to your github origin. Then, create a pull request, and get your fix pulled in. In your working copy, you can now switch back to master or just create a new branch for your next fix. I don't know Github Desktop, but switching with git bash or Tortoise-git it totally easy and will take only a few seconds in this situation. Branching locally does not duplicate your working copy.

Ahhh I see now. Let me give that a shot. If that is the case then maybe I can delete my current pull and redo it with as a split into four separate pulls.

So not sure what's the next step. Here is what I have done so far:

Cloned the project to my desktop
Created a branch for my fix
Developed my fix
Committed the fix to my branch
Publish my branch.

On step number 5 I get this error in GitHub Desktop
"Authentication failed. You may not have permission to access the repository or the repository may have been archived. Open options and verify that you're signed in with an account that has permission to access this repository."

Ok I think I had some of this wrong. New to GitHub so it was a challenge. Please check my pull request at https://github.com/DotSpatial/DotSpatial/pull/1244 Here is my revised process:

Go to MY fork of DotSpatial on the GitHub webpage and clone that repo to my desktop
Create a branch for my fix
Develop my fix in Visual Studio
Commit the fix in GitHub Desktop
Publish the branch in GitHub Desktop
Go to the original GitHub DotSpatial webpage. This is the original repo and NOT your personal fork
Click on "Compare & pull request". confirm you are merging from your personal fork/branch into the DotSpatial master

That seems to work so I have done it correctly. I will do another fix/branch later today and see how that goes. Please revise my process and pull request and make any suggestions. I hope that after making 4 or 5 of these fixes that perhaps there could be a push for a 2.1 release.

@jany-tenaj @MatthiasSchilder
Ok here is my second pull request following the above procedure https://github.com/DotSpatial/DotSpatial/pull/1245

My third pull request https://github.com/DotSpatial/DotSpatial/pull/1246

Fourth pull request https://github.com/DotSpatial/DotSpatial/pull/1248

Fourth pull request Pull request: https://github.com/DotSpatial/DotSpatial/pull/1249

Fifth pull request (and on Christmas Day) https://github.com/DotSpatial/DotSpatial/pull/1251

Sixth pull request https://github.com/DotSpatial/DotSpatial/pull/1252

Sixth pull request https://github.com/DotSpatial/DotSpatial/pull/1253
I think that's it for now. I have one other issue I am going to look at which could be related to one of my pull requests. That will come later in the week.

Seventh pull request https://github.com/DotSpatial/DotSpatial/pull/1254


Change now config and fix repo url for semantic-release

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


Zcmt: clarify translation of jvt-based addresses in M-mode

The latest draft says this about jvt (and this seems to match the ratified PDF from the riscv-code-size-reduction repo):

jvt.base is a virtual address, whenever virtual memory is enabled.
The memory pointed to by jvt.base is treated as instruction memory for the purpose of executing table jump instructions, implying execute access permission.

The first paragraph seems ambiguous, because virtual memory is "enabled" separately for fetch and load/store/AMO. The second paragraph is a good hint but it's not clear whether this is describing the translation or just X permissions (including PMP).
My question is: are jvt-based accesses translated in M-mode when mstatus.mprv is set and mstatus.mpp = S? If the intent is this is not translated then the first quoted sentence might be written more explicitly like so:

jvt.base is a virtual address, whenever virtual memory is enabled for instruction fetch. This includes S-mode execution when satp.mode is nonzero, and excludes all M-mode execution.

This is relevant because M-mode routines manipulating S-mode memory may also be compiled with Zcmt jumps, using an M-mode-supplied jvt value.

I think the description could be worded more artfully, but the answer to your question is unambiguous, because MPRV is defined to affect only explicit memory accesses.

Thank you for the definitive answer, that clears up my question nicely.

I think the description could be worded more artfully, but the answer to your question is unambiguous, because MPRV is defined to affect only explicit memory accesses.

Thanks, I went looking for that definition of MPRV, because that is a highly useful distinction and covers this neatly. The nearest I could find was this table caption in the section on the hypervisor extension:

Table 32. Effect of MPRV on the translation and protection of explicit memory accesses

If MPRV only affects explicit accesses (and not implicit ones) then would it be possible to add words to that effect to the documentation of mstatus in the section on the machine ISA? That documentation only mentions load/stores and instruction fetch, and jvt-based implicit accesses are neither of those things.

The Zcmt spec makes it clear that JVT accesses are considered implicit accesses.
We can't aggregate this information in one place because it would make the spec unscalable.  The scalable approach is to define common terminology, then use that terminology in the extension specs.  And that's exactly what we've done in this case.

The Zcmt spec makes it clear that JVT accesses are considered implicit accesses.

Agreed, this part is clear. I think the explicit/implicit distinction is a nice cut point and these terms are well defined. I don't see any reference to explicit/implicit accesses in the definition of mstatus.mprv in <IP_ADDRESS>, and it would be useful for me as a reader if it built on those common terms.

The MPRV section was written before the explicit/implicit concept was defined, but you can read that section's use of the phrase "loads and stores" to mean the same thing as "explicit memory accesses".  We'll get around to fixing it eventually, but for the moment, there's no ambiguity: "loads and stores" obviously excludes implicit memory accesses.


Bluetooth Controller: SCO connection fails with 2 existing phones connected (IDFGH-11172)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.2-dev-3065-g272b4091f1
Espressif SoC revision.
ESP32-D0WD-V3 (revision v3.0)
Operating System used.
macOS
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32_LyraT
Power Supply used.
USB
What is the expected behavior?
After connecting an iPhone Mini 12 with iOS 17 and an Google Pixel 7a, I expect both of them to be able to open an SCO for HFP.
What is the actual behavior?
When iOS initiates the SCO connection for WBS, the connection fails with error 0x1b - SCO Offset Rejected
Steps to reproduce.

Run the BTstack hfp_hf_demo
Pair and connect with iPhone
Pair and connect with Android
Start Voice Memos on iPhone and press Record

Here are the HCI traces for both ESP32 as well as an USB Bluetooth Dongle. Can be analyzed with Wireshark.
hfp_hf_two_phones.zip
Debug Logs.
Full logs are in the "Steps to reproduce"

Here the snippet for the SCO setup

Jan 01 18:00:47.382  HCI Event        Connection Request - 48:35:2B:90:47:3C  RECV
	Parameter Length: 10 (0x0A)
	Bluetooth Device Address: 48:35:2B:90:47:3C
	Class Of Device: 0x000000
	Service Class: 0x0000
	Major Class: 0x0000
	    Miscellaneous
	Minor Class: 0x0000
	Link Type: 0x02 -- eSCO Connection
Jan 01 18:00:47.382  HCI Event        00000000: 040A 3C47 902B 3548 0000 0002            ..<G.+5H....  RECV
Jan 01 18:00:47.387  Note             hci.c.3644: Connection_incoming: 48:35:2B:90:47:3C, type 2  RECV
Jan 01 18:00:47.394  Note             hci.c.316: create_connection_for_addr 48:35:2B:90:47:3C, type fc  RECV
Jan 01 18:00:47.402  Note             hfp.c.896: accept sco 2  RECV
Jan 01 18:00:47.406  HCI Event        Undecoded Event  RECV
Jan 01 18:00:47.410  Note             hfp.c.2104: Sending hci_accept_connection_request for link settings 8: packet types 0x0048, sco_voice_setting 0x43  RECV
Jan 01 18:00:47.421  Note             hci.c.7409: Possible SCO packet types 0x0048 => payload length 60  RECV
Jan 01 18:00:47.428  HCI Command      [0429] Accept Synchronous Connection Request - 48:35:2B:90:47:3C  SEND
	[0429] Opcode: 0x0429 (OGF: 0x01    OCF: 0x29)
	Parameter Length: 21 (0x15)
	Bluetooth Device Address: 48:35:2B:90:47:3C
	Transmit Bandwidth: 0x00001F40
	Receive Bandwidth: 0x00001F40
	Max Latency: 0xFFFF
	Content Format: 0x0043
	    Input Coding -- Linear
	    Input Data Format -- 2's Complement
	    Input Sample Size -- 8 Bit
	    Linear PCM Bit Position: 0x0000
	    Air Coding Format -- Transparent Data
	Retransmission Effort: 0x00FF
	    Don't Care
	Packet Type: 0x0388
	    EV3 May Be Used
	    3-EV3 May Not Be Used
	    2-EV5 May Not Be Used
	    3-EV5 May Not Be Used
Jan 01 18:00:47.428  HCI Command      00000000: 2904 153C 4790 2B35 4840 1F00 0040 1F00  )..<G.+5H<EMAIL_ADDRESS> SEND
Jan 01 18:00:47.438  HCI Event        Command Status - Accept Synchronous Connection Request  RECV
Jan 01 18:00:47.441  HCI Event        Synchronous Connection Complete - SCO Offset Rejected  RECV
	Parameter Length: 17 (0x11)
	Status: 0x1B - SCO Offset Rejected
	Connection Handle: 0x0180
	Bluetooth Device Address: 48:35:2B:90:47:3C
	Link Type: 0x02 -- eSCO Connection
	Transmission Interval: 0x06
	Retransmission Window: 0x00
	Rx Packet Length: 0x001E
	Tx Packet Length: 0x001E
	Air Mode: 0x03 -- Transparent Data
Jan 01 18:00:47.441  HCI Event        00000000: 2C11 1B80 013C 4790 2B35 4802 0600 1E00  ,....<G.+5H.....  RECV

More Information.
When running the same demo on a CSR8510 USB Bluetooth dongle, the SCO connection gets initiated as expected.
When only iPhone is connected, the SCO connection gets also correctly initiated.
BTstack uses:

Max Latency: Don't care
Retransmission Efforts: Don't care
Packet Types: EV3 and 2-EV3

Quick look into Bluedroid tells me that it uses:

Max Latency: 13
Retransmission Efforts: At least one retransmission, optimize for link quality
Packet Types: EV3 and 2-EV3

So, BTstack's requirement are even more relaxed, but result in the same connection settings if the connection gets established correctly.

Hi, I have reproduced this issue in my local environment with two android phone too.I found some abnormal behavior in controller when doing eSCO parameter negotiation.
We will fix this issue as soon as possible, thanks for your feedback!

HI, further analysis indicates that this issue is caused by a conflict between the interval events of the Sniff Mode and SCO, resulting in the inability to find a valid SCO offset. As a result, the controller rejected the request to establish an SCO connection.
As this issue involves some underlying logic, the solution is still under discussion. In the meantime, you can temporarily work around this issue by disabling Sniff Mode.

Thanks for reporting, we will close this issue. Feel free to reopen if have more updates.
Thanks for using our Espressif product!


Boolean search not functioning

Search doesn’t appear to be executing Boolean operators fully, and is instead doing fuzzy matching only. See video clip here.

@dannymandel I am checking- does iSC intend to support Boolean search? Or out of scope?

It seems like a reasonable request, but I suspect it requires some additional work.

Solr definitely supports it, we'd just need to do a bit of work to interpret it.


🐛 Bug | Issues with code blocks in dark mode

Description
When you enable dark mode in the app, the code blocks are not working properly.
We need to fix the style of:

inline code blocks
multi-line code blocks

@gregogun can we make it the same for light and dark mode and change the background for both of them to color n°2(dark mode) with a line stroke (color 7 but respecting the light and dark themes)

It will look like this:

@pradel you got with it?

Sounds good 👌


Metabase container not working on Rancher

Rancher Version:
1.1.3
Docker Version:
1.12.1
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu Linode
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single Node
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Create a stack based on this docker-compose.yml
metabase:
  image: metabase/metabase:v0.19.3
  ports:
    - "3000:3000"
  links:
  - postgres
postgres:
  environment:
    PGDATA: /var/lib/postgresql/data/pgdata
    POSTGRES_PASSWORD: asdfghjkl
    POSTGRES_USER: someuser
  image: postgres:9.5
  volumes:
  - metabase:/var/lib/postgresql/data/pgdata

and go to http://RANCHER_IP:3000 on your browser.
Results:
Can't connect to the server.
Expected:
If you instead of running the stack with Rancher, you locally start the containers using
docker-compose up -d

and go to http://localhost:3000 on your browser, you will see metabase welcome page.
Notes
It takes about a minute for the metabase container to configure itself before it starts serving on port 3000.

You'd need to connect to the IP of the host running the container, not the one running rancher/server.

@vincent99 Its single node, they are the same IP.

it would be nice to have Metabase in Rancher apps with all the config options available @vincent99


Add possibility to see validities for non-trip offers

For non-trip offers there is no possibility to see the the validity before the travelAccount is created for the pass. Reference id to the travelAccount is controlNumber, first available after fulfillment.
Suggested improvement is to add a new object, nonTripValidity, to the admissionOfferPart and the booked admission. I am open for other solutions but there is a need to have validity period and the regional constraints from the beginning somehow.

The improvement is needed in 3.4 as well.

The ideal place is under regionalValiditySummary of AdmissionOfferPart.
ValidFrom/ValidUntil are already parts of that object.

regionalValiditySummary should be in admission and ancillary only. reservation is always bound to vehicle number (trip).


spatialize_vit_mlp should begin with index 1?

Hi! @evandez,
Thanks for this outstanding work. As shown in DINO ViT, it looks like that DINO utilizes the first token as the [CLS] (index 0).
However, in your implementation of spatialize_vit_mlp , the [CLS] is excluded through hiddens[:, :-1]?  Should it be hiddens[:, 1:]?

Doh! I swear I checked that, but it looks like you're right. Likely this only slightly affects the visualizations, since the patches are fairly small. I will submit a fix and add an errata note somewhere.
Thanks for pointing it out!


Hermes takes a very long time to clear high number of pending packets

Summary
With thousands of pending packets hermes progress when clearing packets is very very slow. Some steps in a typical flow (e.g. build_recv_packet_and_timeout_msgs) are:

determine the sequences of pending packets
query_txs() for each sequence to find the packet
generate the messages
for each chunk of N msgs:

create the Tx
simulate the Tx
broadcast_tx_sync

During testing with thousands of pending packets I noticed that a Tx simulation will fail pretty early. And the clearing process above starts from the beginning. With 5k pending packets on a local (fast) setup just the query_txs() takes 2-3 minutes. And it takes 3-5 mins in the end to clear a few hundred packets.
The typical failure for simulation is the account mismatch error. And the recaching of the account sequence on that error causes the second try to fail again immediately.
Note: ignoring that sequence mismatch and continuing with the default gas improves things significantly.

Problem Definition
Clearing a high number of pending packets takes a very long time

Proposal

limit the number of events generating one operational data. For example for 5k pending packets we could generate 50 operational data elements. This way we minimize the work hermes does until the Tx-es go through or fail.
probably also redesign the retry in relay_pending_packets().
(maybe) ignore the sequence mismatch in the Tx simulation. If there is a real mismatch the checkTx will catch that and we can recache there.

Acceptance Criteria

Copied from #2077. Please see that issue and comments therein for an extended discussion on acceptance criteria and requirements.

Discussion
Hermes CLI for packet clearing should provide support for splitting the workload in multiple, smaller batches, to make this command more tractable. This can be done, for instance, with any of the following suggestions:
A. By adding a flag clear packets ... --limit X to specify that Hermes should limit itself to fetching only X amount of packets/acks (instead of all pages). The limit option should probably be mandatory.
B. Alternatively, we could handle splitting into smaller batches of X messages automatically within the implementation of clear packets and have a simpler interface.
The advantage of A. is that the command is a lot more interactive and will finish faster. The problem is that the operators will not know if there will still be packets left to relay, so they will need to repeatedly invoke clear packets --limit X until this method returns an empty result (signalling there was nothing to clear).
The advantage of B. is that this command is smarter and simpler. The disadvantage is that will take longer to finish. On a high-activity path with constant activity, depending on the implementation and how we split-up the batches, I can even imagine that this method will constantly run for as long as there are packets being created, which is a problem (the CLI should return, instead of grabbing & relaying every new packet).
Other solutions might exist. We should evaluate the pros and cons through the lenses of operator user experience and simplicity.
Tasks

[ ] add integration tests to assert the correctness of new behavior

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate milestone (priority) applied
[ ] Appropriate contributors tagged
[ ] Contributor assigned/self-assigned

Alternative option, from my comment at https://github.com/informalsystems/ibc-rs/issues/2077#issuecomment-1091797287

On a high-activity path with constant activity, depending on the implementation and how we split-up the batches, I can even imagine that this method will constantly run for as long as there are packets being created

That's indeed an issue, not clear how to avoid that. Perhaps by not trying to clear packets at a higher height than the one the chain was at when the command was started? ie. the command would clear packets from oldest to newest and stop once it sees a packet at a height higher than the starting height.

Also, ideally the command would use pagination and display its progress as it clears the packets, perhaps with a nice TUI progress bar?

I have tried a scenario where 100m packets are generated first, and then hemes is started. At this time, the clearing packet of Hermes will be triggered.
When there are too many events on the chain, call query_txs(PacketRequest) takes a long time. each request takes about 200ms (local node), which makes the clearing packet extremely slow.
I tried to build a layer of cache, using KVDB to store all SendPacket and ACK information. when query_txs is called, the cache will be queried first.

when the query commitments on chain is called, the query will become very slow when the request paging is set to all (when there are too many non relayed packets on the chain), so I set the limit to chain config: num_ msg - 1  (The remaining msg is reserved for UpdateClient)

query_txs also fails occasionally (I don't know why), which is one of the reasons why clearing packets slow down
https://github.com/informalsystems/ibc-rs/blob/master/relayer/src/link/relay_path.rs#L1025

Hi @lyqingye, I took a first stab at having a more incremental approach to clearing packets. Do you mind having a look over the PR and testing in your setup? Many thanks for the suggestions above & for any additional feedback!

Hi @lyqingye, I took a first stab at having a more incremental approach to clearing packets. Do you mind having a look over the PR and testing in your setup -- #2167? Many thanks for the suggestions above & for any additional feedback!

Hi @adizere , i will review your PR  and give some suggestions


Unsupported file format (support added in libraw 0.19)

Hi there, I am new to rawpy and I tried to import some raw image from IPX and HUAWEI mate 10, but rawpy dont seems to like it.
Traceback (most recent call last):
File "", line 1, in
File "/****/lib/python2.7/site-packages/rawpy/init.py", line 20, in imread
d.open_file(pathOrFile)
File "rawpy/_rawpy.pyx", line 266, in rawpy._rawpy.RawPy.open_file
File "rawpy/_rawpy.pyx", line 662, in rawpy._rawpy.RawPy.handle_error
rawpy._rawpy.LibRawNonFatalError: Unsupported file format or not RAW file
I did check Libraw and Iphone X and Mate 10 are in their supported list. So I am not sure what to do atm, please help.
Best,
LaTieCheng

Those two cameras were added in libraw 0.19 which was released just three days ago. The binary wheels of rawpy bundle 0.18 currently. I'll do a new release asap. Thanks for reporting!

Np, thanks for the prompt reply!

A new rawpy version is out. Should work now!


CLOUDP-184889: remove API path from method list

Community feedback that table is to wide and paths aren't adding any benefits. Individual paths can be also seen in the details if needed

@sarahsimpers Do you have opinion about this change? Does it make sense?

@sarahsimpers Do you have opinion about this change? Does it make sense?

This works for me! Thanks


@[local ext] should not generate a global ext_iff lemma

Prerequisites
Please put an X between the brackets as you perform the following steps:

[x] Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues
[x] Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries.
[x] Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)

Description
Tagging a structure Foo with @[local ext] generates global Foo.ext and Foo.ext_iff. It seems better to generate them as private lemmas instead.
Context
Zulip
Steps to Reproduce
In file MWE:
@[local ext]
structure Foo where
  toNat := Nat

In another file,
import MWE

#check Foo.ext
#check Foo.ext_iff

Expected behavior: The #checks fail
Actual behavior: They succeed
Versions
4.14.0-rc2
Ubuntu
Impact
Add :+1: to issues you consider important. If others are impacted by this issue, please ask them to add :+1: to it.

lean4#3643 seems related and closed.


add devmode launcher implementation

with the new orchestrator trait design, we can now implement a proper devmode orchestrator directly on top of the auto-seal-consensus implementation and we no longer need to mimic the engine API internally:
https://github.com/paradigmxyz/reth/blob/eda161af2c4cb3457eed9d3b81b9b2e5f55db313/crates/consensus/auto-seal/src/task.rs#L159-L163
TODO

Add DevOrchestrator implementation that drives the MiningTask and advances the node
https://github.com/paradigmxyz/reth/blob/eda161af2c4cb3457eed9d3b81b9b2e5f55db313/crates/consensus/auto-seal/src/task.rs#L83-L89
This should start as a duplicated implementation of MiningTask that emits new ExecutedBlock
the DevOrchestrator then uses that block to advance the chain by persisting the block, similar to

https://github.com/paradigmxyz/reth/blob/eda161af2c4cb3457eed9d3b81b9b2e5f55db313/crates/engine/tree/src/tree/mod.rs#L541-L544
see for reference:
https://github.com/paradigmxyz/reth/blob/eda161af2c4cb3457eed9d3b81b9b2e5f55db313/crates/ethereum/node/src/launch.rs#L259-L259

@mattsse assign me

@malik672 do you still have the capacity to work on this?

@mattsse yes I do, was already working on it but stopped, it's kinda hard ngl

hehe it is
please open a draft pr and I can provide more directions

completed


add "variables" argument to argspec.kwonlyaards

no unit tests written
not tested locally
This is related to these two pull issues:
https://github.com/tensorflow/tensorflow/issues/31945
https://github.com/tensorflow/tensorflow/issues/38622
What this should do is force the input of grad() function of class Loss to forget an extra argument required when instantiating a Variable() with the custom loss function.
Ideally I'd implement the patch and build from source, but I'm encountering build from source issues via bazel: https://github.com/tensorflow/tensorflow/issues/38736, likely due to Fedora.
Let me know what need be changed.
It'd be awesome to be able to build from source so that I can test the patch, but bazel is still messing up, if one of the devs knows a quick fix I can implement it.

@googlebot I signed it!

@drezap  Can you please address Ubuntu Sanity errors? Thanks!

yes easy fix not now too busy. soon

@drezap Any update on this PR? Please. Thanks!

This bug remains unsolved then?


Issues in scripts

It would appear that some scripts contain now deprecated commands.
Specifically, I am having problems with the following in: samples/DevTestLabs/Scripts/ImageFactory/Scripts/DistributionHelpers.psm1
function SaveProfile {
    $profilePath = Join-Path $PSScriptRoot "profile.json"

    If (Test-Path $profilePath){
	    Remove-Item $profilePath
    }

    Save-AzureRmProfile -Path $profilePath
}

function LoadProfile {
    $scriptFolder = Split-Path $Script:MyInvocation.MyCommand.Path
    Import-AzureRmContext -Path (Join-Path $scriptFolder "profile.json") | Out-Null
}

Save-AzureRmProfile and Import-AzureRmContext appear to be non-functional now

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

ID: 855f24d1-954e-ca8a-02de-817b77dfef6d
Version Independent ID: 94326314-cf86-f4f5-5062-7663070fd393
Content: Run an image factory from Azure DevOps in Azure DevTest Labs - Azure DevTest Labs
Content Source: articles/devtest-labs/image-factory-set-up-devops-lab.md
Service: devtest-lab
GitHub Login: @Juliako
Microsoft Alias: juliako

@tobyfiserv -
Thanks for brining this to our attention. We will investigate it further and update you shortly.

Hey @tobyfiserv
Thanks for the feedback. Adding the response from another issue you reported for clarity.
The commandlets were deprecated in the latest versions of Azure PowerShell. For other customers we have been recommending using an older version of PowerShell, but more recently we have newer native Azure services that supercede the Image Factory solution.
I know you mentioned you were exploring the the Azure Image Builder & Shared Image Gallery services instead of DTL Image Factory. Please let us know how that's going and if you have questions or feedback for us.
We are also working on updating the Image Factory solution with the newer approach to ensure users don't hit older scripts.

@tanmayeekamath - Thank you for providing your insights.
@tobyfiserv - I hope @tanmayeekamath has answered your question.
At this moment, Since there is no doc update required, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Yes, thank you!


Connectivity panel improvements

Coverage increased (+0.1%) to 56.339% when pulling 1ec1e65e0d58ab564b7485dbccdbe54afbe13d35 on gabrielburnworth:master into 16988a478c6bb74bdf58a9064891c52ce8ae9744 on FarmBot:master.

Coverage increased (+0.1%) to 56.337% when pulling f1984b97b493dd93f3aec55f1d8ab77547b4bf64 on gabrielburnworth:master into 16988a478c6bb74bdf58a9064891c52ce8ae9744 on FarmBot:master.


[🐛 BUG] - Window title is not updated when changing application

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Login, default app opens, in my case Google Drive
Switch app to another one, eg. Hangouts
Hangouts are launched with Google Drive window title

Expected behavior
3. Hangouts are launched with Google Hangouts title
Screenshots

G Desktop Suite:

Version - g-desktop-suite-git 122.315a78a-1

Platform:

OS: Arch Linux, XFCE desktop environment

Right now window title is managed by a static index.html file, maybe something can update that?

This has been fixed with merging PR #48.


[C-API] revert fill dimension 1

This patch reverts fill dimension to default value 1.
In C# API, interop function ml_tensors_info_get_tensor_dimension is used with length 4 dimension array instead of 16.
/* int ml_tensors_info_get_tensor_dimension (ml_tensors_info_h info, unsigned int index, ml_tensor_dimension dimension) */
[DllImport(Libraries.MlCommon, EntryPoint = "ml_tensors_info_get_tensor_dimension", CallingConvention = CallingConvention.Cdecl)]
internal static extern NNStreamerError GetTensorDimension(IntPtr info, int index, [In, Out] uint[] dimension);

uint[] dim = new uint[Tensor.RankLimit];
.
.
.
ret = Interop.Util.GetTensorDimension(handle, i, dim);
NNStreamer.CheckException(ret, "Fail to get Tensor's dimension");

fill dimension using default value 1 will be added after C# API fixed.

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #300. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.


The webpack watch dosn't rebuild when I perform npm run storybook

this is my demo
here:https://github.com/qiangege/react-storybook-demo.git

first
I perform npm run storybook
now, I  change content of the files in node_modules,the webpack can rebuild
then
I open  another  service, don't  close npm run storybook, I perform npm install range-input-react  or  npm install. now , I  change content of the files in node_modules,the webpack dosn't  rebuild,
this question is very  strange.
What should I do to solve this problem

You mean, when you install new NPM modules, storybook webpack cannot determine that. Is it?

step  npm run storybook  > npm install a modules > change a file
it's not rebuild the project   webpack watch it's not working .
you can try it.

Okay. Got it. I know how to fix this.
Note: Use CRA's WatchMissingNodeModulesPlugin.

@arunoda
The first, thinks for your project.it's very great
About this problem I have a suggestion
see that:
https://www.npmjs.com/package/npm-install-webpack-plugin
npm-install-webpack-plugin

@abnerCrack This plugin does too much.
We don't want to save NPM packages and others. We just need to detect changes.
The plugin I mentioned above would work fine for this usecase.
PRs welcome :)

@arunoda  TOT.ok~~~~

We've fix this (original issue by @qiangege) with the latest Storybook.
Reopen if that doesn't fix your issue.


Edit Japanese translation

Hello
I've fixed some mistakes in Japanese translation before.
Please accept this pull request.
Sorry for bothering you.
Thank you.

Sorry for bothering you.

No problem ;) Thank you!


fix(type): type parameter errors of yjs

This PR fix the type error when using:

latest y-prosemirror
latest yjs
has strcit: true options enabled for typescript

Closes: #95

Thank you! I will get this released this week with some other updates.


Sorceress leveling hydra orb

Since the main branch has been running away, scrapped the old PR and made a new one for my beloved Hydra/Orb (Leveling as nova) sorc profile

Implemented in  c3d358c31e31d8d928713f06678cabbc8ccca65c


Reverts prefabs to default (editable children)

Godot version: 3.2 beta 1
OS/device including version: windows 10
I prepared a prefab (scene) for my project. Then I use that prefab in the root scene. I right-click on that node in the editor and select editable children. change some colors, size and save.
problem is when you move that prefab to another node. When I did that prefab automatically lost the editable children option. I saved everything and restarted Godot.exe and then I saw that all prefabs are reverted back to default.
video: https://www.dropbox.com/s/n61acuojpdnchuq/Test.mp4?dl=0

Duplicate of #23979


Tab/Shift+Tab Focus Needs UX

Seems tabbing through a sidebar form field for instance can completely dismantle the UI.

This has been corrected with focus groups.


oci_push --repository and --tag flags should accept file paths

Useful for stamping, for example

already changed repotags to take a file argument

closing this as we already support stamped repotags

Now that the repository name is back out of the "remote_tags" attribute and in its own "repository" attribute, we lost this ability that we had for a brief while.
The discussion here sounds like the maintainers were convinced of the value of stamping the repository name, but since then we've wavered on which information gets conveyed in which attribute values. Yes, if we could convey the repository name in the stamp-friendly "remote_tags" attribute, this need would be covered, but with the separate "repository" attribute we have today, I think there's still an open gap.

See #338 for taking the repository from the content of a file.


Nitpick in file names in README

<taskdef ... classpath="/path/to/schxslt-ant.jar"

ant-schxslt.jar would be better.

<schematron ... file="test.sch"

test.xml or anything other than *.sch would be better.

Thanks!


[Bug] "GSS initiate failed" error occurs when connect to kerberized Kyuubi with Kyuubi beeline

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the bug
Failed to connect to kerberized Kyuubi with Kyuubi beeline.
$ ./bin/beeline -u<EMAIL_ADDRESS>log4j:WARN No appenders could be found for logger (org.apache.hadoop.util.Shell).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Connecting to<EMAIL_ADDRESS>Error: Could not open client transport with JDBC Uri<EMAIL_ADDRESS>GSS initiate failed (state=08S01,code=0)
Beeline version 1.4.0-incubating by Apache Kyuubi (Incubating)

Affects Version(s)
1.4.0
Kyuubi Server Log Output
21/12/15 19:12:22 ERROR server.TThreadPoolServer: Error occurred during processing of message.
java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: Peer indicated failure: GSS initiate failed
	at org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:219)
	at org.apache.kyuubi.service.authentication.HadoopThriftAuthBridgeServer$TUGIAssumingTransportFactory$$anon$4.run(HadoopThriftAuthBridgeServer.scala:117)
	at org.apache.kyuubi.service.authentication.HadoopThriftAuthBridgeServer$TUGIAssumingTransportFactory$$anon$4.run(HadoopThriftAuthBridgeServer.scala:116)
	at java.security.AccessController.doPrivileged(Native Method)
	at javax.security.auth.Subject.doAs(Subject.java:360)
	at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1855)
	at org.apache.kyuubi.service.authentication.HadoopThriftAuthBridgeServer$TUGIAssumingTransportFactory.getTransport(HadoopThriftAuthBridgeServer.scala:116)
	at org.apache.thrift.server.TThreadPoolServer$WorkerProcess.run(TThreadPoolServer.java:269)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.thrift.transport.TTransportException: Peer indicated failure: GSS initiate failed
	at org.apache.thrift.transport.TSaslTransport.receiveSaslMessage(TSaslTransport.java:199)
	at org.apache.thrift.transport.TSaslServerTransport.handleSaslStartMessage(TSaslServerTransport.java:125)
	at org.apache.thrift.transport.TSaslTransport.open(TSaslTransport.java:271)
	at org.apache.thrift.transport.TSaslServerTransport.open(TSaslServerTransport.java:41)
	at org.apache.thrift.transport.TSaslServerTransport$Factory.getTransport(TSaslServerTransport.java:216)
	... 10 more

Kyuubi Engine Log Output
No response
Kyuubi Server Configurations
kyuubi.authentication KERBEROS
kyuubi.kinit.principal<EMAIL_ADDRESS>kyuubi.kinit.keytab /etc/security/keytabs/hive.keytab

Kyuubi Engine Configurations
No response
Additional context
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

I confronted with the same issue. Is there any solution?

@YetiCuzMountain Which version of Kyuubi are you using? This issue has been fixed, the fixed version is v1.4.1-incubating.

@YetiCuzMountain Which version of Kyuubi are you using? This issue has been fixed in v1.4.1-incubating.

kyuubi-1.4.1. the latest one  .
when config keytab and principle in kyuubi-defaults,and use kyuubi beeline to connect. it happened

@YetiCuzMountain Which version of Kyuubi are you using? This issue has been fixed in v1.4.1-incubating.

kyuubi-1.4.1. the latest one  .
when config keytab and principle in kyuubi-defaults,and use kyuubi beeline to connect. it happened

Have you set HADOOP_CONF_DIR in conf/kyuubi-env.sh?

yes.  HADOOP_CONF_DIR configured indeed
then bin/beeline -u 'jdbc:hive2://hostname:10009/' -n user
got issue:
ERROR server.TThreadPoolServer: Error occurred during processing of message.
java.lang.RuntimeException: org.apache.thrift.transport.TTransportException: Unsupported mechanism type PLAIN

yes i have.


Add auth-type as input param

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #1124
Special notes for reviewers:

Release note:

auth-type can be input as param to auth from provider to openstack

Hi, what if we don't specify auth-type but provide configs like application-credential-id and application-credential-secret, will the authentication will fail?

Hi, what if we don't specify auth-type but provide configs like application-credential-id and application-credential-secret, will the authentication will fail?

@lingxiankong no, it won't

Hi, what if we don't specify auth-type but provide configs like application-credential-id and application-credential-secret, will the authentication will fail?

@lingxiankong with the current master branch, no, it won't. with this change - probably yes.

Thanks @kayrus, so is it necessary to add the extra auth-type config option?

@kayrus @lingxiankong from my test, if didn't change auth-type, the auth will fail
maybe I used wrong configuration before... so I will redo my test and paste result here

@lingxiankong I never had issues with auth. app creds works, password auth works.

I think I misunderstood the logic
gophercloud handles the logic for us https://github.com/gophercloud/gophercloud/blob/master/auth_options.go#L224
so we should close this PR


[bn] Localize content/bn/docs/home/supported-doc-versions.md

Signed-off-by: Shahriyar<EMAIL_ADDRESS>Localizes content/bn/docs/home/supported-doc-versions.md to Bengali
This is an initial PR as may need some improvements!
Tracking issue: #31677

/lgtm


Maybe the OssLicense screen should be in dark mode only

Overview
Currently, the dark and light modes have changed depending on the OS environment in OssLicense, but I thought it would not be good for the app to suddenly have a white light screen in terms of its design.
https://github.com/user-attachments/assets/a9d8bca7-0a30-4f79-910b-50d83877783f

I would like to take on the challenge.


Reorganize the dictionary

To make the handling of dates with large amounts of files, it would be easier to have every date just have a class that manages its files.
This would allow for the date level to manage the construction of folders, updating of local pickle files.
This makes the "Add file to dictionary" logic a lot cleaner.  Right now it is quite messy as it is handling the creation of the big date class.

Need to decide how to figure out where to put the files.

we could have the FileClusterManager broker this information, but its not allowed to have init parameters and doesn't know where is located.
we could call some function that passes the highest level directory for the main dict to the FileClusterManager
we could also just have the FileClusterManager track the current path and have the CopyFunctionDetermine where the files go

Need to decide how to figure out where to put the files.

we could have the FileClusterManager broker this information, but its not allowed to have init parameters and doesn't know where is located.
we could call some function that passes the highest level directory for the main dict to the FileClusterManager
we could also just have the FileClusterManager track the current path and have the CopyFunctionDetermine where the files go


feat: Adding shellcheck

Shellcheck is a lightweight package that allows us to do linting on bash scripts. This
allows us to use the same docker image rather than the circleci/orb which has some issues
with the git client (extremely slow).
Figured given the size of the package it wouldn't be an issue adding it into this package, hope thats okay!

Yes no problems if it's helpful @yasserf! Thanks for the update :)


City council events source:

City council and committee meetings are available here:
http://ocd.datamade.us/events/?jurisdiction=ocd-jurisdiction/country:us/state:il/place:chicago/government

Handy!

Awesome, I picked up the city clerk site but it looks like this feed already scrapes the meetings on a daily basis. Any problems with modifying the city clerk spider to point to Councilmatic?

Please don't scrape councilmatic. Use this the API endpoint referenced
above instead. docs are at ocd.datamade.us
On Tue, Aug 22, 2017 at 7:32 PM, bonfirefan<EMAIL_ADDRESS>wrote:

Awesome, I picked up the city clerk site but it looks like this feed
already scrapes the meetings on a daily basis. Any problems with modifying
the city clerk spider to point to Councilmatic?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/City-Bureau/documenters-aggregator/issues/5#issuecomment-324188025,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgxbfxD7tE6MEcFR9hJseDeibEHTx7Tks5sa3MagaJpZM4Olr9S
.

--
773.888.2718

Yes, definitely not scraping councilmatic - looking through the documentation now, as well as the source code itself - a few of the Cook County agencies also appear to use Legistar.

Forest - do you happen to know how to ascertain the client names for other legistar sites? I know we were also looking at https://cook-county.legistar.com/calendar.aspx
Unfortunately "cook-county" and variants don't seem to work. I've also tested out variants for other legistar sites, some which seem to follow an obvious logic, and other which don't (Madison's legistar site, for example).

Also - what would be the main difference in sending a direct request through the legistar api and querying the ocd API endpoint?

As I said in #78, legistar does not expose cook county data through an API, you'll need to scrape the website.

The main difference is that we have spent a few years figuring out the vagaries of legistar data sources and how to assimilate those to an OCD data model. If you don't build off of our work, you will have to replicate all that learning yourself, which is not trivial.

Great, thanks! Ok - bear with' me here. I'm trying to query the events endpoint on the OCD API and it appears I'm not finding a start_time. I've gone to the detail page of an individual event_id and still didn't find one. Perhaps I'm querying the API wrong? The "T##:##:##" ending string does correspond to the actual start_time.

Example url?

Edited the previous comment with an example: I'm checking both your link and the more general: https://ocd.datamade.us/events/

An example detail event query: https://ocd.datamade.us/ocd-event/7872bdf0-0ffa-41b5-a778-7116635eb0b7/

I'm seeing start_date, but you are not?
"start_date": "2013-04-08T15:00:00+00:00"

start_date is a fully datetime (date and time combined)

Okay, so for example the Committe on Housing and Real Estate on 9/27/2017 at 10am: https://chicago.legistar.com/MeetingDetail.aspx?ID=563656&GUID=7286E5BA-E48E-46D3-AB0F-0ACC61767B68&Options=&Search=
On the OCD API, the details page for this event is https://ocd.datamade.us/ocd-event/8bf4b996-ffe0-4d57-86c6-16ead15c8848/
Which lists
start_date : "2017-09-27T15:00:00+00:00"

Okay, what's the problem?
T15:00:00+00:00 means 3 in the afternoon UTC. Which is 10am Chicago time.

Ah, that is it, I had the wrong timezone. Thanks for clearing that up.

in T15:00:00***+00:00*** the bolded part is the timezone relative to UTC. since it's 00:00 the timezone is UTC.

resolved by #156


Package bumps

Package updates.
@pcraig3 note the Nodemailer was bumped (major) not sure what's the best way to test that.
This PR doesn't update to the latest React Router (had some failing tests on that).  Can look at that separately.

Getting blocked on CI
Your lockfile needs to be updated, but yarn was run with --frozen-lockfile
If we remove the --frozen-lockfile we run out of memory on the build.


Could not resolve project :react-native-interactable.

Hi,
dose anyone know how to solve this?

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: ln -sf lib/{ios,android} .
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output
above.
i am also getting this error when trying to link
PS C:\Test\Projectwow\client> react-native link react-native-interactable
Scanning folders for symlinks in C:\Test\Projectwow\client\node_modules (24ms)
{ Error: Cannot find module 'C:\Test\Projectwow\client\node_modules\react-native-interactable\package.json'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at getRNPMConfig (C:/Test/Projectwow/client/node_modules/react-native/local-cli/core/index.js:53:3)
at Object.getDependencyConfig (C:/Test/Projectwow/client/node_modules/react-native/local-cli/core/index.js:115:18)
at deps.reduce (C:/Test/Projectwow/client/node_modules/react-native/local-cli/link/getDependencyConfig.js:16:24)
at Array.reduce ()
at getDependencyConfig (C:/Test/Projectwow/client/node_modules/react-native/local-cli/link/getDependencyConfig.js:13:15)
at Object.link (C:/Test/Projectwow/client/node_modules/react-native/local-cli/link/link.js:131:24) code: 'MODULE_NOT_FOUND' }
rnpm-install info Linking assets to ios project
rnpm-install info Linking assets to android project
rnpm-install info Assets have been successfully linked to your project
PS C:\Test\Projectwow\client>
thanks

Which operating system are you using??

Android, probably. If that's the case, go to android/settings.gradle and change
project(':react-native-interactable').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-interactable/android')
to
project(':react-native-interactable').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-interactable/lib/android').
It seems like the folders for native codes, /ios and /android that is, have been moved to /lib.

I switched to yarn and I was able to successfully install react-native-interactable


add webpack config for Public Maps static view

add Public Maps to webpack workflow to generate static HTML

Why am I the assigned person? :joy:


small format, linear grad

quick format change from prettier.

Current dependencies on/for this PR:

master

PR #1866   👈

This stack of pull requests is managed by Graphite.


I want to add args to vscode.StatusBarItem command,but there have no api to support?

I add a vscode.StatusBarItem in my extension,and bind comand for the StatusBar，But I can't send a args to the command.How can i solve the problem?Thannks!

Please give more details. Why can't you send args?


Update package requirement

Packages pathlib and pathlib2 are conflicting when doc-warden and virtualenv is installed together. Fix is to update package requirement to pathlib2

LGTM. pathlib2 is the official replacement of pathlib.


Pull in updates from run-sync-framework

Coverage remained the same at 98.1% when pulling 6908c7e562c0e86eeabaf365cea33b25bde84e20 on ken/run-sync into 63aa122c00ddf31c8cae0cabc165ca7fa22905d8 on master.