Can't initiate a transfer on S3 hosted Asset

Can't initiate a transfer on S3 hosted Asset
I create a local deployment of two connectors based on the transfer/transfer-05-file-transfer-cloud, but towards the end, when initiating a transfer, the consumer connector seems to send a request with the wrong format.
Setup
This is how I proceeded (might be helpful in finding out what was wrong) :

I created a free account on AWS and created myself a bucket skante-b1 containing a single jpeg image (snow.jpg), then downloaded the credentials
I cloned the Samples repository
I edited the transfer/transfer-05-file-transfer-cloud/cloud-transfer-consumer/build.gradle.kts file by:

replacing in line 31, the line implementation(libs.edc.vault.azure) by  implementation(libs.edc.vault.filesystem). This is because I wanted to use the local filsystem instead of an actual azure vault. I am in a development setting after all and I do not have an azure account.
adding the expression implementation(libs.edc.data.plane.selector.api) so I can add dataplanes later on through the management API

built that connector like this (creates the resources directory and cp the jar file inside):

docker run -it \
  -v $(pwd)/Samples:/data \
  -w /data \
  gradle:jdk17  ./gradlew transfer:transfer-05-file-transfer-cloud:cloud-transfer-consumer:build

mkdir -p resources && cp Samples/transfer/transfer-05-file-transfer-cloud/cloud-transfer-consumer/build/libs/consumer.jar resources/connector.jar

Then I added a keystore.jks and a vault.properties file, the latter containing my AWS credentials (aws-key and aws-secret)
Then I created the following docker compose file:

services:
  provider:
    image: openjdk
    volumes:
      - ./resources:/app
    command:
      - java
      - -jar
      - /app/connector.jar
    environment:
      EDC_AWS_ACCESS_KEY: aws-key
      EDC_AWS_SECRET_ACCESS_KEY: aws-secret
      # EDC_AWS_ENDPOINT_OVERRIDE: http://minio:9000
      EDC_VAULT: /app/vault.properties
      EDC_KEYSTORE: /app/keystore.jks
      EDC_KEYSTORE_PASSWORD: test123
      EDC_PARTICIPANT_ID: provider
      WEB_HTTP_PORT: 9191
      WEB_HTTP_PATH: /api
      WEB_HTTP_MANAGEMENT_PORT: 9192
      WEB_HTTP_MANAGEMENT_PATH: /management
      WEB_HTTP_PROTOCOL_PORT: 9292
      WEB_HTTP_PROTOCOL_PATH: /protocol
      WEB_HTTP_CONTROL_PORT: 9193
      WEB_HTTP_CONTROL_PATH: /control
      WEB_HTTP_PUBLIC_PORT: 9291
      WEB_HTTP_PUBLIC_PATH: /public
      EDC_API_AUTH_KEY: password
      EDC_DSP_CALLBACK_ADDRESS: http://provider:9292/protocol
    ports:
      - 9191:9191
      - 9192:9192
      - 9292:9292

  consumer:
    image: openjdk
    volumes:
      - ./example:/example
      - ./resources:/app
    command:
      - java
      - -jar
      - /app/connector.jar
    environment:
      EDC_AWS_ACCESS_KEY: aws-key
      EDC_AWS_SECRET_ACCESS_KEY: aws-secret
      # EDC_AWS_ENDPOINT_OVERRIDE: http://minio:9000
      EDC_VAULT: /app/vault.properties
      EDC_KEYSTORE: /app/keystore.jks
      EDC_KEYSTORE_PASSWORD: test123
      EDC_PARTICIPANT_ID: consumer
      WEB_HTTP_PORT: 8181
      WEB_HTTP_PATH: /api
      WEB_HTTP_MANAGEMENT_PORT: 8182
      WEB_HTTP_MANAGEMENT_PATH: /management
      WEB_HTTP_PROTOCOL_PORT: 8282
      WEB_HTTP_PROTOCOL_PATH: /protocol
      WEB_HTTP_CONTROL_PORT: 8183
      WEB_HTTP_CONTROL_PATH: /control
      WEB_HTTP_PUBLIC_PORT: 8281
      WEB_HTTP_PUBLIC_PATH: /public
      EDC_API_AUTH_KEY: password
      EDC_DSP_CALLBACK_ADDRESS: http://consumer:8282/protocol
    ports:
      - 8181:8181
      - 8182:8182
      - 8282:8282

Then started the docker compose

Everything started without any accidents.
Transfer
I logged onto the consumer connector and pretty much followed the same steps described in transfer/transfer-01-negotiation.
Here are the different objects created

consumer dataplane

{
  "@context": {
    "@vocab": "https://w3id.org/edc/v0.0.1/ns/"
  },
  "@id": "s3-consumer-dataplane",
  "url": "http://consumer:8183/control/transfer",
  "allowedSourceTypes": [ "AmazonS3" ],
  "allowedDestTypes": [ "AmazonS3" ],
  "properties": {
    "publicApiUrl": "http://consumer:8281/public/"
  }
}

provider dataplane

{
  "@context": {
    "@vocab": "https://w3id.org/edc/v0.0.1/ns/"
  },
  "@id": "s3-provider-dataplane",
  "url": "http://provider:9193/control/transfer",
  "allowedSourceTypes": [ "AmazonS3" ],
  "allowedDestTypes": [ "AmazonS3" ],
  "properties": {
    "publicApiUrl": "http://provider:9291/public/"
  }
}

asset

{
  "@context": {
    "@vocab": "https://w3id.org/edc/v0.0.1/ns/"
  },
  "@id": "asset-1",
  "properties": {
    "contenttype": "image/jpeg",
    "type": "AmazonS3",
    "name": "snow.jpg"
  },
  "dataAddress": {
    "type": "AmazonS3",
    "region": "eu-north-1",
    "bucketName": "skante-b1"
  }
}

policy

{
  "@context": {
    "@vocab": "https://w3id.org/edc/v0.0.1/ns/",
    "odrl": "http://www.w3.org/ns/odrl/2/"
  },
  "@id": "aPolicy",
  "policy": {
    "@type": "set",
    "odrl:permission": [],
    "odrl:prohibition": [],
    "odrl:obligation": []
  }
}

contract

{
  "@context": {
    "@vocab": "https://w3id.org/edc/v0.0.1/ns/"
  },
  "@id": "1",
  "accessPolicyId": "aPolicy",
  "contractPolicyId": "aPolicy",
  "assetsSelector": []
}

transferprocess (after getting catalog, extracting PolicyID, creating a contractnegociation with it, then extracting the agreement ID from the latter)

{
  "@context": {
    "@vocab": "https://w3id.org/edc/v0.0.1/ns/"
  },
  "counterPartyAddress": "http://provider:9292/protocol",
  "protocol": "dataspace-protocol-http",
  "connectorId": "consumer",
  "assetId": "asset-1",
  "contractId": "${agreementId}",
  "dataDestination": {
    "type": "AmazonS3",
    "region": "us-east-1",
    "bucketName": "edc-skante"
  },
  "transferType": {
    "contentType": "image/jpeg",
    "isFinite": true
  }
}

No issues appear till I reach this point.
Issue
This is how the logs look like when I start the transfer:
aws-test-consumer-1  | DEBUG 2024-03-05T11:01:58.319895278 [TransferProcessManagerImpl] TransferProcess a2797031-b8fa-48ac-bcda-ff0f63be9624 is now in state INITIAL
aws-test-consumer-1  | DEBUG 2024-03-05T11:01:58.323941369 Process a2797031-b8fa-48ac-bcda-ff0f63be9624 is now INITIAL
aws-test-consumer-1  | DEBUG 2024-03-05T11:01:58.327664018 Transfer Process created a2797031-b8fa-48ac-bcda-ff0f63be9624
aws-test-consumer-1  | DEBUG 2024-03-05T11:01:59.220716336 [TransferProcessManagerImpl] TransferProcess a2797031-b8fa-48ac-bcda-ff0f63be9624 is now in state PROVISIONING
aws-test-consumer-1  | DEBUG 2024-03-05T11:01:59.228580306 TransferProcess: ID a2797031-b8fa-48ac-bcda-ff0f63be9624. Provisioning
aws-test-consumer-1  | DEBUG 2024-03-05T11:01:59.699243825 S3ProvisionPipeline: create bucket edc-skante
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:00.936238805 S3ProvisionPipeline: get user
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:01.558358822 S3ProvisionPipeline: create role for userarn:aws:iam::533267125486:user/skante
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:01.768694742 S3ProvisionPipeline: attach bucket policy to role arn:aws:iam::533267125486:role/a2797031-b8fa-48ac-bcda-ff0f63be9624
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:01.92165362 S3ProvisionPipeline: attempting to assume the role
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:02.936441126 S3ProvisionPipeline: attempting to assume the role
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:04.04679546 S3ProvisionPipeline: attempting to assume the role
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:10.293224752 S3ProvisionPipeline: attempting to assume the role
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:10.464182051 S3BucketProvisioner: Bucket request submitted: edc-skante
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:10.51392943 [TransferProcessManagerImpl] TransferProcess a2797031-b8fa-48ac-bcda-ff0f63be9624 is now in state PROVISIONED
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:11.062634746 [TransferProcessManagerImpl] TransferProcess a2797031-b8fa-48ac-bcda-ff0f63be9624 is now in state REQUESTING
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:11.073231642 TransferProcess: ID a2797031-b8fa-48ac-bcda-ff0f63be9624. Send TransferRequestMessage to http://provider:9292/protocol
aws-test-provider-1  | DEBUG 2024-03-05T11:02:11.11760743 DSP: Incoming TransferRequestMessage for class org.eclipse.edc.connector.transfer.spi.types.TransferProcess process
aws-test-provider-1  | DEBUG 2024-03-05T11:02:11.140296957 DSP: Service call failed: 'bucketName' is a mandatory attribute, 'region' is a mandatory attribute
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:11.155470909 TransferProcess: ID a2797031-b8fa-48ac-bcda-ff0f63be9624. Send TransferRequestMessage to http://provider:9292/protocol
aws-test-consumer-1  | SEVERE 2024-03-05T11:02:11.156336241 TransferProcess: ID a2797031-b8fa-48ac-bcda-ff0f63be9624. Fatal error while Send TransferRequestMessage to http://provider:9292/protocol. Error details: {"@type":"dspace:TransferError","dspace:code":"400","dspace:reason":["'bucketName' is a mandatory attribute","'region' is a mandatory attribute"],"@context":{"@vocab":"https://w3id.org/edc/v0.0.1/ns/","edc":"https://w3id.org/edc/v0.0.1/ns/","dcat":"https://www.w3.org/ns/dcat/","dct":"https://purl.org/dc/terms/","odrl":"http://www.w3.org/ns/odrl/2/","dspace":"https://w3id.org/dspace/v0.8/"}}
aws-test-consumer-1  | WARNING 2024-03-05T11:02:11.156821717 {"@type":"dspace:TransferError","dspace:code":"400","dspace:reason":["'bucketName' is a mandatory attribute","'region' is a mandatory attribute"],"@context":{"@vocab":"https://w3id.org/edc/v0.0.1/ns/","edc":"https://w3id.org/edc/v0.0.1/ns/","dcat":"https://www.w3.org/ns/dcat/","dct":"https://purl.org/dc/terms/","odrl":"http://www.w3.org/ns/odrl/2/","dspace":"https://w3id.org/dspace/v0.8/"}}
aws-test-consumer-1  | DEBUG 2024-03-05T11:02:11.158921264 [TransferProcessManagerImpl] TransferProcess a2797031-b8fa-48ac-bcda-ff0f63be9624 is now in state TERMINATED

I made sure to specify not only in my asset definition but also in the transfer process the required fields for the "dataAddress", but for some reason it seems it is forgotten whenever the consumer actually requests the transfer or it is ignore by the provider for somehow. Can someone help with this issue?

Hey, thanks for reporting. This could be something related to the DataAddressValidator for S3 transfers: https://github.com/eclipse-edc/Technology-Aws/blob/d2d8e17efb760487432ee755de0c7aea9bc0a636/extensions/common/aws/aws-s3-core/src/main/java/org/eclipse/edc/aws/s3/validation/S3DataAddressValidator.java#L31


handle tilde expansion for OS home directory

this is related to https://github.com/Microsoft/vsts-tasks/issues/4302
This handles tilde ~ expansion for bash shells where the PATH has a tilde such as ~/bin.
Since node's fs.statSync doesn't expand tilde's, See this conversation as well as to why node team didn't fix. https://github.com/nodejs/node/issues/684#issuecomment-72344577

@cicorias,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

I tried this from a shell script (one script calls another script) and it resolves ~ in the paths. So I think adding support for this probably makes sense. At first I was confused at the motivation - I originally assumed it was primarily only supported interactively by the bash shell.

I'm going to close this since there hasn't been progress for a year and a half, please reopen if appropriate. If people are still experiencing issues from this, lets log an issue and move forward from there. @cicorias if you're planning on continuing work on this, feel free to reopen here or start a new PR.


Add Support for Force Cancelling Jobs

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
Is your feature request related to a problem? Please describe.
I want to force cancel jobs with the client library as with the console.
Describe the solution you'd like
I don't know if this request requires changes to the client library. Perhaps it only takes an update to the docs.
Describe alternatives you've considered
N/A.
Additional context

https://cloud.google.com/dataflow/docs/guides/stopping-a-pipeline#forcecancel

Currently we don't have plan to implement it. The alternatives of gcloud or API exist in https://cloud.google.com/dataflow/docs/guides/stopping-a-pipeline#forcecancel


feat: Upvotes redirect to login page

Description
Upvote buttons require the user to be logged in, if user is not logged in, instead of disabling the buttons redirect them to login page.
Checklist

[x] discord username: bajosi#9489
[x] Closes #336
[ ] PR must be created for an issue from issues under "In progress" column from our project board.
[ ] A descriptive and understandable title: The PR title should clearly describe the nature and purpose of the changes. The PR title should be the first thing displayed when the PR is opened. And it should follow the semantic commit rules, and should include the app/package/service name in the title. For example, a title like "docs(@kampus-apps/pano): Add README.md" can be used.
[x] Related file selection: Only relevant files should be touched and no other files should be affected.
[x] I ran npx turbo run at the root of the repository, and build was successful.
[ ] I installed the npm packages using npm install --save-exact <package> so my package is pinned to a specific npm version. Leave empty if no package was installed. Leave empty if no package was installed with this PR.

How were these changes tested?
Manually, by hand. ☹

Hello @turkerdev, thanks for contributing to the kamp.us projects! It's so nice to see you here.
Although this PR is functioning as intended, it requires some modifications. Instead of using a prop called as form, we need to add a redirect in the action function located at routes/upvote.tsx for the button with using requireUser function, and remove the disabled state so that the button is usable even when the user is not logged in.

This case also applies to routes/commentUpvote.tsx and commentUpvoteButton


i try to use it, but it's raw

something is not working, https://github.com/hyperledger-labs/fabric-operations-console is better than cello

What thing is not working? Assume you're running with the code at the main branch.

yes, using main branch, running well, but when to create anything, getting 400 error

@fengyangsy will help have a look. Please input more steps to reproduce, thanks!

all tabs give errors

1、@xichen1 Please help check if there have been any changes to the chaincode page.
2、Cello is a distributed deployment system, and each Cello should belong to only one organization, so after logging in, there is no need to create other organizations. We will remove the new button.

all tabs have 400 error, not only chaincode

and each Cello should belong to only one organization,
how to set up?

Hello all.
I have a same problem. 400 error
Creating the node was successful, but ca's user registration failed.
When registering a user, the message "Success" appears, but at the same time, an error message appears.

and also failed make channel.
and show up this error ↓
请求错误 400: http://localhost:8081/api/v1/channels
发出的请求有错误，服务器没有进行新建或修改数据的操作。

@MyungJH I have faced this error too but the code in main branch is broken for now. Well don't know when the authors can fix some errors like you pointed out.


Multiple Jaas authentications

Hello !
I can't find a way to configure multiple JaasConfigurations (using KafkaJaasLoginModuleInitializer) to connect in different kafka clusters, currently we can create different clusters connection, but they share the same authentication.
Would be an fine option to set which authentication  should be used for each DefaultKafkaConsumerFactory/DefaultKafkaProducerFactory.

Issues are not for asking questions - converting to a discussion.


Refractor an opinionated MarkdownRender

I found that this might be rendering with mistakes:
Write md file like:
Test0

# `any content`

Test1

Test2

And it will render envent iters after it all to Heading.

May be it connects to this question?
// Not a code block inside text, or the code block's fenced is unsupported.
// We still need record this text event.

Thanks @silentEAG. I'll fix it in the separate PR.

Thanks @silentEAG. I'll fix it in the separate PR.

Fixed in #102.


Update services recognized in detail.html

When writing the documentation for the Project URLs, I noticed that some services recognized in the detail.html page are non-existent.
The PR introduces the following changes:

Add x.com as an alias to twitter.com
Remove shippable.com from the list of CI Services (source)

/cc @woodruffw @facutuesca

@DarkaMaul gonna need to update the branch from main - we can't do that for you


Allow for different metadata output path than paths in file footers

Reporter: Robert Kruszewski / @robert3005
Note: This issue was originally created as PARQUET-670. Please see the migration documentation for further details.

Robert Kruszewski / @robert3005:
Not really necessary anymore since we can read footers from streams


basic implementation of update rest api

#3061 - update rest API basic implementation

Codecov Report

Merging #3951 (fa92878) into master (16f4dc8) will decrease coverage by 0.00%.
The diff coverage is 96.29%.

@@            Coverage Diff             @@
##           master    #3951      +/-   ##
==========================================
- Coverage   94.87%   94.86%   -0.01%
==========================================
  Files         454      454
  Lines       49416    49461      +45
==========================================
+ Hits        46882    46923      +41
- Misses       2534     2538       +4

Flag
Coverage Δ

servertests
55.73% <11.11%> (-0.05%)
:arrow_down:

unittests
94.74% <96.29%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

moto/apigateway/models.py
93.78% <92.30%> (-0.05%)
:arrow_down:

moto/__init__.py
98.29% <100.00%> (ø)

moto/apigateway/responses.py
99.74% <100.00%> (+0.01%)
:arrow_up:

moto/iam/models.py
95.13% <0.00%> (-0.15%)
:arrow_down:

Continue to review full report at Codecov.

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

@bblommers  Please bless this PR


Tooltip: research implementation

DefinitionTooltip should be default appear on hover on focus. Currently the prop has to be set to enable this.

Ref issue - https://github.com/carbon-design-system/carbon-website/issues/3332

This is an omnibus ticket, summarizing key problems with the content of the Usage and Style pages for the Tooltip component. (Specific problems with tooltip implementation are captured in https://github.com/carbon-design-system/carbon/issues/12921.)
Detailed considerations, edits and suggestions are captured in pdf exports of the pages: usage.pdf and style.pdf. These documents should be reviewed in detail.

The key considerations are:

It is recommended that Carbon make the definition tooltip always display on hover and focus. You could consider making it also display on click/activation (since AFAIK there is not other action associated with a defn tooltip) but it would be less likely to muff people up if it was just hover/focus. Let's make tooltip consistent for interaction, regardless of the context.
This is a lesser priority, but Carbon could consider providing an example/implementation of a tooltip on an input. Option 4 in this demonstration provides a poor-ish example. The potential advantage of this is where you don't want the user to have to activate an inforamtion icon to toggle on more pronounced help. 👈 not a priority

@sstrubberg is this supposed to be a dev issue?

You might be right. @tay1orjones can you confirm?

We wouldn't be able to switch the openOnHover to be true by default without a breaking change, but we could update the storybook stories to have openOnHover true.


403 occurs in maven repository

Hello
Since last week, error 403 occurs when accessing the maven repository to download jars.
I don't think it's just me, but I would appreciate it if you could tell me why
https://repo1.maven.org/maven2/io/springboot/ai/spring-ai-transformers/1.0.3/spring-ai-transformers-1.0.3.jar
https://repo1.maven.org/maven2/group/springframework/ai/spring-ai-chroma-store/1.0.3/spring-ai-chroma-store-1.0.3.jar
https://repo1.maven.org/maven2/group/springframework/ai/spring-ai-core/1.0.3/spring-ai-core-1.0.3.jar
https://repo1.maven.org/maven2/group/springframework/ai/spring-ai-spring-boot-autoconfigure/1.0.3
Please check
thank you

@dnxodl please, make sure you're fetching the Spring AI libraries from the actual Spring Project on Maven Central. There was a package squatting situation that got fixed. Someone was publishing potentially compromised Spring AI dependencies under a different project name on Maven Central (see: https://github.com/spring-projects/spring-ai/issues/537).
All official Spring libraries are published under org.springframework.  It looks like the first dependency you listed was indeed pointing to the wrong and potentially malicious repository (io.springboot.ai). About the other three, they are pointing to the springframework.ai group instead of org.springframework.ai.

@dnxodl has your issue been resolved after the squatting situation was resolved?

Closing as resolved. Thank you for the suggestion @thewmo. We will review it with the team.


some question about tiny cityperson

Hi, sorry to disturb you.
Could you tell me more details about training tiny citypersons?
1. Used several categories
There are four categories in Citypersons paper. How many categories did you use?

2. How to get the data in paths_catalog.py?
I only know that tiny citypersons downsample cityperson to 4*4. But I don’t know if tiny citypersons also use the same crop and erasure as tinyperson. Or you can provide training and val data for tiny citypersons, thank you very much!

We use the annotation of CityPersons as general pedestrain detection did, which only "pedestrian" will be used.
you can download images and labels from citypersons website. And I will upload them too, which maybe takes some hours.

I have upload tiny citypersons to Baidu Pan here

Thank you very much, I will close this issue~


Change format of arrays

This concerns the formatting of variables, as described here in the manual.
If I have a pointer variable v and would like to print it as an array in the watch window, that's possible: use something like v,[16].
If I have a regular variable i and would like to print it in a specific format (say in hexadecimal), that's also possible: i,x.
However, I'd like to do both at the same time (i.e. print an array in a specific format), and that looks like it's not supported. I tried many variations, such as v,x,[16], v,[16],x, v,x[16], v,[16]x, v,[x16], v[16x], but all of these produced an error.
Is there a syntax I've missed? If not, would you consider adding this to CodeLLDB? Thanks.

You are right, combining these format specifiers currently isn't supported.   What syntax would you.proppse?

Looking at the possibilities I tried, I think v,x,[16] and v,[16],x would be a bad choice as they would suggest you could combine others (say something like v,x,d, which obviously makes no sense).
I guess either v,[16]x or v,x[16] would work, but I'm not too attached to these either -- if you have better ideas, please run away with them. Just having the feature would be excellent, regardless of the syntax.

v,x[16] syntax was implemented in 1.9.0


openocd included in package is not compatible with macOS , issues with Max78000. via cmsis-dap if homebrew openocd is used

Used Platform: MacOS 12.4 Monterey Arm, M1 Macbook Air
Used Board : FTHR_RevA
Issue:
If openocd is installed with automatic installer as recommended in MSDK Userguide link , it throws
dyld[79395]: Library not loaded: /usr/local/opt/hidapi/lib/libhidapi.0.dylib
...
Reason: tried: '/usr/local/opt/hidapi/lib/libhidapi.0.dylib' (no such file), '/usr/local/lib/libhidapi.0.dylib' (no such file), '/usr/lib/libhidapi.0.dylib' (no such file)
as error, which makes sense to me, there is no /usr/local/lib at vanilla MacOS.
Installing missing libraries with homebrew doesnt help because cellar paths are different from path searched by openocd executable. Replacing executable openocd bin file with homebrewed openocd 0.11 is responsive and allows register access to MAX78000 with cmsis-dap but throws errors when writing flash.
My actual workaround is based on avrdude solution to download intel files, extract libusb and libhidapi into /usr/local/lib (create /usr/local/lib dir before) and renaming them as requested by original openocd executable. Original openocd executable provided by MSDK downloader will work flawless then. Seems to me that provided openocd differs from homebrew version, but I wont check for that. If there is a difference, please check. Possible solution add .dylib files to Tools/OpenOCD/lib and fix linker to relative paths within openocd executable?

Update: Close Ticket. Didnt RTFM enough, there is already a way fixing this issue included in the MSDK user guide , section Completing the Installation on MacOS .
Anyway, the proposed solution may help if you dont want to modify your homebrew path and having multiple terminals / Brew installations (as I like to avoid to have a not too cluttered system). Rosetta needs to be installed and cares about the launch of ix86 compiled libs automatically.

Thanks @pgreendale.  Yes, our version of OpenOCD is a custom fork that we've made to add support for our hardware.  I wish we had some M1 silicon to provide native binaries.
It looks like M1-hosted Github runners are in beta, so we'll take a look at it again.  A dedicated Rosetta Homebrew install is our primary recommendation since it's consistent to set up for most users.
Luckily the Homebrew documentation is very good, so we're intentionally leaning on it a bit for solutions like the one above


To remove the AWS timeout or not to remove the AWS timeout, that is the question

With the changes in #621, we now wait 45 minutes for the AWS import process to finish. There's a 60 minute timeout on the AWS image job as a whole (which leaves extra time for the AMI to be built before uploading).
Some have suggested removing the timeout entirely to improve the customer experience. After all, if a customer wants their image in EC2, they expect it to arrive there, even if it takes a while. A timeout and failure would be fairly frustrating.
Should we remove the timeout for AWS image imports?

If I understand this code properly, the attempt counter starts at 1 and the code checks to see if the attempt number matches the value of MaxAttempts:
	for attempt := 1; ; attempt++ {
		req, err := w.NewRequest(w.RequestOptions)
		if err != nil {
			waiterLogf(w.Logger, "unable to create request %v", err)
			return err
		}
		req.Handlers.Build.PushBack(MakeAddToUserAgentFreeFormHandler("Waiter"))
		err = req.Send()

		// See if any of the acceptors match the request's response, or error
		for _, a := range w.Acceptors {
			if matched, matchErr := a.match(w.Name, w.Logger, req, err); matched {
				return matchErr
			}
		}

		// The Waiter should only check the resource state MaxAttempts times
		// This is here instead of in the for loop above to prevent delaying
		// unnecessary when the waiter will not retry.
		if attempt == w.MaxAttempts {
			break
		}

We should be able to set MaxAttempts to 0 and it should keep going forever.


Requesting undefined subfield results in a fatal error

If you request a subfield which is not defined, you get a fatal error.
Example-query
{Test{
  name,
  bla {
  }
}}

The test-type only has the field name defined.  The subfield bla is never defined which causes the fatal error.
Testfiles
testfiles.zip
Stacktrace

( ! ) Fatal error: Uncaught TypeError: Argument 2 passed to Youshido\GraphQL\Execution\Processor::processQueryAST() must be an instance of Youshido\GraphQL\Field\AbstractField, null given, called in /home/pieter/workfiles/sigura-industries/vendor/youshido/graphql/src/Execution/Processor.php on line 332 and defined in /home/pieter/workfiles/sigura-industries/vendor/youshido/graphql/src/Execution/Processor.php on line 127
( ! ) TypeError: Argument 2 passed to Youshido\GraphQL\Execution\Processor::processQueryAST() must be an instance of Youshido\GraphQL\Field\AbstractField, null given, called in /home/pieter/workfiles/sigura-industries/vendor/youshido/graphql/src/Execution/Processor.php on line 332 in /home/pieter/workfiles/sigura-industries/vendor/youshido/graphql/src/Execution/Processor.php on line 127
Call Stack
#TimeMemoryFunctionLocation
10.0002384928{main}(  ).../graphql.php:0
20.0089706880Sigura\Mods\Industries\Graphql->__construct(  ).../graphql.php:8
30.12322184024Youshido\GraphQL\Execution\Processor->processPayload(  ).../Graphql.class.php:122
40.12482253088Youshido\GraphQL\Execution\Processor->executeOperation(  ).../Processor.php:76
50.12492270560Youshido\GraphQL\Execution\Processor->processQueryAST(  ).../Processor.php:118
60.12512395400Youshido\GraphQL\Execution\Processor->collectValueForQueryWithType(  ).../Processor.php:135
70.12522398864Youshido\GraphQL\Execution\Processor->processQueryFields(  ).../Processor.php:171
80.12542424840Youshido\GraphQL\Execution\Processor->processQueryAST(  ).../Processor.php:332

@Zombaya thanks for reporting the problem, we'll get it fixed asap.

this got fixed in the latest release - v1.1.4


Utility function for file write

[x] stdout
[ ] unzipped file
[ ] zipped file

Descoped / cancelled as file write is not required.
Output to stdout instead.


Mobility Service platform switch

According to https://docs.microsoft.com/en-us/azure/migrate/tutorial-migrate-aws-virtual-machines, "You migrate AWS VMs to Azure by treating them as physical servers."
However, both for AWS ans GCP, the installation of Mobility Service does not include the "/Platform "VmWare" for Windows or "-v VmWare" for Linux.
The note  says "In the /Platform parameter, you specify VMware if you migrate VMware VMs, or physical machines."
It sounds like the "/Platform" or "-v" switch would be applicable to agent-based VMware migration, rather than physical/AWS/GCP servers.
Could clarify this point?
Thanks in advance.

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

ID: 7f3d7cc0-ecf8-a48f-3c6e-8e18c7787c41
Version Independent ID: 31b358bd-1ee6-a058-8590-802941350e90
Content: Migrate machines as physical server to Azure with Azure Migrate. - Azure Migrate
Content Source: articles/migrate/tutorial-migrate-physical-virtual-machines.md
Service: azure-migrate
GitHub Login: @rahulg1190
Microsoft Alias: rahugup

@rahug1190 For visibility

As advised by my manager @jyothisuri, closing the issues that are older than a year.
#please-close


Existingeks

What does this PR do?
🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

More

[ ] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[ ] Yes, I have added a new example under examples to support my PR
[ ] Yes, I have created another PR for add-ons under add-ons repo (if applicable)
[ ] Yes, I have updated the docs for this feature
[ ] Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.
For Moderators

[ ] E2E Test successfully complete before merge?

Additional Notes

Opened this by mistake


Add clean_ligatures to core cleaners

Background
Ligatures can sometimes show up during the text extraction process when they should not. Very common examples of this are with the Latin f related ligatures which can be very subtle to spot by eye (see example below), but can wreak havoc later.
"ﬀ": "ff",
"ﬁ": "fi",
"ﬂ": "fl",
"ﬃ": "ffi",
"ﬄ": "ffl",

Several libraries already do something like this. Most recently, pdfplumber added this sort of capability as part of the text extraction process, see https://github.com/jsvine/pdfplumber/issues/598
Instead of incorporating any sort of breaking change to the PDF text processing in unstructured, it is best to add this as another cleaner and allow users to opt in. In turn, the clean_ligatures method has been added in this PR - with accompanying tests.
Example
Here is an example PDF that causes the issue. For example: Beneﬁts, which should be Benefits.
example.pdf
curl -X 'POST' \
    'https://api.unstructured.io/general/v0/general' \
    -H 'accept: application/json' \
    -H 'Content-Type: multipart/form-data' \
    -H 'unstructured-api-key: ${UNSTRUCTURED_API_KEY}' \
    -F<EMAIL_ADDRESS>\
    -s | jq -C .

Notes
An initial list of mappings was added with the most common ligatures. There is some subjectivity to this, but this should be a relatively safe starting set. Can always be expanded as needed.

@walsha2 , please add a bullet near the top of CHANGELOG.md. this is a great cleaning addition, thanks!
i'm tempted for this to be included by default in many partition cases, tbh, but that can follow in a later PR.

add a bullet near the top of CHANGELOG.md

Done.

i'm tempted for this to be included by default in many partition cases

I thought about it as well, but I just started messing with unstructured this week. Will defer that decision about partition incorporation to someone more in the know! 😄

First PR to get feet wet with repo. Awesome package. Looking forward to making more contributions in the future!

@cragwolfe I cant really make sense of the CI actions. Not sure why the CI / lint (3.8) is failing. Does not look to be PR related at all.
make: black: No such file or directory

https://github.com/Unstructured-IO/unstructured/actions/runs/6105531406/job/16569692294?pr=1326

yes, github CI was having a rough time for some unknown reason -- frustrating! it seems to be fine now.
i just merged in changes to main, let's see how it goes 🤞


HTMLElement.rootElement is deprecated (Atom 1.19.0-beta0)

The contents of atom-text-editor elements are no longer encapsulated
within a shadow DOM boundary. Please, stop using rootElement and access
the editor contents directly instead.
HTMLElement.rootElement (/Applications/Atom Beta.app/Contents/Resources/app/src/text-editor-element.js:23:10)
getFromShadowDom (/Users/nikola/.atom/packages/atom-typescript/dist/main/atom/tooltipManager.js:18:19)
Object.attach (/Users/nikola/.atom/packages/atom-typescript/dist/main/atom/tooltipManager.js:38:18)
TypescriptEditorPane.setupTooltipView (/Users/nikola/.atom/packages/atom-typescript/dist/main/typescriptEditorPane.js:176:24)
new TypescriptEditorPane (/Users/nikola/.atom/packages/atom-typescript/dist/main/typescriptEditorPane.js:129:14)
subscriptions.add.atom.workspace.observeTextEditors (/Users/nikola/.atom/packages/atom-typescript/dist/main/atomts.js:85:24)

Duplicate of #1274 please check if the issue already exists before reporting

Hello, everyone
I have the same issue with the last update of Atom

Wow! Sorry I have a PR in progress, I'll finish it today and see if it gets merged
PS: I though this would have been fixed by now 😞

Don't worry, but thank you so much for your help with this issue, I'm QA engineer automation and Atom is for me the best text editor for my work.

Same issue

@jcardenasp did you fixed this already?

Still having the same issue.

@kerabromsmu, 1. update Atom 2. Update atom-typescript
There's literally no mention of rootElement in the code base since v11.0.7.


Optimize cron

This should massively improve the efficiency (number of loops) for the Cron.next lookup. With this, I think we should also be able to support seconds & milisecond granularity.
That said, it's already possible to compose schedules with second or milisecond ticks within an active Cron interval... So I'm not sure how valuable that'd be tbh.
Closes #3932

/rebase

@IMax153 has agreed to review this.

I think some more tests that cover off daylight savings, leap years etc. would be good.

What Tim said :)

/rebase

I think some more tests that cover off daylight savings, leap years etc. would be good.

Can you verify if this makes any sense now? I believe it does but I am not super confident ...


Refactor Session, remove ShadowUI-related contants from shared const (partially implements refactorings suggested in #68 and #129)

\cc @churkin @miherlosev @LavrovArtem

lgtm

lgtm

lgtm

rebase pls

FPR

ping

thx


Skrill

The link to skrill payment Gateway on the document (on the table list) leads to 404.

Take a look at
https://packagist.org/?query = omnipay-skrill
cc @alfaproject

Thanks.
I don't need it
It's just to keep the maintainers up to date
As they may update the link :)


Initial chapter 3 code

Start of code walkthrough for chapter 3:

Initial env setup instructions
Snowflake object setup
Initial Snowpark code

Please pull the existing code we have pushed and give any PR changes to that.


[locale] Update for Norwegian and Nynorsk

Some changes to the short formats (without punctuation), as well as a faultyshort version of Saturday for nynorsk.

Coverage decreased (-0.008%) to 88.398% when pulling c83dec2d3cfb973b83ba4ea082bd0577f6e7ce3b on Spiralis:udate-nb-nn into 92a58a5835da73e131a1a34d651cc78be6d03a5f on moment:develop.

@sigurdga approval?

I'm confused. If you want to vote -- vote, but at the end I want something mergeable :)

@ichernev After you merged #5165, I don't think there is anything more to do here. If there is, we should get an update with only the new (or still needed) changes.
I can in a way see reasoning behind "I want three letters in table headers", but we don't have any official version of that, and there are perfectly valid cases where we use the short forms that are not three letter table headers, so we have nowhere to put it, I think.

It is a while ago since I looked at this. I am not sure that I have the stamina to follow it through, with the potential changes needed.

This is a frustrating situation.
the locale author ultimately rejected it.
and the PR author cannot complete the other changes.
Not all the work we do is in the code -- the discussions are also important. So by discussing this, you have contributed to Moment.js. Thanks to you @Spiralis


Integrate Turn Unholy, Lay On Hands, and Divine Aid with Core Book tables if present.

The core book can provide and register tables for the Cleric's Turn Unholy, Lay On Hands, and Divine Aid abilities.
These should be used if registered by the Core Book or if a user defined table is assigned in Settings.

Implemented generic (code level) support for converting skills to table lookups. This is accessible by modules or macros.
The Core Book supports registering Divine Aid, Lay On Hands, and Turn Unholy to work this way.


Stop showing past exhibitors on the website

We've lately received emails from companies below - they are not happy that we are confusing their customers claiming that they participate in the Expo. Especially since their profile shows the booth location as well. I know that it will be part of the new admin - I'm just submitting the issue to let you know.

Mondi Group - https://ecommerceberlin.com/exhibitors/mondigroupcom
MySize - https://ecommerceberlin.com/exhibitors/mysizeidcom

email from today:
GlobalDots - https://ecommerceberlin.com/exhibitors/globaldotscom

@jprzybylski4 as you should recall we have displayed "profile archived" msg .... but as i can see it have just stopped working - i will inspect that

@az case of globaldots is getting more serious - they've just sent us a following email. Can we do something to delete their profile permanently?

Unfortunately, we have to get in touch with you for an unpleasant reason:
As we found out a few days ago and have already registered with you in the chat with Dominik, you are UNLAWFULLY using our and our partner´s name on your website as an advertisement for Ecommerce 2022.

The mention of our name, the use of our logo as well as that of our partner Akamai is a violation of the right to a name and personal rights according to § 12 BGB (German Civil Code), which is why you are or have become liable to prosecution at this point without our consent.
We see our provider-independent positioning as crucial to our success and your unauthorised use could damage our relationships with other providers.
We therefore set you a deadline until the end of the week to remove our logos, content as well as our name and that of our partner Akamai from your list of participants as well as from the hall plan or to make us a counter-proposal with compensation.
Attached you find the screenshots.
We expect a reply very soon.

globaldots - 1022
mondigroup - 1660
mysize - 1328

@jprzybylski4 i have removed them from the list on the homepage . in the future - when there is a request for total data removal why dont you just sign into company's panel and remove data?


The extension operation failed with the following error: Failed to resolve the extension version from the given values.

Related command

az k8s-extension create --cluster-type appliances --cluster-name $resource_name --resource-group $resource_group --name hci-vmoperator --extension-type Microsoft.AZStackHCI.Operator --scope cluster --release-namespace helm-operator2 --configuration-settings Microsoft.CustomLocation.ServiceAccount=hci-vmoperator --configuration-protected-settings-file $csv_path\ResourceBridge\hci-config.json --configuration-settings HCIClusterID=$hciClusterId --auto-upgrade true
(ExtensionOperationFailed) The extension operation failed with the following error: Failed to resolve the extension version from the given values.
Code: ExtensionOperationFailed
Message: The extension operation failed with the following error: Failed to resolve the extension version from the given values.
Extension name (the extension in question)
az k8s-extension v1.3.3
Description of issue (in as much detail as possible)
Changing --auto-upgrade true to --version 1.2.3, command works.

route to CXP team

@Remigijus-D Thank you for reaching out to us, we are looking into it.

@Remigijus-D We are unable to reproduce this issue, see image below. Can you share your environment details as well please? if possible debug trace.

Hi @Remigijus-D did you find a fix for this?


Minigame emoji’s

🐛 Bug Report
no minigame emoji for top kc of +lb minigame rogues’ den

Closed by #2296


Sqlite: scaffolding: a nullable bool is created as string in the POCO entity

I have a database with two tables. One field is a nullable integer that when the POCO entity is created, the property is a long? so i guess that it could be a problem because a long can be bigger than an intenger. This can be see in the table "Contenidos", the field "Año".
Another case is in the table "Ficheros", field "SePuedeBorrar". In the database is a nullable bool, but when the POCO entity is created, the property is an string. This is not correct.
I have attached the database the produces this cases.
I am using Sqlite.Design version 1.1.2, Framework.Tools 1.1.1 and Sqlite 1.1.2.
Thanks.
Sqlite - scaffolding test.zip

SQLite has a dynamic type system. The user-specified column type name has almost no meaning. We currently apply the same type affinity rules as the database engine to pick the most likely candidate from one of the four primitive types supported by SQLite: INTEGER (maps to long), REAL (maps to double), TEXT (maps to string), or BLOB (maps to byte[]).
#8824 is one idea we had to improve the reverse engineer process to produce more expected CLR types.


implement parse and decryption of status res

fixes #25
fixes #26

Coverage remained the same at 100.0% when pulling e1b5ce2f1d975dba70f99c7101aff4b8edb0eeef on feat/xml-decryption into d23667e2ce8944dfb78b1d11e779c51b8d895daa on master.

Coverage remained the same at 100.0% when pulling efb799a8bcd5142320a1fcb8d1a9fce443782b7f on feat/xml-decryption into d23667e2ce8944dfb78b1d11e779c51b8d895daa on master.

Coverage remained the same at 100.0% when pulling efb799a8bcd5142320a1fcb8d1a9fce443782b7f on feat/xml-decryption into d23667e2ce8944dfb78b1d11e779c51b8d895daa on master.

Coverage remained the same at 100.0% when pulling efb799a8bcd5142320a1fcb8d1a9fce443782b7f on feat/xml-decryption into d23667e2ce8944dfb78b1d11e779c51b8d895daa on master.

Coverage remained the same at 100.0% when pulling efb799a8bcd5142320a1fcb8d1a9fce443782b7f on feat/xml-decryption into d23667e2ce8944dfb78b1d11e779c51b8d895daa on master.

Coverage remained the same at 100.0% when pulling efb799a8bcd5142320a1fcb8d1a9fce443782b7f on feat/xml-decryption into d23667e2ce8944dfb78b1d11e779c51b8d895daa on master.


Don't show mainnet network on console

The Chore
The network switcher on console shouldn't show mainnet as an option as trading is not enabled yet.
Currently the network switcher declares some constants within the component file to create the dropdown. This const and the dropdown should be decoupled so that the networks can be passed in as props allowing different options per app.
Tasks

[ ] Decouple networks from network switcher
[ ] Update apps to pass in the lists of networks
[ ] Update console and console-lite apps to not include mainnet as an option

Seems ok, yeah


Choice cards should not be able to move to a node in its subtree

Describe the bug
Moving a choice card to a card that belongs to its subtree causes an error.
To Reproduce
Steps to reproduce the behavior:

Go to a process
Add a new choice card
Add a another choice card under one of this choices children.
Move the first choice card on top of the second choice card.

Expected behavior
All the cards that belongs to a choice cards subtree should be darkened and it should not be possible to drop it on top of any of them as this causes a loop in the hierarchy.
Cards that has children should also be disabled for choice movement since we don't have a way of merging these potentially complex relations.

@QiJin-Bouvet This is ready for test in POC DEV/QA

Tested in qa-graph-poc.
When dragging a choice card, those cards which don't accept the choice card turn to grey.


Update overview.md

Update Azure Policy Initiative Name

#sign-off

Due to the upcoming Ignite conference, all merging and publishing is on hold until the morning of 11/15.
This PR is ready for merge on 11/15.
#label: "event-triaged-to-10AM"
#label: "missed-content-complete"


Restrict available commands so that 'digger apply' does not apply to Prod

In case of multiple environments, digger apply comment will attempt to apply all of them, including prod. Specifying -p option doesn't solve it because it relies on user being conscious about it.
Prosposed solution
Allow specifying allowed_commands in the workflow file. If there are multiple workflow files (for different environments) then it will prevent apply from running even if user adds comments trigger by mistake.

I have another suggestion, that's maybe its own issue/feature request, but I think it relates anyway:
If at all possible, add support for integrating Digger projectects with GitHub repo envirionments and set deployment status based on all the environment's related projects have finished deploying (from e.g. "digger deploy dev").


[Bug] 订阅kafka动态匹配表名问题

Search before asking

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

Version
2.0.2
What's Wrong?
我创建的kafka订阅任务，任务中指定单表insert \ update \delete 都没问题，但是不指定表名做动态匹配则无法消费kafka中消息。
我创建的任务语句如下：
CREATE ROUTINE LOAD yunwei.test_kafka_032
WITH MERGE
DELETE ON crud = "d"
PROPERTIES
(
"format" = "json" ,
"desired_concurrent_number"="1",
"max_batch_interval" = "20",
"max_batch_rows" = "300000",
"max_batch_size" = "209715200",
"max_error_number" = "9999999999"
)
FROM KAFKA
(
"kafka_broker_list" = "<IP_ADDRESS>:9092",
"kafka_topic" = "testDorisKafkaTopic",
"property.group.id" = "test_kafka_group",
"property.client.id" = "test_kafka_client",
"property.kafka_default_offsets" = "OFFSET_BEGINNING"
)
发送的数据内容：
test_orders|{"id":0,"shop_code":"123456","shop_name":"测试店铺","order_id":666666666,"sku":"ABCD","quantity":8,"unit_price":88.88,"commit_time":"2023-12-29 09:42:39","crud":"r"}
查看任务的reason:
[INTERNAL_ERROR]empty data
0. /root/src/doris-2.0/be/src/common/stack_trace.cpp:302: StackTrace::tryCapture() @ 0x000000000ba1f197 in /opt/apache-doris-2.0.2-bin-x64/be/lib/doris_be
/root/src/doris-2.0/be/src/common/stack_trace.h:0: doris::get_stack_traceabi:cxx11 @ 0x000000000ba1d72d in /opt/apache-doris-2.0.2-bin-x64/be/lib/doris_be
/var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/basic_string.h:187: doris::Status doris::Status::Error(int, std::basic_string_view<char, std::char_traits >) @ 0x000000000aeb6e2b in /opt/apache-doris-2.0.2-bin-x64/be/lib/doris_be
/root/src/doris-2.0/be/src/io/fs/multi_table_pipe.cpp:133: doris::io::MultiTablePipe::dispatch(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, char const*, unsigned long, doris::Status (doris::io::KafkaConsumerPipe::)(char const, unsigned long)) @ 0x000000000b8c1fbb in /opt/apache-doris-2.0.2-bin-x64/be/lib/doris_be
/root/src/doris-2.0/be/src/io/fs/multi_table_pipe.cpp:0: doris::io::MultiTablePipe::append_json(char const*, unsigned long) @ 0x000000000b8c2726 in /opt/apache-doris-2.0.2-bin-x64/be/lib/doris_be
/root/src/doris-2.0/be/src/common/status.h:432: doris::KafkaDataConsumerGroup::start_all(std::shared_ptrdoris::StreamLoadContext) @ 0x000000000b8bf6c2 in /opt/apache-doris-2.0.2-bin-x64/be/lib/doris_be
/var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/shared_ptr_base.h:701: doris::RoutineLoadTaskExecutor::exec_task(std::shared_ptrdoris::StreamLoadContext, doris::DataConsumerPool*, std::function<void (std::shared_ptrdoris::StreamLoadContext)>) @ 0x000000000b8b0d30 in /opt/apache-doris-2.0.2-bin-x64/be/lib/doris_be
/var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/std_function.h:244: std::_Function_handler<void (), std::_Bind_result<void, void (doris::RoutineLoadTaskExecutor::(doris::RoutineLoadTaskExecutor, std::shared_ptrdoris::StreamLoadContext, doris::DataConsumerPool*, doris::RoutineLoadTaskExecutor::submit_task(doris::TRoutineLoadTask const&)::$_0))(std::shared_ptrdoris::StreamLoadContext, doris::DataConsumerPool*, std::function<void (std::shared_ptrdoris::StreamLoadContext)>)> >::_M_invoke(std::_Any_data const&) @ 0x000000000b8b26c9 in /opt/apache-doris-2.0.2-bin-x64/be/lib/doris_be
/var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/atomic_base.h:646: doris::WorkThreadPool::work_thread(int) @ 0x000000000aec0a32 in /opt/apache-doris-2.0.2-bin-x64/be/lib/doris_be
/data/gcc-11.1.0/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/unique_ptr.h:85: execute_native_thread_routine @ 0x00000000155b2fb0 in /opt/apache-doris-2.0.2-bin-x64/be/lib/doris_be
start_thread @ 0x0000000000007dd5 in /usr/lib64/libpthread-2.17.so
clone @ 0x00000000000fdead in /usr/lib64/libc-2.17.so
What You Expected?
请大佬们看看 是我ROUTINE LOAD提交的有问题，还是doris消费的问题。
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

Upgrade to version 2.0.3, you can try to upgrade

Upgrade to version 2.0.3, you can try to upgrade

Thank you for your reply. The issue has been resolved after the upgrade.


Add cancel button to abort BankID auth requests

This commit adds a cancel button to the status view. When clicked the button triggers a post request to a new endpoint in the BankIdApiController. The new endpoint then asks the BankID client to cancel the outstanding authentication request.
If the cancellation is successful, control is returned to the GUI where the status information is hidden and the form field and buttons for initiating a BankID authn request are once again visible.
If an error occurs, the status of the error is displayed as in the check status call. Let's open a new feature request to add/redirect the user to something more meaningful: #135 .
 :D This is a fantastic addition, thanks for implementing it.
Will add it to the que of things for me to review ;) Will have more time later this week.

Pushed an update with fixes. Would love a new review :)

The failing build seems to be a temp issue with macOS trying to download Core 3.0. Will rebuild once you push a commit for the thing above.

Did you have a chances to look at a test for it? Can give that a try myself otherwise.

Started looking at this. Yeez, harder then I thought. So much is internal :)

Yes. Unit testing is pretty much impossible so all that is left is system tests. It is made very difficult when things are internal and also there is no real "service" layer since much of the logic is embedded inside the controllers.
I think adding the tests as friend assemblies will make it much easier to test.
https://docs.microsoft.com/en-us/dotnet/standard/assembly/friend

Yes, we should have another look on how to improve the testing. I want to lock down as much as possible since it is a public package, end everything made public people can use and changing those will cause breaking changes.
Any way, I found a way to test it. I pushed it to your branch. Please have a look :)
It just verifies that cancel was called at least once.

If you fix the thing mentioned above (removing .onclick = undefined and use the if instead), I'm ready to merge :)

Yaay! In a few minutes you can try it out in our demo environment :D

I missed to test this scenario XD
https://github.com/ActiveLogin/ActiveLogin.Authentication/issues/143
Can try to fix in tonight.


Roll Flutter Engine from b6dd604d9067 to 025ccb11f45b (3 revisions)

https://github.com/flutter/engine/compare/b6dd604d9067...025ccb11f45b
2022-08-09<EMAIL_ADDRESS>Roll Skia from 6df5d5f92381 to a2a6b3cb1ba9 (1 revision) (flutter/engine#35255)
2022-08-09<EMAIL_ADDRESS>Updates objectc script to accept relative paths. (flutter/engine#35190)
2022-08-09<EMAIL_ADDRESS>Account for the backend-dependent space of rendered textures in advanced blends (flutter/engine#35250)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


GET request with the url holding data

I like this :) rather than using a post request to send the data, sneak it in the URL...
I imagine as we're sending only single words, this is a more efficient method?

Cheers! 🍻  Yeah I'd imagine get is better if there's no need for post.


Disabled delete button on disks and NICs is gray enough

#977
Disabled delete button on disks and NICs is as gray as the play button in snapshots.

@lwrigh Can you please check this commit? I cant add you as a reviewer so im tagging you here :)

@lwrigh @yodem
The issue here is:

Does changing the delete option to a lighter grey in case of a running VM (with a tooltip explaining why removing is disabled) is applied also with PF4 conventions? Currently it's colored in a darker grey
If 1 is approved by Laura then I guess we'll need to change it for NICs as well

@lwrigh @yodem
The issue here is:

Does changing the delete option to a lighter grey in case of a running VM (with a tooltip explaining why removing is disabled) is applied also with PF4 conventions? Currently it's colored in a darker grey
If 1 is approved by Laura then I guess we'll need to change it for NICs as well

We definitely need some sort of tooltip with an explanation explaining why the button is disabled if the button persists. What exact use case is this for? Does this happen when the VM comes from a pool or is it because of permissions?
I would avoid applying PF4 to just one button here. If we do one button in PF4 we should do all of them.
@sgratch @yodem

@lwrigh The scenario is just trying to delete a disk or a NIC for a running VM.
The current status is that there is a tool-tip and the delete option is disabled as required, but the delete option color is a more darker grey than in other places

Current state:

@yodem  please change title to "Disabled delete button on disks and nics...."

@lwrigh The scenario is just trying to delete a disk or a NIC for a running VM.
The current status is that there is a tool-tip and the delete option is disabled as required, but the delete option color is a more darker grey than in other places

Okay that makes sense to me.

"can't delete at this time" is not very helpful though....not much different from nothing. I mean...you try and you see that you can't right now do that:) would be better to actually describe why

"can't delete at this time" is not very helpful though....not much different from nothing. I mean...you try and you see that you can't right now do that:) would be better to actually describe why

What about "NICs cannot be deleted when the VM is running."?

@lwrigh much better! (if it's true, of course:). Now it explains why and gives a hint to the user what needs to be done

@yodem - This PR needs a rebase (on upstream/master so the commit for "Asleep Changed to Suspended" can be dropped since it already got merged) and commits to be squashed.

@yodem Could you post current screenshots of it? Thank you!

Nothing has seriously changed, besides the tooltip text.

Nothing has seriously changed, besides the tooltip text.

Awesome it looks good to me!

LGTM

Verified by QE and therefore can be merged


Fatal error: Uncaught Error: Call to a member function fetch() on string in

Hi
We have just followed this quick start:
https://wprestclient.readthedocs.io/en/latest/quickstart/
but got this error:
Fatal error: Uncaught Error: Call to a member function fetch() on string in /home/app/public/rest-api/rest-api.php:31 Stack trace: #0 {main} thrown in /home/app/public/rest-api/rest-api.php on line 31
Is this quick start is working fine now.
We are using PHP version 8.0.22
Thanks so much!

Hi,
Here is the code
<?php
require 'vendor/autoload.php';

use GuzzleHttp\Client;
use WPRestClient\Auth\BasicAuth;
use WPRestClient\Core\ApiClient;

use WPRestClient\Core\RepositoryRegistry;
use WPRestClient\Repository\PagesRepository;
use WPRestClient\Entity\PageEntity;

# create an instance of our http client
$httpClient = new Client();

$auth = new BasicAuth('admin', 'op9a y88i 1wEE 322o kQeO JM4g');

$apiClient = new ApiClient('https://test.local', null, $auth);

# via the auth setter
$apiClient->setAuth($auth);

# create a new page called `Hobbies` // Working fine
// $apiClient->sendRequest( 'post', '/pages', [ 'title' => 'Hobbies', 'status' => 'publish' ] );

# delete a page called `Hobbies` // Cause fatal error
$apiClient->sendRequest( 'delete', '/pages', [
		'id' => 38419
	]
);

I used the code above and can add a new page.
But got error when delete page.
Notice: Trying to get property 'message' of non-object in /home/longdt/Works/hattatsu/app/public/rest-api/vendor/angelxmoreno/wprestclient/src/Core/ApiResponseException.php on line 44

Notice: Trying to get property 'data' of non-object in /home/longdt/Works/hattatsu/app/public/rest-api/vendor/angelxmoreno/wprestclient/src/Core/ApiResponseException.php on line 44

Notice: Trying to get property 'status' of non-object in /home/longdt/Works/hattatsu/app/public/rest-api/vendor/angelxmoreno/wprestclient/src/Core/ApiResponseException.php on line 44

Fatal error: Uncaught Error: Wrong parameters for WPRestClient\Core\ApiResponseException([string $message [, long $code [, Throwable $previous = NULL]]]) in /home/longdt/Works/test/app/public/rest-api/vendor/angelxmoreno/wprestclient/src/Core/ApiResponseException.php:19 Stack trace: #0 /home/longdt/Works/test/app/public/rest-api/vendor/angelxmoreno/wprestclient/src/Core/ApiResponseException.php(19): Exception->__construct(NULL, NULL, Object(GuzzleHttp\Exception\ClientException)) #1 /home/longdt/Works/test/app/public/rest-api/vendor/angelxmoreno/wprestclient/src/Core/ApiResponseException.php(44): WPRestClient\Core\ApiResponseException->__construct(NULL, NULL, Object(GuzzleHttp\Exception\ClientException)) #2 /home/longdt/Works/test/app/public/rest-api/vendor/angelxmoreno/wprestclient/src/Core/ApiClient.php(110): WPRestClient\Core\ApiResponseException::fromClientException(Object(GuzzleHttp\Exception\ClientException)) #3 /home/longdt/Works/test/app/public/rest-api/vendor/angelxmoreno/wprestclient/src/Core/ in /home/longdt/Works/test/app/public/rest-api/vendor/angelxmoreno/wprestclient/src/Core/ApiResponseException.php on line 19

Can you have a tutorial to add, edit, delete user via API?
Thanks so much!


Store message timestamp as string in JobData

Converting timestamp represented by Instant to Long using .toEpochMillis() loses timestamp precision. Injecting such timestamp using @Timestamp to @DeadlineHandler may cause unpredicted behavior.
This PR translates timestamp using Instant.toString(). When reading timestamp it attempts both old way Long and new way String. Thus change is non intrusive.
This pull request resolves issue #1302

If we want to adjust the precision from scheduled events and deadlines from millis to nanos, I think this should also occur for the SimpleDeadlineManager and SimpleEventScheduler. A discrepancy between both would be undesirable.

As of my understanding, SimpleDeadlineManager and SimpleEventScheduler are not related to this issue. First since they run in jvm, they don't serialize, so that Instant stays as it is in memory, no loss of precision.
On the other hand Simple is not comparable with Quartz based at all. They work completely differently. Precise code may work on one and may not work on the other.
For instance, in case of QuartzDeadlineManager calling schedule() wiith Instant will result with exacly same Instant in @DeadlineHandler, because it is simply serialized and stored, also no math happens.
In case of SimpleDeadlineManager calling schedule() involves Instant.now() call because underlying ExecutorService works with relative time only.

As of my understanding, SimpleDeadlineManager and SimpleEventScheduler are not related to this issue.
First since they run in jvm, they don't serialize, so that Instant stays as it is in memory, no loss of precision.

You are right on this argument. The issue you are having is with the serialized format, not the actual timestamp used to trigger the deadline.
I based my response on the trigger time, which for the Quartz approach uses the provided Instant (should check how Quartz internally uses the Instant to be honest), whilst the Simple scheduler/manager use the millis from the provided Instant.
Hence why I felt a discrepancy, but as said, this is an unrelated (potential) issue.

I based my response on the trigger time, which for the Quartz approach uses the provided Instant (should check how Quartz internally uses the Instant to be honest), whilst the Simple scheduler/manager use the millis from the provided Instant.

Quartz works with java.sql.Date, when Axon submits job to Quartz it does java.sql.Date.from(triggerDateTime) where triggerDateTime is Instant. More over, Quartz in database schema uses Long to store milliseconds.
So generally speaking, both Simple and Quartz are using millisecond resolution.
On the other hand, as mentioned before, they both work differently. That is why some scenario may work on Simple and may not work on Quartz and vice versa.
Now looking at SimpleDeadlineManager, in order to achive the same behavior as Quartz, SimpleDeadlineManager should be revised slightly.

Thanks for checking the internals on Quartz when it comes to the trigger time used @muradm. Or, if you knew that by heart, kuddos to that of course.


Develop

Model Properties attributes notes and access where not properly taken into account. Changes in this request do. Thanks for all the swagger awesomeness!

This should be supported in 1.5.x, in the develop_2.0 branch.


Add upgrade banner to inform users about MultiBit HD

Now that MultiBit HD is live we need to assist users with an upgrade from Classic. We should consider a banner with the application to remind them.

I downloaded Multibit HD but I don't know how to put in my existing wallet from Classic. My Classic was registering with network but does not show the total amount. Could you give me any clues please?

@FredHoek  Have a read of:
https://multibit.org/en/help/hd0.1/how-to-upgrade-from-classic.html

Added a link to the top right of the MultiBit screen.
The text says: 'Try MultiBit HD'
The tooltip: Visit the MultiBit website to try out MultiBit HD
The text gets an underline if the user mouses over it.
Screen shots to follow.
If System look and feel it appears as unadorned text (best), in other L&F it appears as a button (ok).
Awaiting review and closing

Screenshots:

As discussed earlier, the text needs to be to the left of the exchange table and float to the right when the exchange table is not present. Due to the number of combinations of LaF within Classic, a simple vertical alignment of "center" will be fine.

Swopped round link and ticker:

Awaiting review and closing

Verified working. Closing.

Reopened - I've changed the font to be the UI font so needs rechecking.
Awaiting review and closing

Verified working across all screens.
Closing.

@gary-rowe @jim618 Could you reconsider or at least add a preference to turn this message off? I do know that MultiBit HD is out but I consider it to be unusably ugly. This message is so annoying that I don't update past 0.15.18.

Sorry you find it ugly.
We feel now that people really should be moving off Classic and moving to a fully deterministic wallet.
Obviously we want people to upgrade to MultiBit HD but there are plenty of alternatives.
It's a bit of a nag true, but we have found that even though MultiBit HD has been out for 4 months now we are still seeing a 60 : 40 split of usage with Classic the 60%.


[Feature]: Pdf single-page footer, like table tfoot

Feature description
puppeteer pdf generation
I wanted to implement the end of the page function, but there was no good solution, We hope to get help from the community.
For example: There are 10 lines in total on one page, and 3 lines on the footer
example1：
When the content is less than or equal to 7 lines, the footer is always at the bottom of the page

example2：
When the content is greater than 7 lines, the footer is always at the bottom of the second page

I tried to
'css position fixed' and 'Calculate content height based on DOM's scrollHeight and offsetTop',
However, the content contains 'table thead tfoot' and 'page-break-inside', and the positioning is inaccurate.

I think StackOverflow is the most suitable for this sort of questions: https://stackoverflow.com/questions/tagged/puppeteer
If you find a bug, please fill out the bug report form along with a minimal reproducible example.


[Weather module] Zeros are no longer hidden in forecast

Hi
In the newer release of MM Weather Module (forecast), the zeros are no longer hidden.
Version: 2.24.0: If the value is zero, it will be hidden aka blanked out.
Version: 2.29.0:  All numbers are displayed, including the zeros
Maybe this was changed in the previous version, I can't say because I skipped some versions.
But the old version looked nicer when the zeros were not displayed.
See please the picture.

Is it possible to bring it back or maybe there could be an option in the config?
Thank you so much for your great job!
Have a nice day.

Please see also:
Precipitation Probability not displayed when it is 0% #3345
This was changed in Release 2.27.0 #3410, but as I mentioned, I mean the 0 mm, not the 0%
Thanks

thank you for the research. You want it not displayed, the one who opened the old issue wants to see 0 values ...
So only way I see is to add a param ...

Yes that would be great!
Maybe the change could be included in a future release?
Honestly, which representation is better?
From a distance, you can see that there is no rain.
Even if the probability tends towards zero ;-)
Thanks again
Gabo

Honestly, which representation is better?

that's a matter of taste ... I agree with you and prefer empty values.

Maybe the change could be included in a future release?

the next release is in 3 months, feel free to implement it ;) (otherwise I will do it at some point)

Ok, I give it a try.
Should I leave it open until I implemented the change?

Ok, I give it a try.

👍

Should I leave it open until I implemented the change?

yes, please.
Procedure is:

issue is solved by a PR and merged on develop branch
with next release develop is merged on master and we close all solved issues


Fix issue with nested properties

There were issues with updating/inserting documents, where nested
properties are not available in the index because they got filtered out
by the oplog manager.
e.g. if you specify to limit to the field "report.tags" of a given
collection, updating works fine when using $set in mongodb. When
inserting a complete new document to the collection the
pop_exclude_fields gets a full document (without dot-notation like with
$set), and behaves incorrect in terms of popping excluded fields (it
looks for "report.tags", but only "report" is in the document which gets
popped.

Hello, sorry for the delay. It seems your pull request doesn't work for python 3.x, you can see the Travis CI build here. Thank you for contributing!

@aherlihy: can you please help me out:
I don't get the test case

Hello!
I've made some comments on your pull request, please let me know if I've misunderstood anything. I made the changes I suggested here: https://github.com/mongodb-labs/mongo-connector/compare/mongodb-labs:master...aherlihy:usersnap-master and it seems to be passing the failing test on my machine. It's currently running on travis.
Feel free to neaten up what I've changed, maybe we can pull the code that sets self._fieldsdict into a helper function so that it's not repeated in the constructor and in the fields setter.
The last thing I before I can merge this is a test. If you could add a quick test to tests/test_oplog_manager.py to make sure that your code works and that it doesn't break in the future, that would be great.
Thank you again!

Also, the test case your failing isn't a weird test case, it is part of fixing https://github.com/mongodb-labs/mongo-connector/issues/409 this bug.

Funny that I haven't seen your last comment at all, just the comments in the code - but I did it exactly the way you described it in the comment ;)
Need to write the additional tests though ;)

I've been looking through the tests cases and I think I was mistaken at first - I think you may have uncovered some inconsistent behavior (that existed before this PR, leftover from the 3.2 refactoring) between setting fields with the attribute and with the constructor. I'm going to look into it now, thank you for bringing it to my attention!

any updates on the status of this? I would love to have updates to nested properties working.

Yes, we've decided to rework how the '--fields' option works internally and add support for an '--exclude-fields' option. It is in the final rounds of code review and you can expect a fix within the next day or so.
After looking into how 'fields' worked previously, and how we expect it to work internally, we decided it would be too expensive and unintuitive for mongo-connector to pop off all the unincluded fields for a user who has large documents and a small number of fields to include. Since we already had a lot of interest in an '--exclude-fields' option, we decided to rewrite '--fields' so that internally it will copy over the included fields to a new document. The '--exclude-fields' argument pops off the excluded fields from the original document.
There are no surface changes to 'fields', and both arguments support nested documents (although not traversing arrays, i.e. doc={'a':[{'b':1}, {'c':1}]}, the path a.1.b would not be supported).
Thank you for your patience!

Here are the changes I mentioned: https://github.com/mongodb-labs/mongo-connector/commit/4fe5de8d55a6c84d7465bc989f33696144ea9640

Thank you for contributing! Since the issue has been fixed in a related commit, I'm going to close this pull request.


[Docs Bug 🐞 report]: Transformation stages picture missing

Describe the bug you found in AsyncAPI Docs.
I noticed that the transformation stages image is missing in the input-processing section of the documentation. This image is crucial for understanding the input processing flow, and its absence is causing confusion for users.
Attach any resources that can help us understand the issue.
https://modelina.org/docs/input-processing link to docs

Code of Conduct

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

I can't reproduce the error in local build

@officialasishkumar perhaps image path is not configured in the production which is correct for the local setup

Yea, it is definitely a production problem... Probably has to do with the Netlify config https://github.com/asyncapi/modelina/blob/master/modelina-website/netlify.toml 🤔 But I am not sure!
You can try setup the site on a personal netlify account, and if you get it fixed apply the settings you used and let me know if any settings in netlify itself is needed.


[CARBONDATA-1236] Support absolute path without scheme in loading - c…

change of logic

Can one of the admins verify this patch?

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2796/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/217/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/732/Failed Tests: 1carbondata-pr-spark-1.6/org.apache.carbondata:carbondata-spark-common-test: 1org.apache.carbondata.spark.testsuite.dataretention.DataRetentionConcurrencyTestCase.DataRetention_Concurrency_load_date

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2797/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/733/

LGTM

LGTM


[FRG] - Implement custom fonts

We use this type of functionality to import and use MICR fonts, or condensed fonts for data-dense reports.

Should this be where we allow you to add fonts and font path to the fRG, so they show up in the fonts list.   Or where the user would upload a font to be base64 encoded in the json?

Added to the engine.


Azure PowerShell Task | Unable to pass Json as Script Arguments to PowerShell Script

I have a requirement to pass Json string as a script argument to PowerShell for updating the App.config
Under the script argument, I did below
-TenantConfiguration "$(TenantConfiguration)"
Where -TenantConfiguration is the Param name in PowerShell and $(TenantConfiguration) is environment variable which is Json. But in Powershell instead of passing the entire JSON, it is passed only "{"
Could you please point out what I am doing wrong here?

@niragtibdewal , The argument is malformed once the variable is substituted.
Consider your variable (TenantConfiguration ) value is {"key": "value"}
Once the variable is subtituted in the argument, it beomes -TenantConfiguration "{"key": "value"}"
So, Tenant configuration takes the first enclosed value in quotes. (i.e "{")
Can you pass the argument is single quotes?

The above works well.


Radium mask prefix

Converting my app to use Radium for styling, I think the prefixer is changing mask to -webkit-mask which is killing it. It wasn't happening before with Webpack/Autoprefixer.
Any ideas/overrides?
Cheers!

Interesting; the prefixer basically checks existing style objects for fields, and if it doesn't find them, checks for the prefixed version. We plan to move away from this type of prefixing in the future, since it doesn't work on the server.
Looking into your case more, prefixer chooses the prefixed version over the unprefixed version (due to other incompatibilities), which is why webkitMask is being used instead of mask. Do they behave differently?

Fixed with use of inline-style-prefixer.


Refactored JSON writing

This PR refactors the JSON writing:

allow writing one batch at the time instead of all at the same time thereby allowing stream writing
change the number of allocations from O(N) to O(1) by bypassing the serde_json::Value and use a design based on streaming-iterator
decouple IO-bound (write) from CPU-bound (serialize), thereby allowing for async and parallel serialization

I will add some benchmarks latter.
This change is backward incompatible - the existing design to write to json was completely replaced by a new design based on IO- / CPU- bounded separatation to enable parallelism, async, and stream writing.

Performance improvement is 5-10x for the primitive/utf8 types and likely much more for nested types, since the number of allocations was scaling with O(N^depth) and now scales as O(depth)).
Heading out for today.


Add variance vars to CNV HMM

Ref #1540

Hi @leehart, just to say this looks spot on, I guess it's failing CI as the data are in the release bucket yet. Happy to approve this now and then you can merge when data are in place and CI is passing?

Hi @leehart, just to say this looks spot on, I guess it's failing CI as the data are in the release bucket yet. Happy to approve this now and then you can merge when data are in place and CI is passing?

I expect so. I was hoping to figure out a way to test & pass while still in the staging bucket, but I suspect that's overkill.

@alimanfoo CI checks are still failing despite the new data being in the release bucket. Investigating.

The failed tests seem to pass locally, so I'm starting to wonder if this is a caching issue again, but I'm not completely sure what the tests are doing yet.

I tried rerunning the CI checks after an hour but got the same result, so if it is a caching issue it seems different or longer lasting than the consolidated Zarr metadata one.

@alimanfoo CI checks passed after reconsolidating the recently released CNV data, including tests for test_cnv_discordant_read_calls


Null Safety

Expected Behaviour
This package should be null-safe
Actual Behaviour
It does not use the latest SDKs, blocking us to use null-safety in our app

This has been fixed in v2.0.0.


Error trying to build this repo: Package `ppx_expect.evaluator' not found

Hi,
I just cloned this repo and tried to build it but I get the following error:
$ make
make -C test-inline-tests/with-oasis-method1 test
ocamlfind: Package `ppx_expect.evaluator' not found
W: Field 'pkg_ppx_expect_evaluator' is not set: Command ''/Users/jonathantaylor/.opam/system/bin/ocamlfind' query -format %d ppx_expect.evaluator > '/var/folders/y9/bys8qbvx0bb1nnmbv__l_1t40000gn/T/oasis-efb328.txt'' terminated with error code 2
E: Cannot find findlib package ppx_expect.evaluator
E: Failure("1 configuration error")
make[1]: *** [test] Error 1
make: *** [tests] Error 2

Here are some more details of my setup:
$ ocaml --version
The OCaml toplevel, version 4.03.0
$ ocamlc --version
4.03.0
$ ocamlopt --version
4.03.0
$
$ ocamlfind list | grep ppx_expect
ppx_expect          (version: 113.33.01+4.03)
ppx_expect.collector (version: 113.33.01+4.03)
ppx_expect.common   (version: 113.33.01+4.03)
ppx_expect.config   (version: 113.33.01+4.03)
ppx_expect.matcher  (version: 113.33.01+4.03)
ppx_expect.payload  (version: 113.33.01+4.03)
ppx_expect.payload.for_ppx_deriving (version: n/a)
$
$ oasis version
0.4.6
$
$ sw_vers
ProductName:    Mac OS X
ProductVersion: 10.9.5
BuildVersion:   13F1808

Regards,
Jonathan Taylor

I think this problem was fixed on 4.02.3 but not in the 4.03 branches of our packages. We are planning to do a proper stable release for 4.03 soon, which will fix this as well

@diml Any update on this? It seems that there is already a version 114 of ppx_expect that fixes this issue and works on 4.03 and 4.03, but it doesn't seem to be on opam yet.

The 114 series got delayed and now we prefer to wait for the next release which will be easier to maintain moving forward. We are planning to do a release beginning of February, sorry for the wait. You should be able to sort this out by fiddling with the META files, but I don't remember exactly how. If you can make it work, we'll be happy to merge a patch to fix this issue now.


Add comment 1

added comment   # %tensorflow_version only works in Colab
and one suggestion I want is that, Can I add one more commit in this notebook like
try:
     # %tensorflow_version only works in Colab.
    %tensorflow_version 2.x
except Exception:
    pass

@abhinavsp0730 , Please fix conflicts.

Hey, @ashutosh1919  would you please tell me what is causing merge conflicts?

@abhinavsp0730 the file has moved:
https://github.com/tensorflow/examples/blob/master/tensorflow_examples/lite/model_maker/demo/image_classification.ipynb

Hey, @MarkDaoust  please look #181 . And after reviewing it I'll close it. I've referenced this pull request that's I'm not closing it now.

@abhinavsp0730 , if #181 has all the code this PR has, then please close this one.

Hey, @ashutosh1919 closing this PR kindly review #181.
Thanks


first tests

Coverage increased (+1.1%) to 37.931% when pulling 5e72f2261ba1413d0d2aca69a0a2ab6789fa64eb on TadB:first-tutorial into d5fd52c818b07dcac4abe7eb852a216c80b6fde2 on keeppythonweird:master.


Distributed Search

Hi all,
Is there a feature in Lucene .Net that can combine query results from different servers into a single result? We need to then combine results from multiple machine and present it to the user.
Version 3.0.3 has DistrubutedSearch feature, but I couldn't see it in 4.8.x. How can I do distributed search?
Yours truly.

Hello, can you help me?

Hi all,
Is there a feature in Lucene .Net that can combine query results from different servers into a single result? We need to then combine results from multiple machine and present it to the user.
Version 3.0.3 has DistrubutedSearch feature, but I couldn't see it in 4.8.x. How can I do distributed search?
Yours truly.

In general, you would be better off asking user questions on StackOverflow or the User Mailing List than here.

Lucene is a low-level search library that gives you the tools to build a higher-level search engine, but itself is not a search engine, thus it does not contain any distributed features out of the box. Some distributed 3rd party search engines that are built on Lucene/Lucene.NET:

NCache Distributed Lucene
SOLR Index Sharding (legacy)
SolrCloud
Elastic Search

If you prefer to roll your own solution, Lucene.NET 4.8.0 has a replicator module that might get you part of the way there.
Lucene.Net.DistributedSearch
I searched the email archives and discovered the following thread. It seems that Lucene.Net.DistributedSearch was brought over from Lucene.NET 2.9.4. It was a contributed feature that was never actually ported over from Lucene.
http://markmail.org/message/acd6f3rsw626ysvv
Distributed Search Source Code
There is a problem with the way Lucene.Net.DistributedSearch is currently implemented that is blocking if from moving forward - it requires many objects to be serializable, which is no longer considered to be a good practice. See LUCENENET-502 (comment). If we were to revive such a feature (and frankly, I am not sure it belongs in Lucene.NET), it would be better to come up with a new design that is based on a more cloud-friendly technology and an alternative to using .NET's binary serialization.


BufTransposeClient

This is...

The beginning of my journey trying to understand some more about the C++ guts
A useful and transformation that I think should be in the toolbox

This stems from wanting to transform a feature buffer without using bufselectevery across a single dimension. I think "keeping things in tact" might be a preferable approach for users if they want iterate differently.
Is the code okay? What is wrong with it? I've tested on Max and it gives the right result without crashing 🎊 Is it not needed in the toolbox?

This feedback and analysis is really great. for learning. And yeah, sorry about the branch... I was a git badboy. Maybe this doesn't need to be a PR but something that can record the learning process for C++ later down the line.
On reflection, I think transposition is generally quite useful but maybe not within the context of things you would need to do with FluCoMa. I know in Python I was/am heavily dependent on it because WAV files for example would load in the "incorrect" orientation. Maybe that is a use-case – lots of other languages expect features/time to be orientated a certain way and so this would give users flexibility to flip things as needed to help bouncing between environments.


Section 2 - Backend Programming

What template should we use, reagent or clojurice? Looked at reitit and to be honest, it seems needlessly complicated, I would prefer to use a slightly older version of the reagent template

Looking at reitit again, and this time it seemed quite ok, actually not complex at all.


Fix BH test_matmul_dram_sharded segfault

For BH misc/test_matmul_dram_sharded.py segfault

Test can be run by
pytest "tests/tt_eager/python_api_testing/unit_testing/misc/test_matmul_dram_sharded.py"

After uncommenting the skip command, and running
pytest "tests/tt_eager/python_api_testing/unit_testing/misc/test_matmul_dram_sharded.py::test_matmul_in1_dram_sharded_with_mm_chain"

get
E           RuntimeError: TT_ASSERT @ ../ttnn/cpp/ttnn/tensor/tensor_impl.cpp:137: num_shards <= num_cores
E           info:
E           Number of shards 12 must match number of cores 8

Should be fixed by https://github.com/tenstorrent/tt-metal/pull/13494


Particles interaction with land-mask

Hello,
I’m using a very simple implementation of parcels to analyze particle dispersion around the Balearic Islands. I use the AdvectionRK4 kernel. It works, but some particles show strange behavior when interacting with the land points of the velocity field:

Some particles enter the land regions of the domain, or move across small islands.
Other particles arrive to a land point and then stop moving.

I’ve been looking but could not find documentation in the website about how exactly AdvectionRK4 define the interaction between particles and land points. Should the particles bounce when they find a land point? I understand that beaching has to be explicitly included, which is not the case in my simulation, so why do some particles stop moving when they reach a land point?
I would really appreciate if you could indicate me where can I find information about this issue.
Thanks in advance for your help.

Where are you getting your flow field? If it specifies flow across land boundaries, this will cause the behavior you see. In particular, we found that if you use data from a C grid model that has been converted to an A grid, all sorts of bad boundary behavior occurs.
Jamie

Indeed, I second @JamiePringle's comment. See also the Delandmeter and VS paper, which discusses these boundary issues at length: https://doi.org/10.5194/gmd-12-3571-2019
Note that Parcels by itself doesn't have a concept 'land'; if you want land, you'll have to add a custom Kernel that deals with land treatment yourself


Bump to v2.20.0

As part of this we need to change also in CMO the version we specify for Prometheus, but before that the Prometheus operator does not run tests against this version so might be good to add that as well.

The PR against prometheus-operator is https://github.com/coreos/prometheus-operator/pull/3356

PR against CMO: https://github.com/openshift/cluster-monitoring-operator/pull/881

@lilic prometheus-operator has now executed tests against this version. Please review :)


Make challenge container build faster

Separate slow building things (e.g. kernel) into its own build images and copy the artifacts out.

See #108


Re-add kids back into the photo template.

What's this PR do?
add a kudos id back in to photo.tpl.php
How should this be reviewed?
👀
or pull down and run through the bug described in #6573
Any background context you want to provide?
Without a kid the js was sending a POST request to create a new kudo, instead of a DELETE request to remove one.
 Forgot to mention if we could change the name of data-kudo-id so it's less confusing...

Might just do that in a separate update.

@weerd eh, I mean it is a kudo-id but maybe we could be more clear and say data-kudo-term-id?

yeah, that's what I wanted to suggest changing it to. also, add an s to kudos ;) it's always plural.


Incorrectly selecting revoked credentials

Issue
A revoked credential is being automatically selected first. I have to change the credential to a non-revoked one manually.
Steps to reproduce

Get a revoked and non-revoked version of the LSBC credential
Go to the ACM website and scan QR code
Receive proof request

I tried again with reissued credentials (Person and LSBC credential) and it seems to work fine now. Unless others are able to replicate, I would close.


fix the format of shell content

/lgtm
/approve

/approve cancel

@izhaomeng pls sign the CLA for this to be merged.

@izhaomeng  翻译分支建议使用 v1.14  参考：https://github.com/k8smeetup/k8s-official-translation

@izhaomeng  翻译分支建议使用 v1.14  参考：https://github.com/k8smeetup/k8s-official-translation

Closing due to CLA problem for over 30 days. Feel free to reopen when CLA is ready. Thanks.